Executive summary
karlomikus/bar-assistant falls short of our standard for production because it has pages that don't say their language. It scores 47.8 out of 100 and is rated Weak, and 24 of its 27 critical findings are security problems in the build pipeline and in its servers and containers.
Accessibility, at 37.3, is the weakest lens and counts most in the score. The best first step is structuring the pages, worth about 9.4 points. Keeping the encryption keys in a vault comes next, worth about 4.2 points. Raising Accessibility to 70 would lift the score to about 56.4.
Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Six secrets can leak from the build pipeline, and two settings leave the servers or containers unsafe. Pinning each tool to an exact version, limiting each secret to its own step and correcting the unsafe settings would close these risks. The two pages that don't say their language need their language set.
The product code is 41,617 lines, about €75,000 to rebuild.
If Accessibility rose from 37.3 to 70, the lowest score rated Strong, the score would rise from 47.8 to about 56.4.
Rebuild cost: about €75,000 · Estimate
| Cost to rebuild | €25,000 to €120,000, for 413 to 1,312 hours of work, about 0.5 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 48. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 41,617 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 BarAssistant.Domain.Event | 2 BarAssistant.Domain | 3 Kami.Cocktail.Http.Resources | 4 BarAssistant.Domain.User | 5 BarAssistant.Application.User | 6 BarAssistant.Domain.Common | 7 BarAssistant.Domain.Calculator | 8 BarAssistant.Domain.Image | 9 BarAssistant.Domain.Note | 10 BarAssistant.Application.Calculator | 11 BarAssistant.Application.Image | 12 BarAssistant.Domain.Ingredient | 13 BarAssistant.Domain.Cocktail | 14 BarAssistant.Application.Cocktail | 15 BarAssistant.Domain.Bar | 16 BarAssistant.Application.Bar | 17 BarAssistant.Application.Matcher | 18 BarAssistant.Domain.Export | 19 BarAssistant.Domain.IngredientHierarchy | 20 BarAssistant.Domain.Menu | 21 BarAssistant.Domain.Rating | 22 BarAssistant.Domain.Recommendation | 23 BarAssistant.Domain.Review | 24 BarAssistant.Application.Export | 25 BarAssistant.Application.Ingredient | 26 BarAssistant.Application.Recommendation | 27 Kami.Cocktail.External | 28 Kami.Cocktail.OpenAPI.Schemas | 29 Kami.Cocktail.Services.Auth | 30 Kami.Cocktail.Models.ValueObjects | 31 Kami.Cocktail.Models | 32 Kami.Cocktail.External.Model | 33 Kami.Cocktail.Infrastructure | 34 Kami.Cocktail.Services | 35 Kami.Cocktail.Services.Image | 36 Kami.Cocktail.External.Export | 37 Kami.Cocktail.External.Import | 38 Kami.Cocktail.Console.Commands | 39 Kami.Cocktail.Http.Controllers | 40 Kami.Cocktail.Jobs |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 BarAssistant.Domain.Event | ||||||||||||||||||||||||||||||||||||||||
| 2 BarAssistant.Domain | 2 | |||||||||||||||||||||||||||||||||||||||
| 3 Kami.Cocktail.Http.Resources | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 BarAssistant.Domain.User | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 5 BarAssistant.Application.User | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 BarAssistant.Domain.Common | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 7 BarAssistant.Domain.Calculator | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 8 BarAssistant.Domain.Image | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 9 BarAssistant.Domain.Note | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 10 BarAssistant.Application.Calculator | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 BarAssistant.Application.Image | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 BarAssistant.Domain.Ingredient | 3 | 1 | 13 | 1 | 5 | |||||||||||||||||||||||||||||||||||
| 13 BarAssistant.Domain.Cocktail | 6 | 1 | 25 | 2 | 10 | |||||||||||||||||||||||||||||||||||
| 14 BarAssistant.Application.Cocktail | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 15 BarAssistant.Domain.Bar | 3 | 4 | 11 | 5 | 2 | |||||||||||||||||||||||||||||||||||
| 16 BarAssistant.Application.Bar | 10 | |||||||||||||||||||||||||||||||||||||||
| 17 BarAssistant.Application.Matcher | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 BarAssistant.Domain.Export | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 BarAssistant.Domain.IngredientHierarchy | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 20 BarAssistant.Domain.Menu | 2 | 3 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 21 BarAssistant.Domain.Rating | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 22 BarAssistant.Domain.Recommendation | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 BarAssistant.Domain.Review | 2 | 6 | 4 | |||||||||||||||||||||||||||||||||||||
| 24 BarAssistant.Application.Export | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 BarAssistant.Application.Ingredient | 4 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 26 BarAssistant.Application.Recommendation | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 Kami.Cocktail.External | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Kami.Cocktail.OpenAPI.Schemas | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 29 Kami.Cocktail.Services.Auth | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 30 Kami.Cocktail.Models.ValueObjects | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 Kami.Cocktail.Models | 1 | 1 | 7 | |||||||||||||||||||||||||||||||||||||
| 32 Kami.Cocktail.External.Model | 19 | 3 | 9 | |||||||||||||||||||||||||||||||||||||
| 33 Kami.Cocktail.Infrastructure | 5 | 1 | 3 | 3 | 3 | 9 | 17 | 27 | 3 | 2 | 3 | 5 | 2 | 6 | 20 | |||||||||||||||||||||||||
| 34 Kami.Cocktail.Services | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 Kami.Cocktail.Services.Image | 2 | 6 | ||||||||||||||||||||||||||||||||||||||
| 36 Kami.Cocktail.External.Export | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 37 Kami.Cocktail.External.Import | 1 | 1 | 4 | 1 | 3 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||
| 38 Kami.Cocktail.Console.Commands | 2 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 Kami.Cocktail.Http.Controllers | 11 | 1 | 1 | 2 | 5 | 8 | 1 | 2 | 1 | 2 | 2 | 2 | 2 | 8 | 7 | 1 | ||||||||||||||||||||||||
| 40 Kami.Cocktail.Jobs | 1 | 3 | 2 | 1 | 2 |
2→1 BarAssistant.Domain uses BarAssistant.Domain.Event✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Domain uses a type in BarAssistant.Domain.Event.
- The types involved
BarAssistant.Domain.DomainEventDispatcher→BarAssistant.Domain.Event.DomainEventBarAssistant.Domain.DomainEventDispatcher→BarAssistant.Domain.Event.EventSubscriber
- Direction
- BarAssistant.Domain uses BarAssistant.Domain.Event, so a change to BarAssistant.Domain.Event can break BarAssistant.Domain, while a change to BarAssistant.Domain can't break BarAssistant.Domain.Event.
- Position
- Below the diagonal: BarAssistant.Domain uses a module listed above it, which is the healthy direction.
3→31 Kami.Cocktail.Http.Resources uses Kami.Cocktail.Models part of a loop✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Http.Resources uses a type in Kami.Cocktail.Models.
- The types involved
Kami.Cocktail.Http.Resources.AmountFormats→Kami.Cocktail.Models.CocktailIngredient
- Direction
- Kami.Cocktail.Http.Resources uses Kami.Cocktail.Models, so a change to Kami.Cocktail.Models can break Kami.Cocktail.Http.Resources, while a change to Kami.Cocktail.Http.Resources can't break Kami.Cocktail.Models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→2 BarAssistant.Domain.User uses BarAssistant.Domain✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.User uses a type in BarAssistant.Domain.
- The types involved
BarAssistant.Domain.User.User→BarAssistant.Domain.Identity
- Direction
- BarAssistant.Domain.User uses BarAssistant.Domain, so a change to BarAssistant.Domain can break BarAssistant.Domain.User, while a change to BarAssistant.Domain.User can't break BarAssistant.Domain.
- Position
- Below the diagonal: BarAssistant.Domain.User uses a module listed above it, which is the healthy direction.
4→6 BarAssistant.Domain.User uses BarAssistant.Domain.Common part of a loop✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Domain.User uses a type in BarAssistant.Domain.Common.
- The types involved
BarAssistant.Domain.User.User→BarAssistant.Domain.Common.RecordTimestampsBarAssistant.Domain.User.UserId→BarAssistant.Domain.Common.IntegerIdentifier
- Direction
- BarAssistant.Domain.User uses BarAssistant.Domain.Common, so a change to BarAssistant.Domain.Common can break BarAssistant.Domain.User, while a change to BarAssistant.Domain.User can't break BarAssistant.Domain.Common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→4 BarAssistant.Application.User uses BarAssistant.Domain.User✕
- Connections
- 1 pair of types, where a type in BarAssistant.Application.User uses a type in BarAssistant.Domain.User.
- The types involved
BarAssistant.Application.User.UserService→BarAssistant.Domain.User.UserRepository
- Direction
- BarAssistant.Application.User uses BarAssistant.Domain.User, so a change to BarAssistant.Domain.User can break BarAssistant.Application.User, while a change to BarAssistant.Application.User can't break BarAssistant.Domain.User.
- Position
- Below the diagonal: BarAssistant.Application.User uses a module listed above it, which is the healthy direction.
6→2 BarAssistant.Domain.Common uses BarAssistant.Domain✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Common uses a type in BarAssistant.Domain.
- The types involved
BarAssistant.Domain.Common.IntegerIdentifier→BarAssistant.Domain.Identifier
- Direction
- BarAssistant.Domain.Common uses BarAssistant.Domain, so a change to BarAssistant.Domain can break BarAssistant.Domain.Common, while a change to BarAssistant.Domain.Common can't break BarAssistant.Domain.
- Position
- Below the diagonal: BarAssistant.Domain.Common uses a module listed above it, which is the healthy direction.
6→4 BarAssistant.Domain.Common uses BarAssistant.Domain.User✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Common uses a type in BarAssistant.Domain.User.
- The types involved
BarAssistant.Domain.Common.Authors→BarAssistant.Domain.User.UserId
- Direction
- BarAssistant.Domain.Common uses BarAssistant.Domain.User, so a change to BarAssistant.Domain.User can break BarAssistant.Domain.Common, while a change to BarAssistant.Domain.Common can't break BarAssistant.Domain.User.
- Position
- Below the diagonal: BarAssistant.Domain.Common uses a module listed above it, which is the healthy direction.
7→2 BarAssistant.Domain.Calculator uses BarAssistant.Domain✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Calculator uses a type in BarAssistant.Domain.
- The types involved
BarAssistant.Domain.Calculator.Calculator→BarAssistant.Domain.Identity
- Direction
- BarAssistant.Domain.Calculator uses BarAssistant.Domain, so a change to BarAssistant.Domain can break BarAssistant.Domain.Calculator, while a change to BarAssistant.Domain.Calculator can't break BarAssistant.Domain.
- Position
- Below the diagonal: BarAssistant.Domain.Calculator uses a module listed above it, which is the healthy direction.
7→6 BarAssistant.Domain.Calculator uses BarAssistant.Domain.Common✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Domain.Calculator uses a type in BarAssistant.Domain.Common.
- The types involved
BarAssistant.Domain.Calculator.Calculator→BarAssistant.Domain.Common.RecordTimestampsBarAssistant.Domain.Calculator.CalculatorId→BarAssistant.Domain.Common.IntegerIdentifier
- Direction
- BarAssistant.Domain.Calculator uses BarAssistant.Domain.Common, so a change to BarAssistant.Domain.Common can break BarAssistant.Domain.Calculator, while a change to BarAssistant.Domain.Calculator can't break BarAssistant.Domain.Common.
- Position
- Below the diagonal: BarAssistant.Domain.Calculator uses a module listed above it, which is the healthy direction.
7→15 BarAssistant.Domain.Calculator uses BarAssistant.Domain.Bar part of a loop✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Calculator uses a type in BarAssistant.Domain.Bar.
- The types involved
BarAssistant.Domain.Calculator.Calculator→BarAssistant.Domain.Bar.BarId
- Direction
- BarAssistant.Domain.Calculator uses BarAssistant.Domain.Bar, so a change to BarAssistant.Domain.Bar can break BarAssistant.Domain.Calculator, while a change to BarAssistant.Domain.Calculator can't break BarAssistant.Domain.Bar.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→2 BarAssistant.Domain.Image uses BarAssistant.Domain✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Image uses a type in BarAssistant.Domain.
- The types involved
BarAssistant.Domain.Image.Image→BarAssistant.Domain.Identity
- Direction
- BarAssistant.Domain.Image uses BarAssistant.Domain, so a change to BarAssistant.Domain can break BarAssistant.Domain.Image, while a change to BarAssistant.Domain.Image can't break BarAssistant.Domain.
- Position
- Below the diagonal: BarAssistant.Domain.Image uses a module listed above it, which is the healthy direction.
8→4 BarAssistant.Domain.Image uses BarAssistant.Domain.User✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Image uses a type in BarAssistant.Domain.User.
- The types involved
BarAssistant.Domain.Image.Image→BarAssistant.Domain.User.UserId
- Direction
- BarAssistant.Domain.Image uses BarAssistant.Domain.User, so a change to BarAssistant.Domain.User can break BarAssistant.Domain.Image, while a change to BarAssistant.Domain.Image can't break BarAssistant.Domain.User.
- Position
- Below the diagonal: BarAssistant.Domain.Image uses a module listed above it, which is the healthy direction.
8→6 BarAssistant.Domain.Image uses BarAssistant.Domain.Common✕
- Connections
- 4 pairs of types, where a type in BarAssistant.Domain.Image uses a type in BarAssistant.Domain.Common.
- The types involved
BarAssistant.Domain.Image.Image→BarAssistant.Domain.Common.AuthorsBarAssistant.Domain.Image.Image→BarAssistant.Domain.Common.FileBarAssistant.Domain.Image.Image→BarAssistant.Domain.Common.RecordTimestampsBarAssistant.Domain.Image.ImageId→BarAssistant.Domain.Common.IntegerIdentifier
- Direction
- BarAssistant.Domain.Image uses BarAssistant.Domain.Common, so a change to BarAssistant.Domain.Common can break BarAssistant.Domain.Image, while a change to BarAssistant.Domain.Image can't break BarAssistant.Domain.Common.
- Position
- Below the diagonal: BarAssistant.Domain.Image uses a module listed above it, which is the healthy direction.
9→2 BarAssistant.Domain.Note uses BarAssistant.Domain✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Note uses a type in BarAssistant.Domain.
- The types involved
BarAssistant.Domain.Note.Note→BarAssistant.Domain.Identity
- Direction
- BarAssistant.Domain.Note uses BarAssistant.Domain, so a change to BarAssistant.Domain can break BarAssistant.Domain.Note, while a change to BarAssistant.Domain.Note can't break BarAssistant.Domain.
- Position
- Below the diagonal: BarAssistant.Domain.Note uses a module listed above it, which is the healthy direction.
9→4 BarAssistant.Domain.Note uses BarAssistant.Domain.User✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Note uses a type in BarAssistant.Domain.User.
- The types involved
BarAssistant.Domain.Note.Note→BarAssistant.Domain.User.UserId
- Direction
- BarAssistant.Domain.Note uses BarAssistant.Domain.User, so a change to BarAssistant.Domain.User can break BarAssistant.Domain.Note, while a change to BarAssistant.Domain.Note can't break BarAssistant.Domain.User.
- Position
- Below the diagonal: BarAssistant.Domain.Note uses a module listed above it, which is the healthy direction.
9→6 BarAssistant.Domain.Note uses BarAssistant.Domain.Common✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Domain.Note uses a type in BarAssistant.Domain.Common.
- The types involved
BarAssistant.Domain.Note.Note→BarAssistant.Domain.Common.RecordTimestampsBarAssistant.Domain.Note.NoteId→BarAssistant.Domain.Common.IntegerIdentifier
- Direction
- BarAssistant.Domain.Note uses BarAssistant.Domain.Common, so a change to BarAssistant.Domain.Common can break BarAssistant.Domain.Note, while a change to BarAssistant.Domain.Note can't break BarAssistant.Domain.Common.
- Position
- Below the diagonal: BarAssistant.Domain.Note uses a module listed above it, which is the healthy direction.
10→7 BarAssistant.Application.Calculator uses BarAssistant.Domain.Calculator✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Application.Calculator uses a type in BarAssistant.Domain.Calculator.
- The types involved
BarAssistant.Application.Calculator.CalculatorService→BarAssistant.Domain.Calculator.CalculatorBarAssistant.Application.Calculator.CalculatorService→BarAssistant.Domain.Calculator.CalculatorRepository
- Direction
- BarAssistant.Application.Calculator uses BarAssistant.Domain.Calculator, so a change to BarAssistant.Domain.Calculator can break BarAssistant.Application.Calculator, while a change to BarAssistant.Application.Calculator can't break BarAssistant.Domain.Calculator.
- Position
- Below the diagonal: BarAssistant.Application.Calculator uses a module listed above it, which is the healthy direction.
11→8 BarAssistant.Application.Image uses BarAssistant.Domain.Image✕
- Connections
- 1 pair of types, where a type in BarAssistant.Application.Image uses a type in BarAssistant.Domain.Image.
- The types involved
BarAssistant.Application.Image.ImageService→BarAssistant.Domain.Image.ImageRepository
- Direction
- BarAssistant.Application.Image uses BarAssistant.Domain.Image, so a change to BarAssistant.Domain.Image can break BarAssistant.Application.Image, while a change to BarAssistant.Application.Image can't break BarAssistant.Domain.Image.
- Position
- Below the diagonal: BarAssistant.Application.Image uses a module listed above it, which is the healthy direction.
12→2 BarAssistant.Domain.Ingredient uses BarAssistant.Domain✕
- Connections
- 3 pairs of types, where a type in BarAssistant.Domain.Ingredient uses a type in BarAssistant.Domain.
- The types involved
BarAssistant.Domain.Ingredient.Ingredient→BarAssistant.Domain.IdentityBarAssistant.Domain.Ingredient.IngredientMatch→BarAssistant.Domain.IdentityBarAssistant.Domain.Ingredient.PriceCategory→BarAssistant.Domain.Identity
- Direction
- BarAssistant.Domain.Ingredient uses BarAssistant.Domain, so a change to BarAssistant.Domain can break BarAssistant.Domain.Ingredient, while a change to BarAssistant.Domain.Ingredient can't break BarAssistant.Domain.
- Position
- Below the diagonal: BarAssistant.Domain.Ingredient uses a module listed above it, which is the healthy direction.
12→4 BarAssistant.Domain.Ingredient uses BarAssistant.Domain.User✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Ingredient uses a type in BarAssistant.Domain.User.
- The types involved
BarAssistant.Domain.Ingredient.Ingredient→BarAssistant.Domain.User.UserId
- Direction
- BarAssistant.Domain.Ingredient uses BarAssistant.Domain.User, so a change to BarAssistant.Domain.User can break BarAssistant.Domain.Ingredient, while a change to BarAssistant.Domain.Ingredient can't break BarAssistant.Domain.User.
- Position
- Below the diagonal: BarAssistant.Domain.Ingredient uses a module listed above it, which is the healthy direction.
12→6 BarAssistant.Domain.Ingredient uses BarAssistant.Domain.Common✕
- Connections
- 13 pairs of types, where a type in BarAssistant.Domain.Ingredient uses a type in BarAssistant.Domain.Common.
- The types involved
BarAssistant.Domain.Ingredient.ComplexIngredientPart→BarAssistant.Domain.Common.AmountWithUnitsBarAssistant.Domain.Ingredient.Ingredient→BarAssistant.Domain.Common.ABVBarAssistant.Domain.Ingredient.Ingredient→BarAssistant.Domain.Common.AuthorsBarAssistant.Domain.Ingredient.Ingredient→BarAssistant.Domain.Common.ColorBarAssistant.Domain.Ingredient.Ingredient→BarAssistant.Domain.Common.NameBarAssistant.Domain.Ingredient.Ingredient→BarAssistant.Domain.Common.RecordTimestampsBarAssistant.Domain.Ingredient.Ingredient→BarAssistant.Domain.Common.UnitBarAssistant.Domain.Ingredient.IngredientId→BarAssistant.Domain.Common.IntegerIdentifierBarAssistant.Domain.Ingredient.IngredientMatch→BarAssistant.Domain.Common.NameBarAssistant.Domain.Ingredient.IngredientPrice→BarAssistant.Domain.Common.AmountWithUnitsBarAssistant.Domain.Ingredient.IngredientPrice→BarAssistant.Domain.Common.PriceBarAssistant.Domain.Ingredient.PriceCategory→BarAssistant.Domain.Common.NameBarAssistant.Domain.Ingredient.PriceCategoryId→BarAssistant.Domain.Common.IntegerIdentifier
- Direction
- BarAssistant.Domain.Ingredient uses BarAssistant.Domain.Common, so a change to BarAssistant.Domain.Common can break BarAssistant.Domain.Ingredient, while a change to BarAssistant.Domain.Ingredient can't break BarAssistant.Domain.Common.
- Position
- Below the diagonal: BarAssistant.Domain.Ingredient uses a module listed above it, which is the healthy direction.
12→7 BarAssistant.Domain.Ingredient uses BarAssistant.Domain.Calculator✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Ingredient uses a type in BarAssistant.Domain.Calculator.
- The types involved
BarAssistant.Domain.Ingredient.Ingredient→BarAssistant.Domain.Calculator.CalculatorId
- Direction
- BarAssistant.Domain.Ingredient uses BarAssistant.Domain.Calculator, so a change to BarAssistant.Domain.Calculator can break BarAssistant.Domain.Ingredient, while a change to BarAssistant.Domain.Ingredient can't break BarAssistant.Domain.Calculator.
- Position
- Below the diagonal: BarAssistant.Domain.Ingredient uses a module listed above it, which is the healthy direction.
12→15 BarAssistant.Domain.Ingredient uses BarAssistant.Domain.Bar part of a loop✕
- Connections
- 5 pairs of types, where a type in BarAssistant.Domain.Ingredient uses a type in BarAssistant.Domain.Bar.
- The types involved
BarAssistant.Domain.Ingredient.Ingredient→BarAssistant.Domain.Bar.BarIdBarAssistant.Domain.Ingredient.IngredientMatchRepository→BarAssistant.Domain.Bar.BarIdBarAssistant.Domain.Ingredient.IngredientRepository→BarAssistant.Domain.Bar.BarIdBarAssistant.Domain.Ingredient.PriceCategory→BarAssistant.Domain.Bar.BarIdBarAssistant.Domain.Ingredient.PriceCategoryRepository→BarAssistant.Domain.Bar.BarId
- Direction
- BarAssistant.Domain.Ingredient uses BarAssistant.Domain.Bar, so a change to BarAssistant.Domain.Bar can break BarAssistant.Domain.Ingredient, while a change to BarAssistant.Domain.Ingredient can't break BarAssistant.Domain.Bar.
- 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.
13→2 BarAssistant.Domain.Cocktail uses BarAssistant.Domain✕
- Connections
- 6 pairs of types, where a type in BarAssistant.Domain.Cocktail uses a type in BarAssistant.Domain.
- The types involved
BarAssistant.Domain.Cocktail.Cocktail→BarAssistant.Domain.IdentityBarAssistant.Domain.Cocktail.CocktailCollection→BarAssistant.Domain.IdentityBarAssistant.Domain.Cocktail.CocktailMatch→BarAssistant.Domain.IdentityBarAssistant.Domain.Cocktail.CocktailMethod→BarAssistant.Domain.IdentityBarAssistant.Domain.Cocktail.Glass→BarAssistant.Domain.IdentityBarAssistant.Domain.Cocktail.Utensil→BarAssistant.Domain.Identity
- Direction
- BarAssistant.Domain.Cocktail uses BarAssistant.Domain, so a change to BarAssistant.Domain can break BarAssistant.Domain.Cocktail, while a change to BarAssistant.Domain.Cocktail can't break BarAssistant.Domain.
- Position
- Below the diagonal: BarAssistant.Domain.Cocktail uses a module listed above it, which is the healthy direction.
13→4 BarAssistant.Domain.Cocktail uses BarAssistant.Domain.User✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Cocktail uses a type in BarAssistant.Domain.User.
- The types involved
BarAssistant.Domain.Cocktail.Cocktail→BarAssistant.Domain.User.UserId
- Direction
- BarAssistant.Domain.Cocktail uses BarAssistant.Domain.User, so a change to BarAssistant.Domain.User can break BarAssistant.Domain.Cocktail, while a change to BarAssistant.Domain.Cocktail can't break BarAssistant.Domain.User.
- Position
- Below the diagonal: BarAssistant.Domain.Cocktail uses a module listed above it, which is the healthy direction.
13→6 BarAssistant.Domain.Cocktail uses BarAssistant.Domain.Common✕
- Connections
- 25 pairs of types, where a type in BarAssistant.Domain.Cocktail uses a type in BarAssistant.Domain.Common.
- The types involved
BarAssistant.Domain.Cocktail.Cocktail→BarAssistant.Domain.Common.ABVBarAssistant.Domain.Cocktail.Cocktail→BarAssistant.Domain.Common.AuthorsBarAssistant.Domain.Cocktail.Cocktail→BarAssistant.Domain.Common.DilutionBarAssistant.Domain.Cocktail.Cocktail→BarAssistant.Domain.Common.NameBarAssistant.Domain.Cocktail.Cocktail→BarAssistant.Domain.Common.RecordTimestampsBarAssistant.Domain.Cocktail.Cocktail→BarAssistant.Domain.Common.SlugBarAssistant.Domain.Cocktail.CocktailCollection→BarAssistant.Domain.Common.NameBarAssistant.Domain.Cocktail.CocktailCollection→BarAssistant.Domain.Common.RecordTimestampsBarAssistant.Domain.Cocktail.CocktailId→BarAssistant.Domain.Common.IntegerIdentifierBarAssistant.Domain.Cocktail.CocktailIngredient→BarAssistant.Domain.Common.ABVBarAssistant.Domain.Cocktail.CocktailIngredient→BarAssistant.Domain.Common.AmountWithUnitsBarAssistant.Domain.Cocktail.CocktailIngredientSubstitute→BarAssistant.Domain.Common.AmountWithUnitsBarAssistant.Domain.Cocktail.CocktailMatch→BarAssistant.Domain.Common.NameBarAssistant.Domain.Cocktail.CocktailMethod→BarAssistant.Domain.Common.DilutionBarAssistant.Domain.Cocktail.CocktailMethod→BarAssistant.Domain.Common.NameBarAssistant.Domain.Cocktail.CocktailMethod→BarAssistant.Domain.Common.RecordTimestampsBarAssistant.Domain.Cocktail.CollectionId→BarAssistant.Domain.Common.IntegerIdentifierBarAssistant.Domain.Cocktail.Glass→BarAssistant.Domain.Common.AmountWithUnitsBarAssistant.Domain.Cocktail.Glass→BarAssistant.Domain.Common.NameBarAssistant.Domain.Cocktail.Glass→BarAssistant.Domain.Common.RecordTimestampsBarAssistant.Domain.Cocktail.GlassId→BarAssistant.Domain.Common.IntegerIdentifierBarAssistant.Domain.Cocktail.MethodId→BarAssistant.Domain.Common.IntegerIdentifierBarAssistant.Domain.Cocktail.Utensil→BarAssistant.Domain.Common.NameBarAssistant.Domain.Cocktail.Utensil→BarAssistant.Domain.Common.RecordTimestampsBarAssistant.Domain.Cocktail.UtensilId→BarAssistant.Domain.Common.IntegerIdentifier
- Direction
- BarAssistant.Domain.Cocktail uses BarAssistant.Domain.Common, so a change to BarAssistant.Domain.Common can break BarAssistant.Domain.Cocktail, while a change to BarAssistant.Domain.Cocktail can't break BarAssistant.Domain.Common.
- Position
- Below the diagonal: BarAssistant.Domain.Cocktail uses a module listed above it, which is the healthy direction.
13→12 BarAssistant.Domain.Cocktail uses BarAssistant.Domain.Ingredient✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Domain.Cocktail uses a type in BarAssistant.Domain.Ingredient.
- The types involved
BarAssistant.Domain.Cocktail.CocktailIngredient→BarAssistant.Domain.Ingredient.IngredientIdBarAssistant.Domain.Cocktail.CocktailIngredientSubstitute→BarAssistant.Domain.Ingredient.IngredientId
- Direction
- BarAssistant.Domain.Cocktail uses BarAssistant.Domain.Ingredient, so a change to BarAssistant.Domain.Ingredient can break BarAssistant.Domain.Cocktail, while a change to BarAssistant.Domain.Cocktail can't break BarAssistant.Domain.Ingredient.
- Position
- Below the diagonal: BarAssistant.Domain.Cocktail uses a module listed above it, which is the healthy direction.
13→15 BarAssistant.Domain.Cocktail uses BarAssistant.Domain.Bar part of a loop✕
- Connections
- 10 pairs of types, where a type in BarAssistant.Domain.Cocktail uses a type in BarAssistant.Domain.Bar.
- The types involved
BarAssistant.Domain.Cocktail.Cocktail→BarAssistant.Domain.Bar.BarIdBarAssistant.Domain.Cocktail.CocktailCollection→BarAssistant.Domain.Bar.BarIdBarAssistant.Domain.Cocktail.CocktailCollection→BarAssistant.Domain.Bar.MemberIdBarAssistant.Domain.Cocktail.CocktailMatchRepository→BarAssistant.Domain.Bar.BarIdBarAssistant.Domain.Cocktail.CocktailMethod→BarAssistant.Domain.Bar.BarIdBarAssistant.Domain.Cocktail.CocktailMethodRepository→BarAssistant.Domain.Bar.BarIdBarAssistant.Domain.Cocktail.Glass→BarAssistant.Domain.Bar.BarIdBarAssistant.Domain.Cocktail.GlassRepository→BarAssistant.Domain.Bar.BarIdBarAssistant.Domain.Cocktail.ShelfCocktailQueryRepository→BarAssistant.Domain.Bar.BarIdBarAssistant.Domain.Cocktail.Utensil→BarAssistant.Domain.Bar.BarId
- Direction
- BarAssistant.Domain.Cocktail uses BarAssistant.Domain.Bar, so a change to BarAssistant.Domain.Bar can break BarAssistant.Domain.Cocktail, while a change to BarAssistant.Domain.Cocktail can't break BarAssistant.Domain.Bar.
- 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.
14→12 BarAssistant.Application.Cocktail uses BarAssistant.Domain.Ingredient✕
- Connections
- 1 pair of types, where a type in BarAssistant.Application.Cocktail uses a type in BarAssistant.Domain.Ingredient.
- The types involved
BarAssistant.Application.Cocktail.ShelfCocktailService→BarAssistant.Domain.Ingredient.ComplexIngredientResolver
- Direction
- BarAssistant.Application.Cocktail uses BarAssistant.Domain.Ingredient, so a change to BarAssistant.Domain.Ingredient can break BarAssistant.Application.Cocktail, while a change to BarAssistant.Application.Cocktail can't break BarAssistant.Domain.Ingredient.
- Position
- Below the diagonal: BarAssistant.Application.Cocktail uses a module listed above it, which is the healthy direction.
14→13 BarAssistant.Application.Cocktail uses BarAssistant.Domain.Cocktail✕
- Connections
- 7 pairs of types, where a type in BarAssistant.Application.Cocktail uses a type in BarAssistant.Domain.Cocktail.
- The types involved
BarAssistant.Application.Cocktail.CocktailMethodService→BarAssistant.Domain.Cocktail.CocktailMethodRepositoryBarAssistant.Application.Cocktail.CocktailService→BarAssistant.Domain.Cocktail.CocktailRepositoryBarAssistant.Application.Cocktail.CollectionService→BarAssistant.Domain.Cocktail.CocktailCollectionRepositoryBarAssistant.Application.Cocktail.GlassService→BarAssistant.Domain.Cocktail.GlassBarAssistant.Application.Cocktail.GlassService→BarAssistant.Domain.Cocktail.GlassRepositoryBarAssistant.Application.Cocktail.ShelfCocktailService→BarAssistant.Domain.Cocktail.ShelfCocktailQueryRepositoryBarAssistant.Application.Cocktail.UtensilService→BarAssistant.Domain.Cocktail.UtensilRepository
- Direction
- BarAssistant.Application.Cocktail uses BarAssistant.Domain.Cocktail, so a change to BarAssistant.Domain.Cocktail can break BarAssistant.Application.Cocktail, while a change to BarAssistant.Application.Cocktail can't break BarAssistant.Domain.Cocktail.
- Position
- Below the diagonal: BarAssistant.Application.Cocktail uses a module listed above it, which is the healthy direction.
15→2 BarAssistant.Domain.Bar uses BarAssistant.Domain✕
- Connections
- 3 pairs of types, where a type in BarAssistant.Domain.Bar uses a type in BarAssistant.Domain.
- The types involved
BarAssistant.Domain.Bar.Bar→BarAssistant.Domain.IdentityBarAssistant.Domain.Bar.Member→BarAssistant.Domain.IdentityBarAssistant.Domain.Bar.MemberInventory→BarAssistant.Domain.Identity
- Direction
- BarAssistant.Domain.Bar uses BarAssistant.Domain, so a change to BarAssistant.Domain can break BarAssistant.Domain.Bar, while a change to BarAssistant.Domain.Bar can't break BarAssistant.Domain.
- Position
- Below the diagonal: BarAssistant.Domain.Bar uses a module listed above it, which is the healthy direction.
15→4 BarAssistant.Domain.Bar uses BarAssistant.Domain.User✕
- Connections
- 4 pairs of types, where a type in BarAssistant.Domain.Bar uses a type in BarAssistant.Domain.User.
- The types involved
BarAssistant.Domain.Bar.Bar→BarAssistant.Domain.User.UserIdBarAssistant.Domain.Bar.Member→BarAssistant.Domain.User.UserIdBarAssistant.Domain.Bar.MemberInventory→BarAssistant.Domain.User.UserIdBarAssistant.Domain.Bar.MemberRepository→BarAssistant.Domain.User.UserId
- Direction
- BarAssistant.Domain.Bar uses BarAssistant.Domain.User, so a change to BarAssistant.Domain.User can break BarAssistant.Domain.Bar, while a change to BarAssistant.Domain.Bar can't break BarAssistant.Domain.User.
- Position
- Below the diagonal: BarAssistant.Domain.Bar uses a module listed above it, which is the healthy direction.
15→6 BarAssistant.Domain.Bar uses BarAssistant.Domain.Common✕
- Connections
- 11 pairs of types, where a type in BarAssistant.Domain.Bar uses a type in BarAssistant.Domain.Common.
- The types involved
BarAssistant.Domain.Bar.Bar→BarAssistant.Domain.Common.AuthorsBarAssistant.Domain.Bar.Bar→BarAssistant.Domain.Common.NameBarAssistant.Domain.Bar.Bar→BarAssistant.Domain.Common.RecordTimestampsBarAssistant.Domain.Bar.Bar→BarAssistant.Domain.Common.SlugBarAssistant.Domain.Bar.Bar→BarAssistant.Domain.Common.UnitBarAssistant.Domain.Bar.BarId→BarAssistant.Domain.Common.IntegerIdentifierBarAssistant.Domain.Bar.BarSettings→BarAssistant.Domain.Common.UnitBarAssistant.Domain.Bar.MemberId→BarAssistant.Domain.Common.IntegerIdentifierBarAssistant.Domain.Bar.MemberInventory→BarAssistant.Domain.Common.NameBarAssistant.Domain.Bar.MemberInventoryId→BarAssistant.Domain.Common.IntegerIdentifierBarAssistant.Domain.Bar.MemberInventoryRepository→BarAssistant.Domain.Common.Name
- Direction
- BarAssistant.Domain.Bar uses BarAssistant.Domain.Common, so a change to BarAssistant.Domain.Common can break BarAssistant.Domain.Bar, while a change to BarAssistant.Domain.Bar can't break BarAssistant.Domain.Common.
- Position
- Below the diagonal: BarAssistant.Domain.Bar uses a module listed above it, which is the healthy direction.
15→12 BarAssistant.Domain.Bar uses BarAssistant.Domain.Ingredient✕
- Connections
- 5 pairs of types, where a type in BarAssistant.Domain.Bar uses a type in BarAssistant.Domain.Ingredient.
- The types involved
BarAssistant.Domain.Bar.BarInventory→BarAssistant.Domain.Ingredient.IngredientIdBarAssistant.Domain.Bar.IngredientInventoryItem→BarAssistant.Domain.Ingredient.IngredientIdBarAssistant.Domain.Bar.Member→BarAssistant.Domain.Ingredient.IngredientIdBarAssistant.Domain.Bar.MemberInventory→BarAssistant.Domain.Ingredient.IngredientIdBarAssistant.Domain.Bar.ShoppingListItem→BarAssistant.Domain.Ingredient.IngredientId
- Direction
- BarAssistant.Domain.Bar uses BarAssistant.Domain.Ingredient, so a change to BarAssistant.Domain.Ingredient can break BarAssistant.Domain.Bar, while a change to BarAssistant.Domain.Bar can't break BarAssistant.Domain.Ingredient.
- Position
- Below the diagonal: BarAssistant.Domain.Bar uses a module listed above it, which is the healthy direction.
15→13 BarAssistant.Domain.Bar uses BarAssistant.Domain.Cocktail✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Domain.Bar uses a type in BarAssistant.Domain.Cocktail.
- The types involved
BarAssistant.Domain.Bar.CocktailFavorite→BarAssistant.Domain.Cocktail.CocktailIdBarAssistant.Domain.Bar.Member→BarAssistant.Domain.Cocktail.CocktailId
- Direction
- BarAssistant.Domain.Bar uses BarAssistant.Domain.Cocktail, so a change to BarAssistant.Domain.Cocktail can break BarAssistant.Domain.Bar, while a change to BarAssistant.Domain.Bar can't break BarAssistant.Domain.Cocktail.
- Position
- Below the diagonal: BarAssistant.Domain.Bar uses a module listed above it, which is the healthy direction.
16→15 BarAssistant.Application.Bar uses BarAssistant.Domain.Bar✕
- Connections
- 10 pairs of types, where a type in BarAssistant.Application.Bar uses a type in BarAssistant.Domain.Bar.
- The types involved
BarAssistant.Application.Bar.BarService→BarAssistant.Domain.Bar.BarBarAssistant.Application.Bar.BarService→BarAssistant.Domain.Bar.BarRepositoryBarAssistant.Application.Bar.FavoriteService→BarAssistant.Domain.Bar.MemberRepositoryBarAssistant.Application.Bar.InventoryService→BarAssistant.Domain.Bar.BarInventoryRepositoryBarAssistant.Application.Bar.MemberInventoryService→BarAssistant.Domain.Bar.MemberInventoryBarAssistant.Application.Bar.MemberInventoryService→BarAssistant.Domain.Bar.MemberInventoryIdBarAssistant.Application.Bar.MemberInventoryService→BarAssistant.Domain.Bar.MemberInventoryRepositoryBarAssistant.Application.Bar.MemberService→BarAssistant.Domain.Bar.MemberBarAssistant.Application.Bar.MemberService→BarAssistant.Domain.Bar.MemberRepositoryBarAssistant.Application.Bar.ShoppingListService→BarAssistant.Domain.Bar.MemberRepository
- Direction
- BarAssistant.Application.Bar uses BarAssistant.Domain.Bar, so a change to BarAssistant.Domain.Bar can break BarAssistant.Application.Bar, while a change to BarAssistant.Application.Bar can't break BarAssistant.Domain.Bar.
- Position
- Below the diagonal: BarAssistant.Application.Bar uses a module listed above it, which is the healthy direction.
17→12 BarAssistant.Application.Matcher uses BarAssistant.Domain.Ingredient✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Application.Matcher uses a type in BarAssistant.Domain.Ingredient.
- The types involved
BarAssistant.Application.Matcher.IngredientMatcher→BarAssistant.Domain.Ingredient.IngredientMatchRepositoryBarAssistant.Application.Matcher.IngredientMatcher→BarAssistant.Domain.Ingredient.IngredientRepository
- Direction
- BarAssistant.Application.Matcher uses BarAssistant.Domain.Ingredient, so a change to BarAssistant.Domain.Ingredient can break BarAssistant.Application.Matcher, while a change to BarAssistant.Application.Matcher can't break BarAssistant.Domain.Ingredient.
- Position
- Below the diagonal: BarAssistant.Application.Matcher uses a module listed above it, which is the healthy direction.
17→13 BarAssistant.Application.Matcher uses BarAssistant.Domain.Cocktail✕
- Connections
- 3 pairs of types, where a type in BarAssistant.Application.Matcher uses a type in BarAssistant.Domain.Cocktail.
- The types involved
BarAssistant.Application.Matcher.CocktailMatcher→BarAssistant.Domain.Cocktail.CocktailMatchRepositoryBarAssistant.Application.Matcher.GlassMatcher→BarAssistant.Domain.Cocktail.GlassRepositoryBarAssistant.Application.Matcher.MethodMatcher→BarAssistant.Domain.Cocktail.CocktailMethodRepository
- Direction
- BarAssistant.Application.Matcher uses BarAssistant.Domain.Cocktail, so a change to BarAssistant.Domain.Cocktail can break BarAssistant.Application.Matcher, while a change to BarAssistant.Application.Matcher can't break BarAssistant.Domain.Cocktail.
- Position
- Below the diagonal: BarAssistant.Application.Matcher uses a module listed above it, which is the healthy direction.
17→15 BarAssistant.Application.Matcher uses BarAssistant.Domain.Bar✕
- Connections
- 1 pair of types, where a type in BarAssistant.Application.Matcher uses a type in BarAssistant.Domain.Bar.
- The types involved
BarAssistant.Application.Matcher.IngredientMatcher→BarAssistant.Domain.Bar.BarId
- Direction
- BarAssistant.Application.Matcher uses BarAssistant.Domain.Bar, so a change to BarAssistant.Domain.Bar can break BarAssistant.Application.Matcher, while a change to BarAssistant.Application.Matcher can't break BarAssistant.Domain.Bar.
- Position
- Below the diagonal: BarAssistant.Application.Matcher uses a module listed above it, which is the healthy direction.
18→2 BarAssistant.Domain.Export uses BarAssistant.Domain✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Export uses a type in BarAssistant.Domain.
- The types involved
BarAssistant.Domain.Export.Export→BarAssistant.Domain.Identity
- Direction
- BarAssistant.Domain.Export uses BarAssistant.Domain, so a change to BarAssistant.Domain can break BarAssistant.Domain.Export, while a change to BarAssistant.Domain.Export can't break BarAssistant.Domain.
- Position
- Below the diagonal: BarAssistant.Domain.Export uses a module listed above it, which is the healthy direction.
18→4 BarAssistant.Domain.Export uses BarAssistant.Domain.User✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Export uses a type in BarAssistant.Domain.User.
- The types involved
BarAssistant.Domain.Export.Export→BarAssistant.Domain.User.UserId
- Direction
- BarAssistant.Domain.Export uses BarAssistant.Domain.User, so a change to BarAssistant.Domain.User can break BarAssistant.Domain.Export, while a change to BarAssistant.Domain.Export can't break BarAssistant.Domain.User.
- Position
- Below the diagonal: BarAssistant.Domain.Export uses a module listed above it, which is the healthy direction.
18→6 BarAssistant.Domain.Export uses BarAssistant.Domain.Common✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Domain.Export uses a type in BarAssistant.Domain.Common.
- The types involved
BarAssistant.Domain.Export.Export→BarAssistant.Domain.Common.RecordTimestampsBarAssistant.Domain.Export.ExportId→BarAssistant.Domain.Common.IntegerIdentifier
- Direction
- BarAssistant.Domain.Export uses BarAssistant.Domain.Common, so a change to BarAssistant.Domain.Common can break BarAssistant.Domain.Export, while a change to BarAssistant.Domain.Export can't break BarAssistant.Domain.Common.
- Position
- Below the diagonal: BarAssistant.Domain.Export uses a module listed above it, which is the healthy direction.
18→15 BarAssistant.Domain.Export uses BarAssistant.Domain.Bar✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Export uses a type in BarAssistant.Domain.Bar.
- The types involved
BarAssistant.Domain.Export.Export→BarAssistant.Domain.Bar.BarId
- Direction
- BarAssistant.Domain.Export uses BarAssistant.Domain.Bar, so a change to BarAssistant.Domain.Bar can break BarAssistant.Domain.Export, while a change to BarAssistant.Domain.Export can't break BarAssistant.Domain.Bar.
- Position
- Below the diagonal: BarAssistant.Domain.Export uses a module listed above it, which is the healthy direction.
19→2 BarAssistant.Domain.IngredientHierarchy uses BarAssistant.Domain✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.IngredientHierarchy uses a type in BarAssistant.Domain.
- The types involved
BarAssistant.Domain.IngredientHierarchy.IngredientHierarchyNode→BarAssistant.Domain.Identity
- Direction
- BarAssistant.Domain.IngredientHierarchy uses BarAssistant.Domain, so a change to BarAssistant.Domain can break BarAssistant.Domain.IngredientHierarchy, while a change to BarAssistant.Domain.IngredientHierarchy can't break BarAssistant.Domain.
- Position
- Below the diagonal: BarAssistant.Domain.IngredientHierarchy uses a module listed above it, which is the healthy direction.
19→12 BarAssistant.Domain.IngredientHierarchy uses BarAssistant.Domain.Ingredient✕
- Connections
- 3 pairs of types, where a type in BarAssistant.Domain.IngredientHierarchy uses a type in BarAssistant.Domain.Ingredient.
- The types involved
BarAssistant.Domain.IngredientHierarchy.IngredientHierarchyNode→BarAssistant.Domain.Ingredient.IngredientIdBarAssistant.Domain.IngredientHierarchy.IngredientHierarchyNode→BarAssistant.Domain.Ingredient.MaterializedPathBarAssistant.Domain.IngredientHierarchy.IngredientHierarchyRepository→BarAssistant.Domain.Ingredient.IngredientId
- Direction
- BarAssistant.Domain.IngredientHierarchy uses BarAssistant.Domain.Ingredient, so a change to BarAssistant.Domain.Ingredient can break BarAssistant.Domain.IngredientHierarchy, while a change to BarAssistant.Domain.IngredientHierarchy can't break BarAssistant.Domain.Ingredient.
- Position
- Below the diagonal: BarAssistant.Domain.IngredientHierarchy uses a module listed above it, which is the healthy direction.
19→15 BarAssistant.Domain.IngredientHierarchy uses BarAssistant.Domain.Bar✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Domain.IngredientHierarchy uses a type in BarAssistant.Domain.Bar.
- The types involved
BarAssistant.Domain.IngredientHierarchy.IngredientHierarchyNode→BarAssistant.Domain.Bar.BarIdBarAssistant.Domain.IngredientHierarchy.IngredientHierarchyRepository→BarAssistant.Domain.Bar.BarId
- Direction
- BarAssistant.Domain.IngredientHierarchy uses BarAssistant.Domain.Bar, so a change to BarAssistant.Domain.Bar can break BarAssistant.Domain.IngredientHierarchy, while a change to BarAssistant.Domain.IngredientHierarchy can't break BarAssistant.Domain.Bar.
- Position
- Below the diagonal: BarAssistant.Domain.IngredientHierarchy uses a module listed above it, which is the healthy direction.
20→2 BarAssistant.Domain.Menu uses BarAssistant.Domain✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Domain.Menu uses a type in BarAssistant.Domain.
- The types involved
BarAssistant.Domain.Menu.Menu→BarAssistant.Domain.IdentityBarAssistant.Domain.Menu.MenuId→BarAssistant.Domain.Identifier
- Direction
- BarAssistant.Domain.Menu uses BarAssistant.Domain, so a change to BarAssistant.Domain can break BarAssistant.Domain.Menu, while a change to BarAssistant.Domain.Menu can't break BarAssistant.Domain.
- Position
- Below the diagonal: BarAssistant.Domain.Menu uses a module listed above it, which is the healthy direction.
20→6 BarAssistant.Domain.Menu uses BarAssistant.Domain.Common✕
- Connections
- 3 pairs of types, where a type in BarAssistant.Domain.Menu uses a type in BarAssistant.Domain.Common.
- The types involved
BarAssistant.Domain.Menu.Menu→BarAssistant.Domain.Common.RecordTimestampsBarAssistant.Domain.Menu.MenuCategory→BarAssistant.Domain.Common.NameBarAssistant.Domain.Menu.MenuItem→BarAssistant.Domain.Common.Price
- Direction
- BarAssistant.Domain.Menu uses BarAssistant.Domain.Common, so a change to BarAssistant.Domain.Common can break BarAssistant.Domain.Menu, while a change to BarAssistant.Domain.Menu can't break BarAssistant.Domain.Common.
- Position
- Below the diagonal: BarAssistant.Domain.Menu uses a module listed above it, which is the healthy direction.
20→12 BarAssistant.Domain.Menu uses BarAssistant.Domain.Ingredient✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Menu uses a type in BarAssistant.Domain.Ingredient.
- The types involved
BarAssistant.Domain.Menu.MenuItem→BarAssistant.Domain.Ingredient.IngredientId
- Direction
- BarAssistant.Domain.Menu uses BarAssistant.Domain.Ingredient, so a change to BarAssistant.Domain.Ingredient can break BarAssistant.Domain.Menu, while a change to BarAssistant.Domain.Menu can't break BarAssistant.Domain.Ingredient.
- Position
- Below the diagonal: BarAssistant.Domain.Menu uses a module listed above it, which is the healthy direction.
20→13 BarAssistant.Domain.Menu uses BarAssistant.Domain.Cocktail✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Menu uses a type in BarAssistant.Domain.Cocktail.
- The types involved
BarAssistant.Domain.Menu.MenuItem→BarAssistant.Domain.Cocktail.CocktailId
- Direction
- BarAssistant.Domain.Menu uses BarAssistant.Domain.Cocktail, so a change to BarAssistant.Domain.Cocktail can break BarAssistant.Domain.Menu, while a change to BarAssistant.Domain.Menu can't break BarAssistant.Domain.Cocktail.
- Position
- Below the diagonal: BarAssistant.Domain.Menu uses a module listed above it, which is the healthy direction.
20→15 BarAssistant.Domain.Menu uses BarAssistant.Domain.Bar✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Domain.Menu uses a type in BarAssistant.Domain.Bar.
- The types involved
BarAssistant.Domain.Menu.Menu→BarAssistant.Domain.Bar.BarIdBarAssistant.Domain.Menu.MenuRepository→BarAssistant.Domain.Bar.BarId
- Direction
- BarAssistant.Domain.Menu uses BarAssistant.Domain.Bar, so a change to BarAssistant.Domain.Bar can break BarAssistant.Domain.Menu, while a change to BarAssistant.Domain.Menu can't break BarAssistant.Domain.Bar.
- Position
- Below the diagonal: BarAssistant.Domain.Menu uses a module listed above it, which is the healthy direction.
21→2 BarAssistant.Domain.Rating uses BarAssistant.Domain✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Rating uses a type in BarAssistant.Domain.
- The types involved
BarAssistant.Domain.Rating.Rating→BarAssistant.Domain.Identity
- Direction
- BarAssistant.Domain.Rating uses BarAssistant.Domain, so a change to BarAssistant.Domain can break BarAssistant.Domain.Rating, while a change to BarAssistant.Domain.Rating can't break BarAssistant.Domain.
- Position
- Below the diagonal: BarAssistant.Domain.Rating uses a module listed above it, which is the healthy direction.
21→6 BarAssistant.Domain.Rating uses BarAssistant.Domain.Common✕
- Connections
- 3 pairs of types, where a type in BarAssistant.Domain.Rating uses a type in BarAssistant.Domain.Common.
- The types involved
BarAssistant.Domain.Rating.RateableId→BarAssistant.Domain.Common.IntegerIdentifierBarAssistant.Domain.Rating.Rating→BarAssistant.Domain.Common.RatingValueBarAssistant.Domain.Rating.RatingId→BarAssistant.Domain.Common.IntegerIdentifier
- Direction
- BarAssistant.Domain.Rating uses BarAssistant.Domain.Common, so a change to BarAssistant.Domain.Common can break BarAssistant.Domain.Rating, while a change to BarAssistant.Domain.Rating can't break BarAssistant.Domain.Common.
- Position
- Below the diagonal: BarAssistant.Domain.Rating uses a module listed above it, which is the healthy direction.
21→15 BarAssistant.Domain.Rating uses BarAssistant.Domain.Bar✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Domain.Rating uses a type in BarAssistant.Domain.Bar.
- The types involved
BarAssistant.Domain.Rating.Rating→BarAssistant.Domain.Bar.MemberIdBarAssistant.Domain.Rating.RatingRepository→BarAssistant.Domain.Bar.MemberId
- Direction
- BarAssistant.Domain.Rating uses BarAssistant.Domain.Bar, so a change to BarAssistant.Domain.Bar can break BarAssistant.Domain.Rating, while a change to BarAssistant.Domain.Rating can't break BarAssistant.Domain.Bar.
- Position
- Below the diagonal: BarAssistant.Domain.Rating uses a module listed above it, which is the healthy direction.
22→6 BarAssistant.Domain.Recommendation uses BarAssistant.Domain.Common✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Domain.Recommendation uses a type in BarAssistant.Domain.Common.
- The types involved
BarAssistant.Domain.Recommendation.CocktailTagCount→BarAssistant.Domain.Common.NameBarAssistant.Domain.Recommendation.WeightedIngredient→BarAssistant.Domain.Common.Name
- Direction
- BarAssistant.Domain.Recommendation uses BarAssistant.Domain.Common, so a change to BarAssistant.Domain.Common can break BarAssistant.Domain.Recommendation, while a change to BarAssistant.Domain.Recommendation can't break BarAssistant.Domain.Common.
- Position
- Below the diagonal: BarAssistant.Domain.Recommendation uses a module listed above it, which is the healthy direction.
22→12 BarAssistant.Domain.Recommendation uses BarAssistant.Domain.Ingredient✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Recommendation uses a type in BarAssistant.Domain.Ingredient.
- The types involved
BarAssistant.Domain.Recommendation.WeightedIngredient→BarAssistant.Domain.Ingredient.IngredientId
- Direction
- BarAssistant.Domain.Recommendation uses BarAssistant.Domain.Ingredient, so a change to BarAssistant.Domain.Ingredient can break BarAssistant.Domain.Recommendation, while a change to BarAssistant.Domain.Recommendation can't break BarAssistant.Domain.Ingredient.
- Position
- Below the diagonal: BarAssistant.Domain.Recommendation uses a module listed above it, which is the healthy direction.
22→13 BarAssistant.Domain.Recommendation uses BarAssistant.Domain.Cocktail✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Domain.Recommendation uses a type in BarAssistant.Domain.Cocktail.
- The types involved
BarAssistant.Domain.Recommendation.CocktailWithDetails→BarAssistant.Domain.Cocktail.CocktailIdBarAssistant.Domain.Recommendation.RecommendationResult→BarAssistant.Domain.Cocktail.CocktailId
- Direction
- BarAssistant.Domain.Recommendation uses BarAssistant.Domain.Cocktail, so a change to BarAssistant.Domain.Cocktail can break BarAssistant.Domain.Recommendation, while a change to BarAssistant.Domain.Recommendation can't break BarAssistant.Domain.Cocktail.
- Position
- Below the diagonal: BarAssistant.Domain.Recommendation uses a module listed above it, which is the healthy direction.
22→15 BarAssistant.Domain.Recommendation uses BarAssistant.Domain.Bar✕
- Connections
- 1 pair of types, where a type in BarAssistant.Domain.Recommendation uses a type in BarAssistant.Domain.Bar.
- The types involved
BarAssistant.Domain.Recommendation.RecommendationRepository→BarAssistant.Domain.Bar.MemberId
- Direction
- BarAssistant.Domain.Recommendation uses BarAssistant.Domain.Bar, so a change to BarAssistant.Domain.Bar can break BarAssistant.Domain.Recommendation, while a change to BarAssistant.Domain.Recommendation can't break BarAssistant.Domain.Bar.
- Position
- Below the diagonal: BarAssistant.Domain.Recommendation uses a module listed above it, which is the healthy direction.
23→2 BarAssistant.Domain.Review uses BarAssistant.Domain✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Domain.Review uses a type in BarAssistant.Domain.
- The types involved
BarAssistant.Domain.Review.IngredientReview→BarAssistant.Domain.IdentityBarAssistant.Domain.Review.Review→BarAssistant.Domain.Identity
- Direction
- BarAssistant.Domain.Review uses BarAssistant.Domain, so a change to BarAssistant.Domain can break BarAssistant.Domain.Review, while a change to BarAssistant.Domain.Review can't break BarAssistant.Domain.
- Position
- Below the diagonal: BarAssistant.Domain.Review uses a module listed above it, which is the healthy direction.
23→6 BarAssistant.Domain.Review uses BarAssistant.Domain.Common✕
- Connections
- 6 pairs of types, where a type in BarAssistant.Domain.Review uses a type in BarAssistant.Domain.Common.
- The types involved
BarAssistant.Domain.Review.IngredientReview→BarAssistant.Domain.Common.RecordTimestampsBarAssistant.Domain.Review.IngredientReview→BarAssistant.Domain.Common.ReviewContentBarAssistant.Domain.Review.IngredientReviewId→BarAssistant.Domain.Common.IntegerIdentifierBarAssistant.Domain.Review.Review→BarAssistant.Domain.Common.RecordTimestampsBarAssistant.Domain.Review.Review→BarAssistant.Domain.Common.ReviewContentBarAssistant.Domain.Review.ReviewId→BarAssistant.Domain.Common.IntegerIdentifier
- Direction
- BarAssistant.Domain.Review uses BarAssistant.Domain.Common, so a change to BarAssistant.Domain.Common can break BarAssistant.Domain.Review, while a change to BarAssistant.Domain.Review can't break BarAssistant.Domain.Common.
- Position
- Below the diagonal: BarAssistant.Domain.Review uses a module listed above it, which is the healthy direction.
23→15 BarAssistant.Domain.Review uses BarAssistant.Domain.Bar✕
- Connections
- 4 pairs of types, where a type in BarAssistant.Domain.Review uses a type in BarAssistant.Domain.Bar.
- The types involved
BarAssistant.Domain.Review.IngredientReview→BarAssistant.Domain.Bar.MemberIdBarAssistant.Domain.Review.IngredientReviewRepository→BarAssistant.Domain.Bar.MemberIdBarAssistant.Domain.Review.Review→BarAssistant.Domain.Bar.MemberIdBarAssistant.Domain.Review.ReviewRepository→BarAssistant.Domain.Bar.MemberId
- Direction
- BarAssistant.Domain.Review uses BarAssistant.Domain.Bar, so a change to BarAssistant.Domain.Bar can break BarAssistant.Domain.Review, while a change to BarAssistant.Domain.Review can't break BarAssistant.Domain.Bar.
- Position
- Below the diagonal: BarAssistant.Domain.Review uses a module listed above it, which is the healthy direction.
24→15 BarAssistant.Application.Export uses BarAssistant.Domain.Bar✕
- Connections
- 1 pair of types, where a type in BarAssistant.Application.Export uses a type in BarAssistant.Domain.Bar.
- The types involved
BarAssistant.Application.Export.ExportService→BarAssistant.Domain.Bar.BarRepository
- Direction
- BarAssistant.Application.Export uses BarAssistant.Domain.Bar, so a change to BarAssistant.Domain.Bar can break BarAssistant.Application.Export, while a change to BarAssistant.Application.Export can't break BarAssistant.Domain.Bar.
- Position
- Below the diagonal: BarAssistant.Application.Export uses a module listed above it, which is the healthy direction.
24→18 BarAssistant.Application.Export uses BarAssistant.Domain.Export✕
- Connections
- 1 pair of types, where a type in BarAssistant.Application.Export uses a type in BarAssistant.Domain.Export.
- The types involved
BarAssistant.Application.Export.ExportService→BarAssistant.Domain.Export.ExportRepository
- Direction
- BarAssistant.Application.Export uses BarAssistant.Domain.Export, so a change to BarAssistant.Domain.Export can break BarAssistant.Application.Export, while a change to BarAssistant.Application.Export can't break BarAssistant.Domain.Export.
- Position
- Below the diagonal: BarAssistant.Application.Export uses a module listed above it, which is the healthy direction.
25→12 BarAssistant.Application.Ingredient uses BarAssistant.Domain.Ingredient✕
- Connections
- 4 pairs of types, where a type in BarAssistant.Application.Ingredient uses a type in BarAssistant.Domain.Ingredient.
- The types involved
BarAssistant.Application.Ingredient.IngredientService→BarAssistant.Domain.Ingredient.IngredientBarAssistant.Application.Ingredient.IngredientService→BarAssistant.Domain.Ingredient.IngredientRepositoryBarAssistant.Application.Ingredient.IngredientService→BarAssistant.Domain.Ingredient.PriceCategoryRepositoryBarAssistant.Application.Ingredient.PriceCategoryService→BarAssistant.Domain.Ingredient.PriceCategoryRepository
- Direction
- BarAssistant.Application.Ingredient uses BarAssistant.Domain.Ingredient, so a change to BarAssistant.Domain.Ingredient can break BarAssistant.Application.Ingredient, while a change to BarAssistant.Application.Ingredient can't break BarAssistant.Domain.Ingredient.
- Position
- Below the diagonal: BarAssistant.Application.Ingredient uses a module listed above it, which is the healthy direction.
25→15 BarAssistant.Application.Ingredient uses BarAssistant.Domain.Bar✕
- Connections
- 1 pair of types, where a type in BarAssistant.Application.Ingredient uses a type in BarAssistant.Domain.Bar.
- The types involved
BarAssistant.Application.Ingredient.IngredientService→BarAssistant.Domain.Bar.BarId
- Direction
- BarAssistant.Application.Ingredient uses BarAssistant.Domain.Bar, so a change to BarAssistant.Domain.Bar can break BarAssistant.Application.Ingredient, while a change to BarAssistant.Application.Ingredient can't break BarAssistant.Domain.Bar.
- Position
- Below the diagonal: BarAssistant.Application.Ingredient uses a module listed above it, which is the healthy direction.
25→19 BarAssistant.Application.Ingredient uses BarAssistant.Domain.IngredientHierarchy✕
- Connections
- 3 pairs of types, where a type in BarAssistant.Application.Ingredient uses a type in BarAssistant.Domain.IngredientHierarchy.
- The types involved
BarAssistant.Application.Ingredient.IngredientService→BarAssistant.Domain.IngredientHierarchy.IngredientHierarchyManagerBarAssistant.Application.Ingredient.IngredientService→BarAssistant.Domain.IngredientHierarchy.IngredientHierarchyNodeBarAssistant.Application.Ingredient.IngredientService→BarAssistant.Domain.IngredientHierarchy.IngredientHierarchyRepository
- Direction
- BarAssistant.Application.Ingredient uses BarAssistant.Domain.IngredientHierarchy, so a change to BarAssistant.Domain.IngredientHierarchy can break BarAssistant.Application.Ingredient, while a change to BarAssistant.Application.Ingredient can't break BarAssistant.Domain.IngredientHierarchy.
- Position
- Below the diagonal: BarAssistant.Application.Ingredient uses a module listed above it, which is the healthy direction.
26→15 BarAssistant.Application.Recommendation uses BarAssistant.Domain.Bar✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Application.Recommendation uses a type in BarAssistant.Domain.Bar.
- The types involved
BarAssistant.Application.Recommendation.RecommendationService→BarAssistant.Domain.Bar.BarInventoryRepositoryBarAssistant.Application.Recommendation.RecommendationService→BarAssistant.Domain.Bar.MemberRepository
- Direction
- BarAssistant.Application.Recommendation uses BarAssistant.Domain.Bar, so a change to BarAssistant.Domain.Bar can break BarAssistant.Application.Recommendation, while a change to BarAssistant.Application.Recommendation can't break BarAssistant.Domain.Bar.
- Position
- Below the diagonal: BarAssistant.Application.Recommendation uses a module listed above it, which is the healthy direction.
26→22 BarAssistant.Application.Recommendation uses BarAssistant.Domain.Recommendation✕
- Connections
- 2 pairs of types, where a type in BarAssistant.Application.Recommendation uses a type in BarAssistant.Domain.Recommendation.
- The types involved
BarAssistant.Application.Recommendation.RecommendationService→BarAssistant.Domain.Recommendation.RecommendationRepositoryBarAssistant.Application.Recommendation.RecommendationService→BarAssistant.Domain.Recommendation.RecommendationScoringService
- Direction
- BarAssistant.Application.Recommendation uses BarAssistant.Domain.Recommendation, so a change to BarAssistant.Domain.Recommendation can break BarAssistant.Application.Recommendation, while a change to BarAssistant.Application.Recommendation can't break BarAssistant.Domain.Recommendation.
- Position
- Below the diagonal: BarAssistant.Application.Recommendation uses a module listed above it, which is the healthy direction.
27→25 Kami.Cocktail.External uses BarAssistant.Application.Ingredient✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.External uses a type in BarAssistant.Application.Ingredient.
- The types involved
Kami.Cocktail.External.Matcher→BarAssistant.Application.Ingredient.IngredientService
- Direction
- Kami.Cocktail.External uses BarAssistant.Application.Ingredient, so a change to BarAssistant.Application.Ingredient can break Kami.Cocktail.External, while a change to Kami.Cocktail.External can't break BarAssistant.Application.Ingredient.
- Position
- Below the diagonal: Kami.Cocktail.External uses a module listed above it, which is the healthy direction.
28→3 Kami.Cocktail.OpenAPI.Schemas uses Kami.Cocktail.Http.Resources✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.OpenAPI.Schemas uses a type in Kami.Cocktail.Http.Resources.
- The types involved
Kami.Cocktail.OpenAPI.Schemas.IngredientHierarchy→Kami.Cocktail.Http.Resources.IngredientBasicResourceKami.Cocktail.OpenAPI.Schemas.IngredientRecommend→Kami.Cocktail.Http.Resources.IngredientBasicResource
- Direction
- Kami.Cocktail.OpenAPI.Schemas uses Kami.Cocktail.Http.Resources, so a change to Kami.Cocktail.Http.Resources can break Kami.Cocktail.OpenAPI.Schemas, while a change to Kami.Cocktail.OpenAPI.Schemas can't break Kami.Cocktail.Http.Resources.
- Position
- Below the diagonal: Kami.Cocktail.OpenAPI.Schemas uses a module listed above it, which is the healthy direction.
28→27 Kami.Cocktail.OpenAPI.Schemas uses Kami.Cocktail.External✕
- Connections
- 3 pairs of types, where a type in Kami.Cocktail.OpenAPI.Schemas uses a type in Kami.Cocktail.External.
- The types involved
Kami.Cocktail.OpenAPI.Schemas.BarRequest→Kami.Cocktail.External.BarOptionsEnumKami.Cocktail.OpenAPI.Schemas.ExportRequest→Kami.Cocktail.External.ExportTypeEnumKami.Cocktail.OpenAPI.Schemas.ExportRequest→Kami.Cocktail.External.ForceUnitConvertEnum
- Direction
- Kami.Cocktail.OpenAPI.Schemas uses Kami.Cocktail.External, so a change to Kami.Cocktail.External can break Kami.Cocktail.OpenAPI.Schemas, while a change to Kami.Cocktail.OpenAPI.Schemas can't break Kami.Cocktail.External.
- Position
- Below the diagonal: Kami.Cocktail.OpenAPI.Schemas uses a module listed above it, which is the healthy direction.
29→5 Kami.Cocktail.Services.Auth uses BarAssistant.Application.User✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Services.Auth uses a type in BarAssistant.Application.User.
- The types involved
Kami.Cocktail.Services.Auth.RegisterUserService→BarAssistant.Application.User.UserService
- Direction
- Kami.Cocktail.Services.Auth uses BarAssistant.Application.User, so a change to BarAssistant.Application.User can break Kami.Cocktail.Services.Auth, while a change to Kami.Cocktail.Services.Auth can't break BarAssistant.Application.User.
- Position
- Below the diagonal: Kami.Cocktail.Services.Auth uses a module listed above it, which is the healthy direction.
29→28 Kami.Cocktail.Services.Auth uses Kami.Cocktail.OpenAPI.Schemas✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Services.Auth uses a type in Kami.Cocktail.OpenAPI.Schemas.
- The types involved
Kami.Cocktail.Services.Auth.RegisterUserService→Kami.Cocktail.OpenAPI.Schemas.RegisterRequest
- Direction
- Kami.Cocktail.Services.Auth uses Kami.Cocktail.OpenAPI.Schemas, so a change to Kami.Cocktail.OpenAPI.Schemas can break Kami.Cocktail.Services.Auth, while a change to Kami.Cocktail.Services.Auth can't break Kami.Cocktail.OpenAPI.Schemas.
- Position
- Below the diagonal: Kami.Cocktail.Services.Auth uses a module listed above it, which is the healthy direction.
29→31 Kami.Cocktail.Services.Auth uses Kami.Cocktail.Models part of a loop✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.Services.Auth uses a type in Kami.Cocktail.Models.
- The types involved
Kami.Cocktail.Services.Auth.RegisterUserService→Kami.Cocktail.Models.UserKami.Cocktail.Services.Auth.SSOService→Kami.Cocktail.Models.OauthCredential
- Direction
- Kami.Cocktail.Services.Auth uses Kami.Cocktail.Models, so a change to Kami.Cocktail.Models can break Kami.Cocktail.Services.Auth, while a change to Kami.Cocktail.Services.Auth can't break Kami.Cocktail.Models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→29 Kami.Cocktail.Models.ValueObjects uses Kami.Cocktail.Services.Auth✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Models.ValueObjects uses a type in Kami.Cocktail.Services.Auth.
- The types involved
Kami.Cocktail.Models.ValueObjects.SSOProvider→Kami.Cocktail.Services.Auth.OauthProvider
- Direction
- Kami.Cocktail.Models.ValueObjects uses Kami.Cocktail.Services.Auth, so a change to Kami.Cocktail.Services.Auth can break Kami.Cocktail.Models.ValueObjects, while a change to Kami.Cocktail.Models.ValueObjects can't break Kami.Cocktail.Services.Auth.
- Position
- Below the diagonal: Kami.Cocktail.Models.ValueObjects uses a module listed above it, which is the healthy direction.
30→31 Kami.Cocktail.Models.ValueObjects uses Kami.Cocktail.Models part of a loop✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.Models.ValueObjects uses a type in Kami.Cocktail.Models.
- The types involved
Kami.Cocktail.Models.ValueObjects.MenuItem→Kami.Cocktail.Models.MenuCocktailKami.Cocktail.Models.ValueObjects.MenuItem→Kami.Cocktail.Models.MenuIngredient
- Direction
- Kami.Cocktail.Models.ValueObjects uses Kami.Cocktail.Models, so a change to Kami.Cocktail.Models can break Kami.Cocktail.Models.ValueObjects, while a change to Kami.Cocktail.Models.ValueObjects can't break Kami.Cocktail.Models.
- 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.
31→28 Kami.Cocktail.Models uses Kami.Cocktail.OpenAPI.Schemas✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Models uses a type in Kami.Cocktail.OpenAPI.Schemas.
- The types involved
Kami.Cocktail.Models.Calculator→Kami.Cocktail.OpenAPI.Schemas.CalculatorSolveRequest
- Direction
- Kami.Cocktail.Models uses Kami.Cocktail.OpenAPI.Schemas, so a change to Kami.Cocktail.OpenAPI.Schemas can break Kami.Cocktail.Models, while a change to Kami.Cocktail.Models can't break Kami.Cocktail.OpenAPI.Schemas.
- Position
- Below the diagonal: Kami.Cocktail.Models uses a module listed above it, which is the healthy direction.
31→29 Kami.Cocktail.Models uses Kami.Cocktail.Services.Auth✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Models uses a type in Kami.Cocktail.Services.Auth.
- The types involved
Kami.Cocktail.Models.OauthCredential→Kami.Cocktail.Services.Auth.OauthProvider
- Direction
- Kami.Cocktail.Models uses Kami.Cocktail.Services.Auth, so a change to Kami.Cocktail.Services.Auth can break Kami.Cocktail.Models, while a change to Kami.Cocktail.Models can't break Kami.Cocktail.Services.Auth.
- Position
- Below the diagonal: Kami.Cocktail.Models uses a module listed above it, which is the healthy direction.
31→30 Kami.Cocktail.Models uses Kami.Cocktail.Models.ValueObjects✕
- Connections
- 7 pairs of types, where a type in Kami.Cocktail.Models uses a type in Kami.Cocktail.Models.ValueObjects.
- The types involved
Kami.Cocktail.Models.Calculator→Kami.Cocktail.Models.ValueObjects.CalculatorResultKami.Cocktail.Models.CocktailIngredient→Kami.Cocktail.Models.ValueObjects.AmountValueObjectKami.Cocktail.Models.CocktailIngredientSubstitute→Kami.Cocktail.Models.ValueObjects.AmountValueObjectKami.Cocktail.Models.Ingredient→Kami.Cocktail.Models.ValueObjects.MaterializedPathKami.Cocktail.Models.Ingredient→Kami.Cocktail.Models.ValueObjects.UnitValueObjectKami.Cocktail.Models.IngredientPrice→Kami.Cocktail.Models.ValueObjects.AmountValueObjectKami.Cocktail.Models.OauthCredential→Kami.Cocktail.Models.ValueObjects.SSOProvider
- Direction
- Kami.Cocktail.Models uses Kami.Cocktail.Models.ValueObjects, so a change to Kami.Cocktail.Models.ValueObjects can break Kami.Cocktail.Models, while a change to Kami.Cocktail.Models can't break Kami.Cocktail.Models.ValueObjects.
- Position
- Below the diagonal: Kami.Cocktail.Models uses a module listed above it, which is the healthy direction.
32→27 Kami.Cocktail.External.Model uses Kami.Cocktail.External✕
- Connections
- 19 pairs of types, where a type in Kami.Cocktail.External.Model uses a type in Kami.Cocktail.External.
- The types involved
Kami.Cocktail.External.Model.Calculator→Kami.Cocktail.External.SupportsDataPackKami.Cocktail.External.Model.Cocktail→Kami.Cocktail.External.SupportsDataPackKami.Cocktail.External.Model.Cocktail→Kami.Cocktail.External.SupportsJSONLDKami.Cocktail.External.Model.Cocktail→Kami.Cocktail.External.SupportsSchema4Kami.Cocktail.External.Model.CocktailIngredient→Kami.Cocktail.External.SupportsDataPackKami.Cocktail.External.Model.CocktailIngredient→Kami.Cocktail.External.SupportsSchema4Kami.Cocktail.External.Model.CocktailIngredientSubstitute→Kami.Cocktail.External.SupportsDataPackKami.Cocktail.External.Model.CocktailIngredientSubstitute→Kami.Cocktail.External.SupportsSchema4Kami.Cocktail.External.Model.Glass→Kami.Cocktail.External.SupportsDataPackKami.Cocktail.External.Model.Image→Kami.Cocktail.External.SupportsDataPackKami.Cocktail.External.Model.Image→Kami.Cocktail.External.SupportsSchema4Kami.Cocktail.External.Model.Ingredient→Kami.Cocktail.External.SupportsCSVKami.Cocktail.External.Model.Ingredient→Kami.Cocktail.External.SupportsDataPackKami.Cocktail.External.Model.Ingredient→Kami.Cocktail.External.SupportsSchema4Kami.Cocktail.External.Model.IngredientPrice→Kami.Cocktail.External.SupportsDataPackKami.Cocktail.External.Model.Schema→Kami.Cocktail.External.SupportsMarkdownKami.Cocktail.External.Model.Schema→Kami.Cocktail.External.SupportsSchema4Kami.Cocktail.External.Model.Schema→Kami.Cocktail.External.SupportsXMLKami.Cocktail.External.Model.Schema→Kami.Cocktail.External.SupportsYAML
- Direction
- Kami.Cocktail.External.Model uses Kami.Cocktail.External, so a change to Kami.Cocktail.External can break Kami.Cocktail.External.Model, while a change to Kami.Cocktail.External.Model can't break Kami.Cocktail.External.
- Position
- Below the diagonal: Kami.Cocktail.External.Model uses a module listed above it, which is the healthy direction.
32→30 Kami.Cocktail.External.Model uses Kami.Cocktail.Models.ValueObjects✕
- Connections
- 3 pairs of types, where a type in Kami.Cocktail.External.Model uses a type in Kami.Cocktail.Models.ValueObjects.
- The types involved
Kami.Cocktail.External.Model.CocktailIngredient→Kami.Cocktail.Models.ValueObjects.AmountValueObjectKami.Cocktail.External.Model.CocktailIngredientSubstitute→Kami.Cocktail.Models.ValueObjects.AmountValueObjectKami.Cocktail.External.Model.Ingredient→Kami.Cocktail.Models.ValueObjects.UnitValueObject
- Direction
- Kami.Cocktail.External.Model uses Kami.Cocktail.Models.ValueObjects, so a change to Kami.Cocktail.Models.ValueObjects can break Kami.Cocktail.External.Model, while a change to Kami.Cocktail.External.Model can't break Kami.Cocktail.Models.ValueObjects.
- Position
- Below the diagonal: Kami.Cocktail.External.Model uses a module listed above it, which is the healthy direction.
32→31 Kami.Cocktail.External.Model uses Kami.Cocktail.Models✕
- Connections
- 9 pairs of types, where a type in Kami.Cocktail.External.Model uses a type in Kami.Cocktail.Models.
- The types involved
Kami.Cocktail.External.Model.Calculator→Kami.Cocktail.Models.CalculatorKami.Cocktail.External.Model.Cocktail→Kami.Cocktail.Models.CocktailKami.Cocktail.External.Model.CocktailIngredient→Kami.Cocktail.Models.CocktailIngredientKami.Cocktail.External.Model.CocktailIngredientSubstitute→Kami.Cocktail.Models.CocktailIngredientSubstituteKami.Cocktail.External.Model.Glass→Kami.Cocktail.Models.GlassKami.Cocktail.External.Model.Image→Kami.Cocktail.Models.ImageKami.Cocktail.External.Model.Ingredient→Kami.Cocktail.Models.IngredientKami.Cocktail.External.Model.IngredientPrice→Kami.Cocktail.Models.IngredientPriceKami.Cocktail.External.Model.Schema→Kami.Cocktail.Models.Cocktail
- Direction
- Kami.Cocktail.External.Model uses Kami.Cocktail.Models, so a change to Kami.Cocktail.Models can break Kami.Cocktail.External.Model, while a change to Kami.Cocktail.External.Model can't break Kami.Cocktail.Models.
- Position
- Below the diagonal: Kami.Cocktail.External.Model uses a module listed above it, which is the healthy direction.
33→4 Kami.Cocktail.Infrastructure uses BarAssistant.Domain.User✕
- Connections
- 5 pairs of types, where a type in Kami.Cocktail.Infrastructure uses a type in BarAssistant.Domain.User.
- The types involved
Kami.Cocktail.Infrastructure.EloquentMemberRepository→BarAssistant.Domain.User.UserIdKami.Cocktail.Infrastructure.EloquentUserRepository→BarAssistant.Domain.User.UserKami.Cocktail.Infrastructure.EloquentUserRepository→BarAssistant.Domain.User.UserEmailKami.Cocktail.Infrastructure.EloquentUserRepository→BarAssistant.Domain.User.UserIdKami.Cocktail.Infrastructure.EloquentUserRepository→BarAssistant.Domain.User.UserRepository
- Direction
- Kami.Cocktail.Infrastructure uses BarAssistant.Domain.User, so a change to BarAssistant.Domain.User can break Kami.Cocktail.Infrastructure, while a change to Kami.Cocktail.Infrastructure can't break BarAssistant.Domain.User.
- Position
- Below the diagonal: Kami.Cocktail.Infrastructure uses a module listed above it, which is the healthy direction.
33→6 Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Common✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Infrastructure uses a type in BarAssistant.Domain.Common.
- The types involved
Kami.Cocktail.Infrastructure.EloquentMemberInventoryRepository→BarAssistant.Domain.Common.Name
- Direction
- Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Common, so a change to BarAssistant.Domain.Common can break Kami.Cocktail.Infrastructure, while a change to Kami.Cocktail.Infrastructure can't break BarAssistant.Domain.Common.
- Position
- Below the diagonal: Kami.Cocktail.Infrastructure uses a module listed above it, which is the healthy direction.
33→7 Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Calculator✕
- Connections
- 3 pairs of types, where a type in Kami.Cocktail.Infrastructure uses a type in BarAssistant.Domain.Calculator.
- The types involved
Kami.Cocktail.Infrastructure.EloquentCalculatorRepository→BarAssistant.Domain.Calculator.CalculatorKami.Cocktail.Infrastructure.EloquentCalculatorRepository→BarAssistant.Domain.Calculator.CalculatorIdKami.Cocktail.Infrastructure.EloquentCalculatorRepository→BarAssistant.Domain.Calculator.CalculatorRepository
- Direction
- Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Calculator, so a change to BarAssistant.Domain.Calculator can break Kami.Cocktail.Infrastructure, while a change to Kami.Cocktail.Infrastructure can't break BarAssistant.Domain.Calculator.
- Position
- Below the diagonal: Kami.Cocktail.Infrastructure uses a module listed above it, which is the healthy direction.
33→8 Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Image✕
- Connections
- 3 pairs of types, where a type in Kami.Cocktail.Infrastructure uses a type in BarAssistant.Domain.Image.
- The types involved
Kami.Cocktail.Infrastructure.EloquentImageRepository→BarAssistant.Domain.Image.ImageKami.Cocktail.Infrastructure.EloquentImageRepository→BarAssistant.Domain.Image.ImageIdKami.Cocktail.Infrastructure.EloquentImageRepository→BarAssistant.Domain.Image.ImageRepository
- Direction
- Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Image, so a change to BarAssistant.Domain.Image can break Kami.Cocktail.Infrastructure, while a change to Kami.Cocktail.Infrastructure can't break BarAssistant.Domain.Image.
- Position
- Below the diagonal: Kami.Cocktail.Infrastructure uses a module listed above it, which is the healthy direction.
33→9 Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Note✕
- Connections
- 3 pairs of types, where a type in Kami.Cocktail.Infrastructure uses a type in BarAssistant.Domain.Note.
- The types involved
Kami.Cocktail.Infrastructure.EloquentNoteRepository→BarAssistant.Domain.Note.NoteKami.Cocktail.Infrastructure.EloquentNoteRepository→BarAssistant.Domain.Note.NoteIdKami.Cocktail.Infrastructure.EloquentNoteRepository→BarAssistant.Domain.Note.NoteRepository
- Direction
- Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Note, so a change to BarAssistant.Domain.Note can break Kami.Cocktail.Infrastructure, while a change to Kami.Cocktail.Infrastructure can't break BarAssistant.Domain.Note.
- Position
- Below the diagonal: Kami.Cocktail.Infrastructure uses a module listed above it, which is the healthy direction.
33→12 Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Ingredient✕
- Connections
- 9 pairs of types, where a type in Kami.Cocktail.Infrastructure uses a type in BarAssistant.Domain.Ingredient.
- The types involved
Kami.Cocktail.Infrastructure.EloquentComplexIngredientResolver→BarAssistant.Domain.Ingredient.ComplexIngredientResolverKami.Cocktail.Infrastructure.EloquentIngredientHierarchyRepository→BarAssistant.Domain.Ingredient.IngredientIdKami.Cocktail.Infrastructure.EloquentIngredientMatchRepository→BarAssistant.Domain.Ingredient.IngredientMatchRepositoryKami.Cocktail.Infrastructure.EloquentIngredientRepository→BarAssistant.Domain.Ingredient.IngredientKami.Cocktail.Infrastructure.EloquentIngredientRepository→BarAssistant.Domain.Ingredient.IngredientIdKami.Cocktail.Infrastructure.EloquentIngredientRepository→BarAssistant.Domain.Ingredient.IngredientRepositoryKami.Cocktail.Infrastructure.EloquentPriceCategoryRepository→BarAssistant.Domain.Ingredient.PriceCategoryKami.Cocktail.Infrastructure.EloquentPriceCategoryRepository→BarAssistant.Domain.Ingredient.PriceCategoryIdKami.Cocktail.Infrastructure.EloquentPriceCategoryRepository→BarAssistant.Domain.Ingredient.PriceCategoryRepository
- Direction
- Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Ingredient, so a change to BarAssistant.Domain.Ingredient can break Kami.Cocktail.Infrastructure, while a change to Kami.Cocktail.Infrastructure can't break BarAssistant.Domain.Ingredient.
- Position
- Below the diagonal: Kami.Cocktail.Infrastructure uses a module listed above it, which is the healthy direction.
33→13 Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Cocktail✕
- Connections
- 17 pairs of types, where a type in Kami.Cocktail.Infrastructure uses a type in BarAssistant.Domain.Cocktail.
- The types involved
Kami.Cocktail.Infrastructure.EloquentCocktailCollectionRepository→BarAssistant.Domain.Cocktail.CocktailCollectionKami.Cocktail.Infrastructure.EloquentCocktailCollectionRepository→BarAssistant.Domain.Cocktail.CocktailCollectionRepositoryKami.Cocktail.Infrastructure.EloquentCocktailCollectionRepository→BarAssistant.Domain.Cocktail.CollectionIdKami.Cocktail.Infrastructure.EloquentCocktailMatchRepository→BarAssistant.Domain.Cocktail.CocktailMatchRepositoryKami.Cocktail.Infrastructure.EloquentCocktailMethodRepository→BarAssistant.Domain.Cocktail.CocktailMethodKami.Cocktail.Infrastructure.EloquentCocktailMethodRepository→BarAssistant.Domain.Cocktail.CocktailMethodRepositoryKami.Cocktail.Infrastructure.EloquentCocktailMethodRepository→BarAssistant.Domain.Cocktail.MethodIdKami.Cocktail.Infrastructure.EloquentCocktailRepository→BarAssistant.Domain.Cocktail.CocktailKami.Cocktail.Infrastructure.EloquentCocktailRepository→BarAssistant.Domain.Cocktail.CocktailIdKami.Cocktail.Infrastructure.EloquentCocktailRepository→BarAssistant.Domain.Cocktail.CocktailRepositoryKami.Cocktail.Infrastructure.EloquentGlassRepository→BarAssistant.Domain.Cocktail.GlassKami.Cocktail.Infrastructure.EloquentGlassRepository→BarAssistant.Domain.Cocktail.GlassIdKami.Cocktail.Infrastructure.EloquentGlassRepository→BarAssistant.Domain.Cocktail.GlassRepositoryKami.Cocktail.Infrastructure.EloquentShelfCocktailQueryRepository→BarAssistant.Domain.Cocktail.ShelfCocktailQueryRepositoryKami.Cocktail.Infrastructure.EloquentUtensilRepository→BarAssistant.Domain.Cocktail.UtensilKami.Cocktail.Infrastructure.EloquentUtensilRepository→BarAssistant.Domain.Cocktail.UtensilIdKami.Cocktail.Infrastructure.EloquentUtensilRepository→BarAssistant.Domain.Cocktail.UtensilRepository
- Direction
- Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Cocktail, so a change to BarAssistant.Domain.Cocktail can break Kami.Cocktail.Infrastructure, while a change to Kami.Cocktail.Infrastructure can't break BarAssistant.Domain.Cocktail.
- Position
- Below the diagonal: Kami.Cocktail.Infrastructure uses a module listed above it, which is the healthy direction.
33→15 Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Bar✕
- Connections
- 27 pairs of types, where a type in Kami.Cocktail.Infrastructure uses a type in BarAssistant.Domain.Bar. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Kami.Cocktail.Infrastructure.EloquentBarInventoryRepository→BarAssistant.Domain.Bar.BarIdKami.Cocktail.Infrastructure.EloquentBarInventoryRepository→BarAssistant.Domain.Bar.BarInventoryKami.Cocktail.Infrastructure.EloquentBarInventoryRepository→BarAssistant.Domain.Bar.BarInventoryRepositoryKami.Cocktail.Infrastructure.EloquentBarRepository→BarAssistant.Domain.Bar.BarKami.Cocktail.Infrastructure.EloquentBarRepository→BarAssistant.Domain.Bar.BarIdKami.Cocktail.Infrastructure.EloquentBarRepository→BarAssistant.Domain.Bar.BarRepositoryKami.Cocktail.Infrastructure.EloquentCocktailMatchRepository→BarAssistant.Domain.Bar.BarIdKami.Cocktail.Infrastructure.EloquentCocktailMethodRepository→BarAssistant.Domain.Bar.BarIdKami.Cocktail.Infrastructure.EloquentGlassRepository→BarAssistant.Domain.Bar.BarIdKami.Cocktail.Infrastructure.EloquentIngredientHierarchyRepository→BarAssistant.Domain.Bar.BarIdKami.Cocktail.Infrastructure.EloquentIngredientMatchRepository→BarAssistant.Domain.Bar.BarIdKami.Cocktail.Infrastructure.EloquentIngredientRepository→BarAssistant.Domain.Bar.BarIdKami.Cocktail.Infrastructure.EloquentIngredientReviewRepository→BarAssistant.Domain.Bar.MemberIdKami.Cocktail.Infrastructure.EloquentMemberInventoryRepository→BarAssistant.Domain.Bar.MemberIdKami.Cocktail.Infrastructure.EloquentMemberInventoryRepository→BarAssistant.Domain.Bar.MemberInventoryKami.Cocktail.Infrastructure.EloquentMemberInventoryRepository→BarAssistant.Domain.Bar.MemberInventoryIdKami.Cocktail.Infrastructure.EloquentMemberInventoryRepository→BarAssistant.Domain.Bar.MemberInventoryRepositoryKami.Cocktail.Infrastructure.EloquentMemberRepository→BarAssistant.Domain.Bar.BarIdKami.Cocktail.Infrastructure.EloquentMemberRepository→BarAssistant.Domain.Bar.MemberKami.Cocktail.Infrastructure.EloquentMemberRepository→BarAssistant.Domain.Bar.MemberIdKami.Cocktail.Infrastructure.EloquentMemberRepository→BarAssistant.Domain.Bar.MemberRepositoryKami.Cocktail.Infrastructure.EloquentMenuRepository→BarAssistant.Domain.Bar.BarIdKami.Cocktail.Infrastructure.EloquentPriceCategoryRepository→BarAssistant.Domain.Bar.BarIdKami.Cocktail.Infrastructure.EloquentRatingRepository→BarAssistant.Domain.Bar.MemberIdKami.Cocktail.Infrastructure.EloquentRecommendationRepository→BarAssistant.Domain.Bar.MemberId
- Direction
- Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Bar, so a change to BarAssistant.Domain.Bar can break Kami.Cocktail.Infrastructure, while a change to Kami.Cocktail.Infrastructure can't break BarAssistant.Domain.Bar.
- Position
- Below the diagonal: Kami.Cocktail.Infrastructure uses a module listed above it, which is the healthy direction.
33→18 Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Export✕
- Connections
- 3 pairs of types, where a type in Kami.Cocktail.Infrastructure uses a type in BarAssistant.Domain.Export.
- The types involved
Kami.Cocktail.Infrastructure.EloquentExportRepository→BarAssistant.Domain.Export.ExportKami.Cocktail.Infrastructure.EloquentExportRepository→BarAssistant.Domain.Export.ExportIdKami.Cocktail.Infrastructure.EloquentExportRepository→BarAssistant.Domain.Export.ExportRepository
- Direction
- Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Export, so a change to BarAssistant.Domain.Export can break Kami.Cocktail.Infrastructure, while a change to Kami.Cocktail.Infrastructure can't break BarAssistant.Domain.Export.
- Position
- Below the diagonal: Kami.Cocktail.Infrastructure uses a module listed above it, which is the healthy direction.
33→19 Kami.Cocktail.Infrastructure uses BarAssistant.Domain.IngredientHierarchy✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.Infrastructure uses a type in BarAssistant.Domain.IngredientHierarchy.
- The types involved
Kami.Cocktail.Infrastructure.EloquentIngredientHierarchyRepository→BarAssistant.Domain.IngredientHierarchy.IngredientHierarchyNodeKami.Cocktail.Infrastructure.EloquentIngredientHierarchyRepository→BarAssistant.Domain.IngredientHierarchy.IngredientHierarchyRepository
- Direction
- Kami.Cocktail.Infrastructure uses BarAssistant.Domain.IngredientHierarchy, so a change to BarAssistant.Domain.IngredientHierarchy can break Kami.Cocktail.Infrastructure, while a change to Kami.Cocktail.Infrastructure can't break BarAssistant.Domain.IngredientHierarchy.
- Position
- Below the diagonal: Kami.Cocktail.Infrastructure uses a module listed above it, which is the healthy direction.
33→20 Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Menu✕
- Connections
- 3 pairs of types, where a type in Kami.Cocktail.Infrastructure uses a type in BarAssistant.Domain.Menu.
- The types involved
Kami.Cocktail.Infrastructure.EloquentMenuRepository→BarAssistant.Domain.Menu.MenuKami.Cocktail.Infrastructure.EloquentMenuRepository→BarAssistant.Domain.Menu.MenuIdKami.Cocktail.Infrastructure.EloquentMenuRepository→BarAssistant.Domain.Menu.MenuRepository
- Direction
- Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Menu, so a change to BarAssistant.Domain.Menu can break Kami.Cocktail.Infrastructure, while a change to Kami.Cocktail.Infrastructure can't break BarAssistant.Domain.Menu.
- Position
- Below the diagonal: Kami.Cocktail.Infrastructure uses a module listed above it, which is the healthy direction.
33→21 Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Rating✕
- Connections
- 5 pairs of types, where a type in Kami.Cocktail.Infrastructure uses a type in BarAssistant.Domain.Rating.
- The types involved
Kami.Cocktail.Infrastructure.EloquentRatingRepository→BarAssistant.Domain.Rating.RateableIdKami.Cocktail.Infrastructure.EloquentRatingRepository→BarAssistant.Domain.Rating.RateableTypeKami.Cocktail.Infrastructure.EloquentRatingRepository→BarAssistant.Domain.Rating.RatingKami.Cocktail.Infrastructure.EloquentRatingRepository→BarAssistant.Domain.Rating.RatingIdKami.Cocktail.Infrastructure.EloquentRatingRepository→BarAssistant.Domain.Rating.RatingRepository
- Direction
- Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Rating, so a change to BarAssistant.Domain.Rating can break Kami.Cocktail.Infrastructure, while a change to Kami.Cocktail.Infrastructure can't break BarAssistant.Domain.Rating.
- Position
- Below the diagonal: Kami.Cocktail.Infrastructure uses a module listed above it, which is the healthy direction.
33→22 Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Recommendation✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.Infrastructure uses a type in BarAssistant.Domain.Recommendation.
- The types involved
Kami.Cocktail.Infrastructure.EloquentRecommendationRepository→BarAssistant.Domain.Recommendation.RecommendationRepositoryKami.Cocktail.Infrastructure.EloquentRecommendationRepository→BarAssistant.Domain.Recommendation.UserAbvPreference
- Direction
- Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Recommendation, so a change to BarAssistant.Domain.Recommendation can break Kami.Cocktail.Infrastructure, while a change to Kami.Cocktail.Infrastructure can't break BarAssistant.Domain.Recommendation.
- Position
- Below the diagonal: Kami.Cocktail.Infrastructure uses a module listed above it, which is the healthy direction.
33→23 Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Review✕
- Connections
- 6 pairs of types, where a type in Kami.Cocktail.Infrastructure uses a type in BarAssistant.Domain.Review.
- The types involved
Kami.Cocktail.Infrastructure.EloquentIngredientReviewRepository→BarAssistant.Domain.Review.IngredientReviewKami.Cocktail.Infrastructure.EloquentIngredientReviewRepository→BarAssistant.Domain.Review.IngredientReviewIdKami.Cocktail.Infrastructure.EloquentIngredientReviewRepository→BarAssistant.Domain.Review.IngredientReviewRepositoryKami.Cocktail.Infrastructure.EloquentReviewRepository→BarAssistant.Domain.Review.ReviewKami.Cocktail.Infrastructure.EloquentReviewRepository→BarAssistant.Domain.Review.ReviewIdKami.Cocktail.Infrastructure.EloquentReviewRepository→BarAssistant.Domain.Review.ReviewRepository
- Direction
- Kami.Cocktail.Infrastructure uses BarAssistant.Domain.Review, so a change to BarAssistant.Domain.Review can break Kami.Cocktail.Infrastructure, while a change to Kami.Cocktail.Infrastructure can't break BarAssistant.Domain.Review.
- Position
- Below the diagonal: Kami.Cocktail.Infrastructure uses a module listed above it, which is the healthy direction.
33→31 Kami.Cocktail.Infrastructure uses Kami.Cocktail.Models✕
- Connections
- 20 pairs of types, where a type in Kami.Cocktail.Infrastructure uses a type in Kami.Cocktail.Models.
- The types involved
Kami.Cocktail.Infrastructure.EloquentBarRepository→Kami.Cocktail.Models.BarKami.Cocktail.Infrastructure.EloquentCalculatorRepository→Kami.Cocktail.Models.CalculatorKami.Cocktail.Infrastructure.EloquentCocktailCollectionRepository→Kami.Cocktail.Models.CollectionKami.Cocktail.Infrastructure.EloquentCocktailMethodRepository→Kami.Cocktail.Models.CocktailMethodKami.Cocktail.Infrastructure.EloquentCocktailRepository→Kami.Cocktail.Models.CocktailKami.Cocktail.Infrastructure.EloquentExportRepository→Kami.Cocktail.Models.ExportKami.Cocktail.Infrastructure.EloquentGlassRepository→Kami.Cocktail.Models.GlassKami.Cocktail.Infrastructure.EloquentImageRepository→Kami.Cocktail.Models.ImageKami.Cocktail.Infrastructure.EloquentIngredientHierarchyRepository→Kami.Cocktail.Models.IngredientKami.Cocktail.Infrastructure.EloquentIngredientRepository→Kami.Cocktail.Models.IngredientKami.Cocktail.Infrastructure.EloquentIngredientReviewRepository→Kami.Cocktail.Models.IngredientReviewKami.Cocktail.Infrastructure.EloquentMemberInventoryRepository→Kami.Cocktail.Models.MemberInventoryKami.Cocktail.Infrastructure.EloquentMemberRepository→Kami.Cocktail.Models.BarMembershipKami.Cocktail.Infrastructure.EloquentMenuRepository→Kami.Cocktail.Models.MenuKami.Cocktail.Infrastructure.EloquentNoteRepository→Kami.Cocktail.Models.NoteKami.Cocktail.Infrastructure.EloquentPriceCategoryRepository→Kami.Cocktail.Models.PriceCategoryKami.Cocktail.Infrastructure.EloquentRatingRepository→Kami.Cocktail.Models.RatingKami.Cocktail.Infrastructure.EloquentReviewRepository→Kami.Cocktail.Models.CocktailReviewKami.Cocktail.Infrastructure.EloquentUserRepository→Kami.Cocktail.Models.UserKami.Cocktail.Infrastructure.EloquentUtensilRepository→Kami.Cocktail.Models.Utensil
- Direction
- Kami.Cocktail.Infrastructure uses Kami.Cocktail.Models, so a change to Kami.Cocktail.Models can break Kami.Cocktail.Infrastructure, while a change to Kami.Cocktail.Infrastructure can't break Kami.Cocktail.Models.
- Position
- Below the diagonal: Kami.Cocktail.Infrastructure uses a module listed above it, which is the healthy direction.
34→12 Kami.Cocktail.Services uses BarAssistant.Domain.Ingredient✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Services uses a type in BarAssistant.Domain.Ingredient.
- The types involved
Kami.Cocktail.Services.IngredientService→BarAssistant.Domain.Ingredient.ComplexIngredientResolver
- Direction
- Kami.Cocktail.Services uses BarAssistant.Domain.Ingredient, so a change to BarAssistant.Domain.Ingredient can break Kami.Cocktail.Services, while a change to Kami.Cocktail.Services can't break BarAssistant.Domain.Ingredient.
- Position
- Below the diagonal: Kami.Cocktail.Services uses a module listed above it, which is the healthy direction.
34→14 Kami.Cocktail.Services uses BarAssistant.Application.Cocktail✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Services uses a type in BarAssistant.Application.Cocktail.
- The types involved
Kami.Cocktail.Services.CocktailService→BarAssistant.Application.Cocktail.ShelfCocktailService
- Direction
- Kami.Cocktail.Services uses BarAssistant.Application.Cocktail, so a change to BarAssistant.Application.Cocktail can break Kami.Cocktail.Services, while a change to Kami.Cocktail.Services can't break BarAssistant.Application.Cocktail.
- Position
- Below the diagonal: Kami.Cocktail.Services uses a module listed above it, which is the healthy direction.
34→25 Kami.Cocktail.Services uses BarAssistant.Application.Ingredient✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Services uses a type in BarAssistant.Application.Ingredient.
- The types involved
Kami.Cocktail.Services.CocktailService→BarAssistant.Application.Ingredient.IngredientService
- Direction
- Kami.Cocktail.Services uses BarAssistant.Application.Ingredient, so a change to BarAssistant.Application.Ingredient can break Kami.Cocktail.Services, while a change to Kami.Cocktail.Services can't break BarAssistant.Application.Ingredient.
- Position
- Below the diagonal: Kami.Cocktail.Services uses a module listed above it, which is the healthy direction.
34→31 Kami.Cocktail.Services uses Kami.Cocktail.Models✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Services uses a type in Kami.Cocktail.Models.
- The types involved
Kami.Cocktail.Services.CocktailService→Kami.Cocktail.Models.Cocktail
- Direction
- Kami.Cocktail.Services uses Kami.Cocktail.Models, so a change to Kami.Cocktail.Models can break Kami.Cocktail.Services, while a change to Kami.Cocktail.Services can't break Kami.Cocktail.Models.
- Position
- Below the diagonal: Kami.Cocktail.Services uses a module listed above it, which is the healthy direction.
35→11 Kami.Cocktail.Services.Image uses BarAssistant.Application.Image✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.Services.Image uses a type in BarAssistant.Application.Image.
- The types involved
Kami.Cocktail.Services.Image.CocktailImageGenerationService→BarAssistant.Application.Image.ImageServiceKami.Cocktail.Services.Image.IngredientImageGenerationService→BarAssistant.Application.Image.ImageService
- Direction
- Kami.Cocktail.Services.Image uses BarAssistant.Application.Image, so a change to BarAssistant.Application.Image can break Kami.Cocktail.Services.Image, while a change to Kami.Cocktail.Services.Image can't break BarAssistant.Application.Image.
- Position
- Below the diagonal: Kami.Cocktail.Services.Image uses a module listed above it, which is the healthy direction.
35→31 Kami.Cocktail.Services.Image uses Kami.Cocktail.Models✕
- Connections
- 6 pairs of types, where a type in Kami.Cocktail.Services.Image uses a type in Kami.Cocktail.Models.
- The types involved
Kami.Cocktail.Services.Image.CocktailImageGenerationService→Kami.Cocktail.Models.CocktailKami.Cocktail.Services.Image.CocktailImageGenerationService→Kami.Cocktail.Models.ImageKami.Cocktail.Services.Image.ImageStorageService→Kami.Cocktail.Models.BarKami.Cocktail.Services.Image.ImageStorageService→Kami.Cocktail.Models.ImageKami.Cocktail.Services.Image.IngredientImageGenerationService→Kami.Cocktail.Models.ImageKami.Cocktail.Services.Image.IngredientImageGenerationService→Kami.Cocktail.Models.Ingredient
- Direction
- Kami.Cocktail.Services.Image uses Kami.Cocktail.Models, so a change to Kami.Cocktail.Models can break Kami.Cocktail.Services.Image, while a change to Kami.Cocktail.Services.Image can't break Kami.Cocktail.Models.
- Position
- Below the diagonal: Kami.Cocktail.Services.Image uses a module listed above it, which is the healthy direction.
36→27 Kami.Cocktail.External.Export uses Kami.Cocktail.External✕
- Connections
- 3 pairs of types, where a type in Kami.Cocktail.External.Export uses a type in Kami.Cocktail.External.
- The types involved
Kami.Cocktail.External.Export.ToDataPack→Kami.Cocktail.External.ForceUnitConvertEnumKami.Cocktail.External.Export.ToRecipeType→Kami.Cocktail.External.ExportTypeEnumKami.Cocktail.External.Export.ToRecipeType→Kami.Cocktail.External.ForceUnitConvertEnum
- Direction
- Kami.Cocktail.External.Export uses Kami.Cocktail.External, so a change to Kami.Cocktail.External can break Kami.Cocktail.External.Export, while a change to Kami.Cocktail.External.Export can't break Kami.Cocktail.External.
- Position
- Below the diagonal: Kami.Cocktail.External.Export uses a module listed above it, which is the healthy direction.
36→31 Kami.Cocktail.External.Export uses Kami.Cocktail.Models✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.External.Export uses a type in Kami.Cocktail.Models.
- The types involved
Kami.Cocktail.External.Export.ToDataPack→Kami.Cocktail.Models.Image
- Direction
- Kami.Cocktail.External.Export uses Kami.Cocktail.Models, so a change to Kami.Cocktail.Models can break Kami.Cocktail.External.Export, while a change to Kami.Cocktail.External.Export can't break Kami.Cocktail.Models.
- Position
- Below the diagonal: Kami.Cocktail.External.Export uses a module listed above it, which is the healthy direction.
36→35 Kami.Cocktail.External.Export uses Kami.Cocktail.Services.Image✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.External.Export uses a type in Kami.Cocktail.Services.Image.
- The types involved
Kami.Cocktail.External.Export.ToDataPack→Kami.Cocktail.Services.Image.ImageStorageServiceKami.Cocktail.External.Export.ToRecipeType→Kami.Cocktail.Services.Image.ImageStorageService
- Direction
- Kami.Cocktail.External.Export uses Kami.Cocktail.Services.Image, so a change to Kami.Cocktail.Services.Image can break Kami.Cocktail.External.Export, while a change to Kami.Cocktail.External.Export can't break Kami.Cocktail.Services.Image.
- Position
- Below the diagonal: Kami.Cocktail.External.Export uses a module listed above it, which is the healthy direction.
37→11 Kami.Cocktail.External.Import uses BarAssistant.Application.Image✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.External.Import uses a type in BarAssistant.Application.Image.
- The types involved
Kami.Cocktail.External.Import.FromSchema→BarAssistant.Application.Image.ImageService
- Direction
- Kami.Cocktail.External.Import uses BarAssistant.Application.Image, so a change to BarAssistant.Application.Image can break Kami.Cocktail.External.Import, while a change to Kami.Cocktail.External.Import can't break BarAssistant.Application.Image.
- Position
- Below the diagonal: Kami.Cocktail.External.Import uses a module listed above it, which is the healthy direction.
37→14 Kami.Cocktail.External.Import uses BarAssistant.Application.Cocktail✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.External.Import uses a type in BarAssistant.Application.Cocktail.
- The types involved
Kami.Cocktail.External.Import.FromSchema→BarAssistant.Application.Cocktail.CocktailService
- Direction
- Kami.Cocktail.External.Import uses BarAssistant.Application.Cocktail, so a change to BarAssistant.Application.Cocktail can break Kami.Cocktail.External.Import, while a change to Kami.Cocktail.External.Import can't break BarAssistant.Application.Cocktail.
- Position
- Below the diagonal: Kami.Cocktail.External.Import uses a module listed above it, which is the healthy direction.
37→17 Kami.Cocktail.External.Import uses BarAssistant.Application.Matcher✕
- Connections
- 4 pairs of types, where a type in Kami.Cocktail.External.Import uses a type in BarAssistant.Application.Matcher.
- The types involved
Kami.Cocktail.External.Import.FromSchema→BarAssistant.Application.Matcher.CocktailMatcherKami.Cocktail.External.Import.FromSchema→BarAssistant.Application.Matcher.GlassMatcherKami.Cocktail.External.Import.FromSchema→BarAssistant.Application.Matcher.IngredientMatcherKami.Cocktail.External.Import.FromSchema→BarAssistant.Application.Matcher.MethodMatcher
- Direction
- Kami.Cocktail.External.Import uses BarAssistant.Application.Matcher, so a change to BarAssistant.Application.Matcher can break Kami.Cocktail.External.Import, while a change to Kami.Cocktail.External.Import can't break BarAssistant.Application.Matcher.
- Position
- Below the diagonal: Kami.Cocktail.External.Import uses a module listed above it, which is the healthy direction.
37→27 Kami.Cocktail.External.Import uses Kami.Cocktail.External✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.External.Import uses a type in Kami.Cocktail.External.
- The types involved
Kami.Cocktail.External.Import.FromDataPack→Kami.Cocktail.External.BarOptionsEnum
- Direction
- Kami.Cocktail.External.Import uses Kami.Cocktail.External, so a change to Kami.Cocktail.External can break Kami.Cocktail.External.Import, while a change to Kami.Cocktail.External.Import can't break Kami.Cocktail.External.
- Position
- Below the diagonal: Kami.Cocktail.External.Import uses a module listed above it, which is the healthy direction.
37→31 Kami.Cocktail.External.Import uses Kami.Cocktail.Models✕
- Connections
- 3 pairs of types, where a type in Kami.Cocktail.External.Import uses a type in Kami.Cocktail.Models.
- The types involved
Kami.Cocktail.External.Import.FromDataPack→Kami.Cocktail.Models.BarKami.Cocktail.External.Import.FromDataPack→Kami.Cocktail.Models.UserKami.Cocktail.External.Import.FromSchema→Kami.Cocktail.Models.Cocktail
- Direction
- Kami.Cocktail.External.Import uses Kami.Cocktail.Models, so a change to Kami.Cocktail.Models can break Kami.Cocktail.External.Import, while a change to Kami.Cocktail.External.Import can't break Kami.Cocktail.Models.
- Position
- Below the diagonal: Kami.Cocktail.External.Import uses a module listed above it, which is the healthy direction.
37→32 Kami.Cocktail.External.Import uses Kami.Cocktail.External.Model✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.External.Import uses a type in Kami.Cocktail.External.Model.
- The types involved
Kami.Cocktail.External.Import.FromSchema→Kami.Cocktail.External.Model.Schema
- Direction
- Kami.Cocktail.External.Import uses Kami.Cocktail.External.Model, so a change to Kami.Cocktail.External.Model can break Kami.Cocktail.External.Import, while a change to Kami.Cocktail.External.Import can't break Kami.Cocktail.External.Model.
- Position
- Below the diagonal: Kami.Cocktail.External.Import uses a module listed above it, which is the healthy direction.
37→34 Kami.Cocktail.External.Import uses Kami.Cocktail.Services✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.External.Import uses a type in Kami.Cocktail.Services.
- The types involved
Kami.Cocktail.External.Import.FromDataPack→Kami.Cocktail.Services.IngredientService
- Direction
- Kami.Cocktail.External.Import uses Kami.Cocktail.Services, so a change to Kami.Cocktail.Services can break Kami.Cocktail.External.Import, while a change to Kami.Cocktail.External.Import can't break Kami.Cocktail.Services.
- Position
- Below the diagonal: Kami.Cocktail.External.Import uses a module listed above it, which is the healthy direction.
37→35 Kami.Cocktail.External.Import uses Kami.Cocktail.Services.Image✕
- Connections
- 3 pairs of types, where a type in Kami.Cocktail.External.Import uses a type in Kami.Cocktail.Services.Image.
- The types involved
Kami.Cocktail.External.Import.FromDataPack→Kami.Cocktail.Services.Image.StarterMediaCatalogServiceKami.Cocktail.External.Import.FromSchema→Kami.Cocktail.Services.Image.ImageUploadServiceKami.Cocktail.External.Import.FromSchema→Kami.Cocktail.Services.Image.ImageValidatorService
- Direction
- Kami.Cocktail.External.Import uses Kami.Cocktail.Services.Image, so a change to Kami.Cocktail.Services.Image can break Kami.Cocktail.External.Import, while a change to Kami.Cocktail.External.Import can't break Kami.Cocktail.Services.Image.
- Position
- Below the diagonal: Kami.Cocktail.External.Import uses a module listed above it, which is the healthy direction.
38→16 Kami.Cocktail.Console.Commands uses BarAssistant.Application.Bar✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.Console.Commands uses a type in BarAssistant.Application.Bar.
- The types involved
Kami.Cocktail.Console.Commands.BarImportRecipes→BarAssistant.Application.Bar.BarServiceKami.Cocktail.Console.Commands.BarImportRecipes→BarAssistant.Application.Bar.MemberService
- Direction
- Kami.Cocktail.Console.Commands uses BarAssistant.Application.Bar, so a change to BarAssistant.Application.Bar can break Kami.Cocktail.Console.Commands, while a change to Kami.Cocktail.Console.Commands can't break BarAssistant.Application.Bar.
- Position
- Below the diagonal: Kami.Cocktail.Console.Commands uses a module listed above it, which is the healthy direction.
38→35 Kami.Cocktail.Console.Commands uses Kami.Cocktail.Services.Image✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.Console.Commands uses a type in Kami.Cocktail.Services.Image.
- The types involved
Kami.Cocktail.Console.Commands.BarMaintenance→Kami.Cocktail.Services.Image.ImageCleanupServiceKami.Cocktail.Console.Commands.PublishStarterMediaCatalog→Kami.Cocktail.Services.Image.StarterMediaCatalogService
- Direction
- Kami.Cocktail.Console.Commands uses Kami.Cocktail.Services.Image, so a change to Kami.Cocktail.Services.Image can break Kami.Cocktail.Console.Commands, while a change to Kami.Cocktail.Console.Commands can't break Kami.Cocktail.Services.Image.
- Position
- Below the diagonal: Kami.Cocktail.Console.Commands uses a module listed above it, which is the healthy direction.
38→36 Kami.Cocktail.Console.Commands uses Kami.Cocktail.External.Export✕
- Connections
- 3 pairs of types, where a type in Kami.Cocktail.Console.Commands uses a type in Kami.Cocktail.External.Export.
- The types involved
Kami.Cocktail.Console.Commands.BarExportRecipes→Kami.Cocktail.External.Export.ToDataPackKami.Cocktail.Console.Commands.BarExportRecipes→Kami.Cocktail.External.Export.ToRecipeTypeKami.Cocktail.Console.Commands.BarFullBackup→Kami.Cocktail.External.Export.ToFullBackup
- Direction
- Kami.Cocktail.Console.Commands uses Kami.Cocktail.External.Export, so a change to Kami.Cocktail.External.Export can break Kami.Cocktail.Console.Commands, while a change to Kami.Cocktail.Console.Commands can't break Kami.Cocktail.External.Export.
- Position
- Below the diagonal: Kami.Cocktail.Console.Commands uses a module listed above it, which is the healthy direction.
38→37 Kami.Cocktail.Console.Commands uses Kami.Cocktail.External.Import✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Console.Commands uses a type in Kami.Cocktail.External.Import.
- The types involved
Kami.Cocktail.Console.Commands.BarImportRecipes→Kami.Cocktail.External.Import.FromDataPack
- Direction
- Kami.Cocktail.Console.Commands uses Kami.Cocktail.External.Import, so a change to Kami.Cocktail.External.Import can break Kami.Cocktail.Console.Commands, while a change to Kami.Cocktail.Console.Commands can't break Kami.Cocktail.External.Import.
- Position
- Below the diagonal: Kami.Cocktail.Console.Commands uses a module listed above it, which is the healthy direction.
39→3 Kami.Cocktail.Http.Controllers uses Kami.Cocktail.Http.Resources✕
- Connections
- 11 pairs of types, where a type in Kami.Cocktail.Http.Controllers uses a type in Kami.Cocktail.Http.Resources.
- The types involved
Kami.Cocktail.Http.Controllers.CalculatorController→Kami.Cocktail.Http.Resources.CalculatorResultResourceKami.Cocktail.Http.Controllers.GenerateController→Kami.Cocktail.Http.Resources.ImageResourceKami.Cocktail.Http.Controllers.GenerateController→Kami.Cocktail.Http.Resources.ShelfPhotoResultResourceKami.Cocktail.Http.Controllers.IngredientController→Kami.Cocktail.Http.Resources.IngredientTreeResourceKami.Cocktail.Http.Controllers.PATController→Kami.Cocktail.Http.Resources.TokenResourceKami.Cocktail.Http.Controllers.SSOAuthController→Kami.Cocktail.Http.Resources.TokenResourceKami.Cocktail.Http.Controllers.StatsController→Kami.Cocktail.Http.Resources.BarIngredientDistributionResourceKami.Cocktail.Http.Controllers.StatsController→Kami.Cocktail.Http.Resources.BarTopStatsResourceKami.Cocktail.Http.Controllers.StatsController→Kami.Cocktail.Http.Resources.BarTotalStatsResourceKami.Cocktail.Http.Controllers.StatsController→Kami.Cocktail.Http.Resources.UserTasteProfileResourceKami.Cocktail.Http.Controllers.SubscriptionController→Kami.Cocktail.Http.Resources.UserSubscriptionResource
- Direction
- Kami.Cocktail.Http.Controllers uses Kami.Cocktail.Http.Resources, so a change to Kami.Cocktail.Http.Resources can break Kami.Cocktail.Http.Controllers, while a change to Kami.Cocktail.Http.Controllers can't break Kami.Cocktail.Http.Resources.
- Position
- Below the diagonal: Kami.Cocktail.Http.Controllers uses a module listed above it, which is the healthy direction.
39→5 Kami.Cocktail.Http.Controllers uses BarAssistant.Application.User✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Http.Controllers uses a type in BarAssistant.Application.User.
- The types involved
Kami.Cocktail.Http.Controllers.ProfileController→BarAssistant.Application.User.UserService
- Direction
- Kami.Cocktail.Http.Controllers uses BarAssistant.Application.User, so a change to BarAssistant.Application.User can break Kami.Cocktail.Http.Controllers, while a change to Kami.Cocktail.Http.Controllers can't break BarAssistant.Application.User.
- Position
- Below the diagonal: Kami.Cocktail.Http.Controllers uses a module listed above it, which is the healthy direction.
39→10 Kami.Cocktail.Http.Controllers uses BarAssistant.Application.Calculator✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Http.Controllers uses a type in BarAssistant.Application.Calculator.
- The types involved
Kami.Cocktail.Http.Controllers.CalculatorController→BarAssistant.Application.Calculator.CalculatorService
- Direction
- Kami.Cocktail.Http.Controllers uses BarAssistant.Application.Calculator, so a change to BarAssistant.Application.Calculator can break Kami.Cocktail.Http.Controllers, while a change to Kami.Cocktail.Http.Controllers can't break BarAssistant.Application.Calculator.
- Position
- Below the diagonal: Kami.Cocktail.Http.Controllers uses a module listed above it, which is the healthy direction.
39→11 Kami.Cocktail.Http.Controllers uses BarAssistant.Application.Image✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.Http.Controllers uses a type in BarAssistant.Application.Image.
- The types involved
Kami.Cocktail.Http.Controllers.CocktailController→BarAssistant.Application.Image.ImageServiceKami.Cocktail.Http.Controllers.ImageController→BarAssistant.Application.Image.ImageService
- Direction
- Kami.Cocktail.Http.Controllers uses BarAssistant.Application.Image, so a change to BarAssistant.Application.Image can break Kami.Cocktail.Http.Controllers, while a change to Kami.Cocktail.Http.Controllers can't break BarAssistant.Application.Image.
- Position
- Below the diagonal: Kami.Cocktail.Http.Controllers uses a module listed above it, which is the healthy direction.
39→14 Kami.Cocktail.Http.Controllers uses BarAssistant.Application.Cocktail✕
- Connections
- 5 pairs of types, where a type in Kami.Cocktail.Http.Controllers uses a type in BarAssistant.Application.Cocktail.
- The types involved
Kami.Cocktail.Http.Controllers.CocktailController→BarAssistant.Application.Cocktail.CocktailServiceKami.Cocktail.Http.Controllers.CocktailMethodController→BarAssistant.Application.Cocktail.CocktailMethodServiceKami.Cocktail.Http.Controllers.CollectionController→BarAssistant.Application.Cocktail.CollectionServiceKami.Cocktail.Http.Controllers.GlassController→BarAssistant.Application.Cocktail.GlassServiceKami.Cocktail.Http.Controllers.UtensilsController→BarAssistant.Application.Cocktail.UtensilService
- Direction
- Kami.Cocktail.Http.Controllers uses BarAssistant.Application.Cocktail, so a change to BarAssistant.Application.Cocktail can break Kami.Cocktail.Http.Controllers, while a change to Kami.Cocktail.Http.Controllers can't break BarAssistant.Application.Cocktail.
- Position
- Below the diagonal: Kami.Cocktail.Http.Controllers uses a module listed above it, which is the healthy direction.
39→16 Kami.Cocktail.Http.Controllers uses BarAssistant.Application.Bar✕
- Connections
- 8 pairs of types, where a type in Kami.Cocktail.Http.Controllers uses a type in BarAssistant.Application.Bar.
- The types involved
Kami.Cocktail.Http.Controllers.BarController→BarAssistant.Application.Bar.BarServiceKami.Cocktail.Http.Controllers.BarController→BarAssistant.Application.Bar.MemberServiceKami.Cocktail.Http.Controllers.BarInventoryController→BarAssistant.Application.Bar.InventoryServiceKami.Cocktail.Http.Controllers.CocktailController→BarAssistant.Application.Bar.FavoriteServiceKami.Cocktail.Http.Controllers.GenerateController→BarAssistant.Application.Bar.InventoryServiceKami.Cocktail.Http.Controllers.MemberController→BarAssistant.Application.Bar.MemberServiceKami.Cocktail.Http.Controllers.MemberInventoryController→BarAssistant.Application.Bar.MemberInventoryServiceKami.Cocktail.Http.Controllers.ShoppingListController→BarAssistant.Application.Bar.ShoppingListService
- Direction
- Kami.Cocktail.Http.Controllers uses BarAssistant.Application.Bar, so a change to BarAssistant.Application.Bar can break Kami.Cocktail.Http.Controllers, while a change to Kami.Cocktail.Http.Controllers can't break BarAssistant.Application.Bar.
- Position
- Below the diagonal: Kami.Cocktail.Http.Controllers uses a module listed above it, which is the healthy direction.
39→17 Kami.Cocktail.Http.Controllers uses BarAssistant.Application.Matcher✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Http.Controllers uses a type in BarAssistant.Application.Matcher.
- The types involved
Kami.Cocktail.Http.Controllers.GenerateController→BarAssistant.Application.Matcher.IngredientMatcher
- Direction
- Kami.Cocktail.Http.Controllers uses BarAssistant.Application.Matcher, so a change to BarAssistant.Application.Matcher can break Kami.Cocktail.Http.Controllers, while a change to Kami.Cocktail.Http.Controllers can't break BarAssistant.Application.Matcher.
- Position
- Below the diagonal: Kami.Cocktail.Http.Controllers uses a module listed above it, which is the healthy direction.
39→23 Kami.Cocktail.Http.Controllers uses BarAssistant.Domain.Review✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.Http.Controllers uses a type in BarAssistant.Domain.Review.
- The types involved
Kami.Cocktail.Http.Controllers.IngredientReviewController→BarAssistant.Domain.Review.IngredientReviewRepositoryKami.Cocktail.Http.Controllers.ReviewController→BarAssistant.Domain.Review.ReviewRepository
- Direction
- Kami.Cocktail.Http.Controllers uses BarAssistant.Domain.Review, so a change to BarAssistant.Domain.Review can break Kami.Cocktail.Http.Controllers, while a change to Kami.Cocktail.Http.Controllers can't break BarAssistant.Domain.Review.
- Position
- Below the diagonal: Kami.Cocktail.Http.Controllers uses a module listed above it, which is the healthy direction.
39→24 Kami.Cocktail.Http.Controllers uses BarAssistant.Application.Export✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Http.Controllers uses a type in BarAssistant.Application.Export.
- The types involved
Kami.Cocktail.Http.Controllers.ExportController→BarAssistant.Application.Export.ExportService
- Direction
- Kami.Cocktail.Http.Controllers uses BarAssistant.Application.Export, so a change to BarAssistant.Application.Export can break Kami.Cocktail.Http.Controllers, while a change to Kami.Cocktail.Http.Controllers can't break BarAssistant.Application.Export.
- Position
- Below the diagonal: Kami.Cocktail.Http.Controllers uses a module listed above it, which is the healthy direction.
39→25 Kami.Cocktail.Http.Controllers uses BarAssistant.Application.Ingredient✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.Http.Controllers uses a type in BarAssistant.Application.Ingredient.
- The types involved
Kami.Cocktail.Http.Controllers.IngredientController→BarAssistant.Application.Ingredient.IngredientServiceKami.Cocktail.Http.Controllers.PriceCategoryController→BarAssistant.Application.Ingredient.PriceCategoryService
- Direction
- Kami.Cocktail.Http.Controllers uses BarAssistant.Application.Ingredient, so a change to BarAssistant.Application.Ingredient can break Kami.Cocktail.Http.Controllers, while a change to Kami.Cocktail.Http.Controllers can't break BarAssistant.Application.Ingredient.
- Position
- Below the diagonal: Kami.Cocktail.Http.Controllers uses a module listed above it, which is the healthy direction.
39→26 Kami.Cocktail.Http.Controllers uses BarAssistant.Application.Recommendation✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.Http.Controllers uses a type in BarAssistant.Application.Recommendation.
- The types involved
Kami.Cocktail.Http.Controllers.RecommenderController→BarAssistant.Application.Recommendation.RecommendationServiceKami.Cocktail.Http.Controllers.StatsController→BarAssistant.Application.Recommendation.RecommendationService
- Direction
- Kami.Cocktail.Http.Controllers uses BarAssistant.Application.Recommendation, so a change to BarAssistant.Application.Recommendation can break Kami.Cocktail.Http.Controllers, while a change to Kami.Cocktail.Http.Controllers can't break BarAssistant.Application.Recommendation.
- Position
- Below the diagonal: Kami.Cocktail.Http.Controllers uses a module listed above it, which is the healthy direction.
39→29 Kami.Cocktail.Http.Controllers uses Kami.Cocktail.Services.Auth✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.Http.Controllers uses a type in Kami.Cocktail.Services.Auth.
- The types involved
Kami.Cocktail.Http.Controllers.AuthController→Kami.Cocktail.Services.Auth.RegisterUserServiceKami.Cocktail.Http.Controllers.SSOAuthController→Kami.Cocktail.Services.Auth.SSOService
- Direction
- Kami.Cocktail.Http.Controllers uses Kami.Cocktail.Services.Auth, so a change to Kami.Cocktail.Services.Auth can break Kami.Cocktail.Http.Controllers, while a change to Kami.Cocktail.Http.Controllers can't break Kami.Cocktail.Services.Auth.
- Position
- Below the diagonal: Kami.Cocktail.Http.Controllers uses a module listed above it, which is the healthy direction.
39→31 Kami.Cocktail.Http.Controllers uses Kami.Cocktail.Models✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.Http.Controllers uses a type in Kami.Cocktail.Models.
- The types involved
Kami.Cocktail.Http.Controllers.MemberInventoryController→Kami.Cocktail.Models.BarMembershipKami.Cocktail.Http.Controllers.MemberInventoryController→Kami.Cocktail.Models.MemberInventory
- Direction
- Kami.Cocktail.Http.Controllers uses Kami.Cocktail.Models, so a change to Kami.Cocktail.Models can break Kami.Cocktail.Http.Controllers, while a change to Kami.Cocktail.Http.Controllers can't break Kami.Cocktail.Models.
- Position
- Below the diagonal: Kami.Cocktail.Http.Controllers uses a module listed above it, which is the healthy direction.
39→34 Kami.Cocktail.Http.Controllers uses Kami.Cocktail.Services✕
- Connections
- 8 pairs of types, where a type in Kami.Cocktail.Http.Controllers uses a type in Kami.Cocktail.Services.
- The types involved
Kami.Cocktail.Http.Controllers.BarInventoryController→Kami.Cocktail.Services.CocktailServiceKami.Cocktail.Http.Controllers.BarInventoryController→Kami.Cocktail.Services.IngredientServiceKami.Cocktail.Http.Controllers.CocktailController→Kami.Cocktail.Services.CocktailServiceKami.Cocktail.Http.Controllers.IngredientController→Kami.Cocktail.Services.IngredientServiceKami.Cocktail.Http.Controllers.MemberInventoryController→Kami.Cocktail.Services.CocktailServiceKami.Cocktail.Http.Controllers.MemberInventoryController→Kami.Cocktail.Services.IngredientServiceKami.Cocktail.Http.Controllers.ServerController→Kami.Cocktail.Services.VersionCheckServiceKami.Cocktail.Http.Controllers.StatsController→Kami.Cocktail.Services.CocktailService
- Direction
- Kami.Cocktail.Http.Controllers uses Kami.Cocktail.Services, so a change to Kami.Cocktail.Services can break Kami.Cocktail.Http.Controllers, while a change to Kami.Cocktail.Http.Controllers can't break Kami.Cocktail.Services.
- Position
- Below the diagonal: Kami.Cocktail.Http.Controllers uses a module listed above it, which is the healthy direction.
39→35 Kami.Cocktail.Http.Controllers uses Kami.Cocktail.Services.Image✕
- Connections
- 7 pairs of types, where a type in Kami.Cocktail.Http.Controllers uses a type in Kami.Cocktail.Services.Image.
- The types involved
Kami.Cocktail.Http.Controllers.CocktailController→Kami.Cocktail.Services.Image.ImageStorageServiceKami.Cocktail.Http.Controllers.CocktailController→Kami.Cocktail.Services.Image.ImageUploadServiceKami.Cocktail.Http.Controllers.GenerateController→Kami.Cocktail.Services.Image.CocktailImageGenerationServiceKami.Cocktail.Http.Controllers.GenerateController→Kami.Cocktail.Services.Image.IngredientImageGenerationServiceKami.Cocktail.Http.Controllers.ImageController→Kami.Cocktail.Services.Image.ImageResolverKami.Cocktail.Http.Controllers.ImageController→Kami.Cocktail.Services.Image.ImageStorageServiceKami.Cocktail.Http.Controllers.ImageController→Kami.Cocktail.Services.Image.ImageUploadService
- Direction
- Kami.Cocktail.Http.Controllers uses Kami.Cocktail.Services.Image, so a change to Kami.Cocktail.Services.Image can break Kami.Cocktail.Http.Controllers, while a change to Kami.Cocktail.Http.Controllers can't break Kami.Cocktail.Services.Image.
- Position
- Below the diagonal: Kami.Cocktail.Http.Controllers uses a module listed above it, which is the healthy direction.
39→37 Kami.Cocktail.Http.Controllers uses Kami.Cocktail.External.Import✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Http.Controllers uses a type in Kami.Cocktail.External.Import.
- The types involved
Kami.Cocktail.Http.Controllers.ImportController→Kami.Cocktail.External.Import.FromSchema
- Direction
- Kami.Cocktail.Http.Controllers uses Kami.Cocktail.External.Import, so a change to Kami.Cocktail.External.Import can break Kami.Cocktail.Http.Controllers, while a change to Kami.Cocktail.Http.Controllers can't break Kami.Cocktail.External.Import.
- Position
- Below the diagonal: Kami.Cocktail.Http.Controllers uses a module listed above it, which is the healthy direction.
40→24 Kami.Cocktail.Jobs uses BarAssistant.Application.Export✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Jobs uses a type in BarAssistant.Application.Export.
- The types involved
Kami.Cocktail.Jobs.StartTypedExport→BarAssistant.Application.Export.ExportService
- Direction
- Kami.Cocktail.Jobs uses BarAssistant.Application.Export, so a change to BarAssistant.Application.Export can break Kami.Cocktail.Jobs, while a change to Kami.Cocktail.Jobs can't break BarAssistant.Application.Export.
- Position
- Below the diagonal: Kami.Cocktail.Jobs uses a module listed above it, which is the healthy direction.
40→27 Kami.Cocktail.Jobs uses Kami.Cocktail.External✕
- Connections
- 3 pairs of types, where a type in Kami.Cocktail.Jobs uses a type in Kami.Cocktail.External.
- The types involved
Kami.Cocktail.Jobs.SetupBar→Kami.Cocktail.External.BarOptionsEnumKami.Cocktail.Jobs.StartTypedExport→Kami.Cocktail.External.ExportTypeEnumKami.Cocktail.Jobs.StartTypedExport→Kami.Cocktail.External.ForceUnitConvertEnum
- Direction
- Kami.Cocktail.Jobs uses Kami.Cocktail.External, so a change to Kami.Cocktail.External can break Kami.Cocktail.Jobs, while a change to Kami.Cocktail.Jobs can't break Kami.Cocktail.External.
- Position
- Below the diagonal: Kami.Cocktail.Jobs uses a module listed above it, which is the healthy direction.
40→31 Kami.Cocktail.Jobs uses Kami.Cocktail.Models✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.Jobs uses a type in Kami.Cocktail.Models.
- The types involved
Kami.Cocktail.Jobs.SyncBarRecipes→Kami.Cocktail.Models.BarKami.Cocktail.Jobs.SyncBarRecipes→Kami.Cocktail.Models.User
- Direction
- Kami.Cocktail.Jobs uses Kami.Cocktail.Models, so a change to Kami.Cocktail.Models can break Kami.Cocktail.Jobs, while a change to Kami.Cocktail.Jobs can't break Kami.Cocktail.Models.
- Position
- Below the diagonal: Kami.Cocktail.Jobs uses a module listed above it, which is the healthy direction.
40→34 Kami.Cocktail.Jobs uses Kami.Cocktail.Services✕
- Connections
- 1 pair of types, where a type in Kami.Cocktail.Jobs uses a type in Kami.Cocktail.Services.
- The types involved
Kami.Cocktail.Jobs.StartBarOptimization→Kami.Cocktail.Services.BarOptimizerService
- Direction
- Kami.Cocktail.Jobs uses Kami.Cocktail.Services, so a change to Kami.Cocktail.Services can break Kami.Cocktail.Jobs, while a change to Kami.Cocktail.Jobs can't break Kami.Cocktail.Services.
- Position
- Below the diagonal: Kami.Cocktail.Jobs uses a module listed above it, which is the healthy direction.
40→37 Kami.Cocktail.Jobs uses Kami.Cocktail.External.Import✕
- Connections
- 2 pairs of types, where a type in Kami.Cocktail.Jobs uses a type in Kami.Cocktail.External.Import.
- The types involved
Kami.Cocktail.Jobs.SetupBar→Kami.Cocktail.External.Import.FromDataPackKami.Cocktail.Jobs.SyncBarRecipes→Kami.Cocktail.External.Import.FromDataPack
- Direction
- Kami.Cocktail.Jobs uses Kami.Cocktail.External.Import, so a change to Kami.Cocktail.External.Import can break Kami.Cocktail.Jobs, while a change to Kami.Cocktail.Jobs can't break Kami.Cocktail.External.Import.
- Position
- Below the diagonal: Kami.Cocktail.Jobs uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 23 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
| A02:2025 — Security Misconfiguration | 7 | High / Critical |
Roadmap
Top priorities: Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh; Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, HashiCorp Vault — not only APP_KEY in .env) and encrypt the most sensitive columns (Eloquent 'encrypted' casts, CipherSweet) — partial coverage still leaves gaps; Resolve the 1 finding(s) in DR & Backup.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +9.4 pts | Medium | Page structure |
| Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, HashiCorp Vault — not only APP_KEY in .env) and encrypt the most sensitive columns (Eloquent 'encrypted' casts, CipherSweet) — partial coverage still leaves gaps. | +4.2 pts | Medium | Data Protection |
| Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3). | +1.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 Banned license finding(s) in License Compliance. | +1.4 pts | Low | License Compliance |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.2 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 finding(s) in DR & Backup. | +2.2 pts | Medium | DR & Backup |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with artisan. | +0.7 pts | Low | ADR Quality |
| Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). | +0.6 pts | Low | IaC & Container Security |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| app/Http/Controllers/CocktailController.php | 5.5 | Mixed | Code Duplication: Edited copy of a member (64 corresponding lines) |
| app/External/Export/ToDataPack.php | 5.6 | Mixed | Code Duplication: Edited copy of a member (62 corresponding lines) |
| app/Http/Filters/CocktailQueryFilter.php | 6.0 | Mixed | Explicit Debt: TodoComment |
| app/Http/Filters/IngredientQueryFilter.php | 6.0 | Mixed | Explicit Debt: TodoComment |
| app/External/Import/FromSchema.php | 6.0 | Mixed | Explicit Debt: TodoComment |
| app/Infrastructure/EloquentCocktailRepository.php | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| app/External/Import/FromDataPack.php | 7.0 | Mixed | Cyclomatic Complexity: FromDataPack.importBaseCocktails (cyclomatic 28) |
| app/External/Export/ToRecipeType.php | 7.0 | Mixed | Cognitive Complexity: ToRecipeType.dumpCocktails (cognitive 16) |
| src/Domain/Ingredient/Ingredient.php | 7.0 | Mixed | God Classes: TooManyMethods: Ingredient |
| src/Domain/Bar/Bar.php | 7.0 | Mixed | Code Duplication: Edited copy of a member (10 corresponding lines) |
| app/Infrastructure/EloquentRecommendationRepository.php | 7.0 | Mixed | Code Duplication: Edited copy of a member (35 corresponding lines) |
| app/Http/Controllers/IngredientController.php | 7.1 | Mixed | Code Duplication: Edited copy of a member (57 corresponding lines) |
| app/Infrastructure/EloquentCocktailCollectionRepository.php | 7.2 | Mixed | Code Duplication: Members sharing a duplicated core (8 members, 50+ identical tokens) |
| app/Http/Controllers/CalculatorController.php | 7.2 | Mixed | Code Duplication: Edited copy of a member (22 corresponding lines) |
| app/Infrastructure/EloquentCocktailMethodRepository.php | 7.2 | Mixed | Code Duplication: Edited copy of a member (7 corresponding lines) |
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 65 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 65 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, 264 of 278 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.
- 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 (12 contributor(s) across 2329 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 11 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (composer.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (38990 LoC, 758 module-visible types across 97 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `app/BarContext.php`, `app/Console/Commands/BarExportRecipes.php`, `app/Console/Commands/BarFullBackup.php`, `app/Console/Commands/BarImportRecipes.php`, `app/Console/Commands/BarMaintenance.php`, … (+276 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Laravel's service container, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust and Java source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust or Java was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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 REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- 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.
- C5 Data-Subject Rights: This control is scored from in-repo evidence only — absence of evidence here means the scan found no in-repo trace, not that the control does not exist.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
8 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was FromDataPack.importBaseCocktails at 28. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being TuxedoNo2.hintCommonIngredients at 16 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: app/Scraper/Sites/TuxedoNo2.php (TuxedoNo2.hintCommonIngredients at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 8 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with FromDataPack.importBaseCocktails (cyclomatic 28), ReadsLDJson.readJSON (cyclomatic 26), FromDataPack.importIngredients (cyclomatic 24). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cyclomatic Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
15 method(s) exceeded the cognitive complexity threshold of 15; the worst was FromDataPack.importBaseCocktails at 60.
What to do
- Bring the 4 bodies over 30 down to 30 or less in Cognitive Complexity — start with FromDataPack.importBaseCocktails (cognitive 60), FromDataPack.importIngredients (cognitive 46), StarterMediaCatalogService.sourceObjects (cognitive 36). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 7.3 to about 8.1/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
8 god class(es) detected.
What to do
- Resolve the 4 TooManyMethods finding(s) in God Classes — start with Ingredient.php (2), Cocktail.php (2). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 MethodTooLong finding(s) in God Classes — start with CocktailQueryFilter.php, FromDataPack.php, FromSchema.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with FromDataPack.php. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
63 duplicated block group(s) detected. 6.1 % of the production lines (2,545 of 41,617) are in a reported copy. A further 58 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 6 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with GenerateController.php, IngredientReviewController.php, RatingController.php. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with BarInventoryController.php, CollectionResult.php, MemberInventoryController.php. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with EloquentIngredientReviewRepository.php, ImbibeMagazine.php, InventoryService.php. — One of this dimension's main actionable groups (5 warning-level).
D5 · Coupling
10 production modules (source-import), 0 dependency cycle(s), 0 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 1 module(s) off the main sequence, with abstractness counted on 4 of the 10 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
3 of 73 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with Bar.php, Calculator.php, Ingredient.php. — One of this dimension's main actionable groups (3 warning-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 380 tests.
D12 · Dependency Hygiene
4 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
1 of 134 locked Composer package(s) use a banned license. Licences were read from this repository's composer.lock, which records the `license` each package declares, over every package in its production `packages` list, direct and transitive, at the locked version; the 40 package(s) under `packages-dev` are not installed for a consumer and are excluded.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
Top hotspots: app/Http/Filters/CocktailQueryFilter.php (9×18=162); app/External/Import/FromDataPack.php (5×28=140); app/Http/Filters/IngredientQueryFilter.php (2×18=36)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with CocktailQueryFilter.php, FromDataPack.php, IngredientQueryFilter.php. — One of this dimension's main actionable groups (3 warning-level).
D17 · Explicit Debt
7 deducted task-comment markers across 41617 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 7 TodoComment finding(s) in Explicit Debt — start with RegisterUserService.php, EloquentCocktailRepository.php, Kernel.php. — One of this dimension's main actionable groups (7 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 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 — start with artisan. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
66 % of calls cross a namespace and 0 % go through an interface, but 82 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
23 finding(s): 0 critical, 22 high, 0 medium, 1 low. 16 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 281 file(s) — `app/BarContext.php` (line 14), `app/Console/Commands/BarExportRecipes.php` (line 41), `app/Console/Commands/BarFullBackup.php` (line 26), `app/Console/Commands/BarImportRecipes.php` (line 40), `app/Console/Commands/BarMaintenance.php` (line 28), … (+276 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
- No action in Static Analysis (SAST) — all 16 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (16 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
7 finding(s): 0 critical, 2 high, 5 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 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 168 of the 833 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: CocktailController.php↔CocktailIngredientResource.php 60%; ToRecipeType.php↔CocktailIngredient.php 60%; ToDataPack.php↔ToRecipeType.php 50%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with CocktailController.php, ToRecipeType.php, ToDataPack.php. — One of this dimension's main actionable groups (3 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
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 36 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
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <elements-api>, so there is no content here to wrap — render the <main> from the component mounted into it. — resources/views/elements.blade.php:2
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — resources/views/scalar.blade.php:2, resources/views/swagger.blade.php:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it. — resources/views/scalar.blade.php:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — resources/views/swagger.blade.php:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, HashiCorp Vault — not only APP_KEY in .env) and encrypt the most sensitive columns (Eloquent 'encrypted' casts, CipherSweet) — partial coverage still leaves gaps.
- Enforce HTTPS (URL::forceScheme('https') / URL::forceHttps() in Laravel, or requires_channel: https / route schemes in Symfony) so data in transit is always encrypted.
C2 · Access Controls
C5 · Data-Subject Rights
- Corroborated rights: erasure ✓ · export ✗ · consent ✗. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.
What to do
- Implement data export/portability for a data subject (a machine-readable export of their personal data).
- Track GDPR consent (lawful basis) alongside the personal data it authorises.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `PriceCategory`'s public constructor takes `description` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PriceCategory` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/Domain/Ingredient/PriceCategory.php:30
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
- `BarIngredient` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/BarIngredient.php:10
- `CalculatorBlock` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/CalculatorBlock.php:12
- `CocktailIngredient` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/CocktailIngredient.php:14
- `CocktailIngredientSubstitute` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/CocktailIngredientSubstitute.php:12
- `ComplexIngredient` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/ComplexIngredient.php:11
- `Ingredient` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/Ingredient.php:31
- `MemberInventory` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/MemberInventory.php:10
- `MemberInventoryIngredient` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/MemberInventoryIngredient.php:9
- `Menu` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/Menu.php:11
- `MenuCategory` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/MenuCategory.php:13
- `MenuCocktail` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/MenuCocktail.php:13
- `MenuIngredient` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/MenuIngredient.php:13
- `OauthCredential` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/OauthCredential.php:11
- `PriceCategory` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/PriceCategory.php:12
- `Tag` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/Tag.php:12
- `TasteDescriptor` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/TasteDescriptor.php:12
- `UserIngredient` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/UserIngredient.php:10
- `UserShoppingList` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/UserShoppingList.php:10
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `BarIngredient` exposes publicly writable state (timestamps). — app/Models/BarIngredient.php:10
- `CalculatorBlock` exposes publicly writable state (timestamps). — app/Models/CalculatorBlock.php:12
- `CocktailIngredient` exposes publicly writable state (timestamps). — app/Models/CocktailIngredient.php:14
- `CocktailIngredientSubstitute` exposes publicly writable state (timestamps). — app/Models/CocktailIngredientSubstitute.php:12
- `ComplexIngredient` exposes publicly writable state (timestamps). — app/Models/ComplexIngredient.php:11
- `MemberInventory` exposes publicly writable state (timestamps). — app/Models/MemberInventory.php:10
- `MemberInventoryIngredient` exposes publicly writable state (timestamps). — app/Models/MemberInventoryIngredient.php:9
- `MenuCategory` exposes publicly writable state (timestamps). — app/Models/MenuCategory.php:13
- `MenuCocktail` exposes publicly writable state (timestamps). — app/Models/MenuCocktail.php:13
- `MenuIngredient` exposes publicly writable state (timestamps). — app/Models/MenuIngredient.php:13
- `PriceCategory` exposes publicly writable state (timestamps). — app/Models/PriceCategory.php:12
- `Tag` exposes publicly writable state (timestamps, fillable). — app/Models/Tag.php:12
- `UserIngredient` exposes publicly writable state (timestamps). — app/Models/UserIngredient.php:10
- `UserShoppingList` exposes publicly writable state (timestamps). — app/Models/UserShoppingList.php:10
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
DM7 · Repository granularity
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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
P1 · CI/CD gates
P2 · Observability
What to do
- Add a health-check endpoint (Laravel's /up health route or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
P8 · Schema migrations
S1 · Web-Security Posture
- `https://unpkg.com/swagger-ui-dist@4.15.5/swagger-ui-bundle.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. — resources/views/swagger.blade.php:14
- Set: X-Content-Type-Options, X-Frame-Options. Missing: Content-Security-Policy, Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−1.0 on this card.) — REDACTED:1
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
- Add Content-Security-Policy, Strict-Transport-Security beside the headers already set; Content-Security-Policy is the one that pays for itself first, then Strict-Transport-Security, then nosniff and a frame policy.
X14 · Bypassable address classification
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×11) — app/Services/Image/ImageCleanupService.php:33, app/Services/Image/ImageValidatorService.php:43, app/Scraper/Sites/DefaultScraper.php:58, …
- `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — app/Scraper/Sites/CocktailParty.php:82, app/Scraper/Sites/KindredCocktails.php:44, app/Scraper/Sites/LiberAndCo.php:51, …
- `catch (\Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/Models/CocktailIngredient.php:87
What to do
- Swallowed exception (empty catch)
X4 · Structured logging
- `info` at line 38 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade. (×2) — app/Services/Image/CocktailImageGenerationService.php:38, app/Services/Image/IngredientImageGenerationService.php:38
- `info` at line 64 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Http/Controllers/GenerateController.php:64
- `info` at line 134 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Http/Controllers/GenerateController.php:134
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 71.2 | Strong | Solid. |
| Architecture | 86.2 | Strong | Strongest area. |
| Maturity | 70.6 | Strong | Solid. |
| Readiness | 57.2 | Adequate — gated by P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 46.1 | Weak — gated by D29, D36, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 78.6 | Strong | Solid. |
| Accessibility | 37.3 | Weak — gated by AC3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, a change-history library on the models — spatie/laravel-activitylog's LogsActivity, owen-it/laravel-auditing's Auditable, venturecraft/revisionable, Gedmo Loggable — or an Eloquent model event, observer or Doctrine listener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
Not included — 59 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AC6 Visual & motion safety — No styled element found in the parsed markup — AC6 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c install-php-extensions bcmath intl ffi" did not complete successfully: exit code: 100; likely cause (the repository): a RUN step of the repository's REDACTED exited with code 100 (`/bin/sh -c install-php-extensions bcmath intl ffi`): the build's own command failed, for example a compile or test error; runtime evidence skipped The cause is in the repository, not in our sandbox: a RUN step of the repository's REDACTED exited with code 100 (`/bin/sh -c install-php-extensions bcmath intl ffi`): the build's own command failed, for example a compile or test error. Nothing here says the surface is inaccessible, only that it was never rendered.
- 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 does not read PHP, html yet; not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (Models), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .php, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 281 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (6 PHP aggregate(s) recording domain events (recordThat/apply))
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 27 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang resources/views/scalar.blade.php:2
- <html> without a lang resources/views/swagger.blade.php:2
- REDACTED
- REDACTED
- Banned license: joomla/string
Serious — 232 finding(s)
- Anemic entity: BarIngredient app/Models/BarIngredient.php:10
- Anemic entity: CalculatorBlock app/Models/CalculatorBlock.php:12
- Anemic entity: CocktailIngredient app/Models/CocktailIngredient.php:14
- Anemic entity: CocktailIngredientSubstitute app/Models/CocktailIngredientSubstitute.php:12
- Anemic entity: ComplexIngredient app/Models/ComplexIngredient.php:11
- Anemic entity: Ingredient app/Models/Ingredient.php:31
- Anemic entity: MemberInventory app/Models/MemberInventory.php:10
- Anemic entity: MemberInventoryIngredient app/Models/MemberInventoryIngredient.php:9
- Anemic entity: Menu app/Models/Menu.php:11
- Anemic entity: MenuCategory app/Models/MenuCategory.php:13
- Anemic entity: MenuCocktail app/Models/MenuCocktail.php:13
- Anemic entity: MenuIngredient app/Models/MenuIngredient.php:13
- Anemic entity: OauthCredential app/Models/OauthCredential.php:11
- Anemic entity: PriceCategory app/Models/PriceCategory.php:12
- Anemic entity: Tag app/Models/Tag.php:12
- Anemic entity: TasteDescriptor app/Models/TasteDescriptor.php:12
- Anemic entity: UserIngredient app/Models/UserIngredient.php:10
- Anemic entity: UserShoppingList app/Models/UserShoppingList.php:10
- Mutable entity: BarIngredient app/Models/BarIngredient.php:10
- Mutable entity: CalculatorBlock app/Models/CalculatorBlock.php:12
- Mutable entity: CocktailIngredient app/Models/CocktailIngredient.php:14
- Mutable entity: CocktailIngredientSubstitute app/Models/CocktailIngredientSubstitute.php:12
- Mutable entity: ComplexIngredient app/Models/ComplexIngredient.php:11
- Mutable entity: MemberInventory app/Models/MemberInventory.php:10
- Mutable entity: MemberInventoryIngredient app/Models/MemberInventoryIngredient.php:9
- Mutable entity: MenuCategory app/Models/MenuCategory.php:13
- Mutable entity: MenuCocktail app/Models/MenuCocktail.php:13
- Mutable entity: MenuIngredient app/Models/MenuIngredient.php:13
- Mutable entity: PriceCategory app/Models/PriceCategory.php:12
- Mutable entity: Tag app/Models/Tag.php:12
- Mutable entity: UserIngredient app/Models/UserIngredient.php:10
- Mutable entity: UserShoppingList app/Models/UserShoppingList.php:10
- Swallowed exception (empty catch) app/Services/Image/ImageCleanupService.php:33
- Swallowed exception (empty catch) app/Services/Image/ImageValidatorService.php:43
- Swallowed exception (empty catch) app/Scraper/Sites/DefaultScraper.php:58
- Swallowed exception (empty catch) app/Scraper/Sites/DefaultScraper.php:76
- Swallowed exception (empty catch) app/Scraper/Sites/ImbibeMagazine.php:50
- Swallowed exception (empty catch) app/Scraper/Sites/ImbibeMagazine.php:181
- Swallowed exception (empty catch) app/Scraper/Sites/KindredCocktails.php:82
- Swallowed exception (empty catch) app/Scraper/Sites/KindredCocktails.php:91
- Swallowed exception (empty catch) app/Scraper/Sites/LiberAndCo.php:106
- Swallowed exception (empty catch) app/Scraper/Sites/LiberAndCo.php:115
- Swallowed exception (empty catch) app/Http/Resources/SubscriptionResource.php:79
- TodoComment app/Services/Auth/RegisterUserService.php:40
- TodoComment app/Infrastructure/EloquentCocktailRepository.php:57
- TodoComment app/Http/Kernel.php:64
- TodoComment app/Http/Filters/CocktailQueryFilter.php:77
- TodoComment app/Http/Filters/IngredientQueryFilter.php:111
- TodoComment app/External/Import/FromSchema.php:121
- TodoComment app/Console/Commands/BarImportRecipes.php:118
- Duplicated block (10 lines × 2) app/Http/Controllers/GenerateController.php:102
- Duplicated block (10 lines × 2) app/Http/Controllers/IngredientReviewController.php:112
- Duplicated block (10 lines × 2) app/Http/Controllers/RatingController.php:34
- Duplicated block (10 lines × 2) app/Infrastructure/EloquentRecommendationRepository.php:86
- Duplicated block (10 lines × 2) src/Application/Calculator/CalculatorService.php:36
- Duplicated block (10 lines × 2) app/Models/ValueObjects/AmountValueObject.php:40
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (12 corresponding lines) app/Http/Controllers/BarInventoryController.php:120
- Edited copy of a member (12 corresponding lines) src/Application/Cocktail/DTO/CollectionResult.php:27
- Edited copy of a member (12 corresponding lines) app/Http/Controllers/MemberInventoryController.php:73
- Edited copy of a member (12 corresponding lines) src/Application/Bar/MemberInventoryService.php:76
- Edited copy of a member (12 corresponding lines) app/Models/CocktailReview.php:42
- Edited copy of a member (10 corresponding lines) app/Infrastructure/EloquentIngredientReviewRepository.php:129
- Edited copy of a member (10 corresponding lines) app/Scraper/Sites/ImbibeMagazine.php:156
- Edited copy of a member (10 corresponding lines) src/Application/Bar/InventoryService.php:26
- Edited copy of a member (10 corresponding lines) src/Application/Cocktail/CocktailMethodService.php:31
- Edited copy of a member (10 corresponding lines) src/Domain/Bar/Bar.php:208
- Duplicated block (12 lines × 2) app/External/Export/ToDataPack.php:131
- Duplicated block (12 lines × 2) app/Http/Controllers/CalculatorController.php:80
- Duplicated block (12 lines × 2) app/Http/Controllers/IngredientController.php:320
- Duplicated block (12 lines × 2) src/Domain/IngredientHierarchy/IngredientHierarchyManager.php:42
- Duplicated block (12 lines × 2) app/Listeners/ActivateBars.php:15
- Duplicated block (8 lines × 2) app/Http/Controllers/CocktailController.php:120
- Duplicated block (8 lines × 2) src/Application/Ingredient/IngredientService.php:68
- Duplicated block (8 lines × 2) app/Infrastructure/EloquentCocktailMethodRepository.php:36
- Duplicated block (8 lines × 2) app/Models/ValueObjects/MaterializedPath.php:34
- Duplicated block (8 lines × 2) src/Application/Bar/BarService.php:103
- Swallowed exception (caught, then discarded) app/Scraper/Sites/CocktailParty.php:82
- Swallowed exception (caught, then discarded) app/Scraper/Sites/KindredCocktails.php:44
- Swallowed exception (caught, then discarded) app/Scraper/Sites/LiberAndCo.php:51
- Swallowed exception (caught, then discarded) app/Scraper/Sites/LiberAndCo.php:60
- Swallowed exception (caught, then discarded) app/Models/CocktailIngredient.php:87
- TooManyMethods: Ingredient app/Models/Ingredient.php:31
- TooManyMethods: Cocktail src/Domain/Cocktail/Cocktail.php:24
- TooManyMethods: Cocktail app/Models/Cocktail.php:31
- TooManyMethods: Ingredient src/Domain/Ingredient/Ingredient.php:27
- Edited copy of a member (13 corresponding lines) app/Http/Controllers/TagController.php:100
- Edited copy of a member (13 corresponding lines) app/Http/Controllers/MemberController.php:120
- Edited copy of a member (13 corresponding lines) app/Infrastructure/EloquentCocktailMatchRepository.php:21
- Edited copy of a member (13 corresponding lines) app/Http/Controllers/MemberInventoryController.php:177
- Edited copy of a member (14 corresponding lines) app/Infrastructure/EloquentIngredientHierarchyRepository.php:33
- Edited copy of a member (14 corresponding lines) app/Http/Controllers/RatingController.php:34
- Edited copy of a member (14 corresponding lines) app/Http/Controllers/IngredientReviewController.php:144
- Edited copy of a member (14 corresponding lines) app/Http/Controllers/CocktailController.php:387
- Duplicated block (7 lines × 2) app/External/Import/FromDataPack.php:141
- Duplicated block (7 lines × 2) app/Infrastructure/EloquentCocktailRepository.php:55
- Duplicated block (7 lines × 2) app/Infrastructure/EloquentIngredientReviewRepository.php:24
- Duplicated block (7 lines × 2) src/Application/Review/IngredientReviewService.php:64
- Duplicated block (6 lines × 2) app/Console/Commands/BarMergeIngredient.php:43
- Duplicated block (6 lines × 2) app/External/Import/FromDataPack.php:308
- Duplicated block (6 lines × 2) src/Domain/Bar/BarInventory.php:55
- Duplicated block (6 lines × 2) app/Infrastructure/EloquentGlassRepository.php:23
- Page without a main landmark resources/views/elements.blade.php:2
- Page without a main landmark resources/views/scalar.blade.php:2
- Page without a main landmark resources/views/swagger.blade.php:2
- Hotspot: app/Http/Filters/CocktailQueryFilter.php app/Http/Filters/CocktailQueryFilter.php:31
- Hotspot: app/External/Import/FromDataPack.php app/External/Import/FromDataPack.php:447
- Hotspot: app/Http/Filters/IngredientQueryFilter.php app/Http/Filters/IngredientQueryFilter.php:20
- MethodTooLong: CocktailQueryFilter.__construct app/Http/Filters/CocktailQueryFilter.php:31
- MethodTooLong: FromDataPack.importBaseCocktails app/External/Import/FromDataPack.php:447
- MethodTooLong: FromSchema.process app/External/Import/FromSchema.php:45
- Change coupling: CocktailController.php ↔ CocktailIngredientResource.php app/Http/Controllers/CocktailController.php:1
- Change coupling: ToRecipeType.php ↔ CocktailIngredient.php app/External/Export/ToRecipeType.php:1
- Change coupling: ToDataPack.php ↔ ToRecipeType.php app/External/Export/ToDataPack.php:1
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (8 corresponding lines) src/Application/Export/DTO/ExportResult.php:24
- Edited copy of a member (8 corresponding lines) app/Policies/IngredientReviewPolicy.php:28
- Edited copy of a member (8 corresponding lines) app/Infrastructure/EloquentCocktailMethodRepository.php:58
- Low cohesion: Bar (LCOM4 5) src/Domain/Bar/Bar.php:18
- Low cohesion: Calculator (LCOM4 4) src/Domain/Calculator/Calculator.php:13
- Low cohesion: Ingredient (LCOM4 4) src/Domain/Ingredient/Ingredient.php:27
- Edited copy of a member (32 corresponding lines) app/Http/Controllers/CocktailController.php:106
- Edited copy of a member (32 corresponding lines) app/GenAI/CocktailImageHandler.php:18
- Edited copy of a member (23 corresponding lines) app/Http/Controllers/GenerateController.php:219
- Edited copy of a member (23 corresponding lines) src/Domain/IngredientHierarchy/IngredientHierarchyManager.php:31
- Edited copy of a member (22 corresponding lines) app/Http/Controllers/CalculatorController.php:72
- Edited copy of a member (22 corresponding lines) app/Models/Calculator.php:64
- Edited copy of a member (18 corresponding lines) app/Http/Controllers/IngredientController.php:320
- Edited copy of a member (18 corresponding lines) src/Domain/Cocktail/CocktailMethod.php:116
- Edited copy of a member (15 corresponding lines) src/Application/Cocktail/GlassService.php:29
- Edited copy of a member (15 corresponding lines) app/Models/ValueObjects/MenuItem.php:30
- Edited copies of one member (3 members, 13+ corresponding lines) app/Http/Controllers/CocktailMethodController.php:71
- Edited copies of one member (3 members, 13+ corresponding lines) app/Http/Controllers/BarInventoryController.php:65
- Edited copy of a member (7 corresponding lines) app/Infrastructure/EloquentCocktailMethodRepository.php:70
- Edited copy of a member (7 corresponding lines) src/Application/Export/ExportService.php:46
- Edited copies of one member (4 members, 7+ corresponding lines) src/Application/Bar/MemberService.php:58
- Edited copies of one member (4 members, 7+ corresponding lines) src/Application/Cocktail/CocktailMethodService.php:67
- Edited copies of one member (3 members, 6+ corresponding lines) src/Application/Cocktail/DTO/CocktailMethodResult.php:22
- Edited copies of one member (3 members, 6+ corresponding lines) app/Scraper/Sites/EricsCocktailGuide.php:52
- Edited copies of one member (3 members, 9+ corresponding lines) app/Infrastructure/EloquentGlassRepository.php:70
- Edited copies of one member (3 members, 9+ corresponding lines) app/Http/Controllers/CocktailController.php:340
- Edited copy of a member (6 corresponding lines) app/Infrastructure/EloquentMenuRepository.php:102
- Edited copy of a member (6 corresponding lines) app/OpenAPI/Schemas/CocktailMethodRequest.php:22
- Duplicated block (18 lines × 2) app/External/Import/FromSchema.php:138
- Duplicated block (18 lines × 2) app/Infrastructure/EloquentRecommendationRepository.php:100
- Duplicated block (15 lines × 2) app/External/Import/FromDataPack.php:279
- Duplicated block (15 lines × 2) app/Infrastructure/EloquentRecommendationRepository.php:71
- Duplicated block (14 lines × 2) app/Models/ValueObjects/AmountValueObject.php:22
- Duplicated block (14 lines × 2) app/Models/Relations/HasManyAncestors.php:42
- Duplicated block (10 lines × 3) app/Http/Controllers/IngredientRatingController.php:35
- Duplicated block (10 lines × 3) app/Http/Controllers/IngredientRatingController.php:66
- Duplicated block (6 lines × 3) app/Infrastructure/EloquentBarRepository.php:69
- Duplicated block (6 lines × 3) app/Infrastructure/EloquentCocktailMethodRepository.php:20
- Duplicated block (5 lines × 5) app/Infrastructure/EloquentCocktailCollectionRepository.php:40
- Duplicated block (5 lines × 5) app/Infrastructure/EloquentCocktailCollectionRepository.php:40
- Duplicated block (5 lines × 3) app/Infrastructure/EloquentCocktailRepository.php:164
- Duplicated block (5 lines × 3) app/Infrastructure/EloquentGlassRepository.php:41
- Duplicated block (5 lines × 2) app/Infrastructure/EloquentGlassRepository.php:85
- Duplicated block (5 lines × 2) app/Models/ValueObjects/MaterializedPath.php:59
- Duplicated block (9 lines × 2) app/Http/Controllers/CalculatorController.php:143
- Duplicated block (9 lines × 2) src/Domain/Cocktail/Cocktail.php:286
- FromDataPack.importBaseCocktails (cyclomatic 28) app/External/Import/FromDataPack.php:447
- ReadsLDJson.readJSON (cyclomatic 26) app/Scraper/Concerns/ReadsLDJson.php:12
- FromDataPack.importIngredients (cyclomatic 24) app/External/Import/FromDataPack.php:204
- CocktailQueryFilter.__construct (cyclomatic 18) app/Http/Filters/CocktailQueryFilter.php:31
- IngredientQueryFilter.__construct (cyclomatic 18) app/Http/Filters/IngredientQueryFilter.php:20
- ScraperHttpClient.resolveDestination (cyclomatic 18) app/Scraper/ScraperHttpClient.php:94
- RecommendationScoringService.score (cyclomatic 17) src/Domain/Recommendation/RecommendationScoringService.php:35
- IngredientService.getIngredientsOrderedByUnlockedCocktails (cyclomatic 16) app/Services/IngredientService.php:43
- FromDataPack.importBaseCocktails (cognitive 60) app/External/Import/FromDataPack.php:447
- FromDataPack.importIngredients (cognitive 46) app/External/Import/FromDataPack.php:204
- StarterMediaCatalogService.sourceObjects (cognitive 36) app/Services/Image/StarterMediaCatalogService.php:30
- RecommendationScoringService.score (cognitive 31) src/Domain/Recommendation/RecommendationScoringService.php:35
- ReadsLDJson.readJSON (cognitive 29) app/Scraper/Concerns/ReadsLDJson.php:12
- IngredientService.getIngredientsOrderedByUnlockedCocktails (cognitive 27) app/Services/IngredientService.php:43
- ImageController.store (cognitive 25) app/Http/Controllers/ImageController.php:56
- RobotsTxtEvaluator.parse (cognitive 23) app/Scraper/RobotsTxtEvaluator.php:71
- FromDataPack.importGlasses (cognitive 22) app/External/Import/FromDataPack.php:349
- CocktailQueryFilter.__construct (cognitive 20) app/Http/Filters/CocktailQueryFilter.php:31
- IngredientQueryFilter.__construct (cognitive 19) app/Http/Filters/IngredientQueryFilter.php:20
- ScraperHttpClient.resolveDestination (cognitive 19) app/Scraper/ScraperHttpClient.php:94
- FromSchema.process (cognitive 18) app/External/Import/FromSchema.php:45
- ReadsHTMLSchema.readHTML (cognitive 17) app/Scraper/Concerns/ReadsHTMLSchema.php:12
- ToRecipeType.dumpCocktails (cognitive 16) app/External/Export/ToRecipeType.php:99
- ClassTooLong: FromDataPack app/External/Import/FromDataPack.php:35
- REDACTED
- Members sharing a duplicated core (8 members, 50+ identical tokens) app/Infrastructure/EloquentCocktailCollectionRepository.php:34
- Members sharing a duplicated core (4 members, 50+ identical tokens) app/Http/Controllers/IngredientRatingController.php:35
- Edited copy of a member (64 corresponding lines) app/Http/Controllers/CocktailController.php:181
- Edited copy of a member (62 corresponding lines) app/External/Export/ToDataPack.php:47
- Edited copy of a member (57 corresponding lines) app/Http/Controllers/IngredientController.php:158
- Edited copy of a member (35 corresponding lines) app/Infrastructure/EloquentRecommendationRepository.php:61
- Edited copy of a member (38 corresponding lines) app/Infrastructure/EloquentBarInventoryRepository.php:37
- Edited copies of one member (4 members, 20+ corresponding lines) app/External/Matcher.php:31
- Edited copy of a member (19 corresponding lines) src/Application/Matcher/GlassMatcher.php:24
- Edited copies of one member (3 members, 15+ corresponding lines) app/External/Export/ToDataPack.php:114
- Edited copy of a member (21 corresponding lines) app/External/Model/CocktailIngredient.php:54
- Edited copy of a member (16 corresponding lines) app/Http/Controllers/GlassController.php:72
- Edited copies of one member (4 members, 13+ corresponding lines) src/Application/Cocktail/CocktailMethodService.php:49
- Edited copy of a member (11 corresponding lines) app/Http/Controllers/IngredientReviewController.php:44
- Edited copy of a member (9 corresponding lines) app/Utils.php:46
- Duplicated block (33 lines × 2) app/Http/Controllers/CocktailController.php:189
- Duplicated block (29–30 lines × 2) app/External/Import/FromDataPack.php:390
- Duplicated block (29 lines × 2) app/External/Export/ToDataPack.php:81
- Duplicated block (23 lines × 2) src/Application/Cocktail/CocktailService.php:71
- Duplicated block (21 lines × 2) app/Http/Controllers/IngredientController.php:169
- Duplicated block (17–20 lines × 2) app/External/Export/ToDataPack.php:47
- Duplicated block (19 lines × 2) app/Http/Controllers/CocktailController.php:224
- Duplicated block (17 lines × 2) app/Http/Controllers/IngredientController.php:194
- Duplicated block (16 lines × 2) app/Infrastructure/EloquentRecommendationRepository.php:245
- Duplicated block (15–16 lines × 2) app/Services/Image/CocktailImageGenerationService.php:46
- Duplicated block (15 lines × 3) app/Infrastructure/EloquentRecommendationRepository.php:135
- Duplicated block (14 lines × 3) app/External/Import/FromDataPack.php:279
- Duplicated block (12 lines × 3) app/Infrastructure/EloquentRecommendationRepository.php:70
- Duplicated block (10 lines × 4) app/Infrastructure/EloquentRecommendationRepository.php:26
- Duplicated block (7 lines × 4) app/Infrastructure/EloquentCocktailCollectionRepository.php:42
- Duplicated block (8 lines × 3) app/External/Import/FromDataPack.php:259
- Duplicated block (49 lines × 2) app/Models/ValueObjects/UnitValueObject.php:24
- Duplicated block (16 lines × 4) app/Policies/CalculatorPolicy.php:17
- Duplicated block (13 lines × 2) app/Models/MenuCocktail.php:54
- Duplicated block (7 lines × 3) app/Http/Controllers/CalculatorController.php:49
- Duplicated block (9 lines × 5) app/Http/Controllers/CocktailMethodController.php:126
- Off the main sequence: src/Domain
- Constructible in an invalid state: PriceCategory src/Domain/Ingredient/PriceCategory.php:30
- No DR/backup evidence
- Third-party script without Subresource Integrity resources/views/swagger.blade.php:14
Minor — 15 finding(s)
- Interpolated log message defeats structured logging app/Services/Image/CocktailImageGenerationService.php:38
- Interpolated log message defeats structured logging app/Services/Image/IngredientImageGenerationService.php:38
- Interpolated log message defeats structured logging app/Http/Controllers/GenerateController.php:64
- Interpolated log message defeats structured logging app/Http/Controllers/GenerateController.php:134
- Duplicated predicate app/Models/ValueObjects/UnitValueObject.php:57
- Duplicated predicate app/Models/ValueObjects/UnitValueObject.php:43
- Partial data-subject-rights support
- No ADRs found artisan:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Security headers incomplete REDACTED:1
Minor — 4 finding(s)
- Outdated: laravel/ai
- Outdated: laravel/horizon
- Outdated: laravel/sanctum
- Outdated: laravel/socialite
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-ee2f368c6e6742e8900ca429d7087b64/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-ee2f368c6e6742e8900ca429d7087b64/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=1343" --report-format json --report-path /tmp/watchdog-gitleaks-ee2f368c6e6742e8900ca429d7087b64/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ee2f368c6e6742e8900ca429d7087b64/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 . | 23 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 7 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 281 file(s) — `app/BarContext.php`, `app/Console/Commands/BarExportRecipes.php`, `app/Console/Commands/BarFullBackup.php`, `app/Console/Commands/BarImportRecipes.php`, `app/Console/Commands/BarMaintenance.php`, … (+276 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 |