Executive summary
xChiro/KalanMyMoney falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 47 out of 100 and is rated Weak, and six of its eight critical findings are security problems in the packages it uses.
Production Readiness, at 36, is the weakest lens and counts most in the score. The best first step is adding an automated build and test pipeline, worth about 9 points. Improving the documentation comes next, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 56.
Six known security holes in the packages the code depends on can be used by attackers. Updating the vulnerable packages would close this risk. The loop of parts of the code that depend on each other needs breaking by moving the shared parts into a project of their own.
The product code is 1,501 lines, about €3,300 to rebuild.
If Production Readiness rose from 36 to 70, the lowest score rated Strong, the score would rise from 47 to about 56.
New since the last survey: 10 findings
- Platform End-of-Life · End-of-life runtime: .NET net6.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net6.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net6.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net6.0 KalanMoney/KalanMoney.Domain.Entities/KalanMoney.Domain.Entities.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 KalanMoney/KalanMoney.Domain.UseCases.Tests/KalanMoney.Domain.UseCases.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 KalanMoney/KalanMoney.Domain.UseCases/KalanMoney.Domain.UseCases.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net6.0 KalanMoney/KalanMoney.Persistence.MemoryDatabase.Tests/KalanMoney.Persistence.MemoryDatabase.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 KalanMoney/KalanMoney.Persistence.MemoryDatabase/KalanMoney.Persistence.MemoryDatabase.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 KalanMoney/KalanMoney.Startup/KalanMoney.Startup.csproj
Fixed since the last survey: 3 findings
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Platform End-of-Life · End-of-life runtime: .NET net6.0 KalanMoney/KalanMoney.Startup/KalanMoney.Startup.csproj
- Rich vs anemic model · Anemic entity: Transaction KalanMoney/KalanMoney.Domain.Entities/Transaction.cs
Rebuild cost: about €3,300 · Estimate
| Cost to rebuild | €1,100 to €5,400, for 18 to 57 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 47. 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 | Very small: 1,501 lines of product code, of which 47% is declarations and boilerplate, 29% straight logic and 24% logic with branches |
| Comment lines | The estimate prices 1,473 lines. Comment lines count towards the size of 1,501 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 API.Functions | 2 API.Functions.Commons | 3 Domain.Entities.Exceptions | 4 Domain.Entities.ValueObjects | 5 Domain.UseCases.Common.Exceptions | 6 Domain.UseCases.Common.Models | 7 Domain.Entities | 8 Domain.UseCases.Repositories.Models | 9 Domain.UseCases.Repositories | 10 Persistence.CosmosDB.DTOs | 11 Persistence.MemoryDatabase.DTOs | 12 Domain.UseCases.AddIncomeTransaction | 13 Domain.UseCases.AddOutcomeTransaction | 14 Domain.UseCases.GetAccountDashboard | 15 Domain.UseCases.GetCategoriesByAccount | 16 Domain.UseCases.GetMonthlyTransactions | 17 Domain.UseCases.OpenAccount | 18 Persistence.CosmosDB.Repositories | 19 Persistence.MemoryDatabase | 20 Startup | 21 API.Functions.AccountDashboard | 22 API.Functions.AddIncomeTransaction | 23 API.Functions.AddOutcomeTransaction | 24 API.Functions.GetCategoriesByAccount | 25 API.Functions.GetMonthlyTransactions | 26 Domain.UseCases.Adapters | 27 API.Functions.OpenAccount |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 API.Functions | |||||||||||||||||||||||||||
| 2 API.Functions.Commons | |||||||||||||||||||||||||||
| 3 Domain.Entities.Exceptions | |||||||||||||||||||||||||||
| 4 Domain.Entities.ValueObjects | |||||||||||||||||||||||||||
| 5 Domain.UseCases.Common.Exceptions | |||||||||||||||||||||||||||
| 6 Domain.UseCases.Common.Models | |||||||||||||||||||||||||||
| 7 Domain.Entities | 7 | ||||||||||||||||||||||||||
| 8 Domain.UseCases.Repositories.Models | 1 | ||||||||||||||||||||||||||
| 9 Domain.UseCases.Repositories | 2 | 4 | 2 | ||||||||||||||||||||||||
| 10 Persistence.CosmosDB.DTOs | 1 | ||||||||||||||||||||||||||
| 11 Persistence.MemoryDatabase.DTOs | 2 | ||||||||||||||||||||||||||
| 12 Domain.UseCases.AddIncomeTransaction | 3 | 2 | |||||||||||||||||||||||||
| 13 Domain.UseCases.AddOutcomeTransaction | 3 | 2 | |||||||||||||||||||||||||
| 14 Domain.UseCases.GetAccountDashboard | 2 | 2 | 1 | ||||||||||||||||||||||||
| 15 Domain.UseCases.GetCategoriesByAccount | 1 | 1 | |||||||||||||||||||||||||
| 16 Domain.UseCases.GetMonthlyTransactions | 1 | 1 | |||||||||||||||||||||||||
| 17 Domain.UseCases.OpenAccount | 1 | 1 | |||||||||||||||||||||||||
| 18 Persistence.CosmosDB.Repositories | 2 | 4 | 2 | 2 | |||||||||||||||||||||||
| 19 Persistence.MemoryDatabase | 2 | 2 | 2 | 2 | 2 | ||||||||||||||||||||||
| 20 Startup | 2 | ||||||||||||||||||||||||||
| 21 API.Functions.AccountDashboard | 1 | 1 | 3 | ||||||||||||||||||||||||
| 22 API.Functions.AddIncomeTransaction | 1 | 1 | 2 | ||||||||||||||||||||||||
| 23 API.Functions.AddOutcomeTransaction | 1 | 1 | 2 | ||||||||||||||||||||||||
| 24 API.Functions.GetCategoriesByAccount | 1 | 1 | 2 | ||||||||||||||||||||||||
| 25 API.Functions.GetMonthlyTransactions | 1 | 1 | 1 | 2 | |||||||||||||||||||||||
| 26 Domain.UseCases.Adapters | 2 | ||||||||||||||||||||||||||
| 27 API.Functions.OpenAccount | 1 | 2 | 1 |
7→4 Domain.Entities uses Domain.Entities.ValueObjects✕
- Connections
- 7 pairs of types, where a type in Domain.Entities uses a type in Domain.Entities.ValueObjects.
- The types involved
KalanMoney.Domain.Entities.FinancialAccount→KalanMoney.Domain.Entities.ValueObjects.AccountNameKalanMoney.Domain.Entities.FinancialAccount→KalanMoney.Domain.Entities.ValueObjects.BalanceKalanMoney.Domain.Entities.FinancialAccount→KalanMoney.Domain.Entities.ValueObjects.OwnerKalanMoney.Domain.Entities.FinancialAccount→KalanMoney.Domain.Entities.ValueObjects.TimeStampKalanMoney.Domain.Entities.Transaction→KalanMoney.Domain.Entities.ValueObjects.CategoryKalanMoney.Domain.Entities.Transaction→KalanMoney.Domain.Entities.ValueObjects.DescriptionKalanMoney.Domain.Entities.Transaction→KalanMoney.Domain.Entities.ValueObjects.TimeStamp
- Direction
- Domain.Entities uses Domain.Entities.ValueObjects, so a change to Domain.Entities.ValueObjects can break Domain.Entities, while a change to Domain.Entities can't break Domain.Entities.ValueObjects.
- Position
- Below the diagonal: Domain.Entities uses a module listed above it, which is the healthy direction.
8→4 Domain.UseCases.Repositories.Models uses Domain.Entities.ValueObjects✕
- Connections
- 1 pair of types, where a type in Domain.UseCases.Repositories.Models uses a type in Domain.Entities.ValueObjects.
- The types involved
KalanMoney.Domain.UseCases.Repositories.Models.GetTransactionsFilters→KalanMoney.Domain.Entities.ValueObjects.Category
- Direction
- Domain.UseCases.Repositories.Models uses Domain.Entities.ValueObjects, so a change to Domain.Entities.ValueObjects can break Domain.UseCases.Repositories.Models, while a change to Domain.UseCases.Repositories.Models can't break Domain.Entities.ValueObjects.
- Position
- Below the diagonal: Domain.UseCases.Repositories.Models uses a module listed above it, which is the healthy direction.
9→4 Domain.UseCases.Repositories uses Domain.Entities.ValueObjects✕
- Connections
- 2 pairs of types, where a type in Domain.UseCases.Repositories uses a type in Domain.Entities.ValueObjects.
- The types involved
KalanMoney.Domain.UseCases.Repositories.IAccountCommandsRepository→KalanMoney.Domain.Entities.ValueObjects.BalanceKalanMoney.Domain.UseCases.Repositories.IAccountQueriesRepository→KalanMoney.Domain.Entities.ValueObjects.Category
- Direction
- Domain.UseCases.Repositories uses Domain.Entities.ValueObjects, so a change to Domain.Entities.ValueObjects can break Domain.UseCases.Repositories, while a change to Domain.UseCases.Repositories can't break Domain.Entities.ValueObjects.
- Position
- Below the diagonal: Domain.UseCases.Repositories uses a module listed above it, which is the healthy direction.
9→7 Domain.UseCases.Repositories uses Domain.Entities✕
- Connections
- 4 pairs of types, where a type in Domain.UseCases.Repositories uses a type in Domain.Entities.
- The types involved
KalanMoney.Domain.UseCases.Repositories.IAccountCommandsRepository→KalanMoney.Domain.Entities.FinancialAccountKalanMoney.Domain.UseCases.Repositories.IAccountCommandsRepository→KalanMoney.Domain.Entities.TransactionKalanMoney.Domain.UseCases.Repositories.IAccountQueriesRepository→KalanMoney.Domain.Entities.FinancialAccountKalanMoney.Domain.UseCases.Repositories.IAccountQueriesRepository→KalanMoney.Domain.Entities.Transaction
- Direction
- Domain.UseCases.Repositories uses Domain.Entities, so a change to Domain.Entities can break Domain.UseCases.Repositories, while a change to Domain.UseCases.Repositories can't break Domain.Entities.
- Position
- Below the diagonal: Domain.UseCases.Repositories uses a module listed above it, which is the healthy direction.
9→8 Domain.UseCases.Repositories uses Domain.UseCases.Repositories.Models✕
- Connections
- 2 pairs of types, where a type in Domain.UseCases.Repositories uses a type in Domain.UseCases.Repositories.Models.
- The types involved
KalanMoney.Domain.UseCases.Repositories.IAccountQueriesRepository→KalanMoney.Domain.UseCases.Repositories.Models.DateRangeFilterKalanMoney.Domain.UseCases.Repositories.IAccountQueriesRepository→KalanMoney.Domain.UseCases.Repositories.Models.GetTransactionsFilters
- Direction
- Domain.UseCases.Repositories uses Domain.UseCases.Repositories.Models, so a change to Domain.UseCases.Repositories.Models can break Domain.UseCases.Repositories, while a change to Domain.UseCases.Repositories can't break Domain.UseCases.Repositories.Models.
- Position
- Below the diagonal: Domain.UseCases.Repositories uses a module listed above it, which is the healthy direction.
10→7 Persistence.CosmosDB.DTOs uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Persistence.CosmosDB.DTOs uses a type in Domain.Entities.
- The types involved
KalanMoney.Persistence.CosmosDB.DTOs.FinancialAccountDto→KalanMoney.Domain.Entities.FinancialAccount
- Direction
- Persistence.CosmosDB.DTOs uses Domain.Entities, so a change to Domain.Entities can break Persistence.CosmosDB.DTOs, while a change to Persistence.CosmosDB.DTOs can't break Domain.Entities.
- Position
- Below the diagonal: Persistence.CosmosDB.DTOs uses a module listed above it, which is the healthy direction.
11→7 Persistence.MemoryDatabase.DTOs uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Persistence.MemoryDatabase.DTOs uses a type in Domain.Entities.
- The types involved
KalanMoney.Persistence.MemoryDatabase.DTOs.FinancialAccountModel→KalanMoney.Domain.Entities.FinancialAccountKalanMoney.Persistence.MemoryDatabase.DTOs.FinancialAccountModel→KalanMoney.Domain.Entities.Transaction
- Direction
- Persistence.MemoryDatabase.DTOs uses Domain.Entities, so a change to Domain.Entities can break Persistence.MemoryDatabase.DTOs, while a change to Persistence.MemoryDatabase.DTOs can't break Domain.Entities.
- Position
- Below the diagonal: Persistence.MemoryDatabase.DTOs uses a module listed above it, which is the healthy direction.
12→6 Domain.UseCases.AddIncomeTransaction uses Domain.UseCases.Common.Models✕
- Connections
- 3 pairs of types, where a type in Domain.UseCases.AddIncomeTransaction uses a type in Domain.UseCases.Common.Models.
- The types involved
KalanMoney.Domain.UseCases.AddIncomeTransaction.AddIncomeTransaction→KalanMoney.Domain.UseCases.Common.Models.AddTransactionRequestKalanMoney.Domain.UseCases.AddIncomeTransaction.IAddIncomeTransactionInput→KalanMoney.Domain.UseCases.Common.Models.AddTransactionRequestKalanMoney.Domain.UseCases.AddIncomeTransaction.IAddIncomeTransactionOutput→KalanMoney.Domain.UseCases.Common.Models.AddTransactionResponse
- Direction
- Domain.UseCases.AddIncomeTransaction uses Domain.UseCases.Common.Models, so a change to Domain.UseCases.Common.Models can break Domain.UseCases.AddIncomeTransaction, while a change to Domain.UseCases.AddIncomeTransaction can't break Domain.UseCases.Common.Models.
- Position
- Below the diagonal: Domain.UseCases.AddIncomeTransaction uses a module listed above it, which is the healthy direction.
12→9 Domain.UseCases.AddIncomeTransaction uses Domain.UseCases.Repositories✕
- Connections
- 2 pairs of types, where a type in Domain.UseCases.AddIncomeTransaction uses a type in Domain.UseCases.Repositories.
- The types involved
KalanMoney.Domain.UseCases.AddIncomeTransaction.AddIncomeTransaction→KalanMoney.Domain.UseCases.Repositories.IAccountCommandsRepositoryKalanMoney.Domain.UseCases.AddIncomeTransaction.AddIncomeTransaction→KalanMoney.Domain.UseCases.Repositories.IAccountQueriesRepository
- Direction
- Domain.UseCases.AddIncomeTransaction uses Domain.UseCases.Repositories, so a change to Domain.UseCases.Repositories can break Domain.UseCases.AddIncomeTransaction, while a change to Domain.UseCases.AddIncomeTransaction can't break Domain.UseCases.Repositories.
- Position
- Below the diagonal: Domain.UseCases.AddIncomeTransaction uses a module listed above it, which is the healthy direction.
13→6 Domain.UseCases.AddOutcomeTransaction uses Domain.UseCases.Common.Models✕
- Connections
- 3 pairs of types, where a type in Domain.UseCases.AddOutcomeTransaction uses a type in Domain.UseCases.Common.Models.
- The types involved
KalanMoney.Domain.UseCases.AddOutcomeTransaction.AddOutcomeTransaction→KalanMoney.Domain.UseCases.Common.Models.AddTransactionRequestKalanMoney.Domain.UseCases.AddOutcomeTransaction.IAddOutcomeTransactionInput→KalanMoney.Domain.UseCases.Common.Models.AddTransactionRequestKalanMoney.Domain.UseCases.AddOutcomeTransaction.IAddOutcomeTransactionOutput→KalanMoney.Domain.UseCases.Common.Models.AddTransactionResponse
- Direction
- Domain.UseCases.AddOutcomeTransaction uses Domain.UseCases.Common.Models, so a change to Domain.UseCases.Common.Models can break Domain.UseCases.AddOutcomeTransaction, while a change to Domain.UseCases.AddOutcomeTransaction can't break Domain.UseCases.Common.Models.
- Position
- Below the diagonal: Domain.UseCases.AddOutcomeTransaction uses a module listed above it, which is the healthy direction.
13→9 Domain.UseCases.AddOutcomeTransaction uses Domain.UseCases.Repositories✕
- Connections
- 2 pairs of types, where a type in Domain.UseCases.AddOutcomeTransaction uses a type in Domain.UseCases.Repositories.
- The types involved
KalanMoney.Domain.UseCases.AddOutcomeTransaction.AddOutcomeTransaction→KalanMoney.Domain.UseCases.Repositories.IAccountCommandsRepositoryKalanMoney.Domain.UseCases.AddOutcomeTransaction.AddOutcomeTransaction→KalanMoney.Domain.UseCases.Repositories.IAccountQueriesRepository
- Direction
- Domain.UseCases.AddOutcomeTransaction uses Domain.UseCases.Repositories, so a change to Domain.UseCases.Repositories can break Domain.UseCases.AddOutcomeTransaction, while a change to Domain.UseCases.AddOutcomeTransaction can't break Domain.UseCases.Repositories.
- Position
- Below the diagonal: Domain.UseCases.AddOutcomeTransaction uses a module listed above it, which is the healthy direction.
14→4 Domain.UseCases.GetAccountDashboard uses Domain.Entities.ValueObjects✕
- Connections
- 2 pairs of types, where a type in Domain.UseCases.GetAccountDashboard uses a type in Domain.Entities.ValueObjects.
- The types involved
KalanMoney.Domain.UseCases.GetAccountDashboard.AccountDashboardResponse→KalanMoney.Domain.Entities.ValueObjects.AccountNameKalanMoney.Domain.UseCases.GetAccountDashboard.AccountDashboardResponse→KalanMoney.Domain.Entities.ValueObjects.Balance
- Direction
- Domain.UseCases.GetAccountDashboard uses Domain.Entities.ValueObjects, so a change to Domain.Entities.ValueObjects can break Domain.UseCases.GetAccountDashboard, while a change to Domain.UseCases.GetAccountDashboard can't break Domain.Entities.ValueObjects.
- Position
- Below the diagonal: Domain.UseCases.GetAccountDashboard uses a module listed above it, which is the healthy direction.
14→7 Domain.UseCases.GetAccountDashboard uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Domain.UseCases.GetAccountDashboard uses a type in Domain.Entities.
- The types involved
KalanMoney.Domain.UseCases.GetAccountDashboard.AccountDashboardResponse→KalanMoney.Domain.Entities.TransactionKalanMoney.Domain.UseCases.GetAccountDashboard.CategoriesBalances→KalanMoney.Domain.Entities.TransactionCollection
- Direction
- Domain.UseCases.GetAccountDashboard uses Domain.Entities, so a change to Domain.Entities can break Domain.UseCases.GetAccountDashboard, while a change to Domain.UseCases.GetAccountDashboard can't break Domain.Entities.
- Position
- Below the diagonal: Domain.UseCases.GetAccountDashboard uses a module listed above it, which is the healthy direction.
14→9 Domain.UseCases.GetAccountDashboard uses Domain.UseCases.Repositories✕
- Connections
- 1 pair of types, where a type in Domain.UseCases.GetAccountDashboard uses a type in Domain.UseCases.Repositories.
- The types involved
KalanMoney.Domain.UseCases.GetAccountDashboard.GetAccountDashboard→KalanMoney.Domain.UseCases.Repositories.IAccountQueriesRepository
- Direction
- Domain.UseCases.GetAccountDashboard uses Domain.UseCases.Repositories, so a change to Domain.UseCases.Repositories can break Domain.UseCases.GetAccountDashboard, while a change to Domain.UseCases.GetAccountDashboard can't break Domain.UseCases.Repositories.
- Position
- Below the diagonal: Domain.UseCases.GetAccountDashboard uses a module listed above it, which is the healthy direction.
15→4 Domain.UseCases.GetCategoriesByAccount uses Domain.Entities.ValueObjects✕
- Connections
- 1 pair of types, where a type in Domain.UseCases.GetCategoriesByAccount uses a type in Domain.Entities.ValueObjects.
- The types involved
KalanMoney.Domain.UseCases.GetCategoriesByAccount.IGetCategoriesByAccountOutput→KalanMoney.Domain.Entities.ValueObjects.Category
- Direction
- Domain.UseCases.GetCategoriesByAccount uses Domain.Entities.ValueObjects, so a change to Domain.Entities.ValueObjects can break Domain.UseCases.GetCategoriesByAccount, while a change to Domain.UseCases.GetCategoriesByAccount can't break Domain.Entities.ValueObjects.
- Position
- Below the diagonal: Domain.UseCases.GetCategoriesByAccount uses a module listed above it, which is the healthy direction.
15→9 Domain.UseCases.GetCategoriesByAccount uses Domain.UseCases.Repositories✕
- Connections
- 1 pair of types, where a type in Domain.UseCases.GetCategoriesByAccount uses a type in Domain.UseCases.Repositories.
- The types involved
KalanMoney.Domain.UseCases.GetCategoriesByAccount.GetCategoriesByAccount→KalanMoney.Domain.UseCases.Repositories.IAccountQueriesRepository
- Direction
- Domain.UseCases.GetCategoriesByAccount uses Domain.UseCases.Repositories, so a change to Domain.UseCases.Repositories can break Domain.UseCases.GetCategoriesByAccount, while a change to Domain.UseCases.GetCategoriesByAccount can't break Domain.UseCases.Repositories.
- Position
- Below the diagonal: Domain.UseCases.GetCategoriesByAccount uses a module listed above it, which is the healthy direction.
16→7 Domain.UseCases.GetMonthlyTransactions uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Domain.UseCases.GetMonthlyTransactions uses a type in Domain.Entities.
- The types involved
KalanMoney.Domain.UseCases.GetMonthlyTransactions.IGetMonthlyTransactionsOutput→KalanMoney.Domain.Entities.Transaction
- Direction
- Domain.UseCases.GetMonthlyTransactions uses Domain.Entities, so a change to Domain.Entities can break Domain.UseCases.GetMonthlyTransactions, while a change to Domain.UseCases.GetMonthlyTransactions can't break Domain.Entities.
- Position
- Below the diagonal: Domain.UseCases.GetMonthlyTransactions uses a module listed above it, which is the healthy direction.
16→9 Domain.UseCases.GetMonthlyTransactions uses Domain.UseCases.Repositories✕
- Connections
- 1 pair of types, where a type in Domain.UseCases.GetMonthlyTransactions uses a type in Domain.UseCases.Repositories.
- The types involved
KalanMoney.Domain.UseCases.GetMonthlyTransactions.GetMonthlyTransactions→KalanMoney.Domain.UseCases.Repositories.IAccountQueriesRepository
- Direction
- Domain.UseCases.GetMonthlyTransactions uses Domain.UseCases.Repositories, so a change to Domain.UseCases.Repositories can break Domain.UseCases.GetMonthlyTransactions, while a change to Domain.UseCases.GetMonthlyTransactions can't break Domain.UseCases.Repositories.
- Position
- Below the diagonal: Domain.UseCases.GetMonthlyTransactions uses a module listed above it, which is the healthy direction.
17→9 Domain.UseCases.OpenAccount uses Domain.UseCases.Repositories✕
- Connections
- 1 pair of types, where a type in Domain.UseCases.OpenAccount uses a type in Domain.UseCases.Repositories.
- The types involved
KalanMoney.Domain.UseCases.OpenAccount.OpenAccount→KalanMoney.Domain.UseCases.Repositories.IAccountCommandsRepository
- Direction
- Domain.UseCases.OpenAccount uses Domain.UseCases.Repositories, so a change to Domain.UseCases.Repositories can break Domain.UseCases.OpenAccount, while a change to Domain.UseCases.OpenAccount can't break Domain.UseCases.Repositories.
- Position
- Below the diagonal: Domain.UseCases.OpenAccount uses a module listed above it, which is the healthy direction.
17→26 Domain.UseCases.OpenAccount uses Domain.UseCases.Adapters part of a loop✕
- Connections
- 1 pair of types, where a type in Domain.UseCases.OpenAccount uses a type in Domain.UseCases.Adapters.
- The types involved
KalanMoney.Domain.UseCases.OpenAccount.OpenAccount→KalanMoney.Domain.UseCases.Adapters.IOpenAccountInput
- Direction
- Domain.UseCases.OpenAccount uses Domain.UseCases.Adapters, so a change to Domain.UseCases.Adapters can break Domain.UseCases.OpenAccount, while a change to Domain.UseCases.OpenAccount can't break Domain.UseCases.Adapters.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→4 Persistence.CosmosDB.Repositories uses Domain.Entities.ValueObjects✕
- Connections
- 2 pairs of types, where a type in Persistence.CosmosDB.Repositories uses a type in Domain.Entities.ValueObjects.
- The types involved
KalanMoney.Persistence.CosmosDB.Repositories.AccountCommandsRepository→KalanMoney.Domain.Entities.ValueObjects.BalanceKalanMoney.Persistence.CosmosDB.Repositories.AccountQueriesRepository→KalanMoney.Domain.Entities.ValueObjects.Category
- Direction
- Persistence.CosmosDB.Repositories uses Domain.Entities.ValueObjects, so a change to Domain.Entities.ValueObjects can break Persistence.CosmosDB.Repositories, while a change to Persistence.CosmosDB.Repositories can't break Domain.Entities.ValueObjects.
- Position
- Below the diagonal: Persistence.CosmosDB.Repositories uses a module listed above it, which is the healthy direction.
18→7 Persistence.CosmosDB.Repositories uses Domain.Entities✕
- Connections
- 4 pairs of types, where a type in Persistence.CosmosDB.Repositories uses a type in Domain.Entities.
- The types involved
KalanMoney.Persistence.CosmosDB.Repositories.AccountCommandsRepository→KalanMoney.Domain.Entities.FinancialAccountKalanMoney.Persistence.CosmosDB.Repositories.AccountCommandsRepository→KalanMoney.Domain.Entities.TransactionKalanMoney.Persistence.CosmosDB.Repositories.AccountQueriesRepository→KalanMoney.Domain.Entities.FinancialAccountKalanMoney.Persistence.CosmosDB.Repositories.AccountQueriesRepository→KalanMoney.Domain.Entities.Transaction
- Direction
- Persistence.CosmosDB.Repositories uses Domain.Entities, so a change to Domain.Entities can break Persistence.CosmosDB.Repositories, while a change to Persistence.CosmosDB.Repositories can't break Domain.Entities.
- Position
- Below the diagonal: Persistence.CosmosDB.Repositories uses a module listed above it, which is the healthy direction.
18→8 Persistence.CosmosDB.Repositories uses Domain.UseCases.Repositories.Models✕
- Connections
- 2 pairs of types, where a type in Persistence.CosmosDB.Repositories uses a type in Domain.UseCases.Repositories.Models.
- The types involved
KalanMoney.Persistence.CosmosDB.Repositories.AccountQueriesRepository→KalanMoney.Domain.UseCases.Repositories.Models.DateRangeFilterKalanMoney.Persistence.CosmosDB.Repositories.AccountQueriesRepository→KalanMoney.Domain.UseCases.Repositories.Models.GetTransactionsFilters
- Direction
- Persistence.CosmosDB.Repositories uses Domain.UseCases.Repositories.Models, so a change to Domain.UseCases.Repositories.Models can break Persistence.CosmosDB.Repositories, while a change to Persistence.CosmosDB.Repositories can't break Domain.UseCases.Repositories.Models.
- Position
- Below the diagonal: Persistence.CosmosDB.Repositories uses a module listed above it, which is the healthy direction.
18→9 Persistence.CosmosDB.Repositories uses Domain.UseCases.Repositories✕
- Connections
- 2 pairs of types, where a type in Persistence.CosmosDB.Repositories uses a type in Domain.UseCases.Repositories.
- The types involved
KalanMoney.Persistence.CosmosDB.Repositories.AccountCommandsRepository→KalanMoney.Domain.UseCases.Repositories.IAccountCommandsRepositoryKalanMoney.Persistence.CosmosDB.Repositories.AccountQueriesRepository→KalanMoney.Domain.UseCases.Repositories.IAccountQueriesRepository
- Direction
- Persistence.CosmosDB.Repositories uses Domain.UseCases.Repositories, so a change to Domain.UseCases.Repositories can break Persistence.CosmosDB.Repositories, while a change to Persistence.CosmosDB.Repositories can't break Domain.UseCases.Repositories.
- Position
- Below the diagonal: Persistence.CosmosDB.Repositories uses a module listed above it, which is the healthy direction.
19→4 Persistence.MemoryDatabase uses Domain.Entities.ValueObjects✕
- Connections
- 2 pairs of types, where a type in Persistence.MemoryDatabase uses a type in Domain.Entities.ValueObjects.
- The types involved
KalanMoney.Persistence.MemoryDatabase.AccountsMemoryRepository→KalanMoney.Domain.Entities.ValueObjects.BalanceKalanMoney.Persistence.MemoryDatabase.AccountsMemoryRepository→KalanMoney.Domain.Entities.ValueObjects.Category
- Direction
- Persistence.MemoryDatabase uses Domain.Entities.ValueObjects, so a change to Domain.Entities.ValueObjects can break Persistence.MemoryDatabase, while a change to Persistence.MemoryDatabase can't break Domain.Entities.ValueObjects.
- Position
- Below the diagonal: Persistence.MemoryDatabase uses a module listed above it, which is the healthy direction.
19→7 Persistence.MemoryDatabase uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Persistence.MemoryDatabase uses a type in Domain.Entities.
- The types involved
KalanMoney.Persistence.MemoryDatabase.AccountsMemoryRepository→KalanMoney.Domain.Entities.FinancialAccountKalanMoney.Persistence.MemoryDatabase.AccountsMemoryRepository→KalanMoney.Domain.Entities.Transaction
- Direction
- Persistence.MemoryDatabase uses Domain.Entities, so a change to Domain.Entities can break Persistence.MemoryDatabase, while a change to Persistence.MemoryDatabase can't break Domain.Entities.
- Position
- Below the diagonal: Persistence.MemoryDatabase uses a module listed above it, which is the healthy direction.
19→8 Persistence.MemoryDatabase uses Domain.UseCases.Repositories.Models✕
- Connections
- 2 pairs of types, where a type in Persistence.MemoryDatabase uses a type in Domain.UseCases.Repositories.Models.
- The types involved
KalanMoney.Persistence.MemoryDatabase.AccountsMemoryRepository→KalanMoney.Domain.UseCases.Repositories.Models.DateRangeFilterKalanMoney.Persistence.MemoryDatabase.AccountsMemoryRepository→KalanMoney.Domain.UseCases.Repositories.Models.GetTransactionsFilters
- Direction
- Persistence.MemoryDatabase uses Domain.UseCases.Repositories.Models, so a change to Domain.UseCases.Repositories.Models can break Persistence.MemoryDatabase, while a change to Persistence.MemoryDatabase can't break Domain.UseCases.Repositories.Models.
- Position
- Below the diagonal: Persistence.MemoryDatabase uses a module listed above it, which is the healthy direction.
19→9 Persistence.MemoryDatabase uses Domain.UseCases.Repositories✕
- Connections
- 2 pairs of types, where a type in Persistence.MemoryDatabase uses a type in Domain.UseCases.Repositories.
- The types involved
KalanMoney.Persistence.MemoryDatabase.AccountsMemoryRepository→KalanMoney.Domain.UseCases.Repositories.IAccountCommandsRepositoryKalanMoney.Persistence.MemoryDatabase.AccountsMemoryRepository→KalanMoney.Domain.UseCases.Repositories.IAccountQueriesRepository
- Direction
- Persistence.MemoryDatabase uses Domain.UseCases.Repositories, so a change to Domain.UseCases.Repositories can break Persistence.MemoryDatabase, while a change to Persistence.MemoryDatabase can't break Domain.UseCases.Repositories.
- Position
- Below the diagonal: Persistence.MemoryDatabase uses a module listed above it, which is the healthy direction.
19→11 Persistence.MemoryDatabase uses Persistence.MemoryDatabase.DTOs✕
- Connections
- 2 pairs of types, where a type in Persistence.MemoryDatabase uses a type in Persistence.MemoryDatabase.DTOs.
- The types involved
KalanMoney.Persistence.MemoryDatabase.AccountsMemoryRepository→KalanMoney.Persistence.MemoryDatabase.DTOs.FinancialAccountModelKalanMoney.Persistence.MemoryDatabase.MemoryDb→KalanMoney.Persistence.MemoryDatabase.DTOs.FinancialAccountModel
- Direction
- Persistence.MemoryDatabase uses Persistence.MemoryDatabase.DTOs, so a change to Persistence.MemoryDatabase.DTOs can break Persistence.MemoryDatabase, while a change to Persistence.MemoryDatabase can't break Persistence.MemoryDatabase.DTOs.
- Position
- Below the diagonal: Persistence.MemoryDatabase uses a module listed above it, which is the healthy direction.
20→9 Startup uses Domain.UseCases.Repositories✕
- Connections
- 2 pairs of types, where a type in Startup uses a type in Domain.UseCases.Repositories.
- The types involved
KalanMoney.Startup.AccountUseCaseServiceRegistration→KalanMoney.Domain.UseCases.Repositories.IAccountCommandsRepositoryKalanMoney.Startup.AccountUseCaseServiceRegistration→KalanMoney.Domain.UseCases.Repositories.IAccountQueriesRepository
- Direction
- Startup uses Domain.UseCases.Repositories, so a change to Domain.UseCases.Repositories can break Startup, while a change to Startup can't break Domain.UseCases.Repositories.
- Position
- Below the diagonal: Startup uses a module listed above it, which is the healthy direction.
21→1 API.Functions.AccountDashboard uses API.Functions✕
- Connections
- 1 pair of types, where a type in API.Functions.AccountDashboard uses a type in API.Functions.
- The types involved
KalanMoney.API.Functions.AccountDashboard.AccountDashboardFunction→KalanMoney.API.Functions.BaseRequestFunction
- Direction
- API.Functions.AccountDashboard uses API.Functions, so a change to API.Functions can break API.Functions.AccountDashboard, while a change to API.Functions.AccountDashboard can't break API.Functions.
- Position
- Below the diagonal: API.Functions.AccountDashboard uses a module listed above it, which is the healthy direction.
21→2 API.Functions.AccountDashboard uses API.Functions.Commons✕
- Connections
- 1 pair of types, where a type in API.Functions.AccountDashboard uses a type in API.Functions.Commons.
- The types involved
KalanMoney.API.Functions.AccountDashboard.AccountDashboardPresenter→KalanMoney.API.Functions.Commons.TransactionResponse
- Direction
- API.Functions.AccountDashboard uses API.Functions.Commons, so a change to API.Functions.Commons can break API.Functions.AccountDashboard, while a change to API.Functions.AccountDashboard can't break API.Functions.Commons.
- Position
- Below the diagonal: API.Functions.AccountDashboard uses a module listed above it, which is the healthy direction.
21→14 API.Functions.AccountDashboard uses Domain.UseCases.GetAccountDashboard✕
- Connections
- 3 pairs of types, where a type in API.Functions.AccountDashboard uses a type in Domain.UseCases.GetAccountDashboard.
- The types involved
KalanMoney.API.Functions.AccountDashboard.AccountDashboardFunction→KalanMoney.Domain.UseCases.GetAccountDashboard.IAccountDashboardInputKalanMoney.API.Functions.AccountDashboard.AccountDashboardPresenter→KalanMoney.Domain.UseCases.GetAccountDashboard.AccountDashboardResponseKalanMoney.API.Functions.AccountDashboard.AccountDashboardPresenter→KalanMoney.Domain.UseCases.GetAccountDashboard.IAccountDashboardOutput
- Direction
- API.Functions.AccountDashboard uses Domain.UseCases.GetAccountDashboard, so a change to Domain.UseCases.GetAccountDashboard can break API.Functions.AccountDashboard, while a change to API.Functions.AccountDashboard can't break Domain.UseCases.GetAccountDashboard.
- Position
- Below the diagonal: API.Functions.AccountDashboard uses a module listed above it, which is the healthy direction.
22→1 API.Functions.AddIncomeTransaction uses API.Functions✕
- Connections
- 1 pair of types, where a type in API.Functions.AddIncomeTransaction uses a type in API.Functions.
- The types involved
KalanMoney.API.Functions.AddIncomeTransaction.AddIncomeTransactionRequestFunction→KalanMoney.API.Functions.BaseRequestFunction
- Direction
- API.Functions.AddIncomeTransaction uses API.Functions, so a change to API.Functions can break API.Functions.AddIncomeTransaction, while a change to API.Functions.AddIncomeTransaction can't break API.Functions.
- Position
- Below the diagonal: API.Functions.AddIncomeTransaction uses a module listed above it, which is the healthy direction.
22→6 API.Functions.AddIncomeTransaction uses Domain.UseCases.Common.Models✕
- Connections
- 1 pair of types, where a type in API.Functions.AddIncomeTransaction uses a type in Domain.UseCases.Common.Models.
- The types involved
KalanMoney.API.Functions.AddIncomeTransaction.AddIncomeTransactionPresenter→KalanMoney.Domain.UseCases.Common.Models.AddTransactionResponse
- Direction
- API.Functions.AddIncomeTransaction uses Domain.UseCases.Common.Models, so a change to Domain.UseCases.Common.Models can break API.Functions.AddIncomeTransaction, while a change to API.Functions.AddIncomeTransaction can't break Domain.UseCases.Common.Models.
- Position
- Below the diagonal: API.Functions.AddIncomeTransaction uses a module listed above it, which is the healthy direction.
22→12 API.Functions.AddIncomeTransaction uses Domain.UseCases.AddIncomeTransaction✕
- Connections
- 2 pairs of types, where a type in API.Functions.AddIncomeTransaction uses a type in Domain.UseCases.AddIncomeTransaction.
- The types involved
KalanMoney.API.Functions.AddIncomeTransaction.AddIncomeTransactionPresenter→KalanMoney.Domain.UseCases.AddIncomeTransaction.IAddIncomeTransactionOutputKalanMoney.API.Functions.AddIncomeTransaction.AddIncomeTransactionRequestFunction→KalanMoney.Domain.UseCases.AddIncomeTransaction.IAddIncomeTransactionInput
- Direction
- API.Functions.AddIncomeTransaction uses Domain.UseCases.AddIncomeTransaction, so a change to Domain.UseCases.AddIncomeTransaction can break API.Functions.AddIncomeTransaction, while a change to API.Functions.AddIncomeTransaction can't break Domain.UseCases.AddIncomeTransaction.
- Position
- Below the diagonal: API.Functions.AddIncomeTransaction uses a module listed above it, which is the healthy direction.
23→1 API.Functions.AddOutcomeTransaction uses API.Functions✕
- Connections
- 1 pair of types, where a type in API.Functions.AddOutcomeTransaction uses a type in API.Functions.
- The types involved
KalanMoney.API.Functions.AddOutcomeTransaction.AddOutcomeTransactionRequestFunction→KalanMoney.API.Functions.BaseRequestFunction
- Direction
- API.Functions.AddOutcomeTransaction uses API.Functions, so a change to API.Functions can break API.Functions.AddOutcomeTransaction, while a change to API.Functions.AddOutcomeTransaction can't break API.Functions.
- Position
- Below the diagonal: API.Functions.AddOutcomeTransaction uses a module listed above it, which is the healthy direction.
23→6 API.Functions.AddOutcomeTransaction uses Domain.UseCases.Common.Models✕
- Connections
- 1 pair of types, where a type in API.Functions.AddOutcomeTransaction uses a type in Domain.UseCases.Common.Models.
- The types involved
KalanMoney.API.Functions.AddOutcomeTransaction.AddOutcomeTransactionPresenter→KalanMoney.Domain.UseCases.Common.Models.AddTransactionResponse
- Direction
- API.Functions.AddOutcomeTransaction uses Domain.UseCases.Common.Models, so a change to Domain.UseCases.Common.Models can break API.Functions.AddOutcomeTransaction, while a change to API.Functions.AddOutcomeTransaction can't break Domain.UseCases.Common.Models.
- Position
- Below the diagonal: API.Functions.AddOutcomeTransaction uses a module listed above it, which is the healthy direction.
23→13 API.Functions.AddOutcomeTransaction uses Domain.UseCases.AddOutcomeTransaction✕
- Connections
- 2 pairs of types, where a type in API.Functions.AddOutcomeTransaction uses a type in Domain.UseCases.AddOutcomeTransaction.
- The types involved
KalanMoney.API.Functions.AddOutcomeTransaction.AddOutcomeTransactionPresenter→KalanMoney.Domain.UseCases.AddOutcomeTransaction.IAddOutcomeTransactionOutputKalanMoney.API.Functions.AddOutcomeTransaction.AddOutcomeTransactionRequestFunction→KalanMoney.Domain.UseCases.AddOutcomeTransaction.IAddOutcomeTransactionInput
- Direction
- API.Functions.AddOutcomeTransaction uses Domain.UseCases.AddOutcomeTransaction, so a change to Domain.UseCases.AddOutcomeTransaction can break API.Functions.AddOutcomeTransaction, while a change to API.Functions.AddOutcomeTransaction can't break Domain.UseCases.AddOutcomeTransaction.
- Position
- Below the diagonal: API.Functions.AddOutcomeTransaction uses a module listed above it, which is the healthy direction.
24→1 API.Functions.GetCategoriesByAccount uses API.Functions✕
- Connections
- 1 pair of types, where a type in API.Functions.GetCategoriesByAccount uses a type in API.Functions.
- The types involved
KalanMoney.API.Functions.GetCategoriesByAccount.GetCategoriesFunction→KalanMoney.API.Functions.BaseRequestFunction
- Direction
- API.Functions.GetCategoriesByAccount uses API.Functions, so a change to API.Functions can break API.Functions.GetCategoriesByAccount, while a change to API.Functions.GetCategoriesByAccount can't break API.Functions.
- Position
- Below the diagonal: API.Functions.GetCategoriesByAccount uses a module listed above it, which is the healthy direction.
24→4 API.Functions.GetCategoriesByAccount uses Domain.Entities.ValueObjects✕
- Connections
- 1 pair of types, where a type in API.Functions.GetCategoriesByAccount uses a type in Domain.Entities.ValueObjects.
- The types involved
KalanMoney.API.Functions.GetCategoriesByAccount.GetCategoriesPresenter→KalanMoney.Domain.Entities.ValueObjects.Category
- Direction
- API.Functions.GetCategoriesByAccount uses Domain.Entities.ValueObjects, so a change to Domain.Entities.ValueObjects can break API.Functions.GetCategoriesByAccount, while a change to API.Functions.GetCategoriesByAccount can't break Domain.Entities.ValueObjects.
- Position
- Below the diagonal: API.Functions.GetCategoriesByAccount uses a module listed above it, which is the healthy direction.
24→15 API.Functions.GetCategoriesByAccount uses Domain.UseCases.GetCategoriesByAccount✕
- Connections
- 2 pairs of types, where a type in API.Functions.GetCategoriesByAccount uses a type in Domain.UseCases.GetCategoriesByAccount.
- The types involved
KalanMoney.API.Functions.GetCategoriesByAccount.GetCategoriesFunction→KalanMoney.Domain.UseCases.GetCategoriesByAccount.IGetCategoriesByAccountInputKalanMoney.API.Functions.GetCategoriesByAccount.GetCategoriesPresenter→KalanMoney.Domain.UseCases.GetCategoriesByAccount.IGetCategoriesByAccountOutput
- Direction
- API.Functions.GetCategoriesByAccount uses Domain.UseCases.GetCategoriesByAccount, so a change to Domain.UseCases.GetCategoriesByAccount can break API.Functions.GetCategoriesByAccount, while a change to API.Functions.GetCategoriesByAccount can't break Domain.UseCases.GetCategoriesByAccount.
- Position
- Below the diagonal: API.Functions.GetCategoriesByAccount uses a module listed above it, which is the healthy direction.
25→1 API.Functions.GetMonthlyTransactions uses API.Functions✕
- Connections
- 1 pair of types, where a type in API.Functions.GetMonthlyTransactions uses a type in API.Functions.
- The types involved
KalanMoney.API.Functions.GetMonthlyTransactions.GetMonthlyTransactionsFunction→KalanMoney.API.Functions.BaseRequestFunction
- Direction
- API.Functions.GetMonthlyTransactions uses API.Functions, so a change to API.Functions can break API.Functions.GetMonthlyTransactions, while a change to API.Functions.GetMonthlyTransactions can't break API.Functions.
- Position
- Below the diagonal: API.Functions.GetMonthlyTransactions uses a module listed above it, which is the healthy direction.
25→2 API.Functions.GetMonthlyTransactions uses API.Functions.Commons✕
- Connections
- 1 pair of types, where a type in API.Functions.GetMonthlyTransactions uses a type in API.Functions.Commons.
- The types involved
KalanMoney.API.Functions.GetMonthlyTransactions.GetMonthlyTransactionsPresenter→KalanMoney.API.Functions.Commons.TransactionResponse
- Direction
- API.Functions.GetMonthlyTransactions uses API.Functions.Commons, so a change to API.Functions.Commons can break API.Functions.GetMonthlyTransactions, while a change to API.Functions.GetMonthlyTransactions can't break API.Functions.Commons.
- Position
- Below the diagonal: API.Functions.GetMonthlyTransactions uses a module listed above it, which is the healthy direction.
25→7 API.Functions.GetMonthlyTransactions uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in API.Functions.GetMonthlyTransactions uses a type in Domain.Entities.
- The types involved
KalanMoney.API.Functions.GetMonthlyTransactions.GetMonthlyTransactionsPresenter→KalanMoney.Domain.Entities.Transaction
- Direction
- API.Functions.GetMonthlyTransactions uses Domain.Entities, so a change to Domain.Entities can break API.Functions.GetMonthlyTransactions, while a change to API.Functions.GetMonthlyTransactions can't break Domain.Entities.
- Position
- Below the diagonal: API.Functions.GetMonthlyTransactions uses a module listed above it, which is the healthy direction.
25→16 API.Functions.GetMonthlyTransactions uses Domain.UseCases.GetMonthlyTransactions✕
- Connections
- 2 pairs of types, where a type in API.Functions.GetMonthlyTransactions uses a type in Domain.UseCases.GetMonthlyTransactions.
- The types involved
KalanMoney.API.Functions.GetMonthlyTransactions.GetMonthlyTransactionsFunction→KalanMoney.Domain.UseCases.GetMonthlyTransactions.IGetMonthlyTransactionsInputKalanMoney.API.Functions.GetMonthlyTransactions.GetMonthlyTransactionsPresenter→KalanMoney.Domain.UseCases.GetMonthlyTransactions.IGetMonthlyTransactionsOutput
- Direction
- API.Functions.GetMonthlyTransactions uses Domain.UseCases.GetMonthlyTransactions, so a change to Domain.UseCases.GetMonthlyTransactions can break API.Functions.GetMonthlyTransactions, while a change to API.Functions.GetMonthlyTransactions can't break Domain.UseCases.GetMonthlyTransactions.
- Position
- Below the diagonal: API.Functions.GetMonthlyTransactions uses a module listed above it, which is the healthy direction.
26→17 Domain.UseCases.Adapters uses Domain.UseCases.OpenAccount✕
- Connections
- 2 pairs of types, where a type in Domain.UseCases.Adapters uses a type in Domain.UseCases.OpenAccount.
- The types involved
KalanMoney.Domain.UseCases.Adapters.IOpenAccountInput→KalanMoney.Domain.UseCases.OpenAccount.CreateAccountRequestKalanMoney.Domain.UseCases.Adapters.IOpenAccountInput→KalanMoney.Domain.UseCases.OpenAccount.IOpenAccountOutput
- Direction
- Domain.UseCases.Adapters uses Domain.UseCases.OpenAccount, so a change to Domain.UseCases.OpenAccount can break Domain.UseCases.Adapters, while a change to Domain.UseCases.Adapters can't break Domain.UseCases.OpenAccount.
- Position
- Below the diagonal: Domain.UseCases.Adapters uses a module listed above it, which is the healthy direction.
27→1 API.Functions.OpenAccount uses API.Functions✕
- Connections
- 1 pair of types, where a type in API.Functions.OpenAccount uses a type in API.Functions.
- The types involved
KalanMoney.API.Functions.OpenAccount.OpenAccountRequestFunction→KalanMoney.API.Functions.BaseRequestFunction
- Direction
- API.Functions.OpenAccount uses API.Functions, so a change to API.Functions can break API.Functions.OpenAccount, while a change to API.Functions.OpenAccount can't break API.Functions.
- Position
- Below the diagonal: API.Functions.OpenAccount uses a module listed above it, which is the healthy direction.
27→17 API.Functions.OpenAccount uses Domain.UseCases.OpenAccount✕
- Connections
- 2 pairs of types, where a type in API.Functions.OpenAccount uses a type in Domain.UseCases.OpenAccount.
- The types involved
KalanMoney.API.Functions.OpenAccount.OpenAccountPresenter→KalanMoney.Domain.UseCases.OpenAccount.IOpenAccountOutputKalanMoney.API.Functions.OpenAccount.OpenAccountPresenter→KalanMoney.Domain.UseCases.OpenAccount.OpenAccountResponse
- Direction
- API.Functions.OpenAccount uses Domain.UseCases.OpenAccount, so a change to Domain.UseCases.OpenAccount can break API.Functions.OpenAccount, while a change to API.Functions.OpenAccount can't break Domain.UseCases.OpenAccount.
- Position
- Below the diagonal: API.Functions.OpenAccount uses a module listed above it, which is the healthy direction.
27→26 API.Functions.OpenAccount uses Domain.UseCases.Adapters✕
- Connections
- 1 pair of types, where a type in API.Functions.OpenAccount uses a type in Domain.UseCases.Adapters.
- The types involved
KalanMoney.API.Functions.OpenAccount.OpenAccountRequestFunction→KalanMoney.Domain.UseCases.Adapters.IOpenAccountInput
- Direction
- API.Functions.OpenAccount uses Domain.UseCases.Adapters, so a change to Domain.UseCases.Adapters can break API.Functions.OpenAccount, while a change to API.Functions.OpenAccount can't break Domain.UseCases.Adapters.
- Position
- Below the diagonal: API.Functions.OpenAccount uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 8 | High / Critical |
Roadmap
Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2); Resolve the 4 Orphaned file finding(s) in Knowledge Freshness — start with AccountQueriesRepository.cs, AccountsMemoryRepository.cs, AccountUseCaseServiceRegistration.cs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a CI workflow that builds and runs the test suite on every push/PR. | +8.8 pts | Medium | CI/CD gates |
| Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2). | +3.0 pts | Low | Documentation Quality |
| Resolve the 4 Orphaned file finding(s) in Knowledge Freshness — start with AccountQueriesRepository.cs, AccountsMemoryRepository.cs, AccountUseCaseServiceRegistration.cs. | +2.8 pts | Low | Knowledge Freshness |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +1.8 pts | Low | Knowledge Freshness |
| 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. | +2.2 pts | Medium | Architecture documentation |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +1.3 pts | Medium | Documentation (README) |
| Sync-over-async (deadlock risk) | +1.2 pts | Medium | Async correctness |
| Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult(). | +1.2 pts | Medium | Async & latency hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.5 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| KalanMoney/KalanMoney.Domain.Entities/KalanMoney.Domain.Entities.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| KalanMoney/KalanMoney.Domain.UseCases.Tests/KalanMoney.Domain.UseCases.Tests.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| KalanMoney/KalanMoney.Domain.UseCases/KalanMoney.Domain.UseCases.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| KalanMoney/KalanMoney.Persistence.MemoryDatabase.Tests/KalanMoney.Persistence.MemoryDatabase.Tests.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| KalanMoney/KalanMoney.Persistence.MemoryDatabase/KalanMoney.Persistence.MemoryDatabase.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| KalanMoney/KalanMoney.Startup/KalanMoney.Startup.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| KalanMoney/KalanMoney.API.Functions.Tests/AccountDashboardTests/AccountDashboardFunctionTest.cs | 8.2 | Near-clean | Explicit Debt: BareSuppressMessage |
| KalanMoney/KalanMoney.Domain.UseCases.Tests/GetCategoriesByAccountTests/GetCategoriesByAccountUseCaseTest.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| KalanMoney/KalanMoney.API.Functions.Tests/AddIncomeTransactionTests/AddIncomeTransactionFunctionTest.cs | 8.2 | Near-clean | Explicit Debt: Dead code: CreateHttpRequestWithoutNoBody |
| KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountQueriesRepository.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (25–29 lines × 2) |
| KalanMoney/KalanMoney.API.Functions/AddIncomeTransaction/AddIncomeTransactionRequestFunction.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
| KalanMoney/KalanMoney.Domain.UseCases/AddIncomeTransaction/AddIncomeTransaction.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| README.md | 9.3 | Near-clean | Documentation Quality: Documentation: no build, run or usage example |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 70 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 70 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 59 of 70 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — 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. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- 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 scored — the test tier(s) ran but surfaced none of this repository's 81 test method(s) to the runner, so flakiness couldn't be exercised. This is an analysis-environment limitation, not a finding about the tests.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- 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 109 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.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D39 IL Efficiency — 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. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
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.
D4 · Code Duplication
3 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (25–29 lines × 2) finding(s) in Code Duplication — start with AccountQueriesRepository.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with AddIncomeTransactionRequestFunction.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with AddIncomeTransaction.cs. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
10 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 9 classes have LCOM4 above 3.
D9 · Test Distribution
81 test methods: 81 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 2 mock references across 81 tests.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 239 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 11 direct `PackageReference`(s), and 221 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
2 deducted debt markers + 1 dead symbols across 1501 LoC in the .NET projects (0.2/KLoC) → score 9.5.
What to do
- Resolve the 1 BareSuppressMessage finding(s) in Explicit Debt — start with AccountDashboardFunctionTest.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with GetCategoriesByAccountUseCaseTest.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Dead code finding(s) in Explicit Debt — start with AddIncomeTransactionFunctionTest.cs. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
10 projects, 103 source files, 3200 hand-written lines of code (1501 production / 1699 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 13 inter-project edges.
D19 · Documentation Quality
0 of 2 documentation facets pass in full; short on: F2 example, F4 map. 1 document(s) read across 7 unit(s).
What to do
- Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2). — One of this dimension's main actionable groups (2 recommendation-level).
D26 · Project Cohesion
0 of 10 projects flagged as possibly oversized/incoherent.
D27 · Navigability
91 % of calls cross a namespace and 8 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
8 finding(s): 0 critical, 6 high, 2 medium, 0 low.
What to do
- Resolve the 6 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
4 of 4 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountQueriesRepository.cs. Counted over 4 of the 73 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 4 Orphaned file finding(s) in Knowledge Freshness — start with AccountQueriesRepository.cs, AccountsMemoryRepository.cs, AccountUseCaseServiceRegistration.cs. — One of this dimension's main actionable groups (4 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 10 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 10 End-of-life runtime finding(s) in Platform End-of-Life — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (10 warning-level).
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
- The namespaces KalanMoney.Domain.UseCases.Adapters ↔ KalanMoney.Domain.UseCases.OpenAccount depend on each other. The lightest dependency in the cycle is KalanMoney.Domain.UseCases.OpenAccount → KalanMoney.Domain.UseCases.Adapters (KalanMoney.Domain.UseCases.OpenAccount.OpenAccount → KalanMoney.Domain.UseCases.Adapters.IOpenAccountInput, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — KalanMoney/KalanMoney.Domain.UseCases/OpenAccount/OpenAccount.cs:4
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
- `KalanMoney.Startup` (production) references the test project `KalanMoney.Domain.UseCases.Tests`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — KalanMoney/KalanMoney.Startup/KalanMoney.Startup.csproj:15
What to do
- Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
DM11 · Constructible invalid state
- `FinancialAccount`'s public constructor takes `ownerId`, `ownerName` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `FinancialAccount` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — KalanMoney/KalanMoney.Domain.Entities/FinancialAccount.cs:7
- `Transaction`'s public constructor takes `id`, `amount` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Transaction` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — KalanMoney/KalanMoney.Domain.Entities/Transaction.cs:7
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
- `DateRangeFilter` reads `DateTime.UtcNow` inside `CreateMonthRangeFromUtcNow`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — KalanMoney/KalanMoney.Domain.UseCases/Repositories/Models/DateRangeFilter.cs:7
- `TimeStamp` reads `DateTimeOffset.UtcNow` inside `CreateNow`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — KalanMoney/KalanMoney.Domain.Entities/ValueObjects/TimeStamp.cs:15
What to do
- Pass the instant into the domain method that needs it, or inject `TimeProvider` (BCL, .NET 8+) and read it there — then a test can choose the moment a rule is evaluated at.
DM4 · Rich vs anemic model
- `FinancialAccount` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — KalanMoney/KalanMoney.Domain.Entities/FinancialAccount.cs:5
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
DM7 · Repository granularity
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — KalanMoney/KalanMoney.Persistence.MemoryDatabase/AccountsMemoryRepository.cs:70
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
- `RunAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — KalanMoney/KalanMoney.API.Functions/GetCategoriesByAccount/GetCategoriesFunction.cs:25
- `GetCategoriesByAccount` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — KalanMoney/KalanMoney.Persistence.MemoryDatabase/AccountsMemoryRepository.cs:70
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — 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.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 6 of 6 project(s) that lack one — worth up to 2 pts.
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
- Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
What to do
- Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `REDACTED` 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`. — REDACTED:11
What to do
- Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
PF3 · Async & latency hygiene
- 6 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
- `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×6) — KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountCommandsRepository.cs:32, KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountCommandsRepository.cs:51, KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountQueriesRepository.cs:44, …
What to do
- Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
X1 · Async correctness
- Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×6) — KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountCommandsRepository.cs:29, KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountCommandsRepository.cs:43, KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountQueriesRepository.cs:41, …
What to do
- Sync-over-async (deadlock risk)
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
X20 · Mistyped argument guard
- The guard on line 14 rejects `category` and line 14 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(category)` is true of a value that is NOT null: it is satisfied by an EMPTY `category`, and on that path `category` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — KalanMoney/KalanMoney.Domain.Entities/ValueObjects/Category.cs:14
- The guard on line 17 rejects `description` and line 18 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(description)` is true of a value that is NOT null: it is satisfied by an EMPTY `description`, and on that path `description` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — KalanMoney/KalanMoney.Domain.Entities/ValueObjects/Description.cs:18
What to do
- Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
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
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
- Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×4) — KalanMoney/KalanMoney.API.Functions/AccountDashboard/AccountDashboardFunction.cs:42, KalanMoney/KalanMoney.API.Functions/GetCategoriesByAccount/GetCategoriesFunction.cs:48, KalanMoney/KalanMoney.API.Functions/GetMonthlyTransactions/GetMonthlyTransactionsFunction.cs:68, …
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 5/6 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
- ~0.5 `!` suppressions per 1k syntax nodes — 3 suppression(s) across the 5754 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 55% | Adequate — gated by X1, X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 78% | Strong | Solid. |
| Maturity | 51% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 36% | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 87% | Strong | Strongest area. |
| Domain Modelling | 62% | Adequate — gated by DM4, DM11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Adequate | Acceptable, with room to improve. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 3 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 57 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D11 Test Reliability — Test runner surfaced no tests
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (427 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (1,501 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (1 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM8 Value-object opportunities — not scored — the deterministic rule found 1 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- 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 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) 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 — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no async method does work a token could cancel
- 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 — 8 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Namespace dependency cycle KalanMoney/KalanMoney.Domain.UseCases/OpenAccount/OpenAccount.cs:4
- Production project references a test project: KalanMoney.Startup → KalanMoney.Domain.UseCases.Tests KalanMoney/KalanMoney.Startup/KalanMoney.Startup.csproj:15
Serious — 43 finding(s)
- End-of-life runtime: .NET net6.0 REDACTED:4
- End-of-life runtime: .NET net6.0 REDACTED:3
- End-of-life runtime: .NET net6.0 REDACTED:4
- End-of-life runtime: .NET net6.0 KalanMoney/KalanMoney.Domain.Entities/KalanMoney.Domain.Entities.csproj:4
- End-of-life runtime: .NET net6.0 KalanMoney/KalanMoney.Domain.UseCases.Tests/KalanMoney.Domain.UseCases.Tests.csproj:4
- End-of-life runtime: .NET net6.0 KalanMoney/KalanMoney.Domain.UseCases/KalanMoney.Domain.UseCases.csproj:4
- End-of-life runtime: .NET net6.0 REDACTED:4
- End-of-life runtime: .NET net6.0 KalanMoney/KalanMoney.Persistence.MemoryDatabase.Tests/KalanMoney.Persistence.MemoryDatabase.Tests.csproj:4
- End-of-life runtime: .NET net6.0 KalanMoney/KalanMoney.Persistence.MemoryDatabase/KalanMoney.Persistence.MemoryDatabase.csproj:4
- End-of-life runtime: .NET net6.0 KalanMoney/KalanMoney.Startup/KalanMoney.Startup.csproj:4
- Sync-over-async blocking
- Sync-over-async blocking KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountCommandsRepository.cs:32
- Sync-over-async blocking KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountCommandsRepository.cs:51
- Sync-over-async blocking KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountQueriesRepository.cs:44
- Sync-over-async blocking KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountQueriesRepository.cs:75
- Sync-over-async blocking KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountQueriesRepository.cs:114
- Sync-over-async blocking KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountQueriesRepository.cs:156
- Sync-over-async (deadlock risk) KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountCommandsRepository.cs:29
- Sync-over-async (deadlock risk) KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountCommandsRepository.cs:43
- Sync-over-async (deadlock risk) KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountQueriesRepository.cs:41
- Sync-over-async (deadlock risk) KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountQueriesRepository.cs:72
- Sync-over-async (deadlock risk) KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountQueriesRepository.cs:111
- Sync-over-async (deadlock risk) KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountQueriesRepository.cs:153
- REDACTED
- REDACTED
- Constructible in an invalid state: FinancialAccount KalanMoney/KalanMoney.Domain.Entities/FinancialAccount.cs:7
- Constructible in an invalid state: Transaction KalanMoney/KalanMoney.Domain.Entities/Transaction.cs:7
- Domain type reads the wall clock: DateRangeFilter KalanMoney/KalanMoney.Domain.UseCases/Repositories/Models/DateRangeFilter.cs:7
- Domain type reads the wall clock: TimeStamp KalanMoney/KalanMoney.Domain.Entities/ValueObjects/TimeStamp.cs:15
- Argument guard throws the exception its own condition disproves KalanMoney/KalanMoney.Domain.Entities/ValueObjects/Category.cs:14
- Argument guard throws the exception its own condition disproves KalanMoney/KalanMoney.Domain.Entities/ValueObjects/Description.cs:18
- BareSuppressMessage KalanMoney/KalanMoney.API.Functions.Tests/AccountDashboardTests/AccountDashboardFunctionTest.cs:52
- TodoComment KalanMoney/KalanMoney.Domain.UseCases.Tests/GetCategoriesByAccountTests/GetCategoriesByAccountUseCaseTest.cs:156
- Dead code: CreateHttpRequestWithoutNoBody KalanMoney/KalanMoney.API.Functions.Tests/AddIncomeTransactionTests/AddIncomeTransactionFunctionTest.cs:84
- Duplicated block (25–29 lines × 2) KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountQueriesRepository.cs:25
- Duplicated block (6 lines × 2) KalanMoney/KalanMoney.API.Functions/AddIncomeTransaction/AddIncomeTransactionRequestFunction.cs:44
- Duplicated block (7 lines × 2) KalanMoney/KalanMoney.Domain.UseCases/AddIncomeTransaction/AddIncomeTransaction.cs:32
- Anemic entity: FinancialAccount KalanMoney/KalanMoney.Domain.Entities/FinancialAccount.cs:5
- Unfinished stub — throws NotImplementedException KalanMoney/KalanMoney.Persistence.MemoryDatabase/AccountsMemoryRepository.cs:70
- Fake-async — async method never awaits KalanMoney/KalanMoney.API.Functions/GetCategoriesByAccount/GetCategoriesFunction.cs:25
- Unfinished stub — throws NotImplementedException KalanMoney/KalanMoney.Persistence.MemoryDatabase/AccountsMemoryRepository.cs:70
- No CI pipeline
- NuGet dependencies are not locked
Minor — 17 finding(s)
- Orphaned file KalanMoney/KalanMoney.Persistence.CosmosDB/Repositories/AccountQueriesRepository.cs:1
- Orphaned file KalanMoney/KalanMoney.Persistence.MemoryDatabase/AccountsMemoryRepository.cs:1
- Orphaned file KalanMoney/KalanMoney.Startup/AccountUseCaseServiceRegistration.cs:1
- Orphaned file KalanMoney/KalanMoney.API.Functions/GetMonthlyTransactions/GetMonthlyTransactionsFunction.cs:1
- Interpolated log message defeats structured logging KalanMoney/KalanMoney.API.Functions/AccountDashboard/AccountDashboardFunction.cs:42
- Interpolated log message defeats structured logging KalanMoney/KalanMoney.API.Functions/GetCategoriesByAccount/GetCategoriesFunction.cs:48
- Interpolated log message defeats structured logging KalanMoney/KalanMoney.API.Functions/GetMonthlyTransactions/GetMonthlyTransactionsFunction.cs:68
- Interpolated log message defeats structured logging KalanMoney/KalanMoney.API.Functions/OpenAccount/OpenAccountRequestFunction.cs:54
- Documentation: no build, run or usage example README.md:1
- Documentation: no map of the repository's parts README.md:1
- Orphaned files with no living knowledge
- No ADRs
- No tests/ separation
- No SAST
- No dependency-update automation REDACTED:11
- Nullable reference types not enabled everywhere
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 2 finding(s)
- Mock framework: Moq
- Mock framework: Moq
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-b992097f761b4a37a261fa6fdbc9973e/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-b992097f761b4a37a261fa6fdbc9973e/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list KalanMoney/KalanMoney.sln package --vulnerable --include-transitive --format json | 8 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-36d4bf92310d470795ce6a8dd1d49826 | 0 | artifacts/raw/osv-scanner.json |