Executive summary
codeliner/php-ddd-cargo-sample is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 44 out of 100, which the At risk rating leaves unchanged. We judged it as a template or a sample, against a lower bar.
Accessibility, at 30, is the weakest lens and counts most in the score. The best first step is fixing the seven packages their makers have withdrawn or abandoned, worth about 7 points. Making the controls keyboard-usable would lift Accessibility itself, worth about 4 points. Raising Accessibility to 58 would lift the score to about 51.
Four known security holes in the packages the code depends on can be used by attackers. One setting leaves the servers or containers unsafe, and two form fields can't be read by a screen reader. Updating the vulnerable packages, correcting the unsafe settings and labelling the form fields would close these risks. The two labels or groups of fields with no name need connecting to their fields or naming.
The product code is 17,259 lines, about €14,000 to rebuild.
If Accessibility rose from 30 to 58, the lowest score rated Strong, the score would rise from 44 to about 51.
New since the last survey: 17 findings
- Dependency Vulnerabilities · REDACTED
- Visual & motion safety · Low contrast colour pair in CSS (3.6:1) public/css/bootstrap.css
- Visual & motion safety · Low contrast colour pair in CSS (2.5:1) public/css/bootstrap.css
- Visual & motion safety · Low contrast colour pair in CSS (3.1:1) public/css/bootstrap.css
- Visual & motion safety · Low contrast colour pair in CSS (3.6:1) public/css/bootstrap.css
- Visual & motion safety · Low contrast colour pair in CSS (3.6:1) public/css/bootstrap.css
- Visual & motion safety · Low contrast colour pair in CSS (3.6:1) public/css/bootstrap.css
- Visual & motion safety · Low contrast colour pair in CSS (3.6:1) public/css/bootstrap.css
- Visual & motion safety · Low contrast colour pair in CSS (3.6:1) public/css/bootstrap.css
- Visual & motion safety · Low contrast colour pair in CSS (3.3:1) public/css/bootstrap.css
- Visual & motion safety · Low contrast colour pair in CSS (2.5:1) public/css/bootstrap.css
- Visual & motion safety · Low contrast colour pair in CSS (3.9:1) public/css/bootstrap.css
- Visual & motion safety · Low contrast colour pair in CSS (3.6:1) public/css/bootstrap.css
- Visual & motion safety · Low contrast colour pair in CSS (3.6:1) public/css/bootstrap.css
- Visual & motion safety · Low contrast colour pair in CSS (2.5:1) public/css/bootstrap.css
- Visual & motion safety · Low contrast colour pair in CSS (3.9:1) public/css/bootstrap.css
- Visual & motion safety · Low contrast colour pair in CSS (3.3:1) public/css/bootstrap.css
Fixed since the last survey: 1 finding
- Visual & motion safety · Low contrast colour pair in CSS (2.5:1) public/css/bootstrap.css
Rebuild cost: about €14,000 · Estimate
| Cost to rebuild | €4,700 to €24,000, for 79 to 249 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Low, 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 44. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 17,259 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 CargoUI.view.riot | 2 CargoUI.view.riot.booking | 3 CargoUI.view.riot.booking.cargolist | 4 CargoUI.view.riot.booking.jumbotron | 5 CargoUI.view.riot.booking.routing | 6 Codeliner.CargoBackend.Application | 7 Codeliner.CargoBackend.Application.Booking.Dto | 8 Codeliner.CargoBackend.Infrastructure.Container.Application.Action | 9 Codeliner.CargoBackend.Infrastructure.Persistence.Transaction | 10 Codeliner.CargoBackend.Migrations | 11 Codeliner.CargoBackend.Model.Cargo | 12 Codeliner.CargoBackend.Model.Cargo.Exception | 13 Codeliner.CargoFeature | 14 Codeliner.CargoUI | 15 Codeliner.GraphTraversalBackend.Dto | 16 public.js | 17 Codeliner.CargoBackend.Application.Booking.Assembler | 18 Codeliner.CargoBackend.Application.Exception | 19 Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine | 20 Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine.Type | 21 Codeliner.CargoBackend.Model.Routing | 22 Codeliner.CargoUI.Container | 23 Codeliner.GraphTraversalBackend | 24 Codeliner.CargoBackend.Application.Booking | 25 Codeliner.CargoBackend.Infrastructure.Routing | 26 Codeliner.CargoBackend.Http.Action | 27 Codeliner.CargoBackend.Infrastructure.Container.Application.Booking | 28 Codeliner.CargoBackend.Infrastructure.Container.Infrastructure |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 CargoUI.view.riot | ||||||||||||||||||||||||||||
| 2 CargoUI.view.riot.booking | ||||||||||||||||||||||||||||
| 3 CargoUI.view.riot.booking.cargolist | ||||||||||||||||||||||||||||
| 4 CargoUI.view.riot.booking.jumbotron | ||||||||||||||||||||||||||||
| 5 CargoUI.view.riot.booking.routing | ||||||||||||||||||||||||||||
| 6 Codeliner.CargoBackend.Application | ||||||||||||||||||||||||||||
| 7 Codeliner.CargoBackend.Application.Booking.Dto | ||||||||||||||||||||||||||||
| 8 Codeliner.CargoBackend.Infrastructure.Container.Application.Action | ||||||||||||||||||||||||||||
| 9 Codeliner.CargoBackend.Infrastructure.Persistence.Transaction | ||||||||||||||||||||||||||||
| 10 Codeliner.CargoBackend.Migrations | ||||||||||||||||||||||||||||
| 11 Codeliner.CargoBackend.Model.Cargo | ||||||||||||||||||||||||||||
| 12 Codeliner.CargoBackend.Model.Cargo.Exception | ||||||||||||||||||||||||||||
| 13 Codeliner.CargoFeature | ||||||||||||||||||||||||||||
| 14 Codeliner.CargoUI | ||||||||||||||||||||||||||||
| 15 Codeliner.GraphTraversalBackend.Dto | ||||||||||||||||||||||||||||
| 16 public.js | ||||||||||||||||||||||||||||
| 17 Codeliner.CargoBackend.Application.Booking.Assembler | 2 | 2 | ||||||||||||||||||||||||||
| 18 Codeliner.CargoBackend.Application.Exception | 1 | |||||||||||||||||||||||||||
| 19 Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine | 1 | 3 | ||||||||||||||||||||||||||
| 20 Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine.Type | 1 | |||||||||||||||||||||||||||
| 21 Codeliner.CargoBackend.Model.Routing | 1 | |||||||||||||||||||||||||||
| 22 Codeliner.CargoUI.Container | 1 | |||||||||||||||||||||||||||
| 23 Codeliner.GraphTraversalBackend | 1 | |||||||||||||||||||||||||||
| 24 Codeliner.CargoBackend.Application.Booking | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||
| 25 Codeliner.CargoBackend.Infrastructure.Routing | 3 | 2 | 1 | 1 | ||||||||||||||||||||||||
| 26 Codeliner.CargoBackend.Http.Action | 6 | |||||||||||||||||||||||||||
| 27 Codeliner.CargoBackend.Infrastructure.Container.Application.Booking | 1 | |||||||||||||||||||||||||||
| 28 Codeliner.CargoBackend.Infrastructure.Container.Infrastructure | 1 | 1 | 1 |
17→7 Codeliner.CargoBackend.Application.Booking.Assembler uses Codeliner.CargoBackend.Application.Booking.Dto✕
- Connections
- 2 pairs of types, where a type in Codeliner.CargoBackend.Application.Booking.Assembler uses a type in Codeliner.CargoBackend.Application.Booking.Dto.
- The types involved
Codeliner.CargoBackend.Application.Booking.Assembler.CargoRoutingDtoAssembler→Codeliner.CargoBackend.Application.Booking.Dto.CargoRoutingDtoCodeliner.CargoBackend.Application.Booking.Assembler.RouteCandidateDtoAssembler→Codeliner.CargoBackend.Application.Booking.Dto.RouteCandidateDto
- Direction
- Codeliner.CargoBackend.Application.Booking.Assembler uses Codeliner.CargoBackend.Application.Booking.Dto, so a change to Codeliner.CargoBackend.Application.Booking.Dto can break Codeliner.CargoBackend.Application.Booking.Assembler, while a change to Codeliner.CargoBackend.Application.Booking.Assembler can't break Codeliner.CargoBackend.Application.Booking.Dto.
- Position
- Below the diagonal: Codeliner.CargoBackend.Application.Booking.Assembler uses a module listed above it, which is the healthy direction.
17→11 Codeliner.CargoBackend.Application.Booking.Assembler uses Codeliner.CargoBackend.Model.Cargo✕
- Connections
- 2 pairs of types, where a type in Codeliner.CargoBackend.Application.Booking.Assembler uses a type in Codeliner.CargoBackend.Model.Cargo.
- The types involved
Codeliner.CargoBackend.Application.Booking.Assembler.CargoRoutingDtoAssembler→Codeliner.CargoBackend.Model.Cargo.CargoCodeliner.CargoBackend.Application.Booking.Assembler.RouteCandidateDtoAssembler→Codeliner.CargoBackend.Model.Cargo.Itinerary
- Direction
- Codeliner.CargoBackend.Application.Booking.Assembler uses Codeliner.CargoBackend.Model.Cargo, so a change to Codeliner.CargoBackend.Model.Cargo can break Codeliner.CargoBackend.Application.Booking.Assembler, while a change to Codeliner.CargoBackend.Application.Booking.Assembler can't break Codeliner.CargoBackend.Model.Cargo.
- Position
- Below the diagonal: Codeliner.CargoBackend.Application.Booking.Assembler uses a module listed above it, which is the healthy direction.
18→11 Codeliner.CargoBackend.Application.Exception uses Codeliner.CargoBackend.Model.Cargo✕
- Connections
- 1 pair of types, where a type in Codeliner.CargoBackend.Application.Exception uses a type in Codeliner.CargoBackend.Model.Cargo.
- The types involved
Codeliner.CargoBackend.Application.Exception.CargoNotFoundException→Codeliner.CargoBackend.Model.Cargo.TrackingId
- Direction
- Codeliner.CargoBackend.Application.Exception uses Codeliner.CargoBackend.Model.Cargo, so a change to Codeliner.CargoBackend.Model.Cargo can break Codeliner.CargoBackend.Application.Exception, while a change to Codeliner.CargoBackend.Application.Exception can't break Codeliner.CargoBackend.Model.Cargo.
- Position
- Below the diagonal: Codeliner.CargoBackend.Application.Exception uses a module listed above it, which is the healthy direction.
19→6 Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine uses Codeliner.CargoBackend.Application✕
- Connections
- 1 pair of types, where a type in Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine uses a type in Codeliner.CargoBackend.Application.
- The types involved
Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine.DoctrineORMTransactionManager→Codeliner.CargoBackend.Application.TransactionManager
- Direction
- Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine uses Codeliner.CargoBackend.Application, so a change to Codeliner.CargoBackend.Application can break Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine, while a change to Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine can't break Codeliner.CargoBackend.Application.
- Position
- Below the diagonal: Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine uses a module listed above it, which is the healthy direction.
19→11 Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine uses Codeliner.CargoBackend.Model.Cargo✕
- Connections
- 3 pairs of types, where a type in Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine uses a type in Codeliner.CargoBackend.Model.Cargo.
- The types involved
Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine.DoctrineCargoRepository→Codeliner.CargoBackend.Model.Cargo.CargoCodeliner.CargoBackend.Infrastructure.Persistence.Doctrine.DoctrineCargoRepository→Codeliner.CargoBackend.Model.Cargo.CargoRepositoryInterfaceCodeliner.CargoBackend.Infrastructure.Persistence.Doctrine.DoctrineCargoRepository→Codeliner.CargoBackend.Model.Cargo.TrackingId
- Direction
- Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine uses Codeliner.CargoBackend.Model.Cargo, so a change to Codeliner.CargoBackend.Model.Cargo can break Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine, while a change to Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine can't break Codeliner.CargoBackend.Model.Cargo.
- Position
- Below the diagonal: Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine uses a module listed above it, which is the healthy direction.
20→11 Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine.Type uses Codeliner.CargoBackend.Model.Cargo✕
- Connections
- 1 pair of types, where a type in Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine.Type uses a type in Codeliner.CargoBackend.Model.Cargo.
- The types involved
Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine.Type.TrackingIdDoctrineType→Codeliner.CargoBackend.Model.Cargo.TrackingId
- Direction
- Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine.Type uses Codeliner.CargoBackend.Model.Cargo, so a change to Codeliner.CargoBackend.Model.Cargo can break Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine.Type, while a change to Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine.Type can't break Codeliner.CargoBackend.Model.Cargo.
- Position
- Below the diagonal: Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine.Type uses a module listed above it, which is the healthy direction.
21→11 Codeliner.CargoBackend.Model.Routing uses Codeliner.CargoBackend.Model.Cargo✕
- Connections
- 1 pair of types, where a type in Codeliner.CargoBackend.Model.Routing uses a type in Codeliner.CargoBackend.Model.Cargo.
- The types involved
Codeliner.CargoBackend.Model.Routing.RoutingServiceInterface→Codeliner.CargoBackend.Model.Cargo.RouteSpecification
- Direction
- Codeliner.CargoBackend.Model.Routing uses Codeliner.CargoBackend.Model.Cargo, so a change to Codeliner.CargoBackend.Model.Cargo can break Codeliner.CargoBackend.Model.Routing, while a change to Codeliner.CargoBackend.Model.Routing can't break Codeliner.CargoBackend.Model.Cargo.
- Position
- Below the diagonal: Codeliner.CargoBackend.Model.Routing uses a module listed above it, which is the healthy direction.
22→14 Codeliner.CargoUI.Container uses Codeliner.CargoUI✕
- Connections
- 1 pair of types, where a type in Codeliner.CargoUI.Container uses a type in Codeliner.CargoUI.
- The types involved
Codeliner.CargoUI.Container.MainFactory→Codeliner.CargoUI.Main
- Direction
- Codeliner.CargoUI.Container uses Codeliner.CargoUI, so a change to Codeliner.CargoUI can break Codeliner.CargoUI.Container, while a change to Codeliner.CargoUI.Container can't break Codeliner.CargoUI.
- Position
- Below the diagonal: Codeliner.CargoUI.Container uses a module listed above it, which is the healthy direction.
23→15 Codeliner.GraphTraversalBackend uses Codeliner.GraphTraversalBackend.Dto✕
- Connections
- 1 pair of types, where a type in Codeliner.GraphTraversalBackend uses a type in Codeliner.GraphTraversalBackend.Dto.
- The types involved
Codeliner.GraphTraversalBackend.GraphTraversalService→Codeliner.GraphTraversalBackend.Dto.TransitPathDto
- Direction
- Codeliner.GraphTraversalBackend uses Codeliner.GraphTraversalBackend.Dto, so a change to Codeliner.GraphTraversalBackend.Dto can break Codeliner.GraphTraversalBackend, while a change to Codeliner.GraphTraversalBackend can't break Codeliner.GraphTraversalBackend.Dto.
- Position
- Below the diagonal: Codeliner.GraphTraversalBackend uses a module listed above it, which is the healthy direction.
24→6 Codeliner.CargoBackend.Application.Booking uses Codeliner.CargoBackend.Application✕
- Connections
- 1 pair of types, where a type in Codeliner.CargoBackend.Application.Booking uses a type in Codeliner.CargoBackend.Application.
- The types involved
Codeliner.CargoBackend.Application.Booking.BookingService→Codeliner.CargoBackend.Application.TransactionManager
- Direction
- Codeliner.CargoBackend.Application.Booking uses Codeliner.CargoBackend.Application, so a change to Codeliner.CargoBackend.Application can break Codeliner.CargoBackend.Application.Booking, while a change to Codeliner.CargoBackend.Application.Booking can't break Codeliner.CargoBackend.Application.
- Position
- Below the diagonal: Codeliner.CargoBackend.Application.Booking uses a module listed above it, which is the healthy direction.
24→7 Codeliner.CargoBackend.Application.Booking uses Codeliner.CargoBackend.Application.Booking.Dto✕
- Connections
- 2 pairs of types, where a type in Codeliner.CargoBackend.Application.Booking uses a type in Codeliner.CargoBackend.Application.Booking.Dto.
- The types involved
Codeliner.CargoBackend.Application.Booking.BookingService→Codeliner.CargoBackend.Application.Booking.Dto.CargoRoutingDtoCodeliner.CargoBackend.Application.Booking.BookingService→Codeliner.CargoBackend.Application.Booking.Dto.RouteCandidateDto
- Direction
- Codeliner.CargoBackend.Application.Booking uses Codeliner.CargoBackend.Application.Booking.Dto, so a change to Codeliner.CargoBackend.Application.Booking.Dto can break Codeliner.CargoBackend.Application.Booking, while a change to Codeliner.CargoBackend.Application.Booking can't break Codeliner.CargoBackend.Application.Booking.Dto.
- Position
- Below the diagonal: Codeliner.CargoBackend.Application.Booking uses a module listed above it, which is the healthy direction.
24→11 Codeliner.CargoBackend.Application.Booking uses Codeliner.CargoBackend.Model.Cargo✕
- Connections
- 1 pair of types, where a type in Codeliner.CargoBackend.Application.Booking uses a type in Codeliner.CargoBackend.Model.Cargo.
- The types involved
Codeliner.CargoBackend.Application.Booking.BookingService→Codeliner.CargoBackend.Model.Cargo.CargoRepositoryInterface
- Direction
- Codeliner.CargoBackend.Application.Booking uses Codeliner.CargoBackend.Model.Cargo, so a change to Codeliner.CargoBackend.Model.Cargo can break Codeliner.CargoBackend.Application.Booking, while a change to Codeliner.CargoBackend.Application.Booking can't break Codeliner.CargoBackend.Model.Cargo.
- Position
- Below the diagonal: Codeliner.CargoBackend.Application.Booking uses a module listed above it, which is the healthy direction.
24→21 Codeliner.CargoBackend.Application.Booking uses Codeliner.CargoBackend.Model.Routing✕
- Connections
- 1 pair of types, where a type in Codeliner.CargoBackend.Application.Booking uses a type in Codeliner.CargoBackend.Model.Routing.
- The types involved
Codeliner.CargoBackend.Application.Booking.BookingService→Codeliner.CargoBackend.Model.Routing.RoutingServiceInterface
- Direction
- Codeliner.CargoBackend.Application.Booking uses Codeliner.CargoBackend.Model.Routing, so a change to Codeliner.CargoBackend.Model.Routing can break Codeliner.CargoBackend.Application.Booking, while a change to Codeliner.CargoBackend.Application.Booking can't break Codeliner.CargoBackend.Model.Routing.
- Position
- Below the diagonal: Codeliner.CargoBackend.Application.Booking uses a module listed above it, which is the healthy direction.
25→11 Codeliner.CargoBackend.Infrastructure.Routing uses Codeliner.CargoBackend.Model.Cargo✕
- Connections
- 3 pairs of types, where a type in Codeliner.CargoBackend.Infrastructure.Routing uses a type in Codeliner.CargoBackend.Model.Cargo.
- The types involved
Codeliner.CargoBackend.Infrastructure.Routing.ExternalRoutingService→Codeliner.CargoBackend.Model.Cargo.ItineraryCodeliner.CargoBackend.Infrastructure.Routing.ExternalRoutingService→Codeliner.CargoBackend.Model.Cargo.LegCodeliner.CargoBackend.Infrastructure.Routing.ExternalRoutingService→Codeliner.CargoBackend.Model.Cargo.RouteSpecification
- Direction
- Codeliner.CargoBackend.Infrastructure.Routing uses Codeliner.CargoBackend.Model.Cargo, so a change to Codeliner.CargoBackend.Model.Cargo can break Codeliner.CargoBackend.Infrastructure.Routing, while a change to Codeliner.CargoBackend.Infrastructure.Routing can't break Codeliner.CargoBackend.Model.Cargo.
- Position
- Below the diagonal: Codeliner.CargoBackend.Infrastructure.Routing uses a module listed above it, which is the healthy direction.
25→15 Codeliner.CargoBackend.Infrastructure.Routing uses Codeliner.GraphTraversalBackend.Dto✕
- Connections
- 2 pairs of types, where a type in Codeliner.CargoBackend.Infrastructure.Routing uses a type in Codeliner.GraphTraversalBackend.Dto.
- The types involved
Codeliner.CargoBackend.Infrastructure.Routing.ExternalRoutingService→Codeliner.GraphTraversalBackend.Dto.EdgeDtoCodeliner.CargoBackend.Infrastructure.Routing.ExternalRoutingService→Codeliner.GraphTraversalBackend.Dto.TransitPathDto
- Direction
- Codeliner.CargoBackend.Infrastructure.Routing uses Codeliner.GraphTraversalBackend.Dto, so a change to Codeliner.GraphTraversalBackend.Dto can break Codeliner.CargoBackend.Infrastructure.Routing, while a change to Codeliner.CargoBackend.Infrastructure.Routing can't break Codeliner.GraphTraversalBackend.Dto.
- Position
- Below the diagonal: Codeliner.CargoBackend.Infrastructure.Routing uses a module listed above it, which is the healthy direction.
25→21 Codeliner.CargoBackend.Infrastructure.Routing uses Codeliner.CargoBackend.Model.Routing✕
- Connections
- 1 pair of types, where a type in Codeliner.CargoBackend.Infrastructure.Routing uses a type in Codeliner.CargoBackend.Model.Routing.
- The types involved
Codeliner.CargoBackend.Infrastructure.Routing.ExternalRoutingService→Codeliner.CargoBackend.Model.Routing.RoutingServiceInterface
- Direction
- Codeliner.CargoBackend.Infrastructure.Routing uses Codeliner.CargoBackend.Model.Routing, so a change to Codeliner.CargoBackend.Model.Routing can break Codeliner.CargoBackend.Infrastructure.Routing, while a change to Codeliner.CargoBackend.Infrastructure.Routing can't break Codeliner.CargoBackend.Model.Routing.
- Position
- Below the diagonal: Codeliner.CargoBackend.Infrastructure.Routing uses a module listed above it, which is the healthy direction.
25→23 Codeliner.CargoBackend.Infrastructure.Routing uses Codeliner.GraphTraversalBackend✕
- Connections
- 1 pair of types, where a type in Codeliner.CargoBackend.Infrastructure.Routing uses a type in Codeliner.GraphTraversalBackend.
- The types involved
Codeliner.CargoBackend.Infrastructure.Routing.ExternalRoutingService→Codeliner.GraphTraversalBackend.GraphTraversalServiceInterface
- Direction
- Codeliner.CargoBackend.Infrastructure.Routing uses Codeliner.GraphTraversalBackend, so a change to Codeliner.GraphTraversalBackend can break Codeliner.CargoBackend.Infrastructure.Routing, while a change to Codeliner.CargoBackend.Infrastructure.Routing can't break Codeliner.GraphTraversalBackend.
- Position
- Below the diagonal: Codeliner.CargoBackend.Infrastructure.Routing uses a module listed above it, which is the healthy direction.
26→24 Codeliner.CargoBackend.Http.Action uses Codeliner.CargoBackend.Application.Booking✕
- Connections
- 6 pairs of types, where a type in Codeliner.CargoBackend.Http.Action uses a type in Codeliner.CargoBackend.Application.Booking.
- The types involved
Codeliner.CargoBackend.Http.Action.CreateCargo→Codeliner.CargoBackend.Application.Booking.BookingServiceCodeliner.CargoBackend.Http.Action.GetCargo→Codeliner.CargoBackend.Application.Booking.BookingServiceCodeliner.CargoBackend.Http.Action.GetCargos→Codeliner.CargoBackend.Application.Booking.BookingServiceCodeliner.CargoBackend.Http.Action.GetLocations→Codeliner.CargoBackend.Application.Booking.BookingServiceCodeliner.CargoBackend.Http.Action.GetRouteCandidates→Codeliner.CargoBackend.Application.Booking.BookingServiceCodeliner.CargoBackend.Http.Action.UpdateCargo→Codeliner.CargoBackend.Application.Booking.BookingService
- Direction
- Codeliner.CargoBackend.Http.Action uses Codeliner.CargoBackend.Application.Booking, so a change to Codeliner.CargoBackend.Application.Booking can break Codeliner.CargoBackend.Http.Action, while a change to Codeliner.CargoBackend.Http.Action can't break Codeliner.CargoBackend.Application.Booking.
- Position
- Below the diagonal: Codeliner.CargoBackend.Http.Action uses a module listed above it, which is the healthy direction.
27→24 Codeliner.CargoBackend.Infrastructure.Container.Application.Booking uses Codeliner.CargoBackend.Application.Booking✕
- Connections
- 1 pair of types, where a type in Codeliner.CargoBackend.Infrastructure.Container.Application.Booking uses a type in Codeliner.CargoBackend.Application.Booking.
- The types involved
Codeliner.CargoBackend.Infrastructure.Container.Application.Booking.BookingServiceFactory→Codeliner.CargoBackend.Application.Booking.BookingService
- Direction
- Codeliner.CargoBackend.Infrastructure.Container.Application.Booking uses Codeliner.CargoBackend.Application.Booking, so a change to Codeliner.CargoBackend.Application.Booking can break Codeliner.CargoBackend.Infrastructure.Container.Application.Booking, while a change to Codeliner.CargoBackend.Infrastructure.Container.Application.Booking can't break Codeliner.CargoBackend.Application.Booking.
- Position
- Below the diagonal: Codeliner.CargoBackend.Infrastructure.Container.Application.Booking uses a module listed above it, which is the healthy direction.
28→6 Codeliner.CargoBackend.Infrastructure.Container.Infrastructure uses Codeliner.CargoBackend.Application✕
- Connections
- 1 pair of types, where a type in Codeliner.CargoBackend.Infrastructure.Container.Infrastructure uses a type in Codeliner.CargoBackend.Application.
- The types involved
Codeliner.CargoBackend.Infrastructure.Container.Infrastructure.TransactionManagerFactory→Codeliner.CargoBackend.Application.TransactionManager
- Direction
- Codeliner.CargoBackend.Infrastructure.Container.Infrastructure uses Codeliner.CargoBackend.Application, so a change to Codeliner.CargoBackend.Application can break Codeliner.CargoBackend.Infrastructure.Container.Infrastructure, while a change to Codeliner.CargoBackend.Infrastructure.Container.Infrastructure can't break Codeliner.CargoBackend.Application.
- Position
- Below the diagonal: Codeliner.CargoBackend.Infrastructure.Container.Infrastructure uses a module listed above it, which is the healthy direction.
28→19 Codeliner.CargoBackend.Infrastructure.Container.Infrastructure uses Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine✕
- Connections
- 1 pair of types, where a type in Codeliner.CargoBackend.Infrastructure.Container.Infrastructure uses a type in Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine.
- The types involved
Codeliner.CargoBackend.Infrastructure.Container.Infrastructure.DoctrineCargoRepositoryFactory→Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine.DoctrineCargoRepository
- Direction
- Codeliner.CargoBackend.Infrastructure.Container.Infrastructure uses Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine, so a change to Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine can break Codeliner.CargoBackend.Infrastructure.Container.Infrastructure, while a change to Codeliner.CargoBackend.Infrastructure.Container.Infrastructure can't break Codeliner.CargoBackend.Infrastructure.Persistence.Doctrine.
- Position
- Below the diagonal: Codeliner.CargoBackend.Infrastructure.Container.Infrastructure uses a module listed above it, which is the healthy direction.
28→25 Codeliner.CargoBackend.Infrastructure.Container.Infrastructure uses Codeliner.CargoBackend.Infrastructure.Routing✕
- Connections
- 1 pair of types, where a type in Codeliner.CargoBackend.Infrastructure.Container.Infrastructure uses a type in Codeliner.CargoBackend.Infrastructure.Routing.
- The types involved
Codeliner.CargoBackend.Infrastructure.Container.Infrastructure.ExternalRoutingServiceFactory→Codeliner.CargoBackend.Infrastructure.Routing.ExternalRoutingService
- Direction
- Codeliner.CargoBackend.Infrastructure.Container.Infrastructure uses Codeliner.CargoBackend.Infrastructure.Routing, so a change to Codeliner.CargoBackend.Infrastructure.Routing can break Codeliner.CargoBackend.Infrastructure.Container.Infrastructure, while a change to Codeliner.CargoBackend.Infrastructure.Container.Infrastructure can't break Codeliner.CargoBackend.Infrastructure.Routing.
- Position
- Below the diagonal: Codeliner.CargoBackend.Infrastructure.Container.Infrastructure 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 — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 7 | High / Critical |
| A02:2025 — Security Misconfiguration | 4 | High / Critical |
Roadmap
Top priorities: Resolve the 7 Abandoned package finding(s) in Dependency Hygiene; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 7 Abandoned package finding(s) in Dependency Hygiene. | +7.3 pts | Low | Dependency Hygiene |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +3.7 pts | Medium | Keyboard semantics |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +3.7 pts | Medium | Visual & motion safety |
| Adopt pino (or winston) and log at meaningful points in the services you run. | +3.6 pts | Medium | Observability |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +1.7 pts | Low | Documentation Quality |
| Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists. | +2.0 pts | Medium | CI/CD gates |
| Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge. | +1.9 pts | Medium | A11y enforcement |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +1.8 pts | Medium | Forms & labels |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.9 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.5 | Mixed | IaC & Container Security: High IaC: REDACTED |
| GraphTraversalBackend/src/GraphTraversalService.php | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| CargoBackend/src/Infrastructure/Persistence/Doctrine/DoctrineORMTransactionManager.php | 8.5 | Near-clean | Code Duplication: Duplicated block (16 lines × 2) |
| CargoBackend/src/Application/Booking/Dto/LegDto.php | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: LegDto (LCOM4 4) |
| README.md | 9.5 | Near-clean | Documentation Quality: Documentation: no build, run or usage example |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 56 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 56 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, 61 of 94 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
- D1 Cyclomatic Complexity — 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. Most of this repository's production source (.js) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — 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. Most of this repository's production source (.js) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover 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 (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover 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.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (8 contributor(s) across 232 commit(s) sampled, automation and bot accounts excluded). One of them holds 88% of the history; the other 7 hold 1.7% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- 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 (composer.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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 Laminas ServiceManager and a PSR-11 container (Psr\Container), whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- 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.
- X27 Collection changed while being enumerated — 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 Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
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
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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.
- 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
D4 · Code Duplication
2 duplicated block group(s) detected. Measured on part of this repository only: .js (81% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 1 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with GraphTraversalService.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with DoctrineORMTransactionManager.php. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 13 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with LegDto.php. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D12 · Dependency Hygiene
1 outdated, 7 abandoned direct Composer dependencies. 17 of 18 direct production requirements were graded against Packagist (0 not published there, which is what a private Satis repository looks like, 1 with no release resolution). PLATFORM requirements (php, ext-*, lib-*) are deliberately not graded here: they name the runtime rather than a Packagist package, so there is no release for them to be behind — whether that runtime is still supported is a separate question with a separate remedy. Development requirements are excluded, because a consumer never installs them. A newer release is reported only where this repository's OWN constraint already admits it, so the remedy is `composer update` and never a manifest edit. Known CVEs in this dependency graph are D30's question. An ABANDONED package is a migration rather than an upgrade: it receives no further releases at all, including security releases.
What to do
- Resolve the 7 Abandoned package finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (7 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 51 locked Composer package(s) use a banned license. Licences were read from this repository's REDACTED, which records the `license` each package declares, over every package in its production `packages` list, direct and transitive, at the locked version; the 52 package(s) under `packages-dev` are not installed for a consumer and are excluded.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 3183 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 4 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
0 of 50 judged comments only repeat the code they sit on (0.0 %). 4 comment(s) in another language or script were not judged.
D26 · Project Cohesion
1 of 1 build units (Composer) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
34 % of calls cross a namespace and 0 % go through an interface, but 95 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. semgrep hit a parse error in 1 file(s) — `public/js/lodash.js` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
D30 · Dependency Vulnerabilities
7 finding(s): 1 critical, 3 high, 2 medium, 1 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
4 finding(s): 0 critical, 1 high, 3 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D34 · Knowledge Freshness
12 of 12 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is CargoBackend/src/Application/Booking/BookingService.php. Counted over 12 of the 52 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 12 Orphaned file finding(s) in Knowledge Freshness — start with BookingService.php, Cargo.php, GraphTraversalService.php. — One of this dimension's main actionable groups (12 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 18 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
AC1 · Text alternatives
AC2 · Forms & labels
- This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×2) — CargoUI/view/riot/booking/new-cargo.html:5, CargoUI/view/riot/booking/new-cargo.html:11
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — CargoUI/view/riot/booking/new-cargo.html:6, CargoUI/view/riot/booking/new-cargo.html:12
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — CargoUI/view/riot/home.html:10
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. — CargoUI/view/riot/booking/routing/route-candidate.html:9
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety
- `.btn-primary` sets color: #ffffff on background-color: #428bca — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/css/bootstrap.css:2081
- `.btn-success` sets color: #ffffff on background-color: #5cb85c — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/css/bootstrap.css:2204
- `.btn-success:hover, .btn-success:focus, .btn-success:active, .btn-success.active, .open .dropdown-toggle.btn-success` sets color: #ffffff on background-color: #47a447 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/css/bootstrap.css:2214
- `.dropdown-menu > li > a:hover, .dropdown-menu > li > a:focus` sets color: #ffffff on background-color: #428bca — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/css/bootstrap.css:3268
- `.dropdown-menu > .active > a, .dropdown-menu > .active > a:hover, .dropdown-menu > .active > a:focus` sets color: #ffffff on background-color: #428bca — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/css/bootstrap.css:3276
- `.nav-pills > li.active > a, .nav-pills > li.active > a:hover, .nav-pills > li.active > a:focus` sets color: #ffffff on background-color: #428bca — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/css/bootstrap.css:3922
- `.pagination > .active > a, .pagination > .active > span, .pagination > .active > a:hover, .pagination > .active > span:hover, .pagination > .active > a:focus, .pagination > .active > span:focus` sets color: #ffffff on background-color: #428bca — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/css/bootstrap.css:4681
- `a.list-group-item.active > .badge, .nav-pills > .active > a > .badge` sets color: #428bca on background-color: #ffffff — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/css/bootstrap.css:4910
- `.alert-info` sets color: #3a87ad on background-color: #d9edf7 — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/css/bootstrap.css:5041
- `.alert-warning` sets color: #c09853 on background-color: #fcf8e3 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/css/bootstrap.css:5055
- `.alert-danger` sets color: #b94a48 on background-color: #f2dede — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/css/bootstrap.css:5069
- `.panel-primary > .panel-heading` sets color: #ffffff on background-color: #428bca — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/css/bootstrap.css:5452
- `.panel-success > .panel-heading` sets color: #468847 on background-color: #dff0d8 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/css/bootstrap.css:5470
- `.panel-warning > .panel-heading` sets color: #c09853 on background-color: #fcf8e3 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/css/bootstrap.css:5488
- `.panel-danger > .panel-heading` sets color: #b94a48 on background-color: #f2dede — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/css/bootstrap.css:5506
- `.panel-info > .panel-heading` sets color: #3a87ad on background-color: #d9edf7 — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/css/bootstrap.css:5524
- `.btn.active` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/css/bootstrap.css:2024
- `.dropdown-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/css/bootstrap.css:3221
- `.dropdown-menu > .active > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/css/bootstrap.css:3280
- `.open > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/css/bootstrap.css:3303
- `.btn-group > .btn:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/css/bootstrap.css:3399
- `.btn-group.open .dropdown-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/css/bootstrap.css:3480
- `.modal-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/css/bootstrap.css:5644
- `.collapsing` moves (`transition: height 0.35s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — public/css/bootstrap.css:2383
- `.progress-bar` moves (`transition: width 0.6s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — public/css/bootstrap.css:5140
- `.progress.active .progress-bar` moves (`animation: progress-bar-stripes 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — public/css/bootstrap.css:5156
- `.modal.fade .modal-dialog` moves (`transition: transform 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — public/css/bootstrap.css:5621
- `.carousel-inner > .item` moves (`transition: 0.6s ease-in-out left`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — public/css/bootstrap.css:6009
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 14 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX5 · Architecture & structure
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
M3 · Folder & project structure
P1 · CI/CD gates
- The pipeline is well-formed, but the only CI definition is `.travis.yml`, and its `README.md` build badge still points at `travis-ci.org` — a service shut down in June 2021. No other CI is configured in this repository, so nothing has been building or testing changes here since that shutdown — the steps below describe a gate that is not running. Porting it is mostly mechanical: the build and test commands already written here are what a replacement pipeline would run.
What to do
- Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists.
P11 · BDD / executable specs
P2 · Observability
- No logging call was found in the 62 JavaScript/TypeScript, PHP production file(s) this check read across 2 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger; PHP: PSR-3 loggers (Monolog), Laravel's Log facade, error_log()) 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
- Adopt pino (or winston) and log at meaningful points in the services you run.
- Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add phpstan or psalm (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 845 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: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P8 · Schema migrations
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
What to do
- Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 74% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 83% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 72% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 32% | Weak — gated by P1, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 98% | Exemplary | Strongest area. |
| Accessibility | 30% | Weak — gated by AC4, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 3 check(s) recorded observations but carry no score
- AXH1 Runtime security headers — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXI1 Runtime container hardening — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility (rendered) — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 2 control(s) we could not find positive evidence for
- 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
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
- 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
- AXA1 Runtime unauthenticated reachability — This run crawled public routes only — it had no logged-in session, so there is no authenticated surface to compare anonymous access against and nothing was measured. This is a statement about this run, not about your application: nothing here says access control is missing, and nothing here says it is present.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXP1 Runtime third-party data flows — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone_number, …) or stored credential in a Laravel migration, an Eloquent model's $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .js exposed no member bodies
- D10 Test Quality — ~834 lines of test source are present (.php) 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.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D2 Cognitive Complexity — cognitive complexity not measured — .js exposed no member bodies
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, PHP, html 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 (CargoBackend), 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"]`.
- D25 ADR Conformance — no ADRs to check
- D3 God Classes — Most of this repository's production source (.js) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Composer build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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
- D9 Test Distribution — Test source is present (.php) 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 its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit))
- 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
- IC1 Incompleteness & stubs — reported, not scored — this repository's JavaScript/TypeScript declares no class method or module-scope function, and this score is a density of unfinished work per function, which has no denominator here. The file-level signals below were still collected and are shown in full
- M2 Architecture documentation — This repo declares itself a template / kata / sample / demo — formal architecture documentation (ADRs, C4 diagrams) is deferred to a real application built from it, so its absence is not a defect here.
- M4 Documentation accuracy — Not applicable: the 4 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, PHP source, so there is no service whose uptime a failing dependency could take down
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover 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 tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- 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.
- X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — not 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
- 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 — 9 finding(s)
- REDACTED
- REDACTED
- REDACTED
- <label> that labels no control CargoUI/view/riot/booking/new-cargo.html:5
- <label> that labels no control CargoUI/view/riot/booking/new-cargo.html:11
- <select> without a programmatic label CargoUI/view/riot/booking/new-cargo.html:6
- <select> without a programmatic label CargoUI/view/riot/booking/new-cargo.html:12
- REDACTED
- REDACTED
Serious — 64 finding(s)
- Low contrast colour pair in CSS (3.6:1) public/css/bootstrap.css:2081
- Low contrast colour pair in CSS (3.6:1) public/css/bootstrap.css:3268
- Low contrast colour pair in CSS (3.6:1) public/css/bootstrap.css:3276
- Low contrast colour pair in CSS (3.6:1) public/css/bootstrap.css:3922
- Low contrast colour pair in CSS (3.6:1) public/css/bootstrap.css:4681
- Low contrast colour pair in CSS (3.6:1) public/css/bootstrap.css:4910
- Low contrast colour pair in CSS (3.6:1) public/css/bootstrap.css:5452
- Low contrast colour pair in CSS (3.6:1) public/css/bootstrap.css:5470
- Runtime security header not set: content-security-policy
- Runtime security header not set: cross-origin-embedder-policy
- Runtime security header not set: cross-origin-opener-policy
- Runtime security header not set: cross-origin-resource-policy
- Runtime security header not set: permissions-policy
- Runtime security header not set: referrer-policy
- Runtime security header not set: x-dns-prefetch-control
- Runtime security header not set: x-permitted-cross-domain-policies
- Focus outline removed in CSS without a :focus replacement public/css/bootstrap.css:2024
- Focus outline removed in CSS without a :focus replacement public/css/bootstrap.css:3221
- Focus outline removed in CSS without a :focus replacement public/css/bootstrap.css:3280
- Focus outline removed in CSS without a :focus replacement public/css/bootstrap.css:3303
- Focus outline removed in CSS without a :focus replacement public/css/bootstrap.css:3399
- Focus outline removed in CSS without a :focus replacement public/css/bootstrap.css:3480
- Focus outline removed in CSS without a :focus replacement public/css/bootstrap.css:5644
- Abandoned package: zendframework/zend-config
- Abandoned package: zendframework/zend-config-aggregator
- Abandoned package: zendframework/zend-diactoros
- Abandoned package: zendframework/zend-expressive
- Abandoned package: zendframework/zend-expressive-aurarouter
- Abandoned package: zendframework/zend-servicemanager
- Abandoned package: zendframework/zend-stdlib
- Animation without a prefers-reduced-motion guard public/css/bootstrap.css:2383
- Animation without a prefers-reduced-motion guard public/css/bootstrap.css:5140
- Animation without a prefers-reduced-motion guard public/css/bootstrap.css:5156
- Animation without a prefers-reduced-motion guard public/css/bootstrap.css:5621
- Animation without a prefers-reduced-motion guard public/css/bootstrap.css:6009
- Low contrast colour pair in CSS (2.5:1) public/css/bootstrap.css:2204
- Low contrast colour pair in CSS (2.5:1) public/css/bootstrap.css:5055
- Low contrast colour pair in CSS (2.5:1) public/css/bootstrap.css:5488
- Container process runs as root: .-mariadb-1
- Container process runs as root: .-nginx-1
- Container process runs as root: .-php-1
- REDACTED
- REDACTED
- REDACTED
- Low contrast colour pair in CSS (3.3:1) public/css/bootstrap.css:5041
- Low contrast colour pair in CSS (3.3:1) public/css/bootstrap.css:5524
- Low contrast colour pair in CSS (3.9:1) public/css/bootstrap.css:5069
- Low contrast colour pair in CSS (3.9:1) public/css/bootstrap.css:5506
- REDACTED
- REDACTED
- Heading level jumps from h1 to h3 CargoUI/view/riot/home.html:10
- Link used as a button (placeholder href) CargoUI/view/riot/booking/routing/route-candidate.html:9
- Low contrast colour pair in CSS (3.1:1) public/css/bootstrap.css:2214
- Accessibility enforcement below the top rung
- WCAG 1.4.3 reproducibly failed in a rendered surface
- WCAG 2.4.2 reproducibly failed in a rendered surface
- WCAG 2.4.4 reproducibly failed in a rendered surface
- WCAG 3.1.1 reproducibly failed in a rendered surface
- WCAG 4.1.2 reproducibly failed in a rendered surface
- Duplicated block (10 lines × 2) GraphTraversalBackend/src/GraphTraversalService.php:87
- Duplicated block (16 lines × 2) CargoBackend/src/Infrastructure/Persistence/Doctrine/DoctrineORMTransactionManager.php:22
- Low cohesion: LegDto (LCOM4 4) CargoBackend/src/Application/Booking/Dto/LegDto.php:17
- CI pipeline targets a decommissioned service
- No structured logging
Minor — 20 finding(s)
- Orphaned file CargoBackend/src/Application/Booking/BookingService.php:1
- Orphaned file CargoBackend/src/Model/Cargo/Cargo.php:1
- Orphaned file GraphTraversalBackend/src/GraphTraversalService.php:1
- Orphaned file CargoBackend/src/Application/Booking/Dto/CargoRoutingDto.php:1
- Orphaned file features/bootstrap/FeatureContext.php:1
- Orphaned file CargoBackend/src/Infrastructure/Routing/ExternalRoutingService.php:1
- Orphaned file CargoUI/src/Main.php:1
- Orphaned file CargoUI/src/RiotCompiler.php:1
- Orphaned file CargoBackend/src/Infrastructure/Persistence/Doctrine/Type/LegsDoctrineType.php:1
- Orphaned file CargoBackend/src/Http/Action/UpdateCargo.php:1
- Orphaned file CargoBackend/src/Model/Cargo/Leg.php:1
- Orphaned file CargoBackend/src/Application/Booking/Dto/LegDto.php:1
- Documentation: no build, run or usage example README.md:1
- Projects may be oversized for their cohesion
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No SAST
- No rollback/health safety
- PHP static analysis does not check null everywhere
Minor — 1 finding(s)
- Outdated: psr/http-server-middleware
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-13a6d43d5a394c4e92f4532c790c9a45/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-13a6d43d5a394c4e92f4532c790c9a45/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 . | 0 | 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 . | 7 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | 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 |