Executive summary
Team-B1ND/dodamdodam-ios falls short of our standard for production, in part because the project has no automated tests. It scores 43 out of 100 and is rated Weak, and none of its five critical findings concern security.
Production Readiness, at 16, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 17 points. Having someone learn and document the 85 files no active contributor knows is another step, worth about 8 points. Raising Production Readiness to 70 would lift the score to about 61.
The project has no automated tests, so a change can break it without warning. Four sets of files in separate parts keep changing together, which points to hidden dependencies. Adding automated tests and making the hidden dependencies explicit would close both risks.
The product code is 16,569 lines, about €14,000 to rebuild.
If Production Readiness rose from 16 to 70, the lowest score rated Strong, the score would rise from 43 to about 61.
Rebuild cost: about €14,000 · Estimate
| Cost to rebuild | €4,800 to €24,000, for 79 to 252 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: 16,569 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Projects~Data~DataSource | 2 Projects~Feature~Core | 3 Projects~Domain~Model | 4 Projects~Shared~SwiftUI | 5 Projects~Domain~Request | 6 Projects~Domain~Response | 7 Projects~Domain~Repository | 8 Projects~Feature~Club | 9 Projects~Domain~Entity | 10 Projects~Data~Network | 11 Projects~Data~Local~Meal | 12 Projects~Data~Network~Remote | 13 Projects~Feature~All | 14 Projects~Feature~Auth | 15 Projects~Feature~Home | 16 Projects~Feature~Meal | 17 Projects~Feature~NightStudy | 18 Projects~Feature~Out | 19 Projects~Data~DataSource~Auth | 20 Projects~Data~DataSource~Bus | 21 Projects~Data~DataSource~Club | 22 Projects~Data~DataSource~Division | 23 Projects~Data~DataSource~Meal | 24 Projects~Data~DataSource~Member | 25 Projects~Data~DataSource~NightStudy | 26 Projects~Data~DataSource~Notice | 27 Projects~Data~DataSource~OutGoing | 28 Projects~Data~DataSource~OutSleeping | 29 Projects~Data~DataSource~Point | 30 Projects~Data~DataSource~Schedule | 31 Projects~Data~DataSource~WakeupSong | 32 Projects~Feature~ChildrenManage | 33 Projects~Data~Repository~Auth | 34 Projects~Data~Repository~Club | 35 Projects~Data~Repository~Division | 36 Projects~Data~Repository~Member | 37 Projects~Data~Repository~NightStudy | 38 Projects~Data~Repository~OutGoing | 39 Projects~Data~Repository~OutSleeping | 40 Projects~Data~Repository~WakeupSong |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Projects~Data~DataSource | ||||||||||||||||||||||||||||||||||||||||
| 2 Projects~Feature~Core | ||||||||||||||||||||||||||||||||||||||||
| 3 Projects~Domain~Model | 9 | 12 | ||||||||||||||||||||||||||||||||||||||
| 4 Projects~Shared~SwiftUI | 3 | |||||||||||||||||||||||||||||||||||||||
| 5 Projects~Domain~Request | 2 | 8 | 41 | |||||||||||||||||||||||||||||||||||||
| 6 Projects~Domain~Response | 15 | 51 | 61 | |||||||||||||||||||||||||||||||||||||
| 7 Projects~Domain~Repository | 2 | 38 | 32 | 1 | 8 | |||||||||||||||||||||||||||||||||||
| 8 Projects~Feature~Club | 2 | 12 | 12 | 4 | 2 | 8 | ||||||||||||||||||||||||||||||||||
| 9 Projects~Domain~Entity | 1 | 24 | ||||||||||||||||||||||||||||||||||||||
| 10 Projects~Data~Network | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Projects~Data~Local~Meal | 3 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 12 Projects~Data~Network~Remote | 38 | 24 | 1 | 9 | ||||||||||||||||||||||||||||||||||||
| 13 Projects~Feature~All | 1 | 7 | 6 | 5 | 6 | |||||||||||||||||||||||||||||||||||
| 14 Projects~Feature~Auth | 1 | 6 | 2 | 2 | 6 | |||||||||||||||||||||||||||||||||||
| 15 Projects~Feature~Home | 1 | 2 | 8 | 12 | 8 | 2 | 3 | |||||||||||||||||||||||||||||||||
| 16 Projects~Feature~Meal | 1 | 2 | 2 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 17 Projects~Feature~NightStudy | 4 | 15 | 13 | 5 | 7 | 11 | ||||||||||||||||||||||||||||||||||
| 18 Projects~Feature~Out | 1 | 4 | 4 | 4 | 1 | 4 | ||||||||||||||||||||||||||||||||||
| 19 Projects~Data~DataSource~Auth | 1 | 3 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 Projects~Data~DataSource~Bus | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 Projects~Data~DataSource~Club | 1 | 1 | 8 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 22 Projects~Data~DataSource~Division | 1 | 7 | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 23 Projects~Data~DataSource~Meal | 2 | 4 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 24 Projects~Data~DataSource~Member | 1 | 8 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 25 Projects~Data~DataSource~NightStudy | 3 | 6 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 Projects~Data~DataSource~Notice | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 Projects~Data~DataSource~OutGoing | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 28 Projects~Data~DataSource~OutSleeping | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 29 Projects~Data~DataSource~Point | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 Projects~Data~DataSource~Schedule | 1 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 Projects~Data~DataSource~WakeupSong | 1 | 4 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 32 Projects~Feature~ChildrenManage | 1 | 5 | 5 | 2 | 4 | 1 | ||||||||||||||||||||||||||||||||||
| 33 Projects~Data~Repository~Auth | 1 | 3 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 Projects~Data~Repository~Club | 1 | 8 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 Projects~Data~Repository~Division | 7 | 4 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 Projects~Data~Repository~Member | 8 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 37 Projects~Data~Repository~NightStudy | 3 | 6 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 38 Projects~Data~Repository~OutGoing | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 Projects~Data~Repository~OutSleeping | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 40 Projects~Data~Repository~WakeupSong | 4 | 3 | 1 | 1 | 1 |
3→9 Projects~Domain~Model uses Projects~Domain~Entity part of a loop✕
- Connections
- 9 pairs of types, where a type in Projects~Domain~Model uses a type in Projects~Domain~Entity.
- The types involved
Projects~Domain~Model.Club→Projects~Domain~Entity.ClubTypeProjects~Domain~Model.Club→Projects~Domain~Entity.StateTypeProjects~Domain~Model.MealModel→Projects~Domain~Entity.DateProjects~Domain~Model.MealModel→Projects~Domain~Entity.MealTypeProjects~Domain~Model.Member→Projects~Domain~Entity.ActiveStatusProjects~Domain~Model.Member→Projects~Domain~Entity.DateProjects~Domain~Model.Member→Projects~Domain~Entity.RoleProjects~Domain~Model.PointReason→Projects~Domain~Entity.PointTypeProjects~Domain~Model.PointReason→Projects~Domain~Entity.ScoreType
- Direction
- Projects~Domain~Model uses Projects~Domain~Entity, so a change to Projects~Domain~Entity can break Projects~Domain~Model, while a change to Projects~Domain~Model can't break Projects~Domain~Entity.
- 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.
3→10 Projects~Domain~Model uses Projects~Data~Network part of a loop✕
- Connections
- 12 pairs of types, where a type in Projects~Domain~Model uses a type in Projects~Data~Network.
- The types involved
Projects~Domain~Model.Club→Projects~Data~Network.IntProjects~Domain~Model.Club→Projects~Data~Network.StringProjects~Domain~Model.ConnectStudent→Projects~Data~Network.StringProjects~Domain~Model.MealMenu→Projects~Data~Network.IntProjects~Domain~Model.MealMenu→Projects~Data~Network.StringProjects~Domain~Model.Member→Projects~Data~Network.StringProjects~Domain~Model.PointReason→Projects~Data~Network.IntProjects~Domain~Model.PointReason→Projects~Data~Network.StringProjects~Domain~Model.Student→Projects~Data~Network.IntProjects~Domain~Model.Student→Projects~Data~Network.StringProjects~Domain~Model.Teacher→Projects~Data~Network.IntProjects~Domain~Model.Teacher→Projects~Data~Network.String
- Direction
- Projects~Domain~Model uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Domain~Model, while a change to Projects~Domain~Model can't break Projects~Data~Network.
- 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.
4→10 Projects~Shared~SwiftUI uses Projects~Data~Network part of a loop✕
- Connections
- 3 pairs of types, where a type in Projects~Shared~SwiftUI uses a type in Projects~Data~Network.
- The types involved
Projects~Shared~SwiftUI.TextLengthLimiter→Projects~Data~Network.IntProjects~Shared~SwiftUI.TextLengthLimiter→Projects~Data~Network.StringProjects~Shared~SwiftUI.View→Projects~Data~Network.Int
- Direction
- Projects~Shared~SwiftUI uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Shared~SwiftUI, while a change to Projects~Shared~SwiftUI can't break Projects~Data~Network.
- 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.
5→3 Projects~Domain~Request uses Projects~Domain~Model✕
- Connections
- 2 pairs of types, where a type in Projects~Domain~Request uses a type in Projects~Domain~Model.
- The types involved
Projects~Domain~Request.ConnectStudentRequest→Projects~Domain~Model.ConnectStudentProjects~Domain~Request.ConnectStudentRequest→Projects~Domain~Model.ModelProtocol
- Direction
- Projects~Domain~Request uses Projects~Domain~Model, so a change to Projects~Domain~Model can break Projects~Domain~Request, while a change to Projects~Domain~Request can't break Projects~Domain~Model.
- Position
- Below the diagonal: Projects~Domain~Request uses a module listed above it, which is the healthy direction.
5→9 Projects~Domain~Request uses Projects~Domain~Entity part of a loop✕
- Connections
- 8 pairs of types, where a type in Projects~Domain~Request uses a type in Projects~Domain~Entity.
- The types involved
Projects~Domain~Request.ClubApplyRequest→Projects~Domain~Entity.ClubPriorityProjects~Domain~Request.FetchDivisionMembersRequest→Projects~Domain~Entity.AllowStatusProjects~Domain~Request.FetchNoticeRequest→Projects~Domain~Entity.NoticeStatusProjects~Domain~Request.FetchPointRequest→Projects~Domain~Entity.PointTypeProjects~Domain~Request.FetchPointScoreRequest→Projects~Domain~Entity.PointTypeProjects~Domain~Request.PatchMemberPermissionRequest→Projects~Domain~Entity.DivisionPermissionProjects~Domain~Request.PatchMembersStatusRequest→Projects~Domain~Entity.AllowStatusProjects~Domain~Request.PostNightStudyProjectRequest→Projects~Domain~Entity.NightStudyProjectType
- Direction
- Projects~Domain~Request uses Projects~Domain~Entity, so a change to Projects~Domain~Entity can break Projects~Domain~Request, while a change to Projects~Domain~Request can't break Projects~Domain~Entity.
- 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.
5→10 Projects~Domain~Request uses Projects~Data~Network part of a loop✕
- Connections
- 41 pairs of types, where a type in Projects~Domain~Request uses a type in Projects~Data~Network. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Projects~Domain~Request.AddMembersRequest→Projects~Data~Network.StringProjects~Domain~Request.ClubApplyRequest→Projects~Data~Network.IntProjects~Domain~Request.ClubApplyRequest→Projects~Data~Network.StringProjects~Domain~Request.ConnectStudentRequest→Projects~Data~Network.StringProjects~Domain~Request.DeepLinkLoginRequest→Projects~Data~Network.StringProjects~Domain~Request.DeleteDivisionMembersRequest→Projects~Data~Network.IntProjects~Domain~Request.FetchAllowedWakeupSongRequest→Projects~Data~Network.IntProjects~Domain~Request.FetchDivisionRequest→Projects~Data~Network.IntProjects~Domain~Request.FetchDivisionRequest→Projects~Data~Network.StringProjects~Domain~Request.FetchMealRequest→Projects~Data~Network.IntProjects~Domain~Request.FetchMonthlyMealRequest→Projects~Data~Network.IntProjects~Domain~Request.FetchNoticeByDivisionRequest→Projects~Data~Network.IntProjects~Domain~Request.FetchNoticeRequest→Projects~Data~Network.IntProjects~Domain~Request.FetchNoticeRequest→Projects~Data~Network.StringProjects~Domain~Request.FetchScheduleBetweenRequest→Projects~Data~Network.StringProjects~Domain~Request.FetchScheduleByDateRequest→Projects~Data~Network.IntProjects~Domain~Request.FetchScheduleByKeywordRequest→Projects~Data~Network.StringProjects~Domain~Request.FetchScheduleByPageRequest→Projects~Data~Network.IntProjects~Domain~Request.FetchWakeupSongByKeywordRequest→Projects~Data~Network.StringProjects~Domain~Request.NightStudyBanRequest→Projects~Data~Network.IntProjects~Domain~Request.NightStudyBanRequest→Projects~Data~Network.StringProjects~Domain~Request.PatchMemberInfoRequest→Projects~Data~Network.StringProjects~Domain~Request.PatchMembersStatusRequest→Projects~Data~Network.IntProjects~Domain~Request.PatchPasswordRequest→Projects~Data~Network.StringProjects~Domain~Request.PatchStudentInfoRequest→Projects~Data~Network.Int
- Direction
- Projects~Domain~Request uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Domain~Request, while a change to Projects~Domain~Request can't break Projects~Data~Network.
- 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.
6→3 Projects~Domain~Response uses Projects~Domain~Model✕
- Connections
- 15 pairs of types, where a type in Projects~Domain~Response uses a type in Projects~Domain~Model.
- The types involved
Projects~Domain~Response.ClubJoinRequestsResponse→Projects~Domain~Model.ClubProjects~Domain~Response.ConnectStudentResponse→Projects~Domain~Model.ConnectStudentProjects~Domain~Response.LoginResponse→Projects~Domain~Model.MemberProjects~Domain~Response.MealResponse→Projects~Domain~Model.MealDetailProjects~Domain~Response.MealResponse→Projects~Domain~Model.MealModelProjects~Domain~Response.MemberResponse→Projects~Domain~Model.StudentProjects~Domain~Response.MemberResponse→Projects~Domain~Model.TeacherProjects~Domain~Response.NightStudyResponse→Projects~Domain~Model.StudentProjects~Domain~Response.OngoingNightStudyResponse→Projects~Domain~Model.StudentProjects~Domain~Response.OutGoingResponse→Projects~Domain~Model.StudentProjects~Domain~Response.OutSleepingResponse→Projects~Domain~Model.StudentProjects~Domain~Response.PointResponse→Projects~Domain~Model.PointReasonProjects~Domain~Response.PointResponse→Projects~Domain~Model.StudentProjects~Domain~Response.PointResponse→Projects~Domain~Model.TeacherProjects~Domain~Response.PointScoreResponse→Projects~Domain~Model.Student
- Direction
- Projects~Domain~Response uses Projects~Domain~Model, so a change to Projects~Domain~Model can break Projects~Domain~Response, while a change to Projects~Domain~Response can't break Projects~Domain~Model.
- Position
- Below the diagonal: Projects~Domain~Response uses a module listed above it, which is the healthy direction.
6→9 Projects~Domain~Response uses Projects~Domain~Entity part of a loop✕
- Connections
- 51 pairs of types, where a type in Projects~Domain~Response uses a type in Projects~Domain~Entity. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Projects~Domain~Response.BannerResponse→Projects~Domain~Entity.ActiveStatusProjects~Domain~Response.BannerResponse→Projects~Domain~Entity.DateProjects~Domain~Response.ClubApplyResponse→Projects~Domain~Entity.ClubPriorityProjects~Domain~Response.ClubApplyResponse→Projects~Domain~Entity.StateTypeProjects~Domain~Response.ClubDetailResponse→Projects~Domain~Entity.ClubTeacherProjects~Domain~Response.ClubDetailResponse→Projects~Domain~Entity.ClubTypeProjects~Domain~Response.ClubDetailResponse→Projects~Domain~Entity.StateTypeProjects~Domain~Response.ClubJoinRequestsResponse→Projects~Domain~Entity.PermissionTypeProjects~Domain~Response.ClubJoinRequestsResponse→Projects~Domain~Entity.StateTypeProjects~Domain~Response.ClubMembersResponse→Projects~Domain~Entity.PermissionTypeProjects~Domain~Response.ClubMembersResponse→Projects~Domain~Entity.StateTypeProjects~Domain~Response.ClubsResponse→Projects~Domain~Entity.ClubTeacherProjects~Domain~Response.ClubsResponse→Projects~Domain~Entity.ClubTypeProjects~Domain~Response.ClubsResponse→Projects~Domain~Entity.StateTypeProjects~Domain~Response.DivisionDetailResponse→Projects~Domain~Entity.DivisionPermissionProjects~Domain~Response.DivisionMemberResponse→Projects~Domain~Entity.DivisionPermissionProjects~Domain~Response.DivisionMemberResponse→Projects~Domain~Entity.RoleProjects~Domain~Response.JoinedClubResponse→Projects~Domain~Entity.ClubTypeProjects~Domain~Response.JoinedClubResponse→Projects~Domain~Entity.StateTypeProjects~Domain~Response.MealResponse→Projects~Domain~Entity.DateProjects~Domain~Response.MemberResponse→Projects~Domain~Entity.ActiveStatusProjects~Domain~Response.MemberResponse→Projects~Domain~Entity.DateProjects~Domain~Response.MemberResponse→Projects~Domain~Entity.RoleProjects~Domain~Response.MyApplyClubResponse→Projects~Domain~Entity.ClubPriorityProjects~Domain~Response.MyApplyClubResponse→Projects~Domain~Entity.PermissionType
- Direction
- Projects~Domain~Response uses Projects~Domain~Entity, so a change to Projects~Domain~Entity can break Projects~Domain~Response, while a change to Projects~Domain~Response can't break Projects~Domain~Entity.
- 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.
6→10 Projects~Domain~Response uses Projects~Data~Network part of a loop✕
- Connections
- 61 pairs of types, where a type in Projects~Domain~Response uses a type in Projects~Data~Network. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Projects~Domain~Response.BannerResponse→Projects~Data~Network.IntProjects~Domain~Response.BannerResponse→Projects~Data~Network.StringProjects~Domain~Response.BusResponse→Projects~Data~Network.IntProjects~Domain~Response.BusResponse→Projects~Data~Network.StringProjects~Domain~Response.ClubApplyResponse→Projects~Data~Network.IntProjects~Domain~Response.ClubApplyResponse→Projects~Data~Network.StringProjects~Domain~Response.ClubDetailResponse→Projects~Data~Network.IntProjects~Domain~Response.ClubDetailResponse→Projects~Data~Network.StringProjects~Domain~Response.ClubJoinRequestsResponse→Projects~Data~Network.IntProjects~Domain~Response.ClubMembersResponse→Projects~Data~Network.IntProjects~Domain~Response.ClubMembersResponse→Projects~Data~Network.StringProjects~Domain~Response.ClubRegisterTimeResponse→Projects~Data~Network.StringProjects~Domain~Response.ClubsResponse→Projects~Data~Network.IntProjects~Domain~Response.ClubsResponse→Projects~Data~Network.StringProjects~Domain~Response.ConnectStudentResponse→Projects~Data~Network.StringProjects~Domain~Response.DefaultResponse→Projects~Data~Network.IntProjects~Domain~Response.DefaultResponse→Projects~Data~Network.StringProjects~Domain~Response.DivisionDetailResponse→Projects~Data~Network.IntProjects~Domain~Response.DivisionDetailResponse→Projects~Data~Network.StringProjects~Domain~Response.DivisionMemberResponse→Projects~Data~Network.IntProjects~Domain~Response.DivisionMemberResponse→Projects~Data~Network.StringProjects~Domain~Response.DivisionMembersCountResponse→Projects~Data~Network.IntProjects~Domain~Response.DivisionOverviewResponse→Projects~Data~Network.IntProjects~Domain~Response.DivisionOverviewResponse→Projects~Data~Network.StringProjects~Domain~Response.JoinedClubResponse→Projects~Data~Network.Int
- Direction
- Projects~Domain~Response uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Domain~Response, while a change to Projects~Domain~Response can't break Projects~Data~Network.
- 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.
7→3 Projects~Domain~Repository uses Projects~Domain~Model✕
- Connections
- 2 pairs of types, where a type in Projects~Domain~Repository uses a type in Projects~Domain~Model.
- The types involved
Projects~Domain~Repository.AuthRepository→Projects~Domain~Model.MemberProjects~Domain~Repository.MealRepository→Projects~Domain~Model.MealModel
- Direction
- Projects~Domain~Repository uses Projects~Domain~Model, so a change to Projects~Domain~Model can break Projects~Domain~Repository, while a change to Projects~Domain~Repository can't break Projects~Domain~Model.
- Position
- Below the diagonal: Projects~Domain~Repository uses a module listed above it, which is the healthy direction.
7→5 Projects~Domain~Repository uses Projects~Domain~Request✕
- Connections
- 38 pairs of types, where a type in Projects~Domain~Repository uses a type in Projects~Domain~Request. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Projects~Domain~Repository.AuthRepository→Projects~Domain~Request.DeepLinkLoginRequestProjects~Domain~Repository.AuthRepository→Projects~Domain~Request.PostLoginRequestProjects~Domain~Repository.AuthRepository→Projects~Domain~Request.PostReissueRequestProjects~Domain~Repository.ClubRepository→Projects~Domain~Request.ClubApplyRequestProjects~Domain~Repository.DivisionRepository→Projects~Domain~Request.AddMembersRequestProjects~Domain~Repository.DivisionRepository→Projects~Domain~Request.DeleteDivisionMembersRequestProjects~Domain~Repository.DivisionRepository→Projects~Domain~Request.FetchDivisionMembersRequestProjects~Domain~Repository.DivisionRepository→Projects~Domain~Request.FetchDivisionRequestProjects~Domain~Repository.DivisionRepository→Projects~Domain~Request.PatchMemberPermissionRequestProjects~Domain~Repository.DivisionRepository→Projects~Domain~Request.PatchMembersStatusRequestProjects~Domain~Repository.DivisionRepository→Projects~Domain~Request.PostDivisionRequestProjects~Domain~Repository.MealRepository→Projects~Domain~Request.FetchMealRequestProjects~Domain~Repository.MealRepository→Projects~Domain~Request.FetchMonthlyMealRequestProjects~Domain~Repository.MemberRepository→Projects~Domain~Request.PatchMemberInfoRequestProjects~Domain~Repository.MemberRepository→Projects~Domain~Request.PatchPasswordRequestProjects~Domain~Repository.MemberRepository→Projects~Domain~Request.PatchStudentInfoRequestProjects~Domain~Repository.MemberRepository→Projects~Domain~Request.PostAuthCodeRequestProjects~Domain~Repository.MemberRepository→Projects~Domain~Request.PostJoinParentRequestProjects~Domain~Repository.MemberRepository→Projects~Domain~Request.PostJoinStudentRequestProjects~Domain~Repository.MemberRepository→Projects~Domain~Request.PostRelationRequestProjects~Domain~Repository.MemberRepository→Projects~Domain~Request.PostVerifyAuthCodeRequestProjects~Domain~Repository.NightStudyRepository→Projects~Domain~Request.NightStudyBanRequestProjects~Domain~Repository.NightStudyRepository→Projects~Domain~Request.PostNightStudyProjectRequestProjects~Domain~Repository.NightStudyRepository→Projects~Domain~Request.PostNightStudyRequestProjects~Domain~Repository.NoticeRepository→Projects~Domain~Request.FetchNoticeByDivisionRequest
- Direction
- Projects~Domain~Repository uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Domain~Repository, while a change to Projects~Domain~Repository can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Domain~Repository uses a module listed above it, which is the healthy direction.
7→6 Projects~Domain~Repository uses Projects~Domain~Response✕
- Connections
- 32 pairs of types, where a type in Projects~Domain~Repository uses a type in Projects~Domain~Response. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Projects~Domain~Repository.AuthRepository→Projects~Domain~Response.DefaultResponseProjects~Domain~Repository.BannerRepository→Projects~Domain~Response.BannerResponseProjects~Domain~Repository.BusRepository→Projects~Domain~Response.BusResponseProjects~Domain~Repository.ClubRepository→Projects~Domain~Response.ClubDetailResponseProjects~Domain~Repository.ClubRepository→Projects~Domain~Response.ClubJoinRequestsResponseProjects~Domain~Repository.ClubRepository→Projects~Domain~Response.ClubMembersInfoResponseProjects~Domain~Repository.ClubRepository→Projects~Domain~Response.ClubRegisterTimeResponseProjects~Domain~Repository.ClubRepository→Projects~Domain~Response.ClubsResponseProjects~Domain~Repository.ClubRepository→Projects~Domain~Response.JoinedClubResponseProjects~Domain~Repository.ClubRepository→Projects~Domain~Response.MyApplyClubResponseProjects~Domain~Repository.ClubRepository→Projects~Domain~Response.MyClubResponseProjects~Domain~Repository.DivisionRepository→Projects~Domain~Response.DivisionDetailResponseProjects~Domain~Repository.DivisionRepository→Projects~Domain~Response.DivisionMemberResponseProjects~Domain~Repository.DivisionRepository→Projects~Domain~Response.DivisionMembersCountResponseProjects~Domain~Repository.DivisionRepository→Projects~Domain~Response.DivisionOverviewResponseProjects~Domain~Repository.MemberRepository→Projects~Domain~Response.ConnectStudentResponseProjects~Domain~Repository.MemberRepository→Projects~Domain~Response.MemberResponseProjects~Domain~Repository.NightStudyRepository→Projects~Domain~Response.DefaultResponseProjects~Domain~Repository.NightStudyRepository→Projects~Domain~Response.NightStudyBanResponseProjects~Domain~Repository.NightStudyRepository→Projects~Domain~Response.NightStudyProjectResponseProjects~Domain~Repository.NightStudyRepository→Projects~Domain~Response.NightStudyResponseProjects~Domain~Repository.NightStudyRepository→Projects~Domain~Response.NightStudyStudentResponseProjects~Domain~Repository.NightStudyRepository→Projects~Domain~Response.OngoingNightStudyResponseProjects~Domain~Repository.NoticeRepository→Projects~Domain~Response.NoticeResponseProjects~Domain~Repository.OutGoingRepository→Projects~Domain~Response.OutGoingResponse
- Direction
- Projects~Domain~Repository uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Domain~Repository, while a change to Projects~Domain~Repository can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Domain~Repository uses a module listed above it, which is the healthy direction.
7→9 Projects~Domain~Repository uses Projects~Domain~Entity part of a loop✕
- Connections
- 1 pair of types, where a type in Projects~Domain~Repository uses a type in Projects~Domain~Entity.
- The types involved
Projects~Domain~Repository.MemberRepository→Projects~Domain~Entity.AuthType
- Direction
- Projects~Domain~Repository uses Projects~Domain~Entity, so a change to Projects~Domain~Entity can break Projects~Domain~Repository, while a change to Projects~Domain~Repository can't break Projects~Domain~Entity.
- 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.
7→10 Projects~Domain~Repository uses Projects~Data~Network part of a loop✕
- Connections
- 8 pairs of types, where a type in Projects~Domain~Repository uses a type in Projects~Data~Network.
- The types involved
Projects~Domain~Repository.BusRepository→Projects~Data~Network.IntProjects~Domain~Repository.ClubRepository→Projects~Data~Network.IntProjects~Domain~Repository.DivisionRepository→Projects~Data~Network.IntProjects~Domain~Repository.MemberRepository→Projects~Data~Network.StringProjects~Domain~Repository.NightStudyRepository→Projects~Data~Network.IntProjects~Domain~Repository.OutGoingRepository→Projects~Data~Network.IntProjects~Domain~Repository.OutSleepingRepository→Projects~Data~Network.IntProjects~Domain~Repository.WakeupSongRepository→Projects~Data~Network.Int
- Direction
- Projects~Domain~Repository uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Domain~Repository, while a change to Projects~Domain~Repository can't break Projects~Data~Network.
- 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.
8→2 Projects~Feature~Club uses Projects~Feature~Core✕
- Connections
- 2 pairs of types, where a type in Projects~Feature~Club uses a type in Projects~Feature~Core.
- The types involved
Projects~Feature~Club.ClubApplyViewModel→Projects~Feature~Core.OnAppearProtocolProjects~Feature~Club.ClubDetailViewModel→Projects~Feature~Core.OnAppearProtocol
- Direction
- Projects~Feature~Club uses Projects~Feature~Core, so a change to Projects~Feature~Core can break Projects~Feature~Club, while a change to Projects~Feature~Club can't break Projects~Feature~Core.
- Position
- Below the diagonal: Projects~Feature~Club uses a module listed above it, which is the healthy direction.
8→4 Projects~Feature~Club uses Projects~Shared~SwiftUI✕
- Connections
- 12 pairs of types, where a type in Projects~Feature~Club uses a type in Projects~Shared~SwiftUI.
- The types involved
Projects~Feature~Club.AffiliationCell→Projects~Shared~SwiftUI.ViewProjects~Feature~Club.ClubApplyView→Projects~Shared~SwiftUI.ViewProjects~Feature~Club.ClubCell→Projects~Shared~SwiftUI.ViewProjects~Feature~Club.ClubDetailView→Projects~Shared~SwiftUI.ViewProjects~Feature~Club.ClubView→Projects~Shared~SwiftUI.ViewProjects~Feature~Club.CreateClubCell→Projects~Shared~SwiftUI.ViewProjects~Feature~Club.LeaderCell→Projects~Shared~SwiftUI.ViewProjects~Feature~Club.MemberCell→Projects~Shared~SwiftUI.ViewProjects~Feature~Club.MyApplyCell→Projects~Shared~SwiftUI.ViewProjects~Feature~Club.MyClubView→Projects~Shared~SwiftUI.ViewProjects~Feature~Club.StateTypeTag→Projects~Shared~SwiftUI.ViewProjects~Feature~Club.SugestCell→Projects~Shared~SwiftUI.View
- Direction
- Projects~Feature~Club uses Projects~Shared~SwiftUI, so a change to Projects~Shared~SwiftUI can break Projects~Feature~Club, while a change to Projects~Feature~Club can't break Projects~Shared~SwiftUI.
- Position
- Below the diagonal: Projects~Feature~Club uses a module listed above it, which is the healthy direction.
8→6 Projects~Feature~Club uses Projects~Domain~Response✕
- Connections
- 12 pairs of types, where a type in Projects~Feature~Club uses a type in Projects~Domain~Response.
- The types involved
Projects~Feature~Club.ClubApplyViewModel→Projects~Domain~Response.ClubsResponseProjects~Feature~Club.ClubCell→Projects~Domain~Response.ClubsResponseProjects~Feature~Club.ClubDetailViewModel→Projects~Domain~Response.ClubDetailResponseProjects~Feature~Club.ClubDetailViewModel→Projects~Domain~Response.ClubMembersInfoResponseProjects~Feature~Club.ClubViewModel→Projects~Domain~Response.ClubsResponseProjects~Feature~Club.LeaderCell→Projects~Domain~Response.ClubMembersResponseProjects~Feature~Club.MemberCell→Projects~Domain~Response.ClubMembersResponseProjects~Feature~Club.MyClubViewModel→Projects~Domain~Response.ClubJoinRequestsResponseProjects~Feature~Club.MyClubViewModel→Projects~Domain~Response.ClubRegisterTimeResponseProjects~Feature~Club.MyClubViewModel→Projects~Domain~Response.JoinedClubResponseProjects~Feature~Club.MyClubViewModel→Projects~Domain~Response.MyApplyClubResponseProjects~Feature~Club.MyClubViewModel→Projects~Domain~Response.MyClubResponse
- Direction
- Projects~Feature~Club uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Feature~Club, while a change to Projects~Feature~Club can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Feature~Club uses a module listed above it, which is the healthy direction.
8→7 Projects~Feature~Club uses Projects~Domain~Repository✕
- Connections
- 4 pairs of types, where a type in Projects~Feature~Club uses a type in Projects~Domain~Repository.
- The types involved
Projects~Feature~Club.ClubApplyViewModel→Projects~Domain~Repository.ClubRepositoryProjects~Feature~Club.ClubDetailViewModel→Projects~Domain~Repository.ClubRepositoryProjects~Feature~Club.ClubViewModel→Projects~Domain~Repository.ClubRepositoryProjects~Feature~Club.MyClubViewModel→Projects~Domain~Repository.ClubRepository
- Direction
- Projects~Feature~Club uses Projects~Domain~Repository, so a change to Projects~Domain~Repository can break Projects~Feature~Club, while a change to Projects~Feature~Club can't break Projects~Domain~Repository.
- Position
- Below the diagonal: Projects~Feature~Club uses a module listed above it, which is the healthy direction.
8→9 Projects~Feature~Club uses Projects~Domain~Entity part of a loop✕
- Connections
- 2 pairs of types, where a type in Projects~Feature~Club uses a type in Projects~Domain~Entity.
- The types involved
Projects~Feature~Club.CreateClubCell→Projects~Domain~Entity.StateTypeProjects~Feature~Club.MyApplyCell.swift→Projects~Domain~Entity.ClubPriority
- Direction
- Projects~Feature~Club uses Projects~Domain~Entity, so a change to Projects~Domain~Entity can break Projects~Feature~Club, while a change to Projects~Feature~Club can't break Projects~Domain~Entity.
- 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.
8→10 Projects~Feature~Club uses Projects~Data~Network part of a loop✕
- Connections
- 8 pairs of types, where a type in Projects~Feature~Club uses a type in Projects~Data~Network.
- The types involved
Projects~Feature~Club.ClubApplyView→Projects~Data~Network.IntProjects~Feature~Club.ClubApplyViewModel→Projects~Data~Network.StringProjects~Feature~Club.ClubDetailView→Projects~Data~Network.IntProjects~Feature~Club.ClubDetailViewModel→Projects~Data~Network.IntProjects~Feature~Club.ClubView→Projects~Data~Network.IntProjects~Feature~Club.MyApplyCell.swift→Projects~Data~Network.StringProjects~Feature~Club.MyClubViewModel→Projects~Data~Network.IntProjects~Feature~Club.StateTypeTag→Projects~Data~Network.String
- Direction
- Projects~Feature~Club uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Feature~Club, while a change to Projects~Feature~Club can't break Projects~Data~Network.
- 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.
9→8 Projects~Domain~Entity uses Projects~Feature~Club✕
- Connections
- 1 pair of types, where a type in Projects~Domain~Entity uses a type in Projects~Feature~Club.
- The types involved
Projects~Domain~Entity.StateType→Projects~Feature~Club.StateTypeTag
- Direction
- Projects~Domain~Entity uses Projects~Feature~Club, so a change to Projects~Feature~Club can break Projects~Domain~Entity, while a change to Projects~Domain~Entity can't break Projects~Feature~Club.
- Position
- Below the diagonal: Projects~Domain~Entity uses a module listed above it, which is the healthy direction.
9→10 Projects~Domain~Entity uses Projects~Data~Network part of a loop✕
- Connections
- 24 pairs of types, where a type in Projects~Domain~Entity uses a type in Projects~Data~Network.
- The types involved
Projects~Domain~Entity.ActiveStatus→Projects~Data~Network.StringProjects~Domain~Entity.AllowStatus→Projects~Data~Network.StringProjects~Domain~Entity.AuthType→Projects~Data~Network.StringProjects~Domain~Entity.ClubPriority→Projects~Data~Network.StringProjects~Domain~Entity.ClubTeacher→Projects~Data~Network.StringProjects~Domain~Entity.ClubType→Projects~Data~Network.StringProjects~Domain~Entity.Date→Projects~Data~Network.StringProjects~Domain~Entity.DivisionPermission→Projects~Data~Network.StringProjects~Domain~Entity.FileType→Projects~Data~Network.StringProjects~Domain~Entity.Grade→Projects~Data~Network.StringProjects~Domain~Entity.MealType→Projects~Data~Network.IntProjects~Domain~Entity.MealType→Projects~Data~Network.StringProjects~Domain~Entity.NightProjectPlace→Projects~Data~Network.StringProjects~Domain~Entity.NightStudyPlace→Projects~Data~Network.StringProjects~Domain~Entity.NightStudyProjectType→Projects~Data~Network.StringProjects~Domain~Entity.NightStudyType→Projects~Data~Network.StringProjects~Domain~Entity.NoticeStatus→Projects~Data~Network.StringProjects~Domain~Entity.PermissionType→Projects~Data~Network.StringProjects~Domain~Entity.PointType→Projects~Data~Network.StringProjects~Domain~Entity.Role→Projects~Data~Network.StringProjects~Domain~Entity.SchedulePlace→Projects~Data~Network.StringProjects~Domain~Entity.ScheduleType→Projects~Data~Network.StringProjects~Domain~Entity.ScoreType→Projects~Data~Network.StringProjects~Domain~Entity.StateType→Projects~Data~Network.String
- Direction
- Projects~Domain~Entity uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Domain~Entity, while a change to Projects~Domain~Entity can't break Projects~Data~Network.
- 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.
10→9 Projects~Data~Network uses Projects~Domain~Entity✕
- Connections
- 1 pair of types, where a type in Projects~Data~Network uses a type in Projects~Domain~Entity.
- The types involved
Projects~Data~Network.String→Projects~Domain~Entity.Date
- Direction
- Projects~Data~Network uses Projects~Domain~Entity, so a change to Projects~Domain~Entity can break Projects~Data~Network, while a change to Projects~Data~Network can't break Projects~Domain~Entity.
- Position
- Below the diagonal: Projects~Data~Network uses a module listed above it, which is the healthy direction.
11→3 Projects~Data~Local~Meal uses Projects~Domain~Model✕
- Connections
- 3 pairs of types, where a type in Projects~Data~Local~Meal uses a type in Projects~Domain~Model.
- The types involved
Projects~Data~Local~Meal.MealDetailEntity→Projects~Domain~Model.MealDetailProjects~Data~Local~Meal.MealEntity→Projects~Domain~Model.MealModelProjects~Data~Local~Meal.MealMenuEntity→Projects~Domain~Model.MealMenu
- Direction
- Projects~Data~Local~Meal uses Projects~Domain~Model, so a change to Projects~Domain~Model can break Projects~Data~Local~Meal, while a change to Projects~Data~Local~Meal can't break Projects~Domain~Model.
- Position
- Below the diagonal: Projects~Data~Local~Meal uses a module listed above it, which is the healthy direction.
11→5 Projects~Data~Local~Meal uses Projects~Domain~Request✕
- Connections
- 2 pairs of types, where a type in Projects~Data~Local~Meal uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~Local~Meal.MealCache→Projects~Domain~Request.FetchMealRequestProjects~Data~Local~Meal.MealCache→Projects~Domain~Request.FetchMonthlyMealRequest
- Direction
- Projects~Data~Local~Meal uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~Local~Meal, while a change to Projects~Data~Local~Meal can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~Local~Meal uses a module listed above it, which is the healthy direction.
11→9 Projects~Data~Local~Meal uses Projects~Domain~Entity✕
- Connections
- 1 pair of types, where a type in Projects~Data~Local~Meal uses a type in Projects~Domain~Entity.
- The types involved
Projects~Data~Local~Meal.MealEntity→Projects~Domain~Entity.Date
- Direction
- Projects~Data~Local~Meal uses Projects~Domain~Entity, so a change to Projects~Domain~Entity can break Projects~Data~Local~Meal, while a change to Projects~Data~Local~Meal can't break Projects~Domain~Entity.
- Position
- Below the diagonal: Projects~Data~Local~Meal uses a module listed above it, which is the healthy direction.
11→10 Projects~Data~Local~Meal uses Projects~Data~Network✕
- Connections
- 2 pairs of types, where a type in Projects~Data~Local~Meal uses a type in Projects~Data~Network.
- The types involved
Projects~Data~Local~Meal.MealEntity→Projects~Data~Network.IntProjects~Data~Local~Meal.MealMenuEntity→Projects~Data~Network.String
- Direction
- Projects~Data~Local~Meal uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~Local~Meal, while a change to Projects~Data~Local~Meal can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~Local~Meal uses a module listed above it, which is the healthy direction.
12→5 Projects~Data~Network~Remote uses Projects~Domain~Request✕
- Connections
- 38 pairs of types, where a type in Projects~Data~Network~Remote uses a type in Projects~Domain~Request. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Projects~Data~Network~Remote.AuthRemote→Projects~Domain~Request.DeepLinkLoginRequestProjects~Data~Network~Remote.AuthRemote→Projects~Domain~Request.PostLoginRequestProjects~Data~Network~Remote.AuthRemote→Projects~Domain~Request.PostReissueRequestProjects~Data~Network~Remote.ClubRemote→Projects~Domain~Request.ClubApplyRequestProjects~Data~Network~Remote.DivisionRemote→Projects~Domain~Request.AddMembersRequestProjects~Data~Network~Remote.DivisionRemote→Projects~Domain~Request.DeleteDivisionMembersRequestProjects~Data~Network~Remote.DivisionRemote→Projects~Domain~Request.FetchDivisionMembersRequestProjects~Data~Network~Remote.DivisionRemote→Projects~Domain~Request.FetchDivisionRequestProjects~Data~Network~Remote.DivisionRemote→Projects~Domain~Request.PatchMemberPermissionRequestProjects~Data~Network~Remote.DivisionRemote→Projects~Domain~Request.PatchMembersStatusRequestProjects~Data~Network~Remote.DivisionRemote→Projects~Domain~Request.PostDivisionRequestProjects~Data~Network~Remote.MealRemote→Projects~Domain~Request.FetchMealRequestProjects~Data~Network~Remote.MealRemote→Projects~Domain~Request.FetchMonthlyMealRequestProjects~Data~Network~Remote.MemberRemote→Projects~Domain~Request.PatchMemberInfoRequestProjects~Data~Network~Remote.MemberRemote→Projects~Domain~Request.PatchPasswordRequestProjects~Data~Network~Remote.MemberRemote→Projects~Domain~Request.PatchStudentInfoRequestProjects~Data~Network~Remote.MemberRemote→Projects~Domain~Request.PostAuthCodeRequestProjects~Data~Network~Remote.MemberRemote→Projects~Domain~Request.PostJoinParentRequestProjects~Data~Network~Remote.MemberRemote→Projects~Domain~Request.PostJoinStudentRequestProjects~Data~Network~Remote.MemberRemote→Projects~Domain~Request.PostRelationRequestProjects~Data~Network~Remote.MemberRemote→Projects~Domain~Request.PostVerifyAuthCodeRequestProjects~Data~Network~Remote.NightStudyRemote→Projects~Domain~Request.NightStudyBanRequestProjects~Data~Network~Remote.NightStudyRemote→Projects~Domain~Request.PostNightStudyProjectRequestProjects~Data~Network~Remote.NightStudyRemote→Projects~Domain~Request.PostNightStudyRequestProjects~Data~Network~Remote.NoticeRemote→Projects~Domain~Request.FetchNoticeByDivisionRequest
- Direction
- Projects~Data~Network~Remote uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~Network~Remote, while a change to Projects~Data~Network~Remote can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~Network~Remote uses a module listed above it, which is the healthy direction.
12→6 Projects~Data~Network~Remote uses Projects~Domain~Response✕
- Connections
- 24 pairs of types, where a type in Projects~Data~Network~Remote uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~Network~Remote.AuthRemote→Projects~Domain~Response.DefaultResponseProjects~Data~Network~Remote.AuthRemote→Projects~Domain~Response.ResponseProjects~Data~Network~Remote.BannerRemote→Projects~Domain~Response.ResponseProjects~Data~Network~Remote.BusRemote→Projects~Domain~Response.DefaultResponseProjects~Data~Network~Remote.BusRemote→Projects~Domain~Response.ResponseProjects~Data~Network~Remote.ClubRemote→Projects~Domain~Response.ResponseProjects~Data~Network~Remote.DivisionRemote→Projects~Domain~Response.DefaultResponseProjects~Data~Network~Remote.DivisionRemote→Projects~Domain~Response.ResponseProjects~Data~Network~Remote.MealRemote→Projects~Domain~Response.ResponseProjects~Data~Network~Remote.MemberRemote→Projects~Domain~Response.DefaultResponseProjects~Data~Network~Remote.MemberRemote→Projects~Domain~Response.ResponseProjects~Data~Network~Remote.NightStudyRemote→Projects~Domain~Response.DefaultResponseProjects~Data~Network~Remote.NightStudyRemote→Projects~Domain~Response.ResponseProjects~Data~Network~Remote.NoticeRemote→Projects~Domain~Response.ResponseProjects~Data~Network~Remote.OutGoingRemote→Projects~Domain~Response.DefaultResponseProjects~Data~Network~Remote.OutGoingRemote→Projects~Domain~Response.ResponseProjects~Data~Network~Remote.OutSleepingRemote→Projects~Domain~Response.DefaultResponseProjects~Data~Network~Remote.OutSleepingRemote→Projects~Domain~Response.ResponseProjects~Data~Network~Remote.PointRemote→Projects~Domain~Response.ResponseProjects~Data~Network~Remote.RemoteProtocol→Projects~Domain~Response.ResponseProjects~Data~Network~Remote.ScheduleRemote→Projects~Domain~Response.ResponseProjects~Data~Network~Remote.UploadRemote→Projects~Domain~Response.ResponseProjects~Data~Network~Remote.WakeupSongRemote→Projects~Domain~Response.DefaultResponseProjects~Data~Network~Remote.WakeupSongRemote→Projects~Domain~Response.Response
- Direction
- Projects~Data~Network~Remote uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~Network~Remote, while a change to Projects~Data~Network~Remote can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~Network~Remote uses a module listed above it, which is the healthy direction.
12→9 Projects~Data~Network~Remote uses Projects~Domain~Entity✕
- Connections
- 1 pair of types, where a type in Projects~Data~Network~Remote uses a type in Projects~Domain~Entity.
- The types involved
Projects~Data~Network~Remote.MemberRemote→Projects~Domain~Entity.AuthType
- Direction
- Projects~Data~Network~Remote uses Projects~Domain~Entity, so a change to Projects~Domain~Entity can break Projects~Data~Network~Remote, while a change to Projects~Data~Network~Remote can't break Projects~Domain~Entity.
- Position
- Below the diagonal: Projects~Data~Network~Remote uses a module listed above it, which is the healthy direction.
12→10 Projects~Data~Network~Remote uses Projects~Data~Network✕
- Connections
- 9 pairs of types, where a type in Projects~Data~Network~Remote uses a type in Projects~Data~Network.
- The types involved
Projects~Data~Network~Remote.BusRemote→Projects~Data~Network.IntProjects~Data~Network~Remote.ClubRemote→Projects~Data~Network.IntProjects~Data~Network~Remote.DivisionRemote→Projects~Data~Network.IntProjects~Data~Network~Remote.MemberRemote→Projects~Data~Network.StringProjects~Data~Network~Remote.NightStudyRemote→Projects~Data~Network.IntProjects~Data~Network~Remote.OutGoingRemote→Projects~Data~Network.IntProjects~Data~Network~Remote.OutSleepingRemote→Projects~Data~Network.IntProjects~Data~Network~Remote.RemoteInterceptor→Projects~Data~Network.StringProjects~Data~Network~Remote.WakeupSongRemote→Projects~Data~Network.Int
- Direction
- Projects~Data~Network~Remote uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~Network~Remote, while a change to Projects~Data~Network~Remote can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~Network~Remote uses a module listed above it, which is the healthy direction.
13→2 Projects~Feature~All uses Projects~Feature~Core✕
- Connections
- 1 pair of types, where a type in Projects~Feature~All uses a type in Projects~Feature~Core.
- The types involved
Projects~Feature~All.AllViewModel→Projects~Feature~Core.OnAppearProtocol
- Direction
- Projects~Feature~All uses Projects~Feature~Core, so a change to Projects~Feature~Core can break Projects~Feature~All, while a change to Projects~Feature~All can't break Projects~Feature~Core.
- Position
- Below the diagonal: Projects~Feature~All uses a module listed above it, which is the healthy direction.
13→4 Projects~Feature~All uses Projects~Shared~SwiftUI✕
- Connections
- 7 pairs of types, where a type in Projects~Feature~All uses a type in Projects~Shared~SwiftUI.
- The types involved
Projects~Feature~All.AllCell→Projects~Shared~SwiftUI.ViewProjects~Feature~All.AllView→Projects~Shared~SwiftUI.ViewProjects~Feature~All.EditMemberInfoView→Projects~Shared~SwiftUI.ViewProjects~Feature~All.PointCell→Projects~Shared~SwiftUI.ViewProjects~Feature~All.PointView→Projects~Shared~SwiftUI.ViewProjects~Feature~All.SettingCell→Projects~Shared~SwiftUI.ViewProjects~Feature~All.SettingView→Projects~Shared~SwiftUI.View
- Direction
- Projects~Feature~All uses Projects~Shared~SwiftUI, so a change to Projects~Shared~SwiftUI can break Projects~Feature~All, while a change to Projects~Feature~All can't break Projects~Shared~SwiftUI.
- Position
- Below the diagonal: Projects~Feature~All uses a module listed above it, which is the healthy direction.
13→6 Projects~Feature~All uses Projects~Domain~Response✕
- Connections
- 6 pairs of types, where a type in Projects~Feature~All uses a type in Projects~Domain~Response.
- The types involved
Projects~Feature~All.AllViewModel→Projects~Domain~Response.MemberResponseProjects~Feature~All.EditMemberInfoView→Projects~Domain~Response.MemberResponseProjects~Feature~All.PointCell→Projects~Domain~Response.PointResponseProjects~Feature~All.PointViewModel→Projects~Domain~Response.PointResponseProjects~Feature~All.PointViewModel→Projects~Domain~Response.PointScoreResponseProjects~Feature~All.SettingViewModel→Projects~Domain~Response.MemberResponse
- Direction
- Projects~Feature~All uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Feature~All, while a change to Projects~Feature~All can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Feature~All uses a module listed above it, which is the healthy direction.
13→7 Projects~Feature~All uses Projects~Domain~Repository✕
- Connections
- 5 pairs of types, where a type in Projects~Feature~All uses a type in Projects~Domain~Repository.
- The types involved
Projects~Feature~All.AllViewModel→Projects~Domain~Repository.MemberRepositoryProjects~Feature~All.EditMemberInfoViewModel→Projects~Domain~Repository.MemberRepositoryProjects~Feature~All.EditMemberInfoViewModel→Projects~Domain~Repository.UploadRepositoryProjects~Feature~All.PointViewModel→Projects~Domain~Repository.PointRepositoryProjects~Feature~All.SettingViewModel→Projects~Domain~Repository.MemberRepository
- Direction
- Projects~Feature~All uses Projects~Domain~Repository, so a change to Projects~Domain~Repository can break Projects~Feature~All, while a change to Projects~Feature~All can't break Projects~Domain~Repository.
- Position
- Below the diagonal: Projects~Feature~All uses a module listed above it, which is the healthy direction.
13→10 Projects~Feature~All uses Projects~Data~Network✕
- Connections
- 6 pairs of types, where a type in Projects~Feature~All uses a type in Projects~Data~Network.
- The types involved
Projects~Feature~All.AllCell→Projects~Data~Network.StringProjects~Feature~All.AllView→Projects~Data~Network.IntProjects~Feature~All.EditMemberInfoView→Projects~Data~Network.StringProjects~Feature~All.EditMemberInfoViewModel→Projects~Data~Network.StringProjects~Feature~All.PointViewModel→Projects~Data~Network.IntProjects~Feature~All.SettingCell→Projects~Data~Network.String
- Direction
- Projects~Feature~All uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Feature~All, while a change to Projects~Feature~All can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Feature~All uses a module listed above it, which is the healthy direction.
14→3 Projects~Feature~Auth uses Projects~Domain~Model✕
- Connections
- 1 pair of types, where a type in Projects~Feature~Auth uses a type in Projects~Domain~Model.
- The types involved
Projects~Feature~Auth.RegisterViewModel→Projects~Domain~Model.ConnectStudent
- Direction
- Projects~Feature~Auth uses Projects~Domain~Model, so a change to Projects~Domain~Model can break Projects~Feature~Auth, while a change to Projects~Feature~Auth can't break Projects~Domain~Model.
- Position
- Below the diagonal: Projects~Feature~Auth uses a module listed above it, which is the healthy direction.
14→4 Projects~Feature~Auth uses Projects~Shared~SwiftUI✕
- Connections
- 6 pairs of types, where a type in Projects~Feature~Auth uses a type in Projects~Shared~SwiftUI.
- The types involved
Projects~Feature~Auth.AgreeCell→Projects~Shared~SwiftUI.ViewProjects~Feature~Auth.LoginView→Projects~Shared~SwiftUI.ViewProjects~Feature~Auth.RegisterAuthView→Projects~Shared~SwiftUI.ViewProjects~Feature~Auth.RegisterInfoView→Projects~Shared~SwiftUI.ViewProjects~Feature~Auth.RegisterSelectRoleView→Projects~Shared~SwiftUI.ViewProjects~Feature~Auth.SelectRoleCell→Projects~Shared~SwiftUI.View
- Direction
- Projects~Feature~Auth uses Projects~Shared~SwiftUI, so a change to Projects~Shared~SwiftUI can break Projects~Feature~Auth, while a change to Projects~Feature~Auth can't break Projects~Shared~SwiftUI.
- Position
- Below the diagonal: Projects~Feature~Auth uses a module listed above it, which is the healthy direction.
14→7 Projects~Feature~Auth uses Projects~Domain~Repository✕
- Connections
- 2 pairs of types, where a type in Projects~Feature~Auth uses a type in Projects~Domain~Repository.
- The types involved
Projects~Feature~Auth.LoginViewModel→Projects~Domain~Repository.AuthRepositoryProjects~Feature~Auth.RegisterViewModel→Projects~Domain~Repository.MemberRepository
- Direction
- Projects~Feature~Auth uses Projects~Domain~Repository, so a change to Projects~Domain~Repository can break Projects~Feature~Auth, while a change to Projects~Feature~Auth can't break Projects~Domain~Repository.
- Position
- Below the diagonal: Projects~Feature~Auth uses a module listed above it, which is the healthy direction.
14→9 Projects~Feature~Auth uses Projects~Domain~Entity✕
- Connections
- 2 pairs of types, where a type in Projects~Feature~Auth uses a type in Projects~Domain~Entity.
- The types involved
Projects~Feature~Auth.RegisterViewModel→Projects~Domain~Entity.RoleProjects~Feature~Auth.SelectRoleCell→Projects~Domain~Entity.Role
- Direction
- Projects~Feature~Auth uses Projects~Domain~Entity, so a change to Projects~Domain~Entity can break Projects~Feature~Auth, while a change to Projects~Feature~Auth can't break Projects~Domain~Entity.
- Position
- Below the diagonal: Projects~Feature~Auth uses a module listed above it, which is the healthy direction.
14→10 Projects~Feature~Auth uses Projects~Data~Network✕
- Connections
- 6 pairs of types, where a type in Projects~Feature~Auth uses a type in Projects~Data~Network.
- The types involved
Projects~Feature~Auth.AgreeCell→Projects~Data~Network.StringProjects~Feature~Auth.AuthStep→Projects~Data~Network.IntProjects~Feature~Auth.InfoStep→Projects~Data~Network.IntProjects~Feature~Auth.LoginViewModel→Projects~Data~Network.StringProjects~Feature~Auth.RegisterViewModel→Projects~Data~Network.IntProjects~Feature~Auth.RegisterViewModel→Projects~Data~Network.String
- Direction
- Projects~Feature~Auth uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Feature~Auth, while a change to Projects~Feature~Auth can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Feature~Auth uses a module listed above it, which is the healthy direction.
15→2 Projects~Feature~Home uses Projects~Feature~Core✕
- Connections
- 1 pair of types, where a type in Projects~Feature~Home uses a type in Projects~Feature~Core.
- The types involved
Projects~Feature~Home.HomeViewModel→Projects~Feature~Core.OnAppearProtocol
- Direction
- Projects~Feature~Home uses Projects~Feature~Core, so a change to Projects~Feature~Core can break Projects~Feature~Home, while a change to Projects~Feature~Home can't break Projects~Feature~Core.
- Position
- Below the diagonal: Projects~Feature~Home uses a module listed above it, which is the healthy direction.
15→3 Projects~Feature~Home uses Projects~Domain~Model✕
- Connections
- 2 pairs of types, where a type in Projects~Feature~Home uses a type in Projects~Domain~Model.
- The types involved
Projects~Feature~Home.HomeViewModel→Projects~Domain~Model.MealModelProjects~Feature~Home.MealContainer→Projects~Domain~Model.MealModel
- Direction
- Projects~Feature~Home uses Projects~Domain~Model, so a change to Projects~Domain~Model can break Projects~Feature~Home, while a change to Projects~Feature~Home can't break Projects~Domain~Model.
- Position
- Below the diagonal: Projects~Feature~Home uses a module listed above it, which is the healthy direction.
15→4 Projects~Feature~Home uses Projects~Shared~SwiftUI✕
- Connections
- 8 pairs of types, where a type in Projects~Feature~Home uses a type in Projects~Shared~SwiftUI.
- The types involved
Projects~Feature~Home.BannerContainer→Projects~Shared~SwiftUI.ViewProjects~Feature~Home.HomeView→Projects~Shared~SwiftUI.ViewProjects~Feature~Home.MealContainer→Projects~Shared~SwiftUI.ViewProjects~Feature~Home.NightStudyStatusContainer→Projects~Shared~SwiftUI.ViewProjects~Feature~Home.OutStatusContainer→Projects~Shared~SwiftUI.ViewProjects~Feature~Home.ScheduleContainer→Projects~Shared~SwiftUI.ViewProjects~Feature~Home.SupportingContainer→Projects~Shared~SwiftUI.ViewProjects~Feature~Home.WakeupSongContainer→Projects~Shared~SwiftUI.View
- Direction
- Projects~Feature~Home uses Projects~Shared~SwiftUI, so a change to Projects~Shared~SwiftUI can break Projects~Feature~Home, while a change to Projects~Feature~Home can't break Projects~Shared~SwiftUI.
- Position
- Below the diagonal: Projects~Feature~Home uses a module listed above it, which is the healthy direction.
15→6 Projects~Feature~Home uses Projects~Domain~Response✕
- Connections
- 12 pairs of types, where a type in Projects~Feature~Home uses a type in Projects~Domain~Response.
- The types involved
Projects~Feature~Home.BannerContainer→Projects~Domain~Response.BannerResponseProjects~Feature~Home.HomeViewModel→Projects~Domain~Response.BannerResponseProjects~Feature~Home.HomeViewModel→Projects~Domain~Response.MemberResponseProjects~Feature~Home.HomeViewModel→Projects~Domain~Response.NightStudyResponseProjects~Feature~Home.HomeViewModel→Projects~Domain~Response.OutGoingResponseProjects~Feature~Home.HomeViewModel→Projects~Domain~Response.OutSleepingResponseProjects~Feature~Home.HomeViewModel→Projects~Domain~Response.ScheduleResponseProjects~Feature~Home.HomeViewModel→Projects~Domain~Response.WakeupSongResponseProjects~Feature~Home.NightStudyStatusContainer→Projects~Domain~Response.NightStudyResponseProjects~Feature~Home.OutStatusContainer→Projects~Domain~Response.OutGoingResponseProjects~Feature~Home.ScheduleContainer→Projects~Domain~Response.ScheduleResponseProjects~Feature~Home.WakeupSongContainer→Projects~Domain~Response.WakeupSongResponse
- Direction
- Projects~Feature~Home uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Feature~Home, while a change to Projects~Feature~Home can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Feature~Home uses a module listed above it, which is the healthy direction.
15→7 Projects~Feature~Home uses Projects~Domain~Repository✕
- Connections
- 8 pairs of types, where a type in Projects~Feature~Home uses a type in Projects~Domain~Repository.
- The types involved
Projects~Feature~Home.HomeViewModel→Projects~Domain~Repository.BannerRepositoryProjects~Feature~Home.HomeViewModel→Projects~Domain~Repository.MealRepositoryProjects~Feature~Home.HomeViewModel→Projects~Domain~Repository.MemberRepositoryProjects~Feature~Home.HomeViewModel→Projects~Domain~Repository.NightStudyRepositoryProjects~Feature~Home.HomeViewModel→Projects~Domain~Repository.OutGoingRepositoryProjects~Feature~Home.HomeViewModel→Projects~Domain~Repository.OutSleepingRepositoryProjects~Feature~Home.HomeViewModel→Projects~Domain~Repository.ScheduleRepositoryProjects~Feature~Home.HomeViewModel→Projects~Domain~Repository.WakeupSongRepository
- Direction
- Projects~Feature~Home uses Projects~Domain~Repository, so a change to Projects~Domain~Repository can break Projects~Feature~Home, while a change to Projects~Feature~Home can't break Projects~Domain~Repository.
- Position
- Below the diagonal: Projects~Feature~Home uses a module listed above it, which is the healthy direction.
15→9 Projects~Feature~Home uses Projects~Domain~Entity✕
- Connections
- 2 pairs of types, where a type in Projects~Feature~Home uses a type in Projects~Domain~Entity.
- The types involved
Projects~Feature~Home.HomeViewModel→Projects~Domain~Entity.MealTypeProjects~Feature~Home.MealContainer→Projects~Domain~Entity.MealType
- Direction
- Projects~Feature~Home uses Projects~Domain~Entity, so a change to Projects~Domain~Entity can break Projects~Feature~Home, while a change to Projects~Feature~Home can't break Projects~Domain~Entity.
- Position
- Below the diagonal: Projects~Feature~Home uses a module listed above it, which is the healthy direction.
15→10 Projects~Feature~Home uses Projects~Data~Network✕
- Connections
- 3 pairs of types, where a type in Projects~Feature~Home uses a type in Projects~Data~Network.
- The types involved
Projects~Feature~Home.HomeView→Projects~Data~Network.IntProjects~Feature~Home.HomeViewModel→Projects~Data~Network.IntProjects~Feature~Home.SupportingContainer→Projects~Data~Network.String
- Direction
- Projects~Feature~Home uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Feature~Home, while a change to Projects~Feature~Home can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Feature~Home uses a module listed above it, which is the healthy direction.
16→2 Projects~Feature~Meal uses Projects~Feature~Core✕
- Connections
- 1 pair of types, where a type in Projects~Feature~Meal uses a type in Projects~Feature~Core.
- The types involved
Projects~Feature~Meal.MealViewModel→Projects~Feature~Core.OnAppearProtocol
- Direction
- Projects~Feature~Meal uses Projects~Feature~Core, so a change to Projects~Feature~Core can break Projects~Feature~Meal, while a change to Projects~Feature~Meal can't break Projects~Feature~Core.
- Position
- Below the diagonal: Projects~Feature~Meal uses a module listed above it, which is the healthy direction.
16→3 Projects~Feature~Meal uses Projects~Domain~Model✕
- Connections
- 2 pairs of types, where a type in Projects~Feature~Meal uses a type in Projects~Domain~Model.
- The types involved
Projects~Feature~Meal.MealCell→Projects~Domain~Model.MealDetailProjects~Feature~Meal.MealViewModel→Projects~Domain~Model.MealModel
- Direction
- Projects~Feature~Meal uses Projects~Domain~Model, so a change to Projects~Domain~Model can break Projects~Feature~Meal, while a change to Projects~Feature~Meal can't break Projects~Domain~Model.
- Position
- Below the diagonal: Projects~Feature~Meal uses a module listed above it, which is the healthy direction.
16→4 Projects~Feature~Meal uses Projects~Shared~SwiftUI✕
- Connections
- 2 pairs of types, where a type in Projects~Feature~Meal uses a type in Projects~Shared~SwiftUI.
- The types involved
Projects~Feature~Meal.MealCell→Projects~Shared~SwiftUI.ViewProjects~Feature~Meal.MealView→Projects~Shared~SwiftUI.View
- Direction
- Projects~Feature~Meal uses Projects~Shared~SwiftUI, so a change to Projects~Shared~SwiftUI can break Projects~Feature~Meal, while a change to Projects~Feature~Meal can't break Projects~Shared~SwiftUI.
- Position
- Below the diagonal: Projects~Feature~Meal uses a module listed above it, which is the healthy direction.
16→7 Projects~Feature~Meal uses Projects~Domain~Repository✕
- Connections
- 1 pair of types, where a type in Projects~Feature~Meal uses a type in Projects~Domain~Repository.
- The types involved
Projects~Feature~Meal.MealViewModel→Projects~Domain~Repository.MealRepository
- Direction
- Projects~Feature~Meal uses Projects~Domain~Repository, so a change to Projects~Domain~Repository can break Projects~Feature~Meal, while a change to Projects~Feature~Meal can't break Projects~Domain~Repository.
- Position
- Below the diagonal: Projects~Feature~Meal uses a module listed above it, which is the healthy direction.
16→9 Projects~Feature~Meal uses Projects~Domain~Entity✕
- Connections
- 3 pairs of types, where a type in Projects~Feature~Meal uses a type in Projects~Domain~Entity.
- The types involved
Projects~Feature~Meal.MealCell→Projects~Domain~Entity.MealTypeProjects~Feature~Meal.MealView→Projects~Domain~Entity.DateProjects~Feature~Meal.MealViewModel→Projects~Domain~Entity.Date
- Direction
- Projects~Feature~Meal uses Projects~Domain~Entity, so a change to Projects~Domain~Entity can break Projects~Feature~Meal, while a change to Projects~Feature~Meal can't break Projects~Domain~Entity.
- Position
- Below the diagonal: Projects~Feature~Meal uses a module listed above it, which is the healthy direction.
16→10 Projects~Feature~Meal uses Projects~Data~Network✕
- Connections
- 1 pair of types, where a type in Projects~Feature~Meal uses a type in Projects~Data~Network.
- The types involved
Projects~Feature~Meal.MealView→Projects~Data~Network.Int
- Direction
- Projects~Feature~Meal uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Feature~Meal, while a change to Projects~Feature~Meal can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Feature~Meal uses a module listed above it, which is the healthy direction.
17→2 Projects~Feature~NightStudy uses Projects~Feature~Core✕
- Connections
- 4 pairs of types, where a type in Projects~Feature~NightStudy uses a type in Projects~Feature~Core.
- The types involved
Projects~Feature~NightStudy.ApproveNightStudyViewModel→Projects~Feature~Core.OnAppearProtocolProjects~Feature~NightStudy.ManageNightStudyViewModel→Projects~Feature~Core.OnAppearProtocolProjects~Feature~NightStudy.NightProjectApplyViewModel→Projects~Feature~Core.OnAppearProtocolProjects~Feature~NightStudy.NightStudyViewModel→Projects~Feature~Core.OnAppearProtocol
- Direction
- Projects~Feature~NightStudy uses Projects~Feature~Core, so a change to Projects~Feature~Core can break Projects~Feature~NightStudy, while a change to Projects~Feature~NightStudy can't break Projects~Feature~Core.
- Position
- Below the diagonal: Projects~Feature~NightStudy uses a module listed above it, which is the healthy direction.
17→4 Projects~Feature~NightStudy uses Projects~Shared~SwiftUI✕
- Connections
- 15 pairs of types, where a type in Projects~Feature~NightStudy uses a type in Projects~Shared~SwiftUI.
- The types involved
Projects~Feature~NightStudy.ApproveNightStudySheetCell→Projects~Shared~SwiftUI.ViewProjects~Feature~NightStudy.ApproveNightStudyView→Projects~Shared~SwiftUI.ViewProjects~Feature~NightStudy.ApproveStudentInfoHeader→Projects~Shared~SwiftUI.ViewProjects~Feature~NightStudy.ApprovedNightStudyStudentCell→Projects~Shared~SwiftUI.ViewProjects~Feature~NightStudy.DodamStudentCell→Projects~Shared~SwiftUI.ViewProjects~Feature~NightStudy.ManageNightStudyView→Projects~Shared~SwiftUI.ViewProjects~Feature~NightStudy.NightProjectApplyCell→Projects~Shared~SwiftUI.ViewProjects~Feature~NightStudy.NightProjectApplyView→Projects~Shared~SwiftUI.ViewProjects~Feature~NightStudy.NightStudyApplyCell→Projects~Shared~SwiftUI.ViewProjects~Feature~NightStudy.NightStudyApplyMainView→Projects~Shared~SwiftUI.ViewProjects~Feature~NightStudy.NightStudyApplyView→Projects~Shared~SwiftUI.ViewProjects~Feature~NightStudy.NightStudyView→Projects~Shared~SwiftUI.ViewProjects~Feature~NightStudy.PendingNightStudyStudentCell→Projects~Shared~SwiftUI.ViewProjects~Feature~NightStudy.PendingStudentInfoHeader→Projects~Shared~SwiftUI.ViewProjects~Feature~NightStudy.RejectNightStudySheetCell→Projects~Shared~SwiftUI.View
- Direction
- Projects~Feature~NightStudy uses Projects~Shared~SwiftUI, so a change to Projects~Shared~SwiftUI can break Projects~Feature~NightStudy, while a change to Projects~Feature~NightStudy can't break Projects~Shared~SwiftUI.
- Position
- Below the diagonal: Projects~Feature~NightStudy uses a module listed above it, which is the healthy direction.
17→6 Projects~Feature~NightStudy uses Projects~Domain~Response✕
- Connections
- 13 pairs of types, where a type in Projects~Feature~NightStudy uses a type in Projects~Domain~Response.
- The types involved
Projects~Feature~NightStudy.ApproveNightStudySheetCell→Projects~Domain~Response.OngoingNightStudyResponseProjects~Feature~NightStudy.ApproveNightStudyViewModel→Projects~Domain~Response.OngoingNightStudyResponseProjects~Feature~NightStudy.ApprovedNightStudyStudentCell→Projects~Domain~Response.OngoingNightStudyResponseProjects~Feature~NightStudy.DodamStudentCell→Projects~Domain~Response.NightStudyStudentResponseProjects~Feature~NightStudy.ManageNightStudyViewModel→Projects~Domain~Response.OngoingNightStudyResponseProjects~Feature~NightStudy.NightProjectApplyCell→Projects~Domain~Response.NightStudyProjectResponseProjects~Feature~NightStudy.NightProjectApplyViewModel→Projects~Domain~Response.NightStudyStudentResponseProjects~Feature~NightStudy.NightStudyApplyCell→Projects~Domain~Response.NightStudyResponseProjects~Feature~NightStudy.NightStudyViewModel→Projects~Domain~Response.NightStudyBanResponseProjects~Feature~NightStudy.NightStudyViewModel→Projects~Domain~Response.NightStudyProjectResponseProjects~Feature~NightStudy.NightStudyViewModel→Projects~Domain~Response.NightStudyResponseProjects~Feature~NightStudy.PendingNightStudyStudentCell→Projects~Domain~Response.OngoingNightStudyResponseProjects~Feature~NightStudy.RejectNightStudySheetCell→Projects~Domain~Response.OngoingNightStudyResponse
- Direction
- Projects~Feature~NightStudy uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Feature~NightStudy, while a change to Projects~Feature~NightStudy can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Feature~NightStudy uses a module listed above it, which is the healthy direction.
17→7 Projects~Feature~NightStudy uses Projects~Domain~Repository✕
- Connections
- 5 pairs of types, where a type in Projects~Feature~NightStudy uses a type in Projects~Domain~Repository.
- The types involved
Projects~Feature~NightStudy.ApproveNightStudyViewModel→Projects~Domain~Repository.NightStudyRepositoryProjects~Feature~NightStudy.ManageNightStudyViewModel→Projects~Domain~Repository.NightStudyRepositoryProjects~Feature~NightStudy.NightProjectApplyViewModel→Projects~Domain~Repository.NightStudyRepositoryProjects~Feature~NightStudy.NightStudyApplyViewModel→Projects~Domain~Repository.NightStudyRepositoryProjects~Feature~NightStudy.NightStudyViewModel→Projects~Domain~Repository.NightStudyRepository
- Direction
- Projects~Feature~NightStudy uses Projects~Domain~Repository, so a change to Projects~Domain~Repository can break Projects~Feature~NightStudy, while a change to Projects~Feature~NightStudy can't break Projects~Domain~Repository.
- Position
- Below the diagonal: Projects~Feature~NightStudy uses a module listed above it, which is the healthy direction.
17→9 Projects~Feature~NightStudy uses Projects~Domain~Entity✕
- Connections
- 7 pairs of types, where a type in Projects~Feature~NightStudy uses a type in Projects~Domain~Entity.
- The types involved
Projects~Feature~NightStudy.ManageNightStudyViewModel→Projects~Domain~Entity.DateProjects~Feature~NightStudy.NightProjectApplyViewModel→Projects~Domain~Entity.DateProjects~Feature~NightStudy.NightProjectApplyViewModel→Projects~Domain~Entity.NightStudyProjectTypeProjects~Feature~NightStudy.NightStudyApplyViewModel→Projects~Domain~Entity.DateProjects~Feature~NightStudy.NightStudyApplyViewModel→Projects~Domain~Entity.NightStudyPlaceProjects~Feature~NightStudy.NightStudyApplyViewModel→Projects~Domain~Entity.NightStudyTypeProjects~Feature~NightStudy.RejectNightStudySheetCell→Projects~Domain~Entity.Date
- Direction
- Projects~Feature~NightStudy uses Projects~Domain~Entity, so a change to Projects~Domain~Entity can break Projects~Feature~NightStudy, while a change to Projects~Feature~NightStudy can't break Projects~Domain~Entity.
- Position
- Below the diagonal: Projects~Feature~NightStudy uses a module listed above it, which is the healthy direction.
17→10 Projects~Feature~NightStudy uses Projects~Data~Network✕
- Connections
- 11 pairs of types, where a type in Projects~Feature~NightStudy uses a type in Projects~Data~Network.
- The types involved
Projects~Feature~NightStudy.ApproveNightStudyViewModel→Projects~Data~Network.IntProjects~Feature~NightStudy.ApproveNightStudyViewModel→Projects~Data~Network.StringProjects~Feature~NightStudy.ManageNightStudyViewModel→Projects~Data~Network.IntProjects~Feature~NightStudy.ManageNightStudyViewModel→Projects~Data~Network.StringProjects~Feature~NightStudy.NightProjectApplyViewModel→Projects~Data~Network.IntProjects~Feature~NightStudy.NightProjectApplyViewModel→Projects~Data~Network.StringProjects~Feature~NightStudy.NightStudyApplyMainView→Projects~Data~Network.IntProjects~Feature~NightStudy.NightStudyApplyViewModel→Projects~Data~Network.StringProjects~Feature~NightStudy.NightStudyView→Projects~Data~Network.IntProjects~Feature~NightStudy.NightStudyViewModel→Projects~Data~Network.IntProjects~Feature~NightStudy.RejectNightStudySheetCell→Projects~Data~Network.String
- Direction
- Projects~Feature~NightStudy uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Feature~NightStudy, while a change to Projects~Feature~NightStudy can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Feature~NightStudy uses a module listed above it, which is the healthy direction.
18→2 Projects~Feature~Out uses Projects~Feature~Core✕
- Connections
- 1 pair of types, where a type in Projects~Feature~Out uses a type in Projects~Feature~Core.
- The types involved
Projects~Feature~Out.OutViewModel→Projects~Feature~Core.OnAppearProtocol
- Direction
- Projects~Feature~Out uses Projects~Feature~Core, so a change to Projects~Feature~Core can break Projects~Feature~Out, while a change to Projects~Feature~Out can't break Projects~Feature~Core.
- Position
- Below the diagonal: Projects~Feature~Out uses a module listed above it, which is the healthy direction.
18→4 Projects~Feature~Out uses Projects~Shared~SwiftUI✕
- Connections
- 4 pairs of types, where a type in Projects~Feature~Out uses a type in Projects~Shared~SwiftUI.
- The types involved
Projects~Feature~Out.OutApplyView→Projects~Shared~SwiftUI.ViewProjects~Feature~Out.OutGoingCell→Projects~Shared~SwiftUI.ViewProjects~Feature~Out.OutSleepingCell→Projects~Shared~SwiftUI.ViewProjects~Feature~Out.OutView→Projects~Shared~SwiftUI.View
- Direction
- Projects~Feature~Out uses Projects~Shared~SwiftUI, so a change to Projects~Shared~SwiftUI can break Projects~Feature~Out, while a change to Projects~Feature~Out can't break Projects~Shared~SwiftUI.
- Position
- Below the diagonal: Projects~Feature~Out uses a module listed above it, which is the healthy direction.
18→6 Projects~Feature~Out uses Projects~Domain~Response✕
- Connections
- 4 pairs of types, where a type in Projects~Feature~Out uses a type in Projects~Domain~Response.
- The types involved
Projects~Feature~Out.OutGoingCell→Projects~Domain~Response.OutGoingResponseProjects~Feature~Out.OutSleepingCell→Projects~Domain~Response.OutSleepingResponseProjects~Feature~Out.OutViewModel→Projects~Domain~Response.OutGoingResponseProjects~Feature~Out.OutViewModel→Projects~Domain~Response.OutSleepingResponse
- Direction
- Projects~Feature~Out uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Feature~Out, while a change to Projects~Feature~Out can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Feature~Out uses a module listed above it, which is the healthy direction.
18→7 Projects~Feature~Out uses Projects~Domain~Repository✕
- Connections
- 4 pairs of types, where a type in Projects~Feature~Out uses a type in Projects~Domain~Repository.
- The types involved
Projects~Feature~Out.OutApplyViewModel→Projects~Domain~Repository.OutGoingRepositoryProjects~Feature~Out.OutApplyViewModel→Projects~Domain~Repository.OutSleepingRepositoryProjects~Feature~Out.OutViewModel→Projects~Domain~Repository.OutGoingRepositoryProjects~Feature~Out.OutViewModel→Projects~Domain~Repository.OutSleepingRepository
- Direction
- Projects~Feature~Out uses Projects~Domain~Repository, so a change to Projects~Domain~Repository can break Projects~Feature~Out, while a change to Projects~Feature~Out can't break Projects~Domain~Repository.
- Position
- Below the diagonal: Projects~Feature~Out uses a module listed above it, which is the healthy direction.
18→9 Projects~Feature~Out uses Projects~Domain~Entity✕
- Connections
- 1 pair of types, where a type in Projects~Feature~Out uses a type in Projects~Domain~Entity.
- The types involved
Projects~Feature~Out.OutApplyViewModel→Projects~Domain~Entity.Date
- Direction
- Projects~Feature~Out uses Projects~Domain~Entity, so a change to Projects~Domain~Entity can break Projects~Feature~Out, while a change to Projects~Feature~Out can't break Projects~Domain~Entity.
- Position
- Below the diagonal: Projects~Feature~Out uses a module listed above it, which is the healthy direction.
18→10 Projects~Feature~Out uses Projects~Data~Network✕
- Connections
- 4 pairs of types, where a type in Projects~Feature~Out uses a type in Projects~Data~Network.
- The types involved
Projects~Feature~Out.OutApplyView→Projects~Data~Network.IntProjects~Feature~Out.OutApplyViewModel→Projects~Data~Network.StringProjects~Feature~Out.OutView→Projects~Data~Network.IntProjects~Feature~Out.OutViewModel→Projects~Data~Network.Int
- Direction
- Projects~Feature~Out uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Feature~Out, while a change to Projects~Feature~Out can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Feature~Out uses a module listed above it, which is the healthy direction.
19→1 Projects~Data~DataSource~Auth uses Projects~Data~DataSource✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Auth uses a type in Projects~Data~DataSource.
- The types involved
Projects~Data~DataSource~Auth.AuthDataSource→Projects~Data~DataSource.DataSourceProtocol
- Direction
- Projects~Data~DataSource~Auth uses Projects~Data~DataSource, so a change to Projects~Data~DataSource can break Projects~Data~DataSource~Auth, while a change to Projects~Data~DataSource~Auth can't break Projects~Data~DataSource.
- Position
- Below the diagonal: Projects~Data~DataSource~Auth uses a module listed above it, which is the healthy direction.
19→5 Projects~Data~DataSource~Auth uses Projects~Domain~Request✕
- Connections
- 3 pairs of types, where a type in Projects~Data~DataSource~Auth uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~DataSource~Auth.AuthDataSource→Projects~Domain~Request.DeepLinkLoginRequestProjects~Data~DataSource~Auth.AuthDataSource→Projects~Domain~Request.PostLoginRequestProjects~Data~DataSource~Auth.AuthDataSource→Projects~Domain~Request.PostReissueRequest
- Direction
- Projects~Data~DataSource~Auth uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~DataSource~Auth, while a change to Projects~Data~DataSource~Auth can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~DataSource~Auth uses a module listed above it, which is the healthy direction.
19→6 Projects~Data~DataSource~Auth uses Projects~Domain~Response✕
- Connections
- 3 pairs of types, where a type in Projects~Data~DataSource~Auth uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~DataSource~Auth.AuthDataSource→Projects~Domain~Response.DefaultResponseProjects~Data~DataSource~Auth.AuthDataSource→Projects~Domain~Response.LoginResponseProjects~Data~DataSource~Auth.AuthDataSource→Projects~Domain~Response.ReissueResponse
- Direction
- Projects~Data~DataSource~Auth uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~DataSource~Auth, while a change to Projects~Data~DataSource~Auth can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~DataSource~Auth uses a module listed above it, which is the healthy direction.
19→12 Projects~Data~DataSource~Auth uses Projects~Data~Network~Remote✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Auth uses a type in Projects~Data~Network~Remote.
- The types involved
Projects~Data~DataSource~Auth.AuthDataSource→Projects~Data~Network~Remote.AuthRemote
- Direction
- Projects~Data~DataSource~Auth uses Projects~Data~Network~Remote, so a change to Projects~Data~Network~Remote can break Projects~Data~DataSource~Auth, while a change to Projects~Data~DataSource~Auth can't break Projects~Data~Network~Remote.
- Position
- Below the diagonal: Projects~Data~DataSource~Auth uses a module listed above it, which is the healthy direction.
20→1 Projects~Data~DataSource~Bus uses Projects~Data~DataSource✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Bus uses a type in Projects~Data~DataSource.
- The types involved
Projects~Data~DataSource~Bus.BusDataSource→Projects~Data~DataSource.DataSourceProtocol
- Direction
- Projects~Data~DataSource~Bus uses Projects~Data~DataSource, so a change to Projects~Data~DataSource can break Projects~Data~DataSource~Bus, while a change to Projects~Data~DataSource~Bus can't break Projects~Data~DataSource.
- Position
- Below the diagonal: Projects~Data~DataSource~Bus uses a module listed above it, which is the healthy direction.
20→6 Projects~Data~DataSource~Bus uses Projects~Domain~Response✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Bus uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~DataSource~Bus.BusDataSource→Projects~Domain~Response.BusResponse
- Direction
- Projects~Data~DataSource~Bus uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~DataSource~Bus, while a change to Projects~Data~DataSource~Bus can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~DataSource~Bus uses a module listed above it, which is the healthy direction.
20→10 Projects~Data~DataSource~Bus uses Projects~Data~Network✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Bus uses a type in Projects~Data~Network.
- The types involved
Projects~Data~DataSource~Bus.BusDataSource→Projects~Data~Network.Int
- Direction
- Projects~Data~DataSource~Bus uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~DataSource~Bus, while a change to Projects~Data~DataSource~Bus can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~DataSource~Bus uses a module listed above it, which is the healthy direction.
20→12 Projects~Data~DataSource~Bus uses Projects~Data~Network~Remote✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Bus uses a type in Projects~Data~Network~Remote.
- The types involved
Projects~Data~DataSource~Bus.BusDataSource→Projects~Data~Network~Remote.BusRemote
- Direction
- Projects~Data~DataSource~Bus uses Projects~Data~Network~Remote, so a change to Projects~Data~Network~Remote can break Projects~Data~DataSource~Bus, while a change to Projects~Data~DataSource~Bus can't break Projects~Data~Network~Remote.
- Position
- Below the diagonal: Projects~Data~DataSource~Bus uses a module listed above it, which is the healthy direction.
21→1 Projects~Data~DataSource~Club uses Projects~Data~DataSource✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Club uses a type in Projects~Data~DataSource.
- The types involved
Projects~Data~DataSource~Club.ClubDataSource→Projects~Data~DataSource.DataSourceProtocol
- Direction
- Projects~Data~DataSource~Club uses Projects~Data~DataSource, so a change to Projects~Data~DataSource can break Projects~Data~DataSource~Club, while a change to Projects~Data~DataSource~Club can't break Projects~Data~DataSource.
- Position
- Below the diagonal: Projects~Data~DataSource~Club uses a module listed above it, which is the healthy direction.
21→5 Projects~Data~DataSource~Club uses Projects~Domain~Request✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Club uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~DataSource~Club.ClubDataSource→Projects~Domain~Request.ClubApplyRequest
- Direction
- Projects~Data~DataSource~Club uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~DataSource~Club, while a change to Projects~Data~DataSource~Club can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~DataSource~Club uses a module listed above it, which is the healthy direction.
21→6 Projects~Data~DataSource~Club uses Projects~Domain~Response✕
- Connections
- 8 pairs of types, where a type in Projects~Data~DataSource~Club uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~DataSource~Club.ClubDataSource→Projects~Domain~Response.ClubDetailResponseProjects~Data~DataSource~Club.ClubDataSource→Projects~Domain~Response.ClubJoinRequestsResponseProjects~Data~DataSource~Club.ClubDataSource→Projects~Domain~Response.ClubMembersInfoResponseProjects~Data~DataSource~Club.ClubDataSource→Projects~Domain~Response.ClubRegisterTimeResponseProjects~Data~DataSource~Club.ClubDataSource→Projects~Domain~Response.ClubsResponseProjects~Data~DataSource~Club.ClubDataSource→Projects~Domain~Response.JoinedClubResponseProjects~Data~DataSource~Club.ClubDataSource→Projects~Domain~Response.MyApplyClubResponseProjects~Data~DataSource~Club.ClubDataSource→Projects~Domain~Response.MyClubResponse
- Direction
- Projects~Data~DataSource~Club uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~DataSource~Club, while a change to Projects~Data~DataSource~Club can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~DataSource~Club uses a module listed above it, which is the healthy direction.
21→10 Projects~Data~DataSource~Club uses Projects~Data~Network✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Club uses a type in Projects~Data~Network.
- The types involved
Projects~Data~DataSource~Club.ClubDataSource→Projects~Data~Network.Int
- Direction
- Projects~Data~DataSource~Club uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~DataSource~Club, while a change to Projects~Data~DataSource~Club can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~DataSource~Club uses a module listed above it, which is the healthy direction.
21→12 Projects~Data~DataSource~Club uses Projects~Data~Network~Remote✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Club uses a type in Projects~Data~Network~Remote.
- The types involved
Projects~Data~DataSource~Club.ClubDataSource→Projects~Data~Network~Remote.ClubRemote
- Direction
- Projects~Data~DataSource~Club uses Projects~Data~Network~Remote, so a change to Projects~Data~Network~Remote can break Projects~Data~DataSource~Club, while a change to Projects~Data~DataSource~Club can't break Projects~Data~Network~Remote.
- Position
- Below the diagonal: Projects~Data~DataSource~Club uses a module listed above it, which is the healthy direction.
22→1 Projects~Data~DataSource~Division uses Projects~Data~DataSource✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Division uses a type in Projects~Data~DataSource.
- The types involved
Projects~Data~DataSource~Division.DivisionDataSource→Projects~Data~DataSource.DataSourceProtocol
- Direction
- Projects~Data~DataSource~Division uses Projects~Data~DataSource, so a change to Projects~Data~DataSource can break Projects~Data~DataSource~Division, while a change to Projects~Data~DataSource~Division can't break Projects~Data~DataSource.
- Position
- Below the diagonal: Projects~Data~DataSource~Division uses a module listed above it, which is the healthy direction.
22→5 Projects~Data~DataSource~Division uses Projects~Domain~Request✕
- Connections
- 7 pairs of types, where a type in Projects~Data~DataSource~Division uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~DataSource~Division.DivisionDataSource→Projects~Domain~Request.AddMembersRequestProjects~Data~DataSource~Division.DivisionDataSource→Projects~Domain~Request.DeleteDivisionMembersRequestProjects~Data~DataSource~Division.DivisionDataSource→Projects~Domain~Request.FetchDivisionMembersRequestProjects~Data~DataSource~Division.DivisionDataSource→Projects~Domain~Request.FetchDivisionRequestProjects~Data~DataSource~Division.DivisionDataSource→Projects~Domain~Request.PatchMemberPermissionRequestProjects~Data~DataSource~Division.DivisionDataSource→Projects~Domain~Request.PatchMembersStatusRequestProjects~Data~DataSource~Division.DivisionDataSource→Projects~Domain~Request.PostDivisionRequest
- Direction
- Projects~Data~DataSource~Division uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~DataSource~Division, while a change to Projects~Data~DataSource~Division can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~DataSource~Division uses a module listed above it, which is the healthy direction.
22→6 Projects~Data~DataSource~Division uses Projects~Domain~Response✕
- Connections
- 4 pairs of types, where a type in Projects~Data~DataSource~Division uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~DataSource~Division.DivisionDataSource→Projects~Domain~Response.DivisionDetailResponseProjects~Data~DataSource~Division.DivisionDataSource→Projects~Domain~Response.DivisionMemberResponseProjects~Data~DataSource~Division.DivisionDataSource→Projects~Domain~Response.DivisionMembersCountResponseProjects~Data~DataSource~Division.DivisionDataSource→Projects~Domain~Response.DivisionOverviewResponse
- Direction
- Projects~Data~DataSource~Division uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~DataSource~Division, while a change to Projects~Data~DataSource~Division can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~DataSource~Division uses a module listed above it, which is the healthy direction.
22→10 Projects~Data~DataSource~Division uses Projects~Data~Network✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Division uses a type in Projects~Data~Network.
- The types involved
Projects~Data~DataSource~Division.DivisionDataSource→Projects~Data~Network.Int
- Direction
- Projects~Data~DataSource~Division uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~DataSource~Division, while a change to Projects~Data~DataSource~Division can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~DataSource~Division uses a module listed above it, which is the healthy direction.
22→12 Projects~Data~DataSource~Division uses Projects~Data~Network~Remote✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Division uses a type in Projects~Data~Network~Remote.
- The types involved
Projects~Data~DataSource~Division.DivisionDataSource→Projects~Data~Network~Remote.DivisionRemote
- Direction
- Projects~Data~DataSource~Division uses Projects~Data~Network~Remote, so a change to Projects~Data~Network~Remote can break Projects~Data~DataSource~Division, while a change to Projects~Data~DataSource~Division can't break Projects~Data~Network~Remote.
- Position
- Below the diagonal: Projects~Data~DataSource~Division uses a module listed above it, which is the healthy direction.
23→1 Projects~Data~DataSource~Meal uses Projects~Data~DataSource✕
- Connections
- 2 pairs of types, where a type in Projects~Data~DataSource~Meal uses a type in Projects~Data~DataSource.
- The types involved
Projects~Data~DataSource~Meal.LocalMealDataSource→Projects~Data~DataSource.DataSourceProtocolProjects~Data~DataSource~Meal.MealDataSource→Projects~Data~DataSource.DataSourceProtocol
- Direction
- Projects~Data~DataSource~Meal uses Projects~Data~DataSource, so a change to Projects~Data~DataSource can break Projects~Data~DataSource~Meal, while a change to Projects~Data~DataSource~Meal can't break Projects~Data~DataSource.
- Position
- Below the diagonal: Projects~Data~DataSource~Meal uses a module listed above it, which is the healthy direction.
23→5 Projects~Data~DataSource~Meal uses Projects~Domain~Request✕
- Connections
- 4 pairs of types, where a type in Projects~Data~DataSource~Meal uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~DataSource~Meal.LocalMealDataSource→Projects~Domain~Request.FetchMealRequestProjects~Data~DataSource~Meal.LocalMealDataSource→Projects~Domain~Request.FetchMonthlyMealRequestProjects~Data~DataSource~Meal.MealDataSource→Projects~Domain~Request.FetchMealRequestProjects~Data~DataSource~Meal.MealDataSource→Projects~Domain~Request.FetchMonthlyMealRequest
- Direction
- Projects~Data~DataSource~Meal uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~DataSource~Meal, while a change to Projects~Data~DataSource~Meal can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~DataSource~Meal uses a module listed above it, which is the healthy direction.
23→6 Projects~Data~DataSource~Meal uses Projects~Domain~Response✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Meal uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~DataSource~Meal.MealDataSource→Projects~Domain~Response.MealResponse
- Direction
- Projects~Data~DataSource~Meal uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~DataSource~Meal, while a change to Projects~Data~DataSource~Meal can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~DataSource~Meal uses a module listed above it, which is the healthy direction.
23→11 Projects~Data~DataSource~Meal uses Projects~Data~Local~Meal✕
- Connections
- 2 pairs of types, where a type in Projects~Data~DataSource~Meal uses a type in Projects~Data~Local~Meal.
- The types involved
Projects~Data~DataSource~Meal.LocalMealDataSource→Projects~Data~Local~Meal.MealCacheProjects~Data~DataSource~Meal.LocalMealDataSource→Projects~Data~Local~Meal.MealEntity
- Direction
- Projects~Data~DataSource~Meal uses Projects~Data~Local~Meal, so a change to Projects~Data~Local~Meal can break Projects~Data~DataSource~Meal, while a change to Projects~Data~DataSource~Meal can't break Projects~Data~Local~Meal.
- Position
- Below the diagonal: Projects~Data~DataSource~Meal uses a module listed above it, which is the healthy direction.
23→12 Projects~Data~DataSource~Meal uses Projects~Data~Network~Remote✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Meal uses a type in Projects~Data~Network~Remote.
- The types involved
Projects~Data~DataSource~Meal.MealDataSource→Projects~Data~Network~Remote.MealRemote
- Direction
- Projects~Data~DataSource~Meal uses Projects~Data~Network~Remote, so a change to Projects~Data~Network~Remote can break Projects~Data~DataSource~Meal, while a change to Projects~Data~DataSource~Meal can't break Projects~Data~Network~Remote.
- Position
- Below the diagonal: Projects~Data~DataSource~Meal uses a module listed above it, which is the healthy direction.
24→1 Projects~Data~DataSource~Member uses Projects~Data~DataSource✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Member uses a type in Projects~Data~DataSource.
- The types involved
Projects~Data~DataSource~Member.MemberDataSource→Projects~Data~DataSource.DataSourceProtocol
- Direction
- Projects~Data~DataSource~Member uses Projects~Data~DataSource, so a change to Projects~Data~DataSource can break Projects~Data~DataSource~Member, while a change to Projects~Data~DataSource~Member can't break Projects~Data~DataSource.
- Position
- Below the diagonal: Projects~Data~DataSource~Member uses a module listed above it, which is the healthy direction.
24→5 Projects~Data~DataSource~Member uses Projects~Domain~Request✕
- Connections
- 8 pairs of types, where a type in Projects~Data~DataSource~Member uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~DataSource~Member.MemberDataSource→Projects~Domain~Request.PatchMemberInfoRequestProjects~Data~DataSource~Member.MemberDataSource→Projects~Domain~Request.PatchPasswordRequestProjects~Data~DataSource~Member.MemberDataSource→Projects~Domain~Request.PatchStudentInfoRequestProjects~Data~DataSource~Member.MemberDataSource→Projects~Domain~Request.PostAuthCodeRequestProjects~Data~DataSource~Member.MemberDataSource→Projects~Domain~Request.PostJoinParentRequestProjects~Data~DataSource~Member.MemberDataSource→Projects~Domain~Request.PostJoinStudentRequestProjects~Data~DataSource~Member.MemberDataSource→Projects~Domain~Request.PostRelationRequestProjects~Data~DataSource~Member.MemberDataSource→Projects~Domain~Request.PostVerifyAuthCodeRequest
- Direction
- Projects~Data~DataSource~Member uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~DataSource~Member, while a change to Projects~Data~DataSource~Member can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~DataSource~Member uses a module listed above it, which is the healthy direction.
24→6 Projects~Data~DataSource~Member uses Projects~Domain~Response✕
- Connections
- 2 pairs of types, where a type in Projects~Data~DataSource~Member uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~DataSource~Member.MemberDataSource→Projects~Domain~Response.ConnectStudentResponseProjects~Data~DataSource~Member.MemberDataSource→Projects~Domain~Response.MemberResponse
- Direction
- Projects~Data~DataSource~Member uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~DataSource~Member, while a change to Projects~Data~DataSource~Member can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~DataSource~Member uses a module listed above it, which is the healthy direction.
24→9 Projects~Data~DataSource~Member uses Projects~Domain~Entity✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Member uses a type in Projects~Domain~Entity.
- The types involved
Projects~Data~DataSource~Member.MemberDataSource→Projects~Domain~Entity.AuthType
- Direction
- Projects~Data~DataSource~Member uses Projects~Domain~Entity, so a change to Projects~Domain~Entity can break Projects~Data~DataSource~Member, while a change to Projects~Data~DataSource~Member can't break Projects~Domain~Entity.
- Position
- Below the diagonal: Projects~Data~DataSource~Member uses a module listed above it, which is the healthy direction.
24→10 Projects~Data~DataSource~Member uses Projects~Data~Network✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Member uses a type in Projects~Data~Network.
- The types involved
Projects~Data~DataSource~Member.MemberDataSource→Projects~Data~Network.String
- Direction
- Projects~Data~DataSource~Member uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~DataSource~Member, while a change to Projects~Data~DataSource~Member can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~DataSource~Member uses a module listed above it, which is the healthy direction.
24→12 Projects~Data~DataSource~Member uses Projects~Data~Network~Remote✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Member uses a type in Projects~Data~Network~Remote.
- The types involved
Projects~Data~DataSource~Member.MemberDataSource→Projects~Data~Network~Remote.MemberRemote
- Direction
- Projects~Data~DataSource~Member uses Projects~Data~Network~Remote, so a change to Projects~Data~Network~Remote can break Projects~Data~DataSource~Member, while a change to Projects~Data~DataSource~Member can't break Projects~Data~Network~Remote.
- Position
- Below the diagonal: Projects~Data~DataSource~Member uses a module listed above it, which is the healthy direction.
25→5 Projects~Data~DataSource~NightStudy uses Projects~Domain~Request✕
- Connections
- 3 pairs of types, where a type in Projects~Data~DataSource~NightStudy uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~DataSource~NightStudy.NightStudyDataSource→Projects~Domain~Request.NightStudyBanRequestProjects~Data~DataSource~NightStudy.NightStudyDataSource→Projects~Domain~Request.PostNightStudyProjectRequestProjects~Data~DataSource~NightStudy.NightStudyDataSource→Projects~Domain~Request.PostNightStudyRequest
- Direction
- Projects~Data~DataSource~NightStudy uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~DataSource~NightStudy, while a change to Projects~Data~DataSource~NightStudy can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~DataSource~NightStudy uses a module listed above it, which is the healthy direction.
25→6 Projects~Data~DataSource~NightStudy uses Projects~Domain~Response✕
- Connections
- 6 pairs of types, where a type in Projects~Data~DataSource~NightStudy uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~DataSource~NightStudy.NightStudyDataSource→Projects~Domain~Response.DefaultResponseProjects~Data~DataSource~NightStudy.NightStudyDataSource→Projects~Domain~Response.NightStudyBanResponseProjects~Data~DataSource~NightStudy.NightStudyDataSource→Projects~Domain~Response.NightStudyProjectResponseProjects~Data~DataSource~NightStudy.NightStudyDataSource→Projects~Domain~Response.NightStudyResponseProjects~Data~DataSource~NightStudy.NightStudyDataSource→Projects~Domain~Response.NightStudyStudentResponseProjects~Data~DataSource~NightStudy.NightStudyDataSource→Projects~Domain~Response.OngoingNightStudyResponse
- Direction
- Projects~Data~DataSource~NightStudy uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~DataSource~NightStudy, while a change to Projects~Data~DataSource~NightStudy can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~DataSource~NightStudy uses a module listed above it, which is the healthy direction.
25→10 Projects~Data~DataSource~NightStudy uses Projects~Data~Network✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~NightStudy uses a type in Projects~Data~Network.
- The types involved
Projects~Data~DataSource~NightStudy.NightStudyDataSource→Projects~Data~Network.Int
- Direction
- Projects~Data~DataSource~NightStudy uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~DataSource~NightStudy, while a change to Projects~Data~DataSource~NightStudy can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~DataSource~NightStudy uses a module listed above it, which is the healthy direction.
25→12 Projects~Data~DataSource~NightStudy uses Projects~Data~Network~Remote✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~NightStudy uses a type in Projects~Data~Network~Remote.
- The types involved
Projects~Data~DataSource~NightStudy.NightStudyDataSource→Projects~Data~Network~Remote.NightStudyRemote
- Direction
- Projects~Data~DataSource~NightStudy uses Projects~Data~Network~Remote, so a change to Projects~Data~Network~Remote can break Projects~Data~DataSource~NightStudy, while a change to Projects~Data~DataSource~NightStudy can't break Projects~Data~Network~Remote.
- Position
- Below the diagonal: Projects~Data~DataSource~NightStudy uses a module listed above it, which is the healthy direction.
26→1 Projects~Data~DataSource~Notice uses Projects~Data~DataSource✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Notice uses a type in Projects~Data~DataSource.
- The types involved
Projects~Data~DataSource~Notice.NoticeDataSource→Projects~Data~DataSource.DataSourceProtocol
- Direction
- Projects~Data~DataSource~Notice uses Projects~Data~DataSource, so a change to Projects~Data~DataSource can break Projects~Data~DataSource~Notice, while a change to Projects~Data~DataSource~Notice can't break Projects~Data~DataSource.
- Position
- Below the diagonal: Projects~Data~DataSource~Notice uses a module listed above it, which is the healthy direction.
26→5 Projects~Data~DataSource~Notice uses Projects~Domain~Request✕
- Connections
- 2 pairs of types, where a type in Projects~Data~DataSource~Notice uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~DataSource~Notice.NoticeDataSource→Projects~Domain~Request.FetchNoticeByDivisionRequestProjects~Data~DataSource~Notice.NoticeDataSource→Projects~Domain~Request.FetchNoticeRequest
- Direction
- Projects~Data~DataSource~Notice uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~DataSource~Notice, while a change to Projects~Data~DataSource~Notice can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~DataSource~Notice uses a module listed above it, which is the healthy direction.
26→6 Projects~Data~DataSource~Notice uses Projects~Domain~Response✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Notice uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~DataSource~Notice.NoticeDataSource→Projects~Domain~Response.NoticeResponse
- Direction
- Projects~Data~DataSource~Notice uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~DataSource~Notice, while a change to Projects~Data~DataSource~Notice can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~DataSource~Notice uses a module listed above it, which is the healthy direction.
26→12 Projects~Data~DataSource~Notice uses Projects~Data~Network~Remote✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Notice uses a type in Projects~Data~Network~Remote.
- The types involved
Projects~Data~DataSource~Notice.NoticeDataSource→Projects~Data~Network~Remote.NoticeRemote
- Direction
- Projects~Data~DataSource~Notice uses Projects~Data~Network~Remote, so a change to Projects~Data~Network~Remote can break Projects~Data~DataSource~Notice, while a change to Projects~Data~DataSource~Notice can't break Projects~Data~Network~Remote.
- Position
- Below the diagonal: Projects~Data~DataSource~Notice uses a module listed above it, which is the healthy direction.
27→1 Projects~Data~DataSource~OutGoing uses Projects~Data~DataSource✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~OutGoing uses a type in Projects~Data~DataSource.
- The types involved
Projects~Data~DataSource~OutGoing.OutGoingDataSource→Projects~Data~DataSource.DataSourceProtocol
- Direction
- Projects~Data~DataSource~OutGoing uses Projects~Data~DataSource, so a change to Projects~Data~DataSource can break Projects~Data~DataSource~OutGoing, while a change to Projects~Data~DataSource~OutGoing can't break Projects~Data~DataSource.
- Position
- Below the diagonal: Projects~Data~DataSource~OutGoing uses a module listed above it, which is the healthy direction.
27→5 Projects~Data~DataSource~OutGoing uses Projects~Domain~Request✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~OutGoing uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~DataSource~OutGoing.OutGoingDataSource→Projects~Domain~Request.PostOutGoingRequest
- Direction
- Projects~Data~DataSource~OutGoing uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~DataSource~OutGoing, while a change to Projects~Data~DataSource~OutGoing can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~DataSource~OutGoing uses a module listed above it, which is the healthy direction.
27→6 Projects~Data~DataSource~OutGoing uses Projects~Domain~Response✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~OutGoing uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~DataSource~OutGoing.OutGoingDataSource→Projects~Domain~Response.OutGoingResponse
- Direction
- Projects~Data~DataSource~OutGoing uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~DataSource~OutGoing, while a change to Projects~Data~DataSource~OutGoing can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~DataSource~OutGoing uses a module listed above it, which is the healthy direction.
27→10 Projects~Data~DataSource~OutGoing uses Projects~Data~Network✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~OutGoing uses a type in Projects~Data~Network.
- The types involved
Projects~Data~DataSource~OutGoing.OutGoingDataSource→Projects~Data~Network.Int
- Direction
- Projects~Data~DataSource~OutGoing uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~DataSource~OutGoing, while a change to Projects~Data~DataSource~OutGoing can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~DataSource~OutGoing uses a module listed above it, which is the healthy direction.
27→12 Projects~Data~DataSource~OutGoing uses Projects~Data~Network~Remote✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~OutGoing uses a type in Projects~Data~Network~Remote.
- The types involved
Projects~Data~DataSource~OutGoing.OutGoingDataSource→Projects~Data~Network~Remote.OutGoingRemote
- Direction
- Projects~Data~DataSource~OutGoing uses Projects~Data~Network~Remote, so a change to Projects~Data~Network~Remote can break Projects~Data~DataSource~OutGoing, while a change to Projects~Data~DataSource~OutGoing can't break Projects~Data~Network~Remote.
- Position
- Below the diagonal: Projects~Data~DataSource~OutGoing uses a module listed above it, which is the healthy direction.
28→1 Projects~Data~DataSource~OutSleeping uses Projects~Data~DataSource✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~OutSleeping uses a type in Projects~Data~DataSource.
- The types involved
Projects~Data~DataSource~OutSleeping.OutSleepingDataSource→Projects~Data~DataSource.DataSourceProtocol
- Direction
- Projects~Data~DataSource~OutSleeping uses Projects~Data~DataSource, so a change to Projects~Data~DataSource can break Projects~Data~DataSource~OutSleeping, while a change to Projects~Data~DataSource~OutSleeping can't break Projects~Data~DataSource.
- Position
- Below the diagonal: Projects~Data~DataSource~OutSleeping uses a module listed above it, which is the healthy direction.
28→5 Projects~Data~DataSource~OutSleeping uses Projects~Domain~Request✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~OutSleeping uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~DataSource~OutSleeping.OutSleepingDataSource→Projects~Domain~Request.PostOutSleepingRequest
- Direction
- Projects~Data~DataSource~OutSleeping uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~DataSource~OutSleeping, while a change to Projects~Data~DataSource~OutSleeping can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~DataSource~OutSleeping uses a module listed above it, which is the healthy direction.
28→6 Projects~Data~DataSource~OutSleeping uses Projects~Domain~Response✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~OutSleeping uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~DataSource~OutSleeping.OutSleepingDataSource→Projects~Domain~Response.OutSleepingResponse
- Direction
- Projects~Data~DataSource~OutSleeping uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~DataSource~OutSleeping, while a change to Projects~Data~DataSource~OutSleeping can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~DataSource~OutSleeping uses a module listed above it, which is the healthy direction.
28→10 Projects~Data~DataSource~OutSleeping uses Projects~Data~Network✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~OutSleeping uses a type in Projects~Data~Network.
- The types involved
Projects~Data~DataSource~OutSleeping.OutSleepingDataSource→Projects~Data~Network.Int
- Direction
- Projects~Data~DataSource~OutSleeping uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~DataSource~OutSleeping, while a change to Projects~Data~DataSource~OutSleeping can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~DataSource~OutSleeping uses a module listed above it, which is the healthy direction.
28→12 Projects~Data~DataSource~OutSleeping uses Projects~Data~Network~Remote✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~OutSleeping uses a type in Projects~Data~Network~Remote.
- The types involved
Projects~Data~DataSource~OutSleeping.OutSleepingDataSource→Projects~Data~Network~Remote.OutSleepingRemote
- Direction
- Projects~Data~DataSource~OutSleeping uses Projects~Data~Network~Remote, so a change to Projects~Data~Network~Remote can break Projects~Data~DataSource~OutSleeping, while a change to Projects~Data~DataSource~OutSleeping can't break Projects~Data~Network~Remote.
- Position
- Below the diagonal: Projects~Data~DataSource~OutSleeping uses a module listed above it, which is the healthy direction.
29→1 Projects~Data~DataSource~Point uses Projects~Data~DataSource✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Point uses a type in Projects~Data~DataSource.
- The types involved
Projects~Data~DataSource~Point.PointDataSource→Projects~Data~DataSource.DataSourceProtocol
- Direction
- Projects~Data~DataSource~Point uses Projects~Data~DataSource, so a change to Projects~Data~DataSource can break Projects~Data~DataSource~Point, while a change to Projects~Data~DataSource~Point can't break Projects~Data~DataSource.
- Position
- Below the diagonal: Projects~Data~DataSource~Point uses a module listed above it, which is the healthy direction.
29→5 Projects~Data~DataSource~Point uses Projects~Domain~Request✕
- Connections
- 2 pairs of types, where a type in Projects~Data~DataSource~Point uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~DataSource~Point.PointDataSource→Projects~Domain~Request.FetchPointRequestProjects~Data~DataSource~Point.PointDataSource→Projects~Domain~Request.FetchPointScoreRequest
- Direction
- Projects~Data~DataSource~Point uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~DataSource~Point, while a change to Projects~Data~DataSource~Point can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~DataSource~Point uses a module listed above it, which is the healthy direction.
29→6 Projects~Data~DataSource~Point uses Projects~Domain~Response✕
- Connections
- 2 pairs of types, where a type in Projects~Data~DataSource~Point uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~DataSource~Point.PointDataSource→Projects~Domain~Response.PointResponseProjects~Data~DataSource~Point.PointDataSource→Projects~Domain~Response.PointScoreResponse
- Direction
- Projects~Data~DataSource~Point uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~DataSource~Point, while a change to Projects~Data~DataSource~Point can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~DataSource~Point uses a module listed above it, which is the healthy direction.
29→12 Projects~Data~DataSource~Point uses Projects~Data~Network~Remote✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Point uses a type in Projects~Data~Network~Remote.
- The types involved
Projects~Data~DataSource~Point.PointDataSource→Projects~Data~Network~Remote.PointRemote
- Direction
- Projects~Data~DataSource~Point uses Projects~Data~Network~Remote, so a change to Projects~Data~Network~Remote can break Projects~Data~DataSource~Point, while a change to Projects~Data~DataSource~Point can't break Projects~Data~Network~Remote.
- Position
- Below the diagonal: Projects~Data~DataSource~Point uses a module listed above it, which is the healthy direction.
30→1 Projects~Data~DataSource~Schedule uses Projects~Data~DataSource✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Schedule uses a type in Projects~Data~DataSource.
- The types involved
Projects~Data~DataSource~Schedule.ScheduleDataSource→Projects~Data~DataSource.DataSourceProtocol
- Direction
- Projects~Data~DataSource~Schedule uses Projects~Data~DataSource, so a change to Projects~Data~DataSource can break Projects~Data~DataSource~Schedule, while a change to Projects~Data~DataSource~Schedule can't break Projects~Data~DataSource.
- Position
- Below the diagonal: Projects~Data~DataSource~Schedule uses a module listed above it, which is the healthy direction.
30→5 Projects~Data~DataSource~Schedule uses Projects~Domain~Request✕
- Connections
- 4 pairs of types, where a type in Projects~Data~DataSource~Schedule uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~DataSource~Schedule.ScheduleDataSource→Projects~Domain~Request.FetchScheduleBetweenRequestProjects~Data~DataSource~Schedule.ScheduleDataSource→Projects~Domain~Request.FetchScheduleByDateRequestProjects~Data~DataSource~Schedule.ScheduleDataSource→Projects~Domain~Request.FetchScheduleByKeywordRequestProjects~Data~DataSource~Schedule.ScheduleDataSource→Projects~Domain~Request.FetchScheduleByPageRequest
- Direction
- Projects~Data~DataSource~Schedule uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~DataSource~Schedule, while a change to Projects~Data~DataSource~Schedule can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~DataSource~Schedule uses a module listed above it, which is the healthy direction.
30→6 Projects~Data~DataSource~Schedule uses Projects~Domain~Response✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Schedule uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~DataSource~Schedule.ScheduleDataSource→Projects~Domain~Response.ScheduleResponse
- Direction
- Projects~Data~DataSource~Schedule uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~DataSource~Schedule, while a change to Projects~Data~DataSource~Schedule can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~DataSource~Schedule uses a module listed above it, which is the healthy direction.
30→12 Projects~Data~DataSource~Schedule uses Projects~Data~Network~Remote✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~Schedule uses a type in Projects~Data~Network~Remote.
- The types involved
Projects~Data~DataSource~Schedule.ScheduleDataSource→Projects~Data~Network~Remote.ScheduleRemote
- Direction
- Projects~Data~DataSource~Schedule uses Projects~Data~Network~Remote, so a change to Projects~Data~Network~Remote can break Projects~Data~DataSource~Schedule, while a change to Projects~Data~DataSource~Schedule can't break Projects~Data~Network~Remote.
- Position
- Below the diagonal: Projects~Data~DataSource~Schedule uses a module listed above it, which is the healthy direction.
31→1 Projects~Data~DataSource~WakeupSong uses Projects~Data~DataSource✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~WakeupSong uses a type in Projects~Data~DataSource.
- The types involved
Projects~Data~DataSource~WakeupSong.WakeupSongDataSource→Projects~Data~DataSource.DataSourceProtocol
- Direction
- Projects~Data~DataSource~WakeupSong uses Projects~Data~DataSource, so a change to Projects~Data~DataSource can break Projects~Data~DataSource~WakeupSong, while a change to Projects~Data~DataSource~WakeupSong can't break Projects~Data~DataSource.
- Position
- Below the diagonal: Projects~Data~DataSource~WakeupSong uses a module listed above it, which is the healthy direction.
31→5 Projects~Data~DataSource~WakeupSong uses Projects~Domain~Request✕
- Connections
- 4 pairs of types, where a type in Projects~Data~DataSource~WakeupSong uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~DataSource~WakeupSong.WakeupSongDataSource→Projects~Domain~Request.FetchAllowedWakeupSongRequestProjects~Data~DataSource~WakeupSong.WakeupSongDataSource→Projects~Domain~Request.FetchWakeupSongByKeywordRequestProjects~Data~DataSource~WakeupSong.WakeupSongDataSource→Projects~Domain~Request.PostWakeupSongByKeywordRequestProjects~Data~DataSource~WakeupSong.WakeupSongDataSource→Projects~Domain~Request.PostWakeupSongRequest
- Direction
- Projects~Data~DataSource~WakeupSong uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~DataSource~WakeupSong, while a change to Projects~Data~DataSource~WakeupSong can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~DataSource~WakeupSong uses a module listed above it, which is the healthy direction.
31→6 Projects~Data~DataSource~WakeupSong uses Projects~Domain~Response✕
- Connections
- 3 pairs of types, where a type in Projects~Data~DataSource~WakeupSong uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~DataSource~WakeupSong.WakeupSongDataSource→Projects~Domain~Response.WakeupSongChartResponseProjects~Data~DataSource~WakeupSong.WakeupSongDataSource→Projects~Domain~Response.WakeupSongResponseProjects~Data~DataSource~WakeupSong.WakeupSongDataSource→Projects~Domain~Response.WakeupSongSearchResponse
- Direction
- Projects~Data~DataSource~WakeupSong uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~DataSource~WakeupSong, while a change to Projects~Data~DataSource~WakeupSong can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~DataSource~WakeupSong uses a module listed above it, which is the healthy direction.
31→10 Projects~Data~DataSource~WakeupSong uses Projects~Data~Network✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~WakeupSong uses a type in Projects~Data~Network.
- The types involved
Projects~Data~DataSource~WakeupSong.WakeupSongDataSource→Projects~Data~Network.Int
- Direction
- Projects~Data~DataSource~WakeupSong uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~DataSource~WakeupSong, while a change to Projects~Data~DataSource~WakeupSong can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~DataSource~WakeupSong uses a module listed above it, which is the healthy direction.
31→12 Projects~Data~DataSource~WakeupSong uses Projects~Data~Network~Remote✕
- Connections
- 1 pair of types, where a type in Projects~Data~DataSource~WakeupSong uses a type in Projects~Data~Network~Remote.
- The types involved
Projects~Data~DataSource~WakeupSong.WakeupSongDataSource→Projects~Data~Network~Remote.WakeupSongRemote
- Direction
- Projects~Data~DataSource~WakeupSong uses Projects~Data~Network~Remote, so a change to Projects~Data~Network~Remote can break Projects~Data~DataSource~WakeupSong, while a change to Projects~Data~DataSource~WakeupSong can't break Projects~Data~Network~Remote.
- Position
- Below the diagonal: Projects~Data~DataSource~WakeupSong uses a module listed above it, which is the healthy direction.
32→2 Projects~Feature~ChildrenManage uses Projects~Feature~Core✕
- Connections
- 1 pair of types, where a type in Projects~Feature~ChildrenManage uses a type in Projects~Feature~Core.
- The types involved
Projects~Feature~ChildrenManage.ChildrenManageViewModelImpl→Projects~Feature~Core.OnAppearProtocol
- Direction
- Projects~Feature~ChildrenManage uses Projects~Feature~Core, so a change to Projects~Feature~Core can break Projects~Feature~ChildrenManage, while a change to Projects~Feature~ChildrenManage can't break Projects~Feature~Core.
- Position
- Below the diagonal: Projects~Feature~ChildrenManage uses a module listed above it, which is the healthy direction.
32→3 Projects~Feature~ChildrenManage uses Projects~Domain~Model✕
- Connections
- 5 pairs of types, where a type in Projects~Feature~ChildrenManage uses a type in Projects~Domain~Model.
- The types involved
Projects~Feature~ChildrenManage.ChildCell→Projects~Domain~Model.ConnectStudentProjects~Feature~ChildrenManage.ChildrenManageViewModel→Projects~Domain~Model.ConnectStudentProjects~Feature~ChildrenManage.ChildrenManageViewModelForRegister→Projects~Domain~Model.ConnectStudentProjects~Feature~ChildrenManage.ChildrenManageViewModelImpl→Projects~Domain~Model.ConnectStudentProjects~Feature~ChildrenManage.ContentView→Projects~Domain~Model.ConnectStudent
- Direction
- Projects~Feature~ChildrenManage uses Projects~Domain~Model, so a change to Projects~Domain~Model can break Projects~Feature~ChildrenManage, while a change to Projects~Feature~ChildrenManage can't break Projects~Domain~Model.
- Position
- Below the diagonal: Projects~Feature~ChildrenManage uses a module listed above it, which is the healthy direction.
32→4 Projects~Feature~ChildrenManage uses Projects~Shared~SwiftUI✕
- Connections
- 5 pairs of types, where a type in Projects~Feature~ChildrenManage uses a type in Projects~Shared~SwiftUI.
- The types involved
Projects~Feature~ChildrenManage.ChildCell→Projects~Shared~SwiftUI.ViewProjects~Feature~ChildrenManage.ChildrenManageView→Projects~Shared~SwiftUI.ViewProjects~Feature~ChildrenManage.ChildrenManageViewForRegister→Projects~Shared~SwiftUI.ViewProjects~Feature~ChildrenManage.ContentView→Projects~Shared~SwiftUI.ViewProjects~Feature~ChildrenManage.RelationCell→Projects~Shared~SwiftUI.View
- Direction
- Projects~Feature~ChildrenManage uses Projects~Shared~SwiftUI, so a change to Projects~Shared~SwiftUI can break Projects~Feature~ChildrenManage, while a change to Projects~Feature~ChildrenManage can't break Projects~Shared~SwiftUI.
- Position
- Below the diagonal: Projects~Feature~ChildrenManage uses a module listed above it, which is the healthy direction.
32→7 Projects~Feature~ChildrenManage uses Projects~Domain~Repository✕
- Connections
- 2 pairs of types, where a type in Projects~Feature~ChildrenManage uses a type in Projects~Domain~Repository.
- The types involved
Projects~Feature~ChildrenManage.ChildrenManageViewModelForRegister→Projects~Domain~Repository.MemberRepositoryProjects~Feature~ChildrenManage.ChildrenManageViewModelImpl→Projects~Domain~Repository.MemberRepository
- Direction
- Projects~Feature~ChildrenManage uses Projects~Domain~Repository, so a change to Projects~Domain~Repository can break Projects~Feature~ChildrenManage, while a change to Projects~Feature~ChildrenManage can't break Projects~Domain~Repository.
- Position
- Below the diagonal: Projects~Feature~ChildrenManage uses a module listed above it, which is the healthy direction.
32→10 Projects~Feature~ChildrenManage uses Projects~Data~Network✕
- Connections
- 4 pairs of types, where a type in Projects~Feature~ChildrenManage uses a type in Projects~Data~Network.
- The types involved
Projects~Feature~ChildrenManage.ChildrenManageViewModel→Projects~Data~Network.StringProjects~Feature~ChildrenManage.ChildrenManageViewModelForRegister→Projects~Data~Network.StringProjects~Feature~ChildrenManage.ChildrenManageViewModelImpl→Projects~Data~Network.StringProjects~Feature~ChildrenManage.RelationCell→Projects~Data~Network.String
- Direction
- Projects~Feature~ChildrenManage uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Feature~ChildrenManage, while a change to Projects~Feature~ChildrenManage can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Feature~ChildrenManage uses a module listed above it, which is the healthy direction.
32→14 Projects~Feature~ChildrenManage uses Projects~Feature~Auth✕
- Connections
- 1 pair of types, where a type in Projects~Feature~ChildrenManage uses a type in Projects~Feature~Auth.
- The types involved
Projects~Feature~ChildrenManage.ChildrenManageViewForRegister→Projects~Feature~Auth.RegisterViewModel
- Direction
- Projects~Feature~ChildrenManage uses Projects~Feature~Auth, so a change to Projects~Feature~Auth can break Projects~Feature~ChildrenManage, while a change to Projects~Feature~ChildrenManage can't break Projects~Feature~Auth.
- Position
- Below the diagonal: Projects~Feature~ChildrenManage uses a module listed above it, which is the healthy direction.
33→3 Projects~Data~Repository~Auth uses Projects~Domain~Model✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~Auth uses a type in Projects~Domain~Model.
- The types involved
Projects~Data~Repository~Auth.AuthRepositoryImpl→Projects~Domain~Model.Member
- Direction
- Projects~Data~Repository~Auth uses Projects~Domain~Model, so a change to Projects~Domain~Model can break Projects~Data~Repository~Auth, while a change to Projects~Data~Repository~Auth can't break Projects~Domain~Model.
- Position
- Below the diagonal: Projects~Data~Repository~Auth uses a module listed above it, which is the healthy direction.
33→5 Projects~Data~Repository~Auth uses Projects~Domain~Request✕
- Connections
- 3 pairs of types, where a type in Projects~Data~Repository~Auth uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~Repository~Auth.AuthRepositoryImpl→Projects~Domain~Request.DeepLinkLoginRequestProjects~Data~Repository~Auth.AuthRepositoryImpl→Projects~Domain~Request.PostLoginRequestProjects~Data~Repository~Auth.AuthRepositoryImpl→Projects~Domain~Request.PostReissueRequest
- Direction
- Projects~Data~Repository~Auth uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~Repository~Auth, while a change to Projects~Data~Repository~Auth can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~Repository~Auth uses a module listed above it, which is the healthy direction.
33→6 Projects~Data~Repository~Auth uses Projects~Domain~Response✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~Auth uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~Repository~Auth.AuthRepositoryImpl→Projects~Domain~Response.DefaultResponse
- Direction
- Projects~Data~Repository~Auth uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~Repository~Auth, while a change to Projects~Data~Repository~Auth can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~Repository~Auth uses a module listed above it, which is the healthy direction.
33→7 Projects~Data~Repository~Auth uses Projects~Domain~Repository✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~Auth uses a type in Projects~Domain~Repository.
- The types involved
Projects~Data~Repository~Auth.AuthRepositoryImpl→Projects~Domain~Repository.AuthRepository
- Direction
- Projects~Data~Repository~Auth uses Projects~Domain~Repository, so a change to Projects~Domain~Repository can break Projects~Data~Repository~Auth, while a change to Projects~Data~Repository~Auth can't break Projects~Domain~Repository.
- Position
- Below the diagonal: Projects~Data~Repository~Auth uses a module listed above it, which is the healthy direction.
33→19 Projects~Data~Repository~Auth uses Projects~Data~DataSource~Auth✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~Auth uses a type in Projects~Data~DataSource~Auth.
- The types involved
Projects~Data~Repository~Auth.AuthRepositoryImpl→Projects~Data~DataSource~Auth.AuthDataSource
- Direction
- Projects~Data~Repository~Auth uses Projects~Data~DataSource~Auth, so a change to Projects~Data~DataSource~Auth can break Projects~Data~Repository~Auth, while a change to Projects~Data~Repository~Auth can't break Projects~Data~DataSource~Auth.
- Position
- Below the diagonal: Projects~Data~Repository~Auth uses a module listed above it, which is the healthy direction.
34→5 Projects~Data~Repository~Club uses Projects~Domain~Request✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~Club uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~Repository~Club.ClubRepositoryImpl→Projects~Domain~Request.ClubApplyRequest
- Direction
- Projects~Data~Repository~Club uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~Repository~Club, while a change to Projects~Data~Repository~Club can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~Repository~Club uses a module listed above it, which is the healthy direction.
34→6 Projects~Data~Repository~Club uses Projects~Domain~Response✕
- Connections
- 8 pairs of types, where a type in Projects~Data~Repository~Club uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~Repository~Club.ClubRepositoryImpl→Projects~Domain~Response.ClubDetailResponseProjects~Data~Repository~Club.ClubRepositoryImpl→Projects~Domain~Response.ClubJoinRequestsResponseProjects~Data~Repository~Club.ClubRepositoryImpl→Projects~Domain~Response.ClubMembersInfoResponseProjects~Data~Repository~Club.ClubRepositoryImpl→Projects~Domain~Response.ClubRegisterTimeResponseProjects~Data~Repository~Club.ClubRepositoryImpl→Projects~Domain~Response.ClubsResponseProjects~Data~Repository~Club.ClubRepositoryImpl→Projects~Domain~Response.JoinedClubResponseProjects~Data~Repository~Club.ClubRepositoryImpl→Projects~Domain~Response.MyApplyClubResponseProjects~Data~Repository~Club.ClubRepositoryImpl→Projects~Domain~Response.MyClubResponse
- Direction
- Projects~Data~Repository~Club uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~Repository~Club, while a change to Projects~Data~Repository~Club can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~Repository~Club uses a module listed above it, which is the healthy direction.
34→7 Projects~Data~Repository~Club uses Projects~Domain~Repository✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~Club uses a type in Projects~Domain~Repository.
- The types involved
Projects~Data~Repository~Club.ClubRepositoryImpl→Projects~Domain~Repository.ClubRepository
- Direction
- Projects~Data~Repository~Club uses Projects~Domain~Repository, so a change to Projects~Domain~Repository can break Projects~Data~Repository~Club, while a change to Projects~Data~Repository~Club can't break Projects~Domain~Repository.
- Position
- Below the diagonal: Projects~Data~Repository~Club uses a module listed above it, which is the healthy direction.
34→10 Projects~Data~Repository~Club uses Projects~Data~Network✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~Club uses a type in Projects~Data~Network.
- The types involved
Projects~Data~Repository~Club.ClubRepositoryImpl→Projects~Data~Network.Int
- Direction
- Projects~Data~Repository~Club uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~Repository~Club, while a change to Projects~Data~Repository~Club can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~Repository~Club uses a module listed above it, which is the healthy direction.
34→21 Projects~Data~Repository~Club uses Projects~Data~DataSource~Club✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~Club uses a type in Projects~Data~DataSource~Club.
- The types involved
Projects~Data~Repository~Club.ClubRepositoryImpl→Projects~Data~DataSource~Club.ClubDataSource
- Direction
- Projects~Data~Repository~Club uses Projects~Data~DataSource~Club, so a change to Projects~Data~DataSource~Club can break Projects~Data~Repository~Club, while a change to Projects~Data~Repository~Club can't break Projects~Data~DataSource~Club.
- Position
- Below the diagonal: Projects~Data~Repository~Club uses a module listed above it, which is the healthy direction.
35→5 Projects~Data~Repository~Division uses Projects~Domain~Request✕
- Connections
- 7 pairs of types, where a type in Projects~Data~Repository~Division uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~Repository~Division.DivisionRepositoryImpl→Projects~Domain~Request.AddMembersRequestProjects~Data~Repository~Division.DivisionRepositoryImpl→Projects~Domain~Request.DeleteDivisionMembersRequestProjects~Data~Repository~Division.DivisionRepositoryImpl→Projects~Domain~Request.FetchDivisionMembersRequestProjects~Data~Repository~Division.DivisionRepositoryImpl→Projects~Domain~Request.FetchDivisionRequestProjects~Data~Repository~Division.DivisionRepositoryImpl→Projects~Domain~Request.PatchMemberPermissionRequestProjects~Data~Repository~Division.DivisionRepositoryImpl→Projects~Domain~Request.PatchMembersStatusRequestProjects~Data~Repository~Division.DivisionRepositoryImpl→Projects~Domain~Request.PostDivisionRequest
- Direction
- Projects~Data~Repository~Division uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~Repository~Division, while a change to Projects~Data~Repository~Division can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~Repository~Division uses a module listed above it, which is the healthy direction.
35→6 Projects~Data~Repository~Division uses Projects~Domain~Response✕
- Connections
- 4 pairs of types, where a type in Projects~Data~Repository~Division uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~Repository~Division.DivisionRepositoryImpl→Projects~Domain~Response.DivisionDetailResponseProjects~Data~Repository~Division.DivisionRepositoryImpl→Projects~Domain~Response.DivisionMemberResponseProjects~Data~Repository~Division.DivisionRepositoryImpl→Projects~Domain~Response.DivisionMembersCountResponseProjects~Data~Repository~Division.DivisionRepositoryImpl→Projects~Domain~Response.DivisionOverviewResponse
- Direction
- Projects~Data~Repository~Division uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~Repository~Division, while a change to Projects~Data~Repository~Division can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~Repository~Division uses a module listed above it, which is the healthy direction.
35→7 Projects~Data~Repository~Division uses Projects~Domain~Repository✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~Division uses a type in Projects~Domain~Repository.
- The types involved
Projects~Data~Repository~Division.DivisionRepositoryImpl→Projects~Domain~Repository.DivisionRepository
- Direction
- Projects~Data~Repository~Division uses Projects~Domain~Repository, so a change to Projects~Domain~Repository can break Projects~Data~Repository~Division, while a change to Projects~Data~Repository~Division can't break Projects~Domain~Repository.
- Position
- Below the diagonal: Projects~Data~Repository~Division uses a module listed above it, which is the healthy direction.
35→10 Projects~Data~Repository~Division uses Projects~Data~Network✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~Division uses a type in Projects~Data~Network.
- The types involved
Projects~Data~Repository~Division.DivisionRepositoryImpl→Projects~Data~Network.Int
- Direction
- Projects~Data~Repository~Division uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~Repository~Division, while a change to Projects~Data~Repository~Division can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~Repository~Division uses a module listed above it, which is the healthy direction.
35→22 Projects~Data~Repository~Division uses Projects~Data~DataSource~Division✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~Division uses a type in Projects~Data~DataSource~Division.
- The types involved
Projects~Data~Repository~Division.DivisionRepositoryImpl→Projects~Data~DataSource~Division.DivisionDataSource
- Direction
- Projects~Data~Repository~Division uses Projects~Data~DataSource~Division, so a change to Projects~Data~DataSource~Division can break Projects~Data~Repository~Division, while a change to Projects~Data~Repository~Division can't break Projects~Data~DataSource~Division.
- Position
- Below the diagonal: Projects~Data~Repository~Division uses a module listed above it, which is the healthy direction.
36→5 Projects~Data~Repository~Member uses Projects~Domain~Request✕
- Connections
- 8 pairs of types, where a type in Projects~Data~Repository~Member uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~Repository~Member.MemberRepositoryImpl→Projects~Domain~Request.PatchMemberInfoRequestProjects~Data~Repository~Member.MemberRepositoryImpl→Projects~Domain~Request.PatchPasswordRequestProjects~Data~Repository~Member.MemberRepositoryImpl→Projects~Domain~Request.PatchStudentInfoRequestProjects~Data~Repository~Member.MemberRepositoryImpl→Projects~Domain~Request.PostAuthCodeRequestProjects~Data~Repository~Member.MemberRepositoryImpl→Projects~Domain~Request.PostJoinParentRequestProjects~Data~Repository~Member.MemberRepositoryImpl→Projects~Domain~Request.PostJoinStudentRequestProjects~Data~Repository~Member.MemberRepositoryImpl→Projects~Domain~Request.PostRelationRequestProjects~Data~Repository~Member.MemberRepositoryImpl→Projects~Domain~Request.PostVerifyAuthCodeRequest
- Direction
- Projects~Data~Repository~Member uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~Repository~Member, while a change to Projects~Data~Repository~Member can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~Repository~Member uses a module listed above it, which is the healthy direction.
36→6 Projects~Data~Repository~Member uses Projects~Domain~Response✕
- Connections
- 2 pairs of types, where a type in Projects~Data~Repository~Member uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~Repository~Member.MemberRepositoryImpl→Projects~Domain~Response.ConnectStudentResponseProjects~Data~Repository~Member.MemberRepositoryImpl→Projects~Domain~Response.MemberResponse
- Direction
- Projects~Data~Repository~Member uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~Repository~Member, while a change to Projects~Data~Repository~Member can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~Repository~Member uses a module listed above it, which is the healthy direction.
36→7 Projects~Data~Repository~Member uses Projects~Domain~Repository✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~Member uses a type in Projects~Domain~Repository.
- The types involved
Projects~Data~Repository~Member.MemberRepositoryImpl→Projects~Domain~Repository.MemberRepository
- Direction
- Projects~Data~Repository~Member uses Projects~Domain~Repository, so a change to Projects~Domain~Repository can break Projects~Data~Repository~Member, while a change to Projects~Data~Repository~Member can't break Projects~Domain~Repository.
- Position
- Below the diagonal: Projects~Data~Repository~Member uses a module listed above it, which is the healthy direction.
36→9 Projects~Data~Repository~Member uses Projects~Domain~Entity✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~Member uses a type in Projects~Domain~Entity.
- The types involved
Projects~Data~Repository~Member.MemberRepositoryImpl→Projects~Domain~Entity.AuthType
- Direction
- Projects~Data~Repository~Member uses Projects~Domain~Entity, so a change to Projects~Domain~Entity can break Projects~Data~Repository~Member, while a change to Projects~Data~Repository~Member can't break Projects~Domain~Entity.
- Position
- Below the diagonal: Projects~Data~Repository~Member uses a module listed above it, which is the healthy direction.
36→10 Projects~Data~Repository~Member uses Projects~Data~Network✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~Member uses a type in Projects~Data~Network.
- The types involved
Projects~Data~Repository~Member.MemberRepositoryImpl→Projects~Data~Network.String
- Direction
- Projects~Data~Repository~Member uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~Repository~Member, while a change to Projects~Data~Repository~Member can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~Repository~Member uses a module listed above it, which is the healthy direction.
36→24 Projects~Data~Repository~Member uses Projects~Data~DataSource~Member✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~Member uses a type in Projects~Data~DataSource~Member.
- The types involved
Projects~Data~Repository~Member.MemberRepositoryImpl→Projects~Data~DataSource~Member.MemberDataSource
- Direction
- Projects~Data~Repository~Member uses Projects~Data~DataSource~Member, so a change to Projects~Data~DataSource~Member can break Projects~Data~Repository~Member, while a change to Projects~Data~Repository~Member can't break Projects~Data~DataSource~Member.
- Position
- Below the diagonal: Projects~Data~Repository~Member uses a module listed above it, which is the healthy direction.
37→5 Projects~Data~Repository~NightStudy uses Projects~Domain~Request✕
- Connections
- 3 pairs of types, where a type in Projects~Data~Repository~NightStudy uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~Repository~NightStudy.NightStudyRepositoryImpl→Projects~Domain~Request.NightStudyBanRequestProjects~Data~Repository~NightStudy.NightStudyRepositoryImpl→Projects~Domain~Request.PostNightStudyProjectRequestProjects~Data~Repository~NightStudy.NightStudyRepositoryImpl→Projects~Domain~Request.PostNightStudyRequest
- Direction
- Projects~Data~Repository~NightStudy uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~Repository~NightStudy, while a change to Projects~Data~Repository~NightStudy can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~Repository~NightStudy uses a module listed above it, which is the healthy direction.
37→6 Projects~Data~Repository~NightStudy uses Projects~Domain~Response✕
- Connections
- 6 pairs of types, where a type in Projects~Data~Repository~NightStudy uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~Repository~NightStudy.NightStudyRepositoryImpl→Projects~Domain~Response.DefaultResponseProjects~Data~Repository~NightStudy.NightStudyRepositoryImpl→Projects~Domain~Response.NightStudyBanResponseProjects~Data~Repository~NightStudy.NightStudyRepositoryImpl→Projects~Domain~Response.NightStudyProjectResponseProjects~Data~Repository~NightStudy.NightStudyRepositoryImpl→Projects~Domain~Response.NightStudyResponseProjects~Data~Repository~NightStudy.NightStudyRepositoryImpl→Projects~Domain~Response.NightStudyStudentResponseProjects~Data~Repository~NightStudy.NightStudyRepositoryImpl→Projects~Domain~Response.OngoingNightStudyResponse
- Direction
- Projects~Data~Repository~NightStudy uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~Repository~NightStudy, while a change to Projects~Data~Repository~NightStudy can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~Repository~NightStudy uses a module listed above it, which is the healthy direction.
37→7 Projects~Data~Repository~NightStudy uses Projects~Domain~Repository✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~NightStudy uses a type in Projects~Domain~Repository.
- The types involved
Projects~Data~Repository~NightStudy.NightStudyRepositoryImpl→Projects~Domain~Repository.NightStudyRepository
- Direction
- Projects~Data~Repository~NightStudy uses Projects~Domain~Repository, so a change to Projects~Domain~Repository can break Projects~Data~Repository~NightStudy, while a change to Projects~Data~Repository~NightStudy can't break Projects~Domain~Repository.
- Position
- Below the diagonal: Projects~Data~Repository~NightStudy uses a module listed above it, which is the healthy direction.
37→10 Projects~Data~Repository~NightStudy uses Projects~Data~Network✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~NightStudy uses a type in Projects~Data~Network.
- The types involved
Projects~Data~Repository~NightStudy.NightStudyRepositoryImpl→Projects~Data~Network.Int
- Direction
- Projects~Data~Repository~NightStudy uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~Repository~NightStudy, while a change to Projects~Data~Repository~NightStudy can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~Repository~NightStudy uses a module listed above it, which is the healthy direction.
37→25 Projects~Data~Repository~NightStudy uses Projects~Data~DataSource~NightStudy✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~NightStudy uses a type in Projects~Data~DataSource~NightStudy.
- The types involved
Projects~Data~Repository~NightStudy.NightStudyRepositoryImpl→Projects~Data~DataSource~NightStudy.NightStudyDataSource
- Direction
- Projects~Data~Repository~NightStudy uses Projects~Data~DataSource~NightStudy, so a change to Projects~Data~DataSource~NightStudy can break Projects~Data~Repository~NightStudy, while a change to Projects~Data~Repository~NightStudy can't break Projects~Data~DataSource~NightStudy.
- Position
- Below the diagonal: Projects~Data~Repository~NightStudy uses a module listed above it, which is the healthy direction.
38→5 Projects~Data~Repository~OutGoing uses Projects~Domain~Request✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~OutGoing uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~Repository~OutGoing.OutGoingRepositoryImpl→Projects~Domain~Request.PostOutGoingRequest
- Direction
- Projects~Data~Repository~OutGoing uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~Repository~OutGoing, while a change to Projects~Data~Repository~OutGoing can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~Repository~OutGoing uses a module listed above it, which is the healthy direction.
38→6 Projects~Data~Repository~OutGoing uses Projects~Domain~Response✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~OutGoing uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~Repository~OutGoing.OutGoingRepositoryImpl→Projects~Domain~Response.OutGoingResponse
- Direction
- Projects~Data~Repository~OutGoing uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~Repository~OutGoing, while a change to Projects~Data~Repository~OutGoing can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~Repository~OutGoing uses a module listed above it, which is the healthy direction.
38→7 Projects~Data~Repository~OutGoing uses Projects~Domain~Repository✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~OutGoing uses a type in Projects~Domain~Repository.
- The types involved
Projects~Data~Repository~OutGoing.OutGoingRepositoryImpl→Projects~Domain~Repository.OutGoingRepository
- Direction
- Projects~Data~Repository~OutGoing uses Projects~Domain~Repository, so a change to Projects~Domain~Repository can break Projects~Data~Repository~OutGoing, while a change to Projects~Data~Repository~OutGoing can't break Projects~Domain~Repository.
- Position
- Below the diagonal: Projects~Data~Repository~OutGoing uses a module listed above it, which is the healthy direction.
38→10 Projects~Data~Repository~OutGoing uses Projects~Data~Network✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~OutGoing uses a type in Projects~Data~Network.
- The types involved
Projects~Data~Repository~OutGoing.OutGoingRepositoryImpl→Projects~Data~Network.Int
- Direction
- Projects~Data~Repository~OutGoing uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~Repository~OutGoing, while a change to Projects~Data~Repository~OutGoing can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~Repository~OutGoing uses a module listed above it, which is the healthy direction.
38→27 Projects~Data~Repository~OutGoing uses Projects~Data~DataSource~OutGoing✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~OutGoing uses a type in Projects~Data~DataSource~OutGoing.
- The types involved
Projects~Data~Repository~OutGoing.OutGoingRepositoryImpl→Projects~Data~DataSource~OutGoing.OutGoingDataSource
- Direction
- Projects~Data~Repository~OutGoing uses Projects~Data~DataSource~OutGoing, so a change to Projects~Data~DataSource~OutGoing can break Projects~Data~Repository~OutGoing, while a change to Projects~Data~Repository~OutGoing can't break Projects~Data~DataSource~OutGoing.
- Position
- Below the diagonal: Projects~Data~Repository~OutGoing uses a module listed above it, which is the healthy direction.
39→5 Projects~Data~Repository~OutSleeping uses Projects~Domain~Request✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~OutSleeping uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~Repository~OutSleeping.OutSleepingRepositoryImpl→Projects~Domain~Request.PostOutSleepingRequest
- Direction
- Projects~Data~Repository~OutSleeping uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~Repository~OutSleeping, while a change to Projects~Data~Repository~OutSleeping can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~Repository~OutSleeping uses a module listed above it, which is the healthy direction.
39→6 Projects~Data~Repository~OutSleeping uses Projects~Domain~Response✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~OutSleeping uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~Repository~OutSleeping.OutSleepingRepositoryImpl→Projects~Domain~Response.OutSleepingResponse
- Direction
- Projects~Data~Repository~OutSleeping uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~Repository~OutSleeping, while a change to Projects~Data~Repository~OutSleeping can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~Repository~OutSleeping uses a module listed above it, which is the healthy direction.
39→7 Projects~Data~Repository~OutSleeping uses Projects~Domain~Repository✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~OutSleeping uses a type in Projects~Domain~Repository.
- The types involved
Projects~Data~Repository~OutSleeping.OutSleepingRepositoryImpl→Projects~Domain~Repository.OutSleepingRepository
- Direction
- Projects~Data~Repository~OutSleeping uses Projects~Domain~Repository, so a change to Projects~Domain~Repository can break Projects~Data~Repository~OutSleeping, while a change to Projects~Data~Repository~OutSleeping can't break Projects~Domain~Repository.
- Position
- Below the diagonal: Projects~Data~Repository~OutSleeping uses a module listed above it, which is the healthy direction.
39→10 Projects~Data~Repository~OutSleeping uses Projects~Data~Network✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~OutSleeping uses a type in Projects~Data~Network.
- The types involved
Projects~Data~Repository~OutSleeping.OutSleepingRepositoryImpl→Projects~Data~Network.Int
- Direction
- Projects~Data~Repository~OutSleeping uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~Repository~OutSleeping, while a change to Projects~Data~Repository~OutSleeping can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~Repository~OutSleeping uses a module listed above it, which is the healthy direction.
39→28 Projects~Data~Repository~OutSleeping uses Projects~Data~DataSource~OutSleeping✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~OutSleeping uses a type in Projects~Data~DataSource~OutSleeping.
- The types involved
Projects~Data~Repository~OutSleeping.OutSleepingRepositoryImpl→Projects~Data~DataSource~OutSleeping.OutSleepingDataSource
- Direction
- Projects~Data~Repository~OutSleeping uses Projects~Data~DataSource~OutSleeping, so a change to Projects~Data~DataSource~OutSleeping can break Projects~Data~Repository~OutSleeping, while a change to Projects~Data~Repository~OutSleeping can't break Projects~Data~DataSource~OutSleeping.
- Position
- Below the diagonal: Projects~Data~Repository~OutSleeping uses a module listed above it, which is the healthy direction.
40→5 Projects~Data~Repository~WakeupSong uses Projects~Domain~Request✕
- Connections
- 4 pairs of types, where a type in Projects~Data~Repository~WakeupSong uses a type in Projects~Domain~Request.
- The types involved
Projects~Data~Repository~WakeupSong.WakeupSongRepositoryImpl→Projects~Domain~Request.FetchAllowedWakeupSongRequestProjects~Data~Repository~WakeupSong.WakeupSongRepositoryImpl→Projects~Domain~Request.FetchWakeupSongByKeywordRequestProjects~Data~Repository~WakeupSong.WakeupSongRepositoryImpl→Projects~Domain~Request.PostWakeupSongByKeywordRequestProjects~Data~Repository~WakeupSong.WakeupSongRepositoryImpl→Projects~Domain~Request.PostWakeupSongRequest
- Direction
- Projects~Data~Repository~WakeupSong uses Projects~Domain~Request, so a change to Projects~Domain~Request can break Projects~Data~Repository~WakeupSong, while a change to Projects~Data~Repository~WakeupSong can't break Projects~Domain~Request.
- Position
- Below the diagonal: Projects~Data~Repository~WakeupSong uses a module listed above it, which is the healthy direction.
40→6 Projects~Data~Repository~WakeupSong uses Projects~Domain~Response✕
- Connections
- 3 pairs of types, where a type in Projects~Data~Repository~WakeupSong uses a type in Projects~Domain~Response.
- The types involved
Projects~Data~Repository~WakeupSong.WakeupSongRepositoryImpl→Projects~Domain~Response.WakeupSongChartResponseProjects~Data~Repository~WakeupSong.WakeupSongRepositoryImpl→Projects~Domain~Response.WakeupSongResponseProjects~Data~Repository~WakeupSong.WakeupSongRepositoryImpl→Projects~Domain~Response.WakeupSongSearchResponse
- Direction
- Projects~Data~Repository~WakeupSong uses Projects~Domain~Response, so a change to Projects~Domain~Response can break Projects~Data~Repository~WakeupSong, while a change to Projects~Data~Repository~WakeupSong can't break Projects~Domain~Response.
- Position
- Below the diagonal: Projects~Data~Repository~WakeupSong uses a module listed above it, which is the healthy direction.
40→7 Projects~Data~Repository~WakeupSong uses Projects~Domain~Repository✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~WakeupSong uses a type in Projects~Domain~Repository.
- The types involved
Projects~Data~Repository~WakeupSong.WakeupSongRepositoryImpl→Projects~Domain~Repository.WakeupSongRepository
- Direction
- Projects~Data~Repository~WakeupSong uses Projects~Domain~Repository, so a change to Projects~Domain~Repository can break Projects~Data~Repository~WakeupSong, while a change to Projects~Data~Repository~WakeupSong can't break Projects~Domain~Repository.
- Position
- Below the diagonal: Projects~Data~Repository~WakeupSong uses a module listed above it, which is the healthy direction.
40→10 Projects~Data~Repository~WakeupSong uses Projects~Data~Network✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~WakeupSong uses a type in Projects~Data~Network.
- The types involved
Projects~Data~Repository~WakeupSong.WakeupSongRepositoryImpl→Projects~Data~Network.Int
- Direction
- Projects~Data~Repository~WakeupSong uses Projects~Data~Network, so a change to Projects~Data~Network can break Projects~Data~Repository~WakeupSong, while a change to Projects~Data~Repository~WakeupSong can't break Projects~Data~Network.
- Position
- Below the diagonal: Projects~Data~Repository~WakeupSong uses a module listed above it, which is the healthy direction.
40→31 Projects~Data~Repository~WakeupSong uses Projects~Data~DataSource~WakeupSong✕
- Connections
- 1 pair of types, where a type in Projects~Data~Repository~WakeupSong uses a type in Projects~Data~DataSource~WakeupSong.
- The types involved
Projects~Data~Repository~WakeupSong.WakeupSongRepositoryImpl→Projects~Data~DataSource~WakeupSong.WakeupSongDataSource
- Direction
- Projects~Data~Repository~WakeupSong uses Projects~Data~DataSource~WakeupSong, so a change to Projects~Data~DataSource~WakeupSong can break Projects~Data~Repository~WakeupSong, while a change to Projects~Data~Repository~WakeupSong can't break Projects~Data~DataSource~WakeupSong.
- Position
- Below the diagonal: Projects~Data~Repository~WakeupSong 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
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No tests found finding(s) in Test Distribution; Resolve the 85 Orphaned file finding(s) in Knowledge Freshness — start with ClubApplyView.swift, RegisterInfoView.swift, NightProjectApplyView.swift.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No tests found finding(s) in Test Distribution. | +17.3 pts | Low | Test Distribution |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +17.3 pts | High | Code Coverage |
| Resolve the 85 Orphaned file finding(s) in Knowledge Freshness — start with ClubApplyView.swift, RegisterInfoView.swift, NightProjectApplyView.swift. | +8.3 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. | +7.1 pts | Medium | Architecture documentation |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +4.7 pts | Medium | CI/CD gates |
| Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +4.7 pts | Medium | Observability |
| Resolve the 1 Floating branch dependency finding(s) in Dependency Hygiene. | +1.9 pts | Low | Dependency Hygiene |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.9 pts | Medium | Release Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| Projects/Feature/Source/NightStudy/Component/NightStudyApplyCell.swift | 5.8 | Mixed | Change Coupling: Boundary-crossing change coupling: NightStudyApplyCell.swift ↔ DataUtil.swift |
| Projects/Feature/Source/Meal/MealView.swift | 6.2 | Mixed | Change Coupling: Boundary-crossing change coupling: MealView.swift ↔ DataUtil.swift |
| Projects/Feature/Source/NightStudy/NightStudyView.swift | 6.3 | Mixed | Cognitive Complexity: NightStudyView.body (cognitive 37) |
| Projects/Feature/Source/Out/Component/OutGoingCell.swift | 6.5 | Mixed | Change Coupling: Boundary-crossing change coupling: OutGoingCell.swift ↔ DataUtil.swift |
| Projects/Feature/Source/Division/DivisionView.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Projects/Feature/Source/Club/MyClub/Component/AffiliationCell.swift | 7.0 | Mixed | Cognitive Complexity: AffiliationCell.body (cognitive 19) |
| Projects/Feature/Source/Home/Component/NightStudyStatusContainer.swift | 7.0 | Mixed | Code Duplication: Duplicated block (30–31 lines × 2) |
| Projects/Feature/Source/WakeupSong/Component/TomorrowWakeupSongCell.swift | 7.0 | Mixed | Code Duplication: Duplicated block (14 lines × 2) |
| Projects/Feature/Source/NightStudy/Component/NightProjectApplyCell.swift | 7.1 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| Projects/Feature/Source/Club/Apply/ClubApplyView.swift | 7.2 | Mixed | Cyclomatic Complexity: ClubApplyView.body (cyclomatic 17) |
| Projects/Feature/Source/Auth/Register/Info/RegisterInfoView.swift | 7.4 | Mixed | Cyclomatic Complexity: RegisterInfoView.body (cyclomatic 32) |
| Projects/Feature/Source/NightStudy/NightProjectApply/NightProjectApplyView.swift | 7.4 | Mixed | God Classes: MethodTooLong: NightProjectApplyView.body |
| Projects/Feature/Source/NightStudy/ManageNightStudy/Ban/Component/RejectNightStudySheetCell.swift | 7.4 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| Projects/Feature/Source/Club/ClubView.swift | 7.8 | Mixed | Cognitive Complexity: ClubView.body (cognitive 24) |
| Projects/Feature/Source/WakeupSong/WakeupSongView.swift | 7.8 | Mixed | Cognitive Complexity: WakeupSongView.body (cognitive 21) |
| Projects/Feature/Source/Home/HomeView.swift | 7.8 | Mixed | Cognitive Complexity: HomeView.body (cognitive 17) |
| Projects/Feature/Source/Out/OutApply/OutApplyView.swift | 7.8 | Mixed | Cognitive Complexity: OutApplyView.body (cognitive 16) |
| Projects/Feature/Source/NightStudy/ManageNightStudy/Approve/ApproveNightStudyView.swift | 7.8 | Mixed | Code Duplication: Duplicated block (26 lines × 2) |
| Projects/Feature/Source/Division/Detail/DivisionDetailViewModel.swift | 7.8 | Mixed | Code Duplication: Duplicated block (13 lines × 2) |
| Projects/Data/Network/Source/Service/OutGoing/OutGoingService.swift | 7.8 | Mixed | Code Duplication: Duplicated block (7 lines × 2) |
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 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 40 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, 189 of 209 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D20 ADR Quality — 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. The ADR expectation is gated on whether a repository ships a deployable product. Our repo-kind classifier reads .NET project files and the host and package markers of the other ecosystems it knows (a Go `package main`, a Cargo binary, a package.json `bin`, `start` script or application dev server such as Vite or Next, Python console scripts or a Django/WSGI entry point, a Spring Boot / WAR / Gradle application build, a Rack or Rails app, a Composer project, an OTP release or escript, a Dockerfile, a Procfile, a Platform.sh `.platform/routes.yaml`, and the corresponding published-package manifests, including an OTP `*.app.src`, a Drupal module's `*.info` and a Claude Code `.claude-plugin/plugin.json`), and found none here, so we could not tell what kind of repository this is and did not assess its ADR log. This is a gap in our analyzer, not a finding about this repository.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — 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. Project size and spread are measured over build units (a .NET project, a Maven or Gradle module, an npm, Deno or JSR package, a Go module, a Cargo crate, a Python, Composer, Bundler, RubyGems, Mix, rebar3, sbt, SwiftPM or pub package, an OTP application, an Xcode project or XcodeGen spec, or a checkout that declares no build at all) whose source a code model reads. This repository's production source is in a language no model reads, or in units whose build tool D26 does not recognise. That is a gap in this analyzer's language reach — not a finding that the repository's projects are cohesive.
- D32 Data Compliance (PII/GDPR) — 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. `Projects/App/iOS-Widget/Source/Component/MealMenuText.swift`, `Projects/App/iOS-Widget/Source/DI/Assembly/RepositoryAssembly.swift`, `Projects/App/iOS-Widget/Source/Widget/DodamMealWidget.swift`, `Projects/App/iOS/Source/DI/Assembly/RepositoryAssembly.swift`, `Projects/App/iOS/Source/DI/Assembly/UseCaseAssembly.swift`, … (+23 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Swinject, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: a native UI project (Projects/App/iOS/Resource/LaunchScreen.storyboard). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P8 Schema migrations — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust and Dart source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust or Dart was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Scala, JavaScript/TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart and Ruby source only, and no C# was loaded and no Scala, JavaScript, TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RegisterInfoView.body at 32.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with RegisterInfoView.body (cyclomatic 32), ClubApplyView.body (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
11 method(s) exceeded the cognitive complexity threshold of 15; the worst was RegisterInfoView.body at 39.
What to do
- Bring the 11 bodies over 15 down to 15 or less in Cognitive Complexity — start with RegisterInfoView.body (cognitive 39), NightStudyView.body (cognitive 37), OutView.body (cognitive 26). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 11 together lifts Cognitive Complexity from 8.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
8 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 8 MethodTooLong finding(s) in God Classes — start with RegisterInfoView.swift, ClubApplyView.swift, NightProjectApplyView.swift. — One of this dimension's main actionable groups (8 warning-level).
- Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
48 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 4 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with OutGoingResponse.swift, DivisionView.swift, ApproveNightStudySheetCell.swift. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with AllView.swift, NightProjectApplyView.swift, AddMemberViewModel.swift. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with AffiliationCell.swift, NightProjectApplyCell.swift, RejectNightStudySheetCell.swift. — One of this dimension's main actionable groups (3 warning-level).
- Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
10 production modules (Tuist), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence.
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Stand up a CI pipeline, then gate Coupling in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
2 of 37 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with AppDelegate.swift, MealType.swift. — One of this dimension's main actionable groups (2 warning-level).
- Stand up a CI pipeline, then gate Cohesion (LCOM4) in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
- Stand up a CI pipeline, then gate Code Coverage in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
No test suite found.
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D12 · Dependency Hygiene
4 outdated direct SwiftPM dependencies, 1 pinning defect(s). 9 of 10 direct dependencies had their releases listed (0 naming no readable repository, 1 pinned to a branch or a revision rather than a version). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question.
What to do
- Resolve the 1 Floating branch dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 28 SwiftPM package(s) use a banned license. SwiftPM has no package registry, so each package's licence is the one its repository declares: 26 of them read from the licence file the repository carries at the revision Package.resolved pins, and 2 — unpinned, or whose licence file could not be read or named — from api.deps.dev, which reports the licence the repository declares today. Graded: every package a committed Package.resolved pins, direct and transitive, and every declared dependency none pins. 1 of them declare no licence that matches a known SPDX licence; that is missing data, not a violation, and none of them is charged.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: Projects/Feature/Source/Home/HomeViewModel.swift (3 of 3 changes were fixes)
What to do
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with HomeViewModel.swift. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Projects/Feature/Source/Club/Apply/ClubApplyView.swift. Counted over 85 of the 372 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
5 deducted task-comment markers across 16569 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 5 TodoComment finding(s) in Explicit Debt — start with NoticeView.swift, NoticeFile.swift, MealView.swift. — One of this dimension's main actionable groups (5 warning-level).
- Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D27 · Navigability
66 % of calls cross a namespace and 31 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
85 of 85 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Projects/Feature/Source/Club/Apply/ClubApplyView.swift. Counted over 85 of the 372 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 85 Orphaned file finding(s) in Knowledge Freshness — start with ClubApplyView.swift, RegisterInfoView.swift, NightProjectApplyView.swift. — One of this dimension's main actionable groups (85 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: NightStudyStatusContainer.swift↔OutStatusContainer.swift 86%; NightStudyDataSource.swift↔NightStudyRepository.swift 85%; TomorrowWakeupSongCell.swift↔WakeupSongCell.swift 82%
What to do
- Resolve the 4 Boundary-crossing change coupling finding(s) in Change Coupling — start with MealView.swift, OutSleepingCell.swift, OutGoingCell.swift. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 11 Change coupling finding(s) in Change Coupling — start with NightStudyApplyCell.swift (2), WakeupSongApplyViewModel.swift (2), NightStudyStatusContainer.swift. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 3 Change-coupling hub finding(s) in Change Coupling — start with NightStudyRepository.swift, NightStudyRepositoryImpl.swift, NightStudyView.swift. — One of this dimension's main actionable groups (3 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
DM4 · Rich vs anemic domain model
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- 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 1 of 1 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
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
- Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Run what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
- `sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — Projects/Shared/Source/Foundation/TaskExt.swift:12
What to do
- Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.
X14 · Bypassable address classification
X26 · Unsynchronised callback handoff
X28 · Index access outside its own emptiness guard
X3 · Exception handling
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 93% | Exemplary | Solid. |
| Architecture | 90% | Exemplary | Solid. |
| Maturity | 39% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 16% | Critical — gated by D8, D9, P1, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Checked 2 of 7 | Strongest area. |
| Domain Modelling | 100% | Exemplary | Solid. |
| Performance | 85% | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 80 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — Repository kind not determined
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Swift not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .swift, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 measured no build unit over this repository's .swift source. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 28 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Aggregate boundaries — not scored for Swift: the sidecar flattens array/collection types (a child COLLECTION = legitimate membership vs a single embedded aggregate is indistinguishable), and aggregate-vs-value-object classification cannot be told apart in source (every struct-holding-struct reads alike) — reported as guidance rather than measured
- DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
- DM3 Integration-event coupling — not scored for Swift: a cross-SwiftPM-target domain leak cannot be told apart in source from a legitimate shared-kernel/contracts module, and most repositories ship a single module — reported as guidance rather than measured
- DM7 Repository granularity — not scored for Swift: 'a repository per CHILD entity' needs the aggregate-root structure, which is not source-resolvable — reported as guidance rather than measured
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Swift source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `swift test --enable-code-coverage` (SwiftPM) or `xcodebuild test -scheme <YourScheme> -enableCodeCoverage YES` (an .xcodeproj/.xcworkspace suite), then `xcrun llvm-cov export -format=lcov`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X15 Unvalidated length from an untrusted reader — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — Not applicable: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. Swift has no `++` or `--`, and an assignment yields `()`, which cannot be an operand of `&&`, `||` or `?:` nor the Bool a `case … where` clause needs. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. Swift's `Array`, `Dictionary` and `Set` are values: `for x in items` walks the copy taken when the loop starts, so a body that adds to or removes from `items` changes a different value, nothing is invalidated, and every original element is still visited. This repository's Swift names no Foundation mutable collection (`NSMutableArray` and kin), the one kind a Swift loop can walk by reference. Not a gap in the analyzer and not a finding about your code.
- X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 5 finding(s)
- Boundary-crossing change coupling: MealView.swift ↔ DataUtil.swift Projects/Feature/Source/Meal/MealView.swift:1
- Boundary-crossing change coupling: OutSleepingCell.swift ↔ DataUtil.swift Projects/Feature/Source/Out/Component/OutSleepingCell.swift:1
- Boundary-crossing change coupling: OutGoingCell.swift ↔ DataUtil.swift Projects/Feature/Source/Out/Component/OutGoingCell.swift:1
- Boundary-crossing change coupling: NightStudyApplyCell.swift ↔ DataUtil.swift Projects/Feature/Source/NightStudy/Component/NightStudyApplyCell.swift:1
- No automated tests
Serious — 100 finding(s)
- Change coupling: NightStudyStatusContainer.swift ↔ OutStatusContainer.swift Projects/Feature/Source/Home/Component/NightStudyStatusContainer.swift:1
- Change coupling: TomorrowWakeupSongCell.swift ↔ WakeupSongCell.swift Projects/Feature/Source/WakeupSong/Component/TomorrowWakeupSongCell.swift:1
- Change coupling: OutGoingCell.swift ↔ OutSleepingCell.swift Projects/Feature/Source/Out/Component/OutGoingCell.swift:1
- Change coupling: NightStudyApplyCell.swift ↔ OutGoingCell.swift Projects/Feature/Source/NightStudy/Component/NightStudyApplyCell.swift:1
- Change coupling: Project.swift ↔ Project.swift Projects/App/Project.swift:1
- Change coupling: NightStudyDataSource.swift ↔ NightStudyService.swift Projects/Data/DataSource/Source/NightStudy/NightStudyDataSource.swift:1
- Change coupling: NightStudyApplyCell.swift ↔ OutSleepingCell.swift Projects/Feature/Source/NightStudy/Component/NightStudyApplyCell.swift:1
- Change coupling: HomeViewModel.swift ↔ MealViewModel.swift Projects/Feature/Source/Home/HomeViewModel.swift:1
- Change coupling: WakeupSongApplyViewModel.swift ↔ WakeupSongViewModel.swift Projects/Feature/Source/WakeupSong/Apply/WakeupSongApplyViewModel.swift:1
- Change coupling: WakeupSongApplyViewModel.swift ↔ WakeupSongView.swift Projects/Feature/Source/WakeupSong/Apply/WakeupSongApplyViewModel.swift:1
- Change coupling: NightProjectApplyViewModel.swift ↔ NightStudyApplyView.swift Projects/Feature/Source/NightStudy/NightProjectApply/NightProjectApplyViewModel.swift:1
- MethodTooLong: RegisterInfoView.body Projects/Feature/Source/Auth/Register/Info/RegisterInfoView.swift:19
- MethodTooLong: ClubApplyView.body Projects/Feature/Source/Club/Apply/ClubApplyView.swift:25
- MethodTooLong: NightProjectApplyView.body Projects/Feature/Source/NightStudy/NightProjectApply/NightProjectApplyView.swift:21
- MethodTooLong: OutApplyView.body Projects/Feature/Source/Out/OutApply/OutApplyView.swift:26
- MethodTooLong: HomeView.body Projects/Feature/Source/Home/HomeView.swift:23
- MethodTooLong: WakeupSongApplyView.body Projects/Feature/Source/WakeupSong/Apply/WakeupSongApplyView.swift:20
- MethodTooLong: NightStudyApplyView.body Projects/Feature/Source/NightStudy/NightStudyApply/NightStudyApplyView.swift:21
- MethodTooLong: WakeupSongView.body Projects/Feature/Source/WakeupSong/WakeupSongView.swift:20
- TodoComment Projects/Feature/Source/Notice/NoticeView.swift:47
- TodoComment Projects/Feature/Source/Notice/Component/NoticeFile.swift:24
- TodoComment Projects/Feature/Source/Meal/MealView.swift:114
- TodoComment Projects/Feature/Source/Division/DivisionView.swift:89
- TodoComment Projects/Feature/Source/Division/CreateDivision/CreateDivisionView.swift:38
- Duplicated block (10 lines × 2) Projects/Domain/Source/Response/OutGoing/OutGoingResponse.swift:23
- Duplicated block (10 lines × 2) Projects/Feature/Source/Division/DivisionView.swift:29
- Duplicated block (10 lines × 2) Projects/Feature/Source/NightStudy/ManageNightStudy/Approve/Component/ApproveNightStudySheetCell.swift:42
- Duplicated block (10 lines × 2) Projects/Data/Network/Source/Service/OutGoing/OutGoingService.swift:40
- Duplicated block (8 lines × 2) Projects/Feature/Source/All/AllView.swift:33
- Duplicated block (8 lines × 2) Projects/Feature/Source/NightStudy/NightProjectApply/NightProjectApplyView.swift:49
- Duplicated block (8 lines × 2) Projects/Feature/Source/Division/AddMember/AddMemberViewModel.swift:59
- Duplicated block (8 lines × 2) Projects/Feature/Source/Division/Detail/DivisionDetailViewModel.swift:44
- Change-coupling hub: NightStudyRepository.swift → NightStudyDataSource.swift, NightStudyRemote.swift, NightStudyService.swift, NightProjectApplyView.swift Projects/Domain/Source/Repository/NightStudy/NightStudyRepository.swift
- Change-coupling hub: NightStudyRepositoryImpl.swift → NightStudyRemote.swift, NightStudyService.swift, NightProjectApplyViewModel.swift, NightStudyView.swift, NightStudyViewModel.swift Projects/Data/Repository/Source/NightStudy/NightStudyRepositoryImpl.swift
- Change-coupling hub: NightStudyView.swift → NightStudyDataSource.swift, NightStudyRemote.swift, NightProjectApplyViewModel.swift Projects/Feature/Source/NightStudy/NightStudyView.swift
- Members sharing a duplicated core (4 members, 50+ identical tokens) Projects/Feature/Source/Club/MyClub/Component/AffiliationCell.swift:20
- Members sharing a duplicated core (4 members, 50+ identical tokens) Projects/Feature/Source/NightStudy/Component/NightProjectApplyCell.swift:27
- Members sharing a duplicated core (4 members, 50+ identical tokens) Projects/Feature/Source/NightStudy/ManageNightStudy/Ban/Component/RejectNightStudySheetCell.swift:22
- Duplicated block (16 lines × 2) Projects/Feature/Source/Club/MyClub/Component/CreateClubCell.swift:42
- Duplicated block (16 lines × 2) Projects/Feature/Source/NightStudy/Component/NightProjectApplyCell.swift:50
- Duplicated block (16 lines × 2) Projects/Feature/Source/NightStudy/NightStudyView.swift:36
- Duplicated block (7 lines × 2) Projects/App/iOS-Widget/Source/DI/Assembly/DataSourceAssembly.swift:17
- Duplicated block (7 lines × 2) Projects/Domain/Source/Model/MealModel.swift:22
- Duplicated block (7 lines × 2) Projects/Data/Network/Source/Service/OutGoing/OutGoingService.swift:24
- Duplicated block (17 lines × 2) Projects/Feature/Source/Club/MyClub/Component/AffiliationCell.swift:42
- Duplicated block (17 lines × 2) Projects/Feature/Source/Club/MyClub/Component/AffiliationCell.swift:84
- Duplicated block (15 lines × 2) Projects/Feature/Source/Club/Apply/ClubApplyView.swift:112
- Duplicated block (15 lines × 2) Projects/Feature/Source/NightStudy/ManageNightStudy/Approve/ApproveNightStudyView.swift:18
- Duplicated block (14 lines × 2) Projects/Domain/Source/Response/Member/MemberResponse.swift:32
- Duplicated block (14 lines × 2) Projects/Feature/Source/WakeupSong/Component/TomorrowWakeupSongCell.swift:32
- Duplicated block (13 lines × 2) Projects/Feature/Source/Club/MyClub/Component/AffiliationCell.swift:60
- Duplicated block (13 lines × 2) Projects/Feature/Source/Division/Detail/DivisionDetailViewModel.swift:53
- Duplicated block (5 lines × 2) Projects/App/iOS-Widget/Source/DI/Assembly/LocalAssembly.swift:15
- Duplicated block (5 lines × 2) Projects/Feature/Source/Division/Detail/DivisionDetailView.swift:210
- Duplicated block (6 lines × 2) Projects/Domain/Source/Request/Auth/DeepLinkLoginRequest.swift:9
- Duplicated block (6 lines × 2) Projects/Feature/Source/Division/DivisionViewModel.swift:124
- Duplicated block (8 lines × 3) Projects/Feature/Source/All/AllViewModel.swift:43
- Duplicated block (8 lines × 3) Projects/Data/Network/Source/Service/Meal/MealService.swift:37
- Off the main sequence: DIContainer
- Off the main sequence: Domain
- Low cohesion: AppDelegate (LCOM4 5) Projects/App/iOS/Source/AppDelegate.swift:14
- Low cohesion: Date (LCOM4 4) Projects/Domain/Source/Entity/MealType.swift:38
- RegisterInfoView.body (cyclomatic 32) Projects/Feature/Source/Auth/Register/Info/RegisterInfoView.swift:19
- ClubApplyView.body (cyclomatic 17) Projects/Feature/Source/Club/Apply/ClubApplyView.swift:25
- Floating branch dependency: flowkit
- Repeated repair: Projects/Feature/Source/Home/HomeViewModel.swift Projects/Feature/Source/Home/HomeViewModel.swift:85
- RegisterInfoView.body (cognitive 39) Projects/Feature/Source/Auth/Register/Info/RegisterInfoView.swift:19
- NightStudyView.body (cognitive 37) Projects/Feature/Source/NightStudy/NightStudyView.swift:21
- OutView.body (cognitive 26) Projects/Feature/Source/Out/OutView.swift:22
- ClubView.body (cognitive 24) Projects/Feature/Source/Club/ClubView.swift:19
- ClubApplyView.body (cognitive 24) Projects/Feature/Source/Club/Apply/ClubApplyView.swift:25
- MyClubView.body (cognitive 23) Projects/Feature/Source/Club/MyClub/MyClubView.swift:20
- WakeupSongView.body (cognitive 21) Projects/Feature/Source/WakeupSong/WakeupSongView.swift:20
- AffiliationCell.body (cognitive 19) Projects/Feature/Source/Club/MyClub/Component/AffiliationCell.swift:20
- RemoteInterceptor.retry (cognitive 17) Projects/Data/Network/Source/Remote/RemoteInterceptor.swift:36
- HomeView.body (cognitive 17) Projects/Feature/Source/Home/HomeView.swift:23
- OutApplyView.body (cognitive 16) Projects/Feature/Source/Out/OutApply/OutApplyView.swift:26
- Duplicated block (73–80 lines × 2) Projects/Feature/Source/NightStudy/NightProjectApply/NightProjectApplyView.swift:65
- Duplicated block (30–31 lines × 2) Projects/Feature/Source/Home/Component/NightStudyStatusContainer.swift:25
- Duplicated block (29 lines × 2) Projects/Feature/Source/NightStudy/Component/NightProjectApplyCell.swift:66
- Duplicated block (28 lines × 2) Projects/Feature/Source/Club/MyClub/Component/AffiliationCell.swift:20
- Duplicated block (26 lines × 2) Projects/Feature/Source/NightStudy/ManageNightStudy/Approve/ApproveNightStudyView.swift:46
- Duplicated block (17–25 lines × 2) Projects/Feature/Source/NightStudy/ManageNightStudy/Approve/Component/PendingStudentInfoHeader.swift:12
- Duplicated block (24 lines × 2) Projects/Feature/Source/Club/ClubView.swift:25
- Duplicated block (22 lines × 2) Projects/Feature/Source/NightStudy/Component/NightProjectApplyCell.swift:27
- Duplicated block (19 lines × 2) Projects/Feature/Source/NightStudy/ManageNightStudy/Approve/Component/PendingNightStudyStudentCell.swift:29
- Duplicated block (17 lines × 4) Projects/Feature/Source/NightStudy/Component/NightProjectApplyCell.swift:32
- Duplicated block (11–14 lines × 5) Projects/Feature/Source/NightStudy/ManageNightStudy/Ban/Component/RejectNightStudySheetCell.swift:50
- Duplicated block (12 lines × 3) Projects/Feature/Source/Club/MyClub/Component/AffiliationCell.swift:91
- Duplicated block (11 lines × 4) Projects/Feature/Source/Club/MyClub/Component/AffiliationCell.swift:93
- Duplicated block (11 lines × 3) Projects/Feature/Source/NightStudy/Component/NightProjectApplyCell.swift:91
- Duplicated block (10 lines × 8) Projects/Feature/Source/NightStudy/ManageNightStudy/Ban/Component/RejectNightStudySheetCell.swift:55
- Duplicated block (10 lines × 4) Projects/Feature/Source/Club/MyClub/Component/AffiliationCell.swift:40
- Duplicated block (9 lines × 2) Projects/Feature/Source/NightStudy/ManageNightStudy/Approve/ApproveNightStudyViewModel.swift:28
- Duplicated block (7 lines × 3) Projects/Feature/Source/Club/MyClub/Component/AffiliationCell.swift:29
- Duplicated block (5 lines × 4) Projects/Domain/Source/Entity/ClubTeacher.swift:15
- Duplicated block (5 lines × 3) Projects/Domain/Source/Request/Meal/FetchMealRequest.swift:14
- No CI pipeline
- No structured logging
- Sync-over-async blocking Projects/Shared/Source/Foundation/TaskExt.swift:12
Minor — 99 finding(s)
- Orphaned file Projects/Feature/Source/Club/Apply/ClubApplyView.swift:1
- Orphaned file Projects/Feature/Source/Auth/Register/Info/RegisterInfoView.swift:1
- Orphaned file Projects/Feature/Source/NightStudy/NightProjectApply/NightProjectApplyView.swift:1
- Orphaned file Projects/Feature/Source/ChildrenManage/ChildrenManageView.swift:1
- Orphaned file Projects/Feature/Source/Home/HomeView.swift:1
- Orphaned file Projects/Feature/Source/Out/OutApply/OutApplyView.swift:1
- Orphaned file Projects/Feature/Source/WakeupSong/WakeupSongView.swift:1
- Orphaned file Projects/Feature/Source/Meal/MealView.swift:1
- Orphaned file Projects/Feature/Source/WakeupSong/Apply/WakeupSongApplyView.swift:1
- Orphaned file Projects/Feature/Source/Division/Detail/DivisionDetailView.swift:1
- Orphaned file Projects/Feature/Source/NightStudy/NightStudyApply/NightStudyApplyView.swift:1
- Orphaned file Projects/Feature/Source/Home/HomeViewModel.swift:1
- Orphaned file Projects/Feature/Source/Club/Detail/ClubDetailView.swift:1
- Orphaned file Projects/Feature/Source/All/AllView.swift:1
- Orphaned file Projects/Feature/Source/NightStudy/NightStudyView.swift:1
- Orphaned file Projects/Feature/Source/Out/OutView.swift:1
- Orphaned file Projects/Feature/Source/All/Setting/SettingView.swift:1
- Orphaned file Projects/Feature/Source/Auth/Register/RegisterViewModel.swift:1
- Orphaned file Projects/Feature/Source/Division/AddMember/DivisionAddMember.swift:1
- Orphaned file Projects/Feature/Source/Auth/Login/LoginView.swift:1
- Orphaned file Projects/Feature/Source/All/Setting/EditMemberInfo/EditMemberInfoView.swift:1
- Orphaned file Projects/Feature/Source/Club/MyClub/Component/AffiliationCell.swift:1
- Orphaned file Projects/Feature/Source/NightStudy/Component/NightStudyApplyCell.swift:1
- Orphaned file Projects/Feature/Source/Division/DivisionView.swift:1
- Orphaned file Projects/App/iOS-Widget/Source/Widget/DodamMealWidget.swift:1
- Duplicated predicate Projects/Feature/Source/Home/Component/NightStudyStatusContainer.swift:31
- Duplicated predicate Projects/Feature/Source/NightStudy/ManageNightStudy/Approve/ApproveNightStudyViewModel.swift:34
- Duplicated predicate Projects/Feature/Source/NightStudy/ManageNightStudy/Approve/ApproveNightStudyViewModel.swift:33
- Duplicated predicate Projects/Feature/Source/NightStudy/ManageNightStudy/Approve/ApproveNightStudyViewModel.swift:32
- Duplicated predicate Projects/Feature/Source/NightStudy/ManageNightStudy/Approve/ApproveNightStudyViewModel.swift:31
- Off-boarding risk: anonymized user #1
- High interface indirection
- Dormant codebase
- No tests found
- No ADRs
- No architecture diagram/doc
- No src/ separation
- No SAST
- No changelog
Minor — 5 finding(s)
- Outdated: realm-swift
- Outdated: swiftui-cached-async-image
- Outdated: swiftui-introspect
- Outdated: swinject
- Off the main sequence: Shared
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-983a112fc5bb447cbd0efe916807377f/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-983a112fc5bb447cbd0efe916807377f/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 28 file(s) — `Projects/App/iOS-Widget/Source/Component/MealMenuText.swift`, `Projects/App/iOS-Widget/Source/DI/Assembly/RepositoryAssembly.swift`, `Projects/App/iOS-Widget/Source/Widget/DodamMealWidget.swift`, `Projects/App/iOS/Source/DI/Assembly/RepositoryAssembly.swift`, `Projects/App/iOS/Source/DI/Assembly/UseCaseAssembly.swift`, … (+23 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |