Executive summary
mchekin/rpg is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 36 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Production Readiness, at 24, is the weakest lens and counts most in the score. The best first step is fixing the two packages their makers have withdrawn or abandoned, worth about 5 points. Adding automated security scanning would lift Production Readiness itself, worth about 4 points. Raising Production Readiness to 62 would lift the score to about 46.
Sixty-two known security holes in the packages the code depends on can be used by attackers. Four settings leave the servers or containers unsafe, and eight images have no description for people who can't see them. Updating the vulnerable packages, correcting the unsafe settings and describing the images would close these risks. The password or key in the code's history needs replacing, with the old one switched off. The three form fields without a label need a label.
The product code is 12,802 lines, about €15,000 to rebuild.
If Production Readiness rose from 24 to 62, the lowest score rated Strong, the score would rise from 36 to about 46.
New since the last survey: 7 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 31 findings
- REDACTED Scanning · Leaked secret: hardcoded-credential app/Http/Controllers/Auth/RegisterController.php
- Boundary Type-Coupling · Cross-context type Character (Character → Battle) app/Modules/Battle/Domain/Battle.php
- Boundary Type-Coupling · Cross-context type Character (Character → Battle) app/Modules/Battle/Domain/Battle.php
- Boundary Type-Coupling · Cross-context type Character (Character → Battle) app/Modules/Battle/Domain/Battle.php
- Boundary Type-Coupling · Cross-context type Character (Character → Battle) app/Modules/Battle/Domain/Battle.php
- Boundary Type-Coupling · Cross-context type Character (Character → Battle) app/Modules/Battle/Domain/Battle.php
- Boundary Type-Coupling · Cross-context type Character (Character → Battle) app/Modules/Battle/Domain/BattleRound.php
- Boundary Type-Coupling · Cross-context type Character (Character → Battle) app/Modules/Battle/Domain/BattleTurn.php
- Boundary Type-Coupling · Cross-context type Character (Character → Battle) app/Modules/Battle/Domain/BattleTurn.php
- Boundary Type-Coupling · Cross-context type Character (Character → Battle) app/Modules/Battle/Domain/BattleTurn.php
- Boundary Type-Coupling · Cross-context type Inventory (Equipment → Character) app/Modules/Character/Application/Factories/CharacterFactory.php
- Boundary Type-Coupling · Cross-context type Image (Image → Character) app/Modules/Character/Application/Services/CharacterService.php
- Boundary Type-Coupling · Cross-context type Inventory (Equipment → Character) app/Modules/Character/Domain/Character.php
- Boundary Type-Coupling · Cross-context type Item (Equipment → Character) app/Modules/Character/Domain/Character.php
- Boundary Type-Coupling · Cross-context type Inventory (Equipment → Character) app/Modules/Character/Domain/Character.php
- Boundary Type-Coupling · Cross-context type Item (Equipment → Trade) app/Modules/Trade/Domain/Store.php
- Boundary Type-Coupling · Cross-context type Item (Equipment → Trade) app/Modules/Trade/Domain/Store.php
- Boundary Type-Coupling · Cross-context type Item (Equipment → Trade) app/Modules/Trade/Domain/Store.php
- Boundary Type-Coupling · Cross-context type Item (Equipment → Trade) app/Modules/Trade/Domain/Store.php
- Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/Api/AuthController.php
- Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/Api/AuthController.php
- Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/Auth/AuthController.php
- Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/Auth/RegisterController.php
- Secrets (history) · High secret: WD-SECRET-0005 REDACTED
- Dependency Vulnerabilities · High vulnerability: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Rebuild cost: about €15,000 · Estimate
| Cost to rebuild | €5,100 to €26,000, for 85 to 270 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 36. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 12,802 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 Models | 2 Modules.Generic.Domain | 3 Modules.Level.Application.Services | 4 Modules.Equipment.Domain | 5 Modules.Image.Domain | 6 Modules.User.Application.Services | 7 Modules.Character.Domain | 8 Modules.Equipment.Infrastructure.ReconstitutionFactories | 9 Modules.Battle.Domain | 10 Modules.Character.Application.Commands | 11 Modules.Character.Application.Contracts | 12 Modules.Character.Infrastructure.ReconstitutionFactories | 13 Modules.Equipment.Application.Commands | 14 Modules.Equipment.Application.Contracts | 15 Modules.Equipment.Application.Factories | 16 Modules.Image.Application.Commands | 17 Modules.Image.Application.Contracts | 18 Modules.Image.Application.Factories | 19 Modules.Message.Application.Commands | 20 Modules.Message.Domain | 21 Modules.Trade.Domain | 22 Modules.Battle.Application.Contracts | 23 Modules.Character.Application.Factories | 24 Modules.Character.Infrastructure.Repositories | 25 Modules.Equipment.Application.Services | 26 Modules.Equipment.Infrastructure.Repositories | 27 Modules.Equipment.UI.Http.CommandMappers | 28 Modules.Image.Infrastructure.Repositories | 29 Modules.Message.Application.Contracts | 30 Modules.Trade.Application.Commands | 31 Modules.Trade.Application.Contracts | 32 Modules.Trade.Infrastructure.ReconstitutionFactories | 33 Modules.Message.Application.Services | 34 Modules.Trade.Application.Services | 35 Modules.Trade.Infrastructure.Repositories | 36 Modules.Character.Application.Services | 37 Modules.Image.Application.Services | 38 Http.Controllers | 39 Http.Controllers.Api | 40 Http.Controllers.Auth |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Models | ||||||||||||||||||||||||||||||||||||||||
| 2 Modules.Generic.Domain | ||||||||||||||||||||||||||||||||||||||||
| 3 Modules.Level.Application.Services | ||||||||||||||||||||||||||||||||||||||||
| 4 Modules.Equipment.Domain | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 5 Modules.Image.Domain | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 6 Modules.User.Application.Services | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 Modules.Character.Domain | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 8 Modules.Equipment.Infrastructure.ReconstitutionFactories | 4 | 4 | ||||||||||||||||||||||||||||||||||||||
| 9 Modules.Battle.Domain | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 10 Modules.Character.Application.Commands | 3 | |||||||||||||||||||||||||||||||||||||||
| 11 Modules.Character.Application.Contracts | 4 | |||||||||||||||||||||||||||||||||||||||
| 12 Modules.Character.Infrastructure.ReconstitutionFactories | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 Modules.Equipment.Application.Commands | 3 | 4 | ||||||||||||||||||||||||||||||||||||||
| 14 Modules.Equipment.Application.Contracts | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 Modules.Equipment.Application.Factories | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 Modules.Image.Application.Commands | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Modules.Image.Application.Contracts | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 Modules.Image.Application.Factories | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 Modules.Message.Application.Commands | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Modules.Message.Domain | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Modules.Trade.Domain | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 Modules.Battle.Application.Contracts | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 Modules.Character.Application.Factories | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 Modules.Character.Infrastructure.Repositories | 4 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 Modules.Equipment.Application.Services | 1 | 1 | 3 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 26 Modules.Equipment.Infrastructure.Repositories | 6 | 1 | 3 | 3 | ||||||||||||||||||||||||||||||||||||
| 27 Modules.Equipment.UI.Http.CommandMappers | 3 | |||||||||||||||||||||||||||||||||||||||
| 28 Modules.Image.Infrastructure.Repositories | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 Modules.Message.Application.Contracts | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 Modules.Trade.Application.Commands | 1 | 7 | 7 | 2 | ||||||||||||||||||||||||||||||||||||
| 31 Modules.Trade.Application.Contracts | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 32 Modules.Trade.Infrastructure.ReconstitutionFactories | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 Modules.Message.Application.Services | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 Modules.Trade.Application.Services | 4 | 1 | 1 | 6 | 3 | |||||||||||||||||||||||||||||||||||
| 35 Modules.Trade.Infrastructure.Repositories | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 Modules.Character.Application.Services | 1 | 1 | 2 | 1 | 4 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 37 Modules.Image.Application.Services | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 38 Http.Controllers | 1 | 2 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 39 Http.Controllers.Api | 1 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||||
| 40 Http.Controllers.Auth | 1 | 6 |
4→2 Modules.Equipment.Domain uses Modules.Generic.Domain✕
- Connections
- 3 pairs of types, where a type in Modules.Equipment.Domain uses a type in Modules.Generic.Domain.
- The types involved
App.Modules.Equipment.Domain.InventoryId→App.Modules.Generic.Domain.BaseIdApp.Modules.Equipment.Domain.ItemId→App.Modules.Generic.Domain.BaseIdApp.Modules.Equipment.Domain.ItemPrototypeId→App.Modules.Generic.Domain.BaseId
- Direction
- Modules.Equipment.Domain uses Modules.Generic.Domain, so a change to Modules.Generic.Domain can break Modules.Equipment.Domain, while a change to Modules.Equipment.Domain can't break Modules.Generic.Domain.
- Position
- Below the diagonal: Modules.Equipment.Domain uses a module listed above it, which is the healthy direction.
4→7 Modules.Equipment.Domain uses Modules.Character.Domain part of a loop✕
- Connections
- 2 pairs of types, where a type in Modules.Equipment.Domain uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Equipment.Domain.Inventory→App.Modules.Character.Domain.CharacterIdApp.Modules.Equipment.Domain.Item→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Equipment.Domain uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Equipment.Domain, while a change to Modules.Equipment.Domain can't break Modules.Character.Domain.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→2 Modules.Image.Domain uses Modules.Generic.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Image.Domain uses a type in Modules.Generic.Domain.
- The types involved
App.Modules.Image.Domain.ImageId→App.Modules.Generic.Domain.BaseId
- Direction
- Modules.Image.Domain uses Modules.Generic.Domain, so a change to Modules.Generic.Domain can break Modules.Image.Domain, while a change to Modules.Image.Domain can't break Modules.Generic.Domain.
- Position
- Below the diagonal: Modules.Image.Domain uses a module listed above it, which is the healthy direction.
5→7 Modules.Image.Domain uses Modules.Character.Domain part of a loop✕
- Connections
- 1 pair of types, where a type in Modules.Image.Domain uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Image.Domain.Image→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Image.Domain uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Image.Domain, while a change to Modules.Image.Domain can't break Modules.Character.Domain.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→1 Modules.User.Application.Services uses Models✕
- Connections
- 1 pair of types, where a type in Modules.User.Application.Services uses a type in Models.
- The types involved
App.Modules.User.Application.Services.UserService→App.Models.User
- Direction
- Modules.User.Application.Services uses Models, so a change to Models can break Modules.User.Application.Services, while a change to Modules.User.Application.Services can't break Models.
- Position
- Below the diagonal: Modules.User.Application.Services uses a module listed above it, which is the healthy direction.
7→2 Modules.Character.Domain uses Modules.Generic.Domain✕
- Connections
- 2 pairs of types, where a type in Modules.Character.Domain uses a type in Modules.Generic.Domain.
- The types involved
App.Modules.Character.Domain.CharacterId→App.Modules.Generic.Domain.BaseIdApp.Modules.Character.Domain.LocationId→App.Modules.Generic.Domain.BaseId
- Direction
- Modules.Character.Domain uses Modules.Generic.Domain, so a change to Modules.Generic.Domain can break Modules.Character.Domain, while a change to Modules.Character.Domain can't break Modules.Generic.Domain.
- Position
- Below the diagonal: Modules.Character.Domain uses a module listed above it, which is the healthy direction.
7→4 Modules.Character.Domain uses Modules.Equipment.Domain✕
- Connections
- 3 pairs of types, where a type in Modules.Character.Domain uses a type in Modules.Equipment.Domain.
- The types involved
App.Modules.Character.Domain.Character→App.Modules.Equipment.Domain.InventoryApp.Modules.Character.Domain.Character→App.Modules.Equipment.Domain.ItemApp.Modules.Character.Domain.Character→App.Modules.Equipment.Domain.Money
- Direction
- Modules.Character.Domain uses Modules.Equipment.Domain, so a change to Modules.Equipment.Domain can break Modules.Character.Domain, while a change to Modules.Character.Domain can't break Modules.Equipment.Domain.
- Position
- Below the diagonal: Modules.Character.Domain uses a module listed above it, which is the healthy direction.
7→5 Modules.Character.Domain uses Modules.Image.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Character.Domain uses a type in Modules.Image.Domain.
- The types involved
App.Modules.Character.Domain.Character→App.Modules.Image.Domain.ImageId
- Direction
- Modules.Character.Domain uses Modules.Image.Domain, so a change to Modules.Image.Domain can break Modules.Character.Domain, while a change to Modules.Character.Domain can't break Modules.Image.Domain.
- Position
- Below the diagonal: Modules.Character.Domain uses a module listed above it, which is the healthy direction.
8→1 Modules.Equipment.Infrastructure.ReconstitutionFactories uses Models✕
- Connections
- 4 pairs of types, where a type in Modules.Equipment.Infrastructure.ReconstitutionFactories uses a type in Models.
- The types involved
App.Modules.Equipment.Infrastructure.ReconstitutionFactories.InventoryItemReconstitutionFactory→App.Models.ItemApp.Modules.Equipment.Infrastructure.ReconstitutionFactories.InventoryReconstitutionFactory→App.Models.InventoryApp.Modules.Equipment.Infrastructure.ReconstitutionFactories.ItemPrototypeReconstitutionFactory→App.Models.ItemPrototypeApp.Modules.Equipment.Infrastructure.ReconstitutionFactories.ItemReconstitutionFactory→App.Models.Item
- Direction
- Modules.Equipment.Infrastructure.ReconstitutionFactories uses Models, so a change to Models can break Modules.Equipment.Infrastructure.ReconstitutionFactories, while a change to Modules.Equipment.Infrastructure.ReconstitutionFactories can't break Models.
- Position
- Below the diagonal: Modules.Equipment.Infrastructure.ReconstitutionFactories uses a module listed above it, which is the healthy direction.
8→4 Modules.Equipment.Infrastructure.ReconstitutionFactories uses Modules.Equipment.Domain✕
- Connections
- 4 pairs of types, where a type in Modules.Equipment.Infrastructure.ReconstitutionFactories uses a type in Modules.Equipment.Domain.
- The types involved
App.Modules.Equipment.Infrastructure.ReconstitutionFactories.InventoryItemReconstitutionFactory→App.Modules.Equipment.Domain.InventoryItemApp.Modules.Equipment.Infrastructure.ReconstitutionFactories.InventoryReconstitutionFactory→App.Modules.Equipment.Domain.InventoryApp.Modules.Equipment.Infrastructure.ReconstitutionFactories.ItemPrototypeReconstitutionFactory→App.Modules.Equipment.Domain.ItemPrototypeApp.Modules.Equipment.Infrastructure.ReconstitutionFactories.ItemReconstitutionFactory→App.Modules.Equipment.Domain.Item
- Direction
- Modules.Equipment.Infrastructure.ReconstitutionFactories uses Modules.Equipment.Domain, so a change to Modules.Equipment.Domain can break Modules.Equipment.Infrastructure.ReconstitutionFactories, while a change to Modules.Equipment.Infrastructure.ReconstitutionFactories can't break Modules.Equipment.Domain.
- Position
- Below the diagonal: Modules.Equipment.Infrastructure.ReconstitutionFactories uses a module listed above it, which is the healthy direction.
9→2 Modules.Battle.Domain uses Modules.Generic.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Battle.Domain uses a type in Modules.Generic.Domain.
- The types involved
App.Modules.Battle.Domain.BattleId→App.Modules.Generic.Domain.BaseId
- Direction
- Modules.Battle.Domain uses Modules.Generic.Domain, so a change to Modules.Generic.Domain can break Modules.Battle.Domain, while a change to Modules.Battle.Domain can't break Modules.Generic.Domain.
- Position
- Below the diagonal: Modules.Battle.Domain uses a module listed above it, which is the healthy direction.
9→7 Modules.Battle.Domain uses Modules.Character.Domain✕
- Connections
- 3 pairs of types, where a type in Modules.Battle.Domain uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Battle.Domain.Battle→App.Modules.Character.Domain.CharacterApp.Modules.Battle.Domain.BattleRound→App.Modules.Character.Domain.CharacterApp.Modules.Battle.Domain.BattleTurn→App.Modules.Character.Domain.Character
- Direction
- Modules.Battle.Domain uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Battle.Domain, while a change to Modules.Battle.Domain can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Battle.Domain uses a module listed above it, which is the healthy direction.
10→7 Modules.Character.Application.Commands uses Modules.Character.Domain✕
- Connections
- 3 pairs of types, where a type in Modules.Character.Application.Commands uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Character.Application.Commands.AttackCharacterCommand→App.Modules.Character.Domain.CharacterIdApp.Modules.Character.Application.Commands.IncreaseAttributeCommand→App.Modules.Character.Domain.CharacterIdApp.Modules.Character.Application.Commands.MoveCharacterCommand→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Character.Application.Commands uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Character.Application.Commands, while a change to Modules.Character.Application.Commands can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Character.Application.Commands uses a module listed above it, which is the healthy direction.
11→7 Modules.Character.Application.Contracts uses Modules.Character.Domain✕
- Connections
- 4 pairs of types, where a type in Modules.Character.Application.Contracts uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Character.Application.Contracts.CharacterRepositoryInterface→App.Modules.Character.Domain.CharacterApp.Modules.Character.Application.Contracts.CharacterRepositoryInterface→App.Modules.Character.Domain.CharacterIdApp.Modules.Character.Application.Contracts.LocationRepositoryInterface→App.Modules.Character.Domain.LocationIdApp.Modules.Character.Application.Contracts.RaceRepositoryInterface→App.Modules.Character.Domain.Race
- Direction
- Modules.Character.Application.Contracts uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Character.Application.Contracts, while a change to Modules.Character.Application.Contracts can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Character.Application.Contracts uses a module listed above it, which is the healthy direction.
12→1 Modules.Character.Infrastructure.ReconstitutionFactories uses Models✕
- Connections
- 1 pair of types, where a type in Modules.Character.Infrastructure.ReconstitutionFactories uses a type in Models.
- The types involved
App.Modules.Character.Infrastructure.ReconstitutionFactories.CharacterReconstitutionFactory→App.Models.Character
- Direction
- Modules.Character.Infrastructure.ReconstitutionFactories uses Models, so a change to Models can break Modules.Character.Infrastructure.ReconstitutionFactories, while a change to Modules.Character.Infrastructure.ReconstitutionFactories can't break Models.
- Position
- Below the diagonal: Modules.Character.Infrastructure.ReconstitutionFactories uses a module listed above it, which is the healthy direction.
12→7 Modules.Character.Infrastructure.ReconstitutionFactories uses Modules.Character.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Character.Infrastructure.ReconstitutionFactories uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Character.Infrastructure.ReconstitutionFactories.CharacterReconstitutionFactory→App.Modules.Character.Domain.Character
- Direction
- Modules.Character.Infrastructure.ReconstitutionFactories uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Character.Infrastructure.ReconstitutionFactories, while a change to Modules.Character.Infrastructure.ReconstitutionFactories can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Character.Infrastructure.ReconstitutionFactories uses a module listed above it, which is the healthy direction.
12→8 Modules.Character.Infrastructure.ReconstitutionFactories uses Modules.Equipment.Infrastructure.ReconstitutionFactories✕
- Connections
- 1 pair of types, where a type in Modules.Character.Infrastructure.ReconstitutionFactories uses a type in Modules.Equipment.Infrastructure.ReconstitutionFactories.
- The types involved
App.Modules.Character.Infrastructure.ReconstitutionFactories.CharacterReconstitutionFactory→App.Modules.Equipment.Infrastructure.ReconstitutionFactories.InventoryReconstitutionFactory
- Direction
- Modules.Character.Infrastructure.ReconstitutionFactories uses Modules.Equipment.Infrastructure.ReconstitutionFactories, so a change to Modules.Equipment.Infrastructure.ReconstitutionFactories can break Modules.Character.Infrastructure.ReconstitutionFactories, while a change to Modules.Character.Infrastructure.ReconstitutionFactories can't break Modules.Equipment.Infrastructure.ReconstitutionFactories.
- Position
- Below the diagonal: Modules.Character.Infrastructure.ReconstitutionFactories uses a module listed above it, which is the healthy direction.
13→4 Modules.Equipment.Application.Commands uses Modules.Equipment.Domain✕
- Connections
- 3 pairs of types, where a type in Modules.Equipment.Application.Commands uses a type in Modules.Equipment.Domain.
- The types involved
App.Modules.Equipment.Application.Commands.AddItemToInventoryCommand→App.Modules.Equipment.Domain.ItemIdApp.Modules.Equipment.Application.Commands.CreateItemCommand→App.Modules.Equipment.Domain.ItemPrototypeIdApp.Modules.Equipment.Application.Commands.EquipItemCommand→App.Modules.Equipment.Domain.ItemId
- Direction
- Modules.Equipment.Application.Commands uses Modules.Equipment.Domain, so a change to Modules.Equipment.Domain can break Modules.Equipment.Application.Commands, while a change to Modules.Equipment.Application.Commands can't break Modules.Equipment.Domain.
- Position
- Below the diagonal: Modules.Equipment.Application.Commands uses a module listed above it, which is the healthy direction.
13→7 Modules.Equipment.Application.Commands uses Modules.Character.Domain✕
- Connections
- 4 pairs of types, where a type in Modules.Equipment.Application.Commands uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Equipment.Application.Commands.AddItemToInventoryCommand→App.Modules.Character.Domain.CharacterIdApp.Modules.Equipment.Application.Commands.CreateInventoryCommand→App.Modules.Character.Domain.CharacterIdApp.Modules.Equipment.Application.Commands.CreateItemCommand→App.Modules.Character.Domain.CharacterIdApp.Modules.Equipment.Application.Commands.EquipItemCommand→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Equipment.Application.Commands uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Equipment.Application.Commands, while a change to Modules.Equipment.Application.Commands can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Equipment.Application.Commands uses a module listed above it, which is the healthy direction.
14→4 Modules.Equipment.Application.Contracts uses Modules.Equipment.Domain✕
- Connections
- 6 pairs of types, where a type in Modules.Equipment.Application.Contracts uses a type in Modules.Equipment.Domain.
- The types involved
App.Modules.Equipment.Application.Contracts.InventoryRepositoryInterface→App.Modules.Equipment.Domain.InventoryApp.Modules.Equipment.Application.Contracts.InventoryRepositoryInterface→App.Modules.Equipment.Domain.InventoryIdApp.Modules.Equipment.Application.Contracts.ItemPrototypeRepositoryInterface→App.Modules.Equipment.Domain.ItemPrototypeApp.Modules.Equipment.Application.Contracts.ItemPrototypeRepositoryInterface→App.Modules.Equipment.Domain.ItemPrototypeIdApp.Modules.Equipment.Application.Contracts.ItemRepositoryInterface→App.Modules.Equipment.Domain.ItemApp.Modules.Equipment.Application.Contracts.ItemRepositoryInterface→App.Modules.Equipment.Domain.ItemId
- Direction
- Modules.Equipment.Application.Contracts uses Modules.Equipment.Domain, so a change to Modules.Equipment.Domain can break Modules.Equipment.Application.Contracts, while a change to Modules.Equipment.Application.Contracts can't break Modules.Equipment.Domain.
- Position
- Below the diagonal: Modules.Equipment.Application.Contracts uses a module listed above it, which is the healthy direction.
14→7 Modules.Equipment.Application.Contracts uses Modules.Character.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Equipment.Application.Contracts uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Equipment.Application.Contracts.InventoryRepositoryInterface→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Equipment.Application.Contracts uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Equipment.Application.Contracts, while a change to Modules.Equipment.Application.Contracts can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Equipment.Application.Contracts uses a module listed above it, which is the healthy direction.
15→4 Modules.Equipment.Application.Factories uses Modules.Equipment.Domain✕
- Connections
- 3 pairs of types, where a type in Modules.Equipment.Application.Factories uses a type in Modules.Equipment.Domain.
- The types involved
App.Modules.Equipment.Application.Factories.ItemFactory→App.Modules.Equipment.Domain.ItemApp.Modules.Equipment.Application.Factories.ItemFactory→App.Modules.Equipment.Domain.ItemIdApp.Modules.Equipment.Application.Factories.ItemFactory→App.Modules.Equipment.Domain.ItemPrototype
- Direction
- Modules.Equipment.Application.Factories uses Modules.Equipment.Domain, so a change to Modules.Equipment.Domain can break Modules.Equipment.Application.Factories, while a change to Modules.Equipment.Application.Factories can't break Modules.Equipment.Domain.
- Position
- Below the diagonal: Modules.Equipment.Application.Factories uses a module listed above it, which is the healthy direction.
15→7 Modules.Equipment.Application.Factories uses Modules.Character.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Equipment.Application.Factories uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Equipment.Application.Factories.ItemFactory→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Equipment.Application.Factories uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Equipment.Application.Factories, while a change to Modules.Equipment.Application.Factories can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Equipment.Application.Factories uses a module listed above it, which is the healthy direction.
16→7 Modules.Image.Application.Commands uses Modules.Character.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Image.Application.Commands uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Image.Application.Commands.AddImageCommand→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Image.Application.Commands uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Image.Application.Commands, while a change to Modules.Image.Application.Commands can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Image.Application.Commands uses a module listed above it, which is the healthy direction.
17→5 Modules.Image.Application.Contracts uses Modules.Image.Domain✕
- Connections
- 2 pairs of types, where a type in Modules.Image.Application.Contracts uses a type in Modules.Image.Domain.
- The types involved
App.Modules.Image.Application.Contracts.ImageRepositoryInterface→App.Modules.Image.Domain.ImageApp.Modules.Image.Application.Contracts.ImageRepositoryInterface→App.Modules.Image.Domain.ImageId
- Direction
- Modules.Image.Application.Contracts uses Modules.Image.Domain, so a change to Modules.Image.Domain can break Modules.Image.Application.Contracts, while a change to Modules.Image.Application.Contracts can't break Modules.Image.Domain.
- Position
- Below the diagonal: Modules.Image.Application.Contracts uses a module listed above it, which is the healthy direction.
17→7 Modules.Image.Application.Contracts uses Modules.Character.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Image.Application.Contracts uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Image.Application.Contracts.ImageRepositoryInterface→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Image.Application.Contracts uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Image.Application.Contracts, while a change to Modules.Image.Application.Contracts can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Image.Application.Contracts uses a module listed above it, which is the healthy direction.
18→5 Modules.Image.Application.Factories uses Modules.Image.Domain✕
- Connections
- 2 pairs of types, where a type in Modules.Image.Application.Factories uses a type in Modules.Image.Domain.
- The types involved
App.Modules.Image.Application.Factories.ImageFactory→App.Modules.Image.Domain.ImageApp.Modules.Image.Application.Factories.ImageFactory→App.Modules.Image.Domain.ImageId
- Direction
- Modules.Image.Application.Factories uses Modules.Image.Domain, so a change to Modules.Image.Domain can break Modules.Image.Application.Factories, while a change to Modules.Image.Application.Factories can't break Modules.Image.Domain.
- Position
- Below the diagonal: Modules.Image.Application.Factories uses a module listed above it, which is the healthy direction.
18→7 Modules.Image.Application.Factories uses Modules.Character.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Image.Application.Factories uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Image.Application.Factories.ImageFactory→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Image.Application.Factories uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Image.Application.Factories, while a change to Modules.Image.Application.Factories can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Image.Application.Factories uses a module listed above it, which is the healthy direction.
19→7 Modules.Message.Application.Commands uses Modules.Character.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Message.Application.Commands uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Message.Application.Commands.SendMessageCommand→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Message.Application.Commands uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Message.Application.Commands, while a change to Modules.Message.Application.Commands can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Message.Application.Commands uses a module listed above it, which is the healthy direction.
20→2 Modules.Message.Domain uses Modules.Generic.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Message.Domain uses a type in Modules.Generic.Domain.
- The types involved
App.Modules.Message.Domain.MessageId→App.Modules.Generic.Domain.BaseId
- Direction
- Modules.Message.Domain uses Modules.Generic.Domain, so a change to Modules.Generic.Domain can break Modules.Message.Domain, while a change to Modules.Message.Domain can't break Modules.Generic.Domain.
- Position
- Below the diagonal: Modules.Message.Domain uses a module listed above it, which is the healthy direction.
20→7 Modules.Message.Domain uses Modules.Character.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Message.Domain uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Message.Domain.Message→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Message.Domain uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Message.Domain, while a change to Modules.Message.Domain can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Message.Domain uses a module listed above it, which is the healthy direction.
21→2 Modules.Trade.Domain uses Modules.Generic.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Trade.Domain uses a type in Modules.Generic.Domain.
- The types involved
App.Modules.Trade.Domain.StoreId→App.Modules.Generic.Domain.BaseId
- Direction
- Modules.Trade.Domain uses Modules.Generic.Domain, so a change to Modules.Generic.Domain can break Modules.Trade.Domain, while a change to Modules.Trade.Domain can't break Modules.Generic.Domain.
- Position
- Below the diagonal: Modules.Trade.Domain uses a module listed above it, which is the healthy direction.
21→4 Modules.Trade.Domain uses Modules.Equipment.Domain✕
- Connections
- 4 pairs of types, where a type in Modules.Trade.Domain uses a type in Modules.Equipment.Domain.
- The types involved
App.Modules.Trade.Domain.Store→App.Modules.Equipment.Domain.ItemApp.Modules.Trade.Domain.Store→App.Modules.Equipment.Domain.ItemIdApp.Modules.Trade.Domain.Store→App.Modules.Equipment.Domain.ItemTypeApp.Modules.Trade.Domain.Store→App.Modules.Equipment.Domain.Money
- Direction
- Modules.Trade.Domain uses Modules.Equipment.Domain, so a change to Modules.Equipment.Domain can break Modules.Trade.Domain, while a change to Modules.Trade.Domain can't break Modules.Equipment.Domain.
- Position
- Below the diagonal: Modules.Trade.Domain uses a module listed above it, which is the healthy direction.
21→7 Modules.Trade.Domain uses Modules.Character.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Trade.Domain uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Trade.Domain.Store→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Trade.Domain uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Trade.Domain, while a change to Modules.Trade.Domain can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Trade.Domain uses a module listed above it, which is the healthy direction.
22→9 Modules.Battle.Application.Contracts uses Modules.Battle.Domain✕
- Connections
- 2 pairs of types, where a type in Modules.Battle.Application.Contracts uses a type in Modules.Battle.Domain.
- The types involved
App.Modules.Battle.Application.Contracts.BattleRepositoryInterface→App.Modules.Battle.Domain.BattleApp.Modules.Battle.Application.Contracts.BattleRepositoryInterface→App.Modules.Battle.Domain.BattleId
- Direction
- Modules.Battle.Application.Contracts uses Modules.Battle.Domain, so a change to Modules.Battle.Domain can break Modules.Battle.Application.Contracts, while a change to Modules.Battle.Application.Contracts can't break Modules.Battle.Domain.
- Position
- Below the diagonal: Modules.Battle.Application.Contracts uses a module listed above it, which is the healthy direction.
23→4 Modules.Character.Application.Factories uses Modules.Equipment.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Character.Application.Factories uses a type in Modules.Equipment.Domain.
- The types involved
App.Modules.Character.Application.Factories.CharacterFactory→App.Modules.Equipment.Domain.Inventory
- Direction
- Modules.Character.Application.Factories uses Modules.Equipment.Domain, so a change to Modules.Equipment.Domain can break Modules.Character.Application.Factories, while a change to Modules.Character.Application.Factories can't break Modules.Equipment.Domain.
- Position
- Below the diagonal: Modules.Character.Application.Factories uses a module listed above it, which is the healthy direction.
23→7 Modules.Character.Application.Factories uses Modules.Character.Domain✕
- Connections
- 3 pairs of types, where a type in Modules.Character.Application.Factories uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Character.Application.Factories.CharacterFactory→App.Modules.Character.Domain.CharacterApp.Modules.Character.Application.Factories.CharacterFactory→App.Modules.Character.Domain.CharacterIdApp.Modules.Character.Application.Factories.CharacterFactory→App.Modules.Character.Domain.Race
- Direction
- Modules.Character.Application.Factories uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Character.Application.Factories, while a change to Modules.Character.Application.Factories can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Character.Application.Factories uses a module listed above it, which is the healthy direction.
23→10 Modules.Character.Application.Factories uses Modules.Character.Application.Commands✕
- Connections
- 1 pair of types, where a type in Modules.Character.Application.Factories uses a type in Modules.Character.Application.Commands.
- The types involved
App.Modules.Character.Application.Factories.CharacterFactory→App.Modules.Character.Application.Commands.CreateCharacterCommand
- Direction
- Modules.Character.Application.Factories uses Modules.Character.Application.Commands, so a change to Modules.Character.Application.Commands can break Modules.Character.Application.Factories, while a change to Modules.Character.Application.Factories can't break Modules.Character.Application.Commands.
- Position
- Below the diagonal: Modules.Character.Application.Factories uses a module listed above it, which is the healthy direction.
24→7 Modules.Character.Infrastructure.Repositories uses Modules.Character.Domain✕
- Connections
- 4 pairs of types, where a type in Modules.Character.Infrastructure.Repositories uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Character.Infrastructure.Repositories.CharacterRepository→App.Modules.Character.Domain.CharacterApp.Modules.Character.Infrastructure.Repositories.CharacterRepository→App.Modules.Character.Domain.CharacterIdApp.Modules.Character.Infrastructure.Repositories.LocationRepository→App.Modules.Character.Domain.LocationIdApp.Modules.Character.Infrastructure.Repositories.RaceRepository→App.Modules.Character.Domain.Race
- Direction
- Modules.Character.Infrastructure.Repositories uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Character.Infrastructure.Repositories, while a change to Modules.Character.Infrastructure.Repositories can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Character.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
24→11 Modules.Character.Infrastructure.Repositories uses Modules.Character.Application.Contracts✕
- Connections
- 3 pairs of types, where a type in Modules.Character.Infrastructure.Repositories uses a type in Modules.Character.Application.Contracts.
- The types involved
App.Modules.Character.Infrastructure.Repositories.CharacterRepository→App.Modules.Character.Application.Contracts.CharacterRepositoryInterfaceApp.Modules.Character.Infrastructure.Repositories.LocationRepository→App.Modules.Character.Application.Contracts.LocationRepositoryInterfaceApp.Modules.Character.Infrastructure.Repositories.RaceRepository→App.Modules.Character.Application.Contracts.RaceRepositoryInterface
- Direction
- Modules.Character.Infrastructure.Repositories uses Modules.Character.Application.Contracts, so a change to Modules.Character.Application.Contracts can break Modules.Character.Infrastructure.Repositories, while a change to Modules.Character.Infrastructure.Repositories can't break Modules.Character.Application.Contracts.
- Position
- Below the diagonal: Modules.Character.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
24→12 Modules.Character.Infrastructure.Repositories uses Modules.Character.Infrastructure.ReconstitutionFactories✕
- Connections
- 1 pair of types, where a type in Modules.Character.Infrastructure.Repositories uses a type in Modules.Character.Infrastructure.ReconstitutionFactories.
- The types involved
App.Modules.Character.Infrastructure.Repositories.CharacterRepository→App.Modules.Character.Infrastructure.ReconstitutionFactories.CharacterReconstitutionFactory
- Direction
- Modules.Character.Infrastructure.Repositories uses Modules.Character.Infrastructure.ReconstitutionFactories, so a change to Modules.Character.Infrastructure.ReconstitutionFactories can break Modules.Character.Infrastructure.Repositories, while a change to Modules.Character.Infrastructure.Repositories can't break Modules.Character.Infrastructure.ReconstitutionFactories.
- Position
- Below the diagonal: Modules.Character.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
25→4 Modules.Equipment.Application.Services uses Modules.Equipment.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Equipment.Application.Services uses a type in Modules.Equipment.Domain.
- The types involved
App.Modules.Equipment.Application.Services.InventoryService→App.Modules.Equipment.Domain.Inventory
- Direction
- Modules.Equipment.Application.Services uses Modules.Equipment.Domain, so a change to Modules.Equipment.Domain can break Modules.Equipment.Application.Services, while a change to Modules.Equipment.Application.Services can't break Modules.Equipment.Domain.
- Position
- Below the diagonal: Modules.Equipment.Application.Services uses a module listed above it, which is the healthy direction.
25→11 Modules.Equipment.Application.Services uses Modules.Character.Application.Contracts✕
- Connections
- 1 pair of types, where a type in Modules.Equipment.Application.Services uses a type in Modules.Character.Application.Contracts.
- The types involved
App.Modules.Equipment.Application.Services.ItemService→App.Modules.Character.Application.Contracts.CharacterRepositoryInterface
- Direction
- Modules.Equipment.Application.Services uses Modules.Character.Application.Contracts, so a change to Modules.Character.Application.Contracts can break Modules.Equipment.Application.Services, while a change to Modules.Equipment.Application.Services can't break Modules.Character.Application.Contracts.
- Position
- Below the diagonal: Modules.Equipment.Application.Services uses a module listed above it, which is the healthy direction.
25→13 Modules.Equipment.Application.Services uses Modules.Equipment.Application.Commands✕
- Connections
- 3 pairs of types, where a type in Modules.Equipment.Application.Services uses a type in Modules.Equipment.Application.Commands.
- The types involved
App.Modules.Equipment.Application.Services.InventoryService→App.Modules.Equipment.Application.Commands.CreateInventoryCommandApp.Modules.Equipment.Application.Services.InventoryService→App.Modules.Equipment.Application.Commands.EquipItemCommandApp.Modules.Equipment.Application.Services.ItemService→App.Modules.Equipment.Application.Commands.CreateItemCommand
- Direction
- Modules.Equipment.Application.Services uses Modules.Equipment.Application.Commands, so a change to Modules.Equipment.Application.Commands can break Modules.Equipment.Application.Services, while a change to Modules.Equipment.Application.Services can't break Modules.Equipment.Application.Commands.
- Position
- Below the diagonal: Modules.Equipment.Application.Services uses a module listed above it, which is the healthy direction.
25→14 Modules.Equipment.Application.Services uses Modules.Equipment.Application.Contracts✕
- Connections
- 3 pairs of types, where a type in Modules.Equipment.Application.Services uses a type in Modules.Equipment.Application.Contracts.
- The types involved
App.Modules.Equipment.Application.Services.InventoryService→App.Modules.Equipment.Application.Contracts.InventoryRepositoryInterfaceApp.Modules.Equipment.Application.Services.ItemService→App.Modules.Equipment.Application.Contracts.ItemPrototypeRepositoryInterfaceApp.Modules.Equipment.Application.Services.ItemService→App.Modules.Equipment.Application.Contracts.ItemRepositoryInterface
- Direction
- Modules.Equipment.Application.Services uses Modules.Equipment.Application.Contracts, so a change to Modules.Equipment.Application.Contracts can break Modules.Equipment.Application.Services, while a change to Modules.Equipment.Application.Services can't break Modules.Equipment.Application.Contracts.
- Position
- Below the diagonal: Modules.Equipment.Application.Services uses a module listed above it, which is the healthy direction.
25→15 Modules.Equipment.Application.Services uses Modules.Equipment.Application.Factories✕
- Connections
- 1 pair of types, where a type in Modules.Equipment.Application.Services uses a type in Modules.Equipment.Application.Factories.
- The types involved
App.Modules.Equipment.Application.Services.ItemService→App.Modules.Equipment.Application.Factories.ItemFactory
- Direction
- Modules.Equipment.Application.Services uses Modules.Equipment.Application.Factories, so a change to Modules.Equipment.Application.Factories can break Modules.Equipment.Application.Services, while a change to Modules.Equipment.Application.Services can't break Modules.Equipment.Application.Factories.
- Position
- Below the diagonal: Modules.Equipment.Application.Services uses a module listed above it, which is the healthy direction.
26→4 Modules.Equipment.Infrastructure.Repositories uses Modules.Equipment.Domain✕
- Connections
- 6 pairs of types, where a type in Modules.Equipment.Infrastructure.Repositories uses a type in Modules.Equipment.Domain.
- The types involved
App.Modules.Equipment.Infrastructure.Repositories.InventoryRepository→App.Modules.Equipment.Domain.InventoryApp.Modules.Equipment.Infrastructure.Repositories.InventoryRepository→App.Modules.Equipment.Domain.InventoryIdApp.Modules.Equipment.Infrastructure.Repositories.ItemPrototypeRepository→App.Modules.Equipment.Domain.ItemPrototypeApp.Modules.Equipment.Infrastructure.Repositories.ItemPrototypeRepository→App.Modules.Equipment.Domain.ItemPrototypeIdApp.Modules.Equipment.Infrastructure.Repositories.ItemRepository→App.Modules.Equipment.Domain.ItemApp.Modules.Equipment.Infrastructure.Repositories.ItemRepository→App.Modules.Equipment.Domain.ItemId
- Direction
- Modules.Equipment.Infrastructure.Repositories uses Modules.Equipment.Domain, so a change to Modules.Equipment.Domain can break Modules.Equipment.Infrastructure.Repositories, while a change to Modules.Equipment.Infrastructure.Repositories can't break Modules.Equipment.Domain.
- Position
- Below the diagonal: Modules.Equipment.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
26→7 Modules.Equipment.Infrastructure.Repositories uses Modules.Character.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Equipment.Infrastructure.Repositories uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Equipment.Infrastructure.Repositories.InventoryRepository→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Equipment.Infrastructure.Repositories uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Equipment.Infrastructure.Repositories, while a change to Modules.Equipment.Infrastructure.Repositories can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Equipment.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
26→8 Modules.Equipment.Infrastructure.Repositories uses Modules.Equipment.Infrastructure.ReconstitutionFactories✕
- Connections
- 3 pairs of types, where a type in Modules.Equipment.Infrastructure.Repositories uses a type in Modules.Equipment.Infrastructure.ReconstitutionFactories.
- The types involved
App.Modules.Equipment.Infrastructure.Repositories.InventoryRepository→App.Modules.Equipment.Infrastructure.ReconstitutionFactories.InventoryReconstitutionFactoryApp.Modules.Equipment.Infrastructure.Repositories.ItemPrototypeRepository→App.Modules.Equipment.Infrastructure.ReconstitutionFactories.ItemPrototypeReconstitutionFactoryApp.Modules.Equipment.Infrastructure.Repositories.ItemRepository→App.Modules.Equipment.Infrastructure.ReconstitutionFactories.ItemReconstitutionFactory
- Direction
- Modules.Equipment.Infrastructure.Repositories uses Modules.Equipment.Infrastructure.ReconstitutionFactories, so a change to Modules.Equipment.Infrastructure.ReconstitutionFactories can break Modules.Equipment.Infrastructure.Repositories, while a change to Modules.Equipment.Infrastructure.Repositories can't break Modules.Equipment.Infrastructure.ReconstitutionFactories.
- Position
- Below the diagonal: Modules.Equipment.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
26→14 Modules.Equipment.Infrastructure.Repositories uses Modules.Equipment.Application.Contracts✕
- Connections
- 3 pairs of types, where a type in Modules.Equipment.Infrastructure.Repositories uses a type in Modules.Equipment.Application.Contracts.
- The types involved
App.Modules.Equipment.Infrastructure.Repositories.InventoryRepository→App.Modules.Equipment.Application.Contracts.InventoryRepositoryInterfaceApp.Modules.Equipment.Infrastructure.Repositories.ItemPrototypeRepository→App.Modules.Equipment.Application.Contracts.ItemPrototypeRepositoryInterfaceApp.Modules.Equipment.Infrastructure.Repositories.ItemRepository→App.Modules.Equipment.Application.Contracts.ItemRepositoryInterface
- Direction
- Modules.Equipment.Infrastructure.Repositories uses Modules.Equipment.Application.Contracts, so a change to Modules.Equipment.Application.Contracts can break Modules.Equipment.Infrastructure.Repositories, while a change to Modules.Equipment.Infrastructure.Repositories can't break Modules.Equipment.Application.Contracts.
- Position
- Below the diagonal: Modules.Equipment.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
27→13 Modules.Equipment.UI.Http.CommandMappers uses Modules.Equipment.Application.Commands✕
- Connections
- 3 pairs of types, where a type in Modules.Equipment.UI.Http.CommandMappers uses a type in Modules.Equipment.Application.Commands.
- The types involved
App.Modules.Equipment.UI.Http.CommandMappers.AddItemToInventoryCommandMapper→App.Modules.Equipment.Application.Commands.AddItemToInventoryCommandApp.Modules.Equipment.UI.Http.CommandMappers.CreateItemCommandMapper→App.Modules.Equipment.Application.Commands.CreateItemCommandApp.Modules.Equipment.UI.Http.CommandMappers.EquipItemCommandMapper→App.Modules.Equipment.Application.Commands.EquipItemCommand
- Direction
- Modules.Equipment.UI.Http.CommandMappers uses Modules.Equipment.Application.Commands, so a change to Modules.Equipment.Application.Commands can break Modules.Equipment.UI.Http.CommandMappers, while a change to Modules.Equipment.UI.Http.CommandMappers can't break Modules.Equipment.Application.Commands.
- Position
- Below the diagonal: Modules.Equipment.UI.Http.CommandMappers uses a module listed above it, which is the healthy direction.
28→5 Modules.Image.Infrastructure.Repositories uses Modules.Image.Domain✕
- Connections
- 3 pairs of types, where a type in Modules.Image.Infrastructure.Repositories uses a type in Modules.Image.Domain.
- The types involved
App.Modules.Image.Infrastructure.Repositories.ImageRepository→App.Modules.Image.Domain.ImageApp.Modules.Image.Infrastructure.Repositories.ImageRepository→App.Modules.Image.Domain.ImageFileApp.Modules.Image.Infrastructure.Repositories.ImageRepository→App.Modules.Image.Domain.ImageId
- Direction
- Modules.Image.Infrastructure.Repositories uses Modules.Image.Domain, so a change to Modules.Image.Domain can break Modules.Image.Infrastructure.Repositories, while a change to Modules.Image.Infrastructure.Repositories can't break Modules.Image.Domain.
- Position
- Below the diagonal: Modules.Image.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
28→7 Modules.Image.Infrastructure.Repositories uses Modules.Character.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Image.Infrastructure.Repositories uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Image.Infrastructure.Repositories.ImageRepository→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Image.Infrastructure.Repositories uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Image.Infrastructure.Repositories, while a change to Modules.Image.Infrastructure.Repositories can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Image.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
28→17 Modules.Image.Infrastructure.Repositories uses Modules.Image.Application.Contracts✕
- Connections
- 1 pair of types, where a type in Modules.Image.Infrastructure.Repositories uses a type in Modules.Image.Application.Contracts.
- The types involved
App.Modules.Image.Infrastructure.Repositories.ImageRepository→App.Modules.Image.Application.Contracts.ImageRepositoryInterface
- Direction
- Modules.Image.Infrastructure.Repositories uses Modules.Image.Application.Contracts, so a change to Modules.Image.Application.Contracts can break Modules.Image.Infrastructure.Repositories, while a change to Modules.Image.Infrastructure.Repositories can't break Modules.Image.Application.Contracts.
- Position
- Below the diagonal: Modules.Image.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
29→20 Modules.Message.Application.Contracts uses Modules.Message.Domain✕
- Connections
- 2 pairs of types, where a type in Modules.Message.Application.Contracts uses a type in Modules.Message.Domain.
- The types involved
App.Modules.Message.Application.Contracts.MessageRepositoryInterface→App.Modules.Message.Domain.MessageApp.Modules.Message.Application.Contracts.MessageRepositoryInterface→App.Modules.Message.Domain.MessageId
- Direction
- Modules.Message.Application.Contracts uses Modules.Message.Domain, so a change to Modules.Message.Domain can break Modules.Message.Application.Contracts, while a change to Modules.Message.Application.Contracts can't break Modules.Message.Domain.
- Position
- Below the diagonal: Modules.Message.Application.Contracts uses a module listed above it, which is the healthy direction.
30→2 Modules.Trade.Application.Commands uses Modules.Generic.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Trade.Application.Commands uses a type in Modules.Generic.Domain.
- The types involved
App.Modules.Trade.Application.Commands.ChangeItemPriceCommand→App.Modules.Generic.Domain.ContainerType
- Direction
- Modules.Trade.Application.Commands uses Modules.Generic.Domain, so a change to Modules.Generic.Domain can break Modules.Trade.Application.Commands, while a change to Modules.Trade.Application.Commands can't break Modules.Generic.Domain.
- Position
- Below the diagonal: Modules.Trade.Application.Commands uses a module listed above it, which is the healthy direction.
30→4 Modules.Trade.Application.Commands uses Modules.Equipment.Domain✕
- Connections
- 7 pairs of types, where a type in Modules.Trade.Application.Commands uses a type in Modules.Equipment.Domain.
- The types involved
App.Modules.Trade.Application.Commands.AddItemToStoreCommand→App.Modules.Equipment.Domain.ItemIdApp.Modules.Trade.Application.Commands.BuyItemCommand→App.Modules.Equipment.Domain.ItemIdApp.Modules.Trade.Application.Commands.ChangeItemPriceCommand→App.Modules.Equipment.Domain.ItemIdApp.Modules.Trade.Application.Commands.ChangeItemPriceCommand→App.Modules.Equipment.Domain.ItemPriceApp.Modules.Trade.Application.Commands.MoveItemToContainerCommand→App.Modules.Equipment.Domain.ItemIdApp.Modules.Trade.Application.Commands.MoveMoneyToContainerCommand→App.Modules.Equipment.Domain.MoneyApp.Modules.Trade.Application.Commands.SellItemCommand→App.Modules.Equipment.Domain.ItemId
- Direction
- Modules.Trade.Application.Commands uses Modules.Equipment.Domain, so a change to Modules.Equipment.Domain can break Modules.Trade.Application.Commands, while a change to Modules.Trade.Application.Commands can't break Modules.Equipment.Domain.
- Position
- Below the diagonal: Modules.Trade.Application.Commands uses a module listed above it, which is the healthy direction.
30→7 Modules.Trade.Application.Commands uses Modules.Character.Domain✕
- Connections
- 7 pairs of types, where a type in Modules.Trade.Application.Commands uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Trade.Application.Commands.AddItemToStoreCommand→App.Modules.Character.Domain.CharacterIdApp.Modules.Trade.Application.Commands.BuyItemCommand→App.Modules.Character.Domain.CharacterIdApp.Modules.Trade.Application.Commands.ChangeItemPriceCommand→App.Modules.Character.Domain.CharacterIdApp.Modules.Trade.Application.Commands.CreateStoreCommand→App.Modules.Character.Domain.CharacterIdApp.Modules.Trade.Application.Commands.MoveItemToContainerCommand→App.Modules.Character.Domain.CharacterIdApp.Modules.Trade.Application.Commands.MoveMoneyToContainerCommand→App.Modules.Character.Domain.CharacterIdApp.Modules.Trade.Application.Commands.SellItemCommand→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Trade.Application.Commands uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Trade.Application.Commands, while a change to Modules.Trade.Application.Commands can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Trade.Application.Commands uses a module listed above it, which is the healthy direction.
30→21 Modules.Trade.Application.Commands uses Modules.Trade.Domain✕
- Connections
- 2 pairs of types, where a type in Modules.Trade.Application.Commands uses a type in Modules.Trade.Domain.
- The types involved
App.Modules.Trade.Application.Commands.BuyItemCommand→App.Modules.Trade.Domain.StoreIdApp.Modules.Trade.Application.Commands.SellItemCommand→App.Modules.Trade.Domain.StoreId
- Direction
- Modules.Trade.Application.Commands uses Modules.Trade.Domain, so a change to Modules.Trade.Domain can break Modules.Trade.Application.Commands, while a change to Modules.Trade.Application.Commands can't break Modules.Trade.Domain.
- Position
- Below the diagonal: Modules.Trade.Application.Commands uses a module listed above it, which is the healthy direction.
31→7 Modules.Trade.Application.Contracts uses Modules.Character.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Trade.Application.Contracts uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Trade.Application.Contracts.StoreRepositoryInterface→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Trade.Application.Contracts uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Trade.Application.Contracts, while a change to Modules.Trade.Application.Contracts can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Trade.Application.Contracts uses a module listed above it, which is the healthy direction.
31→21 Modules.Trade.Application.Contracts uses Modules.Trade.Domain✕
- Connections
- 2 pairs of types, where a type in Modules.Trade.Application.Contracts uses a type in Modules.Trade.Domain.
- The types involved
App.Modules.Trade.Application.Contracts.StoreRepositoryInterface→App.Modules.Trade.Domain.StoreApp.Modules.Trade.Application.Contracts.StoreRepositoryInterface→App.Modules.Trade.Domain.StoreId
- Direction
- Modules.Trade.Application.Contracts uses Modules.Trade.Domain, so a change to Modules.Trade.Domain can break Modules.Trade.Application.Contracts, while a change to Modules.Trade.Application.Contracts can't break Modules.Trade.Domain.
- Position
- Below the diagonal: Modules.Trade.Application.Contracts uses a module listed above it, which is the healthy direction.
32→1 Modules.Trade.Infrastructure.ReconstitutionFactories uses Models✕
- Connections
- 1 pair of types, where a type in Modules.Trade.Infrastructure.ReconstitutionFactories uses a type in Models.
- The types involved
App.Modules.Trade.Infrastructure.ReconstitutionFactories.StoreReconstitutionFactory→App.Models.Store
- Direction
- Modules.Trade.Infrastructure.ReconstitutionFactories uses Models, so a change to Models can break Modules.Trade.Infrastructure.ReconstitutionFactories, while a change to Modules.Trade.Infrastructure.ReconstitutionFactories can't break Models.
- Position
- Below the diagonal: Modules.Trade.Infrastructure.ReconstitutionFactories uses a module listed above it, which is the healthy direction.
32→8 Modules.Trade.Infrastructure.ReconstitutionFactories uses Modules.Equipment.Infrastructure.ReconstitutionFactories✕
- Connections
- 1 pair of types, where a type in Modules.Trade.Infrastructure.ReconstitutionFactories uses a type in Modules.Equipment.Infrastructure.ReconstitutionFactories.
- The types involved
App.Modules.Trade.Infrastructure.ReconstitutionFactories.StoreReconstitutionFactory→App.Modules.Equipment.Infrastructure.ReconstitutionFactories.ItemReconstitutionFactory
- Direction
- Modules.Trade.Infrastructure.ReconstitutionFactories uses Modules.Equipment.Infrastructure.ReconstitutionFactories, so a change to Modules.Equipment.Infrastructure.ReconstitutionFactories can break Modules.Trade.Infrastructure.ReconstitutionFactories, while a change to Modules.Trade.Infrastructure.ReconstitutionFactories can't break Modules.Equipment.Infrastructure.ReconstitutionFactories.
- Position
- Below the diagonal: Modules.Trade.Infrastructure.ReconstitutionFactories uses a module listed above it, which is the healthy direction.
32→21 Modules.Trade.Infrastructure.ReconstitutionFactories uses Modules.Trade.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Trade.Infrastructure.ReconstitutionFactories uses a type in Modules.Trade.Domain.
- The types involved
App.Modules.Trade.Infrastructure.ReconstitutionFactories.StoreReconstitutionFactory→App.Modules.Trade.Domain.Store
- Direction
- Modules.Trade.Infrastructure.ReconstitutionFactories uses Modules.Trade.Domain, so a change to Modules.Trade.Domain can break Modules.Trade.Infrastructure.ReconstitutionFactories, while a change to Modules.Trade.Infrastructure.ReconstitutionFactories can't break Modules.Trade.Domain.
- Position
- Below the diagonal: Modules.Trade.Infrastructure.ReconstitutionFactories uses a module listed above it, which is the healthy direction.
33→19 Modules.Message.Application.Services uses Modules.Message.Application.Commands✕
- Connections
- 1 pair of types, where a type in Modules.Message.Application.Services uses a type in Modules.Message.Application.Commands.
- The types involved
App.Modules.Message.Application.Services.MessageService→App.Modules.Message.Application.Commands.SendMessageCommand
- Direction
- Modules.Message.Application.Services uses Modules.Message.Application.Commands, so a change to Modules.Message.Application.Commands can break Modules.Message.Application.Services, while a change to Modules.Message.Application.Services can't break Modules.Message.Application.Commands.
- Position
- Below the diagonal: Modules.Message.Application.Services uses a module listed above it, which is the healthy direction.
33→29 Modules.Message.Application.Services uses Modules.Message.Application.Contracts✕
- Connections
- 1 pair of types, where a type in Modules.Message.Application.Services uses a type in Modules.Message.Application.Contracts.
- The types involved
App.Modules.Message.Application.Services.MessageService→App.Modules.Message.Application.Contracts.MessageRepositoryInterface
- Direction
- Modules.Message.Application.Services uses Modules.Message.Application.Contracts, so a change to Modules.Message.Application.Contracts can break Modules.Message.Application.Services, while a change to Modules.Message.Application.Services can't break Modules.Message.Application.Contracts.
- Position
- Below the diagonal: Modules.Message.Application.Services uses a module listed above it, which is the healthy direction.
34→14 Modules.Trade.Application.Services uses Modules.Equipment.Application.Contracts✕
- Connections
- 4 pairs of types, where a type in Modules.Trade.Application.Services uses a type in Modules.Equipment.Application.Contracts.
- The types involved
App.Modules.Trade.Application.Services.ManageStoreService→App.Modules.Equipment.Application.Contracts.InventoryRepositoryInterfaceApp.Modules.Trade.Application.Services.TradeService→App.Modules.Equipment.Application.Contracts.InventoryRepositoryInterfaceApp.Modules.Trade.Application.Services.TradeService→App.Modules.Equipment.Application.Contracts.ItemPrototypeRepositoryInterfaceApp.Modules.Trade.Application.Services.TradeService→App.Modules.Equipment.Application.Contracts.ItemRepositoryInterface
- Direction
- Modules.Trade.Application.Services uses Modules.Equipment.Application.Contracts, so a change to Modules.Equipment.Application.Contracts can break Modules.Trade.Application.Services, while a change to Modules.Trade.Application.Services can't break Modules.Equipment.Application.Contracts.
- Position
- Below the diagonal: Modules.Trade.Application.Services uses a module listed above it, which is the healthy direction.
34→21 Modules.Trade.Application.Services uses Modules.Trade.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Trade.Application.Services uses a type in Modules.Trade.Domain.
- The types involved
App.Modules.Trade.Application.Services.CreateStoreService→App.Modules.Trade.Domain.Store
- Direction
- Modules.Trade.Application.Services uses Modules.Trade.Domain, so a change to Modules.Trade.Domain can break Modules.Trade.Application.Services, while a change to Modules.Trade.Application.Services can't break Modules.Trade.Domain.
- Position
- Below the diagonal: Modules.Trade.Application.Services uses a module listed above it, which is the healthy direction.
34→26 Modules.Trade.Application.Services uses Modules.Equipment.Infrastructure.Repositories✕
- Connections
- 1 pair of types, where a type in Modules.Trade.Application.Services uses a type in Modules.Equipment.Infrastructure.Repositories.
- The types involved
App.Modules.Trade.Application.Services.ManageStoreService→App.Modules.Equipment.Infrastructure.Repositories.ItemRepository
- Direction
- Modules.Trade.Application.Services uses Modules.Equipment.Infrastructure.Repositories, so a change to Modules.Equipment.Infrastructure.Repositories can break Modules.Trade.Application.Services, while a change to Modules.Trade.Application.Services can't break Modules.Equipment.Infrastructure.Repositories.
- Position
- Below the diagonal: Modules.Trade.Application.Services uses a module listed above it, which is the healthy direction.
34→30 Modules.Trade.Application.Services uses Modules.Trade.Application.Commands✕
- Connections
- 6 pairs of types, where a type in Modules.Trade.Application.Services uses a type in Modules.Trade.Application.Commands.
- The types involved
App.Modules.Trade.Application.Services.CreateStoreService→App.Modules.Trade.Application.Commands.CreateStoreCommandApp.Modules.Trade.Application.Services.ManageStoreService→App.Modules.Trade.Application.Commands.ChangeItemPriceCommandApp.Modules.Trade.Application.Services.ManageStoreService→App.Modules.Trade.Application.Commands.MoveItemToContainerCommandApp.Modules.Trade.Application.Services.ManageStoreService→App.Modules.Trade.Application.Commands.MoveMoneyToContainerCommandApp.Modules.Trade.Application.Services.TradeService→App.Modules.Trade.Application.Commands.BuyItemCommandApp.Modules.Trade.Application.Services.TradeService→App.Modules.Trade.Application.Commands.SellItemCommand
- Direction
- Modules.Trade.Application.Services uses Modules.Trade.Application.Commands, so a change to Modules.Trade.Application.Commands can break Modules.Trade.Application.Services, while a change to Modules.Trade.Application.Services can't break Modules.Trade.Application.Commands.
- Position
- Below the diagonal: Modules.Trade.Application.Services uses a module listed above it, which is the healthy direction.
34→31 Modules.Trade.Application.Services uses Modules.Trade.Application.Contracts✕
- Connections
- 3 pairs of types, where a type in Modules.Trade.Application.Services uses a type in Modules.Trade.Application.Contracts.
- The types involved
App.Modules.Trade.Application.Services.CreateStoreService→App.Modules.Trade.Application.Contracts.StoreRepositoryInterfaceApp.Modules.Trade.Application.Services.ManageStoreService→App.Modules.Trade.Application.Contracts.StoreRepositoryInterfaceApp.Modules.Trade.Application.Services.TradeService→App.Modules.Trade.Application.Contracts.StoreRepositoryInterface
- Direction
- Modules.Trade.Application.Services uses Modules.Trade.Application.Contracts, so a change to Modules.Trade.Application.Contracts can break Modules.Trade.Application.Services, while a change to Modules.Trade.Application.Services can't break Modules.Trade.Application.Contracts.
- Position
- Below the diagonal: Modules.Trade.Application.Services uses a module listed above it, which is the healthy direction.
35→7 Modules.Trade.Infrastructure.Repositories uses Modules.Character.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Trade.Infrastructure.Repositories uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Trade.Infrastructure.Repositories.StoreRepository→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Trade.Infrastructure.Repositories uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Trade.Infrastructure.Repositories, while a change to Modules.Trade.Infrastructure.Repositories can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Trade.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
35→21 Modules.Trade.Infrastructure.Repositories uses Modules.Trade.Domain✕
- Connections
- 2 pairs of types, where a type in Modules.Trade.Infrastructure.Repositories uses a type in Modules.Trade.Domain.
- The types involved
App.Modules.Trade.Infrastructure.Repositories.StoreRepository→App.Modules.Trade.Domain.StoreApp.Modules.Trade.Infrastructure.Repositories.StoreRepository→App.Modules.Trade.Domain.StoreId
- Direction
- Modules.Trade.Infrastructure.Repositories uses Modules.Trade.Domain, so a change to Modules.Trade.Domain can break Modules.Trade.Infrastructure.Repositories, while a change to Modules.Trade.Infrastructure.Repositories can't break Modules.Trade.Domain.
- Position
- Below the diagonal: Modules.Trade.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
35→31 Modules.Trade.Infrastructure.Repositories uses Modules.Trade.Application.Contracts✕
- Connections
- 1 pair of types, where a type in Modules.Trade.Infrastructure.Repositories uses a type in Modules.Trade.Application.Contracts.
- The types involved
App.Modules.Trade.Infrastructure.Repositories.StoreRepository→App.Modules.Trade.Application.Contracts.StoreRepositoryInterface
- Direction
- Modules.Trade.Infrastructure.Repositories uses Modules.Trade.Application.Contracts, so a change to Modules.Trade.Application.Contracts can break Modules.Trade.Infrastructure.Repositories, while a change to Modules.Trade.Infrastructure.Repositories can't break Modules.Trade.Application.Contracts.
- Position
- Below the diagonal: Modules.Trade.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
35→32 Modules.Trade.Infrastructure.Repositories uses Modules.Trade.Infrastructure.ReconstitutionFactories✕
- Connections
- 1 pair of types, where a type in Modules.Trade.Infrastructure.Repositories uses a type in Modules.Trade.Infrastructure.ReconstitutionFactories.
- The types involved
App.Modules.Trade.Infrastructure.Repositories.StoreRepository→App.Modules.Trade.Infrastructure.ReconstitutionFactories.StoreReconstitutionFactory
- Direction
- Modules.Trade.Infrastructure.Repositories uses Modules.Trade.Infrastructure.ReconstitutionFactories, so a change to Modules.Trade.Infrastructure.ReconstitutionFactories can break Modules.Trade.Infrastructure.Repositories, while a change to Modules.Trade.Infrastructure.Repositories can't break Modules.Trade.Infrastructure.ReconstitutionFactories.
- Position
- Below the diagonal: Modules.Trade.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
36→3 Modules.Character.Application.Services uses Modules.Level.Application.Services✕
- Connections
- 1 pair of types, where a type in Modules.Character.Application.Services uses a type in Modules.Level.Application.Services.
- The types involved
App.Modules.Character.Application.Services.CharacterService→App.Modules.Level.Application.Services.LevelService
- Direction
- Modules.Character.Application.Services uses Modules.Level.Application.Services, so a change to Modules.Level.Application.Services can break Modules.Character.Application.Services, while a change to Modules.Character.Application.Services can't break Modules.Level.Application.Services.
- Position
- Below the diagonal: Modules.Character.Application.Services uses a module listed above it, which is the healthy direction.
36→5 Modules.Character.Application.Services uses Modules.Image.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Character.Application.Services uses a type in Modules.Image.Domain.
- The types involved
App.Modules.Character.Application.Services.CharacterService→App.Modules.Image.Domain.Image
- Direction
- Modules.Character.Application.Services uses Modules.Image.Domain, so a change to Modules.Image.Domain can break Modules.Character.Application.Services, while a change to Modules.Character.Application.Services can't break Modules.Image.Domain.
- Position
- Below the diagonal: Modules.Character.Application.Services uses a module listed above it, which is the healthy direction.
36→7 Modules.Character.Application.Services uses Modules.Character.Domain✕
- Connections
- 2 pairs of types, where a type in Modules.Character.Application.Services uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Character.Application.Services.CharacterService→App.Modules.Character.Domain.CharacterApp.Modules.Character.Application.Services.CharacterService→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Character.Application.Services uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Character.Application.Services, while a change to Modules.Character.Application.Services can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Character.Application.Services uses a module listed above it, which is the healthy direction.
36→9 Modules.Character.Application.Services uses Modules.Battle.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Character.Application.Services uses a type in Modules.Battle.Domain.
- The types involved
App.Modules.Character.Application.Services.CharacterService→App.Modules.Battle.Domain.BattleId
- Direction
- Modules.Character.Application.Services uses Modules.Battle.Domain, so a change to Modules.Battle.Domain can break Modules.Character.Application.Services, while a change to Modules.Character.Application.Services can't break Modules.Battle.Domain.
- Position
- Below the diagonal: Modules.Character.Application.Services uses a module listed above it, which is the healthy direction.
36→10 Modules.Character.Application.Services uses Modules.Character.Application.Commands✕
- Connections
- 4 pairs of types, where a type in Modules.Character.Application.Services uses a type in Modules.Character.Application.Commands.
- The types involved
App.Modules.Character.Application.Services.CharacterService→App.Modules.Character.Application.Commands.AttackCharacterCommandApp.Modules.Character.Application.Services.CharacterService→App.Modules.Character.Application.Commands.CreateCharacterCommandApp.Modules.Character.Application.Services.CharacterService→App.Modules.Character.Application.Commands.IncreaseAttributeCommandApp.Modules.Character.Application.Services.CharacterService→App.Modules.Character.Application.Commands.MoveCharacterCommand
- Direction
- Modules.Character.Application.Services uses Modules.Character.Application.Commands, so a change to Modules.Character.Application.Commands can break Modules.Character.Application.Services, while a change to Modules.Character.Application.Services can't break Modules.Character.Application.Commands.
- Position
- Below the diagonal: Modules.Character.Application.Services uses a module listed above it, which is the healthy direction.
36→11 Modules.Character.Application.Services uses Modules.Character.Application.Contracts✕
- Connections
- 2 pairs of types, where a type in Modules.Character.Application.Services uses a type in Modules.Character.Application.Contracts.
- The types involved
App.Modules.Character.Application.Services.CharacterService→App.Modules.Character.Application.Contracts.CharacterRepositoryInterfaceApp.Modules.Character.Application.Services.CharacterService→App.Modules.Character.Application.Contracts.RaceRepositoryInterface
- Direction
- Modules.Character.Application.Services uses Modules.Character.Application.Contracts, so a change to Modules.Character.Application.Contracts can break Modules.Character.Application.Services, while a change to Modules.Character.Application.Services can't break Modules.Character.Application.Contracts.
- Position
- Below the diagonal: Modules.Character.Application.Services uses a module listed above it, which is the healthy direction.
36→22 Modules.Character.Application.Services uses Modules.Battle.Application.Contracts✕
- Connections
- 1 pair of types, where a type in Modules.Character.Application.Services uses a type in Modules.Battle.Application.Contracts.
- The types involved
App.Modules.Character.Application.Services.CharacterService→App.Modules.Battle.Application.Contracts.BattleRepositoryInterface
- Direction
- Modules.Character.Application.Services uses Modules.Battle.Application.Contracts, so a change to Modules.Battle.Application.Contracts can break Modules.Character.Application.Services, while a change to Modules.Character.Application.Services can't break Modules.Battle.Application.Contracts.
- Position
- Below the diagonal: Modules.Character.Application.Services uses a module listed above it, which is the healthy direction.
36→23 Modules.Character.Application.Services uses Modules.Character.Application.Factories✕
- Connections
- 1 pair of types, where a type in Modules.Character.Application.Services uses a type in Modules.Character.Application.Factories.
- The types involved
App.Modules.Character.Application.Services.CharacterService→App.Modules.Character.Application.Factories.CharacterFactory
- Direction
- Modules.Character.Application.Services uses Modules.Character.Application.Factories, so a change to Modules.Character.Application.Factories can break Modules.Character.Application.Services, while a change to Modules.Character.Application.Services can't break Modules.Character.Application.Factories.
- Position
- Below the diagonal: Modules.Character.Application.Services uses a module listed above it, which is the healthy direction.
36→25 Modules.Character.Application.Services uses Modules.Equipment.Application.Services✕
- Connections
- 1 pair of types, where a type in Modules.Character.Application.Services uses a type in Modules.Equipment.Application.Services.
- The types involved
App.Modules.Character.Application.Services.CharacterService→App.Modules.Equipment.Application.Services.InventoryService
- Direction
- Modules.Character.Application.Services uses Modules.Equipment.Application.Services, so a change to Modules.Equipment.Application.Services can break Modules.Character.Application.Services, while a change to Modules.Character.Application.Services can't break Modules.Equipment.Application.Services.
- Position
- Below the diagonal: Modules.Character.Application.Services uses a module listed above it, which is the healthy direction.
36→34 Modules.Character.Application.Services uses Modules.Trade.Application.Services✕
- Connections
- 1 pair of types, where a type in Modules.Character.Application.Services uses a type in Modules.Trade.Application.Services.
- The types involved
App.Modules.Character.Application.Services.CharacterService→App.Modules.Trade.Application.Services.CreateStoreService
- Direction
- Modules.Character.Application.Services uses Modules.Trade.Application.Services, so a change to Modules.Trade.Application.Services can break Modules.Character.Application.Services, while a change to Modules.Character.Application.Services can't break Modules.Trade.Application.Services.
- Position
- Below the diagonal: Modules.Character.Application.Services uses a module listed above it, which is the healthy direction.
37→7 Modules.Image.Application.Services uses Modules.Character.Domain✕
- Connections
- 1 pair of types, where a type in Modules.Image.Application.Services uses a type in Modules.Character.Domain.
- The types involved
App.Modules.Image.Application.Services.ProfilePictureService→App.Modules.Character.Domain.CharacterId
- Direction
- Modules.Image.Application.Services uses Modules.Character.Domain, so a change to Modules.Character.Domain can break Modules.Image.Application.Services, while a change to Modules.Image.Application.Services can't break Modules.Character.Domain.
- Position
- Below the diagonal: Modules.Image.Application.Services uses a module listed above it, which is the healthy direction.
37→16 Modules.Image.Application.Services uses Modules.Image.Application.Commands✕
- Connections
- 1 pair of types, where a type in Modules.Image.Application.Services uses a type in Modules.Image.Application.Commands.
- The types involved
App.Modules.Image.Application.Services.ProfilePictureService→App.Modules.Image.Application.Commands.AddImageCommand
- Direction
- Modules.Image.Application.Services uses Modules.Image.Application.Commands, so a change to Modules.Image.Application.Commands can break Modules.Image.Application.Services, while a change to Modules.Image.Application.Services can't break Modules.Image.Application.Commands.
- Position
- Below the diagonal: Modules.Image.Application.Services uses a module listed above it, which is the healthy direction.
37→17 Modules.Image.Application.Services uses Modules.Image.Application.Contracts✕
- Connections
- 1 pair of types, where a type in Modules.Image.Application.Services uses a type in Modules.Image.Application.Contracts.
- The types involved
App.Modules.Image.Application.Services.ProfilePictureService→App.Modules.Image.Application.Contracts.ImageRepositoryInterface
- Direction
- Modules.Image.Application.Services uses Modules.Image.Application.Contracts, so a change to Modules.Image.Application.Contracts can break Modules.Image.Application.Services, while a change to Modules.Image.Application.Services can't break Modules.Image.Application.Contracts.
- Position
- Below the diagonal: Modules.Image.Application.Services uses a module listed above it, which is the healthy direction.
37→18 Modules.Image.Application.Services uses Modules.Image.Application.Factories✕
- Connections
- 1 pair of types, where a type in Modules.Image.Application.Services uses a type in Modules.Image.Application.Factories.
- The types involved
App.Modules.Image.Application.Services.ProfilePictureService→App.Modules.Image.Application.Factories.ImageFactory
- Direction
- Modules.Image.Application.Services uses Modules.Image.Application.Factories, so a change to Modules.Image.Application.Factories can break Modules.Image.Application.Services, while a change to Modules.Image.Application.Services can't break Modules.Image.Application.Factories.
- Position
- Below the diagonal: Modules.Image.Application.Services uses a module listed above it, which is the healthy direction.
37→36 Modules.Image.Application.Services uses Modules.Character.Application.Services✕
- Connections
- 1 pair of types, where a type in Modules.Image.Application.Services uses a type in Modules.Character.Application.Services.
- The types involved
App.Modules.Image.Application.Services.ProfilePictureService→App.Modules.Character.Application.Services.CharacterService
- Direction
- Modules.Image.Application.Services uses Modules.Character.Application.Services, so a change to Modules.Character.Application.Services can break Modules.Image.Application.Services, while a change to Modules.Image.Application.Services can't break Modules.Character.Application.Services.
- Position
- Below the diagonal: Modules.Image.Application.Services uses a module listed above it, which is the healthy direction.
38→3 Http.Controllers uses Modules.Level.Application.Services✕
- Connections
- 1 pair of types, where a type in Http.Controllers uses a type in Modules.Level.Application.Services.
- The types involved
App.Http.Controllers.InventoryController→App.Modules.Level.Application.Services.LevelService
- Direction
- Http.Controllers uses Modules.Level.Application.Services, so a change to Modules.Level.Application.Services can break Http.Controllers, while a change to Http.Controllers can't break Modules.Level.Application.Services.
- Position
- Below the diagonal: Http.Controllers uses a module listed above it, which is the healthy direction.
38→25 Http.Controllers uses Modules.Equipment.Application.Services✕
- Connections
- 2 pairs of types, where a type in Http.Controllers uses a type in Modules.Equipment.Application.Services.
- The types involved
App.Http.Controllers.InventoryController→App.Modules.Equipment.Application.Services.InventoryServiceApp.Http.Controllers.ItemCreateController→App.Modules.Equipment.Application.Services.ItemService
- Direction
- Http.Controllers uses Modules.Equipment.Application.Services, so a change to Modules.Equipment.Application.Services can break Http.Controllers, while a change to Http.Controllers can't break Modules.Equipment.Application.Services.
- Position
- Below the diagonal: Http.Controllers uses a module listed above it, which is the healthy direction.
38→27 Http.Controllers uses Modules.Equipment.UI.Http.CommandMappers✕
- Connections
- 2 pairs of types, where a type in Http.Controllers uses a type in Modules.Equipment.UI.Http.CommandMappers.
- The types involved
App.Http.Controllers.InventoryController→App.Modules.Equipment.UI.Http.CommandMappers.EquipItemCommandMapperApp.Http.Controllers.ItemCreateController→App.Modules.Equipment.UI.Http.CommandMappers.CreateItemCommandMapper
- Direction
- Http.Controllers uses Modules.Equipment.UI.Http.CommandMappers, so a change to Modules.Equipment.UI.Http.CommandMappers can break Http.Controllers, while a change to Http.Controllers can't break Modules.Equipment.UI.Http.CommandMappers.
- Position
- Below the diagonal: Http.Controllers uses a module listed above it, which is the healthy direction.
38→33 Http.Controllers uses Modules.Message.Application.Services✕
- Connections
- 1 pair of types, where a type in Http.Controllers uses a type in Modules.Message.Application.Services.
- The types involved
App.Http.Controllers.CharacterMessageController→App.Modules.Message.Application.Services.MessageService
- Direction
- Http.Controllers uses Modules.Message.Application.Services, so a change to Modules.Message.Application.Services can break Http.Controllers, while a change to Http.Controllers can't break Modules.Message.Application.Services.
- Position
- Below the diagonal: Http.Controllers uses a module listed above it, which is the healthy direction.
38→36 Http.Controllers uses Modules.Character.Application.Services✕
- Connections
- 1 pair of types, where a type in Http.Controllers uses a type in Modules.Character.Application.Services.
- The types involved
App.Http.Controllers.CharacterController→App.Modules.Character.Application.Services.CharacterService
- Direction
- Http.Controllers uses Modules.Character.Application.Services, so a change to Modules.Character.Application.Services can break Http.Controllers, while a change to Http.Controllers can't break Modules.Character.Application.Services.
- Position
- Below the diagonal: Http.Controllers uses a module listed above it, which is the healthy direction.
38→37 Http.Controllers uses Modules.Image.Application.Services✕
- Connections
- 1 pair of types, where a type in Http.Controllers uses a type in Modules.Image.Application.Services.
- The types involved
App.Http.Controllers.ProfilePictureController→App.Modules.Image.Application.Services.ProfilePictureService
- Direction
- Http.Controllers uses Modules.Image.Application.Services, so a change to Modules.Image.Application.Services can break Http.Controllers, while a change to Http.Controllers can't break Modules.Image.Application.Services.
- Position
- Below the diagonal: Http.Controllers uses a module listed above it, which is the healthy direction.
39→25 Http.Controllers.Api uses Modules.Equipment.Application.Services✕
- Connections
- 1 pair of types, where a type in Http.Controllers.Api uses a type in Modules.Equipment.Application.Services.
- The types involved
App.Http.Controllers.Api.ManageInventoryController→App.Modules.Equipment.Application.Services.InventoryService
- Direction
- Http.Controllers.Api uses Modules.Equipment.Application.Services, so a change to Modules.Equipment.Application.Services can break Http.Controllers.Api, while a change to Http.Controllers.Api can't break Modules.Equipment.Application.Services.
- Position
- Below the diagonal: Http.Controllers.Api uses a module listed above it, which is the healthy direction.
39→27 Http.Controllers.Api uses Modules.Equipment.UI.Http.CommandMappers✕
- Connections
- 1 pair of types, where a type in Http.Controllers.Api uses a type in Modules.Equipment.UI.Http.CommandMappers.
- The types involved
App.Http.Controllers.Api.ManageInventoryController→App.Modules.Equipment.UI.Http.CommandMappers.EquipItemCommandMapper
- Direction
- Http.Controllers.Api uses Modules.Equipment.UI.Http.CommandMappers, so a change to Modules.Equipment.UI.Http.CommandMappers can break Http.Controllers.Api, while a change to Http.Controllers.Api can't break Modules.Equipment.UI.Http.CommandMappers.
- Position
- Below the diagonal: Http.Controllers.Api uses a module listed above it, which is the healthy direction.
39→34 Http.Controllers.Api uses Modules.Trade.Application.Services✕
- Connections
- 2 pairs of types, where a type in Http.Controllers.Api uses a type in Modules.Trade.Application.Services.
- The types involved
App.Http.Controllers.Api.ManageStoreController→App.Modules.Trade.Application.Services.ManageStoreServiceApp.Http.Controllers.Api.TradeController→App.Modules.Trade.Application.Services.TradeService
- Direction
- Http.Controllers.Api uses Modules.Trade.Application.Services, so a change to Modules.Trade.Application.Services can break Http.Controllers.Api, while a change to Http.Controllers.Api can't break Modules.Trade.Application.Services.
- Position
- Below the diagonal: Http.Controllers.Api uses a module listed above it, which is the healthy direction.
39→38 Http.Controllers.Api uses Http.Controllers✕
- Connections
- 3 pairs of types, where a type in Http.Controllers.Api uses a type in Http.Controllers.
- The types involved
App.Http.Controllers.Api.ManageInventoryController→App.Http.Controllers.ControllerApp.Http.Controllers.Api.ManageStoreController→App.Http.Controllers.ControllerApp.Http.Controllers.Api.TradeController→App.Http.Controllers.Controller
- Direction
- Http.Controllers.Api uses Http.Controllers, so a change to Http.Controllers can break Http.Controllers.Api, while a change to Http.Controllers.Api can't break Http.Controllers.
- Position
- Below the diagonal: Http.Controllers.Api uses a module listed above it, which is the healthy direction.
40→6 Http.Controllers.Auth uses Modules.User.Application.Services✕
- Connections
- 1 pair of types, where a type in Http.Controllers.Auth uses a type in Modules.User.Application.Services.
- The types involved
App.Http.Controllers.Auth.RegisterController→App.Modules.User.Application.Services.UserService
- Direction
- Http.Controllers.Auth uses Modules.User.Application.Services, so a change to Modules.User.Application.Services can break Http.Controllers.Auth, while a change to Http.Controllers.Auth can't break Modules.User.Application.Services.
- Position
- Below the diagonal: Http.Controllers.Auth uses a module listed above it, which is the healthy direction.
40→38 Http.Controllers.Auth uses Http.Controllers✕
- Connections
- 6 pairs of types, where a type in Http.Controllers.Auth uses a type in Http.Controllers.
- The types involved
App.Http.Controllers.Auth.ConfirmPasswordController→App.Http.Controllers.ControllerApp.Http.Controllers.Auth.ForgotPasswordController→App.Http.Controllers.ControllerApp.Http.Controllers.Auth.LoginController→App.Http.Controllers.ControllerApp.Http.Controllers.Auth.RegisterController→App.Http.Controllers.ControllerApp.Http.Controllers.Auth.ResetPasswordController→App.Http.Controllers.ControllerApp.Http.Controllers.Auth.VerificationController→App.Http.Controllers.Controller
- Direction
- Http.Controllers.Auth uses Http.Controllers, so a change to Http.Controllers can break Http.Controllers.Auth, while a change to Http.Controllers.Auth can't break Http.Controllers.
- Position
- Below the diagonal: Http.Controllers.Auth uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 91 | High / Critical |
| A02:2025 — Security Misconfiguration | 9 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
| A05:2025 — Injection | 1 | Medium |
Roadmap
Top priorities: Resolve the 2 Abandoned package finding(s) in Dependency Hygiene; Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Abandoned package finding(s) in Dependency Hygiene. | +5.0 pts | Low | Dependency Hygiene |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.9 pts | Low | ADR Quality |
| Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +4.1 pts | Medium | Security & performance tooling |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +4.1 pts | Medium | DR & Backup |
| Add a test runner (vitest / jest / playwright) and eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI. | +4.1 pts | Medium | Tooling |
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +3.2 pts | Medium | Type Safety |
| Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package. | +3.2 pts | Medium | Large Files |
| Resolve the 39 Orphaned file finding(s) in Knowledge Freshness — start with Character.php (2), DataRowsTableSeeder.php, TranslationsTableSeeder.php. | +2.8 pts | Medium | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.0 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 6.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| database/seeders/DataRowsTableSeeder.php | 7.4 | Near-clean | Cyclomatic Complexity: DataRowsTableSeeder.run (cyclomatic 22) |
| app/Modules/Equipment/Domain/Inventory.php | 7.8 | Near-clean | Code Duplication: Duplicated block (13 lines × 2) |
| app/Modules/Trade/Application/Services/ManageStoreService.php | 7.8 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| database/seeders/TranslationsTableSeeder.php | 7.8 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| database/migrations/2017_05_16_144929_create_battles_table.php | 7.8 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| composer.json | 7.9 | Near-clean | Platform End-of-Life: End-of-life framework: Laravel 8 |
| database/migrations/2020_02_29_205331_create_inventories.php | 8.2 | Near-clean | Explicit Debt: TodoComment |
| app/Models/Character.php | 8.5 | Near-clean | God Classes: TooManyMethods: Character |
| app/Modules/Character/Domain/Character.php | 8.5 | Near-clean | God Classes: TooManyMethods: Character |
| database/seeders/MenuItemsTableSeeder.php | 8.5 | Near-clean | God Classes: MethodTooLong: MenuItemsTableSeeder.run |
| database/seeders/SettingsTableSeeder.php | 8.5 | Near-clean | God Classes: MethodTooLong: SettingsTableSeeder.run |
| database/migrations/2019_08_31_182034_create_items_table.php | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| database/migrations/2017_05_16_181844_create_battle_turns_table.php | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 76 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 76 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, 226 of 246 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its Composer package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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 (4 contributor(s) across 376 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 3 hold 0.3% 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.
- D19 Documentation Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — 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.
- D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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)` (9824 LoC, 229 module-visible types across 64 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.
- 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 Laravel's service container, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c apt-get update && apt-get upgrade -y && apt-get install -y build-essential git curl libpng-dev libonig-dev libxml2-dev libzip-dev zip unzip nodejs yarn" did not complete successfully: exit code: 100; runtime evidence skipped.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's PHP, Vue components is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's PHP, Vue components 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 and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin 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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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.
- 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.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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 DataRowsTableSeeder.run at 22.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with DataRowsTableSeeder.run (cyclomatic 22). — Refactoring it lifts Cyclomatic Complexity from 9.5 to about 10.0/10.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was DataRowsTableSeeder.run at 21.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with DataRowsTableSeeder.run (cognitive 21). — Refactoring it lifts Cognitive Complexity from 9.6 to about 10.0/10.
D3 · God Classes
5 god class(es) detected.
What to do
- Resolve the 3 MethodTooLong finding(s) in God Classes — start with DataRowsTableSeeder.php, MenuItemsTableSeeder.php, SettingsTableSeeder.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with Character.php (2). — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
17 duplicated block group(s) detected.
What to do
- Resolve the 3 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with ManageStoreService.php (2), TranslationsTableSeeder.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with 2017_05_16_181844_create_battle_turns_table.php, Inventory.php, BuyItemCommandMapper.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with 2017_05_16_144929_create_battles_table.php, 2017_05_16_181330_create_battle_rounds_table.php, EquipItemCommandMapper.php. — One of this dimension's main actionable groups (3 warning-level).
D6 · Cohesion (LCOM4)
0 of 23 classes have LCOM4 above 3.
D12 · Dependency Hygiene
2 outdated, 2 abandoned direct Composer dependencies. 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
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 86 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 45 package(s) under `packages-dev` are not installed for a consumer and are excluded. ★ COVERAGE OF THIS VERDICT: it grades this repository's Composer package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
1 deducted task-comment markers across 12802 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 1 TodoComment finding(s) in Explicit Debt — start with 2020_02_29_205331_create_inventories.php. — One of this dimension's main actionable groups (1 warning-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
18 domain type(s) cross context boundaries across 7 contexts; they are measured and withheld (not published, not scored). Contexts: Battle, Character, Equipment, Image, Level, Message, Trade.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D30 · Dependency Vulnerabilities
91 finding(s): 14 critical, 48 high, 22 medium, 7 low.
What to do
- Resolve the 47 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (40), REDACTED (7). — One of this dimension's main actionable groups (47 issue-level).
- Resolve the 13 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10), REDACTED (3). — One of this dimension's main actionable groups (13 issue-level).
- Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
9 finding(s): 0 critical, 4 high, 4 medium, 1 low.
What to do
- Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
39 of 39 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is database/seeders/DataRowsTableSeeder.php. Counted over 39 of the 275 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 39 Orphaned file finding(s) in Knowledge Freshness — start with Character.php (2), DataRowsTableSeeder.php, TranslationsTableSeeder.php. — One of this dimension's main actionable groups (39 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: login.blade.php↔register.blade.php 90%; UserFactory.php↔CharacterSeeder.php 62%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with login.blade.php, UserFactory.php. — One of this dimension's main actionable groups (2 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 1 end-of-life framework(s), read from 0 platform declaration(s) and 9 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 1 End-of-life framework finding(s) in Platform End-of-Life — start with composer.json. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×8) — resources/views/character/create.blade.php:16, resources/views/character/partials/character-display.blade.php:18, resources/views/character/partials/equipment-item-mutable.blade.php:4, …
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×2) — resources/views/character/create.blade.php:37, resources/views/character/message/index.blade.php:17
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — resources/views/character/partials/character-display.blade.php:29
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — resources/views/base.blade.php:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — resources/views/base.blade.php:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (eslint-plugin-vuejs-accessibility) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 44 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — package.json:12
What to do
- Enforce accessibility in the toolchain: add eslint-plugin-vuejs-accessibility, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / REDACTED Manager, HashiCorp Vault — not only APP_KEY in .env) and encrypt the most sensitive columns (Eloquent 'encrypted' casts, CipherSweet) — partial coverage still leaves gaps.
- Enforce HTTPS (URL::forceScheme('https') / URL::forceHttps() in Laravel, or requires_channel: https / route schemes in Symfony) so data in transit is always encrypted.
C2 · Access Controls
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
- `CharacterService.attack` saves ``, `Battle` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — app/Modules/Character/Application/Services/CharacterService.php:114
- `ItemService.create` saves `itemRepository`, `characterRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — app/Modules/Equipment/Application/Services/ItemService.php:46
- `ManageStoreService.moveItemToStore` saves `inventoryRepository`, `storeRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — app/Modules/Trade/Application/Services/ManageStoreService.php:40
- `ManageStoreService.moveItemToInventory` saves `inventoryRepository`, `storeRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — app/Modules/Trade/Application/Services/ManageStoreService.php:52
- `ManageStoreService.moveMoneyToStore` saves `inventoryRepository`, `storeRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — app/Modules/Trade/Application/Services/ManageStoreService.php:81
- `ManageStoreService.moveMoneyToInventory` saves `inventoryRepository`, `storeRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — app/Modules/Trade/Application/Services/ManageStoreService.php:93
- `TradeService.buyItem` saves `inventoryRepository`, `storeRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — app/Modules/Trade/Application/Services/TradeService.php:48
- `TradeService.sellItem` saves `itemRepository`, `inventoryRepository`, `storeRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — app/Modules/Trade/Application/Services/TradeService.php:62
What to do
- Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
DM11 · Constructible invalid state
- `Battle`'s public constructor takes `locationId`, `victorXpGained` 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 `Battle` 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. — app/Modules/Battle/Domain/Battle.php:47
- `BattleRound`'s public constructor takes `id` 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 `BattleRound` 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. — app/Modules/Battle/Domain/BattleRound.php:33
- `BattleTurn`'s public constructor takes `id` 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 `BattleTurn` 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. — app/Modules/Battle/Domain/BattleTurn.php:34
- `Character`'s public constructor takes `raceId`, `levelId`, `locationId`, `name`, … 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 `Character` 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. — app/Modules/Character/Domain/Character.php:78
- `Race`'s public constructor takes `id`, `startingLocationId`, `name`, `description`, … 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 `Race` 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. — app/Modules/Character/Domain/Race.php:37
- `Item`'s public constructor takes `name`, `description`, `imageFilePath` 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 `Item` 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. — app/Modules/Equipment/Domain/Item.php:48
- `ItemPrototype`'s public constructor takes `name`, `description`, `imageFilePath` 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 `ItemPrototype` 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. — app/Modules/Equipment/Domain/ItemPrototype.php:39
- `Level`'s public constructor takes `id`, `currentLevelThreshHold`, `nextLevelXpThreshold` 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 `Level` 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. — app/Modules/Level/Domain/Level.php:22
- `Message`'s public constructor takes `content`, `state` 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 `Message` 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. — app/Modules/Message/Domain/Message.php:34
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.
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
- `Battle` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/Battle.php:19
- `BattleRound` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/BattleRound.php:9
- `BattleTurn` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/BattleTurn.php:9
- `Character` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/Character.php:42
- `Image` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/Image.php:15
- `Inventory` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/Inventory.php:18
- `Item` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/Item.php:27
- `ItemPrototype` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/ItemPrototype.php:17
- `Message` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/Message.php:17
- `Store` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/Store.php:19
- `Race` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Modules/Character/Domain/Race.php:6
- `ItemPrototype` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Modules/Equipment/Domain/ItemPrototype.php:8
- `Image` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Modules/Image/Domain/Image.php:7
- `Level` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Modules/Level/Domain/Level.php:7
- `Message` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Modules/Message/Domain/Message.php:8
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `Message` exposes publicly writable state (timestamps). — app/Models/Message.php:17
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
M1 · Documentation (README)
- The root README is 49 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — readme.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
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
M4 · Documentation accuracy
P1 · CI/CD gates
- The pipeline is well-formed, but the only CI definition is `.travis.yml`, and its `readme.md` build badge still points at `travis-ci.org` — a service shut down in June 2021. No other CI is configured in this repository, so nothing has been building or testing changes here since that shutdown — the steps below describe a gate that is not running. Porting it is mostly mechanical: the build and test commands already written here are what a replacement pipeline would run.
What to do
- Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists.
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry-php) and a health-check endpoint (Laravel's /up health route or a /health route) for operability.
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) as a CI step. What was searched, so you can tell an absence from a miss: the 1 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.
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:12
What to do
- Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
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.
P8 · Schema migrations
R1 · Type Safety
- 0 typed · 5 plain JS — the untyped files are resources/js/components/FlashMessages.vue, resources/js/components/InventoryManagement.vue, resources/js/components/PopupModal.vue, REDACTED, resources/js/components/StoreTrade.vue.
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- resources/js/components/InventoryManagement.vue:146 · REDACTED:200 — these 2 files are line-for-line copies of one another — 142 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/components/InventoryManagement.vue:146
- REDACTED:419 · resources/js/components/StoreTrade.vue:408 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:419
- resources/js/components/InventoryManagement.vue:377 · REDACTED:419 · resources/js/components/StoreTrade.vue:408 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/components/InventoryManagement.vue:377
- resources/js/components/StoreTrade.vue:328 · resources/js/components/StoreTrade.vue:343 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/components/StoreTrade.vue:328
- resources/js/components/StoreTrade.vue:278 · resources/js/components/StoreTrade.vue:313 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/components/StoreTrade.vue:278
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
R3 · Large Files
- REDACTED has 412 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
- resources/js/components/StoreTrade.vue has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — resources/js/components/StoreTrade.vue:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R5 · Dependency Freshness
R6 · Tooling
- test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add a test runner (vitest / jest / playwright) and eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R8 · Dependency Hygiene
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
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 `app.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/conf.d/app.conf:1
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.
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
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.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 36% | Weak — gated by R1, R3, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 87% | Exemplary | Strongest area. |
| Maturity | 45% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 24% | Weak — gated by R6, P1, P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 59% | Adequate — gated by C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 71% | Strong | Solid. |
| Accessibility | 58% | Adequate | Acceptable, with room to improve. |
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 — 63 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c apt-get update && apt-get upgrade -y && apt-get install -y build-essential git curl libpng-dev libonig-dev libxml2-dev libzip-dev zip unzip nodejs yarn" did not complete successfully: exit code: 100; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D10 Test Quality — ~586 lines of test source are present (.php) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — no .php test runner
- 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.
- D19 Documentation Quality — D19 reads .NET projects and npm packages as units; 1 folder(s) declared by composer.json were not judged for an overview, an example or the map.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, PHP not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- 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.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Composer build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.php) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- 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
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows 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 and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the PHP source (service entry point: routes/api.php:17 (Route::middleware())
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — the JS/TS workspace (5 production file(s)) has no JavaScript/TypeScript test, but it is 9.47% of this repository's production source and the other 90.53% carries 586 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
- R7 Dead Code — Not measured — no application, tooling or test entry point was detected, so no file can be shown to be reachable or unreachable. Declare an entry (package.json main/module/exports, src/index.*, or an index.html script) to enable reachability.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- 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
- 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.
- 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. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 79 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <img> without a text alternative resources/views/character/create.blade.php:16
- <img> without a text alternative resources/views/character/partials/character-display.blade.php:18
- <img> without a text alternative resources/views/character/partials/equipment-item-mutable.blade.php:4
- <img> without a text alternative resources/views/character/partials/equipment-item.blade.php:2
- <img> without a text alternative resources/views/character/partials/inventory.blade.php:21
- <img> without a text alternative resources/views/character/partials/inventory.blade.php:26
- <img> without a text alternative resources/views/location/show.blade.php:17
- <img> without a text alternative resources/views/pages/index.blade.php:14
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label resources/views/character/create.blade.php:37
- <input> without a programmatic label resources/views/character/partials/character-display.blade.php:29
- <textarea> without a programmatic label resources/views/character/message/index.blade.php:17
- Document without a <title> resources/views/base.blade.php:2
- REDACTED
- REDACTED
- REDACTED
Serious — 105 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Anemic entity: Battle app/Models/Battle.php:19
- Anemic entity: BattleRound app/Models/BattleRound.php:9
- Anemic entity: BattleTurn app/Models/BattleTurn.php:9
- Anemic entity: Character app/Models/Character.php:42
- Anemic entity: Image app/Models/Image.php:15
- Anemic entity: Inventory app/Models/Inventory.php:18
- Anemic entity: Item app/Models/Item.php:27
- Anemic entity: ItemPrototype app/Models/ItemPrototype.php:17
- Anemic entity: Message app/Models/Message.php:17
- Anemic entity: Store app/Models/Store.php:19
- Anemic entity: Race app/Modules/Character/Domain/Race.php:6
- Anemic entity: ItemPrototype app/Modules/Equipment/Domain/ItemPrototype.php:8
- Anemic entity: Image app/Modules/Image/Domain/Image.php:7
- Anemic entity: Level app/Modules/Level/Domain/Level.php:7
- Anemic entity: Message app/Modules/Message/Domain/Message.php:8
- Constructible in an invalid state: Battle app/Modules/Battle/Domain/Battle.php:47
- Constructible in an invalid state: BattleRound app/Modules/Battle/Domain/BattleRound.php:33
- Constructible in an invalid state: BattleTurn app/Modules/Battle/Domain/BattleTurn.php:34
- Constructible in an invalid state: Character app/Modules/Character/Domain/Character.php:78
- Constructible in an invalid state: Race app/Modules/Character/Domain/Race.php:37
- Constructible in an invalid state: Item app/Modules/Equipment/Domain/Item.php:48
- Constructible in an invalid state: ItemPrototype app/Modules/Equipment/Domain/ItemPrototype.php:39
- Constructible in an invalid state: Level app/Modules/Level/Domain/Level.php:22
- Constructible in an invalid state: Message app/Modules/Message/Domain/Message.php:34
- One operation mutates 2 aggregates: CharacterService.attack app/Modules/Character/Application/Services/CharacterService.php:114
- One operation mutates 2 aggregates: ItemService.create app/Modules/Equipment/Application/Services/ItemService.php:46
- One operation mutates 2 aggregates: ManageStoreService.moveItemToStore app/Modules/Trade/Application/Services/ManageStoreService.php:40
- One operation mutates 2 aggregates: ManageStoreService.moveItemToInventory app/Modules/Trade/Application/Services/ManageStoreService.php:52
- One operation mutates 2 aggregates: ManageStoreService.moveMoneyToStore app/Modules/Trade/Application/Services/ManageStoreService.php:81
- One operation mutates 2 aggregates: ManageStoreService.moveMoneyToInventory app/Modules/Trade/Application/Services/ManageStoreService.php:93
- One operation mutates 2 aggregates: TradeService.buyItem app/Modules/Trade/Application/Services/TradeService.php:48
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: DataRowsTableSeeder.run database/seeders/DataRowsTableSeeder.php:14
- MethodTooLong: MenuItemsTableSeeder.run database/seeders/MenuItemsTableSeeder.php:16
- MethodTooLong: SettingsTableSeeder.run database/seeders/SettingsTableSeeder.php:13
- Duplicated block (8 lines × 2) app/Modules/Trade/Application/Services/ManageStoreService.php:42
- Duplicated block (8 lines × 2) app/Modules/Trade/Application/Services/ManageStoreService.php:83
- Duplicated block (8 lines × 2) database/seeders/TranslationsTableSeeder.php:57
- Duplicated block (7 lines × 2) database/migrations/2017_05_16_181844_create_battle_turns_table.php:31
- Duplicated block (7 lines × 2) app/Modules/Equipment/Domain/Inventory.php:158
- Duplicated block (7 lines × 2) app/Modules/Trade/UI/Http/CommandMappers/BuyItemCommandMapper.php:18
- Duplicated block (6 lines × 2) database/migrations/2017_05_16_144929_create_battles_table.php:23
- Duplicated block (6 lines × 2) database/migrations/2017_05_16_181330_create_battle_rounds_table.php:16
- Duplicated block (6 lines × 2) app/Modules/Equipment/UI/Http/CommandMappers/EquipItemCommandMapper.php:16
- Duplicated block (5 lines × 2) database/migrations/2020_02_29_205957_create_inventory_item.php:26
- Duplicated block (5 lines × 2) app/Modules/Equipment/Domain/ItemType.php:35
- Duplicated block (5 lines × 2) database/seeders/TranslationsTableSeeder.php:36
- Abandoned package: fruitcake/laravel-cors
- Abandoned package: tcg/voyager
- TooManyMethods: Character app/Models/Character.php:42
- TooManyMethods: Character app/Modules/Character/Domain/Character.php:13
- Change coupling: login.blade.php ↔ register.blade.php resources/views/auth/login.blade.php:1
- Change coupling: UserFactory.php ↔ CharacterSeeder.php database/factories/UserFactory.php:1
- Duplicated block (18 lines × 2) app/Modules/Equipment/Application/Commands/AddItemToInventoryCommand.php:25
- Duplicated block (18 lines × 2) app/Modules/Trade/Application/Commands/BuyItemCommand.php:26
- Page without a main landmark resources/views/base.blade.php:2
- Accessibility enforcement below the top rung package.json:12
- DataRowsTableSeeder.run (cyclomatic 22) database/seeders/DataRowsTableSeeder.php:14
- TodoComment database/migrations/2020_02_29_205331_create_inventories.php:21
- DataRowsTableSeeder.run (cognitive 21) database/seeders/DataRowsTableSeeder.php:14
- REDACTED
- Duplicated block (13 lines × 2) app/Modules/Equipment/Domain/Inventory.php:117
- Duplicated block (10 lines × 2) database/migrations/2019_08_31_182034_create_items_table.php:27
- Duplicated block (5 lines × 3) database/migrations/2017_05_16_144929_create_battles_table.php:22
- End-of-life framework: Laravel 8 composer.json:1
- One operation mutates 3 aggregates: TradeService.sellItem app/Modules/Trade/Application/Services/TradeService.php:62
- Mutable entity: Message app/Models/Message.php:17
- CI pipeline targets a decommissioned service
- No DR/backup evidence
- Type Safety
- Wholesale file copy (142 identical lines × 2 files) resources/js/components/InventoryManagement.vue:146
- Duplicated block (49 lines × 2 locations) REDACTED:419
- Duplicated block (33 lines × 3 locations) resources/js/components/InventoryManagement.vue:377
- Duplicated block (9 lines × 2 locations) resources/js/components/StoreTrade.vue:328
- Duplicated block (7 lines × 2 locations) resources/js/components/StoreTrade.vue:278
- REDACTED: 412 lines of code REDACTED:1
- resources/js/components/StoreTrade.vue: 402 lines of code resources/js/components/StoreTrade.vue:1
- No test, lint or typecheck script
- Unused dependency '@fortawesome/fontawesome-free'
- Unused dependency 'vue-template-compiler'
Minor — 60 finding(s)
- Orphaned file database/seeders/DataRowsTableSeeder.php:1
- Orphaned file database/seeders/TranslationsTableSeeder.php:1
- Orphaned file app/Modules/Character/Domain/Character.php:1
- Orphaned file app/Models/Character.php:1
- Orphaned file resources/views/character/create.blade.php:1
- Orphaned file database/seeders/MenuItemsTableSeeder.php:1
- Orphaned file database/migrations/2019_08_31_182034_create_items_table.php:1
- Orphaned file app/Modules/Character/Application/Services/CharacterService.php:1
- Orphaned file database/factories/UserFactory.php:1
- Orphaned file database/seeders/SettingsTableSeeder.php:1
- Orphaned file app/Modules/Equipment/Domain/Inventory.php:1
- Orphaned file resources/views/partials/navbar.blade.php:1
- Orphaned file database/migrations/2017_05_14_055744_create_locations_table.php:1
- Orphaned file resources/views/battle/show.blade.php:1
- Orphaned file app/Modules/Character/Infrastructure/Repositories/CharacterRepository.php:1
- Orphaned file app/Modules/Trade/Domain/Store.php:1
- Orphaned file database/seeders/CharacterSeeder.php:1
- Orphaned file app/Modules/Image/Infrastructure/Repositories/ImageRepository.php:1
- Orphaned file database/migrations/2017_05_14_055823_create_races_table.php:1
- Orphaned file app/Http/Controllers/Api/ManageStoreController.php:1
- Orphaned file resources/views/auth/register.blade.php:1
- Orphaned file app/Modules/Trade/Application/Services/ManageStoreService.php:1
- Orphaned file routes/web.php:1
- Orphaned file app/Models/Location.php:1
- Orphaned file resources/views/location/partials/navigator.blade.php:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs found
- REDACTED
- REDACTED
- Dormant codebase
- REDACTED
- Thin README readme.md:1
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation package.json:12
- No rollback/health safety
- No changelog
- No security response headers detected docker/nginx/conf.d/app.conf:1
- PHP static analysis does not check null everywhere
Minor — 2 finding(s)
- Outdated: fideloper/proxy
- Outdated: laravel/legacy-factories
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-59c7e46c1f27457a9e4188af0c7de52c/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-59c7e46c1f27457a9e4188af0c7de52c/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude public/js --exclude resources/sass . | 1 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 91 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 9 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |