Executive summary
JetBrains/kotlinconf-app falls short of our standard for production because it has controls that only work with a mouse. It scores 51 out of 100 and is rated Adequate, and 21 of its 24 critical findings are security problems in the build pipeline and in the packages it uses.
Accessibility, at 37, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 8 points. Recording design decisions comes next, worth about 2 points. Raising Accessibility to 70 would lift the score to about 62.
Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five 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. Making the controls work with a keyboard, pinning each tool to an exact version and updating the vulnerable packages would close these risks. The form field without a label needs a label.
The product code is 18,831 lines, about €19,000 to rebuild.
If Accessibility rose from 37 to 70, the lowest score rated Strong, the score would rise from 51 to about 62.
New since the last survey: 7 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Visual & motion safety · Animation without a prefers-reduced-motion guard app/adminApp/src/jsMain/resources/index.html
Fixed since the last survey: 24 findings
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- 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
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €19,000 · Estimate
| Cost to rebuild | €6,200 to €31,000, for 104 to 329 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 51. 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,831 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 backend.plugins | 2 backend.services.AssetService | 3 backend.utils | 4 ui.components | 5 LocalNotificationId | 6 backend.services.AssetService.AssetType | 7 utils | 8 LocalNotificationId.Type | 9 storage | 10 flags | 11 network | 12 di | 13 di.IosAppGraph | 14 di.JvmAppGraph | 15 di.WebAppGraph | 16 di.YearGraph | 17 org.jetbrains.kotlinconf | 18 JsJodaTimeZone | 19 MapHandler | 20 Score | 21 SessionState | 22 Theme | 23 admin | 24 android | 25 backend.model | 26 backend.routes | 27 backend.schema | 28 backend.services | 29 navigation | 30 admin.Screen | 31 admin.SortKey | 32 android.AndroidAppGraph | 33 backend.repositories | 34 navigation.BrowserIntegration | 35 screens | 36 screens.FeedbackViewModel | 37 screens.GoldenKodeeFinalistViewModel | 38 screens.PartnerDetailViewModel | 39 screens.SessionViewModel | 40 screens.SpeakerDetailViewModel |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 backend.plugins | ||||||||||||||||||||||||||||||||||||||||
| 2 backend.services.AssetService | ||||||||||||||||||||||||||||||||||||||||
| 3 backend.utils | ||||||||||||||||||||||||||||||||||||||||
| 4 ui.components | ||||||||||||||||||||||||||||||||||||||||
| 5 LocalNotificationId | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 backend.services.AssetService.AssetType | 3 | |||||||||||||||||||||||||||||||||||||||
| 7 utils | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 LocalNotificationId.Type | 3 | |||||||||||||||||||||||||||||||||||||||
| 9 storage | 4 | 2 | 17 | |||||||||||||||||||||||||||||||||||||
| 10 flags | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 network | 4 | 1 | 7 | |||||||||||||||||||||||||||||||||||||
| 12 di | 3 | 2 | 2 | 2 | 4 | |||||||||||||||||||||||||||||||||||
| 13 di.IosAppGraph | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 di.JvmAppGraph | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 di.WebAppGraph | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 di.YearGraph | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 org.jetbrains.kotlinconf | 1 | 1 | 11 | 2 | 2 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 18 JsJodaTimeZone | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 MapHandler | 4 | |||||||||||||||||||||||||||||||||||||||
| 20 Score | 4 | |||||||||||||||||||||||||||||||||||||||
| 21 SessionState | 4 | |||||||||||||||||||||||||||||||||||||||
| 22 Theme | 3 | |||||||||||||||||||||||||||||||||||||||
| 23 admin | 11 | |||||||||||||||||||||||||||||||||||||||
| 24 android | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 backend.model | 3 | |||||||||||||||||||||||||||||||||||||||
| 26 backend.routes | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 backend.schema | 3 | |||||||||||||||||||||||||||||||||||||||
| 28 backend.services | 1 | 5 | 4 | |||||||||||||||||||||||||||||||||||||
| 29 navigation | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 30 admin.Screen | 2 | |||||||||||||||||||||||||||||||||||||||
| 31 admin.SortKey | 9 | |||||||||||||||||||||||||||||||||||||||
| 32 android.AndroidAppGraph | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 backend.repositories | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 34 navigation.BrowserIntegration | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 screens | 8 | 10 | 1 | 77 | 1 | |||||||||||||||||||||||||||||||||||
| 36 screens.FeedbackViewModel | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 screens.GoldenKodeeFinalistViewModel | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 screens.PartnerDetailViewModel | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 screens.SessionViewModel | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 screens.SpeakerDetailViewModel | 1 | 1 |
5→17 LocalNotificationId uses org.jetbrains.kotlinconf part of a loop✕
- Connections
- 1 pair of types, where a type in LocalNotificationId uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.LocalNotificationId.Companion→org.jetbrains.kotlinconf.LocalNotificationId
- Direction
- LocalNotificationId uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break LocalNotificationId, while a change to LocalNotificationId can't break org.jetbrains.kotlinconf.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→2 backend.services.AssetService.AssetType uses backend.services.AssetService✕
- Connections
- 3 pairs of types, where a type in backend.services.AssetService.AssetType uses a type in backend.services.AssetService.
- The types involved
org.jetbrains.kotlinconf.backend.services.AssetService.AssetType.Document→org.jetbrains.kotlinconf.backend.services.AssetService.AssetTypeorg.jetbrains.kotlinconf.backend.services.AssetService.AssetType.Map→org.jetbrains.kotlinconf.backend.services.AssetService.AssetTypeorg.jetbrains.kotlinconf.backend.services.AssetService.AssetType.Partner→org.jetbrains.kotlinconf.backend.services.AssetService.AssetType
- Direction
- backend.services.AssetService.AssetType uses backend.services.AssetService, so a change to backend.services.AssetService can break backend.services.AssetService.AssetType, while a change to backend.services.AssetService.AssetType can't break backend.services.AssetService.
- Position
- Below the diagonal: backend.services.AssetService.AssetType uses a module listed above it, which is the healthy direction.
7→17 utils uses org.jetbrains.kotlinconf part of a loop✕
- Connections
- 1 pair of types, where a type in utils uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.utils.EmotionMappingKt→org.jetbrains.kotlinconf.Score
- Direction
- utils uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break utils, while a change to utils can't break org.jetbrains.kotlinconf.
- 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→5 LocalNotificationId.Type uses LocalNotificationId✕
- Connections
- 3 pairs of types, where a type in LocalNotificationId.Type uses a type in LocalNotificationId.
- The types involved
org.jetbrains.kotlinconf.LocalNotificationId.Type.Companion→org.jetbrains.kotlinconf.LocalNotificationId.Typeorg.jetbrains.kotlinconf.LocalNotificationId.Type.SessionEnd→org.jetbrains.kotlinconf.LocalNotificationId.Typeorg.jetbrains.kotlinconf.LocalNotificationId.Type.SessionStart→org.jetbrains.kotlinconf.LocalNotificationId.Type
- Direction
- LocalNotificationId.Type uses LocalNotificationId, so a change to LocalNotificationId can break LocalNotificationId.Type, while a change to LocalNotificationId.Type can't break LocalNotificationId.
- Position
- Below the diagonal: LocalNotificationId.Type uses a module listed above it, which is the healthy direction.
9→7 storage uses utils✕
- Connections
- 4 pairs of types, where a type in storage uses a type in utils.
- The types involved
org.jetbrains.kotlinconf.storage.ApplicationStorageImpl→org.jetbrains.kotlinconf.utils.Loggerorg.jetbrains.kotlinconf.storage.ApplicationStorageImpl→org.jetbrains.kotlinconf.utils.TaggedLoggerorg.jetbrains.kotlinconf.storage.OkioAssetStorage→org.jetbrains.kotlinconf.utils.Loggerorg.jetbrains.kotlinconf.storage.OkioAssetStorage→org.jetbrains.kotlinconf.utils.TaggedLogger
- Direction
- storage uses utils, so a change to utils can break storage, while a change to storage can't break utils.
- Position
- Below the diagonal: storage uses a module listed above it, which is the healthy direction.
9→10 storage uses flags part of a loop✕
- Connections
- 2 pairs of types, where a type in storage uses a type in flags.
- The types involved
org.jetbrains.kotlinconf.storage.ApplicationStorage→org.jetbrains.kotlinconf.flags.Flagsorg.jetbrains.kotlinconf.storage.ApplicationStorageImpl→org.jetbrains.kotlinconf.flags.Flags
- Direction
- storage uses flags, so a change to flags can break storage, while a change to storage can't break flags.
- 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→17 storage uses org.jetbrains.kotlinconf part of a loop✕
- Connections
- 17 pairs of types, where a type in storage uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.storage.ApplicationStorage→org.jetbrains.kotlinconf.AppConfigorg.jetbrains.kotlinconf.storage.ApplicationStorage→org.jetbrains.kotlinconf.Themeorg.jetbrains.kotlinconf.storage.ApplicationStorageImpl→org.jetbrains.kotlinconf.AppConfigorg.jetbrains.kotlinconf.storage.ApplicationStorageImpl→org.jetbrains.kotlinconf.Themeorg.jetbrains.kotlinconf.storage.DefaultValuesKt→org.jetbrains.kotlinconf.AppConfigorg.jetbrains.kotlinconf.storage.YearlyStorage→org.jetbrains.kotlinconf.Conferenceorg.jetbrains.kotlinconf.storage.YearlyStorage→org.jetbrains.kotlinconf.ConferenceInfoorg.jetbrains.kotlinconf.storage.YearlyStorage→org.jetbrains.kotlinconf.GoldenKodeeDataorg.jetbrains.kotlinconf.storage.YearlyStorage→org.jetbrains.kotlinconf.NotificationSettingsorg.jetbrains.kotlinconf.storage.YearlyStorage→org.jetbrains.kotlinconf.SessionIdorg.jetbrains.kotlinconf.storage.YearlyStorage→org.jetbrains.kotlinconf.VoteInfoorg.jetbrains.kotlinconf.storage.YearlyStorageImpl→org.jetbrains.kotlinconf.Conferenceorg.jetbrains.kotlinconf.storage.YearlyStorageImpl→org.jetbrains.kotlinconf.ConferenceInfoorg.jetbrains.kotlinconf.storage.YearlyStorageImpl→org.jetbrains.kotlinconf.GoldenKodeeDataorg.jetbrains.kotlinconf.storage.YearlyStorageImpl→org.jetbrains.kotlinconf.NotificationSettingsorg.jetbrains.kotlinconf.storage.YearlyStorageImpl→org.jetbrains.kotlinconf.SessionIdorg.jetbrains.kotlinconf.storage.YearlyStorageImpl→org.jetbrains.kotlinconf.VoteInfo
- Direction
- storage uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break storage, while a change to storage can't break org.jetbrains.kotlinconf.
- 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→9 flags uses storage✕
- Connections
- 1 pair of types, where a type in flags uses a type in storage.
- The types involved
org.jetbrains.kotlinconf.flags.FlagsManager→org.jetbrains.kotlinconf.storage.ApplicationStorage
- Direction
- flags uses storage, so a change to storage can break flags, while a change to flags can't break storage.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
10→17 flags uses org.jetbrains.kotlinconf part of a loop✕
- Connections
- 1 pair of types, where a type in flags uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.flags.FakeGoldenKodeeDataKt→org.jetbrains.kotlinconf.GoldenKodeeData
- Direction
- flags uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break flags, while a change to flags can't break org.jetbrains.kotlinconf.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→7 network uses utils✕
- Connections
- 4 pairs of types, where a type in network uses a type in utils.
- The types involved
org.jetbrains.kotlinconf.network.ApplicationApi→org.jetbrains.kotlinconf.utils.Loggerorg.jetbrains.kotlinconf.network.ApplicationApi→org.jetbrains.kotlinconf.utils.TaggedLoggerorg.jetbrains.kotlinconf.network.YearlyApi→org.jetbrains.kotlinconf.utils.Loggerorg.jetbrains.kotlinconf.network.YearlyApi→org.jetbrains.kotlinconf.utils.TaggedLogger
- Direction
- network uses utils, so a change to utils can break network, while a change to network can't break utils.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
11→9 network uses storage✕
- Connections
- 1 pair of types, where a type in network uses a type in storage.
- The types involved
org.jetbrains.kotlinconf.network.YearlyApi→org.jetbrains.kotlinconf.storage.ApplicationStorage
- Direction
- network uses storage, so a change to storage can break network, while a change to network can't break storage.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
11→17 network uses org.jetbrains.kotlinconf part of a loop✕
- Connections
- 7 pairs of types, where a type in network uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.network.ApplicationApi→org.jetbrains.kotlinconf.AppConfigorg.jetbrains.kotlinconf.network.YearlyApi→org.jetbrains.kotlinconf.Conferenceorg.jetbrains.kotlinconf.network.YearlyApi→org.jetbrains.kotlinconf.ConferenceInfoorg.jetbrains.kotlinconf.network.YearlyApi→org.jetbrains.kotlinconf.GoldenKodeeDataorg.jetbrains.kotlinconf.network.YearlyApi→org.jetbrains.kotlinconf.Scoreorg.jetbrains.kotlinconf.network.YearlyApi→org.jetbrains.kotlinconf.SessionIdorg.jetbrains.kotlinconf.network.YearlyApi→org.jetbrains.kotlinconf.VoteInfo
- Direction
- network uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break network, while a change to network can't break org.jetbrains.kotlinconf.
- 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→7 di uses utils✕
- Connections
- 3 pairs of types, where a type in di uses a type in utils.
- The types involved
org.jetbrains.kotlinconf.di.AppBindings→org.jetbrains.kotlinconf.utils.Loggerorg.jetbrains.kotlinconf.di.AppGraph→org.jetbrains.kotlinconf.utils.BufferedDelegatingLoggerorg.jetbrains.kotlinconf.di.AppGraph→org.jetbrains.kotlinconf.utils.Logger
- Direction
- di uses utils, so a change to utils can break di, while a change to di can't break utils.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
12→9 di uses storage✕
- Connections
- 2 pairs of types, where a type in di uses a type in storage.
- The types involved
org.jetbrains.kotlinconf.di.AppBindings→org.jetbrains.kotlinconf.storage.ApplicationStorageorg.jetbrains.kotlinconf.di.YearGraph→org.jetbrains.kotlinconf.storage.YearlyStorage
- Direction
- di uses storage, so a change to storage can break di, while a change to di can't break storage.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
12→10 di uses flags✕
- Connections
- 2 pairs of types, where a type in di uses a type in flags.
- The types involved
org.jetbrains.kotlinconf.di.AppBindings→org.jetbrains.kotlinconf.flags.Flagsorg.jetbrains.kotlinconf.di.AppGraph→org.jetbrains.kotlinconf.flags.FlagsManager
- Direction
- di uses flags, so a change to flags can break di, while a change to di can't break flags.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
12→11 di uses network✕
- Connections
- 2 pairs of types, where a type in di uses a type in network.
- The types involved
org.jetbrains.kotlinconf.di.AppBindings→org.jetbrains.kotlinconf.network.ApplicationApiorg.jetbrains.kotlinconf.di.YearGraph→org.jetbrains.kotlinconf.network.YearlyApi
- Direction
- di uses network, so a change to network can break di, while a change to di can't break network.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
12→17 di uses org.jetbrains.kotlinconf part of a loop✕
- Connections
- 4 pairs of types, where a type in di uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.di.AppBindings→org.jetbrains.kotlinconf.TimeProviderorg.jetbrains.kotlinconf.di.AppGraph→org.jetbrains.kotlinconf.ConferenceServiceorg.jetbrains.kotlinconf.di.AppGraph→org.jetbrains.kotlinconf.TimeProviderorg.jetbrains.kotlinconf.di.JvmBindings→org.jetbrains.kotlinconf.LocalNotificationService
- Direction
- di uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break di, while a change to di can't break org.jetbrains.kotlinconf.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→10 di.IosAppGraph uses flags✕
- Connections
- 1 pair of types, where a type in di.IosAppGraph uses a type in flags.
- The types involved
org.jetbrains.kotlinconf.di.IosAppGraph.Factory→org.jetbrains.kotlinconf.flags.Flags
- Direction
- di.IosAppGraph uses flags, so a change to flags can break di.IosAppGraph, while a change to di.IosAppGraph can't break flags.
- Position
- Below the diagonal: di.IosAppGraph uses a module listed above it, which is the healthy direction.
13→12 di.IosAppGraph uses di✕
- Connections
- 1 pair of types, where a type in di.IosAppGraph uses a type in di.
- The types involved
org.jetbrains.kotlinconf.di.IosAppGraph.Factory→org.jetbrains.kotlinconf.di.IosAppGraph
- Direction
- di.IosAppGraph uses di, so a change to di can break di.IosAppGraph, while a change to di.IosAppGraph can't break di.
- Position
- Below the diagonal: di.IosAppGraph uses a module listed above it, which is the healthy direction.
14→10 di.JvmAppGraph uses flags✕
- Connections
- 1 pair of types, where a type in di.JvmAppGraph uses a type in flags.
- The types involved
org.jetbrains.kotlinconf.di.JvmAppGraph.Factory→org.jetbrains.kotlinconf.flags.Flags
- Direction
- di.JvmAppGraph uses flags, so a change to flags can break di.JvmAppGraph, while a change to di.JvmAppGraph can't break flags.
- Position
- Below the diagonal: di.JvmAppGraph uses a module listed above it, which is the healthy direction.
14→12 di.JvmAppGraph uses di✕
- Connections
- 1 pair of types, where a type in di.JvmAppGraph uses a type in di.
- The types involved
org.jetbrains.kotlinconf.di.JvmAppGraph.Factory→org.jetbrains.kotlinconf.di.JvmAppGraph
- Direction
- di.JvmAppGraph uses di, so a change to di can break di.JvmAppGraph, while a change to di.JvmAppGraph can't break di.
- Position
- Below the diagonal: di.JvmAppGraph uses a module listed above it, which is the healthy direction.
15→10 di.WebAppGraph uses flags✕
- Connections
- 1 pair of types, where a type in di.WebAppGraph uses a type in flags.
- The types involved
org.jetbrains.kotlinconf.di.WebAppGraph.Factory→org.jetbrains.kotlinconf.flags.Flags
- Direction
- di.WebAppGraph uses flags, so a change to flags can break di.WebAppGraph, while a change to di.WebAppGraph can't break flags.
- Position
- Below the diagonal: di.WebAppGraph uses a module listed above it, which is the healthy direction.
15→12 di.WebAppGraph uses di✕
- Connections
- 1 pair of types, where a type in di.WebAppGraph uses a type in di.
- The types involved
org.jetbrains.kotlinconf.di.WebAppGraph.Factory→org.jetbrains.kotlinconf.di.WebAppGraph
- Direction
- di.WebAppGraph uses di, so a change to di can break di.WebAppGraph, while a change to di.WebAppGraph can't break di.
- Position
- Below the diagonal: di.WebAppGraph uses a module listed above it, which is the healthy direction.
16→12 di.YearGraph uses di✕
- Connections
- 1 pair of types, where a type in di.YearGraph uses a type in di.
- The types involved
org.jetbrains.kotlinconf.di.YearGraph.Factory→org.jetbrains.kotlinconf.di.YearGraph
- Direction
- di.YearGraph uses di, so a change to di can break di.YearGraph, while a change to di.YearGraph can't break di.
- Position
- Below the diagonal: di.YearGraph uses a module listed above it, which is the healthy direction.
17→4 org.jetbrains.kotlinconf uses ui.components✕
- Connections
- 1 pair of types, where a type in org.jetbrains.kotlinconf uses a type in ui.components.
- The types involved
org.jetbrains.kotlinconf.SessionCardViewKt→org.jetbrains.kotlinconf.ui.components.Emotion
- Direction
- org.jetbrains.kotlinconf uses ui.components, so a change to ui.components can break org.jetbrains.kotlinconf, while a change to org.jetbrains.kotlinconf can't break ui.components.
- Position
- Below the diagonal: org.jetbrains.kotlinconf uses a module listed above it, which is the healthy direction.
17→5 org.jetbrains.kotlinconf uses LocalNotificationId✕
- Connections
- 1 pair of types, where a type in org.jetbrains.kotlinconf uses a type in LocalNotificationId.
- The types involved
org.jetbrains.kotlinconf.LocalNotificationId→org.jetbrains.kotlinconf.LocalNotificationId.Type
- Direction
- org.jetbrains.kotlinconf uses LocalNotificationId, so a change to LocalNotificationId can break org.jetbrains.kotlinconf, while a change to org.jetbrains.kotlinconf can't break LocalNotificationId.
- Position
- Below the diagonal: org.jetbrains.kotlinconf uses a module listed above it, which is the healthy direction.
17→7 org.jetbrains.kotlinconf uses utils✕
- Connections
- 11 pairs of types, where a type in org.jetbrains.kotlinconf uses a type in utils.
- The types involved
org.jetbrains.kotlinconf.AndroidLocalNotificationService→org.jetbrains.kotlinconf.utils.Loggerorg.jetbrains.kotlinconf.AppInitKt→org.jetbrains.kotlinconf.utils.BufferedDelegatingLoggerorg.jetbrains.kotlinconf.AppInitKt→org.jetbrains.kotlinconf.utils.Loggerorg.jetbrains.kotlinconf.BaseScreensKt→org.jetbrains.kotlinconf.utils.ErrorLoadingStateorg.jetbrains.kotlinconf.ConferenceService→org.jetbrains.kotlinconf.utils.Loggerorg.jetbrains.kotlinconf.ConferenceService→org.jetbrains.kotlinconf.utils.TaggedLoggerorg.jetbrains.kotlinconf.FakeTimeProvider→org.jetbrains.kotlinconf.utils.Loggerorg.jetbrains.kotlinconf.IOSLocalNotificationService→org.jetbrains.kotlinconf.utils.Loggerorg.jetbrains.kotlinconf.IOSLogger→org.jetbrains.kotlinconf.utils.Loggerorg.jetbrains.kotlinconf.JvmLogger→org.jetbrains.kotlinconf.utils.Loggerorg.jetbrains.kotlinconf.PermissionHandler→org.jetbrains.kotlinconf.utils.Logger
- Direction
- org.jetbrains.kotlinconf uses utils, so a change to utils can break org.jetbrains.kotlinconf, while a change to org.jetbrains.kotlinconf can't break utils.
- Position
- Below the diagonal: org.jetbrains.kotlinconf uses a module listed above it, which is the healthy direction.
17→9 org.jetbrains.kotlinconf uses storage✕
- Connections
- 2 pairs of types, where a type in org.jetbrains.kotlinconf uses a type in storage.
- The types involved
org.jetbrains.kotlinconf.ConferenceService→org.jetbrains.kotlinconf.storage.ApplicationStorageorg.jetbrains.kotlinconf.ConferenceService→org.jetbrains.kotlinconf.storage.YearlyStorage
- Direction
- org.jetbrains.kotlinconf uses storage, so a change to storage can break org.jetbrains.kotlinconf, while a change to org.jetbrains.kotlinconf can't break storage.
- Position
- Below the diagonal: org.jetbrains.kotlinconf uses a module listed above it, which is the healthy direction.
17→10 org.jetbrains.kotlinconf uses flags✕
- Connections
- 2 pairs of types, where a type in org.jetbrains.kotlinconf uses a type in flags.
- The types involved
org.jetbrains.kotlinconf.AppInitKt→org.jetbrains.kotlinconf.flags.FlagsManagerorg.jetbrains.kotlinconf.ConferenceService→org.jetbrains.kotlinconf.flags.FlagsManager
- Direction
- org.jetbrains.kotlinconf uses flags, so a change to flags can break org.jetbrains.kotlinconf, while a change to org.jetbrains.kotlinconf can't break flags.
- Position
- Below the diagonal: org.jetbrains.kotlinconf uses a module listed above it, which is the healthy direction.
17→11 org.jetbrains.kotlinconf uses network✕
- Connections
- 2 pairs of types, where a type in org.jetbrains.kotlinconf uses a type in network.
- The types involved
org.jetbrains.kotlinconf.ConferenceService→org.jetbrains.kotlinconf.network.ApplicationApiorg.jetbrains.kotlinconf.ServerBasedTimeProvider→org.jetbrains.kotlinconf.network.ApplicationApi
- Direction
- org.jetbrains.kotlinconf uses network, so a change to network can break org.jetbrains.kotlinconf, while a change to org.jetbrains.kotlinconf can't break network.
- Position
- Below the diagonal: org.jetbrains.kotlinconf uses a module listed above it, which is the healthy direction.
17→12 org.jetbrains.kotlinconf uses di✕
- Connections
- 3 pairs of types, where a type in org.jetbrains.kotlinconf uses a type in di.
- The types involved
org.jetbrains.kotlinconf.AppInitKt→org.jetbrains.kotlinconf.di.AppGraphorg.jetbrains.kotlinconf.AppKt→org.jetbrains.kotlinconf.di.AppGraphorg.jetbrains.kotlinconf.ConferenceService→org.jetbrains.kotlinconf.di.YearGraph
- Direction
- org.jetbrains.kotlinconf uses di, so a change to di can break org.jetbrains.kotlinconf, while a change to org.jetbrains.kotlinconf can't break di.
- Position
- Below the diagonal: org.jetbrains.kotlinconf uses a module listed above it, which is the healthy direction.
17→16 org.jetbrains.kotlinconf uses di.YearGraph✕
- Connections
- 1 pair of types, where a type in org.jetbrains.kotlinconf uses a type in di.YearGraph.
- The types involved
org.jetbrains.kotlinconf.ConferenceService→org.jetbrains.kotlinconf.di.YearGraph.Factory
- Direction
- org.jetbrains.kotlinconf uses di.YearGraph, so a change to di.YearGraph can break org.jetbrains.kotlinconf, while a change to org.jetbrains.kotlinconf can't break di.YearGraph.
- Position
- Below the diagonal: org.jetbrains.kotlinconf uses a module listed above it, which is the healthy direction.
18→17 JsJodaTimeZone uses org.jetbrains.kotlinconf✕
- Connections
- 1 pair of types, where a type in JsJodaTimeZone uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.JsJodaTimeZone.webKt→org.jetbrains.kotlinconf.JsJodaTimeZoneModule
- Direction
- JsJodaTimeZone uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break JsJodaTimeZone, while a change to JsJodaTimeZone can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: JsJodaTimeZone uses a module listed above it, which is the healthy direction.
19→17 MapHandler uses org.jetbrains.kotlinconf✕
- Connections
- 4 pairs of types, where a type in MapHandler uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.MapHandler.androidKt→org.jetbrains.kotlinconf.MapHandlerorg.jetbrains.kotlinconf.MapHandler.iosKt→org.jetbrains.kotlinconf.MapHandlerorg.jetbrains.kotlinconf.MapHandler.jvmKt→org.jetbrains.kotlinconf.MapHandlerorg.jetbrains.kotlinconf.MapHandler.webKt→org.jetbrains.kotlinconf.MapHandler
- Direction
- MapHandler uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break MapHandler, while a change to MapHandler can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: MapHandler uses a module listed above it, which is the healthy direction.
20→17 Score uses org.jetbrains.kotlinconf✕
- Connections
- 4 pairs of types, where a type in Score uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.Score.BAD→org.jetbrains.kotlinconf.Scoreorg.jetbrains.kotlinconf.Score.Companion→org.jetbrains.kotlinconf.Scoreorg.jetbrains.kotlinconf.Score.GOOD→org.jetbrains.kotlinconf.Scoreorg.jetbrains.kotlinconf.Score.OK→org.jetbrains.kotlinconf.Score
- Direction
- Score uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break Score, while a change to Score can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: Score uses a module listed above it, which is the healthy direction.
21→17 SessionState uses org.jetbrains.kotlinconf✕
- Connections
- 4 pairs of types, where a type in SessionState uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.SessionState.Companion→org.jetbrains.kotlinconf.SessionStateorg.jetbrains.kotlinconf.SessionState.Live→org.jetbrains.kotlinconf.SessionStateorg.jetbrains.kotlinconf.SessionState.Past→org.jetbrains.kotlinconf.SessionStateorg.jetbrains.kotlinconf.SessionState.Upcoming→org.jetbrains.kotlinconf.SessionState
- Direction
- SessionState uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break SessionState, while a change to SessionState can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: SessionState uses a module listed above it, which is the healthy direction.
22→17 Theme uses org.jetbrains.kotlinconf✕
- Connections
- 3 pairs of types, where a type in Theme uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.Theme.DARK→org.jetbrains.kotlinconf.Themeorg.jetbrains.kotlinconf.Theme.LIGHT→org.jetbrains.kotlinconf.Themeorg.jetbrains.kotlinconf.Theme.SYSTEM→org.jetbrains.kotlinconf.Theme
- Direction
- Theme uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break Theme, while a change to Theme can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: Theme uses a module listed above it, which is the healthy direction.
23→17 admin uses org.jetbrains.kotlinconf✕
- Connections
- 11 pairs of types, where a type in admin uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.admin.AdminApi→org.jetbrains.kotlinconf.Conferenceorg.jetbrains.kotlinconf.admin.AdminFeedbackRow→org.jetbrains.kotlinconf.SessionIdorg.jetbrains.kotlinconf.admin.AdminVoteRow→org.jetbrains.kotlinconf.Scoreorg.jetbrains.kotlinconf.admin.AdminVoteRow→org.jetbrains.kotlinconf.SessionIdorg.jetbrains.kotlinconf.admin.AggregatedData→org.jetbrains.kotlinconf.Scoreorg.jetbrains.kotlinconf.admin.AggregatedData→org.jetbrains.kotlinconf.Sessionorg.jetbrains.kotlinconf.admin.AggregatedData→org.jetbrains.kotlinconf.Speakerorg.jetbrains.kotlinconf.admin.AggregationKt→org.jetbrains.kotlinconf.Conferenceorg.jetbrains.kotlinconf.admin.OverviewScreenKt→org.jetbrains.kotlinconf.Scoreorg.jetbrains.kotlinconf.admin.UserScreenKt→org.jetbrains.kotlinconf.Scoreorg.jetbrains.kotlinconf.admin.UserVote→org.jetbrains.kotlinconf.Score
- Direction
- admin uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break admin, while a change to admin can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: admin uses a module listed above it, which is the healthy direction.
24→12 android uses di✕
- Connections
- 1 pair of types, where a type in android uses a type in di.
- The types involved
org.jetbrains.kotlinconf.android.AndroidAppGraph→org.jetbrains.kotlinconf.di.BaseAndroidAppGraph
- Direction
- android uses di, so a change to di can break android, while a change to android can't break di.
- Position
- Below the diagonal: android uses a module listed above it, which is the healthy direction.
24→17 android uses org.jetbrains.kotlinconf✕
- Connections
- 1 pair of types, where a type in android uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.android.MainActivity→org.jetbrains.kotlinconf.PermissionHandler
- Direction
- android uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break android, while a change to android can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: android uses a module listed above it, which is the healthy direction.
25→17 backend.model uses org.jetbrains.kotlinconf✕
- Connections
- 3 pairs of types, where a type in backend.model uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.backend.model.SessionData→org.jetbrains.kotlinconf.SessionIdorg.jetbrains.kotlinconf.backend.model.SessionData→org.jetbrains.kotlinconf.SpeakerIdorg.jetbrains.kotlinconf.backend.model.SpeakerData→org.jetbrains.kotlinconf.SpeakerId
- Direction
- backend.model uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break backend.model, while a change to backend.model can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: backend.model uses a module listed above it, which is the healthy direction.
26→1 backend.routes uses backend.plugins✕
- Connections
- 1 pair of types, where a type in backend.routes uses a type in backend.plugins.
- The types involved
org.jetbrains.kotlinconf.backend.routes.UtilsKt→org.jetbrains.kotlinconf.backend.plugins.KotlinConfPrincipal
- Direction
- backend.routes uses backend.plugins, so a change to backend.plugins can break backend.routes, while a change to backend.routes can't break backend.plugins.
- Position
- Below the diagonal: backend.routes uses a module listed above it, which is the healthy direction.
26→3 backend.routes uses backend.utils✕
- Connections
- 1 pair of types, where a type in backend.routes uses a type in backend.utils.
- The types involved
org.jetbrains.kotlinconf.backend.routes.UtilsKt→org.jetbrains.kotlinconf.backend.utils.ConferenceConfig
- Direction
- backend.routes uses backend.utils, so a change to backend.utils can break backend.routes, while a change to backend.routes can't break backend.utils.
- Position
- Below the diagonal: backend.routes uses a module listed above it, which is the healthy direction.
26→17 backend.routes uses org.jetbrains.kotlinconf✕
- Connections
- 3 pairs of types, where a type in backend.routes uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.backend.routes.AdminFeedbackInfo→org.jetbrains.kotlinconf.SessionIdorg.jetbrains.kotlinconf.backend.routes.AdminVoteInfo→org.jetbrains.kotlinconf.Scoreorg.jetbrains.kotlinconf.backend.routes.AdminVoteInfo→org.jetbrains.kotlinconf.SessionId
- Direction
- backend.routes uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break backend.routes, while a change to backend.routes can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: backend.routes uses a module listed above it, which is the healthy direction.
26→33 backend.routes uses backend.repositories part of a loop✕
- Connections
- 1 pair of types, where a type in backend.routes uses a type in backend.repositories.
- The types involved
org.jetbrains.kotlinconf.backend.routes.UtilsKt→org.jetbrains.kotlinconf.backend.repositories.KotlinConfRepository
- Direction
- backend.routes uses backend.repositories, so a change to backend.repositories can break backend.routes, while a change to backend.routes can't break backend.repositories.
- 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→17 backend.schema uses org.jetbrains.kotlinconf✕
- Connections
- 3 pairs of types, where a type in backend.schema uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.backend.schema.Feedback→org.jetbrains.kotlinconf.SessionIdorg.jetbrains.kotlinconf.backend.schema.SessionIdTransformer→org.jetbrains.kotlinconf.SessionIdorg.jetbrains.kotlinconf.backend.schema.Votes→org.jetbrains.kotlinconf.SessionId
- Direction
- backend.schema uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break backend.schema, while a change to backend.schema can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: backend.schema uses a module listed above it, which is the healthy direction.
28→2 backend.services uses backend.services.AssetService✕
- Connections
- 1 pair of types, where a type in backend.services uses a type in backend.services.AssetService.
- The types involved
org.jetbrains.kotlinconf.backend.services.AssetService→org.jetbrains.kotlinconf.backend.services.AssetService.AssetType
- Direction
- backend.services uses backend.services.AssetService, so a change to backend.services.AssetService can break backend.services, while a change to backend.services can't break backend.services.AssetService.
- Position
- Below the diagonal: backend.services uses a module listed above it, which is the healthy direction.
28→3 backend.services uses backend.utils✕
- Connections
- 5 pairs of types, where a type in backend.services uses a type in backend.utils.
- The types involved
org.jetbrains.kotlinconf.backend.services.ArchivedDataService→org.jetbrains.kotlinconf.backend.utils.ConferenceConfigorg.jetbrains.kotlinconf.backend.services.AssetService→org.jetbrains.kotlinconf.backend.utils.ConferenceConfigorg.jetbrains.kotlinconf.backend.services.ConferenceInfoService→org.jetbrains.kotlinconf.backend.utils.ConferenceConfigorg.jetbrains.kotlinconf.backend.services.GoldenKodeeService→org.jetbrains.kotlinconf.backend.utils.ConferenceConfigorg.jetbrains.kotlinconf.backend.services.SessionizeService→org.jetbrains.kotlinconf.backend.utils.ConferenceConfig
- Direction
- backend.services uses backend.utils, so a change to backend.utils can break backend.services, while a change to backend.services can't break backend.utils.
- Position
- Below the diagonal: backend.services uses a module listed above it, which is the healthy direction.
28→17 backend.services uses org.jetbrains.kotlinconf✕
- Connections
- 4 pairs of types, where a type in backend.services uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.backend.services.ConferenceInfoService→org.jetbrains.kotlinconf.ConferenceInfoorg.jetbrains.kotlinconf.backend.services.GoldenKodeeService→org.jetbrains.kotlinconf.GoldenKodeeDataorg.jetbrains.kotlinconf.backend.services.SessionizeService→org.jetbrains.kotlinconf.Conferenceorg.jetbrains.kotlinconf.backend.services.SessionizeService→org.jetbrains.kotlinconf.Session
- Direction
- backend.services uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break backend.services, while a change to backend.services can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: backend.services uses a module listed above it, which is the healthy direction.
29→4 navigation uses ui.components✕
- Connections
- 1 pair of types, where a type in navigation uses a type in ui.components.
- The types involved
org.jetbrains.kotlinconf.navigation.NavScaffoldKt→org.jetbrains.kotlinconf.ui.components.MainNavDestination
- Direction
- navigation uses ui.components, so a change to ui.components can break navigation, while a change to navigation can't break ui.components.
- Position
- Below the diagonal: navigation uses a module listed above it, which is the healthy direction.
29→17 navigation uses org.jetbrains.kotlinconf✕
- Connections
- 6 pairs of types, where a type in navigation uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.navigation.GoldenKodeeFinalistScreen→org.jetbrains.kotlinconf.AwardCategoryIdorg.jetbrains.kotlinconf.navigation.GoldenKodeeFinalistScreen→org.jetbrains.kotlinconf.NomineeIdorg.jetbrains.kotlinconf.navigation.NavHostKt→org.jetbrains.kotlinconf.SessionIdorg.jetbrains.kotlinconf.navigation.PartnerDetailScreen→org.jetbrains.kotlinconf.PartnerIdorg.jetbrains.kotlinconf.navigation.SessionScreen→org.jetbrains.kotlinconf.SessionIdorg.jetbrains.kotlinconf.navigation.SpeakerDetailScreen→org.jetbrains.kotlinconf.SpeakerId
- Direction
- navigation uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break navigation, while a change to navigation can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: navigation uses a module listed above it, which is the healthy direction.
30→23 admin.Screen uses admin✕
- Connections
- 2 pairs of types, where a type in admin.Screen uses a type in admin.
- The types involved
org.jetbrains.kotlinconf.admin.Screen.Overview→org.jetbrains.kotlinconf.admin.Screenorg.jetbrains.kotlinconf.admin.Screen.User→org.jetbrains.kotlinconf.admin.Screen
- Direction
- admin.Screen uses admin, so a change to admin can break admin.Screen, while a change to admin.Screen can't break admin.
- Position
- Below the diagonal: admin.Screen uses a module listed above it, which is the healthy direction.
31→23 admin.SortKey uses admin✕
- Connections
- 9 pairs of types, where a type in admin.SortKey uses a type in admin.
- The types involved
org.jetbrains.kotlinconf.admin.SortKey.BAD→org.jetbrains.kotlinconf.admin.SortKeyorg.jetbrains.kotlinconf.admin.SortKey.FEEDBACK→org.jetbrains.kotlinconf.admin.SortKeyorg.jetbrains.kotlinconf.admin.SortKey.GOOD→org.jetbrains.kotlinconf.admin.SortKeyorg.jetbrains.kotlinconf.admin.SortKey.OK→org.jetbrains.kotlinconf.admin.SortKeyorg.jetbrains.kotlinconf.admin.SortKey.POPULARITY→org.jetbrains.kotlinconf.admin.SortKeyorg.jetbrains.kotlinconf.admin.SortKey.RATING→org.jetbrains.kotlinconf.admin.SortKeyorg.jetbrains.kotlinconf.admin.SortKey.SPEAKER→org.jetbrains.kotlinconf.admin.SortKeyorg.jetbrains.kotlinconf.admin.SortKey.TITLE→org.jetbrains.kotlinconf.admin.SortKeyorg.jetbrains.kotlinconf.admin.SortKey.TOTAL→org.jetbrains.kotlinconf.admin.SortKey
- Direction
- admin.SortKey uses admin, so a change to admin can break admin.SortKey, while a change to admin.SortKey can't break admin.
- Position
- Below the diagonal: admin.SortKey uses a module listed above it, which is the healthy direction.
32→10 android.AndroidAppGraph uses flags✕
- Connections
- 1 pair of types, where a type in android.AndroidAppGraph uses a type in flags.
- The types involved
org.jetbrains.kotlinconf.android.AndroidAppGraph.Factory→org.jetbrains.kotlinconf.flags.Flags
- Direction
- android.AndroidAppGraph uses flags, so a change to flags can break android.AndroidAppGraph, while a change to android.AndroidAppGraph can't break flags.
- Position
- Below the diagonal: android.AndroidAppGraph uses a module listed above it, which is the healthy direction.
32→24 android.AndroidAppGraph uses android✕
- Connections
- 1 pair of types, where a type in android.AndroidAppGraph uses a type in android.
- The types involved
org.jetbrains.kotlinconf.android.AndroidAppGraph.Factory→org.jetbrains.kotlinconf.android.AndroidAppGraph
- Direction
- android.AndroidAppGraph uses android, so a change to android can break android.AndroidAppGraph, while a change to android.AndroidAppGraph can't break android.
- Position
- Below the diagonal: android.AndroidAppGraph uses a module listed above it, which is the healthy direction.
33→17 backend.repositories uses org.jetbrains.kotlinconf✕
- Connections
- 3 pairs of types, where a type in backend.repositories uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.backend.repositories.KotlinConfRepository→org.jetbrains.kotlinconf.Scoreorg.jetbrains.kotlinconf.backend.repositories.KotlinConfRepository→org.jetbrains.kotlinconf.SessionIdorg.jetbrains.kotlinconf.backend.repositories.KotlinConfRepository→org.jetbrains.kotlinconf.VoteInfo
- Direction
- backend.repositories uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break backend.repositories, while a change to backend.repositories can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: backend.repositories uses a module listed above it, which is the healthy direction.
33→26 backend.repositories uses backend.routes✕
- Connections
- 2 pairs of types, where a type in backend.repositories uses a type in backend.routes.
- The types involved
org.jetbrains.kotlinconf.backend.repositories.KotlinConfRepository→org.jetbrains.kotlinconf.backend.routes.AdminFeedbackInfoorg.jetbrains.kotlinconf.backend.repositories.KotlinConfRepository→org.jetbrains.kotlinconf.backend.routes.AdminVoteInfo
- Direction
- backend.repositories uses backend.routes, so a change to backend.routes can break backend.repositories, while a change to backend.repositories can't break backend.routes.
- Position
- Below the diagonal: backend.repositories uses a module listed above it, which is the healthy direction.
34→29 navigation.BrowserIntegration uses navigation✕
- Connections
- 2 pairs of types, where a type in navigation.BrowserIntegration uses a type in navigation.
- The types involved
org.jetbrains.kotlinconf.navigation.BrowserIntegration.nonwebKt→org.jetbrains.kotlinconf.navigation.NavStateorg.jetbrains.kotlinconf.navigation.BrowserIntegration.webKt→org.jetbrains.kotlinconf.navigation.NavState
- Direction
- navigation.BrowserIntegration uses navigation, so a change to navigation can break navigation.BrowserIntegration, while a change to navigation.BrowserIntegration can't break navigation.
- Position
- Below the diagonal: navigation.BrowserIntegration uses a module listed above it, which is the healthy direction.
35→4 screens uses ui.components✕
- Connections
- 8 pairs of types, where a type in screens uses a type in ui.components.
- The types involved
org.jetbrains.kotlinconf.screens.FeedbackKt→org.jetbrains.kotlinconf.ui.components.Emotionorg.jetbrains.kotlinconf.screens.FeedbackKt→org.jetbrains.kotlinconf.ui.components.TalkStatusorg.jetbrains.kotlinconf.screens.FeedbackViewModel→org.jetbrains.kotlinconf.ui.components.Emotionorg.jetbrains.kotlinconf.screens.ScheduleScreenKt→org.jetbrains.kotlinconf.ui.components.FilterItemorg.jetbrains.kotlinconf.screens.ScheduleScreenKt→org.jetbrains.kotlinconf.ui.components.MainHeaderContainerStateorg.jetbrains.kotlinconf.screens.ScheduleScreenKt→org.jetbrains.kotlinconf.ui.components.NowButtonStateorg.jetbrains.kotlinconf.screens.ScheduleViewModel→org.jetbrains.kotlinconf.ui.components.FilterItemorg.jetbrains.kotlinconf.screens.ScheduleViewModel→org.jetbrains.kotlinconf.ui.components.FilterItemType
- Direction
- screens uses ui.components, so a change to ui.components can break screens, while a change to screens can't break ui.components.
- Position
- Below the diagonal: screens uses a module listed above it, which is the healthy direction.
35→7 screens uses utils✕
- Connections
- 10 pairs of types, where a type in screens uses a type in utils.
- The types involved
org.jetbrains.kotlinconf.screens.DocumentsViewModel→org.jetbrains.kotlinconf.utils.ErrorLoadingStateorg.jetbrains.kotlinconf.screens.MapViewModel→org.jetbrains.kotlinconf.utils.ErrorLoadingStateorg.jetbrains.kotlinconf.screens.MapViewModel→org.jetbrains.kotlinconf.utils.Loggerorg.jetbrains.kotlinconf.screens.MapViewModel→org.jetbrains.kotlinconf.utils.TaggedLoggerorg.jetbrains.kotlinconf.screens.PartnerDetailViewModel→org.jetbrains.kotlinconf.utils.ErrorLoadingStateorg.jetbrains.kotlinconf.screens.PrivacyNoticeViewModel→org.jetbrains.kotlinconf.utils.ErrorLoadingStateorg.jetbrains.kotlinconf.screens.ScheduleViewModel→org.jetbrains.kotlinconf.utils.ErrorLoadingStateorg.jetbrains.kotlinconf.screens.SessionViewModel→org.jetbrains.kotlinconf.utils.ErrorLoadingStateorg.jetbrains.kotlinconf.screens.SpeakerDetailViewModel→org.jetbrains.kotlinconf.utils.ErrorLoadingStateorg.jetbrains.kotlinconf.screens.SpeakersViewModel→org.jetbrains.kotlinconf.utils.ErrorLoadingState
- Direction
- screens uses utils, so a change to utils can break screens, while a change to screens can't break utils.
- Position
- Below the diagonal: screens uses a module listed above it, which is the healthy direction.
35→10 screens uses flags✕
- Connections
- 1 pair of types, where a type in screens uses a type in flags.
- The types involved
org.jetbrains.kotlinconf.screens.AboutAppScreenKt→org.jetbrains.kotlinconf.flags.Flags
- Direction
- screens uses flags, so a change to flags can break screens, while a change to screens can't break flags.
- Position
- Below the diagonal: screens uses a module listed above it, which is the healthy direction.
35→17 screens uses org.jetbrains.kotlinconf✕
- Connections
- 77 pairs of types, where a type in screens uses a type in org.jetbrains.kotlinconf. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.jetbrains.kotlinconf.screens.AboutConferenceEvent→org.jetbrains.kotlinconf.SessionCardVieworg.jetbrains.kotlinconf.screens.AboutConferenceEvent→org.jetbrains.kotlinconf.Speakerorg.jetbrains.kotlinconf.screens.AboutConferenceKt→org.jetbrains.kotlinconf.Speakerorg.jetbrains.kotlinconf.screens.AboutConferenceKt→org.jetbrains.kotlinconf.SpeakerIdorg.jetbrains.kotlinconf.screens.AboutConferenceViewModel→org.jetbrains.kotlinconf.ConferenceInfoorg.jetbrains.kotlinconf.screens.AboutConferenceViewModel→org.jetbrains.kotlinconf.ConferenceServiceorg.jetbrains.kotlinconf.screens.DayHeaderItem→org.jetbrains.kotlinconf.Dayorg.jetbrains.kotlinconf.screens.DocumentsViewModel→org.jetbrains.kotlinconf.ConferenceServiceorg.jetbrains.kotlinconf.screens.FeedbackKt→org.jetbrains.kotlinconf.SessionIdorg.jetbrains.kotlinconf.screens.FeedbackViewModel→org.jetbrains.kotlinconf.ConferenceServiceorg.jetbrains.kotlinconf.screens.FeedbackViewModel→org.jetbrains.kotlinconf.SessionIdorg.jetbrains.kotlinconf.screens.GoldenKodeeFinalistScreenKt→org.jetbrains.kotlinconf.AwardCategoryIdorg.jetbrains.kotlinconf.screens.GoldenKodeeFinalistScreenKt→org.jetbrains.kotlinconf.NomineeIdorg.jetbrains.kotlinconf.screens.GoldenKodeeFinalistViewModel→org.jetbrains.kotlinconf.AwardCategoryIdorg.jetbrains.kotlinconf.screens.GoldenKodeeFinalistViewModel→org.jetbrains.kotlinconf.ConferenceServiceorg.jetbrains.kotlinconf.screens.GoldenKodeeFinalistViewModel→org.jetbrains.kotlinconf.Nomineeorg.jetbrains.kotlinconf.screens.GoldenKodeeFinalistViewModel→org.jetbrains.kotlinconf.NomineeIdorg.jetbrains.kotlinconf.screens.GoldenKodeeScreenKt→org.jetbrains.kotlinconf.AwardCategoryIdorg.jetbrains.kotlinconf.screens.GoldenKodeeScreenKt→org.jetbrains.kotlinconf.Nomineeorg.jetbrains.kotlinconf.screens.GoldenKodeeScreenKt→org.jetbrains.kotlinconf.NomineeIdorg.jetbrains.kotlinconf.screens.GoldenKodeeViewModel→org.jetbrains.kotlinconf.AwardCategoryorg.jetbrains.kotlinconf.screens.GoldenKodeeViewModel→org.jetbrains.kotlinconf.ConferenceServiceorg.jetbrains.kotlinconf.screens.InfoViewModel→org.jetbrains.kotlinconf.ConferenceImagesorg.jetbrains.kotlinconf.screens.InfoViewModel→org.jetbrains.kotlinconf.ConferenceServiceorg.jetbrains.kotlinconf.screens.MapContent→org.jetbrains.kotlinconf.MapData
- Direction
- screens uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break screens, while a change to screens can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: screens uses a module listed above it, which is the healthy direction.
35→29 screens uses navigation✕
- Connections
- 1 pair of types, where a type in screens uses a type in navigation.
- The types involved
org.jetbrains.kotlinconf.screens.ScheduleScreenKt→org.jetbrains.kotlinconf.navigation.TopLevelRoute
- Direction
- screens uses navigation, so a change to navigation can break screens, while a change to screens can't break navigation.
- Position
- Below the diagonal: screens uses a module listed above it, which is the healthy direction.
36→17 screens.FeedbackViewModel uses org.jetbrains.kotlinconf✕
- Connections
- 1 pair of types, where a type in screens.FeedbackViewModel uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.screens.FeedbackViewModel.Factory→org.jetbrains.kotlinconf.SessionId
- Direction
- screens.FeedbackViewModel uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break screens.FeedbackViewModel, while a change to screens.FeedbackViewModel can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: screens.FeedbackViewModel uses a module listed above it, which is the healthy direction.
36→35 screens.FeedbackViewModel uses screens✕
- Connections
- 1 pair of types, where a type in screens.FeedbackViewModel uses a type in screens.
- The types involved
org.jetbrains.kotlinconf.screens.FeedbackViewModel.Factory→org.jetbrains.kotlinconf.screens.FeedbackViewModel
- Direction
- screens.FeedbackViewModel uses screens, so a change to screens can break screens.FeedbackViewModel, while a change to screens.FeedbackViewModel can't break screens.
- Position
- Below the diagonal: screens.FeedbackViewModel uses a module listed above it, which is the healthy direction.
37→17 screens.GoldenKodeeFinalistViewModel uses org.jetbrains.kotlinconf✕
- Connections
- 2 pairs of types, where a type in screens.GoldenKodeeFinalistViewModel uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.screens.GoldenKodeeFinalistViewModel.Factory→org.jetbrains.kotlinconf.AwardCategoryIdorg.jetbrains.kotlinconf.screens.GoldenKodeeFinalistViewModel.Factory→org.jetbrains.kotlinconf.NomineeId
- Direction
- screens.GoldenKodeeFinalistViewModel uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break screens.GoldenKodeeFinalistViewModel, while a change to screens.GoldenKodeeFinalistViewModel can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: screens.GoldenKodeeFinalistViewModel uses a module listed above it, which is the healthy direction.
37→35 screens.GoldenKodeeFinalistViewModel uses screens✕
- Connections
- 1 pair of types, where a type in screens.GoldenKodeeFinalistViewModel uses a type in screens.
- The types involved
org.jetbrains.kotlinconf.screens.GoldenKodeeFinalistViewModel.Factory→org.jetbrains.kotlinconf.screens.GoldenKodeeFinalistViewModel
- Direction
- screens.GoldenKodeeFinalistViewModel uses screens, so a change to screens can break screens.GoldenKodeeFinalistViewModel, while a change to screens.GoldenKodeeFinalistViewModel can't break screens.
- Position
- Below the diagonal: screens.GoldenKodeeFinalistViewModel uses a module listed above it, which is the healthy direction.
38→17 screens.PartnerDetailViewModel uses org.jetbrains.kotlinconf✕
- Connections
- 1 pair of types, where a type in screens.PartnerDetailViewModel uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.screens.PartnerDetailViewModel.Factory→org.jetbrains.kotlinconf.PartnerId
- Direction
- screens.PartnerDetailViewModel uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break screens.PartnerDetailViewModel, while a change to screens.PartnerDetailViewModel can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: screens.PartnerDetailViewModel uses a module listed above it, which is the healthy direction.
38→35 screens.PartnerDetailViewModel uses screens✕
- Connections
- 1 pair of types, where a type in screens.PartnerDetailViewModel uses a type in screens.
- The types involved
org.jetbrains.kotlinconf.screens.PartnerDetailViewModel.Factory→org.jetbrains.kotlinconf.screens.PartnerDetailViewModel
- Direction
- screens.PartnerDetailViewModel uses screens, so a change to screens can break screens.PartnerDetailViewModel, while a change to screens.PartnerDetailViewModel can't break screens.
- Position
- Below the diagonal: screens.PartnerDetailViewModel uses a module listed above it, which is the healthy direction.
39→17 screens.SessionViewModel uses org.jetbrains.kotlinconf✕
- Connections
- 1 pair of types, where a type in screens.SessionViewModel uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.screens.SessionViewModel.Factory→org.jetbrains.kotlinconf.SessionId
- Direction
- screens.SessionViewModel uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break screens.SessionViewModel, while a change to screens.SessionViewModel can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: screens.SessionViewModel uses a module listed above it, which is the healthy direction.
39→35 screens.SessionViewModel uses screens✕
- Connections
- 1 pair of types, where a type in screens.SessionViewModel uses a type in screens.
- The types involved
org.jetbrains.kotlinconf.screens.SessionViewModel.Factory→org.jetbrains.kotlinconf.screens.SessionViewModel
- Direction
- screens.SessionViewModel uses screens, so a change to screens can break screens.SessionViewModel, while a change to screens.SessionViewModel can't break screens.
- Position
- Below the diagonal: screens.SessionViewModel uses a module listed above it, which is the healthy direction.
40→17 screens.SpeakerDetailViewModel uses org.jetbrains.kotlinconf✕
- Connections
- 1 pair of types, where a type in screens.SpeakerDetailViewModel uses a type in org.jetbrains.kotlinconf.
- The types involved
org.jetbrains.kotlinconf.screens.SpeakerDetailViewModel.Factory→org.jetbrains.kotlinconf.SpeakerId
- Direction
- screens.SpeakerDetailViewModel uses org.jetbrains.kotlinconf, so a change to org.jetbrains.kotlinconf can break screens.SpeakerDetailViewModel, while a change to screens.SpeakerDetailViewModel can't break org.jetbrains.kotlinconf.
- Position
- Below the diagonal: screens.SpeakerDetailViewModel uses a module listed above it, which is the healthy direction.
40→35 screens.SpeakerDetailViewModel uses screens✕
- Connections
- 1 pair of types, where a type in screens.SpeakerDetailViewModel uses a type in screens.
- The types involved
org.jetbrains.kotlinconf.screens.SpeakerDetailViewModel.Factory→org.jetbrains.kotlinconf.screens.SpeakerDetailViewModel
- Direction
- screens.SpeakerDetailViewModel uses screens, so a change to screens can break screens.SpeakerDetailViewModel, while a change to screens.SpeakerDetailViewModel can't break screens.
- Position
- Below the diagonal: screens.SpeakerDetailViewModel 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 | 16 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 14 | High / Critical |
Roadmap
First, ensure all custom controls are fully keyboard-operable and anchors have valid hrefs to fix immediate interaction barriers. Next, enforce accessibility standards by integrating automated checks into your UI test suite and gating merges in CI to prevent regressions. Simultaneously, address visual and motion safety by maintaining visible focus styles, respecting reduced-motion preferences, and improving color contrast. Finally, correct page structure by adding essential landmarks and language attributes, and resolve the missing architectural decision records to improve documentation quality.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +8.3 pts | Medium | Keyboard semantics |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.0 pts | Low | ADR Quality |
| Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge. | +3.9 pts | Medium | A11y enforcement |
| 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. | +2.4 pts | Medium | Visual & motion safety |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +2.3 pts | Medium | Page structure |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +1.1 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.1 pts | Low | Bus Factor |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +1.8 pts | Medium | Forms & labels |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/screens/ScheduleViewModel.kt | 6.3 | Mixed | Cyclomatic Complexity: ScheduleViewModel.buildNonSearchItems (cyclomatic 19) |
| app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/screens/ScheduleScreen.kt | 7.8 | Mixed | Cognitive Complexity: ScheduleScreenKt.ScheduleScreen (cognitive 16) |
| app/ui-components/src/commonMain/kotlin/org/jetbrains/kotlinconf/ui/components/TalkCard.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| app/shared/src/webMain/kotlin/org/jetbrains/kotlinconf/navigation/BrowserIntegration.web.kt | 8.5 | Near-clean | Cyclomatic Complexity: webKt.BrowserIntegration (cyclomatic 31) |
| backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/GoldenKodeeService.kt | 8.5 | Near-clean | Cognitive Complexity: GoldenKodeeService.validateGoldenKodeeData (cognitive 25) |
| backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt | 8.5 | Near-clean | Cognitive Complexity: ConferenceInfoService.validatePartnerData (cognitive 20) |
| app/adminApp/src/jsMain/kotlin/org/jetbrains/kotlinconf/admin/OverviewScreen.kt | 8.5 | Near-clean | Cognitive Complexity: OverviewScreenKt.OverviewScreen (cognitive 19) |
| app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/screens/DeveloperMenuScreen.kt | 8.5 | Near-clean | God Classes: MethodTooLong: DeveloperMenuScreenKt.DeveloperMenuScreen |
| app/ui-components/src/commonMain/kotlin/org/jetbrains/kotlinconf/ui/components/PartyAnimation.kt | 8.5 | Near-clean | God Classes: FileTooLong: components/PartyAnimation.kt |
| app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/screens/SpeakersScreen.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (32 lines × 2) |
| app/ui-components/src/commonMain/kotlin/org/jetbrains/kotlinconf/ui/components/MainNavigationBar.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (30–31 lines × 2) |
| app/ui-components/src/commonMain/kotlin/org/jetbrains/kotlinconf/ui/components/PageTitle.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (18 lines × 2) |
| app/ui-components/src/commonMain/kotlin/org/jetbrains/kotlinconf/ui/components/LargeSearchBar.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (15 lines × 2) |
| app/ui-components/src/commonMain/kotlin/org/jetbrains/kotlinconf/ui/components/MainHeader.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (14 lines × 2) |
| app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/network/ApplicationApi.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/storage/ApplicationStorageImpl.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 65 of 65 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 65 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, 98 of 114 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.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. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — a Gradle build resolved 1140 artifact(s) across its subprojects (419 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `app/shared/src/androidMain/kotlin/org/jetbrains/kotlinconf/AndroidLocalNotificationService.kt`, `app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/ConferenceService.kt`, `app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/TimeProvider.kt`, `app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/screens/DocumentsViewModel.kt`, `app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/screens/FeedbackViewModel.kt`, … (+11 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Koin and Metro, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 6 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Kotlin, Swift 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin, Swift 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These 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.
- X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 9 further occurrence(s) are not listed individually; the score already reflects all 49.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- 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.
- 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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was webKt.BrowserIntegration at 31. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being webKt.toBrowserHistoryFragment at 26 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/screens/ScheduleScreen.kt (ScheduleScreenKt.ScheduleList at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with webKt.BrowserIntegration (cyclomatic 31), ScheduleViewModel.buildNonSearchItems (cyclomatic 19). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
5 method(s) exceeded the cognitive complexity threshold of 15; the worst was GoldenKodeeService.validateGoldenKodeeData at 25.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cognitive Complexity — start with GoldenKodeeService.validateGoldenKodeeData (cognitive 25), ScheduleViewModel.buildNonSearchItems (cognitive 21), ConferenceInfoService.validatePartnerData (cognitive 20). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
3 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with DeveloperMenuScreen.kt, ScheduleScreen.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with PartyAnimation.kt. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
7 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (32 lines × 2) finding(s) in Code Duplication — start with SpeakersScreen.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (30–31 lines × 2) finding(s) in Code Duplication — start with MainNavigationBar.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 PageTitle.kt. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
9 production modules (Gradle), 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; 2 module(s) off the main sequence.
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
2 of 29 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with KotlinConfRepository.kt, ScheduleViewModel.kt. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 73 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 10 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. A further 3 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
61 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is app/ui-components/src/commonMain/kotlin/org/jetbrains/kotlinconf/ui/components/PartyAnimation.kt. Counted over 98 of the 261 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
1 deducted task-comment markers across 18831 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 1 TodoComment finding(s) in Explicit Debt — start with TalkCard.kt. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 9 build units (Gradle, Xcode) 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)
16 finding(s): 0 critical, 16 high, 0 medium, 0 low. 16 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `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
- No action in Static Analysis (SAST) — all 16 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 (16 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
7 finding(s): 0 critical, 5 high, 1 medium, 1 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 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
3 of 98 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/routes/VotingRoutes.kt. Counted over 98 of the 261 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: App.kt↔main.ios.kt 50%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with App.kt. — One of this dimension's main actionable groups (1 warning-level).
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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 5 platform declaration(s) and 76 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — app/adminApp/src/jsMain/kotlin/org/jetbrains/kotlinconf/admin/OverviewScreen.kt:53
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/adminApp/src/jsMain/resources/index.html:4
- 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="ComposeApp">, so there is no content here to wrap — render the <main> from the component mounted into it. — app/webApp/src/webMain/resources/index.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
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/adminApp/src/jsMain/kotlin/org/jetbrains/kotlinconf/admin/OverviewScreen.kt:90, app/adminApp/src/jsMain/kotlin/org/jetbrains/kotlinconf/admin/OverviewScreen.kt:112
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
- `.chart-bar` moves (`transition: height .15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/adminApp/src/jsMain/resources/index.html:112
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 6 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 8 of 8 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
- Only 2/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `app/adminApp`, `app/desktopApp`, `app/iosApp`, `app/webApp`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) so requests are traceable across the system, not just health-probable.
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 4281 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P8 · Schema migrations
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 13 use(s) across 20,839 production line(s) (~0.6/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
- Kotlin: on hot paths, use primitive arrays (IntArray, LongArray …) and @JvmInline value classes instead of boxed values, primitive collections (androidx.collection, fastutil) instead of boxed ones, and presize collections and StringBuilders.
- Swift: on hot paths, reserveCapacity before appending, use ContiguousArray for class-element arrays, work in place with withUnsafeBufferPointer/withUnsafeTemporaryAllocation, and make large values ~Copyable with borrowing/consuming parameters.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/androidApp/src/main/kotlin/org/jetbrains/kotlinconf/android/MainActivity.kt:78
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `warn` at line 26 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ArchivedDataService.kt:26
- `info` at line 32 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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ArchivedDataService.kt:32
- `error` at line 34 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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ArchivedDataService.kt:34
- `warn` 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ArchivedDataService.kt:56
- `error` at line 63 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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ArchivedDataService.kt:63
- `warn` at line 28 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/AssetService.kt:28
- `warn` 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/AssetService.kt:33
- `warn` at line 47 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/AssetService.kt:47
- `error` at line 54 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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/AssetService.kt:54
- `error` at line 74 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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/AssetService.kt:74
- `error` at line 75 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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/AssetService.kt:75
- `info` at line 79 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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/AssetService.kt:79
- `warn` 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/AssetService.kt:81
- `warn` at line 34 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:34
- `error` at line 42 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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:42
- `warn` at line 78 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:78
- `info` at line 89 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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:89
- `warn` at line 91 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:91
- `warn` at line 110 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:110
- `warn` at line 125 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:125
- `warn` 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:129
- `warn` at line 137 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:137
- `warn` 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:143
- `warn` at line 163 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:163
- `warn` at line 169 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:169
- `warn` at line 187 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:187
- `warn` at line 191 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:191
- `warn` at line 195 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:195
- `warn` at line 200 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:200
- `warn` at line 204 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:204
- `warn` at line 208 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:208
- `warn` at line 32 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/GoldenKodeeService.kt:32
- `error` at line 40 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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/GoldenKodeeService.kt:40
- `warn` at line 50 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/GoldenKodeeService.kt:50
- `warn` at line 57 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/GoldenKodeeService.kt:57
- `warn` at line 61 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/GoldenKodeeService.kt:61
- `warn` at line 66 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/GoldenKodeeService.kt:66
- `warn` at line 70 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/GoldenKodeeService.kt:70
- `info` at line 77 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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/GoldenKodeeService.kt:77
- `warn` at line 79 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.warn("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. — backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/GoldenKodeeService.kt:79
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 |
|---|---|---|
| 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 |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 66% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 94% | Exemplary | Strongest area. |
| Maturity | 62% | Adequate — gated by D16, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 57% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 78% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 37% | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 79% | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 51 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~979 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 — a Gradle build resolved 1140 artifact(s) across its subprojects (419 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Kotlin, Swift, html not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .kt, .swift, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.kt), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 16 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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
- D9 Test Distribution — Test source is 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 its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 5 strongly-typed id(s); 59 value object(s)
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Swift source, so there is no service whose uptime a failing dependency could take down
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- 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.
- 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 — 24 finding(s)
- REDACTED
- 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/adminApp/src/jsMain/kotlin/org/jetbrains/kotlinconf/admin/OverviewScreen.kt:53
- Click handler on a non-interactive <th> app/adminApp/src/jsMain/kotlin/org/jetbrains/kotlinconf/admin/OverviewScreen.kt:90
- Click handler on a non-interactive <tr> app/adminApp/src/jsMain/kotlin/org/jetbrains/kotlinconf/admin/OverviewScreen.kt:112
- REDACTED
Serious — 32 finding(s)
- Page without a main landmark app/adminApp/src/jsMain/resources/index.html:4
- Page without a main landmark app/webApp/src/webMain/resources/index.html:2
- MethodTooLong: DeveloperMenuScreenKt.DeveloperMenuScreen app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/screens/DeveloperMenuScreen.kt:57
- MethodTooLong: ScheduleScreenKt.ScheduleScreen app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/screens/ScheduleScreen.kt:88
- Off the main sequence: :core
- Off the main sequence: :app:ui-components
- Low cohesion: KotlinConfRepository (LCOM4 10) backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/repositories/KotlinConfRepository.kt:30
- Low cohesion: ScheduleViewModel (LCOM4 5) app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/screens/ScheduleViewModel.kt:77
- Animation without a prefers-reduced-motion guard app/adminApp/src/jsMain/resources/index.html:112
- Accessibility enforcement below the top rung
- webKt.BrowserIntegration (cyclomatic 31) app/shared/src/webMain/kotlin/org/jetbrains/kotlinconf/navigation/BrowserIntegration.web.kt:84
- ScheduleViewModel.buildNonSearchItems (cyclomatic 19) app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/screens/ScheduleViewModel.kt:217
- TodoComment app/ui-components/src/commonMain/kotlin/org/jetbrains/kotlinconf/ui/components/TalkCard.kt:155
- GoldenKodeeService.validateGoldenKodeeData (cognitive 25) backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/GoldenKodeeService.kt:45
- ScheduleViewModel.buildNonSearchItems (cognitive 21) app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/screens/ScheduleViewModel.kt:217
- ConferenceInfoService.validatePartnerData (cognitive 20) backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:117
- OverviewScreenKt.OverviewScreen (cognitive 19) app/adminApp/src/jsMain/kotlin/org/jetbrains/kotlinconf/admin/OverviewScreen.kt:33
- ScheduleScreenKt.ScheduleScreen (cognitive 16) app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/screens/ScheduleScreen.kt:88
- FileTooLong: components/PartyAnimation.kt app/ui-components/src/commonMain/kotlin/org/jetbrains/kotlinconf/ui/components/PartyAnimation.kt
- REDACTED
- Change coupling: App.kt ↔ main.ios.kt app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/App.kt:1
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (32 lines × 2) app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/screens/SpeakersScreen.kt:87
- Duplicated block (30–31 lines × 2) app/ui-components/src/commonMain/kotlin/org/jetbrains/kotlinconf/ui/components/MainNavigationBar.kt:115
- Duplicated block (18 lines × 2) app/ui-components/src/commonMain/kotlin/org/jetbrains/kotlinconf/ui/components/PageTitle.kt:198
- Duplicated block (15 lines × 2) app/ui-components/src/commonMain/kotlin/org/jetbrains/kotlinconf/ui/components/LargeSearchBar.kt:103
- Duplicated block (14 lines × 2) app/ui-components/src/commonMain/kotlin/org/jetbrains/kotlinconf/ui/components/MainHeader.kt:195
- Duplicated block (10 lines × 2) app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/network/ApplicationApi.kt:46
- Duplicated block (8 lines × 2) app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/storage/ApplicationStorageImpl.kt:42
- Swallowed exception (caught, then discarded) app/androidApp/src/main/kotlin/org/jetbrains/kotlinconf/android/MainActivity.kt:78
Minor — 58 finding(s)
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ArchivedDataService.kt:26
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ArchivedDataService.kt:32
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ArchivedDataService.kt:34
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ArchivedDataService.kt:56
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ArchivedDataService.kt:63
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/AssetService.kt:28
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/AssetService.kt:33
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/AssetService.kt:47
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/AssetService.kt:54
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/AssetService.kt:74
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/AssetService.kt:75
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/AssetService.kt:79
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/AssetService.kt:81
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:34
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:42
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:78
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:89
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:91
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:110
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:125
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:129
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:137
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:143
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:163
- Interpolated log message defeats structured logging backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/services/ConferenceInfoService.kt:169
- Orphaned file backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/routes/VotingRoutes.kt:1
- Orphaned file app/adminApp/src/jsMain/kotlin/org/jetbrains/kotlinconf/admin/UserScreen.kt:1
- Orphaned file backend/src/main/kotlin/org/jetbrains/kotlinconf/backend/PluginsModule.kt:1
- Duplicated predicate app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/navigation/NavHost.kt:189
- Duplicated predicate app/ui-components/src/commonMain/kotlin/org/jetbrains/kotlinconf/ui/components/LargeSearchBar.kt:106
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No SAST
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-61d797e8949144e8ad434a86e2b9c966/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-61d797e8949144e8ad434a86e2b9c966/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude kotlin-js-store . | 16 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 7 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 16 file(s) — `app/shared/src/androidMain/kotlin/org/jetbrains/kotlinconf/AndroidLocalNotificationService.kt`, `app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/ConferenceService.kt`, `app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/TimeProvider.kt`, `app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/screens/DocumentsViewModel.kt`, `app/shared/src/commonMain/kotlin/org/jetbrains/kotlinconf/screens/FeedbackViewModel.kt`, … (+11 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |