Executive summary
sivaprasadreddy/spring-boot-application-architecture-patterns is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 66 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 59, is the weakest lens and counts most in the score. The best first step is making the tests check their results, worth about 4 points. Adding automated security scanning would lift Production Readiness itself, also worth about 4. Raising Production Readiness to 70 would lift the score to about 70.
Fourteen known security holes in the packages the code depends on can be used by attackers. Five weaknesses in the code could be used by an attacker, and two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages, fixing the weaknesses the scanner points to and pinning each tool to an exact version would close these risks. The test that checks nothing needs to check the result it produces.
The product code is 6,373 lines, about €12,000 to rebuild.
If Production Readiness rose from 59 to 70, the lowest score rated Strong, the score would rise from 66 to about 70.
New since the last survey: 1 finding
- Test Quality · No assertions (empty test): contextLoads meetup4j-layered/src/test/java/dev/sivalabs/meetup4j/Meetup4jApplicationTests.java
Fixed since the last survey: 35 findings
- Test Quality · No assertions (empty test): contextLoads meetup4j-modulith-tomato/src/test/java/dev/sivalabs/meetup4j/Meetup4jApplicationTests.java
- Boundary Type-Coupling · Cross-context type EventVM (events → registrations)
- Boundary Type-Coupling · Cross-context type EventVM (events → registrations)
- Boundary Type-Coupling · Cross-context type EventVM (events → registrations)
- Boundary Type-Coupling · Cross-context type EventId (events → registrations) meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/EventRegistrationEntity.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/EventRegistrationEntity.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/EventRegistrationEntity.java
- Boundary Type-Coupling · Cross-context type EventId (events → registrations) meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/EventRegistrationEntity.java
- Boundary Type-Coupling · Cross-context type EventId (events → registrations) meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/EventRegistrationEntity.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/EventRegistrationEntity.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/EventRegistrationQueryService.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/EventRegistrationQueryService.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/EventRegistrationQueryService.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations)
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations)
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/RegistrationRepository.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/RegistrationRepository.java
- Boundary Type-Coupling · Cross-context type EventId (events → registrations) meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/RegistrationRepository.java
- Boundary Type-Coupling · Cross-context type EventId (events → registrations) meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/RegistrationRepository.java
- Boundary Type-Coupling · Cross-context type EventId (events → registrations) meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/RegistrationRepository.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations)
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations)
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/domain/repository/RegistrationRepository.java
- Boundary Type-Coupling · Cross-context type EventId (events → registrations) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/domain/model/EventRegistration.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/domain/model/EventRegistration.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/domain/model/EventRegistration.java
- Boundary Type-Coupling · Cross-context type EventId (events → registrations) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/domain/model/EventRegistration.java
- Boundary Type-Coupling · Cross-context type EventId (events → registrations) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/domain/model/EventRegistration.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/domain/model/EventRegistration.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/application/query/RegistrationQueryService.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/application/query/RegistrationQueryService.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/application/query/RegistrationQueryService.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/application/query/RegistrationQueryRepository.java
- Boundary Type-Coupling · Cross-context type EventId (events → registrations) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/application/query/RegistrationQueryRepository.java
- Boundary Type-Coupling · Cross-context type EventCode (events → registrations) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/application/query/RegistrationQueryRepository.java
Rebuild cost: about €12,000 · Estimate
| Cost to rebuild | €4,100 to €21,000, for 68 to 217 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 66. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 6,373 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 domain.models | 2 events.domain.vo | 3 registrations.domain.vo | 4 shared | 5 domain.entities | 6 domain.events | 7 events.domain.event | 8 events.domain.events | 9 events.domain.model | 10 events.domain.models | 11 registrations.application.command.dto | 12 registrations.domain.event | 13 registrations.domain.events | 14 registrations.domain.model | 15 rest.dto | 16 domain.repositories | 17 events.application.command.dto | 18 events.application.query.dto | 19 events.domain | 20 events.domain.repository | 21 notifications.eventhandler | 22 notifications.interfaces.eventhandler | 23 registrations.domain.repository | 24 domain.services | 25 events | 26 events.application.command | 27 events.application.query | 28 events.rest.dto | 29 registrations.application.query.dto | 30 events.application | 31 events.infra.persistence | 32 events.interfaces.rest | 33 events.rest | 34 registrations.domain | 35 rest | 36 registrations.application.command | 37 registrations.application.query | 38 registrations.rest | 39 registrations.infra.persistence | 40 registrations.interfaces.rest |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 domain.models | ||||||||||||||||||||||||||||||||||||||||
| 2 events.domain.vo | ||||||||||||||||||||||||||||||||||||||||
| 3 registrations.domain.vo | ||||||||||||||||||||||||||||||||||||||||
| 4 shared | ||||||||||||||||||||||||||||||||||||||||
| 5 domain.entities | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 domain.events | 5 | |||||||||||||||||||||||||||||||||||||||
| 7 events.domain.event | 3 | |||||||||||||||||||||||||||||||||||||||
| 8 events.domain.events | 3 | |||||||||||||||||||||||||||||||||||||||
| 9 events.domain.model | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 events.domain.models | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 registrations.application.command.dto | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 registrations.domain.event | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 registrations.domain.events | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 registrations.domain.model | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 15 rest.dto | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 domain.repositories | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 events.application.command.dto | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 events.application.query.dto | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 events.domain | 2 | 6 | 3 | |||||||||||||||||||||||||||||||||||||
| 20 events.domain.repository | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 notifications.eventhandler | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 22 notifications.interfaces.eventhandler | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 23 registrations.domain.repository | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 domain.services | 13 | 2 | 5 | 2 | ||||||||||||||||||||||||||||||||||||
| 25 events | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 26 events.application.command | 2 | 3 | 3 | 4 | ||||||||||||||||||||||||||||||||||||
| 27 events.application.query | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 28 events.rest.dto | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 registrations.application.query.dto | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 events.application | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 events.infra.persistence | 4 | 1 | 4 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 32 events.interfaces.rest | 1 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 events.rest | 5 | 2 | 2 | 3 | ||||||||||||||||||||||||||||||||||||
| 34 registrations.domain | 1 | 1 | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 35 rest | 5 | 5 | 3 | |||||||||||||||||||||||||||||||||||||
| 36 registrations.application.command | 1 | 2 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 37 registrations.application.query | 3 | 2 | 6 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 registrations.rest | 1 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 39 registrations.infra.persistence | 6 | 7 | 1 | 2 | 1 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 40 registrations.interfaces.rest | 1 | 2 | 4 | 2 | 2 |
5→1 domain.entities uses domain.models✕
- Connections
- 2 pairs of types, where a type in domain.entities uses a type in domain.models.
- The types involved
dev.sivalabs.meetup4j.domain.entities.EventEntity→dev.sivalabs.meetup4j.domain.models.EventStatusdev.sivalabs.meetup4j.domain.entities.EventEntity→dev.sivalabs.meetup4j.domain.models.EventType
- Direction
- domain.entities uses domain.models, so a change to domain.models can break domain.entities, while a change to domain.entities can't break domain.models.
- Position
- Below the diagonal: domain.entities uses a module listed above it, which is the healthy direction.
6→1 domain.events uses domain.models✕
- Connections
- 5 pairs of types, where a type in domain.events uses a type in domain.models.
- The types involved
dev.sivalabs.meetup4j.domain.events.EventCancelled→dev.sivalabs.meetup4j.domain.models.DomainEventdev.sivalabs.meetup4j.domain.events.EventCreated→dev.sivalabs.meetup4j.domain.models.DomainEventdev.sivalabs.meetup4j.domain.events.EventPublished→dev.sivalabs.meetup4j.domain.models.DomainEventdev.sivalabs.meetup4j.domain.events.RegistrationAdded→dev.sivalabs.meetup4j.domain.models.DomainEventdev.sivalabs.meetup4j.domain.events.RegistrationCancelled→dev.sivalabs.meetup4j.domain.models.DomainEvent
- Direction
- domain.events uses domain.models, so a change to domain.models can break domain.events, while a change to domain.events can't break domain.models.
- Position
- Below the diagonal: domain.events uses a module listed above it, which is the healthy direction.
7→4 events.domain.event uses shared✕
- Connections
- 3 pairs of types, where a type in events.domain.event uses a type in shared.
- The types involved
dev.sivalabs.meetup4j.events.domain.event.EventCancelled→dev.sivalabs.meetup4j.shared.DomainEventdev.sivalabs.meetup4j.events.domain.event.EventCreated→dev.sivalabs.meetup4j.shared.DomainEventdev.sivalabs.meetup4j.events.domain.event.EventPublished→dev.sivalabs.meetup4j.shared.DomainEvent
- Direction
- events.domain.event uses shared, so a change to shared can break events.domain.event, while a change to events.domain.event can't break shared.
- Position
- Below the diagonal: events.domain.event uses a module listed above it, which is the healthy direction.
8→4 events.domain.events uses shared✕
- Connections
- 3 pairs of types, where a type in events.domain.events uses a type in shared.
- The types involved
dev.sivalabs.meetup4j.events.domain.events.EventCancelled→dev.sivalabs.meetup4j.shared.DomainEventdev.sivalabs.meetup4j.events.domain.events.EventCreated→dev.sivalabs.meetup4j.shared.DomainEventdev.sivalabs.meetup4j.events.domain.events.EventPublished→dev.sivalabs.meetup4j.shared.DomainEvent
- Direction
- events.domain.events uses shared, so a change to shared can break events.domain.events, while a change to events.domain.events can't break shared.
- Position
- Below the diagonal: events.domain.events uses a module listed above it, which is the healthy direction.
9→4 events.domain.model uses shared✕
- Connections
- 1 pair of types, where a type in events.domain.model uses a type in shared.
- The types involved
dev.sivalabs.meetup4j.events.domain.model.Event→dev.sivalabs.meetup4j.shared.AggregateRoot
- Direction
- events.domain.model uses shared, so a change to shared can break events.domain.model, while a change to events.domain.model can't break shared.
- Position
- Below the diagonal: events.domain.model uses a module listed above it, which is the healthy direction.
10→19 events.domain.models uses events.domain part of a loop✕
- Connections
- 2 pairs of types, where a type in events.domain.models uses a type in events.domain.
- The types involved
dev.sivalabs.meetup4j.events.domain.models.EventVM→dev.sivalabs.meetup4j.events.domain.EventStatusdev.sivalabs.meetup4j.events.domain.models.EventVM→dev.sivalabs.meetup4j.events.domain.EventType
- Direction
- events.domain.models uses events.domain, so a change to events.domain can break events.domain.models, while a change to events.domain.models can't break events.domain.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→2 registrations.application.command.dto uses events.domain.vo✕
- Connections
- 1 pair of types, where a type in registrations.application.command.dto uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.application.command.dto.RegisterAttendeeCmd→dev.sivalabs.meetup4j.events.domain.vo.EventCode
- Direction
- registrations.application.command.dto uses events.domain.vo, so a change to events.domain.vo can break registrations.application.command.dto, while a change to registrations.application.command.dto can't break events.domain.vo.
- Position
- Below the diagonal: registrations.application.command.dto uses a module listed above it, which is the healthy direction.
11→3 registrations.application.command.dto uses registrations.domain.vo✕
- Connections
- 2 pairs of types, where a type in registrations.application.command.dto uses a type in registrations.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.application.command.dto.CancelRegistrationCmd→dev.sivalabs.meetup4j.registrations.domain.vo.RegistrationCodedev.sivalabs.meetup4j.registrations.application.command.dto.RegisterAttendeeCmd→dev.sivalabs.meetup4j.registrations.domain.vo.Email
- Direction
- registrations.application.command.dto uses registrations.domain.vo, so a change to registrations.domain.vo can break registrations.application.command.dto, while a change to registrations.application.command.dto can't break registrations.domain.vo.
- Position
- Below the diagonal: registrations.application.command.dto uses a module listed above it, which is the healthy direction.
12→4 registrations.domain.event uses shared✕
- Connections
- 2 pairs of types, where a type in registrations.domain.event uses a type in shared.
- The types involved
dev.sivalabs.meetup4j.registrations.domain.event.RegistrationAdded→dev.sivalabs.meetup4j.shared.DomainEventdev.sivalabs.meetup4j.registrations.domain.event.RegistrationCancelled→dev.sivalabs.meetup4j.shared.DomainEvent
- Direction
- registrations.domain.event uses shared, so a change to shared can break registrations.domain.event, while a change to registrations.domain.event can't break shared.
- Position
- Below the diagonal: registrations.domain.event uses a module listed above it, which is the healthy direction.
13→4 registrations.domain.events uses shared✕
- Connections
- 2 pairs of types, where a type in registrations.domain.events uses a type in shared.
- The types involved
dev.sivalabs.meetup4j.registrations.domain.events.RegistrationAdded→dev.sivalabs.meetup4j.shared.DomainEventdev.sivalabs.meetup4j.registrations.domain.events.RegistrationCancelled→dev.sivalabs.meetup4j.shared.DomainEvent
- Direction
- registrations.domain.events uses shared, so a change to shared can break registrations.domain.events, while a change to registrations.domain.events can't break shared.
- Position
- Below the diagonal: registrations.domain.events uses a module listed above it, which is the healthy direction.
14→2 registrations.domain.model uses events.domain.vo✕
- Connections
- 2 pairs of types, where a type in registrations.domain.model uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.domain.model.EventRegistration→dev.sivalabs.meetup4j.events.domain.vo.EventCodedev.sivalabs.meetup4j.registrations.domain.model.EventRegistration→dev.sivalabs.meetup4j.events.domain.vo.EventId
- Direction
- registrations.domain.model uses events.domain.vo, so a change to events.domain.vo can break registrations.domain.model, while a change to registrations.domain.model can't break events.domain.vo.
- Position
- Below the diagonal: registrations.domain.model uses a module listed above it, which is the healthy direction.
14→3 registrations.domain.model uses registrations.domain.vo✕
- Connections
- 3 pairs of types, where a type in registrations.domain.model uses a type in registrations.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.domain.model.EventRegistration→dev.sivalabs.meetup4j.registrations.domain.vo.Emaildev.sivalabs.meetup4j.registrations.domain.model.EventRegistration→dev.sivalabs.meetup4j.registrations.domain.vo.RegistrationCodedev.sivalabs.meetup4j.registrations.domain.model.EventRegistration→dev.sivalabs.meetup4j.registrations.domain.vo.RegistrationId
- Direction
- registrations.domain.model uses registrations.domain.vo, so a change to registrations.domain.vo can break registrations.domain.model, while a change to registrations.domain.model can't break registrations.domain.vo.
- Position
- Below the diagonal: registrations.domain.model uses a module listed above it, which is the healthy direction.
14→4 registrations.domain.model uses shared✕
- Connections
- 1 pair of types, where a type in registrations.domain.model uses a type in shared.
- The types involved
dev.sivalabs.meetup4j.registrations.domain.model.EventRegistration→dev.sivalabs.meetup4j.shared.AggregateRoot
- Direction
- registrations.domain.model uses shared, so a change to shared can break registrations.domain.model, while a change to registrations.domain.model can't break shared.
- Position
- Below the diagonal: registrations.domain.model uses a module listed above it, which is the healthy direction.
15→1 rest.dto uses domain.models✕
- Connections
- 2 pairs of types, where a type in rest.dto uses a type in domain.models.
- The types involved
dev.sivalabs.meetup4j.rest.dto.CreateEventRequest→dev.sivalabs.meetup4j.domain.models.EventTypedev.sivalabs.meetup4j.rest.dto.EventsResponse→dev.sivalabs.meetup4j.domain.models.EventVM
- Direction
- rest.dto uses domain.models, so a change to domain.models can break rest.dto, while a change to rest.dto can't break domain.models.
- Position
- Below the diagonal: rest.dto uses a module listed above it, which is the healthy direction.
16→5 domain.repositories uses domain.entities✕
- Connections
- 2 pairs of types, where a type in domain.repositories uses a type in domain.entities.
- The types involved
dev.sivalabs.meetup4j.domain.repositories.EventRepository→dev.sivalabs.meetup4j.domain.entities.EventEntitydev.sivalabs.meetup4j.domain.repositories.RegistrationRepository→dev.sivalabs.meetup4j.domain.entities.EventRegistrationEntity
- Direction
- domain.repositories uses domain.entities, so a change to domain.entities can break domain.repositories, while a change to domain.repositories can't break domain.entities.
- Position
- Below the diagonal: domain.repositories uses a module listed above it, which is the healthy direction.
17→2 events.application.command.dto uses events.domain.vo✕
- Connections
- 2 pairs of types, where a type in events.application.command.dto uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.events.application.command.dto.CancelEventCmd→dev.sivalabs.meetup4j.events.domain.vo.EventCodedev.sivalabs.meetup4j.events.application.command.dto.PublishEventCmd→dev.sivalabs.meetup4j.events.domain.vo.EventCode
- Direction
- events.application.command.dto uses events.domain.vo, so a change to events.domain.vo can break events.application.command.dto, while a change to events.application.command.dto can't break events.domain.vo.
- Position
- Below the diagonal: events.application.command.dto uses a module listed above it, which is the healthy direction.
17→9 events.application.command.dto uses events.domain.model✕
- Connections
- 1 pair of types, where a type in events.application.command.dto uses a type in events.domain.model.
- The types involved
dev.sivalabs.meetup4j.events.application.command.dto.CreateEventCmd→dev.sivalabs.meetup4j.events.domain.model.EventType
- Direction
- events.application.command.dto uses events.domain.model, so a change to events.domain.model can break events.application.command.dto, while a change to events.application.command.dto can't break events.domain.model.
- Position
- Below the diagonal: events.application.command.dto uses a module listed above it, which is the healthy direction.
18→9 events.application.query.dto uses events.domain.model✕
- Connections
- 2 pairs of types, where a type in events.application.query.dto uses a type in events.domain.model.
- The types involved
dev.sivalabs.meetup4j.events.application.query.dto.EventVM→dev.sivalabs.meetup4j.events.domain.model.EventStatusdev.sivalabs.meetup4j.events.application.query.dto.EventVM→dev.sivalabs.meetup4j.events.domain.model.EventType
- Direction
- events.application.query.dto uses events.domain.model, so a change to events.domain.model can break events.application.query.dto, while a change to events.application.query.dto can't break events.domain.model.
- Position
- Below the diagonal: events.application.query.dto uses a module listed above it, which is the healthy direction.
19→2 events.domain uses events.domain.vo✕
- Connections
- 2 pairs of types, where a type in events.domain uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.events.domain.EventQueryService→dev.sivalabs.meetup4j.events.domain.vo.EventCodedev.sivalabs.meetup4j.events.domain.EventQueryService→dev.sivalabs.meetup4j.events.domain.vo.EventId
- Direction
- events.domain uses events.domain.vo, so a change to events.domain.vo can break events.domain, while a change to events.domain can't break events.domain.vo.
- Position
- Below the diagonal: events.domain uses a module listed above it, which is the healthy direction.
19→4 events.domain uses shared✕
- Connections
- 6 pairs of types, where a type in events.domain uses a type in shared.
- The types involved
dev.sivalabs.meetup4j.events.domain.EventCancellationException→dev.sivalabs.meetup4j.shared.DomainExceptiondev.sivalabs.meetup4j.events.domain.EventEntity→dev.sivalabs.meetup4j.shared.BaseEntitydev.sivalabs.meetup4j.events.domain.EventQueryService→dev.sivalabs.meetup4j.shared.SpringEventPublisherdev.sivalabs.meetup4j.events.domain.EventService→dev.sivalabs.meetup4j.shared.SpringEventPublisherdev.sivalabs.meetup4j.events.domain.EventSlotReservationException→dev.sivalabs.meetup4j.shared.DomainExceptiondev.sivalabs.meetup4j.events.domain.InvalidEventCreationException→dev.sivalabs.meetup4j.shared.DomainException
- Direction
- events.domain uses shared, so a change to shared can break events.domain, while a change to events.domain can't break shared.
- Position
- Below the diagonal: events.domain uses a module listed above it, which is the healthy direction.
19→10 events.domain uses events.domain.models✕
- Connections
- 3 pairs of types, where a type in events.domain uses a type in events.domain.models.
- The types involved
dev.sivalabs.meetup4j.events.domain.EventMapper→dev.sivalabs.meetup4j.events.domain.models.EventVMdev.sivalabs.meetup4j.events.domain.EventQueryService→dev.sivalabs.meetup4j.events.domain.models.EventVMdev.sivalabs.meetup4j.events.domain.EventService→dev.sivalabs.meetup4j.events.domain.models.EventVM
- Direction
- events.domain uses events.domain.models, so a change to events.domain.models can break events.domain, while a change to events.domain can't break events.domain.models.
- Position
- Below the diagonal: events.domain uses a module listed above it, which is the healthy direction.
20→2 events.domain.repository uses events.domain.vo✕
- Connections
- 2 pairs of types, where a type in events.domain.repository uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.events.domain.repository.EventRepository→dev.sivalabs.meetup4j.events.domain.vo.EventCodedev.sivalabs.meetup4j.events.domain.repository.EventRepository→dev.sivalabs.meetup4j.events.domain.vo.EventId
- Direction
- events.domain.repository uses events.domain.vo, so a change to events.domain.vo can break events.domain.repository, while a change to events.domain.repository can't break events.domain.vo.
- Position
- Below the diagonal: events.domain.repository uses a module listed above it, which is the healthy direction.
20→9 events.domain.repository uses events.domain.model✕
- Connections
- 1 pair of types, where a type in events.domain.repository uses a type in events.domain.model.
- The types involved
dev.sivalabs.meetup4j.events.domain.repository.EventRepository→dev.sivalabs.meetup4j.events.domain.model.Event
- Direction
- events.domain.repository uses events.domain.model, so a change to events.domain.model can break events.domain.repository, while a change to events.domain.repository can't break events.domain.model.
- Position
- Below the diagonal: events.domain.repository uses a module listed above it, which is the healthy direction.
21→8 notifications.eventhandler uses events.domain.events✕
- Connections
- 3 pairs of types, where a type in notifications.eventhandler uses a type in events.domain.events.
- The types involved
dev.sivalabs.meetup4j.notifications.eventhandler.EventActivityListener→dev.sivalabs.meetup4j.events.domain.events.EventCancelleddev.sivalabs.meetup4j.notifications.eventhandler.EventActivityListener→dev.sivalabs.meetup4j.events.domain.events.EventCreateddev.sivalabs.meetup4j.notifications.eventhandler.EventActivityListener→dev.sivalabs.meetup4j.events.domain.events.EventPublished
- Direction
- notifications.eventhandler uses events.domain.events, so a change to events.domain.events can break notifications.eventhandler, while a change to notifications.eventhandler can't break events.domain.events.
- Position
- Below the diagonal: notifications.eventhandler uses a module listed above it, which is the healthy direction.
21→13 notifications.eventhandler uses registrations.domain.events✕
- Connections
- 2 pairs of types, where a type in notifications.eventhandler uses a type in registrations.domain.events.
- The types involved
dev.sivalabs.meetup4j.notifications.eventhandler.RegistrationEventListener→dev.sivalabs.meetup4j.registrations.domain.events.RegistrationAddeddev.sivalabs.meetup4j.notifications.eventhandler.RegistrationEventListener→dev.sivalabs.meetup4j.registrations.domain.events.RegistrationCancelled
- Direction
- notifications.eventhandler uses registrations.domain.events, so a change to registrations.domain.events can break notifications.eventhandler, while a change to notifications.eventhandler can't break registrations.domain.events.
- Position
- Below the diagonal: notifications.eventhandler uses a module listed above it, which is the healthy direction.
22→7 notifications.interfaces.eventhandler uses events.domain.event✕
- Connections
- 3 pairs of types, where a type in notifications.interfaces.eventhandler uses a type in events.domain.event.
- The types involved
dev.sivalabs.meetup4j.notifications.interfaces.eventhandler.EventActivityListener→dev.sivalabs.meetup4j.events.domain.event.EventCancelleddev.sivalabs.meetup4j.notifications.interfaces.eventhandler.EventActivityListener→dev.sivalabs.meetup4j.events.domain.event.EventCreateddev.sivalabs.meetup4j.notifications.interfaces.eventhandler.EventActivityListener→dev.sivalabs.meetup4j.events.domain.event.EventPublished
- Direction
- notifications.interfaces.eventhandler uses events.domain.event, so a change to events.domain.event can break notifications.interfaces.eventhandler, while a change to notifications.interfaces.eventhandler can't break events.domain.event.
- Position
- Below the diagonal: notifications.interfaces.eventhandler uses a module listed above it, which is the healthy direction.
22→12 notifications.interfaces.eventhandler uses registrations.domain.event✕
- Connections
- 2 pairs of types, where a type in notifications.interfaces.eventhandler uses a type in registrations.domain.event.
- The types involved
dev.sivalabs.meetup4j.notifications.interfaces.eventhandler.RegistrationEventListener→dev.sivalabs.meetup4j.registrations.domain.event.RegistrationAddeddev.sivalabs.meetup4j.notifications.interfaces.eventhandler.RegistrationEventListener→dev.sivalabs.meetup4j.registrations.domain.event.RegistrationCancelled
- Direction
- notifications.interfaces.eventhandler uses registrations.domain.event, so a change to registrations.domain.event can break notifications.interfaces.eventhandler, while a change to notifications.interfaces.eventhandler can't break registrations.domain.event.
- Position
- Below the diagonal: notifications.interfaces.eventhandler uses a module listed above it, which is the healthy direction.
23→2 registrations.domain.repository uses events.domain.vo✕
- Connections
- 1 pair of types, where a type in registrations.domain.repository uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.domain.repository.RegistrationRepository→dev.sivalabs.meetup4j.events.domain.vo.EventCode
- Direction
- registrations.domain.repository uses events.domain.vo, so a change to events.domain.vo can break registrations.domain.repository, while a change to registrations.domain.repository can't break events.domain.vo.
- Position
- Below the diagonal: registrations.domain.repository uses a module listed above it, which is the healthy direction.
23→3 registrations.domain.repository uses registrations.domain.vo✕
- Connections
- 2 pairs of types, where a type in registrations.domain.repository uses a type in registrations.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.domain.repository.RegistrationRepository→dev.sivalabs.meetup4j.registrations.domain.vo.Emaildev.sivalabs.meetup4j.registrations.domain.repository.RegistrationRepository→dev.sivalabs.meetup4j.registrations.domain.vo.RegistrationCode
- Direction
- registrations.domain.repository uses registrations.domain.vo, so a change to registrations.domain.vo can break registrations.domain.repository, while a change to registrations.domain.repository can't break registrations.domain.vo.
- Position
- Below the diagonal: registrations.domain.repository uses a module listed above it, which is the healthy direction.
23→14 registrations.domain.repository uses registrations.domain.model✕
- Connections
- 1 pair of types, where a type in registrations.domain.repository uses a type in registrations.domain.model.
- The types involved
dev.sivalabs.meetup4j.registrations.domain.repository.RegistrationRepository→dev.sivalabs.meetup4j.registrations.domain.model.EventRegistration
- Direction
- registrations.domain.repository uses registrations.domain.model, so a change to registrations.domain.model can break registrations.domain.repository, while a change to registrations.domain.repository can't break registrations.domain.model.
- Position
- Below the diagonal: registrations.domain.repository uses a module listed above it, which is the healthy direction.
24→1 domain.services uses domain.models✕
- Connections
- 13 pairs of types, where a type in domain.services uses a type in domain.models.
- The types involved
dev.sivalabs.meetup4j.domain.services.EventMapper→dev.sivalabs.meetup4j.domain.models.EventVMdev.sivalabs.meetup4j.domain.services.EventRegistrationService→dev.sivalabs.meetup4j.domain.models.AttendeesVMdev.sivalabs.meetup4j.domain.services.EventRegistrationService→dev.sivalabs.meetup4j.domain.models.CancelRegistrationCmddev.sivalabs.meetup4j.domain.services.EventRegistrationService→dev.sivalabs.meetup4j.domain.models.RegisterAttendeeCmddev.sivalabs.meetup4j.domain.services.EventRegistrationService→dev.sivalabs.meetup4j.domain.models.RegistrationVMdev.sivalabs.meetup4j.domain.services.EventRegistrationService→dev.sivalabs.meetup4j.domain.models.UserEventsVMdev.sivalabs.meetup4j.domain.services.EventRegistrationService→dev.sivalabs.meetup4j.domain.models.UserRegistrationStatusdev.sivalabs.meetup4j.domain.services.EventService→dev.sivalabs.meetup4j.domain.models.CancelEventCmddev.sivalabs.meetup4j.domain.services.EventService→dev.sivalabs.meetup4j.domain.models.CreateEventCmddev.sivalabs.meetup4j.domain.services.EventService→dev.sivalabs.meetup4j.domain.models.EventVMdev.sivalabs.meetup4j.domain.services.EventService→dev.sivalabs.meetup4j.domain.models.PublishEventCmddev.sivalabs.meetup4j.domain.services.RegistrationMapper→dev.sivalabs.meetup4j.domain.models.RegistrationVMdev.sivalabs.meetup4j.domain.services.SpringEventPublisher→dev.sivalabs.meetup4j.domain.models.DomainEvent
- Direction
- domain.services uses domain.models, so a change to domain.models can break domain.services, while a change to domain.services can't break domain.models.
- Position
- Below the diagonal: domain.services uses a module listed above it, which is the healthy direction.
24→5 domain.services uses domain.entities✕
- Connections
- 2 pairs of types, where a type in domain.services uses a type in domain.entities.
- The types involved
dev.sivalabs.meetup4j.domain.services.EventMapper→dev.sivalabs.meetup4j.domain.entities.EventEntitydev.sivalabs.meetup4j.domain.services.RegistrationMapper→dev.sivalabs.meetup4j.domain.entities.EventRegistrationEntity
- Direction
- domain.services uses domain.entities, so a change to domain.entities can break domain.services, while a change to domain.services can't break domain.entities.
- Position
- Below the diagonal: domain.services uses a module listed above it, which is the healthy direction.
24→6 domain.services uses domain.events✕
- Connections
- 5 pairs of types, where a type in domain.services uses a type in domain.events.
- The types involved
dev.sivalabs.meetup4j.domain.services.EventActivityListener→dev.sivalabs.meetup4j.domain.events.EventCancelleddev.sivalabs.meetup4j.domain.services.EventActivityListener→dev.sivalabs.meetup4j.domain.events.EventCreateddev.sivalabs.meetup4j.domain.services.EventActivityListener→dev.sivalabs.meetup4j.domain.events.EventPublisheddev.sivalabs.meetup4j.domain.services.RegistrationEventListener→dev.sivalabs.meetup4j.domain.events.RegistrationAddeddev.sivalabs.meetup4j.domain.services.RegistrationEventListener→dev.sivalabs.meetup4j.domain.events.RegistrationCancelled
- Direction
- domain.services uses domain.events, so a change to domain.events can break domain.services, while a change to domain.services can't break domain.events.
- Position
- Below the diagonal: domain.services uses a module listed above it, which is the healthy direction.
24→16 domain.services uses domain.repositories✕
- Connections
- 2 pairs of types, where a type in domain.services uses a type in domain.repositories.
- The types involved
dev.sivalabs.meetup4j.domain.services.EventRegistrationService→dev.sivalabs.meetup4j.domain.repositories.RegistrationRepositorydev.sivalabs.meetup4j.domain.services.EventService→dev.sivalabs.meetup4j.domain.repositories.EventRepository
- Direction
- domain.services uses domain.repositories, so a change to domain.repositories can break domain.services, while a change to domain.services can't break domain.repositories.
- Position
- Below the diagonal: domain.services uses a module listed above it, which is the healthy direction.
25→2 events uses events.domain.vo✕
- Connections
- 2 pairs of types, where a type in events uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.events.EventsAPI→dev.sivalabs.meetup4j.events.domain.vo.EventCodedev.sivalabs.meetup4j.events.EventsAPI→dev.sivalabs.meetup4j.events.domain.vo.EventId
- Direction
- events uses events.domain.vo, so a change to events.domain.vo can break events, while a change to events can't break events.domain.vo.
- Position
- Below the diagonal: events uses a module listed above it, which is the healthy direction.
25→10 events uses events.domain.models✕
- Connections
- 1 pair of types, where a type in events uses a type in events.domain.models.
- The types involved
dev.sivalabs.meetup4j.events.EventsAPI→dev.sivalabs.meetup4j.events.domain.models.EventVM
- Direction
- events uses events.domain.models, so a change to events.domain.models can break events, while a change to events can't break events.domain.models.
- Position
- Below the diagonal: events uses a module listed above it, which is the healthy direction.
25→19 events uses events.domain✕
- Connections
- 2 pairs of types, where a type in events uses a type in events.domain.
- The types involved
dev.sivalabs.meetup4j.events.EventsAPI→dev.sivalabs.meetup4j.events.domain.EventQueryServicedev.sivalabs.meetup4j.events.EventsAPI→dev.sivalabs.meetup4j.events.domain.EventService
- Direction
- events uses events.domain, so a change to events.domain can break events, while a change to events can't break events.domain.
- Position
- Below the diagonal: events uses a module listed above it, which is the healthy direction.
26→2 events.application.command uses events.domain.vo✕
- Connections
- 2 pairs of types, where a type in events.application.command uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.events.application.command.CreateEventUseCase→dev.sivalabs.meetup4j.events.domain.vo.EventCodedev.sivalabs.meetup4j.events.application.command.EventSlotReservationUseCase→dev.sivalabs.meetup4j.events.domain.vo.EventId
- Direction
- events.application.command uses events.domain.vo, so a change to events.domain.vo can break events.application.command, while a change to events.application.command can't break events.domain.vo.
- Position
- Below the diagonal: events.application.command uses a module listed above it, which is the healthy direction.
26→4 events.application.command uses shared✕
- Connections
- 3 pairs of types, where a type in events.application.command uses a type in shared.
- The types involved
dev.sivalabs.meetup4j.events.application.command.CancelEventUseCase→dev.sivalabs.meetup4j.shared.DomainEventPublisherdev.sivalabs.meetup4j.events.application.command.CreateEventUseCase→dev.sivalabs.meetup4j.shared.DomainEventPublisherdev.sivalabs.meetup4j.events.application.command.PublishEventUseCase→dev.sivalabs.meetup4j.shared.DomainEventPublisher
- Direction
- events.application.command uses shared, so a change to shared can break events.application.command, while a change to events.application.command can't break shared.
- Position
- Below the diagonal: events.application.command uses a module listed above it, which is the healthy direction.
26→17 events.application.command uses events.application.command.dto✕
- Connections
- 3 pairs of types, where a type in events.application.command uses a type in events.application.command.dto.
- The types involved
dev.sivalabs.meetup4j.events.application.command.CancelEventUseCase→dev.sivalabs.meetup4j.events.application.command.dto.CancelEventCmddev.sivalabs.meetup4j.events.application.command.CreateEventUseCase→dev.sivalabs.meetup4j.events.application.command.dto.CreateEventCmddev.sivalabs.meetup4j.events.application.command.PublishEventUseCase→dev.sivalabs.meetup4j.events.application.command.dto.PublishEventCmd
- Direction
- events.application.command uses events.application.command.dto, so a change to events.application.command.dto can break events.application.command, while a change to events.application.command can't break events.application.command.dto.
- Position
- Below the diagonal: events.application.command uses a module listed above it, which is the healthy direction.
26→20 events.application.command uses events.domain.repository✕
- Connections
- 4 pairs of types, where a type in events.application.command uses a type in events.domain.repository.
- The types involved
dev.sivalabs.meetup4j.events.application.command.CancelEventUseCase→dev.sivalabs.meetup4j.events.domain.repository.EventRepositorydev.sivalabs.meetup4j.events.application.command.CreateEventUseCase→dev.sivalabs.meetup4j.events.domain.repository.EventRepositorydev.sivalabs.meetup4j.events.application.command.EventSlotReservationUseCase→dev.sivalabs.meetup4j.events.domain.repository.EventRepositorydev.sivalabs.meetup4j.events.application.command.PublishEventUseCase→dev.sivalabs.meetup4j.events.domain.repository.EventRepository
- Direction
- events.application.command uses events.domain.repository, so a change to events.domain.repository can break events.application.command, while a change to events.application.command can't break events.domain.repository.
- Position
- Below the diagonal: events.application.command uses a module listed above it, which is the healthy direction.
27→2 events.application.query uses events.domain.vo✕
- Connections
- 4 pairs of types, where a type in events.application.query uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.events.application.query.EventQueryRepository→dev.sivalabs.meetup4j.events.domain.vo.EventCodedev.sivalabs.meetup4j.events.application.query.EventQueryRepository→dev.sivalabs.meetup4j.events.domain.vo.EventIddev.sivalabs.meetup4j.events.application.query.EventQueryService→dev.sivalabs.meetup4j.events.domain.vo.EventCodedev.sivalabs.meetup4j.events.application.query.EventQueryService→dev.sivalabs.meetup4j.events.domain.vo.EventId
- Direction
- events.application.query uses events.domain.vo, so a change to events.domain.vo can break events.application.query, while a change to events.application.query can't break events.domain.vo.
- Position
- Below the diagonal: events.application.query uses a module listed above it, which is the healthy direction.
27→18 events.application.query uses events.application.query.dto✕
- Connections
- 2 pairs of types, where a type in events.application.query uses a type in events.application.query.dto.
- The types involved
dev.sivalabs.meetup4j.events.application.query.EventQueryRepository→dev.sivalabs.meetup4j.events.application.query.dto.EventVMdev.sivalabs.meetup4j.events.application.query.EventQueryService→dev.sivalabs.meetup4j.events.application.query.dto.EventVM
- Direction
- events.application.query uses events.application.query.dto, so a change to events.application.query.dto can break events.application.query, while a change to events.application.query can't break events.application.query.dto.
- Position
- Below the diagonal: events.application.query uses a module listed above it, which is the healthy direction.
28→10 events.rest.dto uses events.domain.models✕
- Connections
- 1 pair of types, where a type in events.rest.dto uses a type in events.domain.models.
- The types involved
dev.sivalabs.meetup4j.events.rest.dto.EventsResponse→dev.sivalabs.meetup4j.events.domain.models.EventVM
- Direction
- events.rest.dto uses events.domain.models, so a change to events.domain.models can break events.rest.dto, while a change to events.rest.dto can't break events.domain.models.
- Position
- Below the diagonal: events.rest.dto uses a module listed above it, which is the healthy direction.
28→19 events.rest.dto uses events.domain✕
- Connections
- 1 pair of types, where a type in events.rest.dto uses a type in events.domain.
- The types involved
dev.sivalabs.meetup4j.events.rest.dto.CreateEventRequest→dev.sivalabs.meetup4j.events.domain.EventType
- Direction
- events.rest.dto uses events.domain, so a change to events.domain can break events.rest.dto, while a change to events.rest.dto can't break events.domain.
- Position
- Below the diagonal: events.rest.dto uses a module listed above it, which is the healthy direction.
29→18 registrations.application.query.dto uses events.application.query.dto✕
- Connections
- 1 pair of types, where a type in registrations.application.query.dto uses a type in events.application.query.dto.
- The types involved
dev.sivalabs.meetup4j.registrations.application.query.dto.UserEventsVM→dev.sivalabs.meetup4j.events.application.query.dto.EventVM
- Direction
- registrations.application.query.dto uses events.application.query.dto, so a change to events.application.query.dto can break registrations.application.query.dto, while a change to registrations.application.query.dto can't break events.application.query.dto.
- Position
- Below the diagonal: registrations.application.query.dto uses a module listed above it, which is the healthy direction.
30→2 events.application uses events.domain.vo✕
- Connections
- 2 pairs of types, where a type in events.application uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.events.application.EventsAPI→dev.sivalabs.meetup4j.events.domain.vo.EventCodedev.sivalabs.meetup4j.events.application.EventsAPI→dev.sivalabs.meetup4j.events.domain.vo.EventId
- Direction
- events.application uses events.domain.vo, so a change to events.domain.vo can break events.application, while a change to events.application can't break events.domain.vo.
- Position
- Below the diagonal: events.application uses a module listed above it, which is the healthy direction.
30→18 events.application uses events.application.query.dto✕
- Connections
- 1 pair of types, where a type in events.application uses a type in events.application.query.dto.
- The types involved
dev.sivalabs.meetup4j.events.application.EventsAPI→dev.sivalabs.meetup4j.events.application.query.dto.EventVM
- Direction
- events.application uses events.application.query.dto, so a change to events.application.query.dto can break events.application, while a change to events.application can't break events.application.query.dto.
- Position
- Below the diagonal: events.application uses a module listed above it, which is the healthy direction.
30→26 events.application uses events.application.command✕
- Connections
- 1 pair of types, where a type in events.application uses a type in events.application.command.
- The types involved
dev.sivalabs.meetup4j.events.application.EventsAPI→dev.sivalabs.meetup4j.events.application.command.EventSlotReservationUseCase
- Direction
- events.application uses events.application.command, so a change to events.application.command can break events.application, while a change to events.application can't break events.application.command.
- Position
- Below the diagonal: events.application uses a module listed above it, which is the healthy direction.
30→27 events.application uses events.application.query✕
- Connections
- 1 pair of types, where a type in events.application uses a type in events.application.query.
- The types involved
dev.sivalabs.meetup4j.events.application.EventsAPI→dev.sivalabs.meetup4j.events.application.query.EventQueryService
- Direction
- events.application uses events.application.query, so a change to events.application.query can break events.application, while a change to events.application can't break events.application.query.
- Position
- Below the diagonal: events.application uses a module listed above it, which is the healthy direction.
31→2 events.infra.persistence uses events.domain.vo✕
- Connections
- 4 pairs of types, where a type in events.infra.persistence uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.events.infra.persistence.EventRepositoryAdapter→dev.sivalabs.meetup4j.events.domain.vo.EventCodedev.sivalabs.meetup4j.events.infra.persistence.EventRepositoryAdapter→dev.sivalabs.meetup4j.events.domain.vo.EventIddev.sivalabs.meetup4j.events.infra.persistence.JpaEventRepository→dev.sivalabs.meetup4j.events.domain.vo.EventCodedev.sivalabs.meetup4j.events.infra.persistence.JpaEventRepository→dev.sivalabs.meetup4j.events.domain.vo.EventId
- Direction
- events.infra.persistence uses events.domain.vo, so a change to events.domain.vo can break events.infra.persistence, while a change to events.infra.persistence can't break events.domain.vo.
- Position
- Below the diagonal: events.infra.persistence uses a module listed above it, which is the healthy direction.
31→4 events.infra.persistence uses shared✕
- Connections
- 1 pair of types, where a type in events.infra.persistence uses a type in shared.
- The types involved
dev.sivalabs.meetup4j.events.infra.persistence.EventEntity→dev.sivalabs.meetup4j.shared.BaseEntity
- Direction
- events.infra.persistence uses shared, so a change to shared can break events.infra.persistence, while a change to events.infra.persistence can't break shared.
- Position
- Below the diagonal: events.infra.persistence uses a module listed above it, which is the healthy direction.
31→9 events.infra.persistence uses events.domain.model✕
- Connections
- 4 pairs of types, where a type in events.infra.persistence uses a type in events.domain.model.
- The types involved
dev.sivalabs.meetup4j.events.infra.persistence.EventEntity→dev.sivalabs.meetup4j.events.domain.model.EventStatusdev.sivalabs.meetup4j.events.infra.persistence.EventEntity→dev.sivalabs.meetup4j.events.domain.model.EventTypedev.sivalabs.meetup4j.events.infra.persistence.EventEntityMapper→dev.sivalabs.meetup4j.events.domain.model.Eventdev.sivalabs.meetup4j.events.infra.persistence.EventRepositoryAdapter→dev.sivalabs.meetup4j.events.domain.model.Event
- Direction
- events.infra.persistence uses events.domain.model, so a change to events.domain.model can break events.infra.persistence, while a change to events.infra.persistence can't break events.domain.model.
- Position
- Below the diagonal: events.infra.persistence uses a module listed above it, which is the healthy direction.
31→18 events.infra.persistence uses events.application.query.dto✕
- Connections
- 2 pairs of types, where a type in events.infra.persistence uses a type in events.application.query.dto.
- The types involved
dev.sivalabs.meetup4j.events.infra.persistence.EventRepositoryAdapter→dev.sivalabs.meetup4j.events.application.query.dto.EventVMdev.sivalabs.meetup4j.events.infra.persistence.EventViewMapper→dev.sivalabs.meetup4j.events.application.query.dto.EventVM
- Direction
- events.infra.persistence uses events.application.query.dto, so a change to events.application.query.dto can break events.infra.persistence, while a change to events.infra.persistence can't break events.application.query.dto.
- Position
- Below the diagonal: events.infra.persistence uses a module listed above it, which is the healthy direction.
31→20 events.infra.persistence uses events.domain.repository✕
- Connections
- 1 pair of types, where a type in events.infra.persistence uses a type in events.domain.repository.
- The types involved
dev.sivalabs.meetup4j.events.infra.persistence.EventRepositoryAdapter→dev.sivalabs.meetup4j.events.domain.repository.EventRepository
- Direction
- events.infra.persistence uses events.domain.repository, so a change to events.domain.repository can break events.infra.persistence, while a change to events.infra.persistence can't break events.domain.repository.
- Position
- Below the diagonal: events.infra.persistence uses a module listed above it, which is the healthy direction.
31→27 events.infra.persistence uses events.application.query✕
- Connections
- 1 pair of types, where a type in events.infra.persistence uses a type in events.application.query.
- The types involved
dev.sivalabs.meetup4j.events.infra.persistence.EventRepositoryAdapter→dev.sivalabs.meetup4j.events.application.query.EventQueryRepository
- Direction
- events.infra.persistence uses events.application.query, so a change to events.application.query can break events.infra.persistence, while a change to events.infra.persistence can't break events.application.query.
- Position
- Below the diagonal: events.infra.persistence uses a module listed above it, which is the healthy direction.
32→9 events.interfaces.rest uses events.domain.model✕
- Connections
- 1 pair of types, where a type in events.interfaces.rest uses a type in events.domain.model.
- The types involved
dev.sivalabs.meetup4j.events.interfaces.rest.CreateEventRequest→dev.sivalabs.meetup4j.events.domain.model.EventType
- Direction
- events.interfaces.rest uses events.domain.model, so a change to events.domain.model can break events.interfaces.rest, while a change to events.interfaces.rest can't break events.domain.model.
- Position
- Below the diagonal: events.interfaces.rest uses a module listed above it, which is the healthy direction.
32→18 events.interfaces.rest uses events.application.query.dto✕
- Connections
- 2 pairs of types, where a type in events.interfaces.rest uses a type in events.application.query.dto.
- The types involved
dev.sivalabs.meetup4j.events.interfaces.rest.EventsController→dev.sivalabs.meetup4j.events.application.query.dto.EventVMdev.sivalabs.meetup4j.events.interfaces.rest.EventsResponse→dev.sivalabs.meetup4j.events.application.query.dto.EventVM
- Direction
- events.interfaces.rest uses events.application.query.dto, so a change to events.application.query.dto can break events.interfaces.rest, while a change to events.interfaces.rest can't break events.application.query.dto.
- Position
- Below the diagonal: events.interfaces.rest uses a module listed above it, which is the healthy direction.
32→26 events.interfaces.rest uses events.application.command✕
- Connections
- 3 pairs of types, where a type in events.interfaces.rest uses a type in events.application.command.
- The types involved
dev.sivalabs.meetup4j.events.interfaces.rest.EventsController→dev.sivalabs.meetup4j.events.application.command.CancelEventUseCasedev.sivalabs.meetup4j.events.interfaces.rest.EventsController→dev.sivalabs.meetup4j.events.application.command.CreateEventUseCasedev.sivalabs.meetup4j.events.interfaces.rest.EventsController→dev.sivalabs.meetup4j.events.application.command.PublishEventUseCase
- Direction
- events.interfaces.rest uses events.application.command, so a change to events.application.command can break events.interfaces.rest, while a change to events.interfaces.rest can't break events.application.command.
- Position
- Below the diagonal: events.interfaces.rest uses a module listed above it, which is the healthy direction.
32→27 events.interfaces.rest uses events.application.query✕
- Connections
- 1 pair of types, where a type in events.interfaces.rest uses a type in events.application.query.
- The types involved
dev.sivalabs.meetup4j.events.interfaces.rest.EventsController→dev.sivalabs.meetup4j.events.application.query.EventQueryService
- Direction
- events.interfaces.rest uses events.application.query, so a change to events.application.query can break events.interfaces.rest, while a change to events.interfaces.rest can't break events.application.query.
- Position
- Below the diagonal: events.interfaces.rest uses a module listed above it, which is the healthy direction.
33→2 events.rest uses events.domain.vo✕
- Connections
- 5 pairs of types, where a type in events.rest uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.events.rest.CreateEventRequest→dev.sivalabs.meetup4j.events.domain.vo.Capacitydev.sivalabs.meetup4j.events.rest.CreateEventRequest→dev.sivalabs.meetup4j.events.domain.vo.EventDetailsdev.sivalabs.meetup4j.events.rest.CreateEventRequest→dev.sivalabs.meetup4j.events.domain.vo.EventLocationdev.sivalabs.meetup4j.events.rest.CreateEventRequest→dev.sivalabs.meetup4j.events.domain.vo.Scheduledev.sivalabs.meetup4j.events.rest.CreateEventRequest→dev.sivalabs.meetup4j.events.domain.vo.TicketPrice
- Direction
- events.rest uses events.domain.vo, so a change to events.domain.vo can break events.rest, while a change to events.rest can't break events.domain.vo.
- Position
- Below the diagonal: events.rest uses a module listed above it, which is the healthy direction.
33→10 events.rest uses events.domain.models✕
- Connections
- 2 pairs of types, where a type in events.rest uses a type in events.domain.models.
- The types involved
dev.sivalabs.meetup4j.events.rest.EventsController→dev.sivalabs.meetup4j.events.domain.models.EventVMdev.sivalabs.meetup4j.events.rest.EventsResponse→dev.sivalabs.meetup4j.events.domain.models.EventVM
- Direction
- events.rest uses events.domain.models, so a change to events.domain.models can break events.rest, while a change to events.rest can't break events.domain.models.
- Position
- Below the diagonal: events.rest uses a module listed above it, which is the healthy direction.
33→19 events.rest uses events.domain✕
- Connections
- 2 pairs of types, where a type in events.rest uses a type in events.domain.
- The types involved
dev.sivalabs.meetup4j.events.rest.CreateEventRequest→dev.sivalabs.meetup4j.events.domain.EventTypedev.sivalabs.meetup4j.events.rest.EventsController→dev.sivalabs.meetup4j.events.domain.EventService
- Direction
- events.rest uses events.domain, so a change to events.domain can break events.rest, while a change to events.rest can't break events.domain.
- Position
- Below the diagonal: events.rest uses a module listed above it, which is the healthy direction.
33→28 events.rest uses events.rest.dto✕
- Connections
- 3 pairs of types, where a type in events.rest uses a type in events.rest.dto.
- The types involved
dev.sivalabs.meetup4j.events.rest.EventsController→dev.sivalabs.meetup4j.events.rest.dto.CreateEventRequestdev.sivalabs.meetup4j.events.rest.EventsController→dev.sivalabs.meetup4j.events.rest.dto.CreateEventResponsedev.sivalabs.meetup4j.events.rest.EventsController→dev.sivalabs.meetup4j.events.rest.dto.EventsResponse
- Direction
- events.rest uses events.rest.dto, so a change to events.rest.dto can break events.rest, while a change to events.rest can't break events.rest.dto.
- Position
- Below the diagonal: events.rest uses a module listed above it, which is the healthy direction.
34→2 registrations.domain uses events.domain.vo✕
- Connections
- 1 pair of types, where a type in registrations.domain uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.domain.EventRegistrationQueryService→dev.sivalabs.meetup4j.events.domain.vo.EventCode
- Direction
- registrations.domain uses events.domain.vo, so a change to events.domain.vo can break registrations.domain, while a change to registrations.domain can't break events.domain.vo.
- Position
- Below the diagonal: registrations.domain uses a module listed above it, which is the healthy direction.
34→3 registrations.domain uses registrations.domain.vo✕
- Connections
- 1 pair of types, where a type in registrations.domain uses a type in registrations.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.domain.EventRegistrationQueryService→dev.sivalabs.meetup4j.registrations.domain.vo.Email
- Direction
- registrations.domain uses registrations.domain.vo, so a change to registrations.domain.vo can break registrations.domain, while a change to registrations.domain can't break registrations.domain.vo.
- Position
- Below the diagonal: registrations.domain uses a module listed above it, which is the healthy direction.
34→4 registrations.domain uses shared✕
- Connections
- 3 pairs of types, where a type in registrations.domain uses a type in shared.
- The types involved
dev.sivalabs.meetup4j.registrations.domain.EventRegistrationEntity→dev.sivalabs.meetup4j.shared.BaseEntitydev.sivalabs.meetup4j.registrations.domain.EventRegistrationService→dev.sivalabs.meetup4j.shared.SpringEventPublisherdev.sivalabs.meetup4j.registrations.domain.RegistrationCancellationException→dev.sivalabs.meetup4j.shared.DomainException
- Direction
- registrations.domain uses shared, so a change to shared can break registrations.domain, while a change to registrations.domain can't break shared.
- Position
- Below the diagonal: registrations.domain uses a module listed above it, which is the healthy direction.
34→10 registrations.domain uses events.domain.models✕
- Connections
- 1 pair of types, where a type in registrations.domain uses a type in events.domain.models.
- The types involved
dev.sivalabs.meetup4j.registrations.domain.UserEventsVM→dev.sivalabs.meetup4j.events.domain.models.EventVM
- Direction
- registrations.domain uses events.domain.models, so a change to events.domain.models can break registrations.domain, while a change to registrations.domain can't break events.domain.models.
- Position
- Below the diagonal: registrations.domain uses a module listed above it, which is the healthy direction.
34→19 registrations.domain uses events.domain✕
- Connections
- 1 pair of types, where a type in registrations.domain uses a type in events.domain.
- The types involved
dev.sivalabs.meetup4j.registrations.domain.EventRegistrationService→dev.sivalabs.meetup4j.events.domain.EventService
- Direction
- registrations.domain uses events.domain, so a change to events.domain can break registrations.domain, while a change to registrations.domain can't break events.domain.
- Position
- Below the diagonal: registrations.domain uses a module listed above it, which is the healthy direction.
34→25 registrations.domain uses events✕
- Connections
- 1 pair of types, where a type in registrations.domain uses a type in events.
- The types involved
dev.sivalabs.meetup4j.registrations.domain.EventRegistrationQueryService→dev.sivalabs.meetup4j.events.EventsAPI
- Direction
- registrations.domain uses events, so a change to events can break registrations.domain, while a change to registrations.domain can't break events.
- Position
- Below the diagonal: registrations.domain uses a module listed above it, which is the healthy direction.
35→1 rest uses domain.models✕
- Connections
- 5 pairs of types, where a type in rest uses a type in domain.models.
- The types involved
dev.sivalabs.meetup4j.rest.EventRegistrationController→dev.sivalabs.meetup4j.domain.models.AttendeesVMdev.sivalabs.meetup4j.rest.EventRegistrationController→dev.sivalabs.meetup4j.domain.models.EventRegistrationsdev.sivalabs.meetup4j.rest.EventRegistrationController→dev.sivalabs.meetup4j.domain.models.UserRegistrationStatusdev.sivalabs.meetup4j.rest.EventsController→dev.sivalabs.meetup4j.domain.models.EventVMdev.sivalabs.meetup4j.rest.UserEventsController→dev.sivalabs.meetup4j.domain.models.UserEventsVM
- Direction
- rest uses domain.models, so a change to domain.models can break rest, while a change to rest can't break domain.models.
- Position
- Below the diagonal: rest uses a module listed above it, which is the healthy direction.
35→15 rest uses rest.dto✕
- Connections
- 5 pairs of types, where a type in rest uses a type in rest.dto.
- The types involved
dev.sivalabs.meetup4j.rest.EventRegistrationController→dev.sivalabs.meetup4j.rest.dto.EventRegistrationRequestdev.sivalabs.meetup4j.rest.EventRegistrationController→dev.sivalabs.meetup4j.rest.dto.EventRegistrationResponsedev.sivalabs.meetup4j.rest.EventsController→dev.sivalabs.meetup4j.rest.dto.CreateEventRequestdev.sivalabs.meetup4j.rest.EventsController→dev.sivalabs.meetup4j.rest.dto.CreateEventResponsedev.sivalabs.meetup4j.rest.EventsController→dev.sivalabs.meetup4j.rest.dto.EventsResponse
- Direction
- rest uses rest.dto, so a change to rest.dto can break rest, while a change to rest can't break rest.dto.
- Position
- Below the diagonal: rest uses a module listed above it, which is the healthy direction.
35→24 rest uses domain.services✕
- Connections
- 3 pairs of types, where a type in rest uses a type in domain.services.
- The types involved
dev.sivalabs.meetup4j.rest.EventRegistrationController→dev.sivalabs.meetup4j.domain.services.EventRegistrationServicedev.sivalabs.meetup4j.rest.EventsController→dev.sivalabs.meetup4j.domain.services.EventServicedev.sivalabs.meetup4j.rest.UserEventsController→dev.sivalabs.meetup4j.domain.services.EventRegistrationService
- Direction
- rest uses domain.services, so a change to domain.services can break rest, while a change to rest can't break domain.services.
- Position
- Below the diagonal: rest uses a module listed above it, which is the healthy direction.
36→3 registrations.application.command uses registrations.domain.vo✕
- Connections
- 1 pair of types, where a type in registrations.application.command uses a type in registrations.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.application.command.RegisterAttendeeUseCase→dev.sivalabs.meetup4j.registrations.domain.vo.RegistrationCode
- Direction
- registrations.application.command uses registrations.domain.vo, so a change to registrations.domain.vo can break registrations.application.command, while a change to registrations.application.command can't break registrations.domain.vo.
- Position
- Below the diagonal: registrations.application.command uses a module listed above it, which is the healthy direction.
36→4 registrations.application.command uses shared✕
- Connections
- 2 pairs of types, where a type in registrations.application.command uses a type in shared.
- The types involved
dev.sivalabs.meetup4j.registrations.application.command.CancelRegistrationUseCase→dev.sivalabs.meetup4j.shared.DomainEventPublisherdev.sivalabs.meetup4j.registrations.application.command.RegisterAttendeeUseCase→dev.sivalabs.meetup4j.shared.DomainEventPublisher
- Direction
- registrations.application.command uses shared, so a change to shared can break registrations.application.command, while a change to registrations.application.command can't break shared.
- Position
- Below the diagonal: registrations.application.command uses a module listed above it, which is the healthy direction.
36→11 registrations.application.command uses registrations.application.command.dto✕
- Connections
- 2 pairs of types, where a type in registrations.application.command uses a type in registrations.application.command.dto.
- The types involved
dev.sivalabs.meetup4j.registrations.application.command.CancelRegistrationUseCase→dev.sivalabs.meetup4j.registrations.application.command.dto.CancelRegistrationCmddev.sivalabs.meetup4j.registrations.application.command.RegisterAttendeeUseCase→dev.sivalabs.meetup4j.registrations.application.command.dto.RegisterAttendeeCmd
- Direction
- registrations.application.command uses registrations.application.command.dto, so a change to registrations.application.command.dto can break registrations.application.command, while a change to registrations.application.command can't break registrations.application.command.dto.
- Position
- Below the diagonal: registrations.application.command uses a module listed above it, which is the healthy direction.
36→23 registrations.application.command uses registrations.domain.repository✕
- Connections
- 2 pairs of types, where a type in registrations.application.command uses a type in registrations.domain.repository.
- The types involved
dev.sivalabs.meetup4j.registrations.application.command.CancelRegistrationUseCase→dev.sivalabs.meetup4j.registrations.domain.repository.RegistrationRepositorydev.sivalabs.meetup4j.registrations.application.command.RegisterAttendeeUseCase→dev.sivalabs.meetup4j.registrations.domain.repository.RegistrationRepository
- Direction
- registrations.application.command uses registrations.domain.repository, so a change to registrations.domain.repository can break registrations.application.command, while a change to registrations.application.command can't break registrations.domain.repository.
- Position
- Below the diagonal: registrations.application.command uses a module listed above it, which is the healthy direction.
36→30 registrations.application.command uses events.application✕
- Connections
- 2 pairs of types, where a type in registrations.application.command uses a type in events.application.
- The types involved
dev.sivalabs.meetup4j.registrations.application.command.CancelRegistrationUseCase→dev.sivalabs.meetup4j.events.application.EventsAPIdev.sivalabs.meetup4j.registrations.application.command.RegisterAttendeeUseCase→dev.sivalabs.meetup4j.events.application.EventsAPI
- Direction
- registrations.application.command uses events.application, so a change to events.application can break registrations.application.command, while a change to registrations.application.command can't break events.application.
- Position
- Below the diagonal: registrations.application.command uses a module listed above it, which is the healthy direction.
37→2 registrations.application.query uses events.domain.vo✕
- Connections
- 3 pairs of types, where a type in registrations.application.query uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.application.query.RegistrationQueryRepository→dev.sivalabs.meetup4j.events.domain.vo.EventCodedev.sivalabs.meetup4j.registrations.application.query.RegistrationQueryRepository→dev.sivalabs.meetup4j.events.domain.vo.EventIddev.sivalabs.meetup4j.registrations.application.query.RegistrationQueryService→dev.sivalabs.meetup4j.events.domain.vo.EventCode
- Direction
- registrations.application.query uses events.domain.vo, so a change to events.domain.vo can break registrations.application.query, while a change to registrations.application.query can't break events.domain.vo.
- Position
- Below the diagonal: registrations.application.query uses a module listed above it, which is the healthy direction.
37→3 registrations.application.query uses registrations.domain.vo✕
- Connections
- 2 pairs of types, where a type in registrations.application.query uses a type in registrations.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.application.query.RegistrationQueryRepository→dev.sivalabs.meetup4j.registrations.domain.vo.Emaildev.sivalabs.meetup4j.registrations.application.query.RegistrationQueryService→dev.sivalabs.meetup4j.registrations.domain.vo.Email
- Direction
- registrations.application.query uses registrations.domain.vo, so a change to registrations.domain.vo can break registrations.application.query, while a change to registrations.application.query can't break registrations.domain.vo.
- Position
- Below the diagonal: registrations.application.query uses a module listed above it, which is the healthy direction.
37→29 registrations.application.query uses registrations.application.query.dto✕
- Connections
- 6 pairs of types, where a type in registrations.application.query uses a type in registrations.application.query.dto.
- The types involved
dev.sivalabs.meetup4j.registrations.application.query.RegistrationQueryRepository→dev.sivalabs.meetup4j.registrations.application.query.dto.RegistrationVMdev.sivalabs.meetup4j.registrations.application.query.RegistrationQueryRepository→dev.sivalabs.meetup4j.registrations.application.query.dto.UserEventsVMdev.sivalabs.meetup4j.registrations.application.query.RegistrationQueryService→dev.sivalabs.meetup4j.registrations.application.query.dto.AttendeesVMdev.sivalabs.meetup4j.registrations.application.query.RegistrationQueryService→dev.sivalabs.meetup4j.registrations.application.query.dto.RegistrationVMdev.sivalabs.meetup4j.registrations.application.query.RegistrationQueryService→dev.sivalabs.meetup4j.registrations.application.query.dto.UserEventsVMdev.sivalabs.meetup4j.registrations.application.query.RegistrationQueryService→dev.sivalabs.meetup4j.registrations.application.query.dto.UserRegistrationStatus
- Direction
- registrations.application.query uses registrations.application.query.dto, so a change to registrations.application.query.dto can break registrations.application.query, while a change to registrations.application.query can't break registrations.application.query.dto.
- Position
- Below the diagonal: registrations.application.query uses a module listed above it, which is the healthy direction.
37→30 registrations.application.query uses events.application✕
- Connections
- 1 pair of types, where a type in registrations.application.query uses a type in events.application.
- The types involved
dev.sivalabs.meetup4j.registrations.application.query.RegistrationQueryService→dev.sivalabs.meetup4j.events.application.EventsAPI
- Direction
- registrations.application.query uses events.application, so a change to events.application can break registrations.application.query, while a change to registrations.application.query can't break events.application.
- Position
- Below the diagonal: registrations.application.query uses a module listed above it, which is the healthy direction.
38→2 registrations.rest uses events.domain.vo✕
- Connections
- 1 pair of types, where a type in registrations.rest uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.rest.EventRegistrationRequest→dev.sivalabs.meetup4j.events.domain.vo.EventCode
- Direction
- registrations.rest uses events.domain.vo, so a change to events.domain.vo can break registrations.rest, while a change to registrations.rest can't break events.domain.vo.
- Position
- Below the diagonal: registrations.rest uses a module listed above it, which is the healthy direction.
38→3 registrations.rest uses registrations.domain.vo✕
- Connections
- 1 pair of types, where a type in registrations.rest uses a type in registrations.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.rest.EventRegistrationRequest→dev.sivalabs.meetup4j.registrations.domain.vo.Email
- Direction
- registrations.rest uses registrations.domain.vo, so a change to registrations.domain.vo can break registrations.rest, while a change to registrations.rest can't break registrations.domain.vo.
- Position
- Below the diagonal: registrations.rest uses a module listed above it, which is the healthy direction.
38→34 registrations.rest uses registrations.domain✕
- Connections
- 6 pairs of types, where a type in registrations.rest uses a type in registrations.domain.
- The types involved
dev.sivalabs.meetup4j.registrations.rest.EventRegistrationController→dev.sivalabs.meetup4j.registrations.domain.AttendeesVMdev.sivalabs.meetup4j.registrations.rest.EventRegistrationController→dev.sivalabs.meetup4j.registrations.domain.EventRegistrationServicedev.sivalabs.meetup4j.registrations.rest.EventRegistrationController→dev.sivalabs.meetup4j.registrations.domain.EventRegistrationsdev.sivalabs.meetup4j.registrations.rest.EventRegistrationController→dev.sivalabs.meetup4j.registrations.domain.UserRegistrationStatusdev.sivalabs.meetup4j.registrations.rest.UserEventsController→dev.sivalabs.meetup4j.registrations.domain.EventRegistrationServicedev.sivalabs.meetup4j.registrations.rest.UserEventsController→dev.sivalabs.meetup4j.registrations.domain.UserEventsVM
- Direction
- registrations.rest uses registrations.domain, so a change to registrations.domain can break registrations.rest, while a change to registrations.rest can't break registrations.domain.
- Position
- Below the diagonal: registrations.rest uses a module listed above it, which is the healthy direction.
39→2 registrations.infra.persistence uses events.domain.vo✕
- Connections
- 6 pairs of types, where a type in registrations.infra.persistence uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.infra.persistence.EventRegistrationEntity→dev.sivalabs.meetup4j.events.domain.vo.EventCodedev.sivalabs.meetup4j.registrations.infra.persistence.EventRegistrationEntity→dev.sivalabs.meetup4j.events.domain.vo.EventIddev.sivalabs.meetup4j.registrations.infra.persistence.JpaRegistrationRepository→dev.sivalabs.meetup4j.events.domain.vo.EventCodedev.sivalabs.meetup4j.registrations.infra.persistence.JpaRegistrationRepository→dev.sivalabs.meetup4j.events.domain.vo.EventIddev.sivalabs.meetup4j.registrations.infra.persistence.RegistrationRepositoryAdapter→dev.sivalabs.meetup4j.events.domain.vo.EventCodedev.sivalabs.meetup4j.registrations.infra.persistence.RegistrationRepositoryAdapter→dev.sivalabs.meetup4j.events.domain.vo.EventId
- Direction
- registrations.infra.persistence uses events.domain.vo, so a change to events.domain.vo can break registrations.infra.persistence, while a change to registrations.infra.persistence can't break events.domain.vo.
- Position
- Below the diagonal: registrations.infra.persistence uses a module listed above it, which is the healthy direction.
39→3 registrations.infra.persistence uses registrations.domain.vo✕
- Connections
- 7 pairs of types, where a type in registrations.infra.persistence uses a type in registrations.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.infra.persistence.EventRegistrationEntity→dev.sivalabs.meetup4j.registrations.domain.vo.Emaildev.sivalabs.meetup4j.registrations.infra.persistence.EventRegistrationEntity→dev.sivalabs.meetup4j.registrations.domain.vo.RegistrationCodedev.sivalabs.meetup4j.registrations.infra.persistence.EventRegistrationEntity→dev.sivalabs.meetup4j.registrations.domain.vo.RegistrationIddev.sivalabs.meetup4j.registrations.infra.persistence.JpaRegistrationRepository→dev.sivalabs.meetup4j.registrations.domain.vo.Emaildev.sivalabs.meetup4j.registrations.infra.persistence.JpaRegistrationRepository→dev.sivalabs.meetup4j.registrations.domain.vo.RegistrationCodedev.sivalabs.meetup4j.registrations.infra.persistence.RegistrationRepositoryAdapter→dev.sivalabs.meetup4j.registrations.domain.vo.Emaildev.sivalabs.meetup4j.registrations.infra.persistence.RegistrationRepositoryAdapter→dev.sivalabs.meetup4j.registrations.domain.vo.RegistrationCode
- Direction
- registrations.infra.persistence uses registrations.domain.vo, so a change to registrations.domain.vo can break registrations.infra.persistence, while a change to registrations.infra.persistence can't break registrations.domain.vo.
- Position
- Below the diagonal: registrations.infra.persistence uses a module listed above it, which is the healthy direction.
39→4 registrations.infra.persistence uses shared✕
- Connections
- 1 pair of types, where a type in registrations.infra.persistence uses a type in shared.
- The types involved
dev.sivalabs.meetup4j.registrations.infra.persistence.EventRegistrationEntity→dev.sivalabs.meetup4j.shared.BaseEntity
- Direction
- registrations.infra.persistence uses shared, so a change to shared can break registrations.infra.persistence, while a change to registrations.infra.persistence can't break shared.
- Position
- Below the diagonal: registrations.infra.persistence uses a module listed above it, which is the healthy direction.
39→14 registrations.infra.persistence uses registrations.domain.model✕
- Connections
- 2 pairs of types, where a type in registrations.infra.persistence uses a type in registrations.domain.model.
- The types involved
dev.sivalabs.meetup4j.registrations.infra.persistence.RegistrationEntityMapper→dev.sivalabs.meetup4j.registrations.domain.model.EventRegistrationdev.sivalabs.meetup4j.registrations.infra.persistence.RegistrationRepositoryAdapter→dev.sivalabs.meetup4j.registrations.domain.model.EventRegistration
- Direction
- registrations.infra.persistence uses registrations.domain.model, so a change to registrations.domain.model can break registrations.infra.persistence, while a change to registrations.infra.persistence can't break registrations.domain.model.
- Position
- Below the diagonal: registrations.infra.persistence uses a module listed above it, which is the healthy direction.
39→23 registrations.infra.persistence uses registrations.domain.repository✕
- Connections
- 1 pair of types, where a type in registrations.infra.persistence uses a type in registrations.domain.repository.
- The types involved
dev.sivalabs.meetup4j.registrations.infra.persistence.RegistrationRepositoryAdapter→dev.sivalabs.meetup4j.registrations.domain.repository.RegistrationRepository
- Direction
- registrations.infra.persistence uses registrations.domain.repository, so a change to registrations.domain.repository can break registrations.infra.persistence, while a change to registrations.infra.persistence can't break registrations.domain.repository.
- Position
- Below the diagonal: registrations.infra.persistence uses a module listed above it, which is the healthy direction.
39→29 registrations.infra.persistence uses registrations.application.query.dto✕
- Connections
- 3 pairs of types, where a type in registrations.infra.persistence uses a type in registrations.application.query.dto.
- The types involved
dev.sivalabs.meetup4j.registrations.infra.persistence.RegistrationRepositoryAdapter→dev.sivalabs.meetup4j.registrations.application.query.dto.RegistrationVMdev.sivalabs.meetup4j.registrations.infra.persistence.RegistrationRepositoryAdapter→dev.sivalabs.meetup4j.registrations.application.query.dto.UserEventsVMdev.sivalabs.meetup4j.registrations.infra.persistence.RegistrationViewMapper→dev.sivalabs.meetup4j.registrations.application.query.dto.RegistrationVM
- Direction
- registrations.infra.persistence uses registrations.application.query.dto, so a change to registrations.application.query.dto can break registrations.infra.persistence, while a change to registrations.infra.persistence can't break registrations.application.query.dto.
- Position
- Below the diagonal: registrations.infra.persistence uses a module listed above it, which is the healthy direction.
39→30 registrations.infra.persistence uses events.application✕
- Connections
- 1 pair of types, where a type in registrations.infra.persistence uses a type in events.application.
- The types involved
dev.sivalabs.meetup4j.registrations.infra.persistence.RegistrationRepositoryAdapter→dev.sivalabs.meetup4j.events.application.EventsAPI
- Direction
- registrations.infra.persistence uses events.application, so a change to events.application can break registrations.infra.persistence, while a change to registrations.infra.persistence can't break events.application.
- Position
- Below the diagonal: registrations.infra.persistence uses a module listed above it, which is the healthy direction.
39→37 registrations.infra.persistence uses registrations.application.query✕
- Connections
- 1 pair of types, where a type in registrations.infra.persistence uses a type in registrations.application.query.
- The types involved
dev.sivalabs.meetup4j.registrations.infra.persistence.RegistrationRepositoryAdapter→dev.sivalabs.meetup4j.registrations.application.query.RegistrationQueryRepository
- Direction
- registrations.infra.persistence uses registrations.application.query, so a change to registrations.application.query can break registrations.infra.persistence, while a change to registrations.infra.persistence can't break registrations.application.query.
- Position
- Below the diagonal: registrations.infra.persistence uses a module listed above it, which is the healthy direction.
40→2 registrations.interfaces.rest uses events.domain.vo✕
- Connections
- 1 pair of types, where a type in registrations.interfaces.rest uses a type in events.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.interfaces.rest.EventRegistrationController→dev.sivalabs.meetup4j.events.domain.vo.EventCode
- Direction
- registrations.interfaces.rest uses events.domain.vo, so a change to events.domain.vo can break registrations.interfaces.rest, while a change to registrations.interfaces.rest can't break events.domain.vo.
- Position
- Below the diagonal: registrations.interfaces.rest uses a module listed above it, which is the healthy direction.
40→3 registrations.interfaces.rest uses registrations.domain.vo✕
- Connections
- 2 pairs of types, where a type in registrations.interfaces.rest uses a type in registrations.domain.vo.
- The types involved
dev.sivalabs.meetup4j.registrations.interfaces.rest.EventRegistrationController→dev.sivalabs.meetup4j.registrations.domain.vo.Emaildev.sivalabs.meetup4j.registrations.interfaces.rest.EventRegistrationController→dev.sivalabs.meetup4j.registrations.domain.vo.RegistrationCode
- Direction
- registrations.interfaces.rest uses registrations.domain.vo, so a change to registrations.domain.vo can break registrations.interfaces.rest, while a change to registrations.interfaces.rest can't break registrations.domain.vo.
- Position
- Below the diagonal: registrations.interfaces.rest uses a module listed above it, which is the healthy direction.
40→29 registrations.interfaces.rest uses registrations.application.query.dto✕
- Connections
- 4 pairs of types, where a type in registrations.interfaces.rest uses a type in registrations.application.query.dto.
- The types involved
dev.sivalabs.meetup4j.registrations.interfaces.rest.EventRegistrationController→dev.sivalabs.meetup4j.registrations.application.query.dto.AttendeesVMdev.sivalabs.meetup4j.registrations.interfaces.rest.EventRegistrationController→dev.sivalabs.meetup4j.registrations.application.query.dto.EventRegistrationsdev.sivalabs.meetup4j.registrations.interfaces.rest.EventRegistrationController→dev.sivalabs.meetup4j.registrations.application.query.dto.UserRegistrationStatusdev.sivalabs.meetup4j.registrations.interfaces.rest.UserEventsController→dev.sivalabs.meetup4j.registrations.application.query.dto.UserEventsVM
- Direction
- registrations.interfaces.rest uses registrations.application.query.dto, so a change to registrations.application.query.dto can break registrations.interfaces.rest, while a change to registrations.interfaces.rest can't break registrations.application.query.dto.
- Position
- Below the diagonal: registrations.interfaces.rest uses a module listed above it, which is the healthy direction.
40→36 registrations.interfaces.rest uses registrations.application.command✕
- Connections
- 2 pairs of types, where a type in registrations.interfaces.rest uses a type in registrations.application.command.
- The types involved
dev.sivalabs.meetup4j.registrations.interfaces.rest.EventRegistrationController→dev.sivalabs.meetup4j.registrations.application.command.CancelRegistrationUseCasedev.sivalabs.meetup4j.registrations.interfaces.rest.EventRegistrationController→dev.sivalabs.meetup4j.registrations.application.command.RegisterAttendeeUseCase
- Direction
- registrations.interfaces.rest uses registrations.application.command, so a change to registrations.application.command can break registrations.interfaces.rest, while a change to registrations.interfaces.rest can't break registrations.application.command.
- Position
- Below the diagonal: registrations.interfaces.rest uses a module listed above it, which is the healthy direction.
40→37 registrations.interfaces.rest uses registrations.application.query✕
- Connections
- 2 pairs of types, where a type in registrations.interfaces.rest uses a type in registrations.application.query.
- The types involved
dev.sivalabs.meetup4j.registrations.interfaces.rest.EventRegistrationController→dev.sivalabs.meetup4j.registrations.application.query.RegistrationQueryServicedev.sivalabs.meetup4j.registrations.interfaces.rest.UserEventsController→dev.sivalabs.meetup4j.registrations.application.query.RegistrationQueryService
- Direction
- registrations.interfaces.rest uses registrations.application.query, so a change to registrations.application.query can break registrations.interfaces.rest, while a change to registrations.interfaces.rest can't break registrations.application.query.
- Position
- Below the diagonal: registrations.interfaces.rest uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 19 | High / Critical |
| A05:2025 — Injection | 9 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | Medium |
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with Meetup4jApplicationTests.java; Resolve the 1 No ADRs found finding(s) in ADR Quality.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with Meetup4jApplicationTests.java. | +3.8 pts | Low | Test Quality |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.6 pts | Low | ADR Quality |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +4.2 pts | Medium | Security & performance tooling |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.3 pts | Medium | Architecture documentation |
| 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. | +2.8 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.8 pts | Medium | Release Hygiene |
| Resolve the 1 No assertions finding(s) in Test Quality — start with ArchUnitTests.java. | +1.2 pts | Low | Test Quality |
| Add a README to the 5 of 5 project(s) that lack one — worth up to 2 pts. | +1.4 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/config/GlobalExceptionHandler.java | 7.1 | Mixed | Code Duplication: Members sharing a duplicated core (5 members, 50+ identical tokens) |
| meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/EventService.java | 7.1 | Mixed | Code Duplication: Duplicated block (18 lines × 3) |
| meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/EventRegistrationService.java | 7.1 | Mixed | Code Duplication: Duplicated block (12 lines × 3) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| meetup4j-layered/src/test/java/dev/sivalabs/meetup4j/Meetup4jApplicationTests.java | 8.0 | Near-clean | Test Quality: No assertions (empty test): contextLoads |
| meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/EventMapper.java | 8.5 | Near-clean | Code Duplication: Duplicated block (16 lines × 3) |
| meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/rest/EventsController.java | 8.5 | Near-clean | Code Duplication: Duplicated block (16 lines × 3) |
| meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/events/infra/persistence/EventViewMapper.java | 8.5 | Near-clean | Code Duplication: Duplicated block (16 lines × 2) |
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 70 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 70 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, 87 of 248 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java) 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 (JaCoCo XML — `mvn jacoco:report`) 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 (JaCoCo XML — `mvn jacoco:report`) 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 (.java) and this repository declares a JVM test suite (repository root, Maven), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — 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. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Maven tree, and its score reflects currency alone.
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Git history depth insufficient — this repository has 3 commit(s), too few for a reliable trend signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 3 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- 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: 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.
- D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (3 commit(s) sampled).
- D35 Change Coupling — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Git history depth insufficient — this repository has 3 commit(s), too few for a reliable change-coupling signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via ToolchainServer (meetup4j-layered). the service did not build — `mvn -B -q -DskipTests compile` exited -1: Tool stalled (no output) after 00:02:00.0059696.; runtime evidence skipped (launch chosen because REDACTED declares spring-boot-starter-web and the Spring Boot Maven plugin).
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — 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 authorization 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 authorization controls.
- C3 Audit Trail — 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 audit 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 audit controls.
- C4 Data Retention — 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 retention 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 retention controls.
- C5 Data-Subject Rights — 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 data-subject rights 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 data-subject rights controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm one resolves each comparison operand to the domain member it judges, and that binding exists only in a Roslyn compilation, which this run did not load. Arm two ran over the neutral model because this repository's frontend declares whether each construction is produced or passed. A rule decided in two places would not appear above.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java 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.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- 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.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
32 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with EventRegistrationService.java (3), RegistrationViewMapper.java, TSIDUtil.java. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with Event.java, EventRegistration.java, EventRegistrationEntity.java. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Members sharing a duplicated core (5 members, 50+ identical tokens) finding(s) in Code Duplication — start with GlobalExceptionHandler.java (2). — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
5 production modules (Maven), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
1 of 23 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with EventsController.java. — 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.
D9 · Test Distribution
42 test methods: 42 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 2 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 42 tests.
What to do
- Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with Meetup4jApplicationTests.java. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 No assertions finding(s) in Test Quality — start with ArchUnitTests.java. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D12 · Dependency Hygiene
155 outdated artifact(s) of 177 resolved by the build, graded against Maven Central. The poms themselves state a version for only 5 of 107 declaration(s) — the rest are parent- or BOM-managed, which is why this is read from the resolved graph rather than from the manifests. Whether any of these is DEPRECATED is not graded — Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Known CVEs in this graph are D30's question, read from the manifest there.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 1 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 6 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 102 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 6373 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
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
34 domain type(s) cross context boundaries across 3 contexts; they are measured and withheld (not published, not scored). Contexts: domain, events, registrations.
D26 · Project Cohesion
0 of 5 build units (Maven) flagged as possibly oversized/incoherent.
D27 · Navigability
41 % of calls cross a namespace and 9 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
9 finding(s): 0 critical, 7 high, 2 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `mvnw` (line 86, line 124, line 134, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
19 finding(s): 3 critical, 11 high, 3 medium, 2 low.
What to do
- Resolve the 10 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
5 finding(s): 0 critical, 0 high, 5 medium, 0 low.
What to do
- Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-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 6 platform declaration(s) and 13 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `EventRegistrationEntity`'s public constructor takes `attendeeName` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `EventRegistrationEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. (×2) — meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/EventRegistrationEntity.java:49, meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/infra/persistence/EventRegistrationEntity.java:49
- `EventRegistration`'s public constructor takes `attendeeName` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `EventRegistration` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/domain/model/EventRegistration.java:24
- `EventEntity`'s public constructor takes `registrationsCount` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `EventEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/events/infra/persistence/EventEntity.java:67
- `Event`'s public constructor takes `registrationsCount` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Event` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/events/domain/model/Event.java:26
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
- `EventRegistrationEntity` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/EventRegistrationEntity.java:16
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM7 · Repository granularity
- `RegistrationRepository` is a repository over `EventRegistrationEntity`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EventRegistrationEntity` through its owning aggregate instead. (×2) — meetup4j-package-by-feature/src/main/java/dev/sivalabs/meetup4j/registrations/domain/RegistrationRepository.java:11, meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/repositories/RegistrationRepository.java:12
- `JpaRegistrationRepository` is a repository over `EventRegistrationEntity`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EventRegistrationEntity` through its owning aggregate instead. — meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/infra/persistence/JpaRegistrationRepository.java:15
- `JpaEventRepository` is a repository over `EventEntity`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EventEntity` through its owning aggregate instead. — meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/events/infra/persistence/JpaEventRepository.java:14
What to do
- Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
DM9 · Scattered domain decisions
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a README to the 5 of 5 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (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 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P8 · Schema migrations
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
- 0/83 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
- Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 75% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96% | Exemplary | Strongest area. |
| Maturity | 65% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 59% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 83% | Checked 5 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 74% | Adequate — gated by DM7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit 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 audit 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.
- C4 Data Retention — Not assessed: these retention 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 retention 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.
- C5 Data-Subject Rights — Not assessed: these data-subject rights 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 data-subject rights 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.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 54 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the service did not build — `mvn -B -q -DskipTests compile` exited -1: Tool stalled (no output) after 00:02:00.0059696.; runtime evidence skipped (launch chosen because REDACTED declares spring-boot-starter-web and the Spring Boot Maven plugin) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization 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 authorization 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.
- D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- 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.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (4 event handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 4 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — Not applicable: the 1 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 — no outbound HTTP usage detected — no HTTP client call or construction in the JVM source (service entry point: meetup4j-package-by-feature/src/main/java/dev/sivalabs/meetup4j/Meetup4jApplication.java:7 (@SpringBootApplication))
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) 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 `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a REDACTED, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Java was read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 22 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No assertions (empty test): contextLoads meetup4j-layered/src/test/java/dev/sivalabs/meetup4j/Meetup4jApplicationTests.java:8
- REDACTED
Serious — 57 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/EventRegistrationService.java:68
- Duplicated block (9 lines × 2) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/infra/persistence/RegistrationViewMapper.java:10
- Duplicated block (9 lines × 2) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/shared/TSIDUtil.java:6
- Duplicated block (9 lines × 2) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/EventRegistrationService.java:34
- Duplicated block (9 lines × 2) meetup4j-modulith-simple/src/main/java/dev/sivalabs/meetup4j/registrations/domain/EventRegistrationService.java:32
- Constructible in an invalid state: EventRegistrationEntity meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/EventRegistrationEntity.java:49
- Constructible in an invalid state: EventRegistrationEntity meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/infra/persistence/EventRegistrationEntity.java:49
- Constructible in an invalid state: EventRegistration meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/domain/model/EventRegistration.java:24
- Constructible in an invalid state: EventEntity meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/events/infra/persistence/EventEntity.java:67
- Constructible in an invalid state: Event meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/events/domain/model/Event.java:26
- Repository for a non-root entity: RegistrationRepository → EventRegistrationEntity meetup4j-package-by-feature/src/main/java/dev/sivalabs/meetup4j/registrations/domain/RegistrationRepository.java:11
- Repository for a non-root entity: JpaRegistrationRepository → EventRegistrationEntity meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/infra/persistence/JpaRegistrationRepository.java:15
- Repository for a non-root entity: JpaEventRepository → EventEntity meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/events/infra/persistence/JpaEventRepository.java:14
- Repository for a non-root entity: RegistrationRepository → EventRegistrationEntity meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/repositories/RegistrationRepository.java:12
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (11 lines × 2) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/events/domain/model/Event.java:47
- Duplicated block (11 lines × 2) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/domain/model/EventRegistration.java:31
- Duplicated block (11 lines × 2) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/infra/persistence/EventRegistrationEntity.java:71
- REDACTED
- REDACTED
- Members sharing a duplicated core (5 members, 50+ identical tokens) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/config/GlobalExceptionHandler.java:34
- Members sharing a duplicated core (5 members, 50+ identical tokens) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/config/GlobalExceptionHandler.java:65
- Duplicated block (16 lines × 3) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/EventMapper.java:11
- Duplicated block (16 lines × 3) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/rest/EventsController.java:52
- Duplicated block (8 lines × 3) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/EventRegistrationService.java:89
- Duplicated block (8 lines × 3) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/EventService.java:88
- Duplicated block (5 lines × 3) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/rest/EventRegistrationController.java:29
- Duplicated block (5 lines × 3) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/EventService.java:116
- Duplicated block (5 lines × 2) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/registrations/application/command/RegisterAttendeeUseCase.java:30
- Duplicated block (5 lines × 2) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/EventRegistrationService.java:78
- Duplicated block (7 lines × 5) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/config/GlobalExceptionHandler.java:47
- Duplicated block (7 lines × 5) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/config/GlobalExceptionHandler.java:56
- No assertions: shouldVerifyHexagonalArchitecture meetup4j-modulith-ddd-ha/src/test/java/dev/sivalabs/meetup4j/ArchUnitTests.java:15
- REDACTED
- Duplicated block (18 lines × 3) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/EventService.java:53
- Duplicated block (16 lines × 2) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/events/infra/persistence/EventViewMapper.java:10
- Duplicated block (15 lines × 3) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/EventService.java:99
- Duplicated block (12 lines × 5) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/config/GlobalExceptionHandler.java:66
- Duplicated block (12 lines × 3) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/EventRegistrationService.java:53
- Duplicated block (11 lines × 3) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/EventService.java:74
- Duplicated block (10 lines × 5) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/config/GlobalExceptionHandler.java:35
- Duplicated block (6 lines × 3) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/rest/dto/CreateEventRequest.java:45
- Duplicated block (6 lines × 2) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/events/application/command/dto/CreateEventCmd.java:17
- Duplicated block (9 lines × 6) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/repositories/EventRepository.java:30
- Duplicated block (28 lines × 5) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/EventActivityListener.java:1
- Duplicated block (22 lines × 5) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/RegistrationEventListener.java:1
- Duplicated block (17 lines × 3) meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/domain/services/RegistrationMapper.java:1
- Duplicated block (20 lines × 2) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/events/application/EventsAPI.java:19
- Low cohesion: EventsController (LCOM4 4) meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/events/interfaces/rest/EventsController.java:24
- Anemic entity: EventRegistrationEntity meetup4j-modulith-tomato/src/main/java/dev/sivalabs/meetup4j/registrations/domain/EventRegistrationEntity.java:16
Minor — 14 finding(s)
- Duplicated predicate meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/events/domain/model/Event.java:84
- Duplicated predicate meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/config/GlobalExceptionHandler.java:81
- Duplicated predicate meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/events/application/command/dto/CreateEventCmd.java:16
- Duplicated predicate meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/rest/dto/CreateEventRequest.java:44
- Duplicated predicate meetup4j-modulith-ddd-ha/src/main/java/dev/sivalabs/meetup4j/events/application/command/dto/CreateEventCmd.java:19
- Duplicated predicate meetup4j-layered/src/main/java/dev/sivalabs/meetup4j/rest/dto/CreateEventRequest.java:47
- REDACTED
- REDACTED
- No ADRs found
- No ADRs
- No SAST
- No rollback/health safety
- No changelog
- Java packages are not null-marked everywhere
Minor — 155 finding(s)
- Outdated (compile -- module spring.boot.starter.webmvc [auto]): org.springframework.boot:spring-boot-starter-webmvc
- Outdated (compile -- module spring.boot.starter [auto]): org.springframework.boot:spring-boot-starter
- Outdated (compile -- module spring.boot.starter.logging [auto]): org.springframework.boot:spring-boot-starter-logging
- Outdated (compile -- module ch.qos.logback.classic): ch.qos.logback:logback-classic
- Outdated (compile -- module ch.qos.logback.core): ch.qos.logback:logback-core
- Outdated (compile -- module org.apache.logging.log4j.to.slf4j): org.apache.logging.log4j:log4j-to-slf4j
- Outdated (compile -- module org.apache.logging.log4j): org.apache.logging.log4j:log4j-api
- Outdated (compile -- module jul.to.slf4j): org.slf4j:jul-to-slf4j
- Outdated (compile -- module org.yaml.snakeyaml): org.yaml:snakeyaml
- Outdated (compile -- module spring.boot.starter.jackson [auto]): org.springframework.boot:spring-boot-starter-jackson
- Outdated (compile -- module spring.boot.jackson [auto]): org.springframework.boot:spring-boot-jackson
- Outdated (compile -- module spring.boot.starter.tomcat [auto]): org.springframework.boot:spring-boot-starter-tomcat
- Outdated (compile -- module spring.boot.starter.tomcat.runtime [auto]): org.springframework.boot:spring-boot-starter-tomcat-runtime
- Outdated (compile -- module org.apache.tomcat.embed.core): org.apache.tomcat.embed:tomcat-embed-core
- Outdated (compile -- module org.apache.tomcat.embed.websocket): org.apache.tomcat.embed:tomcat-embed-websocket
- Outdated (compile -- module spring.boot.tomcat [auto]): org.springframework.boot:spring-boot-tomcat
- Outdated (compile -- module spring.boot.http.converter [auto]): org.springframework.boot:spring-boot-http-converter
- Outdated (compile -- module spring.web [auto]): org.springframework:spring-web
- Outdated (compile -- module spring.beans [auto]): org.springframework:spring-beans
- Outdated (compile -- module spring.boot.webmvc [auto]): org.springframework.boot:spring-boot-webmvc
- Outdated (compile -- module spring.boot.servlet [auto]): org.springframework.boot:spring-boot-servlet
- Outdated (compile -- module spring.webmvc [auto]): org.springframework:spring-webmvc
- Outdated (compile -- module spring.aop [auto]): org.springframework:spring-aop
- Outdated (compile -- module spring.expression [auto]): org.springframework:spring-expression
- Outdated (compile -- module spring.boot.starter.validation [auto]): org.springframework.boot:spring-boot-starter-validation
- Outdated (compile -- module spring.boot.validation [auto]): org.springframework.boot:spring-boot-validation
- Outdated (compile -- module org.apache.tomcat.embed.el): org.apache.tomcat.embed:tomcat-embed-el
- Outdated (compile -- module org.hibernate.validator): org.hibernate.validator:hibernate-validator
- Outdated (compile -- module org.jboss.logging): org.jboss.logging:jboss-logging
- Outdated (compile -- module com.fasterxml.classmate): com.fasterxml:classmate
- Outdated (compile -- module spring.boot.starter.actuator [auto]): org.springframework.boot:spring-boot-starter-actuator
- Outdated (compile -- module spring.boot.starter.micrometer.metrics [auto]): org.springframework.boot:spring-boot-starter-micrometer-metrics
- Outdated (compile -- module spring.boot.micrometer.metrics [auto]): org.springframework.boot:spring-boot-micrometer-metrics
- Outdated (compile -- module spring.boot.micrometer.observation [auto]): org.springframework.boot:spring-boot-micrometer-observation
- Outdated (compile -- module spring.boot.actuator.autoconfigure [auto]): org.springframework.boot:spring-boot-actuator-autoconfigure
- Outdated (compile -- module spring.boot.actuator [auto]): org.springframework.boot:spring-boot-actuator
- Outdated (compile -- module spring.boot.health [auto]): org.springframework.boot:spring-boot-health
- Outdated (compile -- module micrometer.observation [auto]): io.micrometer:micrometer-observation
- Outdated (compile -- module org.jspecify): org.jspecify:jspecify
- Outdated (compile -- module micrometer.commons [auto]): io.micrometer:micrometer-commons
- Outdated (compile -- module micrometer.jakarta9 [auto]): io.micrometer:micrometer-jakarta9
- Outdated (compile -- module micrometer.core [auto]): io.micrometer:micrometer-core
- Outdated (compile -- module spring.boot.starter.data.jpa [auto]): org.springframework.boot:spring-boot-starter-data-jpa
- Outdated (compile -- module spring.boot.starter.jdbc [auto]): org.springframework.boot:spring-boot-starter-jdbc
- Outdated (compile -- module com.zaxxer.hikari): com.zaxxer:HikariCP
- Outdated (compile -- module spring.boot.data.jpa [auto]): org.springframework.boot:spring-boot-data-jpa
- Outdated (compile -- module spring.boot.data.commons [auto]): org.springframework.boot:spring-boot-data-commons
- Outdated (compile -- module spring.boot.persistence [auto]): org.springframework.boot:spring-boot-persistence
- Outdated (compile -- module spring.data.commons [auto]): org.springframework.data:spring-data-commons
- Outdated (compile -- module spring.boot.hibernate [auto]): org.springframework.boot:spring-boot-hibernate
- Outdated (compile -- module spring.boot.jpa [auto]): org.springframework.boot:spring-boot-jpa
- Outdated (compile -- module org.hibernate.orm.core [auto]): org.hibernate.orm:hibernate-core
- Outdated (runtime -- module org.hibernate.models [auto]): org.hibernate.models:hibernate-models
- Outdated (runtime -- module org.glassfish.jaxb.runtime): org.glassfish.jaxb:jaxb-runtime
- Outdated (runtime -- module org.glassfish.jaxb.core): org.glassfish.jaxb:jaxb-core
- Outdated (runtime -- module com.sun.xml.txw2): org.glassfish.jaxb:txw2
- Outdated (runtime -- module com.sun.istack.runtime): com.sun.istack:istack-commons-runtime
- Outdated (compile -- module spring.orm [auto]): org.springframework:spring-orm
- Outdated (compile -- module spring.data.jpa [auto]): org.springframework.data:spring-data-jpa
- Outdated (compile -- module spring.tx [auto]): org.springframework:spring-tx
- Outdated (compile -- module spring.aspects [auto]): org.springframework:spring-aspects
- Outdated (compile -- module org.aspectj.weaver [auto]): org.aspectj:aspectjweaver
- Outdated (compile -- module spring.boot.jdbc [auto]): org.springframework.boot:spring-boot-jdbc
- Outdated (compile -- module spring.boot.sql [auto]): org.springframework.boot:spring-boot-sql
- Outdated (compile -- module spring.boot.transaction [auto]): org.springframework.boot:spring-boot-transaction
- Outdated (compile -- module spring.jdbc [auto]): org.springframework:spring-jdbc
- Outdated (runtime -- module org.postgresql.jdbc [auto]): org.postgresql:postgresql
- Outdated (runtime -- module org.checkerframework.checker.qual): org.checkerframework:checker-qual
- Outdated (compile -- module spring.boot.starter.flyway [auto]): org.springframework.boot:spring-boot-starter-flyway
- Outdated (compile -- module spring.boot.flyway [auto]): org.springframework.boot:spring-boot-flyway
- Outdated (compile -- module flyway.database.postgresql (auto)): org.flywaydb:flyway-database-postgresql
- Outdated (compile -- module flyway.core (auto)): org.flywaydb:flyway-core
- Outdated (compile -- module com.fasterxml.jackson.databind): com.fasterxml.jackson.core:jackson-databind
- Outdated (compile -- module com.fasterxml.jackson.core): com.fasterxml.jackson.core:jackson-core
- Outdated (compile -- module io.hypersistence.utils.hibernate.type [auto]): io.hypersistence:hypersistence-utils-hibernate-71
- Outdated (compile -- module jakarta.xml.bind): jakarta.xml.bind:jakarta.xml.bind-api
- Outdated (runtime (optional) -- module spring.boot.devtools [auto]): org.springframework.boot:spring-boot-devtools
- Outdated (compile -- module spring.boot [auto]): org.springframework.boot:spring-boot
- Outdated (compile -- module spring.core [auto]): org.springframework:spring-core
- Outdated (compile -- module org.apache.commons.logging): commons-logging:commons-logging
- Outdated (compile -- module spring.context [auto]): org.springframework:spring-context
- Outdated (compile -- module spring.boot.autoconfigure [auto]): org.springframework.boot:spring-boot-autoconfigure
- Outdated (compile (optional) -- module spring.boot.configuration.processor [auto]): org.springframework.boot:spring-boot-configuration-processor
- Outdated (runtime (optional) -- module spring.boot.docker.compose [auto]): org.springframework.boot:spring-boot-docker-compose
- Outdated (compile -- module tools.jackson.databind): tools.jackson.core:jackson-databind
- Outdated (compile -- module com.fasterxml.jackson.annotation): com.fasterxml.jackson.core:jackson-annotations
- Outdated (compile -- module tools.jackson.core): tools.jackson.core:jackson-core
- Outdated (test -- module spring.boot.starter.webmvc.test [auto]): org.springframework.boot:spring-boot-starter-webmvc-test
- Outdated (test -- module spring.boot.starter.jackson.test [auto]): org.springframework.boot:spring-boot-starter-jackson-test
- Outdated (test -- module spring.boot.starter.test [auto]): org.springframework.boot:spring-boot-starter-test
- Outdated (test -- module spring.boot.test [auto]): org.springframework.boot:spring-boot-test
- Outdated (test -- module spring.boot.test.autoconfigure [auto]): org.springframework.boot:spring-boot-test-autoconfigure
- Outdated (test -- module json.path [auto]): com.jayway.jsonpath:json-path
- Outdated (test -- module json.smart (auto)): net.minidev:json-smart
- Outdated (test -- module accessors.smart (auto)): net.minidev:accessors-smart
- Outdated (test -- module org.objectweb.asm): org.ow2.asm:asm
- Outdated (test -- module org.assertj.core): org.assertj:assertj-core
- Outdated (runtime -- module net.bytebuddy): net.bytebuddy:byte-buddy
- Outdated (test -- module org.junit.jupiter): org.junit.jupiter:junit-jupiter
- Outdated (test -- module org.junit.jupiter.api): org.junit.jupiter:junit-jupiter-api
- Outdated (test -- module org.junit.platform.commons): org.junit.platform:junit-platform-commons
- Outdated (test -- module org.junit.jupiter.params): org.junit.jupiter:junit-jupiter-params
- Outdated (test -- module org.junit.jupiter.engine): org.junit.jupiter:junit-jupiter-engine
- Outdated (test -- module org.junit.platform.engine): org.junit.platform:junit-platform-engine
- Outdated (test -- module org.mockito): org.mockito:mockito-core
- Outdated (test -- module net.bytebuddy.agent): net.bytebuddy:byte-buddy-agent
- Outdated (test -- module org.objenesis [auto]): org.objenesis:objenesis
- Outdated (test -- module org.mockito.junit.jupiter): org.mockito:mockito-junit-jupiter
- Outdated (test -- module spring.test [auto]): org.springframework:spring-test
- Outdated (test -- module org.xmlunit [auto]): org.xmlunit:xmlunit-core
- Outdated (test -- module spring.boot.webmvc.test [auto]): org.springframework.boot:spring-boot-webmvc-test
- Outdated (compile -- module spring.boot.web.server [auto]): org.springframework.boot:spring-boot-web-server
- Outdated (test -- module spring.boot.resttestclient [auto]): org.springframework.boot:spring-boot-resttestclient
- Outdated (test -- module spring.boot.starter.validation.test [auto]): org.springframework.boot:spring-boot-starter-validation-test
- Outdated (test -- module spring.boot.starter.actuator.test [auto]): org.springframework.boot:spring-boot-starter-actuator-test
- Outdated (test -- module spring.boot.starter.micrometer.metrics.test [auto]): org.springframework.boot:spring-boot-starter-micrometer-metrics-test
- Outdated (test -- module spring.boot.micrometer.metrics.test [auto]): org.springframework.boot:spring-boot-micrometer-metrics-test
- Outdated (test -- module spring.boot.starter.data.jpa.test [auto]): org.springframework.boot:spring-boot-starter-data-jpa-test
- Outdated (test -- module spring.boot.starter.jdbc.test [auto]): org.springframework.boot:spring-boot-starter-jdbc-test
- Outdated (test -- module spring.boot.jdbc.test [auto]): org.springframework.boot:spring-boot-jdbc-test
- Outdated (test -- module spring.boot.data.jpa.test [auto]): org.springframework.boot:spring-boot-data-jpa-test
- Outdated (test -- module spring.boot.jpa.test [auto]): org.springframework.boot:spring-boot-jpa-test
- Outdated (test -- module spring.boot.starter.flyway.test [auto]): org.springframework.boot:spring-boot-starter-flyway-test
- Outdated (test -- module spring.boot.testcontainers [auto]): org.springframework.boot:spring-boot-testcontainers
- Outdated (test -- module testcontainers (auto)): org.testcontainers:testcontainers
- Outdated (compile -- module org.slf4j): org.slf4j:slf4j-api
- Outdated (test -- module org.apache.commons.codec): commons-codec:commons-codec
- Outdated (test -- module org.apache.commons.io): commons-io:commons-io
- Outdated (test -- module org.apache.commons.lang3): org.apache.commons:commons-lang3
- Outdated (test -- module org.jetbrains.annotations [auto]): org.jetbrains:annotations
- Outdated (test -- module com.github.dockerjava.api [auto]): com.github.docker-java:docker-java-api
- Outdated (test -- module com.github.dockerjava.transport.zerodep [auto]): com.github.docker-java:docker-java-transport-zerodep
- Outdated (test -- module com.github.dockerjava.transport [auto]): com.github.docker-java:docker-java-transport
- Outdated (test -- module com.sun.jna [auto]): net.java.dev.jna:jna
- Outdated (test -- module testcontainers.junit.jupiter (auto)): org.testcontainers:testcontainers-junit-jupiter
- Outdated (test -- module testcontainers.postgresql (auto)): org.testcontainers:testcontainers-postgresql
- Outdated (test -- module testcontainers.jdbc (auto)): org.testcontainers:testcontainers-jdbc
- Outdated (test -- module testcontainers.database.commons (auto)): org.testcontainers:testcontainers-database-commons
- Outdated (compile -- module spring.modulith.starter.core [auto]): org.springframework.modulith:spring-modulith-starter-core
- Outdated (compile -- module spring.modulith.api [auto]): org.springframework.modulith:spring-modulith-api
- Outdated (compile -- module spring.modulith.apt [auto]): org.springframework.modulith:spring-modulith-apt
- Outdated (runtime -- module spring.modulith.core [auto]): org.springframework.modulith:spring-modulith-core
- Outdated (runtime -- module com.tngtech.archunit [auto]): com.tngtech.archunit:archunit
- Outdated (compile -- module spring.modulith.moments [auto]): org.springframework.modulith:spring-modulith-moments
- Outdated (compile -- module spring.modulith.events.api [auto]): org.springframework.modulith:spring-modulith-events-api
- Outdated (compile -- module spring.modulith.starter.jdbc [auto]): org.springframework.modulith:spring-modulith-starter-jdbc
- Outdated (runtime -- module spring.modulith.events.core [auto]): org.springframework.modulith:spring-modulith-events-core
- Outdated (runtime -- module org.apache.commons.logging): org.slf4j:jcl-over-slf4j
- Outdated (runtime -- module spring.modulith.events.jackson [auto]): org.springframework.modulith:spring-modulith-events-jackson
- Outdated (runtime -- module spring.modulith.events.jdbc [auto]): org.springframework.modulith:spring-modulith-events-jdbc
- Outdated (test -- module spring.modulith.starter.test [auto]): org.springframework.modulith:spring-modulith-starter-test
- Outdated (test -- module spring.modulith.test [auto]): org.springframework.modulith:spring-modulith-test
- Outdated (test -- module spring.modulith.docs [auto]): org.springframework.modulith:spring-modulith-docs
- Outdated (test -- module structurizr.core (auto)): com.structurizr:structurizr-core
- Outdated (test -- module structurizr.export (auto)): com.structurizr:structurizr-export
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-ef5093402e4746d4a026a6c753e57757/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-ef5093402e4746d4a026a6c753e57757/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 . | 9 | 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 . | 19 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | 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 |