Executive summary
ahuamana/prestamistAPP falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 61.7 out of 100 and is rated Adequate, and all 11 of its critical findings are security problems.
Production Readiness, at 50.2, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 7.9 points. Fixing the password or key in the code comes next, worth about 7.6 points. Raising Production Readiness to 70 would lift the score to about 67.9.
Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One password or key in the code and one in the code's history are open to anyone who can read the repository. Replacing each exposed password or key and pinning each tool to an exact version would close both risks.
The product code is 7,078 lines, about €8,000 to rebuild.
If Production Readiness rose from 50.2 to 70, the lowest score rated Strong, the score would rise from 61.7 to about 67.9.
Rebuild cost: about €8,000 · Estimate
| Cost to rebuild | €2,700 to €13,000, for 44 to 140 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 62. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 7,078 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: which parts of the code depend on which
| uses → | 1 application | 2 data.network | 3 domain | 4 domain.clients | 5 domain.notification | 6 helper.base.BaseViewModel | 7 presentation.clients.ClientsAddViewModel | 8 presentation.dashboard.viewmodels.ViewModelDetailReceipt | 9 presentation.principal.viewmodels.ViewModelPrincipal | 10 data.providers | 11 data.utils | 12 frameworks.network | 13 helper.base | 14 presentation.clients.adater.ClientAdapter | 15 presentation.dashboard.interfaces | 16 presentation.dashboard.viewmodels.ViewModelDashboard | 17 presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState | 18 presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal | 19 presentation.principal.views | 20 presentation.registro.adapter.ClientSelectAdapter | 21 presentation.tesoreria.adapter | 22 data.remote.clients | 23 data.services | 24 presentation.clients.adater | 25 presentation.dashboard.adapters | 26 presentation.dashboard.adapters.LoanAdapter | 27 presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent | 28 presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState | 29 presentation.registro.adapter | 30 data.remote | 31 presentation.dashboard.views | 32 data.repository | 33 presentation.clients | 34 presentation.dashboard.viewmodels | 35 presentation.login.viewmodels | 36 presentation.principal.viewmodels | 37 presentation.registro.viewmodels | 38 presentation.login.views | 39 presentation.registro.views | 40 presentation.tesoreria.views |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 application | ||||||||||||||||||||||||||||||||||||||||
| 2 data.network | ||||||||||||||||||||||||||||||||||||||||
| 3 domain | ||||||||||||||||||||||||||||||||||||||||
| 4 domain.clients | ||||||||||||||||||||||||||||||||||||||||
| 5 domain.notification | ||||||||||||||||||||||||||||||||||||||||
| 6 helper.base.BaseViewModel | ||||||||||||||||||||||||||||||||||||||||
| 7 presentation.clients.ClientsAddViewModel | ||||||||||||||||||||||||||||||||||||||||
| 8 presentation.dashboard.viewmodels.ViewModelDetailReceipt | ||||||||||||||||||||||||||||||||||||||||
| 9 presentation.principal.viewmodels.ViewModelPrincipal | ||||||||||||||||||||||||||||||||||||||||
| 10 data.providers | 3 | 7 | 5 | 1 | ||||||||||||||||||||||||||||||||||||
| 11 data.utils | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 frameworks.network | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 helper.base | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 presentation.clients.adater.ClientAdapter | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 presentation.dashboard.interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 presentation.dashboard.viewmodels.ViewModelDashboard | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 18 presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 19 presentation.principal.views | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 presentation.registro.adapter.ClientSelectAdapter | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 presentation.tesoreria.adapter | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 data.remote.clients | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 data.services | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 presentation.clients.adater | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 presentation.dashboard.adapters | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 presentation.dashboard.adapters.LoanAdapter | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 27 presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent | 3 | 6 | ||||||||||||||||||||||||||||||||||||||
| 28 presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 presentation.registro.adapter | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 data.remote | 12 | 10 | 4 | 7 | 1 | |||||||||||||||||||||||||||||||||||
| 31 presentation.dashboard.views | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 32 data.repository | 6 | 8 | 2 | 2 | 1 | 1 | 7 | |||||||||||||||||||||||||||||||||
| 33 presentation.clients | 1 | 1 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 34 presentation.dashboard.viewmodels | 1 | 3 | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||||
| 35 presentation.login.viewmodels | 2 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 36 presentation.principal.viewmodels | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 37 presentation.registro.viewmodels | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 presentation.login.views | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 39 presentation.registro.views | 1 | 3 | 2 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 40 presentation.tesoreria.views | 1 | 1 | 1 | 1 |
10→1 data.providers uses application✕
- Connections
- 3 pairs of types, where a type in data.providers uses a type in application.
- The types involved
com.paparazziapps.pretamistapp.data.providers.DetailLoanProvider→com.paparazziapps.pretamistapp.application.MyPreferencescom.paparazziapps.pretamistapp.data.providers.LoanProvider→com.paparazziapps.pretamistapp.application.MyPreferencescom.paparazziapps.pretamistapp.data.providers.LoginProvider→com.paparazziapps.pretamistapp.application.MyPreferences
- Direction
- data.providers uses application, so a change to application can break data.providers, while a change to data.providers can't break application.
- Position
- Below the diagonal: data.providers uses a module listed above it, which is the healthy direction.
10→2 data.providers uses data.network✕
- Connections
- 7 pairs of types, where a type in data.providers uses a type in data.network.
- The types involved
com.paparazziapps.pretamistapp.data.providers.BranchesProvider→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.providers.ClientsProvider→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.providers.DetailLoanProvider→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.providers.LoanProvider→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.providers.LoginProvider→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.providers.RegisterProvider→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.providers.UserProvider→com.paparazziapps.pretamistapp.data.network.PAResult
- Direction
- data.providers uses data.network, so a change to data.network can break data.providers, while a change to data.providers can't break data.network.
- Position
- Below the diagonal: data.providers uses a module listed above it, which is the healthy direction.
10→3 data.providers uses domain✕
- Connections
- 5 pairs of types, where a type in data.providers uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.data.providers.DetailLoanProvider→com.paparazziapps.pretamistapp.domain.DetailLoanDomaincom.paparazziapps.pretamistapp.data.providers.DetailLoanProvider→com.paparazziapps.pretamistapp.domain.DetailLoanFormcom.paparazziapps.pretamistapp.data.providers.LoanProvider→com.paparazziapps.pretamistapp.domain.LoanDomaincom.paparazziapps.pretamistapp.data.providers.LoginProvider→com.paparazziapps.pretamistapp.domain.UserFormcom.paparazziapps.pretamistapp.data.providers.UserProvider→com.paparazziapps.pretamistapp.domain.UserForm
- Direction
- data.providers uses domain, so a change to domain can break data.providers, while a change to data.providers can't break domain.
- Position
- Below the diagonal: data.providers uses a module listed above it, which is the healthy direction.
10→4 data.providers uses domain.clients✕
- Connections
- 1 pair of types, where a type in data.providers uses a type in domain.clients.
- The types involved
com.paparazziapps.pretamistapp.data.providers.ClientsProvider→com.paparazziapps.pretamistapp.domain.clients.ClientDomain
- Direction
- data.providers uses domain.clients, so a change to domain.clients can break data.providers, while a change to data.providers can't break domain.clients.
- Position
- Below the diagonal: data.providers uses a module listed above it, which is the healthy direction.
11→5 data.utils uses domain.notification✕
- Connections
- 1 pair of types, where a type in data.utils uses a type in domain.notification.
- The types involved
com.paparazziapps.pretamistapp.data.utils.ReceiptHtmlTemplate→com.paparazziapps.pretamistapp.domain.notification.ReceiptParams
- Direction
- data.utils uses domain.notification, so a change to domain.notification can break data.utils, while a change to data.utils can't break domain.notification.
- Position
- Below the diagonal: data.utils uses a module listed above it, which is the healthy direction.
12→1 frameworks.network uses application✕
- Connections
- 2 pairs of types, where a type in frameworks.network uses a type in application.
- The types involved
com.paparazziapps.pretamistapp.frameworks.network.HeaderInterceptor→com.paparazziapps.pretamistapp.application.MyPreferencescom.paparazziapps.pretamistapp.frameworks.network.NetworkModuleImpl→com.paparazziapps.pretamistapp.application.MyPreferences
- Direction
- frameworks.network uses application, so a change to application can break frameworks.network, while a change to frameworks.network can't break application.
- Position
- Below the diagonal: frameworks.network uses a module listed above it, which is the healthy direction.
13→6 helper.base uses helper.base.BaseViewModel✕
- Connections
- 1 pair of types, where a type in helper.base uses a type in helper.base.BaseViewModel.
- The types involved
com.paparazziapps.pretamistapp.helper.base.BaseViewModel→com.paparazziapps.pretamistapp.helper.base.BaseViewModel.UiState
- Direction
- helper.base uses helper.base.BaseViewModel, so a change to helper.base.BaseViewModel can break helper.base, while a change to helper.base can't break helper.base.BaseViewModel.
- Position
- Below the diagonal: helper.base uses a module listed above it, which is the healthy direction.
14→4 presentation.clients.adater.ClientAdapter uses domain.clients✕
- Connections
- 1 pair of types, where a type in presentation.clients.adater.ClientAdapter uses a type in domain.clients.
- The types involved
com.paparazziapps.pretamistapp.presentation.clients.adater.ClientAdapter.ClientViewHolder→com.paparazziapps.pretamistapp.domain.clients.ClientDomain
- Direction
- presentation.clients.adater.ClientAdapter uses domain.clients, so a change to domain.clients can break presentation.clients.adater.ClientAdapter, while a change to presentation.clients.adater.ClientAdapter can't break domain.clients.
- Position
- Below the diagonal: presentation.clients.adater.ClientAdapter uses a module listed above it, which is the healthy direction.
15→3 presentation.dashboard.interfaces uses domain✕
- Connections
- 1 pair of types, where a type in presentation.dashboard.interfaces uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.interfaces.SetOnClickedLoan→com.paparazziapps.pretamistapp.domain.LoanDomain
- Direction
- presentation.dashboard.interfaces uses domain, so a change to domain can break presentation.dashboard.interfaces, while a change to presentation.dashboard.interfaces can't break domain.
- Position
- Below the diagonal: presentation.dashboard.interfaces uses a module listed above it, which is the healthy direction.
16→3 presentation.dashboard.viewmodels.ViewModelDashboard uses domain✕
- Connections
- 2 pairs of types, where a type in presentation.dashboard.viewmodels.ViewModelDashboard uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState→com.paparazziapps.pretamistapp.domain.InformationReceiptDomaincom.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState→com.paparazziapps.pretamistapp.domain.LoanDomain
- Direction
- presentation.dashboard.viewmodels.ViewModelDashboard uses domain, so a change to domain can break presentation.dashboard.viewmodels.ViewModelDashboard, while a change to presentation.dashboard.viewmodels.ViewModelDashboard can't break domain.
- Position
- Below the diagonal: presentation.dashboard.viewmodels.ViewModelDashboard uses a module listed above it, which is the healthy direction.
17→3 presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState uses domain✕
- Connections
- 1 pair of types, where a type in presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState.Success→com.paparazziapps.pretamistapp.domain.InformationReceiptDomain
- Direction
- presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState uses domain, so a change to domain can break presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState, while a change to presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState can't break domain.
- Position
- Below the diagonal: presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState uses a module listed above it, which is the healthy direction.
17→8 presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState uses presentation.dashboard.viewmodels.ViewModelDetailReceipt✕
- Connections
- 3 pairs of types, where a type in presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState uses a type in presentation.dashboard.viewmodels.ViewModelDetailReceipt.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState.Error→com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptStatecom.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState.Loading→com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptStatecom.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState.Success→com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState
- Direction
- presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState uses presentation.dashboard.viewmodels.ViewModelDetailReceipt, so a change to presentation.dashboard.viewmodels.ViewModelDetailReceipt can break presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState, while a change to presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState can't break presentation.dashboard.viewmodels.ViewModelDetailReceipt.
- Position
- Below the diagonal: presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState uses a module listed above it, which is the healthy direction.
18→3 presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal uses domain✕
- Connections
- 2 pairs of types, where a type in presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal.SuccessActiveUser→com.paparazziapps.pretamistapp.domain.Sucursalescom.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal.SuccessInactiveUser→com.paparazziapps.pretamistapp.domain.Sucursales
- Direction
- presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal uses domain, so a change to domain can break presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal, while a change to presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal can't break domain.
- Position
- Below the diagonal: presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal uses a module listed above it, which is the healthy direction.
18→9 presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal uses presentation.principal.viewmodels.ViewModelPrincipal✕
- Connections
- 4 pairs of types, where a type in presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal uses a type in presentation.principal.viewmodels.ViewModelPrincipal.
- The types involved
com.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal.Error→com.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipalcom.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal.Loading→com.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipalcom.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal.SuccessActiveUser→com.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipalcom.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal.SuccessInactiveUser→com.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal
- Direction
- presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal uses presentation.principal.viewmodels.ViewModelPrincipal, so a change to presentation.principal.viewmodels.ViewModelPrincipal can break presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal, while a change to presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal can't break presentation.principal.viewmodels.ViewModelPrincipal.
- Position
- Below the diagonal: presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal uses a module listed above it, which is the healthy direction.
19→1 presentation.principal.views uses application✕
- Connections
- 1 pair of types, where a type in presentation.principal.views uses a type in application.
- The types involved
com.paparazziapps.pretamistapp.presentation.principal.views.PrincipalActivity→com.paparazziapps.pretamistapp.application.MyPreferences
- Direction
- presentation.principal.views uses application, so a change to application can break presentation.principal.views, while a change to presentation.principal.views can't break application.
- Position
- Below the diagonal: presentation.principal.views uses a module listed above it, which is the healthy direction.
19→3 presentation.principal.views uses domain✕
- Connections
- 1 pair of types, where a type in presentation.principal.views uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.principal.views.PrincipalActivity→com.paparazziapps.pretamistapp.domain.LoanDomain
- Direction
- presentation.principal.views uses domain, so a change to domain can break presentation.principal.views, while a change to presentation.principal.views can't break domain.
- Position
- Below the diagonal: presentation.principal.views uses a module listed above it, which is the healthy direction.
19→9 presentation.principal.views uses presentation.principal.viewmodels.ViewModelPrincipal✕
- Connections
- 1 pair of types, where a type in presentation.principal.views uses a type in presentation.principal.viewmodels.ViewModelPrincipal.
- The types involved
com.paparazziapps.pretamistapp.presentation.principal.views.PrincipalActivity→com.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal
- Direction
- presentation.principal.views uses presentation.principal.viewmodels.ViewModelPrincipal, so a change to presentation.principal.viewmodels.ViewModelPrincipal can break presentation.principal.views, while a change to presentation.principal.views can't break presentation.principal.viewmodels.ViewModelPrincipal.
- Position
- Below the diagonal: presentation.principal.views uses a module listed above it, which is the healthy direction.
20→4 presentation.registro.adapter.ClientSelectAdapter uses domain.clients✕
- Connections
- 1 pair of types, where a type in presentation.registro.adapter.ClientSelectAdapter uses a type in domain.clients.
- The types involved
com.paparazziapps.pretamistapp.presentation.registro.adapter.ClientSelectAdapter.ClientSelectViewHolder→com.paparazziapps.pretamistapp.domain.clients.ClientDomainSelect
- Direction
- presentation.registro.adapter.ClientSelectAdapter uses domain.clients, so a change to domain.clients can break presentation.registro.adapter.ClientSelectAdapter, while a change to presentation.registro.adapter.ClientSelectAdapter can't break domain.clients.
- Position
- Below the diagonal: presentation.registro.adapter.ClientSelectAdapter uses a module listed above it, which is the healthy direction.
21→3 presentation.tesoreria.adapter uses domain✕
- Connections
- 1 pair of types, where a type in presentation.tesoreria.adapter uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.tesoreria.adapter.LoanDetailAdapter→com.paparazziapps.pretamistapp.domain.LoanDomain
- Direction
- presentation.tesoreria.adapter uses domain, so a change to domain can break presentation.tesoreria.adapter, while a change to presentation.tesoreria.adapter can't break domain.
- Position
- Below the diagonal: presentation.tesoreria.adapter uses a module listed above it, which is the healthy direction.
22→2 data.remote.clients uses data.network✕
- Connections
- 2 pairs of types, where a type in data.remote.clients uses a type in data.network.
- The types involved
com.paparazziapps.pretamistapp.data.remote.clients.RemoteClientsDataSource→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.remote.clients.RemoteClientsDataSourceImpl→com.paparazziapps.pretamistapp.data.network.PAResult
- Direction
- data.remote.clients uses data.network, so a change to data.network can break data.remote.clients, while a change to data.remote.clients can't break data.network.
- Position
- Below the diagonal: data.remote.clients uses a module listed above it, which is the healthy direction.
22→4 data.remote.clients uses domain.clients✕
- Connections
- 2 pairs of types, where a type in data.remote.clients uses a type in domain.clients.
- The types involved
com.paparazziapps.pretamistapp.data.remote.clients.RemoteClientsDataSource→com.paparazziapps.pretamistapp.domain.clients.ClientDomaincom.paparazziapps.pretamistapp.data.remote.clients.RemoteClientsDataSourceImpl→com.paparazziapps.pretamistapp.domain.clients.ClientDomain
- Direction
- data.remote.clients uses domain.clients, so a change to domain.clients can break data.remote.clients, while a change to data.remote.clients can't break domain.clients.
- Position
- Below the diagonal: data.remote.clients uses a module listed above it, which is the healthy direction.
22→10 data.remote.clients uses data.providers✕
- Connections
- 1 pair of types, where a type in data.remote.clients uses a type in data.providers.
- The types involved
com.paparazziapps.pretamistapp.data.remote.clients.RemoteClientsDataSourceImpl→com.paparazziapps.pretamistapp.data.providers.ClientsProvider
- Direction
- data.remote.clients uses data.providers, so a change to data.providers can break data.remote.clients, while a change to data.remote.clients can't break data.providers.
- Position
- Below the diagonal: data.remote.clients uses a module listed above it, which is the healthy direction.
23→5 data.services uses domain.notification✕
- Connections
- 2 pairs of types, where a type in data.services uses a type in domain.notification.
- The types involved
com.paparazziapps.pretamistapp.data.services.EmailRetrofit→com.paparazziapps.pretamistapp.domain.notification.EmailReceiptResponsecom.paparazziapps.pretamistapp.data.services.EmailRetrofit→com.paparazziapps.pretamistapp.domain.notification.EmailRequest
- Direction
- data.services uses domain.notification, so a change to domain.notification can break data.services, while a change to data.services can't break domain.notification.
- Position
- Below the diagonal: data.services uses a module listed above it, which is the healthy direction.
23→12 data.services uses frameworks.network✕
- Connections
- 1 pair of types, where a type in data.services uses a type in frameworks.network.
- The types involved
com.paparazziapps.pretamistapp.data.services.ServiceProviderImpl→com.paparazziapps.pretamistapp.frameworks.network.NetworkModule
- Direction
- data.services uses frameworks.network, so a change to frameworks.network can break data.services, while a change to data.services can't break frameworks.network.
- Position
- Below the diagonal: data.services uses a module listed above it, which is the healthy direction.
24→4 presentation.clients.adater uses domain.clients✕
- Connections
- 2 pairs of types, where a type in presentation.clients.adater uses a type in domain.clients.
- The types involved
com.paparazziapps.pretamistapp.presentation.clients.adater.ClientAdapter→com.paparazziapps.pretamistapp.domain.clients.ClientDomaincom.paparazziapps.pretamistapp.presentation.clients.adater.SetOnClickListenerClient→com.paparazziapps.pretamistapp.domain.clients.ClientDomain
- Direction
- presentation.clients.adater uses domain.clients, so a change to domain.clients can break presentation.clients.adater, while a change to presentation.clients.adater can't break domain.clients.
- Position
- Below the diagonal: presentation.clients.adater uses a module listed above it, which is the healthy direction.
24→14 presentation.clients.adater uses presentation.clients.adater.ClientAdapter✕
- Connections
- 1 pair of types, where a type in presentation.clients.adater uses a type in presentation.clients.adater.ClientAdapter.
- The types involved
com.paparazziapps.pretamistapp.presentation.clients.adater.ClientAdapter→com.paparazziapps.pretamistapp.presentation.clients.adater.ClientAdapter.ClientViewHolder
- Direction
- presentation.clients.adater uses presentation.clients.adater.ClientAdapter, so a change to presentation.clients.adater.ClientAdapter can break presentation.clients.adater, while a change to presentation.clients.adater can't break presentation.clients.adater.ClientAdapter.
- Position
- Below the diagonal: presentation.clients.adater uses a module listed above it, which is the healthy direction.
25→3 presentation.dashboard.adapters uses domain✕
- Connections
- 1 pair of types, where a type in presentation.dashboard.adapters uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.adapters.LoanAdapter→com.paparazziapps.pretamistapp.domain.LoanDomain
- Direction
- presentation.dashboard.adapters uses domain, so a change to domain can break presentation.dashboard.adapters, while a change to presentation.dashboard.adapters can't break domain.
- Position
- Below the diagonal: presentation.dashboard.adapters uses a module listed above it, which is the healthy direction.
25→15 presentation.dashboard.adapters uses presentation.dashboard.interfaces✕
- Connections
- 1 pair of types, where a type in presentation.dashboard.adapters uses a type in presentation.dashboard.interfaces.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.adapters.LoanAdapter→com.paparazziapps.pretamistapp.presentation.dashboard.interfaces.SetOnClickedLoan
- Direction
- presentation.dashboard.adapters uses presentation.dashboard.interfaces, so a change to presentation.dashboard.interfaces can break presentation.dashboard.adapters, while a change to presentation.dashboard.adapters can't break presentation.dashboard.interfaces.
- Position
- Below the diagonal: presentation.dashboard.adapters uses a module listed above it, which is the healthy direction.
26→3 presentation.dashboard.adapters.LoanAdapter uses domain✕
- Connections
- 3 pairs of types, where a type in presentation.dashboard.adapters.LoanAdapter uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.adapters.LoanAdapter.PrestamoViewHolder→com.paparazziapps.pretamistapp.domain.LoanDomaincom.paparazziapps.pretamistapp.presentation.dashboard.adapters.LoanAdapter.ViewHolder→com.paparazziapps.pretamistapp.domain.LoanDomaincom.paparazziapps.pretamistapp.presentation.dashboard.adapters.LoanAdapter.ViewHolderTitle→com.paparazziapps.pretamistapp.domain.LoanDomain
- Direction
- presentation.dashboard.adapters.LoanAdapter uses domain, so a change to domain can break presentation.dashboard.adapters.LoanAdapter, while a change to presentation.dashboard.adapters.LoanAdapter can't break domain.
- Position
- Below the diagonal: presentation.dashboard.adapters.LoanAdapter uses a module listed above it, which is the healthy direction.
26→15 presentation.dashboard.adapters.LoanAdapter uses presentation.dashboard.interfaces✕
- Connections
- 3 pairs of types, where a type in presentation.dashboard.adapters.LoanAdapter uses a type in presentation.dashboard.interfaces.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.adapters.LoanAdapter.PrestamoViewHolder→com.paparazziapps.pretamistapp.presentation.dashboard.interfaces.SetOnClickedLoancom.paparazziapps.pretamistapp.presentation.dashboard.adapters.LoanAdapter.ViewHolder→com.paparazziapps.pretamistapp.presentation.dashboard.interfaces.SetOnClickedLoancom.paparazziapps.pretamistapp.presentation.dashboard.adapters.LoanAdapter.ViewHolderTitle→com.paparazziapps.pretamistapp.presentation.dashboard.interfaces.SetOnClickedLoan
- Direction
- presentation.dashboard.adapters.LoanAdapter uses presentation.dashboard.interfaces, so a change to presentation.dashboard.interfaces can break presentation.dashboard.adapters.LoanAdapter, while a change to presentation.dashboard.adapters.LoanAdapter can't break presentation.dashboard.interfaces.
- Position
- Below the diagonal: presentation.dashboard.adapters.LoanAdapter uses a module listed above it, which is the healthy direction.
27→3 presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent uses domain✕
- Connections
- 3 pairs of types, where a type in presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent.SendMessageToOtherApp→com.paparazziapps.pretamistapp.domain.LoanDomaincom.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent.SendMessageToWhatsApp→com.paparazziapps.pretamistapp.domain.LoanDomaincom.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent.UpdateLoan→com.paparazziapps.pretamistapp.domain.LoanDomain
- Direction
- presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent uses domain, so a change to domain can break presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent, while a change to presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent can't break domain.
- Position
- Below the diagonal: presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent uses a module listed above it, which is the healthy direction.
27→16 presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent uses presentation.dashboard.viewmodels.ViewModelDashboard✕
- Connections
- 6 pairs of types, where a type in presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent uses a type in presentation.dashboard.viewmodels.ViewModelDashboard.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent.CloseLoan→com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntentcom.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent.LoadLoans→com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntentcom.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent.ResetStatusDialogs→com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntentcom.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent.SendMessageToOtherApp→com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntentcom.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent.SendMessageToWhatsApp→com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntentcom.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent.UpdateLoan→com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent
- Direction
- presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent uses presentation.dashboard.viewmodels.ViewModelDashboard, so a change to presentation.dashboard.viewmodels.ViewModelDashboard can break presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent, while a change to presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent can't break presentation.dashboard.viewmodels.ViewModelDashboard.
- Position
- Below the diagonal: presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntent uses a module listed above it, which is the healthy direction.
28→3 presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState uses domain✕
- Connections
- 1 pair of types, where a type in presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState.Companion→com.paparazziapps.pretamistapp.domain.LoanDomain
- Direction
- presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState uses domain, so a change to domain can break presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState, while a change to presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState can't break domain.
- Position
- Below the diagonal: presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState uses a module listed above it, which is the healthy direction.
28→16 presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState uses presentation.dashboard.viewmodels.ViewModelDashboard✕
- Connections
- 1 pair of types, where a type in presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState uses a type in presentation.dashboard.viewmodels.ViewModelDashboard.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState.Companion→com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState
- Direction
- presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState uses presentation.dashboard.viewmodels.ViewModelDashboard, so a change to presentation.dashboard.viewmodels.ViewModelDashboard can break presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState, while a change to presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState can't break presentation.dashboard.viewmodels.ViewModelDashboard.
- Position
- Below the diagonal: presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState uses a module listed above it, which is the healthy direction.
29→4 presentation.registro.adapter uses domain.clients✕
- Connections
- 2 pairs of types, where a type in presentation.registro.adapter uses a type in domain.clients.
- The types involved
com.paparazziapps.pretamistapp.presentation.registro.adapter.ClientSelectAdapter→com.paparazziapps.pretamistapp.domain.clients.ClientDomainSelectcom.paparazziapps.pretamistapp.presentation.registro.adapter.OnClientSelectListener→com.paparazziapps.pretamistapp.domain.clients.ClientDomainSelect
- Direction
- presentation.registro.adapter uses domain.clients, so a change to domain.clients can break presentation.registro.adapter, while a change to presentation.registro.adapter can't break domain.clients.
- Position
- Below the diagonal: presentation.registro.adapter uses a module listed above it, which is the healthy direction.
29→20 presentation.registro.adapter uses presentation.registro.adapter.ClientSelectAdapter✕
- Connections
- 1 pair of types, where a type in presentation.registro.adapter uses a type in presentation.registro.adapter.ClientSelectAdapter.
- The types involved
com.paparazziapps.pretamistapp.presentation.registro.adapter.ClientSelectAdapter→com.paparazziapps.pretamistapp.presentation.registro.adapter.ClientSelectAdapter.ClientSelectViewHolder
- Direction
- presentation.registro.adapter uses presentation.registro.adapter.ClientSelectAdapter, so a change to presentation.registro.adapter.ClientSelectAdapter can break presentation.registro.adapter, while a change to presentation.registro.adapter can't break presentation.registro.adapter.ClientSelectAdapter.
- Position
- Below the diagonal: presentation.registro.adapter uses a module listed above it, which is the healthy direction.
30→2 data.remote uses data.network✕
- Connections
- 12 pairs of types, where a type in data.remote uses a type in data.network.
- The types involved
com.paparazziapps.pretamistapp.data.remote.RemoteBranchDataSource→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.remote.RemoteBranchDataSourceImpl→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.remote.RemoteDetailLoanDataSource→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.remote.RemoteDetailLoanDataSourceImpl→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.remote.RemoteEmailDataSource→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.remote.RemoteEmailDataSourceImpl→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.remote.RemoteLoanDataSource→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.remote.RemoteLoanDataSourceImpl→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.remote.RemoteLoginDataSource→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.remote.RemoteLoginDataSourceImpl→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.remote.RemoteUserDataSource→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.remote.RemoteUserDataSourceImpl→com.paparazziapps.pretamistapp.data.network.PAResult
- Direction
- data.remote uses data.network, so a change to data.network can break data.remote, while a change to data.remote can't break data.network.
- Position
- Below the diagonal: data.remote uses a module listed above it, which is the healthy direction.
30→3 data.remote uses domain✕
- Connections
- 10 pairs of types, where a type in data.remote uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.data.remote.RemoteDetailLoanDataSource→com.paparazziapps.pretamistapp.domain.DetailLoanDomaincom.paparazziapps.pretamistapp.data.remote.RemoteDetailLoanDataSource→com.paparazziapps.pretamistapp.domain.DetailLoanFormcom.paparazziapps.pretamistapp.data.remote.RemoteDetailLoanDataSourceImpl→com.paparazziapps.pretamistapp.domain.DetailLoanDomaincom.paparazziapps.pretamistapp.data.remote.RemoteDetailLoanDataSourceImpl→com.paparazziapps.pretamistapp.domain.DetailLoanFormcom.paparazziapps.pretamistapp.data.remote.RemoteLoanDataSource→com.paparazziapps.pretamistapp.domain.LoanDomaincom.paparazziapps.pretamistapp.data.remote.RemoteLoanDataSourceImpl→com.paparazziapps.pretamistapp.domain.LoanDomaincom.paparazziapps.pretamistapp.data.remote.RemoteLoginDataSource→com.paparazziapps.pretamistapp.domain.UserFormcom.paparazziapps.pretamistapp.data.remote.RemoteLoginDataSourceImpl→com.paparazziapps.pretamistapp.domain.UserFormcom.paparazziapps.pretamistapp.data.remote.RemoteUserDataSource→com.paparazziapps.pretamistapp.domain.UserFormcom.paparazziapps.pretamistapp.data.remote.RemoteUserDataSourceImpl→com.paparazziapps.pretamistapp.domain.UserForm
- Direction
- data.remote uses domain, so a change to domain can break data.remote, while a change to data.remote can't break domain.
- Position
- Below the diagonal: data.remote uses a module listed above it, which is the healthy direction.
30→5 data.remote uses domain.notification✕
- Connections
- 4 pairs of types, where a type in data.remote uses a type in domain.notification.
- The types involved
com.paparazziapps.pretamistapp.data.remote.RemoteEmailDataSource→com.paparazziapps.pretamistapp.domain.notification.EmailReceiptResponsecom.paparazziapps.pretamistapp.data.remote.RemoteEmailDataSource→com.paparazziapps.pretamistapp.domain.notification.EmailRequestcom.paparazziapps.pretamistapp.data.remote.RemoteEmailDataSourceImpl→com.paparazziapps.pretamistapp.domain.notification.EmailReceiptResponsecom.paparazziapps.pretamistapp.data.remote.RemoteEmailDataSourceImpl→com.paparazziapps.pretamistapp.domain.notification.EmailRequest
- Direction
- data.remote uses domain.notification, so a change to domain.notification can break data.remote, while a change to data.remote can't break domain.notification.
- Position
- Below the diagonal: data.remote uses a module listed above it, which is the healthy direction.
30→10 data.remote uses data.providers✕
- Connections
- 7 pairs of types, where a type in data.remote uses a type in data.providers.
- The types involved
com.paparazziapps.pretamistapp.data.remote.RemoteAnalyticsDataSourceImpl→com.paparazziapps.pretamistapp.data.providers.FirebaseProvidercom.paparazziapps.pretamistapp.data.remote.RemoteBranchDataSourceImpl→com.paparazziapps.pretamistapp.data.providers.BranchesProvidercom.paparazziapps.pretamistapp.data.remote.RemoteDetailLoanDataSourceImpl→com.paparazziapps.pretamistapp.data.providers.DetailLoanProvidercom.paparazziapps.pretamistapp.data.remote.RemoteLoanDataSourceImpl→com.paparazziapps.pretamistapp.data.providers.LoanProvidercom.paparazziapps.pretamistapp.data.remote.RemoteLoginDataSourceImpl→com.paparazziapps.pretamistapp.data.providers.LoginProvidercom.paparazziapps.pretamistapp.data.remote.RemoteLoginDataSourceImpl→com.paparazziapps.pretamistapp.data.providers.RegisterProvidercom.paparazziapps.pretamistapp.data.remote.RemoteUserDataSourceImpl→com.paparazziapps.pretamistapp.data.providers.UserProvider
- Direction
- data.remote uses data.providers, so a change to data.providers can break data.remote, while a change to data.remote can't break data.providers.
- Position
- Below the diagonal: data.remote uses a module listed above it, which is the healthy direction.
30→23 data.remote uses data.services✕
- Connections
- 1 pair of types, where a type in data.remote uses a type in data.services.
- The types involved
com.paparazziapps.pretamistapp.data.remote.RemoteEmailDataSourceImpl→com.paparazziapps.pretamistapp.data.services.ServiceProvider
- Direction
- data.remote uses data.services, so a change to data.services can break data.remote, while a change to data.remote can't break data.services.
- Position
- Below the diagonal: data.remote uses a module listed above it, which is the healthy direction.
31→1 presentation.dashboard.views uses application✕
- Connections
- 1 pair of types, where a type in presentation.dashboard.views uses a type in application.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.views.LoanListHandler→com.paparazziapps.pretamistapp.application.MyPreferences
- Direction
- presentation.dashboard.views uses application, so a change to application can break presentation.dashboard.views, while a change to presentation.dashboard.views can't break application.
- Position
- Below the diagonal: presentation.dashboard.views uses a module listed above it, which is the healthy direction.
31→3 presentation.dashboard.views uses domain✕
- Connections
- 2 pairs of types, where a type in presentation.dashboard.views uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.views.HomeFragment→com.paparazziapps.pretamistapp.domain.LoanDomaincom.paparazziapps.pretamistapp.presentation.dashboard.views.LoanListHandler→com.paparazziapps.pretamistapp.domain.LoanDomain
- Direction
- presentation.dashboard.views uses domain, so a change to domain can break presentation.dashboard.views, while a change to presentation.dashboard.views can't break domain.
- Position
- Below the diagonal: presentation.dashboard.views uses a module listed above it, which is the healthy direction.
31→8 presentation.dashboard.views uses presentation.dashboard.viewmodels.ViewModelDetailReceipt✕
- Connections
- 1 pair of types, where a type in presentation.dashboard.views uses a type in presentation.dashboard.viewmodels.ViewModelDetailReceipt.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.views.DetailReceiptFragment→com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState
- Direction
- presentation.dashboard.views uses presentation.dashboard.viewmodels.ViewModelDetailReceipt, so a change to presentation.dashboard.viewmodels.ViewModelDetailReceipt can break presentation.dashboard.views, while a change to presentation.dashboard.views can't break presentation.dashboard.viewmodels.ViewModelDetailReceipt.
- Position
- Below the diagonal: presentation.dashboard.views uses a module listed above it, which is the healthy direction.
31→15 presentation.dashboard.views uses presentation.dashboard.interfaces✕
- Connections
- 1 pair of types, where a type in presentation.dashboard.views uses a type in presentation.dashboard.interfaces.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.views.HomeFragment→com.paparazziapps.pretamistapp.presentation.dashboard.interfaces.SetOnClickedLoan
- Direction
- presentation.dashboard.views uses presentation.dashboard.interfaces, so a change to presentation.dashboard.interfaces can break presentation.dashboard.views, while a change to presentation.dashboard.views can't break presentation.dashboard.interfaces.
- Position
- Below the diagonal: presentation.dashboard.views uses a module listed above it, which is the healthy direction.
31→16 presentation.dashboard.views uses presentation.dashboard.viewmodels.ViewModelDashboard✕
- Connections
- 1 pair of types, where a type in presentation.dashboard.views uses a type in presentation.dashboard.viewmodels.ViewModelDashboard.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.views.HomeFragment→com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState
- Direction
- presentation.dashboard.views uses presentation.dashboard.viewmodels.ViewModelDashboard, so a change to presentation.dashboard.viewmodels.ViewModelDashboard can break presentation.dashboard.views, while a change to presentation.dashboard.views can't break presentation.dashboard.viewmodels.ViewModelDashboard.
- Position
- Below the diagonal: presentation.dashboard.views uses a module listed above it, which is the healthy direction.
31→25 presentation.dashboard.views uses presentation.dashboard.adapters✕
- Connections
- 1 pair of types, where a type in presentation.dashboard.views uses a type in presentation.dashboard.adapters.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.views.HomeFragment→com.paparazziapps.pretamistapp.presentation.dashboard.adapters.LoanAdapter
- Direction
- presentation.dashboard.views uses presentation.dashboard.adapters, so a change to presentation.dashboard.adapters can break presentation.dashboard.views, while a change to presentation.dashboard.views can't break presentation.dashboard.adapters.
- Position
- Below the diagonal: presentation.dashboard.views uses a module listed above it, which is the healthy direction.
32→2 data.repository uses data.network✕
- Connections
- 6 pairs of types, where a type in data.repository uses a type in data.network.
- The types involved
com.paparazziapps.pretamistapp.data.repository.PAClientsRepository→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.repository.PAClientsRepositoryImpl→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.repository.PAEmailRepository→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.repository.PAEmailRepositoryImpl→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.repository.PARepository→com.paparazziapps.pretamistapp.data.network.PAResultcom.paparazziapps.pretamistapp.data.repository.PARepositoryImpl→com.paparazziapps.pretamistapp.data.network.PAResult
- Direction
- data.repository uses data.network, so a change to data.network can break data.repository, while a change to data.repository can't break data.network.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
32→3 data.repository uses domain✕
- Connections
- 8 pairs of types, where a type in data.repository uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.data.repository.PARepository→com.paparazziapps.pretamistapp.domain.DetailLoanDomaincom.paparazziapps.pretamistapp.data.repository.PARepository→com.paparazziapps.pretamistapp.domain.DetailLoanFormcom.paparazziapps.pretamistapp.data.repository.PARepository→com.paparazziapps.pretamistapp.domain.LoanDomaincom.paparazziapps.pretamistapp.data.repository.PARepository→com.paparazziapps.pretamistapp.domain.UserFormcom.paparazziapps.pretamistapp.data.repository.PARepositoryImpl→com.paparazziapps.pretamistapp.domain.DetailLoanDomaincom.paparazziapps.pretamistapp.data.repository.PARepositoryImpl→com.paparazziapps.pretamistapp.domain.DetailLoanFormcom.paparazziapps.pretamistapp.data.repository.PARepositoryImpl→com.paparazziapps.pretamistapp.domain.LoanDomaincom.paparazziapps.pretamistapp.data.repository.PARepositoryImpl→com.paparazziapps.pretamistapp.domain.UserForm
- Direction
- data.repository uses domain, so a change to domain can break data.repository, while a change to data.repository can't break domain.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
32→4 data.repository uses domain.clients✕
- Connections
- 2 pairs of types, where a type in data.repository uses a type in domain.clients.
- The types involved
com.paparazziapps.pretamistapp.data.repository.PAClientsRepository→com.paparazziapps.pretamistapp.domain.clients.ClientDomaincom.paparazziapps.pretamistapp.data.repository.PAClientsRepositoryImpl→com.paparazziapps.pretamistapp.domain.clients.ClientDomain
- Direction
- data.repository uses domain.clients, so a change to domain.clients can break data.repository, while a change to data.repository can't break domain.clients.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
32→5 data.repository uses domain.notification✕
- Connections
- 2 pairs of types, where a type in data.repository uses a type in domain.notification.
- The types involved
com.paparazziapps.pretamistapp.data.repository.PAEmailRepository→com.paparazziapps.pretamistapp.domain.notification.EmailReceiptResponsecom.paparazziapps.pretamistapp.data.repository.PAEmailRepositoryImpl→com.paparazziapps.pretamistapp.domain.notification.EmailReceiptResponse
- Direction
- data.repository uses domain.notification, so a change to domain.notification can break data.repository, while a change to data.repository can't break domain.notification.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
32→11 data.repository uses data.utils✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in data.utils.
- The types involved
com.paparazziapps.pretamistapp.data.repository.PAEmailRepositoryImpl→com.paparazziapps.pretamistapp.data.utils.ReceiptHtmlTemplate
- Direction
- data.repository uses data.utils, so a change to data.utils can break data.repository, while a change to data.repository can't break data.utils.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
32→22 data.repository uses data.remote.clients✕
- Connections
- 1 pair of types, where a type in data.repository uses a type in data.remote.clients.
- The types involved
com.paparazziapps.pretamistapp.data.repository.PAClientsRepositoryImpl→com.paparazziapps.pretamistapp.data.remote.clients.RemoteClientsDataSource
- Direction
- data.repository uses data.remote.clients, so a change to data.remote.clients can break data.repository, while a change to data.repository can't break data.remote.clients.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
32→30 data.repository uses data.remote✕
- Connections
- 7 pairs of types, where a type in data.repository uses a type in data.remote.
- The types involved
com.paparazziapps.pretamistapp.data.repository.PAAnalyticsRepositoryImpl→com.paparazziapps.pretamistapp.data.remote.RemoteAnalyticsDataSourcecom.paparazziapps.pretamistapp.data.repository.PAEmailRepositoryImpl→com.paparazziapps.pretamistapp.data.remote.RemoteEmailDataSourcecom.paparazziapps.pretamistapp.data.repository.PARepositoryImpl→com.paparazziapps.pretamistapp.data.remote.RemoteBranchDataSourcecom.paparazziapps.pretamistapp.data.repository.PARepositoryImpl→com.paparazziapps.pretamistapp.data.remote.RemoteDetailLoanDataSourcecom.paparazziapps.pretamistapp.data.repository.PARepositoryImpl→com.paparazziapps.pretamistapp.data.remote.RemoteLoanDataSourcecom.paparazziapps.pretamistapp.data.repository.PARepositoryImpl→com.paparazziapps.pretamistapp.data.remote.RemoteLoginDataSourcecom.paparazziapps.pretamistapp.data.repository.PARepositoryImpl→com.paparazziapps.pretamistapp.data.remote.RemoteUserDataSource
- Direction
- data.repository uses data.remote, so a change to data.remote can break data.repository, while a change to data.repository can't break data.remote.
- Position
- Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
33→4 presentation.clients uses domain.clients✕
- Connections
- 1 pair of types, where a type in presentation.clients uses a type in domain.clients.
- The types involved
com.paparazziapps.pretamistapp.presentation.clients.ClientsParentFragment→com.paparazziapps.pretamistapp.domain.clients.ClientDomain
- Direction
- presentation.clients uses domain.clients, so a change to domain.clients can break presentation.clients, while a change to presentation.clients can't break domain.clients.
- Position
- Below the diagonal: presentation.clients uses a module listed above it, which is the healthy direction.
33→7 presentation.clients uses presentation.clients.ClientsAddViewModel✕
- Connections
- 1 pair of types, where a type in presentation.clients uses a type in presentation.clients.ClientsAddViewModel.
- The types involved
com.paparazziapps.pretamistapp.presentation.clients.ClientsAddViewModel→com.paparazziapps.pretamistapp.presentation.clients.ClientsAddViewModel.ClientsAddIntent
- Direction
- presentation.clients uses presentation.clients.ClientsAddViewModel, so a change to presentation.clients.ClientsAddViewModel can break presentation.clients, while a change to presentation.clients can't break presentation.clients.ClientsAddViewModel.
- Position
- Below the diagonal: presentation.clients uses a module listed above it, which is the healthy direction.
33→13 presentation.clients uses helper.base✕
- Connections
- 2 pairs of types, where a type in presentation.clients uses a type in helper.base.
- The types involved
com.paparazziapps.pretamistapp.presentation.clients.ClientsAddViewModel→com.paparazziapps.pretamistapp.helper.base.BaseViewModelcom.paparazziapps.pretamistapp.presentation.clients.ClientsParentViewModel→com.paparazziapps.pretamistapp.helper.base.BaseViewModel
- Direction
- presentation.clients uses helper.base, so a change to helper.base can break presentation.clients, while a change to presentation.clients can't break helper.base.
- Position
- Below the diagonal: presentation.clients uses a module listed above it, which is the healthy direction.
33→24 presentation.clients uses presentation.clients.adater✕
- Connections
- 2 pairs of types, where a type in presentation.clients uses a type in presentation.clients.adater.
- The types involved
com.paparazziapps.pretamistapp.presentation.clients.ClientsParentFragment→com.paparazziapps.pretamistapp.presentation.clients.adater.ClientAdaptercom.paparazziapps.pretamistapp.presentation.clients.ClientsParentFragment→com.paparazziapps.pretamistapp.presentation.clients.adater.SetOnClickListenerClient
- Direction
- presentation.clients uses presentation.clients.adater, so a change to presentation.clients.adater can break presentation.clients, while a change to presentation.clients can't break presentation.clients.adater.
- Position
- Below the diagonal: presentation.clients uses a module listed above it, which is the healthy direction.
33→32 presentation.clients uses data.repository✕
- Connections
- 2 pairs of types, where a type in presentation.clients uses a type in data.repository.
- The types involved
com.paparazziapps.pretamistapp.presentation.clients.ClientsAddViewModel→com.paparazziapps.pretamistapp.data.repository.PAClientsRepositorycom.paparazziapps.pretamistapp.presentation.clients.ClientsParentViewModel→com.paparazziapps.pretamistapp.data.repository.PAClientsRepository
- Direction
- presentation.clients uses data.repository, so a change to data.repository can break presentation.clients, while a change to presentation.clients can't break data.repository.
- Position
- Below the diagonal: presentation.clients uses a module listed above it, which is the healthy direction.
34→1 presentation.dashboard.viewmodels uses application✕
- Connections
- 1 pair of types, where a type in presentation.dashboard.viewmodels uses a type in application.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard→com.paparazziapps.pretamistapp.application.MyPreferences
- Direction
- presentation.dashboard.viewmodels uses application, so a change to application can break presentation.dashboard.viewmodels, while a change to presentation.dashboard.viewmodels can't break application.
- Position
- Below the diagonal: presentation.dashboard.viewmodels uses a module listed above it, which is the healthy direction.
34→3 presentation.dashboard.viewmodels uses domain✕
- Connections
- 3 pairs of types, where a type in presentation.dashboard.viewmodels uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard→com.paparazziapps.pretamistapp.domain.InformationReceiptDomaincom.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard→com.paparazziapps.pretamistapp.domain.LoanDomaincom.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDetailReceipt→com.paparazziapps.pretamistapp.domain.InformationReceiptDomain
- Direction
- presentation.dashboard.viewmodels uses domain, so a change to domain can break presentation.dashboard.viewmodels, while a change to presentation.dashboard.viewmodels can't break domain.
- Position
- Below the diagonal: presentation.dashboard.viewmodels uses a module listed above it, which is the healthy direction.
34→8 presentation.dashboard.viewmodels uses presentation.dashboard.viewmodels.ViewModelDetailReceipt✕
- Connections
- 1 pair of types, where a type in presentation.dashboard.viewmodels uses a type in presentation.dashboard.viewmodels.ViewModelDetailReceipt.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDetailReceipt→com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDetailReceipt.DetailReceiptState
- Direction
- presentation.dashboard.viewmodels uses presentation.dashboard.viewmodels.ViewModelDetailReceipt, so a change to presentation.dashboard.viewmodels.ViewModelDetailReceipt can break presentation.dashboard.viewmodels, while a change to presentation.dashboard.viewmodels can't break presentation.dashboard.viewmodels.ViewModelDetailReceipt.
- Position
- Below the diagonal: presentation.dashboard.viewmodels uses a module listed above it, which is the healthy direction.
34→16 presentation.dashboard.viewmodels uses presentation.dashboard.viewmodels.ViewModelDashboard✕
- Connections
- 2 pairs of types, where a type in presentation.dashboard.viewmodels uses a type in presentation.dashboard.viewmodels.ViewModelDashboard.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard→com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardIntentcom.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard→com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard.DashboardState
- Direction
- presentation.dashboard.viewmodels uses presentation.dashboard.viewmodels.ViewModelDashboard, so a change to presentation.dashboard.viewmodels.ViewModelDashboard can break presentation.dashboard.viewmodels, while a change to presentation.dashboard.viewmodels can't break presentation.dashboard.viewmodels.ViewModelDashboard.
- Position
- Below the diagonal: presentation.dashboard.viewmodels uses a module listed above it, which is the healthy direction.
34→32 presentation.dashboard.viewmodels uses data.repository✕
- Connections
- 4 pairs of types, where a type in presentation.dashboard.viewmodels uses a type in data.repository.
- The types involved
com.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard→com.paparazziapps.pretamistapp.data.repository.PAAnalyticsRepositorycom.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard→com.paparazziapps.pretamistapp.data.repository.PAEmailRepositorycom.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDashboard→com.paparazziapps.pretamistapp.data.repository.PARepositorycom.paparazziapps.pretamistapp.presentation.dashboard.viewmodels.ViewModelDetailReceipt→com.paparazziapps.pretamistapp.data.repository.PAAnalyticsRepository
- Direction
- presentation.dashboard.viewmodels uses data.repository, so a change to data.repository can break presentation.dashboard.viewmodels, while a change to presentation.dashboard.viewmodels can't break data.repository.
- Position
- Below the diagonal: presentation.dashboard.viewmodels uses a module listed above it, which is the healthy direction.
35→1 presentation.login.viewmodels uses application✕
- Connections
- 2 pairs of types, where a type in presentation.login.viewmodels uses a type in application.
- The types involved
com.paparazziapps.pretamistapp.presentation.login.viewmodels.ViewModelLogin→com.paparazziapps.pretamistapp.application.MyPreferencescom.paparazziapps.pretamistapp.presentation.login.viewmodels.ViewModelRegisterUser→com.paparazziapps.pretamistapp.application.MyPreferences
- Direction
- presentation.login.viewmodels uses application, so a change to application can break presentation.login.viewmodels, while a change to presentation.login.viewmodels can't break application.
- Position
- Below the diagonal: presentation.login.viewmodels uses a module listed above it, which is the healthy direction.
35→3 presentation.login.viewmodels uses domain✕
- Connections
- 2 pairs of types, where a type in presentation.login.viewmodels uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.login.viewmodels.ViewModelBranches→com.paparazziapps.pretamistapp.domain.Sucursalescom.paparazziapps.pretamistapp.presentation.login.viewmodels.ViewModelRegisterUser→com.paparazziapps.pretamistapp.domain.UserForm
- Direction
- presentation.login.viewmodels uses domain, so a change to domain can break presentation.login.viewmodels, while a change to presentation.login.viewmodels can't break domain.
- Position
- Below the diagonal: presentation.login.viewmodels uses a module listed above it, which is the healthy direction.
35→32 presentation.login.viewmodels uses data.repository✕
- Connections
- 3 pairs of types, where a type in presentation.login.viewmodels uses a type in data.repository.
- The types involved
com.paparazziapps.pretamistapp.presentation.login.viewmodels.ViewModelBranches→com.paparazziapps.pretamistapp.data.repository.PARepositorycom.paparazziapps.pretamistapp.presentation.login.viewmodels.ViewModelLogin→com.paparazziapps.pretamistapp.data.repository.PARepositorycom.paparazziapps.pretamistapp.presentation.login.viewmodels.ViewModelRegisterUser→com.paparazziapps.pretamistapp.data.repository.PARepository
- Direction
- presentation.login.viewmodels uses data.repository, so a change to data.repository can break presentation.login.viewmodels, while a change to presentation.login.viewmodels can't break data.repository.
- Position
- Below the diagonal: presentation.login.viewmodels uses a module listed above it, which is the healthy direction.
36→1 presentation.principal.viewmodels uses application✕
- Connections
- 1 pair of types, where a type in presentation.principal.viewmodels uses a type in application.
- The types involved
com.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal→com.paparazziapps.pretamistapp.application.MyPreferences
- Direction
- presentation.principal.viewmodels uses application, so a change to application can break presentation.principal.viewmodels, while a change to presentation.principal.viewmodels can't break application.
- Position
- Below the diagonal: presentation.principal.viewmodels uses a module listed above it, which is the healthy direction.
36→3 presentation.principal.viewmodels uses domain✕
- Connections
- 1 pair of types, where a type in presentation.principal.viewmodels uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal→com.paparazziapps.pretamistapp.domain.Sucursales
- Direction
- presentation.principal.viewmodels uses domain, so a change to domain can break presentation.principal.viewmodels, while a change to presentation.principal.viewmodels can't break domain.
- Position
- Below the diagonal: presentation.principal.viewmodels uses a module listed above it, which is the healthy direction.
36→9 presentation.principal.viewmodels uses presentation.principal.viewmodels.ViewModelPrincipal✕
- Connections
- 1 pair of types, where a type in presentation.principal.viewmodels uses a type in presentation.principal.viewmodels.ViewModelPrincipal.
- The types involved
com.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal→com.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal.UIStatePrincipal
- Direction
- presentation.principal.viewmodels uses presentation.principal.viewmodels.ViewModelPrincipal, so a change to presentation.principal.viewmodels.ViewModelPrincipal can break presentation.principal.viewmodels, while a change to presentation.principal.viewmodels can't break presentation.principal.viewmodels.ViewModelPrincipal.
- Position
- Below the diagonal: presentation.principal.viewmodels uses a module listed above it, which is the healthy direction.
36→32 presentation.principal.viewmodels uses data.repository✕
- Connections
- 2 pairs of types, where a type in presentation.principal.viewmodels uses a type in data.repository.
- The types involved
com.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal→com.paparazziapps.pretamistapp.data.repository.PAAnalyticsRepositorycom.paparazziapps.pretamistapp.presentation.principal.viewmodels.ViewModelPrincipal→com.paparazziapps.pretamistapp.data.repository.PARepository
- Direction
- presentation.principal.viewmodels uses data.repository, so a change to data.repository can break presentation.principal.viewmodels, while a change to presentation.principal.viewmodels can't break data.repository.
- Position
- Below the diagonal: presentation.principal.viewmodels uses a module listed above it, which is the healthy direction.
37→3 presentation.registro.viewmodels uses domain✕
- Connections
- 1 pair of types, where a type in presentation.registro.viewmodels uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.registro.viewmodels.ViewModelRegister→com.paparazziapps.pretamistapp.domain.LoanDomain
- Direction
- presentation.registro.viewmodels uses domain, so a change to domain can break presentation.registro.viewmodels, while a change to presentation.registro.viewmodels can't break domain.
- Position
- Below the diagonal: presentation.registro.viewmodels uses a module listed above it, which is the healthy direction.
37→4 presentation.registro.viewmodels uses domain.clients✕
- Connections
- 1 pair of types, where a type in presentation.registro.viewmodels uses a type in domain.clients.
- The types involved
com.paparazziapps.pretamistapp.presentation.registro.viewmodels.ViewModelRegister→com.paparazziapps.pretamistapp.domain.clients.ClientDomainSelect
- Direction
- presentation.registro.viewmodels uses domain.clients, so a change to domain.clients can break presentation.registro.viewmodels, while a change to presentation.registro.viewmodels can't break domain.clients.
- Position
- Below the diagonal: presentation.registro.viewmodels uses a module listed above it, which is the healthy direction.
37→32 presentation.registro.viewmodels uses data.repository✕
- Connections
- 1 pair of types, where a type in presentation.registro.viewmodels uses a type in data.repository.
- The types involved
com.paparazziapps.pretamistapp.presentation.registro.viewmodels.ViewModelRegister→com.paparazziapps.pretamistapp.data.repository.PARepository
- Direction
- presentation.registro.viewmodels uses data.repository, so a change to data.repository can break presentation.registro.viewmodels, while a change to presentation.registro.viewmodels can't break data.repository.
- Position
- Below the diagonal: presentation.registro.viewmodels uses a module listed above it, which is the healthy direction.
38→3 presentation.login.views uses domain✕
- Connections
- 2 pairs of types, where a type in presentation.login.views uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.login.views.RegisterActivity→com.paparazziapps.pretamistapp.domain.Sucursalescom.paparazziapps.pretamistapp.presentation.login.views.RegisterActivity→com.paparazziapps.pretamistapp.domain.UserForm
- Direction
- presentation.login.views uses domain, so a change to domain can break presentation.login.views, while a change to presentation.login.views can't break domain.
- Position
- Below the diagonal: presentation.login.views uses a module listed above it, which is the healthy direction.
38→35 presentation.login.views uses presentation.login.viewmodels✕
- Connections
- 3 pairs of types, where a type in presentation.login.views uses a type in presentation.login.viewmodels.
- The types involved
com.paparazziapps.pretamistapp.presentation.login.views.LoginActivity→com.paparazziapps.pretamistapp.presentation.login.viewmodels.ViewModelLogincom.paparazziapps.pretamistapp.presentation.login.views.RegisterActivity→com.paparazziapps.pretamistapp.presentation.login.viewmodels.ViewModelBranchescom.paparazziapps.pretamistapp.presentation.login.views.RegisterActivity→com.paparazziapps.pretamistapp.presentation.login.viewmodels.ViewModelRegisterUser
- Direction
- presentation.login.views uses presentation.login.viewmodels, so a change to presentation.login.viewmodels can break presentation.login.views, while a change to presentation.login.views can't break presentation.login.viewmodels.
- Position
- Below the diagonal: presentation.login.views uses a module listed above it, which is the healthy direction.
39→1 presentation.registro.views uses application✕
- Connections
- 1 pair of types, where a type in presentation.registro.views uses a type in application.
- The types involved
com.paparazziapps.pretamistapp.presentation.registro.views.RegistrarLoanFragment→com.paparazziapps.pretamistapp.application.MyPreferences
- Direction
- presentation.registro.views uses application, so a change to application can break presentation.registro.views, while a change to presentation.registro.views can't break application.
- Position
- Below the diagonal: presentation.registro.views uses a module listed above it, which is the healthy direction.
39→3 presentation.registro.views uses domain✕
- Connections
- 3 pairs of types, where a type in presentation.registro.views uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.registro.views.RegistrarFragment→com.paparazziapps.pretamistapp.domain.LoanDomaincom.paparazziapps.pretamistapp.presentation.registro.views.RegistrarFragment→com.paparazziapps.pretamistapp.domain.QuotaDomaincom.paparazziapps.pretamistapp.presentation.registro.views.RegistrarLoanFragment→com.paparazziapps.pretamistapp.domain.Sucursales
- Direction
- presentation.registro.views uses domain, so a change to domain can break presentation.registro.views, while a change to presentation.registro.views can't break domain.
- Position
- Below the diagonal: presentation.registro.views uses a module listed above it, which is the healthy direction.
39→4 presentation.registro.views uses domain.clients✕
- Connections
- 2 pairs of types, where a type in presentation.registro.views uses a type in domain.clients.
- The types involved
com.paparazziapps.pretamistapp.presentation.registro.views.SelectUserFragment→com.paparazziapps.pretamistapp.domain.clients.ClientDomainSelectcom.paparazziapps.pretamistapp.presentation.registro.views.SelectUserViewModel→com.paparazziapps.pretamistapp.domain.clients.ClientDomainSelect
- Direction
- presentation.registro.views uses domain.clients, so a change to domain.clients can break presentation.registro.views, while a change to presentation.registro.views can't break domain.clients.
- Position
- Below the diagonal: presentation.registro.views uses a module listed above it, which is the healthy direction.
39→13 presentation.registro.views uses helper.base✕
- Connections
- 1 pair of types, where a type in presentation.registro.views uses a type in helper.base.
- The types involved
com.paparazziapps.pretamistapp.presentation.registro.views.SelectUserViewModel→com.paparazziapps.pretamistapp.helper.base.BaseViewModel
- Direction
- presentation.registro.views uses helper.base, so a change to helper.base can break presentation.registro.views, while a change to presentation.registro.views can't break helper.base.
- Position
- Below the diagonal: presentation.registro.views uses a module listed above it, which is the healthy direction.
39→29 presentation.registro.views uses presentation.registro.adapter✕
- Connections
- 2 pairs of types, where a type in presentation.registro.views uses a type in presentation.registro.adapter.
- The types involved
com.paparazziapps.pretamistapp.presentation.registro.views.SelectUserFragment→com.paparazziapps.pretamistapp.presentation.registro.adapter.ClientSelectAdaptercom.paparazziapps.pretamistapp.presentation.registro.views.SelectUserFragment→com.paparazziapps.pretamistapp.presentation.registro.adapter.OnClientSelectListener
- Direction
- presentation.registro.views uses presentation.registro.adapter, so a change to presentation.registro.adapter can break presentation.registro.views, while a change to presentation.registro.views can't break presentation.registro.adapter.
- Position
- Below the diagonal: presentation.registro.views uses a module listed above it, which is the healthy direction.
39→32 presentation.registro.views uses data.repository✕
- Connections
- 1 pair of types, where a type in presentation.registro.views uses a type in data.repository.
- The types involved
com.paparazziapps.pretamistapp.presentation.registro.views.SelectUserViewModel→com.paparazziapps.pretamistapp.data.repository.PAClientsRepository
- Direction
- presentation.registro.views uses data.repository, so a change to data.repository can break presentation.registro.views, while a change to presentation.registro.views can't break data.repository.
- Position
- Below the diagonal: presentation.registro.views uses a module listed above it, which is the healthy direction.
39→35 presentation.registro.views uses presentation.login.viewmodels✕
- Connections
- 1 pair of types, where a type in presentation.registro.views uses a type in presentation.login.viewmodels.
- The types involved
com.paparazziapps.pretamistapp.presentation.registro.views.RegistrarLoanFragment→com.paparazziapps.pretamistapp.presentation.login.viewmodels.ViewModelBranches
- Direction
- presentation.registro.views uses presentation.login.viewmodels, so a change to presentation.login.viewmodels can break presentation.registro.views, while a change to presentation.registro.views can't break presentation.login.viewmodels.
- Position
- Below the diagonal: presentation.registro.views uses a module listed above it, which is the healthy direction.
39→37 presentation.registro.views uses presentation.registro.viewmodels✕
- Connections
- 1 pair of types, where a type in presentation.registro.views uses a type in presentation.registro.viewmodels.
- The types involved
com.paparazziapps.pretamistapp.presentation.registro.views.RegistrarLoanFragment→com.paparazziapps.pretamistapp.presentation.registro.viewmodels.RegisterState
- Direction
- presentation.registro.views uses presentation.registro.viewmodels, so a change to presentation.registro.viewmodels can break presentation.registro.views, while a change to presentation.registro.views can't break presentation.registro.viewmodels.
- Position
- Below the diagonal: presentation.registro.views uses a module listed above it, which is the healthy direction.
40→1 presentation.tesoreria.views uses application✕
- Connections
- 1 pair of types, where a type in presentation.tesoreria.views uses a type in application.
- The types involved
com.paparazziapps.pretamistapp.presentation.tesoreria.views.FinanzasFragment→com.paparazziapps.pretamistapp.application.MyPreferences
- Direction
- presentation.tesoreria.views uses application, so a change to application can break presentation.tesoreria.views, while a change to presentation.tesoreria.views can't break application.
- Position
- Below the diagonal: presentation.tesoreria.views uses a module listed above it, which is the healthy direction.
40→3 presentation.tesoreria.views uses domain✕
- Connections
- 1 pair of types, where a type in presentation.tesoreria.views uses a type in domain.
- The types involved
com.paparazziapps.pretamistapp.presentation.tesoreria.views.FinanzasFragment→com.paparazziapps.pretamistapp.domain.Sucursales
- Direction
- presentation.tesoreria.views uses domain, so a change to domain can break presentation.tesoreria.views, while a change to presentation.tesoreria.views can't break domain.
- Position
- Below the diagonal: presentation.tesoreria.views uses a module listed above it, which is the healthy direction.
40→21 presentation.tesoreria.views uses presentation.tesoreria.adapter✕
- Connections
- 1 pair of types, where a type in presentation.tesoreria.views uses a type in presentation.tesoreria.adapter.
- The types involved
com.paparazziapps.pretamistapp.presentation.tesoreria.views.FinanzasFragment→com.paparazziapps.pretamistapp.presentation.tesoreria.adapter.LoanDetailAdapter
- Direction
- presentation.tesoreria.views uses presentation.tesoreria.adapter, so a change to presentation.tesoreria.adapter can break presentation.tesoreria.views, while a change to presentation.tesoreria.views can't break presentation.tesoreria.adapter.
- Position
- Below the diagonal: presentation.tesoreria.views uses a module listed above it, which is the healthy direction.
40→35 presentation.tesoreria.views uses presentation.login.viewmodels✕
- Connections
- 1 pair of types, where a type in presentation.tesoreria.views uses a type in presentation.login.viewmodels.
- The types involved
com.paparazziapps.pretamistapp.presentation.tesoreria.views.FinanzasFragment→com.paparazziapps.pretamistapp.presentation.login.viewmodels.ViewModelBranches
- Direction
- presentation.tesoreria.views uses presentation.login.viewmodels, so a change to presentation.login.viewmodels can break presentation.tesoreria.views, while a change to presentation.tesoreria.views can't break presentation.login.viewmodels.
- Position
- Below the diagonal: presentation.tesoreria.views uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 11 | High / Critical |
| A07:2025 — Authentication Failures | 3 | High / Critical |
| A01:2025 — Broken Access Control | 1 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle; Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle. | +7.9 pts | Low | ADR Quality |
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +7.6 pts | Low | REDACTED Scanning |
| 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. | +7.4 pts | Medium | Architecture documentation |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +4.3 pts | Medium | Security & performance tooling |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.1 pts | Medium | Release Hygiene |
| 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. | +1.9 pts | Medium | Documentation (README) |
| Swallowed exception (caught, then discarded) | +1.8 pts | Medium | Exception handling |
| Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. | +0.2 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.8 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.3 | Mixed | Data Compliance (PII/GDPR): Medium: REDACTED |
| app/src/main/java/com/paparazziapps/pretamistapp/presentation/registro/views/RegistrarFragment.kt | 5.7 | Mixed | Cyclomatic Complexity: RegistrarFragment.validateAll (cyclomatic 29) |
| app/src/main/java/com/paparazziapps/pretamistapp/presentation/dashboard/adapters/LoanAdapter.kt | 5.7 | Mixed | Cyclomatic Complexity: ViewHolder.updateDelayForLoanType (cyclomatic 17) |
| app/src/main/java/com/paparazziapps/pretamistapp/presentation/clients/ClientsParentFragment.kt | 7.4 | Mixed | Code Duplication: Edited copy of a member (24 corresponding lines) |
| app/src/main/java/com/paparazziapps/pretamistapp/presentation/clients/ClientsParentViewModel.kt | 7.4 | Mixed | Code Duplication: Edited copies of one member (4 members, 12+ corresponding lines) |
| app/src/main/java/com/paparazziapps/pretamistapp/presentation/registro/views/RegistrarLoanFragment.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (19 corresponding lines) |
| app/src/main/java/com/paparazziapps/pretamistapp/data/providers/LoanProvider.kt | 7.8 | Mixed | Change Coupling: Change coupling: LoanProvider.kt ↔ PrincipalActivity.kt |
| app/src/main/java/com/paparazziapps/pretamistapp/presentation/login/viewmodels/ViewModelRegisterUser.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| app/src/main/java/com/paparazziapps/pretamistapp/helper/MyTagHandler.kt | 8.5 | Near-clean | Cognitive Complexity: MyTagHandler.handleTag (cognitive 26) |
| app/src/main/java/com/paparazziapps/pretamistapp/presentation/principal/views/PrincipalActivity.kt | 8.5 | Near-clean | Cognitive Complexity: PrincipalActivity.showBottomSheetDetallePrestamoPrincipal (cognitive 23) |
| app/src/main/java/com/paparazziapps/pretamistapp/presentation/tesoreria/viewmodels/ViewModelFinance.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (29 corresponding lines) |
| app/src/main/java/com/paparazziapps/pretamistapp/helper/PADialogFactory.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (26 corresponding lines) |
| app/src/main/java/com/paparazziapps/pretamistapp/presentation/clients/adater/ClientAdapter.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (14 corresponding lines) |
| app/build.gradle | 9.5 | Near-clean | ADR Quality: No ADRs found |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 37 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 37 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, 52 of 127 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.
- D12 Dependency Hygiene — 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. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 282 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: 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.
- D26 Project Cohesion — 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. `app` (7078 LoC, 208 module-visible types across 37 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D32 Data Compliance (PII/GDPR) — 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. `app/src/main/java/com/paparazziapps/pretamistapp/presentation/clients/ClientsAddFragment.kt`, `app/src/main/java/com/paparazziapps/pretamistapp/presentation/dashboard/adapters/LoanAdapter.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Koin, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — 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. 'com.google.firebase.firestore' is imported (app/src/main/java/com/paparazziapps/pretamistapp/presentation/tesoreria/viewmodels/ViewModelFinance.kt:8), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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.
- C3 Audit Trail — 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. 'com.google.firebase.firestore' is imported (app/src/main/java/com/paparazziapps/pretamistapp/presentation/tesoreria/viewmodels/ViewModelFinance.kt:8), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — 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. 'com.google.firebase.firestore' is imported (app/src/main/java/com/paparazziapps/pretamistapp/presentation/tesoreria/viewmodels/ViewModelFinance.kt:8), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — 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. 'com.google.firebase.firestore' is imported (app/src/main/java/com/paparazziapps/pretamistapp/presentation/tesoreria/viewmodels/ViewModelFinance.kt:8), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
- 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.
- 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
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RegistrarFragment.validateAll at 29.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with RegistrarFragment.validateAll (cyclomatic 29), ViewHolder.updateDelayForLoanType (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was RegistrarFragment.validateAll at 28.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with RegistrarFragment.validateAll (cognitive 28), MyTagHandler.handleTag (cognitive 26), ViewHolder.updateDelayForLoanType (cognitive 26). — 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.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with RegistrarFragment.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
9 duplicated block group(s) detected. 5.8 % of the production lines (410 of 7,078) are in a reported copy. A further 8 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 2 Edited copy of a member (19 corresponding lines) finding(s) in Code Duplication — start with LoanAdapter.kt, RegistrarLoanFragment.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with ClientsParentFragment.kt (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with ClientsParentViewModel.kt, RegistrarLoanFragment.kt. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
2 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (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).
D6 · Cohesion (LCOM4)
0 of 33 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Java/Kotlin (repository root, Gradle): measured (0 flaky).
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 255 artifact(s) resolved, 87 of them gradable against Maven Central, and 71 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
D13 · REDACTED Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D14 · License Compliance
0 of 8 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 2 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 19 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
1 deducted task-comment markers across 7078 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with ViewModelRegisterUser.kt. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
11 finding(s): 0 critical, 9 high, 2 medium, 0 low. 9 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 74, line 180) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 9 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (9 issue-level, 0 of them charged here).
D32 · Data Compliance (PII/GDPR)
1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 2 file(s) — `app/src/main/java/com/paparazziapps/pretamistapp/presentation/clients/ClientsAddFragment.kt`, `app/src/main/java/com/paparazziapps/pretamistapp/presentation/dashboard/adapters/LoanAdapter.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
What to do
- Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 34 of the 115 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: LoanProvider.kt↔PrincipalActivity.kt 60%; LoanAdapter.kt↔PrincipalActivity.kt 57%; RegistrarFragment.kt↔RegistrarLoanFragment.kt 53%
What to do
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with LoanProvider.kt (2), LoanAdapter.kt, RegistrarFragment.kt. — One of this dimension's main actionable groups (4 warning-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 31 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `PARepository` declares 16 abstract methods: `geBranchesRepo`, `createDetail`, `getDetailLoanByDate`, `getLoanByDate`, `createIdDetailLoan`, `createLoan`, `getLoans`, `setLastPayment`, `setLastPaymentForQuota`, `closeLoan`, `loginEmail`, `loginWithEmailV2`, `loginAnonymously`, `createUser`, `signOut`, `searchUserByEmail`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/com/paparazziapps/pretamistapp/data/repository/PARepository.kt:13
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X3 · Exception handling
- `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — app/src/main/java/com/paparazziapps/pretamistapp/presentation/dashboard/viewmodels/ViewModelDetailReceipt.kt:44, app/src/main/java/com/paparazziapps/pretamistapp/domain/utils/DateConverter.kt:62, app/src/main/java/com/paparazziapps/pretamistapp/domain/utils/UtilsLoan.kt:31
What to do
- Swallowed exception (caught, then discarded)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 79.0 | Strong | Solid. |
| Architecture | 89.3 | Strong | Solid. |
| Maturity | 56.0 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 50.2 | Adequate — gated by D12, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 92.5 | Checked 5 of 11 | Solid. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'com.google.firebase.firestore' (app/src/main/java/com/paparazziapps/pretamistapp/presentation/tesoreria/viewmodels/ViewModelFinance.kt:8) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'com.google.firebase.firestore' (app/src/main/java/com/paparazziapps/pretamistapp/presentation/tesoreria/viewmodels/ViewModelFinance.kt:8) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'com.google.firebase.firestore' (app/src/main/java/com/paparazziapps/pretamistapp/presentation/tesoreria/viewmodels/ViewModelFinance.kt:8) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
- 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility (rendered) — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: this repository stores data through 'com.google.firebase.firestore' (app/src/main/java/com/paparazziapps/pretamistapp/presentation/tesoreria/viewmodels/ViewModelFinance.kt:8) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- 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.
- D10 Test Quality — ~153 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.
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 4 candidate(s) found and not reported.
- 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
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- 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) — 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 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 17 value object(s); a Domain/Aggregates/ValueObjects layer
- 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
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JVM source (1 module(s), 112 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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
- 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
- X27 Collection changed while being enumerated — 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 — 11 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 37 finding(s)
- Change coupling: LoanProvider.kt ↔ PrincipalActivity.kt app/src/main/java/com/paparazziapps/pretamistapp/data/providers/LoanProvider.kt:1
- Change coupling: LoanAdapter.kt ↔ PrincipalActivity.kt app/src/main/java/com/paparazziapps/pretamistapp/presentation/dashboard/adapters/LoanAdapter.kt:1
- Change coupling: RegistrarFragment.kt ↔ RegistrarLoanFragment.kt app/src/main/java/com/paparazziapps/pretamistapp/presentation/registro/views/RegistrarFragment.kt:1
- Change coupling: LoanProvider.kt ↔ HomeFragment.kt app/src/main/java/com/paparazziapps/pretamistapp/data/providers/LoanProvider.kt:1
- Swallowed exception (caught, then discarded) app/src/main/java/com/paparazziapps/pretamistapp/presentation/dashboard/viewmodels/ViewModelDetailReceipt.kt:44
- Swallowed exception (caught, then discarded) app/src/main/java/com/paparazziapps/pretamistapp/domain/utils/DateConverter.kt:62
- Swallowed exception (caught, then discarded) app/src/main/java/com/paparazziapps/pretamistapp/domain/utils/UtilsLoan.kt:31
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (19 corresponding lines) app/src/main/java/com/paparazziapps/pretamistapp/presentation/dashboard/adapters/LoanAdapter.kt:221
- Edited copy of a member (19 corresponding lines) app/src/main/java/com/paparazziapps/pretamistapp/presentation/registro/views/RegistrarLoanFragment.kt:270
- Duplicated block (16 lines × 2) app/src/main/java/com/paparazziapps/pretamistapp/presentation/clients/ClientsParentFragment.kt:51
- Duplicated block (16 lines × 2) app/src/main/java/com/paparazziapps/pretamistapp/presentation/clients/ClientsParentFragment.kt:78
- Duplicated block (8 lines × 2) app/src/main/java/com/paparazziapps/pretamistapp/presentation/clients/ClientsParentViewModel.kt:15
- Duplicated block (8 lines × 2) app/src/main/java/com/paparazziapps/pretamistapp/presentation/registro/views/RegistrarLoanFragment.kt:139
- RegistrarFragment.validateAll (cyclomatic 29) app/src/main/java/com/paparazziapps/pretamistapp/presentation/registro/views/RegistrarFragment.kt:178
- ViewHolder.updateDelayForLoanType (cyclomatic 17) app/src/main/java/com/paparazziapps/pretamistapp/presentation/dashboard/adapters/LoanAdapter.kt:243
- TodoComment app/src/main/java/com/paparazziapps/pretamistapp/presentation/login/viewmodels/ViewModelRegisterUser.kt:57
- RegistrarFragment.validateAll (cognitive 28) app/src/main/java/com/paparazziapps/pretamistapp/presentation/registro/views/RegistrarFragment.kt:178
- MyTagHandler.handleTag (cognitive 26) app/src/main/java/com/paparazziapps/pretamistapp/helper/MyTagHandler.kt:14
- ViewHolder.updateDelayForLoanType (cognitive 26) app/src/main/java/com/paparazziapps/pretamistapp/presentation/dashboard/adapters/LoanAdapter.kt:243
- PrincipalActivity.showBottomSheetDetallePrestamoPrincipal (cognitive 23) app/src/main/java/com/paparazziapps/pretamistapp/presentation/principal/views/PrincipalActivity.kt:242
- MethodTooLong: RegistrarFragment.validateAll app/src/main/java/com/paparazziapps/pretamistapp/presentation/registro/views/RegistrarFragment.kt:178
- REDACTED
- Edited copy of a member (29 corresponding lines) app/src/main/java/com/paparazziapps/pretamistapp/presentation/tesoreria/viewmodels/ViewModelFinance.kt:80
- Edited copy of a member (24 corresponding lines) app/src/main/java/com/paparazziapps/pretamistapp/presentation/clients/ClientsParentFragment.kt:77
- Edited copy of a member (21 corresponding lines) REDACTED:250
- Edited copy of a member (26 corresponding lines) app/src/main/java/com/paparazziapps/pretamistapp/helper/PADialogFactory.kt:46
- Edited copies of one member (4 members, 12+ corresponding lines) app/src/main/java/com/paparazziapps/pretamistapp/presentation/clients/ClientsParentViewModel.kt:15
- Edited copy of a member (14 corresponding lines) app/src/main/java/com/paparazziapps/pretamistapp/presentation/clients/adater/ClientAdapter.kt:34
- Duplicated block (20 lines × 2) REDACTED:79
- Duplicated block (17–18 lines × 2) REDACTED:256
- Duplicated block (13 lines × 2) app/src/main/java/com/paparazziapps/pretamistapp/presentation/dashboard/adapters/LoanAdapter.kt:222
- Duplicated block (9–10 lines × 2) app/src/main/java/com/paparazziapps/pretamistapp/presentation/registro/views/RegistrarFragment.kt:244
- Duplicated block (9 lines × 2) app/src/main/java/com/paparazziapps/pretamistapp/presentation/clients/ClientsParentViewModel.kt:28
Minor — 8 finding(s)
- Fat interface: PARepository (16 abstract methods) app/src/main/java/com/paparazziapps/pretamistapp/data/repository/PARepository.kt:13
- No ADRs found app/build.gradle:2
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:6
- No changelog
- Duplicated predicate app/src/main/java/com/paparazziapps/pretamistapp/presentation/principal/views/PrincipalActivity.kt:264
Minor — 71 finding(s)
- Outdated (compile): junit:junit
- Outdated (compile): org.hamcrest:hamcrest-core
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-common
- Outdated (compile): org.jetbrains:annotations
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-android
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core
- Outdated (compile): org.jetbrains.kotlinx:atomicfu
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-bom
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk8
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk7
- Outdated (compile): com.google.code.findbugs:jsr305
- Outdated (compile): com.squareup:javawriter
- Outdated (compile): org.hamcrest:hamcrest-library
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-play-services
- Outdated (compile): com.google.errorprone:error_prone_annotations
- Outdated (compile): com.google.protobuf:protobuf-javalite
- Outdated (compile): io.grpc:grpc-android
- Outdated (compile): io.grpc:grpc-core
- Outdated (compile): io.grpc:grpc-api
- Outdated (compile): io.grpc:grpc-context
- Outdated (compile): io.grpc:grpc-okhttp
- Outdated (compile): io.grpc:grpc-protobuf-lite
- Outdated (compile): io.grpc:grpc-stub
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 --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-933859bd99cb4514968fd3883d8ac200/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=82" --report-format json --report-path /tmp/watchdog-gitleaks-933859bd99cb4514968fd3883d8ac200/history-1.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history-1.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-933859bd99cb4514968fd3883d8ac200/tree.json --exit-code 0 --source . | 1 | 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 . | 11 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep --config /opt/semgrep-rules/gdpr.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 . | 1 | artifacts/raw/semgrep-gdpr.json |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |