Executive summary
Tmaturano/Bookify falls short of our standard for production because ten passwords or keys sit in the current code and we found no automated security scanning of the code, its secrets or its dependencies. It scores 50 out of 100 and is rated Adequate, and all 27 of its critical findings are security problems.
Production Readiness, at 39, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 7 points. Replacing the ten exposed passwords or keys and switching the old ones off would lift Production Readiness itself, worth about 9 points. Raising Production Readiness to 70 would lift the score to about 57.
Ten passwords or keys in the code and five in the code's history are open to anyone who can read the repository. Five settings leave the servers or containers unsafe, and three known security holes in the packages the code depends on can be used by attackers. Replacing each exposed password or key, correcting the unsafe settings and updating the vulnerable packages would close these risks. Pinning each tool to an exact version would fix the two pipeline tools referenced by a changeable name, and fixing the weaknesses the scanner points to would deal with the two security weaknesses in the code.
The product code is 2,787 lines, about €6,100 to rebuild.
If Production Readiness rose from 39 to 70, the lowest score rated Strong, the score would rise from 50 to about 57.
New since the last survey: 2 findings
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
Rebuild cost: about €6,100 · Estimate
| Cost to rebuild | €2,100 to €10,000, for 34 to 108 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Very 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 50. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 2,787 lines of product code, of which 39% is declarations and boilerplate, 53% straight logic and 8% logic with branches |
| 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 Application.Abstractions.Clock | 2 Application.Abstractions.Data | 3 Application.Abstractions.Messaging | 4 Domain.Entities.Abstractions | 5 Domain.Entities.Apartments.Enums | 6 Domain.Entities.Apartments.ValueObjects | 7 Domain.Entities.Bookings.Enums | 8 Domain.Entities.Users.ValueObjects | 9 Domain.Shared | 10 Application.Abstractions.Caching | 11 Application.Abstractions.Email | 12 Application.Apartments.SearchApartments | 13 Domain.Apartments | 14 Domain.Entities.Apartments | 15 Domain.Entities.Bookings.ValueObjects | 16 Domain.Entities.Reviews.ValueObjects | 17 Domain.Entities.Users | 18 Infrastructure | 19 Infrastructure.Clock | 20 Infrastructure.Outbox | 21 Application.Abstractions.Authentication | 22 Application.Abstractions.Behaviors | 23 Domain.Entities.Bookings | 24 Domain.Entities.Users.Events | 25 Infrastructure.Authentication.Models | 26 Infrastructure.Authorization | 27 Infrastructure.Caching | 28 Infrastructure.Email | 29 Application.Bookings.GetBooking | 30 Application.Users.GetLoggedInUser | 31 Application.Users.LogInUser | 32 Application.Users.RegisterUser | 33 Domain.Entities.Bookings.Events | 34 Domain.Entities.Reviews | 35 Infrastructure.Authentication | 36 Infrastructure.Repositories | 37 API.Controllers.Bookings | 38 Application.Bookings.ReserveBooking | 39 Domain.Entities.Reviews.Events | 40 Infrastructure.Configurations |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Application.Abstractions.Clock | ||||||||||||||||||||||||||||||||||||||||
| 2 Application.Abstractions.Data | ||||||||||||||||||||||||||||||||||||||||
| 3 Application.Abstractions.Messaging | ||||||||||||||||||||||||||||||||||||||||
| 4 Domain.Entities.Abstractions | ||||||||||||||||||||||||||||||||||||||||
| 5 Domain.Entities.Apartments.Enums | ||||||||||||||||||||||||||||||||||||||||
| 6 Domain.Entities.Apartments.ValueObjects | ||||||||||||||||||||||||||||||||||||||||
| 7 Domain.Entities.Bookings.Enums | ||||||||||||||||||||||||||||||||||||||||
| 8 Domain.Entities.Users.ValueObjects | ||||||||||||||||||||||||||||||||||||||||
| 9 Domain.Shared | ||||||||||||||||||||||||||||||||||||||||
| 10 Application.Abstractions.Caching | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Application.Abstractions.Email | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Application.Apartments.SearchApartments | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 Domain.Apartments | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Domain.Entities.Apartments | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 Domain.Entities.Bookings.ValueObjects | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Domain.Entities.Reviews.ValueObjects | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 Domain.Entities.Users | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 Infrastructure | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 Infrastructure.Clock | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Infrastructure.Outbox | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Application.Abstractions.Authentication | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 Application.Abstractions.Behaviors | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Domain.Entities.Bookings | 3 | 1 | 1 | 4 | 4 | 1 | ||||||||||||||||||||||||||||||||||
| 24 Domain.Entities.Users.Events | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 Infrastructure.Authentication.Models | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Infrastructure.Authorization | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 Infrastructure.Caching | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Infrastructure.Email | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 Application.Bookings.GetBooking | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 30 Application.Users.GetLoggedInUser | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 Application.Users.LogInUser | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 Application.Users.RegisterUser | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 Domain.Entities.Bookings.Events | 5 | 5 | ||||||||||||||||||||||||||||||||||||||
| 34 Domain.Entities.Reviews | 3 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 35 Infrastructure.Authentication | 2 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 Infrastructure.Repositories | 1 | 2 | 1 | 2 | 4 | 1 | ||||||||||||||||||||||||||||||||||
| 37 API.Controllers.Bookings | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 Application.Bookings.ReserveBooking | 1 | 2 | 2 | 1 | 1 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 39 Domain.Entities.Reviews.Events | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 Infrastructure.Configurations | 1 | 4 | 1 | 1 | 1 |
10→3 Application.Abstractions.Caching uses Application.Abstractions.Messaging✕
- Connections
- 1 pair of types, where a type in Application.Abstractions.Caching uses a type in Application.Abstractions.Messaging.
- The types involved
Bookify.Application.Abstractions.Caching.ICachedQuery→Bookify.Application.Abstractions.Messaging.IQuery
- Direction
- Application.Abstractions.Caching uses Application.Abstractions.Messaging, so a change to Application.Abstractions.Messaging can break Application.Abstractions.Caching, while a change to Application.Abstractions.Caching can't break Application.Abstractions.Messaging.
- Position
- Below the diagonal: Application.Abstractions.Caching uses a module listed above it, which is the healthy direction.
11→8 Application.Abstractions.Email uses Domain.Entities.Users.ValueObjects✕
- Connections
- 1 pair of types, where a type in Application.Abstractions.Email uses a type in Domain.Entities.Users.ValueObjects.
- The types involved
Bookify.Application.Abstractions.Email.IEmailService→Bookify.Domain.Entities.Users.ValueObjects.Email
- Direction
- Application.Abstractions.Email uses Domain.Entities.Users.ValueObjects, so a change to Domain.Entities.Users.ValueObjects can break Application.Abstractions.Email, while a change to Application.Abstractions.Email can't break Domain.Entities.Users.ValueObjects.
- Position
- Below the diagonal: Application.Abstractions.Email uses a module listed above it, which is the healthy direction.
12→2 Application.Apartments.SearchApartments uses Application.Abstractions.Data✕
- Connections
- 1 pair of types, where a type in Application.Apartments.SearchApartments uses a type in Application.Abstractions.Data.
- The types involved
Bookify.Application.Apartments.SearchApartments.SearchApartmentQueryHandler→Bookify.Application.Abstractions.Data.ISqlConnectionFactory
- Direction
- Application.Apartments.SearchApartments uses Application.Abstractions.Data, so a change to Application.Abstractions.Data can break Application.Apartments.SearchApartments, while a change to Application.Apartments.SearchApartments can't break Application.Abstractions.Data.
- Position
- Below the diagonal: Application.Apartments.SearchApartments uses a module listed above it, which is the healthy direction.
12→3 Application.Apartments.SearchApartments uses Application.Abstractions.Messaging✕
- Connections
- 2 pairs of types, where a type in Application.Apartments.SearchApartments uses a type in Application.Abstractions.Messaging.
- The types involved
Bookify.Application.Apartments.SearchApartments.SearchApartmentQueryHandler→Bookify.Application.Abstractions.Messaging.IQueryHandlerBookify.Application.Apartments.SearchApartments.SearchApartmentsQuery→Bookify.Application.Abstractions.Messaging.IQuery
- Direction
- Application.Apartments.SearchApartments uses Application.Abstractions.Messaging, so a change to Application.Abstractions.Messaging can break Application.Apartments.SearchApartments, while a change to Application.Apartments.SearchApartments can't break Application.Abstractions.Messaging.
- Position
- Below the diagonal: Application.Apartments.SearchApartments uses a module listed above it, which is the healthy direction.
12→4 Application.Apartments.SearchApartments uses Domain.Entities.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Apartments.SearchApartments uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Application.Apartments.SearchApartments.SearchApartmentQueryHandler→Bookify.Domain.Entities.Abstractions.Result
- Direction
- Application.Apartments.SearchApartments uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Application.Apartments.SearchApartments, while a change to Application.Apartments.SearchApartments can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Application.Apartments.SearchApartments uses a module listed above it, which is the healthy direction.
13→4 Domain.Apartments uses Domain.Entities.Abstractions✕
- Connections
- 1 pair of types, where a type in Domain.Apartments uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Domain.Apartments.ApartmentErrors→Bookify.Domain.Entities.Abstractions.Error
- Direction
- Domain.Apartments uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Domain.Apartments, while a change to Domain.Apartments can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Domain.Apartments uses a module listed above it, which is the healthy direction.
14→4 Domain.Entities.Apartments uses Domain.Entities.Abstractions✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Apartments uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Domain.Entities.Apartments.Apartment→Bookify.Domain.Entities.Abstractions.Entity
- Direction
- Domain.Entities.Apartments uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Domain.Entities.Apartments, while a change to Domain.Entities.Apartments can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Domain.Entities.Apartments uses a module listed above it, which is the healthy direction.
14→5 Domain.Entities.Apartments uses Domain.Entities.Apartments.Enums✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Apartments uses a type in Domain.Entities.Apartments.Enums.
- The types involved
Bookify.Domain.Entities.Apartments.Apartment→Bookify.Domain.Entities.Apartments.Enums.Amenity
- Direction
- Domain.Entities.Apartments uses Domain.Entities.Apartments.Enums, so a change to Domain.Entities.Apartments.Enums can break Domain.Entities.Apartments, while a change to Domain.Entities.Apartments can't break Domain.Entities.Apartments.Enums.
- Position
- Below the diagonal: Domain.Entities.Apartments uses a module listed above it, which is the healthy direction.
14→6 Domain.Entities.Apartments uses Domain.Entities.Apartments.ValueObjects✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Apartments uses a type in Domain.Entities.Apartments.ValueObjects.
- The types involved
Bookify.Domain.Entities.Apartments.Apartment→Bookify.Domain.Entities.Apartments.ValueObjects.Address
- Direction
- Domain.Entities.Apartments uses Domain.Entities.Apartments.ValueObjects, so a change to Domain.Entities.Apartments.ValueObjects can break Domain.Entities.Apartments, while a change to Domain.Entities.Apartments can't break Domain.Entities.Apartments.ValueObjects.
- Position
- Below the diagonal: Domain.Entities.Apartments uses a module listed above it, which is the healthy direction.
14→9 Domain.Entities.Apartments uses Domain.Shared✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Apartments uses a type in Domain.Shared.
- The types involved
Bookify.Domain.Entities.Apartments.Apartment→Bookify.Domain.Shared.Money
- Direction
- Domain.Entities.Apartments uses Domain.Shared, so a change to Domain.Shared can break Domain.Entities.Apartments, while a change to Domain.Entities.Apartments can't break Domain.Shared.
- Position
- Below the diagonal: Domain.Entities.Apartments uses a module listed above it, which is the healthy direction.
15→9 Domain.Entities.Bookings.ValueObjects uses Domain.Shared✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Bookings.ValueObjects uses a type in Domain.Shared.
- The types involved
Bookify.Domain.Entities.Bookings.ValueObjects.PricingDetails→Bookify.Domain.Shared.Money
- Direction
- Domain.Entities.Bookings.ValueObjects uses Domain.Shared, so a change to Domain.Shared can break Domain.Entities.Bookings.ValueObjects, while a change to Domain.Entities.Bookings.ValueObjects can't break Domain.Shared.
- Position
- Below the diagonal: Domain.Entities.Bookings.ValueObjects uses a module listed above it, which is the healthy direction.
16→4 Domain.Entities.Reviews.ValueObjects uses Domain.Entities.Abstractions✕
- Connections
- 2 pairs of types, where a type in Domain.Entities.Reviews.ValueObjects uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Domain.Entities.Reviews.ValueObjects.Rating→Bookify.Domain.Entities.Abstractions.ErrorBookify.Domain.Entities.Reviews.ValueObjects.Rating→Bookify.Domain.Entities.Abstractions.Result
- Direction
- Domain.Entities.Reviews.ValueObjects uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Domain.Entities.Reviews.ValueObjects, while a change to Domain.Entities.Reviews.ValueObjects can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Domain.Entities.Reviews.ValueObjects uses a module listed above it, which is the healthy direction.
17→4 Domain.Entities.Users uses Domain.Entities.Abstractions✕
- Connections
- 2 pairs of types, where a type in Domain.Entities.Users uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Domain.Entities.Users.User→Bookify.Domain.Entities.Abstractions.EntityBookify.Domain.Entities.Users.UserErrors→Bookify.Domain.Entities.Abstractions.Error
- Direction
- Domain.Entities.Users uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Domain.Entities.Users, while a change to Domain.Entities.Users can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Domain.Entities.Users uses a module listed above it, which is the healthy direction.
17→8 Domain.Entities.Users uses Domain.Entities.Users.ValueObjects✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Users uses a type in Domain.Entities.Users.ValueObjects.
- The types involved
Bookify.Domain.Entities.Users.User→Bookify.Domain.Entities.Users.ValueObjects.Email
- Direction
- Domain.Entities.Users uses Domain.Entities.Users.ValueObjects, so a change to Domain.Entities.Users.ValueObjects can break Domain.Entities.Users, while a change to Domain.Entities.Users can't break Domain.Entities.Users.ValueObjects.
- Position
- Below the diagonal: Domain.Entities.Users uses a module listed above it, which is the healthy direction.
18→1 Infrastructure uses Application.Abstractions.Clock✕
- Connections
- 1 pair of types, where a type in Infrastructure uses a type in Application.Abstractions.Clock.
- The types involved
Bookify.Infrastructure.ApplicationDbContext→Bookify.Application.Abstractions.Clock.IDateTimeProvider
- Direction
- Infrastructure uses Application.Abstractions.Clock, so a change to Application.Abstractions.Clock can break Infrastructure, while a change to Infrastructure can't break Application.Abstractions.Clock.
- Position
- Below the diagonal: Infrastructure uses a module listed above it, which is the healthy direction.
18→4 Infrastructure uses Domain.Entities.Abstractions✕
- Connections
- 1 pair of types, where a type in Infrastructure uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Infrastructure.ApplicationDbContext→Bookify.Domain.Entities.Abstractions.IUnitOfWork
- Direction
- Infrastructure uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Infrastructure, while a change to Infrastructure can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Infrastructure uses a module listed above it, which is the healthy direction.
19→1 Infrastructure.Clock uses Application.Abstractions.Clock✕
- Connections
- 1 pair of types, where a type in Infrastructure.Clock uses a type in Application.Abstractions.Clock.
- The types involved
Bookify.Infrastructure.Clock.DateTimeProvider→Bookify.Application.Abstractions.Clock.IDateTimeProvider
- Direction
- Infrastructure.Clock uses Application.Abstractions.Clock, so a change to Application.Abstractions.Clock can break Infrastructure.Clock, while a change to Infrastructure.Clock can't break Application.Abstractions.Clock.
- Position
- Below the diagonal: Infrastructure.Clock uses a module listed above it, which is the healthy direction.
20→1 Infrastructure.Outbox uses Application.Abstractions.Clock✕
- Connections
- 1 pair of types, where a type in Infrastructure.Outbox uses a type in Application.Abstractions.Clock.
- The types involved
Bookify.Infrastructure.Outbox.ProcessOutboxMessagesJob→Bookify.Application.Abstractions.Clock.IDateTimeProvider
- Direction
- Infrastructure.Outbox uses Application.Abstractions.Clock, so a change to Application.Abstractions.Clock can break Infrastructure.Outbox, while a change to Infrastructure.Outbox can't break Application.Abstractions.Clock.
- Position
- Below the diagonal: Infrastructure.Outbox uses a module listed above it, which is the healthy direction.
20→2 Infrastructure.Outbox uses Application.Abstractions.Data✕
- Connections
- 1 pair of types, where a type in Infrastructure.Outbox uses a type in Application.Abstractions.Data.
- The types involved
Bookify.Infrastructure.Outbox.ProcessOutboxMessagesJob→Bookify.Application.Abstractions.Data.ISqlConnectionFactory
- Direction
- Infrastructure.Outbox uses Application.Abstractions.Data, so a change to Application.Abstractions.Data can break Infrastructure.Outbox, while a change to Infrastructure.Outbox can't break Application.Abstractions.Data.
- Position
- Below the diagonal: Infrastructure.Outbox uses a module listed above it, which is the healthy direction.
21→4 Application.Abstractions.Authentication uses Domain.Entities.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Abstractions.Authentication uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Application.Abstractions.Authentication.IJwtService→Bookify.Domain.Entities.Abstractions.Result
- Direction
- Application.Abstractions.Authentication uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Application.Abstractions.Authentication, while a change to Application.Abstractions.Authentication can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Application.Abstractions.Authentication uses a module listed above it, which is the healthy direction.
21→17 Application.Abstractions.Authentication uses Domain.Entities.Users✕
- Connections
- 1 pair of types, where a type in Application.Abstractions.Authentication uses a type in Domain.Entities.Users.
- The types involved
Bookify.Application.Abstractions.Authentication.IAuthenticationService→Bookify.Domain.Entities.Users.User
- Direction
- Application.Abstractions.Authentication uses Domain.Entities.Users, so a change to Domain.Entities.Users can break Application.Abstractions.Authentication, while a change to Application.Abstractions.Authentication can't break Domain.Entities.Users.
- Position
- Below the diagonal: Application.Abstractions.Authentication uses a module listed above it, which is the healthy direction.
22→10 Application.Abstractions.Behaviors uses Application.Abstractions.Caching✕
- Connections
- 1 pair of types, where a type in Application.Abstractions.Behaviors uses a type in Application.Abstractions.Caching.
- The types involved
Bookify.Application.Abstractions.Behaviors.QueryCachingBehavior→Bookify.Application.Abstractions.Caching.ICacheService
- Direction
- Application.Abstractions.Behaviors uses Application.Abstractions.Caching, so a change to Application.Abstractions.Caching can break Application.Abstractions.Behaviors, while a change to Application.Abstractions.Behaviors can't break Application.Abstractions.Caching.
- Position
- Below the diagonal: Application.Abstractions.Behaviors uses a module listed above it, which is the healthy direction.
23→4 Domain.Entities.Bookings uses Domain.Entities.Abstractions✕
- Connections
- 3 pairs of types, where a type in Domain.Entities.Bookings uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Domain.Entities.Bookings.Booking→Bookify.Domain.Entities.Abstractions.EntityBookify.Domain.Entities.Bookings.Booking→Bookify.Domain.Entities.Abstractions.ResultBookify.Domain.Entities.Bookings.BookingErrors→Bookify.Domain.Entities.Abstractions.Error
- Direction
- Domain.Entities.Bookings uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Domain.Entities.Bookings, while a change to Domain.Entities.Bookings can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Domain.Entities.Bookings uses a module listed above it, which is the healthy direction.
23→7 Domain.Entities.Bookings uses Domain.Entities.Bookings.Enums✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Bookings uses a type in Domain.Entities.Bookings.Enums.
- The types involved
Bookify.Domain.Entities.Bookings.Booking→Bookify.Domain.Entities.Bookings.Enums.BookingStatus
- Direction
- Domain.Entities.Bookings uses Domain.Entities.Bookings.Enums, so a change to Domain.Entities.Bookings.Enums can break Domain.Entities.Bookings, while a change to Domain.Entities.Bookings can't break Domain.Entities.Bookings.Enums.
- Position
- Below the diagonal: Domain.Entities.Bookings uses a module listed above it, which is the healthy direction.
23→9 Domain.Entities.Bookings uses Domain.Shared✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Bookings uses a type in Domain.Shared.
- The types involved
Bookify.Domain.Entities.Bookings.Booking→Bookify.Domain.Shared.Money
- Direction
- Domain.Entities.Bookings uses Domain.Shared, so a change to Domain.Shared can break Domain.Entities.Bookings, while a change to Domain.Entities.Bookings can't break Domain.Shared.
- Position
- Below the diagonal: Domain.Entities.Bookings uses a module listed above it, which is the healthy direction.
23→14 Domain.Entities.Bookings uses Domain.Entities.Apartments✕
- Connections
- 4 pairs of types, where a type in Domain.Entities.Bookings uses a type in Domain.Entities.Apartments.
- The types involved
Bookify.Domain.Entities.Bookings.Booking→Bookify.Domain.Entities.Apartments.ApartmentBookify.Domain.Entities.Bookings.Booking→Bookify.Domain.Entities.Apartments.ApartmentIdBookify.Domain.Entities.Bookings.IBookingRepository→Bookify.Domain.Entities.Apartments.ApartmentBookify.Domain.Entities.Bookings.PricingService→Bookify.Domain.Entities.Apartments.Apartment
- Direction
- Domain.Entities.Bookings uses Domain.Entities.Apartments, so a change to Domain.Entities.Apartments can break Domain.Entities.Bookings, while a change to Domain.Entities.Bookings can't break Domain.Entities.Apartments.
- Position
- Below the diagonal: Domain.Entities.Bookings uses a module listed above it, which is the healthy direction.
23→15 Domain.Entities.Bookings uses Domain.Entities.Bookings.ValueObjects✕
- Connections
- 4 pairs of types, where a type in Domain.Entities.Bookings uses a type in Domain.Entities.Bookings.ValueObjects.
- The types involved
Bookify.Domain.Entities.Bookings.Booking→Bookify.Domain.Entities.Bookings.ValueObjects.DateRangeBookify.Domain.Entities.Bookings.IBookingRepository→Bookify.Domain.Entities.Bookings.ValueObjects.DateRangeBookify.Domain.Entities.Bookings.PricingService→Bookify.Domain.Entities.Bookings.ValueObjects.DateRangeBookify.Domain.Entities.Bookings.PricingService→Bookify.Domain.Entities.Bookings.ValueObjects.PricingDetails
- Direction
- Domain.Entities.Bookings uses Domain.Entities.Bookings.ValueObjects, so a change to Domain.Entities.Bookings.ValueObjects can break Domain.Entities.Bookings, while a change to Domain.Entities.Bookings can't break Domain.Entities.Bookings.ValueObjects.
- Position
- Below the diagonal: Domain.Entities.Bookings uses a module listed above it, which is the healthy direction.
23→17 Domain.Entities.Bookings uses Domain.Entities.Users✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Bookings uses a type in Domain.Entities.Users.
- The types involved
Bookify.Domain.Entities.Bookings.Booking→Bookify.Domain.Entities.Users.UserId
- Direction
- Domain.Entities.Bookings uses Domain.Entities.Users, so a change to Domain.Entities.Users can break Domain.Entities.Bookings, while a change to Domain.Entities.Bookings can't break Domain.Entities.Users.
- Position
- Below the diagonal: Domain.Entities.Bookings uses a module listed above it, which is the healthy direction.
24→4 Domain.Entities.Users.Events uses Domain.Entities.Abstractions✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Users.Events uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Domain.Entities.Users.Events.UserCreatedDomainEvent→Bookify.Domain.Entities.Abstractions.IDomainEvent
- Direction
- Domain.Entities.Users.Events uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Domain.Entities.Users.Events, while a change to Domain.Entities.Users.Events can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Domain.Entities.Users.Events uses a module listed above it, which is the healthy direction.
24→17 Domain.Entities.Users.Events uses Domain.Entities.Users✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Users.Events uses a type in Domain.Entities.Users.
- The types involved
Bookify.Domain.Entities.Users.Events.UserCreatedDomainEvent→Bookify.Domain.Entities.Users.UserId
- Direction
- Domain.Entities.Users.Events uses Domain.Entities.Users, so a change to Domain.Entities.Users can break Domain.Entities.Users.Events, while a change to Domain.Entities.Users.Events can't break Domain.Entities.Users.
- Position
- Below the diagonal: Domain.Entities.Users.Events uses a module listed above it, which is the healthy direction.
25→17 Infrastructure.Authentication.Models uses Domain.Entities.Users✕
- Connections
- 1 pair of types, where a type in Infrastructure.Authentication.Models uses a type in Domain.Entities.Users.
- The types involved
Bookify.Infrastructure.Authentication.Models.UserRepresentationModel→Bookify.Domain.Entities.Users.User
- Direction
- Infrastructure.Authentication.Models uses Domain.Entities.Users, so a change to Domain.Entities.Users can break Infrastructure.Authentication.Models, while a change to Infrastructure.Authentication.Models can't break Domain.Entities.Users.
- Position
- Below the diagonal: Infrastructure.Authentication.Models uses a module listed above it, which is the healthy direction.
26→10 Infrastructure.Authorization uses Application.Abstractions.Caching✕
- Connections
- 1 pair of types, where a type in Infrastructure.Authorization uses a type in Application.Abstractions.Caching.
- The types involved
Bookify.Infrastructure.Authorization.AuthorizationService→Bookify.Application.Abstractions.Caching.ICacheService
- Direction
- Infrastructure.Authorization uses Application.Abstractions.Caching, so a change to Application.Abstractions.Caching can break Infrastructure.Authorization, while a change to Infrastructure.Authorization can't break Application.Abstractions.Caching.
- Position
- Below the diagonal: Infrastructure.Authorization uses a module listed above it, which is the healthy direction.
26→17 Infrastructure.Authorization uses Domain.Entities.Users✕
- Connections
- 1 pair of types, where a type in Infrastructure.Authorization uses a type in Domain.Entities.Users.
- The types involved
Bookify.Infrastructure.Authorization.UserRolesResponse→Bookify.Domain.Entities.Users.Role
- Direction
- Infrastructure.Authorization uses Domain.Entities.Users, so a change to Domain.Entities.Users can break Infrastructure.Authorization, while a change to Infrastructure.Authorization can't break Domain.Entities.Users.
- Position
- Below the diagonal: Infrastructure.Authorization uses a module listed above it, which is the healthy direction.
26→18 Infrastructure.Authorization uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Infrastructure.Authorization uses a type in Infrastructure.
- The types involved
Bookify.Infrastructure.Authorization.AuthorizationService→Bookify.Infrastructure.ApplicationDbContext
- Direction
- Infrastructure.Authorization uses Infrastructure, so a change to Infrastructure can break Infrastructure.Authorization, while a change to Infrastructure.Authorization can't break Infrastructure.
- Position
- Below the diagonal: Infrastructure.Authorization uses a module listed above it, which is the healthy direction.
27→10 Infrastructure.Caching uses Application.Abstractions.Caching✕
- Connections
- 1 pair of types, where a type in Infrastructure.Caching uses a type in Application.Abstractions.Caching.
- The types involved
Bookify.Infrastructure.Caching.CacheService→Bookify.Application.Abstractions.Caching.ICacheService
- Direction
- Infrastructure.Caching uses Application.Abstractions.Caching, so a change to Application.Abstractions.Caching can break Infrastructure.Caching, while a change to Infrastructure.Caching can't break Application.Abstractions.Caching.
- Position
- Below the diagonal: Infrastructure.Caching uses a module listed above it, which is the healthy direction.
28→8 Infrastructure.Email uses Domain.Entities.Users.ValueObjects✕
- Connections
- 1 pair of types, where a type in Infrastructure.Email uses a type in Domain.Entities.Users.ValueObjects.
- The types involved
Bookify.Infrastructure.Email.EmailService→Bookify.Domain.Entities.Users.ValueObjects.Email
- Direction
- Infrastructure.Email uses Domain.Entities.Users.ValueObjects, so a change to Domain.Entities.Users.ValueObjects can break Infrastructure.Email, while a change to Infrastructure.Email can't break Domain.Entities.Users.ValueObjects.
- Position
- Below the diagonal: Infrastructure.Email uses a module listed above it, which is the healthy direction.
28→11 Infrastructure.Email uses Application.Abstractions.Email✕
- Connections
- 1 pair of types, where a type in Infrastructure.Email uses a type in Application.Abstractions.Email.
- The types involved
Bookify.Infrastructure.Email.EmailService→Bookify.Application.Abstractions.Email.IEmailService
- Direction
- Infrastructure.Email uses Application.Abstractions.Email, so a change to Application.Abstractions.Email can break Infrastructure.Email, while a change to Infrastructure.Email can't break Application.Abstractions.Email.
- Position
- Below the diagonal: Infrastructure.Email uses a module listed above it, which is the healthy direction.
29→2 Application.Bookings.GetBooking uses Application.Abstractions.Data✕
- Connections
- 1 pair of types, where a type in Application.Bookings.GetBooking uses a type in Application.Abstractions.Data.
- The types involved
Bookify.Application.Bookings.GetBooking.GetBookingQueryHandler→Bookify.Application.Abstractions.Data.ISqlConnectionFactory
- Direction
- Application.Bookings.GetBooking uses Application.Abstractions.Data, so a change to Application.Abstractions.Data can break Application.Bookings.GetBooking, while a change to Application.Bookings.GetBooking can't break Application.Abstractions.Data.
- Position
- Below the diagonal: Application.Bookings.GetBooking uses a module listed above it, which is the healthy direction.
29→3 Application.Bookings.GetBooking uses Application.Abstractions.Messaging✕
- Connections
- 1 pair of types, where a type in Application.Bookings.GetBooking uses a type in Application.Abstractions.Messaging.
- The types involved
Bookify.Application.Bookings.GetBooking.GetBookingQueryHandler→Bookify.Application.Abstractions.Messaging.IQueryHandler
- Direction
- Application.Bookings.GetBooking uses Application.Abstractions.Messaging, so a change to Application.Abstractions.Messaging can break Application.Bookings.GetBooking, while a change to Application.Bookings.GetBooking can't break Application.Abstractions.Messaging.
- Position
- Below the diagonal: Application.Bookings.GetBooking uses a module listed above it, which is the healthy direction.
29→4 Application.Bookings.GetBooking uses Domain.Entities.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Bookings.GetBooking uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Application.Bookings.GetBooking.GetBookingQueryHandler→Bookify.Domain.Entities.Abstractions.Result
- Direction
- Application.Bookings.GetBooking uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Application.Bookings.GetBooking, while a change to Application.Bookings.GetBooking can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Application.Bookings.GetBooking uses a module listed above it, which is the healthy direction.
29→10 Application.Bookings.GetBooking uses Application.Abstractions.Caching✕
- Connections
- 1 pair of types, where a type in Application.Bookings.GetBooking uses a type in Application.Abstractions.Caching.
- The types involved
Bookify.Application.Bookings.GetBooking.GetBookingQuery→Bookify.Application.Abstractions.Caching.ICachedQuery
- Direction
- Application.Bookings.GetBooking uses Application.Abstractions.Caching, so a change to Application.Abstractions.Caching can break Application.Bookings.GetBooking, while a change to Application.Bookings.GetBooking can't break Application.Abstractions.Caching.
- Position
- Below the diagonal: Application.Bookings.GetBooking uses a module listed above it, which is the healthy direction.
29→21 Application.Bookings.GetBooking uses Application.Abstractions.Authentication✕
- Connections
- 1 pair of types, where a type in Application.Bookings.GetBooking uses a type in Application.Abstractions.Authentication.
- The types involved
Bookify.Application.Bookings.GetBooking.GetBookingQueryHandler→Bookify.Application.Abstractions.Authentication.IUserContext
- Direction
- Application.Bookings.GetBooking uses Application.Abstractions.Authentication, so a change to Application.Abstractions.Authentication can break Application.Bookings.GetBooking, while a change to Application.Bookings.GetBooking can't break Application.Abstractions.Authentication.
- Position
- Below the diagonal: Application.Bookings.GetBooking uses a module listed above it, which is the healthy direction.
30→2 Application.Users.GetLoggedInUser uses Application.Abstractions.Data✕
- Connections
- 1 pair of types, where a type in Application.Users.GetLoggedInUser uses a type in Application.Abstractions.Data.
- The types involved
Bookify.Application.Users.GetLoggedInUser.GetLoggedInUserQueryHandler→Bookify.Application.Abstractions.Data.ISqlConnectionFactory
- Direction
- Application.Users.GetLoggedInUser uses Application.Abstractions.Data, so a change to Application.Abstractions.Data can break Application.Users.GetLoggedInUser, while a change to Application.Users.GetLoggedInUser can't break Application.Abstractions.Data.
- Position
- Below the diagonal: Application.Users.GetLoggedInUser uses a module listed above it, which is the healthy direction.
30→3 Application.Users.GetLoggedInUser uses Application.Abstractions.Messaging✕
- Connections
- 2 pairs of types, where a type in Application.Users.GetLoggedInUser uses a type in Application.Abstractions.Messaging.
- The types involved
Bookify.Application.Users.GetLoggedInUser.GetLoggedInUserQuery→Bookify.Application.Abstractions.Messaging.IQueryBookify.Application.Users.GetLoggedInUser.GetLoggedInUserQueryHandler→Bookify.Application.Abstractions.Messaging.IQueryHandler
- Direction
- Application.Users.GetLoggedInUser uses Application.Abstractions.Messaging, so a change to Application.Abstractions.Messaging can break Application.Users.GetLoggedInUser, while a change to Application.Users.GetLoggedInUser can't break Application.Abstractions.Messaging.
- Position
- Below the diagonal: Application.Users.GetLoggedInUser uses a module listed above it, which is the healthy direction.
30→4 Application.Users.GetLoggedInUser uses Domain.Entities.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Users.GetLoggedInUser uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Application.Users.GetLoggedInUser.GetLoggedInUserQueryHandler→Bookify.Domain.Entities.Abstractions.Result
- Direction
- Application.Users.GetLoggedInUser uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Application.Users.GetLoggedInUser, while a change to Application.Users.GetLoggedInUser can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Application.Users.GetLoggedInUser uses a module listed above it, which is the healthy direction.
30→21 Application.Users.GetLoggedInUser uses Application.Abstractions.Authentication✕
- Connections
- 1 pair of types, where a type in Application.Users.GetLoggedInUser uses a type in Application.Abstractions.Authentication.
- The types involved
Bookify.Application.Users.GetLoggedInUser.GetLoggedInUserQueryHandler→Bookify.Application.Abstractions.Authentication.IUserContext
- Direction
- Application.Users.GetLoggedInUser uses Application.Abstractions.Authentication, so a change to Application.Abstractions.Authentication can break Application.Users.GetLoggedInUser, while a change to Application.Users.GetLoggedInUser can't break Application.Abstractions.Authentication.
- Position
- Below the diagonal: Application.Users.GetLoggedInUser uses a module listed above it, which is the healthy direction.
31→3 Application.Users.LogInUser uses Application.Abstractions.Messaging✕
- Connections
- 2 pairs of types, where a type in Application.Users.LogInUser uses a type in Application.Abstractions.Messaging.
- The types involved
Bookify.Application.Users.LogInUser.LogInUserCommand→Bookify.Application.Abstractions.Messaging.ICommandBookify.Application.Users.LogInUser.LogInUserCommandHandler→Bookify.Application.Abstractions.Messaging.ICommandHandler
- Direction
- Application.Users.LogInUser uses Application.Abstractions.Messaging, so a change to Application.Abstractions.Messaging can break Application.Users.LogInUser, while a change to Application.Users.LogInUser can't break Application.Abstractions.Messaging.
- Position
- Below the diagonal: Application.Users.LogInUser uses a module listed above it, which is the healthy direction.
31→4 Application.Users.LogInUser uses Domain.Entities.Abstractions✕
- Connections
- 1 pair of types, where a type in Application.Users.LogInUser uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Application.Users.LogInUser.LogInUserCommandHandler→Bookify.Domain.Entities.Abstractions.Result
- Direction
- Application.Users.LogInUser uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Application.Users.LogInUser, while a change to Application.Users.LogInUser can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Application.Users.LogInUser uses a module listed above it, which is the healthy direction.
31→21 Application.Users.LogInUser uses Application.Abstractions.Authentication✕
- Connections
- 1 pair of types, where a type in Application.Users.LogInUser uses a type in Application.Abstractions.Authentication.
- The types involved
Bookify.Application.Users.LogInUser.LogInUserCommandHandler→Bookify.Application.Abstractions.Authentication.IJwtService
- Direction
- Application.Users.LogInUser uses Application.Abstractions.Authentication, so a change to Application.Abstractions.Authentication can break Application.Users.LogInUser, while a change to Application.Users.LogInUser can't break Application.Abstractions.Authentication.
- Position
- Below the diagonal: Application.Users.LogInUser uses a module listed above it, which is the healthy direction.
32→3 Application.Users.RegisterUser uses Application.Abstractions.Messaging✕
- Connections
- 2 pairs of types, where a type in Application.Users.RegisterUser uses a type in Application.Abstractions.Messaging.
- The types involved
Bookify.Application.Users.RegisterUser.RegisterUserCommand→Bookify.Application.Abstractions.Messaging.ICommandBookify.Application.Users.RegisterUser.RegisterUserCommandHandler→Bookify.Application.Abstractions.Messaging.ICommandHandler
- Direction
- Application.Users.RegisterUser uses Application.Abstractions.Messaging, so a change to Application.Abstractions.Messaging can break Application.Users.RegisterUser, while a change to Application.Users.RegisterUser can't break Application.Abstractions.Messaging.
- Position
- Below the diagonal: Application.Users.RegisterUser uses a module listed above it, which is the healthy direction.
32→4 Application.Users.RegisterUser uses Domain.Entities.Abstractions✕
- Connections
- 2 pairs of types, where a type in Application.Users.RegisterUser uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Application.Users.RegisterUser.RegisterUserCommandHandler→Bookify.Domain.Entities.Abstractions.IUnitOfWorkBookify.Application.Users.RegisterUser.RegisterUserCommandHandler→Bookify.Domain.Entities.Abstractions.Result
- Direction
- Application.Users.RegisterUser uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Application.Users.RegisterUser, while a change to Application.Users.RegisterUser can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Application.Users.RegisterUser uses a module listed above it, which is the healthy direction.
32→17 Application.Users.RegisterUser uses Domain.Entities.Users✕
- Connections
- 1 pair of types, where a type in Application.Users.RegisterUser uses a type in Domain.Entities.Users.
- The types involved
Bookify.Application.Users.RegisterUser.RegisterUserCommandHandler→Bookify.Domain.Entities.Users.IUserRepository
- Direction
- Application.Users.RegisterUser uses Domain.Entities.Users, so a change to Domain.Entities.Users can break Application.Users.RegisterUser, while a change to Application.Users.RegisterUser can't break Domain.Entities.Users.
- Position
- Below the diagonal: Application.Users.RegisterUser uses a module listed above it, which is the healthy direction.
32→21 Application.Users.RegisterUser uses Application.Abstractions.Authentication✕
- Connections
- 1 pair of types, where a type in Application.Users.RegisterUser uses a type in Application.Abstractions.Authentication.
- The types involved
Bookify.Application.Users.RegisterUser.RegisterUserCommandHandler→Bookify.Application.Abstractions.Authentication.IAuthenticationService
- Direction
- Application.Users.RegisterUser uses Application.Abstractions.Authentication, so a change to Application.Abstractions.Authentication can break Application.Users.RegisterUser, while a change to Application.Users.RegisterUser can't break Application.Abstractions.Authentication.
- Position
- Below the diagonal: Application.Users.RegisterUser uses a module listed above it, which is the healthy direction.
33→4 Domain.Entities.Bookings.Events uses Domain.Entities.Abstractions✕
- Connections
- 5 pairs of types, where a type in Domain.Entities.Bookings.Events uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Domain.Entities.Bookings.Events.BookingCancelledDomainEvent→Bookify.Domain.Entities.Abstractions.IDomainEventBookify.Domain.Entities.Bookings.Events.BookingCompletedDomainEvent→Bookify.Domain.Entities.Abstractions.IDomainEventBookify.Domain.Entities.Bookings.Events.BookingConfirmedDomainEvent→Bookify.Domain.Entities.Abstractions.IDomainEventBookify.Domain.Entities.Bookings.Events.BookingRejectedDomainEvent→Bookify.Domain.Entities.Abstractions.IDomainEventBookify.Domain.Entities.Bookings.Events.BookingReservedDomainEvent→Bookify.Domain.Entities.Abstractions.IDomainEvent
- Direction
- Domain.Entities.Bookings.Events uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Domain.Entities.Bookings.Events, while a change to Domain.Entities.Bookings.Events can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Domain.Entities.Bookings.Events uses a module listed above it, which is the healthy direction.
33→23 Domain.Entities.Bookings.Events uses Domain.Entities.Bookings✕
- Connections
- 5 pairs of types, where a type in Domain.Entities.Bookings.Events uses a type in Domain.Entities.Bookings.
- The types involved
Bookify.Domain.Entities.Bookings.Events.BookingCancelledDomainEvent→Bookify.Domain.Entities.Bookings.BookingIdBookify.Domain.Entities.Bookings.Events.BookingCompletedDomainEvent→Bookify.Domain.Entities.Bookings.BookingIdBookify.Domain.Entities.Bookings.Events.BookingConfirmedDomainEvent→Bookify.Domain.Entities.Bookings.BookingIdBookify.Domain.Entities.Bookings.Events.BookingRejectedDomainEvent→Bookify.Domain.Entities.Bookings.BookingIdBookify.Domain.Entities.Bookings.Events.BookingReservedDomainEvent→Bookify.Domain.Entities.Bookings.BookingId
- Direction
- Domain.Entities.Bookings.Events uses Domain.Entities.Bookings, so a change to Domain.Entities.Bookings can break Domain.Entities.Bookings.Events, while a change to Domain.Entities.Bookings.Events can't break Domain.Entities.Bookings.
- Position
- Below the diagonal: Domain.Entities.Bookings.Events uses a module listed above it, which is the healthy direction.
34→4 Domain.Entities.Reviews uses Domain.Entities.Abstractions✕
- Connections
- 3 pairs of types, where a type in Domain.Entities.Reviews uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Domain.Entities.Reviews.Review→Bookify.Domain.Entities.Abstractions.EntityBookify.Domain.Entities.Reviews.Review→Bookify.Domain.Entities.Abstractions.ResultBookify.Domain.Entities.Reviews.ReviewErrors→Bookify.Domain.Entities.Abstractions.Error
- Direction
- Domain.Entities.Reviews uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Domain.Entities.Reviews, while a change to Domain.Entities.Reviews can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Domain.Entities.Reviews uses a module listed above it, which is the healthy direction.
34→14 Domain.Entities.Reviews uses Domain.Entities.Apartments✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Reviews uses a type in Domain.Entities.Apartments.
- The types involved
Bookify.Domain.Entities.Reviews.Review→Bookify.Domain.Entities.Apartments.ApartmentId
- Direction
- Domain.Entities.Reviews uses Domain.Entities.Apartments, so a change to Domain.Entities.Apartments can break Domain.Entities.Reviews, while a change to Domain.Entities.Reviews can't break Domain.Entities.Apartments.
- Position
- Below the diagonal: Domain.Entities.Reviews uses a module listed above it, which is the healthy direction.
34→16 Domain.Entities.Reviews uses Domain.Entities.Reviews.ValueObjects✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Reviews uses a type in Domain.Entities.Reviews.ValueObjects.
- The types involved
Bookify.Domain.Entities.Reviews.Review→Bookify.Domain.Entities.Reviews.ValueObjects.Rating
- Direction
- Domain.Entities.Reviews uses Domain.Entities.Reviews.ValueObjects, so a change to Domain.Entities.Reviews.ValueObjects can break Domain.Entities.Reviews, while a change to Domain.Entities.Reviews can't break Domain.Entities.Reviews.ValueObjects.
- Position
- Below the diagonal: Domain.Entities.Reviews uses a module listed above it, which is the healthy direction.
34→17 Domain.Entities.Reviews uses Domain.Entities.Users✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Reviews uses a type in Domain.Entities.Users.
- The types involved
Bookify.Domain.Entities.Reviews.Review→Bookify.Domain.Entities.Users.UserId
- Direction
- Domain.Entities.Reviews uses Domain.Entities.Users, so a change to Domain.Entities.Users can break Domain.Entities.Reviews, while a change to Domain.Entities.Reviews can't break Domain.Entities.Users.
- Position
- Below the diagonal: Domain.Entities.Reviews uses a module listed above it, which is the healthy direction.
34→23 Domain.Entities.Reviews uses Domain.Entities.Bookings✕
- Connections
- 2 pairs of types, where a type in Domain.Entities.Reviews uses a type in Domain.Entities.Bookings.
- The types involved
Bookify.Domain.Entities.Reviews.Review→Bookify.Domain.Entities.Bookings.BookingBookify.Domain.Entities.Reviews.Review→Bookify.Domain.Entities.Bookings.BookingId
- Direction
- Domain.Entities.Reviews uses Domain.Entities.Bookings, so a change to Domain.Entities.Bookings can break Domain.Entities.Reviews, while a change to Domain.Entities.Reviews can't break Domain.Entities.Bookings.
- Position
- Below the diagonal: Domain.Entities.Reviews uses a module listed above it, which is the healthy direction.
35→4 Infrastructure.Authentication uses Domain.Entities.Abstractions✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Authentication uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Infrastructure.Authentication.JwtService→Bookify.Domain.Entities.Abstractions.ErrorBookify.Infrastructure.Authentication.JwtService→Bookify.Domain.Entities.Abstractions.Result
- Direction
- Infrastructure.Authentication uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Infrastructure.Authentication, while a change to Infrastructure.Authentication can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Infrastructure.Authentication uses a module listed above it, which is the healthy direction.
35→17 Infrastructure.Authentication uses Domain.Entities.Users✕
- Connections
- 1 pair of types, where a type in Infrastructure.Authentication uses a type in Domain.Entities.Users.
- The types involved
Bookify.Infrastructure.Authentication.AuthenticationService→Bookify.Domain.Entities.Users.User
- Direction
- Infrastructure.Authentication uses Domain.Entities.Users, so a change to Domain.Entities.Users can break Infrastructure.Authentication, while a change to Infrastructure.Authentication can't break Domain.Entities.Users.
- Position
- Below the diagonal: Infrastructure.Authentication uses a module listed above it, which is the healthy direction.
35→21 Infrastructure.Authentication uses Application.Abstractions.Authentication✕
- Connections
- 3 pairs of types, where a type in Infrastructure.Authentication uses a type in Application.Abstractions.Authentication.
- The types involved
Bookify.Infrastructure.Authentication.AuthenticationService→Bookify.Application.Abstractions.Authentication.IAuthenticationServiceBookify.Infrastructure.Authentication.JwtService→Bookify.Application.Abstractions.Authentication.IJwtServiceBookify.Infrastructure.Authentication.UserContext→Bookify.Application.Abstractions.Authentication.IUserContext
- Direction
- Infrastructure.Authentication uses Application.Abstractions.Authentication, so a change to Application.Abstractions.Authentication can break Infrastructure.Authentication, while a change to Infrastructure.Authentication can't break Application.Abstractions.Authentication.
- Position
- Below the diagonal: Infrastructure.Authentication uses a module listed above it, which is the healthy direction.
35→25 Infrastructure.Authentication uses Infrastructure.Authentication.Models✕
- Connections
- 1 pair of types, where a type in Infrastructure.Authentication uses a type in Infrastructure.Authentication.Models.
- The types involved
Bookify.Infrastructure.Authentication.AdminAuthorizationDelegatingHandler→Bookify.Infrastructure.Authentication.Models.AuthorizationToken
- Direction
- Infrastructure.Authentication uses Infrastructure.Authentication.Models, so a change to Infrastructure.Authentication.Models can break Infrastructure.Authentication, while a change to Infrastructure.Authentication can't break Infrastructure.Authentication.Models.
- Position
- Below the diagonal: Infrastructure.Authentication uses a module listed above it, which is the healthy direction.
36→7 Infrastructure.Repositories uses Domain.Entities.Bookings.Enums✕
- Connections
- 1 pair of types, where a type in Infrastructure.Repositories uses a type in Domain.Entities.Bookings.Enums.
- The types involved
Bookify.Infrastructure.Repositories.BookingRepository→Bookify.Domain.Entities.Bookings.Enums.BookingStatus
- Direction
- Infrastructure.Repositories uses Domain.Entities.Bookings.Enums, so a change to Domain.Entities.Bookings.Enums can break Infrastructure.Repositories, while a change to Infrastructure.Repositories can't break Domain.Entities.Bookings.Enums.
- Position
- Below the diagonal: Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
36→14 Infrastructure.Repositories uses Domain.Entities.Apartments✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Repositories uses a type in Domain.Entities.Apartments.
- The types involved
Bookify.Infrastructure.Repositories.ApartmentRepository→Bookify.Domain.Entities.Apartments.IApartmentRepositoryBookify.Infrastructure.Repositories.BookingRepository→Bookify.Domain.Entities.Apartments.Apartment
- Direction
- Infrastructure.Repositories uses Domain.Entities.Apartments, so a change to Domain.Entities.Apartments can break Infrastructure.Repositories, while a change to Infrastructure.Repositories can't break Domain.Entities.Apartments.
- Position
- Below the diagonal: Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
36→15 Infrastructure.Repositories uses Domain.Entities.Bookings.ValueObjects✕
- Connections
- 1 pair of types, where a type in Infrastructure.Repositories uses a type in Domain.Entities.Bookings.ValueObjects.
- The types involved
Bookify.Infrastructure.Repositories.BookingRepository→Bookify.Domain.Entities.Bookings.ValueObjects.DateRange
- Direction
- Infrastructure.Repositories uses Domain.Entities.Bookings.ValueObjects, so a change to Domain.Entities.Bookings.ValueObjects can break Infrastructure.Repositories, while a change to Infrastructure.Repositories can't break Domain.Entities.Bookings.ValueObjects.
- Position
- Below the diagonal: Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
36→17 Infrastructure.Repositories uses Domain.Entities.Users✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Repositories uses a type in Domain.Entities.Users.
- The types involved
Bookify.Infrastructure.Repositories.UserRepository→Bookify.Domain.Entities.Users.IUserRepositoryBookify.Infrastructure.Repositories.UserRepository→Bookify.Domain.Entities.Users.User
- Direction
- Infrastructure.Repositories uses Domain.Entities.Users, so a change to Domain.Entities.Users can break Infrastructure.Repositories, while a change to Infrastructure.Repositories can't break Domain.Entities.Users.
- Position
- Below the diagonal: Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
36→18 Infrastructure.Repositories uses Infrastructure✕
- Connections
- 4 pairs of types, where a type in Infrastructure.Repositories uses a type in Infrastructure.
- The types involved
Bookify.Infrastructure.Repositories.ApartmentRepository→Bookify.Infrastructure.ApplicationDbContextBookify.Infrastructure.Repositories.BookingRepository→Bookify.Infrastructure.ApplicationDbContextBookify.Infrastructure.Repositories.Repository→Bookify.Infrastructure.ApplicationDbContextBookify.Infrastructure.Repositories.UserRepository→Bookify.Infrastructure.ApplicationDbContext
- Direction
- Infrastructure.Repositories uses Infrastructure, so a change to Infrastructure can break Infrastructure.Repositories, while a change to Infrastructure.Repositories can't break Infrastructure.
- Position
- Below the diagonal: Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
36→23 Infrastructure.Repositories uses Domain.Entities.Bookings✕
- Connections
- 1 pair of types, where a type in Infrastructure.Repositories uses a type in Domain.Entities.Bookings.
- The types involved
Bookify.Infrastructure.Repositories.BookingRepository→Bookify.Domain.Entities.Bookings.IBookingRepository
- Direction
- Infrastructure.Repositories uses Domain.Entities.Bookings, so a change to Domain.Entities.Bookings can break Infrastructure.Repositories, while a change to Infrastructure.Repositories can't break Domain.Entities.Bookings.
- Position
- Below the diagonal: Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
37→4 API.Controllers.Bookings uses Domain.Entities.Abstractions✕
- Connections
- 1 pair of types, where a type in API.Controllers.Bookings uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.API.Controllers.Bookings.BookingsEndpoints→Bookify.Domain.Entities.Abstractions.Error
- Direction
- API.Controllers.Bookings uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break API.Controllers.Bookings, while a change to API.Controllers.Bookings can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: API.Controllers.Bookings uses a module listed above it, which is the healthy direction.
37→29 API.Controllers.Bookings uses Application.Bookings.GetBooking✕
- Connections
- 1 pair of types, where a type in API.Controllers.Bookings uses a type in Application.Bookings.GetBooking.
- The types involved
Bookify.API.Controllers.Bookings.BookingsEndpoints→Bookify.Application.Bookings.GetBooking.BookingResponse
- Direction
- API.Controllers.Bookings uses Application.Bookings.GetBooking, so a change to Application.Bookings.GetBooking can break API.Controllers.Bookings, while a change to API.Controllers.Bookings can't break Application.Bookings.GetBooking.
- Position
- Below the diagonal: API.Controllers.Bookings uses a module listed above it, which is the healthy direction.
38→1 Application.Bookings.ReserveBooking uses Application.Abstractions.Clock✕
- Connections
- 1 pair of types, where a type in Application.Bookings.ReserveBooking uses a type in Application.Abstractions.Clock.
- The types involved
Bookify.Application.Bookings.ReserveBooking.ReserveBookingCommandHandler→Bookify.Application.Abstractions.Clock.IDateTimeProvider
- Direction
- Application.Bookings.ReserveBooking uses Application.Abstractions.Clock, so a change to Application.Abstractions.Clock can break Application.Bookings.ReserveBooking, while a change to Application.Bookings.ReserveBooking can't break Application.Abstractions.Clock.
- Position
- Below the diagonal: Application.Bookings.ReserveBooking uses a module listed above it, which is the healthy direction.
38→3 Application.Bookings.ReserveBooking uses Application.Abstractions.Messaging✕
- Connections
- 2 pairs of types, where a type in Application.Bookings.ReserveBooking uses a type in Application.Abstractions.Messaging.
- The types involved
Bookify.Application.Bookings.ReserveBooking.ReserveBookingCommand→Bookify.Application.Abstractions.Messaging.ICommandBookify.Application.Bookings.ReserveBooking.ReserveBookingCommandHandler→Bookify.Application.Abstractions.Messaging.ICommandHandler
- Direction
- Application.Bookings.ReserveBooking uses Application.Abstractions.Messaging, so a change to Application.Abstractions.Messaging can break Application.Bookings.ReserveBooking, while a change to Application.Bookings.ReserveBooking can't break Application.Abstractions.Messaging.
- Position
- Below the diagonal: Application.Bookings.ReserveBooking uses a module listed above it, which is the healthy direction.
38→4 Application.Bookings.ReserveBooking uses Domain.Entities.Abstractions✕
- Connections
- 2 pairs of types, where a type in Application.Bookings.ReserveBooking uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Application.Bookings.ReserveBooking.ReserveBookingCommandHandler→Bookify.Domain.Entities.Abstractions.IUnitOfWorkBookify.Application.Bookings.ReserveBooking.ReserveBookingCommandHandler→Bookify.Domain.Entities.Abstractions.Result
- Direction
- Application.Bookings.ReserveBooking uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Application.Bookings.ReserveBooking, while a change to Application.Bookings.ReserveBooking can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Application.Bookings.ReserveBooking uses a module listed above it, which is the healthy direction.
38→11 Application.Bookings.ReserveBooking uses Application.Abstractions.Email✕
- Connections
- 1 pair of types, where a type in Application.Bookings.ReserveBooking uses a type in Application.Abstractions.Email.
- The types involved
Bookify.Application.Bookings.ReserveBooking.BookingReservedDomainEventHandler→Bookify.Application.Abstractions.Email.IEmailService
- Direction
- Application.Bookings.ReserveBooking uses Application.Abstractions.Email, so a change to Application.Abstractions.Email can break Application.Bookings.ReserveBooking, while a change to Application.Bookings.ReserveBooking can't break Application.Abstractions.Email.
- Position
- Below the diagonal: Application.Bookings.ReserveBooking uses a module listed above it, which is the healthy direction.
38→14 Application.Bookings.ReserveBooking uses Domain.Entities.Apartments✕
- Connections
- 1 pair of types, where a type in Application.Bookings.ReserveBooking uses a type in Domain.Entities.Apartments.
- The types involved
Bookify.Application.Bookings.ReserveBooking.ReserveBookingCommandHandler→Bookify.Domain.Entities.Apartments.IApartmentRepository
- Direction
- Application.Bookings.ReserveBooking uses Domain.Entities.Apartments, so a change to Domain.Entities.Apartments can break Application.Bookings.ReserveBooking, while a change to Application.Bookings.ReserveBooking can't break Domain.Entities.Apartments.
- Position
- Below the diagonal: Application.Bookings.ReserveBooking uses a module listed above it, which is the healthy direction.
38→17 Application.Bookings.ReserveBooking uses Domain.Entities.Users✕
- Connections
- 2 pairs of types, where a type in Application.Bookings.ReserveBooking uses a type in Domain.Entities.Users.
- The types involved
Bookify.Application.Bookings.ReserveBooking.BookingReservedDomainEventHandler→Bookify.Domain.Entities.Users.IUserRepositoryBookify.Application.Bookings.ReserveBooking.ReserveBookingCommandHandler→Bookify.Domain.Entities.Users.IUserRepository
- Direction
- Application.Bookings.ReserveBooking uses Domain.Entities.Users, so a change to Domain.Entities.Users can break Application.Bookings.ReserveBooking, while a change to Application.Bookings.ReserveBooking can't break Domain.Entities.Users.
- Position
- Below the diagonal: Application.Bookings.ReserveBooking uses a module listed above it, which is the healthy direction.
38→23 Application.Bookings.ReserveBooking uses Domain.Entities.Bookings✕
- Connections
- 3 pairs of types, where a type in Application.Bookings.ReserveBooking uses a type in Domain.Entities.Bookings.
- The types involved
Bookify.Application.Bookings.ReserveBooking.BookingReservedDomainEventHandler→Bookify.Domain.Entities.Bookings.IBookingRepositoryBookify.Application.Bookings.ReserveBooking.ReserveBookingCommandHandler→Bookify.Domain.Entities.Bookings.IBookingRepositoryBookify.Application.Bookings.ReserveBooking.ReserveBookingCommandHandler→Bookify.Domain.Entities.Bookings.PricingService
- Direction
- Application.Bookings.ReserveBooking uses Domain.Entities.Bookings, so a change to Domain.Entities.Bookings can break Application.Bookings.ReserveBooking, while a change to Application.Bookings.ReserveBooking can't break Domain.Entities.Bookings.
- Position
- Below the diagonal: Application.Bookings.ReserveBooking uses a module listed above it, which is the healthy direction.
38→33 Application.Bookings.ReserveBooking uses Domain.Entities.Bookings.Events✕
- Connections
- 1 pair of types, where a type in Application.Bookings.ReserveBooking uses a type in Domain.Entities.Bookings.Events.
- The types involved
Bookify.Application.Bookings.ReserveBooking.BookingReservedDomainEventHandler→Bookify.Domain.Entities.Bookings.Events.BookingReservedDomainEvent
- Direction
- Application.Bookings.ReserveBooking uses Domain.Entities.Bookings.Events, so a change to Domain.Entities.Bookings.Events can break Application.Bookings.ReserveBooking, while a change to Application.Bookings.ReserveBooking can't break Domain.Entities.Bookings.Events.
- Position
- Below the diagonal: Application.Bookings.ReserveBooking uses a module listed above it, which is the healthy direction.
39→4 Domain.Entities.Reviews.Events uses Domain.Entities.Abstractions✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Reviews.Events uses a type in Domain.Entities.Abstractions.
- The types involved
Bookify.Domain.Entities.Reviews.Events.ReviewCreatedDomainEvent→Bookify.Domain.Entities.Abstractions.IDomainEvent
- Direction
- Domain.Entities.Reviews.Events uses Domain.Entities.Abstractions, so a change to Domain.Entities.Abstractions can break Domain.Entities.Reviews.Events, while a change to Domain.Entities.Reviews.Events can't break Domain.Entities.Abstractions.
- Position
- Below the diagonal: Domain.Entities.Reviews.Events uses a module listed above it, which is the healthy direction.
39→34 Domain.Entities.Reviews.Events uses Domain.Entities.Reviews✕
- Connections
- 1 pair of types, where a type in Domain.Entities.Reviews.Events uses a type in Domain.Entities.Reviews.
- The types involved
Bookify.Domain.Entities.Reviews.Events.ReviewCreatedDomainEvent→Bookify.Domain.Entities.Reviews.ReviewId
- Direction
- Domain.Entities.Reviews.Events uses Domain.Entities.Reviews, so a change to Domain.Entities.Reviews can break Domain.Entities.Reviews.Events, while a change to Domain.Entities.Reviews.Events can't break Domain.Entities.Reviews.
- Position
- Below the diagonal: Domain.Entities.Reviews.Events uses a module listed above it, which is the healthy direction.
40→14 Infrastructure.Configurations uses Domain.Entities.Apartments✕
- Connections
- 1 pair of types, where a type in Infrastructure.Configurations uses a type in Domain.Entities.Apartments.
- The types involved
Bookify.Infrastructure.Configurations.ApartmentConfiguration→Bookify.Domain.Entities.Apartments.Apartment
- Direction
- Infrastructure.Configurations uses Domain.Entities.Apartments, so a change to Domain.Entities.Apartments can break Infrastructure.Configurations, while a change to Infrastructure.Configurations can't break Domain.Entities.Apartments.
- Position
- Below the diagonal: Infrastructure.Configurations uses a module listed above it, which is the healthy direction.
40→17 Infrastructure.Configurations uses Domain.Entities.Users✕
- Connections
- 4 pairs of types, where a type in Infrastructure.Configurations uses a type in Domain.Entities.Users.
- The types involved
Bookify.Infrastructure.Configurations.PermissionConfiguration→Bookify.Domain.Entities.Users.PermissionBookify.Infrastructure.Configurations.RoleConfiguration→Bookify.Domain.Entities.Users.RoleBookify.Infrastructure.Configurations.RolePermissionConfiguration→Bookify.Domain.Entities.Users.RolePermissionBookify.Infrastructure.Configurations.UserConfiguration→Bookify.Domain.Entities.Users.User
- Direction
- Infrastructure.Configurations uses Domain.Entities.Users, so a change to Domain.Entities.Users can break Infrastructure.Configurations, while a change to Infrastructure.Configurations can't break Domain.Entities.Users.
- Position
- Below the diagonal: Infrastructure.Configurations uses a module listed above it, which is the healthy direction.
40→20 Infrastructure.Configurations uses Infrastructure.Outbox✕
- Connections
- 1 pair of types, where a type in Infrastructure.Configurations uses a type in Infrastructure.Outbox.
- The types involved
Bookify.Infrastructure.Configurations.OutboxMessageConfiguration→Bookify.Infrastructure.Outbox.OutboxMessage
- Direction
- Infrastructure.Configurations uses Infrastructure.Outbox, so a change to Infrastructure.Outbox can break Infrastructure.Configurations, while a change to Infrastructure.Configurations can't break Infrastructure.Outbox.
- Position
- Below the diagonal: Infrastructure.Configurations uses a module listed above it, which is the healthy direction.
40→23 Infrastructure.Configurations uses Domain.Entities.Bookings✕
- Connections
- 1 pair of types, where a type in Infrastructure.Configurations uses a type in Domain.Entities.Bookings.
- The types involved
Bookify.Infrastructure.Configurations.BookingConfiguration→Bookify.Domain.Entities.Bookings.Booking
- Direction
- Infrastructure.Configurations uses Domain.Entities.Bookings, so a change to Domain.Entities.Bookings can break Infrastructure.Configurations, while a change to Infrastructure.Configurations can't break Domain.Entities.Bookings.
- Position
- Below the diagonal: Infrastructure.Configurations uses a module listed above it, which is the healthy direction.
40→34 Infrastructure.Configurations uses Domain.Entities.Reviews✕
- Connections
- 1 pair of types, where a type in Infrastructure.Configurations uses a type in Domain.Entities.Reviews.
- The types involved
Bookify.Infrastructure.Configurations.ReviewConfiguration→Bookify.Domain.Entities.Reviews.Review
- Direction
- Infrastructure.Configurations uses Domain.Entities.Reviews, so a change to Domain.Entities.Reviews can break Infrastructure.Configurations, while a change to Infrastructure.Configurations can't break Domain.Entities.Reviews.
- Position
- Below the diagonal: Infrastructure.Configurations 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 — Event-Driven
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 16 | High / Critical |
| A05:2025 — Injection | 8 | High / Critical |
| A02:2025 — Security Misconfiguration | 8 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 3 | High / Critical |
Roadmap
Top priorities: Resolve the 10 Leaked secret finding(s) in Secret Scanning — start with REDACTED (5), REDACTED (4), REDACTED; Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 6 Orphaned file finding(s) in Knowledge Freshness — start with DependencyInjection.cs, Booking.cs, REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +7.5 pts | Low | ADR Quality |
| Resolve the 6 Orphaned file finding(s) in Knowledge Freshness — start with DependencyInjection.cs, Booking.cs, REDACTED. | +7.2 pts | Low | Knowledge Freshness |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +5.4 pts | Low | Documentation Quality |
| Resolve the 10 Leaked secret finding(s) in Secret Scanning — start with REDACTED (5), REDACTED (4), REDACTED. | +9.0 pts | Medium | Secret Scanning |
| 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. | +6.1 pts | Medium | Architecture documentation |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +4.7 pts | Medium | Security & performance tooling |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +1.8 pts | Low | Knowledge Freshness |
| Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down. | +2.6 pts | Medium | Outbound HTTP resilience |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 0.6 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 2.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 2.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/Bookify.Infrastructure/Authorization/PermissionAuthorizationHandler.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/Bookify.Infrastructure/Configurations/ApartmentConfiguration.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (13–14 lines × 2) |
| src/Bookify.Domain/Bookify.Domain.csproj | 8.5 | Near-clean | Coupling: Off the main sequence: Bookify.Domain |
| README.md | 9.5 | Near-clean | Documentation Quality: Documentation: no build, run or usage example |
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 92 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 92 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, 65 of 82 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
- D11 Test Reliability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability is scored on the 1 tier(s) that produced comparable repeat runs; 1 tier(s) did not, and are excluded from the measurement rather than counted (unit: measured (0 flaky); integration: not included — too large to re-run within its budget). This is OUR limitation, not a defect in the repository.
- D12 Dependency Hygiene — 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- 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-contributor repository — bus factor is not applicable (1 contributor(s) across 90 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'docker-compose.dcproj' because the file extension '.dcproj' is not associated with a language.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/Bookify.API/Program.cs`, `src/Bookify.Application/Abstractions/Caching/ICachedQuery.cs` 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.
- D39 IL Efficiency — 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. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged here.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (docker-compose.override.yml). compose up failed (exit 15 — the compose project is invalid) — time="2026-11-08T02:19:41Z" level=warning msg="The \"APPDATA\" variable is not set. Defaulting to a blank string." time="2026-11-08T02:19:41Z" level=warning msg="The \"APPDATA\" variable is not set. Defaulting to a blank string." service "bookify.api" has neither an image nor a build context specified: invalid compose project; runtime evidence skipped.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- 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.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- 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".
- 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
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
1 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (13–14 lines × 2) finding(s) in Code Duplication — start with ApartmentConfiguration.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
9 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling — start with Bookify.Domain.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 11 classes have LCOM4 above 3.
D9 · Test Distribution
24 test methods: 18 unit, 6 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 1 mock references across 24 tests.
D11 · Test Reliability
Only 1 of 2 test tiers measured — the score covers those alone. 0 flaky across 1 measured tier(s). unit: measured (0 flaky); integration: not included — too large to re-run within its budget.
D13 · Secret Scanning
6 secret(s) detected.
What to do
- Resolve the 10 Leaked secret finding(s) in Secret Scanning — start with REDACTED (5), REDACTED (4), REDACTED. — One of this dimension's main actionable groups (10 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 274 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 37 direct `PackageReference`(s), and 213 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
1 deducted debt markers + unmeasured dead symbols across 2787 LoC in the .NET projects (0.0/KLoC) → score 10.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with PermissionAuthorizationHandler.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
9 projects, 163 source files, 3532 hand-written lines of code (2787 production / 745 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 3624 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 12 inter-project edges.
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 1 document(s) read across 5 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 9 projects flagged as possibly oversized/incoherent.
D27 · Navigability
99 % of calls cross a namespace and 2 % go through an interface, but 100 % 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)
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 5 High secret finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
8 finding(s): 0 critical, 4 high, 4 medium, 0 low. 2 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 2 file(s) — `src/Bookify.API/Program.cs` (line 72), `src/Bookify.Application/Abstractions/Caching/ICachedQuery.cs` (lines 5–7) — 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 2 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 (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 3 high, 0 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
D31 · IaC & Container Security
8 finding(s): 0 critical, 5 high, 2 medium, 1 low.
What to do
- Resolve the 5 High IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
6 of 6 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Bookify.Infrastructure/DependencyInjection.cs. Counted over 6 of the 138 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 6 Orphaned file finding(s) in Knowledge Freshness — start with DependencyInjection.cs, Booking.cs, REDACTED. — One of this dimension's main actionable groups (6 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 9 platform declaration(s) and 0 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
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
C1 · Data Protection
- No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
- Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
C2 · Access Controls
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `Apartment`'s public constructor takes `name`, `description` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Apartment` 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/Bookify.Domain/Entities/Apartments/Apartment.cs:9
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
DM2 · Strongly-typed ids
- `User.IdentityId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/Bookify.Domain/Entities/Users/User.cs:21
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model
- `Apartment` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Bookify.Domain/Entities/Apartments/Apartment.cs:7
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
- `Apartment` exposes its own state through a mutable collection (Amenities) — a caller can add to or remove from it directly, without passing through the methods that enforce the invariants. — src/Bookify.Domain/Entities/Apartments/Apartment.cs:7
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
DM9 · Scattered domain decisions
ED1 · Handler temporal coupling
ED2 · Event/command shape
ED3 · Event naming
ED4 · Outbox / dual-write
ED5 · Idempotency
- `RegisterUser.RegisterUserCommandHandler.Handle` mutates persistent state (a database save) and inserts a new `User` with a fresh id (`UserId.New()` → `Guid.NewGuid()`) (line 35), so a re-run inserts another one. A retry or at-least-once redelivery runs it again — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/Bookify.Application/Users/RegisterUser/RegisterUserCommandHandler.cs:21
What to do
- Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×5) — src/Bookify.API/Program.cs:45, src/Bookify.API/Program.cs:62, REDACTED:24, …
What to do
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 4 of 4 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
What to do
- Add OpenTelemetry tracing/metrics (ActivitySource / AddMetrics) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1017 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:9
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:14
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
- `services.AddHttpClient<IAuthenticationService, AuthenticationService>((servic...` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — src/Bookify.Infrastructure/DependencyInjection.cs:90
- `services.AddHttpClient<IJwtService, JwtService>((serviceProvider, httpclient)...` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — src/Bookify.Infrastructure/DependencyInjection.cs:97
What to do
- Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
P8 · Schema migrations
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. — src/Bookify.API/Program.cs:9
What to do
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 27/30 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. (×2) — src/Bookify.Infrastructure/Authorization/AuthorizationService.cs:17, src/Bookify.Infrastructure/Authorization/AuthorizationService.cs:40
- 1 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
- Its signature is fixed by the framework, and the token it carries (`context.RequestAborted`) reaches none of the calls here that take one — so an aborted request or a stopping host still waits for that work. Pass `context.RequestAborted` to them. — src/Bookify.API/Middleware/ExceptionHandlingMiddleware.cs:19
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
X5 · Nullable reference types
- 0/4 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 76% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 84% | Strong | Solid. |
| Maturity | 43% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 39% | Weak — gated by D13, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 61% | Adequate — gated by C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 90% | Strong | Solid. |
| Event-Driven | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- P12 CI test-gate honesty — 2 observation(s) recorded · 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'.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) 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.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 36 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 15 — the compose project is invalid) — time="2026-11-08T02:19:41Z" level=warning msg="The \"APPDATA\" variable is not set. Defaulting to a blank string." time="2026-11-08T02:19:41Z" level=warning msg="The \"APPDATA\" variable is not set. Defaulting to a blank string." service "bookify.api" has neither an image nor a build context specified: invalid compose project; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (756 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (2,787 production LoC in the .NET projects) — bounded contexts are not needed at this size 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 (Bookify.Domain), 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 — Too few judgeable comments (15 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the target did not build
- 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 dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
- 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)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 23 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test project never run by CI REDACTED:1
- Test project never run by CI test/Bookify.Application.IntegrationTests/Bookify.Application.IntegrationTests.csproj:1
- Outbound HTTP without resilience src/Bookify.Infrastructure/DependencyInjection.cs:90
- Outbound HTTP without resilience src/Bookify.Infrastructure/DependencyInjection.cs:97
- Async method without CancellationToken: GetRolesForUserAsync src/Bookify.Infrastructure/Authorization/AuthorizationService.cs:17
- Async method without CancellationToken: GetPermissionsForUserAsync src/Bookify.Infrastructure/Authorization/AuthorizationService.cs:40
- No data-protection/encryption
- TodoComment src/Bookify.Infrastructure/Authorization/PermissionAuthorizationHandler.cs:23
- REDACTED
- Duplicated block (13–14 lines × 2) src/Bookify.Infrastructure/Configurations/ApartmentConfiguration.cs:26
- Off the main sequence: Bookify.Domain src/Bookify.Domain/Bookify.Domain.csproj:1
- Coverage not measured — test suite did not build
- Constructible in an invalid state: Apartment src/Bookify.Domain/Entities/Apartments/Apartment.cs:9
- Anemic entity: Apartment src/Bookify.Domain/Entities/Apartments/Apartment.cs:7
- Non-idempotent mutation: RegisterUser.RegisterUserCommandHandler.Handle src/Bookify.Application/Users/RegisterUser/RegisterUserCommandHandler.cs:21
- NuGet dependencies are not locked
- Async method drops its ambient CancellationToken: InvokeAsync src/Bookify.API/Middleware/ExceptionHandlingMiddleware.cs:19
Minor — 31 finding(s)
- Orphaned file src/Bookify.Infrastructure/DependencyInjection.cs:1
- Orphaned file src/Bookify.Domain/Entities/Bookings/Booking.cs:1
- Orphaned file REDACTED:1
- Orphaned file REDACTED:1
- Orphaned file src/Bookify.Application/Bookings/ReserveBooking/ReserveBookingCommandHandler.cs:1
- Orphaned file src/Bookify.Application/Apartments/SearchApartments/SearchApartmentQueryHandler.cs:1
- Commented-out code src/Bookify.API/Program.cs:45
- Commented-out code src/Bookify.API/Program.cs:62
- Commented-out code REDACTED:24
- Commented-out code REDACTED:66
- Commented-out code REDACTED:68
- No security response headers detected
- No security response headers detected src/Bookify.API/Program.cs:9
- Partial data-retention evidence
- Documentation: no build, run or usage example README.md:1
- No ADRs found
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- Primitive id on a domain type: User.IdentityId src/Bookify.Domain/Entities/Users/User.cs:21
- Mutable entity: Apartment src/Bookify.Domain/Entities/Apartments/Apartment.cs:7
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:9
- No dependency-update automation REDACTED:14
- No rollback/health safety
- No changelog
- Not all async methods take a CancellationToken
- Some async methods drop the CancellationToken they accept
- Nullable reference types not enabled everywhere
Minor — 1 finding(s)
- Mock framework: NSubstitute
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e4f7221b93714a83a49ffc81068d444d/history.json --exit-code 0 --source . | 4 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e4f7221b93714a83a49ffc81068d444d/tree.json --exit-code 0 --source . | 4 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/Bookify.Infrastructure/Migrations . | 8 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Bookify.sln package --vulnerable --include-transitive --format json | 3 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 8 | 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 2 file(s) — `src/Bookify.API/Program.cs`, `src/Bookify.Application/Abstractions/Caching/ICachedQuery.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-0f186452fdd94a2f83197ef042f57e89 | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Name — 10 field(s)
- RegisterUserRequest.FirstName src/Bookify.API/Controllers/Users/RegisterUserRequest.cs:5
- RegisterUserRequest.LastName src/Bookify.API/Controllers/Users/RegisterUserRequest.cs:6
- UserResponse.FirstName src/Bookify.Application/Users/GetLoggedInUser/UserResponse.cs:6
- UserResponse.LastName src/Bookify.Application/Users/GetLoggedInUser/UserResponse.cs:7
- RegisterUserCommand.FirstName src/Bookify.Application/Users/RegisterUser/RegisterUserCommand.cs:6
- RegisterUserCommand.LastName src/Bookify.Application/Users/RegisterUser/RegisterUserCommand.cs:7
- User.FirstName src/Bookify.Domain/Entities/Users/User.cs:22
- User.LastName src/Bookify.Domain/Entities/Users/User.cs:23
- UserRepresentationModel.FirstName src/Bookify.Infrastructure/Authentication/Models/UserRepresentationModel.cs:22
- UserRepresentationModel.LastName src/Bookify.Infrastructure/Authentication/Models/UserRepresentationModel.cs:23
Email — 7 field(s)
- LogInUserRequest.Email src/Bookify.API/Controllers/Users/LogInUserRequest.cs:3
- RegisterUserRequest.Email src/Bookify.API/Controllers/Users/RegisterUserRequest.cs:4
- UserResponse.Email src/Bookify.Application/Users/GetLoggedInUser/UserResponse.cs:5
- LogInUserCommand.Email src/Bookify.Application/Users/LogInUser/LogInUserCommand.cs:4
- RegisterUserCommand.Email src/Bookify.Application/Users/RegisterUser/RegisterUserCommand.cs:5
- User.Email src/Bookify.Domain/Entities/Users/User.cs:24
- UserRepresentationModel.Email src/Bookify.Infrastructure/Authentication/Models/UserRepresentationModel.cs:16
Address — 2 field(s)
- AddressResponse.ZipCode src/Bookify.Application/Apartments/SearchApartments/AddressResponse.cs:6
- Address.ZipCode src/Bookify.Domain/Entities/Apartments/ValueObjects/Address.cs:6