Executive summary
4lessandrodev/finance-project-ddd 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 encryption of stored data, no key vault and no enforced HTTPS, and 58 of the dependencies have a known vulnerability. It scores 46 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 38, is the weakest lens and counts most in the score. The best first step for the work it takes is adding a reporting contact to the security policy, worth about 3 points. Encrypting the sensitive stored data and keeping its keys in a vault would lift Security and Compliance itself, worth about 6 points. Raising Security and Compliance to 70 would lift the score to about 52.
Seventy-eight known security holes in the packages the code depends on can be used by attackers. Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages and pinning each tool to an exact version would close both risks. The four loops of files that import each other need breaking.
The product code is 4,864 lines, about €8,700 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Security and Compliance rose from 38 to 70, the lowest score rated Strong, the score would rise from 46 to about 52.
New since the last survey: 5 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 26 findings
- License Compliance · Banned license: ua-parser-js package.json
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h2 to h5 public/index.html
- Page structure · Heading level jumps from h1 to h3 views/index.ejs
Rebuild cost: about €8,700 · Estimate
| Cost to rebuild | €2,900 to €15,000, for 48 to 153 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 46. 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: 4,864 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 budget-box.domain.interfaces.budget-box_repository_interface | 2 budget-box.domain.reason_domain-entity | 3 budget-box.infra.services.queries.budget-box-query_interface | 4 shared.domain.budget-box-connection_interface | 5 shared.interfaces.domain-service_interface | 6 shared.interfaces.transaction-model_interface | 7 shared.interfaces.user-model_interface | 8 transaction.domain.interfaces.transaction_repository_interface | 9 transaction.domain.transaction-calculations_value-object | 10 transaction.domain.transaction_aggregate | 11 transaction.infra.services.queries.transaction-query_interface | 12 user.domain.interfaces.user_repository_interface | 13 budget-box.domain.budget-box_aggregate | 14 budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service | 15 shared.domain.update-budget-box-balance_domain-service | 16 shared.interfaces.budget-box-model_interface | 17 transaction.domain.services.can-create-benefit_proxy | 18 transaction.domain.services.create-single-calculation_domain-service | 19 transaction.infra.repo.transaction_mapper | 20 user.application.use-cases.get-user-by-id.get-user-by-id_use-case | 21 user.application.use-cases.signin.signin_use-case | 22 user.infra.repo.user_repository | 23 budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case | 24 budget-box.domain.services.can-change-budget-box-percentage_domain-service | 25 budget-box.infra.repo.budget-box_mapper | 26 shared.domain.can-create-transaction_domain-service | 27 transaction.application.use-cases.balance-transference.balance-transference_use-case | 28 transaction.application.use-cases.create-expense.create-expense_use-case | 29 transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case | 30 transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case | 31 transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case | 32 transaction.domain.services.can-create-expense_proxy | 33 transaction.infra.repo.transaction_repository | 34 user.infra.user_service | 35 budget-box.infra.budget-box_service | 36 budget-box.infra.repo.budget-box_repository | 37 transaction.infra.transaction_service | 38 user.infra.resolver.user_resolver | 39 budget-box.infra.resolver.budget-box_resolver | 40 transaction.infra.resolver.transaction_resolver |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 budget-box.domain.interfaces.budget-box_repository_interface | ||||||||||||||||||||||||||||||||||||||||
| 2 budget-box.domain.reason_domain-entity | ||||||||||||||||||||||||||||||||||||||||
| 3 budget-box.infra.services.queries.budget-box-query_interface | ||||||||||||||||||||||||||||||||||||||||
| 4 shared.domain.budget-box-connection_interface | ||||||||||||||||||||||||||||||||||||||||
| 5 shared.interfaces.domain-service_interface | ||||||||||||||||||||||||||||||||||||||||
| 6 shared.interfaces.transaction-model_interface | ||||||||||||||||||||||||||||||||||||||||
| 7 shared.interfaces.user-model_interface | ||||||||||||||||||||||||||||||||||||||||
| 8 transaction.domain.interfaces.transaction_repository_interface | ||||||||||||||||||||||||||||||||||||||||
| 9 transaction.domain.transaction-calculations_value-object | ||||||||||||||||||||||||||||||||||||||||
| 10 transaction.domain.transaction_aggregate | ||||||||||||||||||||||||||||||||||||||||
| 11 transaction.infra.services.queries.transaction-query_interface | ||||||||||||||||||||||||||||||||||||||||
| 12 user.domain.interfaces.user_repository_interface | ||||||||||||||||||||||||||||||||||||||||
| 13 budget-box.domain.budget-box_aggregate | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 shared.domain.update-budget-box-balance_domain-service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 shared.interfaces.budget-box-model_interface | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 transaction.domain.services.can-create-benefit_proxy | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 transaction.domain.services.create-single-calculation_domain-service | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 transaction.infra.repo.transaction_mapper | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 user.application.use-cases.get-user-by-id.get-user-by-id_use-case | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 user.application.use-cases.signin.signin_use-case | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 user.infra.repo.user_repository | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 budget-box.domain.services.can-change-budget-box-percentage_domain-service | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 budget-box.infra.repo.budget-box_mapper | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 shared.domain.can-create-transaction_domain-service | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 transaction.application.use-cases.balance-transference.balance-transference_use-case | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 28 transaction.application.use-cases.create-expense.create-expense_use-case | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 transaction.domain.services.can-create-expense_proxy | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 transaction.infra.repo.transaction_repository | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 user.infra.user_service | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 budget-box.infra.budget-box_service | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 budget-box.infra.repo.budget-box_repository | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 transaction.infra.transaction_service | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 38 user.infra.resolver.user_resolver | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 budget-box.infra.resolver.budget-box_resolver | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 transaction.infra.resolver.transaction_resolver | 1 | 1 |
13→2 budget-box.domain.budget-box_aggregate uses budget-box.domain.reason_domain-entity✕
- Connections
- 1 pair of types, where a type in budget-box.domain.budget-box_aggregate uses a type in budget-box.domain.reason_domain-entity.
- The types involved
src.modules.budget-box.domain.budget-box_aggregate.BudgetBoxAggregate→src.modules.budget-box.domain.reason_domain-entity.ReasonDomainEntity
- Direction
- budget-box.domain.budget-box_aggregate uses budget-box.domain.reason_domain-entity, so a change to budget-box.domain.reason_domain-entity can break budget-box.domain.budget-box_aggregate, while a change to budget-box.domain.budget-box_aggregate can't break budget-box.domain.reason_domain-entity.
- Position
- Below the diagonal: budget-box.domain.budget-box_aggregate uses a module listed above it, which is the healthy direction.
14→3 budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service uses budget-box.infra.services.queries.budget-box-query_interface✕
- Connections
- 1 pair of types, where a type in budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service uses a type in budget-box.infra.services.queries.budget-box-query_interface.
- The types involved
src.modules.budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.CanAllocatePercentageToBudgetBoxDomainService→src.modules.budget-box.infra.services.queries.budget-box-query_interface.IBudgetBoxQueryService
- Direction
- budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service uses budget-box.infra.services.queries.budget-box-query_interface, so a change to budget-box.infra.services.queries.budget-box-query_interface can break budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service, while a change to budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service can't break budget-box.infra.services.queries.budget-box-query_interface.
- Position
- Below the diagonal: budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service uses a module listed above it, which is the healthy direction.
14→5 budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service uses shared.interfaces.domain-service_interface✕
- Connections
- 1 pair of types, where a type in budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service uses a type in shared.interfaces.domain-service_interface.
- The types involved
src.modules.budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.CanAllocatePercentageToBudgetBoxDomainService→src.modules.shared.interfaces.domain-service_interface.IDomainService
- Direction
- budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service uses shared.interfaces.domain-service_interface, so a change to shared.interfaces.domain-service_interface can break budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service, while a change to budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service can't break shared.interfaces.domain-service_interface.
- Position
- Below the diagonal: budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service uses a module listed above it, which is the healthy direction.
15→4 shared.domain.update-budget-box-balance_domain-service uses shared.domain.budget-box-connection_interface✕
- Connections
- 1 pair of types, where a type in shared.domain.update-budget-box-balance_domain-service uses a type in shared.domain.budget-box-connection_interface.
- The types involved
src.modules.shared.domain.update-budget-box-balance_domain-service.UpdateBudgetBoxBalanceDomainService→src.modules.shared.domain.budget-box-connection_interface.IBudgetBoxConnection
- Direction
- shared.domain.update-budget-box-balance_domain-service uses shared.domain.budget-box-connection_interface, so a change to shared.domain.budget-box-connection_interface can break shared.domain.update-budget-box-balance_domain-service, while a change to shared.domain.update-budget-box-balance_domain-service can't break shared.domain.budget-box-connection_interface.
- Position
- Below the diagonal: shared.domain.update-budget-box-balance_domain-service uses a module listed above it, which is the healthy direction.
15→5 shared.domain.update-budget-box-balance_domain-service uses shared.interfaces.domain-service_interface✕
- Connections
- 1 pair of types, where a type in shared.domain.update-budget-box-balance_domain-service uses a type in shared.interfaces.domain-service_interface.
- The types involved
src.modules.shared.domain.update-budget-box-balance_domain-service.UpdateBudgetBoxBalanceDomainService→src.modules.shared.interfaces.domain-service_interface.IDomainService
- Direction
- shared.domain.update-budget-box-balance_domain-service uses shared.interfaces.domain-service_interface, so a change to shared.interfaces.domain-service_interface can break shared.domain.update-budget-box-balance_domain-service, while a change to shared.domain.update-budget-box-balance_domain-service can't break shared.interfaces.domain-service_interface.
- Position
- Below the diagonal: shared.domain.update-budget-box-balance_domain-service uses a module listed above it, which is the healthy direction.
16→6 shared.interfaces.budget-box-model_interface uses shared.interfaces.transaction-model_interface✕
- Connections
- 1 pair of types, where a type in shared.interfaces.budget-box-model_interface uses a type in shared.interfaces.transaction-model_interface.
- The types involved
src.modules.shared.interfaces.budget-box-model_interface.IBudgetBox→src.modules.shared.interfaces.transaction-model_interface.ICurrency
- Direction
- shared.interfaces.budget-box-model_interface uses shared.interfaces.transaction-model_interface, so a change to shared.interfaces.transaction-model_interface can break shared.interfaces.budget-box-model_interface, while a change to shared.interfaces.budget-box-model_interface can't break shared.interfaces.transaction-model_interface.
- Position
- Below the diagonal: shared.interfaces.budget-box-model_interface uses a module listed above it, which is the healthy direction.
17→4 transaction.domain.services.can-create-benefit_proxy uses shared.domain.budget-box-connection_interface✕
- Connections
- 1 pair of types, where a type in transaction.domain.services.can-create-benefit_proxy uses a type in shared.domain.budget-box-connection_interface.
- The types involved
src.modules.transaction.domain.services.can-create-benefit_proxy.CanCreateBenefit→src.modules.shared.domain.budget-box-connection_interface.IBudgetBoxConnection
- Direction
- transaction.domain.services.can-create-benefit_proxy uses shared.domain.budget-box-connection_interface, so a change to shared.domain.budget-box-connection_interface can break transaction.domain.services.can-create-benefit_proxy, while a change to transaction.domain.services.can-create-benefit_proxy can't break shared.domain.budget-box-connection_interface.
- Position
- Below the diagonal: transaction.domain.services.can-create-benefit_proxy uses a module listed above it, which is the healthy direction.
17→5 transaction.domain.services.can-create-benefit_proxy uses shared.interfaces.domain-service_interface✕
- Connections
- 1 pair of types, where a type in transaction.domain.services.can-create-benefit_proxy uses a type in shared.interfaces.domain-service_interface.
- The types involved
src.modules.transaction.domain.services.can-create-benefit_proxy.CanCreateBenefit→src.modules.shared.interfaces.domain-service_interface.IDomainService
- Direction
- transaction.domain.services.can-create-benefit_proxy uses shared.interfaces.domain-service_interface, so a change to shared.interfaces.domain-service_interface can break transaction.domain.services.can-create-benefit_proxy, while a change to transaction.domain.services.can-create-benefit_proxy can't break shared.interfaces.domain-service_interface.
- Position
- Below the diagonal: transaction.domain.services.can-create-benefit_proxy uses a module listed above it, which is the healthy direction.
18→4 transaction.domain.services.create-single-calculation_domain-service uses shared.domain.budget-box-connection_interface✕
- Connections
- 1 pair of types, where a type in transaction.domain.services.create-single-calculation_domain-service uses a type in shared.domain.budget-box-connection_interface.
- The types involved
src.modules.transaction.domain.services.create-single-calculation_domain-service.CreateSingleCalculationDomainService→src.modules.shared.domain.budget-box-connection_interface.IBudgetBoxConnection
- Direction
- transaction.domain.services.create-single-calculation_domain-service uses shared.domain.budget-box-connection_interface, so a change to shared.domain.budget-box-connection_interface can break transaction.domain.services.create-single-calculation_domain-service, while a change to transaction.domain.services.create-single-calculation_domain-service can't break shared.domain.budget-box-connection_interface.
- Position
- Below the diagonal: transaction.domain.services.create-single-calculation_domain-service uses a module listed above it, which is the healthy direction.
18→5 transaction.domain.services.create-single-calculation_domain-service uses shared.interfaces.domain-service_interface✕
- Connections
- 1 pair of types, where a type in transaction.domain.services.create-single-calculation_domain-service uses a type in shared.interfaces.domain-service_interface.
- The types involved
src.modules.transaction.domain.services.create-single-calculation_domain-service.CreateSingleCalculationDomainService→src.modules.shared.interfaces.domain-service_interface.IDomainService
- Direction
- transaction.domain.services.create-single-calculation_domain-service uses shared.interfaces.domain-service_interface, so a change to shared.interfaces.domain-service_interface can break transaction.domain.services.create-single-calculation_domain-service, while a change to transaction.domain.services.create-single-calculation_domain-service can't break shared.interfaces.domain-service_interface.
- Position
- Below the diagonal: transaction.domain.services.create-single-calculation_domain-service uses a module listed above it, which is the healthy direction.
18→9 transaction.domain.services.create-single-calculation_domain-service uses transaction.domain.transaction-calculations_value-object✕
- Connections
- 1 pair of types, where a type in transaction.domain.services.create-single-calculation_domain-service uses a type in transaction.domain.transaction-calculations_value-object.
- The types involved
src.modules.transaction.domain.services.create-single-calculation_domain-service.CreateSingleCalculationDomainService→src.modules.transaction.domain.transaction-calculations_value-object.TransactionCalculationValueObject
- Direction
- transaction.domain.services.create-single-calculation_domain-service uses transaction.domain.transaction-calculations_value-object, so a change to transaction.domain.transaction-calculations_value-object can break transaction.domain.services.create-single-calculation_domain-service, while a change to transaction.domain.services.create-single-calculation_domain-service can't break transaction.domain.transaction-calculations_value-object.
- Position
- Below the diagonal: transaction.domain.services.create-single-calculation_domain-service uses a module listed above it, which is the healthy direction.
19→6 transaction.infra.repo.transaction_mapper uses shared.interfaces.transaction-model_interface✕
- Connections
- 2 pairs of types, where a type in transaction.infra.repo.transaction_mapper uses a type in shared.interfaces.transaction-model_interface.
- The types involved
src.modules.transaction.infra.repo.transaction_mapper.TransactionToDomainMapper→src.modules.shared.interfaces.transaction-model_interface.ICalculationsrc.modules.transaction.infra.repo.transaction_mapper.TransactionToDomainMapper→src.modules.shared.interfaces.transaction-model_interface.ITransaction
- Direction
- transaction.infra.repo.transaction_mapper uses shared.interfaces.transaction-model_interface, so a change to shared.interfaces.transaction-model_interface can break transaction.infra.repo.transaction_mapper, while a change to transaction.infra.repo.transaction_mapper can't break shared.interfaces.transaction-model_interface.
- Position
- Below the diagonal: transaction.infra.repo.transaction_mapper uses a module listed above it, which is the healthy direction.
19→9 transaction.infra.repo.transaction_mapper uses transaction.domain.transaction-calculations_value-object✕
- Connections
- 1 pair of types, where a type in transaction.infra.repo.transaction_mapper uses a type in transaction.domain.transaction-calculations_value-object.
- The types involved
src.modules.transaction.infra.repo.transaction_mapper.TransactionToDomainMapper→src.modules.transaction.domain.transaction-calculations_value-object.TransactionCalculationValueObject
- Direction
- transaction.infra.repo.transaction_mapper uses transaction.domain.transaction-calculations_value-object, so a change to transaction.domain.transaction-calculations_value-object can break transaction.infra.repo.transaction_mapper, while a change to transaction.infra.repo.transaction_mapper can't break transaction.domain.transaction-calculations_value-object.
- Position
- Below the diagonal: transaction.infra.repo.transaction_mapper uses a module listed above it, which is the healthy direction.
19→10 transaction.infra.repo.transaction_mapper uses transaction.domain.transaction_aggregate✕
- Connections
- 1 pair of types, where a type in transaction.infra.repo.transaction_mapper uses a type in transaction.domain.transaction_aggregate.
- The types involved
src.modules.transaction.infra.repo.transaction_mapper.TransactionToDomainMapper→src.modules.transaction.domain.transaction_aggregate.TransactionAggregate
- Direction
- transaction.infra.repo.transaction_mapper uses transaction.domain.transaction_aggregate, so a change to transaction.domain.transaction_aggregate can break transaction.infra.repo.transaction_mapper, while a change to transaction.infra.repo.transaction_mapper can't break transaction.domain.transaction_aggregate.
- Position
- Below the diagonal: transaction.infra.repo.transaction_mapper uses a module listed above it, which is the healthy direction.
20→7 user.application.use-cases.get-user-by-id.get-user-by-id_use-case uses shared.interfaces.user-model_interface✕
- Connections
- 1 pair of types, where a type in user.application.use-cases.get-user-by-id.get-user-by-id_use-case uses a type in shared.interfaces.user-model_interface.
- The types involved
src.modules.user.application.use-cases.get-user-by-id.get-user-by-id_use-case.GetUserByIdUseCase→src.modules.shared.interfaces.user-model_interface.IUser
- Direction
- user.application.use-cases.get-user-by-id.get-user-by-id_use-case uses shared.interfaces.user-model_interface, so a change to shared.interfaces.user-model_interface can break user.application.use-cases.get-user-by-id.get-user-by-id_use-case, while a change to user.application.use-cases.get-user-by-id.get-user-by-id_use-case can't break shared.interfaces.user-model_interface.
- Position
- Below the diagonal: user.application.use-cases.get-user-by-id.get-user-by-id_use-case uses a module listed above it, which is the healthy direction.
21→12 user.application.use-cases.signin.signin_use-case uses user.domain.interfaces.user_repository_interface✕
- Connections
- 1 pair of types, where a type in user.application.use-cases.signin.signin_use-case uses a type in user.domain.interfaces.user_repository_interface.
- The types involved
src.modules.user.application.use-cases.signin.signin_use-case.SigninUseCase→src.modules.user.domain.interfaces.user_repository_interface.IUserRepository
- Direction
- user.application.use-cases.signin.signin_use-case uses user.domain.interfaces.user_repository_interface, so a change to user.domain.interfaces.user_repository_interface can break user.application.use-cases.signin.signin_use-case, while a change to user.application.use-cases.signin.signin_use-case can't break user.domain.interfaces.user_repository_interface.
- Position
- Below the diagonal: user.application.use-cases.signin.signin_use-case uses a module listed above it, which is the healthy direction.
22→11 user.infra.repo.user_repository uses transaction.infra.services.queries.transaction-query_interface✕
- Connections
- 1 pair of types, where a type in user.infra.repo.user_repository uses a type in transaction.infra.services.queries.transaction-query_interface.
- The types involved
src.modules.user.infra.repo.user_repository.UserRepository→src.modules.transaction.infra.services.queries.transaction-query_interface.Filter
- Direction
- user.infra.repo.user_repository uses transaction.infra.services.queries.transaction-query_interface, so a change to transaction.infra.services.queries.transaction-query_interface can break user.infra.repo.user_repository, while a change to user.infra.repo.user_repository can't break transaction.infra.services.queries.transaction-query_interface.
- Position
- Below the diagonal: user.infra.repo.user_repository uses a module listed above it, which is the healthy direction.
22→12 user.infra.repo.user_repository uses user.domain.interfaces.user_repository_interface✕
- Connections
- 1 pair of types, where a type in user.infra.repo.user_repository uses a type in user.domain.interfaces.user_repository_interface.
- The types involved
src.modules.user.infra.repo.user_repository.UserRepository→src.modules.user.domain.interfaces.user_repository_interface.IUserRepository
- Direction
- user.infra.repo.user_repository uses user.domain.interfaces.user_repository_interface, so a change to user.domain.interfaces.user_repository_interface can break user.infra.repo.user_repository, while a change to user.infra.repo.user_repository can't break user.domain.interfaces.user_repository_interface.
- Position
- Below the diagonal: user.infra.repo.user_repository uses a module listed above it, which is the healthy direction.
23→3 budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case uses budget-box.infra.services.queries.budget-box-query_interface✕
- Connections
- 1 pair of types, where a type in budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case uses a type in budget-box.infra.services.queries.budget-box-query_interface.
- The types involved
src.modules.budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case.GetBudgetBoxByIdUseCase→src.modules.budget-box.infra.services.queries.budget-box-query_interface.IBudgetBoxQueryService
- Direction
- budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case uses budget-box.infra.services.queries.budget-box-query_interface, so a change to budget-box.infra.services.queries.budget-box-query_interface can break budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case, while a change to budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case can't break budget-box.infra.services.queries.budget-box-query_interface.
- Position
- Below the diagonal: budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case uses a module listed above it, which is the healthy direction.
23→14 budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case uses budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service✕
- Connections
- 1 pair of types, where a type in budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case uses a type in budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.
- The types involved
src.modules.budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case.GetBudgetBoxByIdUseCase→src.modules.budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.Dto
- Direction
- budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case uses budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service, so a change to budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service can break budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case, while a change to budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case can't break budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.
- Position
- Below the diagonal: budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case uses a module listed above it, which is the healthy direction.
23→16 budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case uses shared.interfaces.budget-box-model_interface✕
- Connections
- 1 pair of types, where a type in budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case uses a type in shared.interfaces.budget-box-model_interface.
- The types involved
src.modules.budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case.GetBudgetBoxByIdUseCase→src.modules.shared.interfaces.budget-box-model_interface.IBudgetBox
- Direction
- budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case uses shared.interfaces.budget-box-model_interface, so a change to shared.interfaces.budget-box-model_interface can break budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case, while a change to budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case can't break shared.interfaces.budget-box-model_interface.
- Position
- Below the diagonal: budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case uses a module listed above it, which is the healthy direction.
24→3 budget-box.domain.services.can-change-budget-box-percentage_domain-service uses budget-box.infra.services.queries.budget-box-query_interface✕
- Connections
- 1 pair of types, where a type in budget-box.domain.services.can-change-budget-box-percentage_domain-service uses a type in budget-box.infra.services.queries.budget-box-query_interface.
- The types involved
src.modules.budget-box.domain.services.can-change-budget-box-percentage_domain-service.CanChangeBudgetBoxPercentageDomainService→src.modules.budget-box.infra.services.queries.budget-box-query_interface.IBudgetBoxQueryService
- Direction
- budget-box.domain.services.can-change-budget-box-percentage_domain-service uses budget-box.infra.services.queries.budget-box-query_interface, so a change to budget-box.infra.services.queries.budget-box-query_interface can break budget-box.domain.services.can-change-budget-box-percentage_domain-service, while a change to budget-box.domain.services.can-change-budget-box-percentage_domain-service can't break budget-box.infra.services.queries.budget-box-query_interface.
- Position
- Below the diagonal: budget-box.domain.services.can-change-budget-box-percentage_domain-service uses a module listed above it, which is the healthy direction.
24→5 budget-box.domain.services.can-change-budget-box-percentage_domain-service uses shared.interfaces.domain-service_interface✕
- Connections
- 1 pair of types, where a type in budget-box.domain.services.can-change-budget-box-percentage_domain-service uses a type in shared.interfaces.domain-service_interface.
- The types involved
src.modules.budget-box.domain.services.can-change-budget-box-percentage_domain-service.CanChangeBudgetBoxPercentageDomainService→src.modules.shared.interfaces.domain-service_interface.IDomainService
- Direction
- budget-box.domain.services.can-change-budget-box-percentage_domain-service uses shared.interfaces.domain-service_interface, so a change to shared.interfaces.domain-service_interface can break budget-box.domain.services.can-change-budget-box-percentage_domain-service, while a change to budget-box.domain.services.can-change-budget-box-percentage_domain-service can't break shared.interfaces.domain-service_interface.
- Position
- Below the diagonal: budget-box.domain.services.can-change-budget-box-percentage_domain-service uses a module listed above it, which is the healthy direction.
24→14 budget-box.domain.services.can-change-budget-box-percentage_domain-service uses budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service✕
- Connections
- 1 pair of types, where a type in budget-box.domain.services.can-change-budget-box-percentage_domain-service uses a type in budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.
- The types involved
src.modules.budget-box.domain.services.can-change-budget-box-percentage_domain-service.CanChangeBudgetBoxPercentageDomainService→src.modules.budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.Dto
- Direction
- budget-box.domain.services.can-change-budget-box-percentage_domain-service uses budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service, so a change to budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service can break budget-box.domain.services.can-change-budget-box-percentage_domain-service, while a change to budget-box.domain.services.can-change-budget-box-percentage_domain-service can't break budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.
- Position
- Below the diagonal: budget-box.domain.services.can-change-budget-box-percentage_domain-service uses a module listed above it, which is the healthy direction.
25→2 budget-box.infra.repo.budget-box_mapper uses budget-box.domain.reason_domain-entity✕
- Connections
- 1 pair of types, where a type in budget-box.infra.repo.budget-box_mapper uses a type in budget-box.domain.reason_domain-entity.
- The types involved
src.modules.budget-box.infra.repo.budget-box_mapper.BudgetBoxToDomainMapper→src.modules.budget-box.domain.reason_domain-entity.ReasonDomainEntity
- Direction
- budget-box.infra.repo.budget-box_mapper uses budget-box.domain.reason_domain-entity, so a change to budget-box.domain.reason_domain-entity can break budget-box.infra.repo.budget-box_mapper, while a change to budget-box.infra.repo.budget-box_mapper can't break budget-box.domain.reason_domain-entity.
- Position
- Below the diagonal: budget-box.infra.repo.budget-box_mapper uses a module listed above it, which is the healthy direction.
25→13 budget-box.infra.repo.budget-box_mapper uses budget-box.domain.budget-box_aggregate✕
- Connections
- 1 pair of types, where a type in budget-box.infra.repo.budget-box_mapper uses a type in budget-box.domain.budget-box_aggregate.
- The types involved
src.modules.budget-box.infra.repo.budget-box_mapper.BudgetBoxToDomainMapper→src.modules.budget-box.domain.budget-box_aggregate.BudgetBoxAggregate
- Direction
- budget-box.infra.repo.budget-box_mapper uses budget-box.domain.budget-box_aggregate, so a change to budget-box.domain.budget-box_aggregate can break budget-box.infra.repo.budget-box_mapper, while a change to budget-box.infra.repo.budget-box_mapper can't break budget-box.domain.budget-box_aggregate.
- Position
- Below the diagonal: budget-box.infra.repo.budget-box_mapper uses a module listed above it, which is the healthy direction.
25→16 budget-box.infra.repo.budget-box_mapper uses shared.interfaces.budget-box-model_interface✕
- Connections
- 1 pair of types, where a type in budget-box.infra.repo.budget-box_mapper uses a type in shared.interfaces.budget-box-model_interface.
- The types involved
src.modules.budget-box.infra.repo.budget-box_mapper.BudgetBoxToDomainMapper→src.modules.shared.interfaces.budget-box-model_interface.IBudgetBox
- Direction
- budget-box.infra.repo.budget-box_mapper uses shared.interfaces.budget-box-model_interface, so a change to shared.interfaces.budget-box-model_interface can break budget-box.infra.repo.budget-box_mapper, while a change to budget-box.infra.repo.budget-box_mapper can't break shared.interfaces.budget-box-model_interface.
- Position
- Below the diagonal: budget-box.infra.repo.budget-box_mapper uses a module listed above it, which is the healthy direction.
26→4 shared.domain.can-create-transaction_domain-service uses shared.domain.budget-box-connection_interface✕
- Connections
- 1 pair of types, where a type in shared.domain.can-create-transaction_domain-service uses a type in shared.domain.budget-box-connection_interface.
- The types involved
src.modules.shared.domain.can-create-transaction_domain-service.CanCreateTransactionDomainService→src.modules.shared.domain.budget-box-connection_interface.IBudgetBoxConnection
- Direction
- shared.domain.can-create-transaction_domain-service uses shared.domain.budget-box-connection_interface, so a change to shared.domain.budget-box-connection_interface can break shared.domain.can-create-transaction_domain-service, while a change to shared.domain.can-create-transaction_domain-service can't break shared.domain.budget-box-connection_interface.
- Position
- Below the diagonal: shared.domain.can-create-transaction_domain-service uses a module listed above it, which is the healthy direction.
26→5 shared.domain.can-create-transaction_domain-service uses shared.interfaces.domain-service_interface✕
- Connections
- 1 pair of types, where a type in shared.domain.can-create-transaction_domain-service uses a type in shared.interfaces.domain-service_interface.
- The types involved
src.modules.shared.domain.can-create-transaction_domain-service.CanCreateTransactionDomainService→src.modules.shared.interfaces.domain-service_interface.IDomainService
- Direction
- shared.domain.can-create-transaction_domain-service uses shared.interfaces.domain-service_interface, so a change to shared.interfaces.domain-service_interface can break shared.domain.can-create-transaction_domain-service, while a change to shared.domain.can-create-transaction_domain-service can't break shared.interfaces.domain-service_interface.
- Position
- Below the diagonal: shared.domain.can-create-transaction_domain-service uses a module listed above it, which is the healthy direction.
26→14 shared.domain.can-create-transaction_domain-service uses budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service✕
- Connections
- 1 pair of types, where a type in shared.domain.can-create-transaction_domain-service uses a type in budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.
- The types involved
src.modules.shared.domain.can-create-transaction_domain-service.CanCreateTransactionDomainService→src.modules.budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.Dto
- Direction
- shared.domain.can-create-transaction_domain-service uses budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service, so a change to budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service can break shared.domain.can-create-transaction_domain-service, while a change to shared.domain.can-create-transaction_domain-service can't break budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.
- Position
- Below the diagonal: shared.domain.can-create-transaction_domain-service uses a module listed above it, which is the healthy direction.
27→5 transaction.application.use-cases.balance-transference.balance-transference_use-case uses shared.interfaces.domain-service_interface✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.balance-transference.balance-transference_use-case uses a type in shared.interfaces.domain-service_interface.
- The types involved
src.modules.transaction.application.use-cases.balance-transference.balance-transference_use-case.BalanceTransferenceUseCase→src.modules.shared.interfaces.domain-service_interface.IDomainService
- Direction
- transaction.application.use-cases.balance-transference.balance-transference_use-case uses shared.interfaces.domain-service_interface, so a change to shared.interfaces.domain-service_interface can break transaction.application.use-cases.balance-transference.balance-transference_use-case, while a change to transaction.application.use-cases.balance-transference.balance-transference_use-case can't break shared.interfaces.domain-service_interface.
- Position
- Below the diagonal: transaction.application.use-cases.balance-transference.balance-transference_use-case uses a module listed above it, which is the healthy direction.
27→8 transaction.application.use-cases.balance-transference.balance-transference_use-case uses transaction.domain.interfaces.transaction_repository_interface✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.balance-transference.balance-transference_use-case uses a type in transaction.domain.interfaces.transaction_repository_interface.
- The types involved
src.modules.transaction.application.use-cases.balance-transference.balance-transference_use-case.BalanceTransferenceUseCase→src.modules.transaction.domain.interfaces.transaction_repository_interface.ITransactionRepository
- Direction
- transaction.application.use-cases.balance-transference.balance-transference_use-case uses transaction.domain.interfaces.transaction_repository_interface, so a change to transaction.domain.interfaces.transaction_repository_interface can break transaction.application.use-cases.balance-transference.balance-transference_use-case, while a change to transaction.application.use-cases.balance-transference.balance-transference_use-case can't break transaction.domain.interfaces.transaction_repository_interface.
- Position
- Below the diagonal: transaction.application.use-cases.balance-transference.balance-transference_use-case uses a module listed above it, which is the healthy direction.
27→9 transaction.application.use-cases.balance-transference.balance-transference_use-case uses transaction.domain.transaction-calculations_value-object✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.balance-transference.balance-transference_use-case uses a type in transaction.domain.transaction-calculations_value-object.
- The types involved
src.modules.transaction.application.use-cases.balance-transference.balance-transference_use-case.BalanceTransferenceUseCase→src.modules.transaction.domain.transaction-calculations_value-object.TransactionCalculationValueObject
- Direction
- transaction.application.use-cases.balance-transference.balance-transference_use-case uses transaction.domain.transaction-calculations_value-object, so a change to transaction.domain.transaction-calculations_value-object can break transaction.application.use-cases.balance-transference.balance-transference_use-case, while a change to transaction.application.use-cases.balance-transference.balance-transference_use-case can't break transaction.domain.transaction-calculations_value-object.
- Position
- Below the diagonal: transaction.application.use-cases.balance-transference.balance-transference_use-case uses a module listed above it, which is the healthy direction.
27→14 transaction.application.use-cases.balance-transference.balance-transference_use-case uses budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.balance-transference.balance-transference_use-case uses a type in budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.
- The types involved
src.modules.transaction.application.use-cases.balance-transference.balance-transference_use-case.BalanceTransferenceUseCase→src.modules.budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.Dto
- Direction
- transaction.application.use-cases.balance-transference.balance-transference_use-case uses budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service, so a change to budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service can break transaction.application.use-cases.balance-transference.balance-transference_use-case, while a change to transaction.application.use-cases.balance-transference.balance-transference_use-case can't break budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.
- Position
- Below the diagonal: transaction.application.use-cases.balance-transference.balance-transference_use-case uses a module listed above it, which is the healthy direction.
27→18 transaction.application.use-cases.balance-transference.balance-transference_use-case uses transaction.domain.services.create-single-calculation_domain-service✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.balance-transference.balance-transference_use-case uses a type in transaction.domain.services.create-single-calculation_domain-service.
- The types involved
src.modules.transaction.application.use-cases.balance-transference.balance-transference_use-case.BalanceTransferenceUseCase→src.modules.transaction.domain.services.create-single-calculation_domain-service.CreateSingleCalculationDto
- Direction
- transaction.application.use-cases.balance-transference.balance-transference_use-case uses transaction.domain.services.create-single-calculation_domain-service, so a change to transaction.domain.services.create-single-calculation_domain-service can break transaction.application.use-cases.balance-transference.balance-transference_use-case, while a change to transaction.application.use-cases.balance-transference.balance-transference_use-case can't break transaction.domain.services.create-single-calculation_domain-service.
- Position
- Below the diagonal: transaction.application.use-cases.balance-transference.balance-transference_use-case uses a module listed above it, which is the healthy direction.
28→5 transaction.application.use-cases.create-expense.create-expense_use-case uses shared.interfaces.domain-service_interface✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.create-expense.create-expense_use-case uses a type in shared.interfaces.domain-service_interface.
- The types involved
src.modules.transaction.application.use-cases.create-expense.create-expense_use-case.CreateExpenseUseCase→src.modules.shared.interfaces.domain-service_interface.IDomainService
- Direction
- transaction.application.use-cases.create-expense.create-expense_use-case uses shared.interfaces.domain-service_interface, so a change to shared.interfaces.domain-service_interface can break transaction.application.use-cases.create-expense.create-expense_use-case, while a change to transaction.application.use-cases.create-expense.create-expense_use-case can't break shared.interfaces.domain-service_interface.
- Position
- Below the diagonal: transaction.application.use-cases.create-expense.create-expense_use-case uses a module listed above it, which is the healthy direction.
28→8 transaction.application.use-cases.create-expense.create-expense_use-case uses transaction.domain.interfaces.transaction_repository_interface✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.create-expense.create-expense_use-case uses a type in transaction.domain.interfaces.transaction_repository_interface.
- The types involved
src.modules.transaction.application.use-cases.create-expense.create-expense_use-case.CreateExpenseUseCase→src.modules.transaction.domain.interfaces.transaction_repository_interface.ITransactionRepository
- Direction
- transaction.application.use-cases.create-expense.create-expense_use-case uses transaction.domain.interfaces.transaction_repository_interface, so a change to transaction.domain.interfaces.transaction_repository_interface can break transaction.application.use-cases.create-expense.create-expense_use-case, while a change to transaction.application.use-cases.create-expense.create-expense_use-case can't break transaction.domain.interfaces.transaction_repository_interface.
- Position
- Below the diagonal: transaction.application.use-cases.create-expense.create-expense_use-case uses a module listed above it, which is the healthy direction.
28→9 transaction.application.use-cases.create-expense.create-expense_use-case uses transaction.domain.transaction-calculations_value-object✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.create-expense.create-expense_use-case uses a type in transaction.domain.transaction-calculations_value-object.
- The types involved
src.modules.transaction.application.use-cases.create-expense.create-expense_use-case.CreateExpenseUseCase→src.modules.transaction.domain.transaction-calculations_value-object.TransactionCalculationValueObject
- Direction
- transaction.application.use-cases.create-expense.create-expense_use-case uses transaction.domain.transaction-calculations_value-object, so a change to transaction.domain.transaction-calculations_value-object can break transaction.application.use-cases.create-expense.create-expense_use-case, while a change to transaction.application.use-cases.create-expense.create-expense_use-case can't break transaction.domain.transaction-calculations_value-object.
- Position
- Below the diagonal: transaction.application.use-cases.create-expense.create-expense_use-case uses a module listed above it, which is the healthy direction.
28→18 transaction.application.use-cases.create-expense.create-expense_use-case uses transaction.domain.services.create-single-calculation_domain-service✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.create-expense.create-expense_use-case uses a type in transaction.domain.services.create-single-calculation_domain-service.
- The types involved
src.modules.transaction.application.use-cases.create-expense.create-expense_use-case.CreateExpenseUseCase→src.modules.transaction.domain.services.create-single-calculation_domain-service.CreateSingleCalculationDto
- Direction
- transaction.application.use-cases.create-expense.create-expense_use-case uses transaction.domain.services.create-single-calculation_domain-service, so a change to transaction.domain.services.create-single-calculation_domain-service can break transaction.application.use-cases.create-expense.create-expense_use-case, while a change to transaction.application.use-cases.create-expense.create-expense_use-case can't break transaction.domain.services.create-single-calculation_domain-service.
- Position
- Below the diagonal: transaction.application.use-cases.create-expense.create-expense_use-case uses a module listed above it, which is the healthy direction.
29→6 transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case uses shared.interfaces.transaction-model_interface✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case uses a type in shared.interfaces.transaction-model_interface.
- The types involved
src.modules.transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case.GetTransactionByIdUseCase→src.modules.shared.interfaces.transaction-model_interface.ITransaction
- Direction
- transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case uses shared.interfaces.transaction-model_interface, so a change to shared.interfaces.transaction-model_interface can break transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case, while a change to transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case can't break shared.interfaces.transaction-model_interface.
- Position
- Below the diagonal: transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case uses a module listed above it, which is the healthy direction.
29→11 transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case uses transaction.infra.services.queries.transaction-query_interface✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case uses a type in transaction.infra.services.queries.transaction-query_interface.
- The types involved
src.modules.transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case.GetTransactionByIdUseCase→src.modules.transaction.infra.services.queries.transaction-query_interface.ITransactionQueryService
- Direction
- transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case uses transaction.infra.services.queries.transaction-query_interface, so a change to transaction.infra.services.queries.transaction-query_interface can break transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case, while a change to transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case can't break transaction.infra.services.queries.transaction-query_interface.
- Position
- Below the diagonal: transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case uses a module listed above it, which is the healthy direction.
29→14 transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case uses budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case uses a type in budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.
- The types involved
src.modules.transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case.GetTransactionByIdUseCase→src.modules.budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.Dto
- Direction
- transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case uses budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service, so a change to budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service can break transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case, while a change to transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case can't break budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.
- Position
- Below the diagonal: transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case uses a module listed above it, which is the healthy direction.
30→5 transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case uses shared.interfaces.domain-service_interface✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case uses a type in shared.interfaces.domain-service_interface.
- The types involved
src.modules.transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case.PercentageCapitalInflowPostingUseCase→src.modules.shared.interfaces.domain-service_interface.IDomainService
- Direction
- transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case uses shared.interfaces.domain-service_interface, so a change to shared.interfaces.domain-service_interface can break transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case, while a change to transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case can't break shared.interfaces.domain-service_interface.
- Position
- Below the diagonal: transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case uses a module listed above it, which is the healthy direction.
30→8 transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case uses transaction.domain.interfaces.transaction_repository_interface✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case uses a type in transaction.domain.interfaces.transaction_repository_interface.
- The types involved
src.modules.transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case.PercentageCapitalInflowPostingUseCase→src.modules.transaction.domain.interfaces.transaction_repository_interface.ITransactionRepository
- Direction
- transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case uses transaction.domain.interfaces.transaction_repository_interface, so a change to transaction.domain.interfaces.transaction_repository_interface can break transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case, while a change to transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case can't break transaction.domain.interfaces.transaction_repository_interface.
- Position
- Below the diagonal: transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case uses a module listed above it, which is the healthy direction.
30→14 transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case uses budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case uses a type in budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.
- The types involved
src.modules.transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case.PercentageCapitalInflowPostingUseCase→src.modules.budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.Dto
- Direction
- transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case uses budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service, so a change to budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service can break transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case, while a change to transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case can't break budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.
- Position
- Below the diagonal: transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case uses a module listed above it, which is the healthy direction.
31→5 transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case uses shared.interfaces.domain-service_interface✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case uses a type in shared.interfaces.domain-service_interface.
- The types involved
src.modules.transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case.PostingToBenefitUseCase→src.modules.shared.interfaces.domain-service_interface.IDomainService
- Direction
- transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case uses shared.interfaces.domain-service_interface, so a change to shared.interfaces.domain-service_interface can break transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case, while a change to transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case can't break shared.interfaces.domain-service_interface.
- Position
- Below the diagonal: transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case uses a module listed above it, which is the healthy direction.
31→8 transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case uses transaction.domain.interfaces.transaction_repository_interface✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case uses a type in transaction.domain.interfaces.transaction_repository_interface.
- The types involved
src.modules.transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case.PostingToBenefitUseCase→src.modules.transaction.domain.interfaces.transaction_repository_interface.ITransactionRepository
- Direction
- transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case uses transaction.domain.interfaces.transaction_repository_interface, so a change to transaction.domain.interfaces.transaction_repository_interface can break transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case, while a change to transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case can't break transaction.domain.interfaces.transaction_repository_interface.
- Position
- Below the diagonal: transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case uses a module listed above it, which is the healthy direction.
31→9 transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case uses transaction.domain.transaction-calculations_value-object✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case uses a type in transaction.domain.transaction-calculations_value-object.
- The types involved
src.modules.transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case.PostingToBenefitUseCase→src.modules.transaction.domain.transaction-calculations_value-object.TransactionCalculationValueObject
- Direction
- transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case uses transaction.domain.transaction-calculations_value-object, so a change to transaction.domain.transaction-calculations_value-object can break transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case, while a change to transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case can't break transaction.domain.transaction-calculations_value-object.
- Position
- Below the diagonal: transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case uses a module listed above it, which is the healthy direction.
31→18 transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case uses transaction.domain.services.create-single-calculation_domain-service✕
- Connections
- 1 pair of types, where a type in transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case uses a type in transaction.domain.services.create-single-calculation_domain-service.
- The types involved
src.modules.transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case.PostingToBenefitUseCase→src.modules.transaction.domain.services.create-single-calculation_domain-service.CreateSingleCalculationDto
- Direction
- transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case uses transaction.domain.services.create-single-calculation_domain-service, so a change to transaction.domain.services.create-single-calculation_domain-service can break transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case, while a change to transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case can't break transaction.domain.services.create-single-calculation_domain-service.
- Position
- Below the diagonal: transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case uses a module listed above it, which is the healthy direction.
32→4 transaction.domain.services.can-create-expense_proxy uses shared.domain.budget-box-connection_interface✕
- Connections
- 1 pair of types, where a type in transaction.domain.services.can-create-expense_proxy uses a type in shared.domain.budget-box-connection_interface.
- The types involved
src.modules.transaction.domain.services.can-create-expense_proxy.CanCreateExpense→src.modules.shared.domain.budget-box-connection_interface.IBudgetBoxConnection
- Direction
- transaction.domain.services.can-create-expense_proxy uses shared.domain.budget-box-connection_interface, so a change to shared.domain.budget-box-connection_interface can break transaction.domain.services.can-create-expense_proxy, while a change to transaction.domain.services.can-create-expense_proxy can't break shared.domain.budget-box-connection_interface.
- Position
- Below the diagonal: transaction.domain.services.can-create-expense_proxy uses a module listed above it, which is the healthy direction.
32→5 transaction.domain.services.can-create-expense_proxy uses shared.interfaces.domain-service_interface✕
- Connections
- 1 pair of types, where a type in transaction.domain.services.can-create-expense_proxy uses a type in shared.interfaces.domain-service_interface.
- The types involved
src.modules.transaction.domain.services.can-create-expense_proxy.CanCreateExpense→src.modules.shared.interfaces.domain-service_interface.IDomainService
- Direction
- transaction.domain.services.can-create-expense_proxy uses shared.interfaces.domain-service_interface, so a change to shared.interfaces.domain-service_interface can break transaction.domain.services.can-create-expense_proxy, while a change to transaction.domain.services.can-create-expense_proxy can't break shared.interfaces.domain-service_interface.
- Position
- Below the diagonal: transaction.domain.services.can-create-expense_proxy uses a module listed above it, which is the healthy direction.
32→17 transaction.domain.services.can-create-expense_proxy uses transaction.domain.services.can-create-benefit_proxy✕
- Connections
- 1 pair of types, where a type in transaction.domain.services.can-create-expense_proxy uses a type in transaction.domain.services.can-create-benefit_proxy.
- The types involved
src.modules.transaction.domain.services.can-create-expense_proxy.CanCreateExpense→src.modules.transaction.domain.services.can-create-benefit_proxy.CanCreateBenefitDto
- Direction
- transaction.domain.services.can-create-expense_proxy uses transaction.domain.services.can-create-benefit_proxy, so a change to transaction.domain.services.can-create-benefit_proxy can break transaction.domain.services.can-create-expense_proxy, while a change to transaction.domain.services.can-create-expense_proxy can't break transaction.domain.services.can-create-benefit_proxy.
- Position
- Below the diagonal: transaction.domain.services.can-create-expense_proxy uses a module listed above it, which is the healthy direction.
33→6 transaction.infra.repo.transaction_repository uses shared.interfaces.transaction-model_interface✕
- Connections
- 1 pair of types, where a type in transaction.infra.repo.transaction_repository uses a type in shared.interfaces.transaction-model_interface.
- The types involved
src.modules.transaction.infra.repo.transaction_repository.TransactionRepository→src.modules.shared.interfaces.transaction-model_interface.ITransaction
- Direction
- transaction.infra.repo.transaction_repository uses shared.interfaces.transaction-model_interface, so a change to shared.interfaces.transaction-model_interface can break transaction.infra.repo.transaction_repository, while a change to transaction.infra.repo.transaction_repository can't break shared.interfaces.transaction-model_interface.
- Position
- Below the diagonal: transaction.infra.repo.transaction_repository uses a module listed above it, which is the healthy direction.
33→8 transaction.infra.repo.transaction_repository uses transaction.domain.interfaces.transaction_repository_interface✕
- Connections
- 1 pair of types, where a type in transaction.infra.repo.transaction_repository uses a type in transaction.domain.interfaces.transaction_repository_interface.
- The types involved
src.modules.transaction.infra.repo.transaction_repository.TransactionRepository→src.modules.transaction.domain.interfaces.transaction_repository_interface.ITransactionRepository
- Direction
- transaction.infra.repo.transaction_repository uses transaction.domain.interfaces.transaction_repository_interface, so a change to transaction.domain.interfaces.transaction_repository_interface can break transaction.infra.repo.transaction_repository, while a change to transaction.infra.repo.transaction_repository can't break transaction.domain.interfaces.transaction_repository_interface.
- Position
- Below the diagonal: transaction.infra.repo.transaction_repository uses a module listed above it, which is the healthy direction.
33→10 transaction.infra.repo.transaction_repository uses transaction.domain.transaction_aggregate✕
- Connections
- 1 pair of types, where a type in transaction.infra.repo.transaction_repository uses a type in transaction.domain.transaction_aggregate.
- The types involved
src.modules.transaction.infra.repo.transaction_repository.TransactionRepository→src.modules.transaction.domain.transaction_aggregate.TransactionAggregate
- Direction
- transaction.infra.repo.transaction_repository uses transaction.domain.transaction_aggregate, so a change to transaction.domain.transaction_aggregate can break transaction.infra.repo.transaction_repository, while a change to transaction.infra.repo.transaction_repository can't break transaction.domain.transaction_aggregate.
- Position
- Below the diagonal: transaction.infra.repo.transaction_repository uses a module listed above it, which is the healthy direction.
33→11 transaction.infra.repo.transaction_repository uses transaction.infra.services.queries.transaction-query_interface✕
- Connections
- 1 pair of types, where a type in transaction.infra.repo.transaction_repository uses a type in transaction.infra.services.queries.transaction-query_interface.
- The types involved
src.modules.transaction.infra.repo.transaction_repository.TransactionRepository→src.modules.transaction.infra.services.queries.transaction-query_interface.Filter
- Direction
- transaction.infra.repo.transaction_repository uses transaction.infra.services.queries.transaction-query_interface, so a change to transaction.infra.services.queries.transaction-query_interface can break transaction.infra.repo.transaction_repository, while a change to transaction.infra.repo.transaction_repository can't break transaction.infra.services.queries.transaction-query_interface.
- Position
- Below the diagonal: transaction.infra.repo.transaction_repository uses a module listed above it, which is the healthy direction.
33→19 transaction.infra.repo.transaction_repository uses transaction.infra.repo.transaction_mapper✕
- Connections
- 1 pair of types, where a type in transaction.infra.repo.transaction_repository uses a type in transaction.infra.repo.transaction_mapper.
- The types involved
src.modules.transaction.infra.repo.transaction_repository.TransactionRepository→src.modules.transaction.infra.repo.transaction_mapper.TransactionToDomainMapper
- Direction
- transaction.infra.repo.transaction_repository uses transaction.infra.repo.transaction_mapper, so a change to transaction.infra.repo.transaction_mapper can break transaction.infra.repo.transaction_repository, while a change to transaction.infra.repo.transaction_repository can't break transaction.infra.repo.transaction_mapper.
- Position
- Below the diagonal: transaction.infra.repo.transaction_repository uses a module listed above it, which is the healthy direction.
34→7 user.infra.user_service uses shared.interfaces.user-model_interface✕
- Connections
- 1 pair of types, where a type in user.infra.user_service uses a type in shared.interfaces.user-model_interface.
- The types involved
src.modules.user.infra.user_service.UserService→src.modules.shared.interfaces.user-model_interface.IUser
- Direction
- user.infra.user_service uses shared.interfaces.user-model_interface, so a change to shared.interfaces.user-model_interface can break user.infra.user_service, while a change to user.infra.user_service can't break shared.interfaces.user-model_interface.
- Position
- Below the diagonal: user.infra.user_service uses a module listed above it, which is the healthy direction.
34→20 user.infra.user_service uses user.application.use-cases.get-user-by-id.get-user-by-id_use-case✕
- Connections
- 1 pair of types, where a type in user.infra.user_service uses a type in user.application.use-cases.get-user-by-id.get-user-by-id_use-case.
- The types involved
src.modules.user.infra.user_service.UserService→src.modules.user.application.use-cases.get-user-by-id.get-user-by-id_use-case.GetUserByIdUseCase
- Direction
- user.infra.user_service uses user.application.use-cases.get-user-by-id.get-user-by-id_use-case, so a change to user.application.use-cases.get-user-by-id.get-user-by-id_use-case can break user.infra.user_service, while a change to user.infra.user_service can't break user.application.use-cases.get-user-by-id.get-user-by-id_use-case.
- Position
- Below the diagonal: user.infra.user_service uses a module listed above it, which is the healthy direction.
34→21 user.infra.user_service uses user.application.use-cases.signin.signin_use-case✕
- Connections
- 1 pair of types, where a type in user.infra.user_service uses a type in user.application.use-cases.signin.signin_use-case.
- The types involved
src.modules.user.infra.user_service.UserService→src.modules.user.application.use-cases.signin.signin_use-case.SigninUseCase
- Direction
- user.infra.user_service uses user.application.use-cases.signin.signin_use-case, so a change to user.application.use-cases.signin.signin_use-case can break user.infra.user_service, while a change to user.infra.user_service can't break user.application.use-cases.signin.signin_use-case.
- Position
- Below the diagonal: user.infra.user_service uses a module listed above it, which is the healthy direction.
35→14 budget-box.infra.budget-box_service uses budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service✕
- Connections
- 1 pair of types, where a type in budget-box.infra.budget-box_service uses a type in budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.
- The types involved
src.modules.budget-box.infra.budget-box_service.BudgetBoxService→src.modules.budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.CanAllocatePercentageToBudgetBoxDomainService
- Direction
- budget-box.infra.budget-box_service uses budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service, so a change to budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service can break budget-box.infra.budget-box_service, while a change to budget-box.infra.budget-box_service can't break budget-box.domain.services.can-allocate-percentage-to-budget-box_domain-service.
- Position
- Below the diagonal: budget-box.infra.budget-box_service uses a module listed above it, which is the healthy direction.
35→16 budget-box.infra.budget-box_service uses shared.interfaces.budget-box-model_interface✕
- Connections
- 1 pair of types, where a type in budget-box.infra.budget-box_service uses a type in shared.interfaces.budget-box-model_interface.
- The types involved
src.modules.budget-box.infra.budget-box_service.BudgetBoxService→src.modules.shared.interfaces.budget-box-model_interface.IBudgetBox
- Direction
- budget-box.infra.budget-box_service uses shared.interfaces.budget-box-model_interface, so a change to shared.interfaces.budget-box-model_interface can break budget-box.infra.budget-box_service, while a change to budget-box.infra.budget-box_service can't break shared.interfaces.budget-box-model_interface.
- Position
- Below the diagonal: budget-box.infra.budget-box_service uses a module listed above it, which is the healthy direction.
35→23 budget-box.infra.budget-box_service uses budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case✕
- Connections
- 1 pair of types, where a type in budget-box.infra.budget-box_service uses a type in budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case.
- The types involved
src.modules.budget-box.infra.budget-box_service.BudgetBoxService→src.modules.budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case.GetBudgetBoxByIdUseCase
- Direction
- budget-box.infra.budget-box_service uses budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case, so a change to budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case can break budget-box.infra.budget-box_service, while a change to budget-box.infra.budget-box_service can't break budget-box.application.use-cases.get-budget-box-by-id.get-budget-box-by-id_use-case.
- Position
- Below the diagonal: budget-box.infra.budget-box_service uses a module listed above it, which is the healthy direction.
35→24 budget-box.infra.budget-box_service uses budget-box.domain.services.can-change-budget-box-percentage_domain-service✕
- Connections
- 1 pair of types, where a type in budget-box.infra.budget-box_service uses a type in budget-box.domain.services.can-change-budget-box-percentage_domain-service.
- The types involved
src.modules.budget-box.infra.budget-box_service.BudgetBoxService→src.modules.budget-box.domain.services.can-change-budget-box-percentage_domain-service.CanChangeBudgetBoxPercentageDomainService
- Direction
- budget-box.infra.budget-box_service uses budget-box.domain.services.can-change-budget-box-percentage_domain-service, so a change to budget-box.domain.services.can-change-budget-box-percentage_domain-service can break budget-box.infra.budget-box_service, while a change to budget-box.infra.budget-box_service can't break budget-box.domain.services.can-change-budget-box-percentage_domain-service.
- Position
- Below the diagonal: budget-box.infra.budget-box_service uses a module listed above it, which is the healthy direction.
36→1 budget-box.infra.repo.budget-box_repository uses budget-box.domain.interfaces.budget-box_repository_interface✕
- Connections
- 1 pair of types, where a type in budget-box.infra.repo.budget-box_repository uses a type in budget-box.domain.interfaces.budget-box_repository_interface.
- The types involved
src.modules.budget-box.infra.repo.budget-box_repository.BudgetBoxRepository→src.modules.budget-box.domain.interfaces.budget-box_repository_interface.IBudgetBoxRepository
- Direction
- budget-box.infra.repo.budget-box_repository uses budget-box.domain.interfaces.budget-box_repository_interface, so a change to budget-box.domain.interfaces.budget-box_repository_interface can break budget-box.infra.repo.budget-box_repository, while a change to budget-box.infra.repo.budget-box_repository can't break budget-box.domain.interfaces.budget-box_repository_interface.
- Position
- Below the diagonal: budget-box.infra.repo.budget-box_repository uses a module listed above it, which is the healthy direction.
36→11 budget-box.infra.repo.budget-box_repository uses transaction.infra.services.queries.transaction-query_interface✕
- Connections
- 1 pair of types, where a type in budget-box.infra.repo.budget-box_repository uses a type in transaction.infra.services.queries.transaction-query_interface.
- The types involved
src.modules.budget-box.infra.repo.budget-box_repository.BudgetBoxRepository→src.modules.transaction.infra.services.queries.transaction-query_interface.Filter
- Direction
- budget-box.infra.repo.budget-box_repository uses transaction.infra.services.queries.transaction-query_interface, so a change to transaction.infra.services.queries.transaction-query_interface can break budget-box.infra.repo.budget-box_repository, while a change to budget-box.infra.repo.budget-box_repository can't break transaction.infra.services.queries.transaction-query_interface.
- Position
- Below the diagonal: budget-box.infra.repo.budget-box_repository uses a module listed above it, which is the healthy direction.
36→13 budget-box.infra.repo.budget-box_repository uses budget-box.domain.budget-box_aggregate✕
- Connections
- 1 pair of types, where a type in budget-box.infra.repo.budget-box_repository uses a type in budget-box.domain.budget-box_aggregate.
- The types involved
src.modules.budget-box.infra.repo.budget-box_repository.BudgetBoxRepository→src.modules.budget-box.domain.budget-box_aggregate.BudgetBoxAggregate
- Direction
- budget-box.infra.repo.budget-box_repository uses budget-box.domain.budget-box_aggregate, so a change to budget-box.domain.budget-box_aggregate can break budget-box.infra.repo.budget-box_repository, while a change to budget-box.infra.repo.budget-box_repository can't break budget-box.domain.budget-box_aggregate.
- Position
- Below the diagonal: budget-box.infra.repo.budget-box_repository uses a module listed above it, which is the healthy direction.
36→16 budget-box.infra.repo.budget-box_repository uses shared.interfaces.budget-box-model_interface✕
- Connections
- 1 pair of types, where a type in budget-box.infra.repo.budget-box_repository uses a type in shared.interfaces.budget-box-model_interface.
- The types involved
src.modules.budget-box.infra.repo.budget-box_repository.BudgetBoxRepository→src.modules.shared.interfaces.budget-box-model_interface.IBudgetBox
- Direction
- budget-box.infra.repo.budget-box_repository uses shared.interfaces.budget-box-model_interface, so a change to shared.interfaces.budget-box-model_interface can break budget-box.infra.repo.budget-box_repository, while a change to budget-box.infra.repo.budget-box_repository can't break shared.interfaces.budget-box-model_interface.
- Position
- Below the diagonal: budget-box.infra.repo.budget-box_repository uses a module listed above it, which is the healthy direction.
36→25 budget-box.infra.repo.budget-box_repository uses budget-box.infra.repo.budget-box_mapper✕
- Connections
- 1 pair of types, where a type in budget-box.infra.repo.budget-box_repository uses a type in budget-box.infra.repo.budget-box_mapper.
- The types involved
src.modules.budget-box.infra.repo.budget-box_repository.BudgetBoxRepository→src.modules.budget-box.infra.repo.budget-box_mapper.BudgetBoxToDomainMapper
- Direction
- budget-box.infra.repo.budget-box_repository uses budget-box.infra.repo.budget-box_mapper, so a change to budget-box.infra.repo.budget-box_mapper can break budget-box.infra.repo.budget-box_repository, while a change to budget-box.infra.repo.budget-box_repository can't break budget-box.infra.repo.budget-box_mapper.
- Position
- Below the diagonal: budget-box.infra.repo.budget-box_repository uses a module listed above it, which is the healthy direction.
37→6 transaction.infra.transaction_service uses shared.interfaces.transaction-model_interface✕
- Connections
- 1 pair of types, where a type in transaction.infra.transaction_service uses a type in shared.interfaces.transaction-model_interface.
- The types involved
src.modules.transaction.infra.transaction_service.TransactionService→src.modules.shared.interfaces.transaction-model_interface.ITransaction
- Direction
- transaction.infra.transaction_service uses shared.interfaces.transaction-model_interface, so a change to shared.interfaces.transaction-model_interface can break transaction.infra.transaction_service, while a change to transaction.infra.transaction_service can't break shared.interfaces.transaction-model_interface.
- Position
- Below the diagonal: transaction.infra.transaction_service uses a module listed above it, which is the healthy direction.
37→17 transaction.infra.transaction_service uses transaction.domain.services.can-create-benefit_proxy✕
- Connections
- 1 pair of types, where a type in transaction.infra.transaction_service uses a type in transaction.domain.services.can-create-benefit_proxy.
- The types involved
src.modules.transaction.infra.transaction_service.TransactionService→src.modules.transaction.domain.services.can-create-benefit_proxy.CanCreateBenefit
- Direction
- transaction.infra.transaction_service uses transaction.domain.services.can-create-benefit_proxy, so a change to transaction.domain.services.can-create-benefit_proxy can break transaction.infra.transaction_service, while a change to transaction.infra.transaction_service can't break transaction.domain.services.can-create-benefit_proxy.
- Position
- Below the diagonal: transaction.infra.transaction_service uses a module listed above it, which is the healthy direction.
37→26 transaction.infra.transaction_service uses shared.domain.can-create-transaction_domain-service✕
- Connections
- 1 pair of types, where a type in transaction.infra.transaction_service uses a type in shared.domain.can-create-transaction_domain-service.
- The types involved
src.modules.transaction.infra.transaction_service.TransactionService→src.modules.shared.domain.can-create-transaction_domain-service.CanCreateTransactionDomainService
- Direction
- transaction.infra.transaction_service uses shared.domain.can-create-transaction_domain-service, so a change to shared.domain.can-create-transaction_domain-service can break transaction.infra.transaction_service, while a change to transaction.infra.transaction_service can't break shared.domain.can-create-transaction_domain-service.
- Position
- Below the diagonal: transaction.infra.transaction_service uses a module listed above it, which is the healthy direction.
37→27 transaction.infra.transaction_service uses transaction.application.use-cases.balance-transference.balance-transference_use-case✕
- Connections
- 1 pair of types, where a type in transaction.infra.transaction_service uses a type in transaction.application.use-cases.balance-transference.balance-transference_use-case.
- The types involved
src.modules.transaction.infra.transaction_service.TransactionService→src.modules.transaction.application.use-cases.balance-transference.balance-transference_use-case.BalanceTransferenceUseCase
- Direction
- transaction.infra.transaction_service uses transaction.application.use-cases.balance-transference.balance-transference_use-case, so a change to transaction.application.use-cases.balance-transference.balance-transference_use-case can break transaction.infra.transaction_service, while a change to transaction.infra.transaction_service can't break transaction.application.use-cases.balance-transference.balance-transference_use-case.
- Position
- Below the diagonal: transaction.infra.transaction_service uses a module listed above it, which is the healthy direction.
37→28 transaction.infra.transaction_service uses transaction.application.use-cases.create-expense.create-expense_use-case✕
- Connections
- 1 pair of types, where a type in transaction.infra.transaction_service uses a type in transaction.application.use-cases.create-expense.create-expense_use-case.
- The types involved
src.modules.transaction.infra.transaction_service.TransactionService→src.modules.transaction.application.use-cases.create-expense.create-expense_use-case.CreateExpenseUseCase
- Direction
- transaction.infra.transaction_service uses transaction.application.use-cases.create-expense.create-expense_use-case, so a change to transaction.application.use-cases.create-expense.create-expense_use-case can break transaction.infra.transaction_service, while a change to transaction.infra.transaction_service can't break transaction.application.use-cases.create-expense.create-expense_use-case.
- Position
- Below the diagonal: transaction.infra.transaction_service uses a module listed above it, which is the healthy direction.
37→29 transaction.infra.transaction_service uses transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case✕
- Connections
- 1 pair of types, where a type in transaction.infra.transaction_service uses a type in transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case.
- The types involved
src.modules.transaction.infra.transaction_service.TransactionService→src.modules.transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case.GetTransactionByIdUseCase
- Direction
- transaction.infra.transaction_service uses transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case, so a change to transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case can break transaction.infra.transaction_service, while a change to transaction.infra.transaction_service can't break transaction.application.use-cases.get-transaction-by-id.get-transaction-by-id_use-case.
- Position
- Below the diagonal: transaction.infra.transaction_service uses a module listed above it, which is the healthy direction.
37→30 transaction.infra.transaction_service uses transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case✕
- Connections
- 1 pair of types, where a type in transaction.infra.transaction_service uses a type in transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case.
- The types involved
src.modules.transaction.infra.transaction_service.TransactionService→src.modules.transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case.PercentageCapitalInflowPostingUseCase
- Direction
- transaction.infra.transaction_service uses transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case, so a change to transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case can break transaction.infra.transaction_service, while a change to transaction.infra.transaction_service can't break transaction.application.use-cases.percentage-capital-inflow-posting.percentage-capital-inflow-posting_use-case.
- Position
- Below the diagonal: transaction.infra.transaction_service uses a module listed above it, which is the healthy direction.
37→31 transaction.infra.transaction_service uses transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case✕
- Connections
- 1 pair of types, where a type in transaction.infra.transaction_service uses a type in transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case.
- The types involved
src.modules.transaction.infra.transaction_service.TransactionService→src.modules.transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case.PostingToBenefitUseCase
- Direction
- transaction.infra.transaction_service uses transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case, so a change to transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case can break transaction.infra.transaction_service, while a change to transaction.infra.transaction_service can't break transaction.application.use-cases.posting-to-benefit.posting-to-benefit_use-case.
- Position
- Below the diagonal: transaction.infra.transaction_service uses a module listed above it, which is the healthy direction.
37→32 transaction.infra.transaction_service uses transaction.domain.services.can-create-expense_proxy✕
- Connections
- 1 pair of types, where a type in transaction.infra.transaction_service uses a type in transaction.domain.services.can-create-expense_proxy.
- The types involved
src.modules.transaction.infra.transaction_service.TransactionService→src.modules.transaction.domain.services.can-create-expense_proxy.CanCreateExpense
- Direction
- transaction.infra.transaction_service uses transaction.domain.services.can-create-expense_proxy, so a change to transaction.domain.services.can-create-expense_proxy can break transaction.infra.transaction_service, while a change to transaction.infra.transaction_service can't break transaction.domain.services.can-create-expense_proxy.
- Position
- Below the diagonal: transaction.infra.transaction_service uses a module listed above it, which is the healthy direction.
38→34 user.infra.resolver.user_resolver uses user.infra.user_service✕
- Connections
- 1 pair of types, where a type in user.infra.resolver.user_resolver uses a type in user.infra.user_service.
- The types involved
src.modules.user.infra.resolver.user_resolver.UserResolver→src.modules.user.infra.user_service.UserService
- Direction
- user.infra.resolver.user_resolver uses user.infra.user_service, so a change to user.infra.user_service can break user.infra.resolver.user_resolver, while a change to user.infra.resolver.user_resolver can't break user.infra.user_service.
- Position
- Below the diagonal: user.infra.resolver.user_resolver uses a module listed above it, which is the healthy direction.
39→35 budget-box.infra.resolver.budget-box_resolver uses budget-box.infra.budget-box_service✕
- Connections
- 1 pair of types, where a type in budget-box.infra.resolver.budget-box_resolver uses a type in budget-box.infra.budget-box_service.
- The types involved
src.modules.budget-box.infra.resolver.budget-box_resolver.BudgetBoxResolver→src.modules.budget-box.infra.budget-box_service.BudgetBoxService
- Direction
- budget-box.infra.resolver.budget-box_resolver uses budget-box.infra.budget-box_service, so a change to budget-box.infra.budget-box_service can break budget-box.infra.resolver.budget-box_resolver, while a change to budget-box.infra.resolver.budget-box_resolver can't break budget-box.infra.budget-box_service.
- Position
- Below the diagonal: budget-box.infra.resolver.budget-box_resolver uses a module listed above it, which is the healthy direction.
40→6 transaction.infra.resolver.transaction_resolver uses shared.interfaces.transaction-model_interface✕
- Connections
- 1 pair of types, where a type in transaction.infra.resolver.transaction_resolver uses a type in shared.interfaces.transaction-model_interface.
- The types involved
src.modules.transaction.infra.resolver.transaction_resolver.TransactionResolver→src.modules.shared.interfaces.transaction-model_interface.ITransaction
- Direction
- transaction.infra.resolver.transaction_resolver uses shared.interfaces.transaction-model_interface, so a change to shared.interfaces.transaction-model_interface can break transaction.infra.resolver.transaction_resolver, while a change to transaction.infra.resolver.transaction_resolver can't break shared.interfaces.transaction-model_interface.
- Position
- Below the diagonal: transaction.infra.resolver.transaction_resolver uses a module listed above it, which is the healthy direction.
40→37 transaction.infra.resolver.transaction_resolver uses transaction.infra.transaction_service✕
- Connections
- 1 pair of types, where a type in transaction.infra.resolver.transaction_resolver uses a type in transaction.infra.transaction_service.
- The types involved
src.modules.transaction.infra.resolver.transaction_resolver.TransactionResolver→src.modules.transaction.infra.transaction_service.TransactionService
- Direction
- transaction.infra.resolver.transaction_resolver uses transaction.infra.transaction_service, so a change to transaction.infra.transaction_service can break transaction.infra.resolver.transaction_resolver, while a change to transaction.infra.resolver.transaction_resolver can't break transaction.infra.transaction_service.
- Position
- Below the diagonal: transaction.infra.resolver.transaction_resolver 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 123 | High / Critical |
| A05:2025 — Injection | 8 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | Medium |
Roadmap
Top priorities: Encrypt sensitive data at rest (AES-256-GCM through node:crypto createCipheriv, or a column-encryption layer such as typeorm-encrypted / prisma-field-encryption / MongoDB CSFLE) and manage keys in a vault (AWS KMS, Azure Key Vault, GCP KMS, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.); Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED; Resolve the 58 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (58).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. | +3.4 pts | Low | Vulnerability-disclosure Policy |
| Encrypt sensitive data at rest (AES-256-GCM through node:crypto createCipheriv, or a column-encryption layer such as typeorm-encrypted / prisma-field-encryption / MongoDB CSFLE) and manage keys in a vault (AWS KMS, Azure Key Vault, GCP KMS, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.). | +5.9 pts | Medium | Data Protection |
| Resolve the 58 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (58). | +2.9 pts | Medium | Dependency Vulnerabilities |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +2.7 pts | Medium | Dependency Hygiene |
| Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.3 pts | Low | Dependency Vulnerabilities |
| Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own. | +2.4 pts | Medium | Access Controls |
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +2.2 pts | Medium | Text alternatives |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.0 pts | Low | ADR Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| package.json | 7.0 | Mixed | Dependency Hygiene: Deprecated: @apollo/gateway |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| src/modules/budget-box/infra/budget-box.service.ts | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: BudgetBoxService (LCOM4 9) |
| src/modules/transaction/infra/transaction.service.ts | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: TransactionService (LCOM4 6) |
| src/modules/budget-box/domain/budget-box.aggregate.ts | 8.5 | Near-clean | Change Coupling: Change-coupling hub: budget-box.aggregate.ts → budget-box.module.ts, budget-box.service.ts, budget-box.resolver.ts |
| src/modules/user/application/use-cases/signin/signin.use-case.ts | 8.5 | Near-clean | Change Coupling: Change coupling: signin.use-case.ts ↔ signup.use-case.ts |
| src/modules/user/domain/subscriptions/after-delete-user-subscription.spec.ts | 9.3 | Near-clean | Test Quality: Mock-dominated test: should dispatch with success |
| REDACTED | 9.3 | Near-clean | Vulnerability-disclosure Policy: REDACTED |
| src/modules/transaction/domain/subscriptions/after-transaction-created-subscription.spec.ts | 9.5 | Near-clean | Test Quality: Mock-dominated test: should dispatch with success |
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 81 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 81 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, 281 of 294 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for the repository root failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in the repository root was NOT MEASURED: the dependency install for the repository root failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- 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-contributor repository — bus factor is not applicable (1 contributor(s) across 372 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — 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. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- AC3 Page structure — 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. 18 further occurrence(s) are not listed individually; the score already reflects all 58.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. User interface: 2 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. Boot: crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:27017: page.goto: net::ERR_CONNECTION_RESET at http://127.0.0.1:27017/ Call log: - navigating to "http://127.0.0.1:27017/", waiting until "load" .
- 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.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 160 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- 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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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.
- C5 Data-Subject Rights: This control is scored from in-repo evidence only — absence of evidence here means the scan found no in-repo trace, not that the control does not exist.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- 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.
- 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
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D6 · Cohesion (LCOM4)
2 of 27 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with budget-box.service.ts, transaction.service.ts. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
206 test methods: 206 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 206 `it`/`test` case(s) across 57 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 206 tests.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 4831 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).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (3 contexts). Contexts: budget-box, transaction, user.
D26 · Project Cohesion
1 of 1 build units (npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
8 finding(s): 0 critical, 5 high, 3 medium, 0 low. 5 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.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 5 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 (5 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
123 finding(s): 19 critical, 59 high, 35 medium, 10 low.
What to do
- Resolve the 58 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (58). — One of this dimension's main actionable groups (58 issue-level).
- Resolve the 19 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (19). — One of this dimension's main actionable groups (19 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- 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).
D34 · Knowledge Freshness
14 of 14 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/types/code-gen.types.ts. Counted over 14 of the 166 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 13 Orphaned file finding(s) in Knowledge Freshness — start with budget-box.service.ts, transaction.service.ts, budget-box.resolver.ts. — One of this dimension's main actionable groups (13 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with code-gen.types.ts. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: budget-box.aggregate.ts↔budget-box.resolver.ts 60%; budget-box.aggregate.ts↔budget-box.module.ts 50%; budget-box.aggregate.ts↔budget-box.service.ts 50%
What to do
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with budget-box.aggregate.ts. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with signin.use-case.ts. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (REDACTED) is present but lists no reporting contact.
What to do
- Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 34 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — public/index.html:15
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — public/index.html:222
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — public/index.html:2
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×39) — public/index.html:238, public/index.html:255, public/index.html:348, …
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (an a11y linter that can read your UI — no component framework was detected, so the JSX/Vue ESLint plugins would have nothing to lint; use an HTML-template a11y linter (html-eslint, htmlhint) or run axe/pa11y over the rendered pages) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 2 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — package.json:77
What to do
- Enforce accessibility in the toolchain: add an a11y linter that can read your UI — no component framework was detected, so the JSX/Vue ESLint plugins would have nothing to lint; use an HTML-template a11y linter (html-eslint, htmlhint) or run axe/pa11y over the rendered pages, then assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
C1 · Data Protection
- No encryption usage (node:crypto createCipheriv, Web Crypto subtle.encrypt, crypto-js AES, tweetnacl/libsodium secretbox, a column-encryption layer such as typeorm-encrypted, prisma-field-encryption or mongoose-field-encryption, or MongoDB client-side field-level encryption) was found, and this repository persists personal data in the model cited here — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore. — src/modules/user/infra/entities/user.schema.ts:14
What to do
- Encrypt sensitive data at rest (AES-256-GCM through node:crypto createCipheriv, or a column-encryption layer such as typeorm-encrypted / prisma-field-encryption / MongoDB CSFLE) and manage keys in a vault (AWS KMS, Azure Key Vault, GCP KMS, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.).
- Enforce HTTPS (serve through https.createServer / NestJS httpsOptions, or redirect plain HTTP with express-sslify behind your TLS terminator) so data in transit is always encrypted.
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect. — src/utils/check-result.interceptor.ts:18
What to do
- Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
C5 · Data-Subject Rights
- Corroborated rights: erasure ✓ · export ✗ · consent ✗. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.
What to do
- Implement data export/portability for a data subject (a machine-readable export of their personal data).
- Track GDPR consent (lawful basis) alongside the personal data it authorises.
DM1 · Aggregate boundaries
DM11 · Constructible invalid state
DM4 · Rich vs anemic model
- `BudgetBoxAggregate` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/modules/budget-box/domain/budget-box.aggregate.ts:28
- `TransactionAggregate` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/modules/transaction/domain/transaction.aggregate.ts:34
- `UserAggregate` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/modules/user/domain/user.aggregate.ts:22
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
- A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/modules/budget-box/infra/repo/budget-box.repository.ts:22, src/modules/transaction/infra/repo/transaction.repository.ts:43
What to do
- Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `find` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — src/modules/budget-box/infra/repo/budget-box.repository.ts:22
- `delete` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — src/modules/transaction/infra/repo/transaction.repository.ts:43
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
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
P1 · CI/CD gates
P2 · Observability
What to do
- Add OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
- `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:40
What to do
- 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
R1 · Type Safety
R10 · Code Duplication
- 32 duplicated blocks under src/modules/ have copies in at least two of the sibling directories budget-box, shared, transaction, user — 11 of them are reported below, and 21 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 32 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 32 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 32 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/modules/budget-box/infra/repo/budget-box.repository.ts:23
- 6 of the duplicated blocks reported below have copies in at least two of the sibling directories add-reason-to-budget-box, change-budget-box-name, change-budget-box-percentage, change-reason-description, create-budget-box, delete-budget-box (+1 more sibling(s) not listed) under src/modules/budget-box/application/use-cases/. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/modules/budget-box/application/use-cases/add-reason-to-budget-box/add-reason-to-budget-box.use-case.ts:8
- src/modules/transaction/application/use-cases/create-expense/create-expense.use-case.ts:1 · src/modules/transaction/application/use-cases/posting-to-benefit/posting-to-benefit.use-case.ts:1 — these 2 files are line-for-line copies of one another — 56 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — src/modules/transaction/application/use-cases/create-expense/create-expense.use-case.ts:1
- src/modules/transaction/domain/transaction-status.value-object.ts:8 · src/modules/transaction/domain/transaction-type.value-object.ts:9 — 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. — src/modules/transaction/domain/transaction-status.value-object.ts:8
- src/modules/shared/domain/delete-budget-box-by-user-id.domain-service.ts:6 · src/modules/shared/domain/delete-transactions-by-user-id.domain-service.ts:6 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/modules/shared/domain/delete-budget-box-by-user-id.domain-service.ts:6
- src/modules/budget-box/application/use-cases/add-reason-to-budget-box/add-reason-to-budget-box.use-case.ts:8 · src/modules/budget-box/application/use-cases/change-reason-description/change-reason-description.use-case.ts:7 — 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. — src/modules/budget-box/application/use-cases/add-reason-to-budget-box/add-reason-to-budget-box.use-case.ts:8
- src/modules/transaction/domain/budget-box-name.value-object.ts:4 · src/modules/transaction/domain/transaction-reason.value-object.ts:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/modules/transaction/domain/budget-box-name.value-object.ts:4
- src/modules/transaction/domain/services/can-create-benefit.proxy.ts:6 · src/modules/transaction/domain/services/can-create-expense.proxy.ts:7 — 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. — src/modules/transaction/domain/services/can-create-benefit.proxy.ts:6
- src/modules/transaction/application/use-cases/create-expense/create-expense.use-case.ts:39 · src/modules/transaction/application/use-cases/percentage-capital-inflow-posting/percentage-capital-inflow-posting.use-case.ts:37 · src/modules/transaction/application/use-cases/posting-to-benefit/posting-to-benefit.use-case.ts:38 — the 3 copies are spread across 3 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. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/modules/transaction/application/use-cases/create-expense/create-expense.use-case.ts:39
- src/modules/transaction/infra/inputs/create-expense.input.ts:4 · src/modules/transaction/infra/inputs/percentage-capital-inflow-posting.input.ts:4 · src/modules/transaction/infra/inputs/posting-to-benefit.input.ts:4 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/modules/transaction/infra/inputs/create-expense.input.ts:4
- src/modules/budget-box/domain/budget-description.value-object.ts:3 · src/modules/budget-box/domain/percentage.value-object.ts:4 · src/modules/budget-box/domain/reason-description.value-object.ts:2 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/modules/budget-box/domain/budget-description.value-object.ts:3
- src/modules/transaction/infra/inputs/balance-transference.input.ts:3 · src/modules/transaction/infra/inputs/create-expense.input.ts:4 · src/modules/transaction/infra/inputs/posting-to-benefit.input.ts:4 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/modules/transaction/infra/inputs/balance-transference.input.ts:3
- src/modules/budget-box/application/use-cases/change-budget-box-percentage/change-budget-box-percentage.use-case.ts:7 · src/modules/budget-box/application/use-cases/remove-reason-from-budget-box/remove-reason-from-budget-box.use-case.ts:6 — 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. — src/modules/budget-box/application/use-cases/change-budget-box-percentage/change-budget-box-percentage.use-case.ts:7
- src/modules/budget-box/domain/budget-description.value-object.ts:5 · src/modules/budget-box/domain/reason-description.value-object.ts:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/modules/budget-box/domain/budget-description.value-object.ts:5
- src/modules/budget-box/domain/services/can-allocate-percentage-to-budget-box.domain-service.ts:6 · src/modules/budget-box/domain/services/can-change-budget-box-percentage.domain-service.ts:6 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/modules/budget-box/domain/services/can-allocate-percentage-to-budget-box.domain-service.ts:6
- src/modules/budget-box/application/use-cases/change-reason-description/change-reason-description.use-case.ts:36 · src/modules/budget-box/application/use-cases/remove-reason-from-budget-box/remove-reason-from-budget-box.use-case.ts:24 — 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/modules/budget-box/application/use-cases/change-reason-description/change-reason-description.use-case.ts:36
- src/modules/budget-box/application/use-cases/get-budget-box-by-id/get-budget-box-by-id.use-case.ts:17 · src/modules/transaction/application/use-cases/get-transaction-by-id/get-transaction-by-id.use-case.ts:17 — 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/modules/budget-box/application/use-cases/get-budget-box-by-id/get-budget-box-by-id.use-case.ts:17
- src/modules/budget-box/application/use-cases/get-budget-boxes-for-auth-user/get-budget-boxes-for-auth-user.use-case.ts:15 · src/modules/transaction/application/use-cases/get-transaction-by-user-id/get-transactions-by-user-id.use-case.ts:14 — 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/modules/budget-box/application/use-cases/get-budget-boxes-for-auth-user/get-budget-boxes-for-auth-user.use-case.ts:15
- src/modules/budget-box/domain/reason-description.value-object.ts:6 · src/modules/transaction/domain/attachment-path.value-object.ts:6 · src/modules/transaction/domain/transaction-note.value-object.ts:5 · src/modules/user/domain/ip.value-object.ts:5 — the 4 copies are spread across 4 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. — src/modules/budget-box/domain/reason-description.value-object.ts:6
- src/modules/budget-box/infra/types/budget-box.type.ts:27 · src/modules/transaction/infra/inputs/balance-transference.input.ts:3 · src/modules/transaction/infra/inputs/create-expense.input.ts:4 · src/modules/transaction/infra/inputs/posting-to-benefit.input.ts:4 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/modules/budget-box/infra/types/budget-box.type.ts:27
- src/modules/budget-box/application/use-cases/change-budget-box-name/change-budget-box-name.use-case.ts:30 · src/modules/budget-box/application/use-cases/change-budget-box-percentage/change-budget-box-percentage.use-case.ts:30 — 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/modules/budget-box/application/use-cases/change-budget-box-name/change-budget-box-name.use-case.ts:30
- src/modules/budget-box/infra/inputs/change-reason-description.input.ts:1 · src/modules/budget-box/infra/inputs/create-budget-box.input.ts:1 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/modules/budget-box/infra/inputs/change-reason-description.input.ts:1
- src/modules/budget-box/infra/resolver/budget-box.resolver.ts:21 · src/modules/budget-box/infra/resolver/budget-box.resolver.ts:53 · src/modules/budget-box/infra/resolver/budget-box.resolver.ts:66 · src/modules/budget-box/infra/resolver/budget-box.resolver.ts:79 · +3 more site(s) not listed — all 7 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/modules/budget-box/infra/resolver/budget-box.resolver.ts:21
- src/modules/budget-box/infra/resolver/budget-box.resolver.ts:59 · src/modules/budget-box/infra/resolver/budget-box.resolver.ts:72 · src/modules/budget-box/infra/resolver/budget-box.resolver.ts:85 · src/modules/budget-box/infra/resolver/budget-box.resolver.ts:98 · +3 more site(s) not listed — the 7 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. — src/modules/budget-box/infra/resolver/budget-box.resolver.ts:59
- src/modules/budget-box/infra/types/reason.type.ts:1 · src/modules/transaction/infra/inputs/balance-transference.input.ts:1 · src/modules/transaction/infra/inputs/create-expense.input.ts:2 · src/modules/transaction/infra/inputs/percentage-capital-inflow-posting.input.ts:2 · +2 more site(s) not listed — the 6 copies are spread across 6 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/modules/budget-box/infra/types/reason.type.ts:1
- src/modules/transaction/application/use-cases/balance-transference/balance-transference.use-case.ts:17 · src/modules/transaction/application/use-cases/create-expense/create-expense.use-case.ts:18 · src/modules/transaction/application/use-cases/posting-to-benefit/posting-to-benefit.use-case.ts:18 — the 3 copies are spread across 3 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. — src/modules/transaction/application/use-cases/balance-transference/balance-transference.use-case.ts:17
- src/modules/transaction/domain/services/can-create-expense.proxy.ts:6 · src/modules/transaction/domain/services/can-transfer.proxy.ts:7 — 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. — src/modules/transaction/domain/services/can-create-expense.proxy.ts:6
- src/modules/transaction/infra/resolver/transaction.resolver.ts:20 · src/modules/transaction/infra/resolver/transaction.resolver.ts:41 · src/modules/transaction/infra/resolver/transaction.resolver.ts:54 · src/modules/transaction/infra/resolver/transaction.resolver.ts:76 · +1 more site(s) not listed — the 5 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. — src/modules/transaction/infra/resolver/transaction.resolver.ts:20
- src/modules/budget-box/application/use-cases/change-budget-box-percentage/change-budget-box-percentage.use-case.ts:3 · src/modules/user/application/use-cases/delete-account/delete-account.use-case.ts:2 — 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. — src/modules/budget-box/application/use-cases/change-budget-box-percentage/change-budget-box-percentage.use-case.ts:3
- src/modules/budget-box/application/use-cases/change-reason-description/change-reason-description.use-case.ts:7 · src/modules/budget-box/application/use-cases/create-budget-box/create-budget-box.use-case.ts:10 — 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. — src/modules/budget-box/application/use-cases/change-reason-description/change-reason-description.use-case.ts:7
- src/modules/budget-box/domain/services/can-allocate-percentage-to-budget-box.domain-service.ts:21 · src/modules/shared/domain/can-create-transaction.domain-service.ts:19 — 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/modules/budget-box/domain/services/can-allocate-percentage-to-budget-box.domain-service.ts:21
- src/modules/budget-box/infra/entities/budget-box.schema.ts:30 · src/modules/user/infra/entities/user.schema.ts:20 — the two spans are one implementation copied and then locally edited — 86 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/modules/budget-box/infra/entities/budget-box.schema.ts:30
- src/modules/budget-box/application/use-cases/change-budget-box-percentage/change-budget-box-percentage.use-case.ts:14 · src/modules/budget-box/application/use-cases/delete-budget-box/delete-budget-box.use-case.ts:12 · src/modules/budget-box/application/use-cases/remove-reason-from-budget-box/remove-reason-from-budget-box.use-case.ts:13 — the 3 copies are spread across 3 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. — src/modules/budget-box/application/use-cases/change-budget-box-percentage/change-budget-box-percentage.use-case.ts:14
- src/modules/budget-box/infra/repo/budget-box-reason.mapper.ts:11 · src/modules/budget-box/infra/repo/budget-box.mapper.ts:41 — 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. — src/modules/budget-box/infra/repo/budget-box-reason.mapper.ts:11
- src/modules/transaction/application/use-cases/balance-transference/balance-transference.use-case.ts:74 · src/modules/transaction/application/use-cases/create-expense/create-expense.use-case.ts:47 · src/modules/transaction/application/use-cases/percentage-capital-inflow-posting/percentage-capital-inflow-posting.use-case.ts:46 · src/modules/transaction/application/use-cases/posting-to-benefit/posting-to-benefit.use-case.ts:46 · +1 more site(s) not listed — the 5 copies are spread across 5 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. There is one copy in each of 5 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/modules/transaction/application/use-cases/balance-transference/balance-transference.use-case.ts:74
- src/modules/transaction/application/use-cases/balance-transference/balance-transference.use-case.ts:49 · src/modules/transaction/application/use-cases/balance-transference/balance-transference.use-case.ts:59 — 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/modules/transaction/application/use-cases/balance-transference/balance-transference.use-case.ts:49
- src/modules/budget-box/infra/entities/budget-box.schema.ts:6 · src/modules/transaction/infra/entities/transaction.schema.ts:13 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/modules/budget-box/infra/entities/budget-box.schema.ts:6
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/modules/transaction/domain/attachment-path.value-object.ts:2 imports validator/lib/isURL, 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/modules/transaction/domain/attachment-path.value-object.ts:2
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
- src/types/code-gen.types.ts has 511 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/types/code-gen.types.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
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. — src/main.ts:1
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
- Nothing ultimately consumes this binding: its only referrer is the re-export in src/modules/shared/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/modules/shared/index.ts in the same commit, or the barrel will import a name that no longer exists. (×4) — src/modules/shared/infra/connections/connection.ts:18, src/modules/shared/interfaces/entity-mock.interface.ts:8, src/modules/shared/interfaces/transaction-model.interface.ts:46, …
- Nothing imports this binding — it is safe to review for removal. (×20) — src/modules/user/domain/ip.value-object.ts:33, src/modules/user/domain/term.value-object.ts:43, src/modules/user/infra/inputs/signin.input.ts:14, …
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 but not declared in any reachable package.json — installs work only by hoisting accident. — src/modules/user/infra/services/decorators/get-user.decorator.ts:3
- 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/modules/budget-box/domain/budget-box.aggregate.ts → src/modules/budget-box/domain/events/budget-box-deleted.event.ts → src/modules/budget-box/domain/budget-box.aggregate.ts — src/modules/budget-box/domain/budget-box.aggregate.ts:10
- src/modules/budget-box/domain/budget-description.value-object.ts → src/modules/shared/index.ts → src/modules/shared/utils/error-messages/messages.ts → src/modules/budget-box/domain/budget-description.value-object.ts (one verified cycle inside a mutually-dependent group of 8 files) — src/modules/budget-box/domain/budget-description.value-object.ts:2
- src/modules/transaction/domain/event/transaction-created.event.ts → src/modules/transaction/domain/transaction.aggregate.ts → src/modules/transaction/domain/event/transaction-created.event.ts — src/modules/transaction/domain/event/transaction-created.event.ts:2
- src/modules/user/domain/events/delete-user-account.event.ts → src/modules/user/domain/user.aggregate.ts → src/modules/user/domain/events/delete-user-account.event.ts — src/modules/user/domain/events/delete-user-account.event.ts:2
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
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
- ~17.5 `!` null assertions per 1k TypeScript source lines — 108 assertion(s) across the 6177 source line(s) of the 159 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: src/modules/transaction/infra/types/transaction.types.ts (15), src/modules/transaction/infra/entities/transaction.schema.ts (11), src/modules/budget-box/infra/types/budget-box.type.ts (10). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
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 `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 79% | Strong | Solid. |
| Architecture | 64% | Adequate — gated by D26, R9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 62% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 44% | Weak — gated by R8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 38% | Weak — gated by C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 77% | Adequate — gated by DM4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 48% | Weak — gated by AC1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D12 Dependency Hygiene — 76 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.
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, an ORM write hook that records changes — a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware — or a change-history plugin such as mongoose-history or sequelize-paper-trail) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 54 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — Not applicable: NestJS makes a provider that injects a request-scoped one request-scoped itself (scope bubbles up the injection chain), and gives every consumer its own transient instance by contract.
- 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — The runtime tier booted this repository's service, but crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:27017: page.goto: net::ERR_CONNECTION_RESET at http://127.0.0.1:27017/ Call log: - navigating to "http://127.0.0.1:27017/", waiting until "load" . This repository also has a user interface (2 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates) that the booted service does not serve, and this scan has no strategy that reaches it — so no WCAG success criterion was verified in a rendered page on this run. That is a gap in OUR tooling, not a finding about your application: nothing here says the interface is inaccessible. The static accessibility checks still ran.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
- D14 License Compliance — Not scored — this repository's 738 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 10 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-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 2 candidate(s) found and not reported.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D24 Comment Value — Too few judgeable comments (6 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- 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.
- 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) 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 — JavaScript/TypeScript suite
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- 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
- M4 Documentation accuracy — Not applicable: the 4 current-state document(s) make no claim of a kind M4 checks. 2 claim(s) of kinds M4 does not check were not checked (command argument 2); M4 checks only links and versions and artefact counts.
- 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 — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: src/main.ts:11 (NestFactory.create))
- 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.
- R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: 160 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
- SC1 Supply-chain hygiene — 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 — 91 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Import cycle (2 files) src/modules/budget-box/domain/budget-box.aggregate.ts:10
- Import cycle (2 files) src/modules/transaction/domain/event/transaction-created.event.ts:2
- Import cycle (2 files) src/modules/user/domain/events/delete-user-account.event.ts:2
- <img> without a text alternative public/index.html:15
- <button> with no accessible text public/index.html:222
- REDACTED
- Orphaned knowledge src/types/code-gen.types.ts:1
- Unlisted import 'express' src/modules/user/infra/services/decorators/get-user.decorator.ts:3
- Import cycle (3 files) src/modules/budget-box/domain/budget-description.value-object.ts:2
Serious — 137 finding(s)
- Heading level jumps from h2 to h5 public/index.html:255
- Heading level jumps from h2 to h5 public/index.html:348
- Heading level jumps from h2 to h5 public/index.html:411
- Heading level jumps from h2 to h5 public/index.html:514
- Heading level jumps from h2 to h5 public/index.html:587
- Heading level jumps from h2 to h5 public/index.html:636
- Heading level jumps from h2 to h5 public/index.html:703
- Heading level jumps from h2 to h5 public/index.html:770
- Heading level jumps from h2 to h5 public/index.html:839
- Heading level jumps from h2 to h5 public/index.html:908
- Heading level jumps from h2 to h5 public/index.html:975
- Heading level jumps from h2 to h5 public/index.html:1042
- Heading level jumps from h2 to h5 public/index.html:1109
- Heading level jumps from h2 to h5 public/index.html:1176
- Heading level jumps from h2 to h5 public/index.html:1245
- Heading level jumps from h2 to h5 public/index.html:1312
- Heading level jumps from h2 to h5 public/index.html:1381
- Heading level jumps from h2 to h5 public/index.html:1450
- Heading level jumps from h2 to h5 public/index.html:1517
- Heading level jumps from h2 to h5 public/index.html:1582
- Heading level jumps from h2 to h5 public/index.html:1636
- Heading level jumps from h2 to h5 public/index.html:1730
- Heading level jumps from h2 to h5 public/index.html:1745
- Heading level jumps from h2 to h5 public/index.html:1899
- Heading level jumps from h2 to h5 public/index.html:1956
- 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
- Anemic entity: BudgetBoxAggregate src/modules/budget-box/domain/budget-box.aggregate.ts:28
- Anemic entity: TransactionAggregate src/modules/transaction/domain/transaction.aggregate.ts:34
- Anemic entity: UserAggregate src/modules/user/domain/user.aggregate.ts:22
- Duplicated block (13 lines × 2 locations) src/modules/budget-box/application/use-cases/change-budget-box-percentage/change-budget-box-percentage.use-case.ts:7
- Duplicated block (13 lines × 2 locations) src/modules/budget-box/domain/budget-description.value-object.ts:5
- Duplicated block (13 lines × 2 locations) src/modules/budget-box/domain/services/can-allocate-percentage-to-budget-box.domain-service.ts:6
- Duplicated block (10 lines × 2 locations) src/modules/budget-box/application/use-cases/change-budget-box-name/change-budget-box-name.use-case.ts:30
- Duplicated block (10 lines × 2 locations) src/modules/budget-box/infra/inputs/change-reason-description.input.ts:1
- Duplicated block (10 lines × 2 locations) src/modules/transaction/domain/services/can-create-expense.proxy.ts:6
- Duplicated block (9 lines × 2 locations) src/modules/budget-box/application/use-cases/change-budget-box-percentage/change-budget-box-percentage.use-case.ts:3
- Duplicated block (9 lines × 2 locations) src/modules/budget-box/application/use-cases/change-reason-description/change-reason-description.use-case.ts:7
- Duplicated block (9 lines × 2 locations) src/modules/budget-box/domain/services/can-allocate-percentage-to-budget-box.domain-service.ts:21
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Low cohesion: BudgetBoxService (LCOM4 9) src/modules/budget-box/infra/budget-box.service.ts:25
- Low cohesion: TransactionService (LCOM4 6) src/modules/transaction/infra/transaction.service.ts:21
- Unfinished stub — throws a "not implemented" error src/modules/budget-box/infra/repo/budget-box.repository.ts:22
- Unfinished stub — throws a "not implemented" error src/modules/transaction/infra/repo/transaction.repository.ts:43
- Unfinished stub — throws a "not implemented" exception src/modules/budget-box/infra/repo/budget-box.repository.ts:22
- Unfinished stub — throws a "not implemented" exception src/modules/transaction/infra/repo/transaction.repository.ts:43
- Duplicated block (17 lines × 2 locations) src/modules/transaction/domain/budget-box-name.value-object.ts:4
- Duplicated block (17 lines × 2 locations) src/modules/transaction/domain/services/can-create-benefit.proxy.ts:6
- Duplicated block (16 lines × 3 locations) src/modules/transaction/application/use-cases/create-expense/create-expense.use-case.ts:39
- Duplicated block (16 lines × 3 locations) src/modules/transaction/infra/inputs/create-expense.input.ts:4
- Duplicated block (14 lines × 3 locations) src/modules/budget-box/domain/budget-description.value-object.ts:3
- Duplicated block (14 lines × 3 locations) src/modules/transaction/infra/inputs/balance-transference.input.ts:3
- Duplicated block (11 lines × 2 locations) src/modules/budget-box/application/use-cases/get-budget-box-by-id/get-budget-box-by-id.use-case.ts:17
- Duplicated block (11 lines × 2 locations) src/modules/budget-box/application/use-cases/get-budget-boxes-for-auth-user/get-budget-boxes-for-auth-user.use-case.ts:15
- Duplicated block (10 lines × 7 locations) src/modules/budget-box/infra/resolver/budget-box.resolver.ts:21
- Duplicated block (10 lines × 7 locations) src/modules/budget-box/infra/resolver/budget-box.resolver.ts:59
- Page without a main landmark public/index.html:2
- Heading level jumps from h1 to h5 public/index.html:238
- Accessibility enforcement below the top rung package.json:77
- No data-protection/encryption src/modules/user/infra/entities/user.schema.ts:14
- REDACTED
- REDACTED
- Change-coupling hub: budget-box.aggregate.ts → budget-box.module.ts, budget-box.service.ts, budget-box.resolver.ts src/modules/budget-box/domain/budget-box.aggregate.ts
- Change coupling: signin.use-case.ts ↔ signup.use-case.ts src/modules/user/application/use-cases/signin/signin.use-case.ts:1
- REDACTED
- Duplication concentrated across 4 sibling directories (32 clone groups) src/modules/budget-box/infra/repo/budget-box.repository.ts:23
- Duplication concentrated across 7 sibling directories (6 clone groups) src/modules/budget-box/application/use-cases/add-reason-to-budget-box/add-reason-to-budget-box.use-case.ts:8
- Wholesale file copy (56 identical lines × 2 files) src/modules/transaction/application/use-cases/create-expense/create-expense.use-case.ts:1
- Duplicated block (30 lines × 2 locations) src/modules/transaction/domain/transaction-status.value-object.ts:8
- Duplicated block (23 lines × 2 locations) src/modules/shared/domain/delete-budget-box-by-user-id.domain-service.ts:6
- Duplicated block (19 lines × 2 locations) src/modules/budget-box/application/use-cases/add-reason-to-budget-box/add-reason-to-budget-box.use-case.ts:8
- Duplicated block (12 lines × 2 locations) src/modules/budget-box/application/use-cases/change-reason-description/change-reason-description.use-case.ts:36
- Duplicated block (11 lines × 4 locations) src/modules/budget-box/domain/reason-description.value-object.ts:6
- Duplicated block (11 lines × 5 locations) src/modules/budget-box/infra/types/budget-box.type.ts:27
- Duplicated block (10 lines × 6 locations) src/modules/budget-box/infra/types/reason.type.ts:1
- Duplicated block (10 lines × 3 locations) src/modules/transaction/application/use-cases/balance-transference/balance-transference.use-case.ts:17
- Duplicated block (10 lines × 5 locations) src/modules/transaction/infra/resolver/transaction.resolver.ts:20
- Duplicated block with local edits (9 matched lines × 2 locations) src/modules/budget-box/infra/entities/budget-box.schema.ts:30
- Duplicated block (8 lines × 3 locations) src/modules/budget-box/application/use-cases/change-budget-box-percentage/change-budget-box-percentage.use-case.ts:14
- Duplicated block (8 lines × 2 locations) src/modules/budget-box/infra/repo/budget-box-reason.mapper.ts:11
- Duplicated block (8 lines × 5 locations) src/modules/transaction/application/use-cases/balance-transference/balance-transference.use-case.ts:74
- Duplicated block (7 lines × 2 locations) src/modules/transaction/application/use-cases/balance-transference/balance-transference.use-case.ts:49
- Duplicated block (6 lines × 2 locations) src/modules/budget-box/infra/entities/budget-box.schema.ts:6
- Boundary violation [package:third-party-deep-import] src/modules/transaction/domain/attachment-path.value-object.ts:2
- src/types/code-gen.types.ts: 511 lines of code src/types/code-gen.types.ts:1
- No test reaches this file src/main.ts:1
- No typecheck script
- Unused dependency '@apollo/gateway'
- Unused dependency '@graphql-codegen/typescript-resolvers'
- Unused dependency '@microsoft/tsdoc'
Minor — 66 finding(s)
- Unused export 'default' src/modules/shared/infra/connections/connection.ts:18
- Unused export 'default' src/modules/shared/interfaces/entity-mock.interface.ts:8
- Unused export 'default' src/modules/shared/interfaces/transaction-model.interface.ts:46
- Unused export 'default' src/modules/shared/interfaces/user-model.interface.ts:31
- Unused export 'default' src/modules/user/domain/ip.value-object.ts:33
- Unused export 'default' src/modules/user/domain/term.value-object.ts:43
- Unused export 'default' src/modules/user/infra/inputs/signin.input.ts:14
- Unused export 'default' src/modules/user/infra/inputs/signup.input.ts:15
- Unused export 'default' src/modules/user/infra/repo/user.mapper.ts:33
- Unused export 'default' src/modules/user/infra/repo/user.repository.ts:51
- Unused export 'default' src/modules/user/infra/resolver/user.resolver.ts:75
- Unused export 'default' src/modules/user/infra/types/jwt-payload.type.ts:11
- Unused export 'default' src/modules/user/infra/types/term.type.ts:16
- Unused export 'default' src/modules/user/infra/types/user-agent.type.ts:18
- Unused export 'default' src/modules/user/infra/types/user.type.ts:17
- Unused export 'default' src/modules/user/infra/user.service.ts:51
- Orphaned file src/modules/budget-box/infra/budget-box.service.ts:1
- Orphaned file src/modules/transaction/infra/transaction.service.ts:1
- Orphaned file src/modules/budget-box/infra/resolver/budget-box.resolver.ts:1
- Orphaned file src/modules/transaction/domain/transaction.aggregate.ts:1
- Orphaned file src/modules/transaction/application/use-cases/balance-transference/balance-transference.use-case.ts:1
- Orphaned file src/modules/transaction/application/use-cases/percentage-capital-inflow-posting/percentage-capital-inflow-posting.use-case.ts:1
- Orphaned file src/modules/transaction/application/use-cases/posting-to-benefit/posting-to-benefit.use-case.ts:1
- Orphaned file src/modules/transaction/application/use-cases/create-expense/create-expense.use-case.ts:1
- Orphaned file src/modules/budget-box/domain/budget-box.aggregate.ts:1
- Orphaned file src/modules/budget-box/infra/budget-box.module.ts:1
- Orphaned file src/modules/transaction/infra/transaction.module.ts:1
- Orphaned file src/modules/transaction/infra/repo/transaction.mapper.ts:1
- Orphaned file src/modules/transaction/infra/resolver/transaction.resolver.ts:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated predicate src/modules/transaction/application/use-cases/balance-transference/balance-transference.use-case.ts:75
- Duplicated predicate src/modules/transaction/application/use-cases/balance-transference/balance-transference.use-case.ts:32
- Duplicated predicate src/modules/transaction/application/use-cases/balance-transference/balance-transference.use-case.ts:31
- Duplicated predicate src/modules/transaction/application/use-cases/balance-transference/balance-transference.use-case.ts:76
- Mock-dominated test: should dispatch with success src/modules/user/domain/subscriptions/after-delete-user-subscription.spec.ts:21
- Mock-dominated test: should dispatch with error src/modules/user/domain/subscriptions/after-delete-user-subscription.spec.ts:37
- Mock-dominated test: should dispatch with success src/modules/transaction/domain/subscriptions/after-transaction-created-subscription.spec.ts:22
- No named authorization policies src/utils/check-result.interceptor.ts:18
- Partial data-subject-rights support
- No ADRs found
- Projects may be oversized for their cohesion
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- No ADRs
- No dependency-update automation package.json:40
- No rollback/health safety
- No changelog
- Unused export 'Exact' src/types/code-gen.types.ts:4
- Unused export 'MakeOptional' src/types/code-gen.types.ts:5
- Unused export 'MakeMaybe' src/types/code-gen.types.ts:6
- Unused export 'SubscriptionResolver' src/types/code-gen.types.ts:382
- Unused export 'TypeResolveFn' src/types/code-gen.types.ts:386
- Unused export 'DirectiveResolverFn' src/types/code-gen.types.ts:396
- Unused export 'DateTimeScalarConfig' src/types/code-gen.types.ts:523
- Unused export 'Resolvers' src/types/code-gen.types.ts:594
- Null assertions (`!`) reduce the strict null checking score
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-7b9be42377864a20a87dd3d9188af487/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-7b9be42377864a20a87dd3d9188af487/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude public/javascripts --exclude public/stylesheets . | 8 | 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 | 123 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 1 | 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 | — |
| 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 |