Executive summary
VinoStudio/auth_service is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because two passwords or keys sit in the current code and we found no working pipeline that builds or tests changes to the code. It scores 55 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 33, is the weakest lens and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 18 points. Adding an automated build and test pipeline comes next, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 71.
Sixteen known security holes in the packages the code depends on can be used by attackers. Two passwords or keys are open to anyone who can read the repository, and one setting leaves the servers or containers unsafe. Updating the vulnerable packages, replacing each exposed password or key and correcting the unsafe settings would close these risks.
The product code is 11,393 lines, about €18,000 to rebuild.
If Production Readiness rose from 33 to 70, the lowest score rated Strong, the score would rise from 55 to about 71.
New since the last survey: 2 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 36 findings
- Boundary Type-Coupling · Cross-context type Permission (domain → infrastructure) src/infrastructure/base/repository/permission_repo.py
- Boundary Type-Coupling · Cross-context type Role (domain → infrastructure) src/infrastructure/base/repository/role_repo.py
- Boundary Type-Coupling · Cross-context type Role (domain → infrastructure) src/infrastructure/base/repository/role_repo.py
- Boundary Type-Coupling · Cross-context type Session (domain → infrastructure) src/infrastructure/base/repository/session_repo.py
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) src/infrastructure/base/repository/user_reader.py
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) src/infrastructure/base/repository/user_reader.py
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) src/infrastructure/base/repository/user_reader.py
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) src/infrastructure/base/repository/user_reader.py
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) src/infrastructure/base/repository/user_reader.py
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) src/infrastructure/base/repository/user_writer.py
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) src/infrastructure/base/repository/user_writer.py
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) src/infrastructure/repositories/converters.py
- Boundary Type-Coupling · Cross-context type Role (domain → infrastructure) src/infrastructure/repositories/converters.py
- Boundary Type-Coupling · Cross-context type Permission (domain → infrastructure) src/infrastructure/repositories/converters.py
- Boundary Type-Coupling · Cross-context type Session (domain → infrastructure) src/infrastructure/repositories/converters.py
- Boundary Type-Coupling · Cross-context type OAuthAccount (domain → infrastructure) src/infrastructure/repositories/converters.py
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) src/infrastructure/repositories/converters.py
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) src/infrastructure/repositories/converters.py
- Boundary Type-Coupling · Cross-context type Role (domain → infrastructure) src/infrastructure/repositories/converters.py
- Boundary Type-Coupling · Cross-context type Role (domain → infrastructure) src/infrastructure/repositories/converters.py
- Boundary Type-Coupling · Cross-context type Session (domain → infrastructure) src/infrastructure/repositories/converters.py
- Boundary Type-Coupling · Cross-context type OAuthAccount (domain → infrastructure) src/infrastructure/repositories/converters.py
- Boundary Type-Coupling · Cross-context type OAuthAccount (domain → infrastructure) src/infrastructure/repositories/oauth/oauth_repo.py
- Boundary Type-Coupling · Cross-context type OAuthAccount (domain → infrastructure) src/infrastructure/repositories/oauth/oauth_repo.py
- Boundary Type-Coupling · Cross-context type Permission (domain → infrastructure) src/infrastructure/repositories/permission/permission_repo.py
- Boundary Type-Coupling · Cross-context type Role (domain → infrastructure) src/infrastructure/repositories/role/role_repo.py
- Boundary Type-Coupling · Cross-context type Role (domain → infrastructure) src/infrastructure/repositories/role/role_repo.py
- Boundary Type-Coupling · Cross-context type Session (domain → infrastructure) src/infrastructure/repositories/session/session_repo.py
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) REDACTED
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) REDACTED
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) REDACTED
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) REDACTED
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) REDACTED
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) REDACTED
- Boundary Type-Coupling · Cross-context type User (domain → infrastructure) REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Rebuild cost: about €18,000 · Estimate
| Cost to rebuild | €5,800 to €29,000, for 97 to 308 hours of work, about 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.8 at a score of 55. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 11,393 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 application.base.commands.base | 2 application.base.commands.command_handler | 3 application.base.interface.request | 4 application.base.queries.base | 5 application.base.queries.query_handler | 6 domain.permission.entity.permission | 7 infrastructure.base.uow | 8 infrastructure.repositories.token.redis_repo | 9 application.base.security.jwt_manager | 10 application.base.session.session_manager | 11 domain.role.entity.role | 12 application.cqrs.user.commands.logout_user | 13 domain.user.entity.user | 14 application.base.security.jwt_user | 15 application.cqrs.user.commands.register_oauth_user | 16 application.cqrs.user.commands.register_user | 17 infrastructure.base.repository.user_reader | 18 infrastructure.repositories.converters | 19 application.cqrs.user.commands.change_user_email | 20 application.cqrs.user.commands.login_user | 21 application.cqrs.user.commands.oauth_login_user | 22 application.cqrs.user.commands.reset_user_password | 23 application.services.rbac.rbac_manager | 24 application.services.security.jwt_manager | 25 application.services.security.oauth_manager | 26 application.services.security.security_user | 27 application.cqrs.permission.commands.create_permission | 28 application.cqrs.permission.commands.delete_permission | 29 application.cqrs.role.commands.assign_role_to_user | 30 application.cqrs.role.commands.create_role | 31 application.cqrs.role.commands.delete_role | 32 application.cqrs.role.commands.remove_role_permissions | 33 application.cqrs.role.commands.remove_user_role | 34 application.cqrs.role.commands.update_role_description | 35 application.cqrs.role.commands.update_role_permissions | 36 application.cqrs.role.commands.update_role_security_lvl | 37 application.cqrs.user.commands.add_oauth_account_request | 38 application.cqrs.user.commands.add_oauth_account_to_current_user | 39 application.cqrs.user.commands.deactivate_oauth_account | 40 application.cqrs.cqrs_di_setup |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 application.base.commands.base | ||||||||||||||||||||||||||||||||||||||||
| 2 application.base.commands.command_handler | ||||||||||||||||||||||||||||||||||||||||
| 3 application.base.interface.request | ||||||||||||||||||||||||||||||||||||||||
| 4 application.base.queries.base | ||||||||||||||||||||||||||||||||||||||||
| 5 application.base.queries.query_handler | ||||||||||||||||||||||||||||||||||||||||
| 6 domain.permission.entity.permission | ||||||||||||||||||||||||||||||||||||||||
| 7 infrastructure.base.uow | ||||||||||||||||||||||||||||||||||||||||
| 8 infrastructure.repositories.token.redis_repo | ||||||||||||||||||||||||||||||||||||||||
| 9 application.base.security.jwt_manager | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 application.base.session.session_manager | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 domain.role.entity.role | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 application.cqrs.user.commands.logout_user | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 13 domain.user.entity.user | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 application.base.security.jwt_user | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 application.cqrs.user.commands.register_oauth_user | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 16 application.cqrs.user.commands.register_user | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 17 infrastructure.base.repository.user_reader | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 infrastructure.repositories.converters | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 19 application.cqrs.user.commands.change_user_email | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 20 application.cqrs.user.commands.login_user | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 21 application.cqrs.user.commands.oauth_login_user | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 22 application.cqrs.user.commands.reset_user_password | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 23 application.services.rbac.rbac_manager | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 application.services.security.jwt_manager | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 application.services.security.oauth_manager | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 application.services.security.security_user | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 application.cqrs.permission.commands.create_permission | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 28 application.cqrs.permission.commands.delete_permission | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 29 application.cqrs.role.commands.assign_role_to_user | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 30 application.cqrs.role.commands.create_role | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 31 application.cqrs.role.commands.delete_role | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 32 application.cqrs.role.commands.remove_role_permissions | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 33 application.cqrs.role.commands.remove_user_role | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 34 application.cqrs.role.commands.update_role_description | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 35 application.cqrs.role.commands.update_role_permissions | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 36 application.cqrs.role.commands.update_role_security_lvl | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 37 application.cqrs.user.commands.add_oauth_account_request | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 38 application.cqrs.user.commands.add_oauth_account_to_current_user | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 39 application.cqrs.user.commands.deactivate_oauth_account | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 40 application.cqrs.cqrs_di_setup | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
9→3 application.base.security.jwt_manager uses application.base.interface.request✕
- Connections
- 1 pair of types, where a type in application.base.security.jwt_manager uses a type in application.base.interface.request.
- The types involved
src.application.base.security.jwt_manager.BaseJWTManager→src.application.base.interface.request.RequestProtocol
- Direction
- application.base.security.jwt_manager uses application.base.interface.request, so a change to application.base.interface.request can break application.base.security.jwt_manager, while a change to application.base.security.jwt_manager can't break application.base.interface.request.
- Position
- Below the diagonal: application.base.security.jwt_manager uses a module listed above it, which is the healthy direction.
10→3 application.base.session.session_manager uses application.base.interface.request✕
- Connections
- 1 pair of types, where a type in application.base.session.session_manager uses a type in application.base.interface.request.
- The types involved
src.application.base.session.session_manager.BaseSessionManager→src.application.base.interface.request.RequestProtocol
- Direction
- application.base.session.session_manager uses application.base.interface.request, so a change to application.base.interface.request can break application.base.session.session_manager, while a change to application.base.session.session_manager can't break application.base.interface.request.
- Position
- Below the diagonal: application.base.session.session_manager uses a module listed above it, which is the healthy direction.
11→6 domain.role.entity.role uses domain.permission.entity.permission✕
- Connections
- 1 pair of types, where a type in domain.role.entity.role uses a type in domain.permission.entity.permission.
- The types involved
src.domain.role.entity.role.Role→src.domain.permission.entity.permission.Permission
- Direction
- domain.role.entity.role uses domain.permission.entity.permission, so a change to domain.permission.entity.permission can break domain.role.entity.role, while a change to domain.role.entity.role can't break domain.permission.entity.permission.
- Position
- Below the diagonal: domain.role.entity.role uses a module listed above it, which is the healthy direction.
12→1 application.cqrs.user.commands.logout_user uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.logout_user uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.user.commands.logout_user.LogoutUserCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.user.commands.logout_user uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.user.commands.logout_user, while a change to application.cqrs.user.commands.logout_user can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.user.commands.logout_user uses a module listed above it, which is the healthy direction.
12→2 application.cqrs.user.commands.logout_user uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.logout_user uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.user.commands.logout_user.LogoutUserCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.user.commands.logout_user uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.user.commands.logout_user, while a change to application.cqrs.user.commands.logout_user can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.user.commands.logout_user uses a module listed above it, which is the healthy direction.
12→3 application.cqrs.user.commands.logout_user uses application.base.interface.request✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.logout_user uses a type in application.base.interface.request.
- The types involved
src.application.cqrs.user.commands.logout_user.LogoutUserCommand→src.application.base.interface.request.RequestProtocol
- Direction
- application.cqrs.user.commands.logout_user uses application.base.interface.request, so a change to application.base.interface.request can break application.cqrs.user.commands.logout_user, while a change to application.cqrs.user.commands.logout_user can't break application.base.interface.request.
- Position
- Below the diagonal: application.cqrs.user.commands.logout_user uses a module listed above it, which is the healthy direction.
12→7 application.cqrs.user.commands.logout_user uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.logout_user uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.user.commands.logout_user.LogoutUserCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.user.commands.logout_user uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.user.commands.logout_user, while a change to application.cqrs.user.commands.logout_user can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.user.commands.logout_user uses a module listed above it, which is the healthy direction.
12→9 application.cqrs.user.commands.logout_user uses application.base.security.jwt_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.logout_user uses a type in application.base.security.jwt_manager.
- The types involved
src.application.cqrs.user.commands.logout_user.LogoutUserCommandHandler→src.application.base.security.jwt_manager.BaseJWTManager
- Direction
- application.cqrs.user.commands.logout_user uses application.base.security.jwt_manager, so a change to application.base.security.jwt_manager can break application.cqrs.user.commands.logout_user, while a change to application.cqrs.user.commands.logout_user can't break application.base.security.jwt_manager.
- Position
- Below the diagonal: application.cqrs.user.commands.logout_user uses a module listed above it, which is the healthy direction.
12→10 application.cqrs.user.commands.logout_user uses application.base.session.session_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.logout_user uses a type in application.base.session.session_manager.
- The types involved
src.application.cqrs.user.commands.logout_user.LogoutUserCommandHandler→src.application.base.session.session_manager.BaseSessionManager
- Direction
- application.cqrs.user.commands.logout_user uses application.base.session.session_manager, so a change to application.base.session.session_manager can break application.cqrs.user.commands.logout_user, while a change to application.cqrs.user.commands.logout_user can't break application.base.session.session_manager.
- Position
- Below the diagonal: application.cqrs.user.commands.logout_user uses a module listed above it, which is the healthy direction.
13→11 domain.user.entity.user uses domain.role.entity.role✕
- Connections
- 1 pair of types, where a type in domain.user.entity.user uses a type in domain.role.entity.role.
- The types involved
src.domain.user.entity.user.User→src.domain.role.entity.role.Role
- Direction
- domain.user.entity.user uses domain.role.entity.role, so a change to domain.role.entity.role can break domain.user.entity.user, while a change to domain.user.entity.user can't break domain.role.entity.role.
- Position
- Below the diagonal: domain.user.entity.user uses a module listed above it, which is the healthy direction.
14→13 application.base.security.jwt_user uses domain.user.entity.user✕
- Connections
- 1 pair of types, where a type in application.base.security.jwt_user uses a type in domain.user.entity.user.
- The types involved
src.application.base.security.jwt_user.JWTUserInterface→src.domain.user.entity.user.User
- Direction
- application.base.security.jwt_user uses domain.user.entity.user, so a change to domain.user.entity.user can break application.base.security.jwt_user, while a change to application.base.security.jwt_user can't break domain.user.entity.user.
- Position
- Below the diagonal: application.base.security.jwt_user uses a module listed above it, which is the healthy direction.
15→1 application.cqrs.user.commands.register_oauth_user uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.register_oauth_user uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.user.commands.register_oauth_user.RegisterOAuthUserCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.user.commands.register_oauth_user uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.user.commands.register_oauth_user, while a change to application.cqrs.user.commands.register_oauth_user can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.user.commands.register_oauth_user uses a module listed above it, which is the healthy direction.
15→2 application.cqrs.user.commands.register_oauth_user uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.register_oauth_user uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.user.commands.register_oauth_user.RegisterOAuthUserCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.user.commands.register_oauth_user uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.user.commands.register_oauth_user, while a change to application.cqrs.user.commands.register_oauth_user can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.user.commands.register_oauth_user uses a module listed above it, which is the healthy direction.
15→7 application.cqrs.user.commands.register_oauth_user uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.register_oauth_user uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.user.commands.register_oauth_user.RegisterOAuthUserCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.user.commands.register_oauth_user uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.user.commands.register_oauth_user, while a change to application.cqrs.user.commands.register_oauth_user can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.user.commands.register_oauth_user uses a module listed above it, which is the healthy direction.
15→13 application.cqrs.user.commands.register_oauth_user uses domain.user.entity.user✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.register_oauth_user uses a type in domain.user.entity.user.
- The types involved
src.application.cqrs.user.commands.register_oauth_user.RegisterOAuthUserCommandHandler→src.domain.user.entity.user.User
- Direction
- application.cqrs.user.commands.register_oauth_user uses domain.user.entity.user, so a change to domain.user.entity.user can break application.cqrs.user.commands.register_oauth_user, while a change to application.cqrs.user.commands.register_oauth_user can't break domain.user.entity.user.
- Position
- Below the diagonal: application.cqrs.user.commands.register_oauth_user uses a module listed above it, which is the healthy direction.
16→1 application.cqrs.user.commands.register_user uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.register_user uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.user.commands.register_user.RegisterUserCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.user.commands.register_user uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.user.commands.register_user, while a change to application.cqrs.user.commands.register_user can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.user.commands.register_user uses a module listed above it, which is the healthy direction.
16→2 application.cqrs.user.commands.register_user uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.register_user uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.user.commands.register_user.RegisterUserCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.user.commands.register_user uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.user.commands.register_user, while a change to application.cqrs.user.commands.register_user can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.user.commands.register_user uses a module listed above it, which is the healthy direction.
16→7 application.cqrs.user.commands.register_user uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.register_user uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.user.commands.register_user.RegisterUserCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.user.commands.register_user uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.user.commands.register_user, while a change to application.cqrs.user.commands.register_user can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.user.commands.register_user uses a module listed above it, which is the healthy direction.
16→13 application.cqrs.user.commands.register_user uses domain.user.entity.user✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.register_user uses a type in domain.user.entity.user.
- The types involved
src.application.cqrs.user.commands.register_user.RegisterUserCommandHandler→src.domain.user.entity.user.User
- Direction
- application.cqrs.user.commands.register_user uses domain.user.entity.user, so a change to domain.user.entity.user can break application.cqrs.user.commands.register_user, while a change to application.cqrs.user.commands.register_user can't break domain.user.entity.user.
- Position
- Below the diagonal: application.cqrs.user.commands.register_user uses a module listed above it, which is the healthy direction.
17→13 infrastructure.base.repository.user_reader uses domain.user.entity.user✕
- Connections
- 1 pair of types, where a type in infrastructure.base.repository.user_reader uses a type in domain.user.entity.user.
- The types involved
src.infrastructure.base.repository.user_reader.BaseUserReader→src.domain.user.entity.user.User
- Direction
- infrastructure.base.repository.user_reader uses domain.user.entity.user, so a change to domain.user.entity.user can break infrastructure.base.repository.user_reader, while a change to infrastructure.base.repository.user_reader can't break domain.user.entity.user.
- Position
- Below the diagonal: infrastructure.base.repository.user_reader uses a module listed above it, which is the healthy direction.
18→6 infrastructure.repositories.converters uses domain.permission.entity.permission✕
- Connections
- 1 pair of types, where a type in infrastructure.repositories.converters uses a type in domain.permission.entity.permission.
- The types involved
src.infrastructure.repositories.converters.OrmToDomainConverter→src.domain.permission.entity.permission.Permission
- Direction
- infrastructure.repositories.converters uses domain.permission.entity.permission, so a change to domain.permission.entity.permission can break infrastructure.repositories.converters, while a change to infrastructure.repositories.converters can't break domain.permission.entity.permission.
- Position
- Below the diagonal: infrastructure.repositories.converters uses a module listed above it, which is the healthy direction.
18→11 infrastructure.repositories.converters uses domain.role.entity.role✕
- Connections
- 2 pairs of types, where a type in infrastructure.repositories.converters uses a type in domain.role.entity.role.
- The types involved
src.infrastructure.repositories.converters.DomainToOrmConverter→src.domain.role.entity.role.Rolesrc.infrastructure.repositories.converters.OrmToDomainConverter→src.domain.role.entity.role.Role
- Direction
- infrastructure.repositories.converters uses domain.role.entity.role, so a change to domain.role.entity.role can break infrastructure.repositories.converters, while a change to infrastructure.repositories.converters can't break domain.role.entity.role.
- Position
- Below the diagonal: infrastructure.repositories.converters uses a module listed above it, which is the healthy direction.
18→13 infrastructure.repositories.converters uses domain.user.entity.user✕
- Connections
- 2 pairs of types, where a type in infrastructure.repositories.converters uses a type in domain.user.entity.user.
- The types involved
src.infrastructure.repositories.converters.DomainToOrmConverter→src.domain.user.entity.user.Usersrc.infrastructure.repositories.converters.OrmToDomainConverter→src.domain.user.entity.user.User
- Direction
- infrastructure.repositories.converters uses domain.user.entity.user, so a change to domain.user.entity.user can break infrastructure.repositories.converters, while a change to infrastructure.repositories.converters can't break domain.user.entity.user.
- Position
- Below the diagonal: infrastructure.repositories.converters uses a module listed above it, which is the healthy direction.
19→1 application.cqrs.user.commands.change_user_email uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.change_user_email uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.user.commands.change_user_email.ChangeUserEmailCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.user.commands.change_user_email uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.user.commands.change_user_email, while a change to application.cqrs.user.commands.change_user_email can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.user.commands.change_user_email uses a module listed above it, which is the healthy direction.
19→2 application.cqrs.user.commands.change_user_email uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.change_user_email uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.user.commands.change_user_email.ChangeUserEmailCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.user.commands.change_user_email uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.user.commands.change_user_email, while a change to application.cqrs.user.commands.change_user_email can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.user.commands.change_user_email uses a module listed above it, which is the healthy direction.
19→7 application.cqrs.user.commands.change_user_email uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.change_user_email uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.user.commands.change_user_email.ChangeUserEmailCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.user.commands.change_user_email uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.user.commands.change_user_email, while a change to application.cqrs.user.commands.change_user_email can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.user.commands.change_user_email uses a module listed above it, which is the healthy direction.
19→8 application.cqrs.user.commands.change_user_email uses infrastructure.repositories.token.redis_repo✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.change_user_email uses a type in infrastructure.repositories.token.redis_repo.
- The types involved
src.application.cqrs.user.commands.change_user_email.ChangeUserEmailCommandHandler→src.infrastructure.repositories.token.redis_repo.TokenBlackListRepository
- Direction
- application.cqrs.user.commands.change_user_email uses infrastructure.repositories.token.redis_repo, so a change to infrastructure.repositories.token.redis_repo can break application.cqrs.user.commands.change_user_email, while a change to application.cqrs.user.commands.change_user_email can't break infrastructure.repositories.token.redis_repo.
- Position
- Below the diagonal: application.cqrs.user.commands.change_user_email uses a module listed above it, which is the healthy direction.
19→13 application.cqrs.user.commands.change_user_email uses domain.user.entity.user✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.change_user_email uses a type in domain.user.entity.user.
- The types involved
src.application.cqrs.user.commands.change_user_email.ChangeUserEmailCommandHandler→src.domain.user.entity.user.User
- Direction
- application.cqrs.user.commands.change_user_email uses domain.user.entity.user, so a change to domain.user.entity.user can break application.cqrs.user.commands.change_user_email, while a change to application.cqrs.user.commands.change_user_email can't break domain.user.entity.user.
- Position
- Below the diagonal: application.cqrs.user.commands.change_user_email uses a module listed above it, which is the healthy direction.
19→17 application.cqrs.user.commands.change_user_email uses infrastructure.base.repository.user_reader✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.change_user_email uses a type in infrastructure.base.repository.user_reader.
- The types involved
src.application.cqrs.user.commands.change_user_email.ChangeUserEmailCommandHandler→src.infrastructure.base.repository.user_reader.BaseUserReader
- Direction
- application.cqrs.user.commands.change_user_email uses infrastructure.base.repository.user_reader, so a change to infrastructure.base.repository.user_reader can break application.cqrs.user.commands.change_user_email, while a change to application.cqrs.user.commands.change_user_email can't break infrastructure.base.repository.user_reader.
- Position
- Below the diagonal: application.cqrs.user.commands.change_user_email uses a module listed above it, which is the healthy direction.
20→1 application.cqrs.user.commands.login_user uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.login_user uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.user.commands.login_user.LoginUserCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.user.commands.login_user uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.user.commands.login_user, while a change to application.cqrs.user.commands.login_user can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.user.commands.login_user uses a module listed above it, which is the healthy direction.
20→2 application.cqrs.user.commands.login_user uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.login_user uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.user.commands.login_user.LoginUserCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.user.commands.login_user uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.user.commands.login_user, while a change to application.cqrs.user.commands.login_user can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.user.commands.login_user uses a module listed above it, which is the healthy direction.
20→7 application.cqrs.user.commands.login_user uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.login_user uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.user.commands.login_user.LoginUserCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.user.commands.login_user uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.user.commands.login_user, while a change to application.cqrs.user.commands.login_user can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.user.commands.login_user uses a module listed above it, which is the healthy direction.
20→9 application.cqrs.user.commands.login_user uses application.base.security.jwt_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.login_user uses a type in application.base.security.jwt_manager.
- The types involved
src.application.cqrs.user.commands.login_user.LoginUserCommandHandler→src.application.base.security.jwt_manager.BaseJWTManager
- Direction
- application.cqrs.user.commands.login_user uses application.base.security.jwt_manager, so a change to application.base.security.jwt_manager can break application.cqrs.user.commands.login_user, while a change to application.cqrs.user.commands.login_user can't break application.base.security.jwt_manager.
- Position
- Below the diagonal: application.cqrs.user.commands.login_user uses a module listed above it, which is the healthy direction.
20→10 application.cqrs.user.commands.login_user uses application.base.session.session_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.login_user uses a type in application.base.session.session_manager.
- The types involved
src.application.cqrs.user.commands.login_user.LoginUserCommandHandler→src.application.base.session.session_manager.BaseSessionManager
- Direction
- application.cqrs.user.commands.login_user uses application.base.session.session_manager, so a change to application.base.session.session_manager can break application.cqrs.user.commands.login_user, while a change to application.cqrs.user.commands.login_user can't break application.base.session.session_manager.
- Position
- Below the diagonal: application.cqrs.user.commands.login_user uses a module listed above it, which is the healthy direction.
20→17 application.cqrs.user.commands.login_user uses infrastructure.base.repository.user_reader✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.login_user uses a type in infrastructure.base.repository.user_reader.
- The types involved
src.application.cqrs.user.commands.login_user.LoginUserCommandHandler→src.infrastructure.base.repository.user_reader.BaseUserReader
- Direction
- application.cqrs.user.commands.login_user uses infrastructure.base.repository.user_reader, so a change to infrastructure.base.repository.user_reader can break application.cqrs.user.commands.login_user, while a change to application.cqrs.user.commands.login_user can't break infrastructure.base.repository.user_reader.
- Position
- Below the diagonal: application.cqrs.user.commands.login_user uses a module listed above it, which is the healthy direction.
21→1 application.cqrs.user.commands.oauth_login_user uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.oauth_login_user uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.user.commands.oauth_login_user.OAuthLoginUserCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.user.commands.oauth_login_user uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.user.commands.oauth_login_user, while a change to application.cqrs.user.commands.oauth_login_user can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.user.commands.oauth_login_user uses a module listed above it, which is the healthy direction.
21→2 application.cqrs.user.commands.oauth_login_user uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.oauth_login_user uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.user.commands.oauth_login_user.OAuthLoginUserCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.user.commands.oauth_login_user uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.user.commands.oauth_login_user, while a change to application.cqrs.user.commands.oauth_login_user can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.user.commands.oauth_login_user uses a module listed above it, which is the healthy direction.
21→7 application.cqrs.user.commands.oauth_login_user uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.oauth_login_user uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.user.commands.oauth_login_user.OAuthLoginUserCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.user.commands.oauth_login_user uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.user.commands.oauth_login_user, while a change to application.cqrs.user.commands.oauth_login_user can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.user.commands.oauth_login_user uses a module listed above it, which is the healthy direction.
21→9 application.cqrs.user.commands.oauth_login_user uses application.base.security.jwt_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.oauth_login_user uses a type in application.base.security.jwt_manager.
- The types involved
src.application.cqrs.user.commands.oauth_login_user.OAuthLoginUserCommandHandler→src.application.base.security.jwt_manager.BaseJWTManager
- Direction
- application.cqrs.user.commands.oauth_login_user uses application.base.security.jwt_manager, so a change to application.base.security.jwt_manager can break application.cqrs.user.commands.oauth_login_user, while a change to application.cqrs.user.commands.oauth_login_user can't break application.base.security.jwt_manager.
- Position
- Below the diagonal: application.cqrs.user.commands.oauth_login_user uses a module listed above it, which is the healthy direction.
21→10 application.cqrs.user.commands.oauth_login_user uses application.base.session.session_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.oauth_login_user uses a type in application.base.session.session_manager.
- The types involved
src.application.cqrs.user.commands.oauth_login_user.OAuthLoginUserCommandHandler→src.application.base.session.session_manager.BaseSessionManager
- Direction
- application.cqrs.user.commands.oauth_login_user uses application.base.session.session_manager, so a change to application.base.session.session_manager can break application.cqrs.user.commands.oauth_login_user, while a change to application.cqrs.user.commands.oauth_login_user can't break application.base.session.session_manager.
- Position
- Below the diagonal: application.cqrs.user.commands.oauth_login_user uses a module listed above it, which is the healthy direction.
21→17 application.cqrs.user.commands.oauth_login_user uses infrastructure.base.repository.user_reader✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.oauth_login_user uses a type in infrastructure.base.repository.user_reader.
- The types involved
src.application.cqrs.user.commands.oauth_login_user.OAuthLoginUserCommandHandler→src.infrastructure.base.repository.user_reader.BaseUserReader
- Direction
- application.cqrs.user.commands.oauth_login_user uses infrastructure.base.repository.user_reader, so a change to infrastructure.base.repository.user_reader can break application.cqrs.user.commands.oauth_login_user, while a change to application.cqrs.user.commands.oauth_login_user can't break infrastructure.base.repository.user_reader.
- Position
- Below the diagonal: application.cqrs.user.commands.oauth_login_user uses a module listed above it, which is the healthy direction.
22→1 application.cqrs.user.commands.reset_user_password uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.reset_user_password uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.user.commands.reset_user_password.ResetUserPasswordCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.user.commands.reset_user_password uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.user.commands.reset_user_password, while a change to application.cqrs.user.commands.reset_user_password can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.user.commands.reset_user_password uses a module listed above it, which is the healthy direction.
22→2 application.cqrs.user.commands.reset_user_password uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.reset_user_password uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.user.commands.reset_user_password.ResetUserPasswordCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.user.commands.reset_user_password uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.user.commands.reset_user_password, while a change to application.cqrs.user.commands.reset_user_password can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.user.commands.reset_user_password uses a module listed above it, which is the healthy direction.
22→7 application.cqrs.user.commands.reset_user_password uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.reset_user_password uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.user.commands.reset_user_password.ResetUserPasswordCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.user.commands.reset_user_password uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.user.commands.reset_user_password, while a change to application.cqrs.user.commands.reset_user_password can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.user.commands.reset_user_password uses a module listed above it, which is the healthy direction.
22→8 application.cqrs.user.commands.reset_user_password uses infrastructure.repositories.token.redis_repo✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.reset_user_password uses a type in infrastructure.repositories.token.redis_repo.
- The types involved
src.application.cqrs.user.commands.reset_user_password.ResetUserPasswordCommandHandler→src.infrastructure.repositories.token.redis_repo.TokenBlackListRepository
- Direction
- application.cqrs.user.commands.reset_user_password uses infrastructure.repositories.token.redis_repo, so a change to infrastructure.repositories.token.redis_repo can break application.cqrs.user.commands.reset_user_password, while a change to application.cqrs.user.commands.reset_user_password can't break infrastructure.repositories.token.redis_repo.
- Position
- Below the diagonal: application.cqrs.user.commands.reset_user_password uses a module listed above it, which is the healthy direction.
22→13 application.cqrs.user.commands.reset_user_password uses domain.user.entity.user✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.reset_user_password uses a type in domain.user.entity.user.
- The types involved
src.application.cqrs.user.commands.reset_user_password.ResetUserPasswordCommandHandler→src.domain.user.entity.user.User
- Direction
- application.cqrs.user.commands.reset_user_password uses domain.user.entity.user, so a change to domain.user.entity.user can break application.cqrs.user.commands.reset_user_password, while a change to application.cqrs.user.commands.reset_user_password can't break domain.user.entity.user.
- Position
- Below the diagonal: application.cqrs.user.commands.reset_user_password uses a module listed above it, which is the healthy direction.
22→17 application.cqrs.user.commands.reset_user_password uses infrastructure.base.repository.user_reader✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.reset_user_password uses a type in infrastructure.base.repository.user_reader.
- The types involved
src.application.cqrs.user.commands.reset_user_password.ResetUserPasswordCommandHandler→src.infrastructure.base.repository.user_reader.BaseUserReader
- Direction
- application.cqrs.user.commands.reset_user_password uses infrastructure.base.repository.user_reader, so a change to infrastructure.base.repository.user_reader can break application.cqrs.user.commands.reset_user_password, while a change to application.cqrs.user.commands.reset_user_password can't break infrastructure.base.repository.user_reader.
- Position
- Below the diagonal: application.cqrs.user.commands.reset_user_password uses a module listed above it, which is the healthy direction.
23→6 application.services.rbac.rbac_manager uses domain.permission.entity.permission✕
- Connections
- 1 pair of types, where a type in application.services.rbac.rbac_manager uses a type in domain.permission.entity.permission.
- The types involved
src.application.services.rbac.rbac_manager.RBACManager→src.domain.permission.entity.permission.Permission
- Direction
- application.services.rbac.rbac_manager uses domain.permission.entity.permission, so a change to domain.permission.entity.permission can break application.services.rbac.rbac_manager, while a change to application.services.rbac.rbac_manager can't break domain.permission.entity.permission.
- Position
- Below the diagonal: application.services.rbac.rbac_manager uses a module listed above it, which is the healthy direction.
23→11 application.services.rbac.rbac_manager uses domain.role.entity.role✕
- Connections
- 1 pair of types, where a type in application.services.rbac.rbac_manager uses a type in domain.role.entity.role.
- The types involved
src.application.services.rbac.rbac_manager.RBACManager→src.domain.role.entity.role.Role
- Direction
- application.services.rbac.rbac_manager uses domain.role.entity.role, so a change to domain.role.entity.role can break application.services.rbac.rbac_manager, while a change to application.services.rbac.rbac_manager can't break domain.role.entity.role.
- Position
- Below the diagonal: application.services.rbac.rbac_manager uses a module listed above it, which is the healthy direction.
23→13 application.services.rbac.rbac_manager uses domain.user.entity.user✕
- Connections
- 1 pair of types, where a type in application.services.rbac.rbac_manager uses a type in domain.user.entity.user.
- The types involved
src.application.services.rbac.rbac_manager.RBACManager→src.domain.user.entity.user.User
- Direction
- application.services.rbac.rbac_manager uses domain.user.entity.user, so a change to domain.user.entity.user can break application.services.rbac.rbac_manager, while a change to application.services.rbac.rbac_manager can't break domain.user.entity.user.
- Position
- Below the diagonal: application.services.rbac.rbac_manager uses a module listed above it, which is the healthy direction.
23→14 application.services.rbac.rbac_manager uses application.base.security.jwt_user✕
- Connections
- 1 pair of types, where a type in application.services.rbac.rbac_manager uses a type in application.base.security.jwt_user.
- The types involved
src.application.services.rbac.rbac_manager.RBACManager→src.application.base.security.jwt_user.JWTUserInterface
- Direction
- application.services.rbac.rbac_manager uses application.base.security.jwt_user, so a change to application.base.security.jwt_user can break application.services.rbac.rbac_manager, while a change to application.services.rbac.rbac_manager can't break application.base.security.jwt_user.
- Position
- Below the diagonal: application.services.rbac.rbac_manager uses a module listed above it, which is the healthy direction.
24→3 application.services.security.jwt_manager uses application.base.interface.request✕
- Connections
- 1 pair of types, where a type in application.services.security.jwt_manager uses a type in application.base.interface.request.
- The types involved
src.application.services.security.jwt_manager.JWTManager→src.application.base.interface.request.RequestProtocol
- Direction
- application.services.security.jwt_manager uses application.base.interface.request, so a change to application.base.interface.request can break application.services.security.jwt_manager, while a change to application.services.security.jwt_manager can't break application.base.interface.request.
- Position
- Below the diagonal: application.services.security.jwt_manager uses a module listed above it, which is the healthy direction.
24→8 application.services.security.jwt_manager uses infrastructure.repositories.token.redis_repo✕
- Connections
- 1 pair of types, where a type in application.services.security.jwt_manager uses a type in infrastructure.repositories.token.redis_repo.
- The types involved
src.application.services.security.jwt_manager.JWTManager→src.infrastructure.repositories.token.redis_repo.TokenBlackListRepository
- Direction
- application.services.security.jwt_manager uses infrastructure.repositories.token.redis_repo, so a change to infrastructure.repositories.token.redis_repo can break application.services.security.jwt_manager, while a change to application.services.security.jwt_manager can't break infrastructure.repositories.token.redis_repo.
- Position
- Below the diagonal: application.services.security.jwt_manager uses a module listed above it, which is the healthy direction.
24→9 application.services.security.jwt_manager uses application.base.security.jwt_manager✕
- Connections
- 1 pair of types, where a type in application.services.security.jwt_manager uses a type in application.base.security.jwt_manager.
- The types involved
src.application.services.security.jwt_manager.JWTManager→src.application.base.security.jwt_manager.BaseJWTManager
- Direction
- application.services.security.jwt_manager uses application.base.security.jwt_manager, so a change to application.base.security.jwt_manager can break application.services.security.jwt_manager, while a change to application.services.security.jwt_manager can't break application.base.security.jwt_manager.
- Position
- Below the diagonal: application.services.security.jwt_manager uses a module listed above it, which is the healthy direction.
24→14 application.services.security.jwt_manager uses application.base.security.jwt_user✕
- Connections
- 1 pair of types, where a type in application.services.security.jwt_manager uses a type in application.base.security.jwt_user.
- The types involved
src.application.services.security.jwt_manager.JWTManager→src.application.base.security.jwt_user.JWTUserInterface
- Direction
- application.services.security.jwt_manager uses application.base.security.jwt_user, so a change to application.base.security.jwt_user can break application.services.security.jwt_manager, while a change to application.services.security.jwt_manager can't break application.base.security.jwt_user.
- Position
- Below the diagonal: application.services.security.jwt_manager uses a module listed above it, which is the healthy direction.
25→17 application.services.security.oauth_manager uses infrastructure.base.repository.user_reader✕
- Connections
- 1 pair of types, where a type in application.services.security.oauth_manager uses a type in infrastructure.base.repository.user_reader.
- The types involved
src.application.services.security.oauth_manager.OAuthManager→src.infrastructure.base.repository.user_reader.BaseUserReader
- Direction
- application.services.security.oauth_manager uses infrastructure.base.repository.user_reader, so a change to infrastructure.base.repository.user_reader can break application.services.security.oauth_manager, while a change to application.services.security.oauth_manager can't break infrastructure.base.repository.user_reader.
- Position
- Below the diagonal: application.services.security.oauth_manager uses a module listed above it, which is the healthy direction.
26→13 application.services.security.security_user uses domain.user.entity.user✕
- Connections
- 1 pair of types, where a type in application.services.security.security_user uses a type in domain.user.entity.user.
- The types involved
src.application.services.security.security_user.SecurityUser→src.domain.user.entity.user.User
- Direction
- application.services.security.security_user uses domain.user.entity.user, so a change to domain.user.entity.user can break application.services.security.security_user, while a change to application.services.security.security_user can't break domain.user.entity.user.
- Position
- Below the diagonal: application.services.security.security_user uses a module listed above it, which is the healthy direction.
26→14 application.services.security.security_user uses application.base.security.jwt_user✕
- Connections
- 1 pair of types, where a type in application.services.security.security_user uses a type in application.base.security.jwt_user.
- The types involved
src.application.services.security.security_user.SecurityUser→src.application.base.security.jwt_user.JWTUserInterface
- Direction
- application.services.security.security_user uses application.base.security.jwt_user, so a change to application.base.security.jwt_user can break application.services.security.security_user, while a change to application.services.security.security_user can't break application.base.security.jwt_user.
- Position
- Below the diagonal: application.services.security.security_user uses a module listed above it, which is the healthy direction.
27→1 application.cqrs.permission.commands.create_permission uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.permission.commands.create_permission uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.permission.commands.create_permission.CreatePermissionCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.permission.commands.create_permission uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.permission.commands.create_permission, while a change to application.cqrs.permission.commands.create_permission can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.permission.commands.create_permission uses a module listed above it, which is the healthy direction.
27→2 application.cqrs.permission.commands.create_permission uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.permission.commands.create_permission uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.permission.commands.create_permission.CreatePermissionCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.permission.commands.create_permission uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.permission.commands.create_permission, while a change to application.cqrs.permission.commands.create_permission can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.permission.commands.create_permission uses a module listed above it, which is the healthy direction.
27→3 application.cqrs.permission.commands.create_permission uses application.base.interface.request✕
- Connections
- 1 pair of types, where a type in application.cqrs.permission.commands.create_permission uses a type in application.base.interface.request.
- The types involved
src.application.cqrs.permission.commands.create_permission.CreatePermissionCommand→src.application.base.interface.request.RequestProtocol
- Direction
- application.cqrs.permission.commands.create_permission uses application.base.interface.request, so a change to application.base.interface.request can break application.cqrs.permission.commands.create_permission, while a change to application.cqrs.permission.commands.create_permission can't break application.base.interface.request.
- Position
- Below the diagonal: application.cqrs.permission.commands.create_permission uses a module listed above it, which is the healthy direction.
27→6 application.cqrs.permission.commands.create_permission uses domain.permission.entity.permission✕
- Connections
- 1 pair of types, where a type in application.cqrs.permission.commands.create_permission uses a type in domain.permission.entity.permission.
- The types involved
src.application.cqrs.permission.commands.create_permission.CreatePermissionCommandHandler→src.domain.permission.entity.permission.Permission
- Direction
- application.cqrs.permission.commands.create_permission uses domain.permission.entity.permission, so a change to domain.permission.entity.permission can break application.cqrs.permission.commands.create_permission, while a change to application.cqrs.permission.commands.create_permission can't break domain.permission.entity.permission.
- Position
- Below the diagonal: application.cqrs.permission.commands.create_permission uses a module listed above it, which is the healthy direction.
27→7 application.cqrs.permission.commands.create_permission uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.permission.commands.create_permission uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.permission.commands.create_permission.CreatePermissionCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.permission.commands.create_permission uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.permission.commands.create_permission, while a change to application.cqrs.permission.commands.create_permission can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.permission.commands.create_permission uses a module listed above it, which is the healthy direction.
27→9 application.cqrs.permission.commands.create_permission uses application.base.security.jwt_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.permission.commands.create_permission uses a type in application.base.security.jwt_manager.
- The types involved
src.application.cqrs.permission.commands.create_permission.CreatePermissionCommandHandler→src.application.base.security.jwt_manager.BaseJWTManager
- Direction
- application.cqrs.permission.commands.create_permission uses application.base.security.jwt_manager, so a change to application.base.security.jwt_manager can break application.cqrs.permission.commands.create_permission, while a change to application.cqrs.permission.commands.create_permission can't break application.base.security.jwt_manager.
- Position
- Below the diagonal: application.cqrs.permission.commands.create_permission uses a module listed above it, which is the healthy direction.
27→23 application.cqrs.permission.commands.create_permission uses application.services.rbac.rbac_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.permission.commands.create_permission uses a type in application.services.rbac.rbac_manager.
- The types involved
src.application.cqrs.permission.commands.create_permission.CreatePermissionCommandHandler→src.application.services.rbac.rbac_manager.RBACManager
- Direction
- application.cqrs.permission.commands.create_permission uses application.services.rbac.rbac_manager, so a change to application.services.rbac.rbac_manager can break application.cqrs.permission.commands.create_permission, while a change to application.cqrs.permission.commands.create_permission can't break application.services.rbac.rbac_manager.
- Position
- Below the diagonal: application.cqrs.permission.commands.create_permission uses a module listed above it, which is the healthy direction.
27→26 application.cqrs.permission.commands.create_permission uses application.services.security.security_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.permission.commands.create_permission uses a type in application.services.security.security_user.
- The types involved
src.application.cqrs.permission.commands.create_permission.CreatePermissionCommandHandler→src.application.services.security.security_user.SecurityUser
- Direction
- application.cqrs.permission.commands.create_permission uses application.services.security.security_user, so a change to application.services.security.security_user can break application.cqrs.permission.commands.create_permission, while a change to application.cqrs.permission.commands.create_permission can't break application.services.security.security_user.
- Position
- Below the diagonal: application.cqrs.permission.commands.create_permission uses a module listed above it, which is the healthy direction.
28→1 application.cqrs.permission.commands.delete_permission uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.permission.commands.delete_permission uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.permission.commands.delete_permission.DeletePermissionCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.permission.commands.delete_permission uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.permission.commands.delete_permission, while a change to application.cqrs.permission.commands.delete_permission can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.permission.commands.delete_permission uses a module listed above it, which is the healthy direction.
28→2 application.cqrs.permission.commands.delete_permission uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.permission.commands.delete_permission uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.permission.commands.delete_permission.DeletePermissionCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.permission.commands.delete_permission uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.permission.commands.delete_permission, while a change to application.cqrs.permission.commands.delete_permission can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.permission.commands.delete_permission uses a module listed above it, which is the healthy direction.
28→3 application.cqrs.permission.commands.delete_permission uses application.base.interface.request✕
- Connections
- 1 pair of types, where a type in application.cqrs.permission.commands.delete_permission uses a type in application.base.interface.request.
- The types involved
src.application.cqrs.permission.commands.delete_permission.DeletePermissionCommand→src.application.base.interface.request.RequestProtocol
- Direction
- application.cqrs.permission.commands.delete_permission uses application.base.interface.request, so a change to application.base.interface.request can break application.cqrs.permission.commands.delete_permission, while a change to application.cqrs.permission.commands.delete_permission can't break application.base.interface.request.
- Position
- Below the diagonal: application.cqrs.permission.commands.delete_permission uses a module listed above it, which is the healthy direction.
28→7 application.cqrs.permission.commands.delete_permission uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.permission.commands.delete_permission uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.permission.commands.delete_permission.DeletePermissionCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.permission.commands.delete_permission uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.permission.commands.delete_permission, while a change to application.cqrs.permission.commands.delete_permission can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.permission.commands.delete_permission uses a module listed above it, which is the healthy direction.
28→9 application.cqrs.permission.commands.delete_permission uses application.base.security.jwt_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.permission.commands.delete_permission uses a type in application.base.security.jwt_manager.
- The types involved
src.application.cqrs.permission.commands.delete_permission.DeletePermissionCommandHandler→src.application.base.security.jwt_manager.BaseJWTManager
- Direction
- application.cqrs.permission.commands.delete_permission uses application.base.security.jwt_manager, so a change to application.base.security.jwt_manager can break application.cqrs.permission.commands.delete_permission, while a change to application.cqrs.permission.commands.delete_permission can't break application.base.security.jwt_manager.
- Position
- Below the diagonal: application.cqrs.permission.commands.delete_permission uses a module listed above it, which is the healthy direction.
28→23 application.cqrs.permission.commands.delete_permission uses application.services.rbac.rbac_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.permission.commands.delete_permission uses a type in application.services.rbac.rbac_manager.
- The types involved
src.application.cqrs.permission.commands.delete_permission.DeletePermissionCommandHandler→src.application.services.rbac.rbac_manager.RBACManager
- Direction
- application.cqrs.permission.commands.delete_permission uses application.services.rbac.rbac_manager, so a change to application.services.rbac.rbac_manager can break application.cqrs.permission.commands.delete_permission, while a change to application.cqrs.permission.commands.delete_permission can't break application.services.rbac.rbac_manager.
- Position
- Below the diagonal: application.cqrs.permission.commands.delete_permission uses a module listed above it, which is the healthy direction.
28→26 application.cqrs.permission.commands.delete_permission uses application.services.security.security_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.permission.commands.delete_permission uses a type in application.services.security.security_user.
- The types involved
src.application.cqrs.permission.commands.delete_permission.DeletePermissionCommandHandler→src.application.services.security.security_user.SecurityUser
- Direction
- application.cqrs.permission.commands.delete_permission uses application.services.security.security_user, so a change to application.services.security.security_user can break application.cqrs.permission.commands.delete_permission, while a change to application.cqrs.permission.commands.delete_permission can't break application.services.security.security_user.
- Position
- Below the diagonal: application.cqrs.permission.commands.delete_permission uses a module listed above it, which is the healthy direction.
29→1 application.cqrs.role.commands.assign_role_to_user uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.assign_role_to_user uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.role.commands.assign_role_to_user.AssignRoleCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.role.commands.assign_role_to_user uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.role.commands.assign_role_to_user, while a change to application.cqrs.role.commands.assign_role_to_user can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.role.commands.assign_role_to_user uses a module listed above it, which is the healthy direction.
29→2 application.cqrs.role.commands.assign_role_to_user uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.assign_role_to_user uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.role.commands.assign_role_to_user.AssignRoleCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.role.commands.assign_role_to_user uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.role.commands.assign_role_to_user, while a change to application.cqrs.role.commands.assign_role_to_user can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.role.commands.assign_role_to_user uses a module listed above it, which is the healthy direction.
29→3 application.cqrs.role.commands.assign_role_to_user uses application.base.interface.request✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.assign_role_to_user uses a type in application.base.interface.request.
- The types involved
src.application.cqrs.role.commands.assign_role_to_user.AssignRoleCommand→src.application.base.interface.request.RequestProtocol
- Direction
- application.cqrs.role.commands.assign_role_to_user uses application.base.interface.request, so a change to application.base.interface.request can break application.cqrs.role.commands.assign_role_to_user, while a change to application.cqrs.role.commands.assign_role_to_user can't break application.base.interface.request.
- Position
- Below the diagonal: application.cqrs.role.commands.assign_role_to_user uses a module listed above it, which is the healthy direction.
29→7 application.cqrs.role.commands.assign_role_to_user uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.assign_role_to_user uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.role.commands.assign_role_to_user.AssignRoleCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.role.commands.assign_role_to_user uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.role.commands.assign_role_to_user, while a change to application.cqrs.role.commands.assign_role_to_user can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.role.commands.assign_role_to_user uses a module listed above it, which is the healthy direction.
29→8 application.cqrs.role.commands.assign_role_to_user uses infrastructure.repositories.token.redis_repo✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.assign_role_to_user uses a type in infrastructure.repositories.token.redis_repo.
- The types involved
src.application.cqrs.role.commands.assign_role_to_user.AssignRoleCommandHandler→src.infrastructure.repositories.token.redis_repo.TokenBlackListRepository
- Direction
- application.cqrs.role.commands.assign_role_to_user uses infrastructure.repositories.token.redis_repo, so a change to infrastructure.repositories.token.redis_repo can break application.cqrs.role.commands.assign_role_to_user, while a change to application.cqrs.role.commands.assign_role_to_user can't break infrastructure.repositories.token.redis_repo.
- Position
- Below the diagonal: application.cqrs.role.commands.assign_role_to_user uses a module listed above it, which is the healthy direction.
29→9 application.cqrs.role.commands.assign_role_to_user uses application.base.security.jwt_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.assign_role_to_user uses a type in application.base.security.jwt_manager.
- The types involved
src.application.cqrs.role.commands.assign_role_to_user.AssignRoleCommandHandler→src.application.base.security.jwt_manager.BaseJWTManager
- Direction
- application.cqrs.role.commands.assign_role_to_user uses application.base.security.jwt_manager, so a change to application.base.security.jwt_manager can break application.cqrs.role.commands.assign_role_to_user, while a change to application.cqrs.role.commands.assign_role_to_user can't break application.base.security.jwt_manager.
- Position
- Below the diagonal: application.cqrs.role.commands.assign_role_to_user uses a module listed above it, which is the healthy direction.
29→13 application.cqrs.role.commands.assign_role_to_user uses domain.user.entity.user✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.assign_role_to_user uses a type in domain.user.entity.user.
- The types involved
src.application.cqrs.role.commands.assign_role_to_user.AssignRoleCommandHandler→src.domain.user.entity.user.User
- Direction
- application.cqrs.role.commands.assign_role_to_user uses domain.user.entity.user, so a change to domain.user.entity.user can break application.cqrs.role.commands.assign_role_to_user, while a change to application.cqrs.role.commands.assign_role_to_user can't break domain.user.entity.user.
- Position
- Below the diagonal: application.cqrs.role.commands.assign_role_to_user uses a module listed above it, which is the healthy direction.
29→17 application.cqrs.role.commands.assign_role_to_user uses infrastructure.base.repository.user_reader✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.assign_role_to_user uses a type in infrastructure.base.repository.user_reader.
- The types involved
src.application.cqrs.role.commands.assign_role_to_user.AssignRoleCommandHandler→src.infrastructure.base.repository.user_reader.BaseUserReader
- Direction
- application.cqrs.role.commands.assign_role_to_user uses infrastructure.base.repository.user_reader, so a change to infrastructure.base.repository.user_reader can break application.cqrs.role.commands.assign_role_to_user, while a change to application.cqrs.role.commands.assign_role_to_user can't break infrastructure.base.repository.user_reader.
- Position
- Below the diagonal: application.cqrs.role.commands.assign_role_to_user uses a module listed above it, which is the healthy direction.
29→23 application.cqrs.role.commands.assign_role_to_user uses application.services.rbac.rbac_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.assign_role_to_user uses a type in application.services.rbac.rbac_manager.
- The types involved
src.application.cqrs.role.commands.assign_role_to_user.AssignRoleCommandHandler→src.application.services.rbac.rbac_manager.RBACManager
- Direction
- application.cqrs.role.commands.assign_role_to_user uses application.services.rbac.rbac_manager, so a change to application.services.rbac.rbac_manager can break application.cqrs.role.commands.assign_role_to_user, while a change to application.cqrs.role.commands.assign_role_to_user can't break application.services.rbac.rbac_manager.
- Position
- Below the diagonal: application.cqrs.role.commands.assign_role_to_user uses a module listed above it, which is the healthy direction.
29→26 application.cqrs.role.commands.assign_role_to_user uses application.services.security.security_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.assign_role_to_user uses a type in application.services.security.security_user.
- The types involved
src.application.cqrs.role.commands.assign_role_to_user.AssignRoleCommandHandler→src.application.services.security.security_user.SecurityUser
- Direction
- application.cqrs.role.commands.assign_role_to_user uses application.services.security.security_user, so a change to application.services.security.security_user can break application.cqrs.role.commands.assign_role_to_user, while a change to application.cqrs.role.commands.assign_role_to_user can't break application.services.security.security_user.
- Position
- Below the diagonal: application.cqrs.role.commands.assign_role_to_user uses a module listed above it, which is the healthy direction.
30→1 application.cqrs.role.commands.create_role uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.create_role uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.role.commands.create_role.CreateRoleCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.role.commands.create_role uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.role.commands.create_role, while a change to application.cqrs.role.commands.create_role can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.role.commands.create_role uses a module listed above it, which is the healthy direction.
30→2 application.cqrs.role.commands.create_role uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.create_role uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.role.commands.create_role.CreateRoleCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.role.commands.create_role uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.role.commands.create_role, while a change to application.cqrs.role.commands.create_role can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.role.commands.create_role uses a module listed above it, which is the healthy direction.
30→3 application.cqrs.role.commands.create_role uses application.base.interface.request✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.create_role uses a type in application.base.interface.request.
- The types involved
src.application.cqrs.role.commands.create_role.CreateRoleCommand→src.application.base.interface.request.RequestProtocol
- Direction
- application.cqrs.role.commands.create_role uses application.base.interface.request, so a change to application.base.interface.request can break application.cqrs.role.commands.create_role, while a change to application.cqrs.role.commands.create_role can't break application.base.interface.request.
- Position
- Below the diagonal: application.cqrs.role.commands.create_role uses a module listed above it, which is the healthy direction.
30→7 application.cqrs.role.commands.create_role uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.create_role uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.role.commands.create_role.CreateRoleCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.role.commands.create_role uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.role.commands.create_role, while a change to application.cqrs.role.commands.create_role can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.role.commands.create_role uses a module listed above it, which is the healthy direction.
30→9 application.cqrs.role.commands.create_role uses application.base.security.jwt_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.create_role uses a type in application.base.security.jwt_manager.
- The types involved
src.application.cqrs.role.commands.create_role.CreateRoleCommandHandler→src.application.base.security.jwt_manager.BaseJWTManager
- Direction
- application.cqrs.role.commands.create_role uses application.base.security.jwt_manager, so a change to application.base.security.jwt_manager can break application.cqrs.role.commands.create_role, while a change to application.cqrs.role.commands.create_role can't break application.base.security.jwt_manager.
- Position
- Below the diagonal: application.cqrs.role.commands.create_role uses a module listed above it, which is the healthy direction.
30→11 application.cqrs.role.commands.create_role uses domain.role.entity.role✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.create_role uses a type in domain.role.entity.role.
- The types involved
src.application.cqrs.role.commands.create_role.CreateRoleCommandHandler→src.domain.role.entity.role.Role
- Direction
- application.cqrs.role.commands.create_role uses domain.role.entity.role, so a change to domain.role.entity.role can break application.cqrs.role.commands.create_role, while a change to application.cqrs.role.commands.create_role can't break domain.role.entity.role.
- Position
- Below the diagonal: application.cqrs.role.commands.create_role uses a module listed above it, which is the healthy direction.
30→23 application.cqrs.role.commands.create_role uses application.services.rbac.rbac_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.create_role uses a type in application.services.rbac.rbac_manager.
- The types involved
src.application.cqrs.role.commands.create_role.CreateRoleCommandHandler→src.application.services.rbac.rbac_manager.RBACManager
- Direction
- application.cqrs.role.commands.create_role uses application.services.rbac.rbac_manager, so a change to application.services.rbac.rbac_manager can break application.cqrs.role.commands.create_role, while a change to application.cqrs.role.commands.create_role can't break application.services.rbac.rbac_manager.
- Position
- Below the diagonal: application.cqrs.role.commands.create_role uses a module listed above it, which is the healthy direction.
30→26 application.cqrs.role.commands.create_role uses application.services.security.security_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.create_role uses a type in application.services.security.security_user.
- The types involved
src.application.cqrs.role.commands.create_role.CreateRoleCommandHandler→src.application.services.security.security_user.SecurityUser
- Direction
- application.cqrs.role.commands.create_role uses application.services.security.security_user, so a change to application.services.security.security_user can break application.cqrs.role.commands.create_role, while a change to application.cqrs.role.commands.create_role can't break application.services.security.security_user.
- Position
- Below the diagonal: application.cqrs.role.commands.create_role uses a module listed above it, which is the healthy direction.
31→1 application.cqrs.role.commands.delete_role uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.delete_role uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.role.commands.delete_role.DeleteRoleCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.role.commands.delete_role uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.role.commands.delete_role, while a change to application.cqrs.role.commands.delete_role can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.role.commands.delete_role uses a module listed above it, which is the healthy direction.
31→2 application.cqrs.role.commands.delete_role uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.delete_role uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.role.commands.delete_role.DeleteRoleCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.role.commands.delete_role uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.role.commands.delete_role, while a change to application.cqrs.role.commands.delete_role can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.role.commands.delete_role uses a module listed above it, which is the healthy direction.
31→3 application.cqrs.role.commands.delete_role uses application.base.interface.request✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.delete_role uses a type in application.base.interface.request.
- The types involved
src.application.cqrs.role.commands.delete_role.DeleteRoleCommand→src.application.base.interface.request.RequestProtocol
- Direction
- application.cqrs.role.commands.delete_role uses application.base.interface.request, so a change to application.base.interface.request can break application.cqrs.role.commands.delete_role, while a change to application.cqrs.role.commands.delete_role can't break application.base.interface.request.
- Position
- Below the diagonal: application.cqrs.role.commands.delete_role uses a module listed above it, which is the healthy direction.
31→7 application.cqrs.role.commands.delete_role uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.delete_role uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.role.commands.delete_role.DeleteRoleCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.role.commands.delete_role uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.role.commands.delete_role, while a change to application.cqrs.role.commands.delete_role can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.role.commands.delete_role uses a module listed above it, which is the healthy direction.
31→9 application.cqrs.role.commands.delete_role uses application.base.security.jwt_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.delete_role uses a type in application.base.security.jwt_manager.
- The types involved
src.application.cqrs.role.commands.delete_role.DeleteRoleCommandHandler→src.application.base.security.jwt_manager.BaseJWTManager
- Direction
- application.cqrs.role.commands.delete_role uses application.base.security.jwt_manager, so a change to application.base.security.jwt_manager can break application.cqrs.role.commands.delete_role, while a change to application.cqrs.role.commands.delete_role can't break application.base.security.jwt_manager.
- Position
- Below the diagonal: application.cqrs.role.commands.delete_role uses a module listed above it, which is the healthy direction.
31→23 application.cqrs.role.commands.delete_role uses application.services.rbac.rbac_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.delete_role uses a type in application.services.rbac.rbac_manager.
- The types involved
src.application.cqrs.role.commands.delete_role.DeleteRoleCommandHandler→src.application.services.rbac.rbac_manager.RBACManager
- Direction
- application.cqrs.role.commands.delete_role uses application.services.rbac.rbac_manager, so a change to application.services.rbac.rbac_manager can break application.cqrs.role.commands.delete_role, while a change to application.cqrs.role.commands.delete_role can't break application.services.rbac.rbac_manager.
- Position
- Below the diagonal: application.cqrs.role.commands.delete_role uses a module listed above it, which is the healthy direction.
31→26 application.cqrs.role.commands.delete_role uses application.services.security.security_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.delete_role uses a type in application.services.security.security_user.
- The types involved
src.application.cqrs.role.commands.delete_role.DeleteRoleCommandHandler→src.application.services.security.security_user.SecurityUser
- Direction
- application.cqrs.role.commands.delete_role uses application.services.security.security_user, so a change to application.services.security.security_user can break application.cqrs.role.commands.delete_role, while a change to application.cqrs.role.commands.delete_role can't break application.services.security.security_user.
- Position
- Below the diagonal: application.cqrs.role.commands.delete_role uses a module listed above it, which is the healthy direction.
32→1 application.cqrs.role.commands.remove_role_permissions uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_role_permissions uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.role.commands.remove_role_permissions.RemoveRolePermissionsCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.role.commands.remove_role_permissions uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.role.commands.remove_role_permissions, while a change to application.cqrs.role.commands.remove_role_permissions can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_role_permissions uses a module listed above it, which is the healthy direction.
32→2 application.cqrs.role.commands.remove_role_permissions uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_role_permissions uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.role.commands.remove_role_permissions.RemoveRolePermissionsCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.role.commands.remove_role_permissions uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.role.commands.remove_role_permissions, while a change to application.cqrs.role.commands.remove_role_permissions can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_role_permissions uses a module listed above it, which is the healthy direction.
32→3 application.cqrs.role.commands.remove_role_permissions uses application.base.interface.request✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_role_permissions uses a type in application.base.interface.request.
- The types involved
src.application.cqrs.role.commands.remove_role_permissions.RemoveRolePermissionsCommand→src.application.base.interface.request.RequestProtocol
- Direction
- application.cqrs.role.commands.remove_role_permissions uses application.base.interface.request, so a change to application.base.interface.request can break application.cqrs.role.commands.remove_role_permissions, while a change to application.cqrs.role.commands.remove_role_permissions can't break application.base.interface.request.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_role_permissions uses a module listed above it, which is the healthy direction.
32→7 application.cqrs.role.commands.remove_role_permissions uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_role_permissions uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.role.commands.remove_role_permissions.RemoveRolePermissionsCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.role.commands.remove_role_permissions uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.role.commands.remove_role_permissions, while a change to application.cqrs.role.commands.remove_role_permissions can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_role_permissions uses a module listed above it, which is the healthy direction.
32→9 application.cqrs.role.commands.remove_role_permissions uses application.base.security.jwt_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_role_permissions uses a type in application.base.security.jwt_manager.
- The types involved
src.application.cqrs.role.commands.remove_role_permissions.RemoveRolePermissionsCommandHandler→src.application.base.security.jwt_manager.BaseJWTManager
- Direction
- application.cqrs.role.commands.remove_role_permissions uses application.base.security.jwt_manager, so a change to application.base.security.jwt_manager can break application.cqrs.role.commands.remove_role_permissions, while a change to application.cqrs.role.commands.remove_role_permissions can't break application.base.security.jwt_manager.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_role_permissions uses a module listed above it, which is the healthy direction.
32→11 application.cqrs.role.commands.remove_role_permissions uses domain.role.entity.role✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_role_permissions uses a type in domain.role.entity.role.
- The types involved
src.application.cqrs.role.commands.remove_role_permissions.RemoveRolePermissionsCommandHandler→src.domain.role.entity.role.Role
- Direction
- application.cqrs.role.commands.remove_role_permissions uses domain.role.entity.role, so a change to domain.role.entity.role can break application.cqrs.role.commands.remove_role_permissions, while a change to application.cqrs.role.commands.remove_role_permissions can't break domain.role.entity.role.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_role_permissions uses a module listed above it, which is the healthy direction.
32→23 application.cqrs.role.commands.remove_role_permissions uses application.services.rbac.rbac_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_role_permissions uses a type in application.services.rbac.rbac_manager.
- The types involved
src.application.cqrs.role.commands.remove_role_permissions.RemoveRolePermissionsCommandHandler→src.application.services.rbac.rbac_manager.RBACManager
- Direction
- application.cqrs.role.commands.remove_role_permissions uses application.services.rbac.rbac_manager, so a change to application.services.rbac.rbac_manager can break application.cqrs.role.commands.remove_role_permissions, while a change to application.cqrs.role.commands.remove_role_permissions can't break application.services.rbac.rbac_manager.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_role_permissions uses a module listed above it, which is the healthy direction.
32→26 application.cqrs.role.commands.remove_role_permissions uses application.services.security.security_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_role_permissions uses a type in application.services.security.security_user.
- The types involved
src.application.cqrs.role.commands.remove_role_permissions.RemoveRolePermissionsCommandHandler→src.application.services.security.security_user.SecurityUser
- Direction
- application.cqrs.role.commands.remove_role_permissions uses application.services.security.security_user, so a change to application.services.security.security_user can break application.cqrs.role.commands.remove_role_permissions, while a change to application.cqrs.role.commands.remove_role_permissions can't break application.services.security.security_user.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_role_permissions uses a module listed above it, which is the healthy direction.
33→1 application.cqrs.role.commands.remove_user_role uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_user_role uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.role.commands.remove_user_role.RemoveRoleCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.role.commands.remove_user_role uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.role.commands.remove_user_role, while a change to application.cqrs.role.commands.remove_user_role can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_user_role uses a module listed above it, which is the healthy direction.
33→2 application.cqrs.role.commands.remove_user_role uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_user_role uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.role.commands.remove_user_role.RemoveRoleCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.role.commands.remove_user_role uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.role.commands.remove_user_role, while a change to application.cqrs.role.commands.remove_user_role can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_user_role uses a module listed above it, which is the healthy direction.
33→3 application.cqrs.role.commands.remove_user_role uses application.base.interface.request✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_user_role uses a type in application.base.interface.request.
- The types involved
src.application.cqrs.role.commands.remove_user_role.RemoveRoleCommand→src.application.base.interface.request.RequestProtocol
- Direction
- application.cqrs.role.commands.remove_user_role uses application.base.interface.request, so a change to application.base.interface.request can break application.cqrs.role.commands.remove_user_role, while a change to application.cqrs.role.commands.remove_user_role can't break application.base.interface.request.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_user_role uses a module listed above it, which is the healthy direction.
33→7 application.cqrs.role.commands.remove_user_role uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_user_role uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.role.commands.remove_user_role.RemoveRoleCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.role.commands.remove_user_role uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.role.commands.remove_user_role, while a change to application.cqrs.role.commands.remove_user_role can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_user_role uses a module listed above it, which is the healthy direction.
33→8 application.cqrs.role.commands.remove_user_role uses infrastructure.repositories.token.redis_repo✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_user_role uses a type in infrastructure.repositories.token.redis_repo.
- The types involved
src.application.cqrs.role.commands.remove_user_role.RemoveRoleCommandHandler→src.infrastructure.repositories.token.redis_repo.TokenBlackListRepository
- Direction
- application.cqrs.role.commands.remove_user_role uses infrastructure.repositories.token.redis_repo, so a change to infrastructure.repositories.token.redis_repo can break application.cqrs.role.commands.remove_user_role, while a change to application.cqrs.role.commands.remove_user_role can't break infrastructure.repositories.token.redis_repo.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_user_role uses a module listed above it, which is the healthy direction.
33→9 application.cqrs.role.commands.remove_user_role uses application.base.security.jwt_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_user_role uses a type in application.base.security.jwt_manager.
- The types involved
src.application.cqrs.role.commands.remove_user_role.RemoveRoleCommandHandler→src.application.base.security.jwt_manager.BaseJWTManager
- Direction
- application.cqrs.role.commands.remove_user_role uses application.base.security.jwt_manager, so a change to application.base.security.jwt_manager can break application.cqrs.role.commands.remove_user_role, while a change to application.cqrs.role.commands.remove_user_role can't break application.base.security.jwt_manager.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_user_role uses a module listed above it, which is the healthy direction.
33→13 application.cqrs.role.commands.remove_user_role uses domain.user.entity.user✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_user_role uses a type in domain.user.entity.user.
- The types involved
src.application.cqrs.role.commands.remove_user_role.RemoveRoleCommandHandler→src.domain.user.entity.user.User
- Direction
- application.cqrs.role.commands.remove_user_role uses domain.user.entity.user, so a change to domain.user.entity.user can break application.cqrs.role.commands.remove_user_role, while a change to application.cqrs.role.commands.remove_user_role can't break domain.user.entity.user.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_user_role uses a module listed above it, which is the healthy direction.
33→17 application.cqrs.role.commands.remove_user_role uses infrastructure.base.repository.user_reader✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_user_role uses a type in infrastructure.base.repository.user_reader.
- The types involved
src.application.cqrs.role.commands.remove_user_role.RemoveRoleCommandHandler→src.infrastructure.base.repository.user_reader.BaseUserReader
- Direction
- application.cqrs.role.commands.remove_user_role uses infrastructure.base.repository.user_reader, so a change to infrastructure.base.repository.user_reader can break application.cqrs.role.commands.remove_user_role, while a change to application.cqrs.role.commands.remove_user_role can't break infrastructure.base.repository.user_reader.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_user_role uses a module listed above it, which is the healthy direction.
33→23 application.cqrs.role.commands.remove_user_role uses application.services.rbac.rbac_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_user_role uses a type in application.services.rbac.rbac_manager.
- The types involved
src.application.cqrs.role.commands.remove_user_role.RemoveRoleCommandHandler→src.application.services.rbac.rbac_manager.RBACManager
- Direction
- application.cqrs.role.commands.remove_user_role uses application.services.rbac.rbac_manager, so a change to application.services.rbac.rbac_manager can break application.cqrs.role.commands.remove_user_role, while a change to application.cqrs.role.commands.remove_user_role can't break application.services.rbac.rbac_manager.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_user_role uses a module listed above it, which is the healthy direction.
33→26 application.cqrs.role.commands.remove_user_role uses application.services.security.security_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.remove_user_role uses a type in application.services.security.security_user.
- The types involved
src.application.cqrs.role.commands.remove_user_role.RemoveRoleCommandHandler→src.application.services.security.security_user.SecurityUser
- Direction
- application.cqrs.role.commands.remove_user_role uses application.services.security.security_user, so a change to application.services.security.security_user can break application.cqrs.role.commands.remove_user_role, while a change to application.cqrs.role.commands.remove_user_role can't break application.services.security.security_user.
- Position
- Below the diagonal: application.cqrs.role.commands.remove_user_role uses a module listed above it, which is the healthy direction.
34→1 application.cqrs.role.commands.update_role_description uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_description uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.role.commands.update_role_description.UpdateRoleDescriptionCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.role.commands.update_role_description uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.role.commands.update_role_description, while a change to application.cqrs.role.commands.update_role_description can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_description uses a module listed above it, which is the healthy direction.
34→2 application.cqrs.role.commands.update_role_description uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_description uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.role.commands.update_role_description.UpdateRoleDescriptionCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.role.commands.update_role_description uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.role.commands.update_role_description, while a change to application.cqrs.role.commands.update_role_description can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_description uses a module listed above it, which is the healthy direction.
34→3 application.cqrs.role.commands.update_role_description uses application.base.interface.request✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_description uses a type in application.base.interface.request.
- The types involved
src.application.cqrs.role.commands.update_role_description.UpdateRoleDescriptionCommand→src.application.base.interface.request.RequestProtocol
- Direction
- application.cqrs.role.commands.update_role_description uses application.base.interface.request, so a change to application.base.interface.request can break application.cqrs.role.commands.update_role_description, while a change to application.cqrs.role.commands.update_role_description can't break application.base.interface.request.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_description uses a module listed above it, which is the healthy direction.
34→7 application.cqrs.role.commands.update_role_description uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_description uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.role.commands.update_role_description.UpdateRoleDescriptionCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.role.commands.update_role_description uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.role.commands.update_role_description, while a change to application.cqrs.role.commands.update_role_description can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_description uses a module listed above it, which is the healthy direction.
34→9 application.cqrs.role.commands.update_role_description uses application.base.security.jwt_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_description uses a type in application.base.security.jwt_manager.
- The types involved
src.application.cqrs.role.commands.update_role_description.UpdateRoleDescriptionCommandHandler→src.application.base.security.jwt_manager.BaseJWTManager
- Direction
- application.cqrs.role.commands.update_role_description uses application.base.security.jwt_manager, so a change to application.base.security.jwt_manager can break application.cqrs.role.commands.update_role_description, while a change to application.cqrs.role.commands.update_role_description can't break application.base.security.jwt_manager.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_description uses a module listed above it, which is the healthy direction.
34→11 application.cqrs.role.commands.update_role_description uses domain.role.entity.role✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_description uses a type in domain.role.entity.role.
- The types involved
src.application.cqrs.role.commands.update_role_description.UpdateRoleDescriptionCommandHandler→src.domain.role.entity.role.Role
- Direction
- application.cqrs.role.commands.update_role_description uses domain.role.entity.role, so a change to domain.role.entity.role can break application.cqrs.role.commands.update_role_description, while a change to application.cqrs.role.commands.update_role_description can't break domain.role.entity.role.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_description uses a module listed above it, which is the healthy direction.
34→23 application.cqrs.role.commands.update_role_description uses application.services.rbac.rbac_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_description uses a type in application.services.rbac.rbac_manager.
- The types involved
src.application.cqrs.role.commands.update_role_description.UpdateRoleDescriptionCommandHandler→src.application.services.rbac.rbac_manager.RBACManager
- Direction
- application.cqrs.role.commands.update_role_description uses application.services.rbac.rbac_manager, so a change to application.services.rbac.rbac_manager can break application.cqrs.role.commands.update_role_description, while a change to application.cqrs.role.commands.update_role_description can't break application.services.rbac.rbac_manager.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_description uses a module listed above it, which is the healthy direction.
34→26 application.cqrs.role.commands.update_role_description uses application.services.security.security_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_description uses a type in application.services.security.security_user.
- The types involved
src.application.cqrs.role.commands.update_role_description.UpdateRoleDescriptionCommandHandler→src.application.services.security.security_user.SecurityUser
- Direction
- application.cqrs.role.commands.update_role_description uses application.services.security.security_user, so a change to application.services.security.security_user can break application.cqrs.role.commands.update_role_description, while a change to application.cqrs.role.commands.update_role_description can't break application.services.security.security_user.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_description uses a module listed above it, which is the healthy direction.
35→1 application.cqrs.role.commands.update_role_permissions uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_permissions uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.role.commands.update_role_permissions.UpdateRolePermissionsCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.role.commands.update_role_permissions uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.role.commands.update_role_permissions, while a change to application.cqrs.role.commands.update_role_permissions can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_permissions uses a module listed above it, which is the healthy direction.
35→2 application.cqrs.role.commands.update_role_permissions uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_permissions uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.role.commands.update_role_permissions.UpdateRolePermissionsCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.role.commands.update_role_permissions uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.role.commands.update_role_permissions, while a change to application.cqrs.role.commands.update_role_permissions can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_permissions uses a module listed above it, which is the healthy direction.
35→3 application.cqrs.role.commands.update_role_permissions uses application.base.interface.request✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_permissions uses a type in application.base.interface.request.
- The types involved
src.application.cqrs.role.commands.update_role_permissions.UpdateRolePermissionsCommand→src.application.base.interface.request.RequestProtocol
- Direction
- application.cqrs.role.commands.update_role_permissions uses application.base.interface.request, so a change to application.base.interface.request can break application.cqrs.role.commands.update_role_permissions, while a change to application.cqrs.role.commands.update_role_permissions can't break application.base.interface.request.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_permissions uses a module listed above it, which is the healthy direction.
35→7 application.cqrs.role.commands.update_role_permissions uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_permissions uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.role.commands.update_role_permissions.UpdateRolePermissionsCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.role.commands.update_role_permissions uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.role.commands.update_role_permissions, while a change to application.cqrs.role.commands.update_role_permissions can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_permissions uses a module listed above it, which is the healthy direction.
35→9 application.cqrs.role.commands.update_role_permissions uses application.base.security.jwt_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_permissions uses a type in application.base.security.jwt_manager.
- The types involved
src.application.cqrs.role.commands.update_role_permissions.UpdateRolePermissionsCommandHandler→src.application.base.security.jwt_manager.BaseJWTManager
- Direction
- application.cqrs.role.commands.update_role_permissions uses application.base.security.jwt_manager, so a change to application.base.security.jwt_manager can break application.cqrs.role.commands.update_role_permissions, while a change to application.cqrs.role.commands.update_role_permissions can't break application.base.security.jwt_manager.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_permissions uses a module listed above it, which is the healthy direction.
35→11 application.cqrs.role.commands.update_role_permissions uses domain.role.entity.role✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_permissions uses a type in domain.role.entity.role.
- The types involved
src.application.cqrs.role.commands.update_role_permissions.UpdateRolePermissionsCommandHandler→src.domain.role.entity.role.Role
- Direction
- application.cqrs.role.commands.update_role_permissions uses domain.role.entity.role, so a change to domain.role.entity.role can break application.cqrs.role.commands.update_role_permissions, while a change to application.cqrs.role.commands.update_role_permissions can't break domain.role.entity.role.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_permissions uses a module listed above it, which is the healthy direction.
35→23 application.cqrs.role.commands.update_role_permissions uses application.services.rbac.rbac_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_permissions uses a type in application.services.rbac.rbac_manager.
- The types involved
src.application.cqrs.role.commands.update_role_permissions.UpdateRolePermissionsCommandHandler→src.application.services.rbac.rbac_manager.RBACManager
- Direction
- application.cqrs.role.commands.update_role_permissions uses application.services.rbac.rbac_manager, so a change to application.services.rbac.rbac_manager can break application.cqrs.role.commands.update_role_permissions, while a change to application.cqrs.role.commands.update_role_permissions can't break application.services.rbac.rbac_manager.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_permissions uses a module listed above it, which is the healthy direction.
35→26 application.cqrs.role.commands.update_role_permissions uses application.services.security.security_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_permissions uses a type in application.services.security.security_user.
- The types involved
src.application.cqrs.role.commands.update_role_permissions.UpdateRolePermissionsCommandHandler→src.application.services.security.security_user.SecurityUser
- Direction
- application.cqrs.role.commands.update_role_permissions uses application.services.security.security_user, so a change to application.services.security.security_user can break application.cqrs.role.commands.update_role_permissions, while a change to application.cqrs.role.commands.update_role_permissions can't break application.services.security.security_user.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_permissions uses a module listed above it, which is the healthy direction.
36→1 application.cqrs.role.commands.update_role_security_lvl uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_security_lvl uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.role.commands.update_role_security_lvl.UpdateRoleSecurityLvlCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.role.commands.update_role_security_lvl uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.role.commands.update_role_security_lvl, while a change to application.cqrs.role.commands.update_role_security_lvl can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_security_lvl uses a module listed above it, which is the healthy direction.
36→2 application.cqrs.role.commands.update_role_security_lvl uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_security_lvl uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.role.commands.update_role_security_lvl.UpdateRoleSecurityLvlCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.role.commands.update_role_security_lvl uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.role.commands.update_role_security_lvl, while a change to application.cqrs.role.commands.update_role_security_lvl can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_security_lvl uses a module listed above it, which is the healthy direction.
36→3 application.cqrs.role.commands.update_role_security_lvl uses application.base.interface.request✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_security_lvl uses a type in application.base.interface.request.
- The types involved
src.application.cqrs.role.commands.update_role_security_lvl.UpdateRoleSecurityLvlCommand→src.application.base.interface.request.RequestProtocol
- Direction
- application.cqrs.role.commands.update_role_security_lvl uses application.base.interface.request, so a change to application.base.interface.request can break application.cqrs.role.commands.update_role_security_lvl, while a change to application.cqrs.role.commands.update_role_security_lvl can't break application.base.interface.request.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_security_lvl uses a module listed above it, which is the healthy direction.
36→7 application.cqrs.role.commands.update_role_security_lvl uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_security_lvl uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.role.commands.update_role_security_lvl.UpdateRoleSecurityLvlCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.role.commands.update_role_security_lvl uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.role.commands.update_role_security_lvl, while a change to application.cqrs.role.commands.update_role_security_lvl can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_security_lvl uses a module listed above it, which is the healthy direction.
36→9 application.cqrs.role.commands.update_role_security_lvl uses application.base.security.jwt_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_security_lvl uses a type in application.base.security.jwt_manager.
- The types involved
src.application.cqrs.role.commands.update_role_security_lvl.UpdateRoleSecurityLvlCommandHandler→src.application.base.security.jwt_manager.BaseJWTManager
- Direction
- application.cqrs.role.commands.update_role_security_lvl uses application.base.security.jwt_manager, so a change to application.base.security.jwt_manager can break application.cqrs.role.commands.update_role_security_lvl, while a change to application.cqrs.role.commands.update_role_security_lvl can't break application.base.security.jwt_manager.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_security_lvl uses a module listed above it, which is the healthy direction.
36→11 application.cqrs.role.commands.update_role_security_lvl uses domain.role.entity.role✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_security_lvl uses a type in domain.role.entity.role.
- The types involved
src.application.cqrs.role.commands.update_role_security_lvl.UpdateRoleSecurityLvlCommandHandler→src.domain.role.entity.role.Role
- Direction
- application.cqrs.role.commands.update_role_security_lvl uses domain.role.entity.role, so a change to domain.role.entity.role can break application.cqrs.role.commands.update_role_security_lvl, while a change to application.cqrs.role.commands.update_role_security_lvl can't break domain.role.entity.role.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_security_lvl uses a module listed above it, which is the healthy direction.
36→23 application.cqrs.role.commands.update_role_security_lvl uses application.services.rbac.rbac_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_security_lvl uses a type in application.services.rbac.rbac_manager.
- The types involved
src.application.cqrs.role.commands.update_role_security_lvl.UpdateRoleSecurityLvlCommandHandler→src.application.services.rbac.rbac_manager.RBACManager
- Direction
- application.cqrs.role.commands.update_role_security_lvl uses application.services.rbac.rbac_manager, so a change to application.services.rbac.rbac_manager can break application.cqrs.role.commands.update_role_security_lvl, while a change to application.cqrs.role.commands.update_role_security_lvl can't break application.services.rbac.rbac_manager.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_security_lvl uses a module listed above it, which is the healthy direction.
36→26 application.cqrs.role.commands.update_role_security_lvl uses application.services.security.security_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.role.commands.update_role_security_lvl uses a type in application.services.security.security_user.
- The types involved
src.application.cqrs.role.commands.update_role_security_lvl.UpdateRoleSecurityLvlCommandHandler→src.application.services.security.security_user.SecurityUser
- Direction
- application.cqrs.role.commands.update_role_security_lvl uses application.services.security.security_user, so a change to application.services.security.security_user can break application.cqrs.role.commands.update_role_security_lvl, while a change to application.cqrs.role.commands.update_role_security_lvl can't break application.services.security.security_user.
- Position
- Below the diagonal: application.cqrs.role.commands.update_role_security_lvl uses a module listed above it, which is the healthy direction.
37→1 application.cqrs.user.commands.add_oauth_account_request uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.add_oauth_account_request uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.user.commands.add_oauth_account_request.AddOAuthAccountRequestCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.user.commands.add_oauth_account_request uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.user.commands.add_oauth_account_request, while a change to application.cqrs.user.commands.add_oauth_account_request can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.user.commands.add_oauth_account_request uses a module listed above it, which is the healthy direction.
37→2 application.cqrs.user.commands.add_oauth_account_request uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.add_oauth_account_request uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.user.commands.add_oauth_account_request.AddOAuthAccountRequestCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.user.commands.add_oauth_account_request uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.user.commands.add_oauth_account_request, while a change to application.cqrs.user.commands.add_oauth_account_request can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.user.commands.add_oauth_account_request uses a module listed above it, which is the healthy direction.
37→3 application.cqrs.user.commands.add_oauth_account_request uses application.base.interface.request✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.add_oauth_account_request uses a type in application.base.interface.request.
- The types involved
src.application.cqrs.user.commands.add_oauth_account_request.AddOAuthAccountRequestCommand→src.application.base.interface.request.RequestProtocol
- Direction
- application.cqrs.user.commands.add_oauth_account_request uses application.base.interface.request, so a change to application.base.interface.request can break application.cqrs.user.commands.add_oauth_account_request, while a change to application.cqrs.user.commands.add_oauth_account_request can't break application.base.interface.request.
- Position
- Below the diagonal: application.cqrs.user.commands.add_oauth_account_request uses a module listed above it, which is the healthy direction.
37→8 application.cqrs.user.commands.add_oauth_account_request uses infrastructure.repositories.token.redis_repo✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.add_oauth_account_request uses a type in infrastructure.repositories.token.redis_repo.
- The types involved
src.application.cqrs.user.commands.add_oauth_account_request.AddOAuthAccountRequestCommandHandler→src.infrastructure.repositories.token.redis_repo.TokenBlackListRepository
- Direction
- application.cqrs.user.commands.add_oauth_account_request uses infrastructure.repositories.token.redis_repo, so a change to infrastructure.repositories.token.redis_repo can break application.cqrs.user.commands.add_oauth_account_request, while a change to application.cqrs.user.commands.add_oauth_account_request can't break infrastructure.repositories.token.redis_repo.
- Position
- Below the diagonal: application.cqrs.user.commands.add_oauth_account_request uses a module listed above it, which is the healthy direction.
37→9 application.cqrs.user.commands.add_oauth_account_request uses application.base.security.jwt_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.add_oauth_account_request uses a type in application.base.security.jwt_manager.
- The types involved
src.application.cqrs.user.commands.add_oauth_account_request.AddOAuthAccountRequestCommandHandler→src.application.base.security.jwt_manager.BaseJWTManager
- Direction
- application.cqrs.user.commands.add_oauth_account_request uses application.base.security.jwt_manager, so a change to application.base.security.jwt_manager can break application.cqrs.user.commands.add_oauth_account_request, while a change to application.cqrs.user.commands.add_oauth_account_request can't break application.base.security.jwt_manager.
- Position
- Below the diagonal: application.cqrs.user.commands.add_oauth_account_request uses a module listed above it, which is the healthy direction.
37→25 application.cqrs.user.commands.add_oauth_account_request uses application.services.security.oauth_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.add_oauth_account_request uses a type in application.services.security.oauth_manager.
- The types involved
src.application.cqrs.user.commands.add_oauth_account_request.AddOAuthAccountRequestCommandHandler→src.application.services.security.oauth_manager.OAuthManager
- Direction
- application.cqrs.user.commands.add_oauth_account_request uses application.services.security.oauth_manager, so a change to application.services.security.oauth_manager can break application.cqrs.user.commands.add_oauth_account_request, while a change to application.cqrs.user.commands.add_oauth_account_request can't break application.services.security.oauth_manager.
- Position
- Below the diagonal: application.cqrs.user.commands.add_oauth_account_request uses a module listed above it, which is the healthy direction.
37→26 application.cqrs.user.commands.add_oauth_account_request uses application.services.security.security_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.add_oauth_account_request uses a type in application.services.security.security_user.
- The types involved
src.application.cqrs.user.commands.add_oauth_account_request.AddOAuthAccountRequestCommandHandler→src.application.services.security.security_user.SecurityUser
- Direction
- application.cqrs.user.commands.add_oauth_account_request uses application.services.security.security_user, so a change to application.services.security.security_user can break application.cqrs.user.commands.add_oauth_account_request, while a change to application.cqrs.user.commands.add_oauth_account_request can't break application.services.security.security_user.
- Position
- Below the diagonal: application.cqrs.user.commands.add_oauth_account_request uses a module listed above it, which is the healthy direction.
38→1 application.cqrs.user.commands.add_oauth_account_to_current_user uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.add_oauth_account_to_current_user uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.user.commands.add_oauth_account_to_current_user.AddOAuthAccountToCurrentUserCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.user.commands.add_oauth_account_to_current_user uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.user.commands.add_oauth_account_to_current_user, while a change to application.cqrs.user.commands.add_oauth_account_to_current_user can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.user.commands.add_oauth_account_to_current_user uses a module listed above it, which is the healthy direction.
38→2 application.cqrs.user.commands.add_oauth_account_to_current_user uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.add_oauth_account_to_current_user uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.user.commands.add_oauth_account_to_current_user.AddOAuthAccountToCurrentUserCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.user.commands.add_oauth_account_to_current_user uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.user.commands.add_oauth_account_to_current_user, while a change to application.cqrs.user.commands.add_oauth_account_to_current_user can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.user.commands.add_oauth_account_to_current_user uses a module listed above it, which is the healthy direction.
38→7 application.cqrs.user.commands.add_oauth_account_to_current_user uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.add_oauth_account_to_current_user uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.user.commands.add_oauth_account_to_current_user.AddOAuthAccountToCurrentUserCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.user.commands.add_oauth_account_to_current_user uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.user.commands.add_oauth_account_to_current_user, while a change to application.cqrs.user.commands.add_oauth_account_to_current_user can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.user.commands.add_oauth_account_to_current_user uses a module listed above it, which is the healthy direction.
38→8 application.cqrs.user.commands.add_oauth_account_to_current_user uses infrastructure.repositories.token.redis_repo✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.add_oauth_account_to_current_user uses a type in infrastructure.repositories.token.redis_repo.
- The types involved
src.application.cqrs.user.commands.add_oauth_account_to_current_user.AddOAuthAccountToCurrentUserCommandHandler→src.infrastructure.repositories.token.redis_repo.TokenBlackListRepository
- Direction
- application.cqrs.user.commands.add_oauth_account_to_current_user uses infrastructure.repositories.token.redis_repo, so a change to infrastructure.repositories.token.redis_repo can break application.cqrs.user.commands.add_oauth_account_to_current_user, while a change to application.cqrs.user.commands.add_oauth_account_to_current_user can't break infrastructure.repositories.token.redis_repo.
- Position
- Below the diagonal: application.cqrs.user.commands.add_oauth_account_to_current_user uses a module listed above it, which is the healthy direction.
38→10 application.cqrs.user.commands.add_oauth_account_to_current_user uses application.base.session.session_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.add_oauth_account_to_current_user uses a type in application.base.session.session_manager.
- The types involved
src.application.cqrs.user.commands.add_oauth_account_to_current_user.AddOAuthAccountToCurrentUserCommandHandler→src.application.base.session.session_manager.BaseSessionManager
- Direction
- application.cqrs.user.commands.add_oauth_account_to_current_user uses application.base.session.session_manager, so a change to application.base.session.session_manager can break application.cqrs.user.commands.add_oauth_account_to_current_user, while a change to application.cqrs.user.commands.add_oauth_account_to_current_user can't break application.base.session.session_manager.
- Position
- Below the diagonal: application.cqrs.user.commands.add_oauth_account_to_current_user uses a module listed above it, which is the healthy direction.
38→17 application.cqrs.user.commands.add_oauth_account_to_current_user uses infrastructure.base.repository.user_reader✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.add_oauth_account_to_current_user uses a type in infrastructure.base.repository.user_reader.
- The types involved
src.application.cqrs.user.commands.add_oauth_account_to_current_user.AddOAuthAccountToCurrentUserCommandHandler→src.infrastructure.base.repository.user_reader.BaseUserReader
- Direction
- application.cqrs.user.commands.add_oauth_account_to_current_user uses infrastructure.base.repository.user_reader, so a change to infrastructure.base.repository.user_reader can break application.cqrs.user.commands.add_oauth_account_to_current_user, while a change to application.cqrs.user.commands.add_oauth_account_to_current_user can't break infrastructure.base.repository.user_reader.
- Position
- Below the diagonal: application.cqrs.user.commands.add_oauth_account_to_current_user uses a module listed above it, which is the healthy direction.
38→25 application.cqrs.user.commands.add_oauth_account_to_current_user uses application.services.security.oauth_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.add_oauth_account_to_current_user uses a type in application.services.security.oauth_manager.
- The types involved
src.application.cqrs.user.commands.add_oauth_account_to_current_user.AddOAuthAccountToCurrentUserCommandHandler→src.application.services.security.oauth_manager.OAuthManager
- Direction
- application.cqrs.user.commands.add_oauth_account_to_current_user uses application.services.security.oauth_manager, so a change to application.services.security.oauth_manager can break application.cqrs.user.commands.add_oauth_account_to_current_user, while a change to application.cqrs.user.commands.add_oauth_account_to_current_user can't break application.services.security.oauth_manager.
- Position
- Below the diagonal: application.cqrs.user.commands.add_oauth_account_to_current_user uses a module listed above it, which is the healthy direction.
39→1 application.cqrs.user.commands.deactivate_oauth_account uses application.base.commands.base✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.deactivate_oauth_account uses a type in application.base.commands.base.
- The types involved
src.application.cqrs.user.commands.deactivate_oauth_account.DeactivateUsersOAuthAccountCommand→src.application.base.commands.base.BaseCommand
- Direction
- application.cqrs.user.commands.deactivate_oauth_account uses application.base.commands.base, so a change to application.base.commands.base can break application.cqrs.user.commands.deactivate_oauth_account, while a change to application.cqrs.user.commands.deactivate_oauth_account can't break application.base.commands.base.
- Position
- Below the diagonal: application.cqrs.user.commands.deactivate_oauth_account uses a module listed above it, which is the healthy direction.
39→2 application.cqrs.user.commands.deactivate_oauth_account uses application.base.commands.command_handler✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.deactivate_oauth_account uses a type in application.base.commands.command_handler.
- The types involved
src.application.cqrs.user.commands.deactivate_oauth_account.DeactivateUsersOAuthAccountCommandHandler→src.application.base.commands.command_handler.CommandHandler
- Direction
- application.cqrs.user.commands.deactivate_oauth_account uses application.base.commands.command_handler, so a change to application.base.commands.command_handler can break application.cqrs.user.commands.deactivate_oauth_account, while a change to application.cqrs.user.commands.deactivate_oauth_account can't break application.base.commands.command_handler.
- Position
- Below the diagonal: application.cqrs.user.commands.deactivate_oauth_account uses a module listed above it, which is the healthy direction.
39→3 application.cqrs.user.commands.deactivate_oauth_account uses application.base.interface.request✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.deactivate_oauth_account uses a type in application.base.interface.request.
- The types involved
src.application.cqrs.user.commands.deactivate_oauth_account.DeactivateUsersOAuthAccountCommand→src.application.base.interface.request.RequestProtocol
- Direction
- application.cqrs.user.commands.deactivate_oauth_account uses application.base.interface.request, so a change to application.base.interface.request can break application.cqrs.user.commands.deactivate_oauth_account, while a change to application.cqrs.user.commands.deactivate_oauth_account can't break application.base.interface.request.
- Position
- Below the diagonal: application.cqrs.user.commands.deactivate_oauth_account uses a module listed above it, which is the healthy direction.
39→7 application.cqrs.user.commands.deactivate_oauth_account uses infrastructure.base.uow✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.deactivate_oauth_account uses a type in infrastructure.base.uow.
- The types involved
src.application.cqrs.user.commands.deactivate_oauth_account.DeactivateUsersOAuthAccountCommandHandler→src.infrastructure.base.uow.UnitOfWork
- Direction
- application.cqrs.user.commands.deactivate_oauth_account uses infrastructure.base.uow, so a change to infrastructure.base.uow can break application.cqrs.user.commands.deactivate_oauth_account, while a change to application.cqrs.user.commands.deactivate_oauth_account can't break infrastructure.base.uow.
- Position
- Below the diagonal: application.cqrs.user.commands.deactivate_oauth_account uses a module listed above it, which is the healthy direction.
39→9 application.cqrs.user.commands.deactivate_oauth_account uses application.base.security.jwt_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.deactivate_oauth_account uses a type in application.base.security.jwt_manager.
- The types involved
src.application.cqrs.user.commands.deactivate_oauth_account.DeactivateUsersOAuthAccountCommandHandler→src.application.base.security.jwt_manager.BaseJWTManager
- Direction
- application.cqrs.user.commands.deactivate_oauth_account uses application.base.security.jwt_manager, so a change to application.base.security.jwt_manager can break application.cqrs.user.commands.deactivate_oauth_account, while a change to application.cqrs.user.commands.deactivate_oauth_account can't break application.base.security.jwt_manager.
- Position
- Below the diagonal: application.cqrs.user.commands.deactivate_oauth_account uses a module listed above it, which is the healthy direction.
39→25 application.cqrs.user.commands.deactivate_oauth_account uses application.services.security.oauth_manager✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.deactivate_oauth_account uses a type in application.services.security.oauth_manager.
- The types involved
src.application.cqrs.user.commands.deactivate_oauth_account.DeactivateUsersOAuthAccountCommandHandler→src.application.services.security.oauth_manager.OAuthManager
- Direction
- application.cqrs.user.commands.deactivate_oauth_account uses application.services.security.oauth_manager, so a change to application.services.security.oauth_manager can break application.cqrs.user.commands.deactivate_oauth_account, while a change to application.cqrs.user.commands.deactivate_oauth_account can't break application.services.security.oauth_manager.
- Position
- Below the diagonal: application.cqrs.user.commands.deactivate_oauth_account uses a module listed above it, which is the healthy direction.
39→26 application.cqrs.user.commands.deactivate_oauth_account uses application.services.security.security_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.user.commands.deactivate_oauth_account uses a type in application.services.security.security_user.
- The types involved
src.application.cqrs.user.commands.deactivate_oauth_account.DeactivateUsersOAuthAccountCommandHandler→src.application.services.security.security_user.SecurityUser
- Direction
- application.cqrs.user.commands.deactivate_oauth_account uses application.services.security.security_user, so a change to application.services.security.security_user can break application.cqrs.user.commands.deactivate_oauth_account, while a change to application.cqrs.user.commands.deactivate_oauth_account can't break application.services.security.security_user.
- Position
- Below the diagonal: application.cqrs.user.commands.deactivate_oauth_account uses a module listed above it, which is the healthy direction.
40→12 application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.logout_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.user.commands.logout_user.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.user.commands.logout_user.LogoutUserCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.logout_user, so a change to application.cqrs.user.commands.logout_user can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.user.commands.logout_user.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→15 application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.register_oauth_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.user.commands.register_oauth_user.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.user.commands.register_oauth_user.RegisterOAuthUserCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.register_oauth_user, so a change to application.cqrs.user.commands.register_oauth_user can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.user.commands.register_oauth_user.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→16 application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.register_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.user.commands.register_user.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.user.commands.register_user.RegisterUserCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.register_user, so a change to application.cqrs.user.commands.register_user can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.user.commands.register_user.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→19 application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.change_user_email✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.user.commands.change_user_email.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.user.commands.change_user_email.ChangeUserEmailCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.change_user_email, so a change to application.cqrs.user.commands.change_user_email can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.user.commands.change_user_email.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→20 application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.login_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.user.commands.login_user.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.user.commands.login_user.LoginUserCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.login_user, so a change to application.cqrs.user.commands.login_user can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.user.commands.login_user.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→21 application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.oauth_login_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.user.commands.oauth_login_user.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.user.commands.oauth_login_user.OAuthLoginUserCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.oauth_login_user, so a change to application.cqrs.user.commands.oauth_login_user can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.user.commands.oauth_login_user.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→22 application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.reset_user_password✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.user.commands.reset_user_password.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.user.commands.reset_user_password.ResetUserPasswordCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.reset_user_password, so a change to application.cqrs.user.commands.reset_user_password can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.user.commands.reset_user_password.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→27 application.cqrs.cqrs_di_setup uses application.cqrs.permission.commands.create_permission✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.permission.commands.create_permission.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.permission.commands.create_permission.CreatePermissionCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.permission.commands.create_permission, so a change to application.cqrs.permission.commands.create_permission can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.permission.commands.create_permission.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→28 application.cqrs.cqrs_di_setup uses application.cqrs.permission.commands.delete_permission✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.permission.commands.delete_permission.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.permission.commands.delete_permission.DeletePermissionCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.permission.commands.delete_permission, so a change to application.cqrs.permission.commands.delete_permission can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.permission.commands.delete_permission.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→29 application.cqrs.cqrs_di_setup uses application.cqrs.role.commands.assign_role_to_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.role.commands.assign_role_to_user.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.role.commands.assign_role_to_user.AssignRoleCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.role.commands.assign_role_to_user, so a change to application.cqrs.role.commands.assign_role_to_user can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.role.commands.assign_role_to_user.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→30 application.cqrs.cqrs_di_setup uses application.cqrs.role.commands.create_role✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.role.commands.create_role.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.role.commands.create_role.CreateRoleCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.role.commands.create_role, so a change to application.cqrs.role.commands.create_role can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.role.commands.create_role.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→31 application.cqrs.cqrs_di_setup uses application.cqrs.role.commands.delete_role✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.role.commands.delete_role.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.role.commands.delete_role.DeleteRoleCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.role.commands.delete_role, so a change to application.cqrs.role.commands.delete_role can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.role.commands.delete_role.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→32 application.cqrs.cqrs_di_setup uses application.cqrs.role.commands.remove_role_permissions✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.role.commands.remove_role_permissions.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.role.commands.remove_role_permissions.RemoveRolePermissionsCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.role.commands.remove_role_permissions, so a change to application.cqrs.role.commands.remove_role_permissions can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.role.commands.remove_role_permissions.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→33 application.cqrs.cqrs_di_setup uses application.cqrs.role.commands.remove_user_role✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.role.commands.remove_user_role.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.role.commands.remove_user_role.RemoveRoleCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.role.commands.remove_user_role, so a change to application.cqrs.role.commands.remove_user_role can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.role.commands.remove_user_role.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→34 application.cqrs.cqrs_di_setup uses application.cqrs.role.commands.update_role_description✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.role.commands.update_role_description.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.role.commands.update_role_description.UpdateRoleDescriptionCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.role.commands.update_role_description, so a change to application.cqrs.role.commands.update_role_description can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.role.commands.update_role_description.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→35 application.cqrs.cqrs_di_setup uses application.cqrs.role.commands.update_role_permissions✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.role.commands.update_role_permissions.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.role.commands.update_role_permissions.UpdateRolePermissionsCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.role.commands.update_role_permissions, so a change to application.cqrs.role.commands.update_role_permissions can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.role.commands.update_role_permissions.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→36 application.cqrs.cqrs_di_setup uses application.cqrs.role.commands.update_role_security_lvl✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.role.commands.update_role_security_lvl.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.role.commands.update_role_security_lvl.UpdateRoleSecurityLvlCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.role.commands.update_role_security_lvl, so a change to application.cqrs.role.commands.update_role_security_lvl can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.role.commands.update_role_security_lvl.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→37 application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.add_oauth_account_request✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.user.commands.add_oauth_account_request.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.user.commands.add_oauth_account_request.AddOAuthAccountRequestCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.add_oauth_account_request, so a change to application.cqrs.user.commands.add_oauth_account_request can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.user.commands.add_oauth_account_request.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→38 application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.add_oauth_account_to_current_user✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.user.commands.add_oauth_account_to_current_user.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.user.commands.add_oauth_account_to_current_user.AddOAuthAccountToCurrentUserCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.add_oauth_account_to_current_user, so a change to application.cqrs.user.commands.add_oauth_account_to_current_user can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.user.commands.add_oauth_account_to_current_user.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
40→39 application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.deactivate_oauth_account✕
- Connections
- 1 pair of types, where a type in application.cqrs.cqrs_di_setup uses a type in application.cqrs.user.commands.deactivate_oauth_account.
- The types involved
src.application.cqrs.cqrs_di_setup.MediatorConfigProvider→src.application.cqrs.user.commands.deactivate_oauth_account.DeactivateUsersOAuthAccountCommandHandler
- Direction
- application.cqrs.cqrs_di_setup uses application.cqrs.user.commands.deactivate_oauth_account, so a change to application.cqrs.user.commands.deactivate_oauth_account can break application.cqrs.cqrs_di_setup, while a change to application.cqrs.cqrs_di_setup can't break application.cqrs.user.commands.deactivate_oauth_account.
- Position
- Below the diagonal: application.cqrs.cqrs_di_setup uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 21 | High / Critical |
| A02:2025 — Security Misconfiguration | 7 | High / Critical |
| A05:2025 — Injection | 6 | Medium |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2); Add a CI workflow that builds and runs the test suite on every push/PR; Run what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). | +18.1 pts | Low | Secret Scanning |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +6.8 pts | Medium | CI/CD gates |
| Run what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — 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. | +6.8 pts | Medium | Security & performance tooling |
| Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters). | +2.8 pts | Medium | Encapsulated state |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +1.3 pts | Low | Project Cohesion |
| Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services. | +2.1 pts | Medium | Rich vs anemic model |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +2.0 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.0 pts | Medium | Release Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.3 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py | 7.1 | Mixed | Code Duplication: Duplicated block (18–20 lines × 2) |
| src/infrastructure/repositories/converters.py | 7.8 | Mixed | Code Duplication: Duplicated block (16 lines × 2) |
| src/application/cqrs/user/commands/register_oauth_user.py | 8.5 | Near-clean | Code Duplication: Duplicated block (18 lines × 2) |
| src/application/services/tasks/email_templates.py | 8.5 | Near-clean | Code Duplication: Duplicated block (14 lines × 2) |
| src/application/exceptions/oauth.py | 8.5 | Near-clean | Code Duplication: Duplicated block (19 lines × 2) |
| src/infrastructure/repositories/role/role_repo.py | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| REDACTED | 9.3 | Near-clean | Static Analysis (SAST): Low: REDACTED |
| REDACTED | 9.3 | Near-clean | Static Analysis (SAST): Low: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 66 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 66 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, 114 of 122 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.py) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) 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. You can widen what we reach: optional: produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) 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 — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.py) and this repository declares a Python test suite (repository root, 5 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's 5 shipped Python distribution(s) across 1 manifest(s) WERE read; what went unanswered is the currency half, because it grades an EXACT pin against the newest release and every declaration here is a floor or a range — which installs the newest release it admits and so cannot be behind one. So pypi.org was never asked. This is a true statement about the repository, and the healthy one, NOT a gap on our side: no reader we could write would find a currency question here.
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 22 commit(s), too few for a reliable trend signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- 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. Too few commits for a meaningful bus factor (22 commit(s) sampled, fewer than the 50 this dimension needs before a bus factor means anything).
- 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (pyproject.toml), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D23 Boundary Type-Coupling — 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 measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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 (22 commit(s) sampled).
- D35 Change Coupling — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 22 commit(s), too few for a reliable change-coupling signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is dishka, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — 24 | -------------------- ERROR: failed to solve: process "/bin/sh -c apt update -y && apt install -y python3-dev gcc musl-dev && pip install --upgrade pip && pip install --no-cache-dir -r requirements.dev.txt && apt-get clean && useradd -r celery_user && chown -R celery_user:celery_user /app" did not complete successfully: exit code: 100; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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.
- 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.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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.
- C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
12 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with 20250515-154426_a5a0703734e0_database_initialization.py (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (18–20 lines × 2) finding(s) in Code Duplication — start with 20250515-154426_a5a0703734e0_database_initialization.py. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (18–19 lines × 2) finding(s) in Code Duplication — start with 20250515-154426_a5a0703734e0_database_initialization.py. — 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.
D6 · Cohesion (LCOM4)
0 of 1 classes have LCOM4 above 3.
D9 · Test Distribution
40 test methods: 40 unit, 0 integration, 0 BDD, 0 e2e. The Python suite contributes 40 test function(s) across 4 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
D13 · Secret Scanning
2 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Stand up a CI pipeline, then gate Secret Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 38 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 5 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (33 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. 2 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: src/presentation/api/v1/auth/auth_router.py (8 of 10 changes were fixes); src/application/cqrs/cqrs_di_setup.py (7 of 12 changes were fixes); src/settings/config.py (7 of 10 changes were fixes)
What to do
- Resolve the 55 Repeated repair finding(s) in Churn × Complexity Hotspots — start with user.py (3), role.py (2), session_manager.py (2). — One of this dimension's main actionable groups (55 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 11393 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D23 · Boundary Type-Coupling
35 domain type(s) cross context boundaries across 2 contexts; they are measured and withheld (not published, not scored). Contexts: domain, infrastructure.
D26 · Project Cohesion
1 of 2 build units (Python) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
80 % of calls cross a namespace and 5 % go through an interface, but 65 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Improve Navigability — currently 8.4/10. — 80 % of calls cross a namespace and 5 % go through an interface, but 65 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
6 finding(s): 0 critical, 0 high, 4 medium, 2 low.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 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 recommendation-level).
D30 · Dependency Vulnerabilities
21 finding(s): 4 critical, 12 high, 5 medium, 0 low.
What to do
- Resolve the 11 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11). — One of this dimension's main actionable groups (11 issue-level).
- Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
7 finding(s): 0 critical, 1 high, 5 medium, 1 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 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.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 5 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
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).
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
- Name the access rules — DRF permission classes, django-guardian or django-rules permissions, a casbin or oso policy, or roles and permissions declared once — and consult them where access is checked (permission_classes, @permission_required, Depends), so the rule set is reviewable and testable on its own.
C3 · Audit Trail
- An audit mechanism is present, but the trail is not yet complete — missing: a write-side hook every change flows through (HistoricalRecords, auditlog.register, reversion.register, pghistory.track, SQLAlchemy-Continuum, a post_save / after_update listener recording each change, or an event-sourced store), per-model coverage (a change-history registration on each model that needs a who-changed-what trail, or an event-sourced aggregate).
What to do
- Back the audit convention with a structural mechanism: HistoricalRecords or auditlog.register on the models that need a who-changed-what trail, or a post_save / after_update listener writing each sensitive change to an audit-log table, with the acting user and time on every entry.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM2 · Strongly-typed ids
DM3 · Integration-event coupling
DM4 · Rich vs anemic model
- `Permission` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/domain/permission/entity/permission.py:8
- `OAuthAccount` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/infrastructure/db/models/oauth_provider.py:8
- `Permission` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/infrastructure/db/models/permission.py:28
- `Role` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/infrastructure/db/models/role.py:28
- `UserSession` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/infrastructure/db/models/session.py:10
- `User` is an aggregate/entity with 10 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/infrastructure/db/models/user.py:19
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `OAuthAccount` exposes publicly writable state (user_id, provider, provider_user_id, provider_email, is_active). — src/domain/oauth_account/entity/oauth_account.py:8
- `Permission` exposes publicly writable state (permission_name). — src/domain/permission/entity/permission.py:8
- `Role` exposes publicly writable state (name, description, security_level). — src/domain/role/entity/role.py:9
- `Session` exposes publicly writable state (user_id, user_agent, device_info, device_id, last_activity, is_active). — src/domain/session/entity/session.py:9
- `User` exposes publicly writable state (id, username, email, password, jwt_data, deleted_at, and 1 more). — src/domain/user/entity/user.py:19
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack — 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.
What to do
- Run what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — 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
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
P8 · Schema migrations
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X17 · Uncapped recursion over a caller-supplied document
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 100% | Exemplary | Solid. |
| Architecture | 75% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 79% | Strong | Solid. |
| Readiness | 33% | Weak — gated by D13, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 77% | Strong | Solid. |
| Domain Modelling | 67% | Adequate — gated by DM5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 3 control(s) we could not find positive evidence for
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- 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.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 61 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.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — 24 | -------------------- ERROR: failed to solve: process "/bin/sh -c apt update -y && apt install -y python3-dev gcc musl-dev && pip install --upgrade pip && pip install --no-cache-dir -r requirements.dev.txt && apt-get clean && useradd -r celery_user && chown -R celery_user:celery_user /app" did not complete successfully: exit code: 100; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~1579 lines of test source are present (.py) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .py suite was found but not re-run
- D12 Dependency Hygiene — Dependency currency not established — no declaration carries an exact pin to grade
- D16 Bus Factor — too few commits for a meaningful bus factor
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Python not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Python build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 integration event(s))
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — This repository's Python source (2 module(s), 299 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 19 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 93 finding(s)
- Repeated repair: src/presentation/api/v1/auth/auth_router.py src/presentation/api/v1/auth/auth_router.py:103
- Repeated repair: src/application/cqrs/cqrs_di_setup.py src/application/cqrs/cqrs_di_setup.py:106
- Repeated repair: src/settings/config.py src/settings/config.py:21
- Repeated repair: src/presentation/api/main.py src/presentation/api/main.py:23
- Repeated repair: src/domain/user/entity/user.py src/domain/user/entity/user.py:51
- Repeated repair: src/application/services/security/jwt_di_setup.py src/application/services/security/jwt_di_setup.py:26
- Repeated repair: REDACTED REDACTED:39
- Repeated repair: src/application/dependency_injector/di.py src/application/dependency_injector/di.py:65
- Repeated repair: src/presentation/api/lifespan.py src/presentation/api/lifespan.py:23
- Repeated repair: src/application/services/security/jwt_manager.py src/application/services/security/jwt_manager.py:101
- Repeated repair: src/infrastructure/repositories/session/session_repo.py src/infrastructure/repositories/session/session_repo.py:33
- Repeated repair: src/domain/permission/values/permission_name.py src/domain/permission/values/permission_name.py:14
- Repeated repair: src/application/services/rbac/rbac_manager.py src/application/services/rbac/rbac_manager.py:444
- Repeated repair: src/application/services/security/oauth_manager.py src/application/services/security/oauth_manager.py:614
- Repeated repair: src/presentation/api/v1/auth/request/user.py src/presentation/api/v1/auth/request/user.py:26
- Repeated repair: src/domain/role/entity/role.py src/domain/role/entity/role.py:16
- Repeated repair: REDACTED REDACTED:130
- Repeated repair: src/application/exceptions/jwt.py src/application/exceptions/jwt.py:23
- Repeated repair: src/application/exceptions/rbac.py src/application/exceptions/rbac.py:22
- Repeated repair: src/application/services/session/session_manager.py src/application/services/session/session_manager.py:29
- Repeated repair: src/infrastructure/repositories/role/role_repo.py src/infrastructure/repositories/role/role_repo.py:42
- Repeated repair: src/infrastructure/repositories/token/redis_repo.py src/infrastructure/repositories/token/redis_repo.py:16
- Repeated repair: src/presentation/api/v1/roles/rbac_router.py src/presentation/api/v1/roles/rbac_router.py:232
- Repeated repair: src/application/base/security/jwt_payload.py src/application/base/security/jwt_payload.py:18
- Repeated repair: src/domain/session/entity/session.py src/domain/session/entity/session.py:21
- Anemic entity: Permission src/domain/permission/entity/permission.py:8
- Anemic entity: OAuthAccount src/infrastructure/db/models/oauth_provider.py:8
- Anemic entity: Permission src/infrastructure/db/models/permission.py:28
- Anemic entity: Role src/infrastructure/db/models/role.py:28
- Anemic entity: UserSession src/infrastructure/db/models/session.py:10
- Anemic entity: User src/infrastructure/db/models/user.py:19
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Mutable entity: OAuthAccount src/domain/oauth_account/entity/oauth_account.py:8
- Mutable entity: Permission src/domain/permission/entity/permission.py:8
- Mutable entity: Role src/domain/role/entity/role.py:9
- Mutable entity: Session src/domain/session/entity/session.py:9
- Mutable entity: User src/domain/user/entity/user.py:19
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (5 lines × 2) src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:42
- Duplicated block (5 lines × 2) src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:98
- Duplicated block (18–20 lines × 2) src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:129
- Duplicated block (18–19 lines × 2) src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:105
- Duplicated block (18 lines × 2) src/application/cqrs/user/commands/register_oauth_user.py:59
- Duplicated block (16 lines × 2) src/infrastructure/repositories/converters.py:64
- Duplicated block (14 lines × 2) src/application/services/tasks/email_templates.py:188
- Duplicated block (12–13 lines × 5) src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:29
- Duplicated block (10–11 lines × 2) src/infrastructure/repositories/converters.py:204
- Duplicated block (7–9 lines × 2) src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:28
- Duplicated block (19 lines × 2) src/application/exceptions/oauth.py:12
- Duplicated block (7 lines × 2) src/infrastructure/repositories/role/role_repo.py:25
- No CI pipeline
Minor — 9 finding(s)
- REDACTED
- REDACTED
- No named authorization policies
- Partial audit-trail evidence
- Projects may be oversized for their cohesion
- REDACTED
- No ADRs
- No SAST
- No changelog
Minor — 1 finding(s)
- Dependency hygiene PARTLY measured — Python dependencies read, no exact pin to grade for currency
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-6672f604de4747bd9e327c5f6d1540d0/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-6672f604de4747bd9e327c5f6d1540d0/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 . | 6 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 21 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 7 | 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 . | 0 | artifacts/raw/osv-scanner.json |