Executive summary
dersonsena/clean-arch-pokemon is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no working pipeline that builds or tests changes to the code and no logging, tracing or health checks in the code. It scores 49 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 31, is the weakest lens and counts most in the score. The best first steps are adding an automated build and test pipeline and logging through a logging library, each worth about 6 points. Raising Production Readiness to 70 would lift the score to about 63.
Five known security holes in the packages the code depends on can be used by attackers. Two settings leave the servers or containers unsafe. Updating the vulnerable packages and correcting the unsafe settings would close both risks.
The product code is 5,024 lines, about €5,200 to rebuild.
If Production Readiness rose from 31 to 70, the lowest score rated Strong, the score would rise from 49 to about 63.
Rebuild cost: about €5,200 · Estimate
| Cost to rebuild | €1,700 to €8,700, for 29 to 92 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 49. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 5,024 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 Market.Domain.ValueObjects | 2 Shared.Adapters.Contracts.Presentation | 3 Shared.Adapters.Contracts.QueryBuilder | 4 Shared.Domain | 5 Shared.Exceptions | 6 Shared.Helpers | 7 Market.Domain | 8 Market.Domain.Exceptions | 9 Player.Domain.Exceptions | 10 Pokedex.Domain.Exceptions | 11 Shared.Adapters.Contracts | 12 Shared.Adapters.Http | 13 Market.Domain.Factory | 14 Player.Domain | 15 Shared.Adapters.QueryBuilder.MySQL | 16 Shared.Adapters.QueryBuilder.Postgres | 17 Shared.Infra | 18 Shared.Infra.Drivers | 19 Market.UseCases.Contracts | 20 Player.Domain.Factory | 21 Player.UseCases.Contracts | 22 Pokedex.Domain | 23 Battle.Domain.ValueObjects | 24 Market.Adapters.Repository | 25 Market.UseCases.CreateItem | 26 Market.UseCases.DeleteItem | 27 Market.UseCases.Purchase | 28 Market.UseCases.UpdateItem | 29 Player.Adapters.Http | 30 Player.Adapters.Repository | 31 Pokedex.Domain.Factory | 32 Pokedex.UseCases.Contracts | 33 Battle.Domain | 34 Market.Adapters.Http | 35 Pokedex.Adapters.Http | 36 Pokedex.Adapters.Repository | 37 Battle.UseCases.Contracts | 38 Battle.Adapters.Repositories | 39 Battle.UseCases.StartBattle | 40 Battle.Adapters.Http |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Market.Domain.ValueObjects | ||||||||||||||||||||||||||||||||||||||||
| 2 Shared.Adapters.Contracts.Presentation | ||||||||||||||||||||||||||||||||||||||||
| 3 Shared.Adapters.Contracts.QueryBuilder | ||||||||||||||||||||||||||||||||||||||||
| 4 Shared.Domain | ||||||||||||||||||||||||||||||||||||||||
| 5 Shared.Exceptions | ||||||||||||||||||||||||||||||||||||||||
| 6 Shared.Helpers | ||||||||||||||||||||||||||||||||||||||||
| 7 Market.Domain | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 8 Market.Domain.Exceptions | 3 | |||||||||||||||||||||||||||||||||||||||
| 9 Player.Domain.Exceptions | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 Pokedex.Domain.Exceptions | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 Shared.Adapters.Contracts | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Shared.Adapters.Http | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 Market.Domain.Factory | 3 | |||||||||||||||||||||||||||||||||||||||
| 14 Player.Domain | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 Shared.Adapters.QueryBuilder.MySQL | 4 | 4 | ||||||||||||||||||||||||||||||||||||||
| 16 Shared.Adapters.QueryBuilder.Postgres | 4 | 4 | ||||||||||||||||||||||||||||||||||||||
| 17 Shared.Infra | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 18 Shared.Infra.Drivers | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 Market.UseCases.Contracts | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 Player.Domain.Factory | 3 | |||||||||||||||||||||||||||||||||||||||
| 21 Player.UseCases.Contracts | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 Pokedex.Domain | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 Battle.Domain.ValueObjects | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 Market.Adapters.Repository | 6 | 3 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 25 Market.UseCases.CreateItem | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 Market.UseCases.DeleteItem | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 Market.UseCases.Purchase | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 Market.UseCases.UpdateItem | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 Player.Adapters.Http | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 Player.Adapters.Repository | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 Pokedex.Domain.Factory | 3 | |||||||||||||||||||||||||||||||||||||||
| 32 Pokedex.UseCases.Contracts | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 33 Battle.Domain | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 34 Market.Adapters.Http | 6 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 35 Pokedex.Adapters.Http | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 Pokedex.Adapters.Repository | 7 | 5 | 1 | 4 | 4 | |||||||||||||||||||||||||||||||||||
| 37 Battle.UseCases.Contracts | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 Battle.Adapters.Repositories | 2 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 39 Battle.UseCases.StartBattle | 2 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 40 Battle.Adapters.Http | 1 | 1 |
7→1 Market.Domain uses Market.Domain.ValueObjects✕
- Connections
- 1 pair of types, where a type in Market.Domain uses a type in Market.Domain.ValueObjects.
- The types involved
App.Market.Domain.Item→App.Market.Domain.ValueObjects.Category
- Direction
- Market.Domain uses Market.Domain.ValueObjects, so a change to Market.Domain.ValueObjects can break Market.Domain, while a change to Market.Domain can't break Market.Domain.ValueObjects.
- Position
- Below the diagonal: Market.Domain uses a module listed above it, which is the healthy direction.
7→4 Market.Domain uses Shared.Domain✕
- Connections
- 3 pairs of types, where a type in Market.Domain uses a type in Shared.Domain.
- The types involved
App.Market.Domain.Cart→App.Shared.Domain.EntityApp.Market.Domain.CartItem→App.Shared.Domain.EntityApp.Market.Domain.Item→App.Shared.Domain.Entity
- Direction
- Market.Domain uses Shared.Domain, so a change to Shared.Domain can break Market.Domain, while a change to Market.Domain can't break Shared.Domain.
- Position
- Below the diagonal: Market.Domain uses a module listed above it, which is the healthy direction.
7→14 Market.Domain uses Player.Domain part of a loop✕
- Connections
- 1 pair of types, where a type in Market.Domain uses a type in Player.Domain.
- The types involved
App.Market.Domain.Cart→App.Player.Domain.Player
- Direction
- Market.Domain uses Player.Domain, so a change to Player.Domain can break Market.Domain, while a change to Market.Domain can't break Player.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.
8→5 Market.Domain.Exceptions uses Shared.Exceptions✕
- Connections
- 3 pairs of types, where a type in Market.Domain.Exceptions uses a type in Shared.Exceptions.
- The types involved
App.Market.Domain.Exceptions.CreatePurchaseException→App.Shared.Exceptions.AppExceptionApp.Market.Domain.Exceptions.InsufficientMoneyException→App.Shared.Exceptions.AppExceptionApp.Market.Domain.Exceptions.MartItemNotFoundException→App.Shared.Exceptions.AppValidationException
- Direction
- Market.Domain.Exceptions uses Shared.Exceptions, so a change to Shared.Exceptions can break Market.Domain.Exceptions, while a change to Market.Domain.Exceptions can't break Shared.Exceptions.
- Position
- Below the diagonal: Market.Domain.Exceptions uses a module listed above it, which is the healthy direction.
9→5 Player.Domain.Exceptions uses Shared.Exceptions✕
- Connections
- 1 pair of types, where a type in Player.Domain.Exceptions uses a type in Shared.Exceptions.
- The types involved
App.Player.Domain.Exceptions.PlayerNotFoundException→App.Shared.Exceptions.AppValidationException
- Direction
- Player.Domain.Exceptions uses Shared.Exceptions, so a change to Shared.Exceptions can break Player.Domain.Exceptions, while a change to Player.Domain.Exceptions can't break Shared.Exceptions.
- Position
- Below the diagonal: Player.Domain.Exceptions uses a module listed above it, which is the healthy direction.
10→5 Pokedex.Domain.Exceptions uses Shared.Exceptions✕
- Connections
- 2 pairs of types, where a type in Pokedex.Domain.Exceptions uses a type in Shared.Exceptions.
- The types involved
App.Pokedex.Domain.Exceptions.PokedexNotFoundException→App.Shared.Exceptions.AppValidationExceptionApp.Pokedex.Domain.Exceptions.PokemonNotFoundException→App.Shared.Exceptions.AppValidationException
- Direction
- Pokedex.Domain.Exceptions uses Shared.Exceptions, so a change to Shared.Exceptions can break Pokedex.Domain.Exceptions, while a change to Pokedex.Domain.Exceptions can't break Shared.Exceptions.
- Position
- Below the diagonal: Pokedex.Domain.Exceptions uses a module listed above it, which is the healthy direction.
11→3 Shared.Adapters.Contracts uses Shared.Adapters.Contracts.QueryBuilder✕
- Connections
- 1 pair of types, where a type in Shared.Adapters.Contracts uses a type in Shared.Adapters.Contracts.QueryBuilder.
- The types involved
App.Shared.Adapters.Contracts.DatabaseDriver→App.Shared.Adapters.Contracts.QueryBuilder.QueryStatement
- Direction
- Shared.Adapters.Contracts uses Shared.Adapters.Contracts.QueryBuilder, so a change to Shared.Adapters.Contracts.QueryBuilder can break Shared.Adapters.Contracts, while a change to Shared.Adapters.Contracts can't break Shared.Adapters.Contracts.QueryBuilder.
- Position
- Below the diagonal: Shared.Adapters.Contracts uses a module listed above it, which is the healthy direction.
12→2 Shared.Adapters.Http uses Shared.Adapters.Contracts.Presentation✕
- Connections
- 2 pairs of types, where a type in Shared.Adapters.Http uses a type in Shared.Adapters.Contracts.Presentation.
- The types involved
App.Shared.Adapters.Http.PayloadAction→App.Shared.Adapters.Contracts.Presentation.PayloadPresenterApp.Shared.Adapters.Http.TemplateAction→App.Shared.Adapters.Contracts.Presentation.TemplatePresenter
- Direction
- Shared.Adapters.Http uses Shared.Adapters.Contracts.Presentation, so a change to Shared.Adapters.Contracts.Presentation can break Shared.Adapters.Http, while a change to Shared.Adapters.Http can't break Shared.Adapters.Contracts.Presentation.
- Position
- Below the diagonal: Shared.Adapters.Http uses a module listed above it, which is the healthy direction.
13→7 Market.Domain.Factory uses Market.Domain✕
- Connections
- 3 pairs of types, where a type in Market.Domain.Factory uses a type in Market.Domain.
- The types involved
App.Market.Domain.Factory.CartFactory→App.Market.Domain.CartApp.Market.Domain.Factory.CartItemFactory→App.Market.Domain.CartItemApp.Market.Domain.Factory.ItemFactory→App.Market.Domain.Item
- Direction
- Market.Domain.Factory uses Market.Domain, so a change to Market.Domain can break Market.Domain.Factory, while a change to Market.Domain.Factory can't break Market.Domain.
- Position
- Below the diagonal: Market.Domain.Factory uses a module listed above it, which is the healthy direction.
14→4 Player.Domain uses Shared.Domain✕
- Connections
- 3 pairs of types, where a type in Player.Domain uses a type in Shared.Domain.
- The types involved
App.Player.Domain.Bag→App.Shared.Domain.EntityApp.Player.Domain.Party→App.Shared.Domain.EntityApp.Player.Domain.Player→App.Shared.Domain.Entity
- Direction
- Player.Domain uses Shared.Domain, so a change to Shared.Domain can break Player.Domain, while a change to Player.Domain can't break Shared.Domain.
- Position
- Below the diagonal: Player.Domain uses a module listed above it, which is the healthy direction.
14→7 Player.Domain uses Market.Domain✕
- Connections
- 1 pair of types, where a type in Player.Domain uses a type in Market.Domain.
- The types involved
App.Player.Domain.Bag→App.Market.Domain.Item
- Direction
- Player.Domain uses Market.Domain, so a change to Market.Domain can break Player.Domain, while a change to Player.Domain can't break Market.Domain.
- Position
- Below the diagonal: Player.Domain uses a module listed above it, which is the healthy direction.
15→3 Shared.Adapters.QueryBuilder.MySQL uses Shared.Adapters.Contracts.QueryBuilder✕
- Connections
- 4 pairs of types, where a type in Shared.Adapters.QueryBuilder.MySQL uses a type in Shared.Adapters.Contracts.QueryBuilder.
- The types involved
App.Shared.Adapters.QueryBuilder.MySQL.Delete→App.Shared.Adapters.Contracts.QueryBuilder.DeleteStatementApp.Shared.Adapters.QueryBuilder.MySQL.Insert→App.Shared.Adapters.Contracts.QueryBuilder.InsertStatementApp.Shared.Adapters.QueryBuilder.MySQL.Select→App.Shared.Adapters.Contracts.QueryBuilder.SelectStatementApp.Shared.Adapters.QueryBuilder.MySQL.Update→App.Shared.Adapters.Contracts.QueryBuilder.UpdateStatement
- Direction
- Shared.Adapters.QueryBuilder.MySQL uses Shared.Adapters.Contracts.QueryBuilder, so a change to Shared.Adapters.Contracts.QueryBuilder can break Shared.Adapters.QueryBuilder.MySQL, while a change to Shared.Adapters.QueryBuilder.MySQL can't break Shared.Adapters.Contracts.QueryBuilder.
- Position
- Below the diagonal: Shared.Adapters.QueryBuilder.MySQL uses a module listed above it, which is the healthy direction.
15→11 Shared.Adapters.QueryBuilder.MySQL uses Shared.Adapters.Contracts✕
- Connections
- 4 pairs of types, where a type in Shared.Adapters.QueryBuilder.MySQL uses a type in Shared.Adapters.Contracts.
- The types involved
App.Shared.Adapters.QueryBuilder.MySQL.Delete→App.Shared.Adapters.Contracts.DatabaseDriverApp.Shared.Adapters.QueryBuilder.MySQL.Insert→App.Shared.Adapters.Contracts.DatabaseDriverApp.Shared.Adapters.QueryBuilder.MySQL.Select→App.Shared.Adapters.Contracts.DatabaseDriverApp.Shared.Adapters.QueryBuilder.MySQL.Update→App.Shared.Adapters.Contracts.DatabaseDriver
- Direction
- Shared.Adapters.QueryBuilder.MySQL uses Shared.Adapters.Contracts, so a change to Shared.Adapters.Contracts can break Shared.Adapters.QueryBuilder.MySQL, while a change to Shared.Adapters.QueryBuilder.MySQL can't break Shared.Adapters.Contracts.
- Position
- Below the diagonal: Shared.Adapters.QueryBuilder.MySQL uses a module listed above it, which is the healthy direction.
16→3 Shared.Adapters.QueryBuilder.Postgres uses Shared.Adapters.Contracts.QueryBuilder✕
- Connections
- 4 pairs of types, where a type in Shared.Adapters.QueryBuilder.Postgres uses a type in Shared.Adapters.Contracts.QueryBuilder.
- The types involved
App.Shared.Adapters.QueryBuilder.Postgres.Delete→App.Shared.Adapters.Contracts.QueryBuilder.DeleteStatementApp.Shared.Adapters.QueryBuilder.Postgres.Insert→App.Shared.Adapters.Contracts.QueryBuilder.InsertStatementApp.Shared.Adapters.QueryBuilder.Postgres.Select→App.Shared.Adapters.Contracts.QueryBuilder.SelectStatementApp.Shared.Adapters.QueryBuilder.Postgres.Update→App.Shared.Adapters.Contracts.QueryBuilder.UpdateStatement
- Direction
- Shared.Adapters.QueryBuilder.Postgres uses Shared.Adapters.Contracts.QueryBuilder, so a change to Shared.Adapters.Contracts.QueryBuilder can break Shared.Adapters.QueryBuilder.Postgres, while a change to Shared.Adapters.QueryBuilder.Postgres can't break Shared.Adapters.Contracts.QueryBuilder.
- Position
- Below the diagonal: Shared.Adapters.QueryBuilder.Postgres uses a module listed above it, which is the healthy direction.
16→11 Shared.Adapters.QueryBuilder.Postgres uses Shared.Adapters.Contracts✕
- Connections
- 4 pairs of types, where a type in Shared.Adapters.QueryBuilder.Postgres uses a type in Shared.Adapters.Contracts.
- The types involved
App.Shared.Adapters.QueryBuilder.Postgres.Delete→App.Shared.Adapters.Contracts.DatabaseDriverApp.Shared.Adapters.QueryBuilder.Postgres.Insert→App.Shared.Adapters.Contracts.DatabaseDriverApp.Shared.Adapters.QueryBuilder.Postgres.Select→App.Shared.Adapters.Contracts.DatabaseDriverApp.Shared.Adapters.QueryBuilder.Postgres.Update→App.Shared.Adapters.Contracts.DatabaseDriver
- Direction
- Shared.Adapters.QueryBuilder.Postgres uses Shared.Adapters.Contracts, so a change to Shared.Adapters.Contracts can break Shared.Adapters.QueryBuilder.Postgres, while a change to Shared.Adapters.QueryBuilder.Postgres can't break Shared.Adapters.Contracts.
- Position
- Below the diagonal: Shared.Adapters.QueryBuilder.Postgres uses a module listed above it, which is the healthy direction.
17→2 Shared.Infra uses Shared.Adapters.Contracts.Presentation✕
- Connections
- 1 pair of types, where a type in Shared.Infra uses a type in Shared.Adapters.Contracts.Presentation.
- The types involved
App.Shared.Infra.TwigEngine→App.Shared.Adapters.Contracts.Presentation.TemplatePresenter
- Direction
- Shared.Infra uses Shared.Adapters.Contracts.Presentation, so a change to Shared.Adapters.Contracts.Presentation can break Shared.Infra, while a change to Shared.Infra can't break Shared.Adapters.Contracts.Presentation.
- Position
- Below the diagonal: Shared.Infra uses a module listed above it, which is the healthy direction.
17→11 Shared.Infra uses Shared.Adapters.Contracts✕
- Connections
- 5 pairs of types, where a type in Shared.Infra uses a type in Shared.Adapters.Contracts.
- The types involved
App.Shared.Infra.GuzzleHttpClient→App.Shared.Adapters.Contracts.HttpClientApp.Shared.Infra.PRedisClient→App.Shared.Adapters.Contracts.CacheSystemApp.Shared.Infra.PokeAPI→App.Shared.Adapters.Contracts.HttpClientApp.Shared.Infra.PokeAPI→App.Shared.Adapters.Contracts.PokemonAPIApp.Shared.Infra.RespectValidation→App.Shared.Adapters.Contracts.ValidatorTool
- Direction
- Shared.Infra uses Shared.Adapters.Contracts, so a change to Shared.Adapters.Contracts can break Shared.Infra, while a change to Shared.Infra can't break Shared.Adapters.Contracts.
- Position
- Below the diagonal: Shared.Infra uses a module listed above it, which is the healthy direction.
18→3 Shared.Infra.Drivers uses Shared.Adapters.Contracts.QueryBuilder✕
- Connections
- 2 pairs of types, where a type in Shared.Infra.Drivers uses a type in Shared.Adapters.Contracts.QueryBuilder.
- The types involved
App.Shared.Infra.Drivers.MySQLDriver→App.Shared.Adapters.Contracts.QueryBuilder.QueryStatementApp.Shared.Infra.Drivers.PostgresDriver→App.Shared.Adapters.Contracts.QueryBuilder.QueryStatement
- Direction
- Shared.Infra.Drivers uses Shared.Adapters.Contracts.QueryBuilder, so a change to Shared.Adapters.Contracts.QueryBuilder can break Shared.Infra.Drivers, while a change to Shared.Infra.Drivers can't break Shared.Adapters.Contracts.QueryBuilder.
- Position
- Below the diagonal: Shared.Infra.Drivers uses a module listed above it, which is the healthy direction.
18→11 Shared.Infra.Drivers uses Shared.Adapters.Contracts✕
- Connections
- 2 pairs of types, where a type in Shared.Infra.Drivers uses a type in Shared.Adapters.Contracts.
- The types involved
App.Shared.Infra.Drivers.MySQLDriver→App.Shared.Adapters.Contracts.DatabaseDriverApp.Shared.Infra.Drivers.PostgresDriver→App.Shared.Adapters.Contracts.DatabaseDriver
- Direction
- Shared.Infra.Drivers uses Shared.Adapters.Contracts, so a change to Shared.Adapters.Contracts can break Shared.Infra.Drivers, while a change to Shared.Infra.Drivers can't break Shared.Adapters.Contracts.
- Position
- Below the diagonal: Shared.Infra.Drivers uses a module listed above it, which is the healthy direction.
19→7 Market.UseCases.Contracts uses Market.Domain✕
- Connections
- 3 pairs of types, where a type in Market.UseCases.Contracts uses a type in Market.Domain.
- The types involved
App.Market.UseCases.Contracts.ItemRepository→App.Market.Domain.ItemApp.Market.UseCases.Contracts.MarketRepository→App.Market.Domain.CartApp.Market.UseCases.Contracts.MarketRepository→App.Market.Domain.Item
- Direction
- Market.UseCases.Contracts uses Market.Domain, so a change to Market.Domain can break Market.UseCases.Contracts, while a change to Market.UseCases.Contracts can't break Market.Domain.
- Position
- Below the diagonal: Market.UseCases.Contracts uses a module listed above it, which is the healthy direction.
19→14 Market.UseCases.Contracts uses Player.Domain✕
- Connections
- 1 pair of types, where a type in Market.UseCases.Contracts uses a type in Player.Domain.
- The types involved
App.Market.UseCases.Contracts.MarketRepository→App.Player.Domain.Player
- Direction
- Market.UseCases.Contracts uses Player.Domain, so a change to Player.Domain can break Market.UseCases.Contracts, while a change to Market.UseCases.Contracts can't break Player.Domain.
- Position
- Below the diagonal: Market.UseCases.Contracts uses a module listed above it, which is the healthy direction.
20→14 Player.Domain.Factory uses Player.Domain✕
- Connections
- 3 pairs of types, where a type in Player.Domain.Factory uses a type in Player.Domain.
- The types involved
App.Player.Domain.Factory.BagFactory→App.Player.Domain.BagApp.Player.Domain.Factory.PartyFactory→App.Player.Domain.PartyApp.Player.Domain.Factory.PlayerFactory→App.Player.Domain.Player
- Direction
- Player.Domain.Factory uses Player.Domain, so a change to Player.Domain can break Player.Domain.Factory, while a change to Player.Domain.Factory can't break Player.Domain.
- Position
- Below the diagonal: Player.Domain.Factory uses a module listed above it, which is the healthy direction.
21→14 Player.UseCases.Contracts uses Player.Domain✕
- Connections
- 1 pair of types, where a type in Player.UseCases.Contracts uses a type in Player.Domain.
- The types involved
App.Player.UseCases.Contracts.PlayerRepository→App.Player.Domain.Player
- Direction
- Player.UseCases.Contracts uses Player.Domain, so a change to Player.Domain can break Player.UseCases.Contracts, while a change to Player.UseCases.Contracts can't break Player.Domain.
- Position
- Below the diagonal: Player.UseCases.Contracts uses a module listed above it, which is the healthy direction.
22→4 Pokedex.Domain uses Shared.Domain✕
- Connections
- 3 pairs of types, where a type in Pokedex.Domain uses a type in Shared.Domain.
- The types involved
App.Pokedex.Domain.Pokedex→App.Shared.Domain.EntityApp.Pokedex.Domain.Pokemon→App.Shared.Domain.EntityApp.Pokedex.Domain.Type→App.Shared.Domain.Entity
- Direction
- Pokedex.Domain uses Shared.Domain, so a change to Shared.Domain can break Pokedex.Domain, while a change to Pokedex.Domain can't break Shared.Domain.
- Position
- Below the diagonal: Pokedex.Domain uses a module listed above it, which is the healthy direction.
22→14 Pokedex.Domain uses Player.Domain✕
- Connections
- 1 pair of types, where a type in Pokedex.Domain uses a type in Player.Domain.
- The types involved
App.Pokedex.Domain.Pokedex→App.Player.Domain.Player
- Direction
- Pokedex.Domain uses Player.Domain, so a change to Player.Domain can break Pokedex.Domain, while a change to Pokedex.Domain can't break Player.Domain.
- Position
- Below the diagonal: Pokedex.Domain uses a module listed above it, which is the healthy direction.
23→14 Battle.Domain.ValueObjects uses Player.Domain✕
- Connections
- 1 pair of types, where a type in Battle.Domain.ValueObjects uses a type in Player.Domain.
- The types involved
App.Battle.Domain.ValueObjects.BattlePokemon→App.Player.Domain.Player
- Direction
- Battle.Domain.ValueObjects uses Player.Domain, so a change to Player.Domain can break Battle.Domain.ValueObjects, while a change to Battle.Domain.ValueObjects can't break Player.Domain.
- Position
- Below the diagonal: Battle.Domain.ValueObjects uses a module listed above it, which is the healthy direction.
23→22 Battle.Domain.ValueObjects uses Pokedex.Domain✕
- Connections
- 1 pair of types, where a type in Battle.Domain.ValueObjects uses a type in Pokedex.Domain.
- The types involved
App.Battle.Domain.ValueObjects.BattlePokemon→App.Pokedex.Domain.Pokemon
- Direction
- Battle.Domain.ValueObjects uses Pokedex.Domain, so a change to Pokedex.Domain can break Battle.Domain.ValueObjects, while a change to Battle.Domain.ValueObjects can't break Pokedex.Domain.
- Position
- Below the diagonal: Battle.Domain.ValueObjects uses a module listed above it, which is the healthy direction.
24→3 Market.Adapters.Repository uses Shared.Adapters.Contracts.QueryBuilder✕
- Connections
- 6 pairs of types, where a type in Market.Adapters.Repository uses a type in Shared.Adapters.Contracts.QueryBuilder.
- The types involved
App.Market.Adapters.Repository.ItemRepository→App.Shared.Adapters.Contracts.QueryBuilder.DeleteStatementApp.Market.Adapters.Repository.ItemRepository→App.Shared.Adapters.Contracts.QueryBuilder.InsertStatementApp.Market.Adapters.Repository.ItemRepository→App.Shared.Adapters.Contracts.QueryBuilder.SelectStatementApp.Market.Adapters.Repository.ItemRepository→App.Shared.Adapters.Contracts.QueryBuilder.UpdateStatementApp.Market.Adapters.Repository.MarketRepository→App.Shared.Adapters.Contracts.QueryBuilder.InsertStatementApp.Market.Adapters.Repository.MarketRepository→App.Shared.Adapters.Contracts.QueryBuilder.SelectStatement
- Direction
- Market.Adapters.Repository uses Shared.Adapters.Contracts.QueryBuilder, so a change to Shared.Adapters.Contracts.QueryBuilder can break Market.Adapters.Repository, while a change to Market.Adapters.Repository can't break Shared.Adapters.Contracts.QueryBuilder.
- Position
- Below the diagonal: Market.Adapters.Repository uses a module listed above it, which is the healthy direction.
24→7 Market.Adapters.Repository uses Market.Domain✕
- Connections
- 3 pairs of types, where a type in Market.Adapters.Repository uses a type in Market.Domain.
- The types involved
App.Market.Adapters.Repository.ItemRepository→App.Market.Domain.ItemApp.Market.Adapters.Repository.MarketRepository→App.Market.Domain.CartApp.Market.Adapters.Repository.MarketRepository→App.Market.Domain.Item
- Direction
- Market.Adapters.Repository uses Market.Domain, so a change to Market.Domain can break Market.Adapters.Repository, while a change to Market.Adapters.Repository can't break Market.Domain.
- Position
- Below the diagonal: Market.Adapters.Repository uses a module listed above it, which is the healthy direction.
24→11 Market.Adapters.Repository uses Shared.Adapters.Contracts✕
- Connections
- 1 pair of types, where a type in Market.Adapters.Repository uses a type in Shared.Adapters.Contracts.
- The types involved
App.Market.Adapters.Repository.MarketRepository→App.Shared.Adapters.Contracts.DatabaseDriver
- Direction
- Market.Adapters.Repository uses Shared.Adapters.Contracts, so a change to Shared.Adapters.Contracts can break Market.Adapters.Repository, while a change to Market.Adapters.Repository can't break Shared.Adapters.Contracts.
- Position
- Below the diagonal: Market.Adapters.Repository uses a module listed above it, which is the healthy direction.
24→14 Market.Adapters.Repository uses Player.Domain✕
- Connections
- 1 pair of types, where a type in Market.Adapters.Repository uses a type in Player.Domain.
- The types involved
App.Market.Adapters.Repository.MarketRepository→App.Player.Domain.Player
- Direction
- Market.Adapters.Repository uses Player.Domain, so a change to Player.Domain can break Market.Adapters.Repository, while a change to Market.Adapters.Repository can't break Player.Domain.
- Position
- Below the diagonal: Market.Adapters.Repository uses a module listed above it, which is the healthy direction.
24→19 Market.Adapters.Repository uses Market.UseCases.Contracts✕
- Connections
- 2 pairs of types, where a type in Market.Adapters.Repository uses a type in Market.UseCases.Contracts.
- The types involved
App.Market.Adapters.Repository.ItemRepository→App.Market.UseCases.Contracts.ItemRepositoryApp.Market.Adapters.Repository.MarketRepository→App.Market.UseCases.Contracts.MarketRepository
- Direction
- Market.Adapters.Repository uses Market.UseCases.Contracts, so a change to Market.UseCases.Contracts can break Market.Adapters.Repository, while a change to Market.Adapters.Repository can't break Market.UseCases.Contracts.
- Position
- Below the diagonal: Market.Adapters.Repository uses a module listed above it, which is the healthy direction.
24→21 Market.Adapters.Repository uses Player.UseCases.Contracts✕
- Connections
- 1 pair of types, where a type in Market.Adapters.Repository uses a type in Player.UseCases.Contracts.
- The types involved
App.Market.Adapters.Repository.MarketRepository→App.Player.UseCases.Contracts.PlayerRepository
- Direction
- Market.Adapters.Repository uses Player.UseCases.Contracts, so a change to Player.UseCases.Contracts can break Market.Adapters.Repository, while a change to Market.Adapters.Repository can't break Player.UseCases.Contracts.
- Position
- Below the diagonal: Market.Adapters.Repository uses a module listed above it, which is the healthy direction.
25→6 Market.UseCases.CreateItem uses Shared.Helpers✕
- Connections
- 2 pairs of types, where a type in Market.UseCases.CreateItem uses a type in Shared.Helpers.
- The types involved
App.Market.UseCases.CreateItem.InputBoundary→App.Shared.Helpers.DTOApp.Market.UseCases.CreateItem.OutputBoundary→App.Shared.Helpers.DTO
- Direction
- Market.UseCases.CreateItem uses Shared.Helpers, so a change to Shared.Helpers can break Market.UseCases.CreateItem, while a change to Market.UseCases.CreateItem can't break Shared.Helpers.
- Position
- Below the diagonal: Market.UseCases.CreateItem uses a module listed above it, which is the healthy direction.
25→19 Market.UseCases.CreateItem uses Market.UseCases.Contracts✕
- Connections
- 1 pair of types, where a type in Market.UseCases.CreateItem uses a type in Market.UseCases.Contracts.
- The types involved
App.Market.UseCases.CreateItem.CreateItem→App.Market.UseCases.Contracts.ItemRepository
- Direction
- Market.UseCases.CreateItem uses Market.UseCases.Contracts, so a change to Market.UseCases.Contracts can break Market.UseCases.CreateItem, while a change to Market.UseCases.CreateItem can't break Market.UseCases.Contracts.
- Position
- Below the diagonal: Market.UseCases.CreateItem uses a module listed above it, which is the healthy direction.
26→6 Market.UseCases.DeleteItem uses Shared.Helpers✕
- Connections
- 2 pairs of types, where a type in Market.UseCases.DeleteItem uses a type in Shared.Helpers.
- The types involved
App.Market.UseCases.DeleteItem.InputBoundary→App.Shared.Helpers.DTOApp.Market.UseCases.DeleteItem.OutputBoundary→App.Shared.Helpers.DTO
- Direction
- Market.UseCases.DeleteItem uses Shared.Helpers, so a change to Shared.Helpers can break Market.UseCases.DeleteItem, while a change to Market.UseCases.DeleteItem can't break Shared.Helpers.
- Position
- Below the diagonal: Market.UseCases.DeleteItem uses a module listed above it, which is the healthy direction.
26→19 Market.UseCases.DeleteItem uses Market.UseCases.Contracts✕
- Connections
- 1 pair of types, where a type in Market.UseCases.DeleteItem uses a type in Market.UseCases.Contracts.
- The types involved
App.Market.UseCases.DeleteItem.DeleteItem→App.Market.UseCases.Contracts.ItemRepository
- Direction
- Market.UseCases.DeleteItem uses Market.UseCases.Contracts, so a change to Market.UseCases.Contracts can break Market.UseCases.DeleteItem, while a change to Market.UseCases.DeleteItem can't break Market.UseCases.Contracts.
- Position
- Below the diagonal: Market.UseCases.DeleteItem uses a module listed above it, which is the healthy direction.
27→6 Market.UseCases.Purchase uses Shared.Helpers✕
- Connections
- 2 pairs of types, where a type in Market.UseCases.Purchase uses a type in Shared.Helpers.
- The types involved
App.Market.UseCases.Purchase.InputBoundary→App.Shared.Helpers.DTOApp.Market.UseCases.Purchase.OutputBoundary→App.Shared.Helpers.DTO
- Direction
- Market.UseCases.Purchase uses Shared.Helpers, so a change to Shared.Helpers can break Market.UseCases.Purchase, while a change to Market.UseCases.Purchase can't break Shared.Helpers.
- Position
- Below the diagonal: Market.UseCases.Purchase uses a module listed above it, which is the healthy direction.
27→11 Market.UseCases.Purchase uses Shared.Adapters.Contracts✕
- Connections
- 1 pair of types, where a type in Market.UseCases.Purchase uses a type in Shared.Adapters.Contracts.
- The types involved
App.Market.UseCases.Purchase.PurchaseValidator→App.Shared.Adapters.Contracts.ValidatorTool
- Direction
- Market.UseCases.Purchase uses Shared.Adapters.Contracts, so a change to Shared.Adapters.Contracts can break Market.UseCases.Purchase, while a change to Market.UseCases.Purchase can't break Shared.Adapters.Contracts.
- Position
- Below the diagonal: Market.UseCases.Purchase uses a module listed above it, which is the healthy direction.
27→19 Market.UseCases.Purchase uses Market.UseCases.Contracts✕
- Connections
- 1 pair of types, where a type in Market.UseCases.Purchase uses a type in Market.UseCases.Contracts.
- The types involved
App.Market.UseCases.Purchase.Purchase→App.Market.UseCases.Contracts.MarketRepository
- Direction
- Market.UseCases.Purchase uses Market.UseCases.Contracts, so a change to Market.UseCases.Contracts can break Market.UseCases.Purchase, while a change to Market.UseCases.Purchase can't break Market.UseCases.Contracts.
- Position
- Below the diagonal: Market.UseCases.Purchase uses a module listed above it, which is the healthy direction.
27→21 Market.UseCases.Purchase uses Player.UseCases.Contracts✕
- Connections
- 1 pair of types, where a type in Market.UseCases.Purchase uses a type in Player.UseCases.Contracts.
- The types involved
App.Market.UseCases.Purchase.Purchase→App.Player.UseCases.Contracts.PlayerRepository
- Direction
- Market.UseCases.Purchase uses Player.UseCases.Contracts, so a change to Player.UseCases.Contracts can break Market.UseCases.Purchase, while a change to Market.UseCases.Purchase can't break Player.UseCases.Contracts.
- Position
- Below the diagonal: Market.UseCases.Purchase uses a module listed above it, which is the healthy direction.
28→6 Market.UseCases.UpdateItem uses Shared.Helpers✕
- Connections
- 2 pairs of types, where a type in Market.UseCases.UpdateItem uses a type in Shared.Helpers.
- The types involved
App.Market.UseCases.UpdateItem.InputBoundary→App.Shared.Helpers.DTOApp.Market.UseCases.UpdateItem.OutputBoundary→App.Shared.Helpers.DTO
- Direction
- Market.UseCases.UpdateItem uses Shared.Helpers, so a change to Shared.Helpers can break Market.UseCases.UpdateItem, while a change to Market.UseCases.UpdateItem can't break Shared.Helpers.
- Position
- Below the diagonal: Market.UseCases.UpdateItem uses a module listed above it, which is the healthy direction.
28→19 Market.UseCases.UpdateItem uses Market.UseCases.Contracts✕
- Connections
- 1 pair of types, where a type in Market.UseCases.UpdateItem uses a type in Market.UseCases.Contracts.
- The types involved
App.Market.UseCases.UpdateItem.UpdateItem→App.Market.UseCases.Contracts.ItemRepository
- Direction
- Market.UseCases.UpdateItem uses Market.UseCases.Contracts, so a change to Market.UseCases.Contracts can break Market.UseCases.UpdateItem, while a change to Market.UseCases.UpdateItem can't break Market.UseCases.Contracts.
- Position
- Below the diagonal: Market.UseCases.UpdateItem uses a module listed above it, which is the healthy direction.
29→12 Player.Adapters.Http uses Shared.Adapters.Http✕
- Connections
- 2 pairs of types, where a type in Player.Adapters.Http uses a type in Shared.Adapters.Http.
- The types involved
App.Player.Adapters.Http.ProfileAction→App.Shared.Adapters.Http.PayloadActionApp.Player.Adapters.Http.ProfilePageAction→App.Shared.Adapters.Http.TemplateAction
- Direction
- Player.Adapters.Http uses Shared.Adapters.Http, so a change to Shared.Adapters.Http can break Player.Adapters.Http, while a change to Player.Adapters.Http can't break Shared.Adapters.Http.
- Position
- Below the diagonal: Player.Adapters.Http uses a module listed above it, which is the healthy direction.
29→21 Player.Adapters.Http uses Player.UseCases.Contracts✕
- Connections
- 1 pair of types, where a type in Player.Adapters.Http uses a type in Player.UseCases.Contracts.
- The types involved
App.Player.Adapters.Http.ProfileAction→App.Player.UseCases.Contracts.PlayerRepository
- Direction
- Player.Adapters.Http uses Player.UseCases.Contracts, so a change to Player.UseCases.Contracts can break Player.Adapters.Http, while a change to Player.Adapters.Http can't break Player.UseCases.Contracts.
- Position
- Below the diagonal: Player.Adapters.Http uses a module listed above it, which is the healthy direction.
30→3 Player.Adapters.Repository uses Shared.Adapters.Contracts.QueryBuilder✕
- Connections
- 2 pairs of types, where a type in Player.Adapters.Repository uses a type in Shared.Adapters.Contracts.QueryBuilder.
- The types involved
App.Player.Adapters.Repository.PlayerRepository→App.Shared.Adapters.Contracts.QueryBuilder.SelectStatementApp.Player.Adapters.Repository.PlayerRepository→App.Shared.Adapters.Contracts.QueryBuilder.UpdateStatement
- Direction
- Player.Adapters.Repository uses Shared.Adapters.Contracts.QueryBuilder, so a change to Shared.Adapters.Contracts.QueryBuilder can break Player.Adapters.Repository, while a change to Player.Adapters.Repository can't break Shared.Adapters.Contracts.QueryBuilder.
- Position
- Below the diagonal: Player.Adapters.Repository uses a module listed above it, which is the healthy direction.
30→11 Player.Adapters.Repository uses Shared.Adapters.Contracts✕
- Connections
- 1 pair of types, where a type in Player.Adapters.Repository uses a type in Shared.Adapters.Contracts.
- The types involved
App.Player.Adapters.Repository.PlayerRepository→App.Shared.Adapters.Contracts.DatabaseDriver
- Direction
- Player.Adapters.Repository uses Shared.Adapters.Contracts, so a change to Shared.Adapters.Contracts can break Player.Adapters.Repository, while a change to Player.Adapters.Repository can't break Shared.Adapters.Contracts.
- Position
- Below the diagonal: Player.Adapters.Repository uses a module listed above it, which is the healthy direction.
30→14 Player.Adapters.Repository uses Player.Domain✕
- Connections
- 1 pair of types, where a type in Player.Adapters.Repository uses a type in Player.Domain.
- The types involved
App.Player.Adapters.Repository.PlayerRepository→App.Player.Domain.Player
- Direction
- Player.Adapters.Repository uses Player.Domain, so a change to Player.Domain can break Player.Adapters.Repository, while a change to Player.Adapters.Repository can't break Player.Domain.
- Position
- Below the diagonal: Player.Adapters.Repository uses a module listed above it, which is the healthy direction.
30→21 Player.Adapters.Repository uses Player.UseCases.Contracts✕
- Connections
- 1 pair of types, where a type in Player.Adapters.Repository uses a type in Player.UseCases.Contracts.
- The types involved
App.Player.Adapters.Repository.PlayerRepository→App.Player.UseCases.Contracts.PlayerRepository
- Direction
- Player.Adapters.Repository uses Player.UseCases.Contracts, so a change to Player.UseCases.Contracts can break Player.Adapters.Repository, while a change to Player.Adapters.Repository can't break Player.UseCases.Contracts.
- Position
- Below the diagonal: Player.Adapters.Repository uses a module listed above it, which is the healthy direction.
31→22 Pokedex.Domain.Factory uses Pokedex.Domain✕
- Connections
- 3 pairs of types, where a type in Pokedex.Domain.Factory uses a type in Pokedex.Domain.
- The types involved
App.Pokedex.Domain.Factory.PokedexFactory→App.Pokedex.Domain.PokedexApp.Pokedex.Domain.Factory.PokemonFactory→App.Pokedex.Domain.PokemonApp.Pokedex.Domain.Factory.TypeFactory→App.Pokedex.Domain.Type
- Direction
- Pokedex.Domain.Factory uses Pokedex.Domain, so a change to Pokedex.Domain can break Pokedex.Domain.Factory, while a change to Pokedex.Domain.Factory can't break Pokedex.Domain.
- Position
- Below the diagonal: Pokedex.Domain.Factory uses a module listed above it, which is the healthy direction.
32→14 Pokedex.UseCases.Contracts uses Player.Domain✕
- Connections
- 1 pair of types, where a type in Pokedex.UseCases.Contracts uses a type in Player.Domain.
- The types involved
App.Pokedex.UseCases.Contracts.PokedexRepository→App.Player.Domain.Player
- Direction
- Pokedex.UseCases.Contracts uses Player.Domain, so a change to Player.Domain can break Pokedex.UseCases.Contracts, while a change to Pokedex.UseCases.Contracts can't break Player.Domain.
- Position
- Below the diagonal: Pokedex.UseCases.Contracts uses a module listed above it, which is the healthy direction.
32→22 Pokedex.UseCases.Contracts uses Pokedex.Domain✕
- Connections
- 4 pairs of types, where a type in Pokedex.UseCases.Contracts uses a type in Pokedex.Domain.
- The types involved
App.Pokedex.UseCases.Contracts.PokedexRepository→App.Pokedex.Domain.PokedexApp.Pokedex.UseCases.Contracts.PokedexRepository→App.Pokedex.Domain.PokemonApp.Pokedex.UseCases.Contracts.PokemonRepository→App.Pokedex.Domain.PokemonApp.Pokedex.UseCases.Contracts.TypeRepository→App.Pokedex.Domain.Type
- Direction
- Pokedex.UseCases.Contracts uses Pokedex.Domain, so a change to Pokedex.Domain can break Pokedex.UseCases.Contracts, while a change to Pokedex.UseCases.Contracts can't break Pokedex.Domain.
- Position
- Below the diagonal: Pokedex.UseCases.Contracts uses a module listed above it, which is the healthy direction.
33→4 Battle.Domain uses Shared.Domain✕
- Connections
- 1 pair of types, where a type in Battle.Domain uses a type in Shared.Domain.
- The types involved
App.Battle.Domain.Battle→App.Shared.Domain.Entity
- Direction
- Battle.Domain uses Shared.Domain, so a change to Shared.Domain can break Battle.Domain, while a change to Battle.Domain can't break Shared.Domain.
- Position
- Below the diagonal: Battle.Domain uses a module listed above it, which is the healthy direction.
33→23 Battle.Domain uses Battle.Domain.ValueObjects✕
- Connections
- 2 pairs of types, where a type in Battle.Domain uses a type in Battle.Domain.ValueObjects.
- The types involved
App.Battle.Domain.Battle→App.Battle.Domain.ValueObjects.BattlePokemonApp.Battle.Domain.Battle→App.Battle.Domain.ValueObjects.BattleStatus
- Direction
- Battle.Domain uses Battle.Domain.ValueObjects, so a change to Battle.Domain.ValueObjects can break Battle.Domain, while a change to Battle.Domain can't break Battle.Domain.ValueObjects.
- Position
- Below the diagonal: Battle.Domain uses a module listed above it, which is the healthy direction.
34→12 Market.Adapters.Http uses Shared.Adapters.Http✕
- Connections
- 6 pairs of types, where a type in Market.Adapters.Http uses a type in Shared.Adapters.Http.
- The types involved
App.Market.Adapters.Http.CreateItemAction→App.Shared.Adapters.Http.PayloadActionApp.Market.Adapters.Http.DeleteItemAction→App.Shared.Adapters.Http.PayloadActionApp.Market.Adapters.Http.GetItemAction→App.Shared.Adapters.Http.PayloadActionApp.Market.Adapters.Http.ItemsListAction→App.Shared.Adapters.Http.PayloadActionApp.Market.Adapters.Http.PurchaseAction→App.Shared.Adapters.Http.PayloadActionApp.Market.Adapters.Http.UpdateItemAction→App.Shared.Adapters.Http.PayloadAction
- Direction
- Market.Adapters.Http uses Shared.Adapters.Http, so a change to Shared.Adapters.Http can break Market.Adapters.Http, while a change to Market.Adapters.Http can't break Shared.Adapters.Http.
- Position
- Below the diagonal: Market.Adapters.Http uses a module listed above it, which is the healthy direction.
34→19 Market.Adapters.Http uses Market.UseCases.Contracts✕
- Connections
- 2 pairs of types, where a type in Market.Adapters.Http uses a type in Market.UseCases.Contracts.
- The types involved
App.Market.Adapters.Http.GetItemAction→App.Market.UseCases.Contracts.ItemRepositoryApp.Market.Adapters.Http.ItemsListAction→App.Market.UseCases.Contracts.MarketRepository
- Direction
- Market.Adapters.Http uses Market.UseCases.Contracts, so a change to Market.UseCases.Contracts can break Market.Adapters.Http, while a change to Market.Adapters.Http can't break Market.UseCases.Contracts.
- Position
- Below the diagonal: Market.Adapters.Http uses a module listed above it, which is the healthy direction.
34→25 Market.Adapters.Http uses Market.UseCases.CreateItem✕
- Connections
- 1 pair of types, where a type in Market.Adapters.Http uses a type in Market.UseCases.CreateItem.
- The types involved
App.Market.Adapters.Http.CreateItemAction→App.Market.UseCases.CreateItem.CreateItem
- Direction
- Market.Adapters.Http uses Market.UseCases.CreateItem, so a change to Market.UseCases.CreateItem can break Market.Adapters.Http, while a change to Market.Adapters.Http can't break Market.UseCases.CreateItem.
- Position
- Below the diagonal: Market.Adapters.Http uses a module listed above it, which is the healthy direction.
34→26 Market.Adapters.Http uses Market.UseCases.DeleteItem✕
- Connections
- 1 pair of types, where a type in Market.Adapters.Http uses a type in Market.UseCases.DeleteItem.
- The types involved
App.Market.Adapters.Http.DeleteItemAction→App.Market.UseCases.DeleteItem.DeleteItem
- Direction
- Market.Adapters.Http uses Market.UseCases.DeleteItem, so a change to Market.UseCases.DeleteItem can break Market.Adapters.Http, while a change to Market.Adapters.Http can't break Market.UseCases.DeleteItem.
- Position
- Below the diagonal: Market.Adapters.Http uses a module listed above it, which is the healthy direction.
34→27 Market.Adapters.Http uses Market.UseCases.Purchase✕
- Connections
- 1 pair of types, where a type in Market.Adapters.Http uses a type in Market.UseCases.Purchase.
- The types involved
App.Market.Adapters.Http.PurchaseAction→App.Market.UseCases.Purchase.Purchase
- Direction
- Market.Adapters.Http uses Market.UseCases.Purchase, so a change to Market.UseCases.Purchase can break Market.Adapters.Http, while a change to Market.Adapters.Http can't break Market.UseCases.Purchase.
- Position
- Below the diagonal: Market.Adapters.Http uses a module listed above it, which is the healthy direction.
34→28 Market.Adapters.Http uses Market.UseCases.UpdateItem✕
- Connections
- 1 pair of types, where a type in Market.Adapters.Http uses a type in Market.UseCases.UpdateItem.
- The types involved
App.Market.Adapters.Http.UpdateItemAction→App.Market.UseCases.UpdateItem.UpdateItem
- Direction
- Market.Adapters.Http uses Market.UseCases.UpdateItem, so a change to Market.UseCases.UpdateItem can break Market.Adapters.Http, while a change to Market.Adapters.Http can't break Market.UseCases.UpdateItem.
- Position
- Below the diagonal: Market.Adapters.Http uses a module listed above it, which is the healthy direction.
35→12 Pokedex.Adapters.Http uses Shared.Adapters.Http✕
- Connections
- 1 pair of types, where a type in Pokedex.Adapters.Http uses a type in Shared.Adapters.Http.
- The types involved
App.Pokedex.Adapters.Http.SearchAction→App.Shared.Adapters.Http.PayloadAction
- Direction
- Pokedex.Adapters.Http uses Shared.Adapters.Http, so a change to Shared.Adapters.Http can break Pokedex.Adapters.Http, while a change to Pokedex.Adapters.Http can't break Shared.Adapters.Http.
- Position
- Below the diagonal: Pokedex.Adapters.Http uses a module listed above it, which is the healthy direction.
35→32 Pokedex.Adapters.Http uses Pokedex.UseCases.Contracts✕
- Connections
- 1 pair of types, where a type in Pokedex.Adapters.Http uses a type in Pokedex.UseCases.Contracts.
- The types involved
App.Pokedex.Adapters.Http.SearchAction→App.Pokedex.UseCases.Contracts.PokemonRepository
- Direction
- Pokedex.Adapters.Http uses Pokedex.UseCases.Contracts, so a change to Pokedex.UseCases.Contracts can break Pokedex.Adapters.Http, while a change to Pokedex.Adapters.Http can't break Pokedex.UseCases.Contracts.
- Position
- Below the diagonal: Pokedex.Adapters.Http uses a module listed above it, which is the healthy direction.
36→3 Pokedex.Adapters.Repository uses Shared.Adapters.Contracts.QueryBuilder✕
- Connections
- 7 pairs of types, where a type in Pokedex.Adapters.Repository uses a type in Shared.Adapters.Contracts.QueryBuilder.
- The types involved
App.Pokedex.Adapters.Repository.PokedexRepository→App.Shared.Adapters.Contracts.QueryBuilder.InsertStatementApp.Pokedex.Adapters.Repository.PokedexRepository→App.Shared.Adapters.Contracts.QueryBuilder.SelectStatementApp.Pokedex.Adapters.Repository.PokedexRepository→App.Shared.Adapters.Contracts.QueryBuilder.UpdateStatementApp.Pokedex.Adapters.Repository.PokemonRepository→App.Shared.Adapters.Contracts.QueryBuilder.InsertStatementApp.Pokedex.Adapters.Repository.PokemonRepository→App.Shared.Adapters.Contracts.QueryBuilder.SelectStatementApp.Pokedex.Adapters.Repository.TypeRepository→App.Shared.Adapters.Contracts.QueryBuilder.InsertStatementApp.Pokedex.Adapters.Repository.TypeRepository→App.Shared.Adapters.Contracts.QueryBuilder.SelectStatement
- Direction
- Pokedex.Adapters.Repository uses Shared.Adapters.Contracts.QueryBuilder, so a change to Shared.Adapters.Contracts.QueryBuilder can break Pokedex.Adapters.Repository, while a change to Pokedex.Adapters.Repository can't break Shared.Adapters.Contracts.QueryBuilder.
- Position
- Below the diagonal: Pokedex.Adapters.Repository uses a module listed above it, which is the healthy direction.
36→11 Pokedex.Adapters.Repository uses Shared.Adapters.Contracts✕
- Connections
- 5 pairs of types, where a type in Pokedex.Adapters.Repository uses a type in Shared.Adapters.Contracts.
- The types involved
App.Pokedex.Adapters.Repository.PokedexRepository→App.Shared.Adapters.Contracts.DatabaseDriverApp.Pokedex.Adapters.Repository.PokemonRepository→App.Shared.Adapters.Contracts.CacheSystemApp.Pokedex.Adapters.Repository.PokemonRepository→App.Shared.Adapters.Contracts.DatabaseDriverApp.Pokedex.Adapters.Repository.PokemonRepository→App.Shared.Adapters.Contracts.PokemonAPIApp.Pokedex.Adapters.Repository.TypeRepository→App.Shared.Adapters.Contracts.DatabaseDriver
- Direction
- Pokedex.Adapters.Repository uses Shared.Adapters.Contracts, so a change to Shared.Adapters.Contracts can break Pokedex.Adapters.Repository, while a change to Pokedex.Adapters.Repository can't break Shared.Adapters.Contracts.
- Position
- Below the diagonal: Pokedex.Adapters.Repository uses a module listed above it, which is the healthy direction.
36→14 Pokedex.Adapters.Repository uses Player.Domain✕
- Connections
- 1 pair of types, where a type in Pokedex.Adapters.Repository uses a type in Player.Domain.
- The types involved
App.Pokedex.Adapters.Repository.PokedexRepository→App.Player.Domain.Player
- Direction
- Pokedex.Adapters.Repository uses Player.Domain, so a change to Player.Domain can break Pokedex.Adapters.Repository, while a change to Pokedex.Adapters.Repository can't break Player.Domain.
- Position
- Below the diagonal: Pokedex.Adapters.Repository uses a module listed above it, which is the healthy direction.
36→22 Pokedex.Adapters.Repository uses Pokedex.Domain✕
- Connections
- 4 pairs of types, where a type in Pokedex.Adapters.Repository uses a type in Pokedex.Domain.
- The types involved
App.Pokedex.Adapters.Repository.PokedexRepository→App.Pokedex.Domain.PokedexApp.Pokedex.Adapters.Repository.PokedexRepository→App.Pokedex.Domain.PokemonApp.Pokedex.Adapters.Repository.PokemonRepository→App.Pokedex.Domain.PokemonApp.Pokedex.Adapters.Repository.TypeRepository→App.Pokedex.Domain.Type
- Direction
- Pokedex.Adapters.Repository uses Pokedex.Domain, so a change to Pokedex.Domain can break Pokedex.Adapters.Repository, while a change to Pokedex.Adapters.Repository can't break Pokedex.Domain.
- Position
- Below the diagonal: Pokedex.Adapters.Repository uses a module listed above it, which is the healthy direction.
36→32 Pokedex.Adapters.Repository uses Pokedex.UseCases.Contracts✕
- Connections
- 4 pairs of types, where a type in Pokedex.Adapters.Repository uses a type in Pokedex.UseCases.Contracts.
- The types involved
App.Pokedex.Adapters.Repository.PokedexRepository→App.Pokedex.UseCases.Contracts.PokedexRepositoryApp.Pokedex.Adapters.Repository.PokemonRepository→App.Pokedex.UseCases.Contracts.PokemonRepositoryApp.Pokedex.Adapters.Repository.PokemonRepository→App.Pokedex.UseCases.Contracts.TypeRepositoryApp.Pokedex.Adapters.Repository.TypeRepository→App.Pokedex.UseCases.Contracts.TypeRepository
- Direction
- Pokedex.Adapters.Repository uses Pokedex.UseCases.Contracts, so a change to Pokedex.UseCases.Contracts can break Pokedex.Adapters.Repository, while a change to Pokedex.Adapters.Repository can't break Pokedex.UseCases.Contracts.
- Position
- Below the diagonal: Pokedex.Adapters.Repository uses a module listed above it, which is the healthy direction.
37→23 Battle.UseCases.Contracts uses Battle.Domain.ValueObjects✕
- Connections
- 1 pair of types, where a type in Battle.UseCases.Contracts uses a type in Battle.Domain.ValueObjects.
- The types involved
App.Battle.UseCases.Contracts.BattleRepository→App.Battle.Domain.ValueObjects.BattlePokemon
- Direction
- Battle.UseCases.Contracts uses Battle.Domain.ValueObjects, so a change to Battle.Domain.ValueObjects can break Battle.UseCases.Contracts, while a change to Battle.UseCases.Contracts can't break Battle.Domain.ValueObjects.
- Position
- Below the diagonal: Battle.UseCases.Contracts uses a module listed above it, which is the healthy direction.
37→33 Battle.UseCases.Contracts uses Battle.Domain✕
- Connections
- 1 pair of types, where a type in Battle.UseCases.Contracts uses a type in Battle.Domain.
- The types involved
App.Battle.UseCases.Contracts.BattleRepository→App.Battle.Domain.Battle
- Direction
- Battle.UseCases.Contracts uses Battle.Domain, so a change to Battle.Domain can break Battle.UseCases.Contracts, while a change to Battle.UseCases.Contracts can't break Battle.Domain.
- Position
- Below the diagonal: Battle.UseCases.Contracts uses a module listed above it, which is the healthy direction.
38→3 Battle.Adapters.Repositories uses Shared.Adapters.Contracts.QueryBuilder✕
- Connections
- 2 pairs of types, where a type in Battle.Adapters.Repositories uses a type in Shared.Adapters.Contracts.QueryBuilder.
- The types involved
App.Battle.Adapters.Repositories.BattleRepository→App.Shared.Adapters.Contracts.QueryBuilder.InsertStatementApp.Battle.Adapters.Repositories.BattleRepository→App.Shared.Adapters.Contracts.QueryBuilder.SelectStatement
- Direction
- Battle.Adapters.Repositories uses Shared.Adapters.Contracts.QueryBuilder, so a change to Shared.Adapters.Contracts.QueryBuilder can break Battle.Adapters.Repositories, while a change to Battle.Adapters.Repositories can't break Shared.Adapters.Contracts.QueryBuilder.
- Position
- Below the diagonal: Battle.Adapters.Repositories uses a module listed above it, which is the healthy direction.
38→21 Battle.Adapters.Repositories uses Player.UseCases.Contracts✕
- Connections
- 1 pair of types, where a type in Battle.Adapters.Repositories uses a type in Player.UseCases.Contracts.
- The types involved
App.Battle.Adapters.Repositories.BattleRepository→App.Player.UseCases.Contracts.PlayerRepository
- Direction
- Battle.Adapters.Repositories uses Player.UseCases.Contracts, so a change to Player.UseCases.Contracts can break Battle.Adapters.Repositories, while a change to Battle.Adapters.Repositories can't break Player.UseCases.Contracts.
- Position
- Below the diagonal: Battle.Adapters.Repositories uses a module listed above it, which is the healthy direction.
38→23 Battle.Adapters.Repositories uses Battle.Domain.ValueObjects✕
- Connections
- 1 pair of types, where a type in Battle.Adapters.Repositories uses a type in Battle.Domain.ValueObjects.
- The types involved
App.Battle.Adapters.Repositories.BattleRepository→App.Battle.Domain.ValueObjects.BattlePokemon
- Direction
- Battle.Adapters.Repositories uses Battle.Domain.ValueObjects, so a change to Battle.Domain.ValueObjects can break Battle.Adapters.Repositories, while a change to Battle.Adapters.Repositories can't break Battle.Domain.ValueObjects.
- Position
- Below the diagonal: Battle.Adapters.Repositories uses a module listed above it, which is the healthy direction.
38→32 Battle.Adapters.Repositories uses Pokedex.UseCases.Contracts✕
- Connections
- 1 pair of types, where a type in Battle.Adapters.Repositories uses a type in Pokedex.UseCases.Contracts.
- The types involved
App.Battle.Adapters.Repositories.BattleRepository→App.Pokedex.UseCases.Contracts.PokemonRepository
- Direction
- Battle.Adapters.Repositories uses Pokedex.UseCases.Contracts, so a change to Pokedex.UseCases.Contracts can break Battle.Adapters.Repositories, while a change to Battle.Adapters.Repositories can't break Pokedex.UseCases.Contracts.
- Position
- Below the diagonal: Battle.Adapters.Repositories uses a module listed above it, which is the healthy direction.
38→33 Battle.Adapters.Repositories uses Battle.Domain✕
- Connections
- 1 pair of types, where a type in Battle.Adapters.Repositories uses a type in Battle.Domain.
- The types involved
App.Battle.Adapters.Repositories.BattleRepository→App.Battle.Domain.Battle
- Direction
- Battle.Adapters.Repositories uses Battle.Domain, so a change to Battle.Domain can break Battle.Adapters.Repositories, while a change to Battle.Adapters.Repositories can't break Battle.Domain.
- Position
- Below the diagonal: Battle.Adapters.Repositories uses a module listed above it, which is the healthy direction.
38→37 Battle.Adapters.Repositories uses Battle.UseCases.Contracts✕
- Connections
- 1 pair of types, where a type in Battle.Adapters.Repositories uses a type in Battle.UseCases.Contracts.
- The types involved
App.Battle.Adapters.Repositories.BattleRepository→App.Battle.UseCases.Contracts.BattleRepository
- Direction
- Battle.Adapters.Repositories uses Battle.UseCases.Contracts, so a change to Battle.UseCases.Contracts can break Battle.Adapters.Repositories, while a change to Battle.Adapters.Repositories can't break Battle.UseCases.Contracts.
- Position
- Below the diagonal: Battle.Adapters.Repositories uses a module listed above it, which is the healthy direction.
39→6 Battle.UseCases.StartBattle uses Shared.Helpers✕
- Connections
- 2 pairs of types, where a type in Battle.UseCases.StartBattle uses a type in Shared.Helpers.
- The types involved
App.Battle.UseCases.StartBattle.InputBoundary→App.Shared.Helpers.DTOApp.Battle.UseCases.StartBattle.OutputBoundary→App.Shared.Helpers.DTO
- Direction
- Battle.UseCases.StartBattle uses Shared.Helpers, so a change to Shared.Helpers can break Battle.UseCases.StartBattle, while a change to Battle.UseCases.StartBattle can't break Shared.Helpers.
- Position
- Below the diagonal: Battle.UseCases.StartBattle uses a module listed above it, which is the healthy direction.
39→11 Battle.UseCases.StartBattle uses Shared.Adapters.Contracts✕
- Connections
- 1 pair of types, where a type in Battle.UseCases.StartBattle uses a type in Shared.Adapters.Contracts.
- The types involved
App.Battle.UseCases.StartBattle.StartBattleValidator→App.Shared.Adapters.Contracts.ValidatorTool
- Direction
- Battle.UseCases.StartBattle uses Shared.Adapters.Contracts, so a change to Shared.Adapters.Contracts can break Battle.UseCases.StartBattle, while a change to Battle.UseCases.StartBattle can't break Shared.Adapters.Contracts.
- Position
- Below the diagonal: Battle.UseCases.StartBattle uses a module listed above it, which is the healthy direction.
39→21 Battle.UseCases.StartBattle uses Player.UseCases.Contracts✕
- Connections
- 1 pair of types, where a type in Battle.UseCases.StartBattle uses a type in Player.UseCases.Contracts.
- The types involved
App.Battle.UseCases.StartBattle.StartBattle→App.Player.UseCases.Contracts.PlayerRepository
- Direction
- Battle.UseCases.StartBattle uses Player.UseCases.Contracts, so a change to Player.UseCases.Contracts can break Battle.UseCases.StartBattle, while a change to Battle.UseCases.StartBattle can't break Player.UseCases.Contracts.
- Position
- Below the diagonal: Battle.UseCases.StartBattle uses a module listed above it, which is the healthy direction.
39→32 Battle.UseCases.StartBattle uses Pokedex.UseCases.Contracts✕
- Connections
- 2 pairs of types, where a type in Battle.UseCases.StartBattle uses a type in Pokedex.UseCases.Contracts.
- The types involved
App.Battle.UseCases.StartBattle.StartBattle→App.Pokedex.UseCases.Contracts.PokedexRepositoryApp.Battle.UseCases.StartBattle.StartBattle→App.Pokedex.UseCases.Contracts.PokemonRepository
- Direction
- Battle.UseCases.StartBattle uses Pokedex.UseCases.Contracts, so a change to Pokedex.UseCases.Contracts can break Battle.UseCases.StartBattle, while a change to Battle.UseCases.StartBattle can't break Pokedex.UseCases.Contracts.
- Position
- Below the diagonal: Battle.UseCases.StartBattle uses a module listed above it, which is the healthy direction.
39→37 Battle.UseCases.StartBattle uses Battle.UseCases.Contracts✕
- Connections
- 1 pair of types, where a type in Battle.UseCases.StartBattle uses a type in Battle.UseCases.Contracts.
- The types involved
App.Battle.UseCases.StartBattle.StartBattle→App.Battle.UseCases.Contracts.BattleRepository
- Direction
- Battle.UseCases.StartBattle uses Battle.UseCases.Contracts, so a change to Battle.UseCases.Contracts can break Battle.UseCases.StartBattle, while a change to Battle.UseCases.StartBattle can't break Battle.UseCases.Contracts.
- Position
- Below the diagonal: Battle.UseCases.StartBattle uses a module listed above it, which is the healthy direction.
40→12 Battle.Adapters.Http uses Shared.Adapters.Http✕
- Connections
- 1 pair of types, where a type in Battle.Adapters.Http uses a type in Shared.Adapters.Http.
- The types involved
App.Battle.Adapters.Http.StartAction→App.Shared.Adapters.Http.PayloadAction
- Direction
- Battle.Adapters.Http uses Shared.Adapters.Http, so a change to Shared.Adapters.Http can break Battle.Adapters.Http, while a change to Battle.Adapters.Http can't break Shared.Adapters.Http.
- Position
- Below the diagonal: Battle.Adapters.Http uses a module listed above it, which is the healthy direction.
40→39 Battle.Adapters.Http uses Battle.UseCases.StartBattle✕
- Connections
- 1 pair of types, where a type in Battle.Adapters.Http uses a type in Battle.UseCases.StartBattle.
- The types involved
App.Battle.Adapters.Http.StartAction→App.Battle.UseCases.StartBattle.StartBattle
- Direction
- Battle.Adapters.Http uses Battle.UseCases.StartBattle, so a change to Battle.UseCases.StartBattle can break Battle.Adapters.Http, while a change to Battle.Adapters.Http can't break Battle.UseCases.StartBattle.
- Position
- Below the diagonal: Battle.Adapters.Http 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 11 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
Roadmap
Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; Log through a PSR-3 logger (Monolog, or Laravel's `Log` facade) with a JSON formatter at meaningful points in the applications you run; Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a CI workflow that builds and runs the test suite on every push/PR. | +6.3 pts | Medium | CI/CD gates |
| Log through a PSR-3 logger (Monolog, or Laravel's `Log` facade) with a JSON formatter at meaningful points in the applications you run. | +6.3 pts | Medium | Observability |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.8 pts | Low | ADR Quality |
| Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices. | +4.2 pts | Medium | Slice cohesion |
| Resolve the 11 Orphaned file finding(s) in Knowledge Freshness — start with Select.php (2), di.php, PayloadAction.php. | +2.8 pts | Medium | Knowledge Freshness |
| 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. | +2.7 pts | Medium | Deployment & Rollback |
| 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. | +2.2 pts | Medium | Nullable reference types |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +0.6 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.4 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.1 | Slop | IaC & Container Security: High IaC: REDACTED |
| src/Shared/Adapters/QueryBuilder/MySQL/Select.php | 7.2 | Mixed | Code Duplication: Duplicated block (36 lines × 2) |
| src/Shared/Adapters/QueryBuilder/MySQL/Delete.php | 7.8 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| src/Shared/Adapters/QueryBuilder/MySQL/Insert.php | 7.8 | Mixed | Code Duplication: Duplicated block (25 lines × 2) |
| src/Shared/Adapters/QueryBuilder/MySQL/Update.php | 7.8 | Mixed | Code Duplication: Duplicated block (19 lines × 2) |
| src/Market/UseCases/Purchase/PurchaseValidator.php | 8.5 | Near-clean | Cognitive Complexity: PurchaseValidator.validate (cognitive 19) |
| src/Shared/Infra/Drivers/MySQLDriver.php | 8.5 | Near-clean | Code Duplication: Duplicated block (20 lines × 2) |
| src/Shared/Adapters/Http/PayloadAction.php | 8.5 | Near-clean | Code Duplication: Duplicated block (14 lines × 2) |
| src/Market/Domain/Factory/ItemFactory.php | 8.5 | Near-clean | Code Duplication: Duplicated block (9 lines × 3) |
| src/Market/Domain/Factory/CartItemFactory.php | 8.5 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
| src/Market/UseCases/CreateItem/OutputBoundary.php | 8.5 | Near-clean | Code Duplication: Duplicated block (41 lines × 3) |
| src/Pokedex/Adapters/Repository/PokemonRepository.php | 8.5 | Near-clean | Code Duplication: Duplicated block (13 lines × 3) |
| src/Player/Domain/Player.php | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: Player (LCOM4 7) |
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 50 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 50 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, 50 of 66 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.
- 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 (2 contributor(s) across 99 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 1 hold 2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (4975 LoC, 129 module-visible types across 47 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 PHP-DI, 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 15 — the compose project is invalid) — yaml: line 37: found character that cannot start any token; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'PDO' is imported (config/di.php:85), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'PDO' is imported (config/di.php:85), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — 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. 'PDO' is imported (config/di.php:85), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — 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. 'PDO' is imported (config/di.php:85), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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 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 is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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".
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was PurchaseValidator.validate at 19.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with PurchaseValidator.validate (cognitive 19). — Refactoring it lifts Cognitive Complexity from 9.7 to about 10.0/10.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
15 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with Select.php (2), CartItemFactory.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (20 lines × 2) finding(s) in Code Duplication — start with Insert.php, MySQLDriver.php. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with Select.php, Update.php. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
1 of 27 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with Player.php. — One of this dimension's main actionable groups (1 warning-level).
D9 · Test Distribution
12 test methods: 12 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 12 tests.
D12 · Dependency Hygiene
7 outdated, 0 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.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 69 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 34 package(s) under `packages-dev` are not installed for a consumer and are excluded.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 5024 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
67 % of calls cross a namespace and 32 % go through an interface, but 68 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. semgrep hit a parse error in 1 file(s) — `REDACTED` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
D30 · Dependency Vulnerabilities
11 finding(s): 2 critical, 3 high, 6 medium, 0 low.
What to do
- Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D31 · IaC & Container Security
5 finding(s): 0 critical, 2 high, 3 medium, 0 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D34 · Knowledge Freshness
11 of 11 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is config/di.php. Counted over 11 of the 135 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 11 Orphaned file finding(s) in Knowledge Freshness — start with Select.php (2), di.php, PayloadAction.php. — One of this dimension's main actionable groups (11 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 14 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX7 · Slice cohesion
- `StartBattle` (slice 'StartBattle') depends on `PlayerRepository` from slice 'Contracts'. — src/Battle/UseCases/StartBattle/StartBattle.php:14
- `CreateItem` (slice 'CreateItem') depends on `ItemRepository` from slice 'Contracts'. — src/Market/UseCases/CreateItem/CreateItem.php:10
- `DeleteItem` (slice 'DeleteItem') depends on `ItemRepository` from slice 'Contracts'. — src/Market/UseCases/DeleteItem/DeleteItem.php:10
- `Purchase` (slice 'Purchase') depends on `PlayerRepository` from slice 'Contracts'. — src/Market/UseCases/Purchase/Purchase.php:11
- `UpdateItem` (slice 'UpdateItem') depends on `ItemRepository` from slice 'Contracts'. — src/Market/UseCases/UpdateItem/UpdateItem.php:10
What to do
- Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability
- No logging call was found in the 136 PHP production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (PHP: PSR-3 loggers (Monolog), Laravel's Log facade, error_log()) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Log through a PSR-3 logger (Monolog, or Laravel's `Log` facade) with a JSON formatter at meaningful points in the applications you run.
- 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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Run what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P7 · Outbound HTTP resilience
P8 · Schema migrations
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
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
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.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 70% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 55% | Adequate — gated by AX7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 66% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 31% | Weak — gated by P1, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 98% | Checked 4 of 9 | Strongest area. |
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'PDO' (config/di.php:85) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'PDO' (config/di.php:85) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'PDO' (config/di.php:85) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 64 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
- 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.
- AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
- 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
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 15 — the compose project is invalid) — yaml: line 37: found character that cannot start any token; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: this repository stores data through 'PDO' (config/di.php:85) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; PHP not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .php, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 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 — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this 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
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
- 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 — no CI workflow found
- 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.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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.
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- 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
- X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 7 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 34 finding(s)
- Cross-slice coupling: StartBattle → Contracts src/Battle/UseCases/StartBattle/StartBattle.php:14
- Cross-slice coupling: CreateItem → Contracts src/Market/UseCases/CreateItem/CreateItem.php:10
- Cross-slice coupling: DeleteItem → Contracts src/Market/UseCases/DeleteItem/DeleteItem.php:10
- Cross-slice coupling: Purchase → Contracts src/Market/UseCases/Purchase/Purchase.php:11
- Cross-slice coupling: UpdateItem → Contracts src/Market/UseCases/UpdateItem/UpdateItem.php:10
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) src/Market/Domain/Factory/CartItemFactory.php:23
- Duplicated block (9 lines × 2) src/Shared/Adapters/QueryBuilder/MySQL/Select.php:29
- Duplicated block (9 lines × 2) src/Shared/Adapters/QueryBuilder/MySQL/Select.php:42
- Duplicated block (20 lines × 2) src/Shared/Adapters/QueryBuilder/MySQL/Insert.php:36
- Duplicated block (20 lines × 2) src/Shared/Infra/Drivers/MySQLDriver.php:84
- Duplicated block (7 lines × 2) src/Shared/Adapters/QueryBuilder/MySQL/Select.php:72
- Duplicated block (7 lines × 2) src/Shared/Adapters/QueryBuilder/MySQL/Update.php:42
- PurchaseValidator.validate (cognitive 19) src/Market/UseCases/Purchase/PurchaseValidator.php:19
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/Shared/Adapters/QueryBuilder/MySQL/Delete.php:50
- Duplicated block (36 lines × 2) src/Shared/Adapters/QueryBuilder/MySQL/Select.php:130
- Duplicated block (25 lines × 2) src/Shared/Adapters/QueryBuilder/MySQL/Insert.php:60
- Duplicated block (19 lines × 2) src/Shared/Adapters/QueryBuilder/MySQL/Update.php:61
- Duplicated block (14 lines × 2) src/Shared/Adapters/Http/PayloadAction.php:52
- Duplicated block (11 lines × 4) src/Shared/Adapters/QueryBuilder/MySQL/Delete.php:52
- Duplicated block (9 lines × 3) src/Market/Domain/Factory/ItemFactory.php:21
- Duplicated block (41 lines × 3) src/Market/UseCases/CreateItem/OutputBoundary.php:23
- Duplicated block (13 lines × 3) src/Pokedex/Adapters/Repository/PokemonRepository.php:47
- Low cohesion: Player (LCOM4 7) src/Player/Domain/Player.php:10
- No CI pipeline
- No structured logging
Minor — 18 finding(s)
- Orphaned file config/di.php:1
- Orphaned file src/Shared/Adapters/QueryBuilder/MySQL/Select.php:1
- Orphaned file src/Shared/Adapters/QueryBuilder/Postgres/Select.php:1
- Orphaned file src/Shared/Adapters/Http/PayloadAction.php:1
- Orphaned file src/Battle/Domain/Battle.php:1
- Orphaned file src/Market/Adapters/Repository/ItemRepository.php:1
- Orphaned file src/Pokedex/Domain/Pokemon.php:1
- Orphaned file src/Player/Domain/Player.php:1
- Orphaned file src/Battle/UseCases/StartBattle/StartBattle.php:1
- Orphaned file src/Shared/Infra/Drivers/PostgresDriver.php:1
- Orphaned file src/Shared/Infra/Drivers/MySQLDriver.php:1
- No ADRs found
- High interface indirection
- Orphaned files with no living knowledge
- No ADRs
- No SAST
- No rollback/health safety
- PHP static analysis does not check null everywhere
Minor — 7 finding(s)
- Outdated: http-interop/http-factory-guzzle
- Outdated: nyholm/psr7
- Outdated: nyholm/psr7-server
- Outdated: slim/psr7
- Outdated: slim/slim
- Outdated: twig/twig
- Outdated: vlucas/phpdotenv
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-40cac24903374f0db18439a828046a97/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-40cac24903374f0db18439a828046a97/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 11 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |