Executive summary
joreilly/PeopleInSpace meets our standard for production. It scores 74 out of 100 and is rated Strong, and all 41 of its critical findings are security problems in the build pipeline.
Production Readiness, at 56, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 4 points. Adding automated security scanning would lift Production Readiness itself, worth about 6 points. Raising Production Readiness to 70 would lift the score to about 81.
Forty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One secret can leak from the build pipeline. Pinning each tool to an exact version and limiting the secret to its own step would close both risks.
The product code is 5,858 lines, about €11,000 to rebuild.
If Production Readiness rose from 56 to 70, the lowest score rated Strong, the score would rise from 74 to about 81.
New since the last survey: 3 findings
- Code Duplication · Edited copy of a member (22 corresponding lines) wearApp/src/main/java/dev/johnoreilly/peopleinspace/peopleinspace/tile/PeopleInSpaceList.kt
- Code Duplication · Duplicated block (14 lines × 2) app/src/main/java/dev/johnoreilly/peopleinspace/peopleinspace/personlist/PersonListScreen.kt
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 6 findings
- Code Duplication · Duplicated block (14 lines × 2) app/src/main/java/dev/johnoreilly/peopleinspace/peopleinspace/personlist/PersonListScreen.kt
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Static Analysis (SAST) · High: gha-curl-pipe-shell REDACTED
- Static Analysis (SAST) · High: gha-curl-pipe-shell REDACTED
- Change Coupling · Change coupling: PersonDetailsScreen.kt ↔ PersonListScreen.kt app/src/main/java/dev/johnoreilly/peopleinspace/peopleinspace/persondetails/PersonDetailsScreen.kt
- Observability · No structured logging
Rebuild cost: about €11,000 · Estimate
| Cost to rebuild | €3,700 to €19,000, for 62 to 198 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.1 at a score of 74. 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: 5,858 lines of product code |
| Comment lines | The estimate prices 5,844 lines. Comment lines count towards the size of 5,858 lines but aren't priced as work. |
| 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 PeopleInSpace.Windows.WinUiApp | 2 SpaceDevsPeopleRepository | 3 compose-web.src.wasmJsMain.resources | 4 dev.johnoreilly | 5 dev.johnoreilly.common.db | 6 dev.johnoreilly.common.remote | 7 dev.johnoreilly.common.repository.PeopleInSpaceRepository | 8 dev.johnoreilly.common.util | 9 dev.johnoreilly.peopleinspace | 10 dev.johnoreilly.peopleinspace.peopleinspace | 11 dev.johnoreilly.peopleinspace.peopleinspace.di | 12 dev.johnoreilly.peopleinspace.peopleinspace.tile.util | 13 repository | 14 (global) | 15 dev.johnoreilly.common.repository | 16 dev.johnoreilly.peopleinspace.peopleinspace.Screen | 17 dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util | 18 dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile | 19 dev.johnoreilly.peopleinspace.persondetails | 20 dev.johnoreilly.peopleinspace.ui | 21 dev.johnoreilly.common.viewmodel | 22 dev.johnoreilly.peopleinspace.glance | 23 dev.johnoreilly.peopleinspace.peopleinspace.glance | 24 dev.johnoreilly.peopleinspace.peopleinspace.list | 25 dev.johnoreilly.peopleinspace.peopleinspace.map | 26 dev.johnoreilly.peopleinspace.peopleinspace.person | 27 dev.johnoreilly.peopleinspace.peopleinspace.remotecompose | 28 dev.johnoreilly.peopleinspace.peopleinspace.tile | 29 dev.johnoreilly.peopleinspace.ui.AppDestinations | 30 dev.johnoreilly.common.di | 31 dev.johnoreilly.common.ui | 32 dev.johnoreilly.common.ui.ISSMapView | 33 dev.johnoreilly.common.viewmodel.IssPositionUiState | 34 dev.johnoreilly.common.viewmodel.PersonListUiState | 35 dev.johnoreilly.common.windows | 36 dev.johnoreilly.peopleinspace.issposition | 37 dev.johnoreilly.peopleinspace.personlist |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 PeopleInSpace.Windows.WinUiApp | |||||||||||||||||||||||||||||||||||||
| 2 SpaceDevsPeopleRepository | |||||||||||||||||||||||||||||||||||||
| 3 compose-web.src.wasmJsMain.resources | |||||||||||||||||||||||||||||||||||||
| 4 dev.johnoreilly | |||||||||||||||||||||||||||||||||||||
| 5 dev.johnoreilly.common.db | |||||||||||||||||||||||||||||||||||||
| 6 dev.johnoreilly.common.remote | |||||||||||||||||||||||||||||||||||||
| 7 dev.johnoreilly.common.repository.PeopleInSpaceRepository | |||||||||||||||||||||||||||||||||||||
| 8 dev.johnoreilly.common.util | |||||||||||||||||||||||||||||||||||||
| 9 dev.johnoreilly.peopleinspace | |||||||||||||||||||||||||||||||||||||
| 10 dev.johnoreilly.peopleinspace.peopleinspace | |||||||||||||||||||||||||||||||||||||
| 11 dev.johnoreilly.peopleinspace.peopleinspace.di | |||||||||||||||||||||||||||||||||||||
| 12 dev.johnoreilly.peopleinspace.peopleinspace.tile.util | |||||||||||||||||||||||||||||||||||||
| 13 repository | |||||||||||||||||||||||||||||||||||||
| 14 (global) | 3 | ||||||||||||||||||||||||||||||||||||
| 15 dev.johnoreilly.common.repository | 8 | 1 | |||||||||||||||||||||||||||||||||||
| 16 dev.johnoreilly.peopleinspace.peopleinspace.Screen | 3 | ||||||||||||||||||||||||||||||||||||
| 17 dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util | 1 | ||||||||||||||||||||||||||||||||||||
| 18 dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile | 1 | ||||||||||||||||||||||||||||||||||||
| 19 dev.johnoreilly.peopleinspace.persondetails | 1 | ||||||||||||||||||||||||||||||||||||
| 20 dev.johnoreilly.peopleinspace.ui | 1 | ||||||||||||||||||||||||||||||||||||
| 21 dev.johnoreilly.common.viewmodel | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 22 dev.johnoreilly.peopleinspace.glance | 2 | ||||||||||||||||||||||||||||||||||||
| 23 dev.johnoreilly.peopleinspace.peopleinspace.glance | 1 | ||||||||||||||||||||||||||||||||||||
| 24 dev.johnoreilly.peopleinspace.peopleinspace.list | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 25 dev.johnoreilly.peopleinspace.peopleinspace.map | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 26 dev.johnoreilly.peopleinspace.peopleinspace.person | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 27 dev.johnoreilly.peopleinspace.peopleinspace.remotecompose | 2 | 3 | |||||||||||||||||||||||||||||||||||
| 28 dev.johnoreilly.peopleinspace.peopleinspace.tile | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 29 dev.johnoreilly.peopleinspace.ui.AppDestinations | 2 | ||||||||||||||||||||||||||||||||||||
| 30 dev.johnoreilly.common.di | 2 | ||||||||||||||||||||||||||||||||||||
| 31 dev.johnoreilly.common.ui | 4 | ||||||||||||||||||||||||||||||||||||
| 32 dev.johnoreilly.common.ui.ISSMapView | 4 | ||||||||||||||||||||||||||||||||||||
| 33 dev.johnoreilly.common.viewmodel.IssPositionUiState | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 34 dev.johnoreilly.common.viewmodel.PersonListUiState | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 35 dev.johnoreilly.common.windows | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 36 dev.johnoreilly.peopleinspace.issposition | 1 | ||||||||||||||||||||||||||||||||||||
| 37 dev.johnoreilly.peopleinspace.personlist | 1 | 1 |
14→6 (global) uses dev.johnoreilly.common.remote✕
- Connections
- 3 pairs of types, where a type in (global) uses a type in dev.johnoreilly.common.remote.
- The types involved
MainKt→dev.johnoreilly.common.remote.AssignmentPeopleDataKt→dev.johnoreilly.common.remote.AssignmentSpaceDevsPeopleRepository→dev.johnoreilly.common.remote.Assignment
- Direction
- (global) uses dev.johnoreilly.common.remote, so a change to dev.johnoreilly.common.remote can break (global), while a change to (global) can't break dev.johnoreilly.common.remote.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
15→6 dev.johnoreilly.common.repository uses dev.johnoreilly.common.remote✕
- Connections
- 8 pairs of types, where a type in dev.johnoreilly.common.repository uses a type in dev.johnoreilly.common.remote.
- The types involved
dev.johnoreilly.common.repository.PeopleInSpaceRepository→dev.johnoreilly.common.remote.Assignmentdev.johnoreilly.common.repository.PeopleInSpaceRepository→dev.johnoreilly.common.remote.AstroviewerApidev.johnoreilly.common.repository.PeopleInSpaceRepository→dev.johnoreilly.common.remote.IssPositiondev.johnoreilly.common.repository.PeopleInSpaceRepository→dev.johnoreilly.common.remote.OrbitPointdev.johnoreilly.common.repository.PeopleInSpaceRepository→dev.johnoreilly.common.remote.PeopleInSpaceApidev.johnoreilly.common.repository.PeopleInSpaceRepositoryInterface→dev.johnoreilly.common.remote.Assignmentdev.johnoreilly.common.repository.PeopleInSpaceRepositoryInterface→dev.johnoreilly.common.remote.IssPositiondev.johnoreilly.common.repository.PeopleInSpaceRepositoryInterface→dev.johnoreilly.common.remote.OrbitPoint
- Direction
- dev.johnoreilly.common.repository uses dev.johnoreilly.common.remote, so a change to dev.johnoreilly.common.remote can break dev.johnoreilly.common.repository, while a change to dev.johnoreilly.common.repository can't break dev.johnoreilly.common.remote.
- Position
- Below the diagonal: dev.johnoreilly.common.repository uses a module listed above it, which is the healthy direction.
15→30 dev.johnoreilly.common.repository uses dev.johnoreilly.common.di part of a loop✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.common.repository uses a type in dev.johnoreilly.common.di.
- The types involved
dev.johnoreilly.common.repository.PeopleInSpaceRepository→dev.johnoreilly.common.di.PeopleInSpaceDatabaseWrapper
- Direction
- dev.johnoreilly.common.repository uses dev.johnoreilly.common.di, so a change to dev.johnoreilly.common.di can break dev.johnoreilly.common.repository, while a change to dev.johnoreilly.common.repository can't break dev.johnoreilly.common.di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→10 dev.johnoreilly.peopleinspace.peopleinspace.Screen uses dev.johnoreilly.peopleinspace.peopleinspace✕
- Connections
- 3 pairs of types, where a type in dev.johnoreilly.peopleinspace.peopleinspace.Screen uses a type in dev.johnoreilly.peopleinspace.peopleinspace.
- The types involved
dev.johnoreilly.peopleinspace.peopleinspace.Screen.IssMap→dev.johnoreilly.peopleinspace.peopleinspace.Screendev.johnoreilly.peopleinspace.peopleinspace.Screen.PersonDetails→dev.johnoreilly.peopleinspace.peopleinspace.Screendev.johnoreilly.peopleinspace.peopleinspace.Screen.PersonList→dev.johnoreilly.peopleinspace.peopleinspace.Screen
- Direction
- dev.johnoreilly.peopleinspace.peopleinspace.Screen uses dev.johnoreilly.peopleinspace.peopleinspace, so a change to dev.johnoreilly.peopleinspace.peopleinspace can break dev.johnoreilly.peopleinspace.peopleinspace.Screen, while a change to dev.johnoreilly.peopleinspace.peopleinspace.Screen can't break dev.johnoreilly.peopleinspace.peopleinspace.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.peopleinspace.Screen uses a module listed above it, which is the healthy direction.
17→6 dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util uses dev.johnoreilly.common.remote✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util uses a type in dev.johnoreilly.common.remote.
- The types involved
dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util.GeoUtilsKt→dev.johnoreilly.common.remote.OrbitPoint
- Direction
- dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util uses dev.johnoreilly.common.remote, so a change to dev.johnoreilly.common.remote can break dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util, while a change to dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util can't break dev.johnoreilly.common.remote.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util uses a module listed above it, which is the healthy direction.
18→6 dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile uses dev.johnoreilly.common.remote✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile uses a type in dev.johnoreilly.common.remote.
- The types involved
dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile.Data→dev.johnoreilly.common.remote.Assignment
- Direction
- dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile uses dev.johnoreilly.common.remote, so a change to dev.johnoreilly.common.remote can break dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile, while a change to dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile can't break dev.johnoreilly.common.remote.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile uses a module listed above it, which is the healthy direction.
19→6 dev.johnoreilly.peopleinspace.persondetails uses dev.johnoreilly.common.remote✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.peopleinspace.persondetails uses a type in dev.johnoreilly.common.remote.
- The types involved
dev.johnoreilly.peopleinspace.persondetails.PersonDetailsScreenKt→dev.johnoreilly.common.remote.Assignment
- Direction
- dev.johnoreilly.peopleinspace.persondetails uses dev.johnoreilly.common.remote, so a change to dev.johnoreilly.common.remote can break dev.johnoreilly.peopleinspace.persondetails, while a change to dev.johnoreilly.peopleinspace.persondetails can't break dev.johnoreilly.common.remote.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.persondetails uses a module listed above it, which is the healthy direction.
20→6 dev.johnoreilly.peopleinspace.ui uses dev.johnoreilly.common.remote✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.peopleinspace.ui uses a type in dev.johnoreilly.common.remote.
- The types involved
dev.johnoreilly.peopleinspace.ui.PeopleInSpacePreviewsKt→dev.johnoreilly.common.remote.Assignment
- Direction
- dev.johnoreilly.peopleinspace.ui uses dev.johnoreilly.common.remote, so a change to dev.johnoreilly.common.remote can break dev.johnoreilly.peopleinspace.ui, while a change to dev.johnoreilly.peopleinspace.ui can't break dev.johnoreilly.common.remote.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.ui uses a module listed above it, which is the healthy direction.
21→6 dev.johnoreilly.common.viewmodel uses dev.johnoreilly.common.remote✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.common.viewmodel uses a type in dev.johnoreilly.common.remote.
- The types involved
dev.johnoreilly.common.viewmodel.ISSPositionViewModel→dev.johnoreilly.common.remote.IssPosition
- Direction
- dev.johnoreilly.common.viewmodel uses dev.johnoreilly.common.remote, so a change to dev.johnoreilly.common.remote can break dev.johnoreilly.common.viewmodel, while a change to dev.johnoreilly.common.viewmodel can't break dev.johnoreilly.common.remote.
- Position
- Below the diagonal: dev.johnoreilly.common.viewmodel uses a module listed above it, which is the healthy direction.
21→15 dev.johnoreilly.common.viewmodel uses dev.johnoreilly.common.repository✕
- Connections
- 2 pairs of types, where a type in dev.johnoreilly.common.viewmodel uses a type in dev.johnoreilly.common.repository.
- The types involved
dev.johnoreilly.common.viewmodel.ISSPositionViewModel→dev.johnoreilly.common.repository.PeopleInSpaceRepositoryInterfacedev.johnoreilly.common.viewmodel.PersonListViewModel→dev.johnoreilly.common.repository.PeopleInSpaceRepositoryInterface
- Direction
- dev.johnoreilly.common.viewmodel uses dev.johnoreilly.common.repository, so a change to dev.johnoreilly.common.repository can break dev.johnoreilly.common.viewmodel, while a change to dev.johnoreilly.common.viewmodel can't break dev.johnoreilly.common.repository.
- Position
- Below the diagonal: dev.johnoreilly.common.viewmodel uses a module listed above it, which is the healthy direction.
22→15 dev.johnoreilly.peopleinspace.glance uses dev.johnoreilly.common.repository✕
- Connections
- 2 pairs of types, where a type in dev.johnoreilly.peopleinspace.glance uses a type in dev.johnoreilly.common.repository.
- The types involved
dev.johnoreilly.peopleinspace.glance.ISSMapWidget→dev.johnoreilly.common.repository.PeopleInSpaceRepositoryInterfacedev.johnoreilly.peopleinspace.glance.PeopleInSpaceWidget→dev.johnoreilly.common.repository.PeopleInSpaceRepositoryInterface
- Direction
- dev.johnoreilly.peopleinspace.glance uses dev.johnoreilly.common.repository, so a change to dev.johnoreilly.common.repository can break dev.johnoreilly.peopleinspace.glance, while a change to dev.johnoreilly.peopleinspace.glance can't break dev.johnoreilly.common.repository.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.glance uses a module listed above it, which is the healthy direction.
23→15 dev.johnoreilly.peopleinspace.peopleinspace.glance uses dev.johnoreilly.common.repository✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.peopleinspace.peopleinspace.glance uses a type in dev.johnoreilly.common.repository.
- The types involved
dev.johnoreilly.peopleinspace.peopleinspace.glance.FetchKt→dev.johnoreilly.common.repository.PeopleInSpaceRepositoryInterface
- Direction
- dev.johnoreilly.peopleinspace.peopleinspace.glance uses dev.johnoreilly.common.repository, so a change to dev.johnoreilly.common.repository can break dev.johnoreilly.peopleinspace.peopleinspace.glance, while a change to dev.johnoreilly.peopleinspace.peopleinspace.glance can't break dev.johnoreilly.common.repository.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.peopleinspace.glance uses a module listed above it, which is the healthy direction.
24→6 dev.johnoreilly.peopleinspace.peopleinspace.list uses dev.johnoreilly.common.remote✕
- Connections
- 2 pairs of types, where a type in dev.johnoreilly.peopleinspace.peopleinspace.list uses a type in dev.johnoreilly.common.remote.
- The types involved
dev.johnoreilly.peopleinspace.peopleinspace.list.PersonListScreenKt→dev.johnoreilly.common.remote.Assignmentdev.johnoreilly.peopleinspace.peopleinspace.list.PersonListViewModel→dev.johnoreilly.common.remote.Assignment
- Direction
- dev.johnoreilly.peopleinspace.peopleinspace.list uses dev.johnoreilly.common.remote, so a change to dev.johnoreilly.common.remote can break dev.johnoreilly.peopleinspace.peopleinspace.list, while a change to dev.johnoreilly.peopleinspace.peopleinspace.list can't break dev.johnoreilly.common.remote.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.peopleinspace.list uses a module listed above it, which is the healthy direction.
24→15 dev.johnoreilly.peopleinspace.peopleinspace.list uses dev.johnoreilly.common.repository✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.peopleinspace.peopleinspace.list uses a type in dev.johnoreilly.common.repository.
- The types involved
dev.johnoreilly.peopleinspace.peopleinspace.list.PersonListViewModel→dev.johnoreilly.common.repository.PeopleInSpaceRepositoryInterface
- Direction
- dev.johnoreilly.peopleinspace.peopleinspace.list uses dev.johnoreilly.common.repository, so a change to dev.johnoreilly.common.repository can break dev.johnoreilly.peopleinspace.peopleinspace.list, while a change to dev.johnoreilly.peopleinspace.peopleinspace.list can't break dev.johnoreilly.common.repository.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.peopleinspace.list uses a module listed above it, which is the healthy direction.
25→6 dev.johnoreilly.peopleinspace.peopleinspace.map uses dev.johnoreilly.common.remote✕
- Connections
- 2 pairs of types, where a type in dev.johnoreilly.peopleinspace.peopleinspace.map uses a type in dev.johnoreilly.common.remote.
- The types involved
dev.johnoreilly.peopleinspace.peopleinspace.map.IssMapKt→dev.johnoreilly.common.remote.IssPositiondev.johnoreilly.peopleinspace.peopleinspace.map.MapViewModel→dev.johnoreilly.common.remote.IssPosition
- Direction
- dev.johnoreilly.peopleinspace.peopleinspace.map uses dev.johnoreilly.common.remote, so a change to dev.johnoreilly.common.remote can break dev.johnoreilly.peopleinspace.peopleinspace.map, while a change to dev.johnoreilly.peopleinspace.peopleinspace.map can't break dev.johnoreilly.common.remote.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.peopleinspace.map uses a module listed above it, which is the healthy direction.
25→15 dev.johnoreilly.peopleinspace.peopleinspace.map uses dev.johnoreilly.common.repository✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.peopleinspace.peopleinspace.map uses a type in dev.johnoreilly.common.repository.
- The types involved
dev.johnoreilly.peopleinspace.peopleinspace.map.MapViewModel→dev.johnoreilly.common.repository.PeopleInSpaceRepositoryInterface
- Direction
- dev.johnoreilly.peopleinspace.peopleinspace.map uses dev.johnoreilly.common.repository, so a change to dev.johnoreilly.common.repository can break dev.johnoreilly.peopleinspace.peopleinspace.map, while a change to dev.johnoreilly.peopleinspace.peopleinspace.map can't break dev.johnoreilly.common.repository.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.peopleinspace.map uses a module listed above it, which is the healthy direction.
26→6 dev.johnoreilly.peopleinspace.peopleinspace.person uses dev.johnoreilly.common.remote✕
- Connections
- 2 pairs of types, where a type in dev.johnoreilly.peopleinspace.peopleinspace.person uses a type in dev.johnoreilly.common.remote.
- The types involved
dev.johnoreilly.peopleinspace.peopleinspace.person.PersonDetailsScreenKt→dev.johnoreilly.common.remote.Assignmentdev.johnoreilly.peopleinspace.peopleinspace.person.PersonDetailsViewModel→dev.johnoreilly.common.remote.Assignment
- Direction
- dev.johnoreilly.peopleinspace.peopleinspace.person uses dev.johnoreilly.common.remote, so a change to dev.johnoreilly.common.remote can break dev.johnoreilly.peopleinspace.peopleinspace.person, while a change to dev.johnoreilly.peopleinspace.peopleinspace.person can't break dev.johnoreilly.common.remote.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.peopleinspace.person uses a module listed above it, which is the healthy direction.
26→15 dev.johnoreilly.peopleinspace.peopleinspace.person uses dev.johnoreilly.common.repository✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.peopleinspace.peopleinspace.person uses a type in dev.johnoreilly.common.repository.
- The types involved
dev.johnoreilly.peopleinspace.peopleinspace.person.PersonDetailsViewModel→dev.johnoreilly.common.repository.PeopleInSpaceRepositoryInterface
- Direction
- dev.johnoreilly.peopleinspace.peopleinspace.person uses dev.johnoreilly.common.repository, so a change to dev.johnoreilly.common.repository can break dev.johnoreilly.peopleinspace.peopleinspace.person, while a change to dev.johnoreilly.peopleinspace.peopleinspace.person can't break dev.johnoreilly.common.repository.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.peopleinspace.person uses a module listed above it, which is the healthy direction.
27→15 dev.johnoreilly.peopleinspace.peopleinspace.remotecompose uses dev.johnoreilly.common.repository✕
- Connections
- 2 pairs of types, where a type in dev.johnoreilly.peopleinspace.peopleinspace.remotecompose uses a type in dev.johnoreilly.common.repository.
- The types involved
dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.PeopleInSpaceWidgetReceiver→dev.johnoreilly.common.repository.PeopleInSpaceRepositoryInterfacedev.johnoreilly.peopleinspace.peopleinspace.remotecompose.RemoteComposeTestActivity→dev.johnoreilly.common.repository.PeopleInSpaceRepositoryInterface
- Direction
- dev.johnoreilly.peopleinspace.peopleinspace.remotecompose uses dev.johnoreilly.common.repository, so a change to dev.johnoreilly.common.repository can break dev.johnoreilly.peopleinspace.peopleinspace.remotecompose, while a change to dev.johnoreilly.peopleinspace.peopleinspace.remotecompose can't break dev.johnoreilly.common.repository.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.peopleinspace.remotecompose uses a module listed above it, which is the healthy direction.
27→17 dev.johnoreilly.peopleinspace.peopleinspace.remotecompose uses dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util✕
- Connections
- 3 pairs of types, where a type in dev.johnoreilly.peopleinspace.peopleinspace.remotecompose uses a type in dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util.
- The types involved
dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.PeopleInSpaceCardKt→dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util.MapResultdev.johnoreilly.peopleinspace.peopleinspace.remotecompose.PeopleInSpaceWidgetReceiver→dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util.AsyncAppWidgetReceiverdev.johnoreilly.peopleinspace.peopleinspace.remotecompose.RemoteComposeTestActivity→dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util.MapResult
- Direction
- dev.johnoreilly.peopleinspace.peopleinspace.remotecompose uses dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util, so a change to dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util can break dev.johnoreilly.peopleinspace.peopleinspace.remotecompose, while a change to dev.johnoreilly.peopleinspace.peopleinspace.remotecompose can't break dev.johnoreilly.peopleinspace.peopleinspace.remotecompose.util.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.peopleinspace.remotecompose uses a module listed above it, which is the healthy direction.
28→6 dev.johnoreilly.peopleinspace.peopleinspace.tile uses dev.johnoreilly.common.remote✕
- Connections
- 2 pairs of types, where a type in dev.johnoreilly.peopleinspace.peopleinspace.tile uses a type in dev.johnoreilly.common.remote.
- The types involved
dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceListKt→dev.johnoreilly.common.remote.Assignmentdev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile→dev.johnoreilly.common.remote.Assignment
- Direction
- dev.johnoreilly.peopleinspace.peopleinspace.tile uses dev.johnoreilly.common.remote, so a change to dev.johnoreilly.common.remote can break dev.johnoreilly.peopleinspace.peopleinspace.tile, while a change to dev.johnoreilly.peopleinspace.peopleinspace.tile can't break dev.johnoreilly.common.remote.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.peopleinspace.tile uses a module listed above it, which is the healthy direction.
28→15 dev.johnoreilly.peopleinspace.peopleinspace.tile uses dev.johnoreilly.common.repository✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.peopleinspace.peopleinspace.tile uses a type in dev.johnoreilly.common.repository.
- The types involved
dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile→dev.johnoreilly.common.repository.PeopleInSpaceRepositoryInterface
- Direction
- dev.johnoreilly.peopleinspace.peopleinspace.tile uses dev.johnoreilly.common.repository, so a change to dev.johnoreilly.common.repository can break dev.johnoreilly.peopleinspace.peopleinspace.tile, while a change to dev.johnoreilly.peopleinspace.peopleinspace.tile can't break dev.johnoreilly.common.repository.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.peopleinspace.tile uses a module listed above it, which is the healthy direction.
28→18 dev.johnoreilly.peopleinspace.peopleinspace.tile uses dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile✕
- Connections
- 2 pairs of types, where a type in dev.johnoreilly.peopleinspace.peopleinspace.tile uses a type in dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile.
- The types involved
dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceListKt→dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile.Datadev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile→dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile.Data
- Direction
- dev.johnoreilly.peopleinspace.peopleinspace.tile uses dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile, so a change to dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile can break dev.johnoreilly.peopleinspace.peopleinspace.tile, while a change to dev.johnoreilly.peopleinspace.peopleinspace.tile can't break dev.johnoreilly.peopleinspace.peopleinspace.tile.PeopleInSpaceTile.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.peopleinspace.tile uses a module listed above it, which is the healthy direction.
29→20 dev.johnoreilly.peopleinspace.ui.AppDestinations uses dev.johnoreilly.peopleinspace.ui✕
- Connections
- 2 pairs of types, where a type in dev.johnoreilly.peopleinspace.ui.AppDestinations uses a type in dev.johnoreilly.peopleinspace.ui.
- The types involved
dev.johnoreilly.peopleinspace.ui.AppDestinations.ISS_POSITION→dev.johnoreilly.peopleinspace.ui.AppDestinationsdev.johnoreilly.peopleinspace.ui.AppDestinations.PERSON_LIST→dev.johnoreilly.peopleinspace.ui.AppDestinations
- Direction
- dev.johnoreilly.peopleinspace.ui.AppDestinations uses dev.johnoreilly.peopleinspace.ui, so a change to dev.johnoreilly.peopleinspace.ui can break dev.johnoreilly.peopleinspace.ui.AppDestinations, while a change to dev.johnoreilly.peopleinspace.ui.AppDestinations can't break dev.johnoreilly.peopleinspace.ui.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.ui.AppDestinations uses a module listed above it, which is the healthy direction.
30→21 dev.johnoreilly.common.di uses dev.johnoreilly.common.viewmodel✕
- Connections
- 2 pairs of types, where a type in dev.johnoreilly.common.di uses a type in dev.johnoreilly.common.viewmodel.
- The types involved
dev.johnoreilly.common.di.KoinKt→dev.johnoreilly.common.viewmodel.ISSPositionViewModeldev.johnoreilly.common.di.KoinKt→dev.johnoreilly.common.viewmodel.PersonListViewModel
- Direction
- dev.johnoreilly.common.di uses dev.johnoreilly.common.viewmodel, so a change to dev.johnoreilly.common.viewmodel can break dev.johnoreilly.common.di, while a change to dev.johnoreilly.common.di can't break dev.johnoreilly.common.viewmodel.
- Position
- Below the diagonal: dev.johnoreilly.common.di uses a module listed above it, which is the healthy direction.
31→21 dev.johnoreilly.common.ui uses dev.johnoreilly.common.viewmodel✕
- Connections
- 4 pairs of types, where a type in dev.johnoreilly.common.ui uses a type in dev.johnoreilly.common.viewmodel.
- The types involved
dev.johnoreilly.common.ui.ISSMapViewKt→dev.johnoreilly.common.viewmodel.ISSPositionViewModeldev.johnoreilly.common.ui.ISSPositionContentKt→dev.johnoreilly.common.viewmodel.ISSPositionViewModeldev.johnoreilly.common.ui.NativeViewFactory→dev.johnoreilly.common.viewmodel.ISSPositionViewModeldev.johnoreilly.common.ui.SharedViewControllersKt→dev.johnoreilly.common.viewmodel.ISSPositionViewModel
- Direction
- dev.johnoreilly.common.ui uses dev.johnoreilly.common.viewmodel, so a change to dev.johnoreilly.common.viewmodel can break dev.johnoreilly.common.ui, while a change to dev.johnoreilly.common.ui can't break dev.johnoreilly.common.viewmodel.
- Position
- Below the diagonal: dev.johnoreilly.common.ui uses a module listed above it, which is the healthy direction.
32→21 dev.johnoreilly.common.ui.ISSMapView uses dev.johnoreilly.common.viewmodel✕
- Connections
- 4 pairs of types, where a type in dev.johnoreilly.common.ui.ISSMapView uses a type in dev.johnoreilly.common.viewmodel.
- The types involved
dev.johnoreilly.common.ui.ISSMapView.androidKt→dev.johnoreilly.common.viewmodel.ISSPositionViewModeldev.johnoreilly.common.ui.ISSMapView.iosKt→dev.johnoreilly.common.viewmodel.ISSPositionViewModeldev.johnoreilly.common.ui.ISSMapView.jvmKt→dev.johnoreilly.common.viewmodel.ISSPositionViewModeldev.johnoreilly.common.ui.ISSMapView.wasmJsKt→dev.johnoreilly.common.viewmodel.ISSPositionViewModel
- Direction
- dev.johnoreilly.common.ui.ISSMapView uses dev.johnoreilly.common.viewmodel, so a change to dev.johnoreilly.common.viewmodel can break dev.johnoreilly.common.ui.ISSMapView, while a change to dev.johnoreilly.common.ui.ISSMapView can't break dev.johnoreilly.common.viewmodel.
- Position
- Below the diagonal: dev.johnoreilly.common.ui.ISSMapView uses a module listed above it, which is the healthy direction.
33→6 dev.johnoreilly.common.viewmodel.IssPositionUiState uses dev.johnoreilly.common.remote✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.common.viewmodel.IssPositionUiState uses a type in dev.johnoreilly.common.remote.
- The types involved
dev.johnoreilly.common.viewmodel.IssPositionUiState.Success→dev.johnoreilly.common.remote.IssPosition
- Direction
- dev.johnoreilly.common.viewmodel.IssPositionUiState uses dev.johnoreilly.common.remote, so a change to dev.johnoreilly.common.remote can break dev.johnoreilly.common.viewmodel.IssPositionUiState, while a change to dev.johnoreilly.common.viewmodel.IssPositionUiState can't break dev.johnoreilly.common.remote.
- Position
- Below the diagonal: dev.johnoreilly.common.viewmodel.IssPositionUiState uses a module listed above it, which is the healthy direction.
33→21 dev.johnoreilly.common.viewmodel.IssPositionUiState uses dev.johnoreilly.common.viewmodel✕
- Connections
- 2 pairs of types, where a type in dev.johnoreilly.common.viewmodel.IssPositionUiState uses a type in dev.johnoreilly.common.viewmodel.
- The types involved
dev.johnoreilly.common.viewmodel.IssPositionUiState.Loading→dev.johnoreilly.common.viewmodel.IssPositionUiStatedev.johnoreilly.common.viewmodel.IssPositionUiState.Success→dev.johnoreilly.common.viewmodel.IssPositionUiState
- Direction
- dev.johnoreilly.common.viewmodel.IssPositionUiState uses dev.johnoreilly.common.viewmodel, so a change to dev.johnoreilly.common.viewmodel can break dev.johnoreilly.common.viewmodel.IssPositionUiState, while a change to dev.johnoreilly.common.viewmodel.IssPositionUiState can't break dev.johnoreilly.common.viewmodel.
- Position
- Below the diagonal: dev.johnoreilly.common.viewmodel.IssPositionUiState uses a module listed above it, which is the healthy direction.
34→6 dev.johnoreilly.common.viewmodel.PersonListUiState uses dev.johnoreilly.common.remote✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.common.viewmodel.PersonListUiState uses a type in dev.johnoreilly.common.remote.
- The types involved
dev.johnoreilly.common.viewmodel.PersonListUiState.Success→dev.johnoreilly.common.remote.Assignment
- Direction
- dev.johnoreilly.common.viewmodel.PersonListUiState uses dev.johnoreilly.common.remote, so a change to dev.johnoreilly.common.remote can break dev.johnoreilly.common.viewmodel.PersonListUiState, while a change to dev.johnoreilly.common.viewmodel.PersonListUiState can't break dev.johnoreilly.common.remote.
- Position
- Below the diagonal: dev.johnoreilly.common.viewmodel.PersonListUiState uses a module listed above it, which is the healthy direction.
34→21 dev.johnoreilly.common.viewmodel.PersonListUiState uses dev.johnoreilly.common.viewmodel✕
- Connections
- 3 pairs of types, where a type in dev.johnoreilly.common.viewmodel.PersonListUiState uses a type in dev.johnoreilly.common.viewmodel.
- The types involved
dev.johnoreilly.common.viewmodel.PersonListUiState.Error→dev.johnoreilly.common.viewmodel.PersonListUiStatedev.johnoreilly.common.viewmodel.PersonListUiState.Loading→dev.johnoreilly.common.viewmodel.PersonListUiStatedev.johnoreilly.common.viewmodel.PersonListUiState.Success→dev.johnoreilly.common.viewmodel.PersonListUiState
- Direction
- dev.johnoreilly.common.viewmodel.PersonListUiState uses dev.johnoreilly.common.viewmodel, so a change to dev.johnoreilly.common.viewmodel can break dev.johnoreilly.common.viewmodel.PersonListUiState, while a change to dev.johnoreilly.common.viewmodel.PersonListUiState can't break dev.johnoreilly.common.viewmodel.
- Position
- Below the diagonal: dev.johnoreilly.common.viewmodel.PersonListUiState uses a module listed above it, which is the healthy direction.
35→15 dev.johnoreilly.common.windows uses dev.johnoreilly.common.repository✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.common.windows uses a type in dev.johnoreilly.common.repository.
- The types involved
dev.johnoreilly.common.windows.PeopleInSpaceClient→dev.johnoreilly.common.repository.PeopleInSpaceRepository
- Direction
- dev.johnoreilly.common.windows uses dev.johnoreilly.common.repository, so a change to dev.johnoreilly.common.repository can break dev.johnoreilly.common.windows, while a change to dev.johnoreilly.common.windows can't break dev.johnoreilly.common.repository.
- Position
- Below the diagonal: dev.johnoreilly.common.windows uses a module listed above it, which is the healthy direction.
35→21 dev.johnoreilly.common.windows uses dev.johnoreilly.common.viewmodel✕
- Connections
- 2 pairs of types, where a type in dev.johnoreilly.common.windows uses a type in dev.johnoreilly.common.viewmodel.
- The types involved
dev.johnoreilly.common.windows.PeopleInSpaceClient→dev.johnoreilly.common.viewmodel.IssPositionUiStatedev.johnoreilly.common.windows.PeopleInSpaceClient→dev.johnoreilly.common.viewmodel.PersonListUiState
- Direction
- dev.johnoreilly.common.windows uses dev.johnoreilly.common.viewmodel, so a change to dev.johnoreilly.common.viewmodel can break dev.johnoreilly.common.windows, while a change to dev.johnoreilly.common.windows can't break dev.johnoreilly.common.viewmodel.
- Position
- Below the diagonal: dev.johnoreilly.common.windows uses a module listed above it, which is the healthy direction.
36→21 dev.johnoreilly.peopleinspace.issposition uses dev.johnoreilly.common.viewmodel✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.peopleinspace.issposition uses a type in dev.johnoreilly.common.viewmodel.
- The types involved
dev.johnoreilly.peopleinspace.issposition.ISSPositionScreenKt→dev.johnoreilly.common.viewmodel.ISSPositionViewModel
- Direction
- dev.johnoreilly.peopleinspace.issposition uses dev.johnoreilly.common.viewmodel, so a change to dev.johnoreilly.common.viewmodel can break dev.johnoreilly.peopleinspace.issposition, while a change to dev.johnoreilly.peopleinspace.issposition can't break dev.johnoreilly.common.viewmodel.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.issposition uses a module listed above it, which is the healthy direction.
37→6 dev.johnoreilly.peopleinspace.personlist uses dev.johnoreilly.common.remote✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.peopleinspace.personlist uses a type in dev.johnoreilly.common.remote.
- The types involved
dev.johnoreilly.peopleinspace.personlist.PersonListScreenKt→dev.johnoreilly.common.remote.Assignment
- Direction
- dev.johnoreilly.peopleinspace.personlist uses dev.johnoreilly.common.remote, so a change to dev.johnoreilly.common.remote can break dev.johnoreilly.peopleinspace.personlist, while a change to dev.johnoreilly.peopleinspace.personlist can't break dev.johnoreilly.common.remote.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.personlist uses a module listed above it, which is the healthy direction.
37→21 dev.johnoreilly.peopleinspace.personlist uses dev.johnoreilly.common.viewmodel✕
- Connections
- 1 pair of types, where a type in dev.johnoreilly.peopleinspace.personlist uses a type in dev.johnoreilly.common.viewmodel.
- The types involved
dev.johnoreilly.peopleinspace.personlist.PersonListScreenKt→dev.johnoreilly.common.viewmodel.PersonListUiState
- Direction
- dev.johnoreilly.peopleinspace.personlist uses dev.johnoreilly.common.viewmodel, so a change to dev.johnoreilly.common.viewmodel can break dev.johnoreilly.peopleinspace.personlist, while a change to dev.johnoreilly.peopleinspace.personlist can't break dev.johnoreilly.common.viewmodel.
- Position
- Below the diagonal: dev.johnoreilly.peopleinspace.personlist 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 | 41 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 2 | Medium |
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with PeopleInSpace.Windows.WinUiApp.csproj.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with PeopleInSpace.Windows.WinUiApp.csproj. | +4.0 pts | Low | ADR Quality |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +6.3 pts | Medium | Security & performance tooling |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +4.1 pts | Medium | Observability |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.8 pts | Medium | Architecture documentation |
| Declare the version where the ecosystem expects it, or keep a CHANGELOG with semver release headings, and follow semver for breaking changes. | +2.6 pts | Medium | Library API & versioning |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.4 pts | Low | Static Analysis (SAST) |
| Resolve the 1 MethodTooLong finding(s) in God Classes — start with ContentView.swift. | +0.1 pts | Medium | God Classes |
| Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with GeoUtilsKt.fetchMapBitmapInRange (cognitive 19), MainKt.PersonView (cognitive 16). | +0.1 pts | Medium | Cognitive Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | 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.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 |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| compose-desktop/src/main/kotlin/main.kt | 7.8 | Mixed | Cognitive Complexity: MainKt.PersonView (cognitive 16) |
| PeopleInSpaceSwiftUI/PeopleInSpaceSwiftUI/ContentView.swift | 7.8 | Mixed | God Classes: MethodTooLong: PersonDetailsScreen.body |
| app/src/main/java/dev/johnoreilly/peopleinspace/peopleinspace/remotecompose/util/GeoUtils.kt | 8.5 | Near-clean | Cognitive Complexity: GeoUtilsKt.fetchMapBitmapInRange (cognitive 19) |
| wearApp/src/main/java/dev/johnoreilly/peopleinspace/peopleinspace/tile/PeopleInSpaceList.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (22 corresponding lines) |
| app/src/main/java/dev/johnoreilly/peopleinspace/peopleinspace/personlist/PersonListScreen.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (14 lines × 2) |
| compose-web/src/wasmJsMain/kotlin/Main.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (13 lines × 2) |
| app/src/main/java/dev/johnoreilly/peopleinspace/peopleinspace/persondetails/PersonDetailsScreen.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (12 lines × 2) |
| wearApp/src/main/java/dev/johnoreilly/peopleinspace/peopleinspace/MainActivity.kt | 8.5 | Near-clean | Change Coupling: Change coupling: MainActivity.kt ↔ PersonListScreen.kt |
| windows/WinUiApp/PeopleInSpace.Windows.WinUiApp.csproj | 9.5 | Near-clean | ADR Quality: No ADRs found |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 36 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 36 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, 57 of 62 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (37 contributor(s) across 1068 commit(s) sampled, automation and bot accounts excluded). One of them holds 82% of the history; the other 36 hold 0.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — 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. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'windows/WinUiApp/PeopleInSpace.Windows.WinUiApp.csproj' with message: The following PackageReference item(s) do not have a version specified: PeopleInSpace.Kotlin.
- D17 Explicit Debt — 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. The 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .kt (5,069 lines, 88% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 2 task marker(s) (TODO/FIXME/HACK/XXX) across 1 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- 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.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- 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. `wearApp/src/main/java/dev/johnoreilly/peopleinspace/peopleinspace/tile/util/Extensions.kt`, `windows/WinUiApp/PeopleInSpaceViewModel.cs` 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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: a from http://172.31.7.1:8790/gradle-plugins/androidx/wear/compose/remote/remote-material3/1.0.0-SNAPSHOT/maven-metadata.xml. > Could not GET 'http://172.31.7.1:8790/gradle-plugins/android…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it).
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for windows/WinUiApp/PeopleInSpace.Windows.WinUiApp.csproj, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- 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.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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".
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
2 method(s) exceeded the cognitive complexity threshold of 15; the worst was GeoUtilsKt.fetchMapBitmapInRange at 19.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with GeoUtilsKt.fetchMapBitmapInRange (cognitive 19), MainKt.PersonView (cognitive 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with ContentView.swift. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
5 duplicated block group(s) detected. 2.8 % of the production lines (162 of 5,777) are in a reported copy. One further row reports members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with Main.kt, main.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (22 corresponding lines) finding(s) in Code Duplication — start with PeopleInSpaceList.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with PersonListScreen.kt. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
10 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 2 module(s) off the main sequence, with abstractness counted on 9 of the 10 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 7 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 95 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 3 direct `PackageReference`(s), and 93 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Gradle build (build.gradle/build.gradle.kts), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted debt markers + unmeasured dead symbols across 240 LoC in the .NET projects (0.0/KLoC) → score 10.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .kt (88% of production source) was not read, and carries at least 2 uncounted task marker(s) in 1 file(s).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with PeopleInSpace.Windows.WinUiApp.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
41 finding(s): 0 critical, 41 high, 0 medium, 0 low. 40 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `gradlew` (line 74, line 178), `windows/WinUiApp/PeopleInSpaceViewModel.cs` (line 174, lines 175–177, line 181) — 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. In 1 of those file(s) — `windows/WinUiApp/PeopleInSpaceViewModel.cs` — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in 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 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 40 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 (40 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 0 high, 1 medium, 1 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
What to do
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 37 of the 94 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: MainActivity.kt↔PersonListScreen.kt 61%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with MainActivity.kt. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 7 platform declaration(s) and 90 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
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- No explicit version was found for the Maven/Gradle library declared by `build.gradle.kts`. This check read a `<version>` in pom.xml, or `version` in build.gradle(.kts) or gradle.properties, and a CHANGELOG/CHANGES/HISTORY/NEWS/RELEASES file with a semver heading, or release tooling (changesets, release-please, semantic-release, goreleaser, cargo-release, bump2version, standard-version, git-cliff) in the library's directory or at the repository root, or a semver release tag (or a Drupal `8.x-1.2` release tag) in the repository. A version computed where none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes. — db/build.gradle.kts
What to do
- Declare the version where the ecosystem expects it, or keep a CHANGELOG with semver release headings, and follow semver for breaking changes.
P2 · Observability
- Only 1/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `PeopleInSpaceSwiftUI`, `compose-desktop`, `compose-web`, `mcp-server`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 7 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
PF3 · Async & latency hygiene
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 98% | Exemplary | Solid. |
| Architecture | 99% | Exemplary | Solid. |
| Maturity | 82% | Strong | Solid. |
| Readiness | 56% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 96% | Exemplary | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 2 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 78 check(s) not relevant to this codebase
- AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: a from http://172.31.7.1:8790/gradle-plugins/androidx/wear/compose/remote/remote-material3/1.0.0-SNAPSHOT/maven-metadata.xml. > Could not GET 'http://172.31.7.1:8790/gradle-plugins/android…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D10 Test Quality — ~566 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .kt, .swift, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (779 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Kotlin surface was not measured.
- D23 Boundary Type-Coupling — small single-context codebase (5,777 production LoC in the .NET projects) — bounded contexts are not needed at this size 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 — no ADRs to check
- D26 Project Cohesion — This repository is one project, `PeopleInSpace.Windows.WinUiApp` (240 LoC, 6 public types across 1 namespaces), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (6 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — IC1 reached only 4% of this repository's production lines — kotlin (5,069 lines), swift (468 lines), javascript (81 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- 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 — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X1 Async correctness — X1 reached only 4% of this repository's production lines — kotlin (5,069 lines), swift (468 lines), javascript (81 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 4% of this repository's production lines — kotlin (5,069 lines), swift (468 lines), javascript (81 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — X18 reached only 4% of this repository's production lines — kotlin (5,069 lines), swift (468 lines), javascript (81 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — X2 reached only 4% of this repository's production lines — kotlin (5,069 lines), swift (468 lines), javascript (81 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — X27 reached only 4% of this repository's production lines — kotlin (5,069 lines), swift (468 lines), javascript (81 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — X3 reached only 4% of this repository's production lines — kotlin (5,069 lines), swift (468 lines), javascript (81 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 41 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
Serious — 14 finding(s)
- Duplicated block (13 lines × 2) compose-web/src/wasmJsMain/kotlin/Main.kt:350
- Duplicated block (13 lines × 2) compose-desktop/src/main/kotlin/main.kt:283
- GeoUtilsKt.fetchMapBitmapInRange (cognitive 19) app/src/main/java/dev/johnoreilly/peopleinspace/peopleinspace/remotecompose/util/GeoUtils.kt:50
- MainKt.PersonView (cognitive 16) compose-desktop/src/main/kotlin/main.kt:180
- MethodTooLong: PersonDetailsScreen.body PeopleInSpaceSwiftUI/PeopleInSpaceSwiftUI/ContentView.swift:211
- REDACTED
- Change coupling: MainActivity.kt ↔ PersonListScreen.kt wearApp/src/main/java/dev/johnoreilly/peopleinspace/peopleinspace/MainActivity.kt:1
- REDACTED
- Edited copy of a member (22 corresponding lines) wearApp/src/main/java/dev/johnoreilly/peopleinspace/peopleinspace/tile/PeopleInSpaceList.kt:150
- Duplicated block (14 lines × 2) app/src/main/java/dev/johnoreilly/peopleinspace/peopleinspace/personlist/PersonListScreen.kt:107
- Duplicated block (12 lines × 2) app/src/main/java/dev/johnoreilly/peopleinspace/peopleinspace/persondetails/PersonDetailsScreen.kt:114
- Duplicated block (7 lines × 2) PeopleInSpaceSwiftUI/PeopleInSpaceSwiftUI/ContentView.swift:281
- Off the main sequence: :db
- NuGet dependencies are not locked
Minor — 6 finding(s)
- No ADRs found windows/WinUiApp/PeopleInSpace.Windows.WinUiApp.csproj:6
- REDACTED
- No ADRs
- No explicit versioning db/build.gradle.kts
- Logging is not universal
- No SAST REDACTED:4
Minor — 1 finding(s)
- Off the main sequence: :common
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-0312be4fa3bc4d08a82ecf93c3bc5484/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-0312be4fa3bc4d08a82ecf93c3bc5484/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 . | 41 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 2 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `wearApp/src/main/java/dev/johnoreilly/peopleinspace/peopleinspace/tile/util/Extensions.kt`, `windows/WinUiApp/PeopleInSpaceViewModel.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |