Executive summary
qdanik/react-clean-architecture-boilerplate is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no automated security scanning of the code, its secrets or its dependencies, and it has uses of packages that aren't listed. It scores 53 out of 100, which the At risk rating leaves unchanged. We judged it as a template or a sample, against a lower bar.
Production Readiness, at 35, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 16 points. Adding automated security scanning would lift Production Readiness itself, worth about 6 points. Raising Production Readiness to 52 would lift the score to about 61.
Twenty-seven known security holes in the packages the code depends on can be used by attackers. Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and three settings leave the servers or containers unsafe. Updating the vulnerable packages, pinning each tool to an exact version and correcting the unsafe settings would close these risks. The two loops of files that import each other need breaking.
The product code is 2,838 lines, about €2,800 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Production Readiness rose from 35 to 52, the lowest score rated Strong, the score would rise from 53 to about 61.
New since the last survey: 1 finding
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 38 findings
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) src/core/adapters/form/react-hook-form.adapter.ts
- Test Coverage · No test reaches this file src/domain/route/route.constants.ts
- Test Coverage · No test reaches this file src/domain/route/services/route.service.container.ts
- Test Coverage · No test reaches this file src/data/repositories/endpoints.ts
- Test Coverage · No test reaches this file src/domain/route/services/route.service.impl.ts
- Test Coverage · No test reaches this file src/presentation/mobile/index.tsx
- Test Coverage · No test reaches this file src/presentation/web/index.tsx
- Test Coverage · No test reaches this file src/data/repositories/auth/token-axios/token-axios.container.ts
- Test Coverage · No test reaches this file src/domain/notification/notification.types.ts
- Test Coverage · No test reaches this file src/domain/auth/entities/auth-form-fields.entity.ts
- Test Coverage · No test reaches this file src/domain/date/date.types.ts
- Test Coverage · No test reaches this file setup/jest/setup-after-env.ts
- Test Coverage · No test reaches this file src/domain/auth/auth.types.ts
- Test Coverage · No test reaches this file src/core/validators/index.ts
- Test Coverage · No test reaches this file src/presentation/web/modules/index.ts
- Dead Code · Dead file (~3 LoC) src/domain/route/index.ts
- Dead Code · Dead file (~3 LoC) src/domain/route/services/route.service.ts
- Dead Code · Dead file (~2 LoC) src/core/http/endpoint/index.ts
- Dead Code · Dead file (~2 LoC) src/domain/auth/entities/index.ts
- Dead Code · Dead file (~2 LoC) src/domain/date/index.ts
- Dead Code · Dead file (~2 LoC) src/presentation/web/components/index.ts
- Dead Code · Dead file (~1 LoC) src/data/dao/notification/index.ts
- Dead Code · Dead file (~1 LoC) src/data/dto/auth/index.ts
- Dead Code · Dead file (~1 LoC) src/data/repositories/auth/index.ts
- Dead Code · Dead file (~1 LoC) src/data/repositories/auth/token-axios/index.ts
- Dead Code · Dead file (~1 LoC) src/domain/auth/services/index.ts
- Dead Code · Dead file (~1 LoC) src/domain/date/entities/index.ts
- Dead Code · Dead file (~1 LoC) src/domain/error/entities/index.ts
- Dead Code · Dead file (~1 LoC) src/domain/error/services/index.ts
- Dead Code · Dead file (~1 LoC) src/domain/notification/entities/index.ts
- Dead Code · Dead file (~1 LoC) src/domain/notification/services/index.ts
- Dead Code · Dead file (~1 LoC) src/domain/route/entities/index.ts
- Dead Code · Dead file (~1 LoC) src/domain/route/services/index.ts
- Dead Code · Dead file (~0 LoC) src/core/validators/index.ts
- Dead Code · Dead file (~0 LoC) src/presentation/web/modules/index.ts
Rebuild cost: about €2,800 · Estimate
| Cost to rebuild | €940 to €4,700, for 16 to 50 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 53. 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: 2,838 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 setup.vite.config_types | 2 src.containers.config | 3 src.core.form.form-api | 4 src.core.http.http-client | 5 src.core.i18n.i18n_types | 6 src.core.logger.logger | 7 src.core.storage.storage | 8 src.domain.auth.entities.auth-form-fields_entity | 9 src.domain.auth.entities.auth-token_entity | 10 src.domain.error.error_types | 11 src.domain.notification.notification_types | 12 src.presentation.web.components.common.button.button_types | 13 setup.vite | 14 src.core.adapters.browser-cookie.browser-cookie_adapter | 15 src.core.i18n.i18n | 16 src.data.dto.auth.auth-token_dto | 17 src.data.repositories.auth.auth_repo | 18 src.domain.auth.services.auth_service | 19 src.domain.error.entities.error_entity | 20 src.domain.notification.entities.notification_entity | 21 src.presentation.forms.base_form | 22 src.presentation.shared.components.ioc.ioc_types | 23 src.core.adapters.axios.axios_adapter | 24 src.core.adapters.i18next.i18next_adapter | 25 src.core.mobx-store.notification-store.notification_store | 26 src.data.dao.notification.notification_dao | 27 src.data.repositories.auth.auth_repo_impl | 28 src.domain.auth.services.auth_service_impl | 29 src.domain.notification.services.notification_service | 30 src.presentation.forms.base_form_impl | 31 src.core.mobx-store.mobx_store | 32 src.core.mobx-store.notification-store.notification_store_impl | 33 src.data.repositories.auth.token-axios.token-axios_adapter | 34 src.domain.error.services.error_service_impl | 35 src.domain.notification.services.notification_service_impl | 36 src.presentation.forms.auth.auth_form | 37 src.data.dao.notification.notification_dao_impl | 38 src.presentation.presenters.auth.auth_presenter | 39 src.presentation.presenters.auth.auth_presenter_impl | 40 src.presentation.web.modules.auth.auth_types |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 setup.vite.config_types | ||||||||||||||||||||||||||||||||||||||||
| 2 src.containers.config | ||||||||||||||||||||||||||||||||||||||||
| 3 src.core.form.form-api | ||||||||||||||||||||||||||||||||||||||||
| 4 src.core.http.http-client | ||||||||||||||||||||||||||||||||||||||||
| 5 src.core.i18n.i18n_types | ||||||||||||||||||||||||||||||||||||||||
| 6 src.core.logger.logger | ||||||||||||||||||||||||||||||||||||||||
| 7 src.core.storage.storage | ||||||||||||||||||||||||||||||||||||||||
| 8 src.domain.auth.entities.auth-form-fields_entity | ||||||||||||||||||||||||||||||||||||||||
| 9 src.domain.auth.entities.auth-token_entity | ||||||||||||||||||||||||||||||||||||||||
| 10 src.domain.error.error_types | ||||||||||||||||||||||||||||||||||||||||
| 11 src.domain.notification.notification_types | ||||||||||||||||||||||||||||||||||||||||
| 12 src.presentation.web.components.common.button.button_types | ||||||||||||||||||||||||||||||||||||||||
| 13 setup.vite | 5 | |||||||||||||||||||||||||||||||||||||||
| 14 src.core.adapters.browser-cookie.browser-cookie_adapter | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 src.core.i18n.i18n | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 src.data.dto.auth.auth-token_dto | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 src.data.repositories.auth.auth_repo | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 src.domain.auth.services.auth_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 src.domain.error.entities.error_entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 src.domain.notification.entities.notification_entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 src.presentation.forms.base_form | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 src.presentation.shared.components.ioc.ioc_types | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 src.core.adapters.axios.axios_adapter | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 src.core.adapters.i18next.i18next_adapter | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 src.core.mobx-store.notification-store.notification_store | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 src.data.dao.notification.notification_dao | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 src.data.repositories.auth.auth_repo_impl | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 src.domain.auth.services.auth_service_impl | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 src.domain.notification.services.notification_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 src.presentation.forms.base_form_impl | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 src.core.mobx-store.mobx_store | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 src.core.mobx-store.notification-store.notification_store_impl | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 src.data.repositories.auth.token-axios.token-axios_adapter | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 src.domain.error.services.error_service_impl | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 src.domain.notification.services.notification_service_impl | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 src.presentation.forms.auth.auth_form | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 src.data.dao.notification.notification_dao_impl | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 src.presentation.presenters.auth.auth_presenter | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 src.presentation.presenters.auth.auth_presenter_impl | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 40 src.presentation.web.modules.auth.auth_types | 1 |
13→1 setup.vite uses setup.vite.config_types✕
- Connections
- 5 pairs of types, where a type in setup.vite uses a type in setup.vite.config_types.
- The types involved
setup.vite.build→setup.vite.config_types.VitePlatformsetup.vite.define→setup.vite.config_types.VitePlatformsetup.vite.env→setup.vite.config_types.ViteModesetup.vite.env→setup.vite.config_types.VitePlatformsetup.vite.plugins→setup.vite.config_types.VitePlatform
- Direction
- setup.vite uses setup.vite.config_types, so a change to setup.vite.config_types can break setup.vite, while a change to setup.vite can't break setup.vite.config_types.
- Position
- Below the diagonal: setup.vite uses a module listed above it, which is the healthy direction.
14→7 src.core.adapters.browser-cookie.browser-cookie_adapter uses src.core.storage.storage✕
- Connections
- 1 pair of types, where a type in src.core.adapters.browser-cookie.browser-cookie_adapter uses a type in src.core.storage.storage.
- The types involved
src.core.adapters.browser-cookie.browser-cookie_adapter.BrowserCookieAdapter→src.core.storage.storage.Storage
- Direction
- src.core.adapters.browser-cookie.browser-cookie_adapter uses src.core.storage.storage, so a change to src.core.storage.storage can break src.core.adapters.browser-cookie.browser-cookie_adapter, while a change to src.core.adapters.browser-cookie.browser-cookie_adapter can't break src.core.storage.storage.
- Position
- Below the diagonal: src.core.adapters.browser-cookie.browser-cookie_adapter uses a module listed above it, which is the healthy direction.
15→5 src.core.i18n.i18n uses src.core.i18n.i18n_types✕
- Connections
- 1 pair of types, where a type in src.core.i18n.i18n uses a type in src.core.i18n.i18n_types.
- The types involved
src.core.i18n.i18n.I18n→src.core.i18n.i18n_types.I18nLanguages
- Direction
- src.core.i18n.i18n uses src.core.i18n.i18n_types, so a change to src.core.i18n.i18n_types can break src.core.i18n.i18n, while a change to src.core.i18n.i18n can't break src.core.i18n.i18n_types.
- Position
- Below the diagonal: src.core.i18n.i18n uses a module listed above it, which is the healthy direction.
16→9 src.data.dto.auth.auth-token_dto uses src.domain.auth.entities.auth-token_entity✕
- Connections
- 1 pair of types, where a type in src.data.dto.auth.auth-token_dto uses a type in src.domain.auth.entities.auth-token_entity.
- The types involved
src.data.dto.auth.auth-token_dto.AuthTokenDto→src.domain.auth.entities.auth-token_entity.AuthToken
- Direction
- src.data.dto.auth.auth-token_dto uses src.domain.auth.entities.auth-token_entity, so a change to src.domain.auth.entities.auth-token_entity can break src.data.dto.auth.auth-token_dto, while a change to src.data.dto.auth.auth-token_dto can't break src.domain.auth.entities.auth-token_entity.
- Position
- Below the diagonal: src.data.dto.auth.auth-token_dto uses a module listed above it, which is the healthy direction.
17→9 src.data.repositories.auth.auth_repo uses src.domain.auth.entities.auth-token_entity✕
- Connections
- 1 pair of types, where a type in src.data.repositories.auth.auth_repo uses a type in src.domain.auth.entities.auth-token_entity.
- The types involved
src.data.repositories.auth.auth_repo.AuthRepo→src.domain.auth.entities.auth-token_entity.AuthToken
- Direction
- src.data.repositories.auth.auth_repo uses src.domain.auth.entities.auth-token_entity, so a change to src.domain.auth.entities.auth-token_entity can break src.data.repositories.auth.auth_repo, while a change to src.data.repositories.auth.auth_repo can't break src.domain.auth.entities.auth-token_entity.
- Position
- Below the diagonal: src.data.repositories.auth.auth_repo uses a module listed above it, which is the healthy direction.
18→9 src.domain.auth.services.auth_service uses src.domain.auth.entities.auth-token_entity✕
- Connections
- 1 pair of types, where a type in src.domain.auth.services.auth_service uses a type in src.domain.auth.entities.auth-token_entity.
- The types involved
src.domain.auth.services.auth_service.AuthService→src.domain.auth.entities.auth-token_entity.AuthToken
- Direction
- src.domain.auth.services.auth_service uses src.domain.auth.entities.auth-token_entity, so a change to src.domain.auth.entities.auth-token_entity can break src.domain.auth.services.auth_service, while a change to src.domain.auth.services.auth_service can't break src.domain.auth.entities.auth-token_entity.
- Position
- Below the diagonal: src.domain.auth.services.auth_service uses a module listed above it, which is the healthy direction.
19→10 src.domain.error.entities.error_entity uses src.domain.error.error_types✕
- Connections
- 1 pair of types, where a type in src.domain.error.entities.error_entity uses a type in src.domain.error.error_types.
- The types involved
src.domain.error.entities.error_entity.Error→src.domain.error.error_types.ErrorCodes
- Direction
- src.domain.error.entities.error_entity uses src.domain.error.error_types, so a change to src.domain.error.error_types can break src.domain.error.entities.error_entity, while a change to src.domain.error.entities.error_entity can't break src.domain.error.error_types.
- Position
- Below the diagonal: src.domain.error.entities.error_entity uses a module listed above it, which is the healthy direction.
20→11 src.domain.notification.entities.notification_entity uses src.domain.notification.notification_types✕
- Connections
- 1 pair of types, where a type in src.domain.notification.entities.notification_entity uses a type in src.domain.notification.notification_types.
- The types involved
src.domain.notification.entities.notification_entity.Notification→src.domain.notification.notification_types.NotificationType
- Direction
- src.domain.notification.entities.notification_entity uses src.domain.notification.notification_types, so a change to src.domain.notification.notification_types can break src.domain.notification.entities.notification_entity, while a change to src.domain.notification.entities.notification_entity can't break src.domain.notification.notification_types.
- Position
- Below the diagonal: src.domain.notification.entities.notification_entity uses a module listed above it, which is the healthy direction.
21→3 src.presentation.forms.base_form uses src.core.form.form-api✕
- Connections
- 1 pair of types, where a type in src.presentation.forms.base_form uses a type in src.core.form.form-api.
- The types involved
src.presentation.forms.base_form.BaseForm→src.core.form.form-api.Form
- Direction
- src.presentation.forms.base_form uses src.core.form.form-api, so a change to src.core.form.form-api can break src.presentation.forms.base_form, while a change to src.presentation.forms.base_form can't break src.core.form.form-api.
- Position
- Below the diagonal: src.presentation.forms.base_form uses a module listed above it, which is the healthy direction.
22→2 src.presentation.shared.components.ioc.ioc_types uses src.containers.config✕
- Connections
- 1 pair of types, where a type in src.presentation.shared.components.ioc.ioc_types uses a type in src.containers.config.
- The types involved
src.presentation.shared.components.ioc.ioc_types.IoCProps→src.containers.config.Container
- Direction
- src.presentation.shared.components.ioc.ioc_types uses src.containers.config, so a change to src.containers.config can break src.presentation.shared.components.ioc.ioc_types, while a change to src.presentation.shared.components.ioc.ioc_types can't break src.containers.config.
- Position
- Below the diagonal: src.presentation.shared.components.ioc.ioc_types uses a module listed above it, which is the healthy direction.
23→4 src.core.adapters.axios.axios_adapter uses src.core.http.http-client✕
- Connections
- 1 pair of types, where a type in src.core.adapters.axios.axios_adapter uses a type in src.core.http.http-client.
- The types involved
src.core.adapters.axios.axios_adapter.AxiosAdapter→src.core.http.http-client.HttpClient
- Direction
- src.core.adapters.axios.axios_adapter uses src.core.http.http-client, so a change to src.core.http.http-client can break src.core.adapters.axios.axios_adapter, while a change to src.core.adapters.axios.axios_adapter can't break src.core.http.http-client.
- Position
- Below the diagonal: src.core.adapters.axios.axios_adapter uses a module listed above it, which is the healthy direction.
23→6 src.core.adapters.axios.axios_adapter uses src.core.logger.logger✕
- Connections
- 1 pair of types, where a type in src.core.adapters.axios.axios_adapter uses a type in src.core.logger.logger.
- The types involved
src.core.adapters.axios.axios_adapter.AxiosAdapter→src.core.logger.logger.Logger
- Direction
- src.core.adapters.axios.axios_adapter uses src.core.logger.logger, so a change to src.core.logger.logger can break src.core.adapters.axios.axios_adapter, while a change to src.core.adapters.axios.axios_adapter can't break src.core.logger.logger.
- Position
- Below the diagonal: src.core.adapters.axios.axios_adapter uses a module listed above it, which is the healthy direction.
23→15 src.core.adapters.axios.axios_adapter uses src.core.i18n.i18n✕
- Connections
- 1 pair of types, where a type in src.core.adapters.axios.axios_adapter uses a type in src.core.i18n.i18n.
- The types involved
src.core.adapters.axios.axios_adapter.AxiosAdapter→src.core.i18n.i18n.I18n
- Direction
- src.core.adapters.axios.axios_adapter uses src.core.i18n.i18n, so a change to src.core.i18n.i18n can break src.core.adapters.axios.axios_adapter, while a change to src.core.adapters.axios.axios_adapter can't break src.core.i18n.i18n.
- Position
- Below the diagonal: src.core.adapters.axios.axios_adapter uses a module listed above it, which is the healthy direction.
24→5 src.core.adapters.i18next.i18next_adapter uses src.core.i18n.i18n_types✕
- Connections
- 1 pair of types, where a type in src.core.adapters.i18next.i18next_adapter uses a type in src.core.i18n.i18n_types.
- The types involved
src.core.adapters.i18next.i18next_adapter.I18nextAdapter→src.core.i18n.i18n_types.I18nLanguages
- Direction
- src.core.adapters.i18next.i18next_adapter uses src.core.i18n.i18n_types, so a change to src.core.i18n.i18n_types can break src.core.adapters.i18next.i18next_adapter, while a change to src.core.adapters.i18next.i18next_adapter can't break src.core.i18n.i18n_types.
- Position
- Below the diagonal: src.core.adapters.i18next.i18next_adapter uses a module listed above it, which is the healthy direction.
24→15 src.core.adapters.i18next.i18next_adapter uses src.core.i18n.i18n✕
- Connections
- 1 pair of types, where a type in src.core.adapters.i18next.i18next_adapter uses a type in src.core.i18n.i18n.
- The types involved
src.core.adapters.i18next.i18next_adapter.I18nextAdapter→src.core.i18n.i18n.I18n
- Direction
- src.core.adapters.i18next.i18next_adapter uses src.core.i18n.i18n, so a change to src.core.i18n.i18n can break src.core.adapters.i18next.i18next_adapter, while a change to src.core.adapters.i18next.i18next_adapter can't break src.core.i18n.i18n.
- Position
- Below the diagonal: src.core.adapters.i18next.i18next_adapter uses a module listed above it, which is the healthy direction.
25→20 src.core.mobx-store.notification-store.notification_store uses src.domain.notification.entities.notification_entity✕
- Connections
- 1 pair of types, where a type in src.core.mobx-store.notification-store.notification_store uses a type in src.domain.notification.entities.notification_entity.
- The types involved
src.core.mobx-store.notification-store.notification_store.NotificationStore→src.domain.notification.entities.notification_entity.Notification
- Direction
- src.core.mobx-store.notification-store.notification_store uses src.domain.notification.entities.notification_entity, so a change to src.domain.notification.entities.notification_entity can break src.core.mobx-store.notification-store.notification_store, while a change to src.core.mobx-store.notification-store.notification_store can't break src.domain.notification.entities.notification_entity.
- Position
- Below the diagonal: src.core.mobx-store.notification-store.notification_store uses a module listed above it, which is the healthy direction.
26→20 src.data.dao.notification.notification_dao uses src.domain.notification.entities.notification_entity✕
- Connections
- 1 pair of types, where a type in src.data.dao.notification.notification_dao uses a type in src.domain.notification.entities.notification_entity.
- The types involved
src.data.dao.notification.notification_dao.NotificationDao→src.domain.notification.entities.notification_entity.Notification
- Direction
- src.data.dao.notification.notification_dao uses src.domain.notification.entities.notification_entity, so a change to src.domain.notification.entities.notification_entity can break src.data.dao.notification.notification_dao, while a change to src.data.dao.notification.notification_dao can't break src.domain.notification.entities.notification_entity.
- Position
- Below the diagonal: src.data.dao.notification.notification_dao uses a module listed above it, which is the healthy direction.
27→4 src.data.repositories.auth.auth_repo_impl uses src.core.http.http-client✕
- Connections
- 1 pair of types, where a type in src.data.repositories.auth.auth_repo_impl uses a type in src.core.http.http-client.
- The types involved
src.data.repositories.auth.auth_repo_impl.AuthRepoImpl→src.core.http.http-client.HttpClient
- Direction
- src.data.repositories.auth.auth_repo_impl uses src.core.http.http-client, so a change to src.core.http.http-client can break src.data.repositories.auth.auth_repo_impl, while a change to src.data.repositories.auth.auth_repo_impl can't break src.core.http.http-client.
- Position
- Below the diagonal: src.data.repositories.auth.auth_repo_impl uses a module listed above it, which is the healthy direction.
27→6 src.data.repositories.auth.auth_repo_impl uses src.core.logger.logger✕
- Connections
- 1 pair of types, where a type in src.data.repositories.auth.auth_repo_impl uses a type in src.core.logger.logger.
- The types involved
src.data.repositories.auth.auth_repo_impl.AuthRepoImpl→src.core.logger.logger.Logger
- Direction
- src.data.repositories.auth.auth_repo_impl uses src.core.logger.logger, so a change to src.core.logger.logger can break src.data.repositories.auth.auth_repo_impl, while a change to src.data.repositories.auth.auth_repo_impl can't break src.core.logger.logger.
- Position
- Below the diagonal: src.data.repositories.auth.auth_repo_impl uses a module listed above it, which is the healthy direction.
27→9 src.data.repositories.auth.auth_repo_impl uses src.domain.auth.entities.auth-token_entity✕
- Connections
- 1 pair of types, where a type in src.data.repositories.auth.auth_repo_impl uses a type in src.domain.auth.entities.auth-token_entity.
- The types involved
src.data.repositories.auth.auth_repo_impl.AuthRepoImpl→src.domain.auth.entities.auth-token_entity.AuthToken
- Direction
- src.data.repositories.auth.auth_repo_impl uses src.domain.auth.entities.auth-token_entity, so a change to src.domain.auth.entities.auth-token_entity can break src.data.repositories.auth.auth_repo_impl, while a change to src.data.repositories.auth.auth_repo_impl can't break src.domain.auth.entities.auth-token_entity.
- Position
- Below the diagonal: src.data.repositories.auth.auth_repo_impl uses a module listed above it, which is the healthy direction.
27→17 src.data.repositories.auth.auth_repo_impl uses src.data.repositories.auth.auth_repo✕
- Connections
- 1 pair of types, where a type in src.data.repositories.auth.auth_repo_impl uses a type in src.data.repositories.auth.auth_repo.
- The types involved
src.data.repositories.auth.auth_repo_impl.AuthRepoImpl→src.data.repositories.auth.auth_repo.AuthRepo
- Direction
- src.data.repositories.auth.auth_repo_impl uses src.data.repositories.auth.auth_repo, so a change to src.data.repositories.auth.auth_repo can break src.data.repositories.auth.auth_repo_impl, while a change to src.data.repositories.auth.auth_repo_impl can't break src.data.repositories.auth.auth_repo.
- Position
- Below the diagonal: src.data.repositories.auth.auth_repo_impl uses a module listed above it, which is the healthy direction.
28→9 src.domain.auth.services.auth_service_impl uses src.domain.auth.entities.auth-token_entity✕
- Connections
- 1 pair of types, where a type in src.domain.auth.services.auth_service_impl uses a type in src.domain.auth.entities.auth-token_entity.
- The types involved
src.domain.auth.services.auth_service_impl.AuthServiceImpl→src.domain.auth.entities.auth-token_entity.AuthToken
- Direction
- src.domain.auth.services.auth_service_impl uses src.domain.auth.entities.auth-token_entity, so a change to src.domain.auth.entities.auth-token_entity can break src.domain.auth.services.auth_service_impl, while a change to src.domain.auth.services.auth_service_impl can't break src.domain.auth.entities.auth-token_entity.
- Position
- Below the diagonal: src.domain.auth.services.auth_service_impl uses a module listed above it, which is the healthy direction.
28→17 src.domain.auth.services.auth_service_impl uses src.data.repositories.auth.auth_repo✕
- Connections
- 1 pair of types, where a type in src.domain.auth.services.auth_service_impl uses a type in src.data.repositories.auth.auth_repo.
- The types involved
src.domain.auth.services.auth_service_impl.AuthServiceImpl→src.data.repositories.auth.auth_repo.AuthRepo
- Direction
- src.domain.auth.services.auth_service_impl uses src.data.repositories.auth.auth_repo, so a change to src.data.repositories.auth.auth_repo can break src.domain.auth.services.auth_service_impl, while a change to src.domain.auth.services.auth_service_impl can't break src.data.repositories.auth.auth_repo.
- Position
- Below the diagonal: src.domain.auth.services.auth_service_impl uses a module listed above it, which is the healthy direction.
28→18 src.domain.auth.services.auth_service_impl uses src.domain.auth.services.auth_service✕
- Connections
- 1 pair of types, where a type in src.domain.auth.services.auth_service_impl uses a type in src.domain.auth.services.auth_service.
- The types involved
src.domain.auth.services.auth_service_impl.AuthServiceImpl→src.domain.auth.services.auth_service.AuthService
- Direction
- src.domain.auth.services.auth_service_impl uses src.domain.auth.services.auth_service, so a change to src.domain.auth.services.auth_service can break src.domain.auth.services.auth_service_impl, while a change to src.domain.auth.services.auth_service_impl can't break src.domain.auth.services.auth_service.
- Position
- Below the diagonal: src.domain.auth.services.auth_service_impl uses a module listed above it, which is the healthy direction.
29→20 src.domain.notification.services.notification_service uses src.domain.notification.entities.notification_entity✕
- Connections
- 1 pair of types, where a type in src.domain.notification.services.notification_service uses a type in src.domain.notification.entities.notification_entity.
- The types involved
src.domain.notification.services.notification_service.NotificationService→src.domain.notification.entities.notification_entity.Notification
- Direction
- src.domain.notification.services.notification_service uses src.domain.notification.entities.notification_entity, so a change to src.domain.notification.entities.notification_entity can break src.domain.notification.services.notification_service, while a change to src.domain.notification.services.notification_service can't break src.domain.notification.entities.notification_entity.
- Position
- Below the diagonal: src.domain.notification.services.notification_service uses a module listed above it, which is the healthy direction.
30→3 src.presentation.forms.base_form_impl uses src.core.form.form-api✕
- Connections
- 1 pair of types, where a type in src.presentation.forms.base_form_impl uses a type in src.core.form.form-api.
- The types involved
src.presentation.forms.base_form_impl.BaseFormImpl→src.core.form.form-api.Form
- Direction
- src.presentation.forms.base_form_impl uses src.core.form.form-api, so a change to src.core.form.form-api can break src.presentation.forms.base_form_impl, while a change to src.presentation.forms.base_form_impl can't break src.core.form.form-api.
- Position
- Below the diagonal: src.presentation.forms.base_form_impl uses a module listed above it, which is the healthy direction.
30→21 src.presentation.forms.base_form_impl uses src.presentation.forms.base_form✕
- Connections
- 1 pair of types, where a type in src.presentation.forms.base_form_impl uses a type in src.presentation.forms.base_form.
- The types involved
src.presentation.forms.base_form_impl.BaseFormImpl→src.presentation.forms.base_form.BaseForm
- Direction
- src.presentation.forms.base_form_impl uses src.presentation.forms.base_form, so a change to src.presentation.forms.base_form can break src.presentation.forms.base_form_impl, while a change to src.presentation.forms.base_form_impl can't break src.presentation.forms.base_form.
- Position
- Below the diagonal: src.presentation.forms.base_form_impl uses a module listed above it, which is the healthy direction.
31→25 src.core.mobx-store.mobx_store uses src.core.mobx-store.notification-store.notification_store✕
- Connections
- 1 pair of types, where a type in src.core.mobx-store.mobx_store uses a type in src.core.mobx-store.notification-store.notification_store.
- The types involved
src.core.mobx-store.mobx_store.MobxStore→src.core.mobx-store.notification-store.notification_store.NotificationStore
- Direction
- src.core.mobx-store.mobx_store uses src.core.mobx-store.notification-store.notification_store, so a change to src.core.mobx-store.notification-store.notification_store can break src.core.mobx-store.mobx_store, while a change to src.core.mobx-store.mobx_store can't break src.core.mobx-store.notification-store.notification_store.
- Position
- Below the diagonal: src.core.mobx-store.mobx_store uses a module listed above it, which is the healthy direction.
32→20 src.core.mobx-store.notification-store.notification_store_impl uses src.domain.notification.entities.notification_entity✕
- Connections
- 1 pair of types, where a type in src.core.mobx-store.notification-store.notification_store_impl uses a type in src.domain.notification.entities.notification_entity.
- The types involved
src.core.mobx-store.notification-store.notification_store_impl.NotificationStoreImpl→src.domain.notification.entities.notification_entity.Notification
- Direction
- src.core.mobx-store.notification-store.notification_store_impl uses src.domain.notification.entities.notification_entity, so a change to src.domain.notification.entities.notification_entity can break src.core.mobx-store.notification-store.notification_store_impl, while a change to src.core.mobx-store.notification-store.notification_store_impl can't break src.domain.notification.entities.notification_entity.
- Position
- Below the diagonal: src.core.mobx-store.notification-store.notification_store_impl uses a module listed above it, which is the healthy direction.
32→25 src.core.mobx-store.notification-store.notification_store_impl uses src.core.mobx-store.notification-store.notification_store✕
- Connections
- 1 pair of types, where a type in src.core.mobx-store.notification-store.notification_store_impl uses a type in src.core.mobx-store.notification-store.notification_store.
- The types involved
src.core.mobx-store.notification-store.notification_store_impl.NotificationStoreImpl→src.core.mobx-store.notification-store.notification_store.NotificationStore
- Direction
- src.core.mobx-store.notification-store.notification_store_impl uses src.core.mobx-store.notification-store.notification_store, so a change to src.core.mobx-store.notification-store.notification_store can break src.core.mobx-store.notification-store.notification_store_impl, while a change to src.core.mobx-store.notification-store.notification_store_impl can't break src.core.mobx-store.notification-store.notification_store.
- Position
- Below the diagonal: src.core.mobx-store.notification-store.notification_store_impl uses a module listed above it, which is the healthy direction.
33→7 src.data.repositories.auth.token-axios.token-axios_adapter uses src.core.storage.storage✕
- Connections
- 1 pair of types, where a type in src.data.repositories.auth.token-axios.token-axios_adapter uses a type in src.core.storage.storage.
- The types involved
src.data.repositories.auth.token-axios.token-axios_adapter.TokenAxiosAdapter→src.core.storage.storage.Storage
- Direction
- src.data.repositories.auth.token-axios.token-axios_adapter uses src.core.storage.storage, so a change to src.core.storage.storage can break src.data.repositories.auth.token-axios.token-axios_adapter, while a change to src.data.repositories.auth.token-axios.token-axios_adapter can't break src.core.storage.storage.
- Position
- Below the diagonal: src.data.repositories.auth.token-axios.token-axios_adapter uses a module listed above it, which is the healthy direction.
33→23 src.data.repositories.auth.token-axios.token-axios_adapter uses src.core.adapters.axios.axios_adapter✕
- Connections
- 1 pair of types, where a type in src.data.repositories.auth.token-axios.token-axios_adapter uses a type in src.core.adapters.axios.axios_adapter.
- The types involved
src.data.repositories.auth.token-axios.token-axios_adapter.TokenAxiosAdapter→src.core.adapters.axios.axios_adapter.AxiosAdapter
- Direction
- src.data.repositories.auth.token-axios.token-axios_adapter uses src.core.adapters.axios.axios_adapter, so a change to src.core.adapters.axios.axios_adapter can break src.data.repositories.auth.token-axios.token-axios_adapter, while a change to src.data.repositories.auth.token-axios.token-axios_adapter can't break src.core.adapters.axios.axios_adapter.
- Position
- Below the diagonal: src.data.repositories.auth.token-axios.token-axios_adapter uses a module listed above it, which is the healthy direction.
34→10 src.domain.error.services.error_service_impl uses src.domain.error.error_types✕
- Connections
- 1 pair of types, where a type in src.domain.error.services.error_service_impl uses a type in src.domain.error.error_types.
- The types involved
src.domain.error.services.error_service_impl.ErrorServiceImpl→src.domain.error.error_types.ErrorResponse
- Direction
- src.domain.error.services.error_service_impl uses src.domain.error.error_types, so a change to src.domain.error.error_types can break src.domain.error.services.error_service_impl, while a change to src.domain.error.services.error_service_impl can't break src.domain.error.error_types.
- Position
- Below the diagonal: src.domain.error.services.error_service_impl uses a module listed above it, which is the healthy direction.
34→19 src.domain.error.services.error_service_impl uses src.domain.error.entities.error_entity✕
- Connections
- 1 pair of types, where a type in src.domain.error.services.error_service_impl uses a type in src.domain.error.entities.error_entity.
- The types involved
src.domain.error.services.error_service_impl.ErrorServiceImpl→src.domain.error.entities.error_entity.Error
- Direction
- src.domain.error.services.error_service_impl uses src.domain.error.entities.error_entity, so a change to src.domain.error.entities.error_entity can break src.domain.error.services.error_service_impl, while a change to src.domain.error.services.error_service_impl can't break src.domain.error.entities.error_entity.
- Position
- Below the diagonal: src.domain.error.services.error_service_impl uses a module listed above it, which is the healthy direction.
34→29 src.domain.error.services.error_service_impl uses src.domain.notification.services.notification_service✕
- Connections
- 1 pair of types, where a type in src.domain.error.services.error_service_impl uses a type in src.domain.notification.services.notification_service.
- The types involved
src.domain.error.services.error_service_impl.ErrorServiceImpl→src.domain.notification.services.notification_service.NotificationService
- Direction
- src.domain.error.services.error_service_impl uses src.domain.notification.services.notification_service, so a change to src.domain.notification.services.notification_service can break src.domain.error.services.error_service_impl, while a change to src.domain.error.services.error_service_impl can't break src.domain.notification.services.notification_service.
- Position
- Below the diagonal: src.domain.error.services.error_service_impl uses a module listed above it, which is the healthy direction.
35→11 src.domain.notification.services.notification_service_impl uses src.domain.notification.notification_types✕
- Connections
- 1 pair of types, where a type in src.domain.notification.services.notification_service_impl uses a type in src.domain.notification.notification_types.
- The types involved
src.domain.notification.services.notification_service_impl.NotificationServiceImpl→src.domain.notification.notification_types.NotificationType
- Direction
- src.domain.notification.services.notification_service_impl uses src.domain.notification.notification_types, so a change to src.domain.notification.notification_types can break src.domain.notification.services.notification_service_impl, while a change to src.domain.notification.services.notification_service_impl can't break src.domain.notification.notification_types.
- Position
- Below the diagonal: src.domain.notification.services.notification_service_impl uses a module listed above it, which is the healthy direction.
35→20 src.domain.notification.services.notification_service_impl uses src.domain.notification.entities.notification_entity✕
- Connections
- 1 pair of types, where a type in src.domain.notification.services.notification_service_impl uses a type in src.domain.notification.entities.notification_entity.
- The types involved
src.domain.notification.services.notification_service_impl.NotificationServiceImpl→src.domain.notification.entities.notification_entity.Notification
- Direction
- src.domain.notification.services.notification_service_impl uses src.domain.notification.entities.notification_entity, so a change to src.domain.notification.entities.notification_entity can break src.domain.notification.services.notification_service_impl, while a change to src.domain.notification.services.notification_service_impl can't break src.domain.notification.entities.notification_entity.
- Position
- Below the diagonal: src.domain.notification.services.notification_service_impl uses a module listed above it, which is the healthy direction.
35→26 src.domain.notification.services.notification_service_impl uses src.data.dao.notification.notification_dao✕
- Connections
- 1 pair of types, where a type in src.domain.notification.services.notification_service_impl uses a type in src.data.dao.notification.notification_dao.
- The types involved
src.domain.notification.services.notification_service_impl.NotificationServiceImpl→src.data.dao.notification.notification_dao.NotificationDao
- Direction
- src.domain.notification.services.notification_service_impl uses src.data.dao.notification.notification_dao, so a change to src.data.dao.notification.notification_dao can break src.domain.notification.services.notification_service_impl, while a change to src.domain.notification.services.notification_service_impl can't break src.data.dao.notification.notification_dao.
- Position
- Below the diagonal: src.domain.notification.services.notification_service_impl uses a module listed above it, which is the healthy direction.
35→29 src.domain.notification.services.notification_service_impl uses src.domain.notification.services.notification_service✕
- Connections
- 1 pair of types, where a type in src.domain.notification.services.notification_service_impl uses a type in src.domain.notification.services.notification_service.
- The types involved
src.domain.notification.services.notification_service_impl.NotificationServiceImpl→src.domain.notification.services.notification_service.NotificationService
- Direction
- src.domain.notification.services.notification_service_impl uses src.domain.notification.services.notification_service, so a change to src.domain.notification.services.notification_service can break src.domain.notification.services.notification_service_impl, while a change to src.domain.notification.services.notification_service_impl can't break src.domain.notification.services.notification_service.
- Position
- Below the diagonal: src.domain.notification.services.notification_service_impl uses a module listed above it, which is the healthy direction.
36→8 src.presentation.forms.auth.auth_form uses src.domain.auth.entities.auth-form-fields_entity✕
- Connections
- 1 pair of types, where a type in src.presentation.forms.auth.auth_form uses a type in src.domain.auth.entities.auth-form-fields_entity.
- The types involved
src.presentation.forms.auth.auth_form.AuthForm→src.domain.auth.entities.auth-form-fields_entity.AuthFormFields
- Direction
- src.presentation.forms.auth.auth_form uses src.domain.auth.entities.auth-form-fields_entity, so a change to src.domain.auth.entities.auth-form-fields_entity can break src.presentation.forms.auth.auth_form, while a change to src.presentation.forms.auth.auth_form can't break src.domain.auth.entities.auth-form-fields_entity.
- Position
- Below the diagonal: src.presentation.forms.auth.auth_form uses a module listed above it, which is the healthy direction.
36→18 src.presentation.forms.auth.auth_form uses src.domain.auth.services.auth_service✕
- Connections
- 1 pair of types, where a type in src.presentation.forms.auth.auth_form uses a type in src.domain.auth.services.auth_service.
- The types involved
src.presentation.forms.auth.auth_form.AuthForm→src.domain.auth.services.auth_service.AuthService
- Direction
- src.presentation.forms.auth.auth_form uses src.domain.auth.services.auth_service, so a change to src.domain.auth.services.auth_service can break src.presentation.forms.auth.auth_form, while a change to src.presentation.forms.auth.auth_form can't break src.domain.auth.services.auth_service.
- Position
- Below the diagonal: src.presentation.forms.auth.auth_form uses a module listed above it, which is the healthy direction.
36→30 src.presentation.forms.auth.auth_form uses src.presentation.forms.base_form_impl✕
- Connections
- 1 pair of types, where a type in src.presentation.forms.auth.auth_form uses a type in src.presentation.forms.base_form_impl.
- The types involved
src.presentation.forms.auth.auth_form.AuthForm→src.presentation.forms.base_form_impl.BaseFormImpl
- Direction
- src.presentation.forms.auth.auth_form uses src.presentation.forms.base_form_impl, so a change to src.presentation.forms.base_form_impl can break src.presentation.forms.auth.auth_form, while a change to src.presentation.forms.auth.auth_form can't break src.presentation.forms.base_form_impl.
- Position
- Below the diagonal: src.presentation.forms.auth.auth_form uses a module listed above it, which is the healthy direction.
37→20 src.data.dao.notification.notification_dao_impl uses src.domain.notification.entities.notification_entity✕
- Connections
- 1 pair of types, where a type in src.data.dao.notification.notification_dao_impl uses a type in src.domain.notification.entities.notification_entity.
- The types involved
src.data.dao.notification.notification_dao_impl.NotificationDaoImpl→src.domain.notification.entities.notification_entity.Notification
- Direction
- src.data.dao.notification.notification_dao_impl uses src.domain.notification.entities.notification_entity, so a change to src.domain.notification.entities.notification_entity can break src.data.dao.notification.notification_dao_impl, while a change to src.data.dao.notification.notification_dao_impl can't break src.domain.notification.entities.notification_entity.
- Position
- Below the diagonal: src.data.dao.notification.notification_dao_impl uses a module listed above it, which is the healthy direction.
37→26 src.data.dao.notification.notification_dao_impl uses src.data.dao.notification.notification_dao✕
- Connections
- 1 pair of types, where a type in src.data.dao.notification.notification_dao_impl uses a type in src.data.dao.notification.notification_dao.
- The types involved
src.data.dao.notification.notification_dao_impl.NotificationDaoImpl→src.data.dao.notification.notification_dao.NotificationDao
- Direction
- src.data.dao.notification.notification_dao_impl uses src.data.dao.notification.notification_dao, so a change to src.data.dao.notification.notification_dao can break src.data.dao.notification.notification_dao_impl, while a change to src.data.dao.notification.notification_dao_impl can't break src.data.dao.notification.notification_dao.
- Position
- Below the diagonal: src.data.dao.notification.notification_dao_impl uses a module listed above it, which is the healthy direction.
37→31 src.data.dao.notification.notification_dao_impl uses src.core.mobx-store.mobx_store✕
- Connections
- 1 pair of types, where a type in src.data.dao.notification.notification_dao_impl uses a type in src.core.mobx-store.mobx_store.
- The types involved
src.data.dao.notification.notification_dao_impl.NotificationDaoImpl→src.core.mobx-store.mobx_store.MobxStore
- Direction
- src.data.dao.notification.notification_dao_impl uses src.core.mobx-store.mobx_store, so a change to src.core.mobx-store.mobx_store can break src.data.dao.notification.notification_dao_impl, while a change to src.data.dao.notification.notification_dao_impl can't break src.core.mobx-store.mobx_store.
- Position
- Below the diagonal: src.data.dao.notification.notification_dao_impl uses a module listed above it, which is the healthy direction.
38→8 src.presentation.presenters.auth.auth_presenter uses src.domain.auth.entities.auth-form-fields_entity✕
- Connections
- 1 pair of types, where a type in src.presentation.presenters.auth.auth_presenter uses a type in src.domain.auth.entities.auth-form-fields_entity.
- The types involved
src.presentation.presenters.auth.auth_presenter.AuthPresenter→src.domain.auth.entities.auth-form-fields_entity.AuthFormFields
- Direction
- src.presentation.presenters.auth.auth_presenter uses src.domain.auth.entities.auth-form-fields_entity, so a change to src.domain.auth.entities.auth-form-fields_entity can break src.presentation.presenters.auth.auth_presenter, while a change to src.presentation.presenters.auth.auth_presenter can't break src.domain.auth.entities.auth-form-fields_entity.
- Position
- Below the diagonal: src.presentation.presenters.auth.auth_presenter uses a module listed above it, which is the healthy direction.
38→21 src.presentation.presenters.auth.auth_presenter uses src.presentation.forms.base_form✕
- Connections
- 1 pair of types, where a type in src.presentation.presenters.auth.auth_presenter uses a type in src.presentation.forms.base_form.
- The types involved
src.presentation.presenters.auth.auth_presenter.AuthPresenter→src.presentation.forms.base_form.BaseForm
- Direction
- src.presentation.presenters.auth.auth_presenter uses src.presentation.forms.base_form, so a change to src.presentation.forms.base_form can break src.presentation.presenters.auth.auth_presenter, while a change to src.presentation.presenters.auth.auth_presenter can't break src.presentation.forms.base_form.
- Position
- Below the diagonal: src.presentation.presenters.auth.auth_presenter uses a module listed above it, which is the healthy direction.
38→36 src.presentation.presenters.auth.auth_presenter uses src.presentation.forms.auth.auth_form✕
- Connections
- 1 pair of types, where a type in src.presentation.presenters.auth.auth_presenter uses a type in src.presentation.forms.auth.auth_form.
- The types involved
src.presentation.presenters.auth.auth_presenter.AuthPresenter→src.presentation.forms.auth.auth_form.AuthFormSubmitResponse
- Direction
- src.presentation.presenters.auth.auth_presenter uses src.presentation.forms.auth.auth_form, so a change to src.presentation.forms.auth.auth_form can break src.presentation.presenters.auth.auth_presenter, while a change to src.presentation.presenters.auth.auth_presenter can't break src.presentation.forms.auth.auth_form.
- Position
- Below the diagonal: src.presentation.presenters.auth.auth_presenter uses a module listed above it, which is the healthy direction.
39→8 src.presentation.presenters.auth.auth_presenter_impl uses src.domain.auth.entities.auth-form-fields_entity✕
- Connections
- 1 pair of types, where a type in src.presentation.presenters.auth.auth_presenter_impl uses a type in src.domain.auth.entities.auth-form-fields_entity.
- The types involved
src.presentation.presenters.auth.auth_presenter_impl.AuthPresenterImpl→src.domain.auth.entities.auth-form-fields_entity.AuthFormFields
- Direction
- src.presentation.presenters.auth.auth_presenter_impl uses src.domain.auth.entities.auth-form-fields_entity, so a change to src.domain.auth.entities.auth-form-fields_entity can break src.presentation.presenters.auth.auth_presenter_impl, while a change to src.presentation.presenters.auth.auth_presenter_impl can't break src.domain.auth.entities.auth-form-fields_entity.
- Position
- Below the diagonal: src.presentation.presenters.auth.auth_presenter_impl uses a module listed above it, which is the healthy direction.
39→15 src.presentation.presenters.auth.auth_presenter_impl uses src.core.i18n.i18n✕
- Connections
- 1 pair of types, where a type in src.presentation.presenters.auth.auth_presenter_impl uses a type in src.core.i18n.i18n.
- The types involved
src.presentation.presenters.auth.auth_presenter_impl.AuthPresenterImpl→src.core.i18n.i18n.I18n
- Direction
- src.presentation.presenters.auth.auth_presenter_impl uses src.core.i18n.i18n, so a change to src.core.i18n.i18n can break src.presentation.presenters.auth.auth_presenter_impl, while a change to src.presentation.presenters.auth.auth_presenter_impl can't break src.core.i18n.i18n.
- Position
- Below the diagonal: src.presentation.presenters.auth.auth_presenter_impl uses a module listed above it, which is the healthy direction.
39→21 src.presentation.presenters.auth.auth_presenter_impl uses src.presentation.forms.base_form✕
- Connections
- 1 pair of types, where a type in src.presentation.presenters.auth.auth_presenter_impl uses a type in src.presentation.forms.base_form.
- The types involved
src.presentation.presenters.auth.auth_presenter_impl.AuthPresenterImpl→src.presentation.forms.base_form.BaseForm
- Direction
- src.presentation.presenters.auth.auth_presenter_impl uses src.presentation.forms.base_form, so a change to src.presentation.forms.base_form can break src.presentation.presenters.auth.auth_presenter_impl, while a change to src.presentation.presenters.auth.auth_presenter_impl can't break src.presentation.forms.base_form.
- Position
- Below the diagonal: src.presentation.presenters.auth.auth_presenter_impl uses a module listed above it, which is the healthy direction.
39→36 src.presentation.presenters.auth.auth_presenter_impl uses src.presentation.forms.auth.auth_form✕
- Connections
- 1 pair of types, where a type in src.presentation.presenters.auth.auth_presenter_impl uses a type in src.presentation.forms.auth.auth_form.
- The types involved
src.presentation.presenters.auth.auth_presenter_impl.AuthPresenterImpl→src.presentation.forms.auth.auth_form.AuthFormSubmitResponse
- Direction
- src.presentation.presenters.auth.auth_presenter_impl uses src.presentation.forms.auth.auth_form, so a change to src.presentation.forms.auth.auth_form can break src.presentation.presenters.auth.auth_presenter_impl, while a change to src.presentation.presenters.auth.auth_presenter_impl can't break src.presentation.forms.auth.auth_form.
- Position
- Below the diagonal: src.presentation.presenters.auth.auth_presenter_impl uses a module listed above it, which is the healthy direction.
39→38 src.presentation.presenters.auth.auth_presenter_impl uses src.presentation.presenters.auth.auth_presenter✕
- Connections
- 1 pair of types, where a type in src.presentation.presenters.auth.auth_presenter_impl uses a type in src.presentation.presenters.auth.auth_presenter.
- The types involved
src.presentation.presenters.auth.auth_presenter_impl.AuthPresenterImpl→src.presentation.presenters.auth.auth_presenter.AuthPresenter
- Direction
- src.presentation.presenters.auth.auth_presenter_impl uses src.presentation.presenters.auth.auth_presenter, so a change to src.presentation.presenters.auth.auth_presenter can break src.presentation.presenters.auth.auth_presenter_impl, while a change to src.presentation.presenters.auth.auth_presenter_impl can't break src.presentation.presenters.auth.auth_presenter.
- Position
- Below the diagonal: src.presentation.presenters.auth.auth_presenter_impl uses a module listed above it, which is the healthy direction.
40→38 src.presentation.web.modules.auth.auth_types uses src.presentation.presenters.auth.auth_presenter✕
- Connections
- 1 pair of types, where a type in src.presentation.web.modules.auth.auth_types uses a type in src.presentation.presenters.auth.auth_presenter.
- The types involved
src.presentation.web.modules.auth.auth_types.AuthProps→src.presentation.presenters.auth.auth_presenter.AuthPresenter
- Direction
- src.presentation.web.modules.auth.auth_types uses src.presentation.presenters.auth.auth_presenter, so a change to src.presentation.presenters.auth.auth_presenter can break src.presentation.web.modules.auth.auth_types, while a change to src.presentation.web.modules.auth.auth_types can't break src.presentation.presenters.auth.auth_presenter.
- Position
- Below the diagonal: src.presentation.web.modules.auth.auth_types uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 45 | High / Critical |
| A05:2025 — Injection | 14 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
| A07:2025 — Authentication Failures | 3 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED; Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +15.6 pts | Low | REDACTED Scanning |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +5.8 pts | Medium | Security & performance tooling |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +4.6 pts | Medium | Dependency Hygiene |
| Resolve the 2 Orphaned file finding(s) in Knowledge Freshness — start with eslint.config.js, axios.adapter.ts. | +2.3 pts | Low | Knowledge Freshness |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +1.9 pts | Low | Knowledge Freshness |
| The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`). | +1.9 pts | Medium | Nullable reference types |
| Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value. | +1.7 pts | Medium | Dead Code |
| 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. | +1.4 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 0.8 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: High IaC: REDACTED |
| package.json | 6.4 | Near-clean | Platform End-of-Life: End-of-life runtime: Node.js 20 |
| REDACTED | 6.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| setup/vite/plugins/react-svg/index.ts | 8.5 | Near-clean | Cognitive Complexity: index.default.transform (cognitive 16) |
| REDACTED | 9.3 | Near-clean | Static Analysis (SAST): Low: REDACTED |
| REDACTED | 9.3 | Near-clean | Static Analysis (SAST): Low: REDACTED |
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 70 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 70 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, 173 of 200 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because registry.npmjs.org — the registry that answers it — was asked and did not reply (registry returned 429). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add registry.npmjs.org to the allowlist and re-run — not to build anything.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 72 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 1 hold 1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- 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 InversifyJS, 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.
- DM9 Scattered domain decisions — 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. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- R4 Test Coverage — 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. 14 further occurrence(s) are not listed individually; the score already reflects all 54.
- R7 Dead Code — 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. 27 further occurrence(s) are not listed individually; the score already reflects all 67.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — 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, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, 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.
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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").
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was index.default.transform at 16.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with index.default.transform (cognitive 16). — Refactoring it lifts Cognitive Complexity from 9.9 to about 10.0/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D6 · Cohesion (LCOM4)
0 of 7 classes have LCOM4 above 3.
D9 · Test Distribution
9 test methods: 9 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 9 `it`/`test` case(s) across 4 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 9 tests.
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).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 2814 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 4 document(s) read across 1 unit(s).
D26 · Project Cohesion
0 of 1 build units (npm) flagged as possibly oversized/incoherent.
D27 · Navigability
10 % of calls cross a namespace and 0 % go through an interface, but 66 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
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)
14 finding(s): 0 critical, 6 high, 6 medium, 2 low. 6 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) — `index.html` (line 11, line 17) — 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 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- 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 6 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 (6 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
45 finding(s): 2 critical, 25 high, 14 medium, 4 low.
What to do
- Resolve the 25 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (25). — One of this dimension's main actionable groups (25 issue-level).
- Resolve the 13 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (13). — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D31 · IaC & Container Security
5 finding(s): 0 critical, 3 high, 1 medium, 1 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
2 of 2 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is eslint.config.js. Counted over 2 of the 200 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 2 Orphaned file finding(s) in Knowledge Freshness — start with eslint.config.js, axios.adapter.ts. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 21 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.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- README.md links to `LICENSE.md`, but `LICENSE.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:59
What to do
- Reconcile the README with reality: README.md links to `LICENSE.md`, but `LICENSE.md` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- `src/presentation/shared/components/ioc/hooks/injection.hook.ts` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/presentation/shared/components/ioc/hooks/injection.hook.ts:12
- `src/core/utils/app-version.util.ts` reports through `console.*` at line 4 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/core/utils/app-version.util.ts:4
- `src/core/adapters/logger/logger.adapter.ts` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/core/adapters/logger/logger.adapter.ts:12
- `src/core/adapters/logger/logger.adapter.ts` reports through `console.*` at line 20 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/core/adapters/logger/logger.adapter.ts:20
- `src/core/adapters/logger/logger.adapter.ts` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/core/adapters/logger/logger.adapter.ts:29
- `src/core/adapters/logger/logger.adapter.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/core/adapters/logger/logger.adapter.ts:38
- `setup/vite/env.ts` reports through `console.*` at line 25 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — setup/vite/env.ts:25
What to do
- Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
- Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 1291 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:2
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:39
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
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
- `readFileSync` in `transform` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — setup/vite/plugins/react-svg/index.ts:71
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety
R10 · Code Duplication
- src/core/adapters/local-storage/local-storage.adapter.ts:4 · src/core/adapters/session-storage/session-storage.adapter.ts:4 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/core/adapters/local-storage/local-storage.adapter.ts:4
- setup/plopjs/entity.ts:37 · setup/plopjs/repo.ts:23 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — setup/plopjs/entity.ts:37
- setup/plopjs/entity.ts:68 · setup/plopjs/service.ts:62 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — setup/plopjs/entity.ts:68
- src/core/adapters/axios/axios.adapter.ts:73 · src/core/adapters/axios/axios.adapter.ts:85 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/core/adapters/axios/axios.adapter.ts:73
- REDACTED:1 · REDACTED:12 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:1
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- src/containers/config.ts:4 imports inversify/lib/annotation/lazy_service_identifier, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/containers/config.ts:4
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — setup/plopjs/entity.ts:1, setup/vite/plugins/react-svg/index.ts:1, setup/plopjs/service.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
- Unreachable from the 8 application, 5 tooling and 4 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/domain/notification/services/notification.service.container.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/notification/services/notification.service.impl.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (src/domain/error/entities/index.ts, src/domain/error/services/error.service.impl.ts, src/domain/error/services/error.service.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/error/entities/error.entity.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/domain/route/entities/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/route/entities/route.entity.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/data/repositories/auth/token-axios/token-axios.container.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/data/repositories/auth/token-axios/token-axios.adapter.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/domain/notification/entities/index.ts, src/domain/notification/services/notification.service.impl.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/notification/entities/notification.entity.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/data/repositories/auth/auth.repo.container.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/data/repositories/auth/auth.repo.impl.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (src/domain/auth/entities/index.ts, src/domain/auth/services/auth.service.impl.ts, src/domain/auth/services/auth.service.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/auth/entities/auth-token.entity.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/domain/error/services/error.service.container.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/error/services/error.service.impl.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/data/dao/notification/notification.dao.container.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/data/dao/notification/notification.dao.impl.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/domain/date/entities/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/date/entities/date.entity.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/http/endpoint/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/http/endpoint/endpoint.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/domain/auth/services/auth.service.container.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/auth/services/auth.service.impl.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/data/dto/auth/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/data/dto/auth/auth-token.dto.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/data/repositories/auth/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/data/repositories/auth/auth.repo.container.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/domain/notification/services/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/notification/services/notification.service.container.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/data/dao/notification/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/data/dao/notification/notification.dao.container.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/domain/auth/services/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/auth/services/auth.service.container.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (src/domain/error/entities/error.entity.ts, src/domain/error/index.ts, src/domain/error/services/error.service.impl.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/error/error.types.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/domain/error/services/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/error/services/error.service.container.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/domain/route/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/route/route.constants.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/domain/route/services/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/route/services/route.service.container.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×5) — src/data/repositories/endpoints.ts, src/presentation/mobile/index.tsx, src/domain/auth/index.ts, …
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/domain/route/services/route.service.container.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/route/services/route.service.impl.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/data/repositories/auth/auth.repo.container.ts, src/data/repositories/auth/auth.repo.impl.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — src/data/repositories/auth/auth.repo.response.ts, src/data/repositories/auth/auth.repo.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/data/repositories/auth/token-axios/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/data/repositories/auth/token-axios/token-axios.container.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/domain/notification/services/notification.service.container.ts, src/domain/notification/services/notification.service.impl.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/notification/services/notification.service.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (src/domain/notification/entities/notification.entity.ts, src/domain/notification/index.ts, src/domain/notification/services/notification.service.impl.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/notification/notification.types.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/data/dao/notification/notification.dao.container.ts, src/data/dao/notification/notification.dao.impl.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/data/dao/notification/notification.dao.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/core/http/endpoint/endpoint.ts, src/core/http/endpoint/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/http/endpoint/endpoint.types.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/domain/auth/entities/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/auth/entities/auth-form-fields.entity.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/domain/error/services/error.service.container.ts, src/domain/error/services/error.service.impl.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/error/services/error.service.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/domain/auth/services/auth.service.container.ts, src/domain/auth/services/auth.service.impl.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/auth/services/auth.service.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/domain/date/entities/date.entity.ts, src/domain/date/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/date/date.types.ts
- no import path from any entry point (8 application, 5 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/domain/auth/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/domain/auth/auth.types.ts
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json. — setup/jest/config.ts:1
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×2) — setup/plopjs/index.ts:1, setup/plopjs/service.ts:1
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- src/data/dto/auth/auth-token.dto.ts → src/data/repositories/auth/index.ts → src/data/repositories/auth/auth.repo.container.ts → src/data/repositories/auth/auth.repo.impl.ts → src/data/dto/auth/index.ts → src/data/dto/auth/auth-token.dto.ts — src/data/dto/auth/auth-token.dto.ts:1
- src/presentation/shared/hoc/error-boundary.hoc.tsx → src/presentation/shared/index.ts → src/presentation/shared/hoc/index.ts → src/presentation/shared/hoc/error-boundary.hoc.tsx — src/presentation/shared/hoc/error-boundary.hoc.tsx:4
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `REDACTED` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — REDACTED:1
What to do
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- 0/2 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65% | Adequate — gated by R7, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 76% | Strong | Solid. |
| Maturity | 65% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 35% | Adequate — gated by R8, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 79% | Strong | Solid. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Performance | 85% | Exemplary | Solid. |
Unscored — 5 check(s) recorded observations but carry no score
- AXH1 Runtime security headers — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXI1 Runtime container hardening — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility (rendered) — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- D12 Dependency Hygiene — 1 observation(s) recorded · Dependency currency not established — registry.npmjs.org did not answer
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). 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.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
- 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 — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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
- AXA1 Runtime unauthenticated reachability — This run crawled public routes only — it had no logged-in session, so there is no authenticated surface to compare anonymous access against and nothing was measured. This is a statement about this run, not about your application: nothing here says access control is missing, and nothing here says it is present.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D11 Test Reliability — Test reliability NOT MEASURED: the JavaScript/TypeScript suite's dependency install refused the committed lockfile, so no test ever ran and flakiness could not be exercised — the dependency install for the repository root refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. It is excluded from the score rather than counted as a defect; a lockfile in sync with package.json is what lets the suite be re-run.
- D14 License Compliance — Not scored — this repository's 75 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 3 of them (registry returned 429), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (2 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- 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.
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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 MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `jest --coverage --coverageReporters=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- 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 — 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
- 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 — 43 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test suite cannot be installed from its own lockfile: the repository root
- REDACTED
- REDACTED
- Unlisted import 'minimist' setup/plopjs/index.ts:1
- Unlisted import 'node-plop' setup/plopjs/service.ts:1
- Import cycle (5 files) src/data/dto/auth/auth-token.dto.ts:1
- Import cycle (3 files) src/presentation/shared/hoc/error-boundary.hoc.tsx:4
Serious — 130 finding(s)
- No test reaches this file setup/plopjs/entity.ts:1
- No test reaches this file setup/vite/plugins/react-svg/index.ts:1
- No test reaches this file setup/plopjs/service.ts:1
- No test reaches this file setup/plopjs/repo.ts:1
- No test reaches this file setup/plopjs/domain.ts:1
- No test reaches this file setup/plopjs/constants.ts:1
- No test reaches this file setup/vite/plugins.ts:1
- No test reaches this file setup/vite/config.ts:1
- No test reaches this file setup/vite/build.ts:1
- No test reaches this file setup/jest/config.ts:1
- No test reaches this file src/domain/notification/services/notification.service.impl.ts:1
- No test reaches this file src/domain/error/entities/error.entity.ts:1
- No test reaches this file src/domain/route/entities/route.entity.ts:1
- No test reaches this file src/data/repositories/auth/token-axios/token-axios.adapter.ts:1
- No test reaches this file src/domain/notification/entities/notification.entity.ts:1
- No test reaches this file src/presentation/web/styles/index.ts:1
- No test reaches this file src/presentation/web/routes/routes.component.tsx:1
- No test reaches this file src/data/repositories/auth/auth.repo.impl.ts:1
- No test reaches this file setup/vite/env.ts:1
- No test reaches this file setup/jest/plugins/fileTransformer.js:1
- No test reaches this file src/domain/auth/entities/auth-token.entity.ts:1
- No test reaches this file src/domain/error/services/error.service.impl.ts:1
- No test reaches this file setup/plopjs/index.ts:1
- No test reaches this file src/data/dao/notification/notification.dao.impl.ts:1
- No test reaches this file src/domain/date/entities/date.entity.ts:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Runtime security header not set: content-security-policy
- Runtime security header not set: cross-origin-embedder-policy
- Runtime security header not set: cross-origin-opener-policy
- Runtime security header not set: cross-origin-resource-policy
- Runtime security header not set: permissions-policy
- Runtime security header not set: referrer-policy
- Runtime security header not set: strict-transport-security
- Runtime security header not set: x-content-type-options
- Runtime security header not set: x-dns-prefetch-control
- Runtime security header not set: x-frame-options
- Runtime security header not set: x-permitted-cross-domain-policies
- Dead file (~12 LoC) src/data/dao/notification/notification.dao.container.ts
- Dead file (~12 LoC) src/domain/auth/services/auth.service.container.ts
- Dead file (~12 LoC) src/domain/error/error.types.ts
- Dead file (~12 LoC) src/domain/error/services/error.service.container.ts
- Dead file (~12 LoC) src/domain/route/route.constants.ts
- Dead file (~12 LoC) src/domain/route/services/route.service.container.ts
- Dead file (~3 LoC) src/domain/auth/auth.types.ts
- Dead file (~3 LoC) src/domain/auth/index.ts
- Dead file (~3 LoC) src/domain/error/index.ts
- Dead file (~3 LoC) src/domain/notification/index.ts
- REDACTED
- REDACTED
- REDACTED
- Dead file (~13 LoC) src/data/dto/auth/auth-token.dto.ts
- Dead file (~13 LoC) src/data/repositories/auth/auth.repo.container.ts
- Dead file (~13 LoC) src/domain/notification/services/notification.service.container.ts
- Dead file (~10 LoC) src/data/repositories/endpoints.ts
- Dead file (~10 LoC) src/domain/route/services/route.service.impl.ts
- Dead file (~10 LoC) src/presentation/mobile/index.tsx
- Dead file (~9 LoC) src/data/repositories/auth/auth.repo.response.ts
- Dead file (~9 LoC) src/data/repositories/auth/token-axios/token-axios.container.ts
- Dead file (~9 LoC) src/domain/notification/services/notification.service.ts
- Dead file (~6 LoC) src/core/http/endpoint/endpoint.types.ts
- Dead file (~6 LoC) src/domain/auth/entities/auth-form-fields.entity.ts
- Dead file (~6 LoC) src/domain/error/services/error.service.ts
- Container process runs as root: nginx
- Container process runs as root: nginx-proxy
- REDACTED
- REDACTED
- Dead file (~36 LoC) src/data/repositories/auth/token-axios/token-axios.adapter.ts
- Dead file (~36 LoC) src/domain/notification/entities/notification.entity.ts
- Dead file (~22 LoC) src/data/dao/notification/notification.dao.impl.ts
- Dead file (~22 LoC) src/domain/date/entities/date.entity.ts
- Dead file (~5 LoC) src/data/repositories/auth/auth.repo.ts
- Dead file (~5 LoC) src/domain/auth/services/auth.service.ts
- WCAG 3.1.1 reproducibly failed in a rendered surface
- Test reliability not measured — JavaScript/TypeScript suite install refused the lockfile
- index.default.transform (cognitive 16) setup/vite/plugins/react-svg/index.ts:53
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- End-of-life runtime: Node.js 20 package.json:9
- Coverage not measured — JavaScript/TypeScript suite
- Sync-over-async blocking setup/vite/plugins/react-svg/index.ts:71
- Duplicated block (43 lines × 2 locations) src/core/adapters/local-storage/local-storage.adapter.ts:4
- Duplicated block (20 lines × 2 locations) setup/plopjs/entity.ts:37
- Duplicated block (17 lines × 2 locations) setup/plopjs/entity.ts:68
- Duplicated block (10 lines × 2 locations) src/core/adapters/axios/axios.adapter.ts:73
- Duplicated block (9 lines × 2 locations) REDACTED:1
- Boundary violation [package:third-party-deep-import] src/containers/config.ts:4
- Dead file (~46 LoC) src/domain/notification/services/notification.service.impl.ts
- Dead file (~39 LoC) src/domain/error/entities/error.entity.ts
- Dead file (~37 LoC) src/domain/route/entities/route.entity.ts
- Dead file (~29 LoC) src/data/repositories/auth/auth.repo.impl.ts
- Dead file (~24 LoC) src/domain/auth/entities/auth-token.entity.ts
- Dead file (~23 LoC) src/domain/error/services/error.service.impl.ts
- Dead file (~19 LoC) src/core/http/endpoint/endpoint.ts
- Dead file (~14 LoC) src/domain/auth/services/auth.service.impl.ts
- Dead file (~8 LoC) src/domain/notification/notification.types.ts
- Dead file (~7 LoC) src/data/dao/notification/notification.dao.ts
- Dead file (~4 LoC) src/domain/date/date.types.ts
- Unlisted import '@jest/types' setup/jest/config.ts:1
- Unused dependency '@commitlint/config-conventional'
- Unused dependency 'ahooks'
- Unused dependency 'i18next-resources-to-backend'
Minor — 27 finding(s)
- Console output used as the logging channel src/presentation/shared/components/ioc/hooks/injection.hook.ts:12
- Console output used as the logging channel src/core/utils/app-version.util.ts:4
- Console output used as the logging channel src/core/adapters/logger/logger.adapter.ts:12
- Console output used as the logging channel src/core/adapters/logger/logger.adapter.ts:20
- Console output used as the logging channel src/core/adapters/logger/logger.adapter.ts:29
- Console output used as the logging channel src/core/adapters/logger/logger.adapter.ts:38
- Console output used as the logging channel setup/vite/env.ts:25
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned file eslint.config.js:1
- Orphaned file src/core/adapters/axios/axios.adapter.ts:1
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- README/code drift README.md:59
- No SAST REDACTED:2
- No dependency-update automation package.json:39
- No rollback/health safety
- No changelog
- No security response headers detected REDACTED:1
- Strict null checking is not enabled everywhere the repository type-checks
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-13e00730a2e242ceb28df19d7da25361/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-13e00730a2e242ceb28df19d7da25361/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 14 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 45 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |