Executive summary
pgorecki/python-ddd is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 50 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 32, is the weakest lens and counts most in the score. The best first step is adding automated security scanning, worth about 6 points. Having someone learn and document the 11 files no active contributor knows comes next, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 64.
Ten known security holes in the packages the code depends on can be used by attackers. Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and one pipeline step installs packages that can change without warning. Updating the vulnerable packages, pinning each tool to an exact version and pinning what the pipeline installs would close these risks.
The product code is 3,015 lines, about €5,800 to rebuild.
If Production Readiness rose from 32 to 70, the lowest score rated Strong, the score would rise from 50 to about 64.
New since the last survey: 3 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 3 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Rebuild cost: about €5,800 · Estimate
| Cost to rebuild | €1,900 to €9,700, for 32 to 102 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 50. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 3,015 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 seedwork.application | 2 seedwork.application.commands | 3 seedwork.application.queries | 4 seedwork.domain.events | 5 seedwork.domain.exceptions | 6 seedwork.domain.repositories | 7 seedwork.domain.rules | 8 seedwork.domain.value_objects | 9 api.models.bidding | 10 modules.bidding.application.command.place_bid | 11 modules.bidding.application.command.retract_bid | 12 modules.bidding.application.query.get_bidding_details | 13 modules.bidding.application.query.get_pastdue_listings | 14 modules.bidding.application.query.model_mappers | 15 modules.bidding.domain.events | 16 modules.bidding.domain.repositories | 17 modules.bidding.domain.rules | 18 modules.bidding.domain.value_objects | 19 modules.catalog.application.query.get_listing_details | 20 modules.catalog.application.query.get_listings_of_seller | 21 modules.catalog.domain.events | 22 modules.catalog.domain.repositories | 23 modules.catalog.domain.rules | 24 modules.iam.application.repository | 25 seedwork.domain.mixins | 26 api.routers | 27 modules.bidding.application.command | 28 modules.bidding.application.event | 29 modules.catalog.application.command | 30 seedwork.domain.entities | 31 modules.bidding.domain.entities | 32 modules.catalog.domain.entities | 33 modules.iam.domain.entities | 34 seedwork.infrastructure.repository | 35 api | 36 modules.bidding.infrastructure.listing_repository | 37 modules.catalog.infrastructure.listing_repository | 38 modules.iam.infrastructure.repository | 39 modules.bidding.application.query | 40 modules.catalog.application.query |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 seedwork.application | ||||||||||||||||||||||||||||||||||||||||
| 2 seedwork.application.commands | ||||||||||||||||||||||||||||||||||||||||
| 3 seedwork.application.queries | ||||||||||||||||||||||||||||||||||||||||
| 4 seedwork.domain.events | ||||||||||||||||||||||||||||||||||||||||
| 5 seedwork.domain.exceptions | ||||||||||||||||||||||||||||||||||||||||
| 6 seedwork.domain.repositories | ||||||||||||||||||||||||||||||||||||||||
| 7 seedwork.domain.rules | ||||||||||||||||||||||||||||||||||||||||
| 8 seedwork.domain.value_objects | ||||||||||||||||||||||||||||||||||||||||
| 9 api.models.bidding | 3 | |||||||||||||||||||||||||||||||||||||||
| 10 modules.bidding.application.command.place_bid | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 modules.bidding.application.command.retract_bid | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 modules.bidding.application.query.get_bidding_details | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 modules.bidding.application.query.get_pastdue_listings | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 modules.bidding.application.query.model_mappers | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 modules.bidding.domain.events | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 16 modules.bidding.domain.repositories | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 modules.bidding.domain.rules | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 modules.bidding.domain.value_objects | 6 | |||||||||||||||||||||||||||||||||||||||
| 19 modules.catalog.application.query.get_listing_details | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 modules.catalog.application.query.get_listings_of_seller | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 modules.catalog.domain.events | 4 | 5 | ||||||||||||||||||||||||||||||||||||||
| 22 modules.catalog.domain.repositories | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 modules.catalog.domain.rules | 7 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 modules.iam.application.repository | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 seedwork.domain.mixins | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 api.routers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 modules.bidding.application.command | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 28 modules.bidding.application.event | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 modules.catalog.application.command | 4 | |||||||||||||||||||||||||||||||||||||||
| 30 seedwork.domain.entities | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 modules.bidding.domain.entities | 1 | 3 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 32 modules.catalog.domain.entities | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 33 modules.iam.domain.entities | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 seedwork.infrastructure.repository | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 35 api | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 modules.bidding.infrastructure.listing_repository | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 modules.catalog.infrastructure.listing_repository | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 modules.iam.infrastructure.repository | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 modules.bidding.application.query | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 40 modules.catalog.application.query | 1 | 1 | 1 |
9→8 api.models.bidding uses seedwork.domain.value_objects✕
- Connections
- 3 pairs of types, where a type in api.models.bidding uses a type in seedwork.domain.value_objects.
- The types involved
src.api.models.bidding.BidReadModel→src.seedwork.domain.value_objects.GenericUUIDsrc.api.models.bidding.BiddingResponse→src.seedwork.domain.value_objects.GenericUUIDsrc.api.models.bidding.PlaceBidRequest→src.seedwork.domain.value_objects.GenericUUID
- Direction
- api.models.bidding uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break api.models.bidding, while a change to api.models.bidding can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: api.models.bidding uses a module listed above it, which is the healthy direction.
10→2 modules.bidding.application.command.place_bid uses seedwork.application.commands✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.command.place_bid uses a type in seedwork.application.commands.
- The types involved
src.modules.bidding.application.command.place_bid.PlaceBidCommand→src.seedwork.application.commands.Command
- Direction
- modules.bidding.application.command.place_bid uses seedwork.application.commands, so a change to seedwork.application.commands can break modules.bidding.application.command.place_bid, while a change to modules.bidding.application.command.place_bid can't break seedwork.application.commands.
- Position
- Below the diagonal: modules.bidding.application.command.place_bid uses a module listed above it, which is the healthy direction.
10→8 modules.bidding.application.command.place_bid uses seedwork.domain.value_objects✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.command.place_bid uses a type in seedwork.domain.value_objects.
- The types involved
src.modules.bidding.application.command.place_bid.PlaceBidCommand→src.seedwork.domain.value_objects.GenericUUID
- Direction
- modules.bidding.application.command.place_bid uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break modules.bidding.application.command.place_bid, while a change to modules.bidding.application.command.place_bid can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: modules.bidding.application.command.place_bid uses a module listed above it, which is the healthy direction.
11→2 modules.bidding.application.command.retract_bid uses seedwork.application.commands✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.command.retract_bid uses a type in seedwork.application.commands.
- The types involved
src.modules.bidding.application.command.retract_bid.RetractBidCommand→src.seedwork.application.commands.Command
- Direction
- modules.bidding.application.command.retract_bid uses seedwork.application.commands, so a change to seedwork.application.commands can break modules.bidding.application.command.retract_bid, while a change to modules.bidding.application.command.retract_bid can't break seedwork.application.commands.
- Position
- Below the diagonal: modules.bidding.application.command.retract_bid uses a module listed above it, which is the healthy direction.
11→8 modules.bidding.application.command.retract_bid uses seedwork.domain.value_objects✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.command.retract_bid uses a type in seedwork.domain.value_objects.
- The types involved
src.modules.bidding.application.command.retract_bid.RetractBidCommand→src.seedwork.domain.value_objects.GenericUUID
- Direction
- modules.bidding.application.command.retract_bid uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break modules.bidding.application.command.retract_bid, while a change to modules.bidding.application.command.retract_bid can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: modules.bidding.application.command.retract_bid uses a module listed above it, which is the healthy direction.
12→3 modules.bidding.application.query.get_bidding_details uses seedwork.application.queries✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.query.get_bidding_details uses a type in seedwork.application.queries.
- The types involved
src.modules.bidding.application.query.get_bidding_details.GetBiddingDetails→src.seedwork.application.queries.Query
- Direction
- modules.bidding.application.query.get_bidding_details uses seedwork.application.queries, so a change to seedwork.application.queries can break modules.bidding.application.query.get_bidding_details, while a change to modules.bidding.application.query.get_bidding_details can't break seedwork.application.queries.
- Position
- Below the diagonal: modules.bidding.application.query.get_bidding_details uses a module listed above it, which is the healthy direction.
12→8 modules.bidding.application.query.get_bidding_details uses seedwork.domain.value_objects✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.query.get_bidding_details uses a type in seedwork.domain.value_objects.
- The types involved
src.modules.bidding.application.query.get_bidding_details.GetBiddingDetails→src.seedwork.domain.value_objects.GenericUUID
- Direction
- modules.bidding.application.query.get_bidding_details uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break modules.bidding.application.query.get_bidding_details, while a change to modules.bidding.application.query.get_bidding_details can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: modules.bidding.application.query.get_bidding_details uses a module listed above it, which is the healthy direction.
13→3 modules.bidding.application.query.get_pastdue_listings uses seedwork.application.queries✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.query.get_pastdue_listings uses a type in seedwork.application.queries.
- The types involved
src.modules.bidding.application.query.get_pastdue_listings.GetPastdueListings→src.seedwork.application.queries.Query
- Direction
- modules.bidding.application.query.get_pastdue_listings uses seedwork.application.queries, so a change to seedwork.application.queries can break modules.bidding.application.query.get_pastdue_listings, while a change to modules.bidding.application.query.get_pastdue_listings can't break seedwork.application.queries.
- Position
- Below the diagonal: modules.bidding.application.query.get_pastdue_listings uses a module listed above it, which is the healthy direction.
14→8 modules.bidding.application.query.model_mappers uses seedwork.domain.value_objects✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.query.model_mappers uses a type in seedwork.domain.value_objects.
- The types involved
src.modules.bidding.application.query.model_mappers.ListingDAO→src.seedwork.domain.value_objects.GenericUUID
- Direction
- modules.bidding.application.query.model_mappers uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break modules.bidding.application.query.model_mappers, while a change to modules.bidding.application.query.model_mappers can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: modules.bidding.application.query.model_mappers uses a module listed above it, which is the healthy direction.
15→4 modules.bidding.domain.events uses seedwork.domain.events✕
- Connections
- 4 pairs of types, where a type in modules.bidding.domain.events uses a type in seedwork.domain.events.
- The types involved
src.modules.bidding.domain.events.BidWasPlaced→src.seedwork.domain.events.DomainEventsrc.modules.bidding.domain.events.BidWasRetracted→src.seedwork.domain.events.DomainEventsrc.modules.bidding.domain.events.HighestBidderWasOutbid→src.seedwork.domain.events.DomainEventsrc.modules.bidding.domain.events.ListingWasCancelled→src.seedwork.domain.events.DomainEvent
- Direction
- modules.bidding.domain.events uses seedwork.domain.events, so a change to seedwork.domain.events can break modules.bidding.domain.events, while a change to modules.bidding.domain.events can't break seedwork.domain.events.
- Position
- Below the diagonal: modules.bidding.domain.events uses a module listed above it, which is the healthy direction.
15→8 modules.bidding.domain.events uses seedwork.domain.value_objects✕
- Connections
- 2 pairs of types, where a type in modules.bidding.domain.events uses a type in seedwork.domain.value_objects.
- The types involved
src.modules.bidding.domain.events.BidWasPlaced→src.seedwork.domain.value_objects.GenericUUIDsrc.modules.bidding.domain.events.HighestBidderWasOutbid→src.seedwork.domain.value_objects.GenericUUID
- Direction
- modules.bidding.domain.events uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break modules.bidding.domain.events, while a change to modules.bidding.domain.events can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: modules.bidding.domain.events uses a module listed above it, which is the healthy direction.
16→6 modules.bidding.domain.repositories uses seedwork.domain.repositories✕
- Connections
- 1 pair of types, where a type in modules.bidding.domain.repositories uses a type in seedwork.domain.repositories.
- The types involved
src.modules.bidding.domain.repositories.ListingRepository→src.seedwork.domain.repositories.GenericRepository
- Direction
- modules.bidding.domain.repositories uses seedwork.domain.repositories, so a change to seedwork.domain.repositories can break modules.bidding.domain.repositories, while a change to modules.bidding.domain.repositories can't break seedwork.domain.repositories.
- Position
- Below the diagonal: modules.bidding.domain.repositories uses a module listed above it, which is the healthy direction.
17→7 modules.bidding.domain.rules uses seedwork.domain.rules✕
- Connections
- 3 pairs of types, where a type in modules.bidding.domain.rules uses a type in seedwork.domain.rules.
- The types involved
src.modules.bidding.domain.rules.BidCanBeRetracted→src.seedwork.domain.rules.BusinessRulesrc.modules.bidding.domain.rules.ListingCanBeCancelled→src.seedwork.domain.rules.BusinessRulesrc.modules.bidding.domain.rules.PriceOfPlacedBidMustBeGreaterOrEqualThanNextMinimumPrice→src.seedwork.domain.rules.BusinessRule
- Direction
- modules.bidding.domain.rules uses seedwork.domain.rules, so a change to seedwork.domain.rules can break modules.bidding.domain.rules, while a change to modules.bidding.domain.rules can't break seedwork.domain.rules.
- Position
- Below the diagonal: modules.bidding.domain.rules uses a module listed above it, which is the healthy direction.
17→8 modules.bidding.domain.rules uses seedwork.domain.value_objects✕
- Connections
- 1 pair of types, where a type in modules.bidding.domain.rules uses a type in seedwork.domain.value_objects.
- The types involved
src.modules.bidding.domain.rules.PriceOfPlacedBidMustBeGreaterOrEqualThanNextMinimumPrice→src.seedwork.domain.value_objects.Money
- Direction
- modules.bidding.domain.rules uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break modules.bidding.domain.rules, while a change to modules.bidding.domain.rules can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: modules.bidding.domain.rules uses a module listed above it, which is the healthy direction.
18→8 modules.bidding.domain.value_objects uses seedwork.domain.value_objects✕
- Connections
- 6 pairs of types, where a type in modules.bidding.domain.value_objects uses a type in seedwork.domain.value_objects.
- The types involved
src.modules.bidding.domain.value_objects.Bid→src.seedwork.domain.value_objects.Moneysrc.modules.bidding.domain.value_objects.Bid→src.seedwork.domain.value_objects.ValueObjectsrc.modules.bidding.domain.value_objects.Bidder→src.seedwork.domain.value_objects.GenericUUIDsrc.modules.bidding.domain.value_objects.Bidder→src.seedwork.domain.value_objects.ValueObjectsrc.modules.bidding.domain.value_objects.Seller→src.seedwork.domain.value_objects.GenericUUIDsrc.modules.bidding.domain.value_objects.Seller→src.seedwork.domain.value_objects.ValueObject
- Direction
- modules.bidding.domain.value_objects uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break modules.bidding.domain.value_objects, while a change to modules.bidding.domain.value_objects can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: modules.bidding.domain.value_objects uses a module listed above it, which is the healthy direction.
19→3 modules.catalog.application.query.get_listing_details uses seedwork.application.queries✕
- Connections
- 1 pair of types, where a type in modules.catalog.application.query.get_listing_details uses a type in seedwork.application.queries.
- The types involved
src.modules.catalog.application.query.get_listing_details.GetListingDetails→src.seedwork.application.queries.Query
- Direction
- modules.catalog.application.query.get_listing_details uses seedwork.application.queries, so a change to seedwork.application.queries can break modules.catalog.application.query.get_listing_details, while a change to modules.catalog.application.query.get_listing_details can't break seedwork.application.queries.
- Position
- Below the diagonal: modules.catalog.application.query.get_listing_details uses a module listed above it, which is the healthy direction.
19→8 modules.catalog.application.query.get_listing_details uses seedwork.domain.value_objects✕
- Connections
- 1 pair of types, where a type in modules.catalog.application.query.get_listing_details uses a type in seedwork.domain.value_objects.
- The types involved
src.modules.catalog.application.query.get_listing_details.GetListingDetails→src.seedwork.domain.value_objects.GenericUUID
- Direction
- modules.catalog.application.query.get_listing_details uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break modules.catalog.application.query.get_listing_details, while a change to modules.catalog.application.query.get_listing_details can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: modules.catalog.application.query.get_listing_details uses a module listed above it, which is the healthy direction.
20→3 modules.catalog.application.query.get_listings_of_seller uses seedwork.application.queries✕
- Connections
- 1 pair of types, where a type in modules.catalog.application.query.get_listings_of_seller uses a type in seedwork.application.queries.
- The types involved
src.modules.catalog.application.query.get_listings_of_seller.GetListingsOfSeller→src.seedwork.application.queries.Query
- Direction
- modules.catalog.application.query.get_listings_of_seller uses seedwork.application.queries, so a change to seedwork.application.queries can break modules.catalog.application.query.get_listings_of_seller, while a change to modules.catalog.application.query.get_listings_of_seller can't break seedwork.application.queries.
- Position
- Below the diagonal: modules.catalog.application.query.get_listings_of_seller uses a module listed above it, which is the healthy direction.
20→8 modules.catalog.application.query.get_listings_of_seller uses seedwork.domain.value_objects✕
- Connections
- 1 pair of types, where a type in modules.catalog.application.query.get_listings_of_seller uses a type in seedwork.domain.value_objects.
- The types involved
src.modules.catalog.application.query.get_listings_of_seller.GetListingsOfSeller→src.seedwork.domain.value_objects.GenericUUID
- Direction
- modules.catalog.application.query.get_listings_of_seller uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break modules.catalog.application.query.get_listings_of_seller, while a change to modules.catalog.application.query.get_listings_of_seller can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: modules.catalog.application.query.get_listings_of_seller uses a module listed above it, which is the healthy direction.
21→4 modules.catalog.domain.events uses seedwork.domain.events✕
- Connections
- 4 pairs of types, where a type in modules.catalog.domain.events uses a type in seedwork.domain.events.
- The types involved
src.modules.catalog.domain.events.ListingDraftCreatedEvent→src.seedwork.domain.events.DomainEventsrc.modules.catalog.domain.events.ListingDraftDeletedEvent→src.seedwork.domain.events.DomainEventsrc.modules.catalog.domain.events.ListingDraftUpdatedEvent→src.seedwork.domain.events.DomainEventsrc.modules.catalog.domain.events.ListingPublishedEvent→src.seedwork.domain.events.DomainEvent
- Direction
- modules.catalog.domain.events uses seedwork.domain.events, so a change to seedwork.domain.events can break modules.catalog.domain.events, while a change to modules.catalog.domain.events can't break seedwork.domain.events.
- Position
- Below the diagonal: modules.catalog.domain.events uses a module listed above it, which is the healthy direction.
21→8 modules.catalog.domain.events uses seedwork.domain.value_objects✕
- Connections
- 5 pairs of types, where a type in modules.catalog.domain.events uses a type in seedwork.domain.value_objects.
- The types involved
src.modules.catalog.domain.events.ListingDraftCreatedEvent→src.seedwork.domain.value_objects.GenericUUIDsrc.modules.catalog.domain.events.ListingDraftDeletedEvent→src.seedwork.domain.value_objects.GenericUUIDsrc.modules.catalog.domain.events.ListingDraftUpdatedEvent→src.seedwork.domain.value_objects.GenericUUIDsrc.modules.catalog.domain.events.ListingPublishedEvent→src.seedwork.domain.value_objects.GenericUUIDsrc.modules.catalog.domain.events.ListingPublishedEvent→src.seedwork.domain.value_objects.Money
- Direction
- modules.catalog.domain.events uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break modules.catalog.domain.events, while a change to modules.catalog.domain.events can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: modules.catalog.domain.events uses a module listed above it, which is the healthy direction.
22→6 modules.catalog.domain.repositories uses seedwork.domain.repositories✕
- Connections
- 1 pair of types, where a type in modules.catalog.domain.repositories uses a type in seedwork.domain.repositories.
- The types involved
src.modules.catalog.domain.repositories.ListingRepository→src.seedwork.domain.repositories.GenericRepository
- Direction
- modules.catalog.domain.repositories uses seedwork.domain.repositories, so a change to seedwork.domain.repositories can break modules.catalog.domain.repositories, while a change to modules.catalog.domain.repositories can't break seedwork.domain.repositories.
- Position
- Below the diagonal: modules.catalog.domain.repositories uses a module listed above it, which is the healthy direction.
23→7 modules.catalog.domain.rules uses seedwork.domain.rules✕
- Connections
- 7 pairs of types, where a type in modules.catalog.domain.rules uses a type in seedwork.domain.rules.
- The types involved
src.modules.catalog.domain.rules.ListingAskPriceMustBeGreaterThanZero→src.seedwork.domain.rules.BusinessRulesrc.modules.catalog.domain.rules.ListingMustBeDraft→src.seedwork.domain.rules.BusinessRulesrc.modules.catalog.domain.rules.ListingMustBeInDraftState→src.seedwork.domain.rules.BusinessRulesrc.modules.catalog.domain.rules.OnlyListingOwnerCanDeleteListing→src.seedwork.domain.rules.BusinessRulesrc.modules.catalog.domain.rules.OnlyListingOwnerCanPublishListing→src.seedwork.domain.rules.BusinessRulesrc.modules.catalog.domain.rules.PublishedListingMustNotBeDeleted→src.seedwork.domain.rules.BusinessRulesrc.modules.catalog.domain.rules.SellerMustBeEligibleForAddingNextListing→src.seedwork.domain.rules.BusinessRule
- Direction
- modules.catalog.domain.rules uses seedwork.domain.rules, so a change to seedwork.domain.rules can break modules.catalog.domain.rules, while a change to modules.catalog.domain.rules can't break seedwork.domain.rules.
- Position
- Below the diagonal: modules.catalog.domain.rules uses a module listed above it, which is the healthy direction.
23→8 modules.catalog.domain.rules uses seedwork.domain.value_objects✕
- Connections
- 1 pair of types, where a type in modules.catalog.domain.rules uses a type in seedwork.domain.value_objects.
- The types involved
src.modules.catalog.domain.rules.ListingAskPriceMustBeGreaterThanZero→src.seedwork.domain.value_objects.Money
- Direction
- modules.catalog.domain.rules uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break modules.catalog.domain.rules, while a change to modules.catalog.domain.rules can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: modules.catalog.domain.rules uses a module listed above it, which is the healthy direction.
24→6 modules.iam.application.repository uses seedwork.domain.repositories✕
- Connections
- 1 pair of types, where a type in modules.iam.application.repository uses a type in seedwork.domain.repositories.
- The types involved
src.modules.iam.application.repository.UserRepository→src.seedwork.domain.repositories.GenericRepository
- Direction
- modules.iam.application.repository uses seedwork.domain.repositories, so a change to seedwork.domain.repositories can break modules.iam.application.repository, while a change to modules.iam.application.repository can't break seedwork.domain.repositories.
- Position
- Below the diagonal: modules.iam.application.repository uses a module listed above it, which is the healthy direction.
24→8 modules.iam.application.repository uses seedwork.domain.value_objects✕
- Connections
- 1 pair of types, where a type in modules.iam.application.repository uses a type in seedwork.domain.value_objects.
- The types involved
src.modules.iam.application.repository.UserRepository→src.seedwork.domain.value_objects.Email
- Direction
- modules.iam.application.repository uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break modules.iam.application.repository, while a change to modules.iam.application.repository can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: modules.iam.application.repository uses a module listed above it, which is the healthy direction.
25→7 seedwork.domain.mixins uses seedwork.domain.rules✕
- Connections
- 1 pair of types, where a type in seedwork.domain.mixins uses a type in seedwork.domain.rules.
- The types involved
src.seedwork.domain.mixins.BusinessRuleValidationMixin→src.seedwork.domain.rules.BusinessRule
- Direction
- seedwork.domain.mixins uses seedwork.domain.rules, so a change to seedwork.domain.rules can break seedwork.domain.mixins, while a change to seedwork.domain.mixins can't break seedwork.domain.rules.
- Position
- Below the diagonal: seedwork.domain.mixins uses a module listed above it, which is the healthy direction.
26→8 api.routers uses seedwork.domain.value_objects✕
- Connections
- 1 pair of types, where a type in api.routers uses a type in seedwork.domain.value_objects.
- The types involved
src.api.routers.catalog→src.seedwork.domain.value_objects.GenericUUID
- Direction
- api.routers uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break api.routers, while a change to api.routers can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: api.routers uses a module listed above it, which is the healthy direction.
26→9 api.routers uses api.models.bidding✕
- Connections
- 1 pair of types, where a type in api.routers uses a type in api.models.bidding.
- The types involved
src.api.routers.bidding→src.api.models.bidding.PlaceBidRequest
- Direction
- api.routers uses api.models.bidding, so a change to api.models.bidding can break api.routers, while a change to api.routers can't break api.models.bidding.
- Position
- Below the diagonal: api.routers uses a module listed above it, which is the healthy direction.
27→10 modules.bidding.application.command uses modules.bidding.application.command.place_bid✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.command uses a type in modules.bidding.application.command.place_bid.
- The types involved
src.modules.bidding.application.command.place_bid→src.modules.bidding.application.command.place_bid.PlaceBidCommand
- Direction
- modules.bidding.application.command uses modules.bidding.application.command.place_bid, so a change to modules.bidding.application.command.place_bid can break modules.bidding.application.command, while a change to modules.bidding.application.command can't break modules.bidding.application.command.place_bid.
- Position
- Below the diagonal: modules.bidding.application.command uses a module listed above it, which is the healthy direction.
27→11 modules.bidding.application.command uses modules.bidding.application.command.retract_bid✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.command uses a type in modules.bidding.application.command.retract_bid.
- The types involved
src.modules.bidding.application.command.retract_bid→src.modules.bidding.application.command.retract_bid.RetractBidCommand
- Direction
- modules.bidding.application.command uses modules.bidding.application.command.retract_bid, so a change to modules.bidding.application.command.retract_bid can break modules.bidding.application.command, while a change to modules.bidding.application.command can't break modules.bidding.application.command.retract_bid.
- Position
- Below the diagonal: modules.bidding.application.command uses a module listed above it, which is the healthy direction.
27→16 modules.bidding.application.command uses modules.bidding.domain.repositories✕
- Connections
- 2 pairs of types, where a type in modules.bidding.application.command uses a type in modules.bidding.domain.repositories.
- The types involved
src.modules.bidding.application.command.place_bid→src.modules.bidding.domain.repositories.ListingRepositorysrc.modules.bidding.application.command.retract_bid→src.modules.bidding.domain.repositories.ListingRepository
- Direction
- modules.bidding.application.command uses modules.bidding.domain.repositories, so a change to modules.bidding.domain.repositories can break modules.bidding.application.command, while a change to modules.bidding.application.command can't break modules.bidding.domain.repositories.
- Position
- Below the diagonal: modules.bidding.application.command uses a module listed above it, which is the healthy direction.
28→15 modules.bidding.application.event uses modules.bidding.domain.events✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.event uses a type in modules.bidding.domain.events.
- The types involved
src.modules.bidding.application.event.notify_outbid_winner→src.modules.bidding.domain.events.BidWasPlaced
- Direction
- modules.bidding.application.event uses modules.bidding.domain.events, so a change to modules.bidding.domain.events can break modules.bidding.application.event, while a change to modules.bidding.application.event can't break modules.bidding.domain.events.
- Position
- Below the diagonal: modules.bidding.application.event uses a module listed above it, which is the healthy direction.
28→16 modules.bidding.application.event uses modules.bidding.domain.repositories✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.event uses a type in modules.bidding.domain.repositories.
- The types involved
src.modules.bidding.application.event.when_listing_is_published_start_auction→src.modules.bidding.domain.repositories.ListingRepository
- Direction
- modules.bidding.application.event uses modules.bidding.domain.repositories, so a change to modules.bidding.domain.repositories can break modules.bidding.application.event, while a change to modules.bidding.application.event can't break modules.bidding.domain.repositories.
- Position
- Below the diagonal: modules.bidding.application.event uses a module listed above it, which is the healthy direction.
28→21 modules.bidding.application.event uses modules.catalog.domain.events✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.event uses a type in modules.catalog.domain.events.
- The types involved
src.modules.bidding.application.event.when_listing_is_published_start_auction→src.modules.catalog.domain.events.ListingPublishedEvent
- Direction
- modules.bidding.application.event uses modules.catalog.domain.events, so a change to modules.catalog.domain.events can break modules.bidding.application.event, while a change to modules.bidding.application.event can't break modules.catalog.domain.events.
- Position
- Below the diagonal: modules.bidding.application.event uses a module listed above it, which is the healthy direction.
29→22 modules.catalog.application.command uses modules.catalog.domain.repositories✕
- Connections
- 4 pairs of types, where a type in modules.catalog.application.command uses a type in modules.catalog.domain.repositories.
- The types involved
src.modules.catalog.application.command.create_listing_draft→src.modules.catalog.domain.repositories.ListingRepositorysrc.modules.catalog.application.command.delete_listing_draft→src.modules.catalog.domain.repositories.ListingRepositorysrc.modules.catalog.application.command.publish_listing_draft→src.modules.catalog.domain.repositories.ListingRepositorysrc.modules.catalog.application.command.update_listing_draft→src.modules.catalog.domain.repositories.ListingRepository
- Direction
- modules.catalog.application.command uses modules.catalog.domain.repositories, so a change to modules.catalog.domain.repositories can break modules.catalog.application.command, while a change to modules.catalog.application.command can't break modules.catalog.domain.repositories.
- Position
- Below the diagonal: modules.catalog.application.command uses a module listed above it, which is the healthy direction.
30→4 seedwork.domain.entities uses seedwork.domain.events✕
- Connections
- 1 pair of types, where a type in seedwork.domain.entities uses a type in seedwork.domain.events.
- The types involved
src.seedwork.domain.entities.AggregateRoot→src.seedwork.domain.events.DomainEvent
- Direction
- seedwork.domain.entities uses seedwork.domain.events, so a change to seedwork.domain.events can break seedwork.domain.entities, while a change to seedwork.domain.entities can't break seedwork.domain.events.
- Position
- Below the diagonal: seedwork.domain.entities uses a module listed above it, which is the healthy direction.
30→25 seedwork.domain.entities uses seedwork.domain.mixins✕
- Connections
- 1 pair of types, where a type in seedwork.domain.entities uses a type in seedwork.domain.mixins.
- The types involved
src.seedwork.domain.entities.AggregateRoot→src.seedwork.domain.mixins.BusinessRuleValidationMixin
- Direction
- seedwork.domain.entities uses seedwork.domain.mixins, so a change to seedwork.domain.mixins can break seedwork.domain.entities, while a change to seedwork.domain.entities can't break seedwork.domain.mixins.
- Position
- Below the diagonal: seedwork.domain.entities uses a module listed above it, which is the healthy direction.
31→4 modules.bidding.domain.entities uses seedwork.domain.events✕
- Connections
- 1 pair of types, where a type in modules.bidding.domain.entities uses a type in seedwork.domain.events.
- The types involved
src.modules.bidding.domain.entities.Listing→src.seedwork.domain.events.DomainEvent
- Direction
- modules.bidding.domain.entities uses seedwork.domain.events, so a change to seedwork.domain.events can break modules.bidding.domain.entities, while a change to modules.bidding.domain.entities can't break seedwork.domain.events.
- Position
- Below the diagonal: modules.bidding.domain.entities uses a module listed above it, which is the healthy direction.
31→5 modules.bidding.domain.entities uses seedwork.domain.exceptions✕
- Connections
- 3 pairs of types, where a type in modules.bidding.domain.entities uses a type in seedwork.domain.exceptions.
- The types involved
src.modules.bidding.domain.entities.BidCannotBeRetracted→src.seedwork.domain.exceptions.DomainExceptionsrc.modules.bidding.domain.entities.BidderIsNotBiddingListing→src.seedwork.domain.exceptions.DomainExceptionsrc.modules.bidding.domain.entities.ListingCannotBeCancelled→src.seedwork.domain.exceptions.DomainException
- Direction
- modules.bidding.domain.entities uses seedwork.domain.exceptions, so a change to seedwork.domain.exceptions can break modules.bidding.domain.entities, while a change to modules.bidding.domain.entities can't break seedwork.domain.exceptions.
- Position
- Below the diagonal: modules.bidding.domain.entities uses a module listed above it, which is the healthy direction.
31→8 modules.bidding.domain.entities uses seedwork.domain.value_objects✕
- Connections
- 1 pair of types, where a type in modules.bidding.domain.entities uses a type in seedwork.domain.value_objects.
- The types involved
src.modules.bidding.domain.entities.Listing→src.seedwork.domain.value_objects.Money
- Direction
- modules.bidding.domain.entities uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break modules.bidding.domain.entities, while a change to modules.bidding.domain.entities can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: modules.bidding.domain.entities uses a module listed above it, which is the healthy direction.
31→18 modules.bidding.domain.entities uses modules.bidding.domain.value_objects✕
- Connections
- 3 pairs of types, where a type in modules.bidding.domain.entities uses a type in modules.bidding.domain.value_objects.
- The types involved
src.modules.bidding.domain.entities.Listing→src.modules.bidding.domain.value_objects.Bidsrc.modules.bidding.domain.entities.Listing→src.modules.bidding.domain.value_objects.Biddersrc.modules.bidding.domain.entities.Listing→src.modules.bidding.domain.value_objects.Seller
- Direction
- modules.bidding.domain.entities uses modules.bidding.domain.value_objects, so a change to modules.bidding.domain.value_objects can break modules.bidding.domain.entities, while a change to modules.bidding.domain.entities can't break modules.bidding.domain.value_objects.
- Position
- Below the diagonal: modules.bidding.domain.entities uses a module listed above it, which is the healthy direction.
31→30 modules.bidding.domain.entities uses seedwork.domain.entities✕
- Connections
- 1 pair of types, where a type in modules.bidding.domain.entities uses a type in seedwork.domain.entities.
- The types involved
src.modules.bidding.domain.entities.Listing→src.seedwork.domain.entities.AggregateRoot
- Direction
- modules.bidding.domain.entities uses seedwork.domain.entities, so a change to seedwork.domain.entities can break modules.bidding.domain.entities, while a change to modules.bidding.domain.entities can't break seedwork.domain.entities.
- Position
- Below the diagonal: modules.bidding.domain.entities uses a module listed above it, which is the healthy direction.
32→8 modules.catalog.domain.entities uses seedwork.domain.value_objects✕
- Connections
- 3 pairs of types, where a type in modules.catalog.domain.entities uses a type in seedwork.domain.value_objects.
- The types involved
src.modules.catalog.domain.entities.Listing→src.seedwork.domain.value_objects.GenericUUIDsrc.modules.catalog.domain.entities.Listing→src.seedwork.domain.value_objects.Moneysrc.modules.catalog.domain.entities.Seller→src.seedwork.domain.value_objects.GenericUUID
- Direction
- modules.catalog.domain.entities uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break modules.catalog.domain.entities, while a change to modules.catalog.domain.entities can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: modules.catalog.domain.entities uses a module listed above it, which is the healthy direction.
32→30 modules.catalog.domain.entities uses seedwork.domain.entities✕
- Connections
- 2 pairs of types, where a type in modules.catalog.domain.entities uses a type in seedwork.domain.entities.
- The types involved
src.modules.catalog.domain.entities.Listing→src.seedwork.domain.entities.AggregateRootsrc.modules.catalog.domain.entities.Seller→src.seedwork.domain.entities.AggregateRoot
- Direction
- modules.catalog.domain.entities uses seedwork.domain.entities, so a change to seedwork.domain.entities can break modules.catalog.domain.entities, while a change to modules.catalog.domain.entities can't break seedwork.domain.entities.
- Position
- Below the diagonal: modules.catalog.domain.entities uses a module listed above it, which is the healthy direction.
33→8 modules.iam.domain.entities uses seedwork.domain.value_objects✕
- Connections
- 2 pairs of types, where a type in modules.iam.domain.entities uses a type in seedwork.domain.value_objects.
- The types involved
src.modules.iam.domain.entities.User→src.seedwork.domain.value_objects.Emailsrc.modules.iam.domain.entities.User→src.seedwork.domain.value_objects.GenericUUID
- Direction
- modules.iam.domain.entities uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break modules.iam.domain.entities, while a change to modules.iam.domain.entities can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: modules.iam.domain.entities uses a module listed above it, which is the healthy direction.
33→30 modules.iam.domain.entities uses seedwork.domain.entities✕
- Connections
- 1 pair of types, where a type in modules.iam.domain.entities uses a type in seedwork.domain.entities.
- The types involved
src.modules.iam.domain.entities.User→src.seedwork.domain.entities.AggregateRoot
- Direction
- modules.iam.domain.entities uses seedwork.domain.entities, so a change to seedwork.domain.entities can break modules.iam.domain.entities, while a change to modules.iam.domain.entities can't break seedwork.domain.entities.
- Position
- Below the diagonal: modules.iam.domain.entities uses a module listed above it, which is the healthy direction.
34→6 seedwork.infrastructure.repository uses seedwork.domain.repositories✕
- Connections
- 2 pairs of types, where a type in seedwork.infrastructure.repository uses a type in seedwork.domain.repositories.
- The types involved
src.seedwork.infrastructure.repository.InMemoryRepository→src.seedwork.domain.repositories.GenericRepositorysrc.seedwork.infrastructure.repository.SqlAlchemyGenericRepository→src.seedwork.domain.repositories.GenericRepository
- Direction
- seedwork.infrastructure.repository uses seedwork.domain.repositories, so a change to seedwork.domain.repositories can break seedwork.infrastructure.repository, while a change to seedwork.infrastructure.repository can't break seedwork.domain.repositories.
- Position
- Below the diagonal: seedwork.infrastructure.repository uses a module listed above it, which is the healthy direction.
34→8 seedwork.infrastructure.repository uses seedwork.domain.value_objects✕
- Connections
- 2 pairs of types, where a type in seedwork.infrastructure.repository uses a type in seedwork.domain.value_objects.
- The types involved
src.seedwork.infrastructure.repository.InMemoryRepository→src.seedwork.domain.value_objects.GenericUUIDsrc.seedwork.infrastructure.repository.SqlAlchemyGenericRepository→src.seedwork.domain.value_objects.GenericUUID
- Direction
- seedwork.infrastructure.repository uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break seedwork.infrastructure.repository, while a change to seedwork.infrastructure.repository can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: seedwork.infrastructure.repository uses a module listed above it, which is the healthy direction.
34→30 seedwork.infrastructure.repository uses seedwork.domain.entities✕
- Connections
- 2 pairs of types, where a type in seedwork.infrastructure.repository uses a type in seedwork.domain.entities.
- The types involved
src.seedwork.infrastructure.repository.InMemoryRepository→src.seedwork.domain.entities.Entitysrc.seedwork.infrastructure.repository.SqlAlchemyGenericRepository→src.seedwork.domain.entities.Entity
- Direction
- seedwork.infrastructure.repository uses seedwork.domain.entities, so a change to seedwork.domain.entities can break seedwork.infrastructure.repository, while a change to seedwork.infrastructure.repository can't break seedwork.domain.entities.
- Position
- Below the diagonal: seedwork.infrastructure.repository uses a module listed above it, which is the healthy direction.
35→5 api uses seedwork.domain.exceptions✕
- Connections
- 2 pairs of types, where a type in api uses a type in seedwork.domain.exceptions.
- The types involved
src.api.main→src.seedwork.domain.exceptions.DomainExceptionsrc.api.main→src.seedwork.domain.exceptions.EntityNotFoundException
- Direction
- api uses seedwork.domain.exceptions, so a change to seedwork.domain.exceptions can break api, while a change to api can't break seedwork.domain.exceptions.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
35→33 api uses modules.iam.domain.entities✕
- Connections
- 1 pair of types, where a type in api uses a type in modules.iam.domain.entities.
- The types involved
src.api.dependencies→src.modules.iam.domain.entities.User
- Direction
- api uses modules.iam.domain.entities, so a change to modules.iam.domain.entities can break api, while a change to api can't break modules.iam.domain.entities.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
36→16 modules.bidding.infrastructure.listing_repository uses modules.bidding.domain.repositories✕
- Connections
- 1 pair of types, where a type in modules.bidding.infrastructure.listing_repository uses a type in modules.bidding.domain.repositories.
- The types involved
src.modules.bidding.infrastructure.listing_repository.PostgresJsonListingRepository→src.modules.bidding.domain.repositories.ListingRepository
- Direction
- modules.bidding.infrastructure.listing_repository uses modules.bidding.domain.repositories, so a change to modules.bidding.domain.repositories can break modules.bidding.infrastructure.listing_repository, while a change to modules.bidding.infrastructure.listing_repository can't break modules.bidding.domain.repositories.
- Position
- Below the diagonal: modules.bidding.infrastructure.listing_repository uses a module listed above it, which is the healthy direction.
36→31 modules.bidding.infrastructure.listing_repository uses modules.bidding.domain.entities✕
- Connections
- 1 pair of types, where a type in modules.bidding.infrastructure.listing_repository uses a type in modules.bidding.domain.entities.
- The types involved
src.modules.bidding.infrastructure.listing_repository.ListingDataMapper→src.modules.bidding.domain.entities.Listing
- Direction
- modules.bidding.infrastructure.listing_repository uses modules.bidding.domain.entities, so a change to modules.bidding.domain.entities can break modules.bidding.infrastructure.listing_repository, while a change to modules.bidding.infrastructure.listing_repository can't break modules.bidding.domain.entities.
- Position
- Below the diagonal: modules.bidding.infrastructure.listing_repository uses a module listed above it, which is the healthy direction.
36→34 modules.bidding.infrastructure.listing_repository uses seedwork.infrastructure.repository✕
- Connections
- 1 pair of types, where a type in modules.bidding.infrastructure.listing_repository uses a type in seedwork.infrastructure.repository.
- The types involved
src.modules.bidding.infrastructure.listing_repository.PostgresJsonListingRepository→src.seedwork.infrastructure.repository.SqlAlchemyGenericRepository
- Direction
- modules.bidding.infrastructure.listing_repository uses seedwork.infrastructure.repository, so a change to seedwork.infrastructure.repository can break modules.bidding.infrastructure.listing_repository, while a change to modules.bidding.infrastructure.listing_repository can't break seedwork.infrastructure.repository.
- Position
- Below the diagonal: modules.bidding.infrastructure.listing_repository uses a module listed above it, which is the healthy direction.
37→22 modules.catalog.infrastructure.listing_repository uses modules.catalog.domain.repositories✕
- Connections
- 1 pair of types, where a type in modules.catalog.infrastructure.listing_repository uses a type in modules.catalog.domain.repositories.
- The types involved
src.modules.catalog.infrastructure.listing_repository.PostgresJsonListingRepository→src.modules.catalog.domain.repositories.ListingRepository
- Direction
- modules.catalog.infrastructure.listing_repository uses modules.catalog.domain.repositories, so a change to modules.catalog.domain.repositories can break modules.catalog.infrastructure.listing_repository, while a change to modules.catalog.infrastructure.listing_repository can't break modules.catalog.domain.repositories.
- Position
- Below the diagonal: modules.catalog.infrastructure.listing_repository uses a module listed above it, which is the healthy direction.
37→32 modules.catalog.infrastructure.listing_repository uses modules.catalog.domain.entities✕
- Connections
- 1 pair of types, where a type in modules.catalog.infrastructure.listing_repository uses a type in modules.catalog.domain.entities.
- The types involved
src.modules.catalog.infrastructure.listing_repository.ListingDataMapper→src.modules.catalog.domain.entities.Listing
- Direction
- modules.catalog.infrastructure.listing_repository uses modules.catalog.domain.entities, so a change to modules.catalog.domain.entities can break modules.catalog.infrastructure.listing_repository, while a change to modules.catalog.infrastructure.listing_repository can't break modules.catalog.domain.entities.
- Position
- Below the diagonal: modules.catalog.infrastructure.listing_repository uses a module listed above it, which is the healthy direction.
37→34 modules.catalog.infrastructure.listing_repository uses seedwork.infrastructure.repository✕
- Connections
- 1 pair of types, where a type in modules.catalog.infrastructure.listing_repository uses a type in seedwork.infrastructure.repository.
- The types involved
src.modules.catalog.infrastructure.listing_repository.PostgresJsonListingRepository→src.seedwork.infrastructure.repository.SqlAlchemyGenericRepository
- Direction
- modules.catalog.infrastructure.listing_repository uses seedwork.infrastructure.repository, so a change to seedwork.infrastructure.repository can break modules.catalog.infrastructure.listing_repository, while a change to modules.catalog.infrastructure.listing_repository can't break seedwork.infrastructure.repository.
- Position
- Below the diagonal: modules.catalog.infrastructure.listing_repository uses a module listed above it, which is the healthy direction.
38→8 modules.iam.infrastructure.repository uses seedwork.domain.value_objects✕
- Connections
- 1 pair of types, where a type in modules.iam.infrastructure.repository uses a type in seedwork.domain.value_objects.
- The types involved
src.modules.iam.infrastructure.repository.PostgresJsonUserRepository→src.seedwork.domain.value_objects.Email
- Direction
- modules.iam.infrastructure.repository uses seedwork.domain.value_objects, so a change to seedwork.domain.value_objects can break modules.iam.infrastructure.repository, while a change to modules.iam.infrastructure.repository can't break seedwork.domain.value_objects.
- Position
- Below the diagonal: modules.iam.infrastructure.repository uses a module listed above it, which is the healthy direction.
38→24 modules.iam.infrastructure.repository uses modules.iam.application.repository✕
- Connections
- 1 pair of types, where a type in modules.iam.infrastructure.repository uses a type in modules.iam.application.repository.
- The types involved
src.modules.iam.infrastructure.repository.PostgresJsonUserRepository→src.modules.iam.application.repository.UserRepository
- Direction
- modules.iam.infrastructure.repository uses modules.iam.application.repository, so a change to modules.iam.application.repository can break modules.iam.infrastructure.repository, while a change to modules.iam.infrastructure.repository can't break modules.iam.application.repository.
- Position
- Below the diagonal: modules.iam.infrastructure.repository uses a module listed above it, which is the healthy direction.
38→33 modules.iam.infrastructure.repository uses modules.iam.domain.entities✕
- Connections
- 1 pair of types, where a type in modules.iam.infrastructure.repository uses a type in modules.iam.domain.entities.
- The types involved
src.modules.iam.infrastructure.repository.UserDataMapper→src.modules.iam.domain.entities.User
- Direction
- modules.iam.infrastructure.repository uses modules.iam.domain.entities, so a change to modules.iam.domain.entities can break modules.iam.infrastructure.repository, while a change to modules.iam.infrastructure.repository can't break modules.iam.domain.entities.
- Position
- Below the diagonal: modules.iam.infrastructure.repository uses a module listed above it, which is the healthy direction.
38→34 modules.iam.infrastructure.repository uses seedwork.infrastructure.repository✕
- Connections
- 1 pair of types, where a type in modules.iam.infrastructure.repository uses a type in seedwork.infrastructure.repository.
- The types involved
src.modules.iam.infrastructure.repository.PostgresJsonUserRepository→src.seedwork.infrastructure.repository.SqlAlchemyGenericRepository
- Direction
- modules.iam.infrastructure.repository uses seedwork.infrastructure.repository, so a change to seedwork.infrastructure.repository can break modules.iam.infrastructure.repository, while a change to modules.iam.infrastructure.repository can't break seedwork.infrastructure.repository.
- Position
- Below the diagonal: modules.iam.infrastructure.repository uses a module listed above it, which is the healthy direction.
39→12 modules.bidding.application.query uses modules.bidding.application.query.get_bidding_details✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.query uses a type in modules.bidding.application.query.get_bidding_details.
- The types involved
src.modules.bidding.application.query.get_bidding_details→src.modules.bidding.application.query.get_bidding_details.GetBiddingDetails
- Direction
- modules.bidding.application.query uses modules.bidding.application.query.get_bidding_details, so a change to modules.bidding.application.query.get_bidding_details can break modules.bidding.application.query, while a change to modules.bidding.application.query can't break modules.bidding.application.query.get_bidding_details.
- Position
- Below the diagonal: modules.bidding.application.query uses a module listed above it, which is the healthy direction.
39→13 modules.bidding.application.query uses modules.bidding.application.query.get_pastdue_listings✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.query uses a type in modules.bidding.application.query.get_pastdue_listings.
- The types involved
src.modules.bidding.application.query.get_pastdue_listings→src.modules.bidding.application.query.get_pastdue_listings.GetPastdueListings
- Direction
- modules.bidding.application.query uses modules.bidding.application.query.get_pastdue_listings, so a change to modules.bidding.application.query.get_pastdue_listings can break modules.bidding.application.query, while a change to modules.bidding.application.query can't break modules.bidding.application.query.get_pastdue_listings.
- Position
- Below the diagonal: modules.bidding.application.query uses a module listed above it, which is the healthy direction.
39→14 modules.bidding.application.query uses modules.bidding.application.query.model_mappers✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.query uses a type in modules.bidding.application.query.model_mappers.
- The types involved
src.modules.bidding.application.query.get_bidding_details→src.modules.bidding.application.query.model_mappers.ListingDAO
- Direction
- modules.bidding.application.query uses modules.bidding.application.query.model_mappers, so a change to modules.bidding.application.query.model_mappers can break modules.bidding.application.query, while a change to modules.bidding.application.query can't break modules.bidding.application.query.model_mappers.
- Position
- Below the diagonal: modules.bidding.application.query uses a module listed above it, which is the healthy direction.
39→16 modules.bidding.application.query uses modules.bidding.domain.repositories✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.query uses a type in modules.bidding.domain.repositories.
- The types involved
src.modules.bidding.application.query.get_pastdue_listings→src.modules.bidding.domain.repositories.ListingRepository
- Direction
- modules.bidding.application.query uses modules.bidding.domain.repositories, so a change to modules.bidding.domain.repositories can break modules.bidding.application.query, while a change to modules.bidding.application.query can't break modules.bidding.domain.repositories.
- Position
- Below the diagonal: modules.bidding.application.query uses a module listed above it, which is the healthy direction.
39→36 modules.bidding.application.query uses modules.bidding.infrastructure.listing_repository✕
- Connections
- 1 pair of types, where a type in modules.bidding.application.query uses a type in modules.bidding.infrastructure.listing_repository.
- The types involved
src.modules.bidding.application.query.model_mappers→src.modules.bidding.infrastructure.listing_repository.ListingModel
- Direction
- modules.bidding.application.query uses modules.bidding.infrastructure.listing_repository, so a change to modules.bidding.infrastructure.listing_repository can break modules.bidding.application.query, while a change to modules.bidding.application.query can't break modules.bidding.infrastructure.listing_repository.
- Position
- Below the diagonal: modules.bidding.application.query uses a module listed above it, which is the healthy direction.
40→19 modules.catalog.application.query uses modules.catalog.application.query.get_listing_details✕
- Connections
- 1 pair of types, where a type in modules.catalog.application.query uses a type in modules.catalog.application.query.get_listing_details.
- The types involved
src.modules.catalog.application.query.get_listing_details→src.modules.catalog.application.query.get_listing_details.GetListingDetails
- Direction
- modules.catalog.application.query uses modules.catalog.application.query.get_listing_details, so a change to modules.catalog.application.query.get_listing_details can break modules.catalog.application.query, while a change to modules.catalog.application.query can't break modules.catalog.application.query.get_listing_details.
- Position
- Below the diagonal: modules.catalog.application.query uses a module listed above it, which is the healthy direction.
40→20 modules.catalog.application.query uses modules.catalog.application.query.get_listings_of_seller✕
- Connections
- 1 pair of types, where a type in modules.catalog.application.query uses a type in modules.catalog.application.query.get_listings_of_seller.
- The types involved
src.modules.catalog.application.query.get_listings_of_seller→src.modules.catalog.application.query.get_listings_of_seller.GetListingsOfSeller
- Direction
- modules.catalog.application.query uses modules.catalog.application.query.get_listings_of_seller, so a change to modules.catalog.application.query.get_listings_of_seller can break modules.catalog.application.query, while a change to modules.catalog.application.query can't break modules.catalog.application.query.get_listings_of_seller.
- Position
- Below the diagonal: modules.catalog.application.query uses a module listed above it, which is the healthy direction.
40→37 modules.catalog.application.query uses modules.catalog.infrastructure.listing_repository✕
- Connections
- 1 pair of types, where a type in modules.catalog.application.query uses a type in modules.catalog.infrastructure.listing_repository.
- The types involved
src.modules.catalog.application.query.model_mappers→src.modules.catalog.infrastructure.listing_repository.ListingModel
- Direction
- modules.catalog.application.query uses modules.catalog.infrastructure.listing_repository, so a change to modules.catalog.infrastructure.listing_repository can break modules.catalog.application.query, while a change to modules.catalog.application.query can't break modules.catalog.infrastructure.listing_repository.
- Position
- Below the diagonal: modules.catalog.application.query 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 |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 15 | High / Critical |
| A05:2025 — Injection | 6 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | Medium |
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing; Resolve the 11 Orphaned file finding(s) in Knowledge Freshness — start with functional.py, __init__.py, container.py; Turn off SQLAlchemy create_all() in production and let the versioned migrations own the schema.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing. | +5.8 pts | Medium | Security & performance tooling |
| Resolve the 11 Orphaned file finding(s) in Knowledge Freshness — start with functional.py, __init__.py, container.py. | +3.8 pts | Medium | Knowledge Freshness |
| Turn off SQLAlchemy create_all() in production and let the versioned migrations own the schema. | +3.0 pts | Medium | Schema migrations |
| Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters). | +2.3 pts | Medium | Encapsulated state |
| Grow the ADR log (currently 6) — reach 8 to raise the maturity tier; document significant decisions as they're made. | +2.1 pts | Medium | Architecture documentation |
| Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs. | +1.9 pts | Medium | Strongly-typed ids |
| Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding. | +1.6 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.6 pts | Medium | Release Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.3 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| src/modules/catalog/application/query/get_listings_of_seller.py | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| src/modules/bidding/domain/services.py | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/modules/bidding/application/query/get_pastdue_listings.py | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/modules/bidding/application/command/place_bid.py | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/config/container.py | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/api/routers/bidding.py | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/api/routers/iam.py | 8.2 | Near-clean | Explicit Debt: TodoComment |
| migrations/env.py | 8.5 | Near-clean | Code Duplication: Duplicated block (41 lines × 2) |
| src/seedwork/application/__init__.py | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: Application (LCOM4 5) |
| REDACTED | 9.0 | Near-clean | IaC & Container Security: Low IaC: REDACTED |
| docs/architecture_decision_log/006_error_handling_during_operation_execution.md | 9.3 | Near-clean | ADR Quality: ADR Decision section is empty |
| docs/architecture_decision_log/005_separate_commands_and_queries.md | 9.5 | Near-clean | ADR Quality: ADR has no Decision section |
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 68 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 — 68 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, 66 of 74 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.py) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- 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 (3 contributor(s) across 73 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 2 hold 1.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — 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 (pyproject.toml), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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 dependency-injector, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, 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.
- X5 Nullable reference types — 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
1 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (41 lines × 2) finding(s) in Code Duplication — start with env.py. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 11 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with __init__.py. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
What to do
- Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D9 · Test Distribution
80 test methods: 80 unit, 0 integration, 0 BDD, 0 e2e. The Python suite contributes 80 test function(s) across 25 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Python (repository root, 26 test files): measured (0 flaky).
D12 · Dependency Hygiene
1 outdated, 0 yanked pinned Python distributions. 1 of 23 shipped distributions were graded against pypi.org (0 not published there, 22 declared without an exact pin, which installs the newest release the declaration admits and so cannot be behind one). Only EXACT pins are graded for currency: a floor or a range already installs the newest release it admits, so reporting one would report this repository for being current. Whether a deliberate upper cap has itself gone stale is a different and weaker question, and is not asked. Whether any distribution is UNMAINTAINED is not graded — PyPI publishes no maintenance status, and release age does not stand in for one. Lockfiles are not read (REDACTED, uv.lock, Pipfile.lock, pdm.lock), so a lock-resolved install is outside this verdict. Known CVEs in this dependency graph are D30's question.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 62 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 23 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (39 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. 3 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
7 deducted task-comment markers across 3015 LoC (0.1/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 6 TodoComment finding(s) in Explicit Debt — start with services.py, get_pastdue_listings.py, place_bid.py. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with get_listings_of_seller.py. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 8 document(s) read across 1 unit(s).
D20 · ADR Quality
2 of 6 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What to do
- Resolve the 1 ADR has no Decision section finding(s) in ADR Quality — start with 005_separate_commands_and_queries.md. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 ADR Decision section is empty finding(s) in ADR Quality — start with 006_error_handling_during_operation_execution.md. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 ADR Consequences section is empty finding(s) in ADR Quality — start with 006_error_handling_during_operation_execution.md. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
No domain types are scored-flagged across 3 context boundaries; 1 contract project(s) carry advisory strong-ID notes. Contexts: bidding, catalog, iam.
D26 · Project Cohesion
0 of 1 build units (Python) flagged as possibly oversized/incoherent.
D27 · Navigability
63 % of calls cross a namespace and 0 % go through an interface, but 57 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
6 finding(s): 0 critical, 3 high, 3 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
15 finding(s): 3 critical, 7 high, 5 medium, 0 low.
What to do
- Resolve the 7 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
2 finding(s): 0 critical, 0 high, 0 medium, 2 low.
D34 · Knowledge Freshness
11 of 11 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/seedwork/utils/functional.py. Counted over 11 of the 107 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 11 Orphaned file finding(s) in Knowledge Freshness — start with functional.py, __init__.py, container.py. — One of this dimension's main actionable groups (11 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 23 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
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.
What to do
- Name the access rules — DRF permission classes, django-guardian or django-rules permissions, a casbin or oso policy, or roles and permissions declared once — and consult them where access is checked (permission_classes, @permission_required, Depends), so the rule set is reviewable and testable on its own.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM2 · Strongly-typed ids
- `BidWasPlaced.listing_id` is a raw `GenericUUID` — give it a strongly-typed id: a dedicated single-field type wrapping the `GenericUUID`, in whatever form your language spells that. — src/modules/bidding/domain/events.py:5
- `BidWasPlaced.bidder_id` is a raw `GenericUUID` — give it a strongly-typed id: a dedicated single-field type wrapping the `GenericUUID`, in whatever form your language spells that. — src/modules/bidding/domain/events.py:5
- `HighestBidderWasOutbid.listing_id` is a raw `GenericUUID` — give it a strongly-typed id: a dedicated single-field type wrapping the `GenericUUID`, in whatever form your language spells that. — src/modules/bidding/domain/events.py:10
- `HighestBidderWasOutbid.outbid_bidder_id` is a raw `GenericUUID` — give it a strongly-typed id: a dedicated single-field type wrapping the `GenericUUID`, in whatever form your language spells that. — src/modules/bidding/domain/events.py:10
- `Listing.seller_id` is a raw `GenericUUID` — give it a strongly-typed id: a dedicated single-field type wrapping the `GenericUUID`, in whatever form your language spells that. — src/modules/catalog/domain/entities.py:19
- `Seller.id` is a raw `GenericUUID` — give it a strongly-typed id: a dedicated single-field type wrapping the `GenericUUID`, in whatever form your language spells that. — src/modules/catalog/domain/entities.py:45
- `ListingDraftCreatedEvent.listing_id` is a raw `GenericUUID` — give it a strongly-typed id: a dedicated single-field type wrapping the `GenericUUID`, in whatever form your language spells that. — src/modules/catalog/domain/events.py:5
- `ListingDraftUpdatedEvent.listing_id` is a raw `GenericUUID` — give it a strongly-typed id: a dedicated single-field type wrapping the `GenericUUID`, in whatever form your language spells that. — src/modules/catalog/domain/events.py:9
- `ListingDraftDeletedEvent.listing_id` is a raw `GenericUUID` — give it a strongly-typed id: a dedicated single-field type wrapping the `GenericUUID`, in whatever form your language spells that. — src/modules/catalog/domain/events.py:13
- `ListingPublishedEvent.listing_id` is a raw `GenericUUID` — give it a strongly-typed id: a dedicated single-field type wrapping the `GenericUUID`, in whatever form your language spells that. — src/modules/catalog/domain/events.py:17
- `ListingPublishedEvent.seller_id` is a raw `GenericUUID` — give it a strongly-typed id: a dedicated single-field type wrapping the `GenericUUID`, in whatever form your language spells that. — src/modules/catalog/domain/events.py:17
- `User.id` is a raw `GenericUUID` — give it a strongly-typed id: a dedicated single-field type wrapping the `GenericUUID`, in whatever form your language spells that. — src/modules/iam/domain/entities.py:10
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model
- `AnonymousUser` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/modules/iam/domain/entities.py:26
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `Listing` exposes publicly writable state (seller, ask_price, starts_at, ends_at, bids). — src/modules/bidding/domain/entities.py:36
- `Listing` exposes publicly writable state (title, description, ask_price, seller_id). — src/modules/catalog/domain/entities.py:19
- `Seller` exposes publicly writable state (id, is_new, currently_published_listings_count). — src/modules/catalog/domain/entities.py:45
- `User` exposes publicly writable state (username, id, email, password_hash, access_token, is_superuser). — src/modules/iam/domain/entities.py:10
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
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.
M2 · Architecture documentation
What to do
- Grow the ADR log (currently 6) — reach 8 to raise the maturity tier; document significant decisions as they're made.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry-sdk) and a health-check endpoint (a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 1111 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:6
What to do
- Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P8 · Schema migrations
- This repository versions its schema (Alembic), but SQLAlchemy create_all() here builds or alters the schema from the model as well, outside that history — the two paths can disagree about the shape, and a change made this way is never a reviewed migration. Turn it off and let Alembic own the schema. (×2) — src/cli/__main__.py:29, src/api/main.py:23
What to do
- Turn off SQLAlchemy create_all() in production and let the versioned migrations own the schema.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X17 · Uncapped recursion over a caller-supplied document
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
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 99% | Exemplary | Solid. |
| Architecture | 83% | Strong | Solid. |
| Maturity | 59% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 32% | Weak — gated by D12, P3, P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 80% | Strong | Solid. |
| Domain Modelling | 58% | Adequate — gated by DM2, DM5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — a class or table named for it — django-simple-history, django-auditlog, django-reversion, django-pghistory or SQLAlchemy-Continuum recording each change, or an event-sourced store beside one) 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.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 60 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — This repository has no user interface to render — no markup (HTML, Razor, JSX, Vue, Svelte or server templates), no UI framework dependency, no UI component source and no native UI project — so WCAG's runtime success criteria have nothing to apply to here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~1578 lines of test source are present (.py) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Python not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — None of 5 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — The CI pipeline 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.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Python build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 14 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (command argument 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Python source (service entry point: src/api/__main__.py:5 (uvicorn.run())
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, 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.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- 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.
- X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 13 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 24 finding(s)
- TodoComment src/modules/bidding/domain/services.py:1
- TodoComment src/modules/bidding/application/query/get_pastdue_listings.py:18
- TodoComment src/modules/bidding/application/command/place_bid.py:13
- TodoComment src/config/container.py:50
- TodoComment src/api/routers/bidding.py:48
- TodoComment src/api/routers/iam.py:44
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Mutable entity: Listing src/modules/bidding/domain/entities.py:36
- Mutable entity: Listing src/modules/catalog/domain/entities.py:19
- Mutable entity: Seller src/modules/catalog/domain/entities.py:45
- Mutable entity: User src/modules/iam/domain/entities.py:10
- REDACTED
- REDACTED
- Schema created by SQLAlchemy create_all() outside the migrations src/cli/__main__.py:29
- Schema created by SQLAlchemy create_all() outside the migrations src/api/main.py:23
- FixmeComment src/modules/catalog/application/query/get_listings_of_seller.py:16
- REDACTED
- Duplicated block (41 lines × 2) migrations/env.py:37
- Low cohesion: Application (LCOM4 5) src/seedwork/application/__init__.py:247
- Anemic entity: AnonymousUser src/modules/iam/domain/entities.py:26
Minor — 35 finding(s)
- Primitive id on a domain type: BidWasPlaced.listing_id src/modules/bidding/domain/events.py:5
- Primitive id on a domain type: BidWasPlaced.bidder_id src/modules/bidding/domain/events.py:5
- Primitive id on a domain type: HighestBidderWasOutbid.listing_id src/modules/bidding/domain/events.py:10
- Primitive id on a domain type: HighestBidderWasOutbid.outbid_bidder_id src/modules/bidding/domain/events.py:10
- Primitive id on a domain type: Listing.seller_id src/modules/catalog/domain/entities.py:19
- Primitive id on a domain type: Seller.id src/modules/catalog/domain/entities.py:45
- Primitive id on a domain type: ListingDraftCreatedEvent.listing_id src/modules/catalog/domain/events.py:5
- Primitive id on a domain type: ListingDraftUpdatedEvent.listing_id src/modules/catalog/domain/events.py:9
- Primitive id on a domain type: ListingDraftDeletedEvent.listing_id src/modules/catalog/domain/events.py:13
- Primitive id on a domain type: ListingPublishedEvent.listing_id src/modules/catalog/domain/events.py:17
- Primitive id on a domain type: ListingPublishedEvent.seller_id src/modules/catalog/domain/events.py:17
- Primitive id on a domain type: User.id src/modules/iam/domain/entities.py:10
- Orphaned file src/seedwork/utils/functional.py:1
- Orphaned file src/seedwork/application/__init__.py:1
- Orphaned file src/config/container.py:1
- Orphaned file src/seedwork/infrastructure/repository.py:1
- Orphaned file src/seedwork/infrastructure/logging.py:1
- Orphaned file src/modules/bidding/domain/entities.py:1
- Orphaned file src/api/routers/catalog.py:1
- Orphaned file src/modules/bidding/infrastructure/listing_repository.py:1
- Orphaned file src/api/main.py:1
- Orphaned file src/api/routers/bidding.py:1
- Orphaned file src/seedwork/application/events.py:1
- REDACTED
- REDACTED
- No named authorization policies
- ADR has no Decision section docs/architecture_decision_log/005_separate_commands_and_queries.md:1
- ADR Decision section is empty docs/architecture_decision_log/006_error_handling_during_operation_execution.md:30
- ADR Consequences section is empty docs/architecture_decision_log/006_error_handling_during_operation_execution.md:35
- Scattered collaborators
- Orphaned files with no living knowledge
- REDACTED
- No SAST REDACTED:6
- No rollback/health safety
- No changelog
Minor — 2 finding(s)
- Outdated: click
- EventResult: 1 contract type(s) expose producer-owned ids/enums
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-b7c689c25b524c20901cde232b4094ac/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b7c689c25b524c20901cde232b4094ac/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 6 | 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 . | 15 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |