Executive summary
Heapy/awesome-kotlin falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 40 out of 100 and is rated Weak, and 23 of its 28 critical findings are security problems.
Production Readiness, at 33, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 3 points. Planning backups and recovery would lift Production Readiness itself, also worth about 3. Raising Production Readiness to 70 would lift the score to about 45.
Fifteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four known security holes in the packages the code depends on can be used by attackers, and two controls can't be used without a mouse. Pinning each tool to an exact version, updating the vulnerable packages and making the controls work with a keyboard would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and limiting each secret to its own step would deal with the secret exposed to more of the pipeline than needed. The form field without a label needs a label.
The product code is 18,219 lines, about €16,000 to rebuild.
If Production Readiness rose from 33 to 70, the lowest score rated Strong, the score would rise from 40 to about 45.
New since the last survey: 3 findings
- Code Duplication · Edited copy of a member (19 corresponding lines) src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt
- Code Duplication · Edited copy of a member (11 corresponding lines) app-backend/src/main/kotlin/usecases/signup/Register.kt
- Code Duplication · Duplicated block (5 lines × 2) app-backend/src/main/kotlin/usecases/version/KotlinVersionFetcher.kt
Fixed since the last survey: 9 findings
- Code Duplication · Duplicated block (5 lines × 2) app-backend/src/main/kotlin/usecases/version/KotlinVersionFetcher.kt
- Secrets (history) · Secret: aws-access-token articles/2016-7c2a676ce11cc26b5bedd5b3.awesome.kts
- Secrets (history) · Secret: aws-access-token articles/2016-7c2a676ce11cc26b5bedd5b3.awesome.kts
- Secrets (history) · Secret: generic-api-key src/main/kotlin/link/kotlin/scripts/Readability.kt
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €16,000 · Estimate
| Cost to rebuild | €5,200 to €26,000, for 86 to 273 hours of work, about 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 40. 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: 18,219 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: which parts of the code depend on which
| uses → | 1 app-frontend.app.src.components.version.KotlinVersion | 2 app-frontend.app.src.model | 3 infra.config | 4 jooq.main.enums | 5 ktor | 6 jooq.main.tables.records | 7 link.kotlin.scripts.model | 8 usecases.github | 9 usecases.kug | 10 usecases.links | 11 usecases.signup | 12 (global) | 13 jooq.main.tables.Article | 14 jooq.main.tables.ArticleAuthor | 15 jooq.main.tables.ArticleKotlinVersion | 16 jooq.main.tables.ArticleLibrary | 17 jooq.main.tables.ArticleTopic | 18 jooq.main.tables.Book | 19 jooq.main.tables.BookLibrary | 20 jooq.main.tables.BookSpeaker | 21 jooq.main.tables.Comment | 22 jooq.main.tables.Company | 23 jooq.main.tables.Course | 24 jooq.main.tables.CourseLibrary | 25 jooq.main.tables.CourseSpeaker | 26 jooq.main.tables.KotlinVersion | 27 jooq.main.tables.Kotliner | 28 jooq.main.tables.KotlinerLikeEntityState | 29 jooq.main.tables.KotlinerReadEntityState | 30 jooq.main.tables.Kug | 31 jooq.main.tables.KugEvent | 32 jooq.main.tables.KugMember | 33 jooq.main.tables.Library | 34 jooq.main.tables.LibraryVersion | 35 jooq.main.tables.Topic | 36 link.kotlin.scripts.dsl | 37 link.kotlin.scripts.utils | 38 jooq.main.tables | 39 link.kotlin.scripts | 40 jooq.main |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 app-frontend.app.src.components.version.KotlinVersion | ||||||||||||||||||||||||||||||||||||||||
| 2 app-frontend.app.src.model | ||||||||||||||||||||||||||||||||||||||||
| 3 infra.config | ||||||||||||||||||||||||||||||||||||||||
| 4 jooq.main.enums | ||||||||||||||||||||||||||||||||||||||||
| 5 ktor | ||||||||||||||||||||||||||||||||||||||||
| 6 jooq.main.tables.records | 6 | |||||||||||||||||||||||||||||||||||||||
| 7 link.kotlin.scripts.model | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 usecases.github | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 9 usecases.kug | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 10 usecases.links | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 usecases.signup | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 12 (global) | 2 | 1 | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 13 jooq.main.tables.Article | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 14 jooq.main.tables.ArticleAuthor | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 15 jooq.main.tables.ArticleKotlinVersion | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 16 jooq.main.tables.ArticleLibrary | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 17 jooq.main.tables.ArticleTopic | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 18 jooq.main.tables.Book | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 jooq.main.tables.BookLibrary | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 20 jooq.main.tables.BookSpeaker | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 jooq.main.tables.Comment | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 22 jooq.main.tables.Company | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 23 jooq.main.tables.Course | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 24 jooq.main.tables.CourseLibrary | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 jooq.main.tables.CourseSpeaker | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 26 jooq.main.tables.KotlinVersion | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 jooq.main.tables.Kotliner | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 28 jooq.main.tables.KotlinerLikeEntityState | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 jooq.main.tables.KotlinerReadEntityState | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 jooq.main.tables.Kug | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 jooq.main.tables.KugEvent | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 32 jooq.main.tables.KugMember | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 33 jooq.main.tables.Library | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 34 jooq.main.tables.LibraryVersion | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 35 jooq.main.tables.Topic | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 36 link.kotlin.scripts.dsl | 2 | |||||||||||||||||||||||||||||||||||||||
| 37 link.kotlin.scripts.utils | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 jooq.main.tables | 6 | 32 | 9 | 2 | 2 | 2 | 2 | 4 | 2 | 2 | 2 | 1 | 4 | 2 | 2 | 2 | 15 | 1 | 1 | 3 | 2 | 2 | 9 | 1 | 3 | |||||||||||||||
| 39 link.kotlin.scripts | 6 | 29 | 4 | |||||||||||||||||||||||||||||||||||||
| 40 jooq.main | 32 |
6→4 jooq.main.tables.records uses jooq.main.enums✕
- Connections
- 6 pairs of types, where a type in jooq.main.tables.records uses a type in jooq.main.enums.
- The types involved
jooq.main.tables.records.KotlinerLikeEntityStateRecord→jooq.main.enums.LikeStateEnumjooq.main.tables.records.KotlinerReadEntityStateRecord→jooq.main.enums.ReadStateEnumjooq.main.tables.records.KotlinerRecord→jooq.main.enums.KotlinerStatusEnumjooq.main.tables.records.KugEventRecord→jooq.main.enums.KugEventStatusEnumjooq.main.tables.records.KugMemberRecord→jooq.main.enums.KugMemberStatusEnumjooq.main.tables.records.KugRecord→jooq.main.enums.KugStatusEnum
- Direction
- jooq.main.tables.records uses jooq.main.enums, so a change to jooq.main.enums can break jooq.main.tables.records, while a change to jooq.main.tables.records can't break jooq.main.enums.
- Position
- Below the diagonal: jooq.main.tables.records uses a module listed above it, which is the healthy direction.
7→36 link.kotlin.scripts.model uses link.kotlin.scripts.dsl part of a loop✕
- Connections
- 2 pairs of types, where a type in link.kotlin.scripts.model uses a type in link.kotlin.scripts.dsl.
- The types involved
link.kotlin.scripts.model.Link→link.kotlin.scripts.dsl.PlatformTypelink.kotlin.scripts.model.LinkDto→link.kotlin.scripts.dsl.PlatformType
- Direction
- link.kotlin.scripts.model uses link.kotlin.scripts.dsl, so a change to link.kotlin.scripts.dsl can break link.kotlin.scripts.model, while a change to link.kotlin.scripts.model can't break link.kotlin.scripts.dsl.
- 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→3 usecases.github uses infra.config✕
- Connections
- 1 pair of types, where a type in usecases.github uses a type in infra.config.
- The types involved
usecases.github.GithubModule→infra.config.ConfigModule
- Direction
- usecases.github uses infra.config, so a change to infra.config can break usecases.github, while a change to usecases.github can't break infra.config.
- Position
- Below the diagonal: usecases.github uses a module listed above it, which is the healthy direction.
8→5 usecases.github uses ktor✕
- Connections
- 2 pairs of types, where a type in usecases.github uses a type in ktor.
- The types involved
usecases.github.GithubCallbackRoute→ktor.KtorRouteusecases.github.GithubRedirectRoute→ktor.KtorRoute
- Direction
- usecases.github uses ktor, so a change to ktor can break usecases.github, while a change to usecases.github can't break ktor.
- Position
- Below the diagonal: usecases.github uses a module listed above it, which is the healthy direction.
8→12 usecases.github uses (global) part of a loop✕
- Connections
- 1 pair of types, where a type in usecases.github uses a type in (global).
- The types involved
usecases.github.GithubModule→HttpClientModule
- Direction
- usecases.github uses (global), so a change to (global) can break usecases.github, while a change to usecases.github can't break (global).
- 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→5 usecases.kug uses ktor✕
- Connections
- 2 pairs of types, where a type in usecases.kug uses a type in ktor.
- The types involved
usecases.kug.GetKugsRoute→ktor.KtorRouteusecases.kug.UpdateKugsRoute→ktor.KtorRoute
- Direction
- usecases.kug uses ktor, so a change to ktor can break usecases.kug, while a change to usecases.kug can't break ktor.
- Position
- Below the diagonal: usecases.kug uses a module listed above it, which is the healthy direction.
9→12 usecases.kug uses (global) part of a loop✕
- Connections
- 3 pairs of types, where a type in usecases.kug uses a type in (global).
- The types involved
usecases.kug.KugModule→HttpClientModuleusecases.kug.KugModule→JooqModuleusecases.kug.KugModule→YamlModule
- Direction
- usecases.kug uses (global), so a change to (global) can break usecases.kug, while a change to usecases.kug can't break (global).
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→5 usecases.links uses ktor✕
- Connections
- 1 pair of types, where a type in usecases.links uses a type in ktor.
- The types involved
usecases.links.LinksRoute→ktor.KtorRoute
- Direction
- usecases.links uses ktor, so a change to ktor can break usecases.links, while a change to usecases.links can't break ktor.
- Position
- Below the diagonal: usecases.links uses a module listed above it, which is the healthy direction.
11→3 usecases.signup uses infra.config✕
- Connections
- 1 pair of types, where a type in usecases.signup uses a type in infra.config.
- The types involved
usecases.signup.JwtModule→infra.config.ConfigModule
- Direction
- usecases.signup uses infra.config, so a change to infra.config can break usecases.signup, while a change to usecases.signup can't break infra.config.
- Position
- Below the diagonal: usecases.signup uses a module listed above it, which is the healthy direction.
11→5 usecases.signup uses ktor✕
- Connections
- 2 pairs of types, where a type in usecases.signup uses a type in ktor.
- The types involved
usecases.signup.LoginRoute→ktor.KtorRouteusecases.signup.RegisterRoute→ktor.KtorRoute
- Direction
- usecases.signup uses ktor, so a change to ktor can break usecases.signup, while a change to usecases.signup can't break ktor.
- Position
- Below the diagonal: usecases.signup uses a module listed above it, which is the healthy direction.
11→12 usecases.signup uses (global) part of a loop✕
- Connections
- 2 pairs of types, where a type in usecases.signup uses a type in (global).
- The types involved
usecases.signup.LoginModule→JooqModuleusecases.signup.RegisterModule→JooqModule
- Direction
- usecases.signup uses (global), so a change to (global) can break usecases.signup, while a change to usecases.signup can't break (global).
- 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→3 (global) uses infra.config✕
- Connections
- 2 pairs of types, where a type in (global) uses a type in infra.config.
- The types involved
JdbcModule→infra.config.ConfigModuleServerModule→infra.config.ConfigModule
- Direction
- (global) uses infra.config, so a change to infra.config can break (global), while a change to (global) can't break infra.config.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
12→5 (global) uses ktor✕
- Connections
- 1 pair of types, where a type in (global) uses a type in ktor.
- The types involved
ServerModule→ktor.KtorRoute
- Direction
- (global) uses ktor, so a change to ktor can break (global), while a change to (global) can't break ktor.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
12→8 (global) uses usecases.github✕
- Connections
- 1 pair of types, where a type in (global) uses a type in usecases.github.
- The types involved
ServerModule→usecases.github.GithubModule
- Direction
- (global) uses usecases.github, so a change to usecases.github can break (global), while a change to (global) can't break usecases.github.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
12→9 (global) uses usecases.kug✕
- Connections
- 1 pair of types, where a type in (global) uses a type in usecases.kug.
- The types involved
ServerModule→usecases.kug.KugModule
- Direction
- (global) uses usecases.kug, so a change to usecases.kug can break (global), while a change to (global) can't break usecases.kug.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
12→10 (global) uses usecases.links✕
- Connections
- 1 pair of types, where a type in (global) uses a type in usecases.links.
- The types involved
ServerModule→usecases.links.LinksModule
- Direction
- (global) uses usecases.links, so a change to usecases.links can break (global), while a change to (global) can't break usecases.links.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
12→11 (global) uses usecases.signup✕
- Connections
- 3 pairs of types, where a type in (global) uses a type in usecases.signup.
- The types involved
ServerModule→usecases.signup.JwtModuleServerModule→usecases.signup.LoginModuleServerModule→usecases.signup.RegisterModule
- Direction
- (global) uses usecases.signup, so a change to usecases.signup can break (global), while a change to (global) can't break usecases.signup.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
13→6 jooq.main.tables.Article uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.Article uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.Article.ArticlePath→jooq.main.tables.records.ArticleRecord
- Direction
- jooq.main.tables.Article uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.Article, while a change to jooq.main.tables.Article can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.Article uses a module listed above it, which is the healthy direction.
13→38 jooq.main.tables.Article uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.Article uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.Article.ArticlePath→jooq.main.tables.Articlejooq.main.tables.Article.Companion→jooq.main.tables.Article
- Direction
- jooq.main.tables.Article uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.Article, while a change to jooq.main.tables.Article can't break jooq.main.tables.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→6 jooq.main.tables.ArticleAuthor uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.ArticleAuthor uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.ArticleAuthor.ArticleAuthorPath→jooq.main.tables.records.ArticleAuthorRecord
- Direction
- jooq.main.tables.ArticleAuthor uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.ArticleAuthor, while a change to jooq.main.tables.ArticleAuthor can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.ArticleAuthor uses a module listed above it, which is the healthy direction.
14→38 jooq.main.tables.ArticleAuthor uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.ArticleAuthor uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.ArticleAuthor.ArticleAuthorPath→jooq.main.tables.ArticleAuthorjooq.main.tables.ArticleAuthor.Companion→jooq.main.tables.ArticleAuthor
- Direction
- jooq.main.tables.ArticleAuthor uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.ArticleAuthor, while a change to jooq.main.tables.ArticleAuthor can't break jooq.main.tables.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→6 jooq.main.tables.ArticleKotlinVersion uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.ArticleKotlinVersion uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.ArticleKotlinVersion.ArticleKotlinVersionPath→jooq.main.tables.records.ArticleKotlinVersionRecord
- Direction
- jooq.main.tables.ArticleKotlinVersion uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.ArticleKotlinVersion, while a change to jooq.main.tables.ArticleKotlinVersion can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.ArticleKotlinVersion uses a module listed above it, which is the healthy direction.
15→38 jooq.main.tables.ArticleKotlinVersion uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.ArticleKotlinVersion uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.ArticleKotlinVersion.ArticleKotlinVersionPath→jooq.main.tables.ArticleKotlinVersionjooq.main.tables.ArticleKotlinVersion.Companion→jooq.main.tables.ArticleKotlinVersion
- Direction
- jooq.main.tables.ArticleKotlinVersion uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.ArticleKotlinVersion, while a change to jooq.main.tables.ArticleKotlinVersion can't break jooq.main.tables.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→6 jooq.main.tables.ArticleLibrary uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.ArticleLibrary uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.ArticleLibrary.ArticleLibraryPath→jooq.main.tables.records.ArticleLibraryRecord
- Direction
- jooq.main.tables.ArticleLibrary uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.ArticleLibrary, while a change to jooq.main.tables.ArticleLibrary can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.ArticleLibrary uses a module listed above it, which is the healthy direction.
16→38 jooq.main.tables.ArticleLibrary uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.ArticleLibrary uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.ArticleLibrary.ArticleLibraryPath→jooq.main.tables.ArticleLibraryjooq.main.tables.ArticleLibrary.Companion→jooq.main.tables.ArticleLibrary
- Direction
- jooq.main.tables.ArticleLibrary uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.ArticleLibrary, while a change to jooq.main.tables.ArticleLibrary can't break jooq.main.tables.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→6 jooq.main.tables.ArticleTopic uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.ArticleTopic uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.ArticleTopic.ArticleTopicPath→jooq.main.tables.records.ArticleTopicRecord
- Direction
- jooq.main.tables.ArticleTopic uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.ArticleTopic, while a change to jooq.main.tables.ArticleTopic can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.ArticleTopic uses a module listed above it, which is the healthy direction.
17→38 jooq.main.tables.ArticleTopic uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.ArticleTopic uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.ArticleTopic.ArticleTopicPath→jooq.main.tables.ArticleTopicjooq.main.tables.ArticleTopic.Companion→jooq.main.tables.ArticleTopic
- Direction
- jooq.main.tables.ArticleTopic uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.ArticleTopic, while a change to jooq.main.tables.ArticleTopic can't break jooq.main.tables.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→6 jooq.main.tables.Book uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.Book uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.Book.BookPath→jooq.main.tables.records.BookRecord
- Direction
- jooq.main.tables.Book uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.Book, while a change to jooq.main.tables.Book can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.Book uses a module listed above it, which is the healthy direction.
18→38 jooq.main.tables.Book uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.Book uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.Book.BookPath→jooq.main.tables.Bookjooq.main.tables.Book.Companion→jooq.main.tables.Book
- Direction
- jooq.main.tables.Book uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.Book, while a change to jooq.main.tables.Book can't break jooq.main.tables.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→6 jooq.main.tables.BookLibrary uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.BookLibrary uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.BookLibrary.BookLibraryPath→jooq.main.tables.records.BookLibraryRecord
- Direction
- jooq.main.tables.BookLibrary uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.BookLibrary, while a change to jooq.main.tables.BookLibrary can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.BookLibrary uses a module listed above it, which is the healthy direction.
19→38 jooq.main.tables.BookLibrary uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.BookLibrary uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.BookLibrary.BookLibraryPath→jooq.main.tables.BookLibraryjooq.main.tables.BookLibrary.Companion→jooq.main.tables.BookLibrary
- Direction
- jooq.main.tables.BookLibrary uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.BookLibrary, while a change to jooq.main.tables.BookLibrary can't break jooq.main.tables.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→6 jooq.main.tables.BookSpeaker uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.BookSpeaker uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.BookSpeaker.BookSpeakerPath→jooq.main.tables.records.BookSpeakerRecord
- Direction
- jooq.main.tables.BookSpeaker uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.BookSpeaker, while a change to jooq.main.tables.BookSpeaker can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.BookSpeaker uses a module listed above it, which is the healthy direction.
20→38 jooq.main.tables.BookSpeaker uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.BookSpeaker uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.BookSpeaker.BookSpeakerPath→jooq.main.tables.BookSpeakerjooq.main.tables.BookSpeaker.Companion→jooq.main.tables.BookSpeaker
- Direction
- jooq.main.tables.BookSpeaker uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.BookSpeaker, while a change to jooq.main.tables.BookSpeaker can't break jooq.main.tables.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→6 jooq.main.tables.Comment uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.Comment uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.Comment.CommentPath→jooq.main.tables.records.CommentRecord
- Direction
- jooq.main.tables.Comment uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.Comment, while a change to jooq.main.tables.Comment can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.Comment uses a module listed above it, which is the healthy direction.
21→38 jooq.main.tables.Comment uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.Comment uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.Comment.CommentPath→jooq.main.tables.Commentjooq.main.tables.Comment.Companion→jooq.main.tables.Comment
- Direction
- jooq.main.tables.Comment uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.Comment, while a change to jooq.main.tables.Comment can't break jooq.main.tables.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→6 jooq.main.tables.Company uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.Company uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.Company.CompanyPath→jooq.main.tables.records.CompanyRecord
- Direction
- jooq.main.tables.Company uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.Company, while a change to jooq.main.tables.Company can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.Company uses a module listed above it, which is the healthy direction.
22→38 jooq.main.tables.Company uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.Company uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.Company.Companion→jooq.main.tables.Companyjooq.main.tables.Company.CompanyPath→jooq.main.tables.Company
- Direction
- jooq.main.tables.Company uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.Company, while a change to jooq.main.tables.Company can't break jooq.main.tables.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→6 jooq.main.tables.Course uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.Course uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.Course.CoursePath→jooq.main.tables.records.CourseRecord
- Direction
- jooq.main.tables.Course uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.Course, while a change to jooq.main.tables.Course can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.Course uses a module listed above it, which is the healthy direction.
23→38 jooq.main.tables.Course uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.Course uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.Course.Companion→jooq.main.tables.Coursejooq.main.tables.Course.CoursePath→jooq.main.tables.Course
- Direction
- jooq.main.tables.Course uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.Course, while a change to jooq.main.tables.Course can't break jooq.main.tables.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→6 jooq.main.tables.CourseLibrary uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.CourseLibrary uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.CourseLibrary.CourseLibraryPath→jooq.main.tables.records.CourseLibraryRecord
- Direction
- jooq.main.tables.CourseLibrary uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.CourseLibrary, while a change to jooq.main.tables.CourseLibrary can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.CourseLibrary uses a module listed above it, which is the healthy direction.
24→38 jooq.main.tables.CourseLibrary uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.CourseLibrary uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.CourseLibrary.Companion→jooq.main.tables.CourseLibraryjooq.main.tables.CourseLibrary.CourseLibraryPath→jooq.main.tables.CourseLibrary
- Direction
- jooq.main.tables.CourseLibrary uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.CourseLibrary, while a change to jooq.main.tables.CourseLibrary can't break jooq.main.tables.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→6 jooq.main.tables.CourseSpeaker uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.CourseSpeaker uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.CourseSpeaker.CourseSpeakerPath→jooq.main.tables.records.CourseSpeakerRecord
- Direction
- jooq.main.tables.CourseSpeaker uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.CourseSpeaker, while a change to jooq.main.tables.CourseSpeaker can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.CourseSpeaker uses a module listed above it, which is the healthy direction.
25→38 jooq.main.tables.CourseSpeaker uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.CourseSpeaker uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.CourseSpeaker.Companion→jooq.main.tables.CourseSpeakerjooq.main.tables.CourseSpeaker.CourseSpeakerPath→jooq.main.tables.CourseSpeaker
- Direction
- jooq.main.tables.CourseSpeaker uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.CourseSpeaker, while a change to jooq.main.tables.CourseSpeaker can't break jooq.main.tables.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→6 jooq.main.tables.KotlinVersion uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.KotlinVersion uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.KotlinVersion.KotlinVersionPath→jooq.main.tables.records.KotlinVersionRecord
- Direction
- jooq.main.tables.KotlinVersion uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.KotlinVersion, while a change to jooq.main.tables.KotlinVersion can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.KotlinVersion uses a module listed above it, which is the healthy direction.
26→38 jooq.main.tables.KotlinVersion uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.KotlinVersion uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.KotlinVersion.Companion→jooq.main.tables.KotlinVersionjooq.main.tables.KotlinVersion.KotlinVersionPath→jooq.main.tables.KotlinVersion
- Direction
- jooq.main.tables.KotlinVersion uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.KotlinVersion, while a change to jooq.main.tables.KotlinVersion can't break jooq.main.tables.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→6 jooq.main.tables.Kotliner uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.Kotliner uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.Kotliner.KotlinerPath→jooq.main.tables.records.KotlinerRecord
- Direction
- jooq.main.tables.Kotliner uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.Kotliner, while a change to jooq.main.tables.Kotliner can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.Kotliner uses a module listed above it, which is the healthy direction.
27→38 jooq.main.tables.Kotliner uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.Kotliner uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.Kotliner.Companion→jooq.main.tables.Kotlinerjooq.main.tables.Kotliner.KotlinerPath→jooq.main.tables.Kotliner
- Direction
- jooq.main.tables.Kotliner uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.Kotliner, while a change to jooq.main.tables.Kotliner can't break jooq.main.tables.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→6 jooq.main.tables.KotlinerLikeEntityState uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.KotlinerLikeEntityState uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.KotlinerLikeEntityState.KotlinerLikeEntityStatePath→jooq.main.tables.records.KotlinerLikeEntityStateRecord
- Direction
- jooq.main.tables.KotlinerLikeEntityState uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.KotlinerLikeEntityState, while a change to jooq.main.tables.KotlinerLikeEntityState can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.KotlinerLikeEntityState uses a module listed above it, which is the healthy direction.
28→38 jooq.main.tables.KotlinerLikeEntityState uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.KotlinerLikeEntityState uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.KotlinerLikeEntityState.Companion→jooq.main.tables.KotlinerLikeEntityStatejooq.main.tables.KotlinerLikeEntityState.KotlinerLikeEntityStatePath→jooq.main.tables.KotlinerLikeEntityState
- Direction
- jooq.main.tables.KotlinerLikeEntityState uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.KotlinerLikeEntityState, while a change to jooq.main.tables.KotlinerLikeEntityState can't break jooq.main.tables.
- 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.
29→6 jooq.main.tables.KotlinerReadEntityState uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.KotlinerReadEntityState uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.KotlinerReadEntityState.KotlinerReadEntityStatePath→jooq.main.tables.records.KotlinerReadEntityStateRecord
- Direction
- jooq.main.tables.KotlinerReadEntityState uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.KotlinerReadEntityState, while a change to jooq.main.tables.KotlinerReadEntityState can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.KotlinerReadEntityState uses a module listed above it, which is the healthy direction.
29→38 jooq.main.tables.KotlinerReadEntityState uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.KotlinerReadEntityState uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.KotlinerReadEntityState.Companion→jooq.main.tables.KotlinerReadEntityStatejooq.main.tables.KotlinerReadEntityState.KotlinerReadEntityStatePath→jooq.main.tables.KotlinerReadEntityState
- Direction
- jooq.main.tables.KotlinerReadEntityState uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.KotlinerReadEntityState, while a change to jooq.main.tables.KotlinerReadEntityState can't break jooq.main.tables.
- 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.
30→6 jooq.main.tables.Kug uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.Kug uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.Kug.KugPath→jooq.main.tables.records.KugRecord
- Direction
- jooq.main.tables.Kug uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.Kug, while a change to jooq.main.tables.Kug can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.Kug uses a module listed above it, which is the healthy direction.
30→38 jooq.main.tables.Kug uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.Kug uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.Kug.Companion→jooq.main.tables.Kugjooq.main.tables.Kug.KugPath→jooq.main.tables.Kug
- Direction
- jooq.main.tables.Kug uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.Kug, while a change to jooq.main.tables.Kug can't break jooq.main.tables.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→6 jooq.main.tables.KugEvent uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.KugEvent uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.KugEvent.KugEventPath→jooq.main.tables.records.KugEventRecord
- Direction
- jooq.main.tables.KugEvent uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.KugEvent, while a change to jooq.main.tables.KugEvent can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.KugEvent uses a module listed above it, which is the healthy direction.
31→38 jooq.main.tables.KugEvent uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.KugEvent uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.KugEvent.Companion→jooq.main.tables.KugEventjooq.main.tables.KugEvent.KugEventPath→jooq.main.tables.KugEvent
- Direction
- jooq.main.tables.KugEvent uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.KugEvent, while a change to jooq.main.tables.KugEvent can't break jooq.main.tables.
- 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.
32→6 jooq.main.tables.KugMember uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.KugMember uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.KugMember.KugMemberPath→jooq.main.tables.records.KugMemberRecord
- Direction
- jooq.main.tables.KugMember uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.KugMember, while a change to jooq.main.tables.KugMember can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.KugMember uses a module listed above it, which is the healthy direction.
32→38 jooq.main.tables.KugMember uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.KugMember uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.KugMember.Companion→jooq.main.tables.KugMemberjooq.main.tables.KugMember.KugMemberPath→jooq.main.tables.KugMember
- Direction
- jooq.main.tables.KugMember uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.KugMember, while a change to jooq.main.tables.KugMember can't break jooq.main.tables.
- 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.
33→6 jooq.main.tables.Library uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.Library uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.Library.LibraryPath→jooq.main.tables.records.LibraryRecord
- Direction
- jooq.main.tables.Library uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.Library, while a change to jooq.main.tables.Library can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.Library uses a module listed above it, which is the healthy direction.
33→38 jooq.main.tables.Library uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.Library uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.Library.Companion→jooq.main.tables.Libraryjooq.main.tables.Library.LibraryPath→jooq.main.tables.Library
- Direction
- jooq.main.tables.Library uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.Library, while a change to jooq.main.tables.Library can't break jooq.main.tables.
- 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.
34→6 jooq.main.tables.LibraryVersion uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.LibraryVersion uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.LibraryVersion.LibraryVersionPath→jooq.main.tables.records.LibraryVersionRecord
- Direction
- jooq.main.tables.LibraryVersion uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.LibraryVersion, while a change to jooq.main.tables.LibraryVersion can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.LibraryVersion uses a module listed above it, which is the healthy direction.
34→38 jooq.main.tables.LibraryVersion uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.LibraryVersion uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.LibraryVersion.Companion→jooq.main.tables.LibraryVersionjooq.main.tables.LibraryVersion.LibraryVersionPath→jooq.main.tables.LibraryVersion
- Direction
- jooq.main.tables.LibraryVersion uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.LibraryVersion, while a change to jooq.main.tables.LibraryVersion can't break jooq.main.tables.
- 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.
35→6 jooq.main.tables.Topic uses jooq.main.tables.records✕
- Connections
- 1 pair of types, where a type in jooq.main.tables.Topic uses a type in jooq.main.tables.records.
- The types involved
jooq.main.tables.Topic.TopicPath→jooq.main.tables.records.TopicRecord
- Direction
- jooq.main.tables.Topic uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables.Topic, while a change to jooq.main.tables.Topic can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables.Topic uses a module listed above it, which is the healthy direction.
35→38 jooq.main.tables.Topic uses jooq.main.tables part of a loop✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables.Topic uses a type in jooq.main.tables.
- The types involved
jooq.main.tables.Topic.Companion→jooq.main.tables.Topicjooq.main.tables.Topic.TopicPath→jooq.main.tables.Topic
- Direction
- jooq.main.tables.Topic uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main.tables.Topic, while a change to jooq.main.tables.Topic can't break jooq.main.tables.
- 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.
36→7 link.kotlin.scripts.dsl uses link.kotlin.scripts.model✕
- Connections
- 2 pairs of types, where a type in link.kotlin.scripts.dsl uses a type in link.kotlin.scripts.model.
- The types involved
link.kotlin.scripts.dsl.LinkBuilder→link.kotlin.scripts.model.Linklink.kotlin.scripts.dsl.Subcategory→link.kotlin.scripts.model.Link
- Direction
- link.kotlin.scripts.dsl uses link.kotlin.scripts.model, so a change to link.kotlin.scripts.model can break link.kotlin.scripts.dsl, while a change to link.kotlin.scripts.dsl can't break link.kotlin.scripts.model.
- Position
- Below the diagonal: link.kotlin.scripts.dsl uses a module listed above it, which is the healthy direction.
37→7 link.kotlin.scripts.utils uses link.kotlin.scripts.model✕
- Connections
- 1 pair of types, where a type in link.kotlin.scripts.utils uses a type in link.kotlin.scripts.model.
- The types involved
link.kotlin.scripts.utils.DisableCache→link.kotlin.scripts.model.ApplicationConfiguration
- Direction
- link.kotlin.scripts.utils uses link.kotlin.scripts.model, so a change to link.kotlin.scripts.model can break link.kotlin.scripts.utils, while a change to link.kotlin.scripts.utils can't break link.kotlin.scripts.model.
- Position
- Below the diagonal: link.kotlin.scripts.utils uses a module listed above it, which is the healthy direction.
38→4 jooq.main.tables uses jooq.main.enums✕
- Connections
- 6 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.enums.
- The types involved
jooq.main.tables.Kotliner→jooq.main.enums.KotlinerStatusEnumjooq.main.tables.KotlinerLikeEntityState→jooq.main.enums.LikeStateEnumjooq.main.tables.KotlinerReadEntityState→jooq.main.enums.ReadStateEnumjooq.main.tables.Kug→jooq.main.enums.KugStatusEnumjooq.main.tables.KugEvent→jooq.main.enums.KugEventStatusEnumjooq.main.tables.KugMember→jooq.main.enums.KugMemberStatusEnum
- Direction
- jooq.main.tables uses jooq.main.enums, so a change to jooq.main.enums can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.enums.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→6 jooq.main.tables uses jooq.main.tables.records✕
- Connections
- 32 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.records. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
jooq.main.tables.Article→jooq.main.tables.records.ArticleRecordjooq.main.tables.ArticleAuthor→jooq.main.tables.records.ArticleAuthorRecordjooq.main.tables.ArticleKotlinVersion→jooq.main.tables.records.ArticleKotlinVersionRecordjooq.main.tables.ArticleLibrary→jooq.main.tables.records.ArticleLibraryRecordjooq.main.tables.ArticleTopic→jooq.main.tables.records.ArticleTopicRecordjooq.main.tables.Book→jooq.main.tables.records.BookRecordjooq.main.tables.BookLibrary→jooq.main.tables.records.BookLibraryRecordjooq.main.tables.BookSpeaker→jooq.main.tables.records.BookSpeakerRecordjooq.main.tables.Bookmark→jooq.main.tables.records.BookmarkRecordjooq.main.tables.Comment→jooq.main.tables.records.CommentRecordjooq.main.tables.Company→jooq.main.tables.records.CompanyRecordjooq.main.tables.Course→jooq.main.tables.records.CourseRecordjooq.main.tables.CourseLibrary→jooq.main.tables.records.CourseLibraryRecordjooq.main.tables.CourseSpeaker→jooq.main.tables.records.CourseSpeakerRecordjooq.main.tables.DmLikes→jooq.main.tables.records.DmLikesRecordjooq.main.tables.EntityTopic→jooq.main.tables.records.EntityTopicRecordjooq.main.tables.FlywaySchemaHistory→jooq.main.tables.records.FlywaySchemaHistoryRecordjooq.main.tables.KotlinVersion→jooq.main.tables.records.KotlinVersionRecordjooq.main.tables.Kotliner→jooq.main.tables.records.KotlinerRecordjooq.main.tables.KotlinerLikeEntityState→jooq.main.tables.records.KotlinerLikeEntityStateRecordjooq.main.tables.KotlinerReadEntityState→jooq.main.tables.records.KotlinerReadEntityStateRecordjooq.main.tables.Kug→jooq.main.tables.records.KugRecordjooq.main.tables.KugEvent→jooq.main.tables.records.KugEventRecordjooq.main.tables.KugMember→jooq.main.tables.records.KugMemberRecordjooq.main.tables.Library→jooq.main.tables.records.LibraryRecord
- Direction
- jooq.main.tables uses jooq.main.tables.records, so a change to jooq.main.tables.records can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.records.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→13 jooq.main.tables uses jooq.main.tables.Article✕
- Connections
- 9 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.Article.
- The types involved
jooq.main.tables.Article→jooq.main.tables.Article.ArticlePathjooq.main.tables.ArticleAuthor→jooq.main.tables.Article.ArticlePathjooq.main.tables.ArticleKotlinVersion→jooq.main.tables.Article.ArticlePathjooq.main.tables.ArticleLibrary→jooq.main.tables.Article.ArticlePathjooq.main.tables.ArticleTopic→jooq.main.tables.Article.ArticlePathjooq.main.tables.KotlinVersion→jooq.main.tables.Article.ArticlePathjooq.main.tables.Kotliner→jooq.main.tables.Article.ArticlePathjooq.main.tables.Library→jooq.main.tables.Article.ArticlePathjooq.main.tables.Topic→jooq.main.tables.Article.ArticlePath
- Direction
- jooq.main.tables uses jooq.main.tables.Article, so a change to jooq.main.tables.Article can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.Article.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→14 jooq.main.tables uses jooq.main.tables.ArticleAuthor✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.ArticleAuthor.
- The types involved
jooq.main.tables.Article→jooq.main.tables.ArticleAuthor.ArticleAuthorPathjooq.main.tables.Kotliner→jooq.main.tables.ArticleAuthor.ArticleAuthorPath
- Direction
- jooq.main.tables uses jooq.main.tables.ArticleAuthor, so a change to jooq.main.tables.ArticleAuthor can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.ArticleAuthor.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→15 jooq.main.tables uses jooq.main.tables.ArticleKotlinVersion✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.ArticleKotlinVersion.
- The types involved
jooq.main.tables.Article→jooq.main.tables.ArticleKotlinVersion.ArticleKotlinVersionPathjooq.main.tables.KotlinVersion→jooq.main.tables.ArticleKotlinVersion.ArticleKotlinVersionPath
- Direction
- jooq.main.tables uses jooq.main.tables.ArticleKotlinVersion, so a change to jooq.main.tables.ArticleKotlinVersion can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.ArticleKotlinVersion.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→16 jooq.main.tables uses jooq.main.tables.ArticleLibrary✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.ArticleLibrary.
- The types involved
jooq.main.tables.Article→jooq.main.tables.ArticleLibrary.ArticleLibraryPathjooq.main.tables.Library→jooq.main.tables.ArticleLibrary.ArticleLibraryPath
- Direction
- jooq.main.tables uses jooq.main.tables.ArticleLibrary, so a change to jooq.main.tables.ArticleLibrary can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.ArticleLibrary.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→17 jooq.main.tables uses jooq.main.tables.ArticleTopic✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.ArticleTopic.
- The types involved
jooq.main.tables.Article→jooq.main.tables.ArticleTopic.ArticleTopicPathjooq.main.tables.Topic→jooq.main.tables.ArticleTopic.ArticleTopicPath
- Direction
- jooq.main.tables uses jooq.main.tables.ArticleTopic, so a change to jooq.main.tables.ArticleTopic can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.ArticleTopic.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→18 jooq.main.tables uses jooq.main.tables.Book✕
- Connections
- 4 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.Book.
- The types involved
jooq.main.tables.BookLibrary→jooq.main.tables.Book.BookPathjooq.main.tables.BookSpeaker→jooq.main.tables.Book.BookPathjooq.main.tables.Kotliner→jooq.main.tables.Book.BookPathjooq.main.tables.Library→jooq.main.tables.Book.BookPath
- Direction
- jooq.main.tables uses jooq.main.tables.Book, so a change to jooq.main.tables.Book can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.Book.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→19 jooq.main.tables uses jooq.main.tables.BookLibrary✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.BookLibrary.
- The types involved
jooq.main.tables.Book→jooq.main.tables.BookLibrary.BookLibraryPathjooq.main.tables.Library→jooq.main.tables.BookLibrary.BookLibraryPath
- Direction
- jooq.main.tables uses jooq.main.tables.BookLibrary, so a change to jooq.main.tables.BookLibrary can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.BookLibrary.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→20 jooq.main.tables uses jooq.main.tables.BookSpeaker✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.BookSpeaker.
- The types involved
jooq.main.tables.Book→jooq.main.tables.BookSpeaker.BookSpeakerPathjooq.main.tables.Kotliner→jooq.main.tables.BookSpeaker.BookSpeakerPath
- Direction
- jooq.main.tables uses jooq.main.tables.BookSpeaker, so a change to jooq.main.tables.BookSpeaker can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.BookSpeaker.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→21 jooq.main.tables uses jooq.main.tables.Comment✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.Comment.
- The types involved
jooq.main.tables.Comment→jooq.main.tables.Comment.CommentPathjooq.main.tables.Kotliner→jooq.main.tables.Comment.CommentPath
- Direction
- jooq.main.tables uses jooq.main.tables.Comment, so a change to jooq.main.tables.Comment can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.Comment.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→22 jooq.main.tables uses jooq.main.tables.Company✕
- Connections
- 1 pair of types, where a type in jooq.main.tables uses a type in jooq.main.tables.Company.
- The types involved
jooq.main.tables.Vacancy→jooq.main.tables.Company.CompanyPath
- Direction
- jooq.main.tables uses jooq.main.tables.Company, so a change to jooq.main.tables.Company can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.Company.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→23 jooq.main.tables uses jooq.main.tables.Course✕
- Connections
- 4 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.Course.
- The types involved
jooq.main.tables.CourseLibrary→jooq.main.tables.Course.CoursePathjooq.main.tables.CourseSpeaker→jooq.main.tables.Course.CoursePathjooq.main.tables.Kotliner→jooq.main.tables.Course.CoursePathjooq.main.tables.Library→jooq.main.tables.Course.CoursePath
- Direction
- jooq.main.tables uses jooq.main.tables.Course, so a change to jooq.main.tables.Course can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.Course.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→24 jooq.main.tables uses jooq.main.tables.CourseLibrary✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.CourseLibrary.
- The types involved
jooq.main.tables.Course→jooq.main.tables.CourseLibrary.CourseLibraryPathjooq.main.tables.Library→jooq.main.tables.CourseLibrary.CourseLibraryPath
- Direction
- jooq.main.tables uses jooq.main.tables.CourseLibrary, so a change to jooq.main.tables.CourseLibrary can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.CourseLibrary.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→25 jooq.main.tables uses jooq.main.tables.CourseSpeaker✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.CourseSpeaker.
- The types involved
jooq.main.tables.Course→jooq.main.tables.CourseSpeaker.CourseSpeakerPathjooq.main.tables.Kotliner→jooq.main.tables.CourseSpeaker.CourseSpeakerPath
- Direction
- jooq.main.tables uses jooq.main.tables.CourseSpeaker, so a change to jooq.main.tables.CourseSpeaker can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.CourseSpeaker.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→26 jooq.main.tables uses jooq.main.tables.KotlinVersion✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.KotlinVersion.
- The types involved
jooq.main.tables.Article→jooq.main.tables.KotlinVersion.KotlinVersionPathjooq.main.tables.ArticleKotlinVersion→jooq.main.tables.KotlinVersion.KotlinVersionPath
- Direction
- jooq.main.tables uses jooq.main.tables.KotlinVersion, so a change to jooq.main.tables.KotlinVersion can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.KotlinVersion.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→27 jooq.main.tables uses jooq.main.tables.Kotliner✕
- Connections
- 15 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.Kotliner.
- The types involved
jooq.main.tables.Article→jooq.main.tables.Kotliner.KotlinerPathjooq.main.tables.ArticleAuthor→jooq.main.tables.Kotliner.KotlinerPathjooq.main.tables.Book→jooq.main.tables.Kotliner.KotlinerPathjooq.main.tables.BookSpeaker→jooq.main.tables.Kotliner.KotlinerPathjooq.main.tables.Comment→jooq.main.tables.Kotliner.KotlinerPathjooq.main.tables.Course→jooq.main.tables.Kotliner.KotlinerPathjooq.main.tables.CourseSpeaker→jooq.main.tables.Kotliner.KotlinerPathjooq.main.tables.KotlinerLikeEntityState→jooq.main.tables.Kotliner.KotlinerPathjooq.main.tables.KotlinerReadEntityState→jooq.main.tables.Kotliner.KotlinerPathjooq.main.tables.Kug→jooq.main.tables.Kotliner.KotlinerPathjooq.main.tables.KugEvent→jooq.main.tables.Kotliner.KotlinerPathjooq.main.tables.KugMember→jooq.main.tables.Kotliner.KotlinerPathjooq.main.tables.Vacancy→jooq.main.tables.Kotliner.KotlinerPathjooq.main.tables.Video→jooq.main.tables.Kotliner.KotlinerPathjooq.main.tables.VideoSpeaker→jooq.main.tables.Kotliner.KotlinerPath
- Direction
- jooq.main.tables uses jooq.main.tables.Kotliner, so a change to jooq.main.tables.Kotliner can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.Kotliner.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→28 jooq.main.tables uses jooq.main.tables.KotlinerLikeEntityState✕
- Connections
- 1 pair of types, where a type in jooq.main.tables uses a type in jooq.main.tables.KotlinerLikeEntityState.
- The types involved
jooq.main.tables.Kotliner→jooq.main.tables.KotlinerLikeEntityState.KotlinerLikeEntityStatePath
- Direction
- jooq.main.tables uses jooq.main.tables.KotlinerLikeEntityState, so a change to jooq.main.tables.KotlinerLikeEntityState can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.KotlinerLikeEntityState.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→29 jooq.main.tables uses jooq.main.tables.KotlinerReadEntityState✕
- Connections
- 1 pair of types, where a type in jooq.main.tables uses a type in jooq.main.tables.KotlinerReadEntityState.
- The types involved
jooq.main.tables.Kotliner→jooq.main.tables.KotlinerReadEntityState.KotlinerReadEntityStatePath
- Direction
- jooq.main.tables uses jooq.main.tables.KotlinerReadEntityState, so a change to jooq.main.tables.KotlinerReadEntityState can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.KotlinerReadEntityState.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→30 jooq.main.tables uses jooq.main.tables.Kug✕
- Connections
- 3 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.Kug.
- The types involved
jooq.main.tables.Kotliner→jooq.main.tables.Kug.KugPathjooq.main.tables.KugEvent→jooq.main.tables.Kug.KugPathjooq.main.tables.KugMember→jooq.main.tables.Kug.KugPath
- Direction
- jooq.main.tables uses jooq.main.tables.Kug, so a change to jooq.main.tables.Kug can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.Kug.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→31 jooq.main.tables uses jooq.main.tables.KugEvent✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.KugEvent.
- The types involved
jooq.main.tables.Kotliner→jooq.main.tables.KugEvent.KugEventPathjooq.main.tables.Kug→jooq.main.tables.KugEvent.KugEventPath
- Direction
- jooq.main.tables uses jooq.main.tables.KugEvent, so a change to jooq.main.tables.KugEvent can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.KugEvent.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→32 jooq.main.tables uses jooq.main.tables.KugMember✕
- Connections
- 2 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.KugMember.
- The types involved
jooq.main.tables.Kotliner→jooq.main.tables.KugMember.KugMemberPathjooq.main.tables.Kug→jooq.main.tables.KugMember.KugMemberPath
- Direction
- jooq.main.tables uses jooq.main.tables.KugMember, so a change to jooq.main.tables.KugMember can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.KugMember.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→33 jooq.main.tables uses jooq.main.tables.Library✕
- Connections
- 9 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.Library.
- The types involved
jooq.main.tables.Article→jooq.main.tables.Library.LibraryPathjooq.main.tables.ArticleLibrary→jooq.main.tables.Library.LibraryPathjooq.main.tables.Book→jooq.main.tables.Library.LibraryPathjooq.main.tables.BookLibrary→jooq.main.tables.Library.LibraryPathjooq.main.tables.Course→jooq.main.tables.Library.LibraryPathjooq.main.tables.CourseLibrary→jooq.main.tables.Library.LibraryPathjooq.main.tables.LibraryVersion→jooq.main.tables.Library.LibraryPathjooq.main.tables.Video→jooq.main.tables.Library.LibraryPathjooq.main.tables.VideoLibrary→jooq.main.tables.Library.LibraryPath
- Direction
- jooq.main.tables uses jooq.main.tables.Library, so a change to jooq.main.tables.Library can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.Library.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→34 jooq.main.tables uses jooq.main.tables.LibraryVersion✕
- Connections
- 1 pair of types, where a type in jooq.main.tables uses a type in jooq.main.tables.LibraryVersion.
- The types involved
jooq.main.tables.Library→jooq.main.tables.LibraryVersion.LibraryVersionPath
- Direction
- jooq.main.tables uses jooq.main.tables.LibraryVersion, so a change to jooq.main.tables.LibraryVersion can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.LibraryVersion.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
38→35 jooq.main.tables uses jooq.main.tables.Topic✕
- Connections
- 3 pairs of types, where a type in jooq.main.tables uses a type in jooq.main.tables.Topic.
- The types involved
jooq.main.tables.Article→jooq.main.tables.Topic.TopicPathjooq.main.tables.ArticleTopic→jooq.main.tables.Topic.TopicPathjooq.main.tables.Topic→jooq.main.tables.Topic.TopicPath
- Direction
- jooq.main.tables uses jooq.main.tables.Topic, so a change to jooq.main.tables.Topic can break jooq.main.tables, while a change to jooq.main.tables can't break jooq.main.tables.Topic.
- Position
- Below the diagonal: jooq.main.tables uses a module listed above it, which is the healthy direction.
39→7 link.kotlin.scripts uses link.kotlin.scripts.model✕
- Connections
- 6 pairs of types, where a type in link.kotlin.scripts uses a type in link.kotlin.scripts.model.
- The types involved
link.kotlin.scripts.CombinedLinksProcessors→link.kotlin.scripts.model.Linklink.kotlin.scripts.DefaultLinksProcessor→link.kotlin.scripts.model.ApplicationConfigurationlink.kotlin.scripts.DefaultLinksProcessor→link.kotlin.scripts.model.Linklink.kotlin.scripts.DefaultSitemapGenerator→link.kotlin.scripts.model.ApplicationConfigurationlink.kotlin.scripts.DescriptionMarkdownLinkProcessor→link.kotlin.scripts.model.Linklink.kotlin.scripts.LinksProcessor→link.kotlin.scripts.model.Link
- Direction
- link.kotlin.scripts uses link.kotlin.scripts.model, so a change to link.kotlin.scripts.model can break link.kotlin.scripts, while a change to link.kotlin.scripts can't break link.kotlin.scripts.model.
- Position
- Below the diagonal: link.kotlin.scripts uses a module listed above it, which is the healthy direction.
39→36 link.kotlin.scripts uses link.kotlin.scripts.dsl✕
- Connections
- 29 pairs of types, where a type in link.kotlin.scripts uses a type in link.kotlin.scripts.dsl. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
link.kotlin.scripts.ArticlesProcessor→link.kotlin.scripts.dsl.Articlelink.kotlin.scripts.ArticlesSource→link.kotlin.scripts.dsl.Articlelink.kotlin.scripts.AwesomeKotlinGenerator→link.kotlin.scripts.dsl.Articlelink.kotlin.scripts.AwesomeKotlinGenerator→link.kotlin.scripts.dsl.Categorylink.kotlin.scripts.CachedGithubTrending→link.kotlin.scripts.dsl.Categorylink.kotlin.scripts.CategoryProcessor→link.kotlin.scripts.dsl.Categorylink.kotlin.scripts.DefaultArticlesProcessor→link.kotlin.scripts.dsl.Articlelink.kotlin.scripts.DefaultAwesomeKotlinGenerator→link.kotlin.scripts.dsl.Articlelink.kotlin.scripts.DefaultAwesomeKotlinGenerator→link.kotlin.scripts.dsl.Categorylink.kotlin.scripts.DefaultPagesGenerator→link.kotlin.scripts.dsl.Articlelink.kotlin.scripts.DefaultRssGenerator→link.kotlin.scripts.dsl.Articlelink.kotlin.scripts.DefaultSiteGenerator→link.kotlin.scripts.dsl.Articlelink.kotlin.scripts.DefaultSiteGenerator→link.kotlin.scripts.dsl.Categorylink.kotlin.scripts.DefaultSitemapGenerator→link.kotlin.scripts.dsl.Articlelink.kotlin.scripts.FileSystemArticlesSource→link.kotlin.scripts.dsl.Articlelink.kotlin.scripts.FileSystemLinksSource→link.kotlin.scripts.dsl.Categorylink.kotlin.scripts.GithubTrending→link.kotlin.scripts.dsl.Categorylink.kotlin.scripts.JSoupGithubTrending→link.kotlin.scripts.dsl.Categorylink.kotlin.scripts.JSoupGithubTrending→link.kotlin.scripts.dsl.Subcategorylink.kotlin.scripts.LinksSource→link.kotlin.scripts.dsl.Categorylink.kotlin.scripts.PagesGenerator→link.kotlin.scripts.dsl.Articlelink.kotlin.scripts.PagesGeneratorKt→link.kotlin.scripts.dsl.Articlelink.kotlin.scripts.PagesGeneratorKt→link.kotlin.scripts.dsl.ArticleFeaturelink.kotlin.scripts.ParallelCategoryProcessor→link.kotlin.scripts.dsl.Categorylink.kotlin.scripts.RssGenerator→link.kotlin.scripts.dsl.Article
- Direction
- link.kotlin.scripts uses link.kotlin.scripts.dsl, so a change to link.kotlin.scripts.dsl can break link.kotlin.scripts, while a change to link.kotlin.scripts can't break link.kotlin.scripts.dsl.
- Position
- Below the diagonal: link.kotlin.scripts uses a module listed above it, which is the healthy direction.
39→37 link.kotlin.scripts uses link.kotlin.scripts.utils✕
- Connections
- 4 pairs of types, where a type in link.kotlin.scripts uses a type in link.kotlin.scripts.utils.
- The types involved
link.kotlin.scripts.CachedGithubTrending→link.kotlin.scripts.utils.Cachelink.kotlin.scripts.DefaultLinksChecker→link.kotlin.scripts.utils.HttpClientlink.kotlin.scripts.DefaultLinksProcessor→link.kotlin.scripts.utils.HttpClientlink.kotlin.scripts.MavenCentralKotlinVersionFetcher→link.kotlin.scripts.utils.HttpClient
- Direction
- link.kotlin.scripts uses link.kotlin.scripts.utils, so a change to link.kotlin.scripts.utils can break link.kotlin.scripts, while a change to link.kotlin.scripts can't break link.kotlin.scripts.utils.
- Position
- Below the diagonal: link.kotlin.scripts uses a module listed above it, which is the healthy direction.
40→38 jooq.main uses jooq.main.tables✕
- Connections
- 32 pairs of types, where a type in jooq.main uses a type in jooq.main.tables. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
jooq.main.Public→jooq.main.tables.Articlejooq.main.Public→jooq.main.tables.ArticleAuthorjooq.main.Public→jooq.main.tables.ArticleKotlinVersionjooq.main.Public→jooq.main.tables.ArticleLibraryjooq.main.Public→jooq.main.tables.ArticleTopicjooq.main.Public→jooq.main.tables.Bookjooq.main.Public→jooq.main.tables.BookLibraryjooq.main.Public→jooq.main.tables.BookSpeakerjooq.main.Public→jooq.main.tables.Bookmarkjooq.main.Public→jooq.main.tables.Commentjooq.main.Public→jooq.main.tables.Companyjooq.main.Public→jooq.main.tables.Coursejooq.main.Public→jooq.main.tables.CourseLibraryjooq.main.Public→jooq.main.tables.CourseSpeakerjooq.main.Public→jooq.main.tables.DmLikesjooq.main.Public→jooq.main.tables.EntityTopicjooq.main.Public→jooq.main.tables.FlywaySchemaHistoryjooq.main.Public→jooq.main.tables.KotlinVersionjooq.main.Public→jooq.main.tables.Kotlinerjooq.main.Public→jooq.main.tables.KotlinerLikeEntityStatejooq.main.Public→jooq.main.tables.KotlinerReadEntityStatejooq.main.Public→jooq.main.tables.Kugjooq.main.Public→jooq.main.tables.KugEventjooq.main.Public→jooq.main.tables.KugMemberjooq.main.Public→jooq.main.tables.Library
- Direction
- jooq.main uses jooq.main.tables, so a change to jooq.main.tables can break jooq.main, while a change to jooq.main can't break jooq.main.tables.
- Position
- Below the diagonal: jooq.main 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 | 20 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 11 | High / Critical |
| A02:2025 — Security Misconfiguration | 4 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts; Resolve the 1 finding(s) in DR & Backup; Add a test runner (vitest / jest / playwright) and eslint and `tsc --noEmit` as package.json scripts and run them in CI.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. | +3.4 pts | Low | ADR Quality |
| Resolve the 1 finding(s) in DR & Backup. | +3.1 pts | Medium | DR & Backup |
| Add a test runner (vitest / jest / playwright) and eslint and `tsc --noEmit` as package.json scripts and run them in CI. | +3.1 pts | Medium | Tooling |
| 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. | +2.3 pts | Medium | Architecture documentation |
| Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry). | +2.2 pts | Medium | Outbound HTTP resilience |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +2.2 pts | Medium | Security & performance tooling |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.1 pts | Low | Bus Factor |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +1.7 pts | Medium | Keyboard semantics |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| app-backend/src/test/kotlin/usecases/kug/KugDownloadServiceTest.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| app-backend/src/main/kotlin/ApplicationModule.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (19 corresponding lines) |
| app-backend/src/main/kotlin/usecases/signup/Register.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (11 corresponding lines) |
| app-backend/src/main/kotlin/usecases/links/Links.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (18 lines × 2) |
| app-backend/src/main/kotlin/usecases/version/KotlinVersionFetcher.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
| app-backend/src/main/kotlin/jooq/main/tables/Kotliner.kt | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: Kotliner (LCOM4 14) |
| REDACTED | 9.3 | Near-clean | IaC & Container Security: Low IaC: REDACTED |
| build.gradle.kts | 9.5 | Near-clean | ADR Quality: No ADRs found |
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 60 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 — 60 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, 67 of 79 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D1 Cyclomatic Complexity — 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. Most of this repository's production source (.kt) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — 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. Most of this repository's production source (.kt) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- 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 (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 4 Maven/Gradle manifest(s) were read, stating a version for 52 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D15 Churn × Complexity Hotspots — 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. A hotspot is churn × complexity. Churn was measured (942 line(s) across the 90-day window), but no complexity could be computed for .kt, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
- D19 Documentation Quality — 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 ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (app-frontend/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — 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.
- 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. `app-backend/build.gradle.kts` 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.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — time="2026-11-14T12:59:13Z" level=warning msg="The \"AWESOME__GITHUB__CLIENT_SECRET\" variable is not set. Defaulting to a blank string." failed to solve: failed to compute cache key: failed to calculate checksum of ref 43f4e61a-50fc-43c1-9636-59687d7c502f::h5duyaxrqv5nvhm1ll8c3cjlo: "/app-frontend/dist": not found; runtime evidence skipped.
- 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.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- S1 Web-Security Posture — 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 web-security 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 web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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
- 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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- 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").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- 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.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
Dimensions
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
2 duplicated block group(s) detected. 0.5 % of the production lines (92 of 18,219) are in a reported copy. A further 2 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 1 Edited copy of a member (19 corresponding lines) finding(s) in Code Duplication — start with LinksProcessor.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with Register.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (18 lines × 2) finding(s) in Code Duplication — start with Links.kt. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
4 production modules (Gradle+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
1 of 15 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with Kotliner.kt. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 52 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 4 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D16 · Bus Factor
5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt. Counted over 18 of the 248 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
2 deducted task-comment markers across 18219 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with KugDownloadServiceTest.kt, ApplicationModule.kt. — One of this dimension's main actionable groups (2 warning-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 4 build units (Gradle, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
20 finding(s): 0 critical, 18 high, 2 medium, 0 low. 15 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 2 file(s) — `app-backend/build.gradle.kts` (line 10), `gradlew` (line 74, line 178) — 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 15 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 (15 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
6 finding(s): 0 critical, 4 high, 2 medium, 0 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
4 finding(s): 0 critical, 1 high, 1 medium, 2 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
1 of 18 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is app-frontend/app/src/components/head/logos.ts. Counted over 18 of the 248 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 52 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
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 htmlFor>, a wrapping <label>, or aria-label. — app-frontend/app/src/components/search/search.tsx:39
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
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — app-frontend/app/index.html:2
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — app-frontend/pages/index.html:2
- user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — app-frontend/pages/index.html:6
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
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×2) — app-frontend/app/src/components/head/head.tsx:53, app-frontend/app/src/components/version/KotlinVersion.tsx:11
- 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) — app-frontend/pages/index.html:37, app-frontend/pages/index.html:48
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety
- `input: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. — app-frontend/pages/styles.css:53
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.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault — not a key compiled into the app) and encrypt the store that holds the personal data (SQLCipher, a Realm encryptionKey, field-level AEAD) — partial coverage still leaves gaps.
- Enforce HTTPS on the server that receives this data: terminate TLS in it (Ktor's sslConnector, Spring's server.ssl and requiresSecure, Netty's SslContextBuilder.forServer) and send Strict-Transport-Security (Ktor's HttpsRedirect), or run it behind a TLS-terminating proxy, so data in transit is always encrypted.
M1 · Documentation (README)
- The root README is 75 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it.
P10 · Library API & versioning
P2 · Observability
- Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `app-backend-dataops`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
P7 · Outbound HTTP resilience
- `HttpClient(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — app-backend/src/main/kotlin/HttpClientModule.kt:14
- `HttpClient {` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — src/main/kotlin/link/kotlin/scripts/utils/HttpClient.kt:11, src/main/kotlin/link/kotlin/scripts/utils/HttpClient.kt:21
What to do
- Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
P8 · Schema migrations
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
R2 · Cyclomatic Complexity
R3 · Large Files
R6 · Tooling
- test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add a test runner (vitest / jest / playwright) and eslint and `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
R8 · Dependency Hygiene
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
- `Files.list(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.toList` 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 `Files.list(…).use { r -> … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. — src/main/kotlin/link/kotlin/scripts/ArticlesSource.kt:21
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
X2 · Cancellation propagation
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X3 · Exception handling
X4 · Structured logging
- `debug` at line 33 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:33
- `error` at line 39 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:39
- `debug` at line 81 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:81
- `error` at line 96 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:96
- `error` at line 101 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:101
- `error` at line 129 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:129
- `error` at line 134 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:134
- `debug` at line 143 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:143
- `error` at line 148 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:148
- `info` at line 39 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. (×2) — REDACTED:39, src/main/kotlin/link/kotlin/scripts/utils/Utils.kt:39
- `info` at line 56 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/link/kotlin/scripts/utils/Utils.kt:56
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
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 |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 77% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 94% | Exemplary | Solid. |
| Maturity | 43% | Weak — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 33% | Weak — gated by R6, P3, P5, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 36% | Weak — gated by D36, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 41% | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — an Exposed table, a data class, a Room entity or a SQL migration's table named for it — Hibernate Envers' @Audited, a JPA entity listener, Hibernate event listener or jOOQ RecordListener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 65 check(s) not relevant to this codebase
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's Kotlin 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 TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — AX6 reached only 4% of this repository's production lines — kotlin (17,554 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — time="2026-11-14T12:59:13Z" level=warning msg="The \"AWESOME__GITHUB__CLIENT_SECRET\" variable is not set. Defaulting to a blank string." failed to solve: failed to compute cache key: failed to calculate checksum of ref 43f4e61a-50fc-43c1-9636-59687d7c502f::h5duyaxrqv5nvhm1ll8c3cjlo: "/app-frontend/dist": not found; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- 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.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .kt exposed no member bodies
- D10 Test Quality — ~71 lines of test source are present (.kt) 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 .kt suite was found but not re-run
- D12 Dependency Hygiene — Not scored — 4 Maven/Gradle manifest(s) were read, stating a version for 52 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D15 Churn × Complexity Hotspots — complexity unreadable for .kt — churn × complexity hotspots could not be measured
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — D19 reads .NET projects and npm packages as units; 3 folder(s) declared by build.gradle.kts were not judged for an overview, an example or the map.
- D2 Cognitive Complexity — cognitive complexity not measured — .kt exposed no member bodies
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .kt source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (46 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — the JS/TS workspace (20 production file(s)) has no JavaScript/TypeScript test, but it is 3.65% of this repository's production source and the other 96.35% carries 71 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
- R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: these web-security 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 web-security 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — X24 reached only 4% of this repository's production lines — kotlin (17,554 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 28 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label app-frontend/app/src/components/search/search.tsx:39
- <html> without a lang app-frontend/pages/index.html:2
- Viewport restricts zoom app-frontend/pages/index.html:6
- Click handler on a non-interactive <div> app-frontend/app/src/components/head/head.tsx:53
- Click handler on a non-interactive <span> app-frontend/app/src/components/version/KotlinVersion.tsx:11
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 24 finding(s)
- Outbound HTTP without resilience app-backend/src/main/kotlin/HttpClientModule.kt:14
- Outbound HTTP without resilience src/main/kotlin/link/kotlin/scripts/utils/HttpClient.kt:11
- Outbound HTTP without resilience src/main/kotlin/link/kotlin/scripts/utils/HttpClient.kt:21
- Anchor without href app-frontend/pages/index.html:37
- Anchor without href app-frontend/pages/index.html:48
- TodoComment app-backend/src/test/kotlin/usecases/kug/KugDownloadServiceTest.kt:23
- TodoComment app-backend/src/main/kotlin/ApplicationModule.kt:18
- REDACTED
- REDACTED
- Page without a main landmark app-frontend/app/index.html:2
- Focus outline removed in CSS without a :focus replacement app-frontend/pages/styles.css:53
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (19 corresponding lines) src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:86
- Edited copy of a member (11 corresponding lines) app-backend/src/main/kotlin/usecases/signup/Register.kt:72
- Duplicated block (18 lines × 2) app-backend/src/main/kotlin/usecases/links/Links.kt:142
- Duplicated block (5 lines × 2) app-backend/src/main/kotlin/usecases/version/KotlinVersionFetcher.kt:35
- Low cohesion: Kotliner (LCOM4 14) app-backend/src/main/kotlin/jooq/main/tables/Kotliner.kt:76
- No DR/backup evidence
- No test, lint or typecheck script
- Disposable created and abandoned in the function that made it src/main/kotlin/link/kotlin/scripts/ArticlesSource.kt:21
Minor — 27 finding(s)
- Interpolated log message defeats structured logging src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:33
- Interpolated log message defeats structured logging src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:39
- Interpolated log message defeats structured logging src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:81
- Interpolated log message defeats structured logging src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:96
- Interpolated log message defeats structured logging src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:101
- Interpolated log message defeats structured logging src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:129
- Interpolated log message defeats structured logging src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:134
- Interpolated log message defeats structured logging src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:143
- Interpolated log message defeats structured logging src/main/kotlin/link/kotlin/scripts/LinksProcessor.kt:148
- Interpolated log message defeats structured logging REDACTED:39
- Interpolated log message defeats structured logging src/main/kotlin/link/kotlin/scripts/utils/Utils.kt:39
- Interpolated log message defeats structured logging src/main/kotlin/link/kotlin/scripts/utils/Utils.kt:56
- REDACTED
- REDACTED
- Off-boarding risk: anonymized user #1
- No ADRs found build.gradle.kts:2
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- Orphaned file app-frontend/app/src/components/head/logos.ts:1
- REDACTED
- REDACTED
- REDACTED
- Thin README README.md:1
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No SAST REDACTED:4
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-b5585d488b2747b8a7dcc0df89fa08f8/history.json --exit-code 0 --source . | 36 | 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-b5585d488b2747b8a7dcc0df89fa08f8/tree.json --exit-code 0 --source . | 5 | 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 . | 20 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 6 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `app-backend/build.gradle.kts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |