Executive summary
scalacenter/scaladex falls short of our standard for a preview release, in part because it has passwords or keys in the code's history. It scores 39 out of 100 and is rated Weak, and 31 of its 54 critical findings are security problems.
Security and Compliance, at 29, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the security flaws the scanner found, worth about 7 points. Replacing the weak hashes would lift Security and Compliance itself, worth about 8 points. Raising Security and Compliance to 68 would lift the score to about 47.
Eleven passwords or keys in the code's history and one in the code are open to anyone who can read the repository. Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and eight weaknesses in the code could be used by an attacker. Replacing each exposed password or key, pinning each tool to an exact version and fixing the weaknesses the scanner points to would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once. The 13 form fields without a label need a label.
The product code is 12,426 lines, about €14,000 to rebuild. Three of our security checks couldn't finish, among them the one for known security holes in its packages, so those results are missing, not clean passes.
If Security and Compliance rose from 29 to 68, the lowest score rated Strong, the score would rise from 39 to about 47.
Fixed since the last survey: 1 finding
- Dependency Vulnerabilities · High CVE: [GHSA redacted] build.sbt
Rebuild cost: about €14,000 · Estimate
| Cost to rebuild | €4,600 to €23,000, for 77 to 244 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 39. 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: 12,426 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 core.model.data | 2 core.service.MavenCentralIndexClient | 3 core.util | 4 core.model.Artifact | 5 core.model.Project | 6 core.model.data.LocalPomRepository | 7 core.model.data.LocalRepository | 8 core.model.search | 9 data.cleanup | 10 infra.config | 11 core.model | 12 core.model.search.Sorting | 13 data.cleanup.BinaryVersionLookup | 14 infra.elasticsearch | 15 core.api | 16 core.model.ArtifactDependency | 17 core.model.Category | 18 core.model.Env | 19 core.model.GithubResponse | 20 core.model.GithubStatus | 21 core.model.MetaCategory | 22 core.model.Version | 23 core.service | 24 core.web | 25 data.init | 26 data.maven | 27 infra.github.GithubModel | 28 infra.migrations | 29 infra.sql | 30 server.config | 31 client | 32 client.Autocompletion | 33 data | 34 data.maven.PomsReader | 35 infra | 36 server.route | 37 server.route.api | 38 view | 39 server.service | 40 server |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 core.model.data | ||||||||||||||||||||||||||||||||||||||||
| 2 core.service.MavenCentralIndexClient | ||||||||||||||||||||||||||||||||||||||||
| 3 core.util | ||||||||||||||||||||||||||||||||||||||||
| 4 core.model.Artifact | 5 | |||||||||||||||||||||||||||||||||||||||
| 5 core.model.Project | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 core.model.data.LocalPomRepository | 3 | |||||||||||||||||||||||||||||||||||||||
| 7 core.model.data.LocalRepository | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 core.model.search | 17 | 2 | ||||||||||||||||||||||||||||||||||||||
| 9 data.cleanup | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 infra.config | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 core.model | 1 | 4 | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 12 core.model.search.Sorting | 5 | |||||||||||||||||||||||||||||||||||||||
| 13 data.cleanup.BinaryVersionLookup | 3 | |||||||||||||||||||||||||||||||||||||||
| 14 infra.elasticsearch | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 core.api | 2 | 4 | 25 | |||||||||||||||||||||||||||||||||||||
| 16 core.model.ArtifactDependency | 6 | |||||||||||||||||||||||||||||||||||||||
| 17 core.model.Category | 76 | |||||||||||||||||||||||||||||||||||||||
| 18 core.model.Env | 3 | |||||||||||||||||||||||||||||||||||||||
| 19 core.model.GithubResponse | 4 | |||||||||||||||||||||||||||||||||||||||
| 20 core.model.GithubStatus | 5 | |||||||||||||||||||||||||||||||||||||||
| 21 core.model.MetaCategory | 28 | |||||||||||||||||||||||||||||||||||||||
| 22 core.model.Version | 3 | |||||||||||||||||||||||||||||||||||||||
| 23 core.service | 2 | 9 | 39 | |||||||||||||||||||||||||||||||||||||
| 24 core.web | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 data.init | 3 | |||||||||||||||||||||||||||||||||||||||
| 26 data.maven | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 infra.github.GithubModel | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 28 infra.migrations | 3 | |||||||||||||||||||||||||||||||||||||||
| 29 infra.sql | 2 | 1 | 13 | |||||||||||||||||||||||||||||||||||||
| 30 server.config | 7 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 client | 3 | |||||||||||||||||||||||||||||||||||||||
| 32 client.Autocompletion | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 data | 3 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 data.maven.PomsReader | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 infra | 3 | 1 | 7 | 1 | 31 | 8 | 6 | |||||||||||||||||||||||||||||||||
| 36 server.route | 4 | 16 | 2 | |||||||||||||||||||||||||||||||||||||
| 37 server.route.api | 2 | 1 | 4 | 5 | ||||||||||||||||||||||||||||||||||||
| 38 view | 2 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 server.service | 1 | 4 | 1 | 15 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 40 server | 1 | 1 | 3 | 3 | 1 | 2 | 2 |
4→11 core.model.Artifact uses core.model part of a loop✕
- Connections
- 5 pairs of types, where a type in core.model.Artifact uses a type in core.model.
- The types involved
scaladex.core.model.Artifact.ArtifactId→scaladex.core.model.BinaryVersionscaladex.core.model.Artifact.Reference→scaladex.core.model.BinaryVersionscaladex.core.model.Artifact.Reference→scaladex.core.model.Languagescaladex.core.model.Artifact.Reference→scaladex.core.model.Platformscaladex.core.model.Artifact.Reference→scaladex.core.model.Version
- Direction
- core.model.Artifact uses core.model, so a change to core.model can break core.model.Artifact, while a change to core.model.Artifact can't break core.model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→11 core.model.Project uses core.model part of a loop✕
- Connections
- 2 pairs of types, where a type in core.model.Project uses a type in core.model.
- The types involved
scaladex.core.model.Project.Settings→scaladex.core.model.Categoryscaladex.core.model.Project.Settings→scaladex.core.model.DocumentationPattern
- Direction
- core.model.Project uses core.model, so a change to core.model can break core.model.Project, while a change to core.model.Project can't break core.model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→1 core.model.data.LocalPomRepository uses core.model.data✕
- Connections
- 3 pairs of types, where a type in core.model.data.LocalPomRepository uses a type in core.model.data.
- The types involved
scaladex.core.model.data.LocalPomRepository.Bintray→scaladex.core.model.data.LocalPomRepositoryscaladex.core.model.data.LocalPomRepository.MavenCentral→scaladex.core.model.data.LocalPomRepositoryscaladex.core.model.data.LocalPomRepository.UserProvided→scaladex.core.model.data.LocalPomRepository
- Direction
- core.model.data.LocalPomRepository uses core.model.data, so a change to core.model.data can break core.model.data.LocalPomRepository, while a change to core.model.data.LocalPomRepository can't break core.model.data.
- Position
- Below the diagonal: core.model.data.LocalPomRepository uses a module listed above it, which is the healthy direction.
7→1 core.model.data.LocalRepository uses core.model.data✕
- Connections
- 1 pair of types, where a type in core.model.data.LocalRepository uses a type in core.model.data.
- The types involved
scaladex.core.model.data.LocalRepository.BintraySbtPlugins→scaladex.core.model.data.LocalRepository
- Direction
- core.model.data.LocalRepository uses core.model.data, so a change to core.model.data can break core.model.data.LocalRepository, while a change to core.model.data.LocalRepository can't break core.model.data.
- Position
- Below the diagonal: core.model.data.LocalRepository uses a module listed above it, which is the healthy direction.
8→11 core.model.search uses core.model part of a loop✕
- Connections
- 17 pairs of types, where a type in core.model.search uses a type in core.model.
- The types involved
scaladex.core.model.search.AwesomeParams→scaladex.core.model.Languagescaladex.core.model.search.AwesomeParams→scaladex.core.model.Platformscaladex.core.model.search.GithubInfoDocument→scaladex.core.model.GithubIssuescaladex.core.model.search.GithubInfoDocument→scaladex.core.model.Licensescaladex.core.model.search.GithubInfoDocument→scaladex.core.model.Urlscaladex.core.model.search.ProjectDocument→scaladex.core.model.Categoryscaladex.core.model.search.ProjectDocument→scaladex.core.model.Languagescaladex.core.model.search.ProjectDocument→scaladex.core.model.MillPluginscaladex.core.model.search.ProjectDocument→scaladex.core.model.Platformscaladex.core.model.search.ProjectDocument→scaladex.core.model.SbtPluginscaladex.core.model.search.ProjectDocument→scaladex.core.model.Scalascaladex.core.model.search.ProjectDocument→scaladex.core.model.ScalaJsscaladex.core.model.search.ProjectDocument→scaladex.core.model.ScalaNativescaladex.core.model.search.ProjectDocument→scaladex.core.model.Versionscaladex.core.model.search.ProjectHit→scaladex.core.model.GithubIssuescaladex.core.model.search.SearchParams→scaladex.core.model.Languagescaladex.core.model.search.SearchParams→scaladex.core.model.Platform
- Direction
- core.model.search uses core.model, so a change to core.model can break core.model.search, while a change to core.model.search can't break core.model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→15 core.model.search uses core.api part of a loop✕
- Connections
- 2 pairs of types, where a type in core.model.search uses a type in core.api.
- The types involved
scaladex.core.model.search.ProjectDocument→scaladex.core.api.AutocompletionResponsescaladex.core.model.search.SearchParams→scaladex.core.api.AutocompletionParams
- Direction
- core.model.search uses core.api, so a change to core.api can break core.model.search, while a change to core.model.search can't break core.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→3 data.cleanup uses core.util✕
- Connections
- 1 pair of types, where a type in data.cleanup uses a type in core.util.
- The types involved
scaladex.data.cleanup.ScmInfoParser→scaladex.core.util.Parsers
- Direction
- data.cleanup uses core.util, so a change to core.util can break data.cleanup, while a change to data.cleanup can't break core.util.
- Position
- Below the diagonal: data.cleanup uses a module listed above it, which is the healthy direction.
10→3 infra.config uses core.util✕
- Connections
- 2 pairs of types, where a type in infra.config uses a type in core.util.
- The types involved
scaladex.infra.config.GithubConfig→scaladex.core.util.Secretscaladex.infra.config.PostgreSQLConfig→scaladex.core.util.Secret
- Direction
- infra.config uses core.util, so a change to core.util can break infra.config, while a change to infra.config can't break core.util.
- Position
- Below the diagonal: infra.config uses a module listed above it, which is the healthy direction.
11→3 core.model uses core.util✕
- Connections
- 1 pair of types, where a type in core.model uses a type in core.util.
- The types involved
scaladex.core.model.UserInfo→scaladex.core.util.Secret
- Direction
- core.model uses core.util, so a change to core.util can break core.model, while a change to core.model can't break core.util.
- Position
- Below the diagonal: core.model uses a module listed above it, which is the healthy direction.
11→4 core.model uses core.model.Artifact✕
- Connections
- 4 pairs of types, where a type in core.model uses a type in core.model.Artifact.
- The types involved
scaladex.core.model.Artifact→scaladex.core.model.Artifact.ArtifactIdscaladex.core.model.Artifact→scaladex.core.model.Artifact.GroupIdscaladex.core.model.Artifact→scaladex.core.model.Artifact.Namescaladex.core.model.Artifact→scaladex.core.model.Artifact.Reference
- Direction
- core.model uses core.model.Artifact, so a change to core.model.Artifact can break core.model, while a change to core.model can't break core.model.Artifact.
- Position
- Below the diagonal: core.model uses a module listed above it, which is the healthy direction.
11→5 core.model uses core.model.Project✕
- Connections
- 4 pairs of types, where a type in core.model uses a type in core.model.Project.
- The types involved
scaladex.core.model.Project→scaladex.core.model.Project.Organizationscaladex.core.model.Project→scaladex.core.model.Project.Referencescaladex.core.model.Project→scaladex.core.model.Project.Repositoryscaladex.core.model.Project→scaladex.core.model.Project.Settings
- Direction
- core.model uses core.model.Project, so a change to core.model.Project can break core.model, while a change to core.model can't break core.model.Project.
- Position
- Below the diagonal: core.model uses a module listed above it, which is the healthy direction.
11→8 core.model uses core.model.search✕
- Connections
- 1 pair of types, where a type in core.model uses a type in core.model.search.
- The types involved
scaladex.core.model.GithubInfo→scaladex.core.model.search.GithubInfoDocument
- Direction
- core.model uses core.model.search, so a change to core.model.search can break core.model, while a change to core.model can't break core.model.search.
- Position
- Below the diagonal: core.model uses a module listed above it, which is the healthy direction.
11→15 core.model uses core.api part of a loop✕
- Connections
- 1 pair of types, where a type in core.model uses a type in core.api.
- The types involved
scaladex.core.model.Artifact→scaladex.core.api.ArtifactResponse
- Direction
- core.model uses core.api, so a change to core.api can break core.model, while a change to core.model can't break core.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→8 core.model.search.Sorting uses core.model.search✕
- Connections
- 5 pairs of types, where a type in core.model.search.Sorting uses a type in core.model.search.
- The types involved
scaladex.core.model.search.Sorting.CommitActivity→scaladex.core.model.search.Sortingscaladex.core.model.search.Sorting.Contributors→scaladex.core.model.search.Sortingscaladex.core.model.search.Sorting.Created→scaladex.core.model.search.Sortingscaladex.core.model.search.Sorting.Dependent→scaladex.core.model.search.Sortingscaladex.core.model.search.Sorting.Stars→scaladex.core.model.search.Sorting
- Direction
- core.model.search.Sorting uses core.model.search, so a change to core.model.search can break core.model.search.Sorting, while a change to core.model.search.Sorting can't break core.model.search.
- Position
- Below the diagonal: core.model.search.Sorting uses a module listed above it, which is the healthy direction.
13→9 data.cleanup.BinaryVersionLookup uses data.cleanup✕
- Connections
- 3 pairs of types, where a type in data.cleanup.BinaryVersionLookup uses a type in data.cleanup.
- The types involved
scaladex.data.cleanup.BinaryVersionLookup.FromArtifactVersion→scaladex.data.cleanup.BinaryVersionLookupscaladex.data.cleanup.BinaryVersionLookup.FromDependency→scaladex.data.cleanup.BinaryVersionLookupscaladex.data.cleanup.BinaryVersionLookup.Java→scaladex.data.cleanup.BinaryVersionLookup
- Direction
- data.cleanup.BinaryVersionLookup uses data.cleanup, so a change to data.cleanup can break data.cleanup.BinaryVersionLookup, while a change to data.cleanup.BinaryVersionLookup can't break data.cleanup.
- Position
- Below the diagonal: data.cleanup.BinaryVersionLookup uses a module listed above it, which is the healthy direction.
14→8 infra.elasticsearch uses core.model.search✕
- Connections
- 2 pairs of types, where a type in infra.elasticsearch uses a type in core.model.search.
- The types involved
scaladex.infra.elasticsearch.RawProjectDocument→scaladex.core.model.search.GithubInfoDocumentscaladex.infra.elasticsearch.RawProjectDocument→scaladex.core.model.search.ProjectDocument
- Direction
- infra.elasticsearch uses core.model.search, so a change to core.model.search can break infra.elasticsearch, while a change to infra.elasticsearch can't break core.model.search.
- Position
- Below the diagonal: infra.elasticsearch uses a module listed above it, which is the healthy direction.
15→5 core.api uses core.model.Project✕
- Connections
- 2 pairs of types, where a type in core.api uses a type in core.model.Project.
- The types involved
scaladex.core.api.ProjectResponse→scaladex.core.model.Project.Organizationscaladex.core.api.ProjectResponse→scaladex.core.model.Project.Repository
- Direction
- core.api uses core.model.Project, so a change to core.model.Project can break core.api, while a change to core.api can't break core.model.Project.
- Position
- Below the diagonal: core.api uses a module listed above it, which is the healthy direction.
15→8 core.api uses core.model.search✕
- Connections
- 4 pairs of types, where a type in core.api uses a type in core.model.search.
- The types involved
scaladex.core.api.AutocompletionParams→scaladex.core.model.search.SearchParamsscaladex.core.api.Endpoints→scaladex.core.model.search.Pagescaladex.core.api.Endpoints→scaladex.core.model.search.PageParamsscaladex.core.api.ProjectSearchParams→scaladex.core.model.search.SearchParams
- Direction
- core.api uses core.model.search, so a change to core.model.search can break core.api, while a change to core.api can't break core.model.search.
- Position
- Below the diagonal: core.api uses a module listed above it, which is the healthy direction.
15→11 core.api uses core.model✕
- Connections
- 25 pairs of types, where a type in core.api uses a type in core.model.
- The types involved
scaladex.core.api.ArtifactResponse→scaladex.core.model.BinaryVersionscaladex.core.api.ArtifactResponse→scaladex.core.model.Languagescaladex.core.api.ArtifactResponse→scaladex.core.model.Licensescaladex.core.api.ArtifactResponse→scaladex.core.model.Platformscaladex.core.api.ArtifactResponse→scaladex.core.model.Versionscaladex.core.api.AutocompletionParams→scaladex.core.model.Languagescaladex.core.api.AutocompletionParams→scaladex.core.model.Platformscaladex.core.api.AutocompletionParams→scaladex.core.model.UserStatescaladex.core.api.Endpoints→scaladex.core.model.BinaryVersionscaladex.core.api.Endpoints→scaladex.core.model.ProjectDependencyscaladex.core.api.Endpoints→scaladex.core.model.Versionscaladex.core.api.ProjectArtifactsParams→scaladex.core.model.BinaryVersionscaladex.core.api.ProjectResponse→scaladex.core.model.Categoryscaladex.core.api.ProjectResponse→scaladex.core.model.DocumentationPatternscaladex.core.api.ProjectResponse→scaladex.core.model.Licensescaladex.core.api.ProjectResponse→scaladex.core.model.Urlscaladex.core.api.ProjectSearchParams→scaladex.core.model.Languagescaladex.core.api.ProjectSearchParams→scaladex.core.model.Platformscaladex.core.api.ProjectSettingsPatch→scaladex.core.model.DocumentationPatternscaladex.core.api.ProjectVersionsParams→scaladex.core.model.BinaryVersionscaladex.core.api.ProjectsParams→scaladex.core.model.Languagescaladex.core.api.ProjectsParams→scaladex.core.model.Platformscaladex.core.api.SearchResult→scaladex.core.model.Languagescaladex.core.api.SearchResult→scaladex.core.model.Platformscaladex.core.api.SearchResult→scaladex.core.model.Version
- Direction
- core.api uses core.model, so a change to core.model can break core.api, while a change to core.api can't break core.model.
- Position
- Below the diagonal: core.api uses a module listed above it, which is the healthy direction.
16→11 core.model.ArtifactDependency uses core.model✕
- Connections
- 6 pairs of types, where a type in core.model.ArtifactDependency uses a type in core.model.
- The types involved
scaladex.core.model.ArtifactDependency.Direct→scaladex.core.model.Artifactscaladex.core.model.ArtifactDependency.Direct→scaladex.core.model.ArtifactDependencyscaladex.core.model.ArtifactDependency.Direct→scaladex.core.model.Versionscaladex.core.model.ArtifactDependency.Reverse→scaladex.core.model.Artifactscaladex.core.model.ArtifactDependency.Reverse→scaladex.core.model.ArtifactDependencyscaladex.core.model.ArtifactDependency.Reverse→scaladex.core.model.Version
- Direction
- core.model.ArtifactDependency uses core.model, so a change to core.model can break core.model.ArtifactDependency, while a change to core.model.ArtifactDependency can't break core.model.
- Position
- Below the diagonal: core.model.ArtifactDependency uses a module listed above it, which is the healthy direction.
17→11 core.model.Category uses core.model✕
- Connections
- 76 pairs of types, where a type in core.model.Category uses a type in core.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
scaladex.core.model.Category.AlgorithmsAndDataStructures→scaladex.core.model.Categoryscaladex.core.model.Category.ArchivesAndCompression→scaladex.core.model.Categoryscaladex.core.model.Category.AssetManagementAndBundlers→scaladex.core.model.Categoryscaladex.core.model.Category.AsynchronousAndReactiveProgramming→scaladex.core.model.Categoryscaladex.core.model.Category.AudioAndMusic→scaladex.core.model.Categoryscaladex.core.model.Category.AuthenticationAndPermissions→scaladex.core.model.Categoryscaladex.core.model.Category.Bioinformatics→scaladex.core.model.Categoryscaladex.core.model.Category.BuildTools→scaladex.core.model.Categoryscaladex.core.model.Category.Caching→scaladex.core.model.Categoryscaladex.core.model.Category.CodeAnalysis→scaladex.core.model.Categoryscaladex.core.model.Category.CodeEditorsAndNotebooks→scaladex.core.model.Categoryscaladex.core.model.Category.CodeFormatting→scaladex.core.model.Categoryscaladex.core.model.Category.CodeGeneration→scaladex.core.model.Categoryscaladex.core.model.Category.CommandLineParsing→scaladex.core.model.Categoryscaladex.core.model.Category.Compilers→scaladex.core.model.Categoryscaladex.core.model.Category.ConfigurationAndEnvironment→scaladex.core.model.Categoryscaladex.core.model.Category.CryptographyAndHashing→scaladex.core.model.Categoryscaladex.core.model.Category.Csv→scaladex.core.model.Categoryscaladex.core.model.Category.DataSourcesAndConnectors→scaladex.core.model.Categoryscaladex.core.model.Category.DataVizualization→scaladex.core.model.Categoryscaladex.core.model.Category.Databases→scaladex.core.model.Categoryscaladex.core.model.Category.DatesAndTime→scaladex.core.model.Categoryscaladex.core.model.Category.DependencyInjection→scaladex.core.model.Categoryscaladex.core.model.Category.DeploymentAndCloud→scaladex.core.model.Categoryscaladex.core.model.Category.DistributedComputing→scaladex.core.model.Category
- Direction
- core.model.Category uses core.model, so a change to core.model can break core.model.Category, while a change to core.model.Category can't break core.model.
- Position
- Below the diagonal: core.model.Category uses a module listed above it, which is the healthy direction.
18→11 core.model.Env uses core.model✕
- Connections
- 3 pairs of types, where a type in core.model.Env uses a type in core.model.
- The types involved
scaladex.core.model.Env.Dev→scaladex.core.model.Envscaladex.core.model.Env.Local→scaladex.core.model.Envscaladex.core.model.Env.Prod→scaladex.core.model.Env
- Direction
- core.model.Env uses core.model, so a change to core.model can break core.model.Env, while a change to core.model.Env can't break core.model.
- Position
- Below the diagonal: core.model.Env uses a module listed above it, which is the healthy direction.
19→11 core.model.GithubResponse uses core.model✕
- Connections
- 4 pairs of types, where a type in core.model.GithubResponse uses a type in core.model.
- The types involved
scaladex.core.model.GithubResponse.Failed→scaladex.core.model.GithubResponsescaladex.core.model.GithubResponse.MovedPermanently→scaladex.core.model.GithubResponsescaladex.core.model.GithubResponse.NotFound→scaladex.core.model.GithubResponsescaladex.core.model.GithubResponse.Ok→scaladex.core.model.GithubResponse
- Direction
- core.model.GithubResponse uses core.model, so a change to core.model can break core.model.GithubResponse, while a change to core.model.GithubResponse can't break core.model.
- Position
- Below the diagonal: core.model.GithubResponse uses a module listed above it, which is the healthy direction.
20→11 core.model.GithubStatus uses core.model✕
- Connections
- 5 pairs of types, where a type in core.model.GithubStatus uses a type in core.model.
- The types involved
scaladex.core.model.GithubStatus.Failed→scaladex.core.model.GithubStatusscaladex.core.model.GithubStatus.Moved→scaladex.core.model.GithubStatusscaladex.core.model.GithubStatus.NotFound→scaladex.core.model.GithubStatusscaladex.core.model.GithubStatus.Ok→scaladex.core.model.GithubStatusscaladex.core.model.GithubStatus.Unknown→scaladex.core.model.GithubStatus
- Direction
- core.model.GithubStatus uses core.model, so a change to core.model can break core.model.GithubStatus, while a change to core.model.GithubStatus can't break core.model.
- Position
- Below the diagonal: core.model.GithubStatus uses a module listed above it, which is the healthy direction.
21→11 core.model.MetaCategory uses core.model✕
- Connections
- 28 pairs of types, where a type in core.model.MetaCategory uses a type in core.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
scaladex.core.model.MetaCategory.AsynchronousAndConcurrentProgramming→scaladex.core.model.Categoryscaladex.core.model.MetaCategory.AsynchronousAndConcurrentProgramming→scaladex.core.model.MetaCategoryscaladex.core.model.MetaCategory.BigData→scaladex.core.model.Categoryscaladex.core.model.MetaCategory.BigData→scaladex.core.model.MetaCategoryscaladex.core.model.MetaCategory.ComputerScience→scaladex.core.model.Categoryscaladex.core.model.MetaCategory.ComputerScience→scaladex.core.model.MetaCategoryscaladex.core.model.MetaCategory.ConfigurationLoggingTestingAndMonitoring→scaladex.core.model.Categoryscaladex.core.model.MetaCategory.ConfigurationLoggingTestingAndMonitoring→scaladex.core.model.MetaCategoryscaladex.core.model.MetaCategory.DatabasesIndexingAndSearching→scaladex.core.model.Categoryscaladex.core.model.MetaCategory.DatabasesIndexingAndSearching→scaladex.core.model.MetaCategoryscaladex.core.model.MetaCategory.DeploymentVirtualizationAndCloud→scaladex.core.model.Categoryscaladex.core.model.MetaCategory.DeploymentVirtualizationAndCloud→scaladex.core.model.MetaCategoryscaladex.core.model.MetaCategory.DevelopmentTooling→scaladex.core.model.Categoryscaladex.core.model.MetaCategory.DevelopmentTooling→scaladex.core.model.MetaCategoryscaladex.core.model.MetaCategory.ImagesAudioAndVideo→scaladex.core.model.Categoryscaladex.core.model.MetaCategory.ImagesAudioAndVideo→scaladex.core.model.MetaCategoryscaladex.core.model.MetaCategory.MathematicsFinanceDataScienceAndBioinformatics→scaladex.core.model.Categoryscaladex.core.model.MetaCategory.MathematicsFinanceDataScienceAndBioinformatics→scaladex.core.model.MetaCategoryscaladex.core.model.MetaCategory.MobileDesktopAndGameDevelopment→scaladex.core.model.Categoryscaladex.core.model.MetaCategory.MobileDesktopAndGameDevelopment→scaladex.core.model.MetaCategoryscaladex.core.model.MetaCategory.OperatingSystemsAndHardware→scaladex.core.model.Categoryscaladex.core.model.MetaCategory.OperatingSystemsAndHardware→scaladex.core.model.MetaCategoryscaladex.core.model.MetaCategory.TextFormatAndCompression→scaladex.core.model.Categoryscaladex.core.model.MetaCategory.TextFormatAndCompression→scaladex.core.model.MetaCategoryscaladex.core.model.MetaCategory.TimePositionsAndUnitsOfMeasurement→scaladex.core.model.Category
- Direction
- core.model.MetaCategory uses core.model, so a change to core.model can break core.model.MetaCategory, while a change to core.model.MetaCategory can't break core.model.
- Position
- Below the diagonal: core.model.MetaCategory uses a module listed above it, which is the healthy direction.
22→11 core.model.Version uses core.model✕
- Connections
- 3 pairs of types, where a type in core.model.Version uses a type in core.model.
- The types involved
scaladex.core.model.Version.Custom→scaladex.core.model.Versionscaladex.core.model.Version.SemanticLike→scaladex.core.model.PreReleasescaladex.core.model.Version.SemanticLike→scaladex.core.model.Version
- Direction
- core.model.Version uses core.model, so a change to core.model can break core.model.Version, while a change to core.model.Version can't break core.model.
- Position
- Below the diagonal: core.model.Version uses a module listed above it, which is the healthy direction.
23→3 core.service uses core.util✕
- Connections
- 2 pairs of types, where a type in core.service uses a type in core.util.
- The types involved
scaladex.core.service.GithubAuth→scaladex.core.util.Secretscaladex.core.service.GithubClient→scaladex.core.util.Secret
- Direction
- core.service uses core.util, so a change to core.util can break core.service, while a change to core.service can't break core.util.
- Position
- Below the diagonal: core.service uses a module listed above it, which is the healthy direction.
23→8 core.service uses core.model.search✕
- Connections
- 9 pairs of types, where a type in core.service uses a type in core.model.search.
- The types involved
scaladex.core.service.ProjectService→scaladex.core.model.search.Pagescaladex.core.service.ProjectService→scaladex.core.model.search.PageParamsscaladex.core.service.ProjectService→scaladex.core.model.search.Paginationscaladex.core.service.SearchEngine→scaladex.core.model.search.AwesomeParamsscaladex.core.service.SearchEngine→scaladex.core.model.search.Pagescaladex.core.service.SearchEngine→scaladex.core.model.search.PageParamsscaladex.core.service.SearchEngine→scaladex.core.model.search.ProjectDocumentscaladex.core.service.SearchEngine→scaladex.core.model.search.ProjectHitscaladex.core.service.SearchEngine→scaladex.core.model.search.SearchParams
- Direction
- core.service uses core.model.search, so a change to core.model.search can break core.service, while a change to core.service can't break core.model.search.
- Position
- Below the diagonal: core.service uses a module listed above it, which is the healthy direction.
23→11 core.service uses core.model✕
- Connections
- 39 pairs of types, where a type in core.service uses a type in core.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
scaladex.core.service.GithubAuth→scaladex.core.model.UserInfoscaladex.core.service.GithubAuth→scaladex.core.model.UserStatescaladex.core.service.GithubClient→scaladex.core.model.GithubResponsescaladex.core.service.GithubClient→scaladex.core.model.UserInfoscaladex.core.service.GithubClient→scaladex.core.model.UserStatescaladex.core.service.MavenCentralClient→scaladex.core.model.Versionscaladex.core.service.MavenCentralIndexClient→scaladex.core.model.IndexCursorscaladex.core.service.ProjectService→scaladex.core.model.BinaryVersionscaladex.core.service.ProjectService→scaladex.core.model.Languagescaladex.core.service.ProjectService→scaladex.core.model.Platformscaladex.core.service.ProjectService→scaladex.core.model.Projectscaladex.core.service.ProjectService→scaladex.core.model.ProjectDependencyscaladex.core.service.ProjectService→scaladex.core.model.ProjectHeaderscaladex.core.service.ProjectService→scaladex.core.model.Versionscaladex.core.service.SchedulerDatabase→scaladex.core.model.Artifactscaladex.core.service.SchedulerDatabase→scaladex.core.model.ArtifactDependencyscaladex.core.service.SchedulerDatabase→scaladex.core.model.DiscoveredGroupIdscaladex.core.service.SchedulerDatabase→scaladex.core.model.IndexCursorscaladex.core.service.SchedulerDatabase→scaladex.core.model.Projectscaladex.core.service.SchedulerDatabase→scaladex.core.model.ProjectDependencyscaladex.core.service.SchedulerDatabase→scaladex.core.model.Versionscaladex.core.service.SearchEngine→scaladex.core.model.BinaryVersionscaladex.core.service.SearchEngine→scaladex.core.model.Categoryscaladex.core.service.SearchEngine→scaladex.core.model.TopicCountscaladex.core.service.Storage→scaladex.core.model.Artifact
- Direction
- core.service uses core.model, so a change to core.model can break core.service, while a change to core.service can't break core.model.
- Position
- Below the diagonal: core.service uses a module listed above it, which is the healthy direction.
24→11 core.web uses core.model✕
- Connections
- 2 pairs of types, where a type in core.web uses a type in core.model.
- The types involved
scaladex.core.web.ArtifactPageParams→scaladex.core.model.BinaryVersionscaladex.core.web.ArtifactsPageParams→scaladex.core.model.BinaryVersion
- Direction
- core.web uses core.model, so a change to core.model can break core.web, while a change to core.web can't break core.model.
- Position
- Below the diagonal: core.web uses a module listed above it, which is the healthy direction.
25→11 data.init uses core.model✕
- Connections
- 3 pairs of types, where a type in data.init uses a type in core.model.
- The types involved
scaladex.data.init.Init→scaladex.core.model.Artifactscaladex.data.init.Init→scaladex.core.model.ArtifactDependencyscaladex.data.init.Init→scaladex.core.model.Project
- Direction
- data.init uses core.model, so a change to core.model can break data.init, while a change to data.init can't break core.model.
- Position
- Below the diagonal: data.init uses a module listed above it, which is the healthy direction.
26→11 data.maven uses core.model✕
- Connections
- 2 pairs of types, where a type in data.maven uses a type in core.model.
- The types involved
scaladex.data.maven.ArtifactModel→scaladex.core.model.Contributorscaladex.data.maven.ArtifactModel→scaladex.core.model.Url
- Direction
- data.maven uses core.model, so a change to core.model can break data.maven, while a change to data.maven can't break core.model.
- Position
- Below the diagonal: data.maven uses a module listed above it, which is the healthy direction.
27→3 infra.github.GithubModel uses core.util✕
- Connections
- 1 pair of types, where a type in infra.github.GithubModel uses a type in core.util.
- The types involved
scaladex.infra.github.GithubModel.UserInfo→scaladex.core.util.Secret
- Direction
- infra.github.GithubModel uses core.util, so a change to core.util can break infra.github.GithubModel, while a change to infra.github.GithubModel can't break core.util.
- Position
- Below the diagonal: infra.github.GithubModel uses a module listed above it, which is the healthy direction.
27→11 infra.github.GithubModel uses core.model✕
- Connections
- 2 pairs of types, where a type in infra.github.GithubModel uses a type in core.model.
- The types involved
scaladex.infra.github.GithubModel.Contributor→scaladex.core.model.GithubContributorscaladex.infra.github.GithubModel.OpenIssue→scaladex.core.model.GithubIssue
- Direction
- infra.github.GithubModel uses core.model, so a change to core.model can break infra.github.GithubModel, while a change to infra.github.GithubModel can't break core.model.
- Position
- Below the diagonal: infra.github.GithubModel uses a module listed above it, which is the healthy direction.
28→11 infra.migrations uses core.model✕
- Connections
- 3 pairs of types, where a type in infra.migrations uses a type in core.model.
- The types involved
scaladex.infra.migrations.V13_2__update_new_fields_in_artifacts→scaladex.core.model.Artifactscaladex.infra.migrations.V17__add_mill_platform→scaladex.core.model.Artifactscaladex.infra.migrations.V9__fix_platform_and_language→scaladex.core.model.Artifact
- Direction
- infra.migrations uses core.model, so a change to core.model can break infra.migrations, while a change to infra.migrations can't break core.model.
- Position
- Below the diagonal: infra.migrations uses a module listed above it, which is the healthy direction.
29→4 infra.sql uses core.model.Artifact✕
- Connections
- 2 pairs of types, where a type in infra.sql uses a type in core.model.Artifact.
- The types involved
scaladex.infra.sql.ArtifactTable→scaladex.core.model.Artifact.GroupIdscaladex.infra.sql.ArtifactTable→scaladex.core.model.Artifact.Reference
- Direction
- infra.sql uses core.model.Artifact, so a change to core.model.Artifact can break infra.sql, while a change to infra.sql can't break core.model.Artifact.
- Position
- Below the diagonal: infra.sql uses a module listed above it, which is the healthy direction.
29→10 infra.sql uses infra.config✕
- Connections
- 1 pair of types, where a type in infra.sql uses a type in infra.config.
- The types involved
scaladex.infra.sql.DoobieUtils→scaladex.infra.config.PostgreSQLConfig
- Direction
- infra.sql uses infra.config, so a change to infra.config can break infra.sql, while a change to infra.sql can't break infra.config.
- Position
- Below the diagonal: infra.sql uses a module listed above it, which is the healthy direction.
29→11 infra.sql uses core.model✕
- Connections
- 13 pairs of types, where a type in infra.sql uses a type in core.model.
- The types involved
scaladex.infra.sql.ArtifactDependencyTable→scaladex.core.model.ArtifactDependencyscaladex.infra.sql.ArtifactDependencyTable→scaladex.core.model.ProjectDependencyscaladex.infra.sql.ArtifactTable→scaladex.core.model.Artifactscaladex.infra.sql.ArtifactTable→scaladex.core.model.Languagescaladex.infra.sql.ArtifactTable→scaladex.core.model.Platformscaladex.infra.sql.ArtifactTable→scaladex.core.model.Versionscaladex.infra.sql.DiscoveredGroupIdTable→scaladex.core.model.DiscoveredGroupIdscaladex.infra.sql.DiscoveredIndexCursorTable→scaladex.core.model.IndexCursorscaladex.infra.sql.InsightsQueries→scaladex.core.model.Scala3MigrationInsightscaladex.infra.sql.InsightsQueries→scaladex.core.model.ScalaVersionInsightscaladex.infra.sql.ProjectDependenciesTable→scaladex.core.model.ProjectDependencyscaladex.infra.sql.ProjectTable→scaladex.core.model.Projectscaladex.infra.sql.UserSessionsTable→scaladex.core.model.UserState
- Direction
- infra.sql uses core.model, so a change to core.model can break infra.sql, while a change to infra.sql can't break core.model.
- Position
- Below the diagonal: infra.sql uses a module listed above it, which is the healthy direction.
30→10 server.config uses infra.config✕
- Connections
- 7 pairs of types, where a type in server.config uses a type in infra.config.
- The types involved
scaladex.server.config.ServerConfig→scaladex.infra.config.CacheConfigscaladex.server.config.ServerConfig→scaladex.infra.config.ElasticsearchConfigscaladex.server.config.ServerConfig→scaladex.infra.config.FilesystemConfigscaladex.server.config.ServerConfig→scaladex.infra.config.GithubConfigscaladex.server.config.ServerConfig→scaladex.infra.config.MavenCentralConfigscaladex.server.config.ServerConfig→scaladex.infra.config.PostgreSQLConfigscaladex.server.config.ServerConfig→scaladex.infra.config.ScaladocConfig
- Direction
- server.config uses infra.config, so a change to infra.config can break server.config, while a change to server.config can't break infra.config.
- Position
- Below the diagonal: server.config uses a module listed above it, which is the healthy direction.
30→11 server.config uses core.model✕
- Connections
- 1 pair of types, where a type in server.config uses a type in core.model.
- The types involved
scaladex.server.config.ServerConfig→scaladex.core.model.Env
- Direction
- server.config uses core.model, so a change to core.model can break server.config, while a change to server.config can't break core.model.
- Position
- Below the diagonal: server.config uses a module listed above it, which is the healthy direction.
31→15 client uses core.api✕
- Connections
- 3 pairs of types, where a type in client uses a type in core.api.
- The types involved
scaladex.client.Autocompletion→scaladex.core.api.AutocompletionResponsescaladex.client.Dom→scaladex.core.api.AutocompletionParamsscaladex.client.RPC→scaladex.core.api.Endpoints
- Direction
- client uses core.api, so a change to core.api can break client, while a change to client can't break core.api.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
32→15 client.Autocompletion uses core.api✕
- Connections
- 1 pair of types, where a type in client.Autocompletion uses a type in core.api.
- The types involved
scaladex.client.Autocompletion.CompletionSelection→scaladex.core.api.AutocompletionResponse
- Direction
- client.Autocompletion uses core.api, so a change to core.api can break client.Autocompletion, while a change to client.Autocompletion can't break core.api.
- Position
- Below the diagonal: client.Autocompletion uses a module listed above it, which is the healthy direction.
33→10 data uses infra.config✕
- Connections
- 3 pairs of types, where a type in data uses a type in infra.config.
- The types involved
scaladex.data.IndexConfig→scaladex.infra.config.CacheConfigscaladex.data.IndexConfig→scaladex.infra.config.FilesystemConfigscaladex.data.IndexConfig→scaladex.infra.config.PostgreSQLConfig
- Direction
- data uses infra.config, so a change to infra.config can break data, while a change to data can't break infra.config.
- Position
- Below the diagonal: data uses a module listed above it, which is the healthy direction.
33→11 data uses core.model✕
- Connections
- 2 pairs of types, where a type in data uses a type in core.model.
- The types involved
scaladex.data.IndexConfig→scaladex.core.model.Envscaladex.data.SubIndex→scaladex.core.model.Project
- Direction
- data uses core.model, so a change to core.model can break data, while a change to data can't break core.model.
- Position
- Below the diagonal: data uses a module listed above it, which is the healthy direction.
33→23 data uses core.service✕
- Connections
- 1 pair of types, where a type in data uses a type in core.service.
- The types involved
scaladex.data.GenerateFeeders→scaladex.core.service.Storage
- Direction
- data uses core.service, so a change to core.service can break data, while a change to data can't break core.service.
- Position
- Below the diagonal: data uses a module listed above it, which is the healthy direction.
34→26 data.maven.PomsReader uses data.maven✕
- Connections
- 2 pairs of types, where a type in data.maven.PomsReader uses a type in data.maven.
- The types involved
scaladex.data.maven.PomsReader.ScaladexModelResolver→scaladex.data.maven.Dependencyscaladex.data.maven.PomsReader.ScaladexModelResolver→scaladex.data.maven.Repository
- Direction
- data.maven.PomsReader uses data.maven, so a change to data.maven can break data.maven.PomsReader, while a change to data.maven.PomsReader can't break data.maven.
- Position
- Below the diagonal: data.maven.PomsReader uses a module listed above it, which is the healthy direction.
35→2 infra uses core.service.MavenCentralIndexClient✕
- Connections
- 3 pairs of types, where a type in infra uses a type in core.service.MavenCentralIndexClient.
- The types involved
scaladex.infra.MavenCentralIndexClientImpl→scaladex.core.service.MavenCentralIndexClient.Recordscaladex.infra.MavenCentralIndexClientImpl→scaladex.core.service.MavenCentralIndexClient.Resultscaladex.infra.MavenCentralIndexParser→scaladex.core.service.MavenCentralIndexClient.Record
- Direction
- infra uses core.service.MavenCentralIndexClient, so a change to core.service.MavenCentralIndexClient can break infra, while a change to infra can't break core.service.MavenCentralIndexClient.
- Position
- Below the diagonal: infra uses a module listed above it, which is the healthy direction.
35→3 infra uses core.util✕
- Connections
- 1 pair of types, where a type in infra uses a type in core.util.
- The types involved
scaladex.infra.GithubClientImpl→scaladex.core.util.Secret
- Direction
- infra uses core.util, so a change to core.util can break infra, while a change to infra can't break core.util.
- Position
- Below the diagonal: infra uses a module listed above it, which is the healthy direction.
35→8 infra uses core.model.search✕
- Connections
- 7 pairs of types, where a type in infra uses a type in core.model.search.
- The types involved
scaladex.infra.ElasticsearchEngine→scaladex.core.model.search.AwesomeParamsscaladex.infra.ElasticsearchEngine→scaladex.core.model.search.Pagescaladex.infra.ElasticsearchEngine→scaladex.core.model.search.PageParamsscaladex.infra.ElasticsearchEngine→scaladex.core.model.search.ProjectDocumentscaladex.infra.ElasticsearchEngine→scaladex.core.model.search.ProjectHitscaladex.infra.ElasticsearchEngine→scaladex.core.model.search.SearchParamsscaladex.infra.ElasticsearchEngine→scaladex.core.model.search.Sorting
- Direction
- infra uses core.model.search, so a change to core.model.search can break infra, while a change to infra can't break core.model.search.
- Position
- Below the diagonal: infra uses a module listed above it, which is the healthy direction.
35→10 infra uses infra.config✕
- Connections
- 1 pair of types, where a type in infra uses a type in infra.config.
- The types involved
scaladex.infra.DataPaths→scaladex.infra.config.FilesystemConfig
- Direction
- infra uses infra.config, so a change to infra.config can break infra, while a change to infra can't break infra.config.
- Position
- Below the diagonal: infra uses a module listed above it, which is the healthy direction.
35→11 infra uses core.model✕
- Connections
- 31 pairs of types, where a type in infra uses a type in core.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
scaladex.infra.ElasticsearchEngine→scaladex.core.model.BinaryVersionscaladex.infra.ElasticsearchEngine→scaladex.core.model.Categoryscaladex.infra.ElasticsearchEngine→scaladex.core.model.GithubIssuescaladex.infra.ElasticsearchEngine→scaladex.core.model.Languagescaladex.infra.ElasticsearchEngine→scaladex.core.model.Platformscaladex.infra.ElasticsearchEngine→scaladex.core.model.TopicCountscaladex.infra.FilesystemStorage→scaladex.core.model.Artifactscaladex.infra.FilesystemStorage→scaladex.core.model.ArtifactDependencyscaladex.infra.FilesystemStorage→scaladex.core.model.Projectscaladex.infra.GithubClientImpl→scaladex.core.model.GithubCommitActivityscaladex.infra.GithubClientImpl→scaladex.core.model.GithubInfoscaladex.infra.GithubClientImpl→scaladex.core.model.GithubResponsescaladex.infra.GithubClientImpl→scaladex.core.model.UserInfoscaladex.infra.GithubClientImpl→scaladex.core.model.UserStatescaladex.infra.MavenCentralClientImpl→scaladex.core.model.Versionscaladex.infra.MavenCentralIndexClientImpl→scaladex.core.model.IndexCursorscaladex.infra.SqlDatabase→scaladex.core.model.Artifactscaladex.infra.SqlDatabase→scaladex.core.model.ArtifactDependencyscaladex.infra.SqlDatabase→scaladex.core.model.DiscoveredGroupIdscaladex.infra.SqlDatabase→scaladex.core.model.GithubInfoscaladex.infra.SqlDatabase→scaladex.core.model.GithubStatusscaladex.infra.SqlDatabase→scaladex.core.model.IndexCursorscaladex.infra.SqlDatabase→scaladex.core.model.Languagescaladex.infra.SqlDatabase→scaladex.core.model.Platformscaladex.infra.SqlDatabase→scaladex.core.model.Project
- Direction
- infra uses core.model, so a change to core.model can break infra, while a change to infra can't break core.model.
- Position
- Below the diagonal: infra uses a module listed above it, which is the healthy direction.
35→23 infra uses core.service✕
- Connections
- 8 pairs of types, where a type in infra uses a type in core.service.
- The types involved
scaladex.infra.CoursierResolver→scaladex.core.service.PomResolverscaladex.infra.ElasticsearchEngine→scaladex.core.service.SearchEnginescaladex.infra.FilesystemStorage→scaladex.core.service.Storagescaladex.infra.GithubClientImpl→scaladex.core.service.GithubClientscaladex.infra.MavenCentralClientImpl→scaladex.core.service.MavenCentralClientscaladex.infra.MavenCentralIndexClientImpl→scaladex.core.service.MavenCentralIndexClientscaladex.infra.MavenCentralIndexParser→scaladex.core.service.MavenCentralIndexClientscaladex.infra.SqlDatabase→scaladex.core.service.SchedulerDatabase
- Direction
- infra uses core.service, so a change to core.service can break infra, while a change to infra can't break core.service.
- Position
- Below the diagonal: infra uses a module listed above it, which is the healthy direction.
35→27 infra uses infra.github.GithubModel✕
- Connections
- 6 pairs of types, where a type in infra uses a type in infra.github.GithubModel.
- The types involved
scaladex.infra.GithubClientImpl→scaladex.infra.github.GithubModel.CommunityProfilescaladex.infra.GithubClientImpl→scaladex.infra.github.GithubModel.Contributorscaladex.infra.GithubClientImpl→scaladex.infra.github.GithubModel.GraphQLPagescaladex.infra.GithubClientImpl→scaladex.infra.github.GithubModel.OpenIssuescaladex.infra.GithubClientImpl→scaladex.infra.github.GithubModel.RepoWithPermissionscaladex.infra.GithubClientImpl→scaladex.infra.github.GithubModel.Repository
- Direction
- infra uses infra.github.GithubModel, so a change to infra.github.GithubModel can break infra, while a change to infra can't break infra.github.GithubModel.
- Position
- Below the diagonal: infra uses a module listed above it, which is the healthy direction.
36→8 server.route uses core.model.search✕
- Connections
- 4 pairs of types, where a type in server.route uses a type in core.model.search.
- The types involved
scaladex.server.route.AwesomePages→scaladex.core.model.search.AwesomeParamsscaladex.server.route.AwesomePages→scaladex.core.model.search.PageParamsscaladex.server.route.SearchPages→scaladex.core.model.search.PageParamsscaladex.server.route.SearchPages→scaladex.core.model.search.SearchParams
- Direction
- server.route uses core.model.search, so a change to core.model.search can break server.route, while a change to server.route can't break core.model.search.
- Position
- Below the diagonal: server.route uses a module listed above it, which is the healthy direction.
36→11 server.route uses core.model✕
- Connections
- 16 pairs of types, where a type in server.route uses a type in core.model.
- The types involved
scaladex.server.route.AdminPage→scaladex.core.model.UserStatescaladex.server.route.ArtifactPages→scaladex.core.model.Artifactscaladex.server.route.ArtifactPages→scaladex.core.model.Projectscaladex.server.route.ArtifactPages→scaladex.core.model.UserStatescaladex.server.route.AuthenticationApi→scaladex.core.model.UserStatescaladex.server.route.AwesomePages→scaladex.core.model.Categoryscaladex.server.route.AwesomePages→scaladex.core.model.UserStatescaladex.server.route.Badges→scaladex.core.model.BinaryVersionscaladex.server.route.Badges→scaladex.core.model.Platformscaladex.server.route.Badges→scaladex.core.model.Projectscaladex.server.route.FrontPage→scaladex.core.model.UserStatescaladex.server.route.InsightsPages→scaladex.core.model.ScalaVersionInsightscaladex.server.route.InsightsPages→scaladex.core.model.UserStatescaladex.server.route.ProjectPages→scaladex.core.model.Projectscaladex.server.route.ProjectPages→scaladex.core.model.UserStatescaladex.server.route.SearchPages→scaladex.core.model.UserState
- Direction
- server.route uses core.model, so a change to core.model can break server.route, while a change to server.route can't break core.model.
- Position
- Below the diagonal: server.route uses a module listed above it, which is the healthy direction.
36→24 server.route uses core.web✕
- Connections
- 2 pairs of types, where a type in server.route uses a type in core.web.
- The types involved
scaladex.server.route.ProjectPages→scaladex.core.web.ArtifactPageParamsscaladex.server.route.ProjectPages→scaladex.core.web.ArtifactsPageParams
- Direction
- server.route uses core.web, so a change to core.web can break server.route, while a change to server.route can't break core.web.
- Position
- Below the diagonal: server.route uses a module listed above it, which is the healthy direction.
37→3 server.route.api uses core.util✕
- Connections
- 2 pairs of types, where a type in server.route.api uses a type in core.util.
- The types involved
scaladex.server.route.api.ApiEndpointsImpl→scaladex.core.util.Secretscaladex.server.route.api.PublishApi→scaladex.core.util.Secret
- Direction
- server.route.api uses core.util, so a change to core.util can break server.route.api, while a change to server.route.api can't break core.util.
- Position
- Below the diagonal: server.route.api uses a module listed above it, which is the healthy direction.
37→8 server.route.api uses core.model.search✕
- Connections
- 1 pair of types, where a type in server.route.api uses a type in core.model.search.
- The types involved
scaladex.server.route.api.ApiEndpointsImpl→scaladex.core.model.search.ProjectDocument
- Direction
- server.route.api uses core.model.search, so a change to core.model.search can break server.route.api, while a change to server.route.api can't break core.model.search.
- Position
- Below the diagonal: server.route.api uses a module listed above it, which is the healthy direction.
37→11 server.route.api uses core.model✕
- Connections
- 4 pairs of types, where a type in server.route.api uses a type in core.model.
- The types involved
scaladex.server.route.api.ApiEndpointsImpl→scaladex.core.model.Projectscaladex.server.route.api.ApiEndpointsImpl→scaladex.core.model.UserStatescaladex.server.route.api.OldSearchApi→scaladex.core.model.BinaryVersionscaladex.server.route.api.PublishApi→scaladex.core.model.UserState
- Direction
- server.route.api uses core.model, so a change to core.model can break server.route.api, while a change to server.route.api can't break core.model.
- Position
- Below the diagonal: server.route.api uses a module listed above it, which is the healthy direction.
37→15 server.route.api uses core.api✕
- Connections
- 5 pairs of types, where a type in server.route.api uses a type in core.api.
- The types involved
scaladex.server.route.api.ApiDocumentation→scaladex.core.api.Endpointsscaladex.server.route.api.ApiEndpointsImpl→scaladex.core.api.Endpointsscaladex.server.route.api.ApiEndpointsImpl→scaladex.core.api.ProjectResponsescaladex.server.route.api.ApiEndpointsImpl→scaladex.core.api.SearchResultscaladex.server.route.api.ApiEndpointsImpl→scaladex.core.api.UserResponse
- Direction
- server.route.api uses core.api, so a change to core.api can break server.route.api, while a change to server.route.api can't break core.api.
- Position
- Below the diagonal: server.route.api uses a module listed above it, which is the healthy direction.
38→8 view uses core.model.search✕
- Connections
- 2 pairs of types, where a type in view uses a type in core.model.search.
- The types involved
scaladex.view.html→scaladex.core.model.search.AwesomeParamsscaladex.view.html→scaladex.core.model.search.SearchParams
- Direction
- view uses core.model.search, so a change to core.model.search can break view, while a change to view can't break core.model.search.
- Position
- Below the diagonal: view uses a module listed above it, which is the healthy direction.
38→11 view uses core.model✕
- Connections
- 4 pairs of types, where a type in view uses a type in core.model.
- The types involved
scaladex.view.html→scaladex.core.model.Artifactscaladex.view.html→scaladex.core.model.BinaryVersionscaladex.view.html→scaladex.core.model.Categoryscaladex.view.html→scaladex.core.model.LabeledLink
- Direction
- view uses core.model, so a change to core.model can break view, while a change to view can't break core.model.
- Position
- Below the diagonal: view uses a module listed above it, which is the healthy direction.
38→24 view uses core.web✕
- Connections
- 1 pair of types, where a type in view uses a type in core.web.
- The types involved
scaladex.view.html→scaladex.core.web.ArtifactsPageParams
- Direction
- view uses core.web, so a change to core.web can break view, while a change to view can't break core.web.
- Position
- Below the diagonal: view uses a module listed above it, which is the healthy direction.
39→3 server.service uses core.util✕
- Connections
- 1 pair of types, where a type in server.service uses a type in core.util.
- The types involved
scaladex.server.service.UserSessionService→scaladex.core.util.Secret
- Direction
- server.service uses core.util, so a change to core.util can break server.service, while a change to server.service can't break core.util.
- Position
- Below the diagonal: server.service uses a module listed above it, which is the healthy direction.
39→4 server.service uses core.model.Artifact✕
- Connections
- 4 pairs of types, where a type in server.service uses a type in core.model.Artifact.
- The types involved
scaladex.server.service.MavenCentralService→scaladex.core.model.Artifact.ArtifactIdscaladex.server.service.MavenCentralService→scaladex.core.model.Artifact.GroupIdscaladex.server.service.MavenCentralService→scaladex.core.model.Artifact.Namescaladex.server.service.MavenCentralService→scaladex.core.model.Artifact.Reference
- Direction
- server.service uses core.model.Artifact, so a change to core.model.Artifact can break server.service, while a change to server.service can't break core.model.Artifact.
- Position
- Below the diagonal: server.service uses a module listed above it, which is the healthy direction.
39→9 server.service uses data.cleanup✕
- Connections
- 1 pair of types, where a type in server.service uses a type in data.cleanup.
- The types involved
scaladex.server.service.ArtifactConverter→scaladex.data.cleanup.BinaryVersionLookup
- Direction
- server.service uses data.cleanup, so a change to data.cleanup can break server.service, while a change to server.service can't break data.cleanup.
- Position
- Below the diagonal: server.service uses a module listed above it, which is the healthy direction.
39→11 server.service uses core.model✕
- Connections
- 15 pairs of types, where a type in server.service uses a type in core.model.
- The types involved
scaladex.server.service.AdminService→scaladex.core.model.UserStatescaladex.server.service.ArtifactConverter→scaladex.core.model.Versionscaladex.server.service.ArtifactService→scaladex.core.model.Artifactscaladex.server.service.ArtifactService→scaladex.core.model.ArtifactDependencyscaladex.server.service.ArtifactService→scaladex.core.model.Versionscaladex.server.service.DependencyUpdater→scaladex.core.model.Projectscaladex.server.service.DiscoveryService→scaladex.core.model.DiscoveredGroupIdscaladex.server.service.DiscoveryService→scaladex.core.model.IndexCursorscaladex.server.service.GithubUpdater→scaladex.core.model.GithubResponsescaladex.server.service.GithubUpdater→scaladex.core.model.GithubStatusscaladex.server.service.JobScheduler→scaladex.core.model.UserStatescaladex.server.service.PublishProcess→scaladex.core.model.UserStatescaladex.server.service.SearchSynchronizer→scaladex.core.model.Projectscaladex.server.service.UserSessionService→scaladex.core.model.GithubResponsescaladex.server.service.UserSessionService→scaladex.core.model.UserState
- Direction
- server.service uses core.model, so a change to core.model can break server.service, while a change to server.service can't break core.model.
- Position
- Below the diagonal: server.service uses a module listed above it, which is the healthy direction.
39→26 server.service uses data.maven✕
- Connections
- 2 pairs of types, where a type in server.service uses a type in data.maven.
- The types involved
scaladex.server.service.ArtifactConverter→scaladex.data.maven.ArtifactModelscaladex.server.service.PublishProcess→scaladex.data.maven.ArtifactModel
- Direction
- server.service uses data.maven, so a change to data.maven can break server.service, while a change to server.service can't break data.maven.
- Position
- Below the diagonal: server.service uses a module listed above it, which is the healthy direction.
39→38 server.service uses view✕
- Connections
- 2 pairs of types, where a type in server.service uses a type in view.
- The types involved
scaladex.server.service.JobScheduler→scaladex.view.Jobscaladex.server.service.TaskRunner→scaladex.view.Task
- Direction
- server.service uses view, so a change to view can break server.service, while a change to server.service can't break view.
- Position
- Below the diagonal: server.service uses a module listed above it, which is the healthy direction.
40→3 server uses core.util✕
- Connections
- 1 pair of types, where a type in server uses a type in core.util.
- The types involved
scaladex.server.GithubAuthImpl→scaladex.core.util.Secret
- Direction
- server uses core.util, so a change to core.util can break server, while a change to server can't break core.util.
- Position
- Below the diagonal: server uses a module listed above it, which is the healthy direction.
40→8 server uses core.model.search✕
- Connections
- 1 pair of types, where a type in server uses a type in core.model.search.
- The types involved
scaladex.server.route→scaladex.core.model.search.PageParams
- Direction
- server uses core.model.search, so a change to core.model.search can break server, while a change to server can't break core.model.search.
- Position
- Below the diagonal: server uses a module listed above it, which is the healthy direction.
40→11 server uses core.model✕
- Connections
- 3 pairs of types, where a type in server uses a type in core.model.
- The types involved
scaladex.server.GithubAuthImpl→scaladex.core.model.UserInfoscaladex.server.GithubAuthImpl→scaladex.core.model.UserStatescaladex.server.route→scaladex.core.model.Version
- Direction
- server uses core.model, so a change to core.model can break server, while a change to server can't break core.model.
- Position
- Below the diagonal: server uses a module listed above it, which is the healthy direction.
40→23 server uses core.service✕
- Connections
- 3 pairs of types, where a type in server uses a type in core.service.
- The types involved
scaladex.server.GithubAuthImpl→scaladex.core.service.GithubAuthscaladex.server.Server→scaladex.core.service.GithubClientscaladex.server.Server→scaladex.core.service.MavenCentralClient
- Direction
- server uses core.service, so a change to core.service can break server, while a change to server can't break core.service.
- Position
- Below the diagonal: server uses a module listed above it, which is the healthy direction.
40→30 server uses server.config✕
- Connections
- 1 pair of types, where a type in server uses a type in server.config.
- The types involved
scaladex.server.Server→scaladex.server.config.ServerConfig
- Direction
- server uses server.config, so a change to server.config can break server, while a change to server can't break server.config.
- Position
- Below the diagonal: server uses a module listed above it, which is the healthy direction.
40→35 server uses infra✕
- Connections
- 2 pairs of types, where a type in server uses a type in infra.
- The types involved
scaladex.server.Server→scaladex.infra.ElasticsearchEnginescaladex.server.Server→scaladex.infra.SqlDatabase
- Direction
- server uses infra, so a change to infra can break server, while a change to server can't break infra.
- Position
- Below the diagonal: server uses a module listed above it, which is the healthy direction.
40→39 server uses server.service✕
- Connections
- 2 pairs of types, where a type in server uses a type in server.service.
- The types involved
scaladex.server.Server→scaladex.server.service.AdminServicescaladex.server.Server→scaladex.server.service.PublishProcess
- Direction
- server uses server.service, so a change to server.service can break server, while a change to server can't break server.service.
- Position
- Below the diagonal: server 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 19 | High / Critical |
| A07:2025 — Authentication Failures | 13 | High / Critical |
Roadmap
Top priorities: 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; Resolve the 11 REDACTED finding(s) in Secrets (history) — start with REDACTED (5), REDACTED (4), REDACTED (2); Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8). | +6.9 pts | Low | Static Analysis (SAST) |
| 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. | +8.5 pts | Medium | Web-Security Posture |
| Resolve the 11 REDACTED finding(s) in Secrets (history) — start with REDACTED (5), REDACTED (4), REDACTED (2). | +7.8 pts | Medium | Secrets (history) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +2.8 pts | Low | Static Analysis (SAST) |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +3.2 pts | Medium | Keyboard semantics |
| Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). | +1.3 pts | Low | Secrets (history) |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +0.9 pts | Low | ADR Quality |
| Interpolated log message defeats structured logging | +1.8 pts | Medium | Structured logging |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| modules/infra/src/main/scala/scaladex/infra/ElasticsearchEngine.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| modules/core/shared/src/main/scala/scaladex/core/model/Artifact.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| modules/server/src/test/scala/scaladex/server/route/api/ApiEndpointsImplTests.scala | 6.5 | Mixed | Explicit Debt: TodoComment |
| modules/server/src/main/scala/scaladex/server/service/PublishProcess.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| modules/template/src/main/twirl/scaladex/view/main.scala.html | 7.2 | Near-clean | Cyclomatic Complexity: main.scala.html.buildCombobox (cyclomatic 17) |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| modules/server-it/src/test/scala/scaladex/RelevanceTest.scala | 7.3 | Near-clean | Explicit Debt: TodoComment |
| modules/data/src/main/scala/scaladex/data/maven/PomsReader.scala | 7.3 | Near-clean | Explicit Debt: TodoComment |
| modules/server/src/main/scala/scaladex/server/route/ProjectPages.scala | 7.8 | Near-clean | Cyclomatic Complexity: ProjectPages.route (cyclomatic 20) |
| modules/infra/src/main/scala/scaladex/infra/MavenCentralIndexClientImpl.scala | 7.8 | Near-clean | Cognitive Complexity: MavenCentralIndexParser.parseChunk (cognitive 27) |
| modules/server/src/main/scala/scaladex/server/route/api/OldSearchApi.scala | 7.8 | Near-clean | Cognitive Complexity: OldSearchApi.parseBinaryVersion (cognitive 17) |
| modules/server/src/main/scala/scaladex/server/route/api/PublishApi.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
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 67 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 — 67 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, 162 of 178 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. 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, 62 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. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because repo1.maven.org — the registry that answers it — was asked and did not reply (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/github/pjfanning/pekko-http-circe_3/maven-metadata.xml). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add repo1.maven.org to the allowlist and re-run — not to build anything.
- 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 an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D30 Dependency Vulnerabilities — 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. Osv: osv-scanner exited 127 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 127 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the 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. `modules/core/shared/src/main/scala/scaladex/core/api/ProjectSettingsPatch.scala`, `modules/core/shared/src/main/scala/scaladex/core/model/ArtifactDependency.scala`, `modules/core/shared/src/main/scala/scaladex/core/model/GithubStatus.scala`, `modules/core/shared/src/main/scala/scaladex/core/model/Version.scala`, `modules/core/shared/src/main/scala/scaladex/core/util/ScalaExtensions.scala`, … (+11 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.
- D43 Malicious 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. Osv: osv-scanner exited 127 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 127 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 33 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- 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.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ProjectPages.route at 20.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ProjectPages.route (cyclomatic 20), main.scala.html.buildCombobox (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
14 method(s) exceeded the cognitive complexity threshold of 15; the worst was FrontPage.frontPage at 76.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with FrontPage.frontPage (cognitive 76), ProjectPages.route (cognitive 40), DiscoveryService.discover (cognitive 32). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 7.2 to about 8.2/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- 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
3 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with ElasticsearchEngine.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with OldSearchApi.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with main.scala.html. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
3 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with Artifact.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (11–13 lines × 2) finding(s) in Code Duplication — start with MavenCentralIndexClientImpl.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (7 lines × 3) finding(s) in Code Duplication — start with Artifact.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
7 production modules (sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 1 module(s) off the main sequence, with abstractness counted on 6 of the 7 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 19 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with ElasticsearchEngine.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
278 test methods: 278 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 278 test case(s) across 50 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
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
Top hotspots: modules/template/src/main/twirl/scaladex/view/main.scala.html (18×17=306); modules/server/src/main/scala/scaladex/server/route/ProjectPages.scala (13×20=260)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with main.scala.html, ProjectPages.scala. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
19 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is modules/infra/src/main/scala/scaladex/infra/sql/DoobieMappings.scala. Counted over 72 of the 193 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 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
17 deducted task-comment markers across 12426 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 17 TodoComment finding(s) in Explicit Debt — start with ApiEndpointsImplTests.scala (6), RelevanceTest.scala (2), ElasticsearchEngine.scala (2). — One of this dimension's main actionable groups (17 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.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
11 finding(s): 0 critical, 11 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 11 REDACTED finding(s) in Secrets (history) — start with REDACTED (5), REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (11 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)
19 finding(s): 0 critical, 19 high, 0 medium, 0 low. 10 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 29 file(s) — `modules/core/shared/src/main/scala/scaladex/core/api/ProjectSettingsPatch.scala`, `modules/core/shared/src/main/scala/scaladex/core/model/Version.scala`, `modules/data/src/main/scala/scaladex/data/GenerateFeeders.scala`, `modules/infra/src/main/scala/scaladex/infra/MavenCentralIndexClientImpl.scala`, `modules/infra/src/main/scala/scaladex/infra/SqlDatabase.scala`, … (+24 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 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 10 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 (10 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
18 of 72 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is modules/core/shared/src/main/scala/scaladex/core/model/License.scala. Counted over 72 of the 193 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 18 Orphaned file finding(s) in Knowledge Freshness — start with License.scala, MetaCategory.scala, Category.scala. — One of this dimension's main actionable groups (18 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: WebDatabase.scala↔SqlDatabase.scala 95%; SqlDatabase.scala↔REDACTED 52%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with WebDatabase.scala, SqlDatabase.scala. — One of this dimension's main actionable groups (2 warning-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×2) — modules/template/src/main/twirl/scaladex/view/insights.scala.html:37, modules/template/src/main/twirl/scaladex/view/project/project.scala.html:69
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×2) — modules/template/src/main/twirl/scaladex/view/project/badges.scala.html:40, modules/template/src/main/twirl/scaladex/view/project/badges.scala.html:47
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×12) — modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:75, modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:79, modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:94, …
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:142
- This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. — modules/template/src/main/twirl/scaladex/view/project/editproject.scala.html:159
- A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — modules/template/src/main/twirl/scaladex/view/project/versionMatrix.scala.html:70
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×11) — modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:26, modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:68, modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:163, …
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — modules/template/src/main/twirl/scaladex/view/main.scala.html:18, modules/template/src/main/twirl/scaladex/view/project/scaladoc.scala.html:7
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.
AC4 · Keyboard semantics
- An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×2) — modules/template/src/main/twirl/scaladex/view/project/artifacts.scala.html:51, modules/template/src/main/twirl/scaladex/view/project/versions.scala.html:61
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
- This role is not a valid WAI-ARIA role, so assistive tech ignores it. Use a valid role (or the native element). (×6) — modules/template/src/main/twirl/scaladex/view/project/headproject.scala.html:113, modules/template/src/main/twirl/scaladex/view/project/headproject.scala.html:115, modules/template/src/main/twirl/scaladex/view/project/headproject.scala.html:116, …
What to do
- Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
AC6 · Visual & motion safety
- `.markdown-body .anchor:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — modules/server/src/main/assets/css/partials/_github.scss:46
- `.btn.active` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — modules/server/src/main/assets/css/base/_buttons.scss:31
- `.dropdown-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — modules/server/src/main/assets/css/base/_navigation.scss:21
- `.progress-bar` moves (`transition: width 0.6s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — modules/server/src/main/assets/css/base/_progress.scss:23
- `.switch .switch-track::after` moves (`transition: transform 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — modules/server/src/main/assets/css/base/_toggles.scss:39
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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 33 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
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `SchedulerDatabase` declares 28 abstract members: `getAllProjects`, `getAllProjectArtifacts`, `insertProject`, `updateProjectCreationDate`, `computeProjectsCreationDates`, `getProjectDependencies`, `computeProjectDependencies`, `insertProjectDependencies`, `deleteProjectDependencies`, `insertArtifacts`, `insertDependencies`, `updateArtifacts`, `updateArtifactReleaseDate`, `getGroupIds`, `getGroupIds`, `getArtifactIds`, `getArtifactRefs`, `getArtifactRefs`, `getArtifactRefs`, `updateLatestVersion`, `insertDiscoveredGroupIds`, `getAllDiscoveredGroupIds`, `getPendingDiscoveredGroupIdsToSync`, `updateDiscoveredGroupIdSync`, `updateDiscoveredGroupIdError`, `getMavenIndexCursor`, `setMavenIndexCursor`, `getProjectRefsByGroupId`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. Those 28 declarations carry 25 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 25 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — modules/core/shared/src/main/scala/scaladex/core/service/SchedulerDatabase.scala:15
- `SearchEngine` declares 18 abstract members under just 11 distinct name(s): `insert`, `delete`, `count`, `countByTopics`, `countByLanguages`, `countByPlatforms`, `getMostDependedUpon`, `getLatest`, `find`, `autocomplete`, `countByTopics`, `countByLanguages`, `countByPlatforms`, `find`, `countByLanguages`, `countByPlatforms`, `find`, `findRefs`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 18 separate responsibilities: a caller binds to 11 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 18 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — modules/core/shared/src/main/scala/scaladex/core/service/SearchEngine.scala:18
- `WebDatabase` declares 37 abstract members: `insertArtifact`, `getArtifactVersions`, `getArtifacts`, `getArtifact`, `getLatestArtifact`, `getLatestArtifacts`, `getAllArtifacts`, `countArtifacts`, `getDirectDependencies`, `getReverseDependencies`, `countReverseDependencies`, `insertProjectRef`, `updateProjectSettings`, `getAllProjectsStatuses`, `getProject`, `getProjectArtifactRefs`, `getProjectArtifactRefs`, `getProjectArtifactRefs`, `getProjectArtifacts`, `getProjectArtifacts`, `getProjectLatestArtifacts`, `getFormerReferences`, `countVersions`, `updateGithubInfoAndStatus`, `updateGithubStatus`, `moveProject`, `countProjectDependents`, `getProjectDependencies`, `countProjectDependencies`, `getProjectReverseDependencies`, `getScalaVersionInsights`, `getScala3MigrationInsights`, `insertUser`, `updateUser`, `getUser`, `getAllUsers`, `deleteUser`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. Those 37 declarations carry 34 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 34 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — modules/core/shared/src/main/scala/scaladex/core/service/WebDatabase.scala:9
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
- Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- `resolveModel` 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. — modules/data/src/main/scala/scaladex/data/maven/PomsReader.scala:50
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
- `resolveModel` 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. — modules/data/src/main/scala/scaladex/data/maven/PomsReader.scala:50
- A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead. — modules/infra/src/main/scala/scaladex/infra/CommonAkkaHttpClient.scala:47
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)
- 100 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
- Review the README against recent changes; refresh the parts that drifted.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P2 · Observability
What to do
- 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
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `gitsubmodule` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P8 · Schema migrations
PF3 · Async & latency hygiene
- `resolve` 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. — modules/infra/src/main/scala/scaladex/infra/CoursierResolver.scala:42
- `waitUntilReady` 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. — modules/infra/src/main/scala/scaladex/infra/ElasticsearchEngine.scala:68
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.
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. — modules/core/shared/src/main/scala/scaladex/core/model/Sha1.scala:5
- `//cdnjs.cloudflare.com/ajax/libs/emojify.js/1.1.0/js/emojify.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 3 such include(s) across the repository's markup. — modules/template/src/main/twirl/scaladex/view/main.scala.html:158
- 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: modules/server/src/main/scala/scaladex/server/Server.scala:133 — `newServerAt`.
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Scala server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: modules/server/src/main/scala/scaladex/server/Server.scala:133 — `newServerAt`.
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.
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
- 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`).
- Set security response headers on what the server sends — keep Play's `SecurityHeadersFilter` enabled, wrap akka/pekko-http routes in `respondWithHeaders(RawHeader("X-Content-Type-Options", "nosniff"), …)`, or add an http4s middleware that sets `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
- `len` is read from the bytes being parsed at line 174 (`readInt`), then used to size a `new Array[Byte]` at line 175 — and nowhere in its scope is `len` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). Whoever wrote those bytes therefore chooses the allocation directly: a 32-bit length asks for up to 2 GiB before a single byte of the payload is known to exist, which either exhausts the heap with an `OutOfMemoryError` or, negative, throws `NegativeArraySizeException` out of a parser whose failure path was written for malformed input, not for hostile input. Bound `len` against the bytes actually remaining and a maximum the format allows before allocating. — modules/infra/src/main/scala/scaladex/infra/MavenCentralIndexClientImpl.scala:175
What to do
- Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
- `Files.list(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.iterator` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.list(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. (×2) — modules/infra/src/main/scala/scaladex/infra/FilesystemStorage.scala:53, modules/infra/src/main/scala/scaladex/infra/FilesystemStorage.scala:55
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 _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — project/Postgres.scala:119
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug` at line 27 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — modules/server/src/main/scala/scaladex/server/HttpRequestLogging.scala:27
- `debug` at line 29 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — modules/server/src/main/scala/scaladex/server/HttpRequestLogging.scala:29
- `debug` at line 90 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — modules/infra/src/main/scala/scaladex/infra/CommonAkkaHttpClient.scala:90
- `debug` at line 91 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — modules/infra/src/main/scala/scaladex/infra/CommonAkkaHttpClient.scala:91
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- No build over this repository's 185 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| 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 |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 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 | 51% | Adequate — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 78% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 64% | Strong | Solid. |
| Security | 29% | Weak — gated by D28, D29, S1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 34% | Weak — gated by AC4, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 70% | Strong | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 2 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.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 47 check(s) not relevant to this codebase
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — 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.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~3865 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 — Dependency currency not established — repo1.maven.org did not answer
- D14 License Compliance — Not scored — this repository's 18 pinned sbt dependency coordinate(s) were read from its 7 sbt build file(s), but Maven Central could not be asked for the licence of 16 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/github/pjfanning/pekko-http-circe_3/3.12.0/pekko-http-circe_3-3.12.0.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.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, Scala, html 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 .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.
- D30 Dependency Vulnerabilities — Scanner failed to run — not a clean result
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 16 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.
- D43 Malicious Dependencies — Scanner failed to run — not a clean result
- 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): 169 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala was 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
- 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.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 54 finding(s)
- <input> without a programmatic label modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:75
- <input> without a programmatic label modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:79
- <input> without a programmatic label modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:94
- <input> without a programmatic label modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:98
- <input> without a programmatic label modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:113
- <input> without a programmatic label modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:117
- <input> without a programmatic label modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:142
- <input> without a programmatic label modules/template/src/main/twirl/scaladex/view/project/editproject.scala.html:52
- <input> without a programmatic label modules/template/src/main/twirl/scaladex/view/project/editproject.scala.html:163
- <input> without a programmatic label modules/template/src/main/twirl/scaladex/view/project/editproject.scala.html:167
- <input> without a programmatic label modules/template/src/main/twirl/scaladex/view/project/editproject.scala.html:176
- <input> without a programmatic label modules/template/src/main/twirl/scaladex/view/project/editproject.scala.html:180
- <input> without a programmatic label modules/template/src/main/twirl/scaladex/view/searchinput.scala.html:8
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <img> without a text alternative modules/template/src/main/twirl/scaladex/view/project/badges.scala.html:40
- <img> without a text alternative modules/template/src/main/twirl/scaladex/view/project/badges.scala.html:47
- <label> that labels no control modules/template/src/main/twirl/scaladex/view/project/editproject.scala.html:159
- Link with no accessible name modules/template/src/main/twirl/scaladex/view/project/versionMatrix.scala.html:70
- Invalid ARIA role "project" modules/template/src/main/twirl/scaladex/view/project/headproject.scala.html:113
- Invalid ARIA role "artifacts" modules/template/src/main/twirl/scaladex/view/project/headproject.scala.html:115
- Invalid ARIA role "versions" modules/template/src/main/twirl/scaladex/view/project/headproject.scala.html:116
- Invalid ARIA role "dependents" modules/template/src/main/twirl/scaladex/view/project/headproject.scala.html:118
- Invalid ARIA role "badges" modules/template/src/main/twirl/scaladex/view/project/headproject.scala.html:119
- Invalid ARIA role "settings" modules/template/src/main/twirl/scaladex/view/project/headproject.scala.html:122
- REDACTED
- REDACTED
Serious — 82 finding(s)
- TodoComment modules/server-it/src/test/scala/scaladex/RelevanceTest.scala:76
- TodoComment modules/server-it/src/test/scala/scaladex/RelevanceTest.scala:106
- TodoComment modules/server/src/test/scala/scaladex/server/route/api/ApiEndpointsImplTests.scala:70
- TodoComment modules/server/src/test/scala/scaladex/server/route/api/ApiEndpointsImplTests.scala:148
- TodoComment modules/server/src/test/scala/scaladex/server/route/api/ApiEndpointsImplTests.scala:198
- TodoComment modules/server/src/test/scala/scaladex/server/route/api/ApiEndpointsImplTests.scala:109
- TodoComment modules/server/src/test/scala/scaladex/server/route/api/ApiEndpointsImplTests.scala:115
- TodoComment modules/server/src/test/scala/scaladex/server/route/api/ApiEndpointsImplTests.scala:204
- TodoComment modules/server/src/main/scala/scaladex/server/service/PublishProcess.scala:71
- TodoComment modules/server/src/main/scala/scaladex/server/route/api/PublishApi.scala:60
- TodoComment modules/infra/src/test/scala/scaladex/infra/ElasticsearchEngineTests.scala:88
- TodoComment modules/infra/src/main/scala/scaladex/infra/ElasticsearchEngine.scala:77
- TodoComment modules/infra/src/main/scala/scaladex/infra/ElasticsearchEngine.scala:482
- TodoComment modules/data/src/main/scala/scaladex/data/maven/PomsReader.scala:36
- TodoComment modules/data/src/main/scala/scaladex/data/maven/PomsReader.scala:73
- TodoComment modules/core/shared/src/main/scala/scaladex/core/model/Artifact.scala:53
- TodoComment modules/core/shared/src/main/scala/scaladex/core/model/Project.scala:6
- Heading level jumps from h2 to h5 modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:26
- Heading level jumps from h2 to h5 modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:68
- Heading level jumps from h2 to h5 modules/template/src/main/twirl/scaladex/view/admin/admin.scala.html:163
- Heading level jumps from h2 to h5 modules/template/src/main/twirl/scaladex/view/project/artifacts.scala.html:68
- Heading level jumps from h2 to h5 modules/template/src/main/twirl/scaladex/view/project/versions.scala.html:80
- Heading level jumps from h2 to h4 modules/template/src/main/twirl/scaladex/view/frontpage.scala.html:46
- Heading level jumps from h2 to h4 modules/template/src/main/twirl/scaladex/view/frontpage.scala.html:76
- Heading level jumps from h2 to h4 modules/template/src/main/twirl/scaladex/view/project/artifact.scala.html:101
- Heading level jumps from h2 to h4 modules/template/src/main/twirl/scaladex/view/search/result.scala.html:24
- Focus outline removed in CSS without a :focus replacement modules/server/src/main/assets/css/partials/_github.scss:46
- Focus outline removed in CSS without a :focus replacement modules/server/src/main/assets/css/base/_buttons.scss:31
- Focus outline removed in CSS without a :focus replacement modules/server/src/main/assets/css/base/_navigation.scss:21
- <canvas> without a text alternative modules/template/src/main/twirl/scaladex/view/insights.scala.html:37
- <canvas> without a text alternative modules/template/src/main/twirl/scaladex/view/project/project.scala.html:69
- Page without a main landmark modules/template/src/main/twirl/scaladex/view/main.scala.html:18
- Page without a main landmark modules/template/src/main/twirl/scaladex/view/project/scaladoc.scala.html:7
- Anchor without href modules/template/src/main/twirl/scaladex/view/project/artifacts.scala.html:51
- Anchor without href modules/template/src/main/twirl/scaladex/view/project/versions.scala.html:61
- Animation without a prefers-reduced-motion guard modules/server/src/main/assets/css/base/_progress.scss:23
- Animation without a prefers-reduced-motion guard modules/server/src/main/assets/css/base/_toggles.scss:39
- Hotspot: modules/template/src/main/twirl/scaladex/view/main.scala.html modules/template/src/main/twirl/scaladex/view/main.scala.html:190
- Hotspot: modules/server/src/main/scala/scaladex/server/route/ProjectPages.scala modules/server/src/main/scala/scaladex/server/route/ProjectPages.scala:39
- Change coupling: WebDatabase.scala ↔ SqlDatabase.scala modules/core/shared/src/main/scala/scaladex/core/service/WebDatabase.scala:1
- Change coupling: SqlDatabase.scala ↔ REDACTED modules/infra/src/main/scala/scaladex/infra/SqlDatabase.scala:1
- REDACTED
- REDACTED
- Sync-over-async blocking modules/infra/src/main/scala/scaladex/infra/CoursierResolver.scala:42
- Sync-over-async blocking modules/infra/src/main/scala/scaladex/infra/ElasticsearchEngine.scala:68
- Disposable created and abandoned in the function that made it modules/infra/src/main/scala/scaladex/infra/FilesystemStorage.scala:53
- Disposable created and abandoned in the function that made it modules/infra/src/main/scala/scaladex/infra/FilesystemStorage.scala:55
- Heading level jumps from h1 to h3 modules/template/src/main/twirl/scaladex/view/awesome/awesomeScala.scala.html:57
- Heading level jumps from h4 to h6 modules/template/src/main/twirl/scaladex/view/project/artifact.scala.html:130
- Accessibility enforcement below the top rung
- ProjectPages.route (cyclomatic 20) modules/server/src/main/scala/scaladex/server/route/ProjectPages.scala:39
- main.scala.html.buildCombobox (cyclomatic 17) modules/template/src/main/twirl/scaladex/view/main.scala.html:190
- FrontPage.frontPage (cognitive 76) modules/server/src/main/scala/scaladex/server/route/FrontPage.scala:28
- ProjectPages.route (cognitive 40) modules/server/src/main/scala/scaladex/server/route/ProjectPages.scala:39
- DiscoveryService.discover (cognitive 32) modules/server/src/main/scala/scaladex/server/service/DiscoveryService.scala:38
- Init.run (cognitive 28) modules/data/src/main/scala/scaladex/data/init/Init.scala:17
- MavenCentralIndexParser.parseChunk (cognitive 27) modules/infra/src/main/scala/scaladex/infra/MavenCentralIndexClientImpl.scala:130
- PublishProcess.publishPom (cognitive 24) modules/server/src/main/scala/scaladex/server/service/PublishProcess.scala:63
- main.scala.html.buildCombobox (cognitive 23) modules/template/src/main/twirl/scaladex/view/main.scala.html:190
- GithubClientImpl.getRepoInfo (cognitive 21) modules/infra/src/main/scala/scaladex/infra/GithubClientImpl.scala:68
- MavenCentralService.findAndIndexMissingArtifacts (cognitive 21) modules/server/src/main/scala/scaladex/server/service/MavenCentralService.scala:52
- html.paginationRender (cognitive 18) modules/template/src/main/scala/scaladex/view/html/package.scala:102
- Server.main (cognitive 17) modules/server/src/main/scala/scaladex/server/Server.scala:48
- OldSearchApi.parseBinaryVersion (cognitive 17) modules/server/src/main/scala/scaladex/server/route/api/OldSearchApi.scala:40
- DependencyUpdater.updateDependencies (cognitive 17) modules/server/src/main/scala/scaladex/server/service/DependencyUpdater.scala:28
- main.scala.html.document.addEventListener("click") (cognitive 17) modules/template/src/main/twirl/scaladex/view/main.scala.html:423
- TooManyMethods: ElasticsearchEngine modules/infra/src/main/scala/scaladex/infra/ElasticsearchEngine.scala:60
- MethodTooLong: OldSearchApi.parseBinaryVersion modules/server/src/main/scala/scaladex/server/route/api/OldSearchApi.scala:40
- FunctionTooLong: main.scala.html.buildCombobox modules/template/src/main/twirl/scaladex/view/main.scala.html:190
- Members sharing a duplicated core (4 members, 50+ identical tokens) modules/core/shared/src/main/scala/scaladex/core/model/Artifact.scala:89
- Duplicated block (11–13 lines × 2) modules/infra/src/main/scala/scaladex/infra/MavenCentralIndexClientImpl.scala:43
- Duplicated block (7 lines × 3) modules/core/shared/src/main/scala/scaladex/core/model/Artifact.scala:143
- Duplicated block (6 lines × 2) modules/core/shared/src/main/scala/scaladex/core/model/Artifact.scala:100
- Off the main sequence: core
- Low cohesion: ElasticsearchEngine (LCOM4 5) modules/infra/src/main/scala/scaladex/infra/ElasticsearchEngine.scala:60
- Unfinished stub — body is `???` modules/data/src/main/scala/scaladex/data/maven/PomsReader.scala:50
- Unfinished stub — body is ??? / NotImplementedError modules/data/src/main/scala/scaladex/data/maven/PomsReader.scala:50
- README may be stale
- Weak hash algorithm modules/core/shared/src/main/scala/scaladex/core/model/Sha1.scala:5
- Third-party script without Subresource Integrity modules/template/src/main/twirl/scaladex/view/main.scala.html:158
- Length read from the parsed input is spent without ever being bounded modules/infra/src/main/scala/scaladex/infra/MavenCentralIndexClientImpl.scala:175
- Swallowed exception (caught, then discarded) project/Postgres.scala:119
Minor — 42 finding(s)
- Orphaned file modules/core/shared/src/main/scala/scaladex/core/model/License.scala:1
- Orphaned file modules/core/shared/src/main/scala/scaladex/core/model/MetaCategory.scala:1
- Orphaned file modules/core/shared/src/main/scala/scaladex/core/model/Category.scala:1
- Orphaned file modules/core/shared/src/main/scala/scaladex/core/model/Project.scala:1
- Orphaned file modules/server/src/main/scala/scaladex/server/route/AuthenticationApi.scala:1
- Orphaned file modules/data/src/main/scala/scaladex/data/maven/ArtifactModel.scala:1
- Orphaned file modules/infra/src/main/scala/scaladex/infra/FilesystemStorage.scala:1
- Orphaned file modules/server/src/main/scala/scaladex/server/service/ArtifactService.scala:1
- Orphaned file modules/core/shared/src/main/scala/scaladex/core/util/ScalaExtensions.scala:1
- Orphaned file modules/server/src/main/scala/scaladex/server/route/AwesomePages.scala:1
- Orphaned file modules/data/src/main/scala/scaladex/data/maven/PomConvert.scala:1
- Orphaned file modules/core/shared/src/main/scala/scaladex/core/model/Platform.scala:1
- Orphaned file modules/data/src/main/scala/scaladex/data/cleanup/GithubRepoExtractor.scala:1
- Orphaned file modules/core/shared/src/main/scala/scaladex/core/model/GithubInfo.scala:1
- Orphaned file modules/server/src/main/scala/scaladex/server/service/SearchSynchronizer.scala:1
- Orphaned file modules/infra/src/main/scala/scaladex/infra/Codecs.scala:1
- Orphaned file modules/core/shared/src/main/scala/scaladex/core/model/search/ProjectDocument.scala:1
- Orphaned file modules/infra/src/main/scala/scaladex/infra/elasticsearch/ElasticsearchMapping.scala:1
- Interpolated log message defeats structured logging modules/server/src/main/scala/scaladex/server/HttpRequestLogging.scala:27
- Interpolated log message defeats structured logging modules/server/src/main/scala/scaladex/server/HttpRequestLogging.scala:29
- Interpolated log message defeats structured logging modules/infra/src/main/scala/scaladex/infra/CommonAkkaHttpClient.scala:90
- Interpolated log message defeats structured logging modules/infra/src/main/scala/scaladex/infra/CommonAkkaHttpClient.scala:91
- Fat interface: SchedulerDatabase (28 abstract members) modules/core/shared/src/main/scala/scaladex/core/service/SchedulerDatabase.scala:15
- Fat interface: SearchEngine (18 abstract members) modules/core/shared/src/main/scala/scaladex/core/service/SearchEngine.scala:18
- Fat interface: WebDatabase (37 abstract members) modules/core/shared/src/main/scala/scaladex/core/service/WebDatabase.scala:9
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Duplicated predicate modules/core/shared/src/main/scala/scaladex/core/util/JsoupUtils.scala:36
- Duplicated predicate modules/server/src/main/scala/scaladex/server/service/ArtifactService.scala:72
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Orphaned files with no living knowledge
- Blanket warning suppression modules/infra/src/main/scala/scaladex/infra/CommonAkkaHttpClient.scala:47
- No ADRs
- CI build step not evidenced
- Dependabot does not watch gitsubmodule REDACTED:2
- No changelog
- No app-layer HTTPS enforcement detected
- No security response headers detected
- Scala's null is not held to the type system everywhere
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-2b487c0cfa294d9a80c0584f2c7ba7ee/history.json --exit-code 0 --source . | 12 | 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-2b487c0cfa294d9a80c0584f2c7ba7ee/tree.json --exit-code 0 --source . | 2 | 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 . | 19 | 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-8841b9f04d05430f9efe2b020f5a1cdc | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 16 file(s) — `modules/core/shared/src/main/scala/scaladex/core/api/ProjectSettingsPatch.scala`, `modules/core/shared/src/main/scala/scaladex/core/model/ArtifactDependency.scala`, `modules/core/shared/src/main/scala/scaladex/core/model/GithubStatus.scala`, `modules/core/shared/src/main/scala/scaladex/core/model/Version.scala`, `modules/core/shared/src/main/scala/scaladex/core/util/ScalaExtensions.scala`, … (+11 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-8841b9f04d05430f9efe2b020f5a1cdc | 0 | artifacts/raw/osv-scanner.json |