Executive summary
Baeldung/scala-tutorials falls short of our standard for a template or a sample, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 47 out of 100 and is rated Adequate, and 13 of its 15 critical findings are security problems.
Production Readiness, at 32, is the weakest lens and counts most in the score. The best first step is documenting the recovery plan, worth about 7 points. Adding automated security scanning comes next, worth about 6 points. Raising Production Readiness to 52 would lift the score to about 56.
Four known security holes in the packages the code depends on can be used by attackers. Three passwords or keys are open to anyone who can read the repository, and three secrets can leak from the build pipeline. Updating the vulnerable packages, replacing each exposed password or key and limiting each secret to its own step would close these risks. Pinning each tool to an exact version would fix the pipeline tool referenced by a changeable name, and the two unsafe settings in infrastructure or container files need changing to safe values. The page that doesn't say its language needs its language set.
The product code is 17,693 lines, about €30,000 to rebuild.
If Production Readiness rose from 32 to 52, the lowest score rated Strong, the score would rise from 47 to about 56.
Fixed since the last survey: 1 finding
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Rebuild cost: about €30,000 · Estimate
| Cost to rebuild | €10,000 to €51,000, for 168 to 534 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Low, 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.7 at a score of 47. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 17,693 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 com.baeldung.enumeratum | 2 com.baeldung.pureconfig | 3 com.baeldung.reflection | 4 com.baeldung.scala.akka.httpstring | 5 com.baeldung.scala.akka_2.persistence.BankAccount | 6 com.baeldung.scala.companionobject | 7 com.baeldung.scala.implicitparameter.ImplicitParameter | 8 com.baeldung.scala.inheritance.Hierarchical | 9 com.baeldung.scala3.enum.ADTExample | 10 (global) | 11 cirisconfig.Configuration | 12 com.baeldung.pureconfig.Env | 13 com.baeldung.pureconfig.Protocol | 14 com.baeldung.scala.adt.Examples | 15 com.baeldung.scala.akka.actordiscovery | 16 com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder | 17 com.baeldung.scala.argumentparsing | 18 com.baeldung.scala.caseobject | 19 com.baeldung.scala.forcomprehension.ForComprehension | 20 com.baeldung.scala.typeclasses.TypeClassExample | 21 com.baeldung.scala.zio.httpapp.repo | 22 models | 23 com.baeldung.scala.concurrency | 24 com.baeldung.scala.exceptionhandling | 25 com.baeldung.scala.extractorobject | 26 com.baeldung.scala.kafka.intro.common | 27 com.baeldung.scala.pathdependenttypes | 28 com.baeldung.scala.scalaz.ScalazExamples | 29 com.baeldung.scala.zio | 30 com.baeldung.scala.zio.httpapp.service | 31 controllers | 32 guice.services | 33 com.baeldung.chimney.ChimneyPatcher | 34 com.baeldung.scala.akka.supervision.SupervisionApplication.Cache | 35 com.baeldung.scala.kafka.intro.consumer.common | 36 com.baeldung.scala.kafka.intro.producer.common | 37 com.baeldung.scala.zio.httpapp.app | 38 com.baeldung.chimney.ChimneyTransformers | 39 com.baeldung.scala.akka.supervision.SupervisionApplication | 40 com.baeldung.chimney |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com.baeldung.enumeratum | ||||||||||||||||||||||||||||||||||||||||
| 2 com.baeldung.pureconfig | ||||||||||||||||||||||||||||||||||||||||
| 3 com.baeldung.reflection | ||||||||||||||||||||||||||||||||||||||||
| 4 com.baeldung.scala.akka.httpstring | ||||||||||||||||||||||||||||||||||||||||
| 5 com.baeldung.scala.akka_2.persistence.BankAccount | ||||||||||||||||||||||||||||||||||||||||
| 6 com.baeldung.scala.companionobject | ||||||||||||||||||||||||||||||||||||||||
| 7 com.baeldung.scala.implicitparameter.ImplicitParameter | ||||||||||||||||||||||||||||||||||||||||
| 8 com.baeldung.scala.inheritance.Hierarchical | ||||||||||||||||||||||||||||||||||||||||
| 9 com.baeldung.scala3.enum.ADTExample | ||||||||||||||||||||||||||||||||||||||||
| 10 (global) | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 cirisconfig.Configuration | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 com.baeldung.pureconfig.Env | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 com.baeldung.pureconfig.Protocol | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 com.baeldung.scala.adt.Examples | 3 | |||||||||||||||||||||||||||||||||||||||
| 15 com.baeldung.scala.akka.actordiscovery | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 com.baeldung.scala.argumentparsing | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 com.baeldung.scala.caseobject | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 com.baeldung.scala.forcomprehension.ForComprehension | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 com.baeldung.scala.typeclasses.TypeClassExample | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 com.baeldung.scala.zio.httpapp.repo | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 22 models | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 com.baeldung.scala.concurrency | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 24 com.baeldung.scala.exceptionhandling | 3 | 7 | ||||||||||||||||||||||||||||||||||||||
| 25 com.baeldung.scala.extractorobject | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 com.baeldung.scala.kafka.intro.common | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 com.baeldung.scala.pathdependenttypes | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 com.baeldung.scala.scalaz.ScalazExamples | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 com.baeldung.scala.zio | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 com.baeldung.scala.zio.httpapp.service | 2 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 31 controllers | 2 | |||||||||||||||||||||||||||||||||||||||
| 32 guice.services | 6 | |||||||||||||||||||||||||||||||||||||||
| 33 com.baeldung.chimney.ChimneyPatcher | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 com.baeldung.scala.akka.supervision.SupervisionApplication.Cache | 5 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 35 com.baeldung.scala.kafka.intro.consumer.common | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 com.baeldung.scala.kafka.intro.producer.common | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 com.baeldung.scala.zio.httpapp.app | 3 | 3 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 com.baeldung.chimney.ChimneyTransformers | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 com.baeldung.scala.akka.supervision.SupervisionApplication | 2 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 com.baeldung.chimney | 5 | 1 | 2 | 3 |
10→8 (global) uses com.baeldung.scala.inheritance.Hierarchical✕
- Connections
- 2 pairs of types, where a type in (global) uses a type in com.baeldung.scala.inheritance.Hierarchical.
- The types involved
Area→com.baeldung.scala.inheritance.Hierarchical.AShapeArea→com.baeldung.scala.inheritance.Hierarchical.A
- Direction
- (global) uses com.baeldung.scala.inheritance.Hierarchical, so a change to com.baeldung.scala.inheritance.Hierarchical can break (global), while a change to (global) can't break com.baeldung.scala.inheritance.Hierarchical.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
11→9 cirisconfig.Configuration uses com.baeldung.scala3.enum.ADTExample✕
- Connections
- 2 pairs of types, where a type in cirisconfig.Configuration uses a type in com.baeldung.scala3.enum.ADTExample.
- The types involved
cirisconfig.Configuration.PostgresConfig2→com.baeldung.scala3.enum.ADTExample.Optioncirisconfig.Configuration.PostgresConfig3→com.baeldung.scala3.enum.ADTExample.Option
- Direction
- cirisconfig.Configuration uses com.baeldung.scala3.enum.ADTExample, so a change to com.baeldung.scala3.enum.ADTExample can break cirisconfig.Configuration, while a change to cirisconfig.Configuration can't break com.baeldung.scala3.enum.ADTExample.
- Position
- Below the diagonal: cirisconfig.Configuration uses a module listed above it, which is the healthy direction.
12→2 com.baeldung.pureconfig.Env uses com.baeldung.pureconfig✕
- Connections
- 2 pairs of types, where a type in com.baeldung.pureconfig.Env uses a type in com.baeldung.pureconfig.
- The types involved
com.baeldung.pureconfig.Env.Prod→com.baeldung.pureconfig.Envcom.baeldung.pureconfig.Env.Test→com.baeldung.pureconfig.Env
- Direction
- com.baeldung.pureconfig.Env uses com.baeldung.pureconfig, so a change to com.baeldung.pureconfig can break com.baeldung.pureconfig.Env, while a change to com.baeldung.pureconfig.Env can't break com.baeldung.pureconfig.
- Position
- Below the diagonal: com.baeldung.pureconfig.Env uses a module listed above it, which is the healthy direction.
13→2 com.baeldung.pureconfig.Protocol uses com.baeldung.pureconfig✕
- Connections
- 2 pairs of types, where a type in com.baeldung.pureconfig.Protocol uses a type in com.baeldung.pureconfig.
- The types involved
com.baeldung.pureconfig.Protocol.Http→com.baeldung.pureconfig.Protocolcom.baeldung.pureconfig.Protocol.Https→com.baeldung.pureconfig.Protocol
- Direction
- com.baeldung.pureconfig.Protocol uses com.baeldung.pureconfig, so a change to com.baeldung.pureconfig can break com.baeldung.pureconfig.Protocol, while a change to com.baeldung.pureconfig.Protocol can't break com.baeldung.pureconfig.
- Position
- Below the diagonal: com.baeldung.pureconfig.Protocol uses a module listed above it, which is the healthy direction.
14→7 com.baeldung.scala.adt.Examples uses com.baeldung.scala.implicitparameter.ImplicitParameter✕
- Connections
- 3 pairs of types, where a type in com.baeldung.scala.adt.Examples uses a type in com.baeldung.scala.implicitparameter.ImplicitParameter.
- The types involved
com.baeldung.scala.adt.Examples.Black→com.baeldung.scala.implicitparameter.ImplicitParameter.Colorcom.baeldung.scala.adt.Examples.ChessPiece→com.baeldung.scala.implicitparameter.ImplicitParameter.Colorcom.baeldung.scala.adt.Examples.White→com.baeldung.scala.implicitparameter.ImplicitParameter.Color
- Direction
- com.baeldung.scala.adt.Examples uses com.baeldung.scala.implicitparameter.ImplicitParameter, so a change to com.baeldung.scala.implicitparameter.ImplicitParameter can break com.baeldung.scala.adt.Examples, while a change to com.baeldung.scala.adt.Examples can't break com.baeldung.scala.implicitparameter.ImplicitParameter.
- Position
- Below the diagonal: com.baeldung.scala.adt.Examples uses a module listed above it, which is the healthy direction.
15→4 com.baeldung.scala.akka.actordiscovery uses com.baeldung.scala.akka.httpstring✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.akka.actordiscovery uses a type in com.baeldung.scala.akka.httpstring.
- The types involved
com.baeldung.scala.akka.actordiscovery.MathActorDiscovery→com.baeldung.scala.akka.httpstring.App
- Direction
- com.baeldung.scala.akka.actordiscovery uses com.baeldung.scala.akka.httpstring, so a change to com.baeldung.scala.akka.httpstring can break com.baeldung.scala.akka.actordiscovery, while a change to com.baeldung.scala.akka.actordiscovery can't break com.baeldung.scala.akka.httpstring.
- Position
- Below the diagonal: com.baeldung.scala.akka.actordiscovery uses a module listed above it, which is the healthy direction.
15→5 com.baeldung.scala.akka.actordiscovery uses com.baeldung.scala.akka_2.persistence.BankAccount✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.akka.actordiscovery uses a type in com.baeldung.scala.akka_2.persistence.BankAccount.
- The types involved
com.baeldung.scala.akka.actordiscovery.Calculator→com.baeldung.scala.akka_2.persistence.BankAccount.Command
- Direction
- com.baeldung.scala.akka.actordiscovery uses com.baeldung.scala.akka_2.persistence.BankAccount, so a change to com.baeldung.scala.akka_2.persistence.BankAccount can break com.baeldung.scala.akka.actordiscovery, while a change to com.baeldung.scala.akka.actordiscovery can't break com.baeldung.scala.akka_2.persistence.BankAccount.
- Position
- Below the diagonal: com.baeldung.scala.akka.actordiscovery uses a module listed above it, which is the healthy direction.
16→5 com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder uses com.baeldung.scala.akka_2.persistence.BankAccount✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder uses a type in com.baeldung.scala.akka_2.persistence.BankAccount.
- The types involved
com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder.Encoded→com.baeldung.scala.akka_2.persistence.BankAccount.Response
- Direction
- com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder uses com.baeldung.scala.akka_2.persistence.BankAccount, so a change to com.baeldung.scala.akka_2.persistence.BankAccount can break com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder, while a change to com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder can't break com.baeldung.scala.akka_2.persistence.BankAccount.
- Position
- Below the diagonal: com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder uses a module listed above it, which is the healthy direction.
17→4 com.baeldung.scala.argumentparsing uses com.baeldung.scala.akka.httpstring✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.argumentparsing uses a type in com.baeldung.scala.akka.httpstring.
- The types involved
com.baeldung.scala.argumentparsing.Sliding→com.baeldung.scala.akka.httpstring.App
- Direction
- com.baeldung.scala.argumentparsing uses com.baeldung.scala.akka.httpstring, so a change to com.baeldung.scala.akka.httpstring can break com.baeldung.scala.argumentparsing, while a change to com.baeldung.scala.argumentparsing can't break com.baeldung.scala.akka.httpstring.
- Position
- Below the diagonal: com.baeldung.scala.argumentparsing uses a module listed above it, which is the healthy direction.
17→5 com.baeldung.scala.argumentparsing uses com.baeldung.scala.akka_2.persistence.BankAccount✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.argumentparsing uses a type in com.baeldung.scala.akka_2.persistence.BankAccount.
- The types involved
com.baeldung.scala.argumentparsing.Config→com.baeldung.scala.akka_2.persistence.BankAccount.Command
- Direction
- com.baeldung.scala.argumentparsing uses com.baeldung.scala.akka_2.persistence.BankAccount, so a change to com.baeldung.scala.akka_2.persistence.BankAccount can break com.baeldung.scala.argumentparsing, while a change to com.baeldung.scala.argumentparsing can't break com.baeldung.scala.akka_2.persistence.BankAccount.
- Position
- Below the diagonal: com.baeldung.scala.argumentparsing uses a module listed above it, which is the healthy direction.
18→4 com.baeldung.scala.caseobject uses com.baeldung.scala.akka.httpstring✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.caseobject uses a type in com.baeldung.scala.akka.httpstring.
- The types involved
com.baeldung.scala.caseobject.ObjectExample→com.baeldung.scala.akka.httpstring.App
- Direction
- com.baeldung.scala.caseobject uses com.baeldung.scala.akka.httpstring, so a change to com.baeldung.scala.akka.httpstring can break com.baeldung.scala.caseobject, while a change to com.baeldung.scala.caseobject can't break com.baeldung.scala.akka.httpstring.
- Position
- Below the diagonal: com.baeldung.scala.caseobject uses a module listed above it, which is the healthy direction.
19→8 com.baeldung.scala.forcomprehension.ForComprehension uses com.baeldung.scala.inheritance.Hierarchical✕
- Connections
- 2 pairs of types, where a type in com.baeldung.scala.forcomprehension.ForComprehension uses a type in com.baeldung.scala.inheritance.Hierarchical.
- The types involved
com.baeldung.scala.forcomprehension.ForComprehension.Result→com.baeldung.scala.inheritance.Hierarchical.Acom.baeldung.scala.forcomprehension.ForComprehension.Result→com.baeldung.scala.inheritance.Hierarchical.B
- Direction
- com.baeldung.scala.forcomprehension.ForComprehension uses com.baeldung.scala.inheritance.Hierarchical, so a change to com.baeldung.scala.inheritance.Hierarchical can break com.baeldung.scala.forcomprehension.ForComprehension, while a change to com.baeldung.scala.forcomprehension.ForComprehension can't break com.baeldung.scala.inheritance.Hierarchical.
- Position
- Below the diagonal: com.baeldung.scala.forcomprehension.ForComprehension uses a module listed above it, which is the healthy direction.
20→8 com.baeldung.scala.typeclasses.TypeClassExample uses com.baeldung.scala.inheritance.Hierarchical✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.typeclasses.TypeClassExample uses a type in com.baeldung.scala.inheritance.Hierarchical.
- The types involved
com.baeldung.scala.typeclasses.TypeClassExample.Printer→com.baeldung.scala.inheritance.Hierarchical.A
- Direction
- com.baeldung.scala.typeclasses.TypeClassExample uses com.baeldung.scala.inheritance.Hierarchical, so a change to com.baeldung.scala.inheritance.Hierarchical can break com.baeldung.scala.typeclasses.TypeClassExample, while a change to com.baeldung.scala.typeclasses.TypeClassExample can't break com.baeldung.scala.inheritance.Hierarchical.
- Position
- Below the diagonal: com.baeldung.scala.typeclasses.TypeClassExample uses a module listed above it, which is the healthy direction.
21→6 com.baeldung.scala.zio.httpapp.repo uses com.baeldung.scala.companionobject✕
- Connections
- 2 pairs of types, where a type in com.baeldung.scala.zio.httpapp.repo uses a type in com.baeldung.scala.companionobject.
- The types involved
com.baeldung.scala.zio.httpapp.repo.InMemoryRecipeRepo→com.baeldung.scala.companionobject.Taskcom.baeldung.scala.zio.httpapp.repo.RecipeRepo→com.baeldung.scala.companionobject.Task
- Direction
- com.baeldung.scala.zio.httpapp.repo uses com.baeldung.scala.companionobject, so a change to com.baeldung.scala.companionobject can break com.baeldung.scala.zio.httpapp.repo, while a change to com.baeldung.scala.zio.httpapp.repo can't break com.baeldung.scala.companionobject.
- Position
- Below the diagonal: com.baeldung.scala.zio.httpapp.repo uses a module listed above it, which is the healthy direction.
21→9 com.baeldung.scala.zio.httpapp.repo uses com.baeldung.scala3.enum.ADTExample✕
- Connections
- 2 pairs of types, where a type in com.baeldung.scala.zio.httpapp.repo uses a type in com.baeldung.scala3.enum.ADTExample.
- The types involved
com.baeldung.scala.zio.httpapp.repo.InMemoryRecipeRepo→com.baeldung.scala3.enum.ADTExample.Optioncom.baeldung.scala.zio.httpapp.repo.RecipeRepo→com.baeldung.scala3.enum.ADTExample.Option
- Direction
- com.baeldung.scala.zio.httpapp.repo uses com.baeldung.scala3.enum.ADTExample, so a change to com.baeldung.scala3.enum.ADTExample can break com.baeldung.scala.zio.httpapp.repo, while a change to com.baeldung.scala.zio.httpapp.repo can't break com.baeldung.scala3.enum.ADTExample.
- Position
- Below the diagonal: com.baeldung.scala.zio.httpapp.repo uses a module listed above it, which is the healthy direction.
21→37 com.baeldung.scala.zio.httpapp.repo uses com.baeldung.scala.zio.httpapp.app part of a loop✕
- Connections
- 2 pairs of types, where a type in com.baeldung.scala.zio.httpapp.repo uses a type in com.baeldung.scala.zio.httpapp.app.
- The types involved
com.baeldung.scala.zio.httpapp.repo.InMemoryRecipeRepo→com.baeldung.scala.zio.httpapp.app.Recipecom.baeldung.scala.zio.httpapp.repo.RecipeRepo→com.baeldung.scala.zio.httpapp.app.Recipe
- Direction
- com.baeldung.scala.zio.httpapp.repo uses com.baeldung.scala.zio.httpapp.app, so a change to com.baeldung.scala.zio.httpapp.app can break com.baeldung.scala.zio.httpapp.repo, while a change to com.baeldung.scala.zio.httpapp.repo can't break com.baeldung.scala.zio.httpapp.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→9 models uses com.baeldung.scala3.enum.ADTExample✕
- Connections
- 1 pair of types, where a type in models uses a type in com.baeldung.scala3.enum.ADTExample.
- The types involved
models.InputFormWithConstraints→com.baeldung.scala3.enum.ADTExample.Option
- Direction
- models uses com.baeldung.scala3.enum.ADTExample, so a change to com.baeldung.scala3.enum.ADTExample can break models, while a change to models can't break com.baeldung.scala3.enum.ADTExample.
- Position
- Below the diagonal: models uses a module listed above it, which is the healthy direction.
23→4 com.baeldung.scala.concurrency uses com.baeldung.scala.akka.httpstring✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.concurrency uses a type in com.baeldung.scala.akka.httpstring.
- The types involved
com.baeldung.scala.concurrency.FutureAndPromiseApp→com.baeldung.scala.akka.httpstring.App
- Direction
- com.baeldung.scala.concurrency uses com.baeldung.scala.akka.httpstring, so a change to com.baeldung.scala.akka.httpstring can break com.baeldung.scala.concurrency, while a change to com.baeldung.scala.concurrency can't break com.baeldung.scala.akka.httpstring.
- Position
- Below the diagonal: com.baeldung.scala.concurrency uses a module listed above it, which is the healthy direction.
23→11 com.baeldung.scala.concurrency uses cirisconfig.Configuration✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.concurrency uses a type in cirisconfig.Configuration.
- The types involved
com.baeldung.scala.concurrency.ScalaAndPromise→cirisconfig.Configuration.Password
- Direction
- com.baeldung.scala.concurrency uses cirisconfig.Configuration, so a change to cirisconfig.Configuration can break com.baeldung.scala.concurrency, while a change to com.baeldung.scala.concurrency can't break cirisconfig.Configuration.
- Position
- Below the diagonal: com.baeldung.scala.concurrency uses a module listed above it, which is the healthy direction.
23→14 com.baeldung.scala.concurrency uses com.baeldung.scala.adt.Examples✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.concurrency uses a type in com.baeldung.scala.adt.Examples.
- The types involved
com.baeldung.scala.concurrency.ScalaAndPromise→com.baeldung.scala.adt.Examples.Name
- Direction
- com.baeldung.scala.concurrency uses com.baeldung.scala.adt.Examples, so a change to com.baeldung.scala.adt.Examples can break com.baeldung.scala.concurrency, while a change to com.baeldung.scala.concurrency can't break com.baeldung.scala.adt.Examples.
- Position
- Below the diagonal: com.baeldung.scala.concurrency uses a module listed above it, which is the healthy direction.
23→22 com.baeldung.scala.concurrency uses models✕
- Connections
- 2 pairs of types, where a type in com.baeldung.scala.concurrency uses a type in models.
- The types involved
com.baeldung.scala.concurrency.FutureAndPromiseApp→models.Usercom.baeldung.scala.concurrency.ScalaAndPromise→models.User
- Direction
- com.baeldung.scala.concurrency uses models, so a change to models can break com.baeldung.scala.concurrency, while a change to com.baeldung.scala.concurrency can't break models.
- Position
- Below the diagonal: com.baeldung.scala.concurrency uses a module listed above it, which is the healthy direction.
24→9 com.baeldung.scala.exceptionhandling uses com.baeldung.scala3.enum.ADTExample✕
- Connections
- 3 pairs of types, where a type in com.baeldung.scala.exceptionhandling uses a type in com.baeldung.scala3.enum.ADTExample.
- The types involved
com.baeldung.scala.exceptionhandling.ExceptionHandling→com.baeldung.scala3.enum.ADTExample.Optioncom.baeldung.scala.exceptionhandling.HandlingWithOption→com.baeldung.scala3.enum.ADTExample.Optioncom.baeldung.scala.exceptionhandling.HandlingWithTryOption→com.baeldung.scala3.enum.ADTExample.Option
- Direction
- com.baeldung.scala.exceptionhandling uses com.baeldung.scala3.enum.ADTExample, so a change to com.baeldung.scala3.enum.ADTExample can break com.baeldung.scala.exceptionhandling, while a change to com.baeldung.scala.exceptionhandling can't break com.baeldung.scala3.enum.ADTExample.
- Position
- Below the diagonal: com.baeldung.scala.exceptionhandling uses a module listed above it, which is the healthy direction.
24→22 com.baeldung.scala.exceptionhandling uses models✕
- Connections
- 7 pairs of types, where a type in com.baeldung.scala.exceptionhandling uses a type in models.
- The types involved
com.baeldung.scala.exceptionhandling.HandlingWithEither→models.Usercom.baeldung.scala.exceptionhandling.HandlingWithMonadError→models.Usercom.baeldung.scala.exceptionhandling.HandlingWithOption→models.Usercom.baeldung.scala.exceptionhandling.HandlingWithTry→models.Usercom.baeldung.scala.exceptionhandling.HandlingWithTryOption→models.Usercom.baeldung.scala.exceptionhandling.HandlingWithValidated→models.Usercom.baeldung.scala.exceptionhandling.LegacyService→models.User
- Direction
- com.baeldung.scala.exceptionhandling uses models, so a change to models can break com.baeldung.scala.exceptionhandling, while a change to com.baeldung.scala.exceptionhandling can't break models.
- Position
- Below the diagonal: com.baeldung.scala.exceptionhandling uses a module listed above it, which is the healthy direction.
25→4 com.baeldung.scala.extractorobject uses com.baeldung.scala.akka.httpstring✕
- Connections
- 2 pairs of types, where a type in com.baeldung.scala.extractorobject uses a type in com.baeldung.scala.akka.httpstring.
- The types involved
com.baeldung.scala.extractorobject.RequestApp→com.baeldung.scala.akka.httpstring.Appcom.baeldung.scala.extractorobject.UserMainApp→com.baeldung.scala.akka.httpstring.App
- Direction
- com.baeldung.scala.extractorobject uses com.baeldung.scala.akka.httpstring, so a change to com.baeldung.scala.akka.httpstring can break com.baeldung.scala.extractorobject, while a change to com.baeldung.scala.extractorobject can't break com.baeldung.scala.akka.httpstring.
- Position
- Below the diagonal: com.baeldung.scala.extractorobject uses a module listed above it, which is the healthy direction.
25→9 com.baeldung.scala.extractorobject uses com.baeldung.scala3.enum.ADTExample✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.extractorobject uses a type in com.baeldung.scala3.enum.ADTExample.
- The types involved
com.baeldung.scala.extractorobject.UserMainApp→com.baeldung.scala3.enum.ADTExample.Option
- Direction
- com.baeldung.scala.extractorobject uses com.baeldung.scala3.enum.ADTExample, so a change to com.baeldung.scala3.enum.ADTExample can break com.baeldung.scala.extractorobject, while a change to com.baeldung.scala.extractorobject can't break com.baeldung.scala3.enum.ADTExample.
- Position
- Below the diagonal: com.baeldung.scala.extractorobject uses a module listed above it, which is the healthy direction.
25→22 com.baeldung.scala.extractorobject uses models✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.extractorobject uses a type in models.
- The types involved
com.baeldung.scala.extractorobject.UserMainApp→models.User
- Direction
- com.baeldung.scala.extractorobject uses models, so a change to models can break com.baeldung.scala.extractorobject, while a change to com.baeldung.scala.extractorobject can't break models.
- Position
- Below the diagonal: com.baeldung.scala.extractorobject uses a module listed above it, which is the healthy direction.
26→17 com.baeldung.scala.kafka.intro.common uses com.baeldung.scala.argumentparsing✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.kafka.intro.common uses a type in com.baeldung.scala.argumentparsing.
- The types involved
com.baeldung.scala.kafka.intro.common.SerdeConfig→com.baeldung.scala.argumentparsing.Config
- Direction
- com.baeldung.scala.kafka.intro.common uses com.baeldung.scala.argumentparsing, so a change to com.baeldung.scala.argumentparsing can break com.baeldung.scala.kafka.intro.common, while a change to com.baeldung.scala.kafka.intro.common can't break com.baeldung.scala.argumentparsing.
- Position
- Below the diagonal: com.baeldung.scala.kafka.intro.common uses a module listed above it, which is the healthy direction.
27→4 com.baeldung.scala.pathdependenttypes uses com.baeldung.scala.akka.httpstring✕
- Connections
- 2 pairs of types, where a type in com.baeldung.scala.pathdependenttypes uses a type in com.baeldung.scala.akka.httpstring.
- The types involved
com.baeldung.scala.pathdependenttypes.AwardPunishmentDiscipline→com.baeldung.scala.akka.httpstring.Appcom.baeldung.scala.pathdependenttypes.PathDependentTypeInnerClasses→com.baeldung.scala.akka.httpstring.App
- Direction
- com.baeldung.scala.pathdependenttypes uses com.baeldung.scala.akka.httpstring, so a change to com.baeldung.scala.akka.httpstring can break com.baeldung.scala.pathdependenttypes, while a change to com.baeldung.scala.pathdependenttypes can't break com.baeldung.scala.akka.httpstring.
- Position
- Below the diagonal: com.baeldung.scala.pathdependenttypes uses a module listed above it, which is the healthy direction.
27→9 com.baeldung.scala.pathdependenttypes uses com.baeldung.scala3.enum.ADTExample✕
- Connections
- 2 pairs of types, where a type in com.baeldung.scala.pathdependenttypes uses a type in com.baeldung.scala3.enum.ADTExample.
- The types involved
com.baeldung.scala.pathdependenttypes.Database→com.baeldung.scala3.enum.ADTExample.Optioncom.baeldung.scala.pathdependenttypes.Operations→com.baeldung.scala3.enum.ADTExample.Option
- Direction
- com.baeldung.scala.pathdependenttypes uses com.baeldung.scala3.enum.ADTExample, so a change to com.baeldung.scala3.enum.ADTExample can break com.baeldung.scala.pathdependenttypes, while a change to com.baeldung.scala.pathdependenttypes can't break com.baeldung.scala3.enum.ADTExample.
- Position
- Below the diagonal: com.baeldung.scala.pathdependenttypes uses a module listed above it, which is the healthy direction.
27→15 com.baeldung.scala.pathdependenttypes uses com.baeldung.scala.akka.actordiscovery✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.pathdependenttypes uses a type in com.baeldung.scala.akka.actordiscovery.
- The types involved
com.baeldung.scala.pathdependenttypes.Database→com.baeldung.scala.akka.actordiscovery.Operations
- Direction
- com.baeldung.scala.pathdependenttypes uses com.baeldung.scala.akka.actordiscovery, so a change to com.baeldung.scala.akka.actordiscovery can break com.baeldung.scala.pathdependenttypes, while a change to com.baeldung.scala.pathdependenttypes can't break com.baeldung.scala.akka.actordiscovery.
- Position
- Below the diagonal: com.baeldung.scala.pathdependenttypes uses a module listed above it, which is the healthy direction.
28→20 com.baeldung.scala.scalaz.ScalazExamples uses com.baeldung.scala.typeclasses.TypeClassExample✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.scalaz.ScalazExamples uses a type in com.baeldung.scala.typeclasses.TypeClassExample.
- The types involved
com.baeldung.scala.scalaz.ScalazExamples.scoreOrdered→com.baeldung.scala.typeclasses.TypeClassExample.Score
- Direction
- com.baeldung.scala.scalaz.ScalazExamples uses com.baeldung.scala.typeclasses.TypeClassExample, so a change to com.baeldung.scala.typeclasses.TypeClassExample can break com.baeldung.scala.scalaz.ScalazExamples, while a change to com.baeldung.scala.scalaz.ScalazExamples can't break com.baeldung.scala.typeclasses.TypeClassExample.
- Position
- Below the diagonal: com.baeldung.scala.scalaz.ScalazExamples uses a module listed above it, which is the healthy direction.
28→22 com.baeldung.scala.scalaz.ScalazExamples uses models✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.scalaz.ScalazExamples uses a type in models.
- The types involved
com.baeldung.scala.scalaz.ScalazExamples.scoreOrdered→models.Order
- Direction
- com.baeldung.scala.scalaz.ScalazExamples uses models, so a change to models can break com.baeldung.scala.scalaz.ScalazExamples, while a change to com.baeldung.scala.scalaz.ScalazExamples can't break models.
- Position
- Below the diagonal: com.baeldung.scala.scalaz.ScalazExamples uses a module listed above it, which is the healthy direction.
29→22 com.baeldung.scala.zio uses models✕
- Connections
- 2 pairs of types, where a type in com.baeldung.scala.zio uses a type in models.
- The types involved
com.baeldung.scala.zio.AsynchronousAPI→models.Usercom.baeldung.scala.zio.LegacyAPI→models.User
- Direction
- com.baeldung.scala.zio uses models, so a change to models can break com.baeldung.scala.zio, while a change to com.baeldung.scala.zio can't break models.
- Position
- Below the diagonal: com.baeldung.scala.zio uses a module listed above it, which is the healthy direction.
30→6 com.baeldung.scala.zio.httpapp.service uses com.baeldung.scala.companionobject✕
- Connections
- 2 pairs of types, where a type in com.baeldung.scala.zio.httpapp.service uses a type in com.baeldung.scala.companionobject.
- The types involved
com.baeldung.scala.zio.httpapp.service.RecipeService→com.baeldung.scala.companionobject.Taskcom.baeldung.scala.zio.httpapp.service.RecipeServiceImpl→com.baeldung.scala.companionobject.Task
- Direction
- com.baeldung.scala.zio.httpapp.service uses com.baeldung.scala.companionobject, so a change to com.baeldung.scala.companionobject can break com.baeldung.scala.zio.httpapp.service, while a change to com.baeldung.scala.zio.httpapp.service can't break com.baeldung.scala.companionobject.
- Position
- Below the diagonal: com.baeldung.scala.zio.httpapp.service uses a module listed above it, which is the healthy direction.
30→9 com.baeldung.scala.zio.httpapp.service uses com.baeldung.scala3.enum.ADTExample✕
- Connections
- 2 pairs of types, where a type in com.baeldung.scala.zio.httpapp.service uses a type in com.baeldung.scala3.enum.ADTExample.
- The types involved
com.baeldung.scala.zio.httpapp.service.RecipeService→com.baeldung.scala3.enum.ADTExample.Optioncom.baeldung.scala.zio.httpapp.service.RecipeServiceImpl→com.baeldung.scala3.enum.ADTExample.Option
- Direction
- com.baeldung.scala.zio.httpapp.service uses com.baeldung.scala3.enum.ADTExample, so a change to com.baeldung.scala3.enum.ADTExample can break com.baeldung.scala.zio.httpapp.service, while a change to com.baeldung.scala.zio.httpapp.service can't break com.baeldung.scala3.enum.ADTExample.
- Position
- Below the diagonal: com.baeldung.scala.zio.httpapp.service uses a module listed above it, which is the healthy direction.
30→21 com.baeldung.scala.zio.httpapp.service uses com.baeldung.scala.zio.httpapp.repo✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.zio.httpapp.service uses a type in com.baeldung.scala.zio.httpapp.repo.
- The types involved
com.baeldung.scala.zio.httpapp.service.RecipeServiceImpl→com.baeldung.scala.zio.httpapp.repo.RecipeRepo
- Direction
- com.baeldung.scala.zio.httpapp.service uses com.baeldung.scala.zio.httpapp.repo, so a change to com.baeldung.scala.zio.httpapp.repo can break com.baeldung.scala.zio.httpapp.service, while a change to com.baeldung.scala.zio.httpapp.service can't break com.baeldung.scala.zio.httpapp.repo.
- Position
- Below the diagonal: com.baeldung.scala.zio.httpapp.service uses a module listed above it, which is the healthy direction.
30→37 com.baeldung.scala.zio.httpapp.service uses com.baeldung.scala.zio.httpapp.app part of a loop✕
- Connections
- 2 pairs of types, where a type in com.baeldung.scala.zio.httpapp.service uses a type in com.baeldung.scala.zio.httpapp.app.
- The types involved
com.baeldung.scala.zio.httpapp.service.RecipeService→com.baeldung.scala.zio.httpapp.app.Recipecom.baeldung.scala.zio.httpapp.service.RecipeServiceImpl→com.baeldung.scala.zio.httpapp.app.Recipe
- Direction
- com.baeldung.scala.zio.httpapp.service uses com.baeldung.scala.zio.httpapp.app, so a change to com.baeldung.scala.zio.httpapp.app can break com.baeldung.scala.zio.httpapp.service, while a change to com.baeldung.scala.zio.httpapp.service can't break com.baeldung.scala.zio.httpapp.app.
- 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.
31→22 controllers uses models✕
- Connections
- 2 pairs of types, where a type in controllers uses a type in models.
- The types involved
controllers.TodoListController→models.NewTodoListItemcontrollers.TodoListController→models.TodoListItem
- Direction
- controllers uses models, so a change to models can break controllers, while a change to controllers can't break models.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
32→22 guice.services uses models✕
- Connections
- 6 pairs of types, where a type in guice.services uses a type in models.
- The types involved
guice.services.BusinessOrderValidationService→models.Orderguice.services.EnterpriseOrderValidationService→models.Orderguice.services.OrderPipelineProcessor→models.Orderguice.services.OrderService→models.Orderguice.services.OrderValidationService→models.Orderguice.services.UserService→models.User
- Direction
- guice.services uses models, so a change to models can break guice.services, while a change to guice.services can't break models.
- Position
- Below the diagonal: guice.services uses a module listed above it, which is the healthy direction.
33→26 com.baeldung.chimney.ChimneyPatcher uses com.baeldung.scala.kafka.intro.common✕
- Connections
- 1 pair of types, where a type in com.baeldung.chimney.ChimneyPatcher uses a type in com.baeldung.scala.kafka.intro.common.
- The types involved
com.baeldung.chimney.ChimneyPatcher.Book→com.baeldung.scala.kafka.intro.common.Author
- Direction
- com.baeldung.chimney.ChimneyPatcher uses com.baeldung.scala.kafka.intro.common, so a change to com.baeldung.scala.kafka.intro.common can break com.baeldung.chimney.ChimneyPatcher, while a change to com.baeldung.chimney.ChimneyPatcher can't break com.baeldung.scala.kafka.intro.common.
- Position
- Below the diagonal: com.baeldung.chimney.ChimneyPatcher uses a module listed above it, which is the healthy direction.
34→5 com.baeldung.scala.akka.supervision.SupervisionApplication.Cache uses com.baeldung.scala.akka_2.persistence.BankAccount✕
- Connections
- 5 pairs of types, where a type in com.baeldung.scala.akka.supervision.SupervisionApplication.Cache uses a type in com.baeldung.scala.akka_2.persistence.BankAccount.
- The types involved
com.baeldung.scala.akka.supervision.SupervisionApplication.Cache.AdaptedFsFound→com.baeldung.scala.akka_2.persistence.BankAccount.Responsecom.baeldung.scala.akka.supervision.SupervisionApplication.Cache.AdaptedFsMiss→com.baeldung.scala.akka_2.persistence.BankAccount.Responsecom.baeldung.scala.akka.supervision.SupervisionApplication.Cache.Find→com.baeldung.scala.akka_2.persistence.BankAccount.Responsecom.baeldung.scala.akka.supervision.SupervisionApplication.Cache.Hit→com.baeldung.scala.akka_2.persistence.BankAccount.Responsecom.baeldung.scala.akka.supervision.SupervisionApplication.Cache.Miss→com.baeldung.scala.akka_2.persistence.BankAccount.Response
- Direction
- com.baeldung.scala.akka.supervision.SupervisionApplication.Cache uses com.baeldung.scala.akka_2.persistence.BankAccount, so a change to com.baeldung.scala.akka_2.persistence.BankAccount can break com.baeldung.scala.akka.supervision.SupervisionApplication.Cache, while a change to com.baeldung.scala.akka.supervision.SupervisionApplication.Cache can't break com.baeldung.scala.akka_2.persistence.BankAccount.
- Position
- Below the diagonal: com.baeldung.scala.akka.supervision.SupervisionApplication.Cache uses a module listed above it, which is the healthy direction.
34→16 com.baeldung.scala.akka.supervision.SupervisionApplication.Cache uses com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder✕
- Connections
- 3 pairs of types, where a type in com.baeldung.scala.akka.supervision.SupervisionApplication.Cache uses a type in com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder.
- The types involved
com.baeldung.scala.akka.supervision.SupervisionApplication.Cache.AdaptedFsFound→com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder.Requestcom.baeldung.scala.akka.supervision.SupervisionApplication.Cache.AdaptedFsMiss→com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder.Requestcom.baeldung.scala.akka.supervision.SupervisionApplication.Cache.Find→com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder.Request
- Direction
- com.baeldung.scala.akka.supervision.SupervisionApplication.Cache uses com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder, so a change to com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder can break com.baeldung.scala.akka.supervision.SupervisionApplication.Cache, while a change to com.baeldung.scala.akka.supervision.SupervisionApplication.Cache can't break com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder.
- Position
- Below the diagonal: com.baeldung.scala.akka.supervision.SupervisionApplication.Cache uses a module listed above it, which is the healthy direction.
34→24 com.baeldung.scala.akka.supervision.SupervisionApplication.Cache uses com.baeldung.scala.exceptionhandling✕
- Connections
- 2 pairs of types, where a type in com.baeldung.scala.akka.supervision.SupervisionApplication.Cache uses a type in com.baeldung.scala.exceptionhandling.
- The types involved
com.baeldung.scala.akka.supervision.SupervisionApplication.Cache.AdaptedFsFound→com.baeldung.scala.exceptionhandling.Resourcecom.baeldung.scala.akka.supervision.SupervisionApplication.Cache.Hit→com.baeldung.scala.exceptionhandling.Resource
- Direction
- com.baeldung.scala.akka.supervision.SupervisionApplication.Cache uses com.baeldung.scala.exceptionhandling, so a change to com.baeldung.scala.exceptionhandling can break com.baeldung.scala.akka.supervision.SupervisionApplication.Cache, while a change to com.baeldung.scala.akka.supervision.SupervisionApplication.Cache can't break com.baeldung.scala.exceptionhandling.
- Position
- Below the diagonal: com.baeldung.scala.akka.supervision.SupervisionApplication.Cache uses a module listed above it, which is the healthy direction.
35→17 com.baeldung.scala.kafka.intro.consumer.common uses com.baeldung.scala.argumentparsing✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.kafka.intro.consumer.common uses a type in com.baeldung.scala.argumentparsing.
- The types involved
com.baeldung.scala.kafka.intro.consumer.common.ConsumerConfig→com.baeldung.scala.argumentparsing.Config
- Direction
- com.baeldung.scala.kafka.intro.consumer.common uses com.baeldung.scala.argumentparsing, so a change to com.baeldung.scala.argumentparsing can break com.baeldung.scala.kafka.intro.consumer.common, while a change to com.baeldung.scala.kafka.intro.consumer.common can't break com.baeldung.scala.argumentparsing.
- Position
- Below the diagonal: com.baeldung.scala.kafka.intro.consumer.common uses a module listed above it, which is the healthy direction.
35→29 com.baeldung.scala.kafka.intro.consumer.common uses com.baeldung.scala.zio✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.kafka.intro.consumer.common uses a type in com.baeldung.scala.zio.
- The types involved
com.baeldung.scala.kafka.intro.consumer.common.ConsumerUtils→com.baeldung.scala.zio.Logging
- Direction
- com.baeldung.scala.kafka.intro.consumer.common uses com.baeldung.scala.zio, so a change to com.baeldung.scala.zio can break com.baeldung.scala.kafka.intro.consumer.common, while a change to com.baeldung.scala.kafka.intro.consumer.common can't break com.baeldung.scala.zio.
- Position
- Below the diagonal: com.baeldung.scala.kafka.intro.consumer.common uses a module listed above it, which is the healthy direction.
36→17 com.baeldung.scala.kafka.intro.producer.common uses com.baeldung.scala.argumentparsing✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.kafka.intro.producer.common uses a type in com.baeldung.scala.argumentparsing.
- The types involved
com.baeldung.scala.kafka.intro.producer.common.ProducerConfig→com.baeldung.scala.argumentparsing.Config
- Direction
- com.baeldung.scala.kafka.intro.producer.common uses com.baeldung.scala.argumentparsing, so a change to com.baeldung.scala.argumentparsing can break com.baeldung.scala.kafka.intro.producer.common, while a change to com.baeldung.scala.kafka.intro.producer.common can't break com.baeldung.scala.argumentparsing.
- Position
- Below the diagonal: com.baeldung.scala.kafka.intro.producer.common uses a module listed above it, which is the healthy direction.
36→29 com.baeldung.scala.kafka.intro.producer.common uses com.baeldung.scala.zio✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.kafka.intro.producer.common uses a type in com.baeldung.scala.zio.
- The types involved
com.baeldung.scala.kafka.intro.producer.common.ProducerUtils→com.baeldung.scala.zio.Logging
- Direction
- com.baeldung.scala.kafka.intro.producer.common uses com.baeldung.scala.zio, so a change to com.baeldung.scala.zio can break com.baeldung.scala.kafka.intro.producer.common, while a change to com.baeldung.scala.kafka.intro.producer.common can't break com.baeldung.scala.zio.
- Position
- Below the diagonal: com.baeldung.scala.kafka.intro.producer.common uses a module listed above it, which is the healthy direction.
37→5 com.baeldung.scala.zio.httpapp.app uses com.baeldung.scala.akka_2.persistence.BankAccount✕
- Connections
- 3 pairs of types, where a type in com.baeldung.scala.zio.httpapp.app uses a type in com.baeldung.scala.akka_2.persistence.BankAccount.
- The types involved
com.baeldung.scala.zio.httpapp.app.IngredientWebsocketApp→com.baeldung.scala.akka_2.persistence.BankAccount.Responsecom.baeldung.scala.zio.httpapp.app.RecipeHttpApp→com.baeldung.scala.akka_2.persistence.BankAccount.Responsecom.baeldung.scala.zio.httpapp.app.SpeedHttpApp→com.baeldung.scala.akka_2.persistence.BankAccount.Response
- Direction
- com.baeldung.scala.zio.httpapp.app uses com.baeldung.scala.akka_2.persistence.BankAccount, so a change to com.baeldung.scala.akka_2.persistence.BankAccount can break com.baeldung.scala.zio.httpapp.app, while a change to com.baeldung.scala.zio.httpapp.app can't break com.baeldung.scala.akka_2.persistence.BankAccount.
- Position
- Below the diagonal: com.baeldung.scala.zio.httpapp.app uses a module listed above it, which is the healthy direction.
37→13 com.baeldung.scala.zio.httpapp.app uses com.baeldung.pureconfig.Protocol✕
- Connections
- 3 pairs of types, where a type in com.baeldung.scala.zio.httpapp.app uses a type in com.baeldung.pureconfig.Protocol.
- The types involved
com.baeldung.scala.zio.httpapp.app.IngredientWebsocketApp→com.baeldung.pureconfig.Protocol.Httpcom.baeldung.scala.zio.httpapp.app.RecipeHttpApp→com.baeldung.pureconfig.Protocol.Httpcom.baeldung.scala.zio.httpapp.app.SpeedHttpApp→com.baeldung.pureconfig.Protocol.Http
- Direction
- com.baeldung.scala.zio.httpapp.app uses com.baeldung.pureconfig.Protocol, so a change to com.baeldung.pureconfig.Protocol can break com.baeldung.scala.zio.httpapp.app, while a change to com.baeldung.scala.zio.httpapp.app can't break com.baeldung.pureconfig.Protocol.
- Position
- Below the diagonal: com.baeldung.scala.zio.httpapp.app uses a module listed above it, which is the healthy direction.
37→16 com.baeldung.scala.zio.httpapp.app uses com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder✕
- Connections
- 3 pairs of types, where a type in com.baeldung.scala.zio.httpapp.app uses a type in com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder.
- The types involved
com.baeldung.scala.zio.httpapp.app.IngredientWebsocketApp→com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder.Requestcom.baeldung.scala.zio.httpapp.app.RecipeHttpApp→com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder.Requestcom.baeldung.scala.zio.httpapp.app.SpeedHttpApp→com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder.Request
- Direction
- com.baeldung.scala.zio.httpapp.app uses com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder, so a change to com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder can break com.baeldung.scala.zio.httpapp.app, while a change to com.baeldung.scala.zio.httpapp.app can't break com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder.
- Position
- Below the diagonal: com.baeldung.scala.zio.httpapp.app uses a module listed above it, which is the healthy direction.
37→30 com.baeldung.scala.zio.httpapp.app uses com.baeldung.scala.zio.httpapp.service✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.zio.httpapp.app uses a type in com.baeldung.scala.zio.httpapp.service.
- The types involved
com.baeldung.scala.zio.httpapp.app.RecipeHttpApp→com.baeldung.scala.zio.httpapp.service.RecipeService
- Direction
- com.baeldung.scala.zio.httpapp.app uses com.baeldung.scala.zio.httpapp.service, so a change to com.baeldung.scala.zio.httpapp.service can break com.baeldung.scala.zio.httpapp.app, while a change to com.baeldung.scala.zio.httpapp.app can't break com.baeldung.scala.zio.httpapp.service.
- Position
- Below the diagonal: com.baeldung.scala.zio.httpapp.app uses a module listed above it, which is the healthy direction.
38→9 com.baeldung.chimney.ChimneyTransformers uses com.baeldung.scala3.enum.ADTExample✕
- Connections
- 1 pair of types, where a type in com.baeldung.chimney.ChimneyTransformers uses a type in com.baeldung.scala3.enum.ADTExample.
- The types involved
com.baeldung.chimney.ChimneyTransformers.BookDTO→com.baeldung.scala3.enum.ADTExample.Option
- Direction
- com.baeldung.chimney.ChimneyTransformers uses com.baeldung.scala3.enum.ADTExample, so a change to com.baeldung.scala3.enum.ADTExample can break com.baeldung.chimney.ChimneyTransformers, while a change to com.baeldung.chimney.ChimneyTransformers can't break com.baeldung.scala3.enum.ADTExample.
- Position
- Below the diagonal: com.baeldung.chimney.ChimneyTransformers uses a module listed above it, which is the healthy direction.
38→26 com.baeldung.chimney.ChimneyTransformers uses com.baeldung.scala.kafka.intro.common✕
- Connections
- 1 pair of types, where a type in com.baeldung.chimney.ChimneyTransformers uses a type in com.baeldung.scala.kafka.intro.common.
- The types involved
com.baeldung.chimney.ChimneyTransformers.Book→com.baeldung.scala.kafka.intro.common.Author
- Direction
- com.baeldung.chimney.ChimneyTransformers uses com.baeldung.scala.kafka.intro.common, so a change to com.baeldung.scala.kafka.intro.common can break com.baeldung.chimney.ChimneyTransformers, while a change to com.baeldung.chimney.ChimneyTransformers can't break com.baeldung.scala.kafka.intro.common.
- Position
- Below the diagonal: com.baeldung.chimney.ChimneyTransformers uses a module listed above it, which is the healthy direction.
38→33 com.baeldung.chimney.ChimneyTransformers uses com.baeldung.chimney.ChimneyPatcher✕
- Connections
- 1 pair of types, where a type in com.baeldung.chimney.ChimneyTransformers uses a type in com.baeldung.chimney.ChimneyPatcher.
- The types involved
com.baeldung.chimney.ChimneyTransformers.Book→com.baeldung.chimney.ChimneyPatcher.Title
- Direction
- com.baeldung.chimney.ChimneyTransformers uses com.baeldung.chimney.ChimneyPatcher, so a change to com.baeldung.chimney.ChimneyPatcher can break com.baeldung.chimney.ChimneyTransformers, while a change to com.baeldung.chimney.ChimneyTransformers can't break com.baeldung.chimney.ChimneyPatcher.
- Position
- Below the diagonal: com.baeldung.chimney.ChimneyTransformers uses a module listed above it, which is the healthy direction.
39→5 com.baeldung.scala.akka.supervision.SupervisionApplication uses com.baeldung.scala.akka_2.persistence.BankAccount✕
- Connections
- 2 pairs of types, where a type in com.baeldung.scala.akka.supervision.SupervisionApplication uses a type in com.baeldung.scala.akka_2.persistence.BankAccount.
- The types involved
com.baeldung.scala.akka.supervision.SupervisionApplication.Cache→com.baeldung.scala.akka_2.persistence.BankAccount.Responsecom.baeldung.scala.akka.supervision.SupervisionApplication.WebServer→com.baeldung.scala.akka_2.persistence.BankAccount.Response
- Direction
- com.baeldung.scala.akka.supervision.SupervisionApplication uses com.baeldung.scala.akka_2.persistence.BankAccount, so a change to com.baeldung.scala.akka_2.persistence.BankAccount can break com.baeldung.scala.akka.supervision.SupervisionApplication, while a change to com.baeldung.scala.akka.supervision.SupervisionApplication can't break com.baeldung.scala.akka_2.persistence.BankAccount.
- Position
- Below the diagonal: com.baeldung.scala.akka.supervision.SupervisionApplication uses a module listed above it, which is the healthy direction.
39→16 com.baeldung.scala.akka.supervision.SupervisionApplication uses com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder✕
- Connections
- 2 pairs of types, where a type in com.baeldung.scala.akka.supervision.SupervisionApplication uses a type in com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder.
- The types involved
com.baeldung.scala.akka.supervision.SupervisionApplication.Cache→com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder.Requestcom.baeldung.scala.akka.supervision.SupervisionApplication.WebServer→com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder.Request
- Direction
- com.baeldung.scala.akka.supervision.SupervisionApplication uses com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder, so a change to com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder can break com.baeldung.scala.akka.supervision.SupervisionApplication, while a change to com.baeldung.scala.akka.supervision.SupervisionApplication can't break com.baeldung.scala.akka.requestresponse.Base64Application.Base64Encoder.
- Position
- Below the diagonal: com.baeldung.scala.akka.supervision.SupervisionApplication uses a module listed above it, which is the healthy direction.
39→24 com.baeldung.scala.akka.supervision.SupervisionApplication uses com.baeldung.scala.exceptionhandling✕
- Connections
- 2 pairs of types, where a type in com.baeldung.scala.akka.supervision.SupervisionApplication uses a type in com.baeldung.scala.exceptionhandling.
- The types involved
com.baeldung.scala.akka.supervision.SupervisionApplication.Cache→com.baeldung.scala.exceptionhandling.Resourcecom.baeldung.scala.akka.supervision.SupervisionApplication.File→com.baeldung.scala.exceptionhandling.Resource
- Direction
- com.baeldung.scala.akka.supervision.SupervisionApplication uses com.baeldung.scala.exceptionhandling, so a change to com.baeldung.scala.exceptionhandling can break com.baeldung.scala.akka.supervision.SupervisionApplication, while a change to com.baeldung.scala.akka.supervision.SupervisionApplication can't break com.baeldung.scala.exceptionhandling.
- Position
- Below the diagonal: com.baeldung.scala.akka.supervision.SupervisionApplication uses a module listed above it, which is the healthy direction.
39→34 com.baeldung.scala.akka.supervision.SupervisionApplication uses com.baeldung.scala.akka.supervision.SupervisionApplication.Cache✕
- Connections
- 1 pair of types, where a type in com.baeldung.scala.akka.supervision.SupervisionApplication uses a type in com.baeldung.scala.akka.supervision.SupervisionApplication.Cache.
- The types involved
com.baeldung.scala.akka.supervision.SupervisionApplication.WebServer→com.baeldung.scala.akka.supervision.SupervisionApplication.Cache.Find
- Direction
- com.baeldung.scala.akka.supervision.SupervisionApplication uses com.baeldung.scala.akka.supervision.SupervisionApplication.Cache, so a change to com.baeldung.scala.akka.supervision.SupervisionApplication.Cache can break com.baeldung.scala.akka.supervision.SupervisionApplication, while a change to com.baeldung.scala.akka.supervision.SupervisionApplication can't break com.baeldung.scala.akka.supervision.SupervisionApplication.Cache.
- Position
- Below the diagonal: com.baeldung.scala.akka.supervision.SupervisionApplication uses a module listed above it, which is the healthy direction.
40→4 com.baeldung.chimney uses com.baeldung.scala.akka.httpstring✕
- Connections
- 5 pairs of types, where a type in com.baeldung.chimney uses a type in com.baeldung.scala.akka.httpstring.
- The types involved
com.baeldung.chimney.ChimneyCodec→com.baeldung.scala.akka.httpstring.Appcom.baeldung.chimney.ChimneyIso→com.baeldung.scala.akka.httpstring.Appcom.baeldung.chimney.ChimneyPartialTransformer→com.baeldung.scala.akka.httpstring.Appcom.baeldung.chimney.ChimneyPatcher→com.baeldung.scala.akka.httpstring.Appcom.baeldung.chimney.ChimneyTransformers→com.baeldung.scala.akka.httpstring.App
- Direction
- com.baeldung.chimney uses com.baeldung.scala.akka.httpstring, so a change to com.baeldung.scala.akka.httpstring can break com.baeldung.chimney, while a change to com.baeldung.chimney can't break com.baeldung.scala.akka.httpstring.
- Position
- Below the diagonal: com.baeldung.chimney uses a module listed above it, which is the healthy direction.
40→19 com.baeldung.chimney uses com.baeldung.scala.forcomprehension.ForComprehension✕
- Connections
- 1 pair of types, where a type in com.baeldung.chimney uses a type in com.baeldung.scala.forcomprehension.ForComprehension.
- The types involved
com.baeldung.chimney.ChimneyPartialTransformer→com.baeldung.scala.forcomprehension.ForComprehension.Result
- Direction
- com.baeldung.chimney uses com.baeldung.scala.forcomprehension.ForComprehension, so a change to com.baeldung.scala.forcomprehension.ForComprehension can break com.baeldung.chimney, while a change to com.baeldung.chimney can't break com.baeldung.scala.forcomprehension.ForComprehension.
- Position
- Below the diagonal: com.baeldung.chimney uses a module listed above it, which is the healthy direction.
40→33 com.baeldung.chimney uses com.baeldung.chimney.ChimneyPatcher✕
- Connections
- 2 pairs of types, where a type in com.baeldung.chimney uses a type in com.baeldung.chimney.ChimneyPatcher.
- The types involved
com.baeldung.chimney.ChimneyPatcher→com.baeldung.chimney.ChimneyPatcher.Bookcom.baeldung.chimney.ChimneyTransformers→com.baeldung.chimney.ChimneyPatcher.Book
- Direction
- com.baeldung.chimney uses com.baeldung.chimney.ChimneyPatcher, so a change to com.baeldung.chimney.ChimneyPatcher can break com.baeldung.chimney, while a change to com.baeldung.chimney can't break com.baeldung.chimney.ChimneyPatcher.
- Position
- Below the diagonal: com.baeldung.chimney uses a module listed above it, which is the healthy direction.
40→38 com.baeldung.chimney uses com.baeldung.chimney.ChimneyTransformers✕
- Connections
- 3 pairs of types, where a type in com.baeldung.chimney uses a type in com.baeldung.chimney.ChimneyTransformers.
- The types involved
com.baeldung.chimney.ChimneyTransformers→com.baeldung.chimney.ChimneyTransformers.BookDTOcom.baeldung.chimney.ChimneyTransformers→com.baeldung.chimney.ChimneyTransformers.MyOtherTypecom.baeldung.chimney.ChimneyTransformers→com.baeldung.chimney.ChimneyTransformers.MyType
- Direction
- com.baeldung.chimney uses com.baeldung.chimney.ChimneyTransformers, so a change to com.baeldung.chimney.ChimneyTransformers can break com.baeldung.chimney, while a change to com.baeldung.chimney can't break com.baeldung.chimney.ChimneyTransformers.
- Position
- Below the diagonal: com.baeldung.chimney 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 — Event-Driven
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 9 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | High / Critical |
| A07:2025 — Authentication Failures | 4 | High / Critical |
| A05:2025 — Injection | 4 | High / Critical |
Roadmap
Top priorities: Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery; Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Migrate the remaining .js/.jsx files to TypeScript.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +7.2 pts | Medium | DR & Backup |
| Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +5.9 pts | Medium | Security & performance tooling |
| Migrate the remaining .js/.jsx files to TypeScript. | +2.7 pts | Medium | Type Safety |
| 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. | +2.7 pts | Medium | Nullable reference types |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +2.4 pts | Medium | Observability |
| Run the test suite in CI via an explicit runner step for your stack, and gate merges on it. | +2.1 pts | Medium | CI/CD gates |
| Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding. | +2.1 pts | Medium | Deployment & Rollback |
| Swallowed exception (caught, then discarded) | +1.7 pts | Medium | Exception handling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.7 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 6.3 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | IaC & Container Security: High IaC: REDACTED |
| scala-core-modules/scala-core-6/src/test/scala/com/baeldung/scala/maps/MapsUnitTest.scala | 7.3 | Near-clean | Explicit Debt: TodoComment |
| cats-effects/src/main/scala/com/baeldung/scala/catseffects/Cancellation.scala | 7.8 | Near-clean | Cognitive Complexity: Cancellation.cancelFiberDirectlySafe (cognitive 28) |
| REDACTED | 7.9 | Near-clean | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 7.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| scala-core-modules/scala-core-3/src/main/scala/com/baeldung/scala/iteratorsvsstreamsvsviews/NonStrictDataStructures.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| zio/src/main/scala/com/baeldung/scala/zio/fibers/PastaCookingFiberAppExample.scala | 8.5 | Near-clean | Cognitive Complexity: PastaCookingFiberAppExample.pastaApp (cognitive 36) |
| zio/src/main/scala/com/baeldung/scala/zio/repeatretry/RepeatSamples.scala | 8.5 | Near-clean | Cognitive Complexity: RepeatSamples.run (cognitive 22) |
| scala-2-modules/scala2-libraries/src/main/scala-2/com/baeldung/scala/pulsar4s/JsonPulsarConsumer.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| scala-core-collections-modules/scala-core-collections-2/src/main/scala/com/baeldung/scala/lazylists/SimpleLazyList.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| play-scala/dependency-injection/app/guice/services/OrderService.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (13 lines × 2) |
| README.md | 9.5 | Near-clean | Documentation Quality: Documentation: no build, run or usage example |
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 73 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 — 73 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, 103 of 119 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ 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. To have real coverage read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — 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, 431 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — 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. Not scored — 3 Maven/Gradle manifest(s) were read, stating a version for 4 dependency(ies) and leaving 2 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D19 Documentation Quality — 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — 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 a COLLECTOR gap, not an environment fault: it declares a published package (sbt-release/REDACTED), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- 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. `scala-core-modules/scala-core-8/src/main/scala/com/baeldung/scala/stackabletrait/StackableTraitExample.scala`, `scala-core-modules/scala-core-8/src/main/scala/com/baeldung/scala/stackabletrait/StackableTraitWithExplicitBaseAndCoreExample.scala`, `scala-core-modules/scala-core-fp/src/main/scala/com/baeldung/scala/freemonad/FreeMonads.scala`, `scala-core-modules/scala-core/src/main/scala-3/com/baeldung/scala/traits/Writer.scala`, `scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/intersectiontypes/BasicIntersectionType.scala`, … (+18 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Guice and MacWire, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX2 Stateful singletons — 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. Those languages run requests on shared-memory threads, so a shared instance mutated without a lock is the same defect this card counts in C#, Java, Kotlin, Python, Go, Swift, Scala, Ruby and F#, but their singleton shapes are not read yet. That is a gap in this analyzer's language reach — not a finding that the code is free of it.
- 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. User interface: 19 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. Boot: crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:5432: page.goto: net::ERR_EMPTY_RESPONSE at http://127.0.0.1:5432/ Call log: - navigating to "http://127.0.0.1:5432/", waiting until "load" .
- 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.
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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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 REDACTED (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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was PastaCookingFiberAppExample.pastaApp at 36.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with PastaCookingFiberAppExample.pastaApp (cognitive 36), Cancellation.cancelFiberDirectlySafe (cognitive 28), RepeatSamples.run (cognitive 22). — 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 4 together lifts Cognitive Complexity from 8.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
3 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with JsonPulsarConsumer.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with SimpleLazyList.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with OrderService.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
86 production modules (Maven+sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 1 module(s) off the main sequence, with abstractness counted on 72 of the 86 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 22 classes have LCOM4 above 3.
D9 · Test Distribution
1756 test methods: 1710 unit, 46 integration, 0 BDD, 0 e2e. The Scala suite contributes 1756 test case(s) across 404 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 23 of the 765 production source files in this repository: 732 are under the ~2,400-byte size floor this dimension measures over, and the remaining 10 have no attributable history left to measure.
D17 · Explicit Debt
3 deducted task-comment markers across 17693 LoC (0.0/KLoC) → score 10.0. 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 3 TodoComment finding(s) in Explicit Debt — start with MapsUnitTest.scala (2), NonStrictDataStructures.scala. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 76 document(s) read across 1 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).
D26 · Project Cohesion
1 of 33 build units (Maven, sbt) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. 1 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 14 file(s) — `play-scala/configuration-access/app/views/main.scala.html` (lines 1–7, line 14, line 15, …), `play-scala/introduction-to-play/app/views/main.scala.html` (lines 1–7, line 14, line 15, …), `play-scala/play-static-assets/app/views/index.scala.html` (lines 1–3, line 4, line 5, …), `play-scala/play-static-assets/app/views/main.scala.html` (lines 1–7, line 14, line 15, …), `play-scala/play-templates/app/views/Baeldung/index.scala.html` (line 1), … (+9 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
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).
- No action in Static Analysis (SAST) — all 1 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 (1 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
8 finding(s): 0 critical, 4 high, 4 medium, 0 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 warning-level).
D31 · IaC & Container Security
9 finding(s): 0 critical, 2 high, 6 medium, 1 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
22 of 33 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is scala-libraries/src/main/scala/com/baeldung/elasticmq/AsyncSQSClient.scala. Counted over 33 of the 765 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 22 Orphaned file finding(s) in Knowledge Freshness — start with Main.scala (3), AsyncSQSClient.scala, FreeMonads.scala. — One of this dimension's main actionable groups (22 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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 0 platform declaration(s) and 4 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
AC2 · Forms & labels
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×4) — play-scala/configuration-access/app/views/main.scala.html:10, play-scala/introduction-to-play/app/views/main.scala.html:10, play-scala/play-static-assets/app/views/main.scala.html:10, …
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — scalatra/src/main/twirl/layouts/default.scala.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 19 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
- `TodoListController` is one shared instance (Play controller: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (todoList; e.g. `todoList` in `markAsDone` at line 44). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt. — play-scala/rest-api/app/controllers/TodoListController.scala:9
What to do
- Scala: keep controllers and singletons stateless — per-request data in locals, shared data in a store — or hold the state in a thread-safe type (TrieMap, AtomicInteger/AtomicReference, a cats-effect Ref) or update it under `synchronized { }`; a flag that is only ever overwritten can be a `@volatile var`.
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
ED4 · Outbox / dual-write
- `InventoryService.saveAndPublish` writes state (`dao.saveAsync`) AND publishes an event (`kafkaProducer.publish`) as two independent side effects across separate infrastructure ports, with no shared transaction or outbox. A crash between them either loses the event (state committed, publish failed) or emits a phantom event (publish succeeded, state rolled back). Wrap both in one transaction / unit-of-work, or use a transactional outbox so the event commits atomically with the state change. — scala-test/src/main/scala/com/baeldung/scala/scalatest/mockito/InventoryService.scala:36
What to do
- Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
GD1 · Unfinished & placeholder code
- `areaByVertexes` 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. — scala-core-modules/scala-core-3/src/main/scala/com/baeldung/scala/accessmodifiers/Star.scala:20
- `doSomething` 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. (×2) — scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/quitesyntax/Example.scala:62, scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/quitesyntax/Example.scala:71
- `apply` 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. (×2) — scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/quitesyntax/Example.scala:65, scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/quitesyntax/Example.scala:75
- `login` 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. — zio/src/main/scala/com/baeldung/scala/zio/AsynchronousProgrammingExample.scala:10
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
- `areaByVertexes` 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. — scala-core-modules/scala-core-3/src/main/scala/com/baeldung/scala/accessmodifiers/Star.scala:20
- `doSomething` 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. (×2) — scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/quitesyntax/Example.scala:62, scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/quitesyntax/Example.scala:71
- `apply` 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. (×2) — scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/quitesyntax/Example.scala:65, scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/quitesyntax/Example.scala:75
- `anyVal` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — scala-lang-modules/scala-lang/src/main/scala/com/baeldung/scala/typehierarchy/TypeHierarchy.scala:6
- `anyRef` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — scala-lang-modules/scala-lang/src/main/scala/com/baeldung/scala/typehierarchy/TypeHierarchy.scala:8
- `login` 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. — zio/src/main/scala/com/baeldung/scala/zio/AsynchronousProgrammingExample.scala:10
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×6) — scala-core-collections-modules/scala-core-collections-4/src/test/scala/com/baeldung/scala/filtertakewhile/FilterAndTakeWhileUnitTest.scala:20, scala-libraries-testing/src/test/scala/com/baeldung/munit/MUnitTest.scala:34, scala-test-2/src/test/scala/com/baeldung/scala/conditionaltests/ConditionalUnitTest.scala:59, …
- `equalTypes` has an empty body — confirm it's an intentional no-op and not an unfinished method. — scala-core-modules/scala-core-4/src/main/scala/com/baeldung/scala/pathdependenttypes/PathDependentTypeInnerClasses.scala:8
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 18 of 39 project(s) that lack one — worth up to 0.9 pts.
M3 · Folder & project structure
P1 · CI/CD gates
- A CI pipeline exists but no test-runner invocation (your stack's test command, or a test job) was found — changes may merge without the suite running.
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P2 · Observability
- Only 3/17 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `sbt-release`, `sbt-standalone`, `scala-2-modules/scala2-libraries/src/finch/hello-world`, `scala-core-modules/scala-core`, `scala-graalvm/scala-graalvm-http-app` and 9 more.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 575 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
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. — specialized-benchmark/src/main/scala-2/com/baeldung/scala/Benchmark.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.
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 19 use(s) across 21,329 production line(s) (~0.9/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
- Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
- Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.
PF3 · Async & latency hygiene
- `queryUserFromDB` is async and calls Thread.sleep — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — scala-2-modules/scala2-libraries/src/main/scala-2/com/baeldung/cache/service/AsyncQueryMemoizeService.scala:49
- `queryResultFuture` is async and calls Thread.sleep — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — scala-2-modules/scala2-libraries/src/main/scala-2/com/baeldung/cache/service/ScalaCacheCachingBlock.scala:51
- `sampleFuture` is async and calls Thread.sleep — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — scala-core-modules/scala-core-2/src/main/scala/com/baeldung/scala/concurrency/FutureAndPromise.scala:13
- `exist` is async and calls Thread.sleep — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — scala-core-modules/scala-core-2/src/main/scala/com/baeldung/scala/concurrency/FutureAndPromise.scala:30
- `avatar` is async and calls Thread.sleep — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — scala-core-modules/scala-core-2/src/main/scala/com/baeldung/scala/concurrency/FutureAndPromise.scala:43
- `fetchDataFrom` is async and calls Thread.sleep — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — scala-core-modules/scala-core-3/src/main/scala/com/baeldung/scala/await/AwaitFuture.scala:13
- `futureWithException` is async and calls Thread.sleep — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — scala-core-modules/scala-core-3/src/main/scala/com/baeldung/scala/await/AwaitFuture.scala:21
- `run` is async and calls unsafeRunSync — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — scala-libraries-fp/src/main/scala/com/baeldung/scala/http4s/SimpleClient.scala:13
What to do
- Scala: compose the Future or effect (map/flatMap, a for-comprehension) instead of Await.result or unsafeRunSync, and wrap unavoidable blocking calls in blocking { } (Future), IO.blocking or ZIO.attemptBlocking.
R1 · Type Safety
- 1 typed · 4 plain JS — the untyped files are play-scala/caching-in-play/public/javascripts/main.js, play-scala/configuration-access/public/javascripts/main.js, play-scala/introduction-to-play/public/javascripts/main.js, play-scala/play-static-assets/public/javascripts/main.js.
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
R2 · Cyclomatic Complexity
R3 · Large Files
R7 · Dead Code
R9 · Circular Imports
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. — scala-core-modules/scala-core-2/src/main/scala/com/baeldung/scala/concurrency/FutureAndPromise.scala:38
- This repository runs an HTTP server and nothing in its Scala source or committed configuration secures the transport: no HTTPS served (akka/pekko-http `ConnectionContext.httpsServer`/`enableHttps`, an http4s builder's `withTLS`, Jetty's `SslContextFactory`, zio-http's `SSLConfig`, Play's `https.port`), no `Strict-Transport-Security` header, HSTS middleware or Play `RedirectHttpsFilter`, no `X-Forwarded-Proto` read or Play `play.http.forwarded.trustedProxies` for a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: play-scala/application-tests/REDACTED:6 — the `PlayScala` plugin.
- Set: Referrer-Policy, X-Content-Type-Options, X-Frame-Options, X-Permitted-Cross-Domain-Policies. Missing: Content-Security-Policy, Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−1.0 on this card.) The server: play-scala/application-tests/REDACTED:6 — the `PlayScala` plugin.
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.
- Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`).
- Add Content-Security-Policy, Strict-Transport-Security beside the headers the Scala server already sets.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
- `Source.fromURL(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.mkString` 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(Source.fromURL(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. (×2) — zio/src/main/scala/com/baeldung/scala/zio/ParallelForeachExample.scala:9, scala-strings/src/main/scala/com/baeldung/scala/strings/keywordsearch/KeywordCounter.scala:10
- `Source.fromFile(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.getLines` 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(Source.fromFile(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. — zio/src/main/scala/com/baeldung/scala/zio/streams/FileProcessingExample.scala:10
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
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `case _` 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) — scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/typesystem/CompoundTypes.scala:7, scala-core-modules/scala-core/src/main/scala/com/baeldung/scala/patternmatching/PatternMatching.scala:150
- `case ex: RuntimeException` 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. — scala-core-modules/scala-core/src/main/scala/com/baeldung/scala/patternmatching/PatternMatching.scala:149
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- 5/674 of this repository's Scala product files are under a null discipline — 0 compiled with `-Yexplicit-nulls`, 5 under WartRemover's `Null` wart or Scalafix's `DisableSyntax.noNulls`. In the rest every reference type admits null and nothing reports the `null` that reaches a method call as a `NullPointerException`.
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.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 52% | Adequate — gated by R1, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 88% | Exemplary | Strongest area. |
| Maturity | 85% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 32% | Adequate — gated by P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 62% | Adequate | Acceptable, with room to improve. |
| Event-Driven | 80% | Exemplary | Solid. |
| Accessibility | 64% | Strong | Solid. |
| Performance | 66% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — a Slick table, a case class or a SQL migration's table named for it — Hibernate Envers' @Audited, a JPA entity listener, Hibernate event listener or jOOQ RecordListener that records each change, or an event-sourced journal beside one) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 52 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
- 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 runtime tier booted this repository's service, but crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:5432: page.goto: net::ERR_EMPTY_RESPONSE at http://127.0.0.1:5432/ Call log: - navigating to "http://127.0.0.1:5432/", waiting until "load" . This repository also has a user interface (19 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates) that the booted service does not serve, and this scan has no strategy that reaches it — so no WCAG success criterion was verified in a rendered page on this run. That is a gap in OUR tooling, not a finding about your application: nothing here says the interface is inaccessible. The static accessibility checks still ran.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~19599 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
- D12 Dependency Hygiene — Not scored — 3 Maven/Gradle manifest(s) were read, stating a version for 4 dependency(ies) and leaving 2 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Not scored — this repository's 4 declared JVM dependency coordinate(s) were read from its 3 Maven/Gradle manifest(s), but Maven Central could not be asked for the licence of 3 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/org/http4s/http4s-blaze-server_3/1.0.0-M39/http4s-blaze-server_3-1.0.0-M39.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, Scala, sc not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ 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.
- D32 Data Compliance (PII/GDPR) — 23 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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): 317 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- 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
- M2 Architecture documentation — This repo declares itself a template / kata / sample / demo — formal architecture documentation (ADRs, C4 diagrams) is deferred to a real application built from it, so its absence is not a defect here.
- M4 Documentation accuracy — Not applicable: the 76 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — the JS/TS workspace (5 production file(s)) has no JavaScript/TypeScript test, but it is 0.04% of this repository's production source and the other 99.96% carries 19,599 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
- R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 15 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang scalatra/src/main/twirl/layouts/default.scala.html:2
- REDACTED
- Dual write (no outbox): InventoryService.saveAndPublish scala-test/src/main/scala/com/baeldung/scala/scalatest/mockito/InventoryService.scala:36
Serious — 59 finding(s)
- Sync-over-async blocking scala-2-modules/scala2-libraries/src/main/scala-2/com/baeldung/cache/service/AsyncQueryMemoizeService.scala:49
- Sync-over-async blocking scala-2-modules/scala2-libraries/src/main/scala-2/com/baeldung/cache/service/ScalaCacheCachingBlock.scala:51
- Sync-over-async blocking scala-core-modules/scala-core-2/src/main/scala/com/baeldung/scala/concurrency/FutureAndPromise.scala:13
- Sync-over-async blocking scala-core-modules/scala-core-2/src/main/scala/com/baeldung/scala/concurrency/FutureAndPromise.scala:30
- Sync-over-async blocking scala-core-modules/scala-core-2/src/main/scala/com/baeldung/scala/concurrency/FutureAndPromise.scala:43
- Sync-over-async blocking scala-core-modules/scala-core-3/src/main/scala/com/baeldung/scala/await/AwaitFuture.scala:13
- Sync-over-async blocking scala-core-modules/scala-core-3/src/main/scala/com/baeldung/scala/await/AwaitFuture.scala:21
- Sync-over-async blocking scala-libraries-fp/src/main/scala/com/baeldung/scala/http4s/SimpleClient.scala:13
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unfinished stub — body is `???` scala-core-modules/scala-core-3/src/main/scala/com/baeldung/scala/accessmodifiers/Star.scala:20
- Unfinished stub — body is `???` scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/quitesyntax/Example.scala:62
- Unfinished stub — body is `???` scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/quitesyntax/Example.scala:65
- Unfinished stub — body is `???` scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/quitesyntax/Example.scala:71
- Unfinished stub — body is `???` scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/quitesyntax/Example.scala:75
- Unfinished stub — body is `???` zio/src/main/scala/com/baeldung/scala/zio/AsynchronousProgrammingExample.scala:10
- Unfinished stub — body is ??? / NotImplementedError scala-core-modules/scala-core-3/src/main/scala/com/baeldung/scala/accessmodifiers/Star.scala:20
- Unfinished stub — body is ??? / NotImplementedError scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/quitesyntax/Example.scala:62
- Unfinished stub — body is ??? / NotImplementedError scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/quitesyntax/Example.scala:65
- Unfinished stub — body is ??? / NotImplementedError scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/quitesyntax/Example.scala:71
- Unfinished stub — body is ??? / NotImplementedError scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/quitesyntax/Example.scala:75
- Unfinished stub — body is ??? / NotImplementedError zio/src/main/scala/com/baeldung/scala/zio/AsynchronousProgrammingExample.scala:10
- Page without a main landmark play-scala/configuration-access/app/views/main.scala.html:10
- Page without a main landmark play-scala/introduction-to-play/app/views/main.scala.html:10
- Page without a main landmark play-scala/play-static-assets/app/views/main.scala.html:10
- Page without a main landmark scalatra/src/main/twirl/layouts/default.scala.html:2
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment scala-core-modules/scala-core-6/src/test/scala/com/baeldung/scala/maps/MapsUnitTest.scala:175
- TodoComment scala-core-modules/scala-core-6/src/test/scala/com/baeldung/scala/maps/MapsUnitTest.scala:215
- TodoComment scala-core-modules/scala-core-3/src/main/scala/com/baeldung/scala/iteratorsvsstreamsvsviews/NonStrictDataStructures.scala:9
- Disposable created and abandoned in the function that made it zio/src/main/scala/com/baeldung/scala/zio/ParallelForeachExample.scala:9
- Disposable created and abandoned in the function that made it zio/src/main/scala/com/baeldung/scala/zio/streams/FileProcessingExample.scala:10
- Disposable created and abandoned in the function that made it scala-strings/src/main/scala/com/baeldung/scala/strings/keywordsearch/KeywordCounter.scala:10
- Swallowed exception (caught, then discarded) scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/typesystem/CompoundTypes.scala:7
- Swallowed exception (caught, then discarded) scala-core-modules/scala-core/src/main/scala/com/baeldung/scala/patternmatching/PatternMatching.scala:149
- Swallowed exception (caught, then discarded) scala-core-modules/scala-core/src/main/scala/com/baeldung/scala/patternmatching/PatternMatching.scala:150
- Hollow method — returns a constant without doing the work scala-lang-modules/scala-lang/src/main/scala/com/baeldung/scala/typehierarchy/TypeHierarchy.scala:6
- Hollow method — returns a constant without doing the work scala-lang-modules/scala-lang/src/main/scala/com/baeldung/scala/typehierarchy/TypeHierarchy.scala:8
- Accessibility enforcement below the top rung
- Stateful singleton: TodoListController play-scala/rest-api/app/controllers/TodoListController.scala:9
- PastaCookingFiberAppExample.pastaApp (cognitive 36) zio/src/main/scala/com/baeldung/scala/zio/fibers/PastaCookingFiberAppExample.scala:52
- Cancellation.cancelFiberDirectlySafe (cognitive 28) cats-effects/src/main/scala/com/baeldung/scala/catseffects/Cancellation.scala:19
- RepeatSamples.run (cognitive 22) zio/src/main/scala/com/baeldung/scala/zio/repeatretry/RepeatSamples.scala:8
- Cancellation.naiveParMap_2 (cognitive 21) cats-effects/src/main/scala/com/baeldung/scala/catseffects/Cancellation.scala:49
- REDACTED
- Duplicated block (10 lines × 2) scala-2-modules/scala2-libraries/src/main/scala-2/com/baeldung/scala/pulsar4s/JsonPulsarConsumer.scala:26
- Duplicated block (8 lines × 2) scala-core-collections-modules/scala-core-collections-2/src/main/scala/com/baeldung/scala/lazylists/SimpleLazyList.scala:8
- Duplicated block (13 lines × 2) play-scala/dependency-injection/app/guice/services/OrderService.scala:17
- Off the main sequence: scala-sbt/wart-remover/customWarts
- No DR/backup evidence
- Type Safety
- Weak hash algorithm scala-core-modules/scala-core-2/src/main/scala/com/baeldung/scala/concurrency/FutureAndPromise.scala:38
Minor — 45 finding(s)
- Orphaned file scala-libraries/src/main/scala/com/baeldung/elasticmq/AsyncSQSClient.scala:1
- Orphaned file scala-core-modules/scala-core-fp/src/main/scala/com/baeldung/scala/freemonad/FreeMonads.scala:1
- Orphaned file spark-scala/src/main/scala-2/com/baeldung/scala/sparkjoin/SparkJoins.scala:1
- Orphaned file scala-core-modules/scala-core-6/src/main/scala/com/baeldung/scala/futures/Futures.scala:1
- Orphaned file play-scala/play-templates/app/models/InputForms.scala:1
- Orphaned file scala-libraries-config/src/main/scala/com/baeldung/cirisconfig/Configuration.scala:1
- Orphaned file scala-libraries-config/src/main/scala/com/baeldung/circeyaml/YamlExample.scala:1
- Orphaned file scala-akka/src/main/scala-2/com/baeldung/scala/akka/typed/PortfolioApplication.scala:1
- Orphaned file scala-core-modules/scala-core-fp/src/main/scala/com/baeldung/scala/tagless/TaglessFinal.scala:1
- Orphaned file scala-libraries-standalone/tapir/server/src/main/scala/com/baeldung/tapir/server/KittensServer.scala:1
- Orphaned file scala-2-modules/scala2-libraries/src/finch/todo/src/main/scala/com/baeldung/finch/todo/Main.scala:1
- Orphaned file scala-akka-2/src/main/scala-2/com/baeldung/scala/akka_2/discovery/Main.scala:1
- Orphaned file cats-effects/src/main/scala/com/baeldung/scala/catseffects/Cancellation.scala:1
- Orphaned file zio3/src/main/scala-3/com/baeldung/scala/zio/httpapp/app/RecipeHttpApp.scala:1
- Orphaned file scala-akka-2/src/main/scala-2/com/baeldung/scala/akka_2/persistence/BankAccount.scala:1
- Orphaned file scala-core-modules/scala-core-6/src/main/scala/com/baeldung/scala/fileio/FileIO.scala:1
- Orphaned file scala-libraries-standalone/nscalatime/src/main/scala/com/baeldung/nscalatime/NscalaTime.scala:1
- Orphaned file scala-core-modules/scala-core/src/main/scala/com/baeldung/scala/forloop/ForLoop.scala:1
- Orphaned file scala-libraries/src/main/scala/com/baeldung/elastic4s/Main.scala:1
- Orphaned file scala-core-modules/scala-core-2/src/main/scala/com/baeldung/scala/concurrency/FutureAndPromise.scala:1
- Orphaned file scala-core-modules/scala-core-4/src/main/scala/com/baeldung/scala/future/FutureRecovery.scala:1
- Orphaned file play-scala/play-templates/app/controllers/FormController.scala:1
- Disabled test scala-core-collections-modules/scala-core-collections-4/src/test/scala/com/baeldung/scala/filtertakewhile/FilterAndTakeWhileUnitTest.scala:20
- Disabled test scala-libraries-testing/src/test/scala/com/baeldung/munit/MUnitTest.scala:34
- Disabled test scala-test-2/src/test/scala/com/baeldung/scala/conditionaltests/ConditionalUnitTest.scala:59
- Disabled test scala-test-junit5/src/test/scala-2/com/baeldung/junit5/ExampleUnitTest.scala:8
- Disabled test scala-test/src/test/scala/com/baeldung/scala/scalatest/ExampleFlatSpecWithMatchersUnitTest.scala:54
- Disabled test zio-2/src/test/scala/com/baeldung/scala/zio/aspects/ZAspectsUnitTest.scala:15
- Documentation: no build, run or usage example README.md:1
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- Dormant codebase
- REDACTED
- Empty method body scala-core-modules/scala-core-4/src/main/scala/com/baeldung/scala/pathdependenttypes/PathDependentTypeInnerClasses.scala:8
- CI test execution not evidenced
- CI build step not evidenced
- Logging is not universal
- No SAST
- No rollback/health safety
- Benchmarks don't track allocations specialized-benchmark/src/main/scala-2/com/baeldung/scala/Benchmark.scala
- No app-layer HTTPS enforcement detected
- Security headers incomplete
- Scala's null is not held to the type system everywhere
- Silent fallback default in catch scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/typesystem/CompoundTypes.scala:7
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-635c981e38c24dc9a05dc44ddae97764/history.json --exit-code 0 --source . | 3 | 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-635c981e38c24dc9a05dc44ddae97764/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 . | 4 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-ed04529c3e7a4a36bf1d53d26a45846a | 8 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 9 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 23 file(s) — `scala-core-modules/scala-core-8/src/main/scala/com/baeldung/scala/stackabletrait/StackableTraitExample.scala`, `scala-core-modules/scala-core-8/src/main/scala/com/baeldung/scala/stackabletrait/StackableTraitWithExplicitBaseAndCoreExample.scala`, `scala-core-modules/scala-core-fp/src/main/scala/com/baeldung/scala/freemonad/FreeMonads.scala`, `scala-core-modules/scala-core/src/main/scala-3/com/baeldung/scala/traits/Writer.scala`, `scala-lang-modules/scala-lang-3/src/main/scala/com/baeldung/scala3/intersectiontypes/BasicIntersectionType.scala`, … (+18 more) — 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-ed04529c3e7a4a36bf1d53d26a45846a | 0 | artifacts/raw/osv-scanner.json |