Executive summary
Volmarg/personal-management-system falls short of our standard for production because the project has no automated tests and we found no working pipeline that builds or tests changes to the code. It scores 39.6 out of 100 and is rated Weak, and 34 of its 42 critical findings are security problems.
Production Readiness, at 21.7, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the password or key in the code, worth about 11.6 points. Adding automated tests would lift Production Readiness itself, worth about 16.5 points. Raising Production Readiness to 70 would lift the score to about 54.6.
Twenty settings leave the servers or containers unsafe. Twelve passwords or keys in the code's history and one in the code are open to anyone who can read the repository, and one known security hole in a package the code depends on can be used by attackers. Replacing each exposed password or key, correcting the unsafe settings and updating the vulnerable packages would close these risks. Referring to the other business object by its identifier would take care of the five business objects holding another business object directly.
The product code is 27,096 lines, about €27,000 to rebuild.
If Production Readiness rose from 21.7 to 70, the lowest score rated Strong, the score would rise from 39.6 to about 54.6.
New since the last survey: 43 findings
- Cyclomatic Complexity · JwtTokenResponseListener.onResponse (cyclomatic 16) src/Listeners/Response/JwtTokenResponseListener.php
- Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) src/Migrations/Version20190717144649.php
- Code Duplication · Edited copy of a member (40 corresponding lines) src/Action/Modules/Reports/Payments/MonthlyPerTypeAction.php
- Code Duplication · Edited copy of a member (24 corresponding lines) src/Action/Modules/Calendar/Settings/ManageCalendarsAction.php
- Code Duplication · Edited copies of one member (4 members, 24+ corresponding lines) src/Action/Modules/Contacts/ContactsAction.php
- Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) src/Action/Modules/Goals/GoalsPaymentsAction.php
- Code Duplication · Edited copy of a member (19 corresponding lines) src/Action/Modules/Payments/MyPaymentsIncomeAction.php
- Code Duplication · Edited copy of a member (21 corresponding lines) src/Action/User/Setting/SecurityAction.php
- Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) src/Action/Modules/Health/DoctorAppointmentAction.php
- Code Duplication · Edited copy of a member (18 corresponding lines) src/Action/Modules/Issues/MyIssuesContactAction.php
- Code Duplication · Edited copy of a member (15 corresponding lines) src/Action/Modules/Issues/MyIssuesAction.php
- Code Duplication · Edited copy of a member (20 corresponding lines) src/Services/Database/DatabaseExporter.php
- Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) src/Services/Settings/SettingsSaver.php
- Code Duplication · Edited copy of a member (17 corresponding lines) src/Services/External/NotifierProxyLoggerService.php
- Code Duplication · Edited copy of a member (15 corresponding lines) src/Action/Modules/System/Settings/Dashboard/WidgetsVisibilityAction.php
- Code Duplication · Edited copy of a member (20 corresponding lines) src/Services/Database/DatabaseExporter.php
- Code Duplication · Edited copy of a member (12 corresponding lines) src/DTO/Settings/Finances/SettingsCurrencyDto.php
- Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) src/Repository/Modules/Job/MyJobHolidaysRepository.php
- Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) src/DTO/Settings/Dashboard/SettingsWidgetSettingsDto.php
- Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) src/Action/Modules/Health/DoctorAction.php
- Code Duplication · Edited copy of a member (8 corresponding lines) src/DTO/Settings/Dashboard/Widget/SettingsWidgetVisibilityDto.php
- Code Duplication · Edited copy of a member (9 corresponding lines) src/Entity/Modules/Payments/MyPaymentsIncome.php
- Code Duplication · Edited copy of a member (8 corresponding lines) src/Security/UriAuthenticator.php
- Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) src/Action/Modules/Goals/GoalsListAction.php
- Code Duplication · Edited copy of a member (20 corresponding lines) src/Repository/Modules/Payments/MyPaymentsMonthlyRepository.php
- Code Duplication · Edited copy of a member (25 corresponding lines) src/Repository/Modules/Reports/ReportsRepository.php
- Code Duplication · Duplicated block (9 lines × 2) src/Migrations/Version20191110042650.php
- Code Duplication · Duplicated block (8 lines × 4) src/Migrations/Version20190824131917.php
- Code Duplication · Duplicated block (6 lines × 7) src/Migrations/Version20190717144649.php
- Code Duplication · Duplicated block (10 lines × 8) src/Migrations/Version20190907074501.php
- Code Duplication · Duplicated block (8 lines × 4) src/Migrations/Version20190908031047.php
- Code Duplication · Duplicated block (10 lines × 2) src/Migrations/Version20191102073301.php
- Code Duplication · Edited copy of a member (20 corresponding lines) src/DataFixtures/Modules/Notes/MyNotesSettingsFixtures.php
- Code Duplication · Edited copy of a member (15 corresponding lines) src/DataFixtures/Modules/Issues/MyIssues.php
- Code Duplication · Edited copy of a member (18 corresponding lines) src/DataFixtures/Modules/Todo/MyTodoFixtures.php
- Coupling · Circular dependency src/Action/File/UploadedFileAction.php
- Coupling · Unstable project src/Action
- Coupling · Off the main sequence: src
- Coupling · Off the main sequence: src/Attribute
- Coupling · Off the main sequence: src/Doctrine
- Coupling · Off the main sequence: src/Exception
- Coupling · Off the main sequence: src/Traits
- Churn × Complexity Hotspots · Hotspot: src/Listeners/Response/JwtTokenResponseListener.php src/Listeners/Response/JwtTokenResponseListener.php
Fixed since the last survey: 28 findings
- Code Duplication · Duplicated block (5 lines × 2) src/Action/Modules/Job/MyJobHolidaysAction.php
- Code Duplication · Duplicated block (15 lines × 2) src/Action/Modules/Contacts/ContactsAction.php
- Dependency Hygiene · Abandoned package: sensio/framework-extra-bundle
- Dependency Hygiene · Abandoned package: sensiolabs/security-checker
- Dependency Hygiene · Abandoned package: twig/extensions
- REDACTED Scanning · Leaked secret: REDACTED config/jwt/dev/private.pem
- Secrets (history) · REDACTED: REDACTED config/jwt/dev/private.pem
- Secrets (history) · High secret: REDACTED package-lock.json
- Secrets (history) · High secret: REDACTED package.json
- Secrets (history) · REDACTED: REDACTED public/assets/app.js
- Secrets (history) · REDACTED: REDACTED public/assets/app.js
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Rebuild cost: about €27,000 · Estimate
| Cost to rebuild | €8,800 to €44,000, for 147 to 466 hours of work, about 0.2 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 40. 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 | Medium: 27,096 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 DTO | 2 Entity.Interfaces | 3 Response.Base | 4 Services.Module.Todo | 5 Services.Routing | 6 Action.Modules.Goals | 7 Action.Modules.Passwords | 8 Entity | 9 Entity.Modules.Contacts | 10 Entity.Modules.Payments | 11 Entity.Modules.Schedules | 12 Entity.System | 13 Repository.Modules.Storage | 14 Services.Attribute | 15 Services.External | 16 Services.Validation.Validators | 17 Action.Modules.Contacts.Settings | 18 Entity.Modules.Todo | 19 Repository | 20 Repository.Modules.Payments | 21 Repository.Modules.Schedules | 22 Services.Validation | 23 Action.Modules.Calendar | 24 Action.Modules.Job | 25 Action.Modules.Payments | 26 Action.Modules.Payments.Bills | 27 Action.Modules.Payments.Settings | 28 Command.Crons | 29 Entity.Modules.Issues | 30 Services.Settings | 31 Action.Modules.Issues | 32 Action.Modules.System.Settings | 33 Command.Module.Schedules | 34 Services.Security | 35 Listeners.Response | 36 Services.System | 37 Action.Modules.Dashboard | 38 Action.Modules.Notes | 39 Listeners.Request.Kernel | 40 Services.Module.Storage |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 DTO | ||||||||||||||||||||||||||||||||||||||||
| 2 Entity.Interfaces | ||||||||||||||||||||||||||||||||||||||||
| 3 Response.Base | ||||||||||||||||||||||||||||||||||||||||
| 4 Services.Module.Todo | ||||||||||||||||||||||||||||||||||||||||
| 5 Services.Routing | ||||||||||||||||||||||||||||||||||||||||
| 6 Action.Modules.Goals | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 Action.Modules.Passwords | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 Entity | 4 | |||||||||||||||||||||||||||||||||||||||
| 9 Entity.Modules.Contacts | 6 | |||||||||||||||||||||||||||||||||||||||
| 10 Entity.Modules.Payments | 19 | |||||||||||||||||||||||||||||||||||||||
| 11 Entity.Modules.Schedules | 5 | |||||||||||||||||||||||||||||||||||||||
| 12 Entity.System | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 Repository.Modules.Storage | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 Services.Attribute | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Services.External | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Services.Validation.Validators | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 Action.Modules.Contacts.Settings | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 18 Entity.Modules.Todo | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 Repository | 3 | |||||||||||||||||||||||||||||||||||||||
| 20 Repository.Modules.Payments | 3 | |||||||||||||||||||||||||||||||||||||||
| 21 Repository.Modules.Schedules | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 Services.Validation | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 Action.Modules.Calendar | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 Action.Modules.Job | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 Action.Modules.Payments | 4 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 26 Action.Modules.Payments.Bills | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 Action.Modules.Payments.Settings | 2 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 Command.Crons | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 29 Entity.Modules.Issues | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 Services.Settings | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 Action.Modules.Issues | 5 | |||||||||||||||||||||||||||||||||||||||
| 32 Action.Modules.System.Settings | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 33 Command.Module.Schedules | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 Services.Security | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 Listeners.Response | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 Services.System | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 Action.Modules.Dashboard | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 Action.Modules.Notes | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 Listeners.Request.Kernel | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 Services.Module.Storage | 3 | 3 | 1 |
6→4 Action.Modules.Goals uses Services.Module.Todo✕
- Connections
- 1 pair of types, where a type in Action.Modules.Goals uses a type in Services.Module.Todo.
- The types involved
App.Action.Modules.Goals.GoalsListAction→App.Services.Module.Todo.MyTodoService
- Direction
- Action.Modules.Goals uses Services.Module.Todo, so a change to Services.Module.Todo can break Action.Modules.Goals, while a change to Action.Modules.Goals can't break Services.Module.Todo.
- Position
- Below the diagonal: Action.Modules.Goals uses a module listed above it, which is the healthy direction.
7→3 Action.Modules.Passwords uses Response.Base✕
- Connections
- 2 pairs of types, where a type in Action.Modules.Passwords uses a type in Response.Base.
- The types involved
App.Action.Modules.Passwords.MyPasswordsAction→App.Response.Base.BaseResponseApp.Action.Modules.Passwords.MyPasswordsGroupsAction→App.Response.Base.BaseResponse
- Direction
- Action.Modules.Passwords uses Response.Base, so a change to Response.Base can break Action.Modules.Passwords, while a change to Action.Modules.Passwords can't break Response.Base.
- Position
- Below the diagonal: Action.Modules.Passwords uses a module listed above it, which is the healthy direction.
8→2 Entity uses Entity.Interfaces✕
- Connections
- 4 pairs of types, where a type in Entity uses a type in Entity.Interfaces.
- The types involved
App.Entity.FilesTags→App.Entity.Interfaces.EntityInterfaceApp.Entity.FilesTags→App.Entity.Interfaces.SoftDeletableEntityInterfaceApp.Entity.Setting→App.Entity.Interfaces.EntityInterfaceApp.Entity.User→App.Entity.Interfaces.EntityInterface
- Direction
- Entity uses Entity.Interfaces, so a change to Entity.Interfaces can break Entity, while a change to Entity can't break Entity.Interfaces.
- Position
- Below the diagonal: Entity uses a module listed above it, which is the healthy direction.
9→2 Entity.Modules.Contacts uses Entity.Interfaces✕
- Connections
- 6 pairs of types, where a type in Entity.Modules.Contacts uses a type in Entity.Interfaces.
- The types involved
App.Entity.Modules.Contacts.MyContact→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Contacts.MyContact→App.Entity.Interfaces.SoftDeletableEntityInterfaceApp.Entity.Modules.Contacts.MyContactGroup→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Contacts.MyContactGroup→App.Entity.Interfaces.SoftDeletableEntityInterfaceApp.Entity.Modules.Contacts.MyContactType→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Contacts.MyContactType→App.Entity.Interfaces.SoftDeletableEntityInterface
- Direction
- Entity.Modules.Contacts uses Entity.Interfaces, so a change to Entity.Interfaces can break Entity.Modules.Contacts, while a change to Entity.Modules.Contacts can't break Entity.Interfaces.
- Position
- Below the diagonal: Entity.Modules.Contacts uses a module listed above it, which is the healthy direction.
10→2 Entity.Modules.Payments uses Entity.Interfaces✕
- Connections
- 19 pairs of types, where a type in Entity.Modules.Payments uses a type in Entity.Interfaces.
- The types involved
App.Entity.Modules.Payments.MyPaymentsBills→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Payments.MyPaymentsBills→App.Entity.Interfaces.SoftDeletableEntityInterfaceApp.Entity.Modules.Payments.MyPaymentsBillsItems→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Payments.MyPaymentsBillsItems→App.Entity.Interfaces.SoftDeletableEntityInterfaceApp.Entity.Modules.Payments.MyPaymentsIncome→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Payments.MyPaymentsIncome→App.Entity.Interfaces.SoftDeletableEntityInterfaceApp.Entity.Modules.Payments.MyPaymentsMonthly→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Payments.MyPaymentsMonthly→App.Entity.Interfaces.SoftDeletableEntityInterfaceApp.Entity.Modules.Payments.MyPaymentsOwed→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Payments.MyPaymentsOwed→App.Entity.Interfaces.SoftDeletableEntityInterfaceApp.Entity.Modules.Payments.MyPaymentsProduct→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Payments.MyPaymentsProduct→App.Entity.Interfaces.SoftDeletableEntityInterfaceApp.Entity.Modules.Payments.MyPaymentsSettings→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Payments.MyPaymentsSettings→App.Entity.Interfaces.SoftDeletableEntityInterfaceApp.Entity.Modules.Payments.MyRecurringPaymentMonthly→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Payments.MyRecurringPaymentMonthly→App.Entity.Interfaces.SoftDeletableEntityInterfaceApp.Entity.Modules.Payments.MyRecurringPaymentMonthly→App.Entity.Interfaces.ValidateEntityForCreateInterfaceApp.Entity.Modules.Payments.MyRecurringPaymentMonthly→App.Entity.Interfaces.ValidateEntityForUpdateInterfaceApp.Entity.Modules.Payments.MyRecurringPaymentMonthly→App.Entity.Interfaces.ValidateEntityInterface
- Direction
- Entity.Modules.Payments uses Entity.Interfaces, so a change to Entity.Interfaces can break Entity.Modules.Payments, while a change to Entity.Modules.Payments can't break Entity.Interfaces.
- Position
- Below the diagonal: Entity.Modules.Payments uses a module listed above it, which is the healthy direction.
11→2 Entity.Modules.Schedules uses Entity.Interfaces✕
- Connections
- 5 pairs of types, where a type in Entity.Modules.Schedules uses a type in Entity.Interfaces.
- The types involved
App.Entity.Modules.Schedules.MySchedule→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Schedules.MySchedule→App.Entity.Interfaces.SoftDeletableEntityInterfaceApp.Entity.Modules.Schedules.MyScheduleCalendar→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Schedules.MyScheduleCalendar→App.Entity.Interfaces.SoftDeletableEntityInterfaceApp.Entity.Modules.Schedules.MyScheduleReminder→App.Entity.Interfaces.SoftDeletableEntityInterface
- Direction
- Entity.Modules.Schedules uses Entity.Interfaces, so a change to Entity.Interfaces can break Entity.Modules.Schedules, while a change to Entity.Modules.Schedules can't break Entity.Interfaces.
- Position
- Below the diagonal: Entity.Modules.Schedules uses a module listed above it, which is the healthy direction.
12→2 Entity.System uses Entity.Interfaces✕
- Connections
- 2 pairs of types, where a type in Entity.System uses a type in Entity.Interfaces.
- The types involved
App.Entity.System.LockedResource→App.Entity.Interfaces.EntityInterfaceApp.Entity.System.Module→App.Entity.Interfaces.EntityInterface
- Direction
- Entity.System uses Entity.Interfaces, so a change to Entity.Interfaces can break Entity.System, while a change to Entity.System can't break Entity.Interfaces.
- Position
- Below the diagonal: Entity.System uses a module listed above it, which is the healthy direction.
13→2 Repository.Modules.Storage uses Entity.Interfaces✕
- Connections
- 2 pairs of types, where a type in Repository.Modules.Storage uses a type in Entity.Interfaces.
- The types involved
App.Repository.Modules.Storage.StorageFileRepository→App.Entity.Interfaces.EntityInterfaceApp.Repository.Modules.Storage.StorageFileRepository→App.Entity.Interfaces.FileStorageAssociationInterface
- Direction
- Repository.Modules.Storage uses Entity.Interfaces, so a change to Entity.Interfaces can break Repository.Modules.Storage, while a change to Repository.Modules.Storage can't break Entity.Interfaces.
- Position
- Below the diagonal: Repository.Modules.Storage uses a module listed above it, which is the healthy direction.
14→5 Services.Attribute uses Services.Routing✕
- Connections
- 1 pair of types, where a type in Services.Attribute uses a type in Services.Routing.
- The types involved
App.Services.Attribute.AttributeReaderService→App.Services.Routing.UrlMatcherService
- Direction
- Services.Attribute uses Services.Routing, so a change to Services.Routing can break Services.Attribute, while a change to Services.Attribute can't break Services.Routing.
- Position
- Below the diagonal: Services.Attribute uses a module listed above it, which is the healthy direction.
15→1 Services.External uses DTO✕
- Connections
- 1 pair of types, where a type in Services.External uses a type in DTO.
- The types involved
App.Services.External.DiscordService→App.DTO.NotificationDto
- Direction
- Services.External uses DTO, so a change to DTO can break Services.External, while a change to Services.External can't break DTO.
- Position
- Below the diagonal: Services.External uses a module listed above it, which is the healthy direction.
16→1 Services.Validation.Validators uses DTO✕
- Connections
- 1 pair of types, where a type in Services.Validation.Validators uses a type in DTO.
- The types involved
App.Services.Validation.Validators.AbstractValidator→App.DTO.ValidationResultDto
- Direction
- Services.Validation.Validators uses DTO, so a change to DTO can break Services.Validation.Validators, while a change to Services.Validation.Validators can't break DTO.
- Position
- Below the diagonal: Services.Validation.Validators uses a module listed above it, which is the healthy direction.
16→2 Services.Validation.Validators uses Entity.Interfaces✕
- Connections
- 1 pair of types, where a type in Services.Validation.Validators uses a type in Entity.Interfaces.
- The types involved
App.Services.Validation.Validators.AbstractValidator→App.Entity.Interfaces.ValidateEntityInterface
- Direction
- Services.Validation.Validators uses Entity.Interfaces, so a change to Entity.Interfaces can break Services.Validation.Validators, while a change to Services.Validation.Validators can't break Entity.Interfaces.
- Position
- Below the diagonal: Services.Validation.Validators uses a module listed above it, which is the healthy direction.
17→3 Action.Modules.Contacts.Settings uses Response.Base✕
- Connections
- 2 pairs of types, where a type in Action.Modules.Contacts.Settings uses a type in Response.Base.
- The types involved
App.Action.Modules.Contacts.Settings.GroupAction→App.Response.Base.BaseResponseApp.Action.Modules.Contacts.Settings.TypeAction→App.Response.Base.BaseResponse
- Direction
- Action.Modules.Contacts.Settings uses Response.Base, so a change to Response.Base can break Action.Modules.Contacts.Settings, while a change to Action.Modules.Contacts.Settings can't break Response.Base.
- Position
- Below the diagonal: Action.Modules.Contacts.Settings uses a module listed above it, which is the healthy direction.
17→9 Action.Modules.Contacts.Settings uses Entity.Modules.Contacts✕
- Connections
- 2 pairs of types, where a type in Action.Modules.Contacts.Settings uses a type in Entity.Modules.Contacts.
- The types involved
App.Action.Modules.Contacts.Settings.GroupAction→App.Entity.Modules.Contacts.MyContactGroupApp.Action.Modules.Contacts.Settings.TypeAction→App.Entity.Modules.Contacts.MyContactType
- Direction
- Action.Modules.Contacts.Settings uses Entity.Modules.Contacts, so a change to Entity.Modules.Contacts can break Action.Modules.Contacts.Settings, while a change to Action.Modules.Contacts.Settings can't break Entity.Modules.Contacts.
- Position
- Below the diagonal: Action.Modules.Contacts.Settings uses a module listed above it, which is the healthy direction.
18→2 Entity.Modules.Todo uses Entity.Interfaces✕
- Connections
- 4 pairs of types, where a type in Entity.Modules.Todo uses a type in Entity.Interfaces.
- The types involved
App.Entity.Modules.Todo.MyTodo→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Todo.MyTodo→App.Entity.Interfaces.SoftDeletableEntityInterfaceApp.Entity.Modules.Todo.MyTodoElement→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Todo.MyTodoElement→App.Entity.Interfaces.SoftDeletableEntityInterface
- Direction
- Entity.Modules.Todo uses Entity.Interfaces, so a change to Entity.Interfaces can break Entity.Modules.Todo, while a change to Entity.Modules.Todo can't break Entity.Interfaces.
- Position
- Below the diagonal: Entity.Modules.Todo uses a module listed above it, which is the healthy direction.
18→12 Entity.Modules.Todo uses Entity.System✕
- Connections
- 1 pair of types, where a type in Entity.Modules.Todo uses a type in Entity.System.
- The types involved
App.Entity.Modules.Todo.MyTodo→App.Entity.System.Module
- Direction
- Entity.Modules.Todo uses Entity.System, so a change to Entity.System can break Entity.Modules.Todo, while a change to Entity.Modules.Todo can't break Entity.System.
- Position
- Below the diagonal: Entity.Modules.Todo uses a module listed above it, which is the healthy direction.
18→29 Entity.Modules.Todo uses Entity.Modules.Issues part of a loop✕
- Connections
- 1 pair of types, where a type in Entity.Modules.Todo uses a type in Entity.Modules.Issues.
- The types involved
App.Entity.Modules.Todo.MyTodo→App.Entity.Modules.Issues.MyIssue
- Direction
- Entity.Modules.Todo uses Entity.Modules.Issues, so a change to Entity.Modules.Issues can break Entity.Modules.Todo, while a change to Entity.Modules.Todo can't break Entity.Modules.Issues.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→8 Repository uses Entity✕
- Connections
- 3 pairs of types, where a type in Repository uses a type in Entity.
- The types involved
App.Repository.FilesTagsRepository→App.Entity.FilesTagsApp.Repository.SettingRepository→App.Entity.SettingApp.Repository.UserRepository→App.Entity.User
- Direction
- Repository uses Entity, so a change to Entity can break Repository, while a change to Repository can't break Entity.
- Position
- Below the diagonal: Repository uses a module listed above it, which is the healthy direction.
20→10 Repository.Modules.Payments uses Entity.Modules.Payments✕
- Connections
- 3 pairs of types, where a type in Repository.Modules.Payments uses a type in Entity.Modules.Payments.
- The types involved
App.Repository.Modules.Payments.MyPaymentsMonthlyRepository→App.Entity.Modules.Payments.MyPaymentsMonthlyApp.Repository.Modules.Payments.MyPaymentsOwedRepository→App.Entity.Modules.Payments.MyPaymentsOwedApp.Repository.Modules.Payments.MyPaymentsSettingsRepository→App.Entity.Modules.Payments.MyPaymentsSettings
- Direction
- Repository.Modules.Payments uses Entity.Modules.Payments, so a change to Entity.Modules.Payments can break Repository.Modules.Payments, while a change to Repository.Modules.Payments can't break Entity.Modules.Payments.
- Position
- Below the diagonal: Repository.Modules.Payments uses a module listed above it, which is the healthy direction.
21→11 Repository.Modules.Schedules uses Entity.Modules.Schedules✕
- Connections
- 1 pair of types, where a type in Repository.Modules.Schedules uses a type in Entity.Modules.Schedules.
- The types involved
App.Repository.Modules.Schedules.MyScheduleReminderRepository→App.Entity.Modules.Schedules.MyScheduleReminder
- Direction
- Repository.Modules.Schedules uses Entity.Modules.Schedules, so a change to Entity.Modules.Schedules can break Repository.Modules.Schedules, while a change to Repository.Modules.Schedules can't break Entity.Modules.Schedules.
- Position
- Below the diagonal: Repository.Modules.Schedules uses a module listed above it, which is the healthy direction.
22→1 Services.Validation uses DTO✕
- Connections
- 2 pairs of types, where a type in Services.Validation uses a type in DTO.
- The types involved
App.Services.Validation.ConstraintValidationService→App.DTO.ValidationResultDtoApp.Services.Validation.EntityValidatorService→App.DTO.ValidationResultDto
- Direction
- Services.Validation uses DTO, so a change to DTO can break Services.Validation, while a change to Services.Validation can't break DTO.
- Position
- Below the diagonal: Services.Validation uses a module listed above it, which is the healthy direction.
22→2 Services.Validation uses Entity.Interfaces✕
- Connections
- 1 pair of types, where a type in Services.Validation uses a type in Entity.Interfaces.
- The types involved
App.Services.Validation.EntityValidatorService→App.Entity.Interfaces.ValidateEntityInterface
- Direction
- Services.Validation uses Entity.Interfaces, so a change to Entity.Interfaces can break Services.Validation, while a change to Services.Validation can't break Entity.Interfaces.
- Position
- Below the diagonal: Services.Validation uses a module listed above it, which is the healthy direction.
22→16 Services.Validation uses Services.Validation.Validators✕
- Connections
- 1 pair of types, where a type in Services.Validation uses a type in Services.Validation.Validators.
- The types involved
App.Services.Validation.EntityValidatorService→App.Services.Validation.Validators.AbstractValidator
- Direction
- Services.Validation uses Services.Validation.Validators, so a change to Services.Validation.Validators can break Services.Validation, while a change to Services.Validation can't break Services.Validation.Validators.
- Position
- Below the diagonal: Services.Validation uses a module listed above it, which is the healthy direction.
23→3 Action.Modules.Calendar uses Response.Base✕
- Connections
- 1 pair of types, where a type in Action.Modules.Calendar uses a type in Response.Base.
- The types involved
App.Action.Modules.Calendar.SchedulesAction→App.Response.Base.BaseResponse
- Direction
- Action.Modules.Calendar uses Response.Base, so a change to Response.Base can break Action.Modules.Calendar, while a change to Action.Modules.Calendar can't break Response.Base.
- Position
- Below the diagonal: Action.Modules.Calendar uses a module listed above it, which is the healthy direction.
23→11 Action.Modules.Calendar uses Entity.Modules.Schedules✕
- Connections
- 1 pair of types, where a type in Action.Modules.Calendar uses a type in Entity.Modules.Schedules.
- The types involved
App.Action.Modules.Calendar.SchedulesAction→App.Entity.Modules.Schedules.MySchedule
- Direction
- Action.Modules.Calendar uses Entity.Modules.Schedules, so a change to Entity.Modules.Schedules can break Action.Modules.Calendar, while a change to Action.Modules.Calendar can't break Entity.Modules.Schedules.
- Position
- Below the diagonal: Action.Modules.Calendar uses a module listed above it, which is the healthy direction.
23→21 Action.Modules.Calendar uses Repository.Modules.Schedules✕
- Connections
- 1 pair of types, where a type in Action.Modules.Calendar uses a type in Repository.Modules.Schedules.
- The types involved
App.Action.Modules.Calendar.SchedulesAction→App.Repository.Modules.Schedules.MyScheduleReminderRepository
- Direction
- Action.Modules.Calendar uses Repository.Modules.Schedules, so a change to Repository.Modules.Schedules can break Action.Modules.Calendar, while a change to Action.Modules.Calendar can't break Repository.Modules.Schedules.
- Position
- Below the diagonal: Action.Modules.Calendar uses a module listed above it, which is the healthy direction.
24→3 Action.Modules.Job uses Response.Base✕
- Connections
- 2 pairs of types, where a type in Action.Modules.Job uses a type in Response.Base.
- The types involved
App.Action.Modules.Job.MyJobAfterhoursAction→App.Response.Base.BaseResponseApp.Action.Modules.Job.MyJobHolidaysAction→App.Response.Base.BaseResponse
- Direction
- Action.Modules.Job uses Response.Base, so a change to Response.Base can break Action.Modules.Job, while a change to Action.Modules.Job can't break Response.Base.
- Position
- Below the diagonal: Action.Modules.Job uses a module listed above it, which is the healthy direction.
24→22 Action.Modules.Job uses Services.Validation✕
- Connections
- 1 pair of types, where a type in Action.Modules.Job uses a type in Services.Validation.
- The types involved
App.Action.Modules.Job.MyJobHolidaysAction→App.Services.Validation.EntityValidatorService
- Direction
- Action.Modules.Job uses Services.Validation, so a change to Services.Validation can break Action.Modules.Job, while a change to Action.Modules.Job can't break Services.Validation.
- Position
- Below the diagonal: Action.Modules.Job uses a module listed above it, which is the healthy direction.
25→3 Action.Modules.Payments uses Response.Base✕
- Connections
- 4 pairs of types, where a type in Action.Modules.Payments uses a type in Response.Base.
- The types involved
App.Action.Modules.Payments.MyPaymentsIncomeAction→App.Response.Base.BaseResponseApp.Action.Modules.Payments.MyPaymentsMonthlyAction→App.Response.Base.BaseResponseApp.Action.Modules.Payments.MyPaymentsOwedAction→App.Response.Base.BaseResponseApp.Action.Modules.Payments.MyPaymentsProductsAction→App.Response.Base.BaseResponse
- Direction
- Action.Modules.Payments uses Response.Base, so a change to Response.Base can break Action.Modules.Payments, while a change to Action.Modules.Payments can't break Response.Base.
- Position
- Below the diagonal: Action.Modules.Payments uses a module listed above it, which is the healthy direction.
25→10 Action.Modules.Payments uses Entity.Modules.Payments✕
- Connections
- 4 pairs of types, where a type in Action.Modules.Payments uses a type in Entity.Modules.Payments.
- The types involved
App.Action.Modules.Payments.MyPaymentsIncomeAction→App.Entity.Modules.Payments.MyPaymentsIncomeApp.Action.Modules.Payments.MyPaymentsMonthlyAction→App.Entity.Modules.Payments.MyPaymentsMonthlyApp.Action.Modules.Payments.MyPaymentsOwedAction→App.Entity.Modules.Payments.MyPaymentsOwedApp.Action.Modules.Payments.MyPaymentsProductsAction→App.Entity.Modules.Payments.MyPaymentsProduct
- Direction
- Action.Modules.Payments uses Entity.Modules.Payments, so a change to Entity.Modules.Payments can break Action.Modules.Payments, while a change to Action.Modules.Payments can't break Entity.Modules.Payments.
- Position
- Below the diagonal: Action.Modules.Payments uses a module listed above it, which is the healthy direction.
25→20 Action.Modules.Payments uses Repository.Modules.Payments✕
- Connections
- 2 pairs of types, where a type in Action.Modules.Payments uses a type in Repository.Modules.Payments.
- The types involved
App.Action.Modules.Payments.MyPaymentsProductsAction→App.Repository.Modules.Payments.MyPaymentsProductRepositoryApp.Action.Modules.Payments.MyPaymentsProductsAction→App.Repository.Modules.Payments.MyPaymentsSettingsRepository
- Direction
- Action.Modules.Payments uses Repository.Modules.Payments, so a change to Repository.Modules.Payments can break Action.Modules.Payments, while a change to Action.Modules.Payments can't break Repository.Modules.Payments.
- Position
- Below the diagonal: Action.Modules.Payments uses a module listed above it, which is the healthy direction.
26→3 Action.Modules.Payments.Bills uses Response.Base✕
- Connections
- 2 pairs of types, where a type in Action.Modules.Payments.Bills uses a type in Response.Base.
- The types involved
App.Action.Modules.Payments.Bills.BillsAction→App.Response.Base.BaseResponseApp.Action.Modules.Payments.Bills.ItemsAction→App.Response.Base.BaseResponse
- Direction
- Action.Modules.Payments.Bills uses Response.Base, so a change to Response.Base can break Action.Modules.Payments.Bills, while a change to Action.Modules.Payments.Bills can't break Response.Base.
- Position
- Below the diagonal: Action.Modules.Payments.Bills uses a module listed above it, which is the healthy direction.
26→10 Action.Modules.Payments.Bills uses Entity.Modules.Payments✕
- Connections
- 2 pairs of types, where a type in Action.Modules.Payments.Bills uses a type in Entity.Modules.Payments.
- The types involved
App.Action.Modules.Payments.Bills.BillsAction→App.Entity.Modules.Payments.MyPaymentsBillsApp.Action.Modules.Payments.Bills.ItemsAction→App.Entity.Modules.Payments.MyPaymentsBillsItems
- Direction
- Action.Modules.Payments.Bills uses Entity.Modules.Payments, so a change to Entity.Modules.Payments can break Action.Modules.Payments.Bills, while a change to Action.Modules.Payments.Bills can't break Entity.Modules.Payments.
- Position
- Below the diagonal: Action.Modules.Payments.Bills uses a module listed above it, which is the healthy direction.
26→20 Action.Modules.Payments.Bills uses Repository.Modules.Payments✕
- Connections
- 1 pair of types, where a type in Action.Modules.Payments.Bills uses a type in Repository.Modules.Payments.
- The types involved
App.Action.Modules.Payments.Bills.BillsAction→App.Repository.Modules.Payments.MyPaymentsBillsRepository
- Direction
- Action.Modules.Payments.Bills uses Repository.Modules.Payments, so a change to Repository.Modules.Payments can break Action.Modules.Payments.Bills, while a change to Action.Modules.Payments.Bills can't break Repository.Modules.Payments.
- Position
- Below the diagonal: Action.Modules.Payments.Bills uses a module listed above it, which is the healthy direction.
27→3 Action.Modules.Payments.Settings uses Response.Base✕
- Connections
- 2 pairs of types, where a type in Action.Modules.Payments.Settings uses a type in Response.Base.
- The types involved
App.Action.Modules.Payments.Settings.PaymentTypeAction→App.Response.Base.BaseResponseApp.Action.Modules.Payments.Settings.RecurringPaymentAction→App.Response.Base.BaseResponse
- Direction
- Action.Modules.Payments.Settings uses Response.Base, so a change to Response.Base can break Action.Modules.Payments.Settings, while a change to Action.Modules.Payments.Settings can't break Response.Base.
- Position
- Below the diagonal: Action.Modules.Payments.Settings uses a module listed above it, which is the healthy direction.
27→10 Action.Modules.Payments.Settings uses Entity.Modules.Payments✕
- Connections
- 2 pairs of types, where a type in Action.Modules.Payments.Settings uses a type in Entity.Modules.Payments.
- The types involved
App.Action.Modules.Payments.Settings.PaymentTypeAction→App.Entity.Modules.Payments.MyPaymentsSettingsApp.Action.Modules.Payments.Settings.RecurringPaymentAction→App.Entity.Modules.Payments.MyRecurringPaymentMonthly
- Direction
- Action.Modules.Payments.Settings uses Entity.Modules.Payments, so a change to Entity.Modules.Payments can break Action.Modules.Payments.Settings, while a change to Action.Modules.Payments.Settings can't break Entity.Modules.Payments.
- Position
- Below the diagonal: Action.Modules.Payments.Settings uses a module listed above it, which is the healthy direction.
27→20 Action.Modules.Payments.Settings uses Repository.Modules.Payments✕
- Connections
- 2 pairs of types, where a type in Action.Modules.Payments.Settings uses a type in Repository.Modules.Payments.
- The types involved
App.Action.Modules.Payments.Settings.CurrencyMultiplierAction→App.Repository.Modules.Payments.MyPaymentsSettingsRepositoryApp.Action.Modules.Payments.Settings.RecurringPaymentAction→App.Repository.Modules.Payments.MyRecurringPaymentMonthlyRepository
- Direction
- Action.Modules.Payments.Settings uses Repository.Modules.Payments, so a change to Repository.Modules.Payments can break Action.Modules.Payments.Settings, while a change to Action.Modules.Payments.Settings can't break Repository.Modules.Payments.
- Position
- Below the diagonal: Action.Modules.Payments.Settings uses a module listed above it, which is the healthy direction.
27→22 Action.Modules.Payments.Settings uses Services.Validation✕
- Connections
- 1 pair of types, where a type in Action.Modules.Payments.Settings uses a type in Services.Validation.
- The types involved
App.Action.Modules.Payments.Settings.RecurringPaymentAction→App.Services.Validation.EntityValidatorService
- Direction
- Action.Modules.Payments.Settings uses Services.Validation, so a change to Services.Validation can break Action.Modules.Payments.Settings, while a change to Action.Modules.Payments.Settings can't break Services.Validation.
- Position
- Below the diagonal: Action.Modules.Payments.Settings uses a module listed above it, which is the healthy direction.
28→10 Command.Crons uses Entity.Modules.Payments✕
- Connections
- 1 pair of types, where a type in Command.Crons uses a type in Entity.Modules.Payments.
- The types involved
App.Command.Crons.CronAddRecurringPaymentsCommand→App.Entity.Modules.Payments.MyRecurringPaymentMonthly
- Direction
- Command.Crons uses Entity.Modules.Payments, so a change to Entity.Modules.Payments can break Command.Crons, while a change to Command.Crons can't break Entity.Modules.Payments.
- Position
- Below the diagonal: Command.Crons uses a module listed above it, which is the healthy direction.
28→15 Command.Crons uses Services.External✕
- Connections
- 1 pair of types, where a type in Command.Crons uses a type in Services.External.
- The types involved
App.Command.Crons.CronTransferSchedulesToNotifierProxyLoggerCommand→App.Services.External.NotifierProxyLoggerService
- Direction
- Command.Crons uses Services.External, so a change to Services.External can break Command.Crons, while a change to Command.Crons can't break Services.External.
- Position
- Below the diagonal: Command.Crons uses a module listed above it, which is the healthy direction.
28→20 Command.Crons uses Repository.Modules.Payments✕
- Connections
- 2 pairs of types, where a type in Command.Crons uses a type in Repository.Modules.Payments.
- The types involved
App.Command.Crons.CronAddRecurringPaymentsCommand→App.Repository.Modules.Payments.MyPaymentsMonthlyRepositoryApp.Command.Crons.CronAddRecurringPaymentsCommand→App.Repository.Modules.Payments.MyRecurringPaymentMonthlyRepository
- Direction
- Command.Crons uses Repository.Modules.Payments, so a change to Repository.Modules.Payments can break Command.Crons, while a change to Command.Crons can't break Repository.Modules.Payments.
- Position
- Below the diagonal: Command.Crons uses a module listed above it, which is the healthy direction.
28→21 Command.Crons uses Repository.Modules.Schedules✕
- Connections
- 2 pairs of types, where a type in Command.Crons uses a type in Repository.Modules.Schedules.
- The types involved
App.Command.Crons.CronTransferSchedulesToNotifierProxyLoggerCommand→App.Repository.Modules.Schedules.MyScheduleReminderRepositoryApp.Command.Crons.CronTransferSchedulesToNotifierProxyLoggerCommand→App.Repository.Modules.Schedules.MyScheduleRepository
- Direction
- Command.Crons uses Repository.Modules.Schedules, so a change to Repository.Modules.Schedules can break Command.Crons, while a change to Command.Crons can't break Repository.Modules.Schedules.
- Position
- Below the diagonal: Command.Crons uses a module listed above it, which is the healthy direction.
29→2 Entity.Modules.Issues uses Entity.Interfaces✕
- Connections
- 6 pairs of types, where a type in Entity.Modules.Issues uses a type in Entity.Interfaces.
- The types involved
App.Entity.Modules.Issues.MyIssue→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Issues.MyIssue→App.Entity.Interfaces.SoftDeletableEntityInterfaceApp.Entity.Modules.Issues.MyIssueContact→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Issues.MyIssueContact→App.Entity.Interfaces.SoftDeletableEntityInterfaceApp.Entity.Modules.Issues.MyIssueProgress→App.Entity.Interfaces.EntityInterfaceApp.Entity.Modules.Issues.MyIssueProgress→App.Entity.Interfaces.SoftDeletableEntityInterface
- Direction
- Entity.Modules.Issues uses Entity.Interfaces, so a change to Entity.Interfaces can break Entity.Modules.Issues, while a change to Entity.Modules.Issues can't break Entity.Interfaces.
- Position
- Below the diagonal: Entity.Modules.Issues uses a module listed above it, which is the healthy direction.
29→18 Entity.Modules.Issues uses Entity.Modules.Todo✕
- Connections
- 1 pair of types, where a type in Entity.Modules.Issues uses a type in Entity.Modules.Todo.
- The types involved
App.Entity.Modules.Issues.MyIssue→App.Entity.Modules.Todo.MyTodo
- Direction
- Entity.Modules.Issues uses Entity.Modules.Todo, so a change to Entity.Modules.Todo can break Entity.Modules.Issues, while a change to Entity.Modules.Issues can't break Entity.Modules.Todo.
- Position
- Below the diagonal: Entity.Modules.Issues uses a module listed above it, which is the healthy direction.
30→8 Services.Settings uses Entity✕
- Connections
- 2 pairs of types, where a type in Services.Settings uses a type in Entity.
- The types involved
App.Services.Settings.SettingsLoader→App.Entity.SettingApp.Services.Settings.SettingsService→App.Entity.Setting
- Direction
- Services.Settings uses Entity, so a change to Entity can break Services.Settings, while a change to Services.Settings can't break Entity.
- Position
- Below the diagonal: Services.Settings uses a module listed above it, which is the healthy direction.
30→19 Services.Settings uses Repository✕
- Connections
- 2 pairs of types, where a type in Services.Settings uses a type in Repository.
- The types involved
App.Services.Settings.SettingsLoader→App.Repository.SettingRepositoryApp.Services.Settings.SettingsLockModuleService→App.Repository.SettingRepository
- Direction
- Services.Settings uses Repository, so a change to Repository can break Services.Settings, while a change to Services.Settings can't break Repository.
- Position
- Below the diagonal: Services.Settings uses a module listed above it, which is the healthy direction.
31→29 Action.Modules.Issues uses Entity.Modules.Issues✕
- Connections
- 5 pairs of types, where a type in Action.Modules.Issues uses a type in Entity.Modules.Issues.
- The types involved
App.Action.Modules.Issues.MyIssuesAction→App.Entity.Modules.Issues.MyIssueApp.Action.Modules.Issues.MyIssuesContactAction→App.Entity.Modules.Issues.MyIssueApp.Action.Modules.Issues.MyIssuesContactAction→App.Entity.Modules.Issues.MyIssueContactApp.Action.Modules.Issues.MyIssuesProgressAction→App.Entity.Modules.Issues.MyIssueApp.Action.Modules.Issues.MyIssuesProgressAction→App.Entity.Modules.Issues.MyIssueProgress
- Direction
- Action.Modules.Issues uses Entity.Modules.Issues, so a change to Entity.Modules.Issues can break Action.Modules.Issues, while a change to Action.Modules.Issues can't break Entity.Modules.Issues.
- Position
- Below the diagonal: Action.Modules.Issues uses a module listed above it, which is the healthy direction.
32→3 Action.Modules.System.Settings uses Response.Base✕
- Connections
- 1 pair of types, where a type in Action.Modules.System.Settings uses a type in Response.Base.
- The types involved
App.Action.Modules.System.Settings.FinancesCurrenciesAction→App.Response.Base.BaseResponse
- Direction
- Action.Modules.System.Settings uses Response.Base, so a change to Response.Base can break Action.Modules.System.Settings, while a change to Action.Modules.System.Settings can't break Response.Base.
- Position
- Below the diagonal: Action.Modules.System.Settings uses a module listed above it, which is the healthy direction.
32→30 Action.Modules.System.Settings uses Services.Settings✕
- Connections
- 3 pairs of types, where a type in Action.Modules.System.Settings uses a type in Services.Settings.
- The types involved
App.Action.Modules.System.Settings.FinancesCurrenciesAction→App.Services.Settings.SettingsFinancesServiceApp.Action.Modules.System.Settings.FinancesCurrenciesAction→App.Services.Settings.SettingsLoaderApp.Action.Modules.System.Settings.FinancesCurrenciesAction→App.Services.Settings.SettingsSaver
- Direction
- Action.Modules.System.Settings uses Services.Settings, so a change to Services.Settings can break Action.Modules.System.Settings, while a change to Action.Modules.System.Settings can't break Services.Settings.
- Position
- Below the diagonal: Action.Modules.System.Settings uses a module listed above it, which is the healthy direction.
33→1 Command.Module.Schedules uses DTO✕
- Connections
- 1 pair of types, where a type in Command.Module.Schedules uses a type in DTO.
- The types involved
App.Command.Module.Schedules.SendRemindersCommand→App.DTO.NotificationDto
- Direction
- Command.Module.Schedules uses DTO, so a change to DTO can break Command.Module.Schedules, while a change to Command.Module.Schedules can't break DTO.
- Position
- Below the diagonal: Command.Module.Schedules uses a module listed above it, which is the healthy direction.
33→15 Command.Module.Schedules uses Services.External✕
- Connections
- 1 pair of types, where a type in Command.Module.Schedules uses a type in Services.External.
- The types involved
App.Command.Module.Schedules.SendRemindersCommand→App.Services.External.DiscordService
- Direction
- Command.Module.Schedules uses Services.External, so a change to Services.External can break Command.Module.Schedules, while a change to Command.Module.Schedules can't break Services.External.
- Position
- Below the diagonal: Command.Module.Schedules uses a module listed above it, which is the healthy direction.
33→21 Command.Module.Schedules uses Repository.Modules.Schedules✕
- Connections
- 1 pair of types, where a type in Command.Module.Schedules uses a type in Repository.Modules.Schedules.
- The types involved
App.Command.Module.Schedules.SendRemindersCommand→App.Repository.Modules.Schedules.MyScheduleRepository
- Direction
- Command.Module.Schedules uses Repository.Modules.Schedules, so a change to Repository.Modules.Schedules can break Command.Module.Schedules, while a change to Command.Module.Schedules can't break Repository.Modules.Schedules.
- Position
- Below the diagonal: Command.Module.Schedules uses a module listed above it, which is the healthy direction.
33→30 Command.Module.Schedules uses Services.Settings✕
- Connections
- 1 pair of types, where a type in Command.Module.Schedules uses a type in Services.Settings.
- The types involved
App.Command.Module.Schedules.SendRemindersCommand→App.Services.Settings.SettingsLoader
- Direction
- Command.Module.Schedules uses Services.Settings, so a change to Services.Settings can break Command.Module.Schedules, while a change to Command.Module.Schedules can't break Services.Settings.
- Position
- Below the diagonal: Command.Module.Schedules uses a module listed above it, which is the healthy direction.
34→8 Services.Security uses Entity✕
- Connections
- 1 pair of types, where a type in Services.Security uses a type in Entity.
- The types involved
App.Services.Security.JwtAuthenticationService→App.Entity.User
- Direction
- Services.Security uses Entity, so a change to Entity can break Services.Security, while a change to Services.Security can't break Entity.
- Position
- Below the diagonal: Services.Security uses a module listed above it, which is the healthy direction.
34→19 Services.Security uses Repository✕
- Connections
- 1 pair of types, where a type in Services.Security uses a type in Repository.
- The types involved
App.Services.Security.JwtAuthenticationService→App.Repository.UserRepository
- Direction
- Services.Security uses Repository, so a change to Repository can break Services.Security, while a change to Services.Security can't break Repository.
- Position
- Below the diagonal: Services.Security uses a module listed above it, which is the healthy direction.
34→30 Services.Security uses Services.Settings✕
- Connections
- 1 pair of types, where a type in Services.Security uses a type in Services.Settings.
- The types involved
App.Services.Security.JwtUserRightsHandler→App.Services.Settings.SettingsLockModuleService
- Direction
- Services.Security uses Services.Settings, so a change to Services.Settings can break Services.Security, while a change to Services.Security can't break Services.Settings.
- Position
- Below the diagonal: Services.Security uses a module listed above it, which is the healthy direction.
35→5 Listeners.Response uses Services.Routing✕
- Connections
- 1 pair of types, where a type in Listeners.Response uses a type in Services.Routing.
- The types involved
App.Listeners.Response.JwtTokenResponseListener→App.Services.Routing.UrlMatcherService
- Direction
- Listeners.Response uses Services.Routing, so a change to Services.Routing can break Listeners.Response, while a change to Listeners.Response can't break Services.Routing.
- Position
- Below the diagonal: Listeners.Response uses a module listed above it, which is the healthy direction.
35→14 Listeners.Response uses Services.Attribute✕
- Connections
- 1 pair of types, where a type in Listeners.Response uses a type in Services.Attribute.
- The types involved
App.Listeners.Response.JwtTokenResponseListener→App.Services.Attribute.AttributeReaderService
- Direction
- Listeners.Response uses Services.Attribute, so a change to Services.Attribute can break Listeners.Response, while a change to Listeners.Response can't break Services.Attribute.
- Position
- Below the diagonal: Listeners.Response uses a module listed above it, which is the healthy direction.
35→34 Listeners.Response uses Services.Security✕
- Connections
- 1 pair of types, where a type in Listeners.Response uses a type in Services.Security.
- The types involved
App.Listeners.Response.JwtTokenResponseListener→App.Services.Security.JwtAuthenticationService
- Direction
- Listeners.Response uses Services.Security, so a change to Services.Security can break Listeners.Response, while a change to Listeners.Response can't break Services.Security.
- Position
- Below the diagonal: Listeners.Response uses a module listed above it, which is the healthy direction.
36→1 Services.System uses DTO✕
- Connections
- 1 pair of types, where a type in Services.System uses a type in DTO.
- The types involved
App.Services.System.EnvReader→App.DTO.DatabaseCredentialsDTO
- Direction
- Services.System uses DTO, so a change to DTO can break Services.System, while a change to Services.System can't break DTO.
- Position
- Below the diagonal: Services.System uses a module listed above it, which is the healthy direction.
36→8 Services.System uses Entity✕
- Connections
- 1 pair of types, where a type in Services.System uses a type in Entity.
- The types involved
App.Services.System.SecurityService→App.Entity.User
- Direction
- Services.System uses Entity, so a change to Entity can break Services.System, while a change to Services.System can't break Entity.
- Position
- Below the diagonal: Services.System uses a module listed above it, which is the healthy direction.
36→12 Services.System uses Entity.System✕
- Connections
- 1 pair of types, where a type in Services.System uses a type in Entity.System.
- The types involved
App.Services.System.LockedResourceService→App.Entity.System.LockedResource
- Direction
- Services.System uses Entity.System, so a change to Entity.System can break Services.System, while a change to Services.System can't break Entity.System.
- Position
- Below the diagonal: Services.System uses a module listed above it, which is the healthy direction.
36→30 Services.System uses Services.Settings✕
- Connections
- 1 pair of types, where a type in Services.System uses a type in Services.Settings.
- The types involved
App.Services.System.LockedResourceService→App.Services.Settings.SettingsLockModuleService
- Direction
- Services.System uses Services.Settings, so a change to Services.Settings can break Services.System, while a change to Services.System can't break Services.Settings.
- Position
- Below the diagonal: Services.System uses a module listed above it, which is the healthy direction.
36→34 Services.System uses Services.Security✕
- Connections
- 1 pair of types, where a type in Services.System uses a type in Services.Security.
- The types involved
App.Services.System.LockedResourceService→App.Services.Security.JwtAuthenticationService
- Direction
- Services.System uses Services.Security, so a change to Services.Security can break Services.System, while a change to Services.System can't break Services.Security.
- Position
- Below the diagonal: Services.System uses a module listed above it, which is the healthy direction.
37→4 Action.Modules.Dashboard uses Services.Module.Todo✕
- Connections
- 1 pair of types, where a type in Action.Modules.Dashboard uses a type in Services.Module.Todo.
- The types involved
App.Action.Modules.Dashboard.DashboardAction→App.Services.Module.Todo.MyTodoService
- Direction
- Action.Modules.Dashboard uses Services.Module.Todo, so a change to Services.Module.Todo can break Action.Modules.Dashboard, while a change to Action.Modules.Dashboard can't break Services.Module.Todo.
- Position
- Below the diagonal: Action.Modules.Dashboard uses a module listed above it, which is the healthy direction.
37→30 Action.Modules.Dashboard uses Services.Settings✕
- Connections
- 1 pair of types, where a type in Action.Modules.Dashboard uses a type in Services.Settings.
- The types involved
App.Action.Modules.Dashboard.DashboardAction→App.Services.Settings.SettingsLockModuleService
- Direction
- Action.Modules.Dashboard uses Services.Settings, so a change to Services.Settings can break Action.Modules.Dashboard, while a change to Action.Modules.Dashboard can't break Services.Settings.
- Position
- Below the diagonal: Action.Modules.Dashboard uses a module listed above it, which is the healthy direction.
37→36 Action.Modules.Dashboard uses Services.System✕
- Connections
- 1 pair of types, where a type in Action.Modules.Dashboard uses a type in Services.System.
- The types involved
App.Action.Modules.Dashboard.DashboardAction→App.Services.System.LockedResourceService
- Direction
- Action.Modules.Dashboard uses Services.System, so a change to Services.System can break Action.Modules.Dashboard, while a change to Action.Modules.Dashboard can't break Services.System.
- Position
- Below the diagonal: Action.Modules.Dashboard uses a module listed above it, which is the healthy direction.
38→3 Action.Modules.Notes uses Response.Base✕
- Connections
- 1 pair of types, where a type in Action.Modules.Notes uses a type in Response.Base.
- The types involved
App.Action.Modules.Notes.MyNotesCategoriesAction→App.Response.Base.BaseResponse
- Direction
- Action.Modules.Notes uses Response.Base, so a change to Response.Base can break Action.Modules.Notes, while a change to Action.Modules.Notes can't break Response.Base.
- Position
- Below the diagonal: Action.Modules.Notes uses a module listed above it, which is the healthy direction.
38→36 Action.Modules.Notes uses Services.System✕
- Connections
- 1 pair of types, where a type in Action.Modules.Notes uses a type in Services.System.
- The types involved
App.Action.Modules.Notes.MyNotesAction→App.Services.System.LockedResourceService
- Direction
- Action.Modules.Notes uses Services.System, so a change to Services.System can break Action.Modules.Notes, while a change to Action.Modules.Notes can't break Services.System.
- Position
- Below the diagonal: Action.Modules.Notes uses a module listed above it, which is the healthy direction.
39→5 Listeners.Request.Kernel uses Services.Routing✕
- Connections
- 1 pair of types, where a type in Listeners.Request.Kernel uses a type in Services.Routing.
- The types involved
App.Listeners.Request.Kernel.KernelRequestResourceLock→App.Services.Routing.UrlMatcherService
- Direction
- Listeners.Request.Kernel uses Services.Routing, so a change to Services.Routing can break Listeners.Request.Kernel, while a change to Listeners.Request.Kernel can't break Services.Routing.
- Position
- Below the diagonal: Listeners.Request.Kernel uses a module listed above it, which is the healthy direction.
39→14 Listeners.Request.Kernel uses Services.Attribute✕
- Connections
- 1 pair of types, where a type in Listeners.Request.Kernel uses a type in Services.Attribute.
- The types involved
App.Listeners.Request.Kernel.KernelRequestResourceLock→App.Services.Attribute.AttributeReaderService
- Direction
- Listeners.Request.Kernel uses Services.Attribute, so a change to Services.Attribute can break Listeners.Request.Kernel, while a change to Listeners.Request.Kernel can't break Services.Attribute.
- Position
- Below the diagonal: Listeners.Request.Kernel uses a module listed above it, which is the healthy direction.
39→36 Listeners.Request.Kernel uses Services.System✕
- Connections
- 1 pair of types, where a type in Listeners.Request.Kernel uses a type in Services.System.
- The types involved
App.Listeners.Request.Kernel.KernelRequestResourceLock→App.Services.System.LockedResourceService
- Direction
- Listeners.Request.Kernel uses Services.System, so a change to Services.System can break Listeners.Request.Kernel, while a change to Listeners.Request.Kernel can't break Services.System.
- Position
- Below the diagonal: Listeners.Request.Kernel uses a module listed above it, which is the healthy direction.
40→3 Services.Module.Storage uses Response.Base✕
- Connections
- 3 pairs of types, where a type in Services.Module.Storage uses a type in Response.Base.
- The types involved
App.Services.Module.Storage.StorageFileService→App.Response.Base.BaseResponseApp.Services.Module.Storage.StorageFolderService→App.Response.Base.BaseResponseApp.Services.Module.Storage.StorageService→App.Response.Base.BaseResponse
- Direction
- Services.Module.Storage uses Response.Base, so a change to Response.Base can break Services.Module.Storage, while a change to Services.Module.Storage can't break Response.Base.
- Position
- Below the diagonal: Services.Module.Storage uses a module listed above it, which is the healthy direction.
40→13 Services.Module.Storage uses Repository.Modules.Storage✕
- Connections
- 3 pairs of types, where a type in Services.Module.Storage uses a type in Repository.Modules.Storage.
- The types involved
App.Services.Module.Storage.StorageFileService→App.Repository.Modules.Storage.StorageFileRepositoryApp.Services.Module.Storage.StorageFolderService→App.Repository.Modules.Storage.StorageFileRepositoryApp.Services.Module.Storage.StorageService→App.Repository.Modules.Storage.StorageFileRepository
- Direction
- Services.Module.Storage uses Repository.Modules.Storage, so a change to Repository.Modules.Storage can break Services.Module.Storage, while a change to Services.Module.Storage can't break Repository.Modules.Storage.
- Position
- Below the diagonal: Services.Module.Storage uses a module listed above it, which is the healthy direction.
40→36 Services.Module.Storage uses Services.System✕
- Connections
- 1 pair of types, where a type in Services.Module.Storage uses a type in Services.System.
- The types involved
App.Services.Module.Storage.StorageService→App.Services.System.LockedResourceService
- Direction
- Services.Module.Storage uses Services.System, so a change to Services.System can break Services.Module.Storage, while a change to Services.Module.Storage can't break Services.System.
- Position
- Below the diagonal: Services.Module.Storage 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 32 | High / Critical |
| A07:2025 — Authentication Failures | 14 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED; Resolve the 2 Abandoned package finding(s) in Dependency Hygiene.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +11.6 pts | Low | REDACTED Scanning |
| Resolve the 2 Abandoned package finding(s) in Dependency Hygiene. | +4.5 pts | Low | Dependency Hygiene |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +4.1 pts | Low | Documentation Quality |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json. | +4.1 pts | Low | ADR Quality |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +16.5 pts | High | Code Coverage |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +4.0 pts | Medium | CI/CD gates |
| 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. | +3.4 pts | Medium | Architecture documentation |
| Resolve the 9 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED, REDACTED. | +1.0 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.1 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/Services/ResponseService.php | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/Services/Database/DatabaseExporter.php | 7.4 | Mixed | Code Duplication: Edited copy of a member (20 corresponding lines) |
| src/Listeners/Response/JwtTokenResponseListener.php | 7.8 | Mixed | Cyclomatic Complexity: JwtTokenResponseListener.onResponse (cyclomatic 16) |
| src/Migrations/Version20190717144649.php | 7.8 | Mixed | Code Duplication: Members sharing a duplicated core (7 members, 50+ identical tokens) |
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 53 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 53 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, 127 of 151 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (11 contributor(s) across 1413 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 10 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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 naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- 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. `(repository root)` (27081 LoC, 363 module-visible types across 160 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- 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. `src/Action/File/UploadedFileAction.php`, `src/Action/Modules/Achievements/AchievementAction.php`, `src/Action/Modules/Calendar/SchedulesAction.php`, `src/Action/Modules/Calendar/Settings/ManageCalendarsAction.php`, `src/Action/Modules/Contacts/ContactTypesAction.php`, … (+104 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.
- D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 34 commits in the last 90 days, yet 112 of 161 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- 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 Symfony DependencyInjection, 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.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — 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. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- 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, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's PHP 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, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's PHP 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.
- 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, Kotlin, Java and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java 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.
- 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, Kotlin, Rust and Java source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust or Java 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, Java, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin 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.
- 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.
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.
- 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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was JwtTokenResponseListener.onResponse at 16. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ZipArchivizer.getHumanReadableStatus at 25 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Services/Files/Archivizer/ZipArchivizer.php (ZipArchivizer.getHumanReadableStatus at 25). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with JwtTokenResponseListener.onResponse (cyclomatic 16). — Refactoring it lifts Cyclomatic Complexity from 9.9 to about 10.0/10.
D2 · Cognitive Complexity
3 method(s) exceeded the cognitive complexity threshold of 15; the worst was JwtTokenResponseListener.onResponse at 17.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with JwtTokenResponseListener.onResponse (cognitive 17), MyIssuesService.getIssuesData (cognitive 17), SearchAction.searchInStorage (cognitive 16). — 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 3 together lifts Cognitive Complexity from 9.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
2 god class(es) detected.
What to do
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with BaseResponse.php, User.php. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
23 duplicated block group(s) detected. 5.7 % of the production lines (1,533 of 27,096) are in a reported copy. A further 28 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 4 of the 51 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 4 Edited copy of a member (20 corresponding lines) finding(s) in Code Duplication — start with DatabaseExporter.php (2), MyPaymentsMonthlyRepository.php, MyNotesSettingsFixtures.php. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with MyIssuesAction.php, WidgetsVisibilityAction.php, MyIssues.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (18 corresponding lines) finding(s) in Code Duplication — start with MyIssuesContactAction.php, MyTodoFixtures.php. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
19 production modules (source-import), 1 dependency cycle(s), 1 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 5 module(s) off the main sequence, with abstractness counted on 16 of the 19 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 5 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 Circular dependency finding(s) in Coupling — start with UploadedFileAction.php. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Unstable project src/Action finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
2 of 116 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with MyTodo.php, MyNotesCategories.php. — One of this dimension's main actionable groups (2 warning-level).
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).
D12 · Dependency Hygiene
0 outdated, 2 abandoned direct Composer dependencies. 44 of 45 direct production requirements were graded against Packagist (1 not published there, which is what a private Satis repository looks like, 0 with no release resolution). PLATFORM requirements (php, ext-*, lib-*) are deliberately not graded here: they name the runtime rather than a Packagist package, so there is no release for them to be behind — whether that runtime is still supported is a separate question with a separate remedy. Development requirements are excluded, because a consumer never installs them. A newer release is reported only where this repository's OWN constraint already admits it, so the remedy is `composer update` and never a manifest edit. Known CVEs in this dependency graph are D30's question. An ABANDONED package is a migration rather than an upgrade: it receives no further releases at all, including security releases.
What to do
- Resolve the 2 Abandoned package finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
D13 · REDACTED Scanning
1 secret(s) detected. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
What to do
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D14 · License Compliance
0 of 104 locked Composer package(s) use a banned license. Licences were read from this repository's REDACTED, which records the `license` each package declares, over every package in its production `packages` list, direct and transitive, at the locked version; the 55 package(s) under `packages-dev` are not installed for a consumer and are excluded.
D15 · Churn × Complexity Hotspots
Top hotspots: src/Listeners/Response/JwtTokenResponseListener.php (3×16=48)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with JwtTokenResponseListener.php. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
3 deducted task-comment markers across 27096 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 3 TodoComment finding(s) in Explicit Debt — start with ResponseService.php (2), ModulesService.php. — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 1 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
83 % of calls cross a namespace and 0 % go through an interface, but 20 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
12 finding(s): 0 critical, 12 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 9 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
semgrep found no security issues. semgrep hit a parse error in 109 file(s) — `src/Action/File/UploadedFileAction.php` (line 37, line 38, line 39, …), `src/Action/Modules/Achievements/AchievementAction.php` (line 24, line 25), `src/Action/Modules/Calendar/SchedulesAction.php` (line 29, line 30, line 31), `src/Action/Modules/Calendar/Settings/ManageCalendarsAction.php` (line 25, line 26), `src/Action/Modules/Contacts/ContactTypesAction.php` (line 33), … (+104 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
32 finding(s): 0 critical, 20 high, 9 medium, 3 low.
What to do
- Resolve the 20 High IaC finding(s) in IaC & Container Security — start with REDACTED (20). — One of this dimension's main actionable groups (20 issue-level).
- Resolve the 9 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 3 Low IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: MyNotesCategoriesRepository.php↔MyNotesRepository.php 60%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with MyNotesCategoriesRepository.php. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 45 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
- The projects src/Action → src/DTO → src/Services → src/Response → src/Action (one cycle inside a mutually-dependent group of 9 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — src/Action/File/UploadedFileAction.php:5
What to do
- Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
C1 · Data Protection
- No encryption usage (Laravel's Crypt facade or encrypt() helper, an Eloquent 'encrypted' cast, openssl_encrypt, libsodium's sodium_crypto_secretbox/aead, defuse/php-encryption, phpseclib, CipherSweet) was found, and this repository persists personal data in the model cited here — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore. — src/Entity/User.php:49
- No in-app HTTPS enforcement, but trusted proxies are configured (TrustProxies $proxies / trustProxies(at: …) / setTrustedProxies) — a reverse-proxy topology, where forcing HTTPS in the app would be wrong. Verify the reverse proxy enforces TLS. — public/index.php:28
What to do
- Encrypt sensitive data at rest (an Eloquent 'encrypted' cast or Crypt::encryptString, libsodium's sodium_crypto_secretbox, or CipherSweet for searchable fields) and manage keys in a vault (AWS KMS / Secrets Manager, GCP KMS / REDACTED Manager, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.).
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
- Name the access rules — Gate abilities and policy classes (Gate::define, a UserPolicy), spatie/laravel-permission roles and permissions, or a Symfony Voter — and consult them where access is checked ($this->authorize, a can: middleware, #[IsGranted]), so the rule set is reviewable and testable on its own.
DM1 · Aggregate boundaries
- `DoctorAppointment` references the aggregate root `Doctor` directly (via `doctor`) — hold its `DoctorId` instead.
- `DoctorAppointment` references the aggregate root `Illness` directly (via `illness`) — hold its `IllnessId` instead.
- `MyIssue` references the aggregate root `MyTodo` directly (via `todo`) — hold its `MyTodoId` instead.
- `ImportFilterRule` references the aggregate root `ImportProfile` directly (via `importProfile`) — hold its `ImportProfileId` instead.
- `StorageFile2Module` references the aggregate root `StorageFile` directly (via `storageFile`) — hold its `StorageFileId` instead.
What to do
- Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `StorageFile`'s public constructor takes `filePath`, `moduleName` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `StorageFile` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/Entity/Modules/Storage/StorageFile.php:25
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM4 · Rich vs anemic model
DM5 · Encapsulated state
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.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
- 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
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add phpstan or psalm (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: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
- `new Client(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — src/Services/External/DiscordService.php:20
What to do
- Give every client an explicit bound: `new Client(['timeout' => 10, 'connect_timeout' => 3])` for Guzzle (whose default is to wait forever), `CURLOPT_TIMEOUT`/`CURLOPT_CONNECTTIMEOUT` before `curl_exec`, `timeout`/`max_duration` on Symfony HttpClient (or `framework.http_client.default_options`), and a stream-context `timeout` or `connection_timeout` for `file_get_contents`/`SoapClient`. In Drupal, use the `http_client` service, which carries core's site-wide timeout, rather than `new Client()`. Add retries with back-off (Guzzle `Middleware::retry`, Symfony `RetryableHttpClient`, Laravel `->retry()`) around dependencies that fail.
P8 · Schema migrations
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `nginx.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — docker/nginx/nginx.conf:92
What to do
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `catch (\Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/Services/System/EnvReader.php:92
What to do
- Swallowed exception (caught, then discarded)
X4 · Structured logging
- `critical` at line 91 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->critical('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::critical('order moved', ['order_id' => $orderId])` with Laravel's facade. — src/Services/Shell/ShellAbstractService.php:91
- `warning` at line 68 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->warning('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::warning('order moved', ['order_id' => $orderId])` with Laravel's facade. — src/Services/Security/JwtUserRightsHandler.php:68
- `critical` at line 213 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->critical('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::critical('order moved', ['order_id' => $orderId])` with Laravel's facade. — src/Services/Module/Storage/StorageFolderService.php:213
- `critical` at line 219 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->critical('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::critical('order moved', ['order_id' => $orderId])` with Laravel's facade. — src/Services/Module/Storage/StorageFolderService.php:219
- `info` at line 93 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade. — src/Command/Crons/CronTransferSchedulesToNotifierProxyLoggerCommand.php:93
- `warning` at line 98 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->warning('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::warning('order moved', ['order_id' => $orderId])` with Laravel's facade. — src/Action/User/Setting/BaseDataAction.php:98
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
What to do
- Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 55.5 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 85.7 | Adequate — gated by D5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 48.3 | Weak — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 21.7 | Critical — gated by D8, P1, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 53.0 | Adequate — gated by D28, D31, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 84.6 | Strong | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, a change-history library on the models — spatie/laravel-activitylog's LogsActivity, owen-it/laravel-auditing's Auditable, venturecraft/revisionable, Gedmo Loggable — or an Eloquent model event, observer or Doctrine listener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 69 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.
- 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 — Not applicable: PHP builds its object graph per request and shares none of it between requests.
- 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
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c wget https://raw.githubusercontent.com/axllent/mailpit/develop/install.sh && chmod +x ./install.sh && sh ./install.sh;" did not complete successfully: exit code: 22; likely cause (the repository): a RUN step of the repository's REDACTED exited with code 22 (`/bin/sh -c wget https://raw.githubusercontent.com/axllent/mailpit/develop/install.sh && chmod +x ./install.sh && sh ./in…`): the build's own command failed, for example a compile or test error; runtime evidence skipped The cause is in the repository, not in our sandbox: a RUN step of the repository's REDACTED exited with code 22 (`/bin/sh -c wget https://raw.githubusercontent.com/axllent/mailpit/develop/install.sh && chmod +x ./install.sh && sh ./in…`): the build's own command failed, for example a compile or test error. Nothing here says the surface is inaccessible, only that it was never rendered.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- 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. Aggregate roots were found in only one source directory (Entity), which is a layered codebase, not two contexts. 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 .php, 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 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 109 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no 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
- DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, 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
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, 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.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- 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
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
- 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.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- 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.
Appendix A — Findings (grouped)
Critical — 42 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Aggregate holds a reference to another aggregate: DoctorAppointment.doctor
- Aggregate holds a reference to another aggregate: DoctorAppointment.illness
- Aggregate holds a reference to another aggregate: MyIssue.todo
- Aggregate holds a reference to another aggregate: ImportFilterRule.importProfile
- Aggregate holds a reference to another aggregate: StorageFile2Module.storageFile
- REDACTED
- REDACTED
- REDACTED
- Project dependency cycle src/Action/File/UploadedFileAction.php:5
- REDACTED
- REDACTED
- Circular dependency src/Action/File/UploadedFileAction.php:5
- No automated tests
Serious — 86 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Off the main sequence: src
- Off the main sequence: src/Attribute
- Off the main sequence: src/Doctrine
- Off the main sequence: src/Exception
- Off the main sequence: src/Traits
- Edited copy of a member (20 corresponding lines) src/Services/Database/DatabaseExporter.php:212
- Edited copy of a member (20 corresponding lines) src/Services/Database/DatabaseExporter.php:243
- Edited copy of a member (20 corresponding lines) src/Repository/Modules/Payments/MyPaymentsMonthlyRepository.php:52
- Edited copy of a member (20 corresponding lines) src/DataFixtures/Modules/Notes/MyNotesSettingsFixtures.php:32
- TodoComment src/Services/ResponseService.php:76
- TodoComment src/Services/ResponseService.php:94
- TodoComment src/Services/Module/ModulesService.php:12
- Edited copy of a member (15 corresponding lines) src/Action/Modules/Issues/MyIssuesAction.php:101
- Edited copy of a member (15 corresponding lines) src/Action/Modules/System/Settings/Dashboard/WidgetsVisibilityAction.php:84
- Edited copy of a member (15 corresponding lines) src/DataFixtures/Modules/Issues/MyIssues.php:65
- Abandoned package: composer/package-versions-deprecated
- Abandoned package: doctrine/annotations
- TooManyMethods: BaseResponse src/Response/Base/BaseResponse.php:16
- TooManyMethods: User src/Entity/User.php:21
- Edited copy of a member (18 corresponding lines) src/Action/Modules/Issues/MyIssuesContactAction.php:37
- Edited copy of a member (18 corresponding lines) src/DataFixtures/Modules/Todo/MyTodoFixtures.php:40
- Edited copy of a member (8 corresponding lines) src/DTO/Settings/Dashboard/Widget/SettingsWidgetVisibilityDto.php:58
- Edited copy of a member (8 corresponding lines) src/Security/UriAuthenticator.php:24
- Duplicated block (15 lines × 2) src/Action/Modules/Reports/Payments/MonthlyPerTypeAction.php:59
- Duplicated block (15 lines × 2) src/Action/User/Setting/SecurityAction.php:42
- Duplicated block (9 lines × 2) src/Action/Modules/Health/DoctorAction.php:141
- Duplicated block (9 lines × 2) src/Migrations/Version20191110042650.php:25
- Duplicated block (8 lines × 4) src/Migrations/Version20190824131917.php:25
- Duplicated block (8 lines × 4) src/Migrations/Version20190908031047.php:17
- Duplicated block (7 lines × 2) src/Action/Modules/Issues/MyIssuesAction.php:105
- Duplicated block (7 lines × 2) src/Repository/Modules/Contacts/MyContactTypeRepository.php:34
- Low cohesion: MyTodo (LCOM4 8) src/Entity/Modules/Todo/MyTodo.php:13
- Low cohesion: MyNotesCategories (LCOM4 6) src/Entity/Modules/Notes/MyNotesCategories.php:12
- No data-protection/encryption src/Entity/User.php:49
- JwtTokenResponseListener.onResponse (cyclomatic 16) src/Listeners/Response/JwtTokenResponseListener.php:57
- Hotspot: src/Listeners/Response/JwtTokenResponseListener.php src/Listeners/Response/JwtTokenResponseListener.php:57
- JwtTokenResponseListener.onResponse (cognitive 17) src/Listeners/Response/JwtTokenResponseListener.php:57
- MyIssuesService.getIssuesData (cognitive 17) src/Services/Module/Issues/MyIssuesService.php:35
- SearchAction.searchInStorage (cognitive 16) src/Action/Modules/System/SearchAction.php:68
- Change coupling: MyNotesCategoriesRepository.php ↔ MyNotesRepository.php src/Repository/Modules/Notes/MyNotesCategoriesRepository.php:1
- Members sharing a duplicated core (7 members, 50+ identical tokens) src/Migrations/Version20190717144649.php:23
- Edited copy of a member (40 corresponding lines) src/Action/Modules/Reports/Payments/MonthlyPerTypeAction.php:34
- Edited copy of a member (24 corresponding lines) src/Action/Modules/Calendar/Settings/ManageCalendarsAction.php:113
- Edited copies of one member (4 members, 24+ corresponding lines) src/Action/Modules/Contacts/ContactsAction.php:106
- Edited copies of one member (3 members, 22+ corresponding lines) src/Action/Modules/Goals/GoalsPaymentsAction.php:100
- Edited copy of a member (19 corresponding lines) src/Action/Modules/Payments/MyPaymentsIncomeAction.php:108
- Edited copy of a member (21 corresponding lines) src/Action/User/Setting/SecurityAction.php:42
- Edited copies of one member (3 members, 19+ corresponding lines) src/Action/Modules/Health/DoctorAppointmentAction.php:152
- Edited copies of one member (3 members, 20+ corresponding lines) src/Services/Settings/SettingsSaver.php:53
- Edited copy of a member (17 corresponding lines) src/Services/External/NotifierProxyLoggerService.php:63
- Edited copy of a member (12 corresponding lines) src/DTO/Settings/Finances/SettingsCurrencyDto.php:118
- Edited copies of one member (3 members, 17+ corresponding lines) src/Repository/Modules/Job/MyJobHolidaysRepository.php:32
- Edited copies of one member (3 members, 12+ corresponding lines) src/DTO/Settings/Dashboard/SettingsWidgetSettingsDto.php:54
- Edited copies of one member (3 members, 9+ corresponding lines) src/Action/Modules/Health/DoctorAction.php:54
- Edited copy of a member (9 corresponding lines) src/Entity/Modules/Payments/MyPaymentsIncome.php:76
- Edited copies of one member (3 members, 6+ corresponding lines) src/Action/Modules/Goals/GoalsListAction.php:33
- Edited copy of a member (25 corresponding lines) src/Repository/Modules/Reports/ReportsRepository.php:148
- Duplicated block (15–16 lines × 2) src/Command/Crons/CronMakeBackupCommand.php:86
- Duplicated block (13 lines × 2) src/Action/Modules/Issues/MyIssuesContactAction.php:67
- Duplicated block (11 lines × 2) src/Action/Modules/Job/MyJobHolidaysAction.php:117
- Duplicated block (6 lines × 7) src/Migrations/Version20190717144649.php:23
- Duplicated block (5 lines × 2) src/Action/Modules/Calendar/Settings/ManageCalendarsAction.php:124
- Duplicated block (55 lines × 2) src/Entity/Modules/Issues/MyIssueContact.php:53
- Duplicated block (25 lines × 4) src/Entity/Modules/Contacts/MyContactType.php:29
- Duplicated block (25 lines × 2) src/Entity/Modules/Payments/MyPaymentsSettings.php:32
- Duplicated block (10 lines × 8) src/Migrations/Version20190907074501.php:17
- Duplicated block (10 lines × 2) src/Migrations/Version20191102073301.php:17
- Duplicated block (5 lines × 30) src/Action/Modules/Achievements/AchievementAction.php:94
- Duplicated block (14 lines × 2) src/Services/Database/DatabaseExporter.php:176
- Duplicated block (14 lines × 5) src/Action/Modules/Contacts/Settings/TypeAction.php:53
- Duplicated block (11 lines × 3) src/DTO/Settings/Dashboard/SettingsWidgetSettingsDto.php:76
- Duplicated block (18 lines × 2) src/DataFixtures/Modules/Todo/MyTodoElementFixtures.php:30
- Unstable project src/Action
- Constructible in an invalid state: StorageFile src/Entity/Modules/Storage/StorageFile.php:25
- No CI pipeline
- Outbound HTTP without resilience src/Services/External/DiscordService.php:20
- Swallowed exception (caught, then discarded) src/Services/System/EnvReader.php:92
Minor — 23 finding(s)
- Interpolated log message defeats structured logging src/Services/Shell/ShellAbstractService.php:91
- Interpolated log message defeats structured logging src/Services/Security/JwtUserRightsHandler.php:68
- Interpolated log message defeats structured logging src/Services/Module/Storage/StorageFolderService.php:213
- Interpolated log message defeats structured logging src/Services/Module/Storage/StorageFolderService.php:219
- Interpolated log message defeats structured logging src/Command/Crons/CronTransferSchedulesToNotifierProxyLoggerCommand.php:93
- Interpolated log message defeats structured logging src/Action/User/Setting/BaseDataAction.php:98
- REDACTED
- REDACTED
- REDACTED
- No named authorization policies
- Documentation: no build, run or usage example README.md:1
- No ADRs found composer.json:18
- Scattered collaborators
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- No rollback/health safety
- No changelog
- No security response headers detected docker/nginx/nginx.conf:92
- Duplicated predicate src/Action/Modules/System/Settings/Dashboard/WidgetsVisibilityAction.php:42
- PHP static analysis does not check null everywhere
- Subsumed condition operand src/Services/Files/PathService.php:92
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 --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-9f4c4be792fe45b69ee78d617d92d629/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-9f4c4be792fe45b69ee78d617d92d629/history-1.json --exit-code 0 --source . | 59 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=413" --report-format json --report-path /tmp/watchdog-gitleaks-9f4c4be792fe45b69ee78d617d92d629/history-2.json --exit-code 0 --source . | 36 | artifacts/raw/gitleaks-history-2.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-9f4c4be792fe45b69ee78d617d92d629/tree.json --exit-code 0 --source . | 4 | 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 . | 1 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 32 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 109 file(s) — `src/Action/File/UploadedFileAction.php`, `src/Action/Modules/Achievements/AchievementAction.php`, `src/Action/Modules/Calendar/SchedulesAction.php`, `src/Action/Modules/Calendar/Settings/ManageCalendarsAction.php`, `src/Action/Modules/Contacts/ContactTypesAction.php`, … (+104 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 |