Executive summary
Enforcer/clean-architecture is rated At risk because critical security findings are open. Its score is held back because we found no logging, tracing or health checks in the code and 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 28, is the weakest lens and counts most in the score. The best first step is replacing each retired release, worth about 10 points. Logging through a logging library would lift Production Readiness itself, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 65.
Seven known security holes in the packages the code depends on can be used by attackers. Four settings leave the servers or containers unsafe, and two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages, correcting the unsafe settings and pinning each tool to an exact version would close these risks. Fixing the weaknesses the scanner points to would fix the security weakness in the code. The package under a licence on your banned list needs replacing, or clearing with your legal team.
The product code is 1,953 lines, about €3,200 to rebuild.
If Production Readiness rose from 28 to 70, the lowest score rated Strong, the score would rise from 50 to about 65.
New since the last survey: 2 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 1 finding
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Rebuild cost: about €3,200 · Estimate
| Cost to rebuild | €1,100 to €5,400, for 18 to 57 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 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 | Very small: 1,953 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 auctions.auctions.application.queries.auctions | 2 auctions.auctions.domain.entities.bid | 3 auctions.auctions.domain.events | 4 auctions.auctions.domain.exceptions | 5 auctions_infrastructure.auctions_infrastructure | 6 auctions_infrastructure.auctions_infrastructure.queries | 7 auctions_infrastructure.auctions_infrastructure.queries.base | 8 auctions_infrastructure.auctions_infrastructure.repositories.auctions | 9 customer_relationship.customer_relationship.config | 10 customer_relationship.customer_relationship.emails | 11 foundation.foundation.serializing | 12 foundation.foundation.value_objects.money | 13 main.main | 14 payments.payments.api.requests | 15 payments.payments.config | 16 payments.payments.dao | 17 payments.payments.events | 18 processes.processes.paying_for_won_item.saga | 19 processes.processes.repository | 20 shipping.shipping.domain.entities.address | 21 auctions.auctions.domain.entities.auction | 22 auctions_infrastructure.auctions_infrastructure.queries.auctions | 23 customer_relationship.customer_relationship.email_sender | 24 customer_relationship.customer_relationship.facade | 25 foundation.foundation | 26 foundation.foundation.value_objects.factories | 27 main | 28 payments.payments.api.consumer | 29 payments.payments.facade | 30 processes.processes | 31 processes.processes.paying_for_won_item.saga_handler | 32 shipping.shipping.application.repositories.address | 33 auctions.auctions.application.repositories.auctions | 34 customer_relationship.customer_relationship | 35 payments.payments | 36 auctions.auctions.application.use_cases.beginning_auction | 37 auctions.auctions.application.use_cases.ending_auction | 38 auctions.auctions.application.use_cases.placing_bid | 39 auctions.auctions.application.use_cases.withdrawing_bids | 40 auctions.auctions |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 auctions.auctions.application.queries.auctions | ||||||||||||||||||||||||||||||||||||||||
| 2 auctions.auctions.domain.entities.bid | ||||||||||||||||||||||||||||||||||||||||
| 3 auctions.auctions.domain.events | ||||||||||||||||||||||||||||||||||||||||
| 4 auctions.auctions.domain.exceptions | ||||||||||||||||||||||||||||||||||||||||
| 5 auctions_infrastructure.auctions_infrastructure | ||||||||||||||||||||||||||||||||||||||||
| 6 auctions_infrastructure.auctions_infrastructure.queries | ||||||||||||||||||||||||||||||||||||||||
| 7 auctions_infrastructure.auctions_infrastructure.queries.base | ||||||||||||||||||||||||||||||||||||||||
| 8 auctions_infrastructure.auctions_infrastructure.repositories.auctions | ||||||||||||||||||||||||||||||||||||||||
| 9 customer_relationship.customer_relationship.config | ||||||||||||||||||||||||||||||||||||||||
| 10 customer_relationship.customer_relationship.emails | ||||||||||||||||||||||||||||||||||||||||
| 11 foundation.foundation.serializing | ||||||||||||||||||||||||||||||||||||||||
| 12 foundation.foundation.value_objects.money | ||||||||||||||||||||||||||||||||||||||||
| 13 main.main | ||||||||||||||||||||||||||||||||||||||||
| 14 payments.payments.api.requests | ||||||||||||||||||||||||||||||||||||||||
| 15 payments.payments.config | ||||||||||||||||||||||||||||||||||||||||
| 16 payments.payments.dao | ||||||||||||||||||||||||||||||||||||||||
| 17 payments.payments.events | ||||||||||||||||||||||||||||||||||||||||
| 18 processes.processes.paying_for_won_item.saga | ||||||||||||||||||||||||||||||||||||||||
| 19 processes.processes.repository | ||||||||||||||||||||||||||||||||||||||||
| 20 shipping.shipping.domain.entities.address | ||||||||||||||||||||||||||||||||||||||||
| 21 auctions.auctions.domain.entities.auction | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 auctions_infrastructure.auctions_infrastructure.queries.auctions | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 customer_relationship.customer_relationship.email_sender | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 customer_relationship.customer_relationship.facade | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 foundation.foundation | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 foundation.foundation.value_objects.factories | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 main | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 payments.payments.api.consumer | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 payments.payments.facade | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 processes.processes | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 processes.processes.paying_for_won_item.saga_handler | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 shipping.shipping.application.repositories.address | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 auctions.auctions.application.repositories.auctions | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 customer_relationship.customer_relationship | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 35 payments.payments | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 36 auctions.auctions.application.use_cases.beginning_auction | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 auctions.auctions.application.use_cases.ending_auction | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 auctions.auctions.application.use_cases.placing_bid | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 auctions.auctions.application.use_cases.withdrawing_bids | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 auctions.auctions | 1 | 1 | 1 | 2 | 1 |
21→2 auctions.auctions.domain.entities.auction uses auctions.auctions.domain.entities.bid✕
- Connections
- 1 pair of types, where a type in auctions.auctions.domain.entities.auction uses a type in auctions.auctions.domain.entities.bid.
- The types involved
auctioning_platform.auctions.auctions.domain.entities.auction.Auction→auctioning_platform.auctions.auctions.domain.entities.bid.Bid
- Direction
- auctions.auctions.domain.entities.auction uses auctions.auctions.domain.entities.bid, so a change to auctions.auctions.domain.entities.bid can break auctions.auctions.domain.entities.auction, while a change to auctions.auctions.domain.entities.auction can't break auctions.auctions.domain.entities.bid.
- Position
- Below the diagonal: auctions.auctions.domain.entities.auction uses a module listed above it, which is the healthy direction.
22→7 auctions_infrastructure.auctions_infrastructure.queries.auctions uses auctions_infrastructure.auctions_infrastructure.queries.base✕
- Connections
- 2 pairs of types, where a type in auctions_infrastructure.auctions_infrastructure.queries.auctions uses a type in auctions_infrastructure.auctions_infrastructure.queries.base.
- The types involved
auctioning_platform.auctions_infrastructure.auctions_infrastructure.queries.auctions.SqlGetActiveAuctions→auctioning_platform.auctions_infrastructure.auctions_infrastructure.queries.base.SqlQueryauctioning_platform.auctions_infrastructure.auctions_infrastructure.queries.auctions.SqlGetSingleAuction→auctioning_platform.auctions_infrastructure.auctions_infrastructure.queries.base.SqlQuery
- Direction
- auctions_infrastructure.auctions_infrastructure.queries.auctions uses auctions_infrastructure.auctions_infrastructure.queries.base, so a change to auctions_infrastructure.auctions_infrastructure.queries.base can break auctions_infrastructure.auctions_infrastructure.queries.auctions, while a change to auctions_infrastructure.auctions_infrastructure.queries.auctions can't break auctions_infrastructure.auctions_infrastructure.queries.base.
- Position
- Below the diagonal: auctions_infrastructure.auctions_infrastructure.queries.auctions uses a module listed above it, which is the healthy direction.
23→9 customer_relationship.customer_relationship.email_sender uses customer_relationship.customer_relationship.config✕
- Connections
- 1 pair of types, where a type in customer_relationship.customer_relationship.email_sender uses a type in customer_relationship.customer_relationship.config.
- The types involved
auctioning_platform.customer_relationship.customer_relationship.email_sender.EmailSender→auctioning_platform.customer_relationship.customer_relationship.config.CustomerRelationshipConfig
- Direction
- customer_relationship.customer_relationship.email_sender uses customer_relationship.customer_relationship.config, so a change to customer_relationship.customer_relationship.config can break customer_relationship.customer_relationship.email_sender, while a change to customer_relationship.customer_relationship.email_sender can't break customer_relationship.customer_relationship.config.
- Position
- Below the diagonal: customer_relationship.customer_relationship.email_sender uses a module listed above it, which is the healthy direction.
23→10 customer_relationship.customer_relationship.email_sender uses customer_relationship.customer_relationship.emails✕
- Connections
- 1 pair of types, where a type in customer_relationship.customer_relationship.email_sender uses a type in customer_relationship.customer_relationship.emails.
- The types involved
auctioning_platform.customer_relationship.customer_relationship.email_sender.EmailSender→auctioning_platform.customer_relationship.customer_relationship.emails.Email
- Direction
- customer_relationship.customer_relationship.email_sender uses customer_relationship.customer_relationship.emails, so a change to customer_relationship.customer_relationship.emails can break customer_relationship.customer_relationship.email_sender, while a change to customer_relationship.customer_relationship.email_sender can't break customer_relationship.customer_relationship.emails.
- Position
- Below the diagonal: customer_relationship.customer_relationship.email_sender uses a module listed above it, which is the healthy direction.
24→9 customer_relationship.customer_relationship.facade uses customer_relationship.customer_relationship.config✕
- Connections
- 1 pair of types, where a type in customer_relationship.customer_relationship.facade uses a type in customer_relationship.customer_relationship.config.
- The types involved
auctioning_platform.customer_relationship.customer_relationship.facade.CustomerRelationshipFacade→auctioning_platform.customer_relationship.customer_relationship.config.CustomerRelationshipConfig
- Direction
- customer_relationship.customer_relationship.facade uses customer_relationship.customer_relationship.config, so a change to customer_relationship.customer_relationship.config can break customer_relationship.customer_relationship.facade, while a change to customer_relationship.customer_relationship.facade can't break customer_relationship.customer_relationship.config.
- Position
- Below the diagonal: customer_relationship.customer_relationship.facade uses a module listed above it, which is the healthy direction.
24→10 customer_relationship.customer_relationship.facade uses customer_relationship.customer_relationship.emails✕
- Connections
- 1 pair of types, where a type in customer_relationship.customer_relationship.facade uses a type in customer_relationship.customer_relationship.emails.
- The types involved
auctioning_platform.customer_relationship.customer_relationship.facade.CustomerRelationshipFacade→auctioning_platform.customer_relationship.customer_relationship.emails.Email
- Direction
- customer_relationship.customer_relationship.facade uses customer_relationship.customer_relationship.emails, so a change to customer_relationship.customer_relationship.emails can break customer_relationship.customer_relationship.facade, while a change to customer_relationship.customer_relationship.facade can't break customer_relationship.customer_relationship.emails.
- Position
- Below the diagonal: customer_relationship.customer_relationship.facade uses a module listed above it, which is the healthy direction.
25→11 foundation.foundation uses foundation.foundation.serializing✕
- Connections
- 1 pair of types, where a type in foundation.foundation uses a type in foundation.foundation.serializing.
- The types involved
auctioning_platform.foundation.foundation.serializing→auctioning_platform.foundation.foundation.serializing.Dataclass
- Direction
- foundation.foundation uses foundation.foundation.serializing, so a change to foundation.foundation.serializing can break foundation.foundation, while a change to foundation.foundation can't break foundation.foundation.serializing.
- Position
- Below the diagonal: foundation.foundation uses a module listed above it, which is the healthy direction.
26→12 foundation.foundation.value_objects.factories uses foundation.foundation.value_objects.money✕
- Connections
- 1 pair of types, where a type in foundation.foundation.value_objects.factories uses a type in foundation.foundation.value_objects.money.
- The types involved
auctioning_platform.foundation.foundation.value_objects.factories.dollars→auctioning_platform.foundation.foundation.value_objects.money.Money
- Direction
- foundation.foundation.value_objects.factories uses foundation.foundation.value_objects.money, so a change to foundation.foundation.value_objects.money can break foundation.foundation.value_objects.factories, while a change to foundation.foundation.value_objects.factories can't break foundation.foundation.value_objects.money.
- Position
- Below the diagonal: foundation.foundation.value_objects.factories uses a module listed above it, which is the healthy direction.
27→13 main uses main.main✕
- Connections
- 1 pair of types, where a type in main uses a type in main.main.
- The types involved
auctioning_platform.main.main→auctioning_platform.main.main.AppContext
- Direction
- main uses main.main, so a change to main.main can break main, while a change to main can't break main.main.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
28→14 payments.payments.api.consumer uses payments.payments.api.requests✕
- Connections
- 1 pair of types, where a type in payments.payments.api.consumer uses a type in payments.payments.api.requests.
- The types involved
auctioning_platform.payments.payments.api.consumer.ApiConsumer→auctioning_platform.payments.payments.api.requests.Request
- Direction
- payments.payments.api.consumer uses payments.payments.api.requests, so a change to payments.payments.api.requests can break payments.payments.api.consumer, while a change to payments.payments.api.consumer can't break payments.payments.api.requests.
- Position
- Below the diagonal: payments.payments.api.consumer uses a module listed above it, which is the healthy direction.
29→15 payments.payments.facade uses payments.payments.config✕
- Connections
- 1 pair of types, where a type in payments.payments.facade uses a type in payments.payments.config.
- The types involved
auctioning_platform.payments.payments.facade.PaymentsFacade→auctioning_platform.payments.payments.config.PaymentsConfig
- Direction
- payments.payments.facade uses payments.payments.config, so a change to payments.payments.config can break payments.payments.facade, while a change to payments.payments.facade can't break payments.payments.config.
- Position
- Below the diagonal: payments.payments.facade uses a module listed above it, which is the healthy direction.
30→18 processes.processes uses processes.processes.paying_for_won_item.saga✕
- Connections
- 1 pair of types, where a type in processes.processes uses a type in processes.processes.paying_for_won_item.saga.
- The types involved
auctioning_platform.processes.processes.Processes→auctioning_platform.processes.processes.paying_for_won_item.saga.PayingForWonItem
- Direction
- processes.processes uses processes.processes.paying_for_won_item.saga, so a change to processes.processes.paying_for_won_item.saga can break processes.processes, while a change to processes.processes can't break processes.processes.paying_for_won_item.saga.
- Position
- Below the diagonal: processes.processes uses a module listed above it, which is the healthy direction.
30→19 processes.processes uses processes.processes.repository✕
- Connections
- 1 pair of types, where a type in processes.processes uses a type in processes.processes.repository.
- The types involved
auctioning_platform.processes.processes.Processes→auctioning_platform.processes.processes.repository.ProcessManagerDataRepo
- Direction
- processes.processes uses processes.processes.repository, so a change to processes.processes.repository can break processes.processes, while a change to processes.processes can't break processes.processes.repository.
- Position
- Below the diagonal: processes.processes uses a module listed above it, which is the healthy direction.
31→18 processes.processes.paying_for_won_item.saga_handler uses processes.processes.paying_for_won_item.saga✕
- Connections
- 2 pairs of types, where a type in processes.processes.paying_for_won_item.saga_handler uses a type in processes.processes.paying_for_won_item.saga.
- The types involved
auctioning_platform.processes.processes.paying_for_won_item.saga_handler.PayingForWonItemHandler→auctioning_platform.processes.processes.paying_for_won_item.saga.PayingForWonItemauctioning_platform.processes.processes.paying_for_won_item.saga_handler.PayingForWonItemHandler→auctioning_platform.processes.processes.paying_for_won_item.saga.PayingForWonItemData
- Direction
- processes.processes.paying_for_won_item.saga_handler uses processes.processes.paying_for_won_item.saga, so a change to processes.processes.paying_for_won_item.saga can break processes.processes.paying_for_won_item.saga_handler, while a change to processes.processes.paying_for_won_item.saga_handler can't break processes.processes.paying_for_won_item.saga.
- Position
- Below the diagonal: processes.processes.paying_for_won_item.saga_handler uses a module listed above it, which is the healthy direction.
31→19 processes.processes.paying_for_won_item.saga_handler uses processes.processes.repository✕
- Connections
- 1 pair of types, where a type in processes.processes.paying_for_won_item.saga_handler uses a type in processes.processes.repository.
- The types involved
auctioning_platform.processes.processes.paying_for_won_item.saga_handler.PayingForWonItemHandler→auctioning_platform.processes.processes.repository.ProcessManagerDataRepo
- Direction
- processes.processes.paying_for_won_item.saga_handler uses processes.processes.repository, so a change to processes.processes.repository can break processes.processes.paying_for_won_item.saga_handler, while a change to processes.processes.paying_for_won_item.saga_handler can't break processes.processes.repository.
- Position
- Below the diagonal: processes.processes.paying_for_won_item.saga_handler uses a module listed above it, which is the healthy direction.
32→20 shipping.shipping.application.repositories.address uses shipping.shipping.domain.entities.address✕
- Connections
- 1 pair of types, where a type in shipping.shipping.application.repositories.address uses a type in shipping.shipping.domain.entities.address.
- The types involved
auctioning_platform.shipping.shipping.application.repositories.address.AddressRepository→auctioning_platform.shipping.shipping.domain.entities.address.Address
- Direction
- shipping.shipping.application.repositories.address uses shipping.shipping.domain.entities.address, so a change to shipping.shipping.domain.entities.address can break shipping.shipping.application.repositories.address, while a change to shipping.shipping.application.repositories.address can't break shipping.shipping.domain.entities.address.
- Position
- Below the diagonal: shipping.shipping.application.repositories.address uses a module listed above it, which is the healthy direction.
33→21 auctions.auctions.application.repositories.auctions uses auctions.auctions.domain.entities.auction✕
- Connections
- 1 pair of types, where a type in auctions.auctions.application.repositories.auctions uses a type in auctions.auctions.domain.entities.auction.
- The types involved
auctioning_platform.auctions.auctions.application.repositories.auctions.AuctionsRepository→auctioning_platform.auctions.auctions.domain.entities.auction.Auction
- Direction
- auctions.auctions.application.repositories.auctions uses auctions.auctions.domain.entities.auction, so a change to auctions.auctions.domain.entities.auction can break auctions.auctions.application.repositories.auctions, while a change to auctions.auctions.application.repositories.auctions can't break auctions.auctions.domain.entities.auction.
- Position
- Below the diagonal: auctions.auctions.application.repositories.auctions uses a module listed above it, which is the healthy direction.
34→9 customer_relationship.customer_relationship uses customer_relationship.customer_relationship.config✕
- Connections
- 1 pair of types, where a type in customer_relationship.customer_relationship uses a type in customer_relationship.customer_relationship.config.
- The types involved
auctioning_platform.customer_relationship.customer_relationship.CustomerRelationship→auctioning_platform.customer_relationship.customer_relationship.config.CustomerRelationshipConfig
- Direction
- customer_relationship.customer_relationship uses customer_relationship.customer_relationship.config, so a change to customer_relationship.customer_relationship.config can break customer_relationship.customer_relationship, while a change to customer_relationship.customer_relationship can't break customer_relationship.customer_relationship.config.
- Position
- Below the diagonal: customer_relationship.customer_relationship uses a module listed above it, which is the healthy direction.
34→24 customer_relationship.customer_relationship uses customer_relationship.customer_relationship.facade✕
- Connections
- 3 pairs of types, where a type in customer_relationship.customer_relationship uses a type in customer_relationship.customer_relationship.facade.
- The types involved
auctioning_platform.customer_relationship.customer_relationship.BidderHasBeenOverbidHandler→auctioning_platform.customer_relationship.customer_relationship.facade.CustomerRelationshipFacadeauctioning_platform.customer_relationship.customer_relationship.CustomerRelationship→auctioning_platform.customer_relationship.customer_relationship.facade.CustomerRelationshipFacadeauctioning_platform.customer_relationship.customer_relationship.WinningBidPlacedHandler→auctioning_platform.customer_relationship.customer_relationship.facade.CustomerRelationshipFacade
- Direction
- customer_relationship.customer_relationship uses customer_relationship.customer_relationship.facade, so a change to customer_relationship.customer_relationship.facade can break customer_relationship.customer_relationship, while a change to customer_relationship.customer_relationship can't break customer_relationship.customer_relationship.facade.
- Position
- Below the diagonal: customer_relationship.customer_relationship uses a module listed above it, which is the healthy direction.
35→15 payments.payments uses payments.payments.config✕
- Connections
- 1 pair of types, where a type in payments.payments uses a type in payments.payments.config.
- The types involved
auctioning_platform.payments.payments.Payments→auctioning_platform.payments.payments.config.PaymentsConfig
- Direction
- payments.payments uses payments.payments.config, so a change to payments.payments.config can break payments.payments, while a change to payments.payments can't break payments.payments.config.
- Position
- Below the diagonal: payments.payments uses a module listed above it, which is the healthy direction.
35→16 payments.payments uses payments.payments.dao✕
- Connections
- 1 pair of types, where a type in payments.payments uses a type in payments.payments.dao.
- The types involved
auctioning_platform.payments.payments.dao→auctioning_platform.payments.payments.dao.PaymentDto
- Direction
- payments.payments uses payments.payments.dao, so a change to payments.payments.dao can break payments.payments, while a change to payments.payments can't break payments.payments.dao.
- Position
- Below the diagonal: payments.payments uses a module listed above it, which is the healthy direction.
35→17 payments.payments uses payments.payments.events✕
- Connections
- 1 pair of types, where a type in payments.payments uses a type in payments.payments.events.
- The types involved
auctioning_platform.payments.payments.PaymentChargedHandler→auctioning_platform.payments.payments.events.PaymentCharged
- Direction
- payments.payments uses payments.payments.events, so a change to payments.payments.events can break payments.payments, while a change to payments.payments can't break payments.payments.events.
- Position
- Below the diagonal: payments.payments uses a module listed above it, which is the healthy direction.
35→29 payments.payments uses payments.payments.facade✕
- Connections
- 2 pairs of types, where a type in payments.payments uses a type in payments.payments.facade.
- The types involved
auctioning_platform.payments.payments.PaymentChargedHandler→auctioning_platform.payments.payments.facade.PaymentsFacadeauctioning_platform.payments.payments.Payments→auctioning_platform.payments.payments.facade.PaymentsFacade
- Direction
- payments.payments uses payments.payments.facade, so a change to payments.payments.facade can break payments.payments, while a change to payments.payments can't break payments.payments.facade.
- Position
- Below the diagonal: payments.payments uses a module listed above it, which is the healthy direction.
36→33 auctions.auctions.application.use_cases.beginning_auction uses auctions.auctions.application.repositories.auctions✕
- Connections
- 1 pair of types, where a type in auctions.auctions.application.use_cases.beginning_auction uses a type in auctions.auctions.application.repositories.auctions.
- The types involved
auctioning_platform.auctions.auctions.application.use_cases.beginning_auction.BeginningAuction→auctioning_platform.auctions.auctions.application.repositories.auctions.AuctionsRepository
- Direction
- auctions.auctions.application.use_cases.beginning_auction uses auctions.auctions.application.repositories.auctions, so a change to auctions.auctions.application.repositories.auctions can break auctions.auctions.application.use_cases.beginning_auction, while a change to auctions.auctions.application.use_cases.beginning_auction can't break auctions.auctions.application.repositories.auctions.
- Position
- Below the diagonal: auctions.auctions.application.use_cases.beginning_auction uses a module listed above it, which is the healthy direction.
37→33 auctions.auctions.application.use_cases.ending_auction uses auctions.auctions.application.repositories.auctions✕
- Connections
- 1 pair of types, where a type in auctions.auctions.application.use_cases.ending_auction uses a type in auctions.auctions.application.repositories.auctions.
- The types involved
auctioning_platform.auctions.auctions.application.use_cases.ending_auction.EndingAuction→auctioning_platform.auctions.auctions.application.repositories.auctions.AuctionsRepository
- Direction
- auctions.auctions.application.use_cases.ending_auction uses auctions.auctions.application.repositories.auctions, so a change to auctions.auctions.application.repositories.auctions can break auctions.auctions.application.use_cases.ending_auction, while a change to auctions.auctions.application.use_cases.ending_auction can't break auctions.auctions.application.repositories.auctions.
- Position
- Below the diagonal: auctions.auctions.application.use_cases.ending_auction uses a module listed above it, which is the healthy direction.
38→33 auctions.auctions.application.use_cases.placing_bid uses auctions.auctions.application.repositories.auctions✕
- Connections
- 1 pair of types, where a type in auctions.auctions.application.use_cases.placing_bid uses a type in auctions.auctions.application.repositories.auctions.
- The types involved
auctioning_platform.auctions.auctions.application.use_cases.placing_bid.PlacingBid→auctioning_platform.auctions.auctions.application.repositories.auctions.AuctionsRepository
- Direction
- auctions.auctions.application.use_cases.placing_bid uses auctions.auctions.application.repositories.auctions, so a change to auctions.auctions.application.repositories.auctions can break auctions.auctions.application.use_cases.placing_bid, while a change to auctions.auctions.application.use_cases.placing_bid can't break auctions.auctions.application.repositories.auctions.
- Position
- Below the diagonal: auctions.auctions.application.use_cases.placing_bid uses a module listed above it, which is the healthy direction.
39→33 auctions.auctions.application.use_cases.withdrawing_bids uses auctions.auctions.application.repositories.auctions✕
- Connections
- 1 pair of types, where a type in auctions.auctions.application.use_cases.withdrawing_bids uses a type in auctions.auctions.application.repositories.auctions.
- The types involved
auctioning_platform.auctions.auctions.application.use_cases.withdrawing_bids.WithdrawingBids→auctioning_platform.auctions.auctions.application.repositories.auctions.AuctionsRepository
- Direction
- auctions.auctions.application.use_cases.withdrawing_bids uses auctions.auctions.application.repositories.auctions, so a change to auctions.auctions.application.repositories.auctions can break auctions.auctions.application.use_cases.withdrawing_bids, while a change to auctions.auctions.application.use_cases.withdrawing_bids can't break auctions.auctions.application.repositories.auctions.
- Position
- Below the diagonal: auctions.auctions.application.use_cases.withdrawing_bids uses a module listed above it, which is the healthy direction.
40→33 auctions.auctions uses auctions.auctions.application.repositories.auctions✕
- Connections
- 1 pair of types, where a type in auctions.auctions uses a type in auctions.auctions.application.repositories.auctions.
- The types involved
auctioning_platform.auctions.auctions.Auctions→auctioning_platform.auctions.auctions.application.repositories.auctions.AuctionsRepository
- Direction
- auctions.auctions uses auctions.auctions.application.repositories.auctions, so a change to auctions.auctions.application.repositories.auctions can break auctions.auctions, while a change to auctions.auctions can't break auctions.auctions.application.repositories.auctions.
- Position
- Below the diagonal: auctions.auctions uses a module listed above it, which is the healthy direction.
40→36 auctions.auctions uses auctions.auctions.application.use_cases.beginning_auction✕
- Connections
- 1 pair of types, where a type in auctions.auctions uses a type in auctions.auctions.application.use_cases.beginning_auction.
- The types involved
auctioning_platform.auctions.auctions.Auctions→auctioning_platform.auctions.auctions.application.use_cases.beginning_auction.BeginningAuction
- Direction
- auctions.auctions uses auctions.auctions.application.use_cases.beginning_auction, so a change to auctions.auctions.application.use_cases.beginning_auction can break auctions.auctions, while a change to auctions.auctions can't break auctions.auctions.application.use_cases.beginning_auction.
- Position
- Below the diagonal: auctions.auctions uses a module listed above it, which is the healthy direction.
40→37 auctions.auctions uses auctions.auctions.application.use_cases.ending_auction✕
- Connections
- 1 pair of types, where a type in auctions.auctions uses a type in auctions.auctions.application.use_cases.ending_auction.
- The types involved
auctioning_platform.auctions.auctions.Auctions→auctioning_platform.auctions.auctions.application.use_cases.ending_auction.EndingAuction
- Direction
- auctions.auctions uses auctions.auctions.application.use_cases.ending_auction, so a change to auctions.auctions.application.use_cases.ending_auction can break auctions.auctions, while a change to auctions.auctions can't break auctions.auctions.application.use_cases.ending_auction.
- Position
- Below the diagonal: auctions.auctions uses a module listed above it, which is the healthy direction.
40→38 auctions.auctions uses auctions.auctions.application.use_cases.placing_bid✕
- Connections
- 2 pairs of types, where a type in auctions.auctions uses a type in auctions.auctions.application.use_cases.placing_bid.
- The types involved
auctioning_platform.auctions.auctions.Auctions→auctioning_platform.auctions.auctions.application.use_cases.placing_bid.PlacingBidauctioning_platform.auctions.auctions.Auctions→auctioning_platform.auctions.auctions.application.use_cases.placing_bid.PlacingBidOutputBoundary
- Direction
- auctions.auctions uses auctions.auctions.application.use_cases.placing_bid, so a change to auctions.auctions.application.use_cases.placing_bid can break auctions.auctions, while a change to auctions.auctions can't break auctions.auctions.application.use_cases.placing_bid.
- Position
- Below the diagonal: auctions.auctions uses a module listed above it, which is the healthy direction.
40→39 auctions.auctions uses auctions.auctions.application.use_cases.withdrawing_bids✕
- Connections
- 1 pair of types, where a type in auctions.auctions uses a type in auctions.auctions.application.use_cases.withdrawing_bids.
- The types involved
auctioning_platform.auctions.auctions.Auctions→auctioning_platform.auctions.auctions.application.use_cases.withdrawing_bids.WithdrawingBids
- Direction
- auctions.auctions uses auctions.auctions.application.use_cases.withdrawing_bids, so a change to auctions.auctions.application.use_cases.withdrawing_bids can break auctions.auctions, while a change to auctions.auctions can't break auctions.auctions.application.use_cases.withdrawing_bids.
- Position
- Below the diagonal: auctions.auctions 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 15 | High / Critical |
| A02:2025 — Security Misconfiguration | 8 | High / Critical |
| A05:2025 — Injection | 6 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Yanked release finding(s) in Dependency Hygiene; Resolve the 10 Orphaned file finding(s) in Knowledge Freshness — start with modules.py, __init__.py, auction.py; Log through `logging.getLogger(__name__)` (or structlog) with a JSON formatter at meaningful points in the modules you run.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Yanked release finding(s) in Dependency Hygiene. | +9.8 pts | Low | Dependency Hygiene |
| Resolve the 1 Banned license finding(s) in License Compliance. | +4.6 pts | Low | License Compliance |
| Resolve the 10 Orphaned file finding(s) in Knowledge Freshness — start with modules.py, __init__.py, auction.py. | +7.7 pts | Medium | Knowledge Freshness |
| Log through `logging.getLogger(__name__)` (or structlog) with a JSON formatter at meaningful points in the modules you run. | +5.3 pts | Medium | Observability |
| 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.3 pts | Medium | Security & performance tooling |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.9 pts | Medium | Architecture documentation |
| Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker. | +2.5 pts | Medium | Outbound HTTP resilience |
| Replace SQLAlchemy create_all() with Alembic (`alembic revision --autogenerate` + `alembic upgrade head`) so the production schema can evolve safely and reproducibly. | +2.5 pts | Medium | Schema migrations |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.4 | Slop | Dependency Vulnerabilities: Critical vulnerability: REDACTED |
| REDACTED | 2.3 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| auctioning_platform/shipping/shipping/application/use_cases/shipping_package.py | 8.2 | Near-clean | Explicit Debt: TodoComment |
| auctioning_platform/main/main/__init__.py | 8.2 | Near-clean | Explicit Debt: TodoComment |
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 62 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 — 62 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, 46 of 105 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.
- D19 Documentation Quality — 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. 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.
- 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 (auctioning_platform/web_app_models/setup.py), 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 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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c make dev" did not complete successfully: exit code: 2; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
0 duplicated block group(s) detected.
D5 · Coupling
12 production modules (Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
0 of 15 classes have LCOM4 above 3.
D9 · Test Distribution
67 test methods: 67 unit, 0 integration, 0 BDD, 0 e2e. The Python suite contributes 67 test function(s) across 13 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 (6 distributions): measured (0 flaky).
D12 · Dependency Hygiene
50 outdated, 1 yanked pinned Python distributions. 59 of 70 shipped distributions were graded against pypi.org (0 not published there, 11 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 (poetry.lock, 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
- Resolve the 1 Yanked release finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
1 of 88 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 70 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (24 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. 6 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
3 deducted task-comment markers across 1953 LoC (0.1/KLoC) → score 9.8. 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 3 TodoComment finding(s) in Explicit Debt — start with REDACTED, shipping_package.py, __init__.py. — One of this dimension's main actionable groups (3 warning-level).
D26 · Project Cohesion
0 of 12 build units (Python) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
7 finding(s): 0 critical, 4 high, 1 medium, 2 low.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D30 · Dependency Vulnerabilities
15 finding(s): 1 critical, 6 high, 8 medium, 0 low.
What to do
- Resolve the 8 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7), REDACTED. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 6 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 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
8 finding(s): 0 critical, 4 high, 3 medium, 1 low.
What to do
- Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
10 of 10 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is auctioning_platform/main/main/modules.py. Counted over 10 of the 105 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 10 Orphaned file finding(s) in Knowledge Freshness — start with modules.py, __init__.py, auction.py. — One of this dimension's main actionable groups (10 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 70 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
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
DM5 · Encapsulated state
- `Auction` exposes publicly writable state (id, title, starting_price, bids, ends_at). — auctioning_platform/auctions/auctions/domain/entities/auction.py:13
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)
- The root README is 111 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging call was found in the 105 Python production file(s) this check read across 12 module(s). Each was searched for its ecosystem's logging libraries (Python: logging, structlog, loguru) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Log through `logging.getLogger(__name__)` (or structlog) with a JSON formatter at meaningful points in the modules you run.
- 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 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- 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.
P7 · Outbound HTTP resilience
- `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — REDACTED:29
What to do
- Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
P8 · Schema migrations
- SQLAlchemy create_all() builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt Alembic (`alembic revision --autogenerate` + `alembic upgrade head`), so every schema change is a versioned file applied the same way in every environment. — auctioning_platform/main/main/__init__.py:94
What to do
- Replace SQLAlchemy create_all() with Alembic (`alembic revision --autogenerate` + `alembic upgrade head`) so the production schema can evolve safely and reproducibly.
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 | Strongest area. |
| Architecture | 96% | Exemplary | Solid. |
| Maturity | 53% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 28% | Weak — gated by P2, P3, P7, P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 82% | Strong | Solid. |
| Domain Modelling | 74% | Adequate — gated by DM5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not evidenced — 5 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
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 64 check(s) not relevant to this codebase
- AC1 Text alternatives — 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
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) 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
- 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 — compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c make dev" did not complete successfully: exit code: 2; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: 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.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here — a library or command-line tool is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- D10 Test Quality — ~1055 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 — bus factor 1 — one contributor carries this repository
- 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.
- D19 Documentation Quality — D19 reads .NET projects and npm packages as units; 12 folder(s) declared by setup.py were not judged for an overview, an example or the map.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — 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.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (auctioning_platform), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- 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 publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). 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.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 — 15 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: text-unidecode
- REDACTED
- REDACTED
Serious — 21 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment REDACTED:27
- TodoComment auctioning_platform/shipping/shipping/application/use_cases/shipping_package.py:19
- TodoComment auctioning_platform/main/main/__init__.py:93
- REDACTED
- REDACTED
- REDACTED
- Yanked release: sqlalchemy-utils
- bus factor 1 — one contributor carries this repository
- REDACTED
- Mutable entity: Auction auctioning_platform/auctions/auctions/domain/entities/auction.py:13
- No structured logging
- Outbound HTTP without resilience REDACTED:29
- Schema created by SQLAlchemy create_all() (no migration path) auctioning_platform/main/main/__init__.py:94
Minor — 19 finding(s)
- Orphaned file auctioning_platform/main/main/modules.py:1
- Orphaned file auctioning_platform/main/main/__init__.py:1
- Orphaned file auctioning_platform/auctions/auctions/domain/entities/auction.py:1
- Orphaned file auctioning_platform/foundation/foundation/events.py:1
- Orphaned file auctioning_platform/foundation/foundation/serializing.py:1
- Orphaned file auctioning_platform/foundation/foundation/value_objects/money.py:1
- Orphaned file auctioning_platform/auctions_infrastructure/auctions_infrastructure/repositories/auctions.py:1
- Orphaned file auctioning_platform/processes/processes/paying_for_won_item/saga.py:1
- Orphaned file auctioning_platform/payments/payments/facade.py:1
- Orphaned file REDACTED:1
- REDACTED
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- Thin README README.md:1
- No ADRs
- No SAST
- No rollback/health safety
Minor — 50 finding(s)
- Outdated: attrs
- Outdated: babel
- Outdated: bcrypt
- Outdated: blinker
- Outdated: certifi
- Outdated: cffi
- Outdated: chardet
- Outdated: click
- Outdated: dnspython
- Outdated: email-validator
- Outdated: factory-boy
- Outdated: faker
- Outdated: flask
- Outdated: flask-injector
- Outdated: flask-login
- Outdated: flask-mail
- Outdated: flask-security
- Outdated: flask-wtf
- Outdated: freezegun
- Outdated: idna
- Outdated: iniconfig
- Outdated: injector
- Outdated: itsdangerous
- Outdated: jinja2
- Outdated: markupsafe
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-77e0f47784bc4d1fb4d2023478a804c3/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-77e0f47784bc4d1fb4d2023478a804c3/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 . | 7 | 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 . | 8 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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 |