Executive summary
brewkits/Grant falls short of our standard for production because we found no logging, tracing or health checks in the code. It scores 61 out of 100 and is rated Adequate, and 67 of its 72 critical findings are security problems.
Production Readiness, at 44, is the weakest lens and counts most in the score. The best first step is adding a diagnostic log, worth about 8 points. Documenting the recovery plan comes next, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 73.
Fifty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Six known security holes in the packages the code depends on can be used by attackers, and two secrets can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting each secret to its own step would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once. The three tests the project itself marks as unreliable need fixing or deleting.
The product code is 12,878 lines, about €34,000 to rebuild.
If Production Readiness rose from 44 to 70, the lowest score rated Strong, the score would rise from 61 to about 73.
New since the last survey: 26 findings
- God Classes · TooManyMethods: PlatformGrantDelegate grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt
- God Classes · FileTooLong: impl/PlatformGrantDelegate.android.kt grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt
- Coupling · Off the main sequence: KMPGrant:grant-testing
- Coupling · Off the main sequence: KMPGrant:grant-core
- Test Reliability · Test declared unreliable: testA_RequestSinglePermission_alreadyGranted grant-core/src/androidInstrumentedTest/kotlin/dev/brewkits/grant/impl/GrantRequestActivityTest.kt
- Test Reliability · Test declared unreliable: testRequestMultiplePermissions grant-core/src/androidInstrumentedTest/kotlin/dev/brewkits/grant/impl/GrantRequestActivityTest.kt
- Test Reliability · Test declared unreliable: testEmptyPermissionList grant-core/src/androidInstrumentedTest/kotlin/dev/brewkits/grant/impl/GrantRequestActivityTest.kt
- Churn × Complexity Hotspots · Repeated repair: grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/GrantRequestActivity.kt grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/GrantRequestActivity.kt
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 13 findings
- Code Duplication · Duplicated block (9 lines × 2) grant-core/src/iosMain/kotlin/dev/brewkits/grant/delegates/LocationManagerDelegate.kt
- Code Duplication · Duplicated block (8 lines × 2) grant-core/src/iosMain/kotlin/dev/brewkits/grant/delegates/LocationManagerDelegate.kt
- Coupling · Off the main sequence: :grant-testing
- Coupling · Off the main sequence: :grant-core
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Exception handling · Swallowed exception (caught, then discarded) grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformServiceDelegate.android.kt
- Exception handling · Swallowed exception (caught, then discarded) grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformServiceDelegate.android.kt
- Exception handling · Swallowed exception (caught, then discarded) grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformServiceDelegate.android.kt
- Exception handling · Swallowed exception (caught, then discarded) grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformServiceDelegate.android.kt
- Exception handling · Swallowed exception (caught, then discarded) grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformServiceDelegate.android.kt
- Exception handling · Swallowed exception (caught, then discarded) grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformServiceDelegate.android.kt
- Exception handling · Swallowed exception (caught, then discarded) grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformServiceDelegate.android.kt
- Exception handling · Swallowed exception (caught, then discarded) grant-core/src/androidMain/kotlin/dev/brewkits/grant/util/ManifestValidator.kt
Rebuild cost: about €34,000 · Estimate
| Cost to rebuild | €11,000 to €57,000, for 189 to 600 hours of work, about 0.2 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.8 at a score of 61. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 12,878 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 (global) | 2 dev.brewkits.grant.GrantAndServiceHandler | 3 dev.brewkits.grant.GrantHandler | 4 dev.brewkits.grant.SharedPreferencesGrantStore | 5 dev.brewkits.grant.impl.GrantRequestActivity | 6 dev.brewkits.grant.impl.SimpleGrantManager | 7 dev.brewkits.grant.utils.GrantLogger | 8 dev.brewkits.grant.GrantHandler.UiStrategy | 9 dev.brewkits.grant.delegates | 10 dev.brewkits.grant.impl.GrantRequestActivity.GrantResult | 11 dev.brewkits.grant.impl.SimpleGrantManager.SimulationMode | 12 dev.brewkits.grant.utils | 13 dev.brewkits.grant.utils.GrantLogger.LogLevel | 14 dev.brewkits.grant.handlers | 15 dev.brewkits.grant.handlers.AVPermissionHandler | 16 dev.brewkits.grant.impl | 17 dev.brewkits.grant | 18 dev.brewkits.grant.impl.AndroidGrantLauncher | 19 com.yourapp.location | 20 dev.brewkits.grant.AppGrant | 21 dev.brewkits.grant.BluetoothReadyStatus | 22 dev.brewkits.grant.GrantFactory | 23 dev.brewkits.grant.GrantHandler.FlowState | 24 dev.brewkits.grant.GrantStatus | 25 dev.brewkits.grant.LocationReadyStatus | 26 dev.brewkits.grant.ServiceStatus | 27 dev.brewkits.grant.ServiceType | 28 dev.brewkits.grant.compose | 29 dev.brewkits.grant.desktop | 30 dev.brewkits.grant.di | 31 dev.brewkits.grant.di.ServiceManagerProvider | 32 dev.brewkits.grant.testing | 33 dev.brewkits.grant.util | 34 com.yourapp.location.LocationFlowResult | 35 dev.brewkits.grant.compose.DialogKind | 36 dev.brewkits.grant.compose.ServiceDialogKind | 37 dev.brewkits.grant.desktop.AVMediaPermissionHandler | 38 dev.brewkits.grant.desktop.WindowsPrivacyHandler | 39 dev.brewkits.grant.desktop.WindowsPrivacyStatus | 40 dev.brewkits.grant.util.ValidationResult |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 dev.brewkits.grant.GrantAndServiceHandler | ||||||||||||||||||||||||||||||||||||||||
| 3 dev.brewkits.grant.GrantHandler | ||||||||||||||||||||||||||||||||||||||||
| 4 dev.brewkits.grant.SharedPreferencesGrantStore | ||||||||||||||||||||||||||||||||||||||||
| 5 dev.brewkits.grant.impl.GrantRequestActivity | ||||||||||||||||||||||||||||||||||||||||
| 6 dev.brewkits.grant.impl.SimpleGrantManager | ||||||||||||||||||||||||||||||||||||||||
| 7 dev.brewkits.grant.utils.GrantLogger | ||||||||||||||||||||||||||||||||||||||||
| 8 dev.brewkits.grant.GrantHandler.UiStrategy | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 dev.brewkits.grant.delegates | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 dev.brewkits.grant.impl.GrantRequestActivity.GrantResult | 4 | |||||||||||||||||||||||||||||||||||||||
| 11 dev.brewkits.grant.impl.SimpleGrantManager.SimulationMode | 4 | |||||||||||||||||||||||||||||||||||||||
| 12 dev.brewkits.grant.utils | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 dev.brewkits.grant.utils.GrantLogger.LogLevel | 4 | |||||||||||||||||||||||||||||||||||||||
| 14 dev.brewkits.grant.handlers | 4 | 17 | ||||||||||||||||||||||||||||||||||||||
| 15 dev.brewkits.grant.handlers.AVPermissionHandler | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 dev.brewkits.grant.impl | 2 | 1 | 1 | 4 | 25 | |||||||||||||||||||||||||||||||||||
| 17 dev.brewkits.grant | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 dev.brewkits.grant.impl.AndroidGrantLauncher | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 com.yourapp.location | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 dev.brewkits.grant.AppGrant | 24 | |||||||||||||||||||||||||||||||||||||||
| 21 dev.brewkits.grant.BluetoothReadyStatus | 7 | |||||||||||||||||||||||||||||||||||||||
| 22 dev.brewkits.grant.GrantFactory | 4 | 4 | ||||||||||||||||||||||||||||||||||||||
| 23 dev.brewkits.grant.GrantHandler.FlowState | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 dev.brewkits.grant.GrantStatus | 6 | |||||||||||||||||||||||||||||||||||||||
| 25 dev.brewkits.grant.LocationReadyStatus | 7 | |||||||||||||||||||||||||||||||||||||||
| 26 dev.brewkits.grant.ServiceStatus | 4 | |||||||||||||||||||||||||||||||||||||||
| 27 dev.brewkits.grant.ServiceType | 6 | |||||||||||||||||||||||||||||||||||||||
| 28 dev.brewkits.grant.compose | 8 | |||||||||||||||||||||||||||||||||||||||
| 29 dev.brewkits.grant.desktop | 2 | 6 | ||||||||||||||||||||||||||||||||||||||
| 30 dev.brewkits.grant.di | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 dev.brewkits.grant.di.ServiceManagerProvider | 2 | |||||||||||||||||||||||||||||||||||||||
| 32 dev.brewkits.grant.testing | 14 | |||||||||||||||||||||||||||||||||||||||
| 33 dev.brewkits.grant.util | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 com.yourapp.location.LocationFlowResult | 4 | |||||||||||||||||||||||||||||||||||||||
| 35 dev.brewkits.grant.compose.DialogKind | 3 | |||||||||||||||||||||||||||||||||||||||
| 36 dev.brewkits.grant.compose.ServiceDialogKind | 4 | |||||||||||||||||||||||||||||||||||||||
| 37 dev.brewkits.grant.desktop.AVMediaPermissionHandler | 2 | |||||||||||||||||||||||||||||||||||||||
| 38 dev.brewkits.grant.desktop.WindowsPrivacyHandler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 dev.brewkits.grant.desktop.WindowsPrivacyStatus | 5 | |||||||||||||||||||||||||||||||||||||||
| 40 dev.brewkits.grant.util.ValidationResult | 2 |
8→3 dev.brewkits.grant.GrantHandler.UiStrategy uses dev.brewkits.grant.GrantHandler✕
- Connections
- 2 pairs of types, where a type in dev.brewkits.grant.GrantHandler.UiStrategy uses a type in dev.brewkits.grant.GrantHandler.
- The types involved
dev.brewkits.grant.GrantHandler.UiStrategy.CustomUi→dev.brewkits.grant.GrantHandler.UiStrategydev.brewkits.grant.GrantHandler.UiStrategy.StateBased→dev.brewkits.grant.GrantHandler.UiStrategy
- Direction
- dev.brewkits.grant.GrantHandler.UiStrategy uses dev.brewkits.grant.GrantHandler, so a change to dev.brewkits.grant.GrantHandler can break dev.brewkits.grant.GrantHandler.UiStrategy, while a change to dev.brewkits.grant.GrantHandler.UiStrategy can't break dev.brewkits.grant.GrantHandler.
- Position
- Below the diagonal: dev.brewkits.grant.GrantHandler.UiStrategy uses a module listed above it, which is the healthy direction.
9→17 dev.brewkits.grant.delegates uses dev.brewkits.grant part of a loop✕
- Connections
- 1 pair of types, where a type in dev.brewkits.grant.delegates uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.delegates.BluetoothManagerDelegate→dev.brewkits.grant.GrantStatus
- Direction
- dev.brewkits.grant.delegates uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.delegates, while a change to dev.brewkits.grant.delegates can't break dev.brewkits.grant.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→5 dev.brewkits.grant.impl.GrantRequestActivity.GrantResult uses dev.brewkits.grant.impl.GrantRequestActivity✕
- Connections
- 4 pairs of types, where a type in dev.brewkits.grant.impl.GrantRequestActivity.GrantResult uses a type in dev.brewkits.grant.impl.GrantRequestActivity.
- The types involved
dev.brewkits.grant.impl.GrantRequestActivity.GrantResult.DENIED→dev.brewkits.grant.impl.GrantRequestActivity.GrantResultdev.brewkits.grant.impl.GrantRequestActivity.GrantResult.DENIED_PERMANENTLY→dev.brewkits.grant.impl.GrantRequestActivity.GrantResultdev.brewkits.grant.impl.GrantRequestActivity.GrantResult.ERROR→dev.brewkits.grant.impl.GrantRequestActivity.GrantResultdev.brewkits.grant.impl.GrantRequestActivity.GrantResult.GRANTED→dev.brewkits.grant.impl.GrantRequestActivity.GrantResult
- Direction
- dev.brewkits.grant.impl.GrantRequestActivity.GrantResult uses dev.brewkits.grant.impl.GrantRequestActivity, so a change to dev.brewkits.grant.impl.GrantRequestActivity can break dev.brewkits.grant.impl.GrantRequestActivity.GrantResult, while a change to dev.brewkits.grant.impl.GrantRequestActivity.GrantResult can't break dev.brewkits.grant.impl.GrantRequestActivity.
- Position
- Below the diagonal: dev.brewkits.grant.impl.GrantRequestActivity.GrantResult uses a module listed above it, which is the healthy direction.
11→6 dev.brewkits.grant.impl.SimpleGrantManager.SimulationMode uses dev.brewkits.grant.impl.SimpleGrantManager✕
- Connections
- 4 pairs of types, where a type in dev.brewkits.grant.impl.SimpleGrantManager.SimulationMode uses a type in dev.brewkits.grant.impl.SimpleGrantManager.
- The types involved
dev.brewkits.grant.impl.SimpleGrantManager.SimulationMode.ALWAYS_DENY→dev.brewkits.grant.impl.SimpleGrantManager.SimulationModedev.brewkits.grant.impl.SimpleGrantManager.SimulationMode.ALWAYS_DENY_PERMANENTLY→dev.brewkits.grant.impl.SimpleGrantManager.SimulationModedev.brewkits.grant.impl.SimpleGrantManager.SimulationMode.AUTO_GRANT→dev.brewkits.grant.impl.SimpleGrantManager.SimulationModedev.brewkits.grant.impl.SimpleGrantManager.SimulationMode.REALISTIC→dev.brewkits.grant.impl.SimpleGrantManager.SimulationMode
- Direction
- dev.brewkits.grant.impl.SimpleGrantManager.SimulationMode uses dev.brewkits.grant.impl.SimpleGrantManager, so a change to dev.brewkits.grant.impl.SimpleGrantManager can break dev.brewkits.grant.impl.SimpleGrantManager.SimulationMode, while a change to dev.brewkits.grant.impl.SimpleGrantManager.SimulationMode can't break dev.brewkits.grant.impl.SimpleGrantManager.
- Position
- Below the diagonal: dev.brewkits.grant.impl.SimpleGrantManager.SimulationMode uses a module listed above it, which is the healthy direction.
12→7 dev.brewkits.grant.utils uses dev.brewkits.grant.utils.GrantLogger✕
- Connections
- 1 pair of types, where a type in dev.brewkits.grant.utils uses a type in dev.brewkits.grant.utils.GrantLogger.
- The types involved
dev.brewkits.grant.utils.GrantLogger→dev.brewkits.grant.utils.GrantLogger.LogLevel
- Direction
- dev.brewkits.grant.utils uses dev.brewkits.grant.utils.GrantLogger, so a change to dev.brewkits.grant.utils.GrantLogger can break dev.brewkits.grant.utils, while a change to dev.brewkits.grant.utils can't break dev.brewkits.grant.utils.GrantLogger.
- Position
- Below the diagonal: dev.brewkits.grant.utils uses a module listed above it, which is the healthy direction.
13→7 dev.brewkits.grant.utils.GrantLogger.LogLevel uses dev.brewkits.grant.utils.GrantLogger✕
- Connections
- 4 pairs of types, where a type in dev.brewkits.grant.utils.GrantLogger.LogLevel uses a type in dev.brewkits.grant.utils.GrantLogger.
- The types involved
dev.brewkits.grant.utils.GrantLogger.LogLevel.DEBUG→dev.brewkits.grant.utils.GrantLogger.LogLeveldev.brewkits.grant.utils.GrantLogger.LogLevel.ERROR→dev.brewkits.grant.utils.GrantLogger.LogLeveldev.brewkits.grant.utils.GrantLogger.LogLevel.INFO→dev.brewkits.grant.utils.GrantLogger.LogLeveldev.brewkits.grant.utils.GrantLogger.LogLevel.WARNING→dev.brewkits.grant.utils.GrantLogger.LogLevel
- Direction
- dev.brewkits.grant.utils.GrantLogger.LogLevel uses dev.brewkits.grant.utils.GrantLogger, so a change to dev.brewkits.grant.utils.GrantLogger can break dev.brewkits.grant.utils.GrantLogger.LogLevel, while a change to dev.brewkits.grant.utils.GrantLogger.LogLevel can't break dev.brewkits.grant.utils.GrantLogger.
- Position
- Below the diagonal: dev.brewkits.grant.utils.GrantLogger.LogLevel uses a module listed above it, which is the healthy direction.
14→9 dev.brewkits.grant.handlers uses dev.brewkits.grant.delegates✕
- Connections
- 4 pairs of types, where a type in dev.brewkits.grant.handlers uses a type in dev.brewkits.grant.delegates.
- The types involved
dev.brewkits.grant.handlers.BluetoothPermissionHandler→dev.brewkits.grant.delegates.BluetoothManagerDelegatedev.brewkits.grant.handlers.LocationAlwaysPermissionHandler→dev.brewkits.grant.delegates.LocationAlwaysManagerDelegatedev.brewkits.grant.handlers.LocationPermissionHandler→dev.brewkits.grant.delegates.LocationManagerDelegatedev.brewkits.grant.handlers.LocationTemporaryFullAccuracyHandler→dev.brewkits.grant.delegates.LocationManagerDelegate
- Direction
- dev.brewkits.grant.handlers uses dev.brewkits.grant.delegates, so a change to dev.brewkits.grant.delegates can break dev.brewkits.grant.handlers, while a change to dev.brewkits.grant.handlers can't break dev.brewkits.grant.delegates.
- Position
- Below the diagonal: dev.brewkits.grant.handlers uses a module listed above it, which is the healthy direction.
14→17 dev.brewkits.grant.handlers uses dev.brewkits.grant part of a loop✕
- Connections
- 17 pairs of types, where a type in dev.brewkits.grant.handlers uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.handlers.AVPermissionHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.handlers.BluetoothPermissionHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.handlers.CalendarPermissionHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.handlers.ContactsPermissionHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.handlers.DesktopPermissionHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.handlers.DesktopPermissionHandlerRegistry→dev.brewkits.grant.GrantPermissiondev.brewkits.grant.handlers.LocationAlwaysPermissionHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.handlers.LocationAlwaysPermissionHandlerKt→dev.brewkits.grant.GrantStatusdev.brewkits.grant.handlers.LocationPermissionHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.handlers.LocationPermissionHandlerKt→dev.brewkits.grant.GrantStatusdev.brewkits.grant.handlers.LocationTemporaryFullAccuracyHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.handlers.MotionPermissionHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.handlers.NotificationPermissionHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.handlers.NotificationPermissionHandlerKt→dev.brewkits.grant.GrantStatusdev.brewkits.grant.handlers.PermissionHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.handlers.PhotoPermissionHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.handlers.TrackingPermissionHandler→dev.brewkits.grant.GrantStatus
- Direction
- dev.brewkits.grant.handlers uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.handlers, while a change to dev.brewkits.grant.handlers can't break dev.brewkits.grant.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→14 dev.brewkits.grant.handlers.AVPermissionHandler uses dev.brewkits.grant.handlers✕
- Connections
- 1 pair of types, where a type in dev.brewkits.grant.handlers.AVPermissionHandler uses a type in dev.brewkits.grant.handlers.
- The types involved
dev.brewkits.grant.handlers.AVPermissionHandler.Companion→dev.brewkits.grant.handlers.AVPermissionHandler
- Direction
- dev.brewkits.grant.handlers.AVPermissionHandler uses dev.brewkits.grant.handlers, so a change to dev.brewkits.grant.handlers can break dev.brewkits.grant.handlers.AVPermissionHandler, while a change to dev.brewkits.grant.handlers.AVPermissionHandler can't break dev.brewkits.grant.handlers.
- Position
- Below the diagonal: dev.brewkits.grant.handlers.AVPermissionHandler uses a module listed above it, which is the healthy direction.
16→5 dev.brewkits.grant.impl uses dev.brewkits.grant.impl.GrantRequestActivity✕
- Connections
- 2 pairs of types, where a type in dev.brewkits.grant.impl uses a type in dev.brewkits.grant.impl.GrantRequestActivity.
- The types involved
dev.brewkits.grant.impl.GrantRequestActivity→dev.brewkits.grant.impl.GrantRequestActivity.GrantResultdev.brewkits.grant.impl.PlatformGrantDelegate→dev.brewkits.grant.impl.GrantRequestActivity.GrantResult
- Direction
- dev.brewkits.grant.impl uses dev.brewkits.grant.impl.GrantRequestActivity, so a change to dev.brewkits.grant.impl.GrantRequestActivity can break dev.brewkits.grant.impl, while a change to dev.brewkits.grant.impl can't break dev.brewkits.grant.impl.GrantRequestActivity.
- Position
- Below the diagonal: dev.brewkits.grant.impl uses a module listed above it, which is the healthy direction.
16→6 dev.brewkits.grant.impl uses dev.brewkits.grant.impl.SimpleGrantManager✕
- Connections
- 1 pair of types, where a type in dev.brewkits.grant.impl uses a type in dev.brewkits.grant.impl.SimpleGrantManager.
- The types involved
dev.brewkits.grant.impl.SimpleGrantManager→dev.brewkits.grant.impl.SimpleGrantManager.SimulationMode
- Direction
- dev.brewkits.grant.impl uses dev.brewkits.grant.impl.SimpleGrantManager, so a change to dev.brewkits.grant.impl.SimpleGrantManager can break dev.brewkits.grant.impl, while a change to dev.brewkits.grant.impl can't break dev.brewkits.grant.impl.SimpleGrantManager.
- Position
- Below the diagonal: dev.brewkits.grant.impl uses a module listed above it, which is the healthy direction.
16→12 dev.brewkits.grant.impl uses dev.brewkits.grant.utils✕
- Connections
- 1 pair of types, where a type in dev.brewkits.grant.impl uses a type in dev.brewkits.grant.utils.
- The types involved
dev.brewkits.grant.impl.PlatformGrantDelegate→dev.brewkits.grant.utils.ReentrantMutex
- Direction
- dev.brewkits.grant.impl uses dev.brewkits.grant.utils, so a change to dev.brewkits.grant.utils can break dev.brewkits.grant.impl, while a change to dev.brewkits.grant.impl can't break dev.brewkits.grant.utils.
- Position
- Below the diagonal: dev.brewkits.grant.impl uses a module listed above it, which is the healthy direction.
16→14 dev.brewkits.grant.impl uses dev.brewkits.grant.handlers✕
- Connections
- 4 pairs of types, where a type in dev.brewkits.grant.impl uses a type in dev.brewkits.grant.handlers.
- The types involved
dev.brewkits.grant.impl.AlwaysGrantedHandler→dev.brewkits.grant.handlers.PermissionHandlerdev.brewkits.grant.impl.ExactAlarmHandler→dev.brewkits.grant.handlers.PermissionHandlerdev.brewkits.grant.impl.LocalNetworkHandler→dev.brewkits.grant.handlers.PermissionHandlerdev.brewkits.grant.impl.NotRegisteredHandler→dev.brewkits.grant.handlers.PermissionHandler
- Direction
- dev.brewkits.grant.impl uses dev.brewkits.grant.handlers, so a change to dev.brewkits.grant.handlers can break dev.brewkits.grant.impl, while a change to dev.brewkits.grant.impl can't break dev.brewkits.grant.handlers.
- Position
- Below the diagonal: dev.brewkits.grant.impl uses a module listed above it, which is the healthy direction.
16→17 dev.brewkits.grant.impl uses dev.brewkits.grant part of a loop✕
- Connections
- 25 pairs of types, where a type in dev.brewkits.grant.impl uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.impl.AlwaysGrantedHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.impl.AndroidGrantLauncher→dev.brewkits.grant.GrantLauncherdev.brewkits.grant.impl.DefaultGrantManager→dev.brewkits.grant.GrantLauncherdev.brewkits.grant.impl.DefaultGrantManager→dev.brewkits.grant.GrantManagerdev.brewkits.grant.impl.DefaultGrantManager→dev.brewkits.grant.GrantPermissiondev.brewkits.grant.impl.DefaultGrantManager→dev.brewkits.grant.GrantStatusdev.brewkits.grant.impl.ExactAlarmHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.impl.LocalNetworkHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.impl.MyServiceManager→dev.brewkits.grant.ServiceManagerdev.brewkits.grant.impl.MyServiceManager→dev.brewkits.grant.ServiceStatusdev.brewkits.grant.impl.MyServiceManager→dev.brewkits.grant.ServiceTypedev.brewkits.grant.impl.NotRegisteredHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.impl.PlatformGrantDelegate→dev.brewkits.grant.AppGrantdev.brewkits.grant.impl.PlatformGrantDelegate→dev.brewkits.grant.GrantLauncherdev.brewkits.grant.impl.PlatformGrantDelegate→dev.brewkits.grant.GrantPermissiondev.brewkits.grant.impl.PlatformGrantDelegate→dev.brewkits.grant.GrantStatusdev.brewkits.grant.impl.PlatformGrantDelegate→dev.brewkits.grant.GrantStoredev.brewkits.grant.impl.PlatformGrantDelegate→dev.brewkits.grant.RawPermissiondev.brewkits.grant.impl.PlatformServiceDelegate→dev.brewkits.grant.ServiceStatusdev.brewkits.grant.impl.PlatformServiceDelegate→dev.brewkits.grant.ServiceTypedev.brewkits.grant.impl.SimpleGrantManager→dev.brewkits.grant.AppGrantdev.brewkits.grant.impl.SimpleGrantManager→dev.brewkits.grant.GrantLauncherdev.brewkits.grant.impl.SimpleGrantManager→dev.brewkits.grant.GrantManagerdev.brewkits.grant.impl.SimpleGrantManager→dev.brewkits.grant.GrantPermissiondev.brewkits.grant.impl.SimpleGrantManager→dev.brewkits.grant.GrantStatus
- Direction
- dev.brewkits.grant.impl uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.impl, while a change to dev.brewkits.grant.impl can't break dev.brewkits.grant.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→3 dev.brewkits.grant uses dev.brewkits.grant.GrantHandler✕
- Connections
- 1 pair of types, where a type in dev.brewkits.grant uses a type in dev.brewkits.grant.GrantHandler.
- The types involved
dev.brewkits.grant.GrantHandler→dev.brewkits.grant.GrantHandler.UiStrategy
- Direction
- dev.brewkits.grant uses dev.brewkits.grant.GrantHandler, so a change to dev.brewkits.grant.GrantHandler can break dev.brewkits.grant, while a change to dev.brewkits.grant can't break dev.brewkits.grant.GrantHandler.
- Position
- Below the diagonal: dev.brewkits.grant uses a module listed above it, which is the healthy direction.
17→12 dev.brewkits.grant uses dev.brewkits.grant.utils✕
- Connections
- 2 pairs of types, where a type in dev.brewkits.grant uses a type in dev.brewkits.grant.utils.
- The types involved
dev.brewkits.grant.InMemoryGrantStore→dev.brewkits.grant.utils.PlatformLockdev.brewkits.grant.SharedPreferencesGrantStore→dev.brewkits.grant.utils.PlatformLock
- Direction
- dev.brewkits.grant uses dev.brewkits.grant.utils, so a change to dev.brewkits.grant.utils can break dev.brewkits.grant, while a change to dev.brewkits.grant can't break dev.brewkits.grant.utils.
- Position
- Below the diagonal: dev.brewkits.grant uses a module listed above it, which is the healthy direction.
17→16 dev.brewkits.grant uses dev.brewkits.grant.impl✕
- Connections
- 1 pair of types, where a type in dev.brewkits.grant uses a type in dev.brewkits.grant.impl.
- The types involved
dev.brewkits.grant.GrantFactoryKt→dev.brewkits.grant.impl.PlatformGrantDelegate
- Direction
- dev.brewkits.grant uses dev.brewkits.grant.impl, so a change to dev.brewkits.grant.impl can break dev.brewkits.grant, while a change to dev.brewkits.grant can't break dev.brewkits.grant.impl.
- Position
- Below the diagonal: dev.brewkits.grant uses a module listed above it, which is the healthy direction.
18→16 dev.brewkits.grant.impl.AndroidGrantLauncher uses dev.brewkits.grant.impl✕
- Connections
- 1 pair of types, where a type in dev.brewkits.grant.impl.AndroidGrantLauncher uses a type in dev.brewkits.grant.impl.
- The types involved
dev.brewkits.grant.impl.AndroidGrantLauncher.Companion→dev.brewkits.grant.impl.AndroidGrantLauncher
- Direction
- dev.brewkits.grant.impl.AndroidGrantLauncher uses dev.brewkits.grant.impl, so a change to dev.brewkits.grant.impl can break dev.brewkits.grant.impl.AndroidGrantLauncher, while a change to dev.brewkits.grant.impl.AndroidGrantLauncher can't break dev.brewkits.grant.impl.
- Position
- Below the diagonal: dev.brewkits.grant.impl.AndroidGrantLauncher uses a module listed above it, which is the healthy direction.
19→17 com.yourapp.location uses dev.brewkits.grant✕
- Connections
- 2 pairs of types, where a type in com.yourapp.location uses a type in dev.brewkits.grant.
- The types involved
com.yourapp.location.LocationPermissionHelper→dev.brewkits.grant.GrantManagercom.yourapp.location.LocationPermissionHelper→dev.brewkits.grant.ServiceManager
- Direction
- com.yourapp.location uses dev.brewkits.grant, so a change to dev.brewkits.grant can break com.yourapp.location, while a change to com.yourapp.location can't break dev.brewkits.grant.
- Position
- Below the diagonal: com.yourapp.location uses a module listed above it, which is the healthy direction.
20→17 dev.brewkits.grant.AppGrant uses dev.brewkits.grant✕
- Connections
- 24 pairs of types, where a type in dev.brewkits.grant.AppGrant uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.AppGrant.APP_TRACKING→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.BLUETOOTH→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.BLUETOOTH_ADVERTISE→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.BLUETOOTH_CONNECT→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.BLUETOOTH_SCAN→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.CALENDAR→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.CAMERA→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.CONTACTS→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.GALLERY→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.GALLERY_ADD_ONLY→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.GALLERY_IMAGES_ONLY→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.GALLERY_VIDEO_ONLY→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.LOCAL_NETWORK→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.LOCATION→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.LOCATION_ALWAYS→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.MICROPHONE→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.MOTION→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.NEARBY_WIFI_DEVICES→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.NOTIFICATION→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.READ_CALENDAR→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.READ_CONTACTS→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.SCHEDULE_EXACT_ALARM→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.STORAGE→dev.brewkits.grant.AppGrantdev.brewkits.grant.AppGrant.USE_FULL_SCREEN_INTENT→dev.brewkits.grant.AppGrant
- Direction
- dev.brewkits.grant.AppGrant uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.AppGrant, while a change to dev.brewkits.grant.AppGrant can't break dev.brewkits.grant.
- Position
- Below the diagonal: dev.brewkits.grant.AppGrant uses a module listed above it, which is the healthy direction.
21→17 dev.brewkits.grant.BluetoothReadyStatus uses dev.brewkits.grant✕
- Connections
- 7 pairs of types, where a type in dev.brewkits.grant.BluetoothReadyStatus uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.BluetoothReadyStatus.BothRequired→dev.brewkits.grant.BluetoothReadyStatusdev.brewkits.grant.BluetoothReadyStatus.BothRequired→dev.brewkits.grant.GrantStatusdev.brewkits.grant.BluetoothReadyStatus.GrantDenied→dev.brewkits.grant.BluetoothReadyStatusdev.brewkits.grant.BluetoothReadyStatus.GrantDenied→dev.brewkits.grant.GrantStatusdev.brewkits.grant.BluetoothReadyStatus.Ready→dev.brewkits.grant.BluetoothReadyStatusdev.brewkits.grant.BluetoothReadyStatus.ServiceDisabled→dev.brewkits.grant.BluetoothReadyStatusdev.brewkits.grant.BluetoothReadyStatus.Unknown→dev.brewkits.grant.BluetoothReadyStatus
- Direction
- dev.brewkits.grant.BluetoothReadyStatus uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.BluetoothReadyStatus, while a change to dev.brewkits.grant.BluetoothReadyStatus can't break dev.brewkits.grant.
- Position
- Below the diagonal: dev.brewkits.grant.BluetoothReadyStatus uses a module listed above it, which is the healthy direction.
22→16 dev.brewkits.grant.GrantFactory uses dev.brewkits.grant.impl✕
- Connections
- 4 pairs of types, where a type in dev.brewkits.grant.GrantFactory uses a type in dev.brewkits.grant.impl.
- The types involved
dev.brewkits.grant.GrantFactory.androidKt→dev.brewkits.grant.impl.PlatformGrantDelegatedev.brewkits.grant.GrantFactory.iosKt→dev.brewkits.grant.impl.PlatformGrantDelegatedev.brewkits.grant.GrantFactory.jvmKt→dev.brewkits.grant.impl.PlatformGrantDelegatedev.brewkits.grant.GrantFactory.webKt→dev.brewkits.grant.impl.PlatformGrantDelegate
- Direction
- dev.brewkits.grant.GrantFactory uses dev.brewkits.grant.impl, so a change to dev.brewkits.grant.impl can break dev.brewkits.grant.GrantFactory, while a change to dev.brewkits.grant.GrantFactory can't break dev.brewkits.grant.impl.
- Position
- Below the diagonal: dev.brewkits.grant.GrantFactory uses a module listed above it, which is the healthy direction.
22→17 dev.brewkits.grant.GrantFactory uses dev.brewkits.grant✕
- Connections
- 4 pairs of types, where a type in dev.brewkits.grant.GrantFactory uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.GrantFactory.androidKt→dev.brewkits.grant.GrantStoredev.brewkits.grant.GrantFactory.iosKt→dev.brewkits.grant.GrantStoredev.brewkits.grant.GrantFactory.jvmKt→dev.brewkits.grant.GrantStoredev.brewkits.grant.GrantFactory.webKt→dev.brewkits.grant.GrantStore
- Direction
- dev.brewkits.grant.GrantFactory uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.GrantFactory, while a change to dev.brewkits.grant.GrantFactory can't break dev.brewkits.grant.
- Position
- Below the diagonal: dev.brewkits.grant.GrantFactory uses a module listed above it, which is the healthy direction.
23→3 dev.brewkits.grant.GrantHandler.FlowState uses dev.brewkits.grant.GrantHandler✕
- Connections
- 3 pairs of types, where a type in dev.brewkits.grant.GrantHandler.FlowState uses a type in dev.brewkits.grant.GrantHandler.
- The types involved
dev.brewkits.grant.GrantHandler.FlowState.Check→dev.brewkits.grant.GrantHandler.FlowStatedev.brewkits.grant.GrantHandler.FlowState.Done→dev.brewkits.grant.GrantHandler.FlowStatedev.brewkits.grant.GrantHandler.FlowState.HandleResult→dev.brewkits.grant.GrantHandler.FlowState
- Direction
- dev.brewkits.grant.GrantHandler.FlowState uses dev.brewkits.grant.GrantHandler, so a change to dev.brewkits.grant.GrantHandler can break dev.brewkits.grant.GrantHandler.FlowState, while a change to dev.brewkits.grant.GrantHandler.FlowState can't break dev.brewkits.grant.GrantHandler.
- Position
- Below the diagonal: dev.brewkits.grant.GrantHandler.FlowState uses a module listed above it, which is the healthy direction.
23→17 dev.brewkits.grant.GrantHandler.FlowState uses dev.brewkits.grant✕
- Connections
- 1 pair of types, where a type in dev.brewkits.grant.GrantHandler.FlowState uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.GrantHandler.FlowState.HandleResult→dev.brewkits.grant.GrantStatus
- Direction
- dev.brewkits.grant.GrantHandler.FlowState uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.GrantHandler.FlowState, while a change to dev.brewkits.grant.GrantHandler.FlowState can't break dev.brewkits.grant.
- Position
- Below the diagonal: dev.brewkits.grant.GrantHandler.FlowState uses a module listed above it, which is the healthy direction.
24→17 dev.brewkits.grant.GrantStatus uses dev.brewkits.grant✕
- Connections
- 6 pairs of types, where a type in dev.brewkits.grant.GrantStatus uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.GrantStatus.BUSY→dev.brewkits.grant.GrantStatusdev.brewkits.grant.GrantStatus.DENIED→dev.brewkits.grant.GrantStatusdev.brewkits.grant.GrantStatus.DENIED_ALWAYS→dev.brewkits.grant.GrantStatusdev.brewkits.grant.GrantStatus.GRANTED→dev.brewkits.grant.GrantStatusdev.brewkits.grant.GrantStatus.NOT_DETERMINED→dev.brewkits.grant.GrantStatusdev.brewkits.grant.GrantStatus.PARTIAL_GRANTED→dev.brewkits.grant.GrantStatus
- Direction
- dev.brewkits.grant.GrantStatus uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.GrantStatus, while a change to dev.brewkits.grant.GrantStatus can't break dev.brewkits.grant.
- Position
- Below the diagonal: dev.brewkits.grant.GrantStatus uses a module listed above it, which is the healthy direction.
25→17 dev.brewkits.grant.LocationReadyStatus uses dev.brewkits.grant✕
- Connections
- 7 pairs of types, where a type in dev.brewkits.grant.LocationReadyStatus uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.LocationReadyStatus.BothRequired→dev.brewkits.grant.GrantStatusdev.brewkits.grant.LocationReadyStatus.BothRequired→dev.brewkits.grant.LocationReadyStatusdev.brewkits.grant.LocationReadyStatus.GrantDenied→dev.brewkits.grant.GrantStatusdev.brewkits.grant.LocationReadyStatus.GrantDenied→dev.brewkits.grant.LocationReadyStatusdev.brewkits.grant.LocationReadyStatus.Ready→dev.brewkits.grant.LocationReadyStatusdev.brewkits.grant.LocationReadyStatus.ServiceDisabled→dev.brewkits.grant.LocationReadyStatusdev.brewkits.grant.LocationReadyStatus.Unknown→dev.brewkits.grant.LocationReadyStatus
- Direction
- dev.brewkits.grant.LocationReadyStatus uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.LocationReadyStatus, while a change to dev.brewkits.grant.LocationReadyStatus can't break dev.brewkits.grant.
- Position
- Below the diagonal: dev.brewkits.grant.LocationReadyStatus uses a module listed above it, which is the healthy direction.
26→17 dev.brewkits.grant.ServiceStatus uses dev.brewkits.grant✕
- Connections
- 4 pairs of types, where a type in dev.brewkits.grant.ServiceStatus uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.ServiceStatus.DISABLED→dev.brewkits.grant.ServiceStatusdev.brewkits.grant.ServiceStatus.ENABLED→dev.brewkits.grant.ServiceStatusdev.brewkits.grant.ServiceStatus.NOT_AVAILABLE→dev.brewkits.grant.ServiceStatusdev.brewkits.grant.ServiceStatus.UNKNOWN→dev.brewkits.grant.ServiceStatus
- Direction
- dev.brewkits.grant.ServiceStatus uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.ServiceStatus, while a change to dev.brewkits.grant.ServiceStatus can't break dev.brewkits.grant.
- Position
- Below the diagonal: dev.brewkits.grant.ServiceStatus uses a module listed above it, which is the healthy direction.
27→17 dev.brewkits.grant.ServiceType uses dev.brewkits.grant✕
- Connections
- 6 pairs of types, where a type in dev.brewkits.grant.ServiceType uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.ServiceType.BLUETOOTH→dev.brewkits.grant.ServiceTypedev.brewkits.grant.ServiceType.CAMERA_HARDWARE→dev.brewkits.grant.ServiceTypedev.brewkits.grant.ServiceType.HEALTH→dev.brewkits.grant.ServiceTypedev.brewkits.grant.ServiceType.LOCATION_GPS→dev.brewkits.grant.ServiceTypedev.brewkits.grant.ServiceType.NFC→dev.brewkits.grant.ServiceTypedev.brewkits.grant.ServiceType.WIFI→dev.brewkits.grant.ServiceType
- Direction
- dev.brewkits.grant.ServiceType uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.ServiceType, while a change to dev.brewkits.grant.ServiceType can't break dev.brewkits.grant.
- Position
- Below the diagonal: dev.brewkits.grant.ServiceType uses a module listed above it, which is the healthy direction.
28→17 dev.brewkits.grant.compose uses dev.brewkits.grant✕
- Connections
- 8 pairs of types, where a type in dev.brewkits.grant.compose uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.compose.GrantComposeExtensionsKt→dev.brewkits.grant.GrantAndServiceUiStatedev.brewkits.grant.compose.GrantComposeExtensionsKt→dev.brewkits.grant.GrantGroupUiStatedev.brewkits.grant.compose.GrantComposeExtensionsKt→dev.brewkits.grant.GrantPermissiondev.brewkits.grant.compose.GrantComposeExtensionsKt→dev.brewkits.grant.GrantStatusdev.brewkits.grant.compose.GrantComposeExtensionsKt→dev.brewkits.grant.GrantUiStatedev.brewkits.grant.compose.GrantDialogsKt→dev.brewkits.grant.GrantAndServiceHandlerdev.brewkits.grant.compose.GrantDialogsKt→dev.brewkits.grant.GrantGroupHandlerdev.brewkits.grant.compose.GrantDialogsKt→dev.brewkits.grant.GrantHandler
- Direction
- dev.brewkits.grant.compose uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.compose, while a change to dev.brewkits.grant.compose can't break dev.brewkits.grant.
- Position
- Below the diagonal: dev.brewkits.grant.compose uses a module listed above it, which is the healthy direction.
29→14 dev.brewkits.grant.desktop uses dev.brewkits.grant.handlers✕
- Connections
- 2 pairs of types, where a type in dev.brewkits.grant.desktop uses a type in dev.brewkits.grant.handlers.
- The types involved
dev.brewkits.grant.desktop.AVMediaPermissionHandler→dev.brewkits.grant.handlers.DesktopPermissionHandlerdev.brewkits.grant.desktop.WindowsPrivacyHandler→dev.brewkits.grant.handlers.DesktopPermissionHandler
- Direction
- dev.brewkits.grant.desktop uses dev.brewkits.grant.handlers, so a change to dev.brewkits.grant.handlers can break dev.brewkits.grant.desktop, while a change to dev.brewkits.grant.desktop can't break dev.brewkits.grant.handlers.
- Position
- Below the diagonal: dev.brewkits.grant.desktop uses a module listed above it, which is the healthy direction.
29→17 dev.brewkits.grant.desktop uses dev.brewkits.grant✕
- Connections
- 6 pairs of types, where a type in dev.brewkits.grant.desktop uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.desktop.AVMediaPermissionHandler→dev.brewkits.grant.GrantStatusdev.brewkits.grant.desktop.GrantDesktop→dev.brewkits.grant.AppGrantdev.brewkits.grant.desktop.GrantDesktop→dev.brewkits.grant.GrantPermissiondev.brewkits.grant.desktop.WindowsPrivacyClient→dev.brewkits.grant.AppGrantdev.brewkits.grant.desktop.WindowsPrivacyHandler→dev.brewkits.grant.AppGrantdev.brewkits.grant.desktop.WindowsPrivacyHandler→dev.brewkits.grant.GrantStatus
- Direction
- dev.brewkits.grant.desktop uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.desktop, while a change to dev.brewkits.grant.desktop can't break dev.brewkits.grant.
- Position
- Below the diagonal: dev.brewkits.grant.desktop uses a module listed above it, which is the healthy direction.
30→17 dev.brewkits.grant.di uses dev.brewkits.grant✕
- Connections
- 1 pair of types, where a type in dev.brewkits.grant.di uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.di.ServiceManagerProviderKt→dev.brewkits.grant.ServiceManager
- Direction
- dev.brewkits.grant.di uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.di, while a change to dev.brewkits.grant.di can't break dev.brewkits.grant.
- Position
- Below the diagonal: dev.brewkits.grant.di uses a module listed above it, which is the healthy direction.
31→17 dev.brewkits.grant.di.ServiceManagerProvider uses dev.brewkits.grant✕
- Connections
- 2 pairs of types, where a type in dev.brewkits.grant.di.ServiceManagerProvider uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.di.ServiceManagerProvider.androidKt→dev.brewkits.grant.ServiceManagerdev.brewkits.grant.di.ServiceManagerProvider.iosKt→dev.brewkits.grant.ServiceManager
- Direction
- dev.brewkits.grant.di.ServiceManagerProvider uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.di.ServiceManagerProvider, while a change to dev.brewkits.grant.di.ServiceManagerProvider can't break dev.brewkits.grant.
- Position
- Below the diagonal: dev.brewkits.grant.di.ServiceManagerProvider uses a module listed above it, which is the healthy direction.
32→17 dev.brewkits.grant.testing uses dev.brewkits.grant✕
- Connections
- 14 pairs of types, where a type in dev.brewkits.grant.testing uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.testing.FakeGrantManager→dev.brewkits.grant.GrantLauncherdev.brewkits.grant.testing.FakeGrantManager→dev.brewkits.grant.GrantManagerdev.brewkits.grant.testing.FakeGrantManager→dev.brewkits.grant.GrantPermissiondev.brewkits.grant.testing.FakeGrantManager→dev.brewkits.grant.GrantStatusdev.brewkits.grant.testing.FakeGrantStore→dev.brewkits.grant.AppGrantdev.brewkits.grant.testing.FakeGrantStore→dev.brewkits.grant.GrantStatusdev.brewkits.grant.testing.FakeGrantStore→dev.brewkits.grant.GrantStoredev.brewkits.grant.testing.FakeServiceManager→dev.brewkits.grant.ServiceManagerdev.brewkits.grant.testing.FakeServiceManager→dev.brewkits.grant.ServiceStatusdev.brewkits.grant.testing.FakeServiceManager→dev.brewkits.grant.ServiceTypedev.brewkits.grant.testing.MultiGrantFakeManager→dev.brewkits.grant.GrantLauncherdev.brewkits.grant.testing.MultiGrantFakeManager→dev.brewkits.grant.GrantManagerdev.brewkits.grant.testing.MultiGrantFakeManager→dev.brewkits.grant.GrantPermissiondev.brewkits.grant.testing.MultiGrantFakeManager→dev.brewkits.grant.GrantStatus
- Direction
- dev.brewkits.grant.testing uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.testing, while a change to dev.brewkits.grant.testing can't break dev.brewkits.grant.
- Position
- Below the diagonal: dev.brewkits.grant.testing uses a module listed above it, which is the healthy direction.
33→17 dev.brewkits.grant.util uses dev.brewkits.grant✕
- Connections
- 1 pair of types, where a type in dev.brewkits.grant.util uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.util.ManifestValidator→dev.brewkits.grant.AppGrant
- Direction
- dev.brewkits.grant.util uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.util, while a change to dev.brewkits.grant.util can't break dev.brewkits.grant.
- Position
- Below the diagonal: dev.brewkits.grant.util uses a module listed above it, which is the healthy direction.
34→19 com.yourapp.location.LocationFlowResult uses com.yourapp.location✕
- Connections
- 4 pairs of types, where a type in com.yourapp.location.LocationFlowResult uses a type in com.yourapp.location.
- The types involved
com.yourapp.location.LocationFlowResult.Error→com.yourapp.location.LocationFlowResultcom.yourapp.location.LocationFlowResult.GpsDisabled→com.yourapp.location.LocationFlowResultcom.yourapp.location.LocationFlowResult.PermissionDenied→com.yourapp.location.LocationFlowResultcom.yourapp.location.LocationFlowResult.Ready→com.yourapp.location.LocationFlowResult
- Direction
- com.yourapp.location.LocationFlowResult uses com.yourapp.location, so a change to com.yourapp.location can break com.yourapp.location.LocationFlowResult, while a change to com.yourapp.location.LocationFlowResult can't break com.yourapp.location.
- Position
- Below the diagonal: com.yourapp.location.LocationFlowResult uses a module listed above it, which is the healthy direction.
35→28 dev.brewkits.grant.compose.DialogKind uses dev.brewkits.grant.compose✕
- Connections
- 3 pairs of types, where a type in dev.brewkits.grant.compose.DialogKind uses a type in dev.brewkits.grant.compose.
- The types involved
dev.brewkits.grant.compose.DialogKind.None→dev.brewkits.grant.compose.DialogKinddev.brewkits.grant.compose.DialogKind.Rationale→dev.brewkits.grant.compose.DialogKinddev.brewkits.grant.compose.DialogKind.Settings→dev.brewkits.grant.compose.DialogKind
- Direction
- dev.brewkits.grant.compose.DialogKind uses dev.brewkits.grant.compose, so a change to dev.brewkits.grant.compose can break dev.brewkits.grant.compose.DialogKind, while a change to dev.brewkits.grant.compose.DialogKind can't break dev.brewkits.grant.compose.
- Position
- Below the diagonal: dev.brewkits.grant.compose.DialogKind uses a module listed above it, which is the healthy direction.
36→28 dev.brewkits.grant.compose.ServiceDialogKind uses dev.brewkits.grant.compose✕
- Connections
- 4 pairs of types, where a type in dev.brewkits.grant.compose.ServiceDialogKind uses a type in dev.brewkits.grant.compose.
- The types involved
dev.brewkits.grant.compose.ServiceDialogKind.None→dev.brewkits.grant.compose.ServiceDialogKinddev.brewkits.grant.compose.ServiceDialogKind.PermissionSettings→dev.brewkits.grant.compose.ServiceDialogKinddev.brewkits.grant.compose.ServiceDialogKind.Rationale→dev.brewkits.grant.compose.ServiceDialogKinddev.brewkits.grant.compose.ServiceDialogKind.ServiceSettings→dev.brewkits.grant.compose.ServiceDialogKind
- Direction
- dev.brewkits.grant.compose.ServiceDialogKind uses dev.brewkits.grant.compose, so a change to dev.brewkits.grant.compose can break dev.brewkits.grant.compose.ServiceDialogKind, while a change to dev.brewkits.grant.compose.ServiceDialogKind can't break dev.brewkits.grant.compose.
- Position
- Below the diagonal: dev.brewkits.grant.compose.ServiceDialogKind uses a module listed above it, which is the healthy direction.
37→29 dev.brewkits.grant.desktop.AVMediaPermissionHandler uses dev.brewkits.grant.desktop✕
- Connections
- 2 pairs of types, where a type in dev.brewkits.grant.desktop.AVMediaPermissionHandler uses a type in dev.brewkits.grant.desktop.
- The types involved
dev.brewkits.grant.desktop.AVMediaPermissionHandler.Companion→dev.brewkits.grant.desktop.AVMediaPermissionHandlerdev.brewkits.grant.desktop.AVMediaPermissionHandler.Companion→dev.brewkits.grant.desktop.GrantDesktopBridgeLibrary
- Direction
- dev.brewkits.grant.desktop.AVMediaPermissionHandler uses dev.brewkits.grant.desktop, so a change to dev.brewkits.grant.desktop can break dev.brewkits.grant.desktop.AVMediaPermissionHandler, while a change to dev.brewkits.grant.desktop.AVMediaPermissionHandler can't break dev.brewkits.grant.desktop.
- Position
- Below the diagonal: dev.brewkits.grant.desktop.AVMediaPermissionHandler uses a module listed above it, which is the healthy direction.
38→17 dev.brewkits.grant.desktop.WindowsPrivacyHandler uses dev.brewkits.grant✕
- Connections
- 1 pair of types, where a type in dev.brewkits.grant.desktop.WindowsPrivacyHandler uses a type in dev.brewkits.grant.
- The types involved
dev.brewkits.grant.desktop.WindowsPrivacyHandler.Companion→dev.brewkits.grant.GrantStatus
- Direction
- dev.brewkits.grant.desktop.WindowsPrivacyHandler uses dev.brewkits.grant, so a change to dev.brewkits.grant can break dev.brewkits.grant.desktop.WindowsPrivacyHandler, while a change to dev.brewkits.grant.desktop.WindowsPrivacyHandler can't break dev.brewkits.grant.
- Position
- Below the diagonal: dev.brewkits.grant.desktop.WindowsPrivacyHandler uses a module listed above it, which is the healthy direction.
38→29 dev.brewkits.grant.desktop.WindowsPrivacyHandler uses dev.brewkits.grant.desktop✕
- Connections
- 1 pair of types, where a type in dev.brewkits.grant.desktop.WindowsPrivacyHandler uses a type in dev.brewkits.grant.desktop.
- The types involved
dev.brewkits.grant.desktop.WindowsPrivacyHandler.Companion→dev.brewkits.grant.desktop.WindowsPrivacyStatus
- Direction
- dev.brewkits.grant.desktop.WindowsPrivacyHandler uses dev.brewkits.grant.desktop, so a change to dev.brewkits.grant.desktop can break dev.brewkits.grant.desktop.WindowsPrivacyHandler, while a change to dev.brewkits.grant.desktop.WindowsPrivacyHandler can't break dev.brewkits.grant.desktop.
- Position
- Below the diagonal: dev.brewkits.grant.desktop.WindowsPrivacyHandler uses a module listed above it, which is the healthy direction.
39→29 dev.brewkits.grant.desktop.WindowsPrivacyStatus uses dev.brewkits.grant.desktop✕
- Connections
- 5 pairs of types, where a type in dev.brewkits.grant.desktop.WindowsPrivacyStatus uses a type in dev.brewkits.grant.desktop.
- The types involved
dev.brewkits.grant.desktop.WindowsPrivacyStatus.ALLOWED→dev.brewkits.grant.desktop.WindowsPrivacyStatusdev.brewkits.grant.desktop.WindowsPrivacyStatus.DENIED_BY_SYSTEM→dev.brewkits.grant.desktop.WindowsPrivacyStatusdev.brewkits.grant.desktop.WindowsPrivacyStatus.DENIED_BY_USER→dev.brewkits.grant.desktop.WindowsPrivacyStatusdev.brewkits.grant.desktop.WindowsPrivacyStatus.UNAVAILABLE→dev.brewkits.grant.desktop.WindowsPrivacyStatusdev.brewkits.grant.desktop.WindowsPrivacyStatus.UNSPECIFIED→dev.brewkits.grant.desktop.WindowsPrivacyStatus
- Direction
- dev.brewkits.grant.desktop.WindowsPrivacyStatus uses dev.brewkits.grant.desktop, so a change to dev.brewkits.grant.desktop can break dev.brewkits.grant.desktop.WindowsPrivacyStatus, while a change to dev.brewkits.grant.desktop.WindowsPrivacyStatus can't break dev.brewkits.grant.desktop.
- Position
- Below the diagonal: dev.brewkits.grant.desktop.WindowsPrivacyStatus uses a module listed above it, which is the healthy direction.
40→33 dev.brewkits.grant.util.ValidationResult uses dev.brewkits.grant.util✕
- Connections
- 2 pairs of types, where a type in dev.brewkits.grant.util.ValidationResult uses a type in dev.brewkits.grant.util.
- The types involved
dev.brewkits.grant.util.ValidationResult.MissingPermissions→dev.brewkits.grant.util.ValidationResultdev.brewkits.grant.util.ValidationResult.Valid→dev.brewkits.grant.util.ValidationResult
- Direction
- dev.brewkits.grant.util.ValidationResult uses dev.brewkits.grant.util, so a change to dev.brewkits.grant.util can break dev.brewkits.grant.util.ValidationResult, while a change to dev.brewkits.grant.util.ValidationResult can't break dev.brewkits.grant.util.
- Position
- Below the diagonal: dev.brewkits.grant.util.ValidationResult 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 | 64 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 21 | High / Critical |
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; Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery); Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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.5 pts | Medium | Observability |
| Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery). | +3.3 pts | Medium | DR & Backup |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.5 pts | Low | Bus Factor |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +2.4 pts | Medium | Deployment & Rollback |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.1 pts | Low | Supply-chain Provenance & Signing |
| Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find. | +1.9 pts | Medium | Architecture documentation |
| Keep implementation types off the public surface (Kotlin: `internal`) so internals can change without breaking consumers. | +1.6 pts | Medium | Library API & versioning |
| Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate. | +1.6 pts | Medium | Security & performance tooling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| grant-core/src/androidInstrumentedTest/kotlin/dev/brewkits/grant/impl/GrantRequestActivityTest.kt | 6.5 | Mixed | Test Reliability: Test declared unreliable: testA_RequestSinglePermission_alreadyGranted |
| grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt | 7.0 | Mixed | Cyclomatic Complexity: PlatformGrantDelegate.toAndroidGrants (cyclomatic 46) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| grant-core/src/commonMain/kotlin/dev/brewkits/grant/GrantHandler.kt | 7.4 | Mixed | Cyclomatic Complexity: GrantHandler.handleStatus (cyclomatic 29) |
| grant-core/src/iosMain/kotlin/dev/brewkits/grant/delegates/LocationManagerDelegate.kt | 7.4 | Mixed | Code Duplication: Duplicated block (12 lines × 2) |
| grant-compose/src/commonMain/kotlin/dev/brewkits/grant/compose/GrantDialogs.kt | 7.8 | Mixed | Code Duplication: Duplicated block (42 lines × 2) |
| grant-core/src/commonMain/kotlin/dev/brewkits/grant/impl/SimpleGrantManager.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
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 62 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 62 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, 116 of 130 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 READ here — but this repository measures it: a coverage step in CI (`koverVerify`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.kt), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number 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. This repository declares 3 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.kt), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — a Gradle build resolved 604 artifact(s) across its subprojects (311 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape 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. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `demo/iosApp/GrantDemo/GrantDemo/ContentView.swift`, `grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt`, `grant-core/src/iosMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.ios.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Koin, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — 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.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (grant-core/src/androidMain/AndroidManifest.xml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Kotlin, cpp is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin, cpp is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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.
- X2 Cancellation propagation — 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PlatformGrantDelegate.toAndroidGrants at 46. A further 1 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 PlatformGrantDelegate.handlerFor at 25 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: grant-core/src/iosMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.ios.kt (PlatformGrantDelegate.handlerFor at 25). 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 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with PlatformGrantDelegate.toAndroidGrants (cyclomatic 46), PlatformGrantDelegate.requestInternal (cyclomatic 35), GrantHandler.handleStatus (cyclomatic 29). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 8.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
5 method(s) exceeded the cognitive complexity threshold of 15; the worst was GrantHandler.handleStatus at 94.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with GrantHandler.handleStatus (cognitive 94). — Refactoring it lifts Cognitive Complexity from 7.7 to about 8.1/10.
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with GrantHandler.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with PlatformGrantDelegate.android.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with PlatformGrantDelegate.android.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
10 duplicated block group(s) detected. 3 of the 10 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with PlatformGrantDelegate.android.kt, LocationManagerDelegate.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (42 lines × 2) finding(s) in Code Duplication — start with GrantDialogs.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (29 lines × 2) finding(s) in Code Duplication — start with GrantDialogs.kt. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
16 production modules (Gradle+CMake), 1 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 2 module(s) off the main sequence, with abstractness counted on 14 of the 16 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Circular dependency finding(s) in Coupling. — One of this dimension's main actionable groups (1 issue-level).
D6 · Cohesion (LCOM4)
0 of 30 classes have LCOM4 above 3.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 18 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 17 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 9 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
Top hotspots: grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt (13×46=598); grant-core/src/iosMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.ios.kt (9×25=225) Repeated repair below the complexity floor: grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/GrantRequestActivity.kt (3 of 5 changes were fixes)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with PlatformGrantDelegate.android.kt, PlatformGrantDelegate.ios.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with GrantRequestActivity.kt. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
44 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt. Counted over 60 of the 144 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
0 deducted task-comment markers across 12878 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 43 document(s) read across 1 unit(s).
D20 · ADR Quality
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D26 · Project Cohesion
1 of 14 build units (Gradle) 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).
D27 · Navigability
34 % of calls cross a namespace and 22 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
64 finding(s): 0 critical, 61 high, 3 medium, 0 low. 58 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 74, line 180) — 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 58 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 (58 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
12 finding(s): 0 critical, 6 high, 4 medium, 2 low.
What to do
- Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 60 of the 144 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- 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).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 14 platform declaration(s) and 27 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.
AX3 · Project dependency cycles
- The projects KMPGrant:grant-core → KMPGrant:grant-testing → KMPGrant:grant-core form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference.
What to do
- Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
AX4 · Dependency direction
M1 · Documentation (README)
What to do
- Describe the projects a newcomer cannot place from the root README: 10 of 15 have no README of their own, in their folder or in their family's project (`desktop-harness`, `grant-bluetooth`, `grant-bom`, `grant-calendar`, `grant-contacts` and 5 more).
M2 · Architecture documentation
- 1 ADR-shaped document(s) detected by content — `docs/grant-core/ARCHITECTURE.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
What to do
- Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
M3 · Folder & project structure
M4 · Documentation accuracy
- grant-core/README.md links to `../docs/advanced/testing.md`, but `docs/advanced/testing.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — grant-core/README.md:336
What to do
- Reconcile the README with reality: grant-core/README.md links to `../docs/advanced/testing.md`, but `docs/advanced/testing.md` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
- 190/247 types (77%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Kotlin: `internal`) so internals can change without breaking consumers.
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
- `REDACTED` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
What to do
- Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
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
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×5) — grant-core/src/iosMain/kotlin/dev/brewkits/grant/impl/PlatformServiceDelegate.ios.kt:77, grant-core/src/commonMain/kotlin/dev/brewkits/grant/impl/MyServiceManager.kt:37, grant-core/src/androidMain/kotlin/dev/brewkits/grant/SharedPreferencesGrantStore.kt:146, …
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 | 83% | Strong | Solid. |
| Architecture | 92% | Exemplary | Solid. |
| Maturity | 74% | Strong | Solid. |
| Readiness | 44% | Weak — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 70% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D11 Test Reliability — 3 observation(s) recorded · This repository declares 3 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.kt), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 56 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~18329 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.
- D12 Dependency Hygiene — Not scored — a Gradle build resolved 604 artifact(s) across its subprojects (311 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Kotlin, Swift not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Kotlin surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .kt, .swift source were not judged.
- D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- 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) — 3 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- 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): 23 value object(s); 4 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript 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.
- X2 Cancellation propagation — 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 — 72 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test declared unreliable: testA_RequestSinglePermission_alreadyGranted grant-core/src/androidInstrumentedTest/kotlin/dev/brewkits/grant/impl/GrantRequestActivityTest.kt:49
- Test declared unreliable: testRequestMultiplePermissions grant-core/src/androidInstrumentedTest/kotlin/dev/brewkits/grant/impl/GrantRequestActivityTest.kt:74
- Test declared unreliable: testEmptyPermissionList grant-core/src/androidInstrumentedTest/kotlin/dev/brewkits/grant/impl/GrantRequestActivityTest.kt:194
- REDACTED
- REDACTED
- Project dependency cycle
- REDACTED
- REDACTED
- Circular dependency
Serious — 47 finding(s)
- Swallowed exception (caught, then discarded) grant-core/src/iosMain/kotlin/dev/brewkits/grant/impl/PlatformServiceDelegate.ios.kt:77
- Swallowed exception (caught, then discarded) grant-core/src/commonMain/kotlin/dev/brewkits/grant/impl/MyServiceManager.kt:37
- Swallowed exception (caught, then discarded) grant-core/src/androidMain/kotlin/dev/brewkits/grant/SharedPreferencesGrantStore.kt:146
- Swallowed exception (caught, then discarded) grant-core/src/androidMain/kotlin/dev/brewkits/grant/util/ManifestValidator.kt:87
- Swallowed exception (caught, then discarded) grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt:681
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Hotspot: grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt:949
- Hotspot: grant-core/src/iosMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.ios.kt grant-core/src/iosMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.ios.kt:290
- REDACTED
- REDACTED
- Duplicated block (6 lines × 2) grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt:365
- Duplicated block (6 lines × 2) grant-core/src/iosMain/kotlin/dev/brewkits/grant/delegates/LocationManagerDelegate.kt:31
- Off the main sequence: KMPGrant:grant-testing
- Off the main sequence: KMPGrant:grant-core
- PlatformGrantDelegate.toAndroidGrants (cyclomatic 46) grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt:949
- PlatformGrantDelegate.requestInternal (cyclomatic 35) grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt:372
- GrantHandler.handleStatus (cyclomatic 29) grant-core/src/commonMain/kotlin/dev/brewkits/grant/GrantHandler.kt:631
- PlatformGrantDelegate.getGrantStatusOverride (cyclomatic 16) grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt:891
- Repeated repair: grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/GrantRequestActivity.kt grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/GrantRequestActivity.kt:50
- GrantHandler.handleStatus (cognitive 94) grant-core/src/commonMain/kotlin/dev/brewkits/grant/GrantHandler.kt:631
- PlatformGrantDelegate.requestInternal (cognitive 58) grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt:372
- PlatformGrantDelegate.toAndroidGrants (cognitive 57) grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt:949
- PlatformGrantDelegate.getGrantStatusOverride (cognitive 31) grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt:891
- PlatformGrantDelegate.requestMultipleInternal (cognitive 19) grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt:544
- REDACTED
- MethodTooLong: GrantHandler.handleStatus grant-core/src/commonMain/kotlin/dev/brewkits/grant/GrantHandler.kt:631
- TooManyMethods: PlatformGrantDelegate grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt:36
- FileTooLong: impl/PlatformGrantDelegate.android.kt grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (42 lines × 2) grant-compose/src/commonMain/kotlin/dev/brewkits/grant/compose/GrantDialogs.kt:262
- Duplicated block (29 lines × 2) grant-compose/src/commonMain/kotlin/dev/brewkits/grant/compose/GrantDialogs.kt:108
- Duplicated block (12 lines × 2) grant-core/src/iosMain/kotlin/dev/brewkits/grant/delegates/LocationManagerDelegate.kt:164
- Duplicated block (7 lines × 2) grant-core/src/commonMain/kotlin/dev/brewkits/grant/impl/SimpleGrantManager.kt:141
- Duplicated block (8 lines × 2) grant-core/src/iosMain/kotlin/dev/brewkits/grant/delegates/LocationManagerDelegate.kt:150
- Duplicated block (16–17 lines × 2) demo/src/commonMain/kotlin/dev/brewkits/grant/demo/DemoApp.kt:35
- Duplicated block (14 lines × 2) demo/src/commonMain/kotlin/dev/brewkits/grant/demo/GrantDemoScreen.kt:162
- Duplicated block (13 lines × 2) demo/src/commonMain/kotlin/dev/brewkits/grant/demo/LocationFlowDemoScreen.kt:127
- No structured logging
- SAST runs, but gates no merge
Minor — 11 finding(s)
- REDACTED
- REDACTED
- Off-boarding risk: anonymized user #1
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- ADRs not easily discoverable
- README/code drift grant-core/README.md:336
- Large public API surface
- Duplicated predicate grant-bluetooth/src/iosMain/kotlin/dev/brewkits/grant/delegates/BluetoothManagerDelegate.kt:53
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-d75cc5794c394af2a37ee9fa702101e6/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-d75cc5794c394af2a37ee9fa702101e6/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 --exclude kotlin-js-store . | 64 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 12 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 3 file(s) — `demo/iosApp/GrantDemo/GrantDemo/ContentView.swift`, `grant-core/src/androidMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.android.kt`, `grant-core/src/iosMain/kotlin/dev/brewkits/grant/impl/PlatformGrantDelegate.ios.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |