Executive summary
thanhpt1110/chit-chat-backend falls short of our standard for production because eight passwords or keys sit in the current code and we found no automated security scanning of the code, its secrets or its dependencies. It scores 43 out of 100 and is rated Weak, and 20 of its 69 critical findings are security problems.
Production Readiness, at 33, is the weakest lens and counts most in the score. The best first step is replacing the eight exposed passwords or keys and switching the old ones off, worth about 9 points. Updating the outdated dependencies comes next, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 52.
Eight passwords or keys in the code and three in the code's history are open to anyone who can read the repository. Five known security holes in the packages the code depends on can be used by attackers. Replacing each exposed password or key and updating the vulnerable packages would close both risks. Pinning each tool to an exact version would fix the two pipeline tools referenced by a changeable name, and limiting each secret to its own step would deal with the secret exposed to more of the pipeline than needed. The 39 pieces of business logic tied to the database or web code need separating from the database and web code.
The product code is 5,183 lines, about €6,800 to rebuild.
If Production Readiness rose from 33 to 70, the lowest score rated Strong, the score would rise from 43 to about 52.
New since the last survey: 40 findings
- Dependency Vulnerabilities · REDACTED
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ConversationDetail src/ChitChat.Domain/Entities/ChatEntities/ConversationDetail.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: Message src/ChitChat.Domain/Entities/ChatEntities/Message.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: Comment src/ChitChat.Domain/Entities/PostEntities/Comment.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: Post src/ChitChat.Domain/Entities/PostEntities/Post.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ReactionComment src/ChitChat.Domain/Entities/PostEntities/Reaction/ReactionComment.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ReactionPost src/ChitChat.Domain/Entities/PostEntities/Reaction/ReactionPost.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: Notification src/ChitChat.Domain/Entities/SystemEntities/Notification/Notification.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: Notification src/ChitChat.Domain/Entities/SystemEntities/Notification/Notification.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserInteraction src/ChitChat.Domain/Entities/SystemEntities/UserInteraction.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: Profile src/ChitChat.Domain/Entities/UserEntities/Profile.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserFollower src/ChitChat.Domain/Entities/UserEntities/UserFollower.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserFollower src/ChitChat.Domain/Entities/UserEntities/UserFollower.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserFollowerRequest src/ChitChat.Domain/Entities/UserEntities/UserFollowerRequest.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserFollowerRequest src/ChitChat.Domain/Entities/UserEntities/UserFollowerRequest.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ApplicationRole src/ChitChat.Domain/Identity/ApplicationRole.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserApplication src/ChitChat.Domain/Identity/UserApplication.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ChitChat.Domain src/ChitChat.Domain/ChitChat.Domain.csproj
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ChitChat.Domain src/ChitChat.Domain/ChitChat.Domain.csproj
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ChitChat.Domain src/ChitChat.Domain/ChitChat.Domain.csproj
Fixed since the last survey: 84 findings
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Dependency Hygiene · Vulnerable: AutoMapper
- Cancellation propagation · Async method without CancellationToken: PostMediaToCloudAsync src/ChitChat.Infrastructure/Services/CloudinaryService.cs
- Cancellation propagation · Async method without CancellationToken: CreateProfileeAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: GetProfileByIdAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: GetAllFollowerAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: GetAllFollowingsAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: ToggleFollowAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: GetRecommendFollowAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: RegisterUser REDACTED
- Cancellation propagation · Async method without CancellationToken: LoginUser REDACTED
- Cancellation propagation · Async method without CancellationToken: LogoutUser REDACTED
- Cancellation propagation · Async method without CancellationToken: RefreshTokenAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: GetAllConversationsAsync src/ChitChat.Application/Services/ConversationService.cs
- Cancellation propagation · Async method without CancellationToken: GetConversationsByIdAsync src/ChitChat.Application/Services/ConversationService.cs
- Cancellation propagation · Async method without CancellationToken: CreateConversationAsync src/ChitChat.Application/Services/ConversationService.cs
- Cancellation propagation · Async method without CancellationToken: SendMessageAsync src/ChitChat.Application/Services/ConversationService.cs
- Cancellation propagation · Async method without CancellationToken: UpdateMessageAsync src/ChitChat.Application/Services/ConversationService.cs
- Cancellation propagation · Async method without CancellationToken: UpdateConversationAsync src/ChitChat.Application/Services/ConversationService.cs
- Cancellation propagation · Async method without CancellationToken: DeleteConversationAsync src/ChitChat.Application/Services/ConversationService.cs
- Cancellation propagation · Async method without CancellationToken: DeleteMessageAsync src/ChitChat.Application/Services/ConversationService.cs
- Cancellation propagation · Async method without CancellationToken: GetAllFollowerAsync src/ChitChat.Application/Services/FollowService.cs
- Cancellation propagation · Async method without CancellationToken: GetAllFollowingsAsync src/ChitChat.Application/Services/FollowService.cs
- Cancellation propagation · Async method without CancellationToken: GetRecommendFollowAsync src/ChitChat.Application/Services/FollowService.cs
- Cancellation propagation · Async method without CancellationToken: ToggleFollowAsync src/ChitChat.Application/Services/FollowService.cs
- Cancellation propagation · Async method without CancellationToken: CreateOrUpdateCommentNotificationAsync src/ChitChat.Application/Services/NotificationService.cs
- Cancellation propagation · Async method without CancellationToken: CreateOrUpdatePostNotificationAsync src/ChitChat.Application/Services/NotificationService.cs
- Cancellation propagation · Async method without CancellationToken: CreateOrUpdateUserNotificationAsync src/ChitChat.Application/Services/NotificationService.cs
- Cancellation propagation · Async method without CancellationToken: GetAllNotificationsAsync src/ChitChat.Application/Services/NotificationService.cs
- Cancellation propagation · Async method without CancellationToken: GetAllPostsAsync src/ChitChat.Application/Services/PostService.cs
- Cancellation propagation · Async method without CancellationToken: GetPostByIdAsync src/ChitChat.Application/Services/PostService.cs
- Cancellation propagation · Async method without CancellationToken: GetReccomendationPostsAsync src/ChitChat.Application/Services/PostService.cs
- Cancellation propagation · Async method without CancellationToken: GetAllReplyCommentsAsync src/ChitChat.Application/Services/PostService.cs
- Cancellation propagation · Async method without CancellationToken: CreateNewPostAsync src/ChitChat.Application/Services/PostService.cs
- Cancellation propagation · Async method without CancellationToken: CreateNewCommentAsync src/ChitChat.Application/Services/PostService.cs
- Cancellation propagation · Async method without CancellationToken: CreateReplyCommentAsync src/ChitChat.Application/Services/PostService.cs
- Cancellation propagation · Async method without CancellationToken: UpdatePostByIdAsync src/ChitChat.Application/Services/PostService.cs
- Cancellation propagation · Async method without CancellationToken: ToggleReactPostAsync src/ChitChat.Application/Services/PostService.cs
- Cancellation propagation · Async method without CancellationToken: UpdateCommentAsync src/ChitChat.Application/Services/PostService.cs
- Cancellation propagation · Async method without CancellationToken: ToggleReactCommentAsync src/ChitChat.Application/Services/PostService.cs
- Cancellation propagation · Async method without CancellationToken: DeletePostByIdAsync src/ChitChat.Application/Services/PostService.cs
- Cancellation propagation · Async method without CancellationToken: DeleteCommentByIdAsync src/ChitChat.Application/Services/PostService.cs
- Cancellation propagation · Async method without CancellationToken: GetAllProfilesAsync src/ChitChat.Application/Services/ProfileService.cs
- Cancellation propagation · Async method without CancellationToken: GetProfileByIdAsync src/ChitChat.Application/Services/ProfileService.cs
- Cancellation propagation · Async method without CancellationToken: CreateProfileAsync src/ChitChat.Application/Services/ProfileService.cs
- Cancellation propagation · Async method without CancellationToken: UpdateProfileAsync src/ChitChat.Application/Services/ProfileService.cs
- Cancellation propagation · Async method without CancellationToken: LoginAsync src/ChitChat.Application/Services/UserService.cs
- Cancellation propagation · Async method without CancellationToken: LogoutAsync src/ChitChat.Application/Services/UserService.cs
- Cancellation propagation · Async method without CancellationToken: RefreshTokenAsync src/ChitChat.Application/Services/UserService.cs
- Cancellation propagation · Async method without CancellationToken: RegisterAsync src/ChitChat.Application/Services/UserService.cs
- Cancellation propagation · Async method without CancellationToken: MigrateAsync src/ChitChat.DataAccess/Data/AutomatedMigration.cs
- Cancellation propagation · Async method without CancellationToken: GetFirstAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetFirstOrDefaultAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetFirstOrDefaultAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetFirstOrDefaultAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: AddAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: UpdateAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: DeleteAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: AnyAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: UpdateRangeAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: AddRangeAsync src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetPaginationEntities src/ChitChat.DataAccess/Repositories/BaseRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetConversationByUserIdAsync src/ChitChat.DataAccess/Repositories/ConversationRepository.cs
- Cancellation propagation · Async method without CancellationToken: IsConversationExisted src/ChitChat.DataAccess/Repositories/ConversationRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetRecommendedUsersAsync src/ChitChat.DataAccess/Repositories/UserFollowerRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetUserInteractionModelForTraining src/ChitChat.DataAccess/Repositories/UserInteractionRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetFirstAsync src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetFirstOrDefaultAsync src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Cancellation propagation · Async method without CancellationToken: UpdateAsync src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Cancellation propagation · Async method without CancellationToken: DeleteAsync src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Cancellation propagation · Async method without CancellationToken: AnyAsync src/ChitChat.DataAccess/Repositories/UserRepository.cs
- Cancellation propagation · Async method without CancellationToken: UpdateRangeAsync src/ChitChat.DataAccess/Repositories/UserRepository.cs
Rebuild cost: about €6,800 · Estimate
| Cost to rebuild | €2,300 to €11,000, for 38 to 119 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 43. 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: 5,183 lines of product code, of which 38% is declarations and boilerplate, 50% straight logic and 12% logic with branches |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 ChitChat.Application.Models | 2 ChitChat.Application.Models.Dtos | 3 ChitChat.Application.Models.Dtos.Post.CreatePost | 4 ChitChat.Application.Models.Dtos.User | 5 ChitChat.Application.Services.Caching | 6 ChitChat.Domain.Common | 7 ChitChat.Application.Exceptions | 8 ChitChat.Application.Localization | 9 ChitChat.Application.Models.Dtos.Message | 10 ChitChat.Application.Models.Dtos.Post.Comments | 11 ChitChat.Application.Models.Dtos.User.Follow | 12 ChitChat.Application.Models.Dtos.User.Profile | 13 ChitChat.Domain.Entities | 14 ChitChat.Application.Models.Dtos.Conversation | 15 ChitChat.Application.Models.Dtos.Post | 16 ChitChat.Domain.Entities.PostEntities | 17 ChitChat.Application.MachineLearning.Models | 18 ChitChat.Application.Models.Dtos.Notification | 19 ChitChat.Domain.Entities.SystemEntities | 20 ChitChat.Application.MachineLearning.Services.Interface | 21 ChitChat.Application.Services.Interface | 22 ChitChat.Application.SignalR.Interface | 23 ChitChat.Domain.Enums | 24 ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient | 25 ChitChat.Application.MachineLearning.Services | 26 ChitChat.Domain.Identity | 27 ChitChat.Infrastructure.SignalR.Services | 28 ChitChat.Application.Helpers | 29 ChitChat.Domain.Entities.ChatEntities | 30 ChitChat.Domain.Entities.PostEntities.Reaction | 31 ChitChat.Domain.Entities.SystemEntities.Notification | 32 ChitChat.Domain.Entities.UserEntities | 33 (global) | 34 ChitChat.Infrastructure.Services | 35 ChitChat.DataAccess.Configurations | 36 ChitChat.DataAccess.Data | 37 ChitChat.DataAccess.Repositories.Interface | 38 ChitChat.Application.Services | 39 ChitChat.DataAccess.Repositories | 40 ChitChat.WebAPI.Controllers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 ChitChat.Application.Models | ||||||||||||||||||||||||||||||||||||||||
| 2 ChitChat.Application.Models.Dtos | ||||||||||||||||||||||||||||||||||||||||
| 3 ChitChat.Application.Models.Dtos.Post.CreatePost | ||||||||||||||||||||||||||||||||||||||||
| 4 ChitChat.Application.Models.Dtos.User | ||||||||||||||||||||||||||||||||||||||||
| 5 ChitChat.Application.Services.Caching | ||||||||||||||||||||||||||||||||||||||||
| 6 ChitChat.Domain.Common | ||||||||||||||||||||||||||||||||||||||||
| 7 ChitChat.Application.Exceptions | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 ChitChat.Application.Localization | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 ChitChat.Application.Models.Dtos.Message | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 ChitChat.Application.Models.Dtos.Post.Comments | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 ChitChat.Application.Models.Dtos.User.Follow | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 ChitChat.Application.Models.Dtos.User.Profile | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 ChitChat.Domain.Entities | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 ChitChat.Application.Models.Dtos.Conversation | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 15 ChitChat.Application.Models.Dtos.Post | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 16 ChitChat.Domain.Entities.PostEntities | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 17 ChitChat.Application.MachineLearning.Models | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 ChitChat.Application.Models.Dtos.Notification | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 ChitChat.Domain.Entities.SystemEntities | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 ChitChat.Application.MachineLearning.Services.Interface | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 ChitChat.Application.Services.Interface | 3 | 1 | 4 | 2 | 2 | 1 | 3 | 2 | 4 | 4 | ||||||||||||||||||||||||||||||
| 22 ChitChat.Application.SignalR.Interface | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 ChitChat.Domain.Enums | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 ChitChat.Application.MachineLearning.Services | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 ChitChat.Domain.Identity | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 ChitChat.Infrastructure.SignalR.Services | 1 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 28 ChitChat.Application.Helpers | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 ChitChat.Domain.Entities.ChatEntities | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 ChitChat.Domain.Entities.PostEntities.Reaction | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 31 ChitChat.Domain.Entities.SystemEntities.Notification | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 ChitChat.Domain.Entities.UserEntities | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 33 (global) | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 ChitChat.Infrastructure.Services | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 35 ChitChat.DataAccess.Configurations | 1 | 4 | 1 | 1 | 2 | 3 | 2 | |||||||||||||||||||||||||||||||||
| 36 ChitChat.DataAccess.Data | 1 | 4 | 1 | 3 | 1 | 2 | 3 | 3 | 2 | |||||||||||||||||||||||||||||||
| 37 ChitChat.DataAccess.Repositories.Interface | 1 | 2 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 38 ChitChat.Application.Services | 3 | 1 | 4 | 2 | 2 | 1 | 3 | 1 | 2 | 4 | 3 | 4 | 1 | 8 | 3 | 2 | 8 | 1 | 2 | 3 | 2 | 1 | 17 | |||||||||||||||||
| 39 ChitChat.DataAccess.Repositories | 1 | 2 | 1 | 2 | 1 | 5 | 7 | |||||||||||||||||||||||||||||||||
| 40 ChitChat.WebAPI.Controllers | 3 | 1 | 3 | 2 | 1 | 2 | 1 | 3 | 1 | 6 | 1 | 1 |
7→1 ChitChat.Application.Exceptions uses ChitChat.Application.Models✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Exceptions uses a type in ChitChat.Application.Models.
- The types involved
ChitChat.Application.Exceptions.ApplicationException→ChitChat.Application.Models.ApiResultErrorCodes
- Direction
- ChitChat.Application.Exceptions uses ChitChat.Application.Models, so a change to ChitChat.Application.Models can break ChitChat.Application.Exceptions, while a change to ChitChat.Application.Exceptions can't break ChitChat.Application.Models.
- Position
- Below the diagonal: ChitChat.Application.Exceptions uses a module listed above it, which is the healthy direction.
8→6 ChitChat.Application.Localization uses ChitChat.Domain.Common✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Localization uses a type in ChitChat.Domain.Common.
- The types involved
ChitChat.Application.Localization.ValidationTexts→ChitChat.Domain.Common.LocalizedText
- Direction
- ChitChat.Application.Localization uses ChitChat.Domain.Common, so a change to ChitChat.Domain.Common can break ChitChat.Application.Localization, while a change to ChitChat.Application.Localization can't break ChitChat.Domain.Common.
- Position
- Below the diagonal: ChitChat.Application.Localization uses a module listed above it, which is the healthy direction.
9→2 ChitChat.Application.Models.Dtos.Message uses ChitChat.Application.Models.Dtos✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Models.Dtos.Message uses a type in ChitChat.Application.Models.Dtos.
- The types involved
ChitChat.Application.Models.Dtos.Message.MessageDto→ChitChat.Application.Models.Dtos.BaseResponseDto
- Direction
- ChitChat.Application.Models.Dtos.Message uses ChitChat.Application.Models.Dtos, so a change to ChitChat.Application.Models.Dtos can break ChitChat.Application.Models.Dtos.Message, while a change to ChitChat.Application.Models.Dtos.Message can't break ChitChat.Application.Models.Dtos.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.Message uses a module listed above it, which is the healthy direction.
10→2 ChitChat.Application.Models.Dtos.Post.Comments uses ChitChat.Application.Models.Dtos✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Models.Dtos.Post.Comments uses a type in ChitChat.Application.Models.Dtos.
- The types involved
ChitChat.Application.Models.Dtos.Post.Comments.CommentDto→ChitChat.Application.Models.Dtos.BaseResponseDto
- Direction
- ChitChat.Application.Models.Dtos.Post.Comments uses ChitChat.Application.Models.Dtos, so a change to ChitChat.Application.Models.Dtos can break ChitChat.Application.Models.Dtos.Post.Comments, while a change to ChitChat.Application.Models.Dtos.Post.Comments can't break ChitChat.Application.Models.Dtos.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.Post.Comments uses a module listed above it, which is the healthy direction.
10→4 ChitChat.Application.Models.Dtos.Post.Comments uses ChitChat.Application.Models.Dtos.User✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Models.Dtos.Post.Comments uses a type in ChitChat.Application.Models.Dtos.User.
- The types involved
ChitChat.Application.Models.Dtos.Post.Comments.CommentDto→ChitChat.Application.Models.Dtos.User.UserDto
- Direction
- ChitChat.Application.Models.Dtos.Post.Comments uses ChitChat.Application.Models.Dtos.User, so a change to ChitChat.Application.Models.Dtos.User can break ChitChat.Application.Models.Dtos.Post.Comments, while a change to ChitChat.Application.Models.Dtos.Post.Comments can't break ChitChat.Application.Models.Dtos.User.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.Post.Comments uses a module listed above it, which is the healthy direction.
11→2 ChitChat.Application.Models.Dtos.User.Follow uses ChitChat.Application.Models.Dtos✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Models.Dtos.User.Follow uses a type in ChitChat.Application.Models.Dtos.
- The types involved
ChitChat.Application.Models.Dtos.User.Follow.FollowDto→ChitChat.Application.Models.Dtos.BaseResponseDto
- Direction
- ChitChat.Application.Models.Dtos.User.Follow uses ChitChat.Application.Models.Dtos, so a change to ChitChat.Application.Models.Dtos can break ChitChat.Application.Models.Dtos.User.Follow, while a change to ChitChat.Application.Models.Dtos.User.Follow can't break ChitChat.Application.Models.Dtos.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.User.Follow uses a module listed above it, which is the healthy direction.
11→4 ChitChat.Application.Models.Dtos.User.Follow uses ChitChat.Application.Models.Dtos.User✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Models.Dtos.User.Follow uses a type in ChitChat.Application.Models.Dtos.User.
- The types involved
ChitChat.Application.Models.Dtos.User.Follow.FollowDto→ChitChat.Application.Models.Dtos.User.UserDto
- Direction
- ChitChat.Application.Models.Dtos.User.Follow uses ChitChat.Application.Models.Dtos.User, so a change to ChitChat.Application.Models.Dtos.User can break ChitChat.Application.Models.Dtos.User.Follow, while a change to ChitChat.Application.Models.Dtos.User.Follow can't break ChitChat.Application.Models.Dtos.User.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.User.Follow uses a module listed above it, which is the healthy direction.
12→1 ChitChat.Application.Models.Dtos.User.Profile uses ChitChat.Application.Models✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Models.Dtos.User.Profile uses a type in ChitChat.Application.Models.
- The types involved
ChitChat.Application.Models.Dtos.User.Profile.ProfileSearchQueryDto→ChitChat.Application.Models.PaginationFilter
- Direction
- ChitChat.Application.Models.Dtos.User.Profile uses ChitChat.Application.Models, so a change to ChitChat.Application.Models can break ChitChat.Application.Models.Dtos.User.Profile, while a change to ChitChat.Application.Models.Dtos.User.Profile can't break ChitChat.Application.Models.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.User.Profile uses a module listed above it, which is the healthy direction.
13→6 ChitChat.Domain.Entities uses ChitChat.Domain.Common✕
- Connections
- 1 pair of types, where a type in ChitChat.Domain.Entities uses a type in ChitChat.Domain.Common.
- The types involved
ChitChat.Domain.Entities.BaseAuditedEntity→ChitChat.Domain.Common.IAuditedEntity
- Direction
- ChitChat.Domain.Entities uses ChitChat.Domain.Common, so a change to ChitChat.Domain.Common can break ChitChat.Domain.Entities, while a change to ChitChat.Domain.Entities can't break ChitChat.Domain.Common.
- Position
- Below the diagonal: ChitChat.Domain.Entities uses a module listed above it, which is the healthy direction.
14→2 ChitChat.Application.Models.Dtos.Conversation uses ChitChat.Application.Models.Dtos✕
- Connections
- 2 pairs of types, where a type in ChitChat.Application.Models.Dtos.Conversation uses a type in ChitChat.Application.Models.Dtos.
- The types involved
ChitChat.Application.Models.Dtos.Conversation.ConversationDetailDto→ChitChat.Application.Models.Dtos.BaseResponseDtoChitChat.Application.Models.Dtos.Conversation.ConversationDto→ChitChat.Application.Models.Dtos.BaseResponseDto
- Direction
- ChitChat.Application.Models.Dtos.Conversation uses ChitChat.Application.Models.Dtos, so a change to ChitChat.Application.Models.Dtos can break ChitChat.Application.Models.Dtos.Conversation, while a change to ChitChat.Application.Models.Dtos.Conversation can't break ChitChat.Application.Models.Dtos.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.Conversation uses a module listed above it, which is the healthy direction.
14→4 ChitChat.Application.Models.Dtos.Conversation uses ChitChat.Application.Models.Dtos.User✕
- Connections
- 2 pairs of types, where a type in ChitChat.Application.Models.Dtos.Conversation uses a type in ChitChat.Application.Models.Dtos.User.
- The types involved
ChitChat.Application.Models.Dtos.Conversation.ConversationDetailDto→ChitChat.Application.Models.Dtos.User.UserDtoChitChat.Application.Models.Dtos.Conversation.ConversationDto→ChitChat.Application.Models.Dtos.User.UserDto
- Direction
- ChitChat.Application.Models.Dtos.Conversation uses ChitChat.Application.Models.Dtos.User, so a change to ChitChat.Application.Models.Dtos.User can break ChitChat.Application.Models.Dtos.Conversation, while a change to ChitChat.Application.Models.Dtos.Conversation can't break ChitChat.Application.Models.Dtos.User.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.Conversation uses a module listed above it, which is the healthy direction.
14→9 ChitChat.Application.Models.Dtos.Conversation uses ChitChat.Application.Models.Dtos.Message✕
- Connections
- 2 pairs of types, where a type in ChitChat.Application.Models.Dtos.Conversation uses a type in ChitChat.Application.Models.Dtos.Message.
- The types involved
ChitChat.Application.Models.Dtos.Conversation.ConversationDetailDto→ChitChat.Application.Models.Dtos.Message.MessageDtoChitChat.Application.Models.Dtos.Conversation.ConversationDto→ChitChat.Application.Models.Dtos.Message.MessageDto
- Direction
- ChitChat.Application.Models.Dtos.Conversation uses ChitChat.Application.Models.Dtos.Message, so a change to ChitChat.Application.Models.Dtos.Message can break ChitChat.Application.Models.Dtos.Conversation, while a change to ChitChat.Application.Models.Dtos.Conversation can't break ChitChat.Application.Models.Dtos.Message.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.Conversation uses a module listed above it, which is the healthy direction.
15→1 ChitChat.Application.Models.Dtos.Post uses ChitChat.Application.Models✕
- Connections
- 2 pairs of types, where a type in ChitChat.Application.Models.Dtos.Post uses a type in ChitChat.Application.Models.
- The types involved
ChitChat.Application.Models.Dtos.Post.PostSearchQueryDto→ChitChat.Application.Models.PaginationFilterChitChat.Application.Models.Dtos.Post.PostUserSearchQueryDto→ChitChat.Application.Models.PaginationFilter
- Direction
- ChitChat.Application.Models.Dtos.Post uses ChitChat.Application.Models, so a change to ChitChat.Application.Models can break ChitChat.Application.Models.Dtos.Post, while a change to ChitChat.Application.Models.Dtos.Post can't break ChitChat.Application.Models.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.Post uses a module listed above it, which is the healthy direction.
15→2 ChitChat.Application.Models.Dtos.Post uses ChitChat.Application.Models.Dtos✕
- Connections
- 2 pairs of types, where a type in ChitChat.Application.Models.Dtos.Post uses a type in ChitChat.Application.Models.Dtos.
- The types involved
ChitChat.Application.Models.Dtos.Post.PostDto→ChitChat.Application.Models.Dtos.BaseResponseDtoChitChat.Application.Models.Dtos.Post.PostMediaDto→ChitChat.Application.Models.Dtos.BaseResponseDto
- Direction
- ChitChat.Application.Models.Dtos.Post uses ChitChat.Application.Models.Dtos, so a change to ChitChat.Application.Models.Dtos can break ChitChat.Application.Models.Dtos.Post, while a change to ChitChat.Application.Models.Dtos.Post can't break ChitChat.Application.Models.Dtos.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.Post uses a module listed above it, which is the healthy direction.
15→4 ChitChat.Application.Models.Dtos.Post uses ChitChat.Application.Models.Dtos.User✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Models.Dtos.Post uses a type in ChitChat.Application.Models.Dtos.User.
- The types involved
ChitChat.Application.Models.Dtos.Post.PostDto→ChitChat.Application.Models.Dtos.User.UserDto
- Direction
- ChitChat.Application.Models.Dtos.Post uses ChitChat.Application.Models.Dtos.User, so a change to ChitChat.Application.Models.Dtos.User can break ChitChat.Application.Models.Dtos.Post, while a change to ChitChat.Application.Models.Dtos.Post can't break ChitChat.Application.Models.Dtos.User.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.Post uses a module listed above it, which is the healthy direction.
15→10 ChitChat.Application.Models.Dtos.Post uses ChitChat.Application.Models.Dtos.Post.Comments✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Models.Dtos.Post uses a type in ChitChat.Application.Models.Dtos.Post.Comments.
- The types involved
ChitChat.Application.Models.Dtos.Post.PostDto→ChitChat.Application.Models.Dtos.Post.Comments.CommentDto
- Direction
- ChitChat.Application.Models.Dtos.Post uses ChitChat.Application.Models.Dtos.Post.Comments, so a change to ChitChat.Application.Models.Dtos.Post.Comments can break ChitChat.Application.Models.Dtos.Post, while a change to ChitChat.Application.Models.Dtos.Post can't break ChitChat.Application.Models.Dtos.Post.Comments.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.Post uses a module listed above it, which is the healthy direction.
16→13 ChitChat.Domain.Entities.PostEntities uses ChitChat.Domain.Entities✕
- Connections
- 4 pairs of types, where a type in ChitChat.Domain.Entities.PostEntities uses a type in ChitChat.Domain.Entities.
- The types involved
ChitChat.Domain.Entities.PostEntities.Comment→ChitChat.Domain.Entities.BaseAuditedEntityChitChat.Domain.Entities.PostEntities.Post→ChitChat.Domain.Entities.BaseAuditedEntityChitChat.Domain.Entities.PostEntities.PostDetailTag→ChitChat.Domain.Entities.BaseEntityChitChat.Domain.Entities.PostEntities.PostMedia→ChitChat.Domain.Entities.BaseEntity
- Direction
- ChitChat.Domain.Entities.PostEntities uses ChitChat.Domain.Entities, so a change to ChitChat.Domain.Entities can break ChitChat.Domain.Entities.PostEntities, while a change to ChitChat.Domain.Entities.PostEntities can't break ChitChat.Domain.Entities.
- Position
- Below the diagonal: ChitChat.Domain.Entities.PostEntities uses a module listed above it, which is the healthy direction.
16→26 ChitChat.Domain.Entities.PostEntities uses ChitChat.Domain.Identity part of a loop✕
- Connections
- 2 pairs of types, where a type in ChitChat.Domain.Entities.PostEntities uses a type in ChitChat.Domain.Identity.
- The types involved
ChitChat.Domain.Entities.PostEntities.Comment→ChitChat.Domain.Identity.UserApplicationChitChat.Domain.Entities.PostEntities.Post→ChitChat.Domain.Identity.UserApplication
- Direction
- ChitChat.Domain.Entities.PostEntities uses ChitChat.Domain.Identity, so a change to ChitChat.Domain.Identity can break ChitChat.Domain.Entities.PostEntities, while a change to ChitChat.Domain.Entities.PostEntities can't break ChitChat.Domain.Identity.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→15 ChitChat.Application.MachineLearning.Models uses ChitChat.Application.Models.Dtos.Post✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.MachineLearning.Models uses a type in ChitChat.Application.Models.Dtos.Post.
- The types involved
ChitChat.Application.MachineLearning.Models.ResponseRecommendationModel→ChitChat.Application.Models.Dtos.Post.PostDto
- Direction
- ChitChat.Application.MachineLearning.Models uses ChitChat.Application.Models.Dtos.Post, so a change to ChitChat.Application.Models.Dtos.Post can break ChitChat.Application.MachineLearning.Models, while a change to ChitChat.Application.MachineLearning.Models can't break ChitChat.Application.Models.Dtos.Post.
- Position
- Below the diagonal: ChitChat.Application.MachineLearning.Models uses a module listed above it, which is the healthy direction.
18→2 ChitChat.Application.Models.Dtos.Notification uses ChitChat.Application.Models.Dtos✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Models.Dtos.Notification uses a type in ChitChat.Application.Models.Dtos.
- The types involved
ChitChat.Application.Models.Dtos.Notification.NotificationDto→ChitChat.Application.Models.Dtos.BaseResponseDto
- Direction
- ChitChat.Application.Models.Dtos.Notification uses ChitChat.Application.Models.Dtos, so a change to ChitChat.Application.Models.Dtos can break ChitChat.Application.Models.Dtos.Notification, while a change to ChitChat.Application.Models.Dtos.Notification can't break ChitChat.Application.Models.Dtos.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.Notification uses a module listed above it, which is the healthy direction.
18→4 ChitChat.Application.Models.Dtos.Notification uses ChitChat.Application.Models.Dtos.User✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Models.Dtos.Notification uses a type in ChitChat.Application.Models.Dtos.User.
- The types involved
ChitChat.Application.Models.Dtos.Notification.NotificationDto→ChitChat.Application.Models.Dtos.User.UserDto
- Direction
- ChitChat.Application.Models.Dtos.Notification uses ChitChat.Application.Models.Dtos.User, so a change to ChitChat.Application.Models.Dtos.User can break ChitChat.Application.Models.Dtos.Notification, while a change to ChitChat.Application.Models.Dtos.Notification can't break ChitChat.Application.Models.Dtos.User.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.Notification uses a module listed above it, which is the healthy direction.
18→10 ChitChat.Application.Models.Dtos.Notification uses ChitChat.Application.Models.Dtos.Post.Comments✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Models.Dtos.Notification uses a type in ChitChat.Application.Models.Dtos.Post.Comments.
- The types involved
ChitChat.Application.Models.Dtos.Notification.NotificationDto→ChitChat.Application.Models.Dtos.Post.Comments.CommentDto
- Direction
- ChitChat.Application.Models.Dtos.Notification uses ChitChat.Application.Models.Dtos.Post.Comments, so a change to ChitChat.Application.Models.Dtos.Post.Comments can break ChitChat.Application.Models.Dtos.Notification, while a change to ChitChat.Application.Models.Dtos.Notification can't break ChitChat.Application.Models.Dtos.Post.Comments.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.Notification uses a module listed above it, which is the healthy direction.
18→15 ChitChat.Application.Models.Dtos.Notification uses ChitChat.Application.Models.Dtos.Post✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Models.Dtos.Notification uses a type in ChitChat.Application.Models.Dtos.Post.
- The types involved
ChitChat.Application.Models.Dtos.Notification.NotificationDto→ChitChat.Application.Models.Dtos.Post.PostDto
- Direction
- ChitChat.Application.Models.Dtos.Notification uses ChitChat.Application.Models.Dtos.Post, so a change to ChitChat.Application.Models.Dtos.Post can break ChitChat.Application.Models.Dtos.Notification, while a change to ChitChat.Application.Models.Dtos.Notification can't break ChitChat.Application.Models.Dtos.Post.
- Position
- Below the diagonal: ChitChat.Application.Models.Dtos.Notification uses a module listed above it, which is the healthy direction.
19→13 ChitChat.Domain.Entities.SystemEntities uses ChitChat.Domain.Entities✕
- Connections
- 1 pair of types, where a type in ChitChat.Domain.Entities.SystemEntities uses a type in ChitChat.Domain.Entities.
- The types involved
ChitChat.Domain.Entities.SystemEntities.UserInteraction→ChitChat.Domain.Entities.BaseEntity
- Direction
- ChitChat.Domain.Entities.SystemEntities uses ChitChat.Domain.Entities, so a change to ChitChat.Domain.Entities can break ChitChat.Domain.Entities.SystemEntities, while a change to ChitChat.Domain.Entities.SystemEntities can't break ChitChat.Domain.Entities.
- Position
- Below the diagonal: ChitChat.Domain.Entities.SystemEntities uses a module listed above it, which is the healthy direction.
19→16 ChitChat.Domain.Entities.SystemEntities uses ChitChat.Domain.Entities.PostEntities✕
- Connections
- 1 pair of types, where a type in ChitChat.Domain.Entities.SystemEntities uses a type in ChitChat.Domain.Entities.PostEntities.
- The types involved
ChitChat.Domain.Entities.SystemEntities.UserInteraction→ChitChat.Domain.Entities.PostEntities.Post
- Direction
- ChitChat.Domain.Entities.SystemEntities uses ChitChat.Domain.Entities.PostEntities, so a change to ChitChat.Domain.Entities.PostEntities can break ChitChat.Domain.Entities.SystemEntities, while a change to ChitChat.Domain.Entities.SystemEntities can't break ChitChat.Domain.Entities.PostEntities.
- Position
- Below the diagonal: ChitChat.Domain.Entities.SystemEntities uses a module listed above it, which is the healthy direction.
19→23 ChitChat.Domain.Entities.SystemEntities uses ChitChat.Domain.Enums part of a loop✕
- Connections
- 1 pair of types, where a type in ChitChat.Domain.Entities.SystemEntities uses a type in ChitChat.Domain.Enums.
- The types involved
ChitChat.Domain.Entities.SystemEntities.UserInteraction→ChitChat.Domain.Enums.InteractionType
- Direction
- ChitChat.Domain.Entities.SystemEntities uses ChitChat.Domain.Enums, so a change to ChitChat.Domain.Enums can break ChitChat.Domain.Entities.SystemEntities, while a change to ChitChat.Domain.Entities.SystemEntities can't break ChitChat.Domain.Enums.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→26 ChitChat.Domain.Entities.SystemEntities uses ChitChat.Domain.Identity part of a loop✕
- Connections
- 1 pair of types, where a type in ChitChat.Domain.Entities.SystemEntities uses a type in ChitChat.Domain.Identity.
- The types involved
ChitChat.Domain.Entities.SystemEntities.UserInteraction→ChitChat.Domain.Identity.UserApplication
- Direction
- ChitChat.Domain.Entities.SystemEntities uses ChitChat.Domain.Identity, so a change to ChitChat.Domain.Identity can break ChitChat.Domain.Entities.SystemEntities, while a change to ChitChat.Domain.Entities.SystemEntities can't break ChitChat.Domain.Identity.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→16 ChitChat.Application.MachineLearning.Services.Interface uses ChitChat.Domain.Entities.PostEntities✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.MachineLearning.Services.Interface uses a type in ChitChat.Domain.Entities.PostEntities.
- The types involved
ChitChat.Application.MachineLearning.Services.Interface.ITrainingModelService→ChitChat.Domain.Entities.PostEntities.Post
- Direction
- ChitChat.Application.MachineLearning.Services.Interface uses ChitChat.Domain.Entities.PostEntities, so a change to ChitChat.Domain.Entities.PostEntities can break ChitChat.Application.MachineLearning.Services.Interface, while a change to ChitChat.Application.MachineLearning.Services.Interface can't break ChitChat.Domain.Entities.PostEntities.
- Position
- Below the diagonal: ChitChat.Application.MachineLearning.Services.Interface uses a module listed above it, which is the healthy direction.
20→17 ChitChat.Application.MachineLearning.Services.Interface uses ChitChat.Application.MachineLearning.Models✕
- Connections
- 2 pairs of types, where a type in ChitChat.Application.MachineLearning.Services.Interface uses a type in ChitChat.Application.MachineLearning.Models.
- The types involved
ChitChat.Application.MachineLearning.Services.Interface.ITrainingModelService→ChitChat.Application.MachineLearning.Models.ResponseRecommendationModelChitChat.Application.MachineLearning.Services.Interface.ITrainingModelService→ChitChat.Application.MachineLearning.Models.UserInteractionModelItem
- Direction
- ChitChat.Application.MachineLearning.Services.Interface uses ChitChat.Application.MachineLearning.Models, so a change to ChitChat.Application.MachineLearning.Models can break ChitChat.Application.MachineLearning.Services.Interface, while a change to ChitChat.Application.MachineLearning.Services.Interface can't break ChitChat.Application.MachineLearning.Models.
- Position
- Below the diagonal: ChitChat.Application.MachineLearning.Services.Interface uses a module listed above it, which is the healthy direction.
21→1 ChitChat.Application.Services.Interface uses ChitChat.Application.Models✕
- Connections
- 3 pairs of types, where a type in ChitChat.Application.Services.Interface uses a type in ChitChat.Application.Models.
- The types involved
ChitChat.Application.Services.Interface.IConversationService→ChitChat.Application.Models.PaginationFilterChitChat.Application.Services.Interface.IFollowService→ChitChat.Application.Models.PaginationFilterChitChat.Application.Services.Interface.INotificationService→ChitChat.Application.Models.PaginationFilter
- Direction
- ChitChat.Application.Services.Interface uses ChitChat.Application.Models, so a change to ChitChat.Application.Models can break ChitChat.Application.Services.Interface, while a change to ChitChat.Application.Services.Interface can't break ChitChat.Application.Models.
- Position
- Below the diagonal: ChitChat.Application.Services.Interface uses a module listed above it, which is the healthy direction.
21→3 ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.Post.CreatePost✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Services.Interface uses a type in ChitChat.Application.Models.Dtos.Post.CreatePost.
- The types involved
ChitChat.Application.Services.Interface.IPostService→ChitChat.Application.Models.Dtos.Post.CreatePost.CreatePostRequestDto
- Direction
- ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.Post.CreatePost, so a change to ChitChat.Application.Models.Dtos.Post.CreatePost can break ChitChat.Application.Services.Interface, while a change to ChitChat.Application.Services.Interface can't break ChitChat.Application.Models.Dtos.Post.CreatePost.
- Position
- Below the diagonal: ChitChat.Application.Services.Interface uses a module listed above it, which is the healthy direction.
21→4 ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.User✕
- Connections
- 4 pairs of types, where a type in ChitChat.Application.Services.Interface uses a type in ChitChat.Application.Models.Dtos.User.
- The types involved
ChitChat.Application.Services.Interface.IUserService→ChitChat.Application.Models.Dtos.User.LoginRequestDtoChitChat.Application.Services.Interface.IUserService→ChitChat.Application.Models.Dtos.User.LoginResponseDtoChitChat.Application.Services.Interface.IUserService→ChitChat.Application.Models.Dtos.User.RefreshTokenDtoChitChat.Application.Services.Interface.IUserService→ChitChat.Application.Models.Dtos.User.RegisterationRequestDto
- Direction
- ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.User, so a change to ChitChat.Application.Models.Dtos.User can break ChitChat.Application.Services.Interface, while a change to ChitChat.Application.Services.Interface can't break ChitChat.Application.Models.Dtos.User.
- Position
- Below the diagonal: ChitChat.Application.Services.Interface uses a module listed above it, which is the healthy direction.
21→9 ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.Message✕
- Connections
- 2 pairs of types, where a type in ChitChat.Application.Services.Interface uses a type in ChitChat.Application.Models.Dtos.Message.
- The types involved
ChitChat.Application.Services.Interface.IConversationService→ChitChat.Application.Models.Dtos.Message.MessageDtoChitChat.Application.Services.Interface.IConversationService→ChitChat.Application.Models.Dtos.Message.RequestSendMessageDto
- Direction
- ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.Message, so a change to ChitChat.Application.Models.Dtos.Message can break ChitChat.Application.Services.Interface, while a change to ChitChat.Application.Services.Interface can't break ChitChat.Application.Models.Dtos.Message.
- Position
- Below the diagonal: ChitChat.Application.Services.Interface uses a module listed above it, which is the healthy direction.
21→10 ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.Post.Comments✕
- Connections
- 2 pairs of types, where a type in ChitChat.Application.Services.Interface uses a type in ChitChat.Application.Models.Dtos.Post.Comments.
- The types involved
ChitChat.Application.Services.Interface.IPostService→ChitChat.Application.Models.Dtos.Post.Comments.CommentDtoChitChat.Application.Services.Interface.IPostService→ChitChat.Application.Models.Dtos.Post.Comments.CommentRequestDto
- Direction
- ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.Post.Comments, so a change to ChitChat.Application.Models.Dtos.Post.Comments can break ChitChat.Application.Services.Interface, while a change to ChitChat.Application.Services.Interface can't break ChitChat.Application.Models.Dtos.Post.Comments.
- Position
- Below the diagonal: ChitChat.Application.Services.Interface uses a module listed above it, which is the healthy direction.
21→11 ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.User.Follow✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Services.Interface uses a type in ChitChat.Application.Models.Dtos.User.Follow.
- The types involved
ChitChat.Application.Services.Interface.IFollowService→ChitChat.Application.Models.Dtos.User.Follow.FollowDto
- Direction
- ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.User.Follow, so a change to ChitChat.Application.Models.Dtos.User.Follow can break ChitChat.Application.Services.Interface, while a change to ChitChat.Application.Services.Interface can't break ChitChat.Application.Models.Dtos.User.Follow.
- Position
- Below the diagonal: ChitChat.Application.Services.Interface uses a module listed above it, which is the healthy direction.
21→12 ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.User.Profile✕
- Connections
- 3 pairs of types, where a type in ChitChat.Application.Services.Interface uses a type in ChitChat.Application.Models.Dtos.User.Profile.
- The types involved
ChitChat.Application.Services.Interface.IProfileService→ChitChat.Application.Models.Dtos.User.Profile.ProfileDtoChitChat.Application.Services.Interface.IProfileService→ChitChat.Application.Models.Dtos.User.Profile.ProfileRequestDtoChitChat.Application.Services.Interface.IProfileService→ChitChat.Application.Models.Dtos.User.Profile.ProfileSearchQueryDto
- Direction
- ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.User.Profile, so a change to ChitChat.Application.Models.Dtos.User.Profile can break ChitChat.Application.Services.Interface, while a change to ChitChat.Application.Services.Interface can't break ChitChat.Application.Models.Dtos.User.Profile.
- Position
- Below the diagonal: ChitChat.Application.Services.Interface uses a module listed above it, which is the healthy direction.
21→14 ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.Conversation✕
- Connections
- 2 pairs of types, where a type in ChitChat.Application.Services.Interface uses a type in ChitChat.Application.Models.Dtos.Conversation.
- The types involved
ChitChat.Application.Services.Interface.IConversationService→ChitChat.Application.Models.Dtos.Conversation.ConversationDetailDtoChitChat.Application.Services.Interface.IConversationService→ChitChat.Application.Models.Dtos.Conversation.ConversationDto
- Direction
- ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.Conversation, so a change to ChitChat.Application.Models.Dtos.Conversation can break ChitChat.Application.Services.Interface, while a change to ChitChat.Application.Services.Interface can't break ChitChat.Application.Models.Dtos.Conversation.
- Position
- Below the diagonal: ChitChat.Application.Services.Interface uses a module listed above it, which is the healthy direction.
21→15 ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.Post✕
- Connections
- 4 pairs of types, where a type in ChitChat.Application.Services.Interface uses a type in ChitChat.Application.Models.Dtos.Post.
- The types involved
ChitChat.Application.Services.Interface.IPostService→ChitChat.Application.Models.Dtos.Post.PostDtoChitChat.Application.Services.Interface.IPostService→ChitChat.Application.Models.Dtos.Post.PostSearchQueryDtoChitChat.Application.Services.Interface.IPostService→ChitChat.Application.Models.Dtos.Post.PostUserSearchQueryDtoChitChat.Application.Services.Interface.IPostService→ChitChat.Application.Models.Dtos.Post.UpdatePostRequestDto
- Direction
- ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.Post, so a change to ChitChat.Application.Models.Dtos.Post can break ChitChat.Application.Services.Interface, while a change to ChitChat.Application.Services.Interface can't break ChitChat.Application.Models.Dtos.Post.
- Position
- Below the diagonal: ChitChat.Application.Services.Interface uses a module listed above it, which is the healthy direction.
21→18 ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.Notification✕
- Connections
- 4 pairs of types, where a type in ChitChat.Application.Services.Interface uses a type in ChitChat.Application.Models.Dtos.Notification.
- The types involved
ChitChat.Application.Services.Interface.INotificationService→ChitChat.Application.Models.Dtos.Notification.CreateCommentNotificationDtoChitChat.Application.Services.Interface.INotificationService→ChitChat.Application.Models.Dtos.Notification.CreatePostNotificationDtoChitChat.Application.Services.Interface.INotificationService→ChitChat.Application.Models.Dtos.Notification.CreateUserNotificationDtoChitChat.Application.Services.Interface.INotificationService→ChitChat.Application.Models.Dtos.Notification.NotificationDto
- Direction
- ChitChat.Application.Services.Interface uses ChitChat.Application.Models.Dtos.Notification, so a change to ChitChat.Application.Models.Dtos.Notification can break ChitChat.Application.Services.Interface, while a change to ChitChat.Application.Services.Interface can't break ChitChat.Application.Models.Dtos.Notification.
- Position
- Below the diagonal: ChitChat.Application.Services.Interface uses a module listed above it, which is the healthy direction.
22→9 ChitChat.Application.SignalR.Interface uses ChitChat.Application.Models.Dtos.Message✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.SignalR.Interface uses a type in ChitChat.Application.Models.Dtos.Message.
- The types involved
ChitChat.Application.SignalR.Interface.IConversationNotificationService→ChitChat.Application.Models.Dtos.Message.MessageDto
- Direction
- ChitChat.Application.SignalR.Interface uses ChitChat.Application.Models.Dtos.Message, so a change to ChitChat.Application.Models.Dtos.Message can break ChitChat.Application.SignalR.Interface, while a change to ChitChat.Application.SignalR.Interface can't break ChitChat.Application.Models.Dtos.Message.
- Position
- Below the diagonal: ChitChat.Application.SignalR.Interface uses a module listed above it, which is the healthy direction.
22→14 ChitChat.Application.SignalR.Interface uses ChitChat.Application.Models.Dtos.Conversation✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.SignalR.Interface uses a type in ChitChat.Application.Models.Dtos.Conversation.
- The types involved
ChitChat.Application.SignalR.Interface.IUserNotificationService→ChitChat.Application.Models.Dtos.Conversation.ConversationDto
- Direction
- ChitChat.Application.SignalR.Interface uses ChitChat.Application.Models.Dtos.Conversation, so a change to ChitChat.Application.Models.Dtos.Conversation can break ChitChat.Application.SignalR.Interface, while a change to ChitChat.Application.SignalR.Interface can't break ChitChat.Application.Models.Dtos.Conversation.
- Position
- Below the diagonal: ChitChat.Application.SignalR.Interface uses a module listed above it, which is the healthy direction.
22→18 ChitChat.Application.SignalR.Interface uses ChitChat.Application.Models.Dtos.Notification✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.SignalR.Interface uses a type in ChitChat.Application.Models.Dtos.Notification.
- The types involved
ChitChat.Application.SignalR.Interface.IUserNotificationService→ChitChat.Application.Models.Dtos.Notification.NotificationDto
- Direction
- ChitChat.Application.SignalR.Interface uses ChitChat.Application.Models.Dtos.Notification, so a change to ChitChat.Application.Models.Dtos.Notification can break ChitChat.Application.SignalR.Interface, while a change to ChitChat.Application.SignalR.Interface can't break ChitChat.Application.Models.Dtos.Notification.
- Position
- Below the diagonal: ChitChat.Application.SignalR.Interface uses a module listed above it, which is the healthy direction.
23→19 ChitChat.Domain.Enums uses ChitChat.Domain.Entities.SystemEntities✕
- Connections
- 1 pair of types, where a type in ChitChat.Domain.Enums uses a type in ChitChat.Domain.Entities.SystemEntities.
- The types involved
ChitChat.Domain.Enums.InteractionTypePoint→ChitChat.Domain.Entities.SystemEntities.UserInteraction
- Direction
- ChitChat.Domain.Enums uses ChitChat.Domain.Entities.SystemEntities, so a change to ChitChat.Domain.Entities.SystemEntities can break ChitChat.Domain.Enums, while a change to ChitChat.Domain.Enums can't break ChitChat.Domain.Entities.SystemEntities.
- Position
- Below the diagonal: ChitChat.Domain.Enums uses a module listed above it, which is the healthy direction.
24→9 ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient uses ChitChat.Application.Models.Dtos.Message✕
- Connections
- 1 pair of types, where a type in ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient uses a type in ChitChat.Application.Models.Dtos.Message.
- The types involved
ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient.IConversationClient→ChitChat.Application.Models.Dtos.Message.MessageDto
- Direction
- ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient uses ChitChat.Application.Models.Dtos.Message, so a change to ChitChat.Application.Models.Dtos.Message can break ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient, while a change to ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient can't break ChitChat.Application.Models.Dtos.Message.
- Position
- Below the diagonal: ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient uses a module listed above it, which is the healthy direction.
24→14 ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient uses ChitChat.Application.Models.Dtos.Conversation✕
- Connections
- 1 pair of types, where a type in ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient uses a type in ChitChat.Application.Models.Dtos.Conversation.
- The types involved
ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient.IUserClient→ChitChat.Application.Models.Dtos.Conversation.ConversationDto
- Direction
- ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient uses ChitChat.Application.Models.Dtos.Conversation, so a change to ChitChat.Application.Models.Dtos.Conversation can break ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient, while a change to ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient can't break ChitChat.Application.Models.Dtos.Conversation.
- Position
- Below the diagonal: ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient uses a module listed above it, which is the healthy direction.
24→18 ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient uses ChitChat.Application.Models.Dtos.Notification✕
- Connections
- 1 pair of types, where a type in ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient uses a type in ChitChat.Application.Models.Dtos.Notification.
- The types involved
ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient.IUserClient→ChitChat.Application.Models.Dtos.Notification.NotificationDto
- Direction
- ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient uses ChitChat.Application.Models.Dtos.Notification, so a change to ChitChat.Application.Models.Dtos.Notification can break ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient, while a change to ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient can't break ChitChat.Application.Models.Dtos.Notification.
- Position
- Below the diagonal: ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient uses a module listed above it, which is the healthy direction.
25→16 ChitChat.Application.MachineLearning.Services uses ChitChat.Domain.Entities.PostEntities✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.MachineLearning.Services uses a type in ChitChat.Domain.Entities.PostEntities.
- The types involved
ChitChat.Application.MachineLearning.Services.TrainingModelService→ChitChat.Domain.Entities.PostEntities.Post
- Direction
- ChitChat.Application.MachineLearning.Services uses ChitChat.Domain.Entities.PostEntities, so a change to ChitChat.Domain.Entities.PostEntities can break ChitChat.Application.MachineLearning.Services, while a change to ChitChat.Application.MachineLearning.Services can't break ChitChat.Domain.Entities.PostEntities.
- Position
- Below the diagonal: ChitChat.Application.MachineLearning.Services uses a module listed above it, which is the healthy direction.
25→17 ChitChat.Application.MachineLearning.Services uses ChitChat.Application.MachineLearning.Models✕
- Connections
- 2 pairs of types, where a type in ChitChat.Application.MachineLearning.Services uses a type in ChitChat.Application.MachineLearning.Models.
- The types involved
ChitChat.Application.MachineLearning.Services.TrainingModelService→ChitChat.Application.MachineLearning.Models.ResponseRecommendationModelChitChat.Application.MachineLearning.Services.TrainingModelService→ChitChat.Application.MachineLearning.Models.UserInteractionModelItem
- Direction
- ChitChat.Application.MachineLearning.Services uses ChitChat.Application.MachineLearning.Models, so a change to ChitChat.Application.MachineLearning.Models can break ChitChat.Application.MachineLearning.Services, while a change to ChitChat.Application.MachineLearning.Services can't break ChitChat.Application.MachineLearning.Models.
- Position
- Below the diagonal: ChitChat.Application.MachineLearning.Services uses a module listed above it, which is the healthy direction.
25→20 ChitChat.Application.MachineLearning.Services uses ChitChat.Application.MachineLearning.Services.Interface✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.MachineLearning.Services uses a type in ChitChat.Application.MachineLearning.Services.Interface.
- The types involved
ChitChat.Application.MachineLearning.Services.TrainingModelService→ChitChat.Application.MachineLearning.Services.Interface.ITrainingModelService
- Direction
- ChitChat.Application.MachineLearning.Services uses ChitChat.Application.MachineLearning.Services.Interface, so a change to ChitChat.Application.MachineLearning.Services.Interface can break ChitChat.Application.MachineLearning.Services, while a change to ChitChat.Application.MachineLearning.Services can't break ChitChat.Application.MachineLearning.Services.Interface.
- Position
- Below the diagonal: ChitChat.Application.MachineLearning.Services uses a module listed above it, which is the healthy direction.
26→23 ChitChat.Domain.Identity uses ChitChat.Domain.Enums✕
- Connections
- 1 pair of types, where a type in ChitChat.Domain.Identity uses a type in ChitChat.Domain.Enums.
- The types involved
ChitChat.Domain.Identity.UserApplication→ChitChat.Domain.Enums.UserStatus
- Direction
- ChitChat.Domain.Identity uses ChitChat.Domain.Enums, so a change to ChitChat.Domain.Enums can break ChitChat.Domain.Identity, while a change to ChitChat.Domain.Identity can't break ChitChat.Domain.Enums.
- Position
- Below the diagonal: ChitChat.Domain.Identity uses a module listed above it, which is the healthy direction.
27→9 ChitChat.Infrastructure.SignalR.Services uses ChitChat.Application.Models.Dtos.Message✕
- Connections
- 1 pair of types, where a type in ChitChat.Infrastructure.SignalR.Services uses a type in ChitChat.Application.Models.Dtos.Message.
- The types involved
ChitChat.Infrastructure.SignalR.Services.ConversationNotificationService→ChitChat.Application.Models.Dtos.Message.MessageDto
- Direction
- ChitChat.Infrastructure.SignalR.Services uses ChitChat.Application.Models.Dtos.Message, so a change to ChitChat.Application.Models.Dtos.Message can break ChitChat.Infrastructure.SignalR.Services, while a change to ChitChat.Infrastructure.SignalR.Services can't break ChitChat.Application.Models.Dtos.Message.
- Position
- Below the diagonal: ChitChat.Infrastructure.SignalR.Services uses a module listed above it, which is the healthy direction.
27→14 ChitChat.Infrastructure.SignalR.Services uses ChitChat.Application.Models.Dtos.Conversation✕
- Connections
- 1 pair of types, where a type in ChitChat.Infrastructure.SignalR.Services uses a type in ChitChat.Application.Models.Dtos.Conversation.
- The types involved
ChitChat.Infrastructure.SignalR.Services.UserNotificationService→ChitChat.Application.Models.Dtos.Conversation.ConversationDto
- Direction
- ChitChat.Infrastructure.SignalR.Services uses ChitChat.Application.Models.Dtos.Conversation, so a change to ChitChat.Application.Models.Dtos.Conversation can break ChitChat.Infrastructure.SignalR.Services, while a change to ChitChat.Infrastructure.SignalR.Services can't break ChitChat.Application.Models.Dtos.Conversation.
- Position
- Below the diagonal: ChitChat.Infrastructure.SignalR.Services uses a module listed above it, which is the healthy direction.
27→18 ChitChat.Infrastructure.SignalR.Services uses ChitChat.Application.Models.Dtos.Notification✕
- Connections
- 1 pair of types, where a type in ChitChat.Infrastructure.SignalR.Services uses a type in ChitChat.Application.Models.Dtos.Notification.
- The types involved
ChitChat.Infrastructure.SignalR.Services.UserNotificationService→ChitChat.Application.Models.Dtos.Notification.NotificationDto
- Direction
- ChitChat.Infrastructure.SignalR.Services uses ChitChat.Application.Models.Dtos.Notification, so a change to ChitChat.Application.Models.Dtos.Notification can break ChitChat.Infrastructure.SignalR.Services, while a change to ChitChat.Infrastructure.SignalR.Services can't break ChitChat.Application.Models.Dtos.Notification.
- Position
- Below the diagonal: ChitChat.Infrastructure.SignalR.Services uses a module listed above it, which is the healthy direction.
27→22 ChitChat.Infrastructure.SignalR.Services uses ChitChat.Application.SignalR.Interface✕
- Connections
- 2 pairs of types, where a type in ChitChat.Infrastructure.SignalR.Services uses a type in ChitChat.Application.SignalR.Interface.
- The types involved
ChitChat.Infrastructure.SignalR.Services.ConversationNotificationService→ChitChat.Application.SignalR.Interface.IConversationNotificationServiceChitChat.Infrastructure.SignalR.Services.UserNotificationService→ChitChat.Application.SignalR.Interface.IUserNotificationService
- Direction
- ChitChat.Infrastructure.SignalR.Services uses ChitChat.Application.SignalR.Interface, so a change to ChitChat.Application.SignalR.Interface can break ChitChat.Infrastructure.SignalR.Services, while a change to ChitChat.Infrastructure.SignalR.Services can't break ChitChat.Application.SignalR.Interface.
- Position
- Below the diagonal: ChitChat.Infrastructure.SignalR.Services uses a module listed above it, which is the healthy direction.
27→24 ChitChat.Infrastructure.SignalR.Services uses ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient✕
- Connections
- 2 pairs of types, where a type in ChitChat.Infrastructure.SignalR.Services uses a type in ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient.
- The types involved
ChitChat.Infrastructure.SignalR.Services.ConversationNotificationService→ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient.IConversationClientChitChat.Infrastructure.SignalR.Services.UserNotificationService→ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient.IUserClient
- Direction
- ChitChat.Infrastructure.SignalR.Services uses ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient, so a change to ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient can break ChitChat.Infrastructure.SignalR.Services, while a change to ChitChat.Infrastructure.SignalR.Services can't break ChitChat.Infrastructure.SignalR.Hubs.InterfaceClient.
- Position
- Below the diagonal: ChitChat.Infrastructure.SignalR.Services uses a module listed above it, which is the healthy direction.
28→13 ChitChat.Application.Helpers uses ChitChat.Domain.Entities✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Helpers uses a type in ChitChat.Domain.Entities.
- The types involved
ChitChat.Application.Helpers.ITokenService→ChitChat.Domain.Entities.LoginHistory
- Direction
- ChitChat.Application.Helpers uses ChitChat.Domain.Entities, so a change to ChitChat.Domain.Entities can break ChitChat.Application.Helpers, while a change to ChitChat.Application.Helpers can't break ChitChat.Domain.Entities.
- Position
- Below the diagonal: ChitChat.Application.Helpers uses a module listed above it, which is the healthy direction.
28→15 ChitChat.Application.Helpers uses ChitChat.Application.Models.Dtos.Post✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Helpers uses a type in ChitChat.Application.Models.Dtos.Post.
- The types involved
ChitChat.Application.Helpers.ICloudinaryService→ChitChat.Application.Models.Dtos.Post.PostMediaDto
- Direction
- ChitChat.Application.Helpers uses ChitChat.Application.Models.Dtos.Post, so a change to ChitChat.Application.Models.Dtos.Post can break ChitChat.Application.Helpers, while a change to ChitChat.Application.Helpers can't break ChitChat.Application.Models.Dtos.Post.
- Position
- Below the diagonal: ChitChat.Application.Helpers uses a module listed above it, which is the healthy direction.
28→26 ChitChat.Application.Helpers uses ChitChat.Domain.Identity✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Helpers uses a type in ChitChat.Domain.Identity.
- The types involved
ChitChat.Application.Helpers.ITokenService→ChitChat.Domain.Identity.UserApplication
- Direction
- ChitChat.Application.Helpers uses ChitChat.Domain.Identity, so a change to ChitChat.Domain.Identity can break ChitChat.Application.Helpers, while a change to ChitChat.Application.Helpers can't break ChitChat.Domain.Identity.
- Position
- Below the diagonal: ChitChat.Application.Helpers uses a module listed above it, which is the healthy direction.
29→13 ChitChat.Domain.Entities.ChatEntities uses ChitChat.Domain.Entities✕
- Connections
- 1 pair of types, where a type in ChitChat.Domain.Entities.ChatEntities uses a type in ChitChat.Domain.Entities.
- The types involved
ChitChat.Domain.Entities.ChatEntities.ConversationDetail→ChitChat.Domain.Entities.BaseEntity
- Direction
- ChitChat.Domain.Entities.ChatEntities uses ChitChat.Domain.Entities, so a change to ChitChat.Domain.Entities can break ChitChat.Domain.Entities.ChatEntities, while a change to ChitChat.Domain.Entities.ChatEntities can't break ChitChat.Domain.Entities.
- Position
- Below the diagonal: ChitChat.Domain.Entities.ChatEntities uses a module listed above it, which is the healthy direction.
29→26 ChitChat.Domain.Entities.ChatEntities uses ChitChat.Domain.Identity✕
- Connections
- 1 pair of types, where a type in ChitChat.Domain.Entities.ChatEntities uses a type in ChitChat.Domain.Identity.
- The types involved
ChitChat.Domain.Entities.ChatEntities.ConversationDetail→ChitChat.Domain.Identity.UserApplication
- Direction
- ChitChat.Domain.Entities.ChatEntities uses ChitChat.Domain.Identity, so a change to ChitChat.Domain.Identity can break ChitChat.Domain.Entities.ChatEntities, while a change to ChitChat.Domain.Entities.ChatEntities can't break ChitChat.Domain.Identity.
- Position
- Below the diagonal: ChitChat.Domain.Entities.ChatEntities uses a module listed above it, which is the healthy direction.
29→33 ChitChat.Domain.Entities.ChatEntities uses (global) part of a loop✕
- Connections
- 1 pair of types, where a type in ChitChat.Domain.Entities.ChatEntities uses a type in (global).
- The types involved
ChitChat.Domain.Entities.ChatEntities.ConversationDetail→Conversation
- Direction
- ChitChat.Domain.Entities.ChatEntities uses (global), so a change to (global) can break ChitChat.Domain.Entities.ChatEntities, while a change to ChitChat.Domain.Entities.ChatEntities can't break (global).
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→13 ChitChat.Domain.Entities.PostEntities.Reaction uses ChitChat.Domain.Entities✕
- Connections
- 2 pairs of types, where a type in ChitChat.Domain.Entities.PostEntities.Reaction uses a type in ChitChat.Domain.Entities.
- The types involved
ChitChat.Domain.Entities.PostEntities.Reaction.ReactionComment→ChitChat.Domain.Entities.BaseAuditedEntityChitChat.Domain.Entities.PostEntities.Reaction.ReactionPost→ChitChat.Domain.Entities.BaseAuditedEntity
- Direction
- ChitChat.Domain.Entities.PostEntities.Reaction uses ChitChat.Domain.Entities, so a change to ChitChat.Domain.Entities can break ChitChat.Domain.Entities.PostEntities.Reaction, while a change to ChitChat.Domain.Entities.PostEntities.Reaction can't break ChitChat.Domain.Entities.
- Position
- Below the diagonal: ChitChat.Domain.Entities.PostEntities.Reaction uses a module listed above it, which is the healthy direction.
30→16 ChitChat.Domain.Entities.PostEntities.Reaction uses ChitChat.Domain.Entities.PostEntities✕
- Connections
- 2 pairs of types, where a type in ChitChat.Domain.Entities.PostEntities.Reaction uses a type in ChitChat.Domain.Entities.PostEntities.
- The types involved
ChitChat.Domain.Entities.PostEntities.Reaction.ReactionComment→ChitChat.Domain.Entities.PostEntities.CommentChitChat.Domain.Entities.PostEntities.Reaction.ReactionPost→ChitChat.Domain.Entities.PostEntities.Post
- Direction
- ChitChat.Domain.Entities.PostEntities.Reaction uses ChitChat.Domain.Entities.PostEntities, so a change to ChitChat.Domain.Entities.PostEntities can break ChitChat.Domain.Entities.PostEntities.Reaction, while a change to ChitChat.Domain.Entities.PostEntities.Reaction can't break ChitChat.Domain.Entities.PostEntities.
- Position
- Below the diagonal: ChitChat.Domain.Entities.PostEntities.Reaction uses a module listed above it, which is the healthy direction.
30→26 ChitChat.Domain.Entities.PostEntities.Reaction uses ChitChat.Domain.Identity✕
- Connections
- 2 pairs of types, where a type in ChitChat.Domain.Entities.PostEntities.Reaction uses a type in ChitChat.Domain.Identity.
- The types involved
ChitChat.Domain.Entities.PostEntities.Reaction.ReactionComment→ChitChat.Domain.Identity.UserApplicationChitChat.Domain.Entities.PostEntities.Reaction.ReactionPost→ChitChat.Domain.Identity.UserApplication
- Direction
- ChitChat.Domain.Entities.PostEntities.Reaction uses ChitChat.Domain.Identity, so a change to ChitChat.Domain.Identity can break ChitChat.Domain.Entities.PostEntities.Reaction, while a change to ChitChat.Domain.Entities.PostEntities.Reaction can't break ChitChat.Domain.Identity.
- Position
- Below the diagonal: ChitChat.Domain.Entities.PostEntities.Reaction uses a module listed above it, which is the healthy direction.
31→13 ChitChat.Domain.Entities.SystemEntities.Notification uses ChitChat.Domain.Entities✕
- Connections
- 1 pair of types, where a type in ChitChat.Domain.Entities.SystemEntities.Notification uses a type in ChitChat.Domain.Entities.
- The types involved
ChitChat.Domain.Entities.SystemEntities.Notification.Notification→ChitChat.Domain.Entities.BaseAuditedEntity
- Direction
- ChitChat.Domain.Entities.SystemEntities.Notification uses ChitChat.Domain.Entities, so a change to ChitChat.Domain.Entities can break ChitChat.Domain.Entities.SystemEntities.Notification, while a change to ChitChat.Domain.Entities.SystemEntities.Notification can't break ChitChat.Domain.Entities.
- Position
- Below the diagonal: ChitChat.Domain.Entities.SystemEntities.Notification uses a module listed above it, which is the healthy direction.
31→16 ChitChat.Domain.Entities.SystemEntities.Notification uses ChitChat.Domain.Entities.PostEntities✕
- Connections
- 2 pairs of types, where a type in ChitChat.Domain.Entities.SystemEntities.Notification uses a type in ChitChat.Domain.Entities.PostEntities.
- The types involved
ChitChat.Domain.Entities.SystemEntities.Notification.CommentNotification→ChitChat.Domain.Entities.PostEntities.CommentChitChat.Domain.Entities.SystemEntities.Notification.PostNotification→ChitChat.Domain.Entities.PostEntities.Post
- Direction
- ChitChat.Domain.Entities.SystemEntities.Notification uses ChitChat.Domain.Entities.PostEntities, so a change to ChitChat.Domain.Entities.PostEntities can break ChitChat.Domain.Entities.SystemEntities.Notification, while a change to ChitChat.Domain.Entities.SystemEntities.Notification can't break ChitChat.Domain.Entities.PostEntities.
- Position
- Below the diagonal: ChitChat.Domain.Entities.SystemEntities.Notification uses a module listed above it, which is the healthy direction.
31→26 ChitChat.Domain.Entities.SystemEntities.Notification uses ChitChat.Domain.Identity✕
- Connections
- 1 pair of types, where a type in ChitChat.Domain.Entities.SystemEntities.Notification uses a type in ChitChat.Domain.Identity.
- The types involved
ChitChat.Domain.Entities.SystemEntities.Notification.Notification→ChitChat.Domain.Identity.UserApplication
- Direction
- ChitChat.Domain.Entities.SystemEntities.Notification uses ChitChat.Domain.Identity, so a change to ChitChat.Domain.Identity can break ChitChat.Domain.Entities.SystemEntities.Notification, while a change to ChitChat.Domain.Entities.SystemEntities.Notification can't break ChitChat.Domain.Identity.
- Position
- Below the diagonal: ChitChat.Domain.Entities.SystemEntities.Notification uses a module listed above it, which is the healthy direction.
32→13 ChitChat.Domain.Entities.UserEntities uses ChitChat.Domain.Entities✕
- Connections
- 3 pairs of types, where a type in ChitChat.Domain.Entities.UserEntities uses a type in ChitChat.Domain.Entities.
- The types involved
ChitChat.Domain.Entities.UserEntities.Profile→ChitChat.Domain.Entities.BaseEntityChitChat.Domain.Entities.UserEntities.UserFollower→ChitChat.Domain.Entities.BaseEntityChitChat.Domain.Entities.UserEntities.UserFollowerRequest→ChitChat.Domain.Entities.BaseEntity
- Direction
- ChitChat.Domain.Entities.UserEntities uses ChitChat.Domain.Entities, so a change to ChitChat.Domain.Entities can break ChitChat.Domain.Entities.UserEntities, while a change to ChitChat.Domain.Entities.UserEntities can't break ChitChat.Domain.Entities.
- Position
- Below the diagonal: ChitChat.Domain.Entities.UserEntities uses a module listed above it, which is the healthy direction.
32→26 ChitChat.Domain.Entities.UserEntities uses ChitChat.Domain.Identity✕
- Connections
- 3 pairs of types, where a type in ChitChat.Domain.Entities.UserEntities uses a type in ChitChat.Domain.Identity.
- The types involved
ChitChat.Domain.Entities.UserEntities.Profile→ChitChat.Domain.Identity.UserApplicationChitChat.Domain.Entities.UserEntities.UserFollower→ChitChat.Domain.Identity.UserApplicationChitChat.Domain.Entities.UserEntities.UserFollowerRequest→ChitChat.Domain.Identity.UserApplication
- Direction
- ChitChat.Domain.Entities.UserEntities uses ChitChat.Domain.Identity, so a change to ChitChat.Domain.Identity can break ChitChat.Domain.Entities.UserEntities, while a change to ChitChat.Domain.Entities.UserEntities can't break ChitChat.Domain.Identity.
- Position
- Below the diagonal: ChitChat.Domain.Entities.UserEntities uses a module listed above it, which is the healthy direction.
33→13 (global) uses ChitChat.Domain.Entities✕
- Connections
- 2 pairs of types, where a type in (global) uses a type in ChitChat.Domain.Entities.
- The types involved
Conversation→ChitChat.Domain.Entities.BaseAuditedEntityMessage→ChitChat.Domain.Entities.BaseAuditedEntity
- Direction
- (global) uses ChitChat.Domain.Entities, so a change to ChitChat.Domain.Entities can break (global), while a change to (global) can't break ChitChat.Domain.Entities.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
33→26 (global) uses ChitChat.Domain.Identity✕
- Connections
- 1 pair of types, where a type in (global) uses a type in ChitChat.Domain.Identity.
- The types involved
Message→ChitChat.Domain.Identity.UserApplication
- Direction
- (global) uses ChitChat.Domain.Identity, so a change to ChitChat.Domain.Identity can break (global), while a change to (global) can't break ChitChat.Domain.Identity.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
33→29 (global) uses ChitChat.Domain.Entities.ChatEntities✕
- Connections
- 1 pair of types, where a type in (global) uses a type in ChitChat.Domain.Entities.ChatEntities.
- The types involved
Conversation→ChitChat.Domain.Entities.ChatEntities.ConversationDetail
- Direction
- (global) uses ChitChat.Domain.Entities.ChatEntities, so a change to ChitChat.Domain.Entities.ChatEntities can break (global), while a change to (global) can't break ChitChat.Domain.Entities.ChatEntities.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
34→13 ChitChat.Infrastructure.Services uses ChitChat.Domain.Entities✕
- Connections
- 1 pair of types, where a type in ChitChat.Infrastructure.Services uses a type in ChitChat.Domain.Entities.
- The types involved
ChitChat.Infrastructure.Services.TokenService→ChitChat.Domain.Entities.LoginHistory
- Direction
- ChitChat.Infrastructure.Services uses ChitChat.Domain.Entities, so a change to ChitChat.Domain.Entities can break ChitChat.Infrastructure.Services, while a change to ChitChat.Infrastructure.Services can't break ChitChat.Domain.Entities.
- Position
- Below the diagonal: ChitChat.Infrastructure.Services uses a module listed above it, which is the healthy direction.
34→15 ChitChat.Infrastructure.Services uses ChitChat.Application.Models.Dtos.Post✕
- Connections
- 1 pair of types, where a type in ChitChat.Infrastructure.Services uses a type in ChitChat.Application.Models.Dtos.Post.
- The types involved
ChitChat.Infrastructure.Services.CloudinaryService→ChitChat.Application.Models.Dtos.Post.PostMediaDto
- Direction
- ChitChat.Infrastructure.Services uses ChitChat.Application.Models.Dtos.Post, so a change to ChitChat.Application.Models.Dtos.Post can break ChitChat.Infrastructure.Services, while a change to ChitChat.Infrastructure.Services can't break ChitChat.Application.Models.Dtos.Post.
- Position
- Below the diagonal: ChitChat.Infrastructure.Services uses a module listed above it, which is the healthy direction.
34→26 ChitChat.Infrastructure.Services uses ChitChat.Domain.Identity✕
- Connections
- 1 pair of types, where a type in ChitChat.Infrastructure.Services uses a type in ChitChat.Domain.Identity.
- The types involved
ChitChat.Infrastructure.Services.TokenService→ChitChat.Domain.Identity.UserApplication
- Direction
- ChitChat.Infrastructure.Services uses ChitChat.Domain.Identity, so a change to ChitChat.Domain.Identity can break ChitChat.Infrastructure.Services, while a change to ChitChat.Infrastructure.Services can't break ChitChat.Domain.Identity.
- Position
- Below the diagonal: ChitChat.Infrastructure.Services uses a module listed above it, which is the healthy direction.
34→28 ChitChat.Infrastructure.Services uses ChitChat.Application.Helpers✕
- Connections
- 3 pairs of types, where a type in ChitChat.Infrastructure.Services uses a type in ChitChat.Application.Helpers.
- The types involved
ChitChat.Infrastructure.Services.ClaimService→ChitChat.Application.Helpers.IClaimServiceChitChat.Infrastructure.Services.CloudinaryService→ChitChat.Application.Helpers.ICloudinaryServiceChitChat.Infrastructure.Services.TokenService→ChitChat.Application.Helpers.ITokenService
- Direction
- ChitChat.Infrastructure.Services uses ChitChat.Application.Helpers, so a change to ChitChat.Application.Helpers can break ChitChat.Infrastructure.Services, while a change to ChitChat.Infrastructure.Services can't break ChitChat.Application.Helpers.
- Position
- Below the diagonal: ChitChat.Infrastructure.Services uses a module listed above it, which is the healthy direction.
35→13 ChitChat.DataAccess.Configurations uses ChitChat.Domain.Entities✕
- Connections
- 1 pair of types, where a type in ChitChat.DataAccess.Configurations uses a type in ChitChat.Domain.Entities.
- The types involved
ChitChat.DataAccess.Configurations.LoginHistoryConfiguration→ChitChat.Domain.Entities.LoginHistory
- Direction
- ChitChat.DataAccess.Configurations uses ChitChat.Domain.Entities, so a change to ChitChat.Domain.Entities can break ChitChat.DataAccess.Configurations, while a change to ChitChat.DataAccess.Configurations can't break ChitChat.Domain.Entities.
- Position
- Below the diagonal: ChitChat.DataAccess.Configurations uses a module listed above it, which is the healthy direction.
35→16 ChitChat.DataAccess.Configurations uses ChitChat.Domain.Entities.PostEntities✕
- Connections
- 4 pairs of types, where a type in ChitChat.DataAccess.Configurations uses a type in ChitChat.Domain.Entities.PostEntities.
- The types involved
ChitChat.DataAccess.Configurations.CommentConfiguration→ChitChat.Domain.Entities.PostEntities.CommentChitChat.DataAccess.Configurations.PostConfiguration→ChitChat.Domain.Entities.PostEntities.PostChitChat.DataAccess.Configurations.PostDetailTagConfiguration→ChitChat.Domain.Entities.PostEntities.PostDetailTagChitChat.DataAccess.Configurations.PostMediaConfiguration→ChitChat.Domain.Entities.PostEntities.PostMedia
- Direction
- ChitChat.DataAccess.Configurations uses ChitChat.Domain.Entities.PostEntities, so a change to ChitChat.Domain.Entities.PostEntities can break ChitChat.DataAccess.Configurations, while a change to ChitChat.DataAccess.Configurations can't break ChitChat.Domain.Entities.PostEntities.
- Position
- Below the diagonal: ChitChat.DataAccess.Configurations uses a module listed above it, which is the healthy direction.
35→19 ChitChat.DataAccess.Configurations uses ChitChat.Domain.Entities.SystemEntities✕
- Connections
- 1 pair of types, where a type in ChitChat.DataAccess.Configurations uses a type in ChitChat.Domain.Entities.SystemEntities.
- The types involved
ChitChat.DataAccess.Configurations.UserInteractionConfiguration→ChitChat.Domain.Entities.SystemEntities.UserInteraction
- Direction
- ChitChat.DataAccess.Configurations uses ChitChat.Domain.Entities.SystemEntities, so a change to ChitChat.Domain.Entities.SystemEntities can break ChitChat.DataAccess.Configurations, while a change to ChitChat.DataAccess.Configurations can't break ChitChat.Domain.Entities.SystemEntities.
- Position
- Below the diagonal: ChitChat.DataAccess.Configurations uses a module listed above it, which is the healthy direction.
35→29 ChitChat.DataAccess.Configurations uses ChitChat.Domain.Entities.ChatEntities✕
- Connections
- 1 pair of types, where a type in ChitChat.DataAccess.Configurations uses a type in ChitChat.Domain.Entities.ChatEntities.
- The types involved
ChitChat.DataAccess.Configurations.ConversationDetailConfiguration→ChitChat.Domain.Entities.ChatEntities.ConversationDetail
- Direction
- ChitChat.DataAccess.Configurations uses ChitChat.Domain.Entities.ChatEntities, so a change to ChitChat.Domain.Entities.ChatEntities can break ChitChat.DataAccess.Configurations, while a change to ChitChat.DataAccess.Configurations can't break ChitChat.Domain.Entities.ChatEntities.
- Position
- Below the diagonal: ChitChat.DataAccess.Configurations uses a module listed above it, which is the healthy direction.
35→30 ChitChat.DataAccess.Configurations uses ChitChat.Domain.Entities.PostEntities.Reaction✕
- Connections
- 2 pairs of types, where a type in ChitChat.DataAccess.Configurations uses a type in ChitChat.Domain.Entities.PostEntities.Reaction.
- The types involved
ChitChat.DataAccess.Configurations.ReactionCommentConfiguration→ChitChat.Domain.Entities.PostEntities.Reaction.ReactionCommentChitChat.DataAccess.Configurations.ReactionPostConfiguration→ChitChat.Domain.Entities.PostEntities.Reaction.ReactionPost
- Direction
- ChitChat.DataAccess.Configurations uses ChitChat.Domain.Entities.PostEntities.Reaction, so a change to ChitChat.Domain.Entities.PostEntities.Reaction can break ChitChat.DataAccess.Configurations, while a change to ChitChat.DataAccess.Configurations can't break ChitChat.Domain.Entities.PostEntities.Reaction.
- Position
- Below the diagonal: ChitChat.DataAccess.Configurations uses a module listed above it, which is the healthy direction.
35→32 ChitChat.DataAccess.Configurations uses ChitChat.Domain.Entities.UserEntities✕
- Connections
- 3 pairs of types, where a type in ChitChat.DataAccess.Configurations uses a type in ChitChat.Domain.Entities.UserEntities.
- The types involved
ChitChat.DataAccess.Configurations.ProfileConfiguration→ChitChat.Domain.Entities.UserEntities.ProfileChitChat.DataAccess.Configurations.UserFollowerConfiguration→ChitChat.Domain.Entities.UserEntities.UserFollowerChitChat.DataAccess.Configurations.UserFollowerRequestConfiguration→ChitChat.Domain.Entities.UserEntities.UserFollowerRequest
- Direction
- ChitChat.DataAccess.Configurations uses ChitChat.Domain.Entities.UserEntities, so a change to ChitChat.Domain.Entities.UserEntities can break ChitChat.DataAccess.Configurations, while a change to ChitChat.DataAccess.Configurations can't break ChitChat.Domain.Entities.UserEntities.
- Position
- Below the diagonal: ChitChat.DataAccess.Configurations uses a module listed above it, which is the healthy direction.
35→33 ChitChat.DataAccess.Configurations uses (global)✕
- Connections
- 2 pairs of types, where a type in ChitChat.DataAccess.Configurations uses a type in (global).
- The types involved
ChitChat.DataAccess.Configurations.ConversationConfiguration→ConversationChitChat.DataAccess.Configurations.MessageConfiguration→Message
- Direction
- ChitChat.DataAccess.Configurations uses (global), so a change to (global) can break ChitChat.DataAccess.Configurations, while a change to ChitChat.DataAccess.Configurations can't break (global).
- Position
- Below the diagonal: ChitChat.DataAccess.Configurations uses a module listed above it, which is the healthy direction.
36→13 ChitChat.DataAccess.Data uses ChitChat.Domain.Entities✕
- Connections
- 1 pair of types, where a type in ChitChat.DataAccess.Data uses a type in ChitChat.Domain.Entities.
- The types involved
ChitChat.DataAccess.Data.ApplicationDbContext→ChitChat.Domain.Entities.LoginHistory
- Direction
- ChitChat.DataAccess.Data uses ChitChat.Domain.Entities, so a change to ChitChat.Domain.Entities can break ChitChat.DataAccess.Data, while a change to ChitChat.DataAccess.Data can't break ChitChat.Domain.Entities.
- Position
- Below the diagonal: ChitChat.DataAccess.Data uses a module listed above it, which is the healthy direction.
36→16 ChitChat.DataAccess.Data uses ChitChat.Domain.Entities.PostEntities✕
- Connections
- 4 pairs of types, where a type in ChitChat.DataAccess.Data uses a type in ChitChat.Domain.Entities.PostEntities.
- The types involved
ChitChat.DataAccess.Data.ApplicationDbContext→ChitChat.Domain.Entities.PostEntities.CommentChitChat.DataAccess.Data.ApplicationDbContext→ChitChat.Domain.Entities.PostEntities.PostChitChat.DataAccess.Data.ApplicationDbContext→ChitChat.Domain.Entities.PostEntities.PostDetailTagChitChat.DataAccess.Data.ApplicationDbContext→ChitChat.Domain.Entities.PostEntities.PostMedia
- Direction
- ChitChat.DataAccess.Data uses ChitChat.Domain.Entities.PostEntities, so a change to ChitChat.Domain.Entities.PostEntities can break ChitChat.DataAccess.Data, while a change to ChitChat.DataAccess.Data can't break ChitChat.Domain.Entities.PostEntities.
- Position
- Below the diagonal: ChitChat.DataAccess.Data uses a module listed above it, which is the healthy direction.
36→19 ChitChat.DataAccess.Data uses ChitChat.Domain.Entities.SystemEntities✕
- Connections
- 1 pair of types, where a type in ChitChat.DataAccess.Data uses a type in ChitChat.Domain.Entities.SystemEntities.
- The types involved
ChitChat.DataAccess.Data.ApplicationDbContext→ChitChat.Domain.Entities.SystemEntities.UserInteraction
- Direction
- ChitChat.DataAccess.Data uses ChitChat.Domain.Entities.SystemEntities, so a change to ChitChat.Domain.Entities.SystemEntities can break ChitChat.DataAccess.Data, while a change to ChitChat.DataAccess.Data can't break ChitChat.Domain.Entities.SystemEntities.
- Position
- Below the diagonal: ChitChat.DataAccess.Data uses a module listed above it, which is the healthy direction.
36→26 ChitChat.DataAccess.Data uses ChitChat.Domain.Identity✕
- Connections
- 3 pairs of types, where a type in ChitChat.DataAccess.Data uses a type in ChitChat.Domain.Identity.
- The types involved
ChitChat.DataAccess.Data.ApplicationDbContext→ChitChat.Domain.Identity.UserApplicationChitChat.DataAccess.Data.DbContextSeed→ChitChat.Domain.Identity.ApplicationRoleChitChat.DataAccess.Data.DbContextSeed→ChitChat.Domain.Identity.UserApplication
- Direction
- ChitChat.DataAccess.Data uses ChitChat.Domain.Identity, so a change to ChitChat.Domain.Identity can break ChitChat.DataAccess.Data, while a change to ChitChat.DataAccess.Data can't break ChitChat.Domain.Identity.
- Position
- Below the diagonal: ChitChat.DataAccess.Data uses a module listed above it, which is the healthy direction.
36→29 ChitChat.DataAccess.Data uses ChitChat.Domain.Entities.ChatEntities✕
- Connections
- 1 pair of types, where a type in ChitChat.DataAccess.Data uses a type in ChitChat.Domain.Entities.ChatEntities.
- The types involved
ChitChat.DataAccess.Data.ApplicationDbContext→ChitChat.Domain.Entities.ChatEntities.ConversationDetail
- Direction
- ChitChat.DataAccess.Data uses ChitChat.Domain.Entities.ChatEntities, so a change to ChitChat.Domain.Entities.ChatEntities can break ChitChat.DataAccess.Data, while a change to ChitChat.DataAccess.Data can't break ChitChat.Domain.Entities.ChatEntities.
- Position
- Below the diagonal: ChitChat.DataAccess.Data uses a module listed above it, which is the healthy direction.
36→30 ChitChat.DataAccess.Data uses ChitChat.Domain.Entities.PostEntities.Reaction✕
- Connections
- 2 pairs of types, where a type in ChitChat.DataAccess.Data uses a type in ChitChat.Domain.Entities.PostEntities.Reaction.
- The types involved
ChitChat.DataAccess.Data.ApplicationDbContext→ChitChat.Domain.Entities.PostEntities.Reaction.ReactionCommentChitChat.DataAccess.Data.ApplicationDbContext→ChitChat.Domain.Entities.PostEntities.Reaction.ReactionPost
- Direction
- ChitChat.DataAccess.Data uses ChitChat.Domain.Entities.PostEntities.Reaction, so a change to ChitChat.Domain.Entities.PostEntities.Reaction can break ChitChat.DataAccess.Data, while a change to ChitChat.DataAccess.Data can't break ChitChat.Domain.Entities.PostEntities.Reaction.
- Position
- Below the diagonal: ChitChat.DataAccess.Data uses a module listed above it, which is the healthy direction.
36→31 ChitChat.DataAccess.Data uses ChitChat.Domain.Entities.SystemEntities.Notification✕
- Connections
- 3 pairs of types, where a type in ChitChat.DataAccess.Data uses a type in ChitChat.Domain.Entities.SystemEntities.Notification.
- The types involved
ChitChat.DataAccess.Data.ApplicationDbContext→ChitChat.Domain.Entities.SystemEntities.Notification.CommentNotificationChitChat.DataAccess.Data.ApplicationDbContext→ChitChat.Domain.Entities.SystemEntities.Notification.PostNotificationChitChat.DataAccess.Data.ApplicationDbContext→ChitChat.Domain.Entities.SystemEntities.Notification.UserNotification
- Direction
- ChitChat.DataAccess.Data uses ChitChat.Domain.Entities.SystemEntities.Notification, so a change to ChitChat.Domain.Entities.SystemEntities.Notification can break ChitChat.DataAccess.Data, while a change to ChitChat.DataAccess.Data can't break ChitChat.Domain.Entities.SystemEntities.Notification.
- Position
- Below the diagonal: ChitChat.DataAccess.Data uses a module listed above it, which is the healthy direction.
36→32 ChitChat.DataAccess.Data uses ChitChat.Domain.Entities.UserEntities✕
- Connections
- 3 pairs of types, where a type in ChitChat.DataAccess.Data uses a type in ChitChat.Domain.Entities.UserEntities.
- The types involved
ChitChat.DataAccess.Data.ApplicationDbContext→ChitChat.Domain.Entities.UserEntities.ProfileChitChat.DataAccess.Data.ApplicationDbContext→ChitChat.Domain.Entities.UserEntities.UserFollowerChitChat.DataAccess.Data.ApplicationDbContext→ChitChat.Domain.Entities.UserEntities.UserFollowerRequest
- Direction
- ChitChat.DataAccess.Data uses ChitChat.Domain.Entities.UserEntities, so a change to ChitChat.Domain.Entities.UserEntities can break ChitChat.DataAccess.Data, while a change to ChitChat.DataAccess.Data can't break ChitChat.Domain.Entities.UserEntities.
- Position
- Below the diagonal: ChitChat.DataAccess.Data uses a module listed above it, which is the healthy direction.
36→33 ChitChat.DataAccess.Data uses (global)✕
- Connections
- 2 pairs of types, where a type in ChitChat.DataAccess.Data uses a type in (global).
- The types involved
ChitChat.DataAccess.Data.ApplicationDbContext→ConversationChitChat.DataAccess.Data.ApplicationDbContext→Message
- Direction
- ChitChat.DataAccess.Data uses (global), so a change to (global) can break ChitChat.DataAccess.Data, while a change to ChitChat.DataAccess.Data can't break (global).
- Position
- Below the diagonal: ChitChat.DataAccess.Data uses a module listed above it, which is the healthy direction.
37→6 ChitChat.DataAccess.Repositories.Interface uses ChitChat.Domain.Common✕
- Connections
- 1 pair of types, where a type in ChitChat.DataAccess.Repositories.Interface uses a type in ChitChat.Domain.Common.
- The types involved
ChitChat.DataAccess.Repositories.Interface.IBaseRepository→ChitChat.Domain.Common.PaginationResponse
- Direction
- ChitChat.DataAccess.Repositories.Interface uses ChitChat.Domain.Common, so a change to ChitChat.Domain.Common can break ChitChat.DataAccess.Repositories.Interface, while a change to ChitChat.DataAccess.Repositories.Interface can't break ChitChat.Domain.Common.
- Position
- Below the diagonal: ChitChat.DataAccess.Repositories.Interface uses a module listed above it, which is the healthy direction.
37→13 ChitChat.DataAccess.Repositories.Interface uses ChitChat.Domain.Entities✕
- Connections
- 2 pairs of types, where a type in ChitChat.DataAccess.Repositories.Interface uses a type in ChitChat.Domain.Entities.
- The types involved
ChitChat.DataAccess.Repositories.Interface.IBaseRepository→ChitChat.Domain.Entities.BaseEntityChitChat.DataAccess.Repositories.Interface.IUserRepository→ChitChat.Domain.Entities.BaseEntity
- Direction
- ChitChat.DataAccess.Repositories.Interface uses ChitChat.Domain.Entities, so a change to ChitChat.Domain.Entities can break ChitChat.DataAccess.Repositories.Interface, while a change to ChitChat.DataAccess.Repositories.Interface can't break ChitChat.Domain.Entities.
- Position
- Below the diagonal: ChitChat.DataAccess.Repositories.Interface uses a module listed above it, which is the healthy direction.
37→17 ChitChat.DataAccess.Repositories.Interface uses ChitChat.Application.MachineLearning.Models✕
- Connections
- 1 pair of types, where a type in ChitChat.DataAccess.Repositories.Interface uses a type in ChitChat.Application.MachineLearning.Models.
- The types involved
ChitChat.DataAccess.Repositories.Interface.IUserInteractionRepository→ChitChat.Application.MachineLearning.Models.UserInteractionModelItem
- Direction
- ChitChat.DataAccess.Repositories.Interface uses ChitChat.Application.MachineLearning.Models, so a change to ChitChat.Application.MachineLearning.Models can break ChitChat.DataAccess.Repositories.Interface, while a change to ChitChat.DataAccess.Repositories.Interface can't break ChitChat.Application.MachineLearning.Models.
- Position
- Below the diagonal: ChitChat.DataAccess.Repositories.Interface uses a module listed above it, which is the healthy direction.
37→26 ChitChat.DataAccess.Repositories.Interface uses ChitChat.Domain.Identity✕
- Connections
- 2 pairs of types, where a type in ChitChat.DataAccess.Repositories.Interface uses a type in ChitChat.Domain.Identity.
- The types involved
ChitChat.DataAccess.Repositories.Interface.IUserFollowerRepository→ChitChat.Domain.Identity.UserApplicationChitChat.DataAccess.Repositories.Interface.IUserRepository→ChitChat.Domain.Identity.UserApplication
- Direction
- ChitChat.DataAccess.Repositories.Interface uses ChitChat.Domain.Identity, so a change to ChitChat.Domain.Identity can break ChitChat.DataAccess.Repositories.Interface, while a change to ChitChat.DataAccess.Repositories.Interface can't break ChitChat.Domain.Identity.
- Position
- Below the diagonal: ChitChat.DataAccess.Repositories.Interface uses a module listed above it, which is the healthy direction.
37→33 ChitChat.DataAccess.Repositories.Interface uses (global)✕
- Connections
- 1 pair of types, where a type in ChitChat.DataAccess.Repositories.Interface uses a type in (global).
- The types involved
ChitChat.DataAccess.Repositories.Interface.IConversationRepository→Conversation
- Direction
- ChitChat.DataAccess.Repositories.Interface uses (global), so a change to (global) can break ChitChat.DataAccess.Repositories.Interface, while a change to ChitChat.DataAccess.Repositories.Interface can't break (global).
- Position
- Below the diagonal: ChitChat.DataAccess.Repositories.Interface uses a module listed above it, which is the healthy direction.
38→1 ChitChat.Application.Services uses ChitChat.Application.Models✕
- Connections
- 3 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Application.Models.
- The types involved
ChitChat.Application.Services.ConversationService→ChitChat.Application.Models.PaginationFilterChitChat.Application.Services.FollowService→ChitChat.Application.Models.PaginationFilterChitChat.Application.Services.NotificationService→ChitChat.Application.Models.PaginationFilter
- Direction
- ChitChat.Application.Services uses ChitChat.Application.Models, so a change to ChitChat.Application.Models can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Application.Models.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→3 ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.Post.CreatePost✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Application.Models.Dtos.Post.CreatePost.
- The types involved
ChitChat.Application.Services.PostService→ChitChat.Application.Models.Dtos.Post.CreatePost.CreatePostRequestDto
- Direction
- ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.Post.CreatePost, so a change to ChitChat.Application.Models.Dtos.Post.CreatePost can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Application.Models.Dtos.Post.CreatePost.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→4 ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.User✕
- Connections
- 4 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Application.Models.Dtos.User.
- The types involved
ChitChat.Application.Services.UserService→ChitChat.Application.Models.Dtos.User.LoginRequestDtoChitChat.Application.Services.UserService→ChitChat.Application.Models.Dtos.User.LoginResponseDtoChitChat.Application.Services.UserService→ChitChat.Application.Models.Dtos.User.RefreshTokenDtoChitChat.Application.Services.UserService→ChitChat.Application.Models.Dtos.User.RegisterationRequestDto
- Direction
- ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.User, so a change to ChitChat.Application.Models.Dtos.User can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Application.Models.Dtos.User.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→9 ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.Message✕
- Connections
- 2 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Application.Models.Dtos.Message.
- The types involved
ChitChat.Application.Services.ConversationService→ChitChat.Application.Models.Dtos.Message.MessageDtoChitChat.Application.Services.ConversationService→ChitChat.Application.Models.Dtos.Message.RequestSendMessageDto
- Direction
- ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.Message, so a change to ChitChat.Application.Models.Dtos.Message can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Application.Models.Dtos.Message.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→10 ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.Post.Comments✕
- Connections
- 2 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Application.Models.Dtos.Post.Comments.
- The types involved
ChitChat.Application.Services.PostService→ChitChat.Application.Models.Dtos.Post.Comments.CommentDtoChitChat.Application.Services.PostService→ChitChat.Application.Models.Dtos.Post.Comments.CommentRequestDto
- Direction
- ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.Post.Comments, so a change to ChitChat.Application.Models.Dtos.Post.Comments can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Application.Models.Dtos.Post.Comments.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→11 ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.User.Follow✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Application.Models.Dtos.User.Follow.
- The types involved
ChitChat.Application.Services.FollowService→ChitChat.Application.Models.Dtos.User.Follow.FollowDto
- Direction
- ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.User.Follow, so a change to ChitChat.Application.Models.Dtos.User.Follow can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Application.Models.Dtos.User.Follow.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→12 ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.User.Profile✕
- Connections
- 3 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Application.Models.Dtos.User.Profile.
- The types involved
ChitChat.Application.Services.ProfileService→ChitChat.Application.Models.Dtos.User.Profile.ProfileDtoChitChat.Application.Services.ProfileService→ChitChat.Application.Models.Dtos.User.Profile.ProfileRequestDtoChitChat.Application.Services.ProfileService→ChitChat.Application.Models.Dtos.User.Profile.ProfileSearchQueryDto
- Direction
- ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.User.Profile, so a change to ChitChat.Application.Models.Dtos.User.Profile can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Application.Models.Dtos.User.Profile.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→13 ChitChat.Application.Services uses ChitChat.Domain.Entities✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Domain.Entities.
- The types involved
ChitChat.Application.Services.UserService→ChitChat.Domain.Entities.LoginHistory
- Direction
- ChitChat.Application.Services uses ChitChat.Domain.Entities, so a change to ChitChat.Domain.Entities can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Domain.Entities.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→14 ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.Conversation✕
- Connections
- 2 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Application.Models.Dtos.Conversation.
- The types involved
ChitChat.Application.Services.ConversationService→ChitChat.Application.Models.Dtos.Conversation.ConversationDetailDtoChitChat.Application.Services.ConversationService→ChitChat.Application.Models.Dtos.Conversation.ConversationDto
- Direction
- ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.Conversation, so a change to ChitChat.Application.Models.Dtos.Conversation can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Application.Models.Dtos.Conversation.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→15 ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.Post✕
- Connections
- 4 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Application.Models.Dtos.Post.
- The types involved
ChitChat.Application.Services.PostService→ChitChat.Application.Models.Dtos.Post.PostDtoChitChat.Application.Services.PostService→ChitChat.Application.Models.Dtos.Post.PostSearchQueryDtoChitChat.Application.Services.PostService→ChitChat.Application.Models.Dtos.Post.PostUserSearchQueryDtoChitChat.Application.Services.PostService→ChitChat.Application.Models.Dtos.Post.UpdatePostRequestDto
- Direction
- ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.Post, so a change to ChitChat.Application.Models.Dtos.Post can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Application.Models.Dtos.Post.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→16 ChitChat.Application.Services uses ChitChat.Domain.Entities.PostEntities✕
- Connections
- 3 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Domain.Entities.PostEntities.
- The types involved
ChitChat.Application.Services.PostService→ChitChat.Domain.Entities.PostEntities.CommentChitChat.Application.Services.PostService→ChitChat.Domain.Entities.PostEntities.PostChitChat.Application.Services.PostService→ChitChat.Domain.Entities.PostEntities.PostMedia
- Direction
- ChitChat.Application.Services uses ChitChat.Domain.Entities.PostEntities, so a change to ChitChat.Domain.Entities.PostEntities can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Domain.Entities.PostEntities.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→18 ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.Notification✕
- Connections
- 4 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Application.Models.Dtos.Notification.
- The types involved
ChitChat.Application.Services.NotificationService→ChitChat.Application.Models.Dtos.Notification.CreateCommentNotificationDtoChitChat.Application.Services.NotificationService→ChitChat.Application.Models.Dtos.Notification.CreatePostNotificationDtoChitChat.Application.Services.NotificationService→ChitChat.Application.Models.Dtos.Notification.CreateUserNotificationDtoChitChat.Application.Services.NotificationService→ChitChat.Application.Models.Dtos.Notification.NotificationDto
- Direction
- ChitChat.Application.Services uses ChitChat.Application.Models.Dtos.Notification, so a change to ChitChat.Application.Models.Dtos.Notification can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Application.Models.Dtos.Notification.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→20 ChitChat.Application.Services uses ChitChat.Application.MachineLearning.Services.Interface✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Application.MachineLearning.Services.Interface.
- The types involved
ChitChat.Application.Services.PostService→ChitChat.Application.MachineLearning.Services.Interface.ITrainingModelService
- Direction
- ChitChat.Application.Services uses ChitChat.Application.MachineLearning.Services.Interface, so a change to ChitChat.Application.MachineLearning.Services.Interface can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Application.MachineLearning.Services.Interface.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→21 ChitChat.Application.Services uses ChitChat.Application.Services.Interface✕
- Connections
- 8 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Application.Services.Interface.
- The types involved
ChitChat.Application.Services.ConversationService→ChitChat.Application.Services.Interface.IConversationServiceChitChat.Application.Services.FollowService→ChitChat.Application.Services.Interface.IFollowServiceChitChat.Application.Services.FollowService→ChitChat.Application.Services.Interface.INotificationServiceChitChat.Application.Services.NotificationService→ChitChat.Application.Services.Interface.INotificationServiceChitChat.Application.Services.PostService→ChitChat.Application.Services.Interface.INotificationServiceChitChat.Application.Services.PostService→ChitChat.Application.Services.Interface.IPostServiceChitChat.Application.Services.ProfileService→ChitChat.Application.Services.Interface.IProfileServiceChitChat.Application.Services.UserService→ChitChat.Application.Services.Interface.IUserService
- Direction
- ChitChat.Application.Services uses ChitChat.Application.Services.Interface, so a change to ChitChat.Application.Services.Interface can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Application.Services.Interface.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→22 ChitChat.Application.Services uses ChitChat.Application.SignalR.Interface✕
- Connections
- 3 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Application.SignalR.Interface.
- The types involved
ChitChat.Application.Services.ConversationService→ChitChat.Application.SignalR.Interface.IConversationNotificationServiceChitChat.Application.Services.ConversationService→ChitChat.Application.SignalR.Interface.IUserNotificationServiceChitChat.Application.Services.NotificationService→ChitChat.Application.SignalR.Interface.IUserNotificationService
- Direction
- ChitChat.Application.Services uses ChitChat.Application.SignalR.Interface, so a change to ChitChat.Application.SignalR.Interface can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Application.SignalR.Interface.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→26 ChitChat.Application.Services uses ChitChat.Domain.Identity✕
- Connections
- 2 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Domain.Identity.
- The types involved
ChitChat.Application.Services.UserService→ChitChat.Domain.Identity.ApplicationRoleChitChat.Application.Services.UserService→ChitChat.Domain.Identity.UserApplication
- Direction
- ChitChat.Application.Services uses ChitChat.Domain.Identity, so a change to ChitChat.Domain.Identity can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Domain.Identity.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→28 ChitChat.Application.Services uses ChitChat.Application.Helpers✕
- Connections
- 8 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Application.Helpers.
- The types involved
ChitChat.Application.Services.ConversationService→ChitChat.Application.Helpers.IClaimServiceChitChat.Application.Services.FollowService→ChitChat.Application.Helpers.IClaimServiceChitChat.Application.Services.NotificationService→ChitChat.Application.Helpers.IClaimServiceChitChat.Application.Services.PostService→ChitChat.Application.Helpers.IClaimServiceChitChat.Application.Services.PostService→ChitChat.Application.Helpers.ICloudinaryServiceChitChat.Application.Services.ProfileService→ChitChat.Application.Helpers.IClaimServiceChitChat.Application.Services.UserService→ChitChat.Application.Helpers.IClaimServiceChitChat.Application.Services.UserService→ChitChat.Application.Helpers.ITokenService
- Direction
- ChitChat.Application.Services uses ChitChat.Application.Helpers, so a change to ChitChat.Application.Helpers can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Application.Helpers.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→29 ChitChat.Application.Services uses ChitChat.Domain.Entities.ChatEntities✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Domain.Entities.ChatEntities.
- The types involved
ChitChat.Application.Services.ConversationService→ChitChat.Domain.Entities.ChatEntities.ConversationDetail
- Direction
- ChitChat.Application.Services uses ChitChat.Domain.Entities.ChatEntities, so a change to ChitChat.Domain.Entities.ChatEntities can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Domain.Entities.ChatEntities.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→30 ChitChat.Application.Services uses ChitChat.Domain.Entities.PostEntities.Reaction✕
- Connections
- 2 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Domain.Entities.PostEntities.Reaction.
- The types involved
ChitChat.Application.Services.PostService→ChitChat.Domain.Entities.PostEntities.Reaction.ReactionCommentChitChat.Application.Services.PostService→ChitChat.Domain.Entities.PostEntities.Reaction.ReactionPost
- Direction
- ChitChat.Application.Services uses ChitChat.Domain.Entities.PostEntities.Reaction, so a change to ChitChat.Domain.Entities.PostEntities.Reaction can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Domain.Entities.PostEntities.Reaction.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→31 ChitChat.Application.Services uses ChitChat.Domain.Entities.SystemEntities.Notification✕
- Connections
- 3 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Domain.Entities.SystemEntities.Notification.
- The types involved
ChitChat.Application.Services.NotificationService→ChitChat.Domain.Entities.SystemEntities.Notification.CommentNotificationChitChat.Application.Services.NotificationService→ChitChat.Domain.Entities.SystemEntities.Notification.PostNotificationChitChat.Application.Services.NotificationService→ChitChat.Domain.Entities.SystemEntities.Notification.UserNotification
- Direction
- ChitChat.Application.Services uses ChitChat.Domain.Entities.SystemEntities.Notification, so a change to ChitChat.Domain.Entities.SystemEntities.Notification can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Domain.Entities.SystemEntities.Notification.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→32 ChitChat.Application.Services uses ChitChat.Domain.Entities.UserEntities✕
- Connections
- 2 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.Domain.Entities.UserEntities.
- The types involved
ChitChat.Application.Services.ProfileService→ChitChat.Domain.Entities.UserEntities.ProfileChitChat.Application.Services.ProfileService→ChitChat.Domain.Entities.UserEntities.UserFollower
- Direction
- ChitChat.Application.Services uses ChitChat.Domain.Entities.UserEntities, so a change to ChitChat.Domain.Entities.UserEntities can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.Domain.Entities.UserEntities.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→33 ChitChat.Application.Services uses (global)✕
- Connections
- 1 pair of types, where a type in ChitChat.Application.Services uses a type in (global).
- The types involved
ChitChat.Application.Services.ConversationService→Message
- Direction
- ChitChat.Application.Services uses (global), so a change to (global) can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break (global).
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
38→37 ChitChat.Application.Services uses ChitChat.DataAccess.Repositories.Interface✕
- Connections
- 17 pairs of types, where a type in ChitChat.Application.Services uses a type in ChitChat.DataAccess.Repositories.Interface.
- The types involved
ChitChat.Application.Services.ConversationService→ChitChat.DataAccess.Repositories.Interface.IBaseRepositoryChitChat.Application.Services.ConversationService→ChitChat.DataAccess.Repositories.Interface.IConversationRepositoryChitChat.Application.Services.ConversationService→ChitChat.DataAccess.Repositories.Interface.IRepositoryFactoryChitChat.Application.Services.ConversationService→ChitChat.DataAccess.Repositories.Interface.IUserRepositoryChitChat.Application.Services.FollowService→ChitChat.DataAccess.Repositories.Interface.IRepositoryFactoryChitChat.Application.Services.FollowService→ChitChat.DataAccess.Repositories.Interface.IUserFollowerRepositoryChitChat.Application.Services.NotificationService→ChitChat.DataAccess.Repositories.Interface.IBaseRepositoryChitChat.Application.Services.NotificationService→ChitChat.DataAccess.Repositories.Interface.IRepositoryFactoryChitChat.Application.Services.PostService→ChitChat.DataAccess.Repositories.Interface.IBaseRepositoryChitChat.Application.Services.PostService→ChitChat.DataAccess.Repositories.Interface.IRepositoryFactoryChitChat.Application.Services.PostService→ChitChat.DataAccess.Repositories.Interface.IUserInteractionRepositoryChitChat.Application.Services.PostService→ChitChat.DataAccess.Repositories.Interface.IUserRepositoryChitChat.Application.Services.ProfileService→ChitChat.DataAccess.Repositories.Interface.IBaseRepositoryChitChat.Application.Services.ProfileService→ChitChat.DataAccess.Repositories.Interface.IUserRepositoryChitChat.Application.Services.UserService→ChitChat.DataAccess.Repositories.Interface.IBaseRepositoryChitChat.Application.Services.UserService→ChitChat.DataAccess.Repositories.Interface.IRepositoryFactoryChitChat.Application.Services.UserService→ChitChat.DataAccess.Repositories.Interface.IUserRepository
- Direction
- ChitChat.Application.Services uses ChitChat.DataAccess.Repositories.Interface, so a change to ChitChat.DataAccess.Repositories.Interface can break ChitChat.Application.Services, while a change to ChitChat.Application.Services can't break ChitChat.DataAccess.Repositories.Interface.
- Position
- Below the diagonal: ChitChat.Application.Services uses a module listed above it, which is the healthy direction.
39→6 ChitChat.DataAccess.Repositories uses ChitChat.Domain.Common✕
- Connections
- 1 pair of types, where a type in ChitChat.DataAccess.Repositories uses a type in ChitChat.Domain.Common.
- The types involved
ChitChat.DataAccess.Repositories.BaseRepository→ChitChat.Domain.Common.PaginationResponse
- Direction
- ChitChat.DataAccess.Repositories uses ChitChat.Domain.Common, so a change to ChitChat.Domain.Common can break ChitChat.DataAccess.Repositories, while a change to ChitChat.DataAccess.Repositories can't break ChitChat.Domain.Common.
- Position
- Below the diagonal: ChitChat.DataAccess.Repositories uses a module listed above it, which is the healthy direction.
39→13 ChitChat.DataAccess.Repositories uses ChitChat.Domain.Entities✕
- Connections
- 2 pairs of types, where a type in ChitChat.DataAccess.Repositories uses a type in ChitChat.Domain.Entities.
- The types involved
ChitChat.DataAccess.Repositories.BaseRepository→ChitChat.Domain.Entities.BaseEntityChitChat.DataAccess.Repositories.UserRepository→ChitChat.Domain.Entities.BaseEntity
- Direction
- ChitChat.DataAccess.Repositories uses ChitChat.Domain.Entities, so a change to ChitChat.Domain.Entities can break ChitChat.DataAccess.Repositories, while a change to ChitChat.DataAccess.Repositories can't break ChitChat.Domain.Entities.
- Position
- Below the diagonal: ChitChat.DataAccess.Repositories uses a module listed above it, which is the healthy direction.
39→17 ChitChat.DataAccess.Repositories uses ChitChat.Application.MachineLearning.Models✕
- Connections
- 1 pair of types, where a type in ChitChat.DataAccess.Repositories uses a type in ChitChat.Application.MachineLearning.Models.
- The types involved
ChitChat.DataAccess.Repositories.UserInteractionRepository→ChitChat.Application.MachineLearning.Models.UserInteractionModelItem
- Direction
- ChitChat.DataAccess.Repositories uses ChitChat.Application.MachineLearning.Models, so a change to ChitChat.Application.MachineLearning.Models can break ChitChat.DataAccess.Repositories, while a change to ChitChat.DataAccess.Repositories can't break ChitChat.Application.MachineLearning.Models.
- Position
- Below the diagonal: ChitChat.DataAccess.Repositories uses a module listed above it, which is the healthy direction.
39→26 ChitChat.DataAccess.Repositories uses ChitChat.Domain.Identity✕
- Connections
- 2 pairs of types, where a type in ChitChat.DataAccess.Repositories uses a type in ChitChat.Domain.Identity.
- The types involved
ChitChat.DataAccess.Repositories.UserFollowerRepository→ChitChat.Domain.Identity.UserApplicationChitChat.DataAccess.Repositories.UserRepository→ChitChat.Domain.Identity.UserApplication
- Direction
- ChitChat.DataAccess.Repositories uses ChitChat.Domain.Identity, so a change to ChitChat.Domain.Identity can break ChitChat.DataAccess.Repositories, while a change to ChitChat.DataAccess.Repositories can't break ChitChat.Domain.Identity.
- Position
- Below the diagonal: ChitChat.DataAccess.Repositories uses a module listed above it, which is the healthy direction.
39→33 ChitChat.DataAccess.Repositories uses (global)✕
- Connections
- 1 pair of types, where a type in ChitChat.DataAccess.Repositories uses a type in (global).
- The types involved
ChitChat.DataAccess.Repositories.ConversationRepository→Conversation
- Direction
- ChitChat.DataAccess.Repositories uses (global), so a change to (global) can break ChitChat.DataAccess.Repositories, while a change to ChitChat.DataAccess.Repositories can't break (global).
- Position
- Below the diagonal: ChitChat.DataAccess.Repositories uses a module listed above it, which is the healthy direction.
39→36 ChitChat.DataAccess.Repositories uses ChitChat.DataAccess.Data✕
- Connections
- 5 pairs of types, where a type in ChitChat.DataAccess.Repositories uses a type in ChitChat.DataAccess.Data.
- The types involved
ChitChat.DataAccess.Repositories.BaseRepository→ChitChat.DataAccess.Data.ApplicationDbContextChitChat.DataAccess.Repositories.ConversationRepository→ChitChat.DataAccess.Data.ApplicationDbContextChitChat.DataAccess.Repositories.UserFollowerRepository→ChitChat.DataAccess.Data.ApplicationDbContextChitChat.DataAccess.Repositories.UserInteractionRepository→ChitChat.DataAccess.Data.ApplicationDbContextChitChat.DataAccess.Repositories.UserRepository→ChitChat.DataAccess.Data.ApplicationDbContext
- Direction
- ChitChat.DataAccess.Repositories uses ChitChat.DataAccess.Data, so a change to ChitChat.DataAccess.Data can break ChitChat.DataAccess.Repositories, while a change to ChitChat.DataAccess.Repositories can't break ChitChat.DataAccess.Data.
- Position
- Below the diagonal: ChitChat.DataAccess.Repositories uses a module listed above it, which is the healthy direction.
39→37 ChitChat.DataAccess.Repositories uses ChitChat.DataAccess.Repositories.Interface✕
- Connections
- 7 pairs of types, where a type in ChitChat.DataAccess.Repositories uses a type in ChitChat.DataAccess.Repositories.Interface.
- The types involved
ChitChat.DataAccess.Repositories.BaseRepository→ChitChat.DataAccess.Repositories.Interface.IBaseRepositoryChitChat.DataAccess.Repositories.ConversationRepository→ChitChat.DataAccess.Repositories.Interface.IConversationRepositoryChitChat.DataAccess.Repositories.RepositoryFactory→ChitChat.DataAccess.Repositories.Interface.IBaseRepositoryChitChat.DataAccess.Repositories.RepositoryFactory→ChitChat.DataAccess.Repositories.Interface.IRepositoryFactoryChitChat.DataAccess.Repositories.UserFollowerRepository→ChitChat.DataAccess.Repositories.Interface.IUserFollowerRepositoryChitChat.DataAccess.Repositories.UserInteractionRepository→ChitChat.DataAccess.Repositories.Interface.IUserInteractionRepositoryChitChat.DataAccess.Repositories.UserRepository→ChitChat.DataAccess.Repositories.Interface.IUserRepository
- Direction
- ChitChat.DataAccess.Repositories uses ChitChat.DataAccess.Repositories.Interface, so a change to ChitChat.DataAccess.Repositories.Interface can break ChitChat.DataAccess.Repositories, while a change to ChitChat.DataAccess.Repositories can't break ChitChat.DataAccess.Repositories.Interface.
- Position
- Below the diagonal: ChitChat.DataAccess.Repositories uses a module listed above it, which is the healthy direction.
40→1 ChitChat.WebAPI.Controllers uses ChitChat.Application.Models✕
- Connections
- 3 pairs of types, where a type in ChitChat.WebAPI.Controllers uses a type in ChitChat.Application.Models.
- The types involved
ChitChat.WebAPI.Controllers.ConversationController→ChitChat.Application.Models.PaginationFilterChitChat.WebAPI.Controllers.NotificationController→ChitChat.Application.Models.PaginationFilterChitChat.WebAPI.Controllers.ProfileController→ChitChat.Application.Models.PaginationFilter
- Direction
- ChitChat.WebAPI.Controllers uses ChitChat.Application.Models, so a change to ChitChat.Application.Models can break ChitChat.WebAPI.Controllers, while a change to ChitChat.WebAPI.Controllers can't break ChitChat.Application.Models.
- Position
- Below the diagonal: ChitChat.WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→3 ChitChat.WebAPI.Controllers uses ChitChat.Application.Models.Dtos.Post.CreatePost✕
- Connections
- 1 pair of types, where a type in ChitChat.WebAPI.Controllers uses a type in ChitChat.Application.Models.Dtos.Post.CreatePost.
- The types involved
ChitChat.WebAPI.Controllers.PostController→ChitChat.Application.Models.Dtos.Post.CreatePost.CreatePostRequestDto
- Direction
- ChitChat.WebAPI.Controllers uses ChitChat.Application.Models.Dtos.Post.CreatePost, so a change to ChitChat.Application.Models.Dtos.Post.CreatePost can break ChitChat.WebAPI.Controllers, while a change to ChitChat.WebAPI.Controllers can't break ChitChat.Application.Models.Dtos.Post.CreatePost.
- Position
- Below the diagonal: ChitChat.WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→4 ChitChat.WebAPI.Controllers uses ChitChat.Application.Models.Dtos.User✕
- Connections
- 3 pairs of types, where a type in ChitChat.WebAPI.Controllers uses a type in ChitChat.Application.Models.Dtos.User.
- The types involved
ChitChat.WebAPI.Controllers.UserController→ChitChat.Application.Models.Dtos.User.LoginRequestDtoChitChat.WebAPI.Controllers.UserController→ChitChat.Application.Models.Dtos.User.RefreshTokenDtoChitChat.WebAPI.Controllers.UserController→ChitChat.Application.Models.Dtos.User.RegisterationRequestDto
- Direction
- ChitChat.WebAPI.Controllers uses ChitChat.Application.Models.Dtos.User, so a change to ChitChat.Application.Models.Dtos.User can break ChitChat.WebAPI.Controllers, while a change to ChitChat.WebAPI.Controllers can't break ChitChat.Application.Models.Dtos.User.
- Position
- Below the diagonal: ChitChat.WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→9 ChitChat.WebAPI.Controllers uses ChitChat.Application.Models.Dtos.Message✕
- Connections
- 2 pairs of types, where a type in ChitChat.WebAPI.Controllers uses a type in ChitChat.Application.Models.Dtos.Message.
- The types involved
ChitChat.WebAPI.Controllers.ConversationController→ChitChat.Application.Models.Dtos.Message.MessageDtoChitChat.WebAPI.Controllers.ConversationController→ChitChat.Application.Models.Dtos.Message.RequestSendMessageDto
- Direction
- ChitChat.WebAPI.Controllers uses ChitChat.Application.Models.Dtos.Message, so a change to ChitChat.Application.Models.Dtos.Message can break ChitChat.WebAPI.Controllers, while a change to ChitChat.WebAPI.Controllers can't break ChitChat.Application.Models.Dtos.Message.
- Position
- Below the diagonal: ChitChat.WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→10 ChitChat.WebAPI.Controllers uses ChitChat.Application.Models.Dtos.Post.Comments✕
- Connections
- 1 pair of types, where a type in ChitChat.WebAPI.Controllers uses a type in ChitChat.Application.Models.Dtos.Post.Comments.
- The types involved
ChitChat.WebAPI.Controllers.PostController→ChitChat.Application.Models.Dtos.Post.Comments.CommentRequestDto
- Direction
- ChitChat.WebAPI.Controllers uses ChitChat.Application.Models.Dtos.Post.Comments, so a change to ChitChat.Application.Models.Dtos.Post.Comments can break ChitChat.WebAPI.Controllers, while a change to ChitChat.WebAPI.Controllers can't break ChitChat.Application.Models.Dtos.Post.Comments.
- Position
- Below the diagonal: ChitChat.WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→12 ChitChat.WebAPI.Controllers uses ChitChat.Application.Models.Dtos.User.Profile✕
- Connections
- 2 pairs of types, where a type in ChitChat.WebAPI.Controllers uses a type in ChitChat.Application.Models.Dtos.User.Profile.
- The types involved
ChitChat.WebAPI.Controllers.ProfileController→ChitChat.Application.Models.Dtos.User.Profile.ProfileRequestDtoChitChat.WebAPI.Controllers.ProfileController→ChitChat.Application.Models.Dtos.User.Profile.ProfileSearchQueryDto
- Direction
- ChitChat.WebAPI.Controllers uses ChitChat.Application.Models.Dtos.User.Profile, so a change to ChitChat.Application.Models.Dtos.User.Profile can break ChitChat.WebAPI.Controllers, while a change to ChitChat.WebAPI.Controllers can't break ChitChat.Application.Models.Dtos.User.Profile.
- Position
- Below the diagonal: ChitChat.WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→14 ChitChat.WebAPI.Controllers uses ChitChat.Application.Models.Dtos.Conversation✕
- Connections
- 1 pair of types, where a type in ChitChat.WebAPI.Controllers uses a type in ChitChat.Application.Models.Dtos.Conversation.
- The types involved
ChitChat.WebAPI.Controllers.ConversationController→ChitChat.Application.Models.Dtos.Conversation.ConversationDto
- Direction
- ChitChat.WebAPI.Controllers uses ChitChat.Application.Models.Dtos.Conversation, so a change to ChitChat.Application.Models.Dtos.Conversation can break ChitChat.WebAPI.Controllers, while a change to ChitChat.WebAPI.Controllers can't break ChitChat.Application.Models.Dtos.Conversation.
- Position
- Below the diagonal: ChitChat.WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→15 ChitChat.WebAPI.Controllers uses ChitChat.Application.Models.Dtos.Post✕
- Connections
- 3 pairs of types, where a type in ChitChat.WebAPI.Controllers uses a type in ChitChat.Application.Models.Dtos.Post.
- The types involved
ChitChat.WebAPI.Controllers.PostController→ChitChat.Application.Models.Dtos.Post.PostSearchQueryDtoChitChat.WebAPI.Controllers.PostController→ChitChat.Application.Models.Dtos.Post.PostUserSearchQueryDtoChitChat.WebAPI.Controllers.PostController→ChitChat.Application.Models.Dtos.Post.UpdatePostRequestDto
- Direction
- ChitChat.WebAPI.Controllers uses ChitChat.Application.Models.Dtos.Post, so a change to ChitChat.Application.Models.Dtos.Post can break ChitChat.WebAPI.Controllers, while a change to ChitChat.WebAPI.Controllers can't break ChitChat.Application.Models.Dtos.Post.
- Position
- Below the diagonal: ChitChat.WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→20 ChitChat.WebAPI.Controllers uses ChitChat.Application.MachineLearning.Services.Interface✕
- Connections
- 1 pair of types, where a type in ChitChat.WebAPI.Controllers uses a type in ChitChat.Application.MachineLearning.Services.Interface.
- The types involved
ChitChat.WebAPI.Controllers.TrainingModelController→ChitChat.Application.MachineLearning.Services.Interface.ITrainingModelService
- Direction
- ChitChat.WebAPI.Controllers uses ChitChat.Application.MachineLearning.Services.Interface, so a change to ChitChat.Application.MachineLearning.Services.Interface can break ChitChat.WebAPI.Controllers, while a change to ChitChat.WebAPI.Controllers can't break ChitChat.Application.MachineLearning.Services.Interface.
- Position
- Below the diagonal: ChitChat.WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→21 ChitChat.WebAPI.Controllers uses ChitChat.Application.Services.Interface✕
- Connections
- 6 pairs of types, where a type in ChitChat.WebAPI.Controllers uses a type in ChitChat.Application.Services.Interface.
- The types involved
ChitChat.WebAPI.Controllers.ConversationController→ChitChat.Application.Services.Interface.IConversationServiceChitChat.WebAPI.Controllers.NotificationController→ChitChat.Application.Services.Interface.INotificationServiceChitChat.WebAPI.Controllers.PostController→ChitChat.Application.Services.Interface.IPostServiceChitChat.WebAPI.Controllers.ProfileController→ChitChat.Application.Services.Interface.IFollowServiceChitChat.WebAPI.Controllers.ProfileController→ChitChat.Application.Services.Interface.IProfileServiceChitChat.WebAPI.Controllers.UserController→ChitChat.Application.Services.Interface.IUserService
- Direction
- ChitChat.WebAPI.Controllers uses ChitChat.Application.Services.Interface, so a change to ChitChat.Application.Services.Interface can break ChitChat.WebAPI.Controllers, while a change to ChitChat.WebAPI.Controllers can't break ChitChat.Application.Services.Interface.
- Position
- Below the diagonal: ChitChat.WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→28 ChitChat.WebAPI.Controllers uses ChitChat.Application.Helpers✕
- Connections
- 1 pair of types, where a type in ChitChat.WebAPI.Controllers uses a type in ChitChat.Application.Helpers.
- The types involved
ChitChat.WebAPI.Controllers.ConversationController→ChitChat.Application.Helpers.IClaimService
- Direction
- ChitChat.WebAPI.Controllers uses ChitChat.Application.Helpers, so a change to ChitChat.Application.Helpers can break ChitChat.WebAPI.Controllers, while a change to ChitChat.WebAPI.Controllers can't break ChitChat.Application.Helpers.
- Position
- Below the diagonal: ChitChat.WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→37 ChitChat.WebAPI.Controllers uses ChitChat.DataAccess.Repositories.Interface✕
- Connections
- 1 pair of types, where a type in ChitChat.WebAPI.Controllers uses a type in ChitChat.DataAccess.Repositories.Interface.
- The types involved
ChitChat.WebAPI.Controllers.TrainingModelController→ChitChat.DataAccess.Repositories.Interface.IUserRepository
- Direction
- ChitChat.WebAPI.Controllers uses ChitChat.DataAccess.Repositories.Interface, so a change to ChitChat.DataAccess.Repositories.Interface can break ChitChat.WebAPI.Controllers, while a change to ChitChat.WebAPI.Controllers can't break ChitChat.DataAccess.Repositories.Interface.
- Position
- Below the diagonal: ChitChat.WebAPI.Controllers 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 |
|---|---|---|
| A05:2025 — Injection | 17 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 14 | High / Critical |
| A07:2025 — Authentication Failures | 11 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
Roadmap
Top priorities: Resolve the 8 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3), REDACTED (3), REDACTED (2); Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 8 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3), REDACTED (3), REDACTED (2). | +9.0 pts | Low | Secret Scanning |
| Resolve the 3 Outdated finding(s) in Dependency Hygiene — start with REDACTED, ChitChat.WebAPI.csproj, REDACTED. | +5.0 pts | Low | Dependency Hygiene |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +4.2 pts | Low | ADR Quality |
| Resolve the 3 redundant comment finding(s) in Comment Value — start with Program.cs (2), DependencyInjection.cs. | +3.9 pts | Low | Comment Value |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +5.8 pts | Medium | Security & performance tooling |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +5.8 pts | Medium | DR & Backup |
| Resolve the 21 Orphaned file finding(s) in Knowledge Freshness — start with DependencyInjection.cs (2), ConversationService.cs, UserService.cs. | +4.5 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.0 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.1 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.3 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 2.3 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 3.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.5 | Slop | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 3.8 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.9 | Slop | Explicit Debt: WriteOnlyPrivateField |
| src/ChitChat.Application/Services/UserService.cs | 5.8 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/ChitChat.WebAPI/Controllers/TrainingModelController.cs | 5.8 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/ChitChat.WebAPI/Controllers/ConversationController.cs | 6.4 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs | 6.6 | Mixed | Explicit Debt: CommentedOutCode |
| REDACTED | 6.7 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/ChitChat.WebAPI/DependencyInjection.cs | 7.3 | Mixed | Explicit Debt: CommentedOutCode |
| src/ChitChat.Application/Services/PostService.cs | 7.6 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: 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 78 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 78 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, 206 of 243 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 — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- 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. All 22 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 22 of the 195 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
- D17 Explicit Debt — 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. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'docker/DockerCompose/DockerCompose.dcproj' because the file extension '.dcproj' is not associated with a language.
- 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- 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 DockerCompose (docker/DockerCompose/docker-compose.override.yml). compose up failed (exit 15 — the compose project is invalid) — time="2026-11-08T02:47:40Z" level=warning msg="The \"APPDATA\" variable is not set. Defaulting to a blank string." time="2026-11-08T02:47:40Z" level=warning msg="The \"APPDATA\" variable is not set. Defaulting to a blank string." service "chitchat.webapi" has neither an image nor a build context specified: invalid compose project; runtime evidence skipped.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- X2 Cancellation propagation — 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. 81 further occurrence(s) are not listed individually; the score already reflects all 121.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being GlobalExceptionHandlerMiddleware.HandleExceptionAsync at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/ChitChat.Infrastructure/Middleware/GlobalExceptionHandlerMiddleware.cs (GlobalExceptionHandlerMiddleware.HandleExceptionAsync at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was ContextSaveChangeInterceptor.SavingChangesAsync at 18.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with ContextSaveChangeInterceptor.SavingChangesAsync (cognitive 18). — Refactoring it lifts Cognitive Complexity from 9.7 to about 10.0/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
1 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (7 lines × 3) finding(s) in Code Duplication — start with CommentNotificationConfiguration.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
5 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 17 classes have LCOM4 above 3.
D12 · Dependency Hygiene
22 outdated, 1 vulnerable, 1 deprecated packages.
What to do
- Resolve the 3 Outdated finding(s) in Dependency Hygiene — start with REDACTED, ChitChat.WebAPI.csproj, REDACTED. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
8 secret(s) detected.
What to do
- Resolve the 8 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (8 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 259 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 26 direct `PackageReference`(s), and 224 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: src/ChitChat.Application/Services/PostService.cs (5 of 8 changes were fixes); REDACTED (3 of 5 changes were fixes); REDACTED (3 of 3 changes were fixes)
What to do
- Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with PostService.cs, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
D17 · Explicit Debt
15 deducted debt markers + unmeasured dead symbols across 5183 LoC in the .NET projects (1.2/KLoC) → score 7.5. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 7 WriteOnlyPrivateField finding(s) in Explicit Debt — start with ConversationController.cs (2), PostService.cs, UserService.cs. — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 7 CommentedOutCode finding(s) in Explicit Debt — start with SerilogRegistration.cs (4), UserService.cs, DependencyInjection.cs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with DependencyInjection.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
5 projects, 195 source files, 5183 hand-written lines of code (5183 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 6159 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 4 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 1 document(s) read across 6 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
3 of 36 judged comments only repeat the code they sit on (8.3 %). 4 comment(s) in another language or script were not judged.
What to do
- Resolve the 3 redundant comment finding(s) in Comment Value — start with Program.cs (2), DependencyInjection.cs. — One of this dimension's main actionable groups (3 recommendation-level).
D26 · Project Cohesion
0 of 5 projects flagged as possibly oversized/incoherent.
D27 · Navigability
100 % of calls cross a namespace and 5 % go through an interface, but 97 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low.
What to do
- Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
D29 · Static Analysis (SAST)
17 finding(s): 0 critical, 3 high, 14 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
8 finding(s): 0 critical, 5 high, 3 medium, 0 low.
What to do
- Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D31 · IaC & Container Security
5 finding(s): 0 critical, 1 high, 3 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 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
22 of 22 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/ChitChat.Application/Services/PostService.cs. Counted over 22 of the 195 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 21 Orphaned file finding(s) in Knowledge Freshness — start with DependencyInjection.cs (2), ConversationService.cs, UserService.cs. — One of this dimension's main actionable groups (21 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with PostService.cs. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D39 · IL Efficiency
0 of 359 first-party methods have an oversized IL body.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 6 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
- The namespaces ChitChat.Domain.Entities.PostEntities ↔ ChitChat.Domain.Entities.SystemEntities ↔ ChitChat.Domain.Enums ↔ ChitChat.Domain.Identity depend on each other. The lightest dependency in the cycle is ChitChat.Domain.Entities.SystemEntities → ChitChat.Domain.Entities.PostEntities (ChitChat.Domain.Entities.SystemEntities.UserInteraction → ChitChat.Domain.Entities.PostEntities.Post, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/ChitChat.Domain/Entities/SystemEntities/UserInteraction.cs:3
- The namespaces (global) ↔ ChitChat.Domain.Entities.ChatEntities depend on each other. The lightest dependency in the cycle is (global) → ChitChat.Domain.Entities.ChatEntities (Conversation → ChitChat.Domain.Entities.ChatEntities.ConversationDetail, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/ChitChat.Domain/Entities/ChatEntities/Conversation.cs:1
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction
- `ChitChat.Application` is a Application project but references `ChitChat.DataAccess`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — REDACTED:22
- This Application file depends on the Infrastructure project `ChitChat.DataAccess`: it names `ChitChat.DataAccess.Repositories.Interface`, `IConversationRepository`, `IBaseRepository`, `IUserRepository`, `IRepositoryFactory`. The inward dependency rule is broken here. It is named again on lines 13, 23, 24, 25, 28, 31, 32, 33. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/ChitChat.Application/Services/ConversationService.cs:12
- This Application file depends on the Infrastructure project `ChitChat.DataAccess`: it names `ChitChat.DataAccess.Repositories.Interface`, `IUserFollowerRepository`, `IRepositoryFactory`. The inward dependency rule is broken here. It is named again on lines 20, 26, 27. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/ChitChat.Application/Services/FollowService.cs:9
- This Application file depends on the Infrastructure project `ChitChat.DataAccess`: it names `ChitChat.DataAccess.Repositories.Interface`, `IBaseRepository`, `IRepositoryFactory`. The inward dependency rule is broken here. It is named again on lines 17, 18, 19, 24. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/ChitChat.Application/Services/NotificationService.cs:8
- This Application file depends on the Infrastructure project `ChitChat.DataAccess`: it names `ChitChat.DataAccess.Repositories.Interface`, `IBaseRepository`, `IUserInteractionRepository`, `IUserRepository`, `IRepositoryFactory`. The inward dependency rule is broken here. It is named again on lines 15, 32, 33, 34, 35, 36, 37, 39, …. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/ChitChat.Application/Services/PostService.cs:14
- This Application file depends on the Infrastructure project `ChitChat.DataAccess`: it names `ChitChat.DataAccess.Repositories.Interface`, `IBaseRepository`, `IUserRepository`. The inward dependency rule is broken here. It is named again on lines 9, 19, 21, 22, 24, 25, 27. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/ChitChat.Application/Services/ProfileService.cs:8
- This Application file depends on the Infrastructure project `ChitChat.DataAccess`: it names `ChitChat.DataAccess.Repositories.Interface`, `IUserRepository`, `IBaseRepository`, `IRepositoryFactory`. The inward dependency rule is broken here. It is named again on lines 11, 22, 23, 31, 32. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/ChitChat.Application/Services/UserService.cs:10
What to do
- Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
AX5 · Architecture & structure
AX6 · Interface segregation
- `IBaseRepository<TEntity>` declares 19 members under just 10 distinct name(s): `GetQuery`, `GetFirstAsync`, `GetFirstOrDefaultAsync`, `GetFirstOrDefaultAsync`, `GetFirstOrDefaultAsync`, `GetAllAsync`, `GetAllAsync`, `GetAllAsync`, `GetAllAsync`, `GetAllAsync`, `GetAllAsync`, `GetAllAsync`, `GetAllAsync`, `AddAsync`, `AddRangeAsync`, `UpdateAsync`, `UpdateRangeAsync`, `DeleteAsync`, `AnyAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 19 separate responsibilities: a caller binds to 10 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 19 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/ChitChat.DataAccess/Repositories/Interface/IBaseRepository.cs:10
What to do
- Collapse overload sets (optional/default parameters, or an options object) — these interfaces are wide in SIGNATURES, not in responsibilities, so segregating them would relieve no caller.
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
C2 · Access Controls
- [AllowAnonymous] (6) outweighs [Authorize] (5) — review whether the open surface is intended.
What to do
- Review the [AllowAnonymous] surface — keep anonymous endpoints deliberate and documented so the open surface stays intentional.
C3 · Audit Trail
- An audit mechanism is present, but the trail is not yet complete — missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.
What to do
- Back the audit convention with a structural mechanism: an EF SaveChanges interceptor (or equivalent) writing every sensitive change to an immutable audit log, and apply [Audited] to the entities that need a who-changed-what trail.
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM12 · Ambient inputs in the domain
- `InteractionTypePoint` reads `DateTime.Now` inside `GetInteractionPoint`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/ChitChat.Domain/Enums/InteractionType.cs:25
What to do
- Pass the instant into the domain method that needs it, or inject `TimeProvider` (BCL, .NET 8+) and read it there — then a test can choose the moment a rule is evaluated at.
DM6 · Domain ↔ infrastructure boundary
- `UserRepository` (a domain rule: it decides over the repository's entities) names `ApplicationDbContext` from `ChitChat.DataAccess.Data` — a persistence/infrastructure type (in a member signature). Move the queries to the caller and pass the loaded values to a pure decision method. (×2) — src/ChitChat.DataAccess/Repositories/UserRepository.cs:15, src/ChitChat.DataAccess/Repositories/UserRepository.cs:17
- `UserRepository` (a domain rule: it decides over the repository's entities) names `DbSet` from `Microsoft.EntityFrameworkCore` — a persistence type (in a member signature). Move the queries to the caller and pass the loaded values to a pure decision method. — src/ChitChat.DataAccess/Repositories/UserRepository.cs:16
- `UserRepository` (a domain rule: it decides over the repository's entities) names `UserApplication` from `ChitChat.Domain.Identity` — a persistence/infrastructure type (in a method body). Move the queries to the caller and pass the loaded values to a pure decision method. (×2) — src/ChitChat.DataAccess/Repositories/UserRepository.cs:20, src/ChitChat.DataAccess/Repositories/UserRepository.cs:27
- `UserRepository` (a domain rule: it decides over the repository's entities) names `UserApplication` from `ChitChat.Domain.Identity` — a persistence/infrastructure type (in a member signature). Move the queries to the caller and pass the loaded values to a pure decision method. (×11) — src/ChitChat.DataAccess/Repositories/UserRepository.cs:22, src/ChitChat.DataAccess/Repositories/UserRepository.cs:24, src/ChitChat.DataAccess/Repositories/UserRepository.cs:30, …
- `UserRepository` (a domain rule: it decides over the repository's entities) names `EntityFrameworkQueryableExtensions` from `Microsoft.EntityFrameworkCore` — a persistence type (in a method body). Move the queries to the caller and pass the loaded values to a pure decision method. (×4) — src/ChitChat.DataAccess/Repositories/UserRepository.cs:45, src/ChitChat.DataAccess/Repositories/UserRepository.cs:48, src/ChitChat.DataAccess/Repositories/UserRepository.cs:57, …
- `ConversationDetail` (domain layer) names `UserApplication` from `ChitChat.Domain.Identity` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/ChitChat.Domain/Entities/ChatEntities/ConversationDetail.cs:8
- `Message` (domain layer) names `UserApplication` from `ChitChat.Domain.Identity` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/ChitChat.Domain/Entities/ChatEntities/Message.cs:9
- `Comment` (domain layer) names `UserApplication` from `ChitChat.Domain.Identity` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/ChitChat.Domain/Entities/PostEntities/Comment.cs:14
- `Post` (domain layer) names `UserApplication` from `ChitChat.Domain.Identity` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/ChitChat.Domain/Entities/PostEntities/Post.cs:9
- `ReactionComment` (domain layer) names `UserApplication` from `ChitChat.Domain.Identity` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/ChitChat.Domain/Entities/PostEntities/Reaction/ReactionComment.cs:8
- `ReactionPost` (domain layer) names `UserApplication` from `ChitChat.Domain.Identity` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/ChitChat.Domain/Entities/PostEntities/Reaction/ReactionPost.cs:8
- `Notification` (domain layer) names `UserApplication` from `ChitChat.Domain.Identity` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/ChitChat.Domain/Entities/SystemEntities/Notification/Notification.cs:10, src/ChitChat.Domain/Entities/SystemEntities/Notification/Notification.cs:11
- `UserInteraction` (domain layer) names `UserApplication` from `ChitChat.Domain.Identity` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/ChitChat.Domain/Entities/SystemEntities/UserInteraction.cs:10
- `Profile` (domain layer) names `UserApplication` from `ChitChat.Domain.Identity` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/ChitChat.Domain/Entities/UserEntities/Profile.cs:10
- `UserFollower` (domain layer) names `UserApplication` from `ChitChat.Domain.Identity` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/ChitChat.Domain/Entities/UserEntities/UserFollower.cs:9, src/ChitChat.Domain/Entities/UserEntities/UserFollower.cs:10
- `UserFollowerRequest` (domain layer) names `UserApplication` from `ChitChat.Domain.Identity` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/ChitChat.Domain/Entities/UserEntities/UserFollowerRequest.cs:11, src/ChitChat.Domain/Entities/UserEntities/UserFollowerRequest.cs:12
- `ApplicationRole` (domain layer) names `IdentityRole` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/ChitChat.Domain/Identity/ApplicationRole.cs:5
- `UserApplication` (domain layer) names `IdentityUser` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/ChitChat.Domain/Identity/UserApplication.cs:7
- The domain project `ChitChat.Domain` references `Microsoft.AspNetCore.Identity.EntityFrameworkCore` — a persistence dependency; the domain should own a port and let an infrastructure project reference it. — src/ChitChat.Domain/ChitChat.Domain.csproj:11
- The domain project `ChitChat.Domain` references `Microsoft.EntityFrameworkCore` — a persistence dependency; the domain should own a port and let an infrastructure project reference it. — src/ChitChat.Domain/ChitChat.Domain.csproj:12
- The domain project `ChitChat.Domain` references `Microsoft.EntityFrameworkCore.Design` — a persistence dependency; the domain should own a port and let an infrastructure project reference it. — src/ChitChat.Domain/ChitChat.Domain.csproj:13
What to do
- Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- 8 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). (×2) — src/ChitChat.Application/Services/UserService.cs:74, src/ChitChat.WebAPI/DependencyInjection.cs:26
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×10) — src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:21, src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:22, src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:24, …
What to do
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 5 of 5 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
P2 · Observability
- `src/ChitChat.Application/MachineLearning/Services/TrainingModelService.cs` reports through `Console.Write…` at line 44 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/ChitChat.Application/MachineLearning/Services/TrainingModelService.cs:44
- `src/ChitChat.Application/MachineLearning/Services/TrainingModelService.cs` reports through `Console.Write…` at line 45 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/ChitChat.Application/MachineLearning/Services/TrainingModelService.cs:45
What to do
- Replace `Console.Write…` in service code with the project's injected `ILogger<T>` (message templates with named properties), so delivery outcomes and failures reach the log pipeline with a level and a category.
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1134 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:11
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P8 · Schema migrations
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path. — src/ChitChat.Infrastructure/Authorization/AuthorizationRegisteration.cs:26
- `ValidateLifetime = false` means expired tokens keep working indefinitely, so a leaked or revoked token never stops being valid. — REDACTED:64
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. — src/ChitChat.WebAPI/Program.cs:13
What to do
- Set RequireHttpsMetadata = true in prod (or pin MetadataAddress to a localhost URL the API can hit directly).
- Re-enable token validation — `ValidateLifetime` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
- `predictor` is a `PredictionEngine`, which implements `IDisposable`, and it is created here (line 46). Every use of it in `GetRecommendationPostModel` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var predictor = …;`), which releases it at the end of the scope on every path including a throw. — src/ChitChat.Application/MachineLearning/Services/TrainingModelService.cs:46
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 1/121 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken. — src/ChitChat.Infrastructure/Middleware/GlobalExceptionHandlerMiddleware.cs:38
- No CancellationToken parameter — this work can't be stopped early once started. (×38) — REDACTED:17, REDACTED:23, REDACTED:29, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
- Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×5) — src/ChitChat.Infrastructure/Middleware/GlobalExceptionHandlerMiddleware.cs:40, src/ChitChat.Infrastructure/Services/CloudinaryService.cs:46, REDACTED:18, …
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 64% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 76% | Strong | Solid. |
| Maturity | 43% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 33% | Weak — gated by D13, P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 59% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 52% | Adequate — gated by DM6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 2 control(s) we could not find positive evidence for
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 41 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- 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 — compose up failed (exit 15 — the compose project is invalid) — time="2026-11-08T02:47:40Z" level=warning msg="The \"APPDATA\" variable is not set. Defaulting to a blank string." time="2026-11-08T02:47:40Z" level=warning msg="The \"APPDATA\" variable is not set. Defaulting to a blank string." service "chitchat.webapi" has neither an image nor a build context specified: invalid compose project; 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.
- D10 Test Quality — ~6 lines of test code exist on disk but weren't loaded from the analyzed solution (excluded from the .sln, or co-located/using a test attribute not loaded here), so test quality couldn't be assessed. Include the tests in the analyzed solution to enable this check.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (5,183 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- D9 Test Distribution — 1 test project(s) found on disk but excluded from the analyzed solution.
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): a Domain/Aggregates/ValueObjects layer; 2 repository port(s) loading or saving an aggregate/entity
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (a message-bus package)
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 69 finding(s)
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:15
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:16
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:17
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:20
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:22
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:24
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:27
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:30
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:34
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:39
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:45
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:48
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:51
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:57
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:60
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:66
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:69
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:77
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:85
- Domain depends on infrastructure: UserRepository src/ChitChat.DataAccess/Repositories/UserRepository.cs:90
- Domain depends on infrastructure: ConversationDetail src/ChitChat.Domain/Entities/ChatEntities/ConversationDetail.cs:8
- Domain depends on infrastructure: Message src/ChitChat.Domain/Entities/ChatEntities/Message.cs:9
- Domain depends on infrastructure: Comment src/ChitChat.Domain/Entities/PostEntities/Comment.cs:14
- Domain depends on infrastructure: Post src/ChitChat.Domain/Entities/PostEntities/Post.cs:9
- Domain depends on infrastructure: ReactionComment src/ChitChat.Domain/Entities/PostEntities/Reaction/ReactionComment.cs:8
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- WriteOnlyPrivateField src/ChitChat.Application/Services/PostService.cs:41
- WriteOnlyPrivateField src/ChitChat.Application/Services/UserService.cs:27
- WriteOnlyPrivateField REDACTED:11
- WriteOnlyPrivateField src/ChitChat.WebAPI/Controllers/ConversationController.cs:17
- WriteOnlyPrivateField src/ChitChat.WebAPI/Controllers/ConversationController.cs:19
- WriteOnlyPrivateField src/ChitChat.WebAPI/Controllers/TrainingModelController.cs:12
- WriteOnlyPrivateField REDACTED:16
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Namespace dependency cycle src/ChitChat.Domain/Entities/SystemEntities/UserInteraction.cs:3
- Namespace dependency cycle src/ChitChat.Domain/Entities/ChatEntities/Conversation.cs:1
- REDACTED
- REDACTED
- Dependency-rule violation: ChitChat.Application (Application) → ChitChat.DataAccess (Infrastructure) REDACTED:22
- REDACTED
- REDACTED
Serious — 87 finding(s)
- Async method without CancellationToken: HandleExceptionAsync src/ChitChat.Infrastructure/Middleware/GlobalExceptionHandlerMiddleware.cs:38
- Async method without CancellationToken: JoinConversationGroup REDACTED:17
- Async method without CancellationToken: SendOffer REDACTED:23
- Async method without CancellationToken: SendAnswer REDACTED:29
- Async method without CancellationToken: SendIceCandidate REDACTED:35
- Async method without CancellationToken: StartCall REDACTED:40
- Async method without CancellationToken: JoinUserHub REDACTED:21
- Async method without CancellationToken: SendMessage src/ChitChat.Infrastructure/SignalR/Services/ConversationNotificationService.cs:15
- Async method without CancellationToken: UpdateMessage src/ChitChat.Infrastructure/SignalR/Services/ConversationNotificationService.cs:20
- Async method without CancellationToken: DeleteMessage src/ChitChat.Infrastructure/SignalR/Services/ConversationNotificationService.cs:24
- Async method without CancellationToken: AddConversation src/ChitChat.Infrastructure/SignalR/Services/UserNotificationService.cs:17
- Async method without CancellationToken: UpdateConversation src/ChitChat.Infrastructure/SignalR/Services/UserNotificationService.cs:25
- Async method without CancellationToken: DeleteConversation src/ChitChat.Infrastructure/SignalR/Services/UserNotificationService.cs:33
- Async method without CancellationToken: NewNotification src/ChitChat.Infrastructure/SignalR/Services/UserNotificationService.cs:41
- Async method without CancellationToken: UpdateNotification src/ChitChat.Infrastructure/SignalR/Services/UserNotificationService.cs:46
- Async method without CancellationToken: GetAllConversationsAsync src/ChitChat.WebAPI/Controllers/ConversationController.cs:30
- Async method without CancellationToken: GetConversationsByIdAsync src/ChitChat.WebAPI/Controllers/ConversationController.cs:38
- Async method without CancellationToken: CreateConversationAsync src/ChitChat.WebAPI/Controllers/ConversationController.cs:45
- Async method without CancellationToken: SendMessageAsync src/ChitChat.WebAPI/Controllers/ConversationController.cs:52
- Async method without CancellationToken: UpdateConversationAsync src/ChitChat.WebAPI/Controllers/ConversationController.cs:59
- Async method without CancellationToken: UpdateMessageAsync src/ChitChat.WebAPI/Controllers/ConversationController.cs:66
- Async method without CancellationToken: DeleteConversationAsync src/ChitChat.WebAPI/Controllers/ConversationController.cs:73
- Async method without CancellationToken: DeleteConversationAsync src/ChitChat.WebAPI/Controllers/ConversationController.cs:80
- Async method without CancellationToken: GetAllNotificationsAsync src/ChitChat.WebAPI/Controllers/NotificationController.cs:23
- Async method without CancellationToken: GetAllPostsAsync REDACTED:25
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- CommentedOutCode src/ChitChat.Application/Services/UserService.cs:74
- CommentedOutCode src/ChitChat.WebAPI/DependencyInjection.cs:26
- CommentedOutCode src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:28
- CommentedOutCode src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:46
- CommentedOutCode src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:75
- CommentedOutCode src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:51
- CommentedOutCode src/ChitChat.WebAPI/Controllers/TrainingModelController.cs:19
- Dependency-rule violation: ChitChat.Application (Application) → ChitChat.DataAccess (Infrastructure) src/ChitChat.Application/Services/ConversationService.cs:12
- Dependency-rule violation: ChitChat.Application (Application) → ChitChat.DataAccess (Infrastructure) src/ChitChat.Application/Services/FollowService.cs:9
- Dependency-rule violation: ChitChat.Application (Application) → ChitChat.DataAccess (Infrastructure) src/ChitChat.Application/Services/NotificationService.cs:8
- Dependency-rule violation: ChitChat.Application (Application) → ChitChat.DataAccess (Infrastructure) src/ChitChat.Application/Services/PostService.cs:14
- Dependency-rule violation: ChitChat.Application (Application) → ChitChat.DataAccess (Infrastructure) src/ChitChat.Application/Services/ProfileService.cs:8
- Dependency-rule violation: ChitChat.Application (Application) → ChitChat.DataAccess (Infrastructure) src/ChitChat.Application/Services/UserService.cs:10
- Repeated repair: src/ChitChat.Application/Services/PostService.cs src/ChitChat.Application/Services/PostService.cs:69
- Repeated repair: REDACTED REDACTED:18
- Repeated repair: REDACTED REDACTED:12
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Deprecated: FluentValidation.AspNetCore REDACTED:13
- TodoComment src/ChitChat.WebAPI/DependencyInjection.cs:78
- ContextSaveChangeInterceptor.SavingChangesAsync (cognitive 18) src/ChitChat.Infrastructure/EntityFrameworkCore/Interceptor/ContextSaveChangeInterceptor.cs:17
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (7 lines × 3) src/ChitChat.DataAccess/Configurations/Notification/CommentNotificationConfiguration.cs:11
- Tests outside the analyzed solution
- Domain type reads the wall clock: InteractionTypePoint src/ChitChat.Domain/Enums/InteractionType.cs:25
- No DR/backup evidence
- Token validation disabled REDACTED:64
- NuGet dependencies are not locked
- Disposable created and abandoned in the method that made it src/ChitChat.Application/MachineLearning/Services/TrainingModelService.cs:46
Minor — 67 finding(s)
- Orphaned file src/ChitChat.Application/Services/ConversationService.cs:1
- Orphaned file src/ChitChat.Application/Services/UserService.cs:1
- Orphaned file src/ChitChat.DataAccess/Repositories/BaseRepository.cs:1
- Orphaned file src/ChitChat.Application/Services/NotificationService.cs:1
- Orphaned file src/ChitChat.Application/Services/ProfileService.cs:1
- Orphaned file src/ChitChat.Application/Services/FollowService.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/ChitChat.WebAPI/DependencyInjection.cs:1
- Orphaned file src/ChitChat.Domain/Extensions/PredicateExtensions.cs:1
- Orphaned file src/ChitChat.WebAPI/Controllers/ConversationController.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/ChitChat.Infrastructure/Middleware/GlobalExceptionHandlerMiddleware.cs:1
- Orphaned file src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/ChitChat.Application/MachineLearning/Services/TrainingModelService.cs:1
- Orphaned file src/ChitChat.DataAccess/Repositories/UserRepository.cs:1
- Orphaned file src/ChitChat.Infrastructure/Services/CloudinaryService.cs:1
- Orphaned file src/ChitChat.DataAccess/Data/DbContextSeed.cs:1
- Orphaned file src/ChitChat.Infrastructure/DependencyInjection.cs:1
- Orphaned file src/ChitChat.DataAccess/Repositories/Interface/IBaseRepository.cs:1
- Orphaned file src/ChitChat.Infrastructure/SignalR/Services/UserNotificationService.cs:1
- Commented-out code src/ChitChat.Application/Services/UserService.cs:74
- Commented-out code src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:21
- Commented-out code src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:22
- Commented-out code src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:24
- Commented-out code src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:26
- Commented-out code src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:51
- Commented-out code src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:58
- Commented-out code src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:71
- Commented-out code src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:73
- Commented-out code src/ChitChat.Infrastructure/Logging/SerilogRegistration.cs:80
- Commented-out code src/ChitChat.WebAPI/Controllers/TrainingModelController.cs:22
- Commented-out code src/ChitChat.WebAPI/DependencyInjection.cs:26
- Interpolated log message defeats structured logging src/ChitChat.Infrastructure/Middleware/GlobalExceptionHandlerMiddleware.cs:40
- Interpolated log message defeats structured logging src/ChitChat.Infrastructure/Services/CloudinaryService.cs:46
- Interpolated log message defeats structured logging REDACTED:18
- Interpolated log message defeats structured logging src/ChitChat.Application/Services/UserService.cs:89
- Interpolated log message defeats structured logging src/ChitChat.Application/Services/UserService.cs:100
- Outdated: Serilog.AspNetCore REDACTED:21
- Outdated: Swashbuckle.AspNetCore src/ChitChat.WebAPI/ChitChat.WebAPI.csproj:17
- Outdated: AutoMapper REDACTED:11
- redundant comment src/ChitChat.Application/DependencyInjection.cs:31
- redundant comment src/ChitChat.WebAPI/Program.cs:15
- redundant comment src/ChitChat.WebAPI/Program.cs:44
- Console output used as the logging channel src/ChitChat.Application/MachineLearning/Services/TrainingModelService.cs:44
- Console output used as the logging channel src/ChitChat.Application/MachineLearning/Services/TrainingModelService.cs:45
- No security response headers detected
- No security response headers detected src/ChitChat.WebAPI/Program.cs:13
- Fat interface: IBaseRepository<TEntity> (19 members) src/ChitChat.DataAccess/Repositories/Interface/IBaseRepository.cs:10
- Anonymous-heavy surface
- Partial audit-trail evidence
- Partial data-retention evidence
- No ADRs found
- REDACTED
- Dormant codebase
- Most significant orphaned file src/ChitChat.Application/Services/PostService.cs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:4
- No dependency-update automation REDACTED:11
- No rollback/health safety
- OIDC metadata fetched over HTTP src/ChitChat.Infrastructure/Authorization/AuthorizationRegisteration.cs:26
- Not all async methods take a CancellationToken
Minor — 20 finding(s)
- Outdated: CloudinaryDotNet
- Outdated: Microsoft.AspNetCore.Authentication.JwtBearer
- Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore
- Outdated: Microsoft.AspNetCore.SignalR.Client
- Outdated: Microsoft.EntityFrameworkCore
- Outdated: Microsoft.EntityFrameworkCore.SqlServer
- Outdated: Microsoft.EntityFrameworkCore.Tools
- Outdated: Serilog.Settings.Configuration
- Outdated: Serilog.Sinks.ApplicationInsights
- Outdated: DotNetEnv
- Outdated: Microsoft.EntityFrameworkCore.Design
- Outdated: Microsoft.VisualStudio.Azure.Containers.Tools.Targets
- Outdated: Serilog
- Outdated: CsvHelper
- Outdated: FluentValidation.AspNetCore
- Outdated: MediatR
- Outdated: Microsoft.ML
- Outdated: Microsoft.ML.Recommender
- Outdated: Pomelo.EntityFrameworkCore.MySql
- doc comments repeat the names src/ChitChat.Domain/Extensions/PredicateExtensions.cs:87
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-3307764d10ec479abe6e41c903794ce0/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-3307764d10ec479abe6e41c903794ce0/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/ChitChat.DataAccess/Migrations . | 17 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list ChitChatSolution.sln package --vulnerable --include-transitive --format json | 8 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-107d9317908d4fedb6f5cc41ac93261e | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Date of birth — 3 field(s)
- ProfileDto.DateOfBirth src/ChitChat.Application/Models/Dtos/User/Profile/ProfileDto.cs:11
- ProfileRequestDto.DateOfBirth src/ChitChat.Application/Models/Dtos/User/Profile/ProfileRequestDto.cs:9
- Profile.DateOfBirth src/ChitChat.Domain/Entities/UserEntities/Profile.cs:7
Phone — 3 field(s)
- ProfileDto.PhoneNumber src/ChitChat.Application/Models/Dtos/User/Profile/ProfileDto.cs:9
- ProfileRequestDto.PhoneNumber src/ChitChat.Application/Models/Dtos/User/Profile/ProfileRequestDto.cs:7
- RegisterationRequestDto.PhoneNumber src/ChitChat.Application/Models/Dtos/User/RegisterationRequestDto.cs:7
Email — 2 field(s)
- ProfileDto.Email src/ChitChat.Application/Models/Dtos/User/Profile/ProfileDto.cs:8
- RegisterationRequestDto.Email src/ChitChat.Application/Models/Dtos/User/RegisterationRequestDto.cs:5
Name — 2 field(s)
- RegisterationRequestDto.LastName src/ChitChat.Application/Models/Dtos/User/RegisterationRequestDto.cs:8
- RegisterationRequestDto.FirstName src/ChitChat.Application/Models/Dtos/User/RegisterationRequestDto.cs:9