Executive summary
meysamhadeli/booking-microservices-expressjs falls short of our standard for production because it has pieces of business logic tied to the database or web code. It scores 27 out of 100 and is rated Weak, and 35 of its 49 critical findings are security problems.
Domain Modelling, at 10, is the weakest lens and counts most in the score. The best first step for the work it takes is replacing the four exposed passwords or keys and switching the old ones off, worth about 9 points. Moving database and web code out of the business core would lift Domain Modelling itself, worth about 15 points. Raising Domain Modelling to 70 would lift the score to about 42.
Twenty-three settings leave the servers or containers unsafe. Four passwords or keys in the code and four in the code's history are open to anyone who can read the repository, and three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Correcting the unsafe settings, replacing each exposed password or key and pinning each tool to an exact version would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed. Adding the tests the test command is meant to run would take care of the three test commands with no tests behind them.
The product code is 6,747 lines, about €7,300 to rebuild.
If Domain Modelling rose from 10 to 70, the lowest score rated Strong, the score would rise from 27 to about 42.
New since the last survey: 2 findings
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
Fixed since the last survey: 44 findings
- Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) src/identity/src/data/repositories/auth.repository.ts
- Test Coverage · No test reaches this file src/building-blocks/logging/morgan.ts
- Test Coverage · No test reaches this file src/building-blocks/swagger/swagger.ts
- Test Coverage · No test reaches this file src/identity/src/data/migrations/1702550291057-create-user-table.ts
- Test Coverage · No test reaches this file src/passenger/src/extensions/rabbitmq.extensions.ts
- Test Coverage · No test reaches this file src/passenger/src/user/consumers/create-user.ts
- Test Coverage · No test reaches this file src/flight/src/data/db.context.ts
- Test Coverage · No test reaches this file src/flight/src/flight/dtos/flight.dto.ts
- Test Coverage · No test reaches this file src/booking/src/data/data-source.ts
- Test Coverage · No test reaches this file src/booking/src/data/repositories/booking.repository.ts
- Test Coverage · No test reaches this file src/booking/src/extensions/rabbitmq.extensions.ts
- Test Coverage · No test reaches this file src/building-blocks/contracts/passenger.contract.ts
- Test Coverage · No test reaches this file src/flight/src/data/data-source.ts
- Test Coverage · No test reaches this file src/flight/src/extensions/rabbitmq.extensions.ts
- Test Coverage · No test reaches this file src/identity/src/data/data-source.ts
- Test Coverage · No test reaches this file src/passenger/src/data/data-source.ts
- Test Coverage · No test reaches this file src/passenger/src/data/migrations/1702553578224-create-passenger-table.ts
- Test Coverage · No test reaches this file src/booking/src/data/db.context.ts
- Test Coverage · No test reaches this file src/building-blocks/contracts/booking.contract.ts
- Test Coverage · No test reaches this file src/passenger/src/data/db.context.ts
- Test Coverage · No test reaches this file src/passenger/src/extensions/mediatr.extensions.ts
- Test Coverage · No test reaches this file src/building-blocks/context/context.ts
- Test Coverage · No test reaches this file src/flight/src/seat/dtos/seat.dto.ts
- Test Coverage · No test reaches this file src/booking/src/data/migrations/1702553396443-create-booking-table.ts
- Test Coverage · No test reaches this file src/booking/src/extensions/otel.extensions.ts
- Test Coverage · No test reaches this file src/flight/src/extensions/otel.extensions.ts
- Test Coverage · No test reaches this file src/passenger/src/extensions/otel.extensions.ts
- Test Coverage · No test reaches this file src/booking/src/booking/dtos/booking.dto.ts
- Test Coverage · No test reaches this file src/flight/src/aircraft/dtos/aircraft.dto.ts
- Test Coverage · No test reaches this file src/flight/src/airport/dtos/airport.dto.ts
- Test Coverage · No test reaches this file src/flight/src/extensions/repository.extensions.ts
- Test Coverage · No test reaches this file src/booking/src/extensions/http-client.extensions.ts
- Test Coverage · No test reaches this file src/passenger/src/passenger/dtos/passenger.dto.ts
- Test Coverage · No test reaches this file src/booking/src/extensions/logger.extensions.ts
- Test Coverage · No test reaches this file src/booking/src/extensions/mediatr.extensions.ts
- Test Coverage · No test reaches this file src/flight/src/extensions/logger.extensions.ts
- Test Coverage · No test reaches this file src/identity/src/extensions/logger.extensions.ts
- Test Coverage · No test reaches this file src/passenger/src/extensions/logger.extensions.ts
- Test Coverage · No test reaches this file src/passenger/src/extensions/repository.extensions.ts
- Test Coverage · No test reaches this file src/flight/src/flight/enums/flight-status.enum.ts
- Test Coverage · No test reaches this file src/booking/src/extensions/repository.extensions.ts
- Test Coverage · No test reaches this file src/flight/src/seat/enums/seat-class.enum.ts
- Test Coverage · No test reaches this file src/flight/src/seat/enums/seat-type.enum.ts
- Test Coverage · No test reaches this file src/passenger/src/passenger/enums/passenger-type.enum.ts
Rebuild cost: about €7,300 · Estimate
| Cost to rebuild | €2,400 to €12,000, for 40 to 128 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 27. 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: 6,747 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 building-blocks.contracts.flight_contract | 2 building-blocks.contracts.identity_contract | 3 building-blocks.contracts.passenger_contract | 4 building-blocks.logging.logger | 5 building-blocks.mediatr-js.mediatr-js | 6 building-blocks.rabbitmq.rabbitmq-connection-options-builder | 7 building-blocks.rabbitmq.rabbitmq-publisher | 8 identity.src.auth.dtos.auth_dto | 9 identity.src.auth.enums.token-type_enum | 10 passenger.src.data.repositories.passenger_repository | 11 booking.src.booking.features.v1.create-booking.create-booking | 12 building-blocks.open-telemetry.otel-diagnostics-provider | 13 flight.src.aircraft.features.v1.create-aircraft.create-aircraft | 14 flight.src.airport.features.v1.create-airport.create-airport | 15 flight.src.flight.entities.flight_entity | 16 identity.src.user.dtos.user_dto | 17 identity.src.user.entities.user_entity | 18 booking.src.extensions | 19 flight.src.data.repositories.flight_repository | 20 flight.src.extensions | 21 flight.src.seat.entities.seat_entity | 22 identity.src.auth.entities.token_entity | 23 identity.src.data.repositories.user_repository | 24 identity.src.extensions | 25 passenger.src.extensions | 26 flight.src.data.repositories.seat_repository | 27 flight.src.flight.features.v1.create-flight.create-flight | 28 flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id | 29 identity.src.auth.features.v1.login.login | 30 identity.src.data.repositories.auth_repository | 31 identity.src.user.features.v1.create-user.create-user | 32 identity.src.user.features.v1.delete-user-by-id.delete-user-by-id | 33 identity.src.user.features.v1.get-user-by-id.get-user-by-id | 34 identity.src.user.features.v1.get-users.get-users | 35 identity.src.user.features.v1.update-user.update-user | 36 flight.src.seat.features.v1.create-seat.create-seat | 37 flight.src.seat.features.v1.reserve-seat.reserve-seat | 38 identity.src.auth.features.v1.generate-token.generate-token | 39 identity.src.auth.features.v1.refresh-token.refresh-token | 40 identity.src.auth.features.v1.validate-token.validate-token |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 building-blocks.contracts.flight_contract | ||||||||||||||||||||||||||||||||||||||||
| 2 building-blocks.contracts.identity_contract | ||||||||||||||||||||||||||||||||||||||||
| 3 building-blocks.contracts.passenger_contract | ||||||||||||||||||||||||||||||||||||||||
| 4 building-blocks.logging.logger | ||||||||||||||||||||||||||||||||||||||||
| 5 building-blocks.mediatr-js.mediatr-js | ||||||||||||||||||||||||||||||||||||||||
| 6 building-blocks.rabbitmq.rabbitmq-connection-options-builder | ||||||||||||||||||||||||||||||||||||||||
| 7 building-blocks.rabbitmq.rabbitmq-publisher | ||||||||||||||||||||||||||||||||||||||||
| 8 identity.src.auth.dtos.auth_dto | ||||||||||||||||||||||||||||||||||||||||
| 9 identity.src.auth.enums.token-type_enum | ||||||||||||||||||||||||||||||||||||||||
| 10 passenger.src.data.repositories.passenger_repository | ||||||||||||||||||||||||||||||||||||||||
| 11 booking.src.booking.features.v1.create-booking.create-booking | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 building-blocks.open-telemetry.otel-diagnostics-provider | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 flight.src.aircraft.features.v1.create-aircraft.create-aircraft | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 flight.src.airport.features.v1.create-airport.create-airport | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 flight.src.flight.entities.flight_entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 identity.src.user.dtos.user_dto | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 identity.src.user.entities.user_entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 booking.src.extensions | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 flight.src.data.repositories.flight_repository | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 flight.src.extensions | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 flight.src.seat.entities.seat_entity | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 identity.src.auth.entities.token_entity | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 identity.src.data.repositories.user_repository | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 identity.src.extensions | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 passenger.src.extensions | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 flight.src.data.repositories.seat_repository | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 flight.src.flight.features.v1.create-flight.create-flight | 4 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 identity.src.auth.features.v1.login.login | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 identity.src.data.repositories.auth_repository | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 identity.src.user.features.v1.create-user.create-user | 2 | 2 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 32 identity.src.user.features.v1.delete-user-by-id.delete-user-by-id | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 identity.src.user.features.v1.get-user-by-id.get-user-by-id | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 identity.src.user.features.v1.get-users.get-users | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 identity.src.user.features.v1.update-user.update-user | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 flight.src.seat.features.v1.create-seat.create-seat | 6 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 flight.src.seat.features.v1.reserve-seat.reserve-seat | 3 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 38 identity.src.auth.features.v1.generate-token.generate-token | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 identity.src.auth.features.v1.refresh-token.refresh-token | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 identity.src.auth.features.v1.validate-token.validate-token | 2 | 1 | 1 | 1 |
11→5 booking.src.booking.features.v1.create-booking.create-booking uses building-blocks.mediatr-js.mediatr-js✕
- Connections
- 2 pairs of types, where a type in booking.src.booking.features.v1.create-booking.create-booking uses a type in building-blocks.mediatr-js.mediatr-js.
- The types involved
src.booking.src.booking.features.v1.create-booking.create-booking.CreateBooking→src.building-blocks.mediatr-js.mediatr-js.IRequestsrc.booking.src.booking.features.v1.create-booking.create-booking.CreateBookingHandler→src.building-blocks.mediatr-js.mediatr-js.IRequestHandler
- Direction
- booking.src.booking.features.v1.create-booking.create-booking uses building-blocks.mediatr-js.mediatr-js, so a change to building-blocks.mediatr-js.mediatr-js can break booking.src.booking.features.v1.create-booking.create-booking, while a change to booking.src.booking.features.v1.create-booking.create-booking can't break building-blocks.mediatr-js.mediatr-js.
- Position
- Below the diagonal: booking.src.booking.features.v1.create-booking.create-booking uses a module listed above it, which is the healthy direction.
11→7 booking.src.booking.features.v1.create-booking.create-booking uses building-blocks.rabbitmq.rabbitmq-publisher✕
- Connections
- 1 pair of types, where a type in booking.src.booking.features.v1.create-booking.create-booking uses a type in building-blocks.rabbitmq.rabbitmq-publisher.
- The types involved
src.booking.src.booking.features.v1.create-booking.create-booking.CreateBookingHandler→src.building-blocks.rabbitmq.rabbitmq-publisher.IPublisher
- Direction
- booking.src.booking.features.v1.create-booking.create-booking uses building-blocks.rabbitmq.rabbitmq-publisher, so a change to building-blocks.rabbitmq.rabbitmq-publisher can break booking.src.booking.features.v1.create-booking.create-booking, while a change to booking.src.booking.features.v1.create-booking.create-booking can't break building-blocks.rabbitmq.rabbitmq-publisher.
- Position
- Below the diagonal: booking.src.booking.features.v1.create-booking.create-booking uses a module listed above it, which is the healthy direction.
12→4 building-blocks.open-telemetry.otel-diagnostics-provider uses building-blocks.logging.logger✕
- Connections
- 1 pair of types, where a type in building-blocks.open-telemetry.otel-diagnostics-provider uses a type in building-blocks.logging.logger.
- The types involved
src.building-blocks.open-telemetry.otel-diagnostics-provider.OtelDiagnosticsProvider→src.building-blocks.logging.logger.Logger
- Direction
- building-blocks.open-telemetry.otel-diagnostics-provider uses building-blocks.logging.logger, so a change to building-blocks.logging.logger can break building-blocks.open-telemetry.otel-diagnostics-provider, while a change to building-blocks.open-telemetry.otel-diagnostics-provider can't break building-blocks.logging.logger.
- Position
- Below the diagonal: building-blocks.open-telemetry.otel-diagnostics-provider uses a module listed above it, which is the healthy direction.
13→5 flight.src.aircraft.features.v1.create-aircraft.create-aircraft uses building-blocks.mediatr-js.mediatr-js✕
- Connections
- 2 pairs of types, where a type in flight.src.aircraft.features.v1.create-aircraft.create-aircraft uses a type in building-blocks.mediatr-js.mediatr-js.
- The types involved
src.flight.src.aircraft.features.v1.create-aircraft.create-aircraft.CreateAircraft→src.building-blocks.mediatr-js.mediatr-js.IRequestsrc.flight.src.aircraft.features.v1.create-aircraft.create-aircraft.CreateAircraftHandler→src.building-blocks.mediatr-js.mediatr-js.IRequestHandler
- Direction
- flight.src.aircraft.features.v1.create-aircraft.create-aircraft uses building-blocks.mediatr-js.mediatr-js, so a change to building-blocks.mediatr-js.mediatr-js can break flight.src.aircraft.features.v1.create-aircraft.create-aircraft, while a change to flight.src.aircraft.features.v1.create-aircraft.create-aircraft can't break building-blocks.mediatr-js.mediatr-js.
- Position
- Below the diagonal: flight.src.aircraft.features.v1.create-aircraft.create-aircraft uses a module listed above it, which is the healthy direction.
13→7 flight.src.aircraft.features.v1.create-aircraft.create-aircraft uses building-blocks.rabbitmq.rabbitmq-publisher✕
- Connections
- 1 pair of types, where a type in flight.src.aircraft.features.v1.create-aircraft.create-aircraft uses a type in building-blocks.rabbitmq.rabbitmq-publisher.
- The types involved
src.flight.src.aircraft.features.v1.create-aircraft.create-aircraft.CreateAircraftHandler→src.building-blocks.rabbitmq.rabbitmq-publisher.IPublisher
- Direction
- flight.src.aircraft.features.v1.create-aircraft.create-aircraft uses building-blocks.rabbitmq.rabbitmq-publisher, so a change to building-blocks.rabbitmq.rabbitmq-publisher can break flight.src.aircraft.features.v1.create-aircraft.create-aircraft, while a change to flight.src.aircraft.features.v1.create-aircraft.create-aircraft can't break building-blocks.rabbitmq.rabbitmq-publisher.
- Position
- Below the diagonal: flight.src.aircraft.features.v1.create-aircraft.create-aircraft uses a module listed above it, which is the healthy direction.
14→5 flight.src.airport.features.v1.create-airport.create-airport uses building-blocks.mediatr-js.mediatr-js✕
- Connections
- 2 pairs of types, where a type in flight.src.airport.features.v1.create-airport.create-airport uses a type in building-blocks.mediatr-js.mediatr-js.
- The types involved
src.flight.src.airport.features.v1.create-airport.create-airport.CreateAirport→src.building-blocks.mediatr-js.mediatr-js.IRequestsrc.flight.src.airport.features.v1.create-airport.create-airport.CreateAirportHandler→src.building-blocks.mediatr-js.mediatr-js.IRequestHandler
- Direction
- flight.src.airport.features.v1.create-airport.create-airport uses building-blocks.mediatr-js.mediatr-js, so a change to building-blocks.mediatr-js.mediatr-js can break flight.src.airport.features.v1.create-airport.create-airport, while a change to flight.src.airport.features.v1.create-airport.create-airport can't break building-blocks.mediatr-js.mediatr-js.
- Position
- Below the diagonal: flight.src.airport.features.v1.create-airport.create-airport uses a module listed above it, which is the healthy direction.
14→7 flight.src.airport.features.v1.create-airport.create-airport uses building-blocks.rabbitmq.rabbitmq-publisher✕
- Connections
- 1 pair of types, where a type in flight.src.airport.features.v1.create-airport.create-airport uses a type in building-blocks.rabbitmq.rabbitmq-publisher.
- The types involved
src.flight.src.airport.features.v1.create-airport.create-airport.CreateAirportHandler→src.building-blocks.rabbitmq.rabbitmq-publisher.IPublisher
- Direction
- flight.src.airport.features.v1.create-airport.create-airport uses building-blocks.rabbitmq.rabbitmq-publisher, so a change to building-blocks.rabbitmq.rabbitmq-publisher can break flight.src.airport.features.v1.create-airport.create-airport, while a change to flight.src.airport.features.v1.create-airport.create-airport can't break building-blocks.rabbitmq.rabbitmq-publisher.
- Position
- Below the diagonal: flight.src.airport.features.v1.create-airport.create-airport uses a module listed above it, which is the healthy direction.
15→1 flight.src.flight.entities.flight_entity uses building-blocks.contracts.flight_contract✕
- Connections
- 1 pair of types, where a type in flight.src.flight.entities.flight_entity uses a type in building-blocks.contracts.flight_contract.
- The types involved
src.flight.src.flight.entities.flight_entity.Flight→src.building-blocks.contracts.flight_contract.FlightStatus
- Direction
- flight.src.flight.entities.flight_entity uses building-blocks.contracts.flight_contract, so a change to building-blocks.contracts.flight_contract can break flight.src.flight.entities.flight_entity, while a change to flight.src.flight.entities.flight_entity can't break building-blocks.contracts.flight_contract.
- Position
- Below the diagonal: flight.src.flight.entities.flight_entity uses a module listed above it, which is the healthy direction.
16→2 identity.src.user.dtos.user_dto uses building-blocks.contracts.identity_contract✕
- Connections
- 1 pair of types, where a type in identity.src.user.dtos.user_dto uses a type in building-blocks.contracts.identity_contract.
- The types involved
src.identity.src.user.dtos.user_dto.UserDto→src.building-blocks.contracts.identity_contract.Role
- Direction
- identity.src.user.dtos.user_dto uses building-blocks.contracts.identity_contract, so a change to building-blocks.contracts.identity_contract can break identity.src.user.dtos.user_dto, while a change to identity.src.user.dtos.user_dto can't break building-blocks.contracts.identity_contract.
- Position
- Below the diagonal: identity.src.user.dtos.user_dto uses a module listed above it, which is the healthy direction.
17→2 identity.src.user.entities.user_entity uses building-blocks.contracts.identity_contract✕
- Connections
- 1 pair of types, where a type in identity.src.user.entities.user_entity uses a type in building-blocks.contracts.identity_contract.
- The types involved
src.identity.src.user.entities.user_entity.User→src.building-blocks.contracts.identity_contract.Role
- Direction
- identity.src.user.entities.user_entity uses building-blocks.contracts.identity_contract, so a change to building-blocks.contracts.identity_contract can break identity.src.user.entities.user_entity, while a change to identity.src.user.entities.user_entity can't break building-blocks.contracts.identity_contract.
- Position
- Below the diagonal: identity.src.user.entities.user_entity uses a module listed above it, which is the healthy direction.
18→4 booking.src.extensions uses building-blocks.logging.logger✕
- Connections
- 1 pair of types, where a type in booking.src.extensions uses a type in building-blocks.logging.logger.
- The types involved
src.booking.src.extensions.logger.extensions→src.building-blocks.logging.logger.Logger
- Direction
- booking.src.extensions uses building-blocks.logging.logger, so a change to building-blocks.logging.logger can break booking.src.extensions, while a change to booking.src.extensions can't break building-blocks.logging.logger.
- Position
- Below the diagonal: booking.src.extensions uses a module listed above it, which is the healthy direction.
18→6 booking.src.extensions uses building-blocks.rabbitmq.rabbitmq-connection-options-builder✕
- Connections
- 1 pair of types, where a type in booking.src.extensions uses a type in building-blocks.rabbitmq.rabbitmq-connection-options-builder.
- The types involved
src.booking.src.extensions.rabbitmq.extensions→src.building-blocks.rabbitmq.rabbitmq-connection-options-builder.RabbitmqConnectionOptions
- Direction
- booking.src.extensions uses building-blocks.rabbitmq.rabbitmq-connection-options-builder, so a change to building-blocks.rabbitmq.rabbitmq-connection-options-builder can break booking.src.extensions, while a change to booking.src.extensions can't break building-blocks.rabbitmq.rabbitmq-connection-options-builder.
- Position
- Below the diagonal: booking.src.extensions uses a module listed above it, which is the healthy direction.
18→12 booking.src.extensions uses building-blocks.open-telemetry.otel-diagnostics-provider✕
- Connections
- 1 pair of types, where a type in booking.src.extensions uses a type in building-blocks.open-telemetry.otel-diagnostics-provider.
- The types involved
src.booking.src.extensions.otel.extensions→src.building-blocks.open-telemetry.otel-diagnostics-provider.OtelDiagnosticsProvider
- Direction
- booking.src.extensions uses building-blocks.open-telemetry.otel-diagnostics-provider, so a change to building-blocks.open-telemetry.otel-diagnostics-provider can break booking.src.extensions, while a change to booking.src.extensions can't break building-blocks.open-telemetry.otel-diagnostics-provider.
- Position
- Below the diagonal: booking.src.extensions uses a module listed above it, which is the healthy direction.
19→15 flight.src.data.repositories.flight_repository uses flight.src.flight.entities.flight_entity✕
- Connections
- 2 pairs of types, where a type in flight.src.data.repositories.flight_repository uses a type in flight.src.flight.entities.flight_entity.
- The types involved
src.flight.src.data.repositories.flight_repository.FlightRepository→src.flight.src.flight.entities.flight_entity.Flightsrc.flight.src.data.repositories.flight_repository.IFlightRepository→src.flight.src.flight.entities.flight_entity.Flight
- Direction
- flight.src.data.repositories.flight_repository uses flight.src.flight.entities.flight_entity, so a change to flight.src.flight.entities.flight_entity can break flight.src.data.repositories.flight_repository, while a change to flight.src.data.repositories.flight_repository can't break flight.src.flight.entities.flight_entity.
- Position
- Below the diagonal: flight.src.data.repositories.flight_repository uses a module listed above it, which is the healthy direction.
20→4 flight.src.extensions uses building-blocks.logging.logger✕
- Connections
- 1 pair of types, where a type in flight.src.extensions uses a type in building-blocks.logging.logger.
- The types involved
src.flight.src.extensions.logger.extensions→src.building-blocks.logging.logger.Logger
- Direction
- flight.src.extensions uses building-blocks.logging.logger, so a change to building-blocks.logging.logger can break flight.src.extensions, while a change to flight.src.extensions can't break building-blocks.logging.logger.
- Position
- Below the diagonal: flight.src.extensions uses a module listed above it, which is the healthy direction.
20→6 flight.src.extensions uses building-blocks.rabbitmq.rabbitmq-connection-options-builder✕
- Connections
- 1 pair of types, where a type in flight.src.extensions uses a type in building-blocks.rabbitmq.rabbitmq-connection-options-builder.
- The types involved
src.flight.src.extensions.rabbitmq.extensions→src.building-blocks.rabbitmq.rabbitmq-connection-options-builder.RabbitmqConnectionOptions
- Direction
- flight.src.extensions uses building-blocks.rabbitmq.rabbitmq-connection-options-builder, so a change to building-blocks.rabbitmq.rabbitmq-connection-options-builder can break flight.src.extensions, while a change to flight.src.extensions can't break building-blocks.rabbitmq.rabbitmq-connection-options-builder.
- Position
- Below the diagonal: flight.src.extensions uses a module listed above it, which is the healthy direction.
20→12 flight.src.extensions uses building-blocks.open-telemetry.otel-diagnostics-provider✕
- Connections
- 1 pair of types, where a type in flight.src.extensions uses a type in building-blocks.open-telemetry.otel-diagnostics-provider.
- The types involved
src.flight.src.extensions.otel.extensions→src.building-blocks.open-telemetry.otel-diagnostics-provider.OtelDiagnosticsProvider
- Direction
- flight.src.extensions uses building-blocks.open-telemetry.otel-diagnostics-provider, so a change to building-blocks.open-telemetry.otel-diagnostics-provider can break flight.src.extensions, while a change to flight.src.extensions can't break building-blocks.open-telemetry.otel-diagnostics-provider.
- Position
- Below the diagonal: flight.src.extensions uses a module listed above it, which is the healthy direction.
21→1 flight.src.seat.entities.seat_entity uses building-blocks.contracts.flight_contract✕
- Connections
- 2 pairs of types, where a type in flight.src.seat.entities.seat_entity uses a type in building-blocks.contracts.flight_contract.
- The types involved
src.flight.src.seat.entities.seat_entity.Seat→src.building-blocks.contracts.flight_contract.SeatClasssrc.flight.src.seat.entities.seat_entity.Seat→src.building-blocks.contracts.flight_contract.SeatType
- Direction
- flight.src.seat.entities.seat_entity uses building-blocks.contracts.flight_contract, so a change to building-blocks.contracts.flight_contract can break flight.src.seat.entities.seat_entity, while a change to flight.src.seat.entities.seat_entity can't break building-blocks.contracts.flight_contract.
- Position
- Below the diagonal: flight.src.seat.entities.seat_entity uses a module listed above it, which is the healthy direction.
21→15 flight.src.seat.entities.seat_entity uses flight.src.flight.entities.flight_entity✕
- Connections
- 1 pair of types, where a type in flight.src.seat.entities.seat_entity uses a type in flight.src.flight.entities.flight_entity.
- The types involved
src.flight.src.seat.entities.seat_entity.Seat→src.flight.src.flight.entities.flight_entity.Flight
- Direction
- flight.src.seat.entities.seat_entity uses flight.src.flight.entities.flight_entity, so a change to flight.src.flight.entities.flight_entity can break flight.src.seat.entities.seat_entity, while a change to flight.src.seat.entities.seat_entity can't break flight.src.flight.entities.flight_entity.
- Position
- Below the diagonal: flight.src.seat.entities.seat_entity uses a module listed above it, which is the healthy direction.
22→9 identity.src.auth.entities.token_entity uses identity.src.auth.enums.token-type_enum✕
- Connections
- 1 pair of types, where a type in identity.src.auth.entities.token_entity uses a type in identity.src.auth.enums.token-type_enum.
- The types involved
src.identity.src.auth.entities.token_entity.Token→src.identity.src.auth.enums.token-type_enum.TokenType
- Direction
- identity.src.auth.entities.token_entity uses identity.src.auth.enums.token-type_enum, so a change to identity.src.auth.enums.token-type_enum can break identity.src.auth.entities.token_entity, while a change to identity.src.auth.entities.token_entity can't break identity.src.auth.enums.token-type_enum.
- Position
- Below the diagonal: identity.src.auth.entities.token_entity uses a module listed above it, which is the healthy direction.
22→17 identity.src.auth.entities.token_entity uses identity.src.user.entities.user_entity✕
- Connections
- 1 pair of types, where a type in identity.src.auth.entities.token_entity uses a type in identity.src.user.entities.user_entity.
- The types involved
src.identity.src.auth.entities.token_entity.Token→src.identity.src.user.entities.user_entity.User
- Direction
- identity.src.auth.entities.token_entity uses identity.src.user.entities.user_entity, so a change to identity.src.user.entities.user_entity can break identity.src.auth.entities.token_entity, while a change to identity.src.auth.entities.token_entity can't break identity.src.user.entities.user_entity.
- Position
- Below the diagonal: identity.src.auth.entities.token_entity uses a module listed above it, which is the healthy direction.
23→17 identity.src.data.repositories.user_repository uses identity.src.user.entities.user_entity✕
- Connections
- 2 pairs of types, where a type in identity.src.data.repositories.user_repository uses a type in identity.src.user.entities.user_entity.
- The types involved
src.identity.src.data.repositories.user_repository.IUserRepository→src.identity.src.user.entities.user_entity.Usersrc.identity.src.data.repositories.user_repository.UserRepository→src.identity.src.user.entities.user_entity.User
- Direction
- identity.src.data.repositories.user_repository uses identity.src.user.entities.user_entity, so a change to identity.src.user.entities.user_entity can break identity.src.data.repositories.user_repository, while a change to identity.src.data.repositories.user_repository can't break identity.src.user.entities.user_entity.
- Position
- Below the diagonal: identity.src.data.repositories.user_repository uses a module listed above it, which is the healthy direction.
24→4 identity.src.extensions uses building-blocks.logging.logger✕
- Connections
- 1 pair of types, where a type in identity.src.extensions uses a type in building-blocks.logging.logger.
- The types involved
src.identity.src.extensions.logger.extensions→src.building-blocks.logging.logger.Logger
- Direction
- identity.src.extensions uses building-blocks.logging.logger, so a change to building-blocks.logging.logger can break identity.src.extensions, while a change to identity.src.extensions can't break building-blocks.logging.logger.
- Position
- Below the diagonal: identity.src.extensions uses a module listed above it, which is the healthy direction.
24→6 identity.src.extensions uses building-blocks.rabbitmq.rabbitmq-connection-options-builder✕
- Connections
- 1 pair of types, where a type in identity.src.extensions uses a type in building-blocks.rabbitmq.rabbitmq-connection-options-builder.
- The types involved
src.identity.src.extensions.rabbitmq.extensions→src.building-blocks.rabbitmq.rabbitmq-connection-options-builder.RabbitmqConnectionOptions
- Direction
- identity.src.extensions uses building-blocks.rabbitmq.rabbitmq-connection-options-builder, so a change to building-blocks.rabbitmq.rabbitmq-connection-options-builder can break identity.src.extensions, while a change to identity.src.extensions can't break building-blocks.rabbitmq.rabbitmq-connection-options-builder.
- Position
- Below the diagonal: identity.src.extensions uses a module listed above it, which is the healthy direction.
24→12 identity.src.extensions uses building-blocks.open-telemetry.otel-diagnostics-provider✕
- Connections
- 1 pair of types, where a type in identity.src.extensions uses a type in building-blocks.open-telemetry.otel-diagnostics-provider.
- The types involved
src.identity.src.extensions.otel.extensions→src.building-blocks.open-telemetry.otel-diagnostics-provider.OtelDiagnosticsProvider
- Direction
- identity.src.extensions uses building-blocks.open-telemetry.otel-diagnostics-provider, so a change to building-blocks.open-telemetry.otel-diagnostics-provider can break identity.src.extensions, while a change to identity.src.extensions can't break building-blocks.open-telemetry.otel-diagnostics-provider.
- Position
- Below the diagonal: identity.src.extensions uses a module listed above it, which is the healthy direction.
25→4 passenger.src.extensions uses building-blocks.logging.logger✕
- Connections
- 1 pair of types, where a type in passenger.src.extensions uses a type in building-blocks.logging.logger.
- The types involved
src.passenger.src.extensions.logger.extensions→src.building-blocks.logging.logger.Logger
- Direction
- passenger.src.extensions uses building-blocks.logging.logger, so a change to building-blocks.logging.logger can break passenger.src.extensions, while a change to passenger.src.extensions can't break building-blocks.logging.logger.
- Position
- Below the diagonal: passenger.src.extensions uses a module listed above it, which is the healthy direction.
25→6 passenger.src.extensions uses building-blocks.rabbitmq.rabbitmq-connection-options-builder✕
- Connections
- 1 pair of types, where a type in passenger.src.extensions uses a type in building-blocks.rabbitmq.rabbitmq-connection-options-builder.
- The types involved
src.passenger.src.extensions.rabbitmq.extensions→src.building-blocks.rabbitmq.rabbitmq-connection-options-builder.RabbitmqConnectionOptions
- Direction
- passenger.src.extensions uses building-blocks.rabbitmq.rabbitmq-connection-options-builder, so a change to building-blocks.rabbitmq.rabbitmq-connection-options-builder can break passenger.src.extensions, while a change to passenger.src.extensions can't break building-blocks.rabbitmq.rabbitmq-connection-options-builder.
- Position
- Below the diagonal: passenger.src.extensions uses a module listed above it, which is the healthy direction.
25→12 passenger.src.extensions uses building-blocks.open-telemetry.otel-diagnostics-provider✕
- Connections
- 1 pair of types, where a type in passenger.src.extensions uses a type in building-blocks.open-telemetry.otel-diagnostics-provider.
- The types involved
src.passenger.src.extensions.otel.extensions→src.building-blocks.open-telemetry.otel-diagnostics-provider.OtelDiagnosticsProvider
- Direction
- passenger.src.extensions uses building-blocks.open-telemetry.otel-diagnostics-provider, so a change to building-blocks.open-telemetry.otel-diagnostics-provider can break passenger.src.extensions, while a change to passenger.src.extensions can't break building-blocks.open-telemetry.otel-diagnostics-provider.
- Position
- Below the diagonal: passenger.src.extensions uses a module listed above it, which is the healthy direction.
26→21 flight.src.data.repositories.seat_repository uses flight.src.seat.entities.seat_entity✕
- Connections
- 2 pairs of types, where a type in flight.src.data.repositories.seat_repository uses a type in flight.src.seat.entities.seat_entity.
- The types involved
src.flight.src.data.repositories.seat_repository.ISeatRepository→src.flight.src.seat.entities.seat_entity.Seatsrc.flight.src.data.repositories.seat_repository.SeatRepository→src.flight.src.seat.entities.seat_entity.Seat
- Direction
- flight.src.data.repositories.seat_repository uses flight.src.seat.entities.seat_entity, so a change to flight.src.seat.entities.seat_entity can break flight.src.data.repositories.seat_repository, while a change to flight.src.data.repositories.seat_repository can't break flight.src.seat.entities.seat_entity.
- Position
- Below the diagonal: flight.src.data.repositories.seat_repository uses a module listed above it, which is the healthy direction.
27→1 flight.src.flight.features.v1.create-flight.create-flight uses building-blocks.contracts.flight_contract✕
- Connections
- 4 pairs of types, where a type in flight.src.flight.features.v1.create-flight.create-flight uses a type in building-blocks.contracts.flight_contract.
- The types involved
src.flight.src.flight.features.v1.create-flight.create-flight.CreateFlight→src.building-blocks.contracts.flight_contract.FlightStatussrc.flight.src.flight.features.v1.create-flight.create-flight.CreateFlightController→src.building-blocks.contracts.flight_contract.FlightDtosrc.flight.src.flight.features.v1.create-flight.create-flight.CreateFlightHandler→src.building-blocks.contracts.flight_contract.FlightDtosrc.flight.src.flight.features.v1.create-flight.create-flight.CreateFlightRequestDto→src.building-blocks.contracts.flight_contract.FlightStatus
- Direction
- flight.src.flight.features.v1.create-flight.create-flight uses building-blocks.contracts.flight_contract, so a change to building-blocks.contracts.flight_contract can break flight.src.flight.features.v1.create-flight.create-flight, while a change to flight.src.flight.features.v1.create-flight.create-flight can't break building-blocks.contracts.flight_contract.
- Position
- Below the diagonal: flight.src.flight.features.v1.create-flight.create-flight uses a module listed above it, which is the healthy direction.
27→5 flight.src.flight.features.v1.create-flight.create-flight uses building-blocks.mediatr-js.mediatr-js✕
- Connections
- 2 pairs of types, where a type in flight.src.flight.features.v1.create-flight.create-flight uses a type in building-blocks.mediatr-js.mediatr-js.
- The types involved
src.flight.src.flight.features.v1.create-flight.create-flight.CreateFlight→src.building-blocks.mediatr-js.mediatr-js.IRequestsrc.flight.src.flight.features.v1.create-flight.create-flight.CreateFlightHandler→src.building-blocks.mediatr-js.mediatr-js.IRequestHandler
- Direction
- flight.src.flight.features.v1.create-flight.create-flight uses building-blocks.mediatr-js.mediatr-js, so a change to building-blocks.mediatr-js.mediatr-js can break flight.src.flight.features.v1.create-flight.create-flight, while a change to flight.src.flight.features.v1.create-flight.create-flight can't break building-blocks.mediatr-js.mediatr-js.
- Position
- Below the diagonal: flight.src.flight.features.v1.create-flight.create-flight uses a module listed above it, which is the healthy direction.
27→7 flight.src.flight.features.v1.create-flight.create-flight uses building-blocks.rabbitmq.rabbitmq-publisher✕
- Connections
- 1 pair of types, where a type in flight.src.flight.features.v1.create-flight.create-flight uses a type in building-blocks.rabbitmq.rabbitmq-publisher.
- The types involved
src.flight.src.flight.features.v1.create-flight.create-flight.CreateFlightHandler→src.building-blocks.rabbitmq.rabbitmq-publisher.IPublisher
- Direction
- flight.src.flight.features.v1.create-flight.create-flight uses building-blocks.rabbitmq.rabbitmq-publisher, so a change to building-blocks.rabbitmq.rabbitmq-publisher can break flight.src.flight.features.v1.create-flight.create-flight, while a change to flight.src.flight.features.v1.create-flight.create-flight can't break building-blocks.rabbitmq.rabbitmq-publisher.
- Position
- Below the diagonal: flight.src.flight.features.v1.create-flight.create-flight uses a module listed above it, which is the healthy direction.
27→19 flight.src.flight.features.v1.create-flight.create-flight uses flight.src.data.repositories.flight_repository✕
- Connections
- 1 pair of types, where a type in flight.src.flight.features.v1.create-flight.create-flight uses a type in flight.src.data.repositories.flight_repository.
- The types involved
src.flight.src.flight.features.v1.create-flight.create-flight.CreateFlightHandler→src.flight.src.data.repositories.flight_repository.IFlightRepository
- Direction
- flight.src.flight.features.v1.create-flight.create-flight uses flight.src.data.repositories.flight_repository, so a change to flight.src.data.repositories.flight_repository can break flight.src.flight.features.v1.create-flight.create-flight, while a change to flight.src.flight.features.v1.create-flight.create-flight can't break flight.src.data.repositories.flight_repository.
- Position
- Below the diagonal: flight.src.flight.features.v1.create-flight.create-flight uses a module listed above it, which is the healthy direction.
28→1 flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id uses building-blocks.contracts.flight_contract✕
- Connections
- 2 pairs of types, where a type in flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id uses a type in building-blocks.contracts.flight_contract.
- The types involved
src.flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id.GetFlightByIdHandler→src.building-blocks.contracts.flight_contract.FlightDtosrc.flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id.GetUserByIdController→src.building-blocks.contracts.flight_contract.FlightDto
- Direction
- flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id uses building-blocks.contracts.flight_contract, so a change to building-blocks.contracts.flight_contract can break flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id, while a change to flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id can't break building-blocks.contracts.flight_contract.
- Position
- Below the diagonal: flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id uses a module listed above it, which is the healthy direction.
28→5 flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id uses building-blocks.mediatr-js.mediatr-js✕
- Connections
- 2 pairs of types, where a type in flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id uses a type in building-blocks.mediatr-js.mediatr-js.
- The types involved
src.flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id.GetFlightById→src.building-blocks.mediatr-js.mediatr-js.IRequestsrc.flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id.GetFlightByIdHandler→src.building-blocks.mediatr-js.mediatr-js.IRequestHandler
- Direction
- flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id uses building-blocks.mediatr-js.mediatr-js, so a change to building-blocks.mediatr-js.mediatr-js can break flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id, while a change to flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id can't break building-blocks.mediatr-js.mediatr-js.
- Position
- Below the diagonal: flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id uses a module listed above it, which is the healthy direction.
28→19 flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id uses flight.src.data.repositories.flight_repository✕
- Connections
- 1 pair of types, where a type in flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id uses a type in flight.src.data.repositories.flight_repository.
- The types involved
src.flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id.GetFlightByIdHandler→src.flight.src.data.repositories.flight_repository.IFlightRepository
- Direction
- flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id uses flight.src.data.repositories.flight_repository, so a change to flight.src.data.repositories.flight_repository can break flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id, while a change to flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id can't break flight.src.data.repositories.flight_repository.
- Position
- Below the diagonal: flight.src.flight.features.v1.get-flight-by-id.get-flight-by-id uses a module listed above it, which is the healthy direction.
29→5 identity.src.auth.features.v1.login.login uses building-blocks.mediatr-js.mediatr-js✕
- Connections
- 2 pairs of types, where a type in identity.src.auth.features.v1.login.login uses a type in building-blocks.mediatr-js.mediatr-js.
- The types involved
src.identity.src.auth.features.v1.login.login.Login→src.building-blocks.mediatr-js.mediatr-js.IRequestsrc.identity.src.auth.features.v1.login.login.LoginHandler→src.building-blocks.mediatr-js.mediatr-js.IRequestHandler
- Direction
- identity.src.auth.features.v1.login.login uses building-blocks.mediatr-js.mediatr-js, so a change to building-blocks.mediatr-js.mediatr-js can break identity.src.auth.features.v1.login.login, while a change to identity.src.auth.features.v1.login.login can't break building-blocks.mediatr-js.mediatr-js.
- Position
- Below the diagonal: identity.src.auth.features.v1.login.login uses a module listed above it, which is the healthy direction.
29→8 identity.src.auth.features.v1.login.login uses identity.src.auth.dtos.auth_dto✕
- Connections
- 2 pairs of types, where a type in identity.src.auth.features.v1.login.login uses a type in identity.src.auth.dtos.auth_dto.
- The types involved
src.identity.src.auth.features.v1.login.login.LoginController→src.identity.src.auth.dtos.auth_dto.AuthDtosrc.identity.src.auth.features.v1.login.login.LoginHandler→src.identity.src.auth.dtos.auth_dto.AuthDto
- Direction
- identity.src.auth.features.v1.login.login uses identity.src.auth.dtos.auth_dto, so a change to identity.src.auth.dtos.auth_dto can break identity.src.auth.features.v1.login.login, while a change to identity.src.auth.features.v1.login.login can't break identity.src.auth.dtos.auth_dto.
- Position
- Below the diagonal: identity.src.auth.features.v1.login.login uses a module listed above it, which is the healthy direction.
29→23 identity.src.auth.features.v1.login.login uses identity.src.data.repositories.user_repository✕
- Connections
- 1 pair of types, where a type in identity.src.auth.features.v1.login.login uses a type in identity.src.data.repositories.user_repository.
- The types involved
src.identity.src.auth.features.v1.login.login.LoginHandler→src.identity.src.data.repositories.user_repository.IUserRepository
- Direction
- identity.src.auth.features.v1.login.login uses identity.src.data.repositories.user_repository, so a change to identity.src.data.repositories.user_repository can break identity.src.auth.features.v1.login.login, while a change to identity.src.auth.features.v1.login.login can't break identity.src.data.repositories.user_repository.
- Position
- Below the diagonal: identity.src.auth.features.v1.login.login uses a module listed above it, which is the healthy direction.
30→9 identity.src.data.repositories.auth_repository uses identity.src.auth.enums.token-type_enum✕
- Connections
- 2 pairs of types, where a type in identity.src.data.repositories.auth_repository uses a type in identity.src.auth.enums.token-type_enum.
- The types involved
src.identity.src.data.repositories.auth_repository.AuthRepository→src.identity.src.auth.enums.token-type_enum.TokenTypesrc.identity.src.data.repositories.auth_repository.IAuthRepository→src.identity.src.auth.enums.token-type_enum.TokenType
- Direction
- identity.src.data.repositories.auth_repository uses identity.src.auth.enums.token-type_enum, so a change to identity.src.auth.enums.token-type_enum can break identity.src.data.repositories.auth_repository, while a change to identity.src.data.repositories.auth_repository can't break identity.src.auth.enums.token-type_enum.
- Position
- Below the diagonal: identity.src.data.repositories.auth_repository uses a module listed above it, which is the healthy direction.
30→22 identity.src.data.repositories.auth_repository uses identity.src.auth.entities.token_entity✕
- Connections
- 2 pairs of types, where a type in identity.src.data.repositories.auth_repository uses a type in identity.src.auth.entities.token_entity.
- The types involved
src.identity.src.data.repositories.auth_repository.AuthRepository→src.identity.src.auth.entities.token_entity.Tokensrc.identity.src.data.repositories.auth_repository.IAuthRepository→src.identity.src.auth.entities.token_entity.Token
- Direction
- identity.src.data.repositories.auth_repository uses identity.src.auth.entities.token_entity, so a change to identity.src.auth.entities.token_entity can break identity.src.data.repositories.auth_repository, while a change to identity.src.data.repositories.auth_repository can't break identity.src.auth.entities.token_entity.
- Position
- Below the diagonal: identity.src.data.repositories.auth_repository uses a module listed above it, which is the healthy direction.
31→2 identity.src.user.features.v1.create-user.create-user uses building-blocks.contracts.identity_contract✕
- Connections
- 2 pairs of types, where a type in identity.src.user.features.v1.create-user.create-user uses a type in building-blocks.contracts.identity_contract.
- The types involved
src.identity.src.user.features.v1.create-user.create-user.CreateUser→src.building-blocks.contracts.identity_contract.Rolesrc.identity.src.user.features.v1.create-user.create-user.CreateUserRequestDto→src.building-blocks.contracts.identity_contract.Role
- Direction
- identity.src.user.features.v1.create-user.create-user uses building-blocks.contracts.identity_contract, so a change to building-blocks.contracts.identity_contract can break identity.src.user.features.v1.create-user.create-user, while a change to identity.src.user.features.v1.create-user.create-user can't break building-blocks.contracts.identity_contract.
- Position
- Below the diagonal: identity.src.user.features.v1.create-user.create-user uses a module listed above it, which is the healthy direction.
31→5 identity.src.user.features.v1.create-user.create-user uses building-blocks.mediatr-js.mediatr-js✕
- Connections
- 2 pairs of types, where a type in identity.src.user.features.v1.create-user.create-user uses a type in building-blocks.mediatr-js.mediatr-js.
- The types involved
src.identity.src.user.features.v1.create-user.create-user.CreateUser→src.building-blocks.mediatr-js.mediatr-js.IRequestsrc.identity.src.user.features.v1.create-user.create-user.CreateUserHandler→src.building-blocks.mediatr-js.mediatr-js.IRequestHandler
- Direction
- identity.src.user.features.v1.create-user.create-user uses building-blocks.mediatr-js.mediatr-js, so a change to building-blocks.mediatr-js.mediatr-js can break identity.src.user.features.v1.create-user.create-user, while a change to identity.src.user.features.v1.create-user.create-user can't break building-blocks.mediatr-js.mediatr-js.
- Position
- Below the diagonal: identity.src.user.features.v1.create-user.create-user uses a module listed above it, which is the healthy direction.
31→7 identity.src.user.features.v1.create-user.create-user uses building-blocks.rabbitmq.rabbitmq-publisher✕
- Connections
- 1 pair of types, where a type in identity.src.user.features.v1.create-user.create-user uses a type in building-blocks.rabbitmq.rabbitmq-publisher.
- The types involved
src.identity.src.user.features.v1.create-user.create-user.CreateUserHandler→src.building-blocks.rabbitmq.rabbitmq-publisher.IPublisher
- Direction
- identity.src.user.features.v1.create-user.create-user uses building-blocks.rabbitmq.rabbitmq-publisher, so a change to building-blocks.rabbitmq.rabbitmq-publisher can break identity.src.user.features.v1.create-user.create-user, while a change to identity.src.user.features.v1.create-user.create-user can't break building-blocks.rabbitmq.rabbitmq-publisher.
- Position
- Below the diagonal: identity.src.user.features.v1.create-user.create-user uses a module listed above it, which is the healthy direction.
31→16 identity.src.user.features.v1.create-user.create-user uses identity.src.user.dtos.user_dto✕
- Connections
- 2 pairs of types, where a type in identity.src.user.features.v1.create-user.create-user uses a type in identity.src.user.dtos.user_dto.
- The types involved
src.identity.src.user.features.v1.create-user.create-user.CreateUserController→src.identity.src.user.dtos.user_dto.UserDtosrc.identity.src.user.features.v1.create-user.create-user.CreateUserHandler→src.identity.src.user.dtos.user_dto.UserDto
- Direction
- identity.src.user.features.v1.create-user.create-user uses identity.src.user.dtos.user_dto, so a change to identity.src.user.dtos.user_dto can break identity.src.user.features.v1.create-user.create-user, while a change to identity.src.user.features.v1.create-user.create-user can't break identity.src.user.dtos.user_dto.
- Position
- Below the diagonal: identity.src.user.features.v1.create-user.create-user uses a module listed above it, which is the healthy direction.
31→23 identity.src.user.features.v1.create-user.create-user uses identity.src.data.repositories.user_repository✕
- Connections
- 1 pair of types, where a type in identity.src.user.features.v1.create-user.create-user uses a type in identity.src.data.repositories.user_repository.
- The types involved
src.identity.src.user.features.v1.create-user.create-user.CreateUserHandler→src.identity.src.data.repositories.user_repository.IUserRepository
- Direction
- identity.src.user.features.v1.create-user.create-user uses identity.src.data.repositories.user_repository, so a change to identity.src.data.repositories.user_repository can break identity.src.user.features.v1.create-user.create-user, while a change to identity.src.user.features.v1.create-user.create-user can't break identity.src.data.repositories.user_repository.
- Position
- Below the diagonal: identity.src.user.features.v1.create-user.create-user uses a module listed above it, which is the healthy direction.
32→5 identity.src.user.features.v1.delete-user-by-id.delete-user-by-id uses building-blocks.mediatr-js.mediatr-js✕
- Connections
- 2 pairs of types, where a type in identity.src.user.features.v1.delete-user-by-id.delete-user-by-id uses a type in building-blocks.mediatr-js.mediatr-js.
- The types involved
src.identity.src.user.features.v1.delete-user-by-id.delete-user-by-id.DeleteUserById→src.building-blocks.mediatr-js.mediatr-js.IRequestsrc.identity.src.user.features.v1.delete-user-by-id.delete-user-by-id.DeleteUserByIdHandler→src.building-blocks.mediatr-js.mediatr-js.IRequestHandler
- Direction
- identity.src.user.features.v1.delete-user-by-id.delete-user-by-id uses building-blocks.mediatr-js.mediatr-js, so a change to building-blocks.mediatr-js.mediatr-js can break identity.src.user.features.v1.delete-user-by-id.delete-user-by-id, while a change to identity.src.user.features.v1.delete-user-by-id.delete-user-by-id can't break building-blocks.mediatr-js.mediatr-js.
- Position
- Below the diagonal: identity.src.user.features.v1.delete-user-by-id.delete-user-by-id uses a module listed above it, which is the healthy direction.
32→7 identity.src.user.features.v1.delete-user-by-id.delete-user-by-id uses building-blocks.rabbitmq.rabbitmq-publisher✕
- Connections
- 1 pair of types, where a type in identity.src.user.features.v1.delete-user-by-id.delete-user-by-id uses a type in building-blocks.rabbitmq.rabbitmq-publisher.
- The types involved
src.identity.src.user.features.v1.delete-user-by-id.delete-user-by-id.DeleteUserByIdHandler→src.building-blocks.rabbitmq.rabbitmq-publisher.IPublisher
- Direction
- identity.src.user.features.v1.delete-user-by-id.delete-user-by-id uses building-blocks.rabbitmq.rabbitmq-publisher, so a change to building-blocks.rabbitmq.rabbitmq-publisher can break identity.src.user.features.v1.delete-user-by-id.delete-user-by-id, while a change to identity.src.user.features.v1.delete-user-by-id.delete-user-by-id can't break building-blocks.rabbitmq.rabbitmq-publisher.
- Position
- Below the diagonal: identity.src.user.features.v1.delete-user-by-id.delete-user-by-id uses a module listed above it, which is the healthy direction.
32→16 identity.src.user.features.v1.delete-user-by-id.delete-user-by-id uses identity.src.user.dtos.user_dto✕
- Connections
- 2 pairs of types, where a type in identity.src.user.features.v1.delete-user-by-id.delete-user-by-id uses a type in identity.src.user.dtos.user_dto.
- The types involved
src.identity.src.user.features.v1.delete-user-by-id.delete-user-by-id.DeleteUserByIdController→src.identity.src.user.dtos.user_dto.UserDtosrc.identity.src.user.features.v1.delete-user-by-id.delete-user-by-id.DeleteUserByIdHandler→src.identity.src.user.dtos.user_dto.UserDto
- Direction
- identity.src.user.features.v1.delete-user-by-id.delete-user-by-id uses identity.src.user.dtos.user_dto, so a change to identity.src.user.dtos.user_dto can break identity.src.user.features.v1.delete-user-by-id.delete-user-by-id, while a change to identity.src.user.features.v1.delete-user-by-id.delete-user-by-id can't break identity.src.user.dtos.user_dto.
- Position
- Below the diagonal: identity.src.user.features.v1.delete-user-by-id.delete-user-by-id uses a module listed above it, which is the healthy direction.
32→23 identity.src.user.features.v1.delete-user-by-id.delete-user-by-id uses identity.src.data.repositories.user_repository✕
- Connections
- 1 pair of types, where a type in identity.src.user.features.v1.delete-user-by-id.delete-user-by-id uses a type in identity.src.data.repositories.user_repository.
- The types involved
src.identity.src.user.features.v1.delete-user-by-id.delete-user-by-id.DeleteUserByIdHandler→src.identity.src.data.repositories.user_repository.IUserRepository
- Direction
- identity.src.user.features.v1.delete-user-by-id.delete-user-by-id uses identity.src.data.repositories.user_repository, so a change to identity.src.data.repositories.user_repository can break identity.src.user.features.v1.delete-user-by-id.delete-user-by-id, while a change to identity.src.user.features.v1.delete-user-by-id.delete-user-by-id can't break identity.src.data.repositories.user_repository.
- Position
- Below the diagonal: identity.src.user.features.v1.delete-user-by-id.delete-user-by-id uses a module listed above it, which is the healthy direction.
33→5 identity.src.user.features.v1.get-user-by-id.get-user-by-id uses building-blocks.mediatr-js.mediatr-js✕
- Connections
- 2 pairs of types, where a type in identity.src.user.features.v1.get-user-by-id.get-user-by-id uses a type in building-blocks.mediatr-js.mediatr-js.
- The types involved
src.identity.src.user.features.v1.get-user-by-id.get-user-by-id.GetUserById→src.building-blocks.mediatr-js.mediatr-js.IRequestsrc.identity.src.user.features.v1.get-user-by-id.get-user-by-id.GetUserByIdHandler→src.building-blocks.mediatr-js.mediatr-js.IRequestHandler
- Direction
- identity.src.user.features.v1.get-user-by-id.get-user-by-id uses building-blocks.mediatr-js.mediatr-js, so a change to building-blocks.mediatr-js.mediatr-js can break identity.src.user.features.v1.get-user-by-id.get-user-by-id, while a change to identity.src.user.features.v1.get-user-by-id.get-user-by-id can't break building-blocks.mediatr-js.mediatr-js.
- Position
- Below the diagonal: identity.src.user.features.v1.get-user-by-id.get-user-by-id uses a module listed above it, which is the healthy direction.
33→16 identity.src.user.features.v1.get-user-by-id.get-user-by-id uses identity.src.user.dtos.user_dto✕
- Connections
- 2 pairs of types, where a type in identity.src.user.features.v1.get-user-by-id.get-user-by-id uses a type in identity.src.user.dtos.user_dto.
- The types involved
src.identity.src.user.features.v1.get-user-by-id.get-user-by-id.GetUserByIdController→src.identity.src.user.dtos.user_dto.UserDtosrc.identity.src.user.features.v1.get-user-by-id.get-user-by-id.GetUserByIdHandler→src.identity.src.user.dtos.user_dto.UserDto
- Direction
- identity.src.user.features.v1.get-user-by-id.get-user-by-id uses identity.src.user.dtos.user_dto, so a change to identity.src.user.dtos.user_dto can break identity.src.user.features.v1.get-user-by-id.get-user-by-id, while a change to identity.src.user.features.v1.get-user-by-id.get-user-by-id can't break identity.src.user.dtos.user_dto.
- Position
- Below the diagonal: identity.src.user.features.v1.get-user-by-id.get-user-by-id uses a module listed above it, which is the healthy direction.
33→23 identity.src.user.features.v1.get-user-by-id.get-user-by-id uses identity.src.data.repositories.user_repository✕
- Connections
- 1 pair of types, where a type in identity.src.user.features.v1.get-user-by-id.get-user-by-id uses a type in identity.src.data.repositories.user_repository.
- The types involved
src.identity.src.user.features.v1.get-user-by-id.get-user-by-id.GetUserByIdHandler→src.identity.src.data.repositories.user_repository.IUserRepository
- Direction
- identity.src.user.features.v1.get-user-by-id.get-user-by-id uses identity.src.data.repositories.user_repository, so a change to identity.src.data.repositories.user_repository can break identity.src.user.features.v1.get-user-by-id.get-user-by-id, while a change to identity.src.user.features.v1.get-user-by-id.get-user-by-id can't break identity.src.data.repositories.user_repository.
- Position
- Below the diagonal: identity.src.user.features.v1.get-user-by-id.get-user-by-id uses a module listed above it, which is the healthy direction.
34→5 identity.src.user.features.v1.get-users.get-users uses building-blocks.mediatr-js.mediatr-js✕
- Connections
- 2 pairs of types, where a type in identity.src.user.features.v1.get-users.get-users uses a type in building-blocks.mediatr-js.mediatr-js.
- The types involved
src.identity.src.user.features.v1.get-users.get-users.GetUsers→src.building-blocks.mediatr-js.mediatr-js.IRequestsrc.identity.src.user.features.v1.get-users.get-users.GetUsersHandler→src.building-blocks.mediatr-js.mediatr-js.IRequestHandler
- Direction
- identity.src.user.features.v1.get-users.get-users uses building-blocks.mediatr-js.mediatr-js, so a change to building-blocks.mediatr-js.mediatr-js can break identity.src.user.features.v1.get-users.get-users, while a change to identity.src.user.features.v1.get-users.get-users can't break building-blocks.mediatr-js.mediatr-js.
- Position
- Below the diagonal: identity.src.user.features.v1.get-users.get-users uses a module listed above it, which is the healthy direction.
34→23 identity.src.user.features.v1.get-users.get-users uses identity.src.data.repositories.user_repository✕
- Connections
- 1 pair of types, where a type in identity.src.user.features.v1.get-users.get-users uses a type in identity.src.data.repositories.user_repository.
- The types involved
src.identity.src.user.features.v1.get-users.get-users.GetUsersHandler→src.identity.src.data.repositories.user_repository.IUserRepository
- Direction
- identity.src.user.features.v1.get-users.get-users uses identity.src.data.repositories.user_repository, so a change to identity.src.data.repositories.user_repository can break identity.src.user.features.v1.get-users.get-users, while a change to identity.src.user.features.v1.get-users.get-users can't break identity.src.data.repositories.user_repository.
- Position
- Below the diagonal: identity.src.user.features.v1.get-users.get-users uses a module listed above it, which is the healthy direction.
35→2 identity.src.user.features.v1.update-user.update-user uses building-blocks.contracts.identity_contract✕
- Connections
- 2 pairs of types, where a type in identity.src.user.features.v1.update-user.update-user uses a type in building-blocks.contracts.identity_contract.
- The types involved
src.identity.src.user.features.v1.update-user.update-user.UpdateUser→src.building-blocks.contracts.identity_contract.Rolesrc.identity.src.user.features.v1.update-user.update-user.UpdateUserRequestDto→src.building-blocks.contracts.identity_contract.Role
- Direction
- identity.src.user.features.v1.update-user.update-user uses building-blocks.contracts.identity_contract, so a change to building-blocks.contracts.identity_contract can break identity.src.user.features.v1.update-user.update-user, while a change to identity.src.user.features.v1.update-user.update-user can't break building-blocks.contracts.identity_contract.
- Position
- Below the diagonal: identity.src.user.features.v1.update-user.update-user uses a module listed above it, which is the healthy direction.
35→5 identity.src.user.features.v1.update-user.update-user uses building-blocks.mediatr-js.mediatr-js✕
- Connections
- 2 pairs of types, where a type in identity.src.user.features.v1.update-user.update-user uses a type in building-blocks.mediatr-js.mediatr-js.
- The types involved
src.identity.src.user.features.v1.update-user.update-user.UpdateUser→src.building-blocks.mediatr-js.mediatr-js.IRequestsrc.identity.src.user.features.v1.update-user.update-user.UpdateUserHandler→src.building-blocks.mediatr-js.mediatr-js.IRequestHandler
- Direction
- identity.src.user.features.v1.update-user.update-user uses building-blocks.mediatr-js.mediatr-js, so a change to building-blocks.mediatr-js.mediatr-js can break identity.src.user.features.v1.update-user.update-user, while a change to identity.src.user.features.v1.update-user.update-user can't break building-blocks.mediatr-js.mediatr-js.
- Position
- Below the diagonal: identity.src.user.features.v1.update-user.update-user uses a module listed above it, which is the healthy direction.
35→7 identity.src.user.features.v1.update-user.update-user uses building-blocks.rabbitmq.rabbitmq-publisher✕
- Connections
- 1 pair of types, where a type in identity.src.user.features.v1.update-user.update-user uses a type in building-blocks.rabbitmq.rabbitmq-publisher.
- The types involved
src.identity.src.user.features.v1.update-user.update-user.UpdateUserHandler→src.building-blocks.rabbitmq.rabbitmq-publisher.IPublisher
- Direction
- identity.src.user.features.v1.update-user.update-user uses building-blocks.rabbitmq.rabbitmq-publisher, so a change to building-blocks.rabbitmq.rabbitmq-publisher can break identity.src.user.features.v1.update-user.update-user, while a change to identity.src.user.features.v1.update-user.update-user can't break building-blocks.rabbitmq.rabbitmq-publisher.
- Position
- Below the diagonal: identity.src.user.features.v1.update-user.update-user uses a module listed above it, which is the healthy direction.
35→23 identity.src.user.features.v1.update-user.update-user uses identity.src.data.repositories.user_repository✕
- Connections
- 1 pair of types, where a type in identity.src.user.features.v1.update-user.update-user uses a type in identity.src.data.repositories.user_repository.
- The types involved
src.identity.src.user.features.v1.update-user.update-user.UpdateUserHandler→src.identity.src.data.repositories.user_repository.IUserRepository
- Direction
- identity.src.user.features.v1.update-user.update-user uses identity.src.data.repositories.user_repository, so a change to identity.src.data.repositories.user_repository can break identity.src.user.features.v1.update-user.update-user, while a change to identity.src.user.features.v1.update-user.update-user can't break identity.src.data.repositories.user_repository.
- Position
- Below the diagonal: identity.src.user.features.v1.update-user.update-user uses a module listed above it, which is the healthy direction.
36→1 flight.src.seat.features.v1.create-seat.create-seat uses building-blocks.contracts.flight_contract✕
- Connections
- 6 pairs of types, where a type in flight.src.seat.features.v1.create-seat.create-seat uses a type in building-blocks.contracts.flight_contract.
- The types involved
src.flight.src.seat.features.v1.create-seat.create-seat.CreateSeat→src.building-blocks.contracts.flight_contract.SeatClasssrc.flight.src.seat.features.v1.create-seat.create-seat.CreateSeat→src.building-blocks.contracts.flight_contract.SeatTypesrc.flight.src.seat.features.v1.create-seat.create-seat.CreateSeatController→src.building-blocks.contracts.flight_contract.SeatDtosrc.flight.src.seat.features.v1.create-seat.create-seat.CreateSeatHandler→src.building-blocks.contracts.flight_contract.SeatDtosrc.flight.src.seat.features.v1.create-seat.create-seat.CreateSeatRequestDto→src.building-blocks.contracts.flight_contract.SeatClasssrc.flight.src.seat.features.v1.create-seat.create-seat.CreateSeatRequestDto→src.building-blocks.contracts.flight_contract.SeatType
- Direction
- flight.src.seat.features.v1.create-seat.create-seat uses building-blocks.contracts.flight_contract, so a change to building-blocks.contracts.flight_contract can break flight.src.seat.features.v1.create-seat.create-seat, while a change to flight.src.seat.features.v1.create-seat.create-seat can't break building-blocks.contracts.flight_contract.
- Position
- Below the diagonal: flight.src.seat.features.v1.create-seat.create-seat uses a module listed above it, which is the healthy direction.
36→5 flight.src.seat.features.v1.create-seat.create-seat uses building-blocks.mediatr-js.mediatr-js✕
- Connections
- 2 pairs of types, where a type in flight.src.seat.features.v1.create-seat.create-seat uses a type in building-blocks.mediatr-js.mediatr-js.
- The types involved
src.flight.src.seat.features.v1.create-seat.create-seat.CreateSeat→src.building-blocks.mediatr-js.mediatr-js.IRequestsrc.flight.src.seat.features.v1.create-seat.create-seat.CreateSeatHandler→src.building-blocks.mediatr-js.mediatr-js.IRequestHandler
- Direction
- flight.src.seat.features.v1.create-seat.create-seat uses building-blocks.mediatr-js.mediatr-js, so a change to building-blocks.mediatr-js.mediatr-js can break flight.src.seat.features.v1.create-seat.create-seat, while a change to flight.src.seat.features.v1.create-seat.create-seat can't break building-blocks.mediatr-js.mediatr-js.
- Position
- Below the diagonal: flight.src.seat.features.v1.create-seat.create-seat uses a module listed above it, which is the healthy direction.
36→7 flight.src.seat.features.v1.create-seat.create-seat uses building-blocks.rabbitmq.rabbitmq-publisher✕
- Connections
- 1 pair of types, where a type in flight.src.seat.features.v1.create-seat.create-seat uses a type in building-blocks.rabbitmq.rabbitmq-publisher.
- The types involved
src.flight.src.seat.features.v1.create-seat.create-seat.CreateSeatHandler→src.building-blocks.rabbitmq.rabbitmq-publisher.IPublisher
- Direction
- flight.src.seat.features.v1.create-seat.create-seat uses building-blocks.rabbitmq.rabbitmq-publisher, so a change to building-blocks.rabbitmq.rabbitmq-publisher can break flight.src.seat.features.v1.create-seat.create-seat, while a change to flight.src.seat.features.v1.create-seat.create-seat can't break building-blocks.rabbitmq.rabbitmq-publisher.
- Position
- Below the diagonal: flight.src.seat.features.v1.create-seat.create-seat uses a module listed above it, which is the healthy direction.
36→19 flight.src.seat.features.v1.create-seat.create-seat uses flight.src.data.repositories.flight_repository✕
- Connections
- 1 pair of types, where a type in flight.src.seat.features.v1.create-seat.create-seat uses a type in flight.src.data.repositories.flight_repository.
- The types involved
src.flight.src.seat.features.v1.create-seat.create-seat.CreateSeatHandler→src.flight.src.data.repositories.flight_repository.IFlightRepository
- Direction
- flight.src.seat.features.v1.create-seat.create-seat uses flight.src.data.repositories.flight_repository, so a change to flight.src.data.repositories.flight_repository can break flight.src.seat.features.v1.create-seat.create-seat, while a change to flight.src.seat.features.v1.create-seat.create-seat can't break flight.src.data.repositories.flight_repository.
- Position
- Below the diagonal: flight.src.seat.features.v1.create-seat.create-seat uses a module listed above it, which is the healthy direction.
36→26 flight.src.seat.features.v1.create-seat.create-seat uses flight.src.data.repositories.seat_repository✕
- Connections
- 1 pair of types, where a type in flight.src.seat.features.v1.create-seat.create-seat uses a type in flight.src.data.repositories.seat_repository.
- The types involved
src.flight.src.seat.features.v1.create-seat.create-seat.CreateSeatHandler→src.flight.src.data.repositories.seat_repository.ISeatRepository
- Direction
- flight.src.seat.features.v1.create-seat.create-seat uses flight.src.data.repositories.seat_repository, so a change to flight.src.data.repositories.seat_repository can break flight.src.seat.features.v1.create-seat.create-seat, while a change to flight.src.seat.features.v1.create-seat.create-seat can't break flight.src.data.repositories.seat_repository.
- Position
- Below the diagonal: flight.src.seat.features.v1.create-seat.create-seat uses a module listed above it, which is the healthy direction.
37→1 flight.src.seat.features.v1.reserve-seat.reserve-seat uses building-blocks.contracts.flight_contract✕
- Connections
- 3 pairs of types, where a type in flight.src.seat.features.v1.reserve-seat.reserve-seat uses a type in building-blocks.contracts.flight_contract.
- The types involved
src.flight.src.seat.features.v1.reserve-seat.reserve-seat.ReserveSeatController→src.building-blocks.contracts.flight_contract.ReserveSeatRequestDtosrc.flight.src.seat.features.v1.reserve-seat.reserve-seat.ReserveSeatHandler→src.building-blocks.contracts.flight_contract.SeatDtosrc.flight.src.seat.features.v1.reserve-seat.reserve-seat.ReserveSeatRequestDto→src.building-blocks.contracts.flight_contract.ReserveSeatRequestDto
- Direction
- flight.src.seat.features.v1.reserve-seat.reserve-seat uses building-blocks.contracts.flight_contract, so a change to building-blocks.contracts.flight_contract can break flight.src.seat.features.v1.reserve-seat.reserve-seat, while a change to flight.src.seat.features.v1.reserve-seat.reserve-seat can't break building-blocks.contracts.flight_contract.
- Position
- Below the diagonal: flight.src.seat.features.v1.reserve-seat.reserve-seat uses a module listed above it, which is the healthy direction.
37→5 flight.src.seat.features.v1.reserve-seat.reserve-seat uses building-blocks.mediatr-js.mediatr-js✕
- Connections
- 2 pairs of types, where a type in flight.src.seat.features.v1.reserve-seat.reserve-seat uses a type in building-blocks.mediatr-js.mediatr-js.
- The types involved
src.flight.src.seat.features.v1.reserve-seat.reserve-seat.ReserveSeat→src.building-blocks.mediatr-js.mediatr-js.IRequestsrc.flight.src.seat.features.v1.reserve-seat.reserve-seat.ReserveSeatHandler→src.building-blocks.mediatr-js.mediatr-js.IRequestHandler
- Direction
- flight.src.seat.features.v1.reserve-seat.reserve-seat uses building-blocks.mediatr-js.mediatr-js, so a change to building-blocks.mediatr-js.mediatr-js can break flight.src.seat.features.v1.reserve-seat.reserve-seat, while a change to flight.src.seat.features.v1.reserve-seat.reserve-seat can't break building-blocks.mediatr-js.mediatr-js.
- Position
- Below the diagonal: flight.src.seat.features.v1.reserve-seat.reserve-seat uses a module listed above it, which is the healthy direction.
37→7 flight.src.seat.features.v1.reserve-seat.reserve-seat uses building-blocks.rabbitmq.rabbitmq-publisher✕
- Connections
- 1 pair of types, where a type in flight.src.seat.features.v1.reserve-seat.reserve-seat uses a type in building-blocks.rabbitmq.rabbitmq-publisher.
- The types involved
src.flight.src.seat.features.v1.reserve-seat.reserve-seat.ReserveSeatHandler→src.building-blocks.rabbitmq.rabbitmq-publisher.IPublisher
- Direction
- flight.src.seat.features.v1.reserve-seat.reserve-seat uses building-blocks.rabbitmq.rabbitmq-publisher, so a change to building-blocks.rabbitmq.rabbitmq-publisher can break flight.src.seat.features.v1.reserve-seat.reserve-seat, while a change to flight.src.seat.features.v1.reserve-seat.reserve-seat can't break building-blocks.rabbitmq.rabbitmq-publisher.
- Position
- Below the diagonal: flight.src.seat.features.v1.reserve-seat.reserve-seat uses a module listed above it, which is the healthy direction.
37→19 flight.src.seat.features.v1.reserve-seat.reserve-seat uses flight.src.data.repositories.flight_repository✕
- Connections
- 1 pair of types, where a type in flight.src.seat.features.v1.reserve-seat.reserve-seat uses a type in flight.src.data.repositories.flight_repository.
- The types involved
src.flight.src.seat.features.v1.reserve-seat.reserve-seat.ReserveSeatHandler→src.flight.src.data.repositories.flight_repository.IFlightRepository
- Direction
- flight.src.seat.features.v1.reserve-seat.reserve-seat uses flight.src.data.repositories.flight_repository, so a change to flight.src.data.repositories.flight_repository can break flight.src.seat.features.v1.reserve-seat.reserve-seat, while a change to flight.src.seat.features.v1.reserve-seat.reserve-seat can't break flight.src.data.repositories.flight_repository.
- Position
- Below the diagonal: flight.src.seat.features.v1.reserve-seat.reserve-seat uses a module listed above it, which is the healthy direction.
37→21 flight.src.seat.features.v1.reserve-seat.reserve-seat uses flight.src.seat.entities.seat_entity✕
- Connections
- 1 pair of types, where a type in flight.src.seat.features.v1.reserve-seat.reserve-seat uses a type in flight.src.seat.entities.seat_entity.
- The types involved
src.flight.src.seat.features.v1.reserve-seat.reserve-seat.ReserveSeatController→src.flight.src.seat.entities.seat_entity.Seat
- Direction
- flight.src.seat.features.v1.reserve-seat.reserve-seat uses flight.src.seat.entities.seat_entity, so a change to flight.src.seat.entities.seat_entity can break flight.src.seat.features.v1.reserve-seat.reserve-seat, while a change to flight.src.seat.features.v1.reserve-seat.reserve-seat can't break flight.src.seat.entities.seat_entity.
- Position
- Below the diagonal: flight.src.seat.features.v1.reserve-seat.reserve-seat uses a module listed above it, which is the healthy direction.
37→26 flight.src.seat.features.v1.reserve-seat.reserve-seat uses flight.src.data.repositories.seat_repository✕
- Connections
- 1 pair of types, where a type in flight.src.seat.features.v1.reserve-seat.reserve-seat uses a type in flight.src.data.repositories.seat_repository.
- The types involved
src.flight.src.seat.features.v1.reserve-seat.reserve-seat.ReserveSeatHandler→src.flight.src.data.repositories.seat_repository.ISeatRepository
- Direction
- flight.src.seat.features.v1.reserve-seat.reserve-seat uses flight.src.data.repositories.seat_repository, so a change to flight.src.data.repositories.seat_repository can break flight.src.seat.features.v1.reserve-seat.reserve-seat, while a change to flight.src.seat.features.v1.reserve-seat.reserve-seat can't break flight.src.data.repositories.seat_repository.
- Position
- Below the diagonal: flight.src.seat.features.v1.reserve-seat.reserve-seat uses a module listed above it, which is the healthy direction.
38→5 identity.src.auth.features.v1.generate-token.generate-token uses building-blocks.mediatr-js.mediatr-js✕
- Connections
- 2 pairs of types, where a type in identity.src.auth.features.v1.generate-token.generate-token uses a type in building-blocks.mediatr-js.mediatr-js.
- The types involved
src.identity.src.auth.features.v1.generate-token.generate-token.GenerateToken→src.building-blocks.mediatr-js.mediatr-js.IRequestsrc.identity.src.auth.features.v1.generate-token.generate-token.GenerateTokenHandler→src.building-blocks.mediatr-js.mediatr-js.IRequestHandler
- Direction
- identity.src.auth.features.v1.generate-token.generate-token uses building-blocks.mediatr-js.mediatr-js, so a change to building-blocks.mediatr-js.mediatr-js can break identity.src.auth.features.v1.generate-token.generate-token, while a change to identity.src.auth.features.v1.generate-token.generate-token can't break building-blocks.mediatr-js.mediatr-js.
- Position
- Below the diagonal: identity.src.auth.features.v1.generate-token.generate-token uses a module listed above it, which is the healthy direction.
38→8 identity.src.auth.features.v1.generate-token.generate-token uses identity.src.auth.dtos.auth_dto✕
- Connections
- 1 pair of types, where a type in identity.src.auth.features.v1.generate-token.generate-token uses a type in identity.src.auth.dtos.auth_dto.
- The types involved
src.identity.src.auth.features.v1.generate-token.generate-token.GenerateTokenHandler→src.identity.src.auth.dtos.auth_dto.AuthDto
- Direction
- identity.src.auth.features.v1.generate-token.generate-token uses identity.src.auth.dtos.auth_dto, so a change to identity.src.auth.dtos.auth_dto can break identity.src.auth.features.v1.generate-token.generate-token, while a change to identity.src.auth.features.v1.generate-token.generate-token can't break identity.src.auth.dtos.auth_dto.
- Position
- Below the diagonal: identity.src.auth.features.v1.generate-token.generate-token uses a module listed above it, which is the healthy direction.
38→30 identity.src.auth.features.v1.generate-token.generate-token uses identity.src.data.repositories.auth_repository✕
- Connections
- 1 pair of types, where a type in identity.src.auth.features.v1.generate-token.generate-token uses a type in identity.src.data.repositories.auth_repository.
- The types involved
src.identity.src.auth.features.v1.generate-token.generate-token.GenerateTokenHandler→src.identity.src.data.repositories.auth_repository.IAuthRepository
- Direction
- identity.src.auth.features.v1.generate-token.generate-token uses identity.src.data.repositories.auth_repository, so a change to identity.src.data.repositories.auth_repository can break identity.src.auth.features.v1.generate-token.generate-token, while a change to identity.src.auth.features.v1.generate-token.generate-token can't break identity.src.data.repositories.auth_repository.
- Position
- Below the diagonal: identity.src.auth.features.v1.generate-token.generate-token uses a module listed above it, which is the healthy direction.
39→5 identity.src.auth.features.v1.refresh-token.refresh-token uses building-blocks.mediatr-js.mediatr-js✕
- Connections
- 2 pairs of types, where a type in identity.src.auth.features.v1.refresh-token.refresh-token uses a type in building-blocks.mediatr-js.mediatr-js.
- The types involved
src.identity.src.auth.features.v1.refresh-token.refresh-token.RefreshToken→src.building-blocks.mediatr-js.mediatr-js.IRequestsrc.identity.src.auth.features.v1.refresh-token.refresh-token.RefreshTokenHandler→src.building-blocks.mediatr-js.mediatr-js.IRequestHandler
- Direction
- identity.src.auth.features.v1.refresh-token.refresh-token uses building-blocks.mediatr-js.mediatr-js, so a change to building-blocks.mediatr-js.mediatr-js can break identity.src.auth.features.v1.refresh-token.refresh-token, while a change to identity.src.auth.features.v1.refresh-token.refresh-token can't break building-blocks.mediatr-js.mediatr-js.
- Position
- Below the diagonal: identity.src.auth.features.v1.refresh-token.refresh-token uses a module listed above it, which is the healthy direction.
39→8 identity.src.auth.features.v1.refresh-token.refresh-token uses identity.src.auth.dtos.auth_dto✕
- Connections
- 2 pairs of types, where a type in identity.src.auth.features.v1.refresh-token.refresh-token uses a type in identity.src.auth.dtos.auth_dto.
- The types involved
src.identity.src.auth.features.v1.refresh-token.refresh-token.RefreshTokenController→src.identity.src.auth.dtos.auth_dto.AuthDtosrc.identity.src.auth.features.v1.refresh-token.refresh-token.RefreshTokenHandler→src.identity.src.auth.dtos.auth_dto.AuthDto
- Direction
- identity.src.auth.features.v1.refresh-token.refresh-token uses identity.src.auth.dtos.auth_dto, so a change to identity.src.auth.dtos.auth_dto can break identity.src.auth.features.v1.refresh-token.refresh-token, while a change to identity.src.auth.features.v1.refresh-token.refresh-token can't break identity.src.auth.dtos.auth_dto.
- Position
- Below the diagonal: identity.src.auth.features.v1.refresh-token.refresh-token uses a module listed above it, which is the healthy direction.
39→30 identity.src.auth.features.v1.refresh-token.refresh-token uses identity.src.data.repositories.auth_repository✕
- Connections
- 1 pair of types, where a type in identity.src.auth.features.v1.refresh-token.refresh-token uses a type in identity.src.data.repositories.auth_repository.
- The types involved
src.identity.src.auth.features.v1.refresh-token.refresh-token.RefreshTokenHandler→src.identity.src.data.repositories.auth_repository.IAuthRepository
- Direction
- identity.src.auth.features.v1.refresh-token.refresh-token uses identity.src.data.repositories.auth_repository, so a change to identity.src.data.repositories.auth_repository can break identity.src.auth.features.v1.refresh-token.refresh-token, while a change to identity.src.auth.features.v1.refresh-token.refresh-token can't break identity.src.data.repositories.auth_repository.
- Position
- Below the diagonal: identity.src.auth.features.v1.refresh-token.refresh-token uses a module listed above it, which is the healthy direction.
40→5 identity.src.auth.features.v1.validate-token.validate-token uses building-blocks.mediatr-js.mediatr-js✕
- Connections
- 2 pairs of types, where a type in identity.src.auth.features.v1.validate-token.validate-token uses a type in building-blocks.mediatr-js.mediatr-js.
- The types involved
src.identity.src.auth.features.v1.validate-token.validate-token.ValidateToken→src.building-blocks.mediatr-js.mediatr-js.IRequestsrc.identity.src.auth.features.v1.validate-token.validate-token.ValidateTokenHandler→src.building-blocks.mediatr-js.mediatr-js.IRequestHandler
- Direction
- identity.src.auth.features.v1.validate-token.validate-token uses building-blocks.mediatr-js.mediatr-js, so a change to building-blocks.mediatr-js.mediatr-js can break identity.src.auth.features.v1.validate-token.validate-token, while a change to identity.src.auth.features.v1.validate-token.validate-token can't break building-blocks.mediatr-js.mediatr-js.
- Position
- Below the diagonal: identity.src.auth.features.v1.validate-token.validate-token uses a module listed above it, which is the healthy direction.
40→9 identity.src.auth.features.v1.validate-token.validate-token uses identity.src.auth.enums.token-type_enum✕
- Connections
- 1 pair of types, where a type in identity.src.auth.features.v1.validate-token.validate-token uses a type in identity.src.auth.enums.token-type_enum.
- The types involved
src.identity.src.auth.features.v1.validate-token.validate-token.ValidateToken→src.identity.src.auth.enums.token-type_enum.TokenType
- Direction
- identity.src.auth.features.v1.validate-token.validate-token uses identity.src.auth.enums.token-type_enum, so a change to identity.src.auth.enums.token-type_enum can break identity.src.auth.features.v1.validate-token.validate-token, while a change to identity.src.auth.features.v1.validate-token.validate-token can't break identity.src.auth.enums.token-type_enum.
- Position
- Below the diagonal: identity.src.auth.features.v1.validate-token.validate-token uses a module listed above it, which is the healthy direction.
40→22 identity.src.auth.features.v1.validate-token.validate-token uses identity.src.auth.entities.token_entity✕
- Connections
- 1 pair of types, where a type in identity.src.auth.features.v1.validate-token.validate-token uses a type in identity.src.auth.entities.token_entity.
- The types involved
src.identity.src.auth.features.v1.validate-token.validate-token.ValidateTokenHandler→src.identity.src.auth.entities.token_entity.Token
- Direction
- identity.src.auth.features.v1.validate-token.validate-token uses identity.src.auth.entities.token_entity, so a change to identity.src.auth.entities.token_entity can break identity.src.auth.features.v1.validate-token.validate-token, while a change to identity.src.auth.features.v1.validate-token.validate-token can't break identity.src.auth.entities.token_entity.
- Position
- Below the diagonal: identity.src.auth.features.v1.validate-token.validate-token uses a module listed above it, which is the healthy direction.
40→30 identity.src.auth.features.v1.validate-token.validate-token uses identity.src.data.repositories.auth_repository✕
- Connections
- 1 pair of types, where a type in identity.src.auth.features.v1.validate-token.validate-token uses a type in identity.src.data.repositories.auth_repository.
- The types involved
src.identity.src.auth.features.v1.validate-token.validate-token.ValidateTokenHandler→src.identity.src.data.repositories.auth_repository.IAuthRepository
- Direction
- identity.src.auth.features.v1.validate-token.validate-token uses identity.src.data.repositories.auth_repository, so a change to identity.src.data.repositories.auth_repository can break identity.src.auth.features.v1.validate-token.validate-token, while a change to identity.src.auth.features.v1.validate-token.validate-token can't break identity.src.data.repositories.auth_repository.
- Position
- Below the diagonal: identity.src.auth.features.v1.validate-token.validate-token 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 306 | High / Critical |
| A05:2025 — Injection | 20 | High / Critical |
| A07:2025 — Authentication Failures | 9 | High / Critical |
Roadmap
Top priorities: Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository); Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4); Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, Azure Key Vault, GCP KMS / REDACTED Manager, HashiCorp Vault) and encrypt the most sensitive columns (typeorm-encrypted, prisma-field-encryption, mongoose-field-encryption or MongoDB CSFLE) — partial coverage still leaves gaps.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4). | +8.9 pts | Low | REDACTED Scanning |
| Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository). | +15.4 pts | Medium | Domain ↔ infrastructure boundary |
| Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, Azure Key Vault, GCP KMS / REDACTED Manager, HashiCorp Vault) and encrypt the most sensitive columns (typeorm-encrypted, prisma-field-encryption, mongoose-field-encryption or MongoDB CSFLE) — partial coverage still leaves gaps. | +2.7 pts | Medium | Data Protection |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +2.2 pts | Medium | Security & performance tooling |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +2.2 pts | Medium | DR & Backup |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +2.2 pts | Medium | Dependency Hygiene |
| Resolve the 1 No network policy finding(s) in Network Egress Confinement. | +0.9 pts | Low | Network Egress Confinement |
| Resolve the 9 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED, REDACTED, REDACTED. | +0.9 pts | Low | Kernel & Syscall Confinement |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.6 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 1.3 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 6.1 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.1 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.1 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.1 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 76 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 76 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 524 of 539 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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not scored — the JavaScript/TypeScript suite (jest via `npm install --ignore-scripts` (no lockfile) in src/booking/ (0 tests); jest via `npm install --ignore-scripts` (no lockfile) in src/flight/ (0 tests); jest via `npm install --ignore-scripts` (no lockfile) in src/passenger/ (0 tests)) ran but surfaced no test cases to the runner, so flakiness couldn't be exercised.
- 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. Not scored — 179 production npm declaration(s) across 5 package.json (5 of them the product) were read for PINNING discipline (1 defect(s) reported), but the outdated/deprecated signal needs registry.npmjs.org, and no committed lockfile here resolves to the concrete versions that question is asked about, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares package.json manifests but commits no lockfile this pass can resolve (npm, pnpm, yarn and bun each write a different one, and `bun.lockb` is a binary format with no published shape), so the set of packages it actually ships is not resolvable from the checkout: its declarations carry version RANGES, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. Commit the lock and this dimension grades its production dependencies against registry.npmjs.org. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 170 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 1 hold 2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (src/passenger/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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 scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- 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/building-blocks/logging/logger.js`, `src/identity/jest.config.ts` 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.
- D43 Malicious Dependencies — measured, with a gap in what it reached — 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 scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is tsyringe, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — time="2026-11-08T01:13:06Z" level=warning msg="The \"FLIGHT_PORT\" variable is not set. Defaulting to a blank string." time="2026-11-08T01:13:06Z" level=warning msg="The \"POSTGRES_PORT\" variable is not set. Defaulting to a blank string." failed to solve: process "/bin/sh -c npm install" did not complete successfully: exit code: 1; runtime evidence skipped.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- ED5 Idempotency — 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 classifies a mutation as idempotent when a guard is visible (an exists check, an upsert, an idempotency key or inbox, a versioned or fixed-value write) and as at risk only on positive evidence that a re-run double-applies it (a fresh-identity insert, an accumulation, a growing collection, an unkeyed outbound send or charge). The rest show neither, and they are the majority here, so a score over the classified minority would not describe this repository. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- R4 Test Coverage — 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. 43 further occurrence(s) are not listed individually; the score already reflects all 83.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- 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.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- 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.
- D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
- D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
- 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.
- 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.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was REDACTED.expressAuthentication at 29.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with REDACTED.expressAuthentication (cognitive 29). — Refactoring it lifts Cognitive Complexity from 9.2 to about 10.0/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D5 · Coupling
5 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- 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 12 classes have LCOM4 above 3.
D9 · Test Distribution
3 test methods: 3 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 3 `it`/`test` case(s) across 3 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3 tests.
D13 · REDACTED Scanning
2 secret(s) detected.
What to do
- Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 4879 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 6 document(s) read across 6 unit(s).
D26 · Project Cohesion
0 of 5 build units (npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
4 finding(s): 0 critical, 4 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 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 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)
20 finding(s): 0 critical, 4 high, 16 medium, 0 low. 3 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 5 file(s) — `REDACTED` (lines 85–116), `src/building-blocks/logging/logger.js` (line 56, line 57, line 65, …), `REDACTED` (lines 84–115), `src/identity/jest.config.ts` (line 9), `REDACTED` (lines 84–115) — 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 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 3 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 (3 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D31 · IaC & Container Security
306 finding(s): 0 critical, 23 high, 238 medium, 45 low.
What to do
- Resolve the 238 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (26), REDACTED (26), REDACTED (26). — One of this dimension's main actionable groups (238 warning-level).
- Resolve the 23 High IaC finding(s) in IaC & Container Security — start with REDACTED (12), REDACTED, REDACTED. — One of this dimension's main actionable groups (23 issue-level).
- Resolve the 45 Low IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED (5), REDACTED (5). — One of this dimension's main actionable groups (45 recommendation-level).
D34 · Knowledge Freshness
19 of 19 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/building-blocks/logging/logger.ts. Counted over 19 of the 148 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 19 Orphaned file finding(s) in Knowledge Freshness — start with logger.ts, create-flight.ts, config.ts. — One of this dimension's main actionable groups (19 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.
D40 · Network Egress Confinement
0/2 network-egress controls present (network policy, egress restriction).
What to do
- Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
D41 · Kernel & Syscall Confinement
0/9 workload(s) run every container under a seccomp profile; 0/9 declare an AppArmor/SELinux profile.
What to do
- Resolve the 9 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (9 recommendation-level).
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
AX9 · CQS / query purity
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, Azure Key Vault, GCP KMS / REDACTED Manager, HashiCorp Vault) and encrypt the most sensitive columns (typeorm-encrypted, prisma-field-encryption, mongoose-field-encryption or MongoDB CSFLE) — partial coverage still leaves gaps.
- Enforce HTTPS (serve through https.createServer / NestJS httpsOptions, or redirect plain HTTP with express-sslify behind your TLS terminator) so data in transit is always encrypted.
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect. — REDACTED:47
What to do
- Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
DM6 · Domain ↔ infrastructure boundary
- Booking is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. — src/booking/src/booking/entities/booking.entity.ts:3
- Airport is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. — src/flight/src/airport/entities/airport.entity.ts:4
- Seat is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. — src/flight/src/seat/entities/seat.entity.ts:6
- Flight is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. — src/flight/src/flight/entities/flight.entity.ts:13
- Aircraft is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. — src/flight/src/aircraft/entities/aircraft.entity.ts:4
- Token is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. — src/identity/src/auth/entities/token.entity.ts:5
- User is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. — src/identity/src/user/entities/user.entity.ts:5
- Passenger is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. — src/passenger/src/passenger/entities/passenger.entity.ts:4
What to do
- Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `registerRepositories` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×4) — src/booking/src/extensions/repository.extensions.ts:4, src/flight/src/extensions/repository.extensions.ts:7, src/identity/src/extensions/repository.extensions.ts:5, …
What to do
- Remove the dead code that still moves this score: delete dead if(false) branches and either do the real async work or drop the async keyword from fake-async functions.
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 a README to the 5 of 5 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.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- `src/building-blocks/open-telemetry/open-telemetry.ts` reports through `console.*` at line 51 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/building-blocks/open-telemetry/open-telemetry.ts:51
- `src/building-blocks/open-telemetry/open-telemetry.ts` reports through `console.*` at line 52 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/building-blocks/open-telemetry/open-telemetry.ts:52
- `src/building-blocks/open-telemetry/open-telemetry.ts` reports through `console.*` at line 58 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/building-blocks/open-telemetry/open-telemetry.ts:58
- `src/building-blocks/open-telemetry/open-telemetry.js` reports through `console.*` at line 45 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/building-blocks/open-telemetry/open-telemetry.js:45
- `src/building-blocks/open-telemetry/open-telemetry.js` reports through `console.*` at line 49 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/building-blocks/open-telemetry/open-telemetry.js:49
What to do
- Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 1559 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
- `src/booking/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/booking/package.json:20
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — 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
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
P8 · Schema migrations
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 47 duplicated blocks under src/ have copies in at least two of the sibling directories booking, building-blocks, flight, identity, passenger — 24 of them are reported below, and 23 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 47 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 47 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 47 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/identity/src/user/features/v1/get-users/get-users.ts:11
- src/flight/src/aircraft/features/v1/create-aircraft/create-aircraft.ts:14 · src/flight/src/airport/features/v1/create-airport/create-airport.ts:14 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/flight/src/aircraft/features/v1/create-aircraft/create-aircraft.ts:14
- src/identity/src/user/features/v1/get-users/get-users.ts:11 · src/passenger/src/passenger/features/v1/get-passengers/get-passengers.ts:11 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/identity/src/user/features/v1/get-users/get-users.ts:11
- REDACTED:1 · REDACTED:1 · REDACTED:1 · REDACTED:1 — these 4 files are line-for-line copies of one another — 52 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — REDACTED:1
- src/booking/src/booking/features/v1/create-booking/create-booking.ts:16 · src/flight/src/aircraft/features/v1/create-aircraft/create-aircraft.ts:14 · src/flight/src/airport/features/v1/create-airport/create-airport.ts:14 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/booking/src/booking/features/v1/create-booking/create-booking.ts:16
- src/flight/src/seat/features/v1/create-seat/create-seat.ts:47 · src/flight/src/seat/features/v1/reserve-seat/reserve-seat.ts:35 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/flight/src/seat/features/v1/create-seat/create-seat.ts:47
- src/flight/src/flight/features/v1/create-flight/create-flight.ts:67 · src/identity/src/user/features/v1/create-user/create-user.ts:46 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/flight/src/flight/features/v1/create-flight/create-flight.ts:67
- src/flight/src/flight/features/v1/get-flight-by-id/get-flight-by-id.ts:11 · src/passenger/src/passenger/features/v1/get-passenger-by-id/get-passenger-by-id.ts:11 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/flight/src/flight/features/v1/get-flight-by-id/get-flight-by-id.ts:11
- src/building-blocks/rabbitmq/rabbitmq-consumer.ts:14 · src/building-blocks/rabbitmq/rabbitmq-publisher.ts:13 — the two spans are one implementation copied and then locally edited — 224 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/building-blocks/rabbitmq/rabbitmq-consumer.ts:14
- src/identity/src/user/features/v1/create-user/create-user.ts:18 · src/identity/src/user/features/v1/update-user/update-user.ts:18 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/identity/src/user/features/v1/create-user/create-user.ts:18
- src/booking/src/booking/mappings.ts:5 · src/flight/src/seat/mappings.ts:5 · src/identity/src/user/mapping.ts:5 — the 3 copies are spread across 3 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — src/booking/src/booking/mappings.ts:5
- src/identity/src/user/features/v1/delete-user-by-id/delete-user-by-id.ts:14 · src/identity/src/user/features/v1/get-user-by-id/get-user-by-id.ts:11 · src/passenger/src/passenger/features/v1/get-passenger-by-id/get-passenger-by-id.ts:11 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/identity/src/user/features/v1/delete-user-by-id/delete-user-by-id.ts:14
- src/identity/src/data/repositories/user.repository.ts:45 · src/passenger/src/data/repositories/passenger.repository.ts:35 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/identity/src/data/repositories/user.repository.ts:45
- src/booking/src/booking/http-client/services/flight/flight.client.ts:17 · src/booking/src/booking/http-client/services/passenger/passenger.client.ts:8 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/booking/src/booking/http-client/services/flight/flight.client.ts:17
- src/flight/src/aircraft/entities/aircraft.entity.ts:4 · src/flight/src/airport/entities/airport.entity.ts:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/flight/src/aircraft/entities/aircraft.entity.ts:4
- src/flight/src/aircraft/mappings.ts:5 · src/flight/src/airport/mappings.ts:5 · src/flight/src/flight/mappings.ts:5 · src/flight/src/seat/mappings.ts:5 · +2 more site(s) not listed — the 6 copies are spread across 6 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — src/flight/src/aircraft/mappings.ts:5
- src/flight/src/flight/entities/flight.entity.ts:15 · src/identity/src/user/entities/user.entity.ts:13 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/flight/src/flight/entities/flight.entity.ts:15
- src/flight/src/flight/features/v1/get-flight-by-id/get-flight-by-id.ts:11 · src/flight/src/seat/features/v1/get-available-seats/get-available-seats.ts:10 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/flight/src/flight/features/v1/get-flight-by-id/get-flight-by-id.ts:11
- src/identity/src/user/entities/user.entity.ts:10 · src/passenger/src/passenger/entities/passenger.entity.ts:6 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/identity/src/user/entities/user.entity.ts:10
- src/booking/src/booking/mappings.ts:50 · src/flight/src/aircraft/mappings.ts:26 · src/flight/src/airport/mappings.ts:26 · src/flight/src/flight/mappings.ts:58 · +2 more site(s) not listed — the 6 copies are spread across 6 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/booking/src/booking/mappings.ts:50
- src/building-blocks/types/exception/application.exception.ts:7 · src/building-blocks/types/exception/conflict.exception.ts:7 · src/building-blocks/types/exception/forbidden.exception.ts:7 · src/building-blocks/types/exception/http-client.exception.ts:7 · +2 more site(s) not listed — the 6 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 6 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/building-blocks/types/exception/application.exception.ts:7
- src/flight/src/data/db.context.ts:9 · src/identity/src/data/db.context.ts:9 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/flight/src/data/db.context.ts:9
- src/identity/src/auth/features/v1/login/login.ts:33 · src/identity/src/auth/features/v1/refresh-token/refresh-token.ts:25 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/identity/src/auth/features/v1/login/login.ts:33
- src/booking/src/booking/entities/booking.entity.ts:1 · src/flight/src/aircraft/entities/aircraft.entity.ts:2 · src/flight/src/airport/entities/airport.entity.ts:2 · src/identity/src/auth/entities/token.entity.ts:3 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/booking/src/booking/entities/booking.entity.ts:1
- src/booking/src/extensions/rabbitmq.extensions.ts:6 · src/flight/src/extensions/rabbitmq.extensions.ts:6 · src/identity/src/extensions/rabbitmq.extensions.ts:6 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/booking/src/extensions/rabbitmq.extensions.ts:6
- src/booking/src/extensions/rabbitmq.extensions.ts:2 · src/flight/src/extensions/rabbitmq.extensions.ts:2 · src/identity/src/extensions/rabbitmq.extensions.ts:2 · src/passenger/src/extensions/rabbitmq.extensions.ts:3 — the 4 copies are spread across 4 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/booking/src/extensions/rabbitmq.extensions.ts:2
- src/building-blocks/contracts/flight.contract.ts:42 · src/building-blocks/contracts/flight.contract.ts:92 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/building-blocks/contracts/flight.contract.ts:42
- src/building-blocks/contracts/identity.contract.ts:35 · src/building-blocks/contracts/passenger.contract.ts:2 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/building-blocks/contracts/identity.contract.ts:35
- src/booking/src/booking/mappings.ts:16 · src/flight/src/seat/mappings.ts:24 · src/identity/src/auth/mappings.ts:12 · src/identity/src/user/mapping.ts:24 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/booking/src/booking/mappings.ts:16
- src/building-blocks/rabbitmq/rabbitmq-connection.ts:38 · src/building-blocks/rabbitmq/rabbitmq-connection.ts:82 — the two spans are one implementation copied and then locally edited — 67 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/building-blocks/rabbitmq/rabbitmq-connection.ts:38
- src/building-blocks/contracts/flight.contract.ts:105 · src/flight/src/seat/features/v1/reserve-seat/reserve-seat.ts:17 · src/identity/src/auth/features/v1/login/login.ts:14 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/building-blocks/contracts/flight.contract.ts:105
- REDACTED:16 · REDACTED:31 · REDACTED:46 · REDACTED:61 · +4 more site(s) not listed — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — REDACTED:16
- src/flight/src/flight/features/v1/get-flight-by-id/get-flight-by-id.ts:11 · src/flight/src/seat/features/v1/get-available-seats/get-available-seats.ts:10 · src/identity/src/auth/features/v1/logout/logout.ts:10 · src/identity/src/auth/features/v1/refresh-token/refresh-token.ts:13 — the 4 copies are spread across 4 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/flight/src/flight/features/v1/get-flight-by-id/get-flight-by-id.ts:11
- src/identity/src/auth/features/v1/generate-token/generate-token.ts:12 · src/identity/src/user/features/v1/delete-user-by-id/delete-user-by-id.ts:14 · src/identity/src/user/features/v1/get-user-by-id/get-user-by-id.ts:11 · src/passenger/src/passenger/features/v1/get-passenger-by-id/get-passenger-by-id.ts:11 — the 4 copies are spread across 4 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/identity/src/auth/features/v1/generate-token/generate-token.ts:12
- src/booking/src/booking/entities/booking.entity.ts:33 · src/flight/src/seat/entities/seat.entity.ts:35 · src/passenger/src/passenger/entities/passenger.entity.ts:23 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/booking/src/booking/entities/booking.entity.ts:33
- src/booking/src/booking/features/v1/create-booking/create-booking.ts:28 · src/flight/src/aircraft/features/v1/create-aircraft/create-aircraft.ts:26 · src/flight/src/airport/features/v1/create-airport/create-airport.ts:26 · src/flight/src/flight/features/v1/create-flight/create-flight.ts:41 · +4 more site(s) not listed — the 8 copies are spread across 8 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/booking/src/booking/features/v1/create-booking/create-booking.ts:28
- src/booking/src/data/db.context.ts:6 · src/passenger/src/data/db.context.ts:6 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/booking/src/data/db.context.ts:6
- src/flight/src/extensions/mediatr.extensions.ts:24 · src/identity/src/extensions/mediatr.extensions.ts:21 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/flight/src/extensions/mediatr.extensions.ts:24
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — src/building-blocks/contracts/flight.contract.ts:1, src/flight/src/flight/features/v1/create-flight/create-flight.ts:1, src/flight/src/data/seeds/flight.seed.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
R7 · Dead Code
- Unreachable from the 10 application, 49 tooling and 14 test entry point(s) detected in this repo. Gate removals on `npm run dev` — an undetected custom entry would make these reachable.
- no import path from any entry point (10 application, 49 tooling, 14 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×6) — src/building-blocks/jwt/jwt.ts, src/flight/src/data/migrations/1702553492495-create-flight-table.ts, src/identity/src/auth/mappings.ts, …
- Nothing imports this binding — it is safe to review for removal. (×18) — src/booking/src/booking/features/v1/create-booking/create-booking.ts:43, src/flight/src/aircraft/features/v1/create-aircraft/create-aircraft.ts:41, src/flight/src/airport/features/v1/create-airport/create-airport.ts:41, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. — src/identity/src/auth/features/v1/generate-token/generate-token.ts:4
- Declared in src/booking/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
- Only test files import it (first: src/identity/test/unit-test/user/features/create-user.test.ts:2) — move it to devDependencies. — src/identity/package.json:78
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- src/flight/src/aircraft/entities/aircraft.entity.ts → src/flight/src/flight/entities/flight.entity.ts → src/flight/src/aircraft/entities/aircraft.entity.ts (one verified cycle inside a mutually-dependent group of 4 files) — src/flight/src/aircraft/entities/aircraft.entity.ts:2
- src/identity/src/auth/entities/token.entity.ts → src/identity/src/user/entities/user.entity.ts → src/identity/src/auth/entities/token.entity.ts — src/identity/src/auth/entities/token.entity.ts:3
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- This code fixes bcrypt at work factor 8. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price. — src/building-blocks/utils/encryption.ts:6
What to do
- Raise the cost parameter to current guidance — PBKDF2 at 1,300,000 (HMAC-SHA1), 600,000 (SHA-256) or 210,000 (SHA-512) iterations; scrypt at N=2^17, r=8, p=1; bcrypt at a work factor of 10 or more — or move to a memory-hard KDF (Argon2id, scrypt) where the platform offers one. Read the parameter from configuration and tune it to roughly 100 ms per derivation on the slowest hardware that must run it, so the price can be raised again without shipping new code.
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
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `info` at line 62 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. (×3) — REDACTED:62, REDACTED:62, REDACTED:62
- `info` at line 23 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/passenger/src/user/consumers/create-user.ts:23
- `error` at line 60 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/building-blocks/rabbitmq/rabbitmq-connection.ts:60
- `error` at line 97 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/building-blocks/rabbitmq/rabbitmq-connection.ts:97
- `info` at line 42 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/building-blocks/rabbitmq/rabbitmq-consumer.ts:42
- `info` at line 56 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/building-blocks/rabbitmq/rabbitmq-consumer.ts:56
- `info` at line 52 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/building-blocks/rabbitmq/rabbitmq-publisher.ts:52
- `error` at line 79 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/building-blocks/rabbitmq/rabbitmq-connection.js:79
- `error` at line 110 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/building-blocks/rabbitmq/rabbitmq-connection.js:110
- `info` at line 36 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/building-blocks/rabbitmq/rabbitmq-consumer.js:36
- `info` at line 43 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/building-blocks/rabbitmq/rabbitmq-consumer.js:43
- `info` at line 47 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/building-blocks/rabbitmq/rabbitmq-publisher.js:47
- `info` at line 63 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — REDACTED:63
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 0/5 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 60% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 85% | Strong | Solid. |
| Maturity | 66% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 24% | Critical — gated by D13, R4, R8, P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 45% | Weak — gated by D29, D31, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 10% | Critical — gated by DM6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 2 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.
- SC1 Supply-chain hygiene — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 12 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, an ORM write hook that records changes — a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware — or a change-history plugin such as mongoose-history or sequelize-paper-trail) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 58 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.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX4 Dependency direction — not applicable to a vertical-slice + CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — vertical-slice architecture detected, but individual slices could not be resolved from namespaces or project layout
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — time="2026-11-08T01:13:06Z" level=warning msg="The \"FLIGHT_PORT\" variable is not set. Defaulting to a blank string." time="2026-11-08T01:13:06Z" level=warning msg="The \"POSTGRES_PORT\" variable is not set. Defaulting to a blank string." failed to solve: process "/bin/sh -c npm install" did not complete successfully: exit code: 1; 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.
- D11 Test Reliability — No tests discovered
- D12 Dependency Hygiene — Not scored — 179 production npm declaration(s) across 5 package.json (5 of them the product) were read for PINNING discipline (1 defect(s) reported), but the outdated/deprecated signal needs registry.npmjs.org, and no committed lockfile here resolves to the concrete versions that question is asked about, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — npm licences not graded — this npm repository commits no lockfile this pass can resolve
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1274 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. 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 (24 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- 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 — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in src/booking/ ran and not one test passed (No tests found, exiting with code 1), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (20 CQRS handler(s))
- ED5 Idempotency — not scored — 1 of 1 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 49 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
- Domain fused to persistence infrastructure: Booking src/booking/src/booking/entities/booking.entity.ts:3
- Domain fused to persistence infrastructure: Airport src/flight/src/airport/entities/airport.entity.ts:4
- Domain fused to persistence infrastructure: Seat src/flight/src/seat/entities/seat.entity.ts:6
- Domain fused to persistence infrastructure: Flight src/flight/src/flight/entities/flight.entity.ts:13
- Domain fused to persistence infrastructure: Aircraft src/flight/src/aircraft/entities/aircraft.entity.ts:4
- Domain fused to persistence infrastructure: Token src/identity/src/auth/entities/token.entity.ts:5
- Domain fused to persistence infrastructure: User src/identity/src/user/entities/user.entity.ts:5
- Domain fused to persistence infrastructure: Passenger src/passenger/src/passenger/entities/passenger.entity.ts:4
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test suite declares a test script but contains no test files: src/booking/
- Test suite declares a test script but contains no test files: src/flight/
- Test suite declares a test script but contains no test files: src/passenger/
- REDACTED
- REDACTED
- REDACTED
- Import cycle (2 files) src/flight/src/aircraft/entities/aircraft.entity.ts:2
- Import cycle (2 files) src/identity/src/auth/entities/token.entity.ts:3
- REDACTED
- Unlisted import 'jsonwebtoken' src/identity/src/auth/features/v1/generate-token/generate-token.ts:4
Serious — 357 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
- No test reaches this file src/building-blocks/contracts/flight.contract.ts:1
- No test reaches this file src/flight/src/flight/features/v1/create-flight/create-flight.ts:1
- No test reaches this file src/flight/src/data/seeds/flight.seed.ts:1
- No test reaches this file src/booking/src/booking/features/v1/create-booking/create-booking.ts:1
- No test reaches this file src/flight/src/seat/features/v1/create-seat/create-seat.ts:1
- No test reaches this file src/flight/src/seat/features/v1/reserve-seat/reserve-seat.ts:1
- No test reaches this file src/flight/src/aircraft/features/v1/create-aircraft/create-aircraft.ts:1
- No test reaches this file src/flight/src/airport/features/v1/create-airport/create-airport.ts:1
- No test reaches this file REDACTED:1
- No test reaches this file src/passenger/src/passenger/features/v1/get-passengers/get-passengers.ts:1
- No test reaches this file REDACTED:1
- No test reaches this file REDACTED:1
- No test reaches this file REDACTED:1
- No test reaches this file src/flight/src/flight/entities/flight.entity.ts:1
- No test reaches this file src/flight/src/flight/mappings.ts:1
- No test reaches this file src/booking/src/booking/mappings.ts:1
- No test reaches this file src/booking/src/booking/http-client/services/flight/flight.client.ts:1
- No test reaches this file src/building-blocks/jwt/jwt.ts:1
- No test reaches this file src/flight/src/data/migrations/1702553492495-create-flight-table.ts:1
- No test reaches this file src/building-blocks/open-telemetry/open-telemetry.ts:1
- No test reaches this file src/flight/src/data/repositories/seat.repository.ts:1
- No test reaches this file src/passenger/src/data/repositories/passenger.repository.ts:1
- No test reaches this file src/passenger/src/passenger/features/v1/get-passenger-by-id/get-passenger-by-id.ts:1
- No test reaches this file src/flight/src/flight/features/v1/get-flight-by-id/get-flight-by-id.ts:1
- No test reaches this file src/flight/src/seat/features/v1/get-available-seats/get-available-seats.ts:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- JavaScript dependencies are not locked src/booking/package.json:20
- JavaScript dependencies are not locked src/building-blocks/package.json:14
- JavaScript dependencies are not locked src/flight/package.json:20
- JavaScript dependencies are not locked src/identity/package.json:20
- JavaScript dependencies are not locked src/passenger/package.json:20
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Fake-async — async method never awaits src/booking/src/extensions/repository.extensions.ts:4
- Fake-async — async method never awaits src/flight/src/extensions/repository.extensions.ts:7
- Fake-async — async method never awaits src/identity/src/extensions/repository.extensions.ts:5
- Fake-async — async method never awaits src/passenger/src/extensions/repository.extensions.ts:7
- Duplicated block (17 lines × 2 locations) src/flight/src/flight/entities/flight.entity.ts:15
- Duplicated block (17 lines × 2 locations) src/flight/src/flight/features/v1/get-flight-by-id/get-flight-by-id.ts:11
- Duplicated block (17 lines × 2 locations) src/identity/src/user/entities/user.entity.ts:10
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (38 lines × 2 locations) src/flight/src/flight/features/v1/create-flight/create-flight.ts:67
- Duplicated block (38 lines × 2 locations) src/flight/src/flight/features/v1/get-flight-by-id/get-flight-by-id.ts:11
- Duplicated block (21 lines × 2 locations) src/booking/src/booking/http-client/services/flight/flight.client.ts:17
- Duplicated block (21 lines × 2 locations) src/flight/src/aircraft/entities/aircraft.entity.ts:4
- Duplicated block (15 lines × 6 locations) src/booking/src/booking/mappings.ts:50
- Duplicated block (15 lines × 6 locations) src/building-blocks/types/exception/application.exception.ts:7
- Duplicated block (15 lines × 2 locations) src/flight/src/data/db.context.ts:9
- Duplicated block (15 lines × 2 locations) src/identity/src/auth/features/v1/login/login.ts:33
- Duplicated block (14 lines × 2 locations) src/building-blocks/contracts/flight.contract.ts:42
- Duplicated block (14 lines × 2 locations) src/building-blocks/contracts/identity.contract.ts:35
- Dead file (~61 LoC) src/building-blocks/jwt/jwt.ts
- Dead file (~61 LoC) src/flight/src/data/migrations/1702553492495-create-flight-table.ts
- REDACTED.expressAuthentication (cognitive 29) src/building-blocks/jwt/jwt.ts:7
- REDACTED
- Off the main sequence: building-blocks
- Coverage not measured — JavaScript/TypeScript suite
- No DR/backup evidence
- Duplication concentrated across 5 sibling directories (47 clone groups) src/identity/src/user/features/v1/get-users/get-users.ts:11
- Duplicated block (62 lines × 2 locations) src/flight/src/aircraft/features/v1/create-aircraft/create-aircraft.ts:14
- Duplicated block (58 lines × 2 locations) src/identity/src/user/features/v1/get-users/get-users.ts:11
- Wholesale file copy (52 identical lines × 4 files) REDACTED:1
- Duplicated block (47 lines × 3 locations) src/booking/src/booking/features/v1/create-booking/create-booking.ts:16
- Duplicated block (40 lines × 2 locations) src/flight/src/seat/features/v1/create-seat/create-seat.ts:47
- Duplicated block with local edits (36 matched lines × 2 locations) src/building-blocks/rabbitmq/rabbitmq-consumer.ts:14
- Duplicated block (32 lines × 2 locations) src/identity/src/user/features/v1/create-user/create-user.ts:18
- Duplicated block (29 lines × 3 locations) src/booking/src/booking/mappings.ts:5
- Duplicated block (25 lines × 3 locations) src/identity/src/user/features/v1/delete-user-by-id/delete-user-by-id.ts:14
- Duplicated block (23 lines × 2 locations) src/identity/src/data/repositories/user.repository.ts:45
- Duplicated block (17 lines × 6 locations) src/flight/src/aircraft/mappings.ts:5
- Duplicated block (14 lines × 5 locations) src/booking/src/booking/entities/booking.entity.ts:1
- Duplicated block (14 lines × 3 locations) src/booking/src/extensions/rabbitmq.extensions.ts:6
- Duplicated block (14 lines × 4 locations) src/booking/src/extensions/rabbitmq.extensions.ts:2
- Duplicated block (13 lines × 4 locations) src/booking/src/booking/mappings.ts:16
- Duplicated block with local edits (13 matched lines × 2 locations) src/building-blocks/rabbitmq/rabbitmq-connection.ts:38
- Duplicated block (12 lines × 3 locations) src/building-blocks/contracts/flight.contract.ts:105
- Duplicated block (12 lines × 8 locations) REDACTED:16
- Duplicated block (12 lines × 4 locations) src/flight/src/flight/features/v1/get-flight-by-id/get-flight-by-id.ts:11
- Duplicated block (11 lines × 4 locations) src/identity/src/auth/features/v1/generate-token/generate-token.ts:12
- Duplicated block (10 lines × 3 locations) src/booking/src/booking/entities/booking.entity.ts:33
- Duplicated block (9 lines × 8 locations) src/booking/src/booking/features/v1/create-booking/create-booking.ts:28
- Duplicated block (9 lines × 2 locations) src/booking/src/data/db.context.ts:6
- Duplicated block (5 lines × 2 locations) src/flight/src/extensions/mediatr.extensions.ts:24
- Dead file (~30 LoC) src/identity/src/auth/mappings.ts
- Dead file (~25 LoC) src/identity/src/data/migrations/1702550291057-create-user-table.ts
- Dead file (~19 LoC) src/passenger/src/data/migrations/1702553578224-create-passenger-table.ts
- Dead file (~15 LoC) src/booking/src/data/migrations/1702553396443-create-booking-table.ts
- Unused dependency '@eslint/js'
- Unused dependency '@faker-js/faker'
- Unused dependency '@opentelemetry/sdk-trace-node'
- Password key derivation is priced too cheaply src/building-blocks/utils/encryption.ts:6
Minor — 133 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
- Orphaned file src/building-blocks/logging/logger.ts:1
- Orphaned file src/flight/src/flight/features/v1/create-flight/create-flight.ts:1
- Orphaned file src/building-blocks/config/config.ts:1
- Orphaned file src/flight/src/data/migrations/1702553492495-create-flight-table.ts:1
- Orphaned file src/booking/src/booking/features/v1/create-booking/create-booking.ts:1
- Orphaned file src/flight/src/data/seeds/flight.seed.ts:1
- Orphaned file src/building-blocks/rabbitmq/rabbitmq-connection.ts:1
- Orphaned file src/building-blocks/rabbitmq/rabbitmq-consumer.ts:1
- Orphaned file REDACTED:1
- Orphaned file src/flight/src/seat/features/v1/create-seat/create-seat.ts:1
- Orphaned file src/identity/src/user/features/v1/update-user/update-user.ts:1
- Orphaned file src/identity/src/user/features/v1/create-user/create-user.ts:1
- Orphaned file src/flight/src/seat/features/v1/reserve-seat/reserve-seat.ts:1
- Orphaned file src/flight/src/aircraft/features/v1/create-aircraft/create-aircraft.ts:1
- Orphaned file src/flight/src/airport/features/v1/create-airport/create-airport.ts:1
- Orphaned file src/passenger/src/passenger/features/v1/get-passengers/get-passengers.ts:1
- Orphaned file src/building-blocks/rabbitmq/rabbitmq-publisher.ts:1
- Orphaned file src/building-blocks/contracts/flight.contract.ts:1
- Orphaned file src/identity/src/user/features/v1/get-users/get-users.ts:1
- Interpolated log message defeats structured logging REDACTED:62
- Interpolated log message defeats structured logging src/passenger/src/user/consumers/create-user.ts:23
- Interpolated log message defeats structured logging REDACTED:62
- Interpolated log message defeats structured logging REDACTED:62
- Interpolated log message defeats structured logging src/building-blocks/rabbitmq/rabbitmq-connection.ts:60
- Interpolated log message defeats structured logging src/building-blocks/rabbitmq/rabbitmq-connection.ts:97
- Interpolated log message defeats structured logging src/building-blocks/rabbitmq/rabbitmq-consumer.ts:42
- Interpolated log message defeats structured logging src/building-blocks/rabbitmq/rabbitmq-consumer.ts:56
- Interpolated log message defeats structured logging src/building-blocks/rabbitmq/rabbitmq-publisher.ts:52
- Interpolated log message defeats structured logging src/building-blocks/rabbitmq/rabbitmq-connection.js:79
- Interpolated log message defeats structured logging src/building-blocks/rabbitmq/rabbitmq-connection.js:110
- Interpolated log message defeats structured logging src/building-blocks/rabbitmq/rabbitmq-consumer.js:36
- Interpolated log message defeats structured logging src/building-blocks/rabbitmq/rabbitmq-consumer.js:43
- Interpolated log message defeats structured logging src/building-blocks/rabbitmq/rabbitmq-publisher.js:47
- Interpolated log message defeats structured logging REDACTED:63
- Duplicated predicate src/building-blocks/utils/validation.js:8
- Duplicated predicate src/building-blocks/jwt/jwt.js:58
- Duplicated predicate src/building-blocks/logging/logger.js:22
- Duplicated predicate src/building-blocks/logging/logger.ts:112
- Duplicated predicate src/building-blocks/logging/logger.ts:113
- Duplicated predicate src/building-blocks/logging/logger.js:122
- Duplicated predicate src/building-blocks/logging/logger.js:122
- Duplicated predicate src/building-blocks/jwt/jwt.js:52
- Duplicated predicate src/building-blocks/jwt/jwt.js:47
- Duplicated predicate src/building-blocks/monitoring/request-counter.middleware.js:57
- Duplicated predicate src/building-blocks/logging/logger.js:20
- Duplicated predicate src/building-blocks/logging/logger.js:42
- No seccomp profile REDACTED:2
- No seccomp profile REDACTED:2
- No seccomp profile REDACTED:2
- No seccomp profile REDACTED:2
- No seccomp profile REDACTED:2
- No seccomp profile REDACTED:2
- No seccomp profile REDACTED:2
- No seccomp profile REDACTED:2
- No seccomp profile REDACTED:2
- Console output used as the logging channel src/building-blocks/open-telemetry/open-telemetry.ts:51
- Console output used as the logging channel src/building-blocks/open-telemetry/open-telemetry.ts:52
- Console output used as the logging channel src/building-blocks/open-telemetry/open-telemetry.ts:58
- Console output used as the logging channel src/building-blocks/open-telemetry/open-telemetry.js:45
- Console output used as the logging channel src/building-blocks/open-telemetry/open-telemetry.js:49
- Unused export 'GetUserByIdController' src/flight/src/flight/features/v1/get-flight-by-id/get-flight-by-id.ts:26
- Unused export 'GetUserByIdController' src/identity/src/user/features/v1/get-user-by-id/get-user-by-id.ts:26
- No named authorization policies REDACTED:47
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No network policy
- No ADRs
- No SAST REDACTED:9
- No dependency-update automation src/booking/package.json:20
- Unused export 'CreateBookingController' src/booking/src/booking/features/v1/create-booking/create-booking.ts:43
- Unused export 'CreateAircraftController' src/flight/src/aircraft/features/v1/create-aircraft/create-aircraft.ts:41
- Unused export 'CreateAirportController' src/flight/src/airport/features/v1/create-airport/create-airport.ts:41
- Unused export 'CreateFlightController' src/flight/src/flight/features/v1/create-flight/create-flight.ts:71
- Unused export 'CreateSeatController' src/flight/src/seat/features/v1/create-seat/create-seat.ts:51
- Unused export 'GetAvailableSeatsController' src/flight/src/seat/features/v1/get-available-seats/get-available-seats.ts:25
- Unused export 'ReserveSeatController' src/flight/src/seat/features/v1/reserve-seat/reserve-seat.ts:39
- Unused export 'LoginController' src/identity/src/auth/features/v1/login/login.ts:36
- Unused export 'LogoutController' src/identity/src/auth/features/v1/logout/logout.ts:25
- Unused export 'RefreshTokenController' src/identity/src/auth/features/v1/refresh-token/refresh-token.ts:28
- Unused export 'CreateUserController' src/identity/src/user/features/v1/create-user/create-user.ts:50
- Unused export 'DeleteUserByIdController' src/identity/src/user/features/v1/delete-user-by-id/delete-user-by-id.ts:29
- Unused export 'GetUsersController' src/identity/src/user/features/v1/get-users/get-users.ts:32
- Unused export 'UpdateUserController' src/identity/src/user/features/v1/update-user/update-user.ts:50
- Unused export 'GetPassengerByIdController' src/passenger/src/passenger/features/v1/get-passenger-by-id/get-passenger-by-id.ts:26
- Unused export 'GetPassengersController' src/passenger/src/passenger/features/v1/get-passengers/get-passengers.ts:32
- Test-only dependency 'typemoq' in production deps src/identity/package.json:78
- Strict null checking is not enabled everywhere the repository type-checks
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-790727391d1042479ec48f56e49a81ea/history.json --exit-code 0 --source . | 5 | 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-790727391d1042479ec48f56e49a81ea/tree.json --exit-code 0 --source . | 2 | 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/booking/src/routes --exclude src/flight/src/routes --exclude src/identity/src/routes --exclude src/passenger/src/routes . | 20 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 306 | 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/building-blocks/logging/logger.js`, `src/identity/jest.config.ts` — 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 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |