Executive summary
HellGuy39/HellNotes falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 47.7 out of 100 and is rated Weak, and its one critical finding doesn't concern security.
Production Readiness, at 24.7, is the weakest lens and counts most in the score. The best first step is improving the documentation, worth about 9.3 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 8.5 points. Raising Production Readiness to 70 would lift the score to about 63.8.
The inner part of the code that depends on an outer part needs turning around so it points inward.
The product code is 27,071 lines, about €30,000 to rebuild.
If Production Readiness rose from 24.7 to 70, the lowest score rated Strong, the score would rise from 47.7 to about 63.8.
Rebuild cost: about €30,000 · Estimate
| Cost to rebuild | €10,000 to €51,000, for 168 to 532 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 48. 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 | Medium: 27,071 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 core.domain.repository.store | 2 core.model.repository.local.file | 3 core.model.repository.remote | 4 core.model.wrapper | 5 core.ui.resources.wrapper | 6 core.ui.state | 7 core.model | 8 core.storeapi.review.factory | 9 core.domain.logger | 10 core.domain.repository.remote | 11 core.model.repository.local.datastore | 12 core.storeapi.di | 13 core.data.repository.remote | 14 core.domain.repository.settings | 15 core.model.repository.local.database | 16 core.database.dao | 17 core.domain.repository.notes | 18 core.domain.repository.system | 19 core.domain.usecase.backup | 20 core.ui.components | 21 feature.locksetup | 22 core.domain.usecase.reminder | 23 core.domain.usecase.trash | 24 feature.home | 25 feature.lock | 26 tools | 27 core.domain.usecase | 28 core.domain.usecase.note | 29 feature.home.reminders | 30 feature.home.trash | 31 core.domain.usecase.archive | 32 core.domain.usecase.label | 33 feature.home.notes | 34 feature.notedetail | 35 feature.search | 36 feature.update | 37 core.data.repository.local | 38 feature.home.archive | 39 feature.home.label | 40 core.data.di |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 core.domain.repository.store | ||||||||||||||||||||||||||||||||||||||||
| 2 core.model.repository.local.file | ||||||||||||||||||||||||||||||||||||||||
| 3 core.model.repository.remote | ||||||||||||||||||||||||||||||||||||||||
| 4 core.model.wrapper | ||||||||||||||||||||||||||||||||||||||||
| 5 core.ui.resources.wrapper | ||||||||||||||||||||||||||||||||||||||||
| 6 core.ui.state | ||||||||||||||||||||||||||||||||||||||||
| 7 core.model | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 8 core.storeapi.review.factory | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 core.domain.logger | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 core.domain.repository.remote | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 core.model.repository.local.datastore | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 core.storeapi.di | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 13 core.data.repository.remote | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 14 core.domain.repository.settings | 4 | |||||||||||||||||||||||||||||||||||||||
| 15 core.model.repository.local.database | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 core.database.dao | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 core.domain.repository.notes | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 18 core.domain.repository.system | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 core.domain.usecase.backup | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 core.ui.components | 3 | |||||||||||||||||||||||||||||||||||||||
| 21 feature.locksetup | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 core.domain.usecase.reminder | 1 | 2 | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||
| 23 core.domain.usecase.trash | 2 | 12 | ||||||||||||||||||||||||||||||||||||||
| 24 feature.home | 2 | 1 | 4 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 25 feature.lock | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 26 tools | 2 | 1 | 1 | 7 | ||||||||||||||||||||||||||||||||||||
| 27 core.domain.usecase | 1 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 core.domain.usecase.note | 5 | 3 | 17 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 feature.home.reminders | 1 | 1 | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 30 feature.home.trash | 1 | 1 | 1 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||
| 31 core.domain.usecase.archive | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 core.domain.usecase.label | 3 | 3 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 33 feature.home.notes | 1 | 1 | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 34 feature.notedetail | 1 | 3 | 3 | 4 | 1 | 4 | ||||||||||||||||||||||||||||||||||
| 35 feature.search | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 feature.update | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 core.data.repository.local | 5 | 1 | 4 | 4 | 5 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 38 feature.home.archive | 1 | 1 | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 39 feature.home.label | 1 | 1 | 2 | 1 | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||
| 40 core.data.di | 1 | 1 | 1 | 5 | 6 |
7→4 core.model uses core.model.wrapper✕
- Connections
- 1 pair of types, where a type in core.model uses a type in core.model.wrapper.
- The types involved
com.hellguy39.hellnotes.core.model.NoteWrapperKt→com.hellguy39.hellnotes.core.model.wrapper.Selectable
- Direction
- core.model uses core.model.wrapper, so a change to core.model.wrapper can break core.model, while a change to core.model can't break core.model.wrapper.
- Position
- Below the diagonal: core.model uses a module listed above it, which is the healthy direction.
7→15 core.model uses core.model.repository.local.database part of a loop✕
- Connections
- 7 pairs of types, where a type in core.model uses a type in core.model.repository.local.database.
- The types involved
com.hellguy39.hellnotes.core.model.NoteWrapper→com.hellguy39.hellnotes.core.model.repository.local.database.Checklistcom.hellguy39.hellnotes.core.model.NoteWrapper→com.hellguy39.hellnotes.core.model.repository.local.database.Labelcom.hellguy39.hellnotes.core.model.NoteWrapper→com.hellguy39.hellnotes.core.model.repository.local.database.Notecom.hellguy39.hellnotes.core.model.NoteWrapper→com.hellguy39.hellnotes.core.model.repository.local.database.Remindercom.hellguy39.hellnotes.core.model.NoteWrapperKt→com.hellguy39.hellnotes.core.model.repository.local.database.Checklistcom.hellguy39.hellnotes.core.model.NoteWrapperKt→com.hellguy39.hellnotes.core.model.repository.local.database.Labelcom.hellguy39.hellnotes.core.model.NoteWrapperKt→com.hellguy39.hellnotes.core.model.repository.local.database.Reminder
- Direction
- core.model uses core.model.repository.local.database, so a change to core.model.repository.local.database can break core.model, while a change to core.model can't break core.model.repository.local.database.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→1 core.storeapi.review.factory uses core.domain.repository.store✕
- Connections
- 1 pair of types, where a type in core.storeapi.review.factory uses a type in core.domain.repository.store.
- The types involved
com.hellguy39.hellnotes.core.storeapi.review.factory.ReviewProviderFactory→com.hellguy39.hellnotes.core.domain.repository.store.ReviewProvider
- Direction
- core.storeapi.review.factory uses core.domain.repository.store, so a change to core.domain.repository.store can break core.storeapi.review.factory, while a change to core.storeapi.review.factory can't break core.domain.repository.store.
- Position
- Below the diagonal: core.storeapi.review.factory uses a module listed above it, which is the healthy direction.
9→7 core.domain.logger uses core.model✕
- Connections
- 1 pair of types, where a type in core.domain.logger uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.core.domain.logger.AnalyticsLogger→com.hellguy39.hellnotes.core.model.AnalyticsEvent
- Direction
- core.domain.logger uses core.model, so a change to core.model can break core.domain.logger, while a change to core.domain.logger can't break core.model.
- Position
- Below the diagonal: core.domain.logger uses a module listed above it, which is the healthy direction.
10→3 core.domain.repository.remote uses core.model.repository.remote✕
- Connections
- 1 pair of types, where a type in core.domain.repository.remote uses a type in core.model.repository.remote.
- The types involved
com.hellguy39.hellnotes.core.domain.repository.remote.GithubRepositoryService→com.hellguy39.hellnotes.core.model.repository.remote.Release
- Direction
- core.domain.repository.remote uses core.model.repository.remote, so a change to core.model.repository.remote can break core.domain.repository.remote, while a change to core.domain.repository.remote can't break core.model.repository.remote.
- Position
- Below the diagonal: core.domain.repository.remote uses a module listed above it, which is the healthy direction.
10→7 core.domain.repository.remote uses core.model✕
- Connections
- 1 pair of types, where a type in core.domain.repository.remote uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.core.domain.repository.remote.GithubRepositoryService→com.hellguy39.hellnotes.core.model.Resource
- Direction
- core.domain.repository.remote uses core.model, so a change to core.model can break core.domain.repository.remote, while a change to core.domain.repository.remote can't break core.model.
- Position
- Below the diagonal: core.domain.repository.remote uses a module listed above it, which is the healthy direction.
11→7 core.model.repository.local.datastore uses core.model✕
- Connections
- 1 pair of types, where a type in core.model.repository.local.datastore uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.core.model.repository.local.datastore.SecurityState→com.hellguy39.hellnotes.core.model.LockScreenType
- Direction
- core.model.repository.local.datastore uses core.model, so a change to core.model can break core.model.repository.local.datastore, while a change to core.model.repository.local.datastore can't break core.model.
- Position
- Below the diagonal: core.model.repository.local.datastore uses a module listed above it, which is the healthy direction.
12→1 core.storeapi.di uses core.domain.repository.store✕
- Connections
- 1 pair of types, where a type in core.storeapi.di uses a type in core.domain.repository.store.
- The types involved
com.hellguy39.hellnotes.core.storeapi.di.StoreAPIModule→com.hellguy39.hellnotes.core.domain.repository.store.InAppStoreManager
- Direction
- core.storeapi.di uses core.domain.repository.store, so a change to core.domain.repository.store can break core.storeapi.di, while a change to core.storeapi.di can't break core.domain.repository.store.
- Position
- Below the diagonal: core.storeapi.di uses a module listed above it, which is the healthy direction.
12→8 core.storeapi.di uses core.storeapi.review.factory✕
- Connections
- 2 pairs of types, where a type in core.storeapi.di uses a type in core.storeapi.review.factory.
- The types involved
com.hellguy39.hellnotes.core.storeapi.di.StoreAPIModule→com.hellguy39.hellnotes.core.storeapi.review.factory.ReviewProviderFactorycom.hellguy39.hellnotes.core.storeapi.di.StoreAPIModule→com.hellguy39.hellnotes.core.storeapi.review.factory.ReviewProviderFactoryImpl
- Direction
- core.storeapi.di uses core.storeapi.review.factory, so a change to core.storeapi.review.factory can break core.storeapi.di, while a change to core.storeapi.di can't break core.storeapi.review.factory.
- Position
- Below the diagonal: core.storeapi.di uses a module listed above it, which is the healthy direction.
13→3 core.data.repository.remote uses core.model.repository.remote✕
- Connections
- 1 pair of types, where a type in core.data.repository.remote uses a type in core.model.repository.remote.
- The types involved
com.hellguy39.hellnotes.core.data.repository.remote.GithubRepositoryServiceImpl→com.hellguy39.hellnotes.core.model.repository.remote.Release
- Direction
- core.data.repository.remote uses core.model.repository.remote, so a change to core.model.repository.remote can break core.data.repository.remote, while a change to core.data.repository.remote can't break core.model.repository.remote.
- Position
- Below the diagonal: core.data.repository.remote uses a module listed above it, which is the healthy direction.
13→7 core.data.repository.remote uses core.model✕
- Connections
- 1 pair of types, where a type in core.data.repository.remote uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.core.data.repository.remote.GithubRepositoryServiceImpl→com.hellguy39.hellnotes.core.model.Resource
- Direction
- core.data.repository.remote uses core.model, so a change to core.model can break core.data.repository.remote, while a change to core.data.repository.remote can't break core.model.
- Position
- Below the diagonal: core.data.repository.remote uses a module listed above it, which is the healthy direction.
13→10 core.data.repository.remote uses core.domain.repository.remote✕
- Connections
- 1 pair of types, where a type in core.data.repository.remote uses a type in core.domain.repository.remote.
- The types involved
com.hellguy39.hellnotes.core.data.repository.remote.GithubRepositoryServiceImpl→com.hellguy39.hellnotes.core.domain.repository.remote.GithubRepositoryService
- Direction
- core.data.repository.remote uses core.domain.repository.remote, so a change to core.domain.repository.remote can break core.data.repository.remote, while a change to core.data.repository.remote can't break core.domain.repository.remote.
- Position
- Below the diagonal: core.data.repository.remote uses a module listed above it, which is the healthy direction.
14→11 core.domain.repository.settings uses core.model.repository.local.datastore✕
- Connections
- 4 pairs of types, where a type in core.domain.repository.settings uses a type in core.model.repository.local.datastore.
- The types involved
com.hellguy39.hellnotes.core.domain.repository.settings.DataStoreRepository→com.hellguy39.hellnotes.core.model.repository.local.datastore.ListStylecom.hellguy39.hellnotes.core.domain.repository.settings.DataStoreRepository→com.hellguy39.hellnotes.core.model.repository.local.datastore.NoteStylecom.hellguy39.hellnotes.core.domain.repository.settings.DataStoreRepository→com.hellguy39.hellnotes.core.model.repository.local.datastore.NoteSwipesStatecom.hellguy39.hellnotes.core.domain.repository.settings.DataStoreRepository→com.hellguy39.hellnotes.core.model.repository.local.datastore.SecurityState
- Direction
- core.domain.repository.settings uses core.model.repository.local.datastore, so a change to core.model.repository.local.datastore can break core.domain.repository.settings, while a change to core.domain.repository.settings can't break core.model.repository.local.datastore.
- Position
- Below the diagonal: core.domain.repository.settings uses a module listed above it, which is the healthy direction.
15→11 core.model.repository.local.database uses core.model.repository.local.datastore✕
- Connections
- 1 pair of types, where a type in core.model.repository.local.database uses a type in core.model.repository.local.datastore.
- The types involved
com.hellguy39.hellnotes.core.model.repository.local.database.Reminder→com.hellguy39.hellnotes.core.model.repository.local.datastore.Repeat
- Direction
- core.model.repository.local.database uses core.model.repository.local.datastore, so a change to core.model.repository.local.datastore can break core.model.repository.local.database, while a change to core.model.repository.local.database can't break core.model.repository.local.datastore.
- Position
- Below the diagonal: core.model.repository.local.database uses a module listed above it, which is the healthy direction.
16→15 core.database.dao uses core.model.repository.local.database✕
- Connections
- 1 pair of types, where a type in core.database.dao uses a type in core.model.repository.local.database.
- The types involved
com.hellguy39.hellnotes.core.database.dao.TrashDao→com.hellguy39.hellnotes.core.model.repository.local.database.Note
- Direction
- core.database.dao uses core.model.repository.local.database, so a change to core.model.repository.local.database can break core.database.dao, while a change to core.database.dao can't break core.model.repository.local.database.
- Position
- Below the diagonal: core.database.dao uses a module listed above it, which is the healthy direction.
17→11 core.domain.repository.notes uses core.model.repository.local.datastore✕
- Connections
- 1 pair of types, where a type in core.domain.repository.notes uses a type in core.model.repository.local.datastore.
- The types involved
com.hellguy39.hellnotes.core.domain.repository.notes.NoteActionController→com.hellguy39.hellnotes.core.model.repository.local.datastore.NoteSwipe
- Direction
- core.domain.repository.notes uses core.model.repository.local.datastore, so a change to core.model.repository.local.datastore can break core.domain.repository.notes, while a change to core.domain.repository.notes can't break core.model.repository.local.datastore.
- Position
- Below the diagonal: core.domain.repository.notes uses a module listed above it, which is the healthy direction.
17→15 core.domain.repository.notes uses core.model.repository.local.database✕
- Connections
- 5 pairs of types, where a type in core.domain.repository.notes uses a type in core.model.repository.local.database.
- The types involved
com.hellguy39.hellnotes.core.domain.repository.notes.ChecklistRepository→com.hellguy39.hellnotes.core.model.repository.local.database.Checklistcom.hellguy39.hellnotes.core.domain.repository.notes.LabelRepository→com.hellguy39.hellnotes.core.model.repository.local.database.Labelcom.hellguy39.hellnotes.core.domain.repository.notes.NoteRepository→com.hellguy39.hellnotes.core.model.repository.local.database.Notecom.hellguy39.hellnotes.core.domain.repository.notes.NoteRepositoryKt→com.hellguy39.hellnotes.core.model.repository.local.database.NoteBuildercom.hellguy39.hellnotes.core.domain.repository.notes.ReminderRepository→com.hellguy39.hellnotes.core.model.repository.local.database.Reminder
- Direction
- core.domain.repository.notes uses core.model.repository.local.database, so a change to core.model.repository.local.database can break core.domain.repository.notes, while a change to core.domain.repository.notes can't break core.model.repository.local.database.
- Position
- Below the diagonal: core.domain.repository.notes uses a module listed above it, which is the healthy direction.
18→7 core.domain.repository.system uses core.model✕
- Connections
- 1 pair of types, where a type in core.domain.repository.system uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.core.domain.repository.system.LanguageHolder→com.hellguy39.hellnotes.core.model.Language
- Direction
- core.domain.repository.system uses core.model, so a change to core.model can break core.domain.repository.system, while a change to core.domain.repository.system can't break core.model.
- Position
- Below the diagonal: core.domain.repository.system uses a module listed above it, which is the healthy direction.
18→15 core.domain.repository.system uses core.model.repository.local.database✕
- Connections
- 1 pair of types, where a type in core.domain.repository.system uses a type in core.model.repository.local.database.
- The types involved
com.hellguy39.hellnotes.core.domain.repository.system.AlarmScheduler→com.hellguy39.hellnotes.core.model.repository.local.database.Reminder
- Direction
- core.domain.repository.system uses core.model.repository.local.database, so a change to core.model.repository.local.database can break core.domain.repository.system, while a change to core.domain.repository.system can't break core.model.repository.local.database.
- Position
- Below the diagonal: core.domain.repository.system uses a module listed above it, which is the healthy direction.
19→2 core.domain.usecase.backup uses core.model.repository.local.file✕
- Connections
- 2 pairs of types, where a type in core.domain.usecase.backup uses a type in core.model.repository.local.file.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.backup.BackupDatabaseUseCase→com.hellguy39.hellnotes.core.model.repository.local.file.Backupcom.hellguy39.hellnotes.core.domain.usecase.backup.RestoreDatabaseUseCase→com.hellguy39.hellnotes.core.model.repository.local.file.Restore
- Direction
- core.domain.usecase.backup uses core.model.repository.local.file, so a change to core.model.repository.local.file can break core.domain.usecase.backup, while a change to core.domain.usecase.backup can't break core.model.repository.local.file.
- Position
- Below the diagonal: core.domain.usecase.backup uses a module listed above it, which is the healthy direction.
19→7 core.domain.usecase.backup uses core.model✕
- Connections
- 2 pairs of types, where a type in core.domain.usecase.backup uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.backup.BackupDatabaseUseCase→com.hellguy39.hellnotes.core.model.Resourcecom.hellguy39.hellnotes.core.domain.usecase.backup.RestoreDatabaseUseCase→com.hellguy39.hellnotes.core.model.Resource
- Direction
- core.domain.usecase.backup uses core.model, so a change to core.model can break core.domain.usecase.backup, while a change to core.domain.usecase.backup can't break core.model.
- Position
- Below the diagonal: core.domain.usecase.backup uses a module listed above it, which is the healthy direction.
19→14 core.domain.usecase.backup uses core.domain.repository.settings✕
- Connections
- 1 pair of types, where a type in core.domain.usecase.backup uses a type in core.domain.repository.settings.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.backup.BackupDatabaseUseCase→com.hellguy39.hellnotes.core.domain.repository.settings.DataStoreRepository
- Direction
- core.domain.usecase.backup uses core.domain.repository.settings, so a change to core.domain.repository.settings can break core.domain.usecase.backup, while a change to core.domain.usecase.backup can't break core.domain.repository.settings.
- Position
- Below the diagonal: core.domain.usecase.backup uses a module listed above it, which is the healthy direction.
20→15 core.ui.components uses core.model.repository.local.database✕
- Connections
- 3 pairs of types, where a type in core.ui.components uses a type in core.model.repository.local.database.
- The types involved
com.hellguy39.hellnotes.core.ui.components.NoteChecklistGroupKt→com.hellguy39.hellnotes.core.model.repository.local.database.Checklistcom.hellguy39.hellnotes.core.ui.components.NoteChipGroupKt→com.hellguy39.hellnotes.core.model.repository.local.database.Labelcom.hellguy39.hellnotes.core.ui.components.NoteChipGroupKt→com.hellguy39.hellnotes.core.model.repository.local.database.Reminder
- Direction
- core.ui.components uses core.model.repository.local.database, so a change to core.model.repository.local.database can break core.ui.components, while a change to core.ui.components can't break core.model.repository.local.database.
- Position
- Below the diagonal: core.ui.components uses a module listed above it, which is the healthy direction.
21→7 feature.locksetup uses core.model✕
- Connections
- 1 pair of types, where a type in feature.locksetup uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.feature.locksetup.LockSetupUiState→com.hellguy39.hellnotes.core.model.LockScreenType
- Direction
- feature.locksetup uses core.model, so a change to core.model can break feature.locksetup, while a change to feature.locksetup can't break core.model.
- Position
- Below the diagonal: feature.locksetup uses a module listed above it, which is the healthy direction.
21→11 feature.locksetup uses core.model.repository.local.datastore✕
- Connections
- 1 pair of types, where a type in feature.locksetup uses a type in core.model.repository.local.datastore.
- The types involved
com.hellguy39.hellnotes.feature.locksetup.LockSetupUiState→com.hellguy39.hellnotes.core.model.repository.local.datastore.SecurityState
- Direction
- feature.locksetup uses core.model.repository.local.datastore, so a change to core.model.repository.local.datastore can break feature.locksetup, while a change to feature.locksetup can't break core.model.repository.local.datastore.
- Position
- Below the diagonal: feature.locksetup uses a module listed above it, which is the healthy direction.
21→14 feature.locksetup uses core.domain.repository.settings✕
- Connections
- 1 pair of types, where a type in feature.locksetup uses a type in core.domain.repository.settings.
- The types involved
com.hellguy39.hellnotes.feature.locksetup.LockSetupViewModel→com.hellguy39.hellnotes.core.domain.repository.settings.DataStoreRepository
- Direction
- feature.locksetup uses core.domain.repository.settings, so a change to core.domain.repository.settings can break feature.locksetup, while a change to feature.locksetup can't break core.domain.repository.settings.
- Position
- Below the diagonal: feature.locksetup uses a module listed above it, which is the healthy direction.
22→7 core.domain.usecase.reminder uses core.model✕
- Connections
- 1 pair of types, where a type in core.domain.usecase.reminder uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.reminder.GetAllNoteWrappersWithRemindersUseCase→com.hellguy39.hellnotes.core.model.NoteWrapper
- Direction
- core.domain.usecase.reminder uses core.model, so a change to core.model can break core.domain.usecase.reminder, while a change to core.domain.usecase.reminder can't break core.model.
- Position
- Below the diagonal: core.domain.usecase.reminder uses a module listed above it, which is the healthy direction.
22→15 core.domain.usecase.reminder uses core.model.repository.local.database✕
- Connections
- 2 pairs of types, where a type in core.domain.usecase.reminder uses a type in core.model.repository.local.database.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.reminder.CreateReminderUseCase→com.hellguy39.hellnotes.core.model.repository.local.database.Remindercom.hellguy39.hellnotes.core.domain.usecase.reminder.UpdateReminderUseCase→com.hellguy39.hellnotes.core.model.repository.local.database.Reminder
- Direction
- core.domain.usecase.reminder uses core.model.repository.local.database, so a change to core.model.repository.local.database can break core.domain.usecase.reminder, while a change to core.domain.usecase.reminder can't break core.model.repository.local.database.
- Position
- Below the diagonal: core.domain.usecase.reminder uses a module listed above it, which is the healthy direction.
22→17 core.domain.usecase.reminder uses core.domain.repository.notes✕
- Connections
- 4 pairs of types, where a type in core.domain.usecase.reminder uses a type in core.domain.repository.notes.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.reminder.ActivateReminderUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ReminderRepositorycom.hellguy39.hellnotes.core.domain.usecase.reminder.CreateReminderUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ReminderRepositorycom.hellguy39.hellnotes.core.domain.usecase.reminder.DeleteReminderUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ReminderRepositorycom.hellguy39.hellnotes.core.domain.usecase.reminder.UpdateReminderUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ReminderRepository
- Direction
- core.domain.usecase.reminder uses core.domain.repository.notes, so a change to core.domain.repository.notes can break core.domain.usecase.reminder, while a change to core.domain.usecase.reminder can't break core.domain.repository.notes.
- Position
- Below the diagonal: core.domain.usecase.reminder uses a module listed above it, which is the healthy direction.
22→18 core.domain.usecase.reminder uses core.domain.repository.system✕
- Connections
- 4 pairs of types, where a type in core.domain.usecase.reminder uses a type in core.domain.repository.system.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.reminder.ActivateReminderUseCase→com.hellguy39.hellnotes.core.domain.repository.system.AlarmSchedulercom.hellguy39.hellnotes.core.domain.usecase.reminder.CreateReminderUseCase→com.hellguy39.hellnotes.core.domain.repository.system.AlarmSchedulercom.hellguy39.hellnotes.core.domain.usecase.reminder.DeleteReminderUseCase→com.hellguy39.hellnotes.core.domain.repository.system.AlarmSchedulercom.hellguy39.hellnotes.core.domain.usecase.reminder.UpdateReminderUseCase→com.hellguy39.hellnotes.core.domain.repository.system.AlarmScheduler
- Direction
- core.domain.usecase.reminder uses core.domain.repository.system, so a change to core.domain.repository.system can break core.domain.usecase.reminder, while a change to core.domain.usecase.reminder can't break core.domain.repository.system.
- Position
- Below the diagonal: core.domain.usecase.reminder uses a module listed above it, which is the healthy direction.
22→28 core.domain.usecase.reminder uses core.domain.usecase.note part of a loop✕
- Connections
- 1 pair of types, where a type in core.domain.usecase.reminder uses a type in core.domain.usecase.note.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.reminder.GetAllNoteWrappersWithRemindersUseCase→com.hellguy39.hellnotes.core.domain.usecase.note.GetAllNoteWrappersFlowUseCase
- Direction
- core.domain.usecase.reminder uses core.domain.usecase.note, so a change to core.domain.usecase.note can break core.domain.usecase.reminder, while a change to core.domain.usecase.reminder can't break core.domain.usecase.note.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→7 core.domain.usecase.trash uses core.model✕
- Connections
- 2 pairs of types, where a type in core.domain.usecase.trash uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.trash.GetAllNoteWrappersAtTrashFlowUseCase→com.hellguy39.hellnotes.core.model.NoteWrappercom.hellguy39.hellnotes.core.domain.usecase.trash.GetAllNoteWrappersAtTrashUseCase→com.hellguy39.hellnotes.core.model.NoteWrapper
- Direction
- core.domain.usecase.trash uses core.model, so a change to core.model can break core.domain.usecase.trash, while a change to core.domain.usecase.trash can't break core.model.
- Position
- Below the diagonal: core.domain.usecase.trash uses a module listed above it, which is the healthy direction.
23→17 core.domain.usecase.trash uses core.domain.repository.notes✕
- Connections
- 12 pairs of types, where a type in core.domain.usecase.trash uses a type in core.domain.repository.notes.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.trash.DeleteNoteUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ChecklistRepositorycom.hellguy39.hellnotes.core.domain.usecase.trash.DeleteNoteUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.LabelRepositorycom.hellguy39.hellnotes.core.domain.usecase.trash.DeleteNoteUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.NoteRepositorycom.hellguy39.hellnotes.core.domain.usecase.trash.DeleteNoteUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ReminderRepositorycom.hellguy39.hellnotes.core.domain.usecase.trash.GetAllNoteWrappersAtTrashFlowUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ChecklistRepositorycom.hellguy39.hellnotes.core.domain.usecase.trash.GetAllNoteWrappersAtTrashFlowUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.LabelRepositorycom.hellguy39.hellnotes.core.domain.usecase.trash.GetAllNoteWrappersAtTrashFlowUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.NoteRepositorycom.hellguy39.hellnotes.core.domain.usecase.trash.GetAllNoteWrappersAtTrashFlowUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ReminderRepositorycom.hellguy39.hellnotes.core.domain.usecase.trash.GetAllNoteWrappersAtTrashUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ChecklistRepositorycom.hellguy39.hellnotes.core.domain.usecase.trash.GetAllNoteWrappersAtTrashUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.LabelRepositorycom.hellguy39.hellnotes.core.domain.usecase.trash.GetAllNoteWrappersAtTrashUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.NoteRepositorycom.hellguy39.hellnotes.core.domain.usecase.trash.GetAllNoteWrappersAtTrashUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ReminderRepository
- Direction
- core.domain.usecase.trash uses core.domain.repository.notes, so a change to core.domain.repository.notes can break core.domain.usecase.trash, while a change to core.domain.usecase.trash can't break core.domain.repository.notes.
- Position
- Below the diagonal: core.domain.usecase.trash uses a module listed above it, which is the healthy direction.
24→1 feature.home uses core.domain.repository.store✕
- Connections
- 2 pairs of types, where a type in feature.home uses a type in core.domain.repository.store.
- The types involved
com.hellguy39.hellnotes.feature.home.HomeUiState→com.hellguy39.hellnotes.core.domain.repository.store.UpdateStatecom.hellguy39.hellnotes.feature.home.HomeViewModel→com.hellguy39.hellnotes.core.domain.repository.store.InAppStoreManager
- Direction
- feature.home uses core.domain.repository.store, so a change to core.domain.repository.store can break feature.home, while a change to feature.home can't break core.domain.repository.store.
- Position
- Below the diagonal: feature.home uses a module listed above it, which is the healthy direction.
24→5 feature.home uses core.ui.resources.wrapper✕
- Connections
- 1 pair of types, where a type in feature.home uses a type in core.ui.resources.wrapper.
- The types involved
com.hellguy39.hellnotes.feature.home.HomeState→com.hellguy39.hellnotes.core.ui.resources.wrapper.UiText
- Direction
- feature.home uses core.ui.resources.wrapper, so a change to core.ui.resources.wrapper can break feature.home, while a change to feature.home can't break core.ui.resources.wrapper.
- Position
- Below the diagonal: feature.home uses a module listed above it, which is the healthy direction.
24→11 feature.home uses core.model.repository.local.datastore✕
- Connections
- 4 pairs of types, where a type in feature.home uses a type in core.model.repository.local.datastore.
- The types involved
com.hellguy39.hellnotes.feature.home.VisualState→com.hellguy39.hellnotes.core.model.repository.local.datastore.ListStylecom.hellguy39.hellnotes.feature.home.VisualState→com.hellguy39.hellnotes.core.model.repository.local.datastore.NoteStylecom.hellguy39.hellnotes.feature.home.VisualState→com.hellguy39.hellnotes.core.model.repository.local.datastore.NoteSwipesStatecom.hellguy39.hellnotes.feature.home.VisualsViewModel→com.hellguy39.hellnotes.core.model.repository.local.datastore.NoteSwipe
- Direction
- feature.home uses core.model.repository.local.datastore, so a change to core.model.repository.local.datastore can break feature.home, while a change to feature.home can't break core.model.repository.local.datastore.
- Position
- Below the diagonal: feature.home uses a module listed above it, which is the healthy direction.
24→14 feature.home uses core.domain.repository.settings✕
- Connections
- 1 pair of types, where a type in feature.home uses a type in core.domain.repository.settings.
- The types involved
com.hellguy39.hellnotes.feature.home.VisualsViewModel→com.hellguy39.hellnotes.core.domain.repository.settings.DataStoreRepository
- Direction
- feature.home uses core.domain.repository.settings, so a change to core.domain.repository.settings can break feature.home, while a change to feature.home can't break core.domain.repository.settings.
- Position
- Below the diagonal: feature.home uses a module listed above it, which is the healthy direction.
24→15 feature.home uses core.model.repository.local.database✕
- Connections
- 2 pairs of types, where a type in feature.home uses a type in core.model.repository.local.database.
- The types involved
com.hellguy39.hellnotes.feature.home.HomeNavGraphKt→com.hellguy39.hellnotes.core.model.repository.local.database.Labelcom.hellguy39.hellnotes.feature.home.HomeUiState→com.hellguy39.hellnotes.core.model.repository.local.database.Label
- Direction
- feature.home uses core.model.repository.local.database, so a change to core.model.repository.local.database can break feature.home, while a change to feature.home can't break core.model.repository.local.database.
- Position
- Below the diagonal: feature.home uses a module listed above it, which is the healthy direction.
24→17 feature.home uses core.domain.repository.notes✕
- Connections
- 1 pair of types, where a type in feature.home uses a type in core.domain.repository.notes.
- The types involved
com.hellguy39.hellnotes.feature.home.HomeViewModel→com.hellguy39.hellnotes.core.domain.repository.notes.LabelRepository
- Direction
- feature.home uses core.domain.repository.notes, so a change to core.domain.repository.notes can break feature.home, while a change to feature.home can't break core.domain.repository.notes.
- Position
- Below the diagonal: feature.home uses a module listed above it, which is the healthy direction.
25→11 feature.lock uses core.model.repository.local.datastore✕
- Connections
- 2 pairs of types, where a type in feature.lock uses a type in core.model.repository.local.datastore.
- The types involved
com.hellguy39.hellnotes.feature.lock.LockUiState→com.hellguy39.hellnotes.core.model.repository.local.datastore.SecurityStatecom.hellguy39.hellnotes.feature.lock.LockViewModel→com.hellguy39.hellnotes.core.model.repository.local.datastore.SecurityState
- Direction
- feature.lock uses core.model.repository.local.datastore, so a change to core.model.repository.local.datastore can break feature.lock, while a change to feature.lock can't break core.model.repository.local.datastore.
- Position
- Below the diagonal: feature.lock uses a module listed above it, which is the healthy direction.
25→14 feature.lock uses core.domain.repository.settings✕
- Connections
- 1 pair of types, where a type in feature.lock uses a type in core.domain.repository.settings.
- The types involved
com.hellguy39.hellnotes.feature.lock.LockViewModel→com.hellguy39.hellnotes.core.domain.repository.settings.DataStoreRepository
- Direction
- feature.lock uses core.domain.repository.settings, so a change to core.domain.repository.settings can break feature.lock, while a change to feature.lock can't break core.domain.repository.settings.
- Position
- Below the diagonal: feature.lock uses a module listed above it, which is the healthy direction.
25→18 feature.lock uses core.domain.repository.system✕
- Connections
- 2 pairs of types, where a type in feature.lock uses a type in core.domain.repository.system.
- The types involved
com.hellguy39.hellnotes.feature.lock.LockRouteKt→com.hellguy39.hellnotes.core.domain.repository.system.BiometricAuthenticatorcom.hellguy39.hellnotes.feature.lock.LockViewModel→com.hellguy39.hellnotes.core.domain.repository.system.BiometricAuthenticator
- Direction
- feature.lock uses core.domain.repository.system, so a change to core.domain.repository.system can break feature.lock, while a change to feature.lock can't break core.domain.repository.system.
- Position
- Below the diagonal: feature.lock uses a module listed above it, which is the healthy direction.
26→7 tools uses core.model✕
- Connections
- 2 pairs of types, where a type in tools uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.tools.AnalyticsLoggerImpl→com.hellguy39.hellnotes.core.model.AnalyticsEventcom.hellguy39.hellnotes.tools.LanguageHolderImpl→com.hellguy39.hellnotes.core.model.Language
- Direction
- tools uses core.model, so a change to core.model can break tools, while a change to tools can't break core.model.
- Position
- Below the diagonal: tools uses a module listed above it, which is the healthy direction.
26→9 tools uses core.domain.logger✕
- Connections
- 1 pair of types, where a type in tools uses a type in core.domain.logger.
- The types involved
com.hellguy39.hellnotes.tools.AnalyticsLoggerImpl→com.hellguy39.hellnotes.core.domain.logger.AnalyticsLogger
- Direction
- tools uses core.domain.logger, so a change to core.domain.logger can break tools, while a change to tools can't break core.domain.logger.
- Position
- Below the diagonal: tools uses a module listed above it, which is the healthy direction.
26→15 tools uses core.model.repository.local.database✕
- Connections
- 1 pair of types, where a type in tools uses a type in core.model.repository.local.database.
- The types involved
com.hellguy39.hellnotes.tools.AlarmSchedulerImpl→com.hellguy39.hellnotes.core.model.repository.local.database.Reminder
- Direction
- tools uses core.model.repository.local.database, so a change to core.model.repository.local.database can break tools, while a change to tools can't break core.model.repository.local.database.
- Position
- Below the diagonal: tools uses a module listed above it, which is the healthy direction.
26→18 tools uses core.domain.repository.system✕
- Connections
- 7 pairs of types, where a type in tools uses a type in core.domain.repository.system.
- The types involved
com.hellguy39.hellnotes.tools.AlarmSchedulerImpl→com.hellguy39.hellnotes.core.domain.repository.system.AlarmSchedulercom.hellguy39.hellnotes.tools.BiometricAuthenticatorImpl→com.hellguy39.hellnotes.core.domain.repository.system.AuthenticationResultcom.hellguy39.hellnotes.tools.BiometricAuthenticatorImpl→com.hellguy39.hellnotes.core.domain.repository.system.BiometricAuthenticatorcom.hellguy39.hellnotes.tools.BiometricAuthenticatorImpl→com.hellguy39.hellnotes.core.domain.repository.system.DeviceBiometricStatuscom.hellguy39.hellnotes.tools.DownloaderImpl→com.hellguy39.hellnotes.core.domain.repository.system.Downloadercom.hellguy39.hellnotes.tools.InAppNotificationManagerImpl→com.hellguy39.hellnotes.core.domain.repository.system.InAppNotificationManagercom.hellguy39.hellnotes.tools.LanguageHolderImpl→com.hellguy39.hellnotes.core.domain.repository.system.LanguageHolder
- Direction
- tools uses core.domain.repository.system, so a change to core.domain.repository.system can break tools, while a change to tools can't break core.domain.repository.system.
- Position
- Below the diagonal: tools uses a module listed above it, which is the healthy direction.
27→3 core.domain.usecase uses core.model.repository.remote✕
- Connections
- 1 pair of types, where a type in core.domain.usecase uses a type in core.model.repository.remote.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.CheckForUpdatesUseCase→com.hellguy39.hellnotes.core.model.repository.remote.Release
- Direction
- core.domain.usecase uses core.model.repository.remote, so a change to core.model.repository.remote can break core.domain.usecase, while a change to core.domain.usecase can't break core.model.repository.remote.
- Position
- Below the diagonal: core.domain.usecase uses a module listed above it, which is the healthy direction.
27→14 core.domain.usecase uses core.domain.repository.settings✕
- Connections
- 1 pair of types, where a type in core.domain.usecase uses a type in core.domain.repository.settings.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.ResetAppUseCase→com.hellguy39.hellnotes.core.domain.repository.settings.DataStoreRepository
- Direction
- core.domain.usecase uses core.domain.repository.settings, so a change to core.domain.repository.settings can break core.domain.usecase, while a change to core.domain.usecase can't break core.domain.repository.settings.
- Position
- Below the diagonal: core.domain.usecase uses a module listed above it, which is the healthy direction.
27→17 core.domain.usecase uses core.domain.repository.notes✕
- Connections
- 4 pairs of types, where a type in core.domain.usecase uses a type in core.domain.repository.notes.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.ResetAppUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ChecklistRepositorycom.hellguy39.hellnotes.core.domain.usecase.ResetAppUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.LabelRepositorycom.hellguy39.hellnotes.core.domain.usecase.ResetAppUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.NoteRepositorycom.hellguy39.hellnotes.core.domain.usecase.ResetAppUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ReminderRepository
- Direction
- core.domain.usecase uses core.domain.repository.notes, so a change to core.domain.repository.notes can break core.domain.usecase, while a change to core.domain.usecase can't break core.domain.repository.notes.
- Position
- Below the diagonal: core.domain.usecase uses a module listed above it, which is the healthy direction.
27→22 core.domain.usecase uses core.domain.usecase.reminder✕
- Connections
- 1 pair of types, where a type in core.domain.usecase uses a type in core.domain.usecase.reminder.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.ResetAppUseCase→com.hellguy39.hellnotes.core.domain.usecase.reminder.DeleteReminderUseCase
- Direction
- core.domain.usecase uses core.domain.usecase.reminder, so a change to core.domain.usecase.reminder can break core.domain.usecase, while a change to core.domain.usecase can't break core.domain.usecase.reminder.
- Position
- Below the diagonal: core.domain.usecase uses a module listed above it, which is the healthy direction.
28→7 core.domain.usecase.note uses core.model✕
- Connections
- 5 pairs of types, where a type in core.domain.usecase.note uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.note.CopyNoteUseCase→com.hellguy39.hellnotes.core.model.NoteWrappercom.hellguy39.hellnotes.core.domain.usecase.note.GetAllNoteWrappersFlowUseCase→com.hellguy39.hellnotes.core.model.NoteWrappercom.hellguy39.hellnotes.core.domain.usecase.note.GetAllNoteWrappersUseCase→com.hellguy39.hellnotes.core.model.NoteWrappercom.hellguy39.hellnotes.core.domain.usecase.note.GetNoteWrapperByIdUseCase→com.hellguy39.hellnotes.core.model.NoteWrappercom.hellguy39.hellnotes.core.domain.usecase.note.PostProcessNoteUseCase→com.hellguy39.hellnotes.core.model.NoteWrapper
- Direction
- core.domain.usecase.note uses core.model, so a change to core.model can break core.domain.usecase.note, while a change to core.domain.usecase.note can't break core.model.
- Position
- Below the diagonal: core.domain.usecase.note uses a module listed above it, which is the healthy direction.
28→15 core.domain.usecase.note uses core.model.repository.local.database✕
- Connections
- 3 pairs of types, where a type in core.domain.usecase.note uses a type in core.model.repository.local.database.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.note.PostProcessNoteUseCase→com.hellguy39.hellnotes.core.model.repository.local.database.Checklistcom.hellguy39.hellnotes.core.domain.usecase.note.PostProcessNoteUseCase→com.hellguy39.hellnotes.core.model.repository.local.database.ChecklistItemcom.hellguy39.hellnotes.core.domain.usecase.note.PostProcessNoteUseCase→com.hellguy39.hellnotes.core.model.repository.local.database.Note
- Direction
- core.domain.usecase.note uses core.model.repository.local.database, so a change to core.model.repository.local.database can break core.domain.usecase.note, while a change to core.domain.usecase.note can't break core.model.repository.local.database.
- Position
- Below the diagonal: core.domain.usecase.note uses a module listed above it, which is the healthy direction.
28→17 core.domain.usecase.note uses core.domain.repository.notes✕
- Connections
- 17 pairs of types, where a type in core.domain.usecase.note uses a type in core.domain.repository.notes.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.note.CopyNoteUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ChecklistRepositorycom.hellguy39.hellnotes.core.domain.usecase.note.CopyNoteUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.LabelRepositorycom.hellguy39.hellnotes.core.domain.usecase.note.CopyNoteUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.NoteRepositorycom.hellguy39.hellnotes.core.domain.usecase.note.GetAllNoteWrappersFlowUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ChecklistRepositorycom.hellguy39.hellnotes.core.domain.usecase.note.GetAllNoteWrappersFlowUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.LabelRepositorycom.hellguy39.hellnotes.core.domain.usecase.note.GetAllNoteWrappersFlowUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.NoteRepositorycom.hellguy39.hellnotes.core.domain.usecase.note.GetAllNoteWrappersFlowUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ReminderRepositorycom.hellguy39.hellnotes.core.domain.usecase.note.GetAllNoteWrappersUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ChecklistRepositorycom.hellguy39.hellnotes.core.domain.usecase.note.GetAllNoteWrappersUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.LabelRepositorycom.hellguy39.hellnotes.core.domain.usecase.note.GetAllNoteWrappersUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.NoteRepositorycom.hellguy39.hellnotes.core.domain.usecase.note.GetAllNoteWrappersUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ReminderRepositorycom.hellguy39.hellnotes.core.domain.usecase.note.GetNoteWrapperByIdUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ChecklistRepositorycom.hellguy39.hellnotes.core.domain.usecase.note.GetNoteWrapperByIdUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.LabelRepositorycom.hellguy39.hellnotes.core.domain.usecase.note.GetNoteWrapperByIdUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.NoteRepositorycom.hellguy39.hellnotes.core.domain.usecase.note.GetNoteWrapperByIdUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.ReminderRepositorycom.hellguy39.hellnotes.core.domain.usecase.note.MoveNoteToTrashUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.NoteRepositorycom.hellguy39.hellnotes.core.domain.usecase.note.RestoreNoteFromTrashUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.NoteRepository
- Direction
- core.domain.usecase.note uses core.domain.repository.notes, so a change to core.domain.repository.notes can break core.domain.usecase.note, while a change to core.domain.usecase.note can't break core.domain.repository.notes.
- Position
- Below the diagonal: core.domain.usecase.note uses a module listed above it, which is the healthy direction.
28→22 core.domain.usecase.note uses core.domain.usecase.reminder✕
- Connections
- 1 pair of types, where a type in core.domain.usecase.note uses a type in core.domain.usecase.reminder.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.note.CopyNoteUseCase→com.hellguy39.hellnotes.core.domain.usecase.reminder.CreateReminderUseCase
- Direction
- core.domain.usecase.note uses core.domain.usecase.reminder, so a change to core.domain.usecase.reminder can break core.domain.usecase.note, while a change to core.domain.usecase.note can't break core.domain.usecase.reminder.
- Position
- Below the diagonal: core.domain.usecase.note uses a module listed above it, which is the healthy direction.
29→4 feature.home.reminders uses core.model.wrapper✕
- Connections
- 1 pair of types, where a type in feature.home.reminders uses a type in core.model.wrapper.
- The types involved
com.hellguy39.hellnotes.feature.home.reminders.RemindersUiState→com.hellguy39.hellnotes.core.model.wrapper.Selectable
- Direction
- feature.home.reminders uses core.model.wrapper, so a change to core.model.wrapper can break feature.home.reminders, while a change to feature.home.reminders can't break core.model.wrapper.
- Position
- Below the diagonal: feature.home.reminders uses a module listed above it, which is the healthy direction.
29→7 feature.home.reminders uses core.model✕
- Connections
- 1 pair of types, where a type in feature.home.reminders uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.feature.home.reminders.RemindersUiState→com.hellguy39.hellnotes.core.model.NoteWrapper
- Direction
- feature.home.reminders uses core.model, so a change to core.model can break feature.home.reminders, while a change to feature.home.reminders can't break core.model.
- Position
- Below the diagonal: feature.home.reminders uses a module listed above it, which is the healthy direction.
29→11 feature.home.reminders uses core.model.repository.local.datastore✕
- Connections
- 1 pair of types, where a type in feature.home.reminders uses a type in core.model.repository.local.datastore.
- The types involved
com.hellguy39.hellnotes.feature.home.reminders.RemindersViewModel→com.hellguy39.hellnotes.core.model.repository.local.datastore.NoteSwipe
- Direction
- feature.home.reminders uses core.model.repository.local.datastore, so a change to core.model.repository.local.datastore can break feature.home.reminders, while a change to feature.home.reminders can't break core.model.repository.local.datastore.
- Position
- Below the diagonal: feature.home.reminders uses a module listed above it, which is the healthy direction.
29→17 feature.home.reminders uses core.domain.repository.notes✕
- Connections
- 1 pair of types, where a type in feature.home.reminders uses a type in core.domain.repository.notes.
- The types involved
com.hellguy39.hellnotes.feature.home.reminders.RemindersViewModel→com.hellguy39.hellnotes.core.domain.repository.notes.NoteActionController
- Direction
- feature.home.reminders uses core.domain.repository.notes, so a change to core.domain.repository.notes can break feature.home.reminders, while a change to feature.home.reminders can't break core.domain.repository.notes.
- Position
- Below the diagonal: feature.home.reminders uses a module listed above it, which is the healthy direction.
29→22 feature.home.reminders uses core.domain.usecase.reminder✕
- Connections
- 1 pair of types, where a type in feature.home.reminders uses a type in core.domain.usecase.reminder.
- The types involved
com.hellguy39.hellnotes.feature.home.reminders.RemindersViewModel→com.hellguy39.hellnotes.core.domain.usecase.reminder.GetAllNoteWrappersWithRemindersUseCase
- Direction
- feature.home.reminders uses core.domain.usecase.reminder, so a change to core.domain.usecase.reminder can break feature.home.reminders, while a change to feature.home.reminders can't break core.domain.usecase.reminder.
- Position
- Below the diagonal: feature.home.reminders uses a module listed above it, which is the healthy direction.
29→24 feature.home.reminders uses feature.home✕
- Connections
- 3 pairs of types, where a type in feature.home.reminders uses a type in feature.home.
- The types involved
com.hellguy39.hellnotes.feature.home.reminders.RemindersRouteKt→com.hellguy39.hellnotes.feature.home.HomeStatecom.hellguy39.hellnotes.feature.home.reminders.RemindersRouteKt→com.hellguy39.hellnotes.feature.home.VisualsViewModelcom.hellguy39.hellnotes.feature.home.reminders.RemindersScreenKt→com.hellguy39.hellnotes.feature.home.VisualState
- Direction
- feature.home.reminders uses feature.home, so a change to feature.home can break feature.home.reminders, while a change to feature.home.reminders can't break feature.home.
- Position
- Below the diagonal: feature.home.reminders uses a module listed above it, which is the healthy direction.
30→4 feature.home.trash uses core.model.wrapper✕
- Connections
- 1 pair of types, where a type in feature.home.trash uses a type in core.model.wrapper.
- The types involved
com.hellguy39.hellnotes.feature.home.trash.TrashUiState→com.hellguy39.hellnotes.core.model.wrapper.Selectable
- Direction
- feature.home.trash uses core.model.wrapper, so a change to core.model.wrapper can break feature.home.trash, while a change to feature.home.trash can't break core.model.wrapper.
- Position
- Below the diagonal: feature.home.trash uses a module listed above it, which is the healthy direction.
30→7 feature.home.trash uses core.model✕
- Connections
- 1 pair of types, where a type in feature.home.trash uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.feature.home.trash.TrashUiState→com.hellguy39.hellnotes.core.model.NoteWrapper
- Direction
- feature.home.trash uses core.model, so a change to core.model can break feature.home.trash, while a change to feature.home.trash can't break core.model.
- Position
- Below the diagonal: feature.home.trash uses a module listed above it, which is the healthy direction.
30→14 feature.home.trash uses core.domain.repository.settings✕
- Connections
- 1 pair of types, where a type in feature.home.trash uses a type in core.domain.repository.settings.
- The types involved
com.hellguy39.hellnotes.feature.home.trash.TrashViewModel→com.hellguy39.hellnotes.core.domain.repository.settings.DataStoreRepository
- Direction
- feature.home.trash uses core.domain.repository.settings, so a change to core.domain.repository.settings can break feature.home.trash, while a change to feature.home.trash can't break core.domain.repository.settings.
- Position
- Below the diagonal: feature.home.trash uses a module listed above it, which is the healthy direction.
30→17 feature.home.trash uses core.domain.repository.notes✕
- Connections
- 1 pair of types, where a type in feature.home.trash uses a type in core.domain.repository.notes.
- The types involved
com.hellguy39.hellnotes.feature.home.trash.TrashViewModel→com.hellguy39.hellnotes.core.domain.repository.notes.NoteActionController
- Direction
- feature.home.trash uses core.domain.repository.notes, so a change to core.domain.repository.notes can break feature.home.trash, while a change to feature.home.trash can't break core.domain.repository.notes.
- Position
- Below the diagonal: feature.home.trash uses a module listed above it, which is the healthy direction.
30→23 feature.home.trash uses core.domain.usecase.trash✕
- Connections
- 2 pairs of types, where a type in feature.home.trash uses a type in core.domain.usecase.trash.
- The types involved
com.hellguy39.hellnotes.feature.home.trash.TrashViewModel→com.hellguy39.hellnotes.core.domain.usecase.trash.DeleteAllNoteWrappersAtTrashUseCasecom.hellguy39.hellnotes.feature.home.trash.TrashViewModel→com.hellguy39.hellnotes.core.domain.usecase.trash.GetAllNoteWrappersAtTrashFlowUseCase
- Direction
- feature.home.trash uses core.domain.usecase.trash, so a change to core.domain.usecase.trash can break feature.home.trash, while a change to feature.home.trash can't break core.domain.usecase.trash.
- Position
- Below the diagonal: feature.home.trash uses a module listed above it, which is the healthy direction.
30→24 feature.home.trash uses feature.home✕
- Connections
- 3 pairs of types, where a type in feature.home.trash uses a type in feature.home.
- The types involved
com.hellguy39.hellnotes.feature.home.trash.TrashRouteKt→com.hellguy39.hellnotes.feature.home.HomeStatecom.hellguy39.hellnotes.feature.home.trash.TrashRouteKt→com.hellguy39.hellnotes.feature.home.VisualsViewModelcom.hellguy39.hellnotes.feature.home.trash.TrashScreenKt→com.hellguy39.hellnotes.feature.home.VisualState
- Direction
- feature.home.trash uses feature.home, so a change to feature.home can break feature.home.trash, while a change to feature.home.trash can't break feature.home.
- Position
- Below the diagonal: feature.home.trash uses a module listed above it, which is the healthy direction.
31→7 core.domain.usecase.archive uses core.model✕
- Connections
- 1 pair of types, where a type in core.domain.usecase.archive uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.archive.GetAllArchivedNoteWrappersFlowUseCase→com.hellguy39.hellnotes.core.model.NoteWrapper
- Direction
- core.domain.usecase.archive uses core.model, so a change to core.model can break core.domain.usecase.archive, while a change to core.domain.usecase.archive can't break core.model.
- Position
- Below the diagonal: core.domain.usecase.archive uses a module listed above it, which is the healthy direction.
31→17 core.domain.usecase.archive uses core.domain.repository.notes✕
- Connections
- 1 pair of types, where a type in core.domain.usecase.archive uses a type in core.domain.repository.notes.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.archive.MoveNoteToArchiveUseCase→com.hellguy39.hellnotes.core.domain.repository.notes.NoteRepository
- Direction
- core.domain.usecase.archive uses core.domain.repository.notes, so a change to core.domain.repository.notes can break core.domain.usecase.archive, while a change to core.domain.usecase.archive can't break core.domain.repository.notes.
- Position
- Below the diagonal: core.domain.usecase.archive uses a module listed above it, which is the healthy direction.
31→28 core.domain.usecase.archive uses core.domain.usecase.note✕
- Connections
- 1 pair of types, where a type in core.domain.usecase.archive uses a type in core.domain.usecase.note.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.archive.GetAllArchivedNoteWrappersFlowUseCase→com.hellguy39.hellnotes.core.domain.usecase.note.GetAllNoteWrappersFlowUseCase
- Direction
- core.domain.usecase.archive uses core.domain.usecase.note, so a change to core.domain.usecase.note can break core.domain.usecase.archive, while a change to core.domain.usecase.archive can't break core.domain.usecase.note.
- Position
- Below the diagonal: core.domain.usecase.archive uses a module listed above it, which is the healthy direction.
32→7 core.domain.usecase.label uses core.model✕
- Connections
- 3 pairs of types, where a type in core.domain.usecase.label uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.label.GetAllArchivedNoteWrappersByLabelId→com.hellguy39.hellnotes.core.model.NoteWrappercom.hellguy39.hellnotes.core.domain.usecase.label.GetAllNoteWrappersAtTrashByLabelId→com.hellguy39.hellnotes.core.model.NoteWrappercom.hellguy39.hellnotes.core.domain.usecase.label.GetAllNoteWrappersByLabelId→com.hellguy39.hellnotes.core.model.NoteWrapper
- Direction
- core.domain.usecase.label uses core.model, so a change to core.model can break core.domain.usecase.label, while a change to core.domain.usecase.label can't break core.model.
- Position
- Below the diagonal: core.domain.usecase.label uses a module listed above it, which is the healthy direction.
32→17 core.domain.usecase.label uses core.domain.repository.notes✕
- Connections
- 3 pairs of types, where a type in core.domain.usecase.label uses a type in core.domain.repository.notes.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.label.GetAllArchivedNoteWrappersByLabelId→com.hellguy39.hellnotes.core.domain.repository.notes.LabelRepositorycom.hellguy39.hellnotes.core.domain.usecase.label.GetAllNoteWrappersAtTrashByLabelId→com.hellguy39.hellnotes.core.domain.repository.notes.LabelRepositorycom.hellguy39.hellnotes.core.domain.usecase.label.GetAllNoteWrappersByLabelId→com.hellguy39.hellnotes.core.domain.repository.notes.LabelRepository
- Direction
- core.domain.usecase.label uses core.domain.repository.notes, so a change to core.domain.repository.notes can break core.domain.usecase.label, while a change to core.domain.usecase.label can't break core.domain.repository.notes.
- Position
- Below the diagonal: core.domain.usecase.label uses a module listed above it, which is the healthy direction.
32→23 core.domain.usecase.label uses core.domain.usecase.trash✕
- Connections
- 1 pair of types, where a type in core.domain.usecase.label uses a type in core.domain.usecase.trash.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.label.GetAllNoteWrappersAtTrashByLabelId→com.hellguy39.hellnotes.core.domain.usecase.trash.GetAllNoteWrappersAtTrashFlowUseCase
- Direction
- core.domain.usecase.label uses core.domain.usecase.trash, so a change to core.domain.usecase.trash can break core.domain.usecase.label, while a change to core.domain.usecase.label can't break core.domain.usecase.trash.
- Position
- Below the diagonal: core.domain.usecase.label uses a module listed above it, which is the healthy direction.
32→28 core.domain.usecase.label uses core.domain.usecase.note✕
- Connections
- 2 pairs of types, where a type in core.domain.usecase.label uses a type in core.domain.usecase.note.
- The types involved
com.hellguy39.hellnotes.core.domain.usecase.label.GetAllArchivedNoteWrappersByLabelId→com.hellguy39.hellnotes.core.domain.usecase.note.GetAllNoteWrappersFlowUseCasecom.hellguy39.hellnotes.core.domain.usecase.label.GetAllNoteWrappersByLabelId→com.hellguy39.hellnotes.core.domain.usecase.note.GetAllNoteWrappersFlowUseCase
- Direction
- core.domain.usecase.label uses core.domain.usecase.note, so a change to core.domain.usecase.note can break core.domain.usecase.label, while a change to core.domain.usecase.label can't break core.domain.usecase.note.
- Position
- Below the diagonal: core.domain.usecase.label uses a module listed above it, which is the healthy direction.
33→4 feature.home.notes uses core.model.wrapper✕
- Connections
- 1 pair of types, where a type in feature.home.notes uses a type in core.model.wrapper.
- The types involved
com.hellguy39.hellnotes.feature.home.notes.NoteListUiState→com.hellguy39.hellnotes.core.model.wrapper.Selectable
- Direction
- feature.home.notes uses core.model.wrapper, so a change to core.model.wrapper can break feature.home.notes, while a change to feature.home.notes can't break core.model.wrapper.
- Position
- Below the diagonal: feature.home.notes uses a module listed above it, which is the healthy direction.
33→7 feature.home.notes uses core.model✕
- Connections
- 1 pair of types, where a type in feature.home.notes uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.feature.home.notes.NoteListUiState→com.hellguy39.hellnotes.core.model.NoteWrapper
- Direction
- feature.home.notes uses core.model, so a change to core.model can break feature.home.notes, while a change to feature.home.notes can't break core.model.
- Position
- Below the diagonal: feature.home.notes uses a module listed above it, which is the healthy direction.
33→11 feature.home.notes uses core.model.repository.local.datastore✕
- Connections
- 1 pair of types, where a type in feature.home.notes uses a type in core.model.repository.local.datastore.
- The types involved
com.hellguy39.hellnotes.feature.home.notes.NotesViewModel→com.hellguy39.hellnotes.core.model.repository.local.datastore.NoteSwipe
- Direction
- feature.home.notes uses core.model.repository.local.datastore, so a change to core.model.repository.local.datastore can break feature.home.notes, while a change to feature.home.notes can't break core.model.repository.local.datastore.
- Position
- Below the diagonal: feature.home.notes uses a module listed above it, which is the healthy direction.
33→17 feature.home.notes uses core.domain.repository.notes✕
- Connections
- 1 pair of types, where a type in feature.home.notes uses a type in core.domain.repository.notes.
- The types involved
com.hellguy39.hellnotes.feature.home.notes.NotesViewModel→com.hellguy39.hellnotes.core.domain.repository.notes.NoteActionController
- Direction
- feature.home.notes uses core.domain.repository.notes, so a change to core.domain.repository.notes can break feature.home.notes, while a change to feature.home.notes can't break core.domain.repository.notes.
- Position
- Below the diagonal: feature.home.notes uses a module listed above it, which is the healthy direction.
33→24 feature.home.notes uses feature.home✕
- Connections
- 3 pairs of types, where a type in feature.home.notes uses a type in feature.home.
- The types involved
com.hellguy39.hellnotes.feature.home.notes.NotesRouteKt→com.hellguy39.hellnotes.feature.home.HomeStatecom.hellguy39.hellnotes.feature.home.notes.NotesRouteKt→com.hellguy39.hellnotes.feature.home.VisualsViewModelcom.hellguy39.hellnotes.feature.home.notes.NotesScreenKt→com.hellguy39.hellnotes.feature.home.VisualState
- Direction
- feature.home.notes uses feature.home, so a change to feature.home can break feature.home.notes, while a change to feature.home.notes can't break feature.home.
- Position
- Below the diagonal: feature.home.notes uses a module listed above it, which is the healthy direction.
33→28 feature.home.notes uses core.domain.usecase.note✕
- Connections
- 1 pair of types, where a type in feature.home.notes uses a type in core.domain.usecase.note.
- The types involved
com.hellguy39.hellnotes.feature.home.notes.NotesViewModel→com.hellguy39.hellnotes.core.domain.usecase.note.GetAllNoteWrappersFlowUseCase
- Direction
- feature.home.notes uses core.domain.usecase.note, so a change to core.domain.usecase.note can break feature.home.notes, while a change to feature.home.notes can't break core.domain.usecase.note.
- Position
- Below the diagonal: feature.home.notes uses a module listed above it, which is the healthy direction.
34→5 feature.notedetail uses core.ui.resources.wrapper✕
- Connections
- 1 pair of types, where a type in feature.notedetail uses a type in core.ui.resources.wrapper.
- The types involved
com.hellguy39.hellnotes.feature.notedetail.HomeState→com.hellguy39.hellnotes.core.ui.resources.wrapper.UiText
- Direction
- feature.notedetail uses core.ui.resources.wrapper, so a change to core.ui.resources.wrapper can break feature.notedetail, while a change to feature.notedetail can't break core.ui.resources.wrapper.
- Position
- Below the diagonal: feature.notedetail uses a module listed above it, which is the healthy direction.
34→7 feature.notedetail uses core.model✕
- Connections
- 3 pairs of types, where a type in feature.notedetail uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.feature.notedetail.HomeState→com.hellguy39.hellnotes.core.model.NoteWrappercom.hellguy39.hellnotes.feature.notedetail.NoteDetailUiState→com.hellguy39.hellnotes.core.model.NoteWrappercom.hellguy39.hellnotes.feature.notedetail.NoteDetailViewModel→com.hellguy39.hellnotes.core.model.NoteWrapper
- Direction
- feature.notedetail uses core.model, so a change to core.model can break feature.notedetail, while a change to feature.notedetail can't break core.model.
- Position
- Below the diagonal: feature.notedetail uses a module listed above it, which is the healthy direction.
34→15 feature.notedetail uses core.model.repository.local.database✕
- Connections
- 3 pairs of types, where a type in feature.notedetail uses a type in core.model.repository.local.database.
- The types involved
com.hellguy39.hellnotes.feature.notedetail.NoteDetailViewModel→com.hellguy39.hellnotes.core.model.repository.local.database.Checklistcom.hellguy39.hellnotes.feature.notedetail.NoteDetailViewModel→com.hellguy39.hellnotes.core.model.repository.local.database.ChecklistItemcom.hellguy39.hellnotes.feature.notedetail.NoteDetailViewModel→com.hellguy39.hellnotes.core.model.repository.local.database.Note
- Direction
- feature.notedetail uses core.model.repository.local.database, so a change to core.model.repository.local.database can break feature.notedetail, while a change to feature.notedetail can't break core.model.repository.local.database.
- Position
- Below the diagonal: feature.notedetail uses a module listed above it, which is the healthy direction.
34→17 feature.notedetail uses core.domain.repository.notes✕
- Connections
- 4 pairs of types, where a type in feature.notedetail uses a type in core.domain.repository.notes.
- The types involved
com.hellguy39.hellnotes.feature.notedetail.NoteDetailViewModel→com.hellguy39.hellnotes.core.domain.repository.notes.ChecklistRepositorycom.hellguy39.hellnotes.feature.notedetail.NoteDetailViewModel→com.hellguy39.hellnotes.core.domain.repository.notes.LabelRepositorycom.hellguy39.hellnotes.feature.notedetail.NoteDetailViewModel→com.hellguy39.hellnotes.core.domain.repository.notes.NoteRepositorycom.hellguy39.hellnotes.feature.notedetail.NoteDetailViewModel→com.hellguy39.hellnotes.core.domain.repository.notes.ReminderRepository
- Direction
- feature.notedetail uses core.domain.repository.notes, so a change to core.domain.repository.notes can break feature.notedetail, while a change to feature.notedetail can't break core.domain.repository.notes.
- Position
- Below the diagonal: feature.notedetail uses a module listed above it, which is the healthy direction.
34→23 feature.notedetail uses core.domain.usecase.trash✕
- Connections
- 1 pair of types, where a type in feature.notedetail uses a type in core.domain.usecase.trash.
- The types involved
com.hellguy39.hellnotes.feature.notedetail.NoteDetailViewModel→com.hellguy39.hellnotes.core.domain.usecase.trash.DeleteNoteUseCase
- Direction
- feature.notedetail uses core.domain.usecase.trash, so a change to core.domain.usecase.trash can break feature.notedetail, while a change to feature.notedetail can't break core.domain.usecase.trash.
- Position
- Below the diagonal: feature.notedetail uses a module listed above it, which is the healthy direction.
34→28 feature.notedetail uses core.domain.usecase.note✕
- Connections
- 4 pairs of types, where a type in feature.notedetail uses a type in core.domain.usecase.note.
- The types involved
com.hellguy39.hellnotes.feature.notedetail.NoteDetailViewModel→com.hellguy39.hellnotes.core.domain.usecase.note.CopyNoteUseCasecom.hellguy39.hellnotes.feature.notedetail.NoteDetailViewModel→com.hellguy39.hellnotes.core.domain.usecase.note.MoveNoteToTrashUseCasecom.hellguy39.hellnotes.feature.notedetail.NoteDetailViewModel→com.hellguy39.hellnotes.core.domain.usecase.note.PostProcessNoteUseCasecom.hellguy39.hellnotes.feature.notedetail.NoteDetailViewModel→com.hellguy39.hellnotes.core.domain.usecase.note.RestoreNoteFromTrashUseCase
- Direction
- feature.notedetail uses core.domain.usecase.note, so a change to core.domain.usecase.note can break feature.notedetail, while a change to feature.notedetail can't break core.domain.usecase.note.
- Position
- Below the diagonal: feature.notedetail uses a module listed above it, which is the healthy direction.
35→4 feature.search uses core.model.wrapper✕
- Connections
- 1 pair of types, where a type in feature.search uses a type in core.model.wrapper.
- The types involved
com.hellguy39.hellnotes.feature.search.SearchUiState→com.hellguy39.hellnotes.core.model.wrapper.Selectable
- Direction
- feature.search uses core.model.wrapper, so a change to core.model.wrapper can break feature.search, while a change to feature.search can't break core.model.wrapper.
- Position
- Below the diagonal: feature.search uses a module listed above it, which is the healthy direction.
35→7 feature.search uses core.model✕
- Connections
- 1 pair of types, where a type in feature.search uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.feature.search.SearchUiState→com.hellguy39.hellnotes.core.model.NoteWrapper
- Direction
- feature.search uses core.model, so a change to core.model can break feature.search, while a change to feature.search can't break core.model.
- Position
- Below the diagonal: feature.search uses a module listed above it, which is the healthy direction.
35→11 feature.search uses core.model.repository.local.datastore✕
- Connections
- 2 pairs of types, where a type in feature.search uses a type in core.model.repository.local.datastore.
- The types involved
com.hellguy39.hellnotes.feature.search.SearchUiState→com.hellguy39.hellnotes.core.model.repository.local.datastore.ListStylecom.hellguy39.hellnotes.feature.search.SearchUiState→com.hellguy39.hellnotes.core.model.repository.local.datastore.NoteStyle
- Direction
- feature.search uses core.model.repository.local.datastore, so a change to core.model.repository.local.datastore can break feature.search, while a change to feature.search can't break core.model.repository.local.datastore.
- Position
- Below the diagonal: feature.search uses a module listed above it, which is the healthy direction.
35→14 feature.search uses core.domain.repository.settings✕
- Connections
- 1 pair of types, where a type in feature.search uses a type in core.domain.repository.settings.
- The types involved
com.hellguy39.hellnotes.feature.search.SearchViewModel→com.hellguy39.hellnotes.core.domain.repository.settings.DataStoreRepository
- Direction
- feature.search uses core.domain.repository.settings, so a change to core.domain.repository.settings can break feature.search, while a change to feature.search can't break core.domain.repository.settings.
- Position
- Below the diagonal: feature.search uses a module listed above it, which is the healthy direction.
35→28 feature.search uses core.domain.usecase.note✕
- Connections
- 1 pair of types, where a type in feature.search uses a type in core.domain.usecase.note.
- The types involved
com.hellguy39.hellnotes.feature.search.SearchViewModel→com.hellguy39.hellnotes.core.domain.usecase.note.GetAllNoteWrappersFlowUseCase
- Direction
- feature.search uses core.domain.usecase.note, so a change to core.domain.usecase.note can break feature.search, while a change to feature.search can't break core.domain.usecase.note.
- Position
- Below the diagonal: feature.search uses a module listed above it, which is the healthy direction.
36→3 feature.update uses core.model.repository.remote✕
- Connections
- 1 pair of types, where a type in feature.update uses a type in core.model.repository.remote.
- The types involved
com.hellguy39.hellnotes.feature.update.UpdateViewModel→com.hellguy39.hellnotes.core.model.repository.remote.Release
- Direction
- feature.update uses core.model.repository.remote, so a change to core.model.repository.remote can break feature.update, while a change to feature.update can't break core.model.repository.remote.
- Position
- Below the diagonal: feature.update uses a module listed above it, which is the healthy direction.
36→5 feature.update uses core.ui.resources.wrapper✕
- Connections
- 1 pair of types, where a type in feature.update uses a type in core.ui.resources.wrapper.
- The types involved
com.hellguy39.hellnotes.feature.update.UpdateUiState→com.hellguy39.hellnotes.core.ui.resources.wrapper.UiText
- Direction
- feature.update uses core.ui.resources.wrapper, so a change to core.ui.resources.wrapper can break feature.update, while a change to feature.update can't break core.ui.resources.wrapper.
- Position
- Below the diagonal: feature.update uses a module listed above it, which is the healthy direction.
36→10 feature.update uses core.domain.repository.remote✕
- Connections
- 1 pair of types, where a type in feature.update uses a type in core.domain.repository.remote.
- The types involved
com.hellguy39.hellnotes.feature.update.UpdateViewModel→com.hellguy39.hellnotes.core.domain.repository.remote.GithubRepositoryService
- Direction
- feature.update uses core.domain.repository.remote, so a change to core.domain.repository.remote can break feature.update, while a change to feature.update can't break core.domain.repository.remote.
- Position
- Below the diagonal: feature.update uses a module listed above it, which is the healthy direction.
36→18 feature.update uses core.domain.repository.system✕
- Connections
- 1 pair of types, where a type in feature.update uses a type in core.domain.repository.system.
- The types involved
com.hellguy39.hellnotes.feature.update.UpdateViewModel→com.hellguy39.hellnotes.core.domain.repository.system.Downloader
- Direction
- feature.update uses core.domain.repository.system, so a change to core.domain.repository.system can break feature.update, while a change to feature.update can't break core.domain.repository.system.
- Position
- Below the diagonal: feature.update uses a module listed above it, which is the healthy direction.
36→27 feature.update uses core.domain.usecase✕
- Connections
- 1 pair of types, where a type in feature.update uses a type in core.domain.usecase.
- The types involved
com.hellguy39.hellnotes.feature.update.UpdateViewModel→com.hellguy39.hellnotes.core.domain.usecase.CheckForUpdatesUseCase
- Direction
- feature.update uses core.domain.usecase, so a change to core.domain.usecase can break feature.update, while a change to feature.update can't break core.domain.usecase.
- Position
- Below the diagonal: feature.update uses a module listed above it, which is the healthy direction.
37→11 core.data.repository.local uses core.model.repository.local.datastore✕
- Connections
- 5 pairs of types, where a type in core.data.repository.local uses a type in core.model.repository.local.datastore.
- The types involved
com.hellguy39.hellnotes.core.data.repository.local.DataStoreRepositoryImpl→com.hellguy39.hellnotes.core.model.repository.local.datastore.ListStylecom.hellguy39.hellnotes.core.data.repository.local.DataStoreRepositoryImpl→com.hellguy39.hellnotes.core.model.repository.local.datastore.NoteStylecom.hellguy39.hellnotes.core.data.repository.local.DataStoreRepositoryImpl→com.hellguy39.hellnotes.core.model.repository.local.datastore.NoteSwipesStatecom.hellguy39.hellnotes.core.data.repository.local.DataStoreRepositoryImpl→com.hellguy39.hellnotes.core.model.repository.local.datastore.SecurityStatecom.hellguy39.hellnotes.core.data.repository.local.NoteActionControllerImpl→com.hellguy39.hellnotes.core.model.repository.local.datastore.NoteSwipe
- Direction
- core.data.repository.local uses core.model.repository.local.datastore, so a change to core.model.repository.local.datastore can break core.data.repository.local, while a change to core.data.repository.local can't break core.model.repository.local.datastore.
- Position
- Below the diagonal: core.data.repository.local uses a module listed above it, which is the healthy direction.
37→14 core.data.repository.local uses core.domain.repository.settings✕
- Connections
- 1 pair of types, where a type in core.data.repository.local uses a type in core.domain.repository.settings.
- The types involved
com.hellguy39.hellnotes.core.data.repository.local.DataStoreRepositoryImpl→com.hellguy39.hellnotes.core.domain.repository.settings.DataStoreRepository
- Direction
- core.data.repository.local uses core.domain.repository.settings, so a change to core.domain.repository.settings can break core.data.repository.local, while a change to core.data.repository.local can't break core.domain.repository.settings.
- Position
- Below the diagonal: core.data.repository.local uses a module listed above it, which is the healthy direction.
37→15 core.data.repository.local uses core.model.repository.local.database✕
- Connections
- 4 pairs of types, where a type in core.data.repository.local uses a type in core.model.repository.local.database.
- The types involved
com.hellguy39.hellnotes.core.data.repository.local.ChecklistRepositoryImpl→com.hellguy39.hellnotes.core.model.repository.local.database.Checklistcom.hellguy39.hellnotes.core.data.repository.local.LabelRepositoryImpl→com.hellguy39.hellnotes.core.model.repository.local.database.Labelcom.hellguy39.hellnotes.core.data.repository.local.NoteRepositoryImpl→com.hellguy39.hellnotes.core.model.repository.local.database.Notecom.hellguy39.hellnotes.core.data.repository.local.ReminderRepositoryImpl→com.hellguy39.hellnotes.core.model.repository.local.database.Reminder
- Direction
- core.data.repository.local uses core.model.repository.local.database, so a change to core.model.repository.local.database can break core.data.repository.local, while a change to core.data.repository.local can't break core.model.repository.local.database.
- Position
- Below the diagonal: core.data.repository.local uses a module listed above it, which is the healthy direction.
37→16 core.data.repository.local uses core.database.dao✕
- Connections
- 4 pairs of types, where a type in core.data.repository.local uses a type in core.database.dao.
- The types involved
com.hellguy39.hellnotes.core.data.repository.local.ChecklistRepositoryImpl→com.hellguy39.hellnotes.core.database.dao.ChecklistDaocom.hellguy39.hellnotes.core.data.repository.local.LabelRepositoryImpl→com.hellguy39.hellnotes.core.database.dao.LabelDaocom.hellguy39.hellnotes.core.data.repository.local.NoteRepositoryImpl→com.hellguy39.hellnotes.core.database.dao.NoteDaocom.hellguy39.hellnotes.core.data.repository.local.ReminderRepositoryImpl→com.hellguy39.hellnotes.core.database.dao.ReminderDao
- Direction
- core.data.repository.local uses core.database.dao, so a change to core.database.dao can break core.data.repository.local, while a change to core.data.repository.local can't break core.database.dao.
- Position
- Below the diagonal: core.data.repository.local uses a module listed above it, which is the healthy direction.
37→17 core.data.repository.local uses core.domain.repository.notes✕
- Connections
- 5 pairs of types, where a type in core.data.repository.local uses a type in core.domain.repository.notes.
- The types involved
com.hellguy39.hellnotes.core.data.repository.local.ChecklistRepositoryImpl→com.hellguy39.hellnotes.core.domain.repository.notes.ChecklistRepositorycom.hellguy39.hellnotes.core.data.repository.local.LabelRepositoryImpl→com.hellguy39.hellnotes.core.domain.repository.notes.LabelRepositorycom.hellguy39.hellnotes.core.data.repository.local.NoteActionControllerImpl→com.hellguy39.hellnotes.core.domain.repository.notes.NoteActionControllercom.hellguy39.hellnotes.core.data.repository.local.NoteRepositoryImpl→com.hellguy39.hellnotes.core.domain.repository.notes.NoteRepositorycom.hellguy39.hellnotes.core.data.repository.local.ReminderRepositoryImpl→com.hellguy39.hellnotes.core.domain.repository.notes.ReminderRepository
- Direction
- core.data.repository.local uses core.domain.repository.notes, so a change to core.domain.repository.notes can break core.data.repository.local, while a change to core.data.repository.local can't break core.domain.repository.notes.
- Position
- Below the diagonal: core.data.repository.local uses a module listed above it, which is the healthy direction.
37→23 core.data.repository.local uses core.domain.usecase.trash✕
- Connections
- 1 pair of types, where a type in core.data.repository.local uses a type in core.domain.usecase.trash.
- The types involved
com.hellguy39.hellnotes.core.data.repository.local.NoteActionControllerImpl→com.hellguy39.hellnotes.core.domain.usecase.trash.DeleteNoteUseCase
- Direction
- core.data.repository.local uses core.domain.usecase.trash, so a change to core.domain.usecase.trash can break core.data.repository.local, while a change to core.data.repository.local can't break core.domain.usecase.trash.
- Position
- Below the diagonal: core.data.repository.local uses a module listed above it, which is the healthy direction.
37→28 core.data.repository.local uses core.domain.usecase.note✕
- Connections
- 2 pairs of types, where a type in core.data.repository.local uses a type in core.domain.usecase.note.
- The types involved
com.hellguy39.hellnotes.core.data.repository.local.NoteActionControllerImpl→com.hellguy39.hellnotes.core.domain.usecase.note.MoveNoteToTrashUseCasecom.hellguy39.hellnotes.core.data.repository.local.NoteActionControllerImpl→com.hellguy39.hellnotes.core.domain.usecase.note.RestoreNoteFromTrashUseCase
- Direction
- core.data.repository.local uses core.domain.usecase.note, so a change to core.domain.usecase.note can break core.data.repository.local, while a change to core.data.repository.local can't break core.domain.usecase.note.
- Position
- Below the diagonal: core.data.repository.local uses a module listed above it, which is the healthy direction.
37→31 core.data.repository.local uses core.domain.usecase.archive✕
- Connections
- 1 pair of types, where a type in core.data.repository.local uses a type in core.domain.usecase.archive.
- The types involved
com.hellguy39.hellnotes.core.data.repository.local.NoteActionControllerImpl→com.hellguy39.hellnotes.core.domain.usecase.archive.MoveNoteToArchiveUseCase
- Direction
- core.data.repository.local uses core.domain.usecase.archive, so a change to core.domain.usecase.archive can break core.data.repository.local, while a change to core.data.repository.local can't break core.domain.usecase.archive.
- Position
- Below the diagonal: core.data.repository.local uses a module listed above it, which is the healthy direction.
38→4 feature.home.archive uses core.model.wrapper✕
- Connections
- 1 pair of types, where a type in feature.home.archive uses a type in core.model.wrapper.
- The types involved
com.hellguy39.hellnotes.feature.home.archive.ArchiveUiState→com.hellguy39.hellnotes.core.model.wrapper.Selectable
- Direction
- feature.home.archive uses core.model.wrapper, so a change to core.model.wrapper can break feature.home.archive, while a change to feature.home.archive can't break core.model.wrapper.
- Position
- Below the diagonal: feature.home.archive uses a module listed above it, which is the healthy direction.
38→7 feature.home.archive uses core.model✕
- Connections
- 1 pair of types, where a type in feature.home.archive uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.feature.home.archive.ArchiveUiState→com.hellguy39.hellnotes.core.model.NoteWrapper
- Direction
- feature.home.archive uses core.model, so a change to core.model can break feature.home.archive, while a change to feature.home.archive can't break core.model.
- Position
- Below the diagonal: feature.home.archive uses a module listed above it, which is the healthy direction.
38→11 feature.home.archive uses core.model.repository.local.datastore✕
- Connections
- 1 pair of types, where a type in feature.home.archive uses a type in core.model.repository.local.datastore.
- The types involved
com.hellguy39.hellnotes.feature.home.archive.ArchiveScreenKt→com.hellguy39.hellnotes.core.model.repository.local.datastore.ListStyle
- Direction
- feature.home.archive uses core.model.repository.local.datastore, so a change to core.model.repository.local.datastore can break feature.home.archive, while a change to feature.home.archive can't break core.model.repository.local.datastore.
- Position
- Below the diagonal: feature.home.archive uses a module listed above it, which is the healthy direction.
38→17 feature.home.archive uses core.domain.repository.notes✕
- Connections
- 1 pair of types, where a type in feature.home.archive uses a type in core.domain.repository.notes.
- The types involved
com.hellguy39.hellnotes.feature.home.archive.ArchiveViewModel→com.hellguy39.hellnotes.core.domain.repository.notes.NoteActionController
- Direction
- feature.home.archive uses core.domain.repository.notes, so a change to core.domain.repository.notes can break feature.home.archive, while a change to feature.home.archive can't break core.domain.repository.notes.
- Position
- Below the diagonal: feature.home.archive uses a module listed above it, which is the healthy direction.
38→24 feature.home.archive uses feature.home✕
- Connections
- 3 pairs of types, where a type in feature.home.archive uses a type in feature.home.
- The types involved
com.hellguy39.hellnotes.feature.home.archive.ArchiveRouteKt→com.hellguy39.hellnotes.feature.home.HomeStatecom.hellguy39.hellnotes.feature.home.archive.ArchiveRouteKt→com.hellguy39.hellnotes.feature.home.VisualsViewModelcom.hellguy39.hellnotes.feature.home.archive.ArchiveScreenKt→com.hellguy39.hellnotes.feature.home.VisualState
- Direction
- feature.home.archive uses feature.home, so a change to feature.home can break feature.home.archive, while a change to feature.home.archive can't break feature.home.
- Position
- Below the diagonal: feature.home.archive uses a module listed above it, which is the healthy direction.
38→31 feature.home.archive uses core.domain.usecase.archive✕
- Connections
- 1 pair of types, where a type in feature.home.archive uses a type in core.domain.usecase.archive.
- The types involved
com.hellguy39.hellnotes.feature.home.archive.ArchiveViewModel→com.hellguy39.hellnotes.core.domain.usecase.archive.GetAllArchivedNoteWrappersFlowUseCase
- Direction
- feature.home.archive uses core.domain.usecase.archive, so a change to core.domain.usecase.archive can break feature.home.archive, while a change to feature.home.archive can't break core.domain.usecase.archive.
- Position
- Below the diagonal: feature.home.archive uses a module listed above it, which is the healthy direction.
39→4 feature.home.label uses core.model.wrapper✕
- Connections
- 1 pair of types, where a type in feature.home.label uses a type in core.model.wrapper.
- The types involved
com.hellguy39.hellnotes.feature.home.label.LabelUiState→com.hellguy39.hellnotes.core.model.wrapper.Selectable
- Direction
- feature.home.label uses core.model.wrapper, so a change to core.model.wrapper can break feature.home.label, while a change to feature.home.label can't break core.model.wrapper.
- Position
- Below the diagonal: feature.home.label uses a module listed above it, which is the healthy direction.
39→7 feature.home.label uses core.model✕
- Connections
- 1 pair of types, where a type in feature.home.label uses a type in core.model.
- The types involved
com.hellguy39.hellnotes.feature.home.label.LabelUiState→com.hellguy39.hellnotes.core.model.NoteWrapper
- Direction
- feature.home.label uses core.model, so a change to core.model can break feature.home.label, while a change to feature.home.label can't break core.model.
- Position
- Below the diagonal: feature.home.label uses a module listed above it, which is the healthy direction.
39→11 feature.home.label uses core.model.repository.local.datastore✕
- Connections
- 2 pairs of types, where a type in feature.home.label uses a type in core.model.repository.local.datastore.
- The types involved
com.hellguy39.hellnotes.feature.home.label.LabelSсreenKt→com.hellguy39.hellnotes.core.model.repository.local.datastore.ListStylecom.hellguy39.hellnotes.feature.home.label.LabelViewModel→com.hellguy39.hellnotes.core.model.repository.local.datastore.NoteSwipe
- Direction
- feature.home.label uses core.model.repository.local.datastore, so a change to core.model.repository.local.datastore can break feature.home.label, while a change to feature.home.label can't break core.model.repository.local.datastore.
- Position
- Below the diagonal: feature.home.label uses a module listed above it, which is the healthy direction.
39→15 feature.home.label uses core.model.repository.local.database✕
- Connections
- 1 pair of types, where a type in feature.home.label uses a type in core.model.repository.local.database.
- The types involved
com.hellguy39.hellnotes.feature.home.label.LabelUiState→com.hellguy39.hellnotes.core.model.repository.local.database.Label
- Direction
- feature.home.label uses core.model.repository.local.database, so a change to core.model.repository.local.database can break feature.home.label, while a change to feature.home.label can't break core.model.repository.local.database.
- Position
- Below the diagonal: feature.home.label uses a module listed above it, which is the healthy direction.
39→17 feature.home.label uses core.domain.repository.notes✕
- Connections
- 2 pairs of types, where a type in feature.home.label uses a type in core.domain.repository.notes.
- The types involved
com.hellguy39.hellnotes.feature.home.label.LabelViewModel→com.hellguy39.hellnotes.core.domain.repository.notes.LabelRepositorycom.hellguy39.hellnotes.feature.home.label.LabelViewModel→com.hellguy39.hellnotes.core.domain.repository.notes.NoteActionController
- Direction
- feature.home.label uses core.domain.repository.notes, so a change to core.domain.repository.notes can break feature.home.label, while a change to feature.home.label can't break core.domain.repository.notes.
- Position
- Below the diagonal: feature.home.label uses a module listed above it, which is the healthy direction.
39→24 feature.home.label uses feature.home✕
- Connections
- 3 pairs of types, where a type in feature.home.label uses a type in feature.home.
- The types involved
com.hellguy39.hellnotes.feature.home.label.LabelRouteKt→com.hellguy39.hellnotes.feature.home.HomeStatecom.hellguy39.hellnotes.feature.home.label.LabelRouteKt→com.hellguy39.hellnotes.feature.home.VisualsViewModelcom.hellguy39.hellnotes.feature.home.label.LabelSсreenKt→com.hellguy39.hellnotes.feature.home.VisualState
- Direction
- feature.home.label uses feature.home, so a change to feature.home can break feature.home.label, while a change to feature.home.label can't break feature.home.
- Position
- Below the diagonal: feature.home.label uses a module listed above it, which is the healthy direction.
39→32 feature.home.label uses core.domain.usecase.label✕
- Connections
- 1 pair of types, where a type in feature.home.label uses a type in core.domain.usecase.label.
- The types involved
com.hellguy39.hellnotes.feature.home.label.LabelViewModel→com.hellguy39.hellnotes.core.domain.usecase.label.GetAllNoteWrappersByLabelId
- Direction
- feature.home.label uses core.domain.usecase.label, so a change to core.domain.usecase.label can break feature.home.label, while a change to feature.home.label can't break core.domain.usecase.label.
- Position
- Below the diagonal: feature.home.label uses a module listed above it, which is the healthy direction.
40→10 core.data.di uses core.domain.repository.remote✕
- Connections
- 1 pair of types, where a type in core.data.di uses a type in core.domain.repository.remote.
- The types involved
com.hellguy39.hellnotes.core.data.di.DataModule→com.hellguy39.hellnotes.core.domain.repository.remote.GithubRepositoryService
- Direction
- core.data.di uses core.domain.repository.remote, so a change to core.domain.repository.remote can break core.data.di, while a change to core.data.di can't break core.domain.repository.remote.
- Position
- Below the diagonal: core.data.di uses a module listed above it, which is the healthy direction.
40→13 core.data.di uses core.data.repository.remote✕
- Connections
- 1 pair of types, where a type in core.data.di uses a type in core.data.repository.remote.
- The types involved
com.hellguy39.hellnotes.core.data.di.DataModule→com.hellguy39.hellnotes.core.data.repository.remote.GithubRepositoryServiceImpl
- Direction
- core.data.di uses core.data.repository.remote, so a change to core.data.repository.remote can break core.data.di, while a change to core.data.di can't break core.data.repository.remote.
- Position
- Below the diagonal: core.data.di uses a module listed above it, which is the healthy direction.
40→14 core.data.di uses core.domain.repository.settings✕
- Connections
- 1 pair of types, where a type in core.data.di uses a type in core.domain.repository.settings.
- The types involved
com.hellguy39.hellnotes.core.data.di.DataModule→com.hellguy39.hellnotes.core.domain.repository.settings.DataStoreRepository
- Direction
- core.data.di uses core.domain.repository.settings, so a change to core.domain.repository.settings can break core.data.di, while a change to core.data.di can't break core.domain.repository.settings.
- Position
- Below the diagonal: core.data.di uses a module listed above it, which is the healthy direction.
40→17 core.data.di uses core.domain.repository.notes✕
- Connections
- 5 pairs of types, where a type in core.data.di uses a type in core.domain.repository.notes.
- The types involved
com.hellguy39.hellnotes.core.data.di.DataModule→com.hellguy39.hellnotes.core.domain.repository.notes.ChecklistRepositorycom.hellguy39.hellnotes.core.data.di.DataModule→com.hellguy39.hellnotes.core.domain.repository.notes.LabelRepositorycom.hellguy39.hellnotes.core.data.di.DataModule→com.hellguy39.hellnotes.core.domain.repository.notes.NoteActionControllercom.hellguy39.hellnotes.core.data.di.DataModule→com.hellguy39.hellnotes.core.domain.repository.notes.NoteRepositorycom.hellguy39.hellnotes.core.data.di.DataModule→com.hellguy39.hellnotes.core.domain.repository.notes.ReminderRepository
- Direction
- core.data.di uses core.domain.repository.notes, so a change to core.domain.repository.notes can break core.data.di, while a change to core.data.di can't break core.domain.repository.notes.
- Position
- Below the diagonal: core.data.di uses a module listed above it, which is the healthy direction.
40→37 core.data.di uses core.data.repository.local✕
- Connections
- 6 pairs of types, where a type in core.data.di uses a type in core.data.repository.local.
- The types involved
com.hellguy39.hellnotes.core.data.di.DataModule→com.hellguy39.hellnotes.core.data.repository.local.ChecklistRepositoryImplcom.hellguy39.hellnotes.core.data.di.DataModule→com.hellguy39.hellnotes.core.data.repository.local.DataStoreRepositoryImplcom.hellguy39.hellnotes.core.data.di.DataModule→com.hellguy39.hellnotes.core.data.repository.local.LabelRepositoryImplcom.hellguy39.hellnotes.core.data.di.DataModule→com.hellguy39.hellnotes.core.data.repository.local.NoteActionControllerImplcom.hellguy39.hellnotes.core.data.di.DataModule→com.hellguy39.hellnotes.core.data.repository.local.NoteRepositoryImplcom.hellguy39.hellnotes.core.data.di.DataModule→com.hellguy39.hellnotes.core.data.repository.local.ReminderRepositoryImpl
- Direction
- core.data.di uses core.data.repository.local, so a change to core.data.repository.local can break core.data.di, while a change to core.data.di can't break core.data.repository.local.
- Position
- Below the diagonal: core.data.di 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 — Domain Modelling
At a glance — Performance
Roadmap
Top priorities: Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts; Resolve the 154 Orphaned file finding(s) in Knowledge Freshness — start with build.gradle.kts (2), NoteDetailRoute.kt, NoteDetailContent.kt.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +9.3 pts | Low | Documentation Quality |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. | +9.3 pts | Low | ADR Quality |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +8.5 pts | Medium | CI/CD gates |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.6 pts | Medium | Architecture documentation |
| Resolve the 154 Orphaned file finding(s) in Knowledge Freshness — start with build.gradle.kts (2), NoteDetailRoute.kt, NoteDetailContent.kt. | +9.3 pts | High | Knowledge Freshness |
| Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery). | +4.0 pts | Medium | DR & Backup |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.2 pts | Medium | Release Hygiene |
| Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure. | +2.3 pts | Medium | Constructible invalid state |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| feature/reminder-edit/src/main/java/com/hellguy39/hellnotes/feature/reminderedit/ReminderEditViewModel.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| feature/lock-setup/src/main/java/com/hellguy39/hellnotes/feature/locksetup/LockSetupPasswordScreen.kt | 7.0 | Mixed | Cognitive Complexity: LockSetupPasswordScreenKt.LockSetupPasswordScreen (cognitive 16) |
| core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/items/HNCheckboxItem.kt | 7.1 | Mixed | Code Duplication: Edited copy of a member (50 corresponding lines) |
| feature/privacy-policy/src/main/java/com/hellguy39/hellnotes/feature/privacypolicy/PrivacyPolicyScreen.kt | 7.2 | Mixed | Code Duplication: Near-duplicate member pair (72 shared lines) |
| feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/archive/ArchiveViewModel.kt | 7.2 | Mixed | Code Duplication: Edited copies of one member (5 members, 16+ corresponding lines) |
| feature/note-detail/src/main/java/com/hellguy39/hellnotes/feature/notedetail/NoteDetailViewModel.kt | 7.3 | Mixed | Explicit Debt: TodoComment |
| feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/archive/components/ArchiveTopAppBar.kt | 7.4 | Mixed | Code Duplication: Edited copies of one member (3 members, 77+ corresponding lines) |
| core/store-api/src/main/java/com/hellguy39/hellnotes/core/storeapi/update/provider/PlayStoreUpdateProvider.kt | 7.4 | Mixed | Code Duplication: Edited copy of a member (20 corresponding lines) |
| core/store-api/src/main/java/com/hellguy39/hellnotes/core/storeapi/review/provider/PlayStoreReviewProvider.kt | 7.4 | Mixed | Code Duplication: Edited copy of a member (12 corresponding lines) |
| core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/CustomDialog.kt | 7.8 | Mixed | Cognitive Complexity: CustomDialogKt.CustomDialog (cognitive 19) |
| core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/NoteChipGroup.kt | 7.8 | Mixed | Cognitive Complexity: NoteChipGroupKt.NoteChipGroup (cognitive 16) |
| feature/lock-setup/src/main/java/com/hellguy39/hellnotes/feature/locksetup/LockSetupPinScreen.kt | 7.8 | Mixed | Cognitive Complexity: LockSetupPinScreenKt.LockSetupPinScreen (cognitive 16) |
| feature/note-detail/src/main/java/com/hellguy39/hellnotes/feature/notedetail/NoteDetailRoute.kt | 7.8 | Mixed | God Classes: MethodTooLong: NoteDetailRouteKt.NoteDetailRoute |
| feature/reminder-edit/src/main/java/com/hellguy39/hellnotes/feature/reminderedit/ReminderEditScreen.kt | 7.8 | Mixed | God Classes: MethodTooLong: ReminderEditScreenKt.ReminderEditScreen |
| feature/changelog/src/main/java/com/hellguy39/hellnotes/feature/changelog/navigation/ChangelogNavigation.kt | 7.8 | Mixed | Code Duplication: Members sharing a duplicated core (5 members, 50+ identical tokens) |
| feature/language-selection/src/main/java/com/hellguy39/hellnotes/feature/languageselection/navigation/LanguageSelectionNavigation.kt | 7.8 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/archive/ArchiveScreen.kt | 7.8 | Mixed | Code Duplication: Edited copies of one member (3 members, 48+ corresponding lines) |
| core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/list/NoteColumnList.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (36 corresponding lines) |
| feature/label-selection/src/main/java/com/hellguy39/hellnotes/feature/labelselection/navigation/LabelSelectionNavigation.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (27 corresponding lines) |
| feature/backup/src/main/java/com/hellguy39/hellnotes/feature/backup/BackupViewModel.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (27 corresponding lines) |
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 43 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 — 43 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, 258 of 269 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 35 Maven/Gradle manifest(s) were read, stating a version for 62 dependency(ies) and leaving 9 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- 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. All 154 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 154 of the 413 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
- 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.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (feature/update/build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (feature/update/src/main/AndroidManifest.xml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- DM8 Value-object opportunities — 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 finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- 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.
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being NoteDetailViewModel.send at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: feature/note-detail/src/main/java/com/hellguy39/hellnotes/feature/notedetail/NoteDetailViewModel.kt (NoteDetailViewModel.send at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was CustomDialogKt.CustomDialog at 19.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with CustomDialogKt.CustomDialog (cognitive 19), NoteChipGroupKt.NoteChipGroup (cognitive 16), LockSetupPasswordScreenKt.LockSetupPasswordScreen (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 4 together lifts Cognitive Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
8 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 8 MethodTooLong finding(s) in God Classes — start with NoteDetailRoute.kt, ReminderEditScreen.kt, NoteDetailContent.kt. — One of this dimension's main actionable groups (8 warning-level).
D4 · Code Duplication
39 duplicated block group(s) detected. 10.5 % of the production lines (2,834 of 27,071) are in a reported copy. A further 35 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with LabelSelectionNavigation.kt, LockScreenPassword.kt, PrivacyPolicyScreen.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with HNCheckboxItem.kt, ChangelogScreen.kt, LabelSсreen.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with ReminderEditScreen.kt, PlayStoreReviewProvider.kt, CustomDialog.kt. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
33 production modules (Gradle), 0 dependency cycle(s), 1 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; 3 module(s) off the main sequence, with abstractness counted on 32 of the 33 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Unstable project HellNotes finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 48 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 22 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 35 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 9 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 40 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
9 deducted task-comment markers across 27071 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 9 TodoComment finding(s) in Explicit Debt — start with NoteDetailViewModel.kt (2), SearchRoute.kt, ReminderEditViewModel.kt. — One of this dimension's main actionable groups (9 warning-level).
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 1 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 33 build units (Gradle) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. semgrep hit a parse error in 1 file(s) — `gradlew` (line 177) — 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.
D34 · Knowledge Freshness
154 of 154 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is feature/note-detail/src/main/java/com/hellguy39/hellnotes/feature/notedetail/NoteDetailRoute.kt. Counted over 154 of the 413 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 154 Orphaned file finding(s) in Knowledge Freshness — start with build.gradle.kts (2), NoteDetailRoute.kt, NoteDetailContent.kt. — One of this dimension's main actionable groups (154 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 62 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
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
- `HellNotes:feature:about-app` is a Application project but references `HellNotes:core:ui`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
What to do
- Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
AX6 · Interface segregation
DM11 · Constructible invalid state
- `ChecklistEntity`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ChecklistEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core/database/src/main/java/com/hellguy39/hellnotes/core/database/entity/ChecklistEntity.kt:26
- `LabelEntity`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `LabelEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core/database/src/main/java/com/hellguy39/hellnotes/core/database/entity/LabelEntity.kt:25
- `NoteEntity`'s public constructor takes `title`, `note` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `NoteEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core/database/src/main/java/com/hellguy39/hellnotes/core/database/entity/NoteEntity.kt:25
- `ReminderEntity`'s public constructor takes `message`, `repeat` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ReminderEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — core/database/src/main/java/com/hellguy39/hellnotes/core/database/entity/ReminderEntity.kt:27
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
- `app/build.gradle.kts` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — app/build.gradle.kts:78
What to do
- Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X2 · Cancellation propagation
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X3 · Exception handling
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 95.2 | Exemplary | Solid. |
| Architecture | 87.5 | Strong | Solid. |
| Maturity | 47.6 | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 24.7 | Critical — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100.0 | Exemplary | Strongest area. |
| Domain Modelling | 75.8 | Strong | Solid. |
| Performance | 94.3 | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
Not included — 82 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Dagger rejects, at compile time, a component that holds a binding with a narrower scope than its own.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~1841 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D12 Dependency Hygiene — Not scored — 35 Maven/Gradle manifest(s) were read, stating a version for 62 dependency(ies) and leaving 9 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (4288 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — This repository's JVM source (33 module(s), 372 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — 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
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 1 finding(s)
- Dependency-rule violation: HellNotes:feature:about-app (Application) → HellNotes:core:ui (Web)
Serious — 103 finding(s)
- TodoComment feature/search/src/main/java/com/hellguy39/hellnotes/feature/search/SearchRoute.kt:35
- TodoComment feature/reminder-edit/src/main/java/com/hellguy39/hellnotes/feature/reminderedit/ReminderEditViewModel.kt:75
- TodoComment feature/note-detail/src/main/java/com/hellguy39/hellnotes/feature/notedetail/NoteDetailViewModel.kt:284
- TodoComment feature/note-detail/src/main/java/com/hellguy39/hellnotes/feature/notedetail/NoteDetailViewModel.kt:353
- TodoComment core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/DateTimeUtils.kt:24
- TodoComment core/model/src/main/java/com/hellguy39/hellnotes/core/model/notification/HellNotesNotificationChannel.kt:21
- TodoComment core/domain/src/main/java/com/hellguy39/hellnotes/core/domain/usecase/reminder/ActivateReminderUseCase.kt:31
- TodoComment core/domain/src/main/java/com/hellguy39/hellnotes/core/domain/usecase/reminder/DeleteReminderUseCase.kt:29
- TodoComment core/domain/src/main/java/com/hellguy39/hellnotes/core/domain/usecase/reminder/UpdateReminderUseCase.kt:30
- MethodTooLong: NoteDetailRouteKt.NoteDetailRoute feature/note-detail/src/main/java/com/hellguy39/hellnotes/feature/notedetail/NoteDetailRoute.kt:63
- MethodTooLong: ReminderEditScreenKt.ReminderEditScreen feature/reminder-edit/src/main/java/com/hellguy39/hellnotes/feature/reminderedit/ReminderEditScreen.kt:58
- MethodTooLong: NoteDetailContentKt.NoteDetailContent feature/note-detail/src/main/java/com/hellguy39/hellnotes/feature/notedetail/components/NoteDetailContent.kt:76
- MethodTooLong: DrawerSheetContentKt.DrawerSheetContent feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/notes/components/DrawerSheetContent.kt:63
- MethodTooLong: LabelRouteKt.LabelRoute feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/label/LabelRoute.kt:62
- MethodTooLong: LockSetupPasswordScreenKt.LockSetupPasswordScreen feature/lock-setup/src/main/java/com/hellguy39/hellnotes/feature/locksetup/LockSetupPasswordScreen.kt:42
- MethodTooLong: LockSetupPinScreenKt.LockSetupPinScreen feature/lock-setup/src/main/java/com/hellguy39/hellnotes/feature/locksetup/LockSetupPinScreen.kt:42
- MethodTooLong: AboutAppScreenContentKt.AboutAppScreenContent feature/about-app/src/main/java/com/hellguy39/hellnotes/feature/aboutapp/components/AboutAppScreenContent.kt:47
- Constructible in an invalid state: ChecklistEntity core/database/src/main/java/com/hellguy39/hellnotes/core/database/entity/ChecklistEntity.kt:26
- Constructible in an invalid state: LabelEntity core/database/src/main/java/com/hellguy39/hellnotes/core/database/entity/LabelEntity.kt:25
- Constructible in an invalid state: NoteEntity core/database/src/main/java/com/hellguy39/hellnotes/core/database/entity/NoteEntity.kt:25
- Constructible in an invalid state: ReminderEntity core/database/src/main/java/com/hellguy39/hellnotes/core/database/entity/ReminderEntity.kt:27
- Duplicated block (15 lines × 2) feature/label-selection/src/main/java/com/hellguy39/hellnotes/feature/labelselection/navigation/LabelSelectionNavigation.kt:36
- Duplicated block (15 lines × 2) feature/lock/src/main/java/com/hellguy39/hellnotes/feature/lock/LockScreenPassword.kt:61
- Duplicated block (15 lines × 2) feature/privacy-policy/src/main/java/com/hellguy39/hellnotes/feature/privacypolicy/PrivacyPolicyScreen.kt:41
- Duplicated block (14 lines × 2) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/items/HNCheckboxItem.kt:49
- Duplicated block (14 lines × 2) feature/changelog/src/main/java/com/hellguy39/hellnotes/feature/changelog/ChangelogScreen.kt:54
- Duplicated block (14 lines × 2) feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/label/LabelSсreen.kt:87
- Duplicated block (12 lines × 2) feature/reminder-edit/src/main/java/com/hellguy39/hellnotes/feature/reminderedit/ReminderEditScreen.kt:267
- Duplicated block (12 lines × 2) core/store-api/src/main/java/com/hellguy39/hellnotes/core/storeapi/review/provider/PlayStoreReviewProvider.kt:53
- Duplicated block (12 lines × 2) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/CustomDialog.kt:212
- Edited copy of a member (27 corresponding lines) feature/label-selection/src/main/java/com/hellguy39/hellnotes/feature/labelselection/navigation/LabelSelectionNavigation.kt:30
- Edited copy of a member (27 corresponding lines) feature/backup/src/main/java/com/hellguy39/hellnotes/feature/backup/BackupViewModel.kt:67
- Edited copy of a member (20 corresponding lines) core/store-api/src/main/java/com/hellguy39/hellnotes/core/storeapi/update/provider/PlayStoreUpdateProvider.kt:61
- Edited copy of a member (20 corresponding lines) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/focus/RequestFocusBeAvailable.kt:29
- Edited copy of a member (15 corresponding lines) core/domain/src/main/java/com/hellguy39/hellnotes/core/domain/usecase/note/GetAllNoteWrappersUseCase.kt:34
- Edited copy of a member (15 corresponding lines) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/items/HNCheckboxItem.kt:163
- Edited copy of a member (12 corresponding lines) core/data/src/main/java/com/hellguy39/hellnotes/core/data/database/BackupManagerImpl.kt:33
- Edited copy of a member (12 corresponding lines) core/store-api/src/main/java/com/hellguy39/hellnotes/core/storeapi/review/provider/PlayStoreReviewProvider.kt:66
- Edited copies of one member (4 members, 8+ corresponding lines) feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/archive/ArchiveViewModel.kt:117
- Edited copies of one member (4 members, 8+ corresponding lines) feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/archive/ArchiveViewModel.kt:126
- Edited copy of a member (8 corresponding lines) core/store-api/src/main/java/com/hellguy39/hellnotes/core/storeapi/update/provider/PlayStoreUpdateProvider.kt:93
- Edited copy of a member (8 corresponding lines) feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/HomeState.kt:46
- Duplicated block (19 lines × 2) core/network/src/main/java/com/hellguy39/hellnotes/core/network/mapper/ReleaseMapper.kt:68
- Duplicated block (19 lines × 2) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/list/NoteGridList.kt:54
- Duplicated block (18 lines × 2) feature/lock/src/main/java/com/hellguy39/hellnotes/feature/lock/LockScreenPassword.kt:129
- Duplicated block (18 lines × 2) feature/privacy-policy/src/main/java/com/hellguy39/hellnotes/feature/privacypolicy/PrivacyPolicyScreen.kt:96
- Duplicated block (17 lines × 2) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/NoteChipGroup.kt:57
- Duplicated block (17 lines × 2) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/items/HNCheckboxItem.kt:133
- Duplicated block (15–16 lines × 2) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/items/HNCheckboxItem.kt:57
- Duplicated block (15–16 lines × 2) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/items/HNCheckboxItem.kt:118
- Duplicated block (9 lines × 2) feature/backup/src/main/java/com/hellguy39/hellnotes/feature/backup/BackupViewModel.kt:70
- Duplicated block (9 lines × 2) feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/HomeState.kt:114
- Off the main sequence: HellNotes:core:model
- Off the main sequence: HellNotes:core:ui
- CustomDialogKt.CustomDialog (cognitive 19) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/CustomDialog.kt:41
- NoteChipGroupKt.NoteChipGroup (cognitive 16) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/NoteChipGroup.kt:38
- LockSetupPasswordScreenKt.LockSetupPasswordScreen (cognitive 16) feature/lock-setup/src/main/java/com/hellguy39/hellnotes/feature/locksetup/LockSetupPasswordScreen.kt:42
- LockSetupPinScreenKt.LockSetupPinScreen (cognitive 16) feature/lock-setup/src/main/java/com/hellguy39/hellnotes/feature/locksetup/LockSetupPinScreen.kt:42
- Near-duplicate member pair (96 shared lines) feature/lock-setup/src/main/java/com/hellguy39/hellnotes/feature/locksetup/LockSetupPasswordScreen.kt:45
- Near-duplicate member pair (72 shared lines) feature/privacy-policy/src/main/java/com/hellguy39/hellnotes/feature/privacypolicy/PrivacyPolicyScreen.kt:40
- Members sharing a duplicated core (5 members, 50+ identical tokens) feature/changelog/src/main/java/com/hellguy39/hellnotes/feature/changelog/navigation/ChangelogNavigation.kt:28
- Members sharing a duplicated core (4 members, 50+ identical tokens) feature/language-selection/src/main/java/com/hellguy39/hellnotes/feature/languageselection/navigation/LanguageSelectionNavigation.kt:28
- Edited copies of one member (3 members, 77+ corresponding lines) feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/archive/components/ArchiveTopAppBar.kt:41
- Edited copy of a member (43 corresponding lines) feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/notes/NotesRoute.kt:43
- Edited copies of one member (3 members, 48+ corresponding lines) feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/archive/ArchiveScreen.kt:54
- Edited copy of a member (44 corresponding lines) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/items/HNListItem.kt:57
- Edited copy of a member (50 corresponding lines) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/items/HNCheckboxItem.kt:48
- Edited copy of a member (36 corresponding lines) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/list/NoteColumnList.kt:49
- Edited copies of one member (3 members, 33+ corresponding lines) feature/changelog/src/main/java/com/hellguy39/hellnotes/feature/changelog/ChangelogViewModel.kt:51
- Edited copy of a member (25 corresponding lines) feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/label/components/LabelDropdownMenu.kt:32
- Edited copy of a member (34 corresponding lines) feature/label-edit/src/main/java/com/hellguy39/hellnotes/feature/labeledit/LabelEditScreen.kt:45
- Edited copies of one member (3 members, 18+ corresponding lines) feature/about-app/src/main/java/com/hellguy39/hellnotes/feature/aboutapp/navigation/AboutAppNavigation.kt:30
- Edited copy of a member (18 corresponding lines) core/domain/src/main/java/com/hellguy39/hellnotes/core/domain/usecase/note/GetAllNoteWrappersFlowUseCase.kt:41
- Edited copy of a member (24 corresponding lines) feature/about-app/src/main/java/com/hellguy39/hellnotes/feature/aboutapp/AboutAppScreen.kt:36
- Edited copies of one member (5 members, 16+ corresponding lines) feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/archive/ArchiveViewModel.kt:65
- Edited copies of one member (5 members, 9+ corresponding lines) core/data/src/main/java/com/hellguy39/hellnotes/core/data/repository/remote/GithubRepositoryServiceImpl.kt:36
- Edited copy of a member (16 corresponding lines) feature/reminder-edit/src/main/java/com/hellguy39/hellnotes/feature/reminderedit/ReminderEditViewModel.kt:95
- Edited copy of a member (19 corresponding lines) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/topappbars/HNLargeTopAppBar.kt:34
- Edited copies of one member (3 members, 6+ corresponding lines) core/domain/src/main/java/com/hellguy39/hellnotes/core/domain/usecase/label/GetAllArchivedNoteWrappersByLabelId.kt:35
- Edited copy of a member (9 corresponding lines) core/store-api/src/main/java/com/hellguy39/hellnotes/core/storeapi/review/provider/PlayStoreReviewProvider.kt:41
- Edited copy of a member (11 corresponding lines) core/store-api/src/main/java/com/hellguy39/hellnotes/core/storeapi/update/provider/PlayStoreUpdateProvider.kt:102
- Duplicated block (41 lines × 2) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/items/NoteItems.kt:54
- Duplicated block (34–35 lines × 2) feature/privacy-policy/src/main/java/com/hellguy39/hellnotes/feature/privacypolicy/PrivacyPolicyScreen.kt:57
- Duplicated block (33 lines × 4) feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/archive/components/ArchiveTopAppBar.kt:55
- Duplicated block (43 lines × 2) feature/lock-setup/src/main/java/com/hellguy39/hellnotes/feature/locksetup/LockSetupPasswordScreen.kt:88
- Duplicated block (31 lines × 2) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/list/NoteList.kt:60
- Duplicated block (30 lines × 3) feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/archive/components/ArchiveTopAppBar.kt:92
- Duplicated block (27 lines × 2) feature/lock-setup/src/main/java/com/hellguy39/hellnotes/feature/locksetup/LockSetupPasswordScreen.kt:137
- Duplicated block (26 lines × 2) feature/lock-setup/src/main/java/com/hellguy39/hellnotes/feature/locksetup/LockSetupPasswordScreen.kt:165
- Duplicated block (22–23 lines × 2) core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/list/NoteColumnList.kt:63
- Duplicated block (21 lines × 2) feature/note-detail/src/main/java/com/hellguy39/hellnotes/feature/notedetail/NoteDetailRoute.kt:227
- Duplicated block (17–20 lines × 3) feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/label/LabelViewModel.kt:149
- Duplicated block (16 lines × 5) feature/changelog/src/main/java/com/hellguy39/hellnotes/feature/changelog/navigation/ChangelogNavigation.kt:31
- Duplicated block (16 lines × 2) feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/label/components/LabelTopAppBar.kt:98
- Duplicated block (14–15 lines × 4) feature/language-selection/src/main/java/com/hellguy39/hellnotes/feature/languageselection/navigation/LanguageSelectionNavigation.kt:32
- Duplicated block (15 lines × 3) feature/changelog/src/main/java/com/hellguy39/hellnotes/feature/changelog/ChangelogScreen.kt:108
- Duplicated block (13 lines × 3) feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/archive/ArchiveScreen.kt:67
- Duplicated block (7 lines × 2) core/domain/src/main/java/com/hellguy39/hellnotes/core/domain/usecase/backup/BackupDatabaseUseCase.kt:45
- Duplicated block (13 lines × 2) core/database/src/main/java/com/hellguy39/hellnotes/core/database/mapper/NoteMapper.kt:21
- Duplicated block (12 lines × 5) feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/archive/ArchiveViewModel.kt:82
- Duplicated block (8 lines × 2) feature/lock-setup/src/main/java/com/hellguy39/hellnotes/feature/locksetup/LockSetupPasswordScreen.kt:241
- Unstable project HellNotes:core:data
- No CI pipeline
Minor — 164 finding(s)
- Orphaned file feature/note-detail/src/main/java/com/hellguy39/hellnotes/feature/notedetail/NoteDetailRoute.kt:1
- Orphaned file feature/note-detail/src/main/java/com/hellguy39/hellnotes/feature/notedetail/components/NoteDetailContent.kt:1
- Orphaned file feature/reminder-edit/src/main/java/com/hellguy39/hellnotes/feature/reminderedit/ReminderEditScreen.kt:1
- Orphaned file feature/note-detail/src/main/java/com/hellguy39/hellnotes/feature/notedetail/NoteDetailViewModel.kt:1
- Orphaned file core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/resources/AppStrings.kt:1
- Orphaned file feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/notes/components/DrawerSheetContent.kt:1
- Orphaned file feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/label/LabelRoute.kt:1
- Orphaned file feature/lock-setup/src/main/java/com/hellguy39/hellnotes/feature/locksetup/LockSetupPasswordScreen.kt:1
- Orphaned file feature/lock-setup/src/main/java/com/hellguy39/hellnotes/feature/locksetup/LockSetupPinScreen.kt:1
- Orphaned file feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/label/LabelViewModel.kt:1
- Orphaned file feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/notes/NotesViewModel.kt:1
- Orphaned file feature/search/src/main/java/com/hellguy39/hellnotes/feature/search/SearchScreen.kt:1
- Orphaned file core/datastore/src/main/java/com/hellguy39/hellnotes/core/datastore/HellNotesPreferencesDataSource.kt:1
- Orphaned file core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/CustomDialog.kt:1
- Orphaned file core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/cards/NoteCard.kt:1
- Orphaned file feature/about-app/src/main/java/com/hellguy39/hellnotes/feature/aboutapp/components/AboutAppScreenContent.kt:1
- Orphaned file core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/navigations/NavigateTo.kt:1
- Orphaned file feature/note-swipe-edit/src/main/java/com/hellguy39/hellnotes/feature/noteswipeedit/NoteSwipeEditScreen.kt:1
- Orphaned file core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/items/HNListItem.kt:1
- Orphaned file feature/reminder-edit/src/main/java/com/hellguy39/hellnotes/feature/reminderedit/ReminderEditViewModel.kt:1
- Orphaned file feature/on-boarding/src/main/java/com/hellguy39/hellnotes/feature/onboarding/OnBoardingScreen.kt:1
- Orphaned file feature/backup/src/main/java/com/hellguy39/hellnotes/feature/backup/BackupScreen.kt:1
- Orphaned file feature/home/src/main/java/com/hellguy39/hellnotes/feature/home/notes/components/NoteListTopAppBar.kt:1
- Orphaned file feature/note-style-edit/src/main/java/com/hellguy39/hellnotes/feature/notestyleedit/NoteStyleEditScreen.kt:1
- Orphaned file feature/lock/src/main/java/com/hellguy39/hellnotes/feature/lock/LockViewModel.kt:1
- Documentation: no build, run or usage example README.md:1
- No ADRs found build-logic/convention/build.gradle.kts:41
- Projects may be oversized for their cohesion core/ui/build.gradle.kts:1
- Dormant codebase
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation app/build.gradle.kts:78
- No changelog
- Duplicated predicate core/ui/src/main/java/com/hellguy39/hellnotes/core/ui/components/list/NoteColumnList.kt:61
Minor — 1 finding(s)
- Off the main sequence: HellNotes:core: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-18dd1df1483e4007a96dac6e07984769/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-18dd1df1483e4007a96dac6e07984769/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |