Executive summary
davidtakac/prognoza falls short of our standard for production because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 52 out of 100 and is rated Adequate, and all seven of its critical findings are security problems in the build pipeline.
Production Readiness, at 36, is the weakest lens and counts most in the score. The best first step for the work it takes is improving the documentation, worth about 7 points. Adding a diagnostic log would lift Production Readiness itself, worth about 8 points. Raising Production Readiness to 70 would lift the score to about 64.
Four secrets can leak from the build pipeline. Three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Limiting each secret to its own step and pinning each tool to an exact version would close both risks.
The product code is 9,381 lines, about €9,900 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Production Readiness rose from 36 to 70, the lowest score rated Strong, the score would rise from 52 to about 64.
Rebuild cost: about €9,900 · Estimate
| Cost to rebuild | €3,300 to €16,000, for 55 to 173 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 52. 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: 9,381 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 androidsettings | 2 presentation | 3 shared.entity | 4 androidsettings.MoodMode | 5 androidsettings.UiMode | 6 presentation.TextResource | 7 shared | 8 shared.data.metnorway.network | 9 shared.data.openmeteo.network | 10 shared.domain.data | 11 shared.entity.AngleUnit | 12 shared.entity.BeaufortScale | 13 shared.entity.CompassDirection | 14 shared.entity.Description | 15 shared.entity.ForecastProvider | 16 ui.theme | 17 shared.data.metnorway | 18 shared.data.openmeteo | 19 shared.data.openstreetmap | 20 shared.data.prognoza | 21 shared.domain.data.ForecastProviderResult | 22 shared.domain.data.ForecastRepositoryResult | 23 shared.domain.data.PlaceSearcherResult | 24 shared.platform | 25 shared.domain | 26 di | 27 presentation.settingsscreen | 28 shared.domain.GetForecastResult | 29 shared.domain.SearchPlacesResult | 30 widget | 31 widget.ForecastWidgetWorker | 32 di.work | 33 presentation.forecast | 34 presentation.places | 35 shared.domain.GetForecastResult.Empty | 36 shared.domain.SearchPlacesResult.Empty | 37 widget.ForecastWidgetState | 38 hr.dtakac.prognoza | 39 ui.forecast | 40 ui.places |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 androidsettings | ||||||||||||||||||||||||||||||||||||||||
| 2 presentation | ||||||||||||||||||||||||||||||||||||||||
| 3 shared.entity | ||||||||||||||||||||||||||||||||||||||||
| 4 androidsettings.MoodMode | 2 | |||||||||||||||||||||||||||||||||||||||
| 5 androidsettings.UiMode | 3 | |||||||||||||||||||||||||||||||||||||||
| 6 presentation.TextResource | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 shared | 21 | |||||||||||||||||||||||||||||||||||||||
| 8 shared.data.metnorway.network | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 shared.data.openmeteo.network | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 shared.domain.data | 10 | |||||||||||||||||||||||||||||||||||||||
| 11 shared.entity.AngleUnit | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 shared.entity.BeaufortScale | 14 | |||||||||||||||||||||||||||||||||||||||
| 13 shared.entity.CompassDirection | 9 | |||||||||||||||||||||||||||||||||||||||
| 14 shared.entity.Description | 84 | |||||||||||||||||||||||||||||||||||||||
| 15 shared.entity.ForecastProvider | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 ui.theme | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 shared.data.metnorway | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 18 shared.data.openmeteo | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 shared.data.openstreetmap | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 20 shared.data.prognoza | 8 | 8 | ||||||||||||||||||||||||||||||||||||||
| 21 shared.domain.data.ForecastProviderResult | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 22 shared.domain.data.ForecastRepositoryResult | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 23 shared.domain.data.PlaceSearcherResult | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 24 shared.platform | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 shared.domain | 22 | 17 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 di | 1 | 21 | ||||||||||||||||||||||||||||||||||||||
| 27 presentation.settingsscreen | 5 | 3 | 10 | 15 | ||||||||||||||||||||||||||||||||||||
| 28 shared.domain.GetForecastResult | 5 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 shared.domain.SearchPlacesResult | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 widget | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 widget.ForecastWidgetWorker | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 di.work | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 presentation.forecast | 9 | 17 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 34 presentation.places | 5 | 2 | 5 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 shared.domain.GetForecastResult.Empty | 2 | |||||||||||||||||||||||||||||||||||||||
| 36 shared.domain.SearchPlacesResult.Empty | 2 | |||||||||||||||||||||||||||||||||||||||
| 37 widget.ForecastWidgetState | 3 | 5 | ||||||||||||||||||||||||||||||||||||||
| 38 hr.dtakac.prognoza | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 ui.forecast | 9 | |||||||||||||||||||||||||||||||||||||||
| 40 ui.places | 1 | 3 |
4→1 androidsettings.MoodMode uses androidsettings✕
- Connections
- 2 pairs of types, where a type in androidsettings.MoodMode uses a type in androidsettings.
- The types involved
hr.dtakac.prognoza.androidsettings.MoodMode.DYNAMIC→hr.dtakac.prognoza.androidsettings.MoodModehr.dtakac.prognoza.androidsettings.MoodMode.FORECAST→hr.dtakac.prognoza.androidsettings.MoodMode
- Direction
- androidsettings.MoodMode uses androidsettings, so a change to androidsettings can break androidsettings.MoodMode, while a change to androidsettings.MoodMode can't break androidsettings.
- Position
- Below the diagonal: androidsettings.MoodMode uses a module listed above it, which is the healthy direction.
5→1 androidsettings.UiMode uses androidsettings✕
- Connections
- 3 pairs of types, where a type in androidsettings.UiMode uses a type in androidsettings.
- The types involved
hr.dtakac.prognoza.androidsettings.UiMode.DARK→hr.dtakac.prognoza.androidsettings.UiModehr.dtakac.prognoza.androidsettings.UiMode.FOLLOW_SYSTEM→hr.dtakac.prognoza.androidsettings.UiModehr.dtakac.prognoza.androidsettings.UiMode.LIGHT→hr.dtakac.prognoza.androidsettings.UiMode
- Direction
- androidsettings.UiMode uses androidsettings, so a change to androidsettings can break androidsettings.UiMode, while a change to androidsettings.UiMode can't break androidsettings.
- Position
- Below the diagonal: androidsettings.UiMode uses a module listed above it, which is the healthy direction.
6→2 presentation.TextResource uses presentation✕
- Connections
- 1 pair of types, where a type in presentation.TextResource uses a type in presentation.
- The types involved
hr.dtakac.prognoza.presentation.TextResource.Companion→hr.dtakac.prognoza.presentation.TextResource
- Direction
- presentation.TextResource uses presentation, so a change to presentation can break presentation.TextResource, while a change to presentation.TextResource can't break presentation.
- Position
- Below the diagonal: presentation.TextResource uses a module listed above it, which is the healthy direction.
7→25 shared uses shared.domain part of a loop✕
- Connections
- 21 pairs of types, where a type in shared uses a type in shared.domain.
- The types involved
hr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.DeleteSavedPlacehr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.GetAllForecastProvidershr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.GetAllPrecipitationUnitshr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.GetAllPressureUnitshr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.GetAllTemperatureUnitshr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.GetAllWindUnitshr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.GetForecasthr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.GetForecastProviderhr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.GetPrecipitationUnithr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.GetPressureUnithr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.GetSavedPlaceshr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.GetSelectedPlacehr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.GetTemperatureUnithr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.GetWindUnithr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.SearchPlaceshr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.SelectPlacehr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.SetForecastProviderhr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.SetPrecipitationUnithr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.SetPressureUnithr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.SetTemperatureUnithr.dtakac.prognoza.shared.PrognozaSdk→hr.dtakac.prognoza.shared.domain.SetWindUnit
- Direction
- shared uses shared.domain, so a change to shared.domain can break shared, while a change to shared can't break shared.domain.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→3 shared.data.metnorway.network uses shared.entity✕
- Connections
- 2 pairs of types, where a type in shared.data.metnorway.network uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.shared.data.metnorway.network.LocationForecastResponseKt→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.data.metnorway.network.LocationForecastResponseKt→hr.dtakac.prognoza.shared.entity.ForecastDatum
- Direction
- shared.data.metnorway.network uses shared.entity, so a change to shared.entity can break shared.data.metnorway.network, while a change to shared.data.metnorway.network can't break shared.entity.
- Position
- Below the diagonal: shared.data.metnorway.network uses a module listed above it, which is the healthy direction.
8→24 shared.data.metnorway.network uses shared.platform part of a loop✕
- Connections
- 1 pair of types, where a type in shared.data.metnorway.network uses a type in shared.platform.
- The types involved
hr.dtakac.prognoza.shared.data.metnorway.network.MetNorwayForecastService→hr.dtakac.prognoza.shared.platform.DotDecimalFormatter
- Direction
- shared.data.metnorway.network uses shared.platform, so a change to shared.platform can break shared.data.metnorway.network, while a change to shared.data.metnorway.network can't break shared.platform.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→3 shared.data.openmeteo.network uses shared.entity✕
- Connections
- 2 pairs of types, where a type in shared.data.openmeteo.network uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.shared.data.openmeteo.network.OpenMeteoResponseKt→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.data.openmeteo.network.OpenMeteoResponseKt→hr.dtakac.prognoza.shared.entity.ForecastDatum
- Direction
- shared.data.openmeteo.network uses shared.entity, so a change to shared.entity can break shared.data.openmeteo.network, while a change to shared.data.openmeteo.network can't break shared.entity.
- Position
- Below the diagonal: shared.data.openmeteo.network uses a module listed above it, which is the healthy direction.
9→24 shared.data.openmeteo.network uses shared.platform part of a loop✕
- Connections
- 1 pair of types, where a type in shared.data.openmeteo.network uses a type in shared.platform.
- The types involved
hr.dtakac.prognoza.shared.data.openmeteo.network.OpenMeteoForecastService→hr.dtakac.prognoza.shared.platform.DotDecimalFormatter
- Direction
- shared.data.openmeteo.network uses shared.platform, so a change to shared.platform can break shared.data.openmeteo.network, while a change to shared.data.openmeteo.network can't break shared.platform.
- 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→3 shared.domain.data uses shared.entity✕
- Connections
- 10 pairs of types, where a type in shared.domain.data uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.shared.domain.data.ForecastRepository→hr.dtakac.prognoza.shared.entity.ForecastProviderhr.dtakac.prognoza.shared.domain.data.PlaceSaver→hr.dtakac.prognoza.shared.entity.Placehr.dtakac.prognoza.shared.domain.data.SavedPlaceGetter→hr.dtakac.prognoza.shared.entity.Placehr.dtakac.prognoza.shared.domain.data.SavedPlaceRemover→hr.dtakac.prognoza.shared.entity.Placehr.dtakac.prognoza.shared.domain.data.SettingsRepository→hr.dtakac.prognoza.shared.entity.ForecastProviderhr.dtakac.prognoza.shared.domain.data.SettingsRepository→hr.dtakac.prognoza.shared.entity.LengthUnithr.dtakac.prognoza.shared.domain.data.SettingsRepository→hr.dtakac.prognoza.shared.entity.Placehr.dtakac.prognoza.shared.domain.data.SettingsRepository→hr.dtakac.prognoza.shared.entity.PressureUnithr.dtakac.prognoza.shared.domain.data.SettingsRepository→hr.dtakac.prognoza.shared.entity.SpeedUnithr.dtakac.prognoza.shared.domain.data.SettingsRepository→hr.dtakac.prognoza.shared.entity.TemperatureUnit
- Direction
- shared.domain.data uses shared.entity, so a change to shared.entity can break shared.domain.data, while a change to shared.domain.data can't break shared.entity.
- Position
- Below the diagonal: shared.domain.data uses a module listed above it, which is the healthy direction.
11→3 shared.entity.AngleUnit uses shared.entity✕
- Connections
- 2 pairs of types, where a type in shared.entity.AngleUnit uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.shared.entity.AngleUnit.DEGREE→hr.dtakac.prognoza.shared.entity.AngleUnithr.dtakac.prognoza.shared.entity.AngleUnit.RADIAN→hr.dtakac.prognoza.shared.entity.AngleUnit
- Direction
- shared.entity.AngleUnit uses shared.entity, so a change to shared.entity can break shared.entity.AngleUnit, while a change to shared.entity.AngleUnit can't break shared.entity.
- Position
- Below the diagonal: shared.entity.AngleUnit uses a module listed above it, which is the healthy direction.
12→3 shared.entity.BeaufortScale uses shared.entity✕
- Connections
- 14 pairs of types, where a type in shared.entity.BeaufortScale uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.shared.entity.BeaufortScale.CALM→hr.dtakac.prognoza.shared.entity.BeaufortScalehr.dtakac.prognoza.shared.entity.BeaufortScale.Companion→hr.dtakac.prognoza.shared.entity.BeaufortScalehr.dtakac.prognoza.shared.entity.BeaufortScale.FRESH_BREEZE→hr.dtakac.prognoza.shared.entity.BeaufortScalehr.dtakac.prognoza.shared.entity.BeaufortScale.GALE→hr.dtakac.prognoza.shared.entity.BeaufortScalehr.dtakac.prognoza.shared.entity.BeaufortScale.GENTLE_BREEZE→hr.dtakac.prognoza.shared.entity.BeaufortScalehr.dtakac.prognoza.shared.entity.BeaufortScale.HURRICANE→hr.dtakac.prognoza.shared.entity.BeaufortScalehr.dtakac.prognoza.shared.entity.BeaufortScale.LIGHT_AIR→hr.dtakac.prognoza.shared.entity.BeaufortScalehr.dtakac.prognoza.shared.entity.BeaufortScale.LIGHT_BREEZE→hr.dtakac.prognoza.shared.entity.BeaufortScalehr.dtakac.prognoza.shared.entity.BeaufortScale.MODERATE_BREEZE→hr.dtakac.prognoza.shared.entity.BeaufortScalehr.dtakac.prognoza.shared.entity.BeaufortScale.NEAR_GALE→hr.dtakac.prognoza.shared.entity.BeaufortScalehr.dtakac.prognoza.shared.entity.BeaufortScale.SEVERE_GALE→hr.dtakac.prognoza.shared.entity.BeaufortScalehr.dtakac.prognoza.shared.entity.BeaufortScale.STORM→hr.dtakac.prognoza.shared.entity.BeaufortScalehr.dtakac.prognoza.shared.entity.BeaufortScale.STRONG_BREEZE→hr.dtakac.prognoza.shared.entity.BeaufortScalehr.dtakac.prognoza.shared.entity.BeaufortScale.VIOLENT_STORM→hr.dtakac.prognoza.shared.entity.BeaufortScale
- Direction
- shared.entity.BeaufortScale uses shared.entity, so a change to shared.entity can break shared.entity.BeaufortScale, while a change to shared.entity.BeaufortScale can't break shared.entity.
- Position
- Below the diagonal: shared.entity.BeaufortScale uses a module listed above it, which is the healthy direction.
13→3 shared.entity.CompassDirection uses shared.entity✕
- Connections
- 9 pairs of types, where a type in shared.entity.CompassDirection uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.shared.entity.CompassDirection.Companion→hr.dtakac.prognoza.shared.entity.CompassDirectionhr.dtakac.prognoza.shared.entity.CompassDirection.E→hr.dtakac.prognoza.shared.entity.CompassDirectionhr.dtakac.prognoza.shared.entity.CompassDirection.N→hr.dtakac.prognoza.shared.entity.CompassDirectionhr.dtakac.prognoza.shared.entity.CompassDirection.NE→hr.dtakac.prognoza.shared.entity.CompassDirectionhr.dtakac.prognoza.shared.entity.CompassDirection.NW→hr.dtakac.prognoza.shared.entity.CompassDirectionhr.dtakac.prognoza.shared.entity.CompassDirection.S→hr.dtakac.prognoza.shared.entity.CompassDirectionhr.dtakac.prognoza.shared.entity.CompassDirection.SE→hr.dtakac.prognoza.shared.entity.CompassDirectionhr.dtakac.prognoza.shared.entity.CompassDirection.SW→hr.dtakac.prognoza.shared.entity.CompassDirectionhr.dtakac.prognoza.shared.entity.CompassDirection.W→hr.dtakac.prognoza.shared.entity.CompassDirection
- Direction
- shared.entity.CompassDirection uses shared.entity, so a change to shared.entity can break shared.entity.CompassDirection, while a change to shared.entity.CompassDirection can't break shared.entity.
- Position
- Below the diagonal: shared.entity.CompassDirection uses a module listed above it, which is the healthy direction.
14→3 shared.entity.Description uses shared.entity✕
- Connections
- 84 pairs of types, where a type in shared.entity.Description uses a type in shared.entity. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
hr.dtakac.prognoza.shared.entity.Description.CLEAR_SKY_DAY→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.CLEAR_SKY_NIGHT→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.CLEAR_SKY_POLAR_TWILIGHT→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.CLOUDY→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.FAIR_DAY→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.FAIR_NIGHT→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.FAIR_POLAR_TWILIGHT→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.FOG→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_RAIN→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_RAIN_AND_THUNDER→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_RAIN_SHOWERS_AND_THUNDER_DAY→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_RAIN_SHOWERS_AND_THUNDER_NIGHT→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_RAIN_SHOWERS_AND_THUNDER_POLAR_TWILIGHT→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_RAIN_SHOWERS_DAY→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_RAIN_SHOWERS_NIGHT→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_RAIN_SHOWERS_POLAR_TWILIGHT→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_SLEET→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_SLEET_AND_THUNDER→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_SLEET_SHOWERS_AND_THUNDER_DAY→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_SLEET_SHOWERS_AND_THUNDER_NIGHT→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_SLEET_SHOWERS_AND_THUNDER_POLAR_TWILIGHT→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_SLEET_SHOWERS_DAY→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_SLEET_SHOWERS_NIGHT→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_SLEET_SHOWERS_POLAR_TWILIGHT→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.shared.entity.Description.HEAVY_SNOW→hr.dtakac.prognoza.shared.entity.Description
- Direction
- shared.entity.Description uses shared.entity, so a change to shared.entity can break shared.entity.Description, while a change to shared.entity.Description can't break shared.entity.
- Position
- Below the diagonal: shared.entity.Description uses a module listed above it, which is the healthy direction.
15→3 shared.entity.ForecastProvider uses shared.entity✕
- Connections
- 2 pairs of types, where a type in shared.entity.ForecastProvider uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.shared.entity.ForecastProvider.MET_NORWAY→hr.dtakac.prognoza.shared.entity.ForecastProviderhr.dtakac.prognoza.shared.entity.ForecastProvider.OPEN_METEO→hr.dtakac.prognoza.shared.entity.ForecastProvider
- Direction
- shared.entity.ForecastProvider uses shared.entity, so a change to shared.entity can break shared.entity.ForecastProvider, while a change to shared.entity.ForecastProvider can't break shared.entity.
- Position
- Below the diagonal: shared.entity.ForecastProvider uses a module listed above it, which is the healthy direction.
16→3 ui.theme uses shared.entity✕
- Connections
- 1 pair of types, where a type in ui.theme uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.ui.theme.ThemeKt→hr.dtakac.prognoza.shared.entity.Mood
- Direction
- ui.theme uses shared.entity, so a change to shared.entity can break ui.theme, while a change to ui.theme can't break shared.entity.
- Position
- Below the diagonal: ui.theme uses a module listed above it, which is the healthy direction.
17→8 shared.data.metnorway uses shared.data.metnorway.network✕
- Connections
- 2 pairs of types, where a type in shared.data.metnorway uses a type in shared.data.metnorway.network.
- The types involved
hr.dtakac.prognoza.shared.data.metnorway.MetNorwayForecastProvider→hr.dtakac.prognoza.shared.data.metnorway.network.LocationForecastResponsehr.dtakac.prognoza.shared.data.metnorway.MetNorwayForecastProvider→hr.dtakac.prognoza.shared.data.metnorway.network.MetNorwayForecastService
- Direction
- shared.data.metnorway uses shared.data.metnorway.network, so a change to shared.data.metnorway.network can break shared.data.metnorway, while a change to shared.data.metnorway can't break shared.data.metnorway.network.
- Position
- Below the diagonal: shared.data.metnorway uses a module listed above it, which is the healthy direction.
17→10 shared.data.metnorway uses shared.domain.data✕
- Connections
- 2 pairs of types, where a type in shared.data.metnorway uses a type in shared.domain.data.
- The types involved
hr.dtakac.prognoza.shared.data.metnorway.MetNorwayForecastProvider→hr.dtakac.prognoza.shared.domain.data.ForecastProviderhr.dtakac.prognoza.shared.data.metnorway.MetNorwayForecastProvider→hr.dtakac.prognoza.shared.domain.data.ForecastProviderResult
- Direction
- shared.data.metnorway uses shared.domain.data, so a change to shared.domain.data can break shared.data.metnorway, while a change to shared.data.metnorway can't break shared.domain.data.
- Position
- Below the diagonal: shared.data.metnorway uses a module listed above it, which is the healthy direction.
18→9 shared.data.openmeteo uses shared.data.openmeteo.network✕
- Connections
- 2 pairs of types, where a type in shared.data.openmeteo uses a type in shared.data.openmeteo.network.
- The types involved
hr.dtakac.prognoza.shared.data.openmeteo.OpenMeteoForecastProvider→hr.dtakac.prognoza.shared.data.openmeteo.network.OpenMeteoForecastServicehr.dtakac.prognoza.shared.data.openmeteo.OpenMeteoForecastProvider→hr.dtakac.prognoza.shared.data.openmeteo.network.OpenMeteoResponse
- Direction
- shared.data.openmeteo uses shared.data.openmeteo.network, so a change to shared.data.openmeteo.network can break shared.data.openmeteo, while a change to shared.data.openmeteo can't break shared.data.openmeteo.network.
- Position
- Below the diagonal: shared.data.openmeteo uses a module listed above it, which is the healthy direction.
18→10 shared.data.openmeteo uses shared.domain.data✕
- Connections
- 2 pairs of types, where a type in shared.data.openmeteo uses a type in shared.domain.data.
- The types involved
hr.dtakac.prognoza.shared.data.openmeteo.OpenMeteoForecastProvider→hr.dtakac.prognoza.shared.domain.data.ForecastProviderhr.dtakac.prognoza.shared.data.openmeteo.OpenMeteoForecastProvider→hr.dtakac.prognoza.shared.domain.data.ForecastProviderResult
- Direction
- shared.data.openmeteo uses shared.domain.data, so a change to shared.domain.data can break shared.data.openmeteo, while a change to shared.data.openmeteo can't break shared.domain.data.
- Position
- Below the diagonal: shared.data.openmeteo uses a module listed above it, which is the healthy direction.
19→3 shared.data.openstreetmap uses shared.entity✕
- Connections
- 1 pair of types, where a type in shared.data.openstreetmap uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.shared.data.openstreetmap.PlaceDataKt→hr.dtakac.prognoza.shared.entity.Place
- Direction
- shared.data.openstreetmap uses shared.entity, so a change to shared.entity can break shared.data.openstreetmap, while a change to shared.data.openstreetmap can't break shared.entity.
- Position
- Below the diagonal: shared.data.openstreetmap uses a module listed above it, which is the healthy direction.
19→10 shared.data.openstreetmap uses shared.domain.data✕
- Connections
- 2 pairs of types, where a type in shared.data.openstreetmap uses a type in shared.domain.data.
- The types involved
hr.dtakac.prognoza.shared.data.openstreetmap.OsmPlaceSearcher→hr.dtakac.prognoza.shared.domain.data.PlaceSearcherhr.dtakac.prognoza.shared.data.openstreetmap.OsmPlaceSearcher→hr.dtakac.prognoza.shared.domain.data.PlaceSearcherResult
- Direction
- shared.data.openstreetmap uses shared.domain.data, so a change to shared.domain.data can break shared.data.openstreetmap, while a change to shared.data.openstreetmap can't break shared.domain.data.
- Position
- Below the diagonal: shared.data.openstreetmap uses a module listed above it, which is the healthy direction.
20→3 shared.data.prognoza uses shared.entity✕
- Connections
- 8 pairs of types, where a type in shared.data.prognoza uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.shared.data.prognoza.DatabaseForecastRepository→hr.dtakac.prognoza.shared.entity.ForecastProviderhr.dtakac.prognoza.shared.data.prognoza.DatabasePlaceRepository→hr.dtakac.prognoza.shared.entity.Placehr.dtakac.prognoza.shared.data.prognoza.DatabaseSettingsRepository→hr.dtakac.prognoza.shared.entity.ForecastProviderhr.dtakac.prognoza.shared.data.prognoza.DatabaseSettingsRepository→hr.dtakac.prognoza.shared.entity.LengthUnithr.dtakac.prognoza.shared.data.prognoza.DatabaseSettingsRepository→hr.dtakac.prognoza.shared.entity.Placehr.dtakac.prognoza.shared.data.prognoza.DatabaseSettingsRepository→hr.dtakac.prognoza.shared.entity.PressureUnithr.dtakac.prognoza.shared.data.prognoza.DatabaseSettingsRepository→hr.dtakac.prognoza.shared.entity.SpeedUnithr.dtakac.prognoza.shared.data.prognoza.DatabaseSettingsRepository→hr.dtakac.prognoza.shared.entity.TemperatureUnit
- Direction
- shared.data.prognoza uses shared.entity, so a change to shared.entity can break shared.data.prognoza, while a change to shared.data.prognoza can't break shared.entity.
- Position
- Below the diagonal: shared.data.prognoza uses a module listed above it, which is the healthy direction.
20→10 shared.data.prognoza uses shared.domain.data✕
- Connections
- 8 pairs of types, where a type in shared.data.prognoza uses a type in shared.domain.data.
- The types involved
hr.dtakac.prognoza.shared.data.prognoza.DatabaseForecastRepository→hr.dtakac.prognoza.shared.domain.data.ForecastProviderhr.dtakac.prognoza.shared.data.prognoza.DatabaseForecastRepository→hr.dtakac.prognoza.shared.domain.data.ForecastRepositoryhr.dtakac.prognoza.shared.data.prognoza.DatabaseForecastRepository→hr.dtakac.prognoza.shared.domain.data.ForecastRepositoryResulthr.dtakac.prognoza.shared.data.prognoza.DatabasePlaceRepository→hr.dtakac.prognoza.shared.domain.data.PlaceSaverhr.dtakac.prognoza.shared.data.prognoza.DatabasePlaceRepository→hr.dtakac.prognoza.shared.domain.data.SavedPlaceGetterhr.dtakac.prognoza.shared.data.prognoza.DatabasePlaceRepository→hr.dtakac.prognoza.shared.domain.data.SavedPlaceRemoverhr.dtakac.prognoza.shared.data.prognoza.DatabaseSettingsRepository→hr.dtakac.prognoza.shared.domain.data.SavedPlaceGetterhr.dtakac.prognoza.shared.data.prognoza.DatabaseSettingsRepository→hr.dtakac.prognoza.shared.domain.data.SettingsRepository
- Direction
- shared.data.prognoza uses shared.domain.data, so a change to shared.domain.data can break shared.data.prognoza, while a change to shared.data.prognoza can't break shared.domain.data.
- Position
- Below the diagonal: shared.data.prognoza uses a module listed above it, which is the healthy direction.
21→3 shared.domain.data.ForecastProviderResult uses shared.entity✕
- Connections
- 1 pair of types, where a type in shared.domain.data.ForecastProviderResult uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.shared.domain.data.ForecastProviderResult.Success→hr.dtakac.prognoza.shared.entity.ForecastDatum
- Direction
- shared.domain.data.ForecastProviderResult uses shared.entity, so a change to shared.entity can break shared.domain.data.ForecastProviderResult, while a change to shared.domain.data.ForecastProviderResult can't break shared.entity.
- Position
- Below the diagonal: shared.domain.data.ForecastProviderResult uses a module listed above it, which is the healthy direction.
21→10 shared.domain.data.ForecastProviderResult uses shared.domain.data✕
- Connections
- 2 pairs of types, where a type in shared.domain.data.ForecastProviderResult uses a type in shared.domain.data.
- The types involved
hr.dtakac.prognoza.shared.domain.data.ForecastProviderResult.Error→hr.dtakac.prognoza.shared.domain.data.ForecastProviderResulthr.dtakac.prognoza.shared.domain.data.ForecastProviderResult.Success→hr.dtakac.prognoza.shared.domain.data.ForecastProviderResult
- Direction
- shared.domain.data.ForecastProviderResult uses shared.domain.data, so a change to shared.domain.data can break shared.domain.data.ForecastProviderResult, while a change to shared.domain.data.ForecastProviderResult can't break shared.domain.data.
- Position
- Below the diagonal: shared.domain.data.ForecastProviderResult uses a module listed above it, which is the healthy direction.
22→3 shared.domain.data.ForecastRepositoryResult uses shared.entity✕
- Connections
- 2 pairs of types, where a type in shared.domain.data.ForecastRepositoryResult uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.shared.domain.data.ForecastRepositoryResult.Success→hr.dtakac.prognoza.shared.entity.ForecastDatumhr.dtakac.prognoza.shared.domain.data.ForecastRepositoryResult.Success→hr.dtakac.prognoza.shared.entity.ForecastProvider
- Direction
- shared.domain.data.ForecastRepositoryResult uses shared.entity, so a change to shared.entity can break shared.domain.data.ForecastRepositoryResult, while a change to shared.domain.data.ForecastRepositoryResult can't break shared.entity.
- Position
- Below the diagonal: shared.domain.data.ForecastRepositoryResult uses a module listed above it, which is the healthy direction.
22→10 shared.domain.data.ForecastRepositoryResult uses shared.domain.data✕
- Connections
- 2 pairs of types, where a type in shared.domain.data.ForecastRepositoryResult uses a type in shared.domain.data.
- The types involved
hr.dtakac.prognoza.shared.domain.data.ForecastRepositoryResult.Empty→hr.dtakac.prognoza.shared.domain.data.ForecastRepositoryResulthr.dtakac.prognoza.shared.domain.data.ForecastRepositoryResult.Success→hr.dtakac.prognoza.shared.domain.data.ForecastRepositoryResult
- Direction
- shared.domain.data.ForecastRepositoryResult uses shared.domain.data, so a change to shared.domain.data can break shared.domain.data.ForecastRepositoryResult, while a change to shared.domain.data.ForecastRepositoryResult can't break shared.domain.data.
- Position
- Below the diagonal: shared.domain.data.ForecastRepositoryResult uses a module listed above it, which is the healthy direction.
23→3 shared.domain.data.PlaceSearcherResult uses shared.entity✕
- Connections
- 1 pair of types, where a type in shared.domain.data.PlaceSearcherResult uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.shared.domain.data.PlaceSearcherResult.Success→hr.dtakac.prognoza.shared.entity.Place
- Direction
- shared.domain.data.PlaceSearcherResult uses shared.entity, so a change to shared.entity can break shared.domain.data.PlaceSearcherResult, while a change to shared.domain.data.PlaceSearcherResult can't break shared.entity.
- Position
- Below the diagonal: shared.domain.data.PlaceSearcherResult uses a module listed above it, which is the healthy direction.
23→10 shared.domain.data.PlaceSearcherResult uses shared.domain.data✕
- Connections
- 2 pairs of types, where a type in shared.domain.data.PlaceSearcherResult uses a type in shared.domain.data.
- The types involved
hr.dtakac.prognoza.shared.domain.data.PlaceSearcherResult.Error→hr.dtakac.prognoza.shared.domain.data.PlaceSearcherResulthr.dtakac.prognoza.shared.domain.data.PlaceSearcherResult.Success→hr.dtakac.prognoza.shared.domain.data.PlaceSearcherResult
- Direction
- shared.domain.data.PlaceSearcherResult uses shared.domain.data, so a change to shared.domain.data can break shared.domain.data.PlaceSearcherResult, while a change to shared.domain.data.PlaceSearcherResult can't break shared.domain.data.
- Position
- Below the diagonal: shared.domain.data.PlaceSearcherResult uses a module listed above it, which is the healthy direction.
24→7 shared.platform uses shared✕
- Connections
- 2 pairs of types, where a type in shared.platform uses a type in shared.
- The types involved
hr.dtakac.prognoza.shared.platform.InternalPrognozaSdkFactory→hr.dtakac.prognoza.shared.PrognozaSdkhr.dtakac.prognoza.shared.platform.PrognozaSdkFactory→hr.dtakac.prognoza.shared.PrognozaSdk
- Direction
- shared.platform uses shared, so a change to shared can break shared.platform, while a change to shared.platform can't break shared.
- Position
- Below the diagonal: shared.platform uses a module listed above it, which is the healthy direction.
24→17 shared.platform uses shared.data.metnorway✕
- Connections
- 1 pair of types, where a type in shared.platform uses a type in shared.data.metnorway.
- The types involved
hr.dtakac.prognoza.shared.platform.InternalPrognozaSdkFactory→hr.dtakac.prognoza.shared.data.metnorway.MetNorwayForecastProvider
- Direction
- shared.platform uses shared.data.metnorway, so a change to shared.data.metnorway can break shared.platform, while a change to shared.platform can't break shared.data.metnorway.
- Position
- Below the diagonal: shared.platform uses a module listed above it, which is the healthy direction.
24→18 shared.platform uses shared.data.openmeteo✕
- Connections
- 1 pair of types, where a type in shared.platform uses a type in shared.data.openmeteo.
- The types involved
hr.dtakac.prognoza.shared.platform.InternalPrognozaSdkFactory→hr.dtakac.prognoza.shared.data.openmeteo.OpenMeteoForecastProvider
- Direction
- shared.platform uses shared.data.openmeteo, so a change to shared.data.openmeteo can break shared.platform, while a change to shared.platform can't break shared.data.openmeteo.
- Position
- Below the diagonal: shared.platform uses a module listed above it, which is the healthy direction.
24→19 shared.platform uses shared.data.openstreetmap✕
- Connections
- 1 pair of types, where a type in shared.platform uses a type in shared.data.openstreetmap.
- The types involved
hr.dtakac.prognoza.shared.platform.InternalPrognozaSdkFactory→hr.dtakac.prognoza.shared.data.openstreetmap.OsmPlaceSearcher
- Direction
- shared.platform uses shared.data.openstreetmap, so a change to shared.data.openstreetmap can break shared.platform, while a change to shared.platform can't break shared.data.openstreetmap.
- Position
- Below the diagonal: shared.platform uses a module listed above it, which is the healthy direction.
25→3 shared.domain uses shared.entity✕
- Connections
- 22 pairs of types, where a type in shared.domain uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.shared.domain.ActualGetForecast→hr.dtakac.prognoza.shared.entity.ForecastDatumhr.dtakac.prognoza.shared.domain.ActualGetForecast→hr.dtakac.prognoza.shared.entity.ForecastProviderhr.dtakac.prognoza.shared.domain.ActualGetForecast→hr.dtakac.prognoza.shared.entity.Placehr.dtakac.prognoza.shared.domain.DeleteSavedPlace→hr.dtakac.prognoza.shared.entity.Placehr.dtakac.prognoza.shared.domain.GetAllForecastProviders→hr.dtakac.prognoza.shared.entity.ForecastProviderhr.dtakac.prognoza.shared.domain.GetAllPrecipitationUnits→hr.dtakac.prognoza.shared.entity.LengthUnithr.dtakac.prognoza.shared.domain.GetAllPressureUnits→hr.dtakac.prognoza.shared.entity.PressureUnithr.dtakac.prognoza.shared.domain.GetAllTemperatureUnits→hr.dtakac.prognoza.shared.entity.TemperatureUnithr.dtakac.prognoza.shared.domain.GetAllWindUnits→hr.dtakac.prognoza.shared.entity.SpeedUnithr.dtakac.prognoza.shared.domain.GetForecastProvider→hr.dtakac.prognoza.shared.entity.ForecastProviderhr.dtakac.prognoza.shared.domain.GetPrecipitationUnit→hr.dtakac.prognoza.shared.entity.LengthUnithr.dtakac.prognoza.shared.domain.GetPressureUnit→hr.dtakac.prognoza.shared.entity.PressureUnithr.dtakac.prognoza.shared.domain.GetSavedPlaces→hr.dtakac.prognoza.shared.entity.Placehr.dtakac.prognoza.shared.domain.GetSelectedPlace→hr.dtakac.prognoza.shared.entity.Placehr.dtakac.prognoza.shared.domain.GetTemperatureUnit→hr.dtakac.prognoza.shared.entity.TemperatureUnithr.dtakac.prognoza.shared.domain.GetWindUnit→hr.dtakac.prognoza.shared.entity.SpeedUnithr.dtakac.prognoza.shared.domain.SelectPlace→hr.dtakac.prognoza.shared.entity.Placehr.dtakac.prognoza.shared.domain.SetForecastProvider→hr.dtakac.prognoza.shared.entity.ForecastProviderhr.dtakac.prognoza.shared.domain.SetPrecipitationUnit→hr.dtakac.prognoza.shared.entity.LengthUnithr.dtakac.prognoza.shared.domain.SetPressureUnit→hr.dtakac.prognoza.shared.entity.PressureUnithr.dtakac.prognoza.shared.domain.SetTemperatureUnit→hr.dtakac.prognoza.shared.entity.TemperatureUnithr.dtakac.prognoza.shared.domain.SetWindUnit→hr.dtakac.prognoza.shared.entity.SpeedUnit
- Direction
- shared.domain uses shared.entity, so a change to shared.entity can break shared.domain, while a change to shared.domain can't break shared.entity.
- Position
- Below the diagonal: shared.domain uses a module listed above it, which is the healthy direction.
25→10 shared.domain uses shared.domain.data✕
- Connections
- 17 pairs of types, where a type in shared.domain uses a type in shared.domain.data.
- The types involved
hr.dtakac.prognoza.shared.domain.ActualGetForecast→hr.dtakac.prognoza.shared.domain.data.ForecastRepositoryhr.dtakac.prognoza.shared.domain.DeleteSavedPlace→hr.dtakac.prognoza.shared.domain.data.SavedPlaceRemoverhr.dtakac.prognoza.shared.domain.GetForecastProvider→hr.dtakac.prognoza.shared.domain.data.SettingsRepositoryhr.dtakac.prognoza.shared.domain.GetPrecipitationUnit→hr.dtakac.prognoza.shared.domain.data.SettingsRepositoryhr.dtakac.prognoza.shared.domain.GetPressureUnit→hr.dtakac.prognoza.shared.domain.data.SettingsRepositoryhr.dtakac.prognoza.shared.domain.GetSavedPlaces→hr.dtakac.prognoza.shared.domain.data.SavedPlaceGetterhr.dtakac.prognoza.shared.domain.GetSelectedPlace→hr.dtakac.prognoza.shared.domain.data.SettingsRepositoryhr.dtakac.prognoza.shared.domain.GetTemperatureUnit→hr.dtakac.prognoza.shared.domain.data.SettingsRepositoryhr.dtakac.prognoza.shared.domain.GetWindUnit→hr.dtakac.prognoza.shared.domain.data.SettingsRepositoryhr.dtakac.prognoza.shared.domain.SearchPlaces→hr.dtakac.prognoza.shared.domain.data.PlaceSearcherhr.dtakac.prognoza.shared.domain.SelectPlace→hr.dtakac.prognoza.shared.domain.data.PlaceSaverhr.dtakac.prognoza.shared.domain.SelectPlace→hr.dtakac.prognoza.shared.domain.data.SettingsRepositoryhr.dtakac.prognoza.shared.domain.SetForecastProvider→hr.dtakac.prognoza.shared.domain.data.SettingsRepositoryhr.dtakac.prognoza.shared.domain.SetPrecipitationUnit→hr.dtakac.prognoza.shared.domain.data.SettingsRepositoryhr.dtakac.prognoza.shared.domain.SetPressureUnit→hr.dtakac.prognoza.shared.domain.data.SettingsRepositoryhr.dtakac.prognoza.shared.domain.SetTemperatureUnit→hr.dtakac.prognoza.shared.domain.data.SettingsRepositoryhr.dtakac.prognoza.shared.domain.SetWindUnit→hr.dtakac.prognoza.shared.domain.data.SettingsRepository
- Direction
- shared.domain uses shared.domain.data, so a change to shared.domain.data can break shared.domain, while a change to shared.domain can't break shared.domain.data.
- Position
- Below the diagonal: shared.domain uses a module listed above it, which is the healthy direction.
25→24 shared.domain uses shared.platform✕
- Connections
- 1 pair of types, where a type in shared.domain uses a type in shared.platform.
- The types involved
hr.dtakac.prognoza.shared.domain.SearchPlaces→hr.dtakac.prognoza.shared.platform.LocalRfc2616LanguageGetter
- Direction
- shared.domain uses shared.platform, so a change to shared.platform can break shared.domain, while a change to shared.domain can't break shared.platform.
- Position
- Below the diagonal: shared.domain uses a module listed above it, which is the healthy direction.
26→7 di uses shared✕
- Connections
- 1 pair of types, where a type in di uses a type in shared.
- The types involved
hr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.PrognozaSdk
- Direction
- di uses shared, so a change to shared can break di, while a change to di can't break shared.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
26→25 di uses shared.domain✕
- Connections
- 21 pairs of types, where a type in di uses a type in shared.domain.
- The types involved
hr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.DeleteSavedPlacehr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.GetAllForecastProvidershr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.GetAllPrecipitationUnitshr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.GetAllPressureUnitshr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.GetAllTemperatureUnitshr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.GetAllWindUnitshr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.GetForecasthr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.GetForecastProviderhr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.GetPrecipitationUnithr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.GetPressureUnithr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.GetSavedPlaceshr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.GetSelectedPlacehr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.GetTemperatureUnithr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.GetWindUnithr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.SearchPlaceshr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.SelectPlacehr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.SetForecastProviderhr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.SetPrecipitationUnithr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.SetPressureUnithr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.SetTemperatureUnithr.dtakac.prognoza.di.UseCaseModule→hr.dtakac.prognoza.shared.domain.SetWindUnit
- Direction
- di uses shared.domain, so a change to shared.domain can break di, while a change to di can't break shared.domain.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
27→1 presentation.settingsscreen uses androidsettings✕
- Connections
- 5 pairs of types, where a type in presentation.settingsscreen uses a type in androidsettings.
- The types involved
hr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenUiMapper→hr.dtakac.prognoza.androidsettings.MoodModehr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenUiMapper→hr.dtakac.prognoza.androidsettings.UiModehr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.androidsettings.AndroidSettingsRepositoryhr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.androidsettings.MoodModehr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.androidsettings.UiMode
- Direction
- presentation.settingsscreen uses androidsettings, so a change to androidsettings can break presentation.settingsscreen, while a change to presentation.settingsscreen can't break androidsettings.
- Position
- Below the diagonal: presentation.settingsscreen uses a module listed above it, which is the healthy direction.
27→2 presentation.settingsscreen uses presentation✕
- Connections
- 3 pairs of types, where a type in presentation.settingsscreen uses a type in presentation.
- The types involved
hr.dtakac.prognoza.presentation.settingsscreen.MultipleChoiceSettingUi→hr.dtakac.prognoza.presentation.TextResourcehr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenState→hr.dtakac.prognoza.presentation.Eventhr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.presentation.WidgetRefresher
- Direction
- presentation.settingsscreen uses presentation, so a change to presentation can break presentation.settingsscreen, while a change to presentation.settingsscreen can't break presentation.
- Position
- Below the diagonal: presentation.settingsscreen uses a module listed above it, which is the healthy direction.
27→3 presentation.settingsscreen uses shared.entity✕
- Connections
- 10 pairs of types, where a type in presentation.settingsscreen uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenUiMapper→hr.dtakac.prognoza.shared.entity.ForecastProviderhr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenUiMapper→hr.dtakac.prognoza.shared.entity.LengthUnithr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenUiMapper→hr.dtakac.prognoza.shared.entity.PressureUnithr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenUiMapper→hr.dtakac.prognoza.shared.entity.SpeedUnithr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenUiMapper→hr.dtakac.prognoza.shared.entity.TemperatureUnithr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.entity.ForecastProviderhr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.entity.LengthUnithr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.entity.PressureUnithr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.entity.SpeedUnithr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.entity.TemperatureUnit
- Direction
- presentation.settingsscreen uses shared.entity, so a change to shared.entity can break presentation.settingsscreen, while a change to presentation.settingsscreen can't break shared.entity.
- Position
- Below the diagonal: presentation.settingsscreen uses a module listed above it, which is the healthy direction.
27→25 presentation.settingsscreen uses shared.domain✕
- Connections
- 15 pairs of types, where a type in presentation.settingsscreen uses a type in shared.domain.
- The types involved
hr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.domain.GetAllForecastProvidershr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.domain.GetAllPrecipitationUnitshr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.domain.GetAllPressureUnitshr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.domain.GetAllTemperatureUnitshr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.domain.GetAllWindUnitshr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.domain.GetForecastProviderhr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.domain.GetPrecipitationUnithr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.domain.GetPressureUnithr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.domain.GetTemperatureUnithr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.domain.GetWindUnithr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.domain.SetForecastProviderhr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.domain.SetPrecipitationUnithr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.domain.SetPressureUnithr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.domain.SetTemperatureUnithr.dtakac.prognoza.presentation.settingsscreen.SettingsScreenViewModel→hr.dtakac.prognoza.shared.domain.SetWindUnit
- Direction
- presentation.settingsscreen uses shared.domain, so a change to shared.domain can break presentation.settingsscreen, while a change to presentation.settingsscreen can't break shared.domain.
- Position
- Below the diagonal: presentation.settingsscreen uses a module listed above it, which is the healthy direction.
28→3 shared.domain.GetForecastResult uses shared.entity✕
- Connections
- 5 pairs of types, where a type in shared.domain.GetForecastResult uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.shared.domain.GetForecastResult.Success→hr.dtakac.prognoza.shared.entity.Forecasthr.dtakac.prognoza.shared.domain.GetForecastResult.Success→hr.dtakac.prognoza.shared.entity.ForecastProviderhr.dtakac.prognoza.shared.domain.GetForecastResult.Success→hr.dtakac.prognoza.shared.entity.LengthUnithr.dtakac.prognoza.shared.domain.GetForecastResult.Success→hr.dtakac.prognoza.shared.entity.SpeedUnithr.dtakac.prognoza.shared.domain.GetForecastResult.Success→hr.dtakac.prognoza.shared.entity.TemperatureUnit
- Direction
- shared.domain.GetForecastResult uses shared.entity, so a change to shared.entity can break shared.domain.GetForecastResult, while a change to shared.domain.GetForecastResult can't break shared.entity.
- Position
- Below the diagonal: shared.domain.GetForecastResult uses a module listed above it, which is the healthy direction.
28→25 shared.domain.GetForecastResult uses shared.domain✕
- Connections
- 2 pairs of types, where a type in shared.domain.GetForecastResult uses a type in shared.domain.
- The types involved
hr.dtakac.prognoza.shared.domain.GetForecastResult.Empty→hr.dtakac.prognoza.shared.domain.GetForecastResulthr.dtakac.prognoza.shared.domain.GetForecastResult.Success→hr.dtakac.prognoza.shared.domain.GetForecastResult
- Direction
- shared.domain.GetForecastResult uses shared.domain, so a change to shared.domain can break shared.domain.GetForecastResult, while a change to shared.domain.GetForecastResult can't break shared.domain.
- Position
- Below the diagonal: shared.domain.GetForecastResult uses a module listed above it, which is the healthy direction.
29→3 shared.domain.SearchPlacesResult uses shared.entity✕
- Connections
- 1 pair of types, where a type in shared.domain.SearchPlacesResult uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.shared.domain.SearchPlacesResult.Success→hr.dtakac.prognoza.shared.entity.Place
- Direction
- shared.domain.SearchPlacesResult uses shared.entity, so a change to shared.entity can break shared.domain.SearchPlacesResult, while a change to shared.domain.SearchPlacesResult can't break shared.entity.
- Position
- Below the diagonal: shared.domain.SearchPlacesResult uses a module listed above it, which is the healthy direction.
29→25 shared.domain.SearchPlacesResult uses shared.domain✕
- Connections
- 2 pairs of types, where a type in shared.domain.SearchPlacesResult uses a type in shared.domain.
- The types involved
hr.dtakac.prognoza.shared.domain.SearchPlacesResult.Empty→hr.dtakac.prognoza.shared.domain.SearchPlacesResulthr.dtakac.prognoza.shared.domain.SearchPlacesResult.Success→hr.dtakac.prognoza.shared.domain.SearchPlacesResult
- Direction
- shared.domain.SearchPlacesResult uses shared.domain, so a change to shared.domain can break shared.domain.SearchPlacesResult, while a change to shared.domain.SearchPlacesResult can't break shared.domain.
- Position
- Below the diagonal: shared.domain.SearchPlacesResult uses a module listed above it, which is the healthy direction.
30→3 widget uses shared.entity✕
- Connections
- 4 pairs of types, where a type in widget uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.widget.ForecastWidget→hr.dtakac.prognoza.shared.entity.TemperatureUnithr.dtakac.prognoza.widget.TemperatureSerializer→hr.dtakac.prognoza.shared.entity.Temperaturehr.dtakac.prognoza.widget.WidgetHour→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.widget.WidgetHour→hr.dtakac.prognoza.shared.entity.Temperature
- Direction
- widget uses shared.entity, so a change to shared.entity can break widget, while a change to widget can't break shared.entity.
- Position
- Below the diagonal: widget uses a module listed above it, which is the healthy direction.
30→25 widget uses shared.domain✕
- Connections
- 1 pair of types, where a type in widget uses a type in shared.domain.
- The types involved
hr.dtakac.prognoza.widget.ForecastWidgetWorker→hr.dtakac.prognoza.shared.domain.GetForecast
- Direction
- widget uses shared.domain, so a change to shared.domain can break widget, while a change to widget can't break shared.domain.
- Position
- Below the diagonal: widget uses a module listed above it, which is the healthy direction.
31→25 widget.ForecastWidgetWorker uses shared.domain✕
- Connections
- 1 pair of types, where a type in widget.ForecastWidgetWorker uses a type in shared.domain.
- The types involved
hr.dtakac.prognoza.widget.ForecastWidgetWorker.Factory→hr.dtakac.prognoza.shared.domain.GetForecast
- Direction
- widget.ForecastWidgetWorker uses shared.domain, so a change to shared.domain can break widget.ForecastWidgetWorker, while a change to widget.ForecastWidgetWorker can't break shared.domain.
- Position
- Below the diagonal: widget.ForecastWidgetWorker uses a module listed above it, which is the healthy direction.
31→32 widget.ForecastWidgetWorker uses di.work part of a loop✕
- Connections
- 1 pair of types, where a type in widget.ForecastWidgetWorker uses a type in di.work.
- The types involved
hr.dtakac.prognoza.widget.ForecastWidgetWorker.Factory→hr.dtakac.prognoza.di.work.ChildWorkerFactory
- Direction
- widget.ForecastWidgetWorker uses di.work, so a change to di.work can break widget.ForecastWidgetWorker, while a change to widget.ForecastWidgetWorker can't break di.work.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→31 di.work uses widget.ForecastWidgetWorker✕
- Connections
- 1 pair of types, where a type in di.work uses a type in widget.ForecastWidgetWorker.
- The types involved
hr.dtakac.prognoza.di.work.WorkerModule→hr.dtakac.prognoza.widget.ForecastWidgetWorker.Factory
- Direction
- di.work uses widget.ForecastWidgetWorker, so a change to widget.ForecastWidgetWorker can break di.work, while a change to di.work can't break widget.ForecastWidgetWorker.
- Position
- Below the diagonal: di.work uses a module listed above it, which is the healthy direction.
33→2 presentation.forecast uses presentation✕
- Connections
- 9 pairs of types, where a type in presentation.forecast uses a type in presentation.
- The types involved
hr.dtakac.prognoza.presentation.forecast.ComingDayHourUi→hr.dtakac.prognoza.presentation.TextResourcehr.dtakac.prognoza.presentation.forecast.ComingDayUi→hr.dtakac.prognoza.presentation.TextResourcehr.dtakac.prognoza.presentation.forecast.CommonMappingKt→hr.dtakac.prognoza.presentation.TextResourcehr.dtakac.prognoza.presentation.forecast.CurrentUi→hr.dtakac.prognoza.presentation.TextResourcehr.dtakac.prognoza.presentation.forecast.DayHourUi→hr.dtakac.prognoza.presentation.TextResourcehr.dtakac.prognoza.presentation.forecast.ForecastState→hr.dtakac.prognoza.presentation.TextResourcehr.dtakac.prognoza.presentation.forecast.ForecastUi→hr.dtakac.prognoza.presentation.TextResourcehr.dtakac.prognoza.presentation.forecast.ForecastUiMapper→hr.dtakac.prognoza.presentation.TextResourcehr.dtakac.prognoza.presentation.forecast.TodayUi→hr.dtakac.prognoza.presentation.TextResource
- Direction
- presentation.forecast uses presentation, so a change to presentation can break presentation.forecast, while a change to presentation.forecast can't break presentation.
- Position
- Below the diagonal: presentation.forecast uses a module listed above it, which is the healthy direction.
33→3 presentation.forecast uses shared.entity✕
- Connections
- 17 pairs of types, where a type in presentation.forecast uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.presentation.forecast.ComingDayHourUi→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.presentation.forecast.ComingDayUi→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.presentation.forecast.CommonMappingKt→hr.dtakac.prognoza.shared.entity.Temperaturehr.dtakac.prognoza.presentation.forecast.CommonMappingKt→hr.dtakac.prognoza.shared.entity.TemperatureUnithr.dtakac.prognoza.presentation.forecast.CurrentUi→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.presentation.forecast.CurrentUi→hr.dtakac.prognoza.shared.entity.Moodhr.dtakac.prognoza.presentation.forecast.DayHourUi→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.presentation.forecast.ForecastUiMapper→hr.dtakac.prognoza.shared.entity.Currenthr.dtakac.prognoza.presentation.forecast.ForecastUiMapper→hr.dtakac.prognoza.shared.entity.Dayhr.dtakac.prognoza.presentation.forecast.ForecastUiMapper→hr.dtakac.prognoza.shared.entity.HourlyDatumhr.dtakac.prognoza.presentation.forecast.ForecastUiMapper→hr.dtakac.prognoza.shared.entity.Lengthhr.dtakac.prognoza.presentation.forecast.ForecastUiMapper→hr.dtakac.prognoza.shared.entity.LengthUnithr.dtakac.prognoza.presentation.forecast.ForecastUiMapper→hr.dtakac.prognoza.shared.entity.SpeedUnithr.dtakac.prognoza.presentation.forecast.ForecastUiMapper→hr.dtakac.prognoza.shared.entity.Temperaturehr.dtakac.prognoza.presentation.forecast.ForecastUiMapper→hr.dtakac.prognoza.shared.entity.TemperatureUnithr.dtakac.prognoza.presentation.forecast.ForecastUiMapper→hr.dtakac.prognoza.shared.entity.Todayhr.dtakac.prognoza.presentation.forecast.ForecastUiMapper→hr.dtakac.prognoza.shared.entity.Wind
- Direction
- presentation.forecast uses shared.entity, so a change to shared.entity can break presentation.forecast, while a change to presentation.forecast can't break shared.entity.
- Position
- Below the diagonal: presentation.forecast uses a module listed above it, which is the healthy direction.
33→25 presentation.forecast uses shared.domain✕
- Connections
- 1 pair of types, where a type in presentation.forecast uses a type in shared.domain.
- The types involved
hr.dtakac.prognoza.presentation.forecast.ForecastViewModel→hr.dtakac.prognoza.shared.domain.GetForecast
- Direction
- presentation.forecast uses shared.domain, so a change to shared.domain can break presentation.forecast, while a change to presentation.forecast can't break shared.domain.
- Position
- Below the diagonal: presentation.forecast uses a module listed above it, which is the healthy direction.
33→28 presentation.forecast uses shared.domain.GetForecastResult✕
- Connections
- 2 pairs of types, where a type in presentation.forecast uses a type in shared.domain.GetForecastResult.
- The types involved
hr.dtakac.prognoza.presentation.forecast.ForecastUiMapper→hr.dtakac.prognoza.shared.domain.GetForecastResult.Emptyhr.dtakac.prognoza.presentation.forecast.ForecastUiMapper→hr.dtakac.prognoza.shared.domain.GetForecastResult.Success
- Direction
- presentation.forecast uses shared.domain.GetForecastResult, so a change to shared.domain.GetForecastResult can break presentation.forecast, while a change to presentation.forecast can't break shared.domain.GetForecastResult.
- Position
- Below the diagonal: presentation.forecast uses a module listed above it, which is the healthy direction.
34→2 presentation.places uses presentation✕
- Connections
- 5 pairs of types, where a type in presentation.places uses a type in presentation.
- The types involved
hr.dtakac.prognoza.presentation.places.PlaceUi→hr.dtakac.prognoza.presentation.TextResourcehr.dtakac.prognoza.presentation.places.PlacesState→hr.dtakac.prognoza.presentation.Eventhr.dtakac.prognoza.presentation.places.PlacesState→hr.dtakac.prognoza.presentation.TextResourcehr.dtakac.prognoza.presentation.places.PlacesUiMapper→hr.dtakac.prognoza.presentation.TextResourcehr.dtakac.prognoza.presentation.places.PlacesViewModel→hr.dtakac.prognoza.presentation.WidgetRefresher
- Direction
- presentation.places uses presentation, so a change to presentation can break presentation.places, while a change to presentation.places can't break presentation.
- Position
- Below the diagonal: presentation.places uses a module listed above it, which is the healthy direction.
34→3 presentation.places uses shared.entity✕
- Connections
- 2 pairs of types, where a type in presentation.places uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.presentation.places.PlacesUiMapper→hr.dtakac.prognoza.shared.entity.Placehr.dtakac.prognoza.presentation.places.PlacesViewModel→hr.dtakac.prognoza.shared.entity.Place
- Direction
- presentation.places uses shared.entity, so a change to shared.entity can break presentation.places, while a change to presentation.places can't break shared.entity.
- Position
- Below the diagonal: presentation.places uses a module listed above it, which is the healthy direction.
34→25 presentation.places uses shared.domain✕
- Connections
- 5 pairs of types, where a type in presentation.places uses a type in shared.domain.
- The types involved
hr.dtakac.prognoza.presentation.places.PlacesViewModel→hr.dtakac.prognoza.shared.domain.DeleteSavedPlacehr.dtakac.prognoza.presentation.places.PlacesViewModel→hr.dtakac.prognoza.shared.domain.GetSavedPlaceshr.dtakac.prognoza.presentation.places.PlacesViewModel→hr.dtakac.prognoza.shared.domain.GetSelectedPlacehr.dtakac.prognoza.presentation.places.PlacesViewModel→hr.dtakac.prognoza.shared.domain.SearchPlaceshr.dtakac.prognoza.presentation.places.PlacesViewModel→hr.dtakac.prognoza.shared.domain.SelectPlace
- Direction
- presentation.places uses shared.domain, so a change to shared.domain can break presentation.places, while a change to presentation.places can't break shared.domain.
- Position
- Below the diagonal: presentation.places uses a module listed above it, which is the healthy direction.
34→29 presentation.places uses shared.domain.SearchPlacesResult✕
- Connections
- 1 pair of types, where a type in presentation.places uses a type in shared.domain.SearchPlacesResult.
- The types involved
hr.dtakac.prognoza.presentation.places.PlacesUiMapper→hr.dtakac.prognoza.shared.domain.SearchPlacesResult.Empty
- Direction
- presentation.places uses shared.domain.SearchPlacesResult, so a change to shared.domain.SearchPlacesResult can break presentation.places, while a change to presentation.places can't break shared.domain.SearchPlacesResult.
- Position
- Below the diagonal: presentation.places uses a module listed above it, which is the healthy direction.
35→28 shared.domain.GetForecastResult.Empty uses shared.domain.GetForecastResult✕
- Connections
- 2 pairs of types, where a type in shared.domain.GetForecastResult.Empty uses a type in shared.domain.GetForecastResult.
- The types involved
hr.dtakac.prognoza.shared.domain.GetForecastResult.Empty.Error→hr.dtakac.prognoza.shared.domain.GetForecastResult.Emptyhr.dtakac.prognoza.shared.domain.GetForecastResult.Empty.NoSelectedPlace→hr.dtakac.prognoza.shared.domain.GetForecastResult.Empty
- Direction
- shared.domain.GetForecastResult.Empty uses shared.domain.GetForecastResult, so a change to shared.domain.GetForecastResult can break shared.domain.GetForecastResult.Empty, while a change to shared.domain.GetForecastResult.Empty can't break shared.domain.GetForecastResult.
- Position
- Below the diagonal: shared.domain.GetForecastResult.Empty uses a module listed above it, which is the healthy direction.
36→29 shared.domain.SearchPlacesResult.Empty uses shared.domain.SearchPlacesResult✕
- Connections
- 2 pairs of types, where a type in shared.domain.SearchPlacesResult.Empty uses a type in shared.domain.SearchPlacesResult.
- The types involved
hr.dtakac.prognoza.shared.domain.SearchPlacesResult.Empty.Error→hr.dtakac.prognoza.shared.domain.SearchPlacesResult.Emptyhr.dtakac.prognoza.shared.domain.SearchPlacesResult.Empty.None→hr.dtakac.prognoza.shared.domain.SearchPlacesResult.Empty
- Direction
- shared.domain.SearchPlacesResult.Empty uses shared.domain.SearchPlacesResult, so a change to shared.domain.SearchPlacesResult can break shared.domain.SearchPlacesResult.Empty, while a change to shared.domain.SearchPlacesResult.Empty can't break shared.domain.SearchPlacesResult.
- Position
- Below the diagonal: shared.domain.SearchPlacesResult.Empty uses a module listed above it, which is the healthy direction.
37→3 widget.ForecastWidgetState uses shared.entity✕
- Connections
- 3 pairs of types, where a type in widget.ForecastWidgetState uses a type in shared.entity.
- The types involved
hr.dtakac.prognoza.widget.ForecastWidgetState.Success→hr.dtakac.prognoza.shared.entity.Descriptionhr.dtakac.prognoza.widget.ForecastWidgetState.Success→hr.dtakac.prognoza.shared.entity.Temperaturehr.dtakac.prognoza.widget.ForecastWidgetState.Success→hr.dtakac.prognoza.shared.entity.TemperatureUnit
- Direction
- widget.ForecastWidgetState uses shared.entity, so a change to shared.entity can break widget.ForecastWidgetState, while a change to widget.ForecastWidgetState can't break shared.entity.
- Position
- Below the diagonal: widget.ForecastWidgetState uses a module listed above it, which is the healthy direction.
37→30 widget.ForecastWidgetState uses widget✕
- Connections
- 5 pairs of types, where a type in widget.ForecastWidgetState uses a type in widget.
- The types involved
hr.dtakac.prognoza.widget.ForecastWidgetState.Error→hr.dtakac.prognoza.widget.ForecastWidgetStatehr.dtakac.prognoza.widget.ForecastWidgetState.Loading→hr.dtakac.prognoza.widget.ForecastWidgetStatehr.dtakac.prognoza.widget.ForecastWidgetState.Success→hr.dtakac.prognoza.widget.ForecastWidgetStatehr.dtakac.prognoza.widget.ForecastWidgetState.Success→hr.dtakac.prognoza.widget.WidgetHourhr.dtakac.prognoza.widget.ForecastWidgetState.Unavailable→hr.dtakac.prognoza.widget.ForecastWidgetState
- Direction
- widget.ForecastWidgetState uses widget, so a change to widget can break widget.ForecastWidgetState, while a change to widget.ForecastWidgetState can't break widget.
- Position
- Below the diagonal: widget.ForecastWidgetState uses a module listed above it, which is the healthy direction.
38→2 hr.dtakac.prognoza uses presentation✕
- Connections
- 1 pair of types, where a type in hr.dtakac.prognoza uses a type in presentation.
- The types involved
hr.dtakac.prognoza.PrognozaApplication→hr.dtakac.prognoza.presentation.WidgetRefresher
- Direction
- hr.dtakac.prognoza uses presentation, so a change to presentation can break hr.dtakac.prognoza, while a change to hr.dtakac.prognoza can't break presentation.
- Position
- Below the diagonal: hr.dtakac.prognoza uses a module listed above it, which is the healthy direction.
38→32 hr.dtakac.prognoza uses di.work✕
- Connections
- 1 pair of types, where a type in hr.dtakac.prognoza uses a type in di.work.
- The types involved
hr.dtakac.prognoza.PrognozaApplication→hr.dtakac.prognoza.di.work.WorkerFactory
- Direction
- hr.dtakac.prognoza uses di.work, so a change to di.work can break hr.dtakac.prognoza, while a change to hr.dtakac.prognoza can't break di.work.
- Position
- Below the diagonal: hr.dtakac.prognoza uses a module listed above it, which is the healthy direction.
39→33 ui.forecast uses presentation.forecast✕
- Connections
- 9 pairs of types, where a type in ui.forecast uses a type in presentation.forecast.
- The types involved
hr.dtakac.prognoza.ui.forecast.ComingDayKt→hr.dtakac.prognoza.presentation.forecast.ComingDayHourUihr.dtakac.prognoza.ui.forecast.ComingDayKt→hr.dtakac.prognoza.presentation.forecast.ComingDayUihr.dtakac.prognoza.ui.forecast.DayHourKt→hr.dtakac.prognoza.presentation.forecast.DayHourUihr.dtakac.prognoza.ui.forecast.ForecastContentKt→hr.dtakac.prognoza.presentation.forecast.ForecastStatehr.dtakac.prognoza.ui.forecast.ForecastDataListKt→hr.dtakac.prognoza.presentation.forecast.ComingDayUihr.dtakac.prognoza.ui.forecast.ForecastDataListKt→hr.dtakac.prognoza.presentation.forecast.CurrentUihr.dtakac.prognoza.ui.forecast.ForecastDataListKt→hr.dtakac.prognoza.presentation.forecast.ForecastUihr.dtakac.prognoza.ui.forecast.ForecastDataListKt→hr.dtakac.prognoza.presentation.forecast.TodayUihr.dtakac.prognoza.ui.forecast.ForecastScreenKt→hr.dtakac.prognoza.presentation.forecast.ForecastState
- Direction
- ui.forecast uses presentation.forecast, so a change to presentation.forecast can break ui.forecast, while a change to ui.forecast can't break presentation.forecast.
- Position
- Below the diagonal: ui.forecast uses a module listed above it, which is the healthy direction.
40→2 ui.places uses presentation✕
- Connections
- 1 pair of types, where a type in ui.places uses a type in presentation.
- The types involved
hr.dtakac.prognoza.ui.places.PlacesListKt→hr.dtakac.prognoza.presentation.TextResource
- Direction
- ui.places uses presentation, so a change to presentation can break ui.places, while a change to ui.places can't break presentation.
- Position
- Below the diagonal: ui.places uses a module listed above it, which is the healthy direction.
40→34 ui.places uses presentation.places✕
- Connections
- 3 pairs of types, where a type in ui.places uses a type in presentation.places.
- The types involved
hr.dtakac.prognoza.ui.places.PlacesContentKt→hr.dtakac.prognoza.presentation.places.PlacesStatehr.dtakac.prognoza.ui.places.PlacesListKt→hr.dtakac.prognoza.presentation.places.PlaceUihr.dtakac.prognoza.ui.places.PlacesScreenKt→hr.dtakac.prognoza.presentation.places.PlacesViewModel
- Direction
- ui.places uses presentation.places, so a change to presentation.places can break ui.places, while a change to ui.places can't break presentation.places.
- Position
- Below the diagonal: ui.places uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 8 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
Roadmap
Top priorities: Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; 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; Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +7.1 pts | Low | Documentation Quality |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +7.1 pts | Low | ADR Quality |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +8.3 pts | Medium | Observability |
| 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. | +8.3 pts | Medium | Security & performance tooling |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.2 pts | Medium | Architecture documentation |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +3.7 pts | Medium | Deployment & Rollback |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). | +1.5 pts | Low | Static Analysis (SAST) |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +2.8 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| shared/src/commonMain/kotlin/hr/dtakac/prognoza/shared/data/openmeteo/network/OpenMeteoResponse.kt | 7.8 | Mixed | Cyclomatic Complexity: OpenMeteoResponseKt.mapWmoCodeToDescription (cyclomatic 45) |
| androidApp/src/main/java/hr/dtakac/prognoza/ui/forecast/ComingDay.kt | 7.8 | Mixed | Cognitive Complexity: ComingDayKt.ComingDay (cognitive 18) |
| androidApp/src/main/java/hr/dtakac/prognoza/PrognozaApplication.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| androidApp/src/main/java/hr/dtakac/prognoza/widget/ForecastWidgetWorker.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| androidApp/src/main/java/hr/dtakac/prognoza/ui/theme/Theme.kt | 8.5 | Near-clean | Cognitive Complexity: ThemeKt.getByMood (cognitive 19) |
| README.md | 9.5 | Near-clean | Documentation Quality: Documentation: no build, run or usage example |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 54 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 54 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, 21 of 33 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because download.jetbrains.com — the registry that answers it — was asked and did not reply (the build stopped because download.jetbrains.com, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it, so the dependency graph was not resolved). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add download.jetbrains.com to the allowlist and re-run — not to build anything.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's 4 Maven/Gradle manifest(s) were read and none of the dependency coordinates they declare carries a version resolvable from the manifest itself: every one is inherited from a parent POM, a <dependencyManagement> block, an imported BOM or a Gradle version reference the catalogue does not define. Licences are resolved from the POMs Maven Central publishes, which requires a version to ask about, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 653 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 2 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (shared/build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (androidApp). the Android app did not build — `./gradlew :androidApp:assembleDebug` exited 1: > Could not get resource 'https://download.jetbrains.com/kotlin/native/builds/releases/1.7.10/linux-x86_64/kotlin-native-prebuilt-linux-x86_64-1.7.10.tar.gz'. > Could not HEAD 'https:/…; runtime evidence skipped (launch chosen because androidApp/build.gradle.kts applies the Android application plugin and gradlew builds it).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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").
- 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was OpenMeteoResponseKt.mapWmoCodeToDescription at 45. A further 7 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 Mood.fromDescription at 85 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: androidApp/src/main/java/hr/dtakac/prognoza/presentation/forecast/CommonMapping.kt (CommonMappingKt.toStringId at 85), androidApp/src/main/java/hr/dtakac/prognoza/ui/theme/WeatherIcons.kt (WeatherIconsKt.asWeatherIconResId at 85), shared/src/commonMain/kotlin/hr/dtakac/prognoza/shared/entity/Mood.kt (Mood.fromDescription at 85), iosApp/iosApp/presentation/ForecastUiMapper.swift (ForecastUiMapper.getWeatherIconKey at 84), shared/src/commonMain/kotlin/hr/dtakac/prognoza/shared/data/metnorway/network/LocationForecastResponse.kt (LocationForecastResponseKt.mapToDescription at 84). 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 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with OpenMeteoResponseKt.mapWmoCodeToDescription (cyclomatic 45). — Refactoring it lifts Cyclomatic Complexity from 8.8 to about 10.0/10.
- 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
3 method(s) exceeded the cognitive complexity threshold of 15; the worst was ThemeKt.getByMood at 19.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with ThemeKt.getByMood (cognitive 19), OpenMeteoResponseKt.mapWmoCodeToDescription (cognitive 18), ComingDayKt.ComingDay (cognitive 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 9.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
1 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with ComingDay.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
3 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; 1 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
0 of 19 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
2 deducted task-comment markers across 9381 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with PrognozaApplication.kt, ForecastWidgetWorker.kt. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 2 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
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 4 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)
8 finding(s): 0 critical, 7 high, 1 medium, 0 low. 3 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` (lines 144–145, line 146, line 147, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 3 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 (3 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 50 of the 162 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
M1 · Documentation (README)
- This repository declares its own end of life: `README.md` line 1 reads “<h1 align="center" style="vertical-align:middle">This project has been archived and will receive no further updates. Work continues in <a href="https://github.com/davidtakac/bura">Bura</a>.</h1>”. That is a first-party statement of intent, not an inference — the Maturity and Knowledge lenses otherwise approximate the same fact from decayed commit history (D16 reports a dormant codebase, D34 orphaned files), and this row says the maintainer already told you. It does NOT change any score: an honest end-of-life notice is the README doing its job, and every dimension below still measures the code as it stands. Read the whole report as an assessment of software the author has stopped working on. — README.md:1
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 3 of 3 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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
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
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
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
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 (_: 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. — shared/src/commonMain/kotlin/hr/dtakac/prognoza/shared/data/openmeteo/OpenMeteoForecastProvider.kt:40
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — shared/src/commonMain/kotlin/hr/dtakac/prognoza/shared/data/openmeteo/OpenMeteoForecastProvider.kt:76, androidApp/src/main/java/hr/dtakac/prognoza/ui/common/Util.kt:10
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82% | Strong | Solid. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 52% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 36% | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 68% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 64 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Dagger rejects, at compile time, a component that holds a binding with a narrower scope than its own.
- 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Android app did not build — `./gradlew :androidApp:assembleDebug` exited 1: > Could not get resource 'https://download.jetbrains.com/kotlin/native/builds/releases/1.7.10/linux-x86_64/kotlin-native-prebuilt-linux-x86_64-1.7.10.tar.gz'. > Could not HEAD 'https:/…; runtime evidence skipped (launch chosen because androidApp/build.gradle.kts applies the Android application plugin and gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
- 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 — ~864 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 — Dependency currency not established — download.jetbrains.com did not answer
- D14 License Compliance — JVM licences not graded — no declared coordinate carries a version the manifest itself resolves
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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# and TypeScript only; Kotlin, Swift not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — 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 — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- 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) — 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.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- 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): 29 value object(s); a Domain/Aggregates/ValueObjects layer
- 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
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, Swift source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (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.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X24 Document value interpolated into markup unescaped — 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
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 7 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 15 finding(s)
- TodoComment androidApp/src/main/java/hr/dtakac/prognoza/PrognozaApplication.kt:26
- TodoComment androidApp/src/main/java/hr/dtakac/prognoza/widget/ForecastWidgetWorker.kt:57
- Swallowed exception (empty catch) shared/src/commonMain/kotlin/hr/dtakac/prognoza/shared/data/openmeteo/OpenMeteoForecastProvider.kt:76
- Swallowed exception (empty catch) androidApp/src/main/java/hr/dtakac/prognoza/ui/common/Util.kt:10
- OpenMeteoResponseKt.mapWmoCodeToDescription (cyclomatic 45) shared/src/commonMain/kotlin/hr/dtakac/prognoza/shared/data/openmeteo/network/OpenMeteoResponse.kt:103
- ThemeKt.getByMood (cognitive 19) androidApp/src/main/java/hr/dtakac/prognoza/ui/theme/Theme.kt:103
- OpenMeteoResponseKt.mapWmoCodeToDescription (cognitive 18) shared/src/commonMain/kotlin/hr/dtakac/prognoza/shared/data/openmeteo/network/OpenMeteoResponse.kt:103
- ComingDayKt.ComingDay (cognitive 18) androidApp/src/main/java/hr/dtakac/prognoza/ui/forecast/ComingDay.kt:45
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) androidApp/src/main/java/hr/dtakac/prognoza/ui/forecast/ComingDay.kt:188
- Repository declared end-of-life README.md:1
- No structured logging
- Swallowed exception (caught, then discarded) shared/src/commonMain/kotlin/hr/dtakac/prognoza/shared/data/openmeteo/OpenMeteoForecastProvider.kt:40
Minor — 10 finding(s)
- Documentation: no build, run or usage example README.md:1
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- No release approval gate
Minor — 1 finding(s)
- Off the main sequence: :shared
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b0a0e647372444658a977a8c8ac99518/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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b0a0e647372444658a977a8c8ac99518/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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 8 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| 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. | 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 | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |