Executive summary
felixsjoberg/Bank.CleanArchitecture.WebApi is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because the project has no automated tests. It scores 36 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 11, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 19 points. Updating the outdated dependencies is another step, worth about 8 points. Raising Production Readiness to 70 would lift the score to about 56.
Nine known security holes in the packages the code depends on can be used by attackers. Two settings leave the servers or containers unsafe, and one password or key is open to anyone who can read the repository. Updating the vulnerable packages, correcting the unsafe settings and replacing the exposed password or key would close these risks. Hashing passwords with a password-hashing function such as Argon2, bcrypt or PBKDF2 would fix the place where passwords are scrambled with a fast general-purpose hash. The three loops of parts of the code that depend on each other need breaking by moving the shared parts into a project of their own.
The product code is 1,719 lines, about €1,600 to rebuild.
If Production Readiness rose from 11 to 70, the lowest score rated Strong, the score would rise from 36 to about 56.
New since the last survey: 6 findings
- Platform End-of-Life · End-of-life runtime: .NET net7.0 BankApplication.Application/BankApplication.Application.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 BankApplication.Domain/BankApplication.Domain.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net7.0 BankApplication.Presentation/BankApplication.Contracts/BankApplication.Contracts.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 REDACTED
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: Loan BankApplication.Domain/Entities/Loan.cs
Fixed since the last survey: 4 findings
- Dependency Hygiene · Vulnerable: System.Data.SqlClient
- Dependency Hygiene · Vulnerable: System.IdentityModel.Tokens.Jwt
- Dependency Hygiene · Vulnerable: Azure.Identity
- Platform End-of-Life · End-of-life runtime: .NET net7.0 REDACTED
Rebuild cost: about €1,600 · Estimate
| Cost to rebuild | €540 to €2,600, for 9 to 28 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, 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 36. 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,719 lines of product code, of which 64% is declarations and boilerplate, 23% straight logic and 13% logic with branches |
| Comment lines | The estimate prices 1,703 lines. Comment lines count towards the size of 1,719 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 (global) | 2 BankApplication.Api | 3 BankApplication.Api.Common.Mapping | 4 BankApplication.Api.Mapping | 5 BankApplication.Api.Service | 6 BankApplication.Application | 7 BankApplication.Application.Accounts | 8 BankApplication.Application.Accounts.Queries.GetAccountById | 9 BankApplication.Application.Adminstrator | 10 BankApplication.Application.Common.Errors | 11 BankApplication.Application.Common.Interfaces.Services | 12 BankApplication.Application.Common.Services | 13 BankApplication.Application.Services.Queries.Login | 14 BankApplication.Contracts.Accounts | 15 BankApplication.Contracts.Adminstrator | 16 BankApplication.Contracts.Authentication | 17 BankApplication.Contracts.Transactions | 18 BankApplication.Api.Controllers | 19 BankApplication.Controllers | 20 BankApplication.Infrastructure | 21 BankApplication.Infrastructure.Services | 22 Domain.Models | 23 Domain.Domains | 24 BankApplication.Application.Authentication.Common | 25 BankApplication.Application.Common.Interfaces | 26 BankApplication.Domain.Aggregates | 27 BankApplication.Application.Accounts.Response.Commands | 28 BankApplication.Application.Adminstrator.Response.Commands | 29 BankApplication.Application.Customers.Response.Commands | 30 BankApplication.Application.Customers.Response.Queries | 31 BankApplication.Infrastructure.Authentication | 32 BankApplication.Application.Customers.Commands.AddAccountCredit | 33 BankApplication.Application.Common.Interfaces.Persistence | 34 BankApplication.Application.Accounts.Queries.GetAccounts | 35 BankApplication.Application.Accounts.Queries.GetTransactionsByAccId | 36 BankApplication.Application.Authentication.Queries.Login | 37 BankApplication.Application.Services.Commands.Register | 38 BankApplication.Application.Transactions.Commands.Transfer | 39 BankApplication.Infrastructure.Presistence | 40 BankApplication.Application.Accounts.Commands |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 BankApplication.Api | ||||||||||||||||||||||||||||||||||||||||
| 3 BankApplication.Api.Common.Mapping | ||||||||||||||||||||||||||||||||||||||||
| 4 BankApplication.Api.Mapping | ||||||||||||||||||||||||||||||||||||||||
| 5 BankApplication.Api.Service | ||||||||||||||||||||||||||||||||||||||||
| 6 BankApplication.Application | ||||||||||||||||||||||||||||||||||||||||
| 7 BankApplication.Application.Accounts | ||||||||||||||||||||||||||||||||||||||||
| 8 BankApplication.Application.Accounts.Queries.GetAccountById | ||||||||||||||||||||||||||||||||||||||||
| 9 BankApplication.Application.Adminstrator | ||||||||||||||||||||||||||||||||||||||||
| 10 BankApplication.Application.Common.Errors | ||||||||||||||||||||||||||||||||||||||||
| 11 BankApplication.Application.Common.Interfaces.Services | ||||||||||||||||||||||||||||||||||||||||
| 12 BankApplication.Application.Common.Services | ||||||||||||||||||||||||||||||||||||||||
| 13 BankApplication.Application.Services.Queries.Login | ||||||||||||||||||||||||||||||||||||||||
| 14 BankApplication.Contracts.Accounts | ||||||||||||||||||||||||||||||||||||||||
| 15 BankApplication.Contracts.Adminstrator | ||||||||||||||||||||||||||||||||||||||||
| 16 BankApplication.Contracts.Authentication | ||||||||||||||||||||||||||||||||||||||||
| 17 BankApplication.Contracts.Transactions | ||||||||||||||||||||||||||||||||||||||||
| 18 BankApplication.Api.Controllers | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 BankApplication.Controllers | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 BankApplication.Infrastructure | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 BankApplication.Infrastructure.Services | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 Domain.Models | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 Domain.Domains | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 BankApplication.Application.Authentication.Common | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 BankApplication.Application.Common.Interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 BankApplication.Domain.Aggregates | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 BankApplication.Application.Accounts.Response.Commands | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 BankApplication.Application.Adminstrator.Response.Commands | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 BankApplication.Application.Customers.Response.Commands | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 BankApplication.Application.Customers.Response.Queries | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 BankApplication.Infrastructure.Authentication | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 BankApplication.Application.Customers.Commands.AddAccountCredit | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 33 BankApplication.Application.Common.Interfaces.Persistence | 1 | 2 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 BankApplication.Application.Accounts.Queries.GetAccounts | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 BankApplication.Application.Accounts.Queries.GetTransactionsByAccId | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 BankApplication.Application.Authentication.Queries.Login | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 BankApplication.Application.Services.Commands.Register | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 BankApplication.Application.Transactions.Commands.Transfer | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 BankApplication.Infrastructure.Presistence | 6 | 1 | 2 | 4 | 1 | 5 | ||||||||||||||||||||||||||||||||||
| 40 BankApplication.Application.Accounts.Commands | 1 | 1 | 1 |
18→5 BankApplication.Api.Controllers uses BankApplication.Api.Service✕
- Connections
- 1 pair of types, where a type in BankApplication.Api.Controllers uses a type in BankApplication.Api.Service.
- The types involved
BankApplication.Api.Controllers.CustomersController→BankApplication.Api.Service.JwtService
- Direction
- BankApplication.Api.Controllers uses BankApplication.Api.Service, so a change to BankApplication.Api.Service can break BankApplication.Api.Controllers, while a change to BankApplication.Api.Controllers can't break BankApplication.Api.Service.
- Position
- Below the diagonal: BankApplication.Api.Controllers uses a module listed above it, which is the healthy direction.
18→14 BankApplication.Api.Controllers uses BankApplication.Contracts.Accounts✕
- Connections
- 2 pairs of types, where a type in BankApplication.Api.Controllers uses a type in BankApplication.Contracts.Accounts.
- The types involved
BankApplication.Api.Controllers.CustomersController→BankApplication.Contracts.Accounts.CreateAccountRequestBankApplication.Api.Controllers.CustomersController→BankApplication.Contracts.Accounts.GetTransactionsByAccIdResultRequest
- Direction
- BankApplication.Api.Controllers uses BankApplication.Contracts.Accounts, so a change to BankApplication.Contracts.Accounts can break BankApplication.Api.Controllers, while a change to BankApplication.Api.Controllers can't break BankApplication.Contracts.Accounts.
- Position
- Below the diagonal: BankApplication.Api.Controllers uses a module listed above it, which is the healthy direction.
18→15 BankApplication.Api.Controllers uses BankApplication.Contracts.Adminstrator✕
- Connections
- 2 pairs of types, where a type in BankApplication.Api.Controllers uses a type in BankApplication.Contracts.Adminstrator.
- The types involved
BankApplication.Api.Controllers.AdminstratorController→BankApplication.Contracts.Adminstrator.AddAccountCreditRequestBankApplication.Api.Controllers.AdminstratorController→BankApplication.Contracts.Adminstrator.NewCustomerAccountRequest
- Direction
- BankApplication.Api.Controllers uses BankApplication.Contracts.Adminstrator, so a change to BankApplication.Contracts.Adminstrator can break BankApplication.Api.Controllers, while a change to BankApplication.Api.Controllers can't break BankApplication.Contracts.Adminstrator.
- Position
- Below the diagonal: BankApplication.Api.Controllers uses a module listed above it, which is the healthy direction.
18→17 BankApplication.Api.Controllers uses BankApplication.Contracts.Transactions✕
- Connections
- 1 pair of types, where a type in BankApplication.Api.Controllers uses a type in BankApplication.Contracts.Transactions.
- The types involved
BankApplication.Api.Controllers.CustomersController→BankApplication.Contracts.Transactions.TransferRequest
- Direction
- BankApplication.Api.Controllers uses BankApplication.Contracts.Transactions, so a change to BankApplication.Contracts.Transactions can break BankApplication.Api.Controllers, while a change to BankApplication.Api.Controllers can't break BankApplication.Contracts.Transactions.
- Position
- Below the diagonal: BankApplication.Api.Controllers uses a module listed above it, which is the healthy direction.
19→16 BankApplication.Controllers uses BankApplication.Contracts.Authentication✕
- Connections
- 2 pairs of types, where a type in BankApplication.Controllers uses a type in BankApplication.Contracts.Authentication.
- The types involved
BankApplication.Controllers.AuthenticationController→BankApplication.Contracts.Authentication.LoginRequestBankApplication.Controllers.AuthenticationController→BankApplication.Contracts.Authentication.RegisterRequest
- Direction
- BankApplication.Controllers uses BankApplication.Contracts.Authentication, so a change to BankApplication.Contracts.Authentication can break BankApplication.Controllers, while a change to BankApplication.Controllers can't break BankApplication.Contracts.Authentication.
- Position
- Below the diagonal: BankApplication.Controllers uses a module listed above it, which is the healthy direction.
20→39 BankApplication.Infrastructure uses BankApplication.Infrastructure.Presistence part of a loop✕
- Connections
- 1 pair of types, where a type in BankApplication.Infrastructure uses a type in BankApplication.Infrastructure.Presistence.
- The types involved
BankApplication.Infrastructure.DapperContext→BankApplication.Infrastructure.Presistence.DapperSettings
- Direction
- BankApplication.Infrastructure uses BankApplication.Infrastructure.Presistence, so a change to BankApplication.Infrastructure.Presistence can break BankApplication.Infrastructure, while a change to BankApplication.Infrastructure can't break BankApplication.Infrastructure.Presistence.
- 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.
21→11 BankApplication.Infrastructure.Services uses BankApplication.Application.Common.Interfaces.Services✕
- Connections
- 1 pair of types, where a type in BankApplication.Infrastructure.Services uses a type in BankApplication.Application.Common.Interfaces.Services.
- The types involved
BankApplication.Infrastructure.Services.DateTimeProvider→BankApplication.Application.Common.Interfaces.Services.IDateTimeProvider
- Direction
- BankApplication.Infrastructure.Services uses BankApplication.Application.Common.Interfaces.Services, so a change to BankApplication.Application.Common.Interfaces.Services can break BankApplication.Infrastructure.Services, while a change to BankApplication.Infrastructure.Services can't break BankApplication.Application.Common.Interfaces.Services.
- Position
- Below the diagonal: BankApplication.Infrastructure.Services uses a module listed above it, which is the healthy direction.
22→23 Domain.Models uses Domain.Domains part of a loop✕
- Connections
- 2 pairs of types, where a type in Domain.Models uses a type in Domain.Domains.
- The types involved
Domain.Models.Account→Domain.Domains.UserDomain.Models.Disposition→Domain.Domains.User
- Direction
- Domain.Models uses Domain.Domains, so a change to Domain.Domains can break Domain.Models, while a change to Domain.Models can't break Domain.Domains.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→22 Domain.Domains uses Domain.Models✕
- Connections
- 1 pair of types, where a type in Domain.Domains uses a type in Domain.Models.
- The types involved
Domain.Domains.User→Domain.Models.Account
- Direction
- Domain.Domains uses Domain.Models, so a change to Domain.Models can break Domain.Domains, while a change to Domain.Domains can't break Domain.Models.
- Position
- Below the diagonal: Domain.Domains uses a module listed above it, which is the healthy direction.
24→23 BankApplication.Application.Authentication.Common uses Domain.Domains✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Authentication.Common uses a type in Domain.Domains.
- The types involved
BankApplication.Application.Authentication.Common.AuthenticationResult→Domain.Domains.User
- Direction
- BankApplication.Application.Authentication.Common uses Domain.Domains, so a change to Domain.Domains can break BankApplication.Application.Authentication.Common, while a change to BankApplication.Application.Authentication.Common can't break Domain.Domains.
- Position
- Below the diagonal: BankApplication.Application.Authentication.Common uses a module listed above it, which is the healthy direction.
25→23 BankApplication.Application.Common.Interfaces uses Domain.Domains✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Common.Interfaces uses a type in Domain.Domains.
- The types involved
BankApplication.Application.Common.Interfaces.IJwtTokenGenerator→Domain.Domains.User
- Direction
- BankApplication.Application.Common.Interfaces uses Domain.Domains, so a change to Domain.Domains can break BankApplication.Application.Common.Interfaces, while a change to BankApplication.Application.Common.Interfaces can't break Domain.Domains.
- Position
- Below the diagonal: BankApplication.Application.Common.Interfaces uses a module listed above it, which is the healthy direction.
26→22 BankApplication.Domain.Aggregates uses Domain.Models✕
- Connections
- 2 pairs of types, where a type in BankApplication.Domain.Aggregates uses a type in Domain.Models.
- The types involved
BankApplication.Domain.Aggregates.NewCustomerAccountAggregate→Domain.Models.AccountBankApplication.Domain.Aggregates.NewCustomerAccountAggregate→Domain.Models.Customer
- Direction
- BankApplication.Domain.Aggregates uses Domain.Models, so a change to Domain.Models can break BankApplication.Domain.Aggregates, while a change to BankApplication.Domain.Aggregates can't break Domain.Models.
- Position
- Below the diagonal: BankApplication.Domain.Aggregates uses a module listed above it, which is the healthy direction.
26→23 BankApplication.Domain.Aggregates uses Domain.Domains✕
- Connections
- 1 pair of types, where a type in BankApplication.Domain.Aggregates uses a type in Domain.Domains.
- The types involved
BankApplication.Domain.Aggregates.NewCustomerAccountAggregate→Domain.Domains.User
- Direction
- BankApplication.Domain.Aggregates uses Domain.Domains, so a change to Domain.Domains can break BankApplication.Domain.Aggregates, while a change to BankApplication.Domain.Aggregates can't break Domain.Domains.
- Position
- Below the diagonal: BankApplication.Domain.Aggregates uses a module listed above it, which is the healthy direction.
27→22 BankApplication.Application.Accounts.Response.Commands uses Domain.Models✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Accounts.Response.Commands uses a type in Domain.Models.
- The types involved
BankApplication.Application.Accounts.Response.Commands.CreateAccountResult→Domain.Models.Account
- Direction
- BankApplication.Application.Accounts.Response.Commands uses Domain.Models, so a change to Domain.Models can break BankApplication.Application.Accounts.Response.Commands, while a change to BankApplication.Application.Accounts.Response.Commands can't break Domain.Models.
- Position
- Below the diagonal: BankApplication.Application.Accounts.Response.Commands uses a module listed above it, which is the healthy direction.
27→26 BankApplication.Application.Accounts.Response.Commands uses BankApplication.Domain.Aggregates✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Accounts.Response.Commands uses a type in BankApplication.Domain.Aggregates.
- The types involved
BankApplication.Application.Accounts.Response.Commands.TransferResult→BankApplication.Domain.Aggregates.TransferAggregate
- Direction
- BankApplication.Application.Accounts.Response.Commands uses BankApplication.Domain.Aggregates, so a change to BankApplication.Domain.Aggregates can break BankApplication.Application.Accounts.Response.Commands, while a change to BankApplication.Application.Accounts.Response.Commands can't break BankApplication.Domain.Aggregates.
- Position
- Below the diagonal: BankApplication.Application.Accounts.Response.Commands uses a module listed above it, which is the healthy direction.
28→26 BankApplication.Application.Adminstrator.Response.Commands uses BankApplication.Domain.Aggregates✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Adminstrator.Response.Commands uses a type in BankApplication.Domain.Aggregates.
- The types involved
BankApplication.Application.Adminstrator.Response.Commands.NewCustomerAccountResult→BankApplication.Domain.Aggregates.NewCustomerAccountAggregate
- Direction
- BankApplication.Application.Adminstrator.Response.Commands uses BankApplication.Domain.Aggregates, so a change to BankApplication.Domain.Aggregates can break BankApplication.Application.Adminstrator.Response.Commands, while a change to BankApplication.Application.Adminstrator.Response.Commands can't break BankApplication.Domain.Aggregates.
- Position
- Below the diagonal: BankApplication.Application.Adminstrator.Response.Commands uses a module listed above it, which is the healthy direction.
29→26 BankApplication.Application.Customers.Response.Commands uses BankApplication.Domain.Aggregates✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Customers.Response.Commands uses a type in BankApplication.Domain.Aggregates.
- The types involved
BankApplication.Application.Customers.Response.Commands.AddAccountCreditResult→BankApplication.Domain.Aggregates.TransferAggregate
- Direction
- BankApplication.Application.Customers.Response.Commands uses BankApplication.Domain.Aggregates, so a change to BankApplication.Domain.Aggregates can break BankApplication.Application.Customers.Response.Commands, while a change to BankApplication.Application.Customers.Response.Commands can't break BankApplication.Domain.Aggregates.
- Position
- Below the diagonal: BankApplication.Application.Customers.Response.Commands uses a module listed above it, which is the healthy direction.
30→22 BankApplication.Application.Customers.Response.Queries uses Domain.Models✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Customers.Response.Queries uses a type in Domain.Models.
- The types involved
BankApplication.Application.Customers.Response.Queries.GetAccountsResult→Domain.Models.Account
- Direction
- BankApplication.Application.Customers.Response.Queries uses Domain.Models, so a change to Domain.Models can break BankApplication.Application.Customers.Response.Queries, while a change to BankApplication.Application.Customers.Response.Queries can't break Domain.Models.
- Position
- Below the diagonal: BankApplication.Application.Customers.Response.Queries uses a module listed above it, which is the healthy direction.
30→26 BankApplication.Application.Customers.Response.Queries uses BankApplication.Domain.Aggregates✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Customers.Response.Queries uses a type in BankApplication.Domain.Aggregates.
- The types involved
BankApplication.Application.Customers.Response.Queries.GetTransactionsByAccIdResult→BankApplication.Domain.Aggregates.AccountAggregate
- Direction
- BankApplication.Application.Customers.Response.Queries uses BankApplication.Domain.Aggregates, so a change to BankApplication.Domain.Aggregates can break BankApplication.Application.Customers.Response.Queries, while a change to BankApplication.Application.Customers.Response.Queries can't break BankApplication.Domain.Aggregates.
- Position
- Below the diagonal: BankApplication.Application.Customers.Response.Queries uses a module listed above it, which is the healthy direction.
31→11 BankApplication.Infrastructure.Authentication uses BankApplication.Application.Common.Interfaces.Services✕
- Connections
- 1 pair of types, where a type in BankApplication.Infrastructure.Authentication uses a type in BankApplication.Application.Common.Interfaces.Services.
- The types involved
BankApplication.Infrastructure.Authentication.JwtTokenGenerator→BankApplication.Application.Common.Interfaces.Services.IDateTimeProvider
- Direction
- BankApplication.Infrastructure.Authentication uses BankApplication.Application.Common.Interfaces.Services, so a change to BankApplication.Application.Common.Interfaces.Services can break BankApplication.Infrastructure.Authentication, while a change to BankApplication.Infrastructure.Authentication can't break BankApplication.Application.Common.Interfaces.Services.
- Position
- Below the diagonal: BankApplication.Infrastructure.Authentication uses a module listed above it, which is the healthy direction.
31→23 BankApplication.Infrastructure.Authentication uses Domain.Domains✕
- Connections
- 1 pair of types, where a type in BankApplication.Infrastructure.Authentication uses a type in Domain.Domains.
- The types involved
BankApplication.Infrastructure.Authentication.JwtTokenGenerator→Domain.Domains.User
- Direction
- BankApplication.Infrastructure.Authentication uses Domain.Domains, so a change to Domain.Domains can break BankApplication.Infrastructure.Authentication, while a change to BankApplication.Infrastructure.Authentication can't break Domain.Domains.
- Position
- Below the diagonal: BankApplication.Infrastructure.Authentication uses a module listed above it, which is the healthy direction.
31→25 BankApplication.Infrastructure.Authentication uses BankApplication.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in BankApplication.Infrastructure.Authentication uses a type in BankApplication.Application.Common.Interfaces.
- The types involved
BankApplication.Infrastructure.Authentication.JwtTokenGenerator→BankApplication.Application.Common.Interfaces.IJwtTokenGenerator
- Direction
- BankApplication.Infrastructure.Authentication uses BankApplication.Application.Common.Interfaces, so a change to BankApplication.Application.Common.Interfaces can break BankApplication.Infrastructure.Authentication, while a change to BankApplication.Infrastructure.Authentication can't break BankApplication.Application.Common.Interfaces.
- Position
- Below the diagonal: BankApplication.Infrastructure.Authentication uses a module listed above it, which is the healthy direction.
32→28 BankApplication.Application.Customers.Commands.AddAccountCredit uses BankApplication.Application.Adminstrator.Response.Commands✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Customers.Commands.AddAccountCredit uses a type in BankApplication.Application.Adminstrator.Response.Commands.
- The types involved
BankApplication.Application.Customers.Commands.AddAccountCredit.NewCustomerAccountCommandHandler→BankApplication.Application.Adminstrator.Response.Commands.NewCustomerAccountResult
- Direction
- BankApplication.Application.Customers.Commands.AddAccountCredit uses BankApplication.Application.Adminstrator.Response.Commands, so a change to BankApplication.Application.Adminstrator.Response.Commands can break BankApplication.Application.Customers.Commands.AddAccountCredit, while a change to BankApplication.Application.Customers.Commands.AddAccountCredit can't break BankApplication.Application.Adminstrator.Response.Commands.
- Position
- Below the diagonal: BankApplication.Application.Customers.Commands.AddAccountCredit uses a module listed above it, which is the healthy direction.
32→29 BankApplication.Application.Customers.Commands.AddAccountCredit uses BankApplication.Application.Customers.Response.Commands✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Customers.Commands.AddAccountCredit uses a type in BankApplication.Application.Customers.Response.Commands.
- The types involved
BankApplication.Application.Customers.Commands.AddAccountCredit.AddAccountCreditCommandHandler→BankApplication.Application.Customers.Response.Commands.AddAccountCreditResult
- Direction
- BankApplication.Application.Customers.Commands.AddAccountCredit uses BankApplication.Application.Customers.Response.Commands, so a change to BankApplication.Application.Customers.Response.Commands can break BankApplication.Application.Customers.Commands.AddAccountCredit, while a change to BankApplication.Application.Customers.Commands.AddAccountCredit can't break BankApplication.Application.Customers.Response.Commands.
- Position
- Below the diagonal: BankApplication.Application.Customers.Commands.AddAccountCredit uses a module listed above it, which is the healthy direction.
32→33 BankApplication.Application.Customers.Commands.AddAccountCredit uses BankApplication.Application.Common.Interfaces.Persistence part of a loop✕
- Connections
- 2 pairs of types, where a type in BankApplication.Application.Customers.Commands.AddAccountCredit uses a type in BankApplication.Application.Common.Interfaces.Persistence.
- The types involved
BankApplication.Application.Customers.Commands.AddAccountCredit.AddAccountCreditCommandHandler→BankApplication.Application.Common.Interfaces.Persistence.IAdminstratorRepositoryBankApplication.Application.Customers.Commands.AddAccountCredit.NewCustomerAccountCommandHandler→BankApplication.Application.Common.Interfaces.Persistence.ICustomerRepository
- Direction
- BankApplication.Application.Customers.Commands.AddAccountCredit uses BankApplication.Application.Common.Interfaces.Persistence, so a change to BankApplication.Application.Common.Interfaces.Persistence can break BankApplication.Application.Customers.Commands.AddAccountCredit, while a change to BankApplication.Application.Customers.Commands.AddAccountCredit can't break BankApplication.Application.Common.Interfaces.Persistence.
- 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.
33→22 BankApplication.Application.Common.Interfaces.Persistence uses Domain.Models✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Common.Interfaces.Persistence uses a type in Domain.Models.
- The types involved
BankApplication.Application.Common.Interfaces.Persistence.IAccountsRepository→Domain.Models.Account
- Direction
- BankApplication.Application.Common.Interfaces.Persistence uses Domain.Models, so a change to Domain.Models can break BankApplication.Application.Common.Interfaces.Persistence, while a change to BankApplication.Application.Common.Interfaces.Persistence can't break Domain.Models.
- Position
- Below the diagonal: BankApplication.Application.Common.Interfaces.Persistence uses a module listed above it, which is the healthy direction.
33→23 BankApplication.Application.Common.Interfaces.Persistence uses Domain.Domains✕
- Connections
- 2 pairs of types, where a type in BankApplication.Application.Common.Interfaces.Persistence uses a type in Domain.Domains.
- The types involved
BankApplication.Application.Common.Interfaces.Persistence.ICustomerRepository→Domain.Domains.UserBankApplication.Application.Common.Interfaces.Persistence.IUserRepository→Domain.Domains.User
- Direction
- BankApplication.Application.Common.Interfaces.Persistence uses Domain.Domains, so a change to Domain.Domains can break BankApplication.Application.Common.Interfaces.Persistence, while a change to BankApplication.Application.Common.Interfaces.Persistence can't break Domain.Domains.
- Position
- Below the diagonal: BankApplication.Application.Common.Interfaces.Persistence uses a module listed above it, which is the healthy direction.
33→26 BankApplication.Application.Common.Interfaces.Persistence uses BankApplication.Domain.Aggregates✕
- Connections
- 4 pairs of types, where a type in BankApplication.Application.Common.Interfaces.Persistence uses a type in BankApplication.Domain.Aggregates.
- The types involved
BankApplication.Application.Common.Interfaces.Persistence.IAdminstratorRepository→BankApplication.Domain.Aggregates.TransferAggregateBankApplication.Application.Common.Interfaces.Persistence.ICustomerRepository→BankApplication.Domain.Aggregates.NewCustomerAccountAggregateBankApplication.Application.Common.Interfaces.Persistence.ITransactionsRepository→BankApplication.Domain.Aggregates.AccountAggregateBankApplication.Application.Common.Interfaces.Persistence.ITransactionsRepository→BankApplication.Domain.Aggregates.TransferAggregate
- Direction
- BankApplication.Application.Common.Interfaces.Persistence uses BankApplication.Domain.Aggregates, so a change to BankApplication.Domain.Aggregates can break BankApplication.Application.Common.Interfaces.Persistence, while a change to BankApplication.Application.Common.Interfaces.Persistence can't break BankApplication.Domain.Aggregates.
- Position
- Below the diagonal: BankApplication.Application.Common.Interfaces.Persistence uses a module listed above it, which is the healthy direction.
33→32 BankApplication.Application.Common.Interfaces.Persistence uses BankApplication.Application.Customers.Commands.AddAccountCredit✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Common.Interfaces.Persistence uses a type in BankApplication.Application.Customers.Commands.AddAccountCredit.
- The types involved
BankApplication.Application.Common.Interfaces.Persistence.ICustomerRepository→BankApplication.Application.Customers.Commands.AddAccountCredit.NewCustomerAccountCommand
- Direction
- BankApplication.Application.Common.Interfaces.Persistence uses BankApplication.Application.Customers.Commands.AddAccountCredit, so a change to BankApplication.Application.Customers.Commands.AddAccountCredit can break BankApplication.Application.Common.Interfaces.Persistence, while a change to BankApplication.Application.Common.Interfaces.Persistence can't break BankApplication.Application.Customers.Commands.AddAccountCredit.
- Position
- Below the diagonal: BankApplication.Application.Common.Interfaces.Persistence uses a module listed above it, which is the healthy direction.
34→30 BankApplication.Application.Accounts.Queries.GetAccounts uses BankApplication.Application.Customers.Response.Queries✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Accounts.Queries.GetAccounts uses a type in BankApplication.Application.Customers.Response.Queries.
- The types involved
BankApplication.Application.Accounts.Queries.GetAccounts.GetAccountsQueryHandler→BankApplication.Application.Customers.Response.Queries.GetAccountsResult
- Direction
- BankApplication.Application.Accounts.Queries.GetAccounts uses BankApplication.Application.Customers.Response.Queries, so a change to BankApplication.Application.Customers.Response.Queries can break BankApplication.Application.Accounts.Queries.GetAccounts, while a change to BankApplication.Application.Accounts.Queries.GetAccounts can't break BankApplication.Application.Customers.Response.Queries.
- Position
- Below the diagonal: BankApplication.Application.Accounts.Queries.GetAccounts uses a module listed above it, which is the healthy direction.
34→33 BankApplication.Application.Accounts.Queries.GetAccounts uses BankApplication.Application.Common.Interfaces.Persistence✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Accounts.Queries.GetAccounts uses a type in BankApplication.Application.Common.Interfaces.Persistence.
- The types involved
BankApplication.Application.Accounts.Queries.GetAccounts.GetAccountsQueryHandler→BankApplication.Application.Common.Interfaces.Persistence.IAccountsRepository
- Direction
- BankApplication.Application.Accounts.Queries.GetAccounts uses BankApplication.Application.Common.Interfaces.Persistence, so a change to BankApplication.Application.Common.Interfaces.Persistence can break BankApplication.Application.Accounts.Queries.GetAccounts, while a change to BankApplication.Application.Accounts.Queries.GetAccounts can't break BankApplication.Application.Common.Interfaces.Persistence.
- Position
- Below the diagonal: BankApplication.Application.Accounts.Queries.GetAccounts uses a module listed above it, which is the healthy direction.
35→8 BankApplication.Application.Accounts.Queries.GetTransactionsByAccId uses BankApplication.Application.Accounts.Queries.GetAccountById✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Accounts.Queries.GetTransactionsByAccId uses a type in BankApplication.Application.Accounts.Queries.GetAccountById.
- The types involved
BankApplication.Application.Accounts.Queries.GetTransactionsByAccId.GetAccountByIdHandler→BankApplication.Application.Accounts.Queries.GetAccountById.GetTransactionsByAccIdQuery
- Direction
- BankApplication.Application.Accounts.Queries.GetTransactionsByAccId uses BankApplication.Application.Accounts.Queries.GetAccountById, so a change to BankApplication.Application.Accounts.Queries.GetAccountById can break BankApplication.Application.Accounts.Queries.GetTransactionsByAccId, while a change to BankApplication.Application.Accounts.Queries.GetTransactionsByAccId can't break BankApplication.Application.Accounts.Queries.GetAccountById.
- Position
- Below the diagonal: BankApplication.Application.Accounts.Queries.GetTransactionsByAccId uses a module listed above it, which is the healthy direction.
35→30 BankApplication.Application.Accounts.Queries.GetTransactionsByAccId uses BankApplication.Application.Customers.Response.Queries✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Accounts.Queries.GetTransactionsByAccId uses a type in BankApplication.Application.Customers.Response.Queries.
- The types involved
BankApplication.Application.Accounts.Queries.GetTransactionsByAccId.GetAccountByIdHandler→BankApplication.Application.Customers.Response.Queries.GetTransactionsByAccIdResult
- Direction
- BankApplication.Application.Accounts.Queries.GetTransactionsByAccId uses BankApplication.Application.Customers.Response.Queries, so a change to BankApplication.Application.Customers.Response.Queries can break BankApplication.Application.Accounts.Queries.GetTransactionsByAccId, while a change to BankApplication.Application.Accounts.Queries.GetTransactionsByAccId can't break BankApplication.Application.Customers.Response.Queries.
- Position
- Below the diagonal: BankApplication.Application.Accounts.Queries.GetTransactionsByAccId uses a module listed above it, which is the healthy direction.
35→33 BankApplication.Application.Accounts.Queries.GetTransactionsByAccId uses BankApplication.Application.Common.Interfaces.Persistence✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Accounts.Queries.GetTransactionsByAccId uses a type in BankApplication.Application.Common.Interfaces.Persistence.
- The types involved
BankApplication.Application.Accounts.Queries.GetTransactionsByAccId.GetAccountByIdHandler→BankApplication.Application.Common.Interfaces.Persistence.ITransactionsRepository
- Direction
- BankApplication.Application.Accounts.Queries.GetTransactionsByAccId uses BankApplication.Application.Common.Interfaces.Persistence, so a change to BankApplication.Application.Common.Interfaces.Persistence can break BankApplication.Application.Accounts.Queries.GetTransactionsByAccId, while a change to BankApplication.Application.Accounts.Queries.GetTransactionsByAccId can't break BankApplication.Application.Common.Interfaces.Persistence.
- Position
- Below the diagonal: BankApplication.Application.Accounts.Queries.GetTransactionsByAccId uses a module listed above it, which is the healthy direction.
36→13 BankApplication.Application.Authentication.Queries.Login uses BankApplication.Application.Services.Queries.Login✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Authentication.Queries.Login uses a type in BankApplication.Application.Services.Queries.Login.
- The types involved
BankApplication.Application.Authentication.Queries.Login.LoginQueryHandler→BankApplication.Application.Services.Queries.Login.LoginQuery
- Direction
- BankApplication.Application.Authentication.Queries.Login uses BankApplication.Application.Services.Queries.Login, so a change to BankApplication.Application.Services.Queries.Login can break BankApplication.Application.Authentication.Queries.Login, while a change to BankApplication.Application.Authentication.Queries.Login can't break BankApplication.Application.Services.Queries.Login.
- Position
- Below the diagonal: BankApplication.Application.Authentication.Queries.Login uses a module listed above it, which is the healthy direction.
36→24 BankApplication.Application.Authentication.Queries.Login uses BankApplication.Application.Authentication.Common✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Authentication.Queries.Login uses a type in BankApplication.Application.Authentication.Common.
- The types involved
BankApplication.Application.Authentication.Queries.Login.LoginQueryHandler→BankApplication.Application.Authentication.Common.AuthenticationResult
- Direction
- BankApplication.Application.Authentication.Queries.Login uses BankApplication.Application.Authentication.Common, so a change to BankApplication.Application.Authentication.Common can break BankApplication.Application.Authentication.Queries.Login, while a change to BankApplication.Application.Authentication.Queries.Login can't break BankApplication.Application.Authentication.Common.
- Position
- Below the diagonal: BankApplication.Application.Authentication.Queries.Login uses a module listed above it, which is the healthy direction.
36→25 BankApplication.Application.Authentication.Queries.Login uses BankApplication.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Authentication.Queries.Login uses a type in BankApplication.Application.Common.Interfaces.
- The types involved
BankApplication.Application.Authentication.Queries.Login.LoginQueryHandler→BankApplication.Application.Common.Interfaces.IJwtTokenGenerator
- Direction
- BankApplication.Application.Authentication.Queries.Login uses BankApplication.Application.Common.Interfaces, so a change to BankApplication.Application.Common.Interfaces can break BankApplication.Application.Authentication.Queries.Login, while a change to BankApplication.Application.Authentication.Queries.Login can't break BankApplication.Application.Common.Interfaces.
- Position
- Below the diagonal: BankApplication.Application.Authentication.Queries.Login uses a module listed above it, which is the healthy direction.
36→33 BankApplication.Application.Authentication.Queries.Login uses BankApplication.Application.Common.Interfaces.Persistence✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Authentication.Queries.Login uses a type in BankApplication.Application.Common.Interfaces.Persistence.
- The types involved
BankApplication.Application.Authentication.Queries.Login.LoginQueryHandler→BankApplication.Application.Common.Interfaces.Persistence.IUserRepository
- Direction
- BankApplication.Application.Authentication.Queries.Login uses BankApplication.Application.Common.Interfaces.Persistence, so a change to BankApplication.Application.Common.Interfaces.Persistence can break BankApplication.Application.Authentication.Queries.Login, while a change to BankApplication.Application.Authentication.Queries.Login can't break BankApplication.Application.Common.Interfaces.Persistence.
- Position
- Below the diagonal: BankApplication.Application.Authentication.Queries.Login uses a module listed above it, which is the healthy direction.
37→24 BankApplication.Application.Services.Commands.Register uses BankApplication.Application.Authentication.Common✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Services.Commands.Register uses a type in BankApplication.Application.Authentication.Common.
- The types involved
BankApplication.Application.Services.Commands.Register.RegisterCommandHandler→BankApplication.Application.Authentication.Common.AuthenticationResult
- Direction
- BankApplication.Application.Services.Commands.Register uses BankApplication.Application.Authentication.Common, so a change to BankApplication.Application.Authentication.Common can break BankApplication.Application.Services.Commands.Register, while a change to BankApplication.Application.Services.Commands.Register can't break BankApplication.Application.Authentication.Common.
- Position
- Below the diagonal: BankApplication.Application.Services.Commands.Register uses a module listed above it, which is the healthy direction.
37→25 BankApplication.Application.Services.Commands.Register uses BankApplication.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Services.Commands.Register uses a type in BankApplication.Application.Common.Interfaces.
- The types involved
BankApplication.Application.Services.Commands.Register.RegisterCommandHandler→BankApplication.Application.Common.Interfaces.IJwtTokenGenerator
- Direction
- BankApplication.Application.Services.Commands.Register uses BankApplication.Application.Common.Interfaces, so a change to BankApplication.Application.Common.Interfaces can break BankApplication.Application.Services.Commands.Register, while a change to BankApplication.Application.Services.Commands.Register can't break BankApplication.Application.Common.Interfaces.
- Position
- Below the diagonal: BankApplication.Application.Services.Commands.Register uses a module listed above it, which is the healthy direction.
37→33 BankApplication.Application.Services.Commands.Register uses BankApplication.Application.Common.Interfaces.Persistence✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Services.Commands.Register uses a type in BankApplication.Application.Common.Interfaces.Persistence.
- The types involved
BankApplication.Application.Services.Commands.Register.RegisterCommandHandler→BankApplication.Application.Common.Interfaces.Persistence.IUserRepository
- Direction
- BankApplication.Application.Services.Commands.Register uses BankApplication.Application.Common.Interfaces.Persistence, so a change to BankApplication.Application.Common.Interfaces.Persistence can break BankApplication.Application.Services.Commands.Register, while a change to BankApplication.Application.Services.Commands.Register can't break BankApplication.Application.Common.Interfaces.Persistence.
- Position
- Below the diagonal: BankApplication.Application.Services.Commands.Register uses a module listed above it, which is the healthy direction.
38→27 BankApplication.Application.Transactions.Commands.Transfer uses BankApplication.Application.Accounts.Response.Commands✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Transactions.Commands.Transfer uses a type in BankApplication.Application.Accounts.Response.Commands.
- The types involved
BankApplication.Application.Transactions.Commands.Transfer.TransferCommandHandler→BankApplication.Application.Accounts.Response.Commands.TransferResult
- Direction
- BankApplication.Application.Transactions.Commands.Transfer uses BankApplication.Application.Accounts.Response.Commands, so a change to BankApplication.Application.Accounts.Response.Commands can break BankApplication.Application.Transactions.Commands.Transfer, while a change to BankApplication.Application.Transactions.Commands.Transfer can't break BankApplication.Application.Accounts.Response.Commands.
- Position
- Below the diagonal: BankApplication.Application.Transactions.Commands.Transfer uses a module listed above it, which is the healthy direction.
38→33 BankApplication.Application.Transactions.Commands.Transfer uses BankApplication.Application.Common.Interfaces.Persistence✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Transactions.Commands.Transfer uses a type in BankApplication.Application.Common.Interfaces.Persistence.
- The types involved
BankApplication.Application.Transactions.Commands.Transfer.TransferCommandHandler→BankApplication.Application.Common.Interfaces.Persistence.ITransactionsRepository
- Direction
- BankApplication.Application.Transactions.Commands.Transfer uses BankApplication.Application.Common.Interfaces.Persistence, so a change to BankApplication.Application.Common.Interfaces.Persistence can break BankApplication.Application.Transactions.Commands.Transfer, while a change to BankApplication.Application.Transactions.Commands.Transfer can't break BankApplication.Application.Common.Interfaces.Persistence.
- Position
- Below the diagonal: BankApplication.Application.Transactions.Commands.Transfer uses a module listed above it, which is the healthy direction.
39→20 BankApplication.Infrastructure.Presistence uses BankApplication.Infrastructure✕
- Connections
- 6 pairs of types, where a type in BankApplication.Infrastructure.Presistence uses a type in BankApplication.Infrastructure.
- The types involved
BankApplication.Infrastructure.Presistence.AccountsRepository→BankApplication.Infrastructure.DapperContextBankApplication.Infrastructure.Presistence.AdminstratorRepository→BankApplication.Infrastructure.DapperContextBankApplication.Infrastructure.Presistence.CustomersRepository→BankApplication.Infrastructure.DapperContextBankApplication.Infrastructure.Presistence.DispositionRepository→BankApplication.Infrastructure.DapperContextBankApplication.Infrastructure.Presistence.TransactionsRepository→BankApplication.Infrastructure.DapperContextBankApplication.Infrastructure.Presistence.UserRepository→BankApplication.Infrastructure.DapperContext
- Direction
- BankApplication.Infrastructure.Presistence uses BankApplication.Infrastructure, so a change to BankApplication.Infrastructure can break BankApplication.Infrastructure.Presistence, while a change to BankApplication.Infrastructure.Presistence can't break BankApplication.Infrastructure.
- Position
- Below the diagonal: BankApplication.Infrastructure.Presistence uses a module listed above it, which is the healthy direction.
39→22 BankApplication.Infrastructure.Presistence uses Domain.Models✕
- Connections
- 1 pair of types, where a type in BankApplication.Infrastructure.Presistence uses a type in Domain.Models.
- The types involved
BankApplication.Infrastructure.Presistence.AccountsRepository→Domain.Models.Account
- Direction
- BankApplication.Infrastructure.Presistence uses Domain.Models, so a change to Domain.Models can break BankApplication.Infrastructure.Presistence, while a change to BankApplication.Infrastructure.Presistence can't break Domain.Models.
- Position
- Below the diagonal: BankApplication.Infrastructure.Presistence uses a module listed above it, which is the healthy direction.
39→23 BankApplication.Infrastructure.Presistence uses Domain.Domains✕
- Connections
- 2 pairs of types, where a type in BankApplication.Infrastructure.Presistence uses a type in Domain.Domains.
- The types involved
BankApplication.Infrastructure.Presistence.CustomersRepository→Domain.Domains.UserBankApplication.Infrastructure.Presistence.UserRepository→Domain.Domains.User
- Direction
- BankApplication.Infrastructure.Presistence uses Domain.Domains, so a change to Domain.Domains can break BankApplication.Infrastructure.Presistence, while a change to BankApplication.Infrastructure.Presistence can't break Domain.Domains.
- Position
- Below the diagonal: BankApplication.Infrastructure.Presistence uses a module listed above it, which is the healthy direction.
39→26 BankApplication.Infrastructure.Presistence uses BankApplication.Domain.Aggregates✕
- Connections
- 4 pairs of types, where a type in BankApplication.Infrastructure.Presistence uses a type in BankApplication.Domain.Aggregates.
- The types involved
BankApplication.Infrastructure.Presistence.AdminstratorRepository→BankApplication.Domain.Aggregates.TransferAggregateBankApplication.Infrastructure.Presistence.CustomersRepository→BankApplication.Domain.Aggregates.NewCustomerAccountAggregateBankApplication.Infrastructure.Presistence.TransactionsRepository→BankApplication.Domain.Aggregates.AccountAggregateBankApplication.Infrastructure.Presistence.TransactionsRepository→BankApplication.Domain.Aggregates.TransferAggregate
- Direction
- BankApplication.Infrastructure.Presistence uses BankApplication.Domain.Aggregates, so a change to BankApplication.Domain.Aggregates can break BankApplication.Infrastructure.Presistence, while a change to BankApplication.Infrastructure.Presistence can't break BankApplication.Domain.Aggregates.
- Position
- Below the diagonal: BankApplication.Infrastructure.Presistence uses a module listed above it, which is the healthy direction.
39→32 BankApplication.Infrastructure.Presistence uses BankApplication.Application.Customers.Commands.AddAccountCredit✕
- Connections
- 1 pair of types, where a type in BankApplication.Infrastructure.Presistence uses a type in BankApplication.Application.Customers.Commands.AddAccountCredit.
- The types involved
BankApplication.Infrastructure.Presistence.CustomersRepository→BankApplication.Application.Customers.Commands.AddAccountCredit.NewCustomerAccountCommand
- Direction
- BankApplication.Infrastructure.Presistence uses BankApplication.Application.Customers.Commands.AddAccountCredit, so a change to BankApplication.Application.Customers.Commands.AddAccountCredit can break BankApplication.Infrastructure.Presistence, while a change to BankApplication.Infrastructure.Presistence can't break BankApplication.Application.Customers.Commands.AddAccountCredit.
- Position
- Below the diagonal: BankApplication.Infrastructure.Presistence uses a module listed above it, which is the healthy direction.
39→33 BankApplication.Infrastructure.Presistence uses BankApplication.Application.Common.Interfaces.Persistence✕
- Connections
- 5 pairs of types, where a type in BankApplication.Infrastructure.Presistence uses a type in BankApplication.Application.Common.Interfaces.Persistence.
- The types involved
BankApplication.Infrastructure.Presistence.AccountsRepository→BankApplication.Application.Common.Interfaces.Persistence.IAccountsRepositoryBankApplication.Infrastructure.Presistence.AdminstratorRepository→BankApplication.Application.Common.Interfaces.Persistence.IAdminstratorRepositoryBankApplication.Infrastructure.Presistence.CustomersRepository→BankApplication.Application.Common.Interfaces.Persistence.ICustomerRepositoryBankApplication.Infrastructure.Presistence.TransactionsRepository→BankApplication.Application.Common.Interfaces.Persistence.ITransactionsRepositoryBankApplication.Infrastructure.Presistence.UserRepository→BankApplication.Application.Common.Interfaces.Persistence.IUserRepository
- Direction
- BankApplication.Infrastructure.Presistence uses BankApplication.Application.Common.Interfaces.Persistence, so a change to BankApplication.Application.Common.Interfaces.Persistence can break BankApplication.Infrastructure.Presistence, while a change to BankApplication.Infrastructure.Presistence can't break BankApplication.Application.Common.Interfaces.Persistence.
- Position
- Below the diagonal: BankApplication.Infrastructure.Presistence uses a module listed above it, which is the healthy direction.
40→27 BankApplication.Application.Accounts.Commands uses BankApplication.Application.Accounts.Response.Commands✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Accounts.Commands uses a type in BankApplication.Application.Accounts.Response.Commands.
- The types involved
BankApplication.Application.Accounts.Commands.CreateAccountCommandHandler→BankApplication.Application.Accounts.Response.Commands.CreateAccountResult
- Direction
- BankApplication.Application.Accounts.Commands uses BankApplication.Application.Accounts.Response.Commands, so a change to BankApplication.Application.Accounts.Response.Commands can break BankApplication.Application.Accounts.Commands, while a change to BankApplication.Application.Accounts.Commands can't break BankApplication.Application.Accounts.Response.Commands.
- Position
- Below the diagonal: BankApplication.Application.Accounts.Commands uses a module listed above it, which is the healthy direction.
40→33 BankApplication.Application.Accounts.Commands uses BankApplication.Application.Common.Interfaces.Persistence✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Accounts.Commands uses a type in BankApplication.Application.Common.Interfaces.Persistence.
- The types involved
BankApplication.Application.Accounts.Commands.CreateAccountCommandHandler→BankApplication.Application.Common.Interfaces.Persistence.IAccountsRepository
- Direction
- BankApplication.Application.Accounts.Commands uses BankApplication.Application.Common.Interfaces.Persistence, so a change to BankApplication.Application.Common.Interfaces.Persistence can break BankApplication.Application.Accounts.Commands, while a change to BankApplication.Application.Accounts.Commands can't break BankApplication.Application.Common.Interfaces.Persistence.
- Position
- Below the diagonal: BankApplication.Application.Accounts.Commands uses a module listed above it, which is the healthy direction.
40→39 BankApplication.Application.Accounts.Commands uses BankApplication.Infrastructure.Presistence✕
- Connections
- 1 pair of types, where a type in BankApplication.Application.Accounts.Commands uses a type in BankApplication.Infrastructure.Presistence.
- The types involved
BankApplication.Application.Accounts.Commands.CreateAccountCommandHandler→BankApplication.Infrastructure.Presistence.IDispositionRepository
- Direction
- BankApplication.Application.Accounts.Commands uses BankApplication.Infrastructure.Presistence, so a change to BankApplication.Infrastructure.Presistence can break BankApplication.Application.Accounts.Commands, while a change to BankApplication.Application.Accounts.Commands can't break BankApplication.Infrastructure.Presistence.
- Position
- Below the diagonal: BankApplication.Application.Accounts.Commands 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 — Event-Driven
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 12 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
| A05:2025 — Injection | 4 | Medium |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No tests found finding(s) in Test Distribution; Resolve the 13 Outdated finding(s) in Dependency Hygiene — start with REDACTED (6), REDACTED (4), BankApplication.Application.csproj (3).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No tests found finding(s) in Test Distribution. | +19.2 pts | Low | Test Distribution |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +19.2 pts | High | Code Coverage |
| Resolve the 13 Outdated finding(s) in Dependency Hygiene — start with REDACTED (6), REDACTED (4), BankApplication.Application.csproj (3). | +8.3 pts | Medium | Dependency Hygiene |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.0 pts | Low | ADR Quality |
| Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with BankApplication.Application.csproj, REDACTED, REDACTED. | +1.9 pts | Low | Dependency Hygiene |
| Resolve the 8 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7), REDACTED. | +1.9 pts | Low | Dependency Vulnerabilities |
| Resolve the 5 End-of-life runtime finding(s) in Platform End-of-Life — start with BankApplication.Application.csproj, BankApplication.Domain.csproj, REDACTED. | +1.7 pts | Low | Platform End-of-Life |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +3.3 pts | Medium | CI/CD gates |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.1 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| BankApplication.Application/BankApplication.Application.csproj | 5.5 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| BankApplication.Domain/BankApplication.Domain.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| BankApplication.Presentation/BankApplication.Contracts/BankApplication.Contracts.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| BankApplication.Domain/Aggregates/AccountAggregate.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (15 lines × 3) |
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 79 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 79 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, 65 of 102 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- 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 36 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.
- D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `REDACTED`, `REDACTED` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (36 commit(s) sampled).
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- 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.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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
1 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (15 lines × 3) finding(s) in Code Duplication — start with AccountAggregate.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
5 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 6 classes have LCOM4 above 3.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
- Stand up a CI pipeline, then gate Code Coverage 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.
D9 · Test Distribution
No test suite found.
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D12 · Dependency Hygiene
18 outdated, 3 vulnerable, 3 deprecated packages.
What to do
- Resolve the 13 Outdated finding(s) in Dependency Hygiene — start with REDACTED (6), REDACTED (4), BankApplication.Application.csproj (3). — One of this dimension's main actionable groups (13 recommendation-level).
- Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with BankApplication.Application.csproj, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Stand up a CI pipeline, then gate Dependency Hygiene 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.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 250 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 18 direct `PackageReference`(s), and 232 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
0 deducted debt markers + 0 dead symbols across 1719 LoC in the .NET projects (0.0/KLoC) → score 10.0.
D18 · Solution Shape
5 projects, 101 source files, 1719 hand-written lines of code (1719 production / 0 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), 5 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 1 document(s) read across 6 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 5 projects flagged as possibly oversized/incoherent.
D27 · Navigability
97 % of calls cross a namespace and 18 % go through an interface, but 95 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What to do
- Improve Navigability — currently 8.9/10. — 97 % of calls cross a namespace and 18 % go through an interface, but 95 % 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)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
4 finding(s): 0 critical, 0 high, 4 medium, 0 low.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D30 · Dependency Vulnerabilities
12 finding(s): 1 critical, 8 high, 3 medium, 0 low.
What to do
- Resolve the 8 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
D31 · IaC & Container Security
5 finding(s): 0 critical, 2 high, 2 medium, 1 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D39 · IL Efficiency
0 of 110 first-party methods have an oversized IL body.
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 5 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 5 End-of-life runtime finding(s) in Platform End-of-Life — start with BankApplication.Application.csproj, BankApplication.Domain.csproj, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
What to do
- The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
AX2 · Stateful singletons
AX3 · Project dependency cycles
- The namespaces Domain.Domains ↔ Domain.Models depend on each other. The lightest dependency in the cycle is Domain.Domains → Domain.Models (Domain.Domains.User → Domain.Models.Account, 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. — BankApplication.Domain/Entities/User.cs:2
- The namespaces BankApplication.Application.Common.Interfaces.Persistence ↔ BankApplication.Application.Customers.Commands.AddAccountCredit depend on each other. The lightest dependency in the cycle is BankApplication.Application.Common.Interfaces.Persistence → BankApplication.Application.Customers.Commands.AddAccountCredit (BankApplication.Application.Common.Interfaces.Persistence.ICustomerRepository → BankApplication.Application.Customers.Commands.AddAccountCredit.NewCustomerAccountCommand, 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. — BankApplication.Application/Common/Interfaces/Persistence/ICustomerRepository.cs:1
- The namespaces BankApplication.Infrastructure ↔ BankApplication.Infrastructure.Presistence depend on each other. The lightest dependency in the cycle is BankApplication.Infrastructure → BankApplication.Infrastructure.Presistence (BankApplication.Infrastructure.DapperContext → BankApplication.Infrastructure.Presistence.DapperSettings, 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. — BankApplication.Infrastructure/DbContext/DapperContext.cs:3
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
AX9 · CQS / query purity
C1 · Data Protection
- No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
- Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
C2 · Access Controls
- Access here is not default-deny: `ErrorsController.Error` is in a controller that declares no authorization (on itself, a base controller or any action) while 2 sibling controllers do, and no fallback policy, global AuthorizeFilter or gated MapControllers covers it. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — BankApplication.Presentation/BankApplication.WebApi/Controllers/ErrorsController.cs:12
- Authorization IS enforced here (via [Authorize]/guards) — this is NOT a claim that endpoints are unprotected. What's missing is NAMED policies (AddAuthorization/AddPolicy, RequireRole/RequireClaim, RequireAuthorization): the access rules are implicit rather than named and testable. Recommendation, not a defect — name the rules so they're reviewable.
What to do
- Put every endpoint behind the guard its siblings carry — [Authorize(Policy = …)] on the action or its controller, RequireAuthorization on the route or its group, or a fallback policy with explicit [AllowAnonymous] opt-outs — so the open surface is only what is public on purpose.
- Add policy-based authorization — name the access rules (AddAuthorization(o => o.AddPolicy(…))) and apply them via [Authorize(Policy = …)] or RequireAuthorization.
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM6 · Domain ↔ infrastructure boundary
- `Loan` (domain layer) names `KeyAttribute` from `System.ComponentModel.DataAnnotations` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — BankApplication.Domain/Entities/Loan.cs:9
What to do
- Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
ED2 · Event/command shape
ED4 · Outbox / dual-write
ED5 · Idempotency
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
- This repository declares its own end of life: `README.md` line 16 reads “This project has been retired and is no longer maintained.”. That is a first-party statement of intent, not an inference — the Maturity and Knowledge lenses otherwise approximate the same fact from decayed commit history (D16 reports a dormant codebase, D34 orphaned files), and this row says the maintainer already told you. It does NOT change any score: an honest end-of-life notice is the README doing its job, and every dimension below still measures the code as it stands. Read the whole report as an assessment of software the author has stopped working on. — README.md:16
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 5 of 5 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
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
- Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
M4 · Documentation accuracy
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability
- No logging call was found in the 116 `.cs` file(s) this check read. Each was searched for the framework names `ILogger`, `Serilog`, `NLog` and `log4net`; for a call on a receiver whose name ends in `Logger`; for a `System.Diagnostics` write; for a level-gated log facade; and for the builder spellings that CONFIGURE logging for everyone else (`AddLogging(`, `ConfigureLogging(`, `UseSerilog(`, `UseNLog(`, `.Logging.Add…(`); and for emission through an `EventSource`, `ActivitySource` or `DiagnosticSource` (`WriteEvent(`, `StartActivity(`, `.Write("event", …)`). That walk sees only `.cs` documents from projects the workspace loaded, so it cannot see logging in source that did not load, in another language, or through a repo-local wrapper whose name does not end in `Logger` — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt ILogger (or Serilog) and log at meaningful points across the projects.
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
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.
- `BankApplication.Application/BankApplication.Application.csproj` 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`. — BankApplication.Application/BankApplication.Application.csproj:66
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.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `user.Password != query.Password` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account. Store a salted KDF hash (PBKDF2/scrypt/Argon2/bcrypt) and verify by deriving again. — BankApplication.Application/Authentication/Queries/Login/LoginQueryHandler.cs:31
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. — BankApplication.Presentation/BankApplication.WebApi/Program.cs:7
What to do
- Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `BankApplication.Application/Authentication/Queries/Login/LoginQueryHandler.cs:31`.
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 8/16 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. (×8) — BankApplication.Presentation/BankApplication.WebApi/Controllers/AdminstratorController.cs:29, BankApplication.Presentation/BankApplication.WebApi/Controllers/AdminstratorController.cs:42, REDACTED:28, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
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
X5 · Nullable reference types
- ~4.3 `!` suppressions per 1k syntax nodes — 37 suppression(s) across the 8528 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 | 84% | Strong | Solid. |
| Architecture | 86% | Strong | Solid. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 11% | Critical — gated by D8, D9, P1, P2, P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 46% | Weak — gated by C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 56% | Adequate | Acceptable, with room to improve. |
| Event-Driven | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 5 check(s) recorded observations but carry no score
- AXH1 Runtime security headers — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXI1 Runtime container hardening — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility (rendered) — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 42 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
- AX8 Test isolation — no test/production split to check
- AXA1 Runtime unauthenticated reachability — This run crawled public routes only — it had no logged-in session, so there is no authenticated surface to compare anonymous access against and nothing was measured. This is a statement about this run, not about your application: nothing here says access control is missing, and nothing here says it is present.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXO1 Runtime API surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (526 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — N/A — too few peer members to establish a convention across 24 exposed C# types.
- D23 Boundary Type-Coupling — small single-context codebase (1,719 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 (9 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
- ED1 Handler temporal coupling — no event handlers detected — temporal-coupling check not applicable
- ED3 Event naming — no domain or integration events detected — event-naming check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
- 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — 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 — 18 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Namespace dependency cycle BankApplication.Domain/Entities/User.cs:2
- Namespace dependency cycle BankApplication.Application/Common/Interfaces/Persistence/ICustomerRepository.cs:1
- Namespace dependency cycle BankApplication.Infrastructure/DbContext/DapperContext.cs:3
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No automated tests
- Domain depends on infrastructure: Loan BankApplication.Domain/Entities/Loan.cs:9
- Password hashing without a KDF BankApplication.Application/Authentication/Queries/Login/LoginQueryHandler.cs:31
Serious — 46 finding(s)
- Runtime security header not set: content-security-policy
- Runtime security header not set: cross-origin-embedder-policy
- Runtime security header not set: cross-origin-opener-policy
- Runtime security header not set: cross-origin-resource-policy
- Runtime security header not set: permissions-policy
- Runtime security header not set: referrer-policy
- Runtime security header not set: strict-transport-security
- Runtime security header not set: x-content-type-options
- Runtime security header not set: x-dns-prefetch-control
- Runtime security header not set: x-frame-options
- Runtime security header not set: x-permitted-cross-domain-policies
- Async method without CancellationToken: AddAccountCredit BankApplication.Presentation/BankApplication.WebApi/Controllers/AdminstratorController.cs:29
- Async method without CancellationToken: NewCustomerAccount BankApplication.Presentation/BankApplication.WebApi/Controllers/AdminstratorController.cs:42
- Async method without CancellationToken: Register REDACTED:28
- Async method without CancellationToken: Login REDACTED:42
- Async method without CancellationToken: CreateAccount BankApplication.Presentation/BankApplication.WebApi/Controllers/CustomersController.cs:37
- Async method without CancellationToken: Transfer BankApplication.Presentation/BankApplication.WebApi/Controllers/CustomersController.cs:54
- Async method without CancellationToken: GetAccounts BankApplication.Presentation/BankApplication.WebApi/Controllers/CustomersController.cs:71
- Async method without CancellationToken: GetTransactionsByAccId BankApplication.Presentation/BankApplication.WebApi/Controllers/CustomersController.cs:87
- End-of-life runtime: .NET net7.0 BankApplication.Application/BankApplication.Application.csproj:4
- End-of-life runtime: .NET net7.0 BankApplication.Domain/BankApplication.Domain.csproj:4
- End-of-life runtime: .NET net7.0 REDACTED:4
- End-of-life runtime: .NET net7.0 BankApplication.Presentation/BankApplication.Contracts/BankApplication.Contracts.csproj:4
- End-of-life runtime: .NET net7.0 REDACTED:4
- Deprecated: Microsoft.Extensions.Configuration.UserSecrets BankApplication.Application/BankApplication.Application.csproj:69
- Deprecated: System.IdentityModel.Tokens.Jwt REDACTED:31
- Deprecated: Azure.Identity REDACTED:14
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Container process runs as root: .-bank-backend-1
- WCAG 2.4.2 reproducibly failed in a rendered surface
- WCAG 3.1.1 reproducibly failed in a rendered surface
- No data-protection/encryption
- Duplicated block (15 lines × 3) BankApplication.Domain/Aggregates/AccountAggregate.cs:10
- Repository declared end-of-life README.md:16
- No CI pipeline
- No structured logging
- No DR/backup evidence
- NuGet dependencies are not locked
Minor — 32 finding(s)
- Outdated: MediatR BankApplication.Application/BankApplication.Application.csproj:67
- Outdated: Microsoft.Extensions.Configuration.UserSecrets BankApplication.Application/BankApplication.Application.csproj:69
- Outdated: Microsoft.Extensions.DependencyInjection.Abstractions BankApplication.Application/BankApplication.Application.csproj:66
- Outdated: Microsoft.AspNetCore.Authentication.JwtBearer REDACTED:34
- Outdated: Microsoft.Extensions.Configuration REDACTED:32
- Outdated: Microsoft.Extensions.Configuration.Abstractions REDACTED:30
- Outdated: Microsoft.Extensions.Options.ConfigurationExtensions REDACTED:33
- Outdated: Mapster REDACTED:15
- Outdated: Mapster.DependencyInjection REDACTED:19
- Outdated: Microsoft.AspNetCore.OpenApi REDACTED:16
- Outdated: Microsoft.VisualStudio.Web.CodeGeneration.Design REDACTED:18
- Outdated: Swashbuckle.AspNetCore REDACTED:17
- Outdated: Swashbuckle.AspNetCore.Filters REDACTED:20
- Silent fallback default in catch BankApplication.Infrastructure/Presistence/AccountsRepository.cs:34
- Silent fallback default in catch BankApplication.Infrastructure/Presistence/DispositionRepository.cs:28
- Silent fallback default in catch BankApplication.Infrastructure/Presistence/UserRepository.cs:39
- No security response headers detected
- No security response headers detected BankApplication.Presentation/BankApplication.WebApi/Program.cs:7
- Endpoints outside the guard BankApplication.Presentation/BankApplication.WebApi/Controllers/ErrorsController.cs:12
- No named authorization policies
- Partial data-retention evidence
- No ADRs found
- REDACTED
- REDACTED
- No tests found
- No ADRs
- No src/ separation
- No SAST
- No dependency-update automation BankApplication.Application/BankApplication.Application.csproj:66
- No rollback/health safety
- Not all async methods take a CancellationToken
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 6 finding(s)
- Outdated: MediatR.Extensions.Microsoft.DependencyInjection
- Outdated: Dapper
- Outdated: System.Data.SqlClient
- Outdated: System.IdentityModel.Tokens.Jwt
- Outdated: Azure.Identity
- Off the main sequence: BankApplication.Contracts BankApplication.Presentation/BankApplication.Contracts/BankApplication.Contracts.csproj:1
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-245e1294505f4ae89f0c6b123d3937ce/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-245e1294505f4ae89f0c6b123d3937ce/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 . | 4 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Bank.CleanArchitecture.WebApi.sln package --vulnerable --include-transitive --format json | 12 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| 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-d008740e1f4e455d9729c2a7dfe11ec6 | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Address — 8 field(s)
- NewCustomerAccountCommand.Streetaddress BankApplication.Application/Adminstrator/Commands/NewCustomerAccount/NewCustomerAccountCommand.cs:12
- NewCustomerAccountCommand.Zipcode BankApplication.Application/Adminstrator/Commands/NewCustomerAccount/NewCustomerAccountCommand.cs:14
- Customer.Streetaddress BankApplication.Domain/Entities/Customer.cs:16
- Customer.Zipcode BankApplication.Domain/Entities/Customer.cs:20
- NewCustomerAccountRequest.Streetaddress BankApplication.Presentation/BankApplication.Contracts/Adminstrator/NewCustomerAccount/NewCustomerAccountRequest.cs:14
- NewCustomerAccountRequest.Zipcode BankApplication.Presentation/BankApplication.Contracts/Adminstrator/NewCustomerAccount/NewCustomerAccountRequest.cs:18
- Customer.Streetaddress BankApplication.Presentation/BankApplication.Contracts/Adminstrator/NewCustomerAccount/NewCustomerAccountResponse.cs:18
- Customer.Zipcode BankApplication.Presentation/BankApplication.Contracts/Adminstrator/NewCustomerAccount/NewCustomerAccountResponse.cs:20
Name — 8 field(s)
- NewCustomerAccountCommand.Givenname BankApplication.Application/Adminstrator/Commands/NewCustomerAccount/NewCustomerAccountCommand.cs:10
- NewCustomerAccountCommand.Surname BankApplication.Application/Adminstrator/Commands/NewCustomerAccount/NewCustomerAccountCommand.cs:11
- Customer.Givenname BankApplication.Domain/Entities/Customer.cs:12
- Customer.Surname BankApplication.Domain/Entities/Customer.cs:14
- NewCustomerAccountRequest.Givenname BankApplication.Presentation/BankApplication.Contracts/Adminstrator/NewCustomerAccount/NewCustomerAccountRequest.cs:10
- NewCustomerAccountRequest.Surname BankApplication.Presentation/BankApplication.Contracts/Adminstrator/NewCustomerAccount/NewCustomerAccountRequest.cs:12
- Customer.Givenname BankApplication.Presentation/BankApplication.Contracts/Adminstrator/NewCustomerAccount/NewCustomerAccountResponse.cs:16
- Customer.Surname BankApplication.Presentation/BankApplication.Contracts/Adminstrator/NewCustomerAccount/NewCustomerAccountResponse.cs:17
Email — 7 field(s)
- RegisterCommand.Email BankApplication.Application/Authentication/Commands/Register/RegisterCommand.cs:7
- LoginQuery.Email BankApplication.Application/Authentication/Queries/Login/LoginQuery.cs:7
- User.Email BankApplication.Domain/Entities/User.cs:10
- User.Email BankApplication.Presentation/BankApplication.Contracts/Adminstrator/NewCustomerAccount/NewCustomerAccountResponse.cs:33
- AuthenticationResponse.Email BankApplication.Presentation/BankApplication.Contracts/Authentication/AuthenticationResponse.cs:6
- LoginRequest.Email BankApplication.Presentation/BankApplication.Contracts/Authentication/LoginRequest.cs:5
- RegisterRequest.Email BankApplication.Presentation/BankApplication.Contracts/Authentication/RegisterRequest.cs:8
Phone — 7 field(s)
- NewCustomerAccountCommand.Telephonecountrycode BankApplication.Application/Adminstrator/Commands/NewCustomerAccount/NewCustomerAccountCommand.cs:18
- NewCustomerAccountCommand.Telephonenumber BankApplication.Application/Adminstrator/Commands/NewCustomerAccount/NewCustomerAccountCommand.cs:19
- Customer.Telephonecountrycode BankApplication.Domain/Entities/Customer.cs:28
- Customer.Telephonenumber BankApplication.Domain/Entities/Customer.cs:30
- NewCustomerAccountRequest.Telephonecountrycode BankApplication.Presentation/BankApplication.Contracts/Adminstrator/NewCustomerAccount/NewCustomerAccountRequest.cs:24
- NewCustomerAccountRequest.Telephonenumber BankApplication.Presentation/BankApplication.Contracts/Adminstrator/NewCustomerAccount/NewCustomerAccountRequest.cs:25
- Customer.Telephonenumber BankApplication.Presentation/BankApplication.Contracts/Adminstrator/NewCustomerAccount/NewCustomerAccountResponse.cs:22