Executive summary
jitterted/ensembler is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because it has images with no text description. It scores 52 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 40, is the weakest lens and counts most in the score. The best first step is adding text alternatives, worth about 7 points. Making the tests check their results comes next, worth about 3 points. Raising Accessibility to 70 would lift the score to about 61.
Eight images have no description for people who can't see them. Seven known security holes in the packages the code depends on can be used by attackers, and fourteen form fields can't be read by a screen reader. Describing the images, updating the vulnerable packages and labelling the form fields would close these risks. Pinning each tool to an exact version would fix the two pipeline tools referenced by a changeable name, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The two tests that check nothing need to check the result they produce.
The product code is 4,521 lines, about €12,000 to rebuild.
If Accessibility rose from 40 to 70, the lowest score rated Strong, the score would rise from 52 to about 61.
New since the last survey: 15 findings
- Test Quality · Assertions commented out: template src/test/java/com/jitterted/mobreg/adapter/in/web/admin/ThymeleafTemplateTest.java
- Test Quality · No assertions (empty test): html src/test/java/com/jitterted/mobreg/adapter/in/web/member/MemberEndpointHtmlTest.java
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Visual & motion safety · Low contrast Tailwind colour pair (3.3:1) src/main/resources/static/index.html
- Visual & motion safety · Low contrast Tailwind colour pair (3.8:1) src/main/resources/templates/ensemble-detail.html
- Visual & motion safety · Low contrast Tailwind colour pair (3.8:1) src/main/resources/templates/ensemble-detail.html
- Visual & motion safety · Low contrast Tailwind colour pair (3.8:1) src/main/resources/templates/ensemble-timer.html
Fixed since the last survey: 1 finding
- Test Quality · No assertions: html src/test/java/com/jitterted/mobreg/adapter/in/web/member/MemberEndpointHtmlTest.java
Rebuild cost: about €12,000 · Estimate
| Cost to rebuild | €3,800 to €19,000, for 64 to 204 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 52. 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: 4,521 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 com.jitterted.mobreg.adapter | 2 com.jitterted.mobreg.adapter.out.membership | 3 com.jitterted.mobreg.domain | 4 org.springframework.security.web.header.writers.ClearSiteDataHeaderWriter | 5 src.main.resources.templates | 6 com.jitterted.mobreg.application | 7 com.jitterted.mobreg.application.port | 8 com.jitterted.mobreg.adapter.in.web | 9 com.jitterted.mobreg.adapter.out | 10 com.jitterted.mobreg.adapter.out.clock | 11 com.jitterted.mobreg.adapter.out.conductor | 12 com.jitterted.mobreg.adapter.out.email | 13 com.jitterted.mobreg.adapter.out.jdbc | 14 com.jitterted.mobreg.adapter.out.notification.pushover | 15 com.jitterted.mobreg.adapter.out.websocket | 16 com.jitterted.mobreg.adapter.out.zoom | 17 com.jitterted.mobreg | 18 com.jitterted.mobreg.adapter.in.web.admin | 19 com.jitterted.mobreg.adapter.in.web.member |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com.jitterted.mobreg.adapter | |||||||||||||||||||
| 2 com.jitterted.mobreg.adapter.out.membership | |||||||||||||||||||
| 3 com.jitterted.mobreg.domain | |||||||||||||||||||
| 4 org.springframework.security.web.header.writers.ClearSiteDataHeaderWriter | |||||||||||||||||||
| 5 src.main.resources.templates | |||||||||||||||||||
| 6 com.jitterted.mobreg.application | 16 | 12 | |||||||||||||||||
| 7 com.jitterted.mobreg.application.port | 17 | 1 | |||||||||||||||||
| 8 com.jitterted.mobreg.adapter.in.web | 1 | 1 | |||||||||||||||||
| 9 com.jitterted.mobreg.adapter.out | 2 | 1 | |||||||||||||||||
| 10 com.jitterted.mobreg.adapter.out.clock | 2 | 1 | 1 | ||||||||||||||||
| 11 com.jitterted.mobreg.adapter.out.conductor | 4 | 1 | |||||||||||||||||
| 12 com.jitterted.mobreg.adapter.out.email | 2 | 2 | 1 | ||||||||||||||||
| 13 com.jitterted.mobreg.adapter.out.jdbc | 9 | 3 | |||||||||||||||||
| 14 com.jitterted.mobreg.adapter.out.notification.pushover | 2 | 1 | |||||||||||||||||
| 15 com.jitterted.mobreg.adapter.out.websocket | 7 | 1 | |||||||||||||||||
| 16 com.jitterted.mobreg.adapter.out.zoom | 2 | 1 | |||||||||||||||||
| 17 com.jitterted.mobreg | 3 | 7 | 1 | 1 | |||||||||||||||
| 18 com.jitterted.mobreg.adapter.in.web.admin | 10 | 4 | 2 | 1 | |||||||||||||||
| 19 com.jitterted.mobreg.adapter.in.web.member | 12 | 9 | 2 | 1 |
6→3 com.jitterted.mobreg.application uses com.jitterted.mobreg.domain✕
- Connections
- 16 pairs of types, where a type in com.jitterted.mobreg.application uses a type in com.jitterted.mobreg.domain.
- The types involved
com.jitterted.mobreg.application.DefaultMemberService→com.jitterted.mobreg.domain.Membercom.jitterted.mobreg.application.DefaultMemberService→com.jitterted.mobreg.domain.MemberIdcom.jitterted.mobreg.application.DoNothingBroadcaster→com.jitterted.mobreg.domain.EnsembleTimercom.jitterted.mobreg.application.DoNothingBroadcaster→com.jitterted.mobreg.domain.TimerEventcom.jitterted.mobreg.application.DoNothingSecondsTicker→com.jitterted.mobreg.domain.EnsembleIdcom.jitterted.mobreg.application.EnsembleService→com.jitterted.mobreg.domain.Ensemblecom.jitterted.mobreg.application.EnsembleService→com.jitterted.mobreg.domain.EnsembleIdcom.jitterted.mobreg.application.EnsembleService→com.jitterted.mobreg.domain.MemberIdcom.jitterted.mobreg.application.EnsembleTimerHolder→com.jitterted.mobreg.domain.Ensemblecom.jitterted.mobreg.application.EnsembleTimerHolder→com.jitterted.mobreg.domain.EnsembleIdcom.jitterted.mobreg.application.EnsembleTimerHolder→com.jitterted.mobreg.domain.EnsembleTimercom.jitterted.mobreg.application.EnsembleTimerHolder→com.jitterted.mobreg.domain.Membercom.jitterted.mobreg.application.EnsembleTimerTickHandler→com.jitterted.mobreg.domain.EnsembleIdcom.jitterted.mobreg.application.GoogleCalendarLinkCreator→com.jitterted.mobreg.domain.Ensemblecom.jitterted.mobreg.application.MemberService→com.jitterted.mobreg.domain.Membercom.jitterted.mobreg.application.MemberService→com.jitterted.mobreg.domain.MemberId
- Direction
- com.jitterted.mobreg.application uses com.jitterted.mobreg.domain, so a change to com.jitterted.mobreg.domain can break com.jitterted.mobreg.application, while a change to com.jitterted.mobreg.application can't break com.jitterted.mobreg.domain.
- Position
- Below the diagonal: com.jitterted.mobreg.application uses a module listed above it, which is the healthy direction.
6→7 com.jitterted.mobreg.application uses com.jitterted.mobreg.application.port part of a loop✕
- Connections
- 12 pairs of types, where a type in com.jitterted.mobreg.application uses a type in com.jitterted.mobreg.application.port.
- The types involved
com.jitterted.mobreg.application.DefaultMemberService→com.jitterted.mobreg.application.port.MemberRepositorycom.jitterted.mobreg.application.DoNothingBroadcaster→com.jitterted.mobreg.application.port.Broadcastercom.jitterted.mobreg.application.DoNothingSecondsTicker→com.jitterted.mobreg.application.port.SecondsTickercom.jitterted.mobreg.application.EnsembleService→com.jitterted.mobreg.application.port.EnsembleRepositorycom.jitterted.mobreg.application.EnsembleService→com.jitterted.mobreg.application.port.MemberRepositorycom.jitterted.mobreg.application.EnsembleService→com.jitterted.mobreg.application.port.Notifiercom.jitterted.mobreg.application.EnsembleService→com.jitterted.mobreg.application.port.VideoConferenceSchedulercom.jitterted.mobreg.application.EnsembleTimerHolder→com.jitterted.mobreg.application.port.Broadcastercom.jitterted.mobreg.application.EnsembleTimerHolder→com.jitterted.mobreg.application.port.EnsembleRepositorycom.jitterted.mobreg.application.EnsembleTimerHolder→com.jitterted.mobreg.application.port.MemberRepositorycom.jitterted.mobreg.application.EnsembleTimerHolder→com.jitterted.mobreg.application.port.SecondsTickercom.jitterted.mobreg.application.EnsembleTimerHolder→com.jitterted.mobreg.application.port.Shuffler
- Direction
- com.jitterted.mobreg.application uses com.jitterted.mobreg.application.port, so a change to com.jitterted.mobreg.application.port can break com.jitterted.mobreg.application, while a change to com.jitterted.mobreg.application can't break com.jitterted.mobreg.application.port.
- 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.
7→3 com.jitterted.mobreg.application.port uses com.jitterted.mobreg.domain✕
- Connections
- 17 pairs of types, where a type in com.jitterted.mobreg.application.port uses a type in com.jitterted.mobreg.domain.
- The types involved
com.jitterted.mobreg.application.port.Broadcaster→com.jitterted.mobreg.domain.EnsembleTimercom.jitterted.mobreg.application.port.Broadcaster→com.jitterted.mobreg.domain.TimerEventcom.jitterted.mobreg.application.port.EnsembleRepository→com.jitterted.mobreg.domain.Ensemblecom.jitterted.mobreg.application.port.EnsembleRepository→com.jitterted.mobreg.domain.EnsembleIdcom.jitterted.mobreg.application.port.InMemoryEnsembleRepository→com.jitterted.mobreg.domain.Ensemblecom.jitterted.mobreg.application.port.InMemoryEnsembleRepository→com.jitterted.mobreg.domain.EnsembleIdcom.jitterted.mobreg.application.port.InMemoryMemberRepository→com.jitterted.mobreg.domain.Membercom.jitterted.mobreg.application.port.InMemoryMemberRepository→com.jitterted.mobreg.domain.MemberIdcom.jitterted.mobreg.application.port.InMemoryMemberRepository→com.jitterted.mobreg.domain.MemberSnapshotcom.jitterted.mobreg.application.port.MemberRepository→com.jitterted.mobreg.domain.Membercom.jitterted.mobreg.application.port.MemberRepository→com.jitterted.mobreg.domain.MemberIdcom.jitterted.mobreg.application.port.Notifier→com.jitterted.mobreg.domain.Ensemblecom.jitterted.mobreg.application.port.Notifier→com.jitterted.mobreg.domain.Membercom.jitterted.mobreg.application.port.SecondsTicker→com.jitterted.mobreg.domain.EnsembleIdcom.jitterted.mobreg.application.port.Shuffler→com.jitterted.mobreg.domain.Membercom.jitterted.mobreg.application.port.VideoConferenceScheduler→com.jitterted.mobreg.domain.ConferenceDetailscom.jitterted.mobreg.application.port.VideoConferenceScheduler→com.jitterted.mobreg.domain.Ensemble
- Direction
- com.jitterted.mobreg.application.port uses com.jitterted.mobreg.domain, so a change to com.jitterted.mobreg.domain can break com.jitterted.mobreg.application.port, while a change to com.jitterted.mobreg.application.port can't break com.jitterted.mobreg.domain.
- Position
- Below the diagonal: com.jitterted.mobreg.application.port uses a module listed above it, which is the healthy direction.
7→6 com.jitterted.mobreg.application.port uses com.jitterted.mobreg.application✕
- Connections
- 1 pair of types, where a type in com.jitterted.mobreg.application.port uses a type in com.jitterted.mobreg.application.
- The types involved
com.jitterted.mobreg.application.port.SecondsTicker→com.jitterted.mobreg.application.EnsembleTimerTickHandler
- Direction
- com.jitterted.mobreg.application.port uses com.jitterted.mobreg.application, so a change to com.jitterted.mobreg.application can break com.jitterted.mobreg.application.port, while a change to com.jitterted.mobreg.application.port can't break com.jitterted.mobreg.application.
- Position
- Below the diagonal: com.jitterted.mobreg.application.port uses a module listed above it, which is the healthy direction.
8→3 com.jitterted.mobreg.adapter.in.web uses com.jitterted.mobreg.domain✕
- Connections
- 1 pair of types, where a type in com.jitterted.mobreg.adapter.in.web uses a type in com.jitterted.mobreg.domain.
- The types involved
com.jitterted.mobreg.adapter.in.web.GitHubGrantedAuthoritiesMapper→com.jitterted.mobreg.domain.Member
- Direction
- com.jitterted.mobreg.adapter.in.web uses com.jitterted.mobreg.domain, so a change to com.jitterted.mobreg.domain can break com.jitterted.mobreg.adapter.in.web, while a change to com.jitterted.mobreg.adapter.in.web can't break com.jitterted.mobreg.domain.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.in.web uses a module listed above it, which is the healthy direction.
8→7 com.jitterted.mobreg.adapter.in.web uses com.jitterted.mobreg.application.port✕
- Connections
- 1 pair of types, where a type in com.jitterted.mobreg.adapter.in.web uses a type in com.jitterted.mobreg.application.port.
- The types involved
com.jitterted.mobreg.adapter.in.web.GitHubGrantedAuthoritiesMapper→com.jitterted.mobreg.application.port.MemberRepository
- Direction
- com.jitterted.mobreg.adapter.in.web uses com.jitterted.mobreg.application.port, so a change to com.jitterted.mobreg.application.port can break com.jitterted.mobreg.adapter.in.web, while a change to com.jitterted.mobreg.adapter.in.web can't break com.jitterted.mobreg.application.port.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.in.web uses a module listed above it, which is the healthy direction.
9→3 com.jitterted.mobreg.adapter.out uses com.jitterted.mobreg.domain✕
- Connections
- 2 pairs of types, where a type in com.jitterted.mobreg.adapter.out uses a type in com.jitterted.mobreg.domain.
- The types involved
com.jitterted.mobreg.adapter.out.CompositeBroadcaster→com.jitterted.mobreg.domain.EnsembleTimercom.jitterted.mobreg.adapter.out.CompositeBroadcaster→com.jitterted.mobreg.domain.TimerEvent
- Direction
- com.jitterted.mobreg.adapter.out uses com.jitterted.mobreg.domain, so a change to com.jitterted.mobreg.domain can break com.jitterted.mobreg.adapter.out, while a change to com.jitterted.mobreg.adapter.out can't break com.jitterted.mobreg.domain.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out uses a module listed above it, which is the healthy direction.
9→7 com.jitterted.mobreg.adapter.out uses com.jitterted.mobreg.application.port✕
- Connections
- 1 pair of types, where a type in com.jitterted.mobreg.adapter.out uses a type in com.jitterted.mobreg.application.port.
- The types involved
com.jitterted.mobreg.adapter.out.CompositeBroadcaster→com.jitterted.mobreg.application.port.Broadcaster
- Direction
- com.jitterted.mobreg.adapter.out uses com.jitterted.mobreg.application.port, so a change to com.jitterted.mobreg.application.port can break com.jitterted.mobreg.adapter.out, while a change to com.jitterted.mobreg.adapter.out can't break com.jitterted.mobreg.application.port.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out uses a module listed above it, which is the healthy direction.
10→3 com.jitterted.mobreg.adapter.out.clock uses com.jitterted.mobreg.domain✕
- Connections
- 2 pairs of types, where a type in com.jitterted.mobreg.adapter.out.clock uses a type in com.jitterted.mobreg.domain.
- The types involved
com.jitterted.mobreg.adapter.out.clock.ScheduledCountdown→com.jitterted.mobreg.domain.EnsembleIdcom.jitterted.mobreg.adapter.out.clock.ScheduledExecutorSecondsTicker→com.jitterted.mobreg.domain.EnsembleId
- Direction
- com.jitterted.mobreg.adapter.out.clock uses com.jitterted.mobreg.domain, so a change to com.jitterted.mobreg.domain can break com.jitterted.mobreg.adapter.out.clock, while a change to com.jitterted.mobreg.adapter.out.clock can't break com.jitterted.mobreg.domain.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out.clock uses a module listed above it, which is the healthy direction.
10→6 com.jitterted.mobreg.adapter.out.clock uses com.jitterted.mobreg.application✕
- Connections
- 1 pair of types, where a type in com.jitterted.mobreg.adapter.out.clock uses a type in com.jitterted.mobreg.application.
- The types involved
com.jitterted.mobreg.adapter.out.clock.ScheduledExecutorSecondsTicker→com.jitterted.mobreg.application.EnsembleTimerTickHandler
- Direction
- com.jitterted.mobreg.adapter.out.clock uses com.jitterted.mobreg.application, so a change to com.jitterted.mobreg.application can break com.jitterted.mobreg.adapter.out.clock, while a change to com.jitterted.mobreg.adapter.out.clock can't break com.jitterted.mobreg.application.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out.clock uses a module listed above it, which is the healthy direction.
10→7 com.jitterted.mobreg.adapter.out.clock uses com.jitterted.mobreg.application.port✕
- Connections
- 1 pair of types, where a type in com.jitterted.mobreg.adapter.out.clock uses a type in com.jitterted.mobreg.application.port.
- The types involved
com.jitterted.mobreg.adapter.out.clock.ScheduledExecutorSecondsTicker→com.jitterted.mobreg.application.port.SecondsTicker
- Direction
- com.jitterted.mobreg.adapter.out.clock uses com.jitterted.mobreg.application.port, so a change to com.jitterted.mobreg.application.port can break com.jitterted.mobreg.adapter.out.clock, while a change to com.jitterted.mobreg.adapter.out.clock can't break com.jitterted.mobreg.application.port.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out.clock uses a module listed above it, which is the healthy direction.
11→3 com.jitterted.mobreg.adapter.out.conductor uses com.jitterted.mobreg.domain✕
- Connections
- 4 pairs of types, where a type in com.jitterted.mobreg.adapter.out.conductor uses a type in com.jitterted.mobreg.domain.
- The types involved
com.jitterted.mobreg.adapter.out.conductor.ConductorHttpBroadcaster→com.jitterted.mobreg.domain.EnsembleTimercom.jitterted.mobreg.adapter.out.conductor.ConductorHttpBroadcaster→com.jitterted.mobreg.domain.TimerEventcom.jitterted.mobreg.adapter.out.conductor.SyncConductorTimerRequest→com.jitterted.mobreg.domain.EnsembleTimercom.jitterted.mobreg.adapter.out.conductor.SyncConductorTimerRequest→com.jitterted.mobreg.domain.TimerState
- Direction
- com.jitterted.mobreg.adapter.out.conductor uses com.jitterted.mobreg.domain, so a change to com.jitterted.mobreg.domain can break com.jitterted.mobreg.adapter.out.conductor, while a change to com.jitterted.mobreg.adapter.out.conductor can't break com.jitterted.mobreg.domain.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out.conductor uses a module listed above it, which is the healthy direction.
11→7 com.jitterted.mobreg.adapter.out.conductor uses com.jitterted.mobreg.application.port✕
- Connections
- 1 pair of types, where a type in com.jitterted.mobreg.adapter.out.conductor uses a type in com.jitterted.mobreg.application.port.
- The types involved
com.jitterted.mobreg.adapter.out.conductor.ConductorHttpBroadcaster→com.jitterted.mobreg.application.port.Broadcaster
- Direction
- com.jitterted.mobreg.adapter.out.conductor uses com.jitterted.mobreg.application.port, so a change to com.jitterted.mobreg.application.port can break com.jitterted.mobreg.adapter.out.conductor, while a change to com.jitterted.mobreg.adapter.out.conductor can't break com.jitterted.mobreg.application.port.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out.conductor uses a module listed above it, which is the healthy direction.
12→3 com.jitterted.mobreg.adapter.out.email uses com.jitterted.mobreg.domain✕
- Connections
- 2 pairs of types, where a type in com.jitterted.mobreg.adapter.out.email uses a type in com.jitterted.mobreg.domain.
- The types involved
com.jitterted.mobreg.adapter.out.email.EmailNotifier→com.jitterted.mobreg.domain.Ensemblecom.jitterted.mobreg.adapter.out.email.EmailNotifier→com.jitterted.mobreg.domain.Member
- Direction
- com.jitterted.mobreg.adapter.out.email uses com.jitterted.mobreg.domain, so a change to com.jitterted.mobreg.domain can break com.jitterted.mobreg.adapter.out.email, while a change to com.jitterted.mobreg.adapter.out.email can't break com.jitterted.mobreg.domain.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out.email uses a module listed above it, which is the healthy direction.
12→6 com.jitterted.mobreg.adapter.out.email uses com.jitterted.mobreg.application✕
- Connections
- 2 pairs of types, where a type in com.jitterted.mobreg.adapter.out.email uses a type in com.jitterted.mobreg.application.
- The types involved
com.jitterted.mobreg.adapter.out.email.EmailNotifier→com.jitterted.mobreg.application.GoogleCalendarLinkCreatorcom.jitterted.mobreg.adapter.out.email.EmailNotifier→com.jitterted.mobreg.application.MemberService
- Direction
- com.jitterted.mobreg.adapter.out.email uses com.jitterted.mobreg.application, so a change to com.jitterted.mobreg.application can break com.jitterted.mobreg.adapter.out.email, while a change to com.jitterted.mobreg.adapter.out.email can't break com.jitterted.mobreg.application.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out.email uses a module listed above it, which is the healthy direction.
12→7 com.jitterted.mobreg.adapter.out.email uses com.jitterted.mobreg.application.port✕
- Connections
- 1 pair of types, where a type in com.jitterted.mobreg.adapter.out.email uses a type in com.jitterted.mobreg.application.port.
- The types involved
com.jitterted.mobreg.adapter.out.email.EmailNotifier→com.jitterted.mobreg.application.port.Notifier
- Direction
- com.jitterted.mobreg.adapter.out.email uses com.jitterted.mobreg.application.port, so a change to com.jitterted.mobreg.application.port can break com.jitterted.mobreg.adapter.out.email, while a change to com.jitterted.mobreg.adapter.out.email can't break com.jitterted.mobreg.application.port.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out.email uses a module listed above it, which is the healthy direction.
13→3 com.jitterted.mobreg.adapter.out.jdbc uses com.jitterted.mobreg.domain✕
- Connections
- 9 pairs of types, where a type in com.jitterted.mobreg.adapter.out.jdbc uses a type in com.jitterted.mobreg.domain.
- The types involved
com.jitterted.mobreg.adapter.out.jdbc.AcceptedMember→com.jitterted.mobreg.domain.MemberIdcom.jitterted.mobreg.adapter.out.jdbc.DeclinedMember→com.jitterted.mobreg.domain.MemberIdcom.jitterted.mobreg.adapter.out.jdbc.EnsembleDbo→com.jitterted.mobreg.domain.Ensemblecom.jitterted.mobreg.adapter.out.jdbc.EnsembleRepositoryDataJdbcAdapter→com.jitterted.mobreg.domain.Ensemblecom.jitterted.mobreg.adapter.out.jdbc.EnsembleRepositoryDataJdbcAdapter→com.jitterted.mobreg.domain.EnsembleIdcom.jitterted.mobreg.adapter.out.jdbc.MemberDbo→com.jitterted.mobreg.domain.Membercom.jitterted.mobreg.adapter.out.jdbc.MemberRepositoryDataJdbcAdapter→com.jitterted.mobreg.domain.Membercom.jitterted.mobreg.adapter.out.jdbc.MemberRepositoryDataJdbcAdapter→com.jitterted.mobreg.domain.MemberIdcom.jitterted.mobreg.adapter.out.jdbc.SpectatorMember→com.jitterted.mobreg.domain.MemberId
- Direction
- com.jitterted.mobreg.adapter.out.jdbc uses com.jitterted.mobreg.domain, so a change to com.jitterted.mobreg.domain can break com.jitterted.mobreg.adapter.out.jdbc, while a change to com.jitterted.mobreg.adapter.out.jdbc can't break com.jitterted.mobreg.domain.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out.jdbc uses a module listed above it, which is the healthy direction.
13→7 com.jitterted.mobreg.adapter.out.jdbc uses com.jitterted.mobreg.application.port✕
- Connections
- 3 pairs of types, where a type in com.jitterted.mobreg.adapter.out.jdbc uses a type in com.jitterted.mobreg.application.port.
- The types involved
com.jitterted.mobreg.adapter.out.jdbc.EnsembleRepositoryDataJdbcAdapter→com.jitterted.mobreg.application.port.EnsembleRepositorycom.jitterted.mobreg.adapter.out.jdbc.InviteJdbcRepository→com.jitterted.mobreg.application.port.InviteRepositorycom.jitterted.mobreg.adapter.out.jdbc.MemberRepositoryDataJdbcAdapter→com.jitterted.mobreg.application.port.MemberRepository
- Direction
- com.jitterted.mobreg.adapter.out.jdbc uses com.jitterted.mobreg.application.port, so a change to com.jitterted.mobreg.application.port can break com.jitterted.mobreg.adapter.out.jdbc, while a change to com.jitterted.mobreg.adapter.out.jdbc can't break com.jitterted.mobreg.application.port.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out.jdbc uses a module listed above it, which is the healthy direction.
14→3 com.jitterted.mobreg.adapter.out.notification.pushover uses com.jitterted.mobreg.domain✕
- Connections
- 2 pairs of types, where a type in com.jitterted.mobreg.adapter.out.notification.pushover uses a type in com.jitterted.mobreg.domain.
- The types involved
com.jitterted.mobreg.adapter.out.notification.pushover.PushoverNotifier→com.jitterted.mobreg.domain.Ensemblecom.jitterted.mobreg.adapter.out.notification.pushover.PushoverNotifier→com.jitterted.mobreg.domain.Member
- Direction
- com.jitterted.mobreg.adapter.out.notification.pushover uses com.jitterted.mobreg.domain, so a change to com.jitterted.mobreg.domain can break com.jitterted.mobreg.adapter.out.notification.pushover, while a change to com.jitterted.mobreg.adapter.out.notification.pushover can't break com.jitterted.mobreg.domain.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out.notification.pushover uses a module listed above it, which is the healthy direction.
14→7 com.jitterted.mobreg.adapter.out.notification.pushover uses com.jitterted.mobreg.application.port✕
- Connections
- 1 pair of types, where a type in com.jitterted.mobreg.adapter.out.notification.pushover uses a type in com.jitterted.mobreg.application.port.
- The types involved
com.jitterted.mobreg.adapter.out.notification.pushover.PushoverNotifier→com.jitterted.mobreg.application.port.Notifier
- Direction
- com.jitterted.mobreg.adapter.out.notification.pushover uses com.jitterted.mobreg.application.port, so a change to com.jitterted.mobreg.application.port can break com.jitterted.mobreg.adapter.out.notification.pushover, while a change to com.jitterted.mobreg.adapter.out.notification.pushover can't break com.jitterted.mobreg.application.port.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out.notification.pushover uses a module listed above it, which is the healthy direction.
15→3 com.jitterted.mobreg.adapter.out.websocket uses com.jitterted.mobreg.domain✕
- Connections
- 7 pairs of types, where a type in com.jitterted.mobreg.adapter.out.websocket uses a type in com.jitterted.mobreg.domain.
- The types involved
com.jitterted.mobreg.adapter.out.websocket.EventToHtmlTransformer→com.jitterted.mobreg.domain.TimerEventcom.jitterted.mobreg.adapter.out.websocket.TimerToHtmlTransformer→com.jitterted.mobreg.domain.EnsembleTimercom.jitterted.mobreg.adapter.out.websocket.TimerToHtmlTransformer→com.jitterted.mobreg.domain.Membercom.jitterted.mobreg.adapter.out.websocket.TimerToHtmlTransformer→com.jitterted.mobreg.domain.Rotationcom.jitterted.mobreg.adapter.out.websocket.TimerToHtmlTransformer→com.jitterted.mobreg.domain.TimeRemainingcom.jitterted.mobreg.adapter.out.websocket.WebSocketBroadcaster→com.jitterted.mobreg.domain.EnsembleTimercom.jitterted.mobreg.adapter.out.websocket.WebSocketBroadcaster→com.jitterted.mobreg.domain.TimerEvent
- Direction
- com.jitterted.mobreg.adapter.out.websocket uses com.jitterted.mobreg.domain, so a change to com.jitterted.mobreg.domain can break com.jitterted.mobreg.adapter.out.websocket, while a change to com.jitterted.mobreg.adapter.out.websocket can't break com.jitterted.mobreg.domain.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out.websocket uses a module listed above it, which is the healthy direction.
15→7 com.jitterted.mobreg.adapter.out.websocket uses com.jitterted.mobreg.application.port✕
- Connections
- 1 pair of types, where a type in com.jitterted.mobreg.adapter.out.websocket uses a type in com.jitterted.mobreg.application.port.
- The types involved
com.jitterted.mobreg.adapter.out.websocket.WebSocketBroadcaster→com.jitterted.mobreg.application.port.Broadcaster
- Direction
- com.jitterted.mobreg.adapter.out.websocket uses com.jitterted.mobreg.application.port, so a change to com.jitterted.mobreg.application.port can break com.jitterted.mobreg.adapter.out.websocket, while a change to com.jitterted.mobreg.adapter.out.websocket can't break com.jitterted.mobreg.application.port.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out.websocket uses a module listed above it, which is the healthy direction.
16→3 com.jitterted.mobreg.adapter.out.zoom uses com.jitterted.mobreg.domain✕
- Connections
- 2 pairs of types, where a type in com.jitterted.mobreg.adapter.out.zoom uses a type in com.jitterted.mobreg.domain.
- The types involved
com.jitterted.mobreg.adapter.out.zoom.ZoomScheduler→com.jitterted.mobreg.domain.ConferenceDetailscom.jitterted.mobreg.adapter.out.zoom.ZoomScheduler→com.jitterted.mobreg.domain.Ensemble
- Direction
- com.jitterted.mobreg.adapter.out.zoom uses com.jitterted.mobreg.domain, so a change to com.jitterted.mobreg.domain can break com.jitterted.mobreg.adapter.out.zoom, while a change to com.jitterted.mobreg.adapter.out.zoom can't break com.jitterted.mobreg.domain.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out.zoom uses a module listed above it, which is the healthy direction.
16→7 com.jitterted.mobreg.adapter.out.zoom uses com.jitterted.mobreg.application.port✕
- Connections
- 1 pair of types, where a type in com.jitterted.mobreg.adapter.out.zoom uses a type in com.jitterted.mobreg.application.port.
- The types involved
com.jitterted.mobreg.adapter.out.zoom.ZoomScheduler→com.jitterted.mobreg.application.port.VideoConferenceScheduler
- Direction
- com.jitterted.mobreg.adapter.out.zoom uses com.jitterted.mobreg.application.port, so a change to com.jitterted.mobreg.application.port can break com.jitterted.mobreg.adapter.out.zoom, while a change to com.jitterted.mobreg.adapter.out.zoom can't break com.jitterted.mobreg.application.port.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.out.zoom uses a module listed above it, which is the healthy direction.
17→6 com.jitterted.mobreg uses com.jitterted.mobreg.application✕
- Connections
- 3 pairs of types, where a type in com.jitterted.mobreg uses a type in com.jitterted.mobreg.application.
- The types involved
com.jitterted.mobreg.EnsemblerConfiguration→com.jitterted.mobreg.application.EnsembleServicecom.jitterted.mobreg.EnsemblerConfiguration→com.jitterted.mobreg.application.EnsembleTimerHoldercom.jitterted.mobreg.EnsemblerConfiguration→com.jitterted.mobreg.application.MemberService
- Direction
- com.jitterted.mobreg uses com.jitterted.mobreg.application, so a change to com.jitterted.mobreg.application can break com.jitterted.mobreg, while a change to com.jitterted.mobreg can't break com.jitterted.mobreg.application.
- Position
- Below the diagonal: com.jitterted.mobreg uses a module listed above it, which is the healthy direction.
17→7 com.jitterted.mobreg uses com.jitterted.mobreg.application.port✕
- Connections
- 7 pairs of types, where a type in com.jitterted.mobreg uses a type in com.jitterted.mobreg.application.port.
- The types involved
com.jitterted.mobreg.EnsemblerApplication→com.jitterted.mobreg.application.port.EnsembleRepositorycom.jitterted.mobreg.EnsemblerApplication→com.jitterted.mobreg.application.port.MemberRepositorycom.jitterted.mobreg.EnsemblerConfiguration→com.jitterted.mobreg.application.port.Broadcastercom.jitterted.mobreg.EnsemblerConfiguration→com.jitterted.mobreg.application.port.EnsembleRepositorycom.jitterted.mobreg.EnsemblerConfiguration→com.jitterted.mobreg.application.port.MemberRepositorycom.jitterted.mobreg.EnsemblerConfiguration→com.jitterted.mobreg.application.port.Notifiercom.jitterted.mobreg.EnsemblerConfiguration→com.jitterted.mobreg.application.port.VideoConferenceScheduler
- Direction
- com.jitterted.mobreg uses com.jitterted.mobreg.application.port, so a change to com.jitterted.mobreg.application.port can break com.jitterted.mobreg, while a change to com.jitterted.mobreg can't break com.jitterted.mobreg.application.port.
- Position
- Below the diagonal: com.jitterted.mobreg uses a module listed above it, which is the healthy direction.
17→13 com.jitterted.mobreg uses com.jitterted.mobreg.adapter.out.jdbc✕
- Connections
- 1 pair of types, where a type in com.jitterted.mobreg uses a type in com.jitterted.mobreg.adapter.out.jdbc.
- The types involved
com.jitterted.mobreg.EnsemblerConfiguration→com.jitterted.mobreg.adapter.out.jdbc.EnsembleJdbcRepository
- Direction
- com.jitterted.mobreg uses com.jitterted.mobreg.adapter.out.jdbc, so a change to com.jitterted.mobreg.adapter.out.jdbc can break com.jitterted.mobreg, while a change to com.jitterted.mobreg can't break com.jitterted.mobreg.adapter.out.jdbc.
- Position
- Below the diagonal: com.jitterted.mobreg uses a module listed above it, which is the healthy direction.
17→15 com.jitterted.mobreg uses com.jitterted.mobreg.adapter.out.websocket✕
- Connections
- 1 pair of types, where a type in com.jitterted.mobreg uses a type in com.jitterted.mobreg.adapter.out.websocket.
- The types involved
com.jitterted.mobreg.WebSocketConfiguration→com.jitterted.mobreg.adapter.out.websocket.WebSocketBroadcaster
- Direction
- com.jitterted.mobreg uses com.jitterted.mobreg.adapter.out.websocket, so a change to com.jitterted.mobreg.adapter.out.websocket can break com.jitterted.mobreg, while a change to com.jitterted.mobreg can't break com.jitterted.mobreg.adapter.out.websocket.
- Position
- Below the diagonal: com.jitterted.mobreg uses a module listed above it, which is the healthy direction.
18→3 com.jitterted.mobreg.adapter.in.web.admin uses com.jitterted.mobreg.domain✕
- Connections
- 10 pairs of types, where a type in com.jitterted.mobreg.adapter.in.web.admin uses a type in com.jitterted.mobreg.domain.
- The types involved
com.jitterted.mobreg.adapter.in.web.admin.AdminDashboardController→com.jitterted.mobreg.domain.EnsembleIdcom.jitterted.mobreg.adapter.in.web.admin.AdminRegistrationForm→com.jitterted.mobreg.domain.EnsembleIdcom.jitterted.mobreg.adapter.in.web.admin.EnsembleDetailView→com.jitterted.mobreg.domain.Ensemblecom.jitterted.mobreg.adapter.in.web.admin.EnsembleDetailView→com.jitterted.mobreg.domain.MemberIdcom.jitterted.mobreg.adapter.in.web.admin.EnsembleSummaryView→com.jitterted.mobreg.domain.Ensemblecom.jitterted.mobreg.adapter.in.web.admin.EnsembleTimerLifecycleController→com.jitterted.mobreg.domain.EnsembleTimercom.jitterted.mobreg.adapter.in.web.admin.MemberView→com.jitterted.mobreg.domain.Membercom.jitterted.mobreg.adapter.in.web.admin.ParticipantsTransformer→com.jitterted.mobreg.domain.EnsembleTimercom.jitterted.mobreg.adapter.in.web.admin.RandomShuffler→com.jitterted.mobreg.domain.Membercom.jitterted.mobreg.adapter.in.web.admin.ScheduleEnsembleForm→com.jitterted.mobreg.domain.Ensemble
- Direction
- com.jitterted.mobreg.adapter.in.web.admin uses com.jitterted.mobreg.domain, so a change to com.jitterted.mobreg.domain can break com.jitterted.mobreg.adapter.in.web.admin, while a change to com.jitterted.mobreg.adapter.in.web.admin can't break com.jitterted.mobreg.domain.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.in.web.admin uses a module listed above it, which is the healthy direction.
18→6 com.jitterted.mobreg.adapter.in.web.admin uses com.jitterted.mobreg.application✕
- Connections
- 4 pairs of types, where a type in com.jitterted.mobreg.adapter.in.web.admin uses a type in com.jitterted.mobreg.application.
- The types involved
com.jitterted.mobreg.adapter.in.web.admin.AdminDashboardController→com.jitterted.mobreg.application.EnsembleServicecom.jitterted.mobreg.adapter.in.web.admin.AdminDashboardController→com.jitterted.mobreg.application.MemberServicecom.jitterted.mobreg.adapter.in.web.admin.EnsembleDetailView→com.jitterted.mobreg.application.MemberServicecom.jitterted.mobreg.adapter.in.web.admin.EnsembleTimerLifecycleController→com.jitterted.mobreg.application.EnsembleTimerHolder
- Direction
- com.jitterted.mobreg.adapter.in.web.admin uses com.jitterted.mobreg.application, so a change to com.jitterted.mobreg.application can break com.jitterted.mobreg.adapter.in.web.admin, while a change to com.jitterted.mobreg.adapter.in.web.admin can't break com.jitterted.mobreg.application.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.in.web.admin uses a module listed above it, which is the healthy direction.
18→7 com.jitterted.mobreg.adapter.in.web.admin uses com.jitterted.mobreg.application.port✕
- Connections
- 2 pairs of types, where a type in com.jitterted.mobreg.adapter.in.web.admin uses a type in com.jitterted.mobreg.application.port.
- The types involved
com.jitterted.mobreg.adapter.in.web.admin.MemberManagementController→com.jitterted.mobreg.application.port.MemberRepositorycom.jitterted.mobreg.adapter.in.web.admin.RandomShuffler→com.jitterted.mobreg.application.port.Shuffler
- Direction
- com.jitterted.mobreg.adapter.in.web.admin uses com.jitterted.mobreg.application.port, so a change to com.jitterted.mobreg.application.port can break com.jitterted.mobreg.adapter.in.web.admin, while a change to com.jitterted.mobreg.adapter.in.web.admin can't break com.jitterted.mobreg.application.port.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.in.web.admin uses a module listed above it, which is the healthy direction.
18→13 com.jitterted.mobreg.adapter.in.web.admin uses com.jitterted.mobreg.adapter.out.jdbc✕
- Connections
- 1 pair of types, where a type in com.jitterted.mobreg.adapter.in.web.admin uses a type in com.jitterted.mobreg.adapter.out.jdbc.
- The types involved
com.jitterted.mobreg.adapter.in.web.admin.InviteEditor→com.jitterted.mobreg.adapter.out.jdbc.InviteJdbcRepository
- Direction
- com.jitterted.mobreg.adapter.in.web.admin uses com.jitterted.mobreg.adapter.out.jdbc, so a change to com.jitterted.mobreg.adapter.out.jdbc can break com.jitterted.mobreg.adapter.in.web.admin, while a change to com.jitterted.mobreg.adapter.in.web.admin can't break com.jitterted.mobreg.adapter.out.jdbc.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.in.web.admin uses a module listed above it, which is the healthy direction.
19→3 com.jitterted.mobreg.adapter.in.web.member uses com.jitterted.mobreg.domain✕
- Connections
- 12 pairs of types, where a type in com.jitterted.mobreg.adapter.in.web.member uses a type in com.jitterted.mobreg.domain.
- The types involved
com.jitterted.mobreg.adapter.in.web.member.EnsembleSortOrder→com.jitterted.mobreg.domain.Ensemblecom.jitterted.mobreg.adapter.in.web.member.EnsembleSummaryView→com.jitterted.mobreg.domain.Ensemblecom.jitterted.mobreg.adapter.in.web.member.EnsembleSummaryView→com.jitterted.mobreg.domain.MemberIdcom.jitterted.mobreg.adapter.in.web.member.EnsembleSummaryView→com.jitterted.mobreg.domain.MemberStatuscom.jitterted.mobreg.adapter.in.web.member.InProgressEnsembleView→com.jitterted.mobreg.domain.Ensemblecom.jitterted.mobreg.adapter.in.web.member.InProgressEnsembleView→com.jitterted.mobreg.domain.MemberIdcom.jitterted.mobreg.adapter.in.web.member.MemberController→com.jitterted.mobreg.domain.Membercom.jitterted.mobreg.adapter.in.web.member.MemberController→com.jitterted.mobreg.domain.MemberIdcom.jitterted.mobreg.adapter.in.web.member.MemberLookup→com.jitterted.mobreg.domain.Membercom.jitterted.mobreg.adapter.in.web.member.MemberProfileForm→com.jitterted.mobreg.domain.Membercom.jitterted.mobreg.adapter.in.web.member.ParticipantAction→com.jitterted.mobreg.domain.MemberStatuscom.jitterted.mobreg.adapter.in.web.member.SpectatorAction→com.jitterted.mobreg.domain.MemberStatus
- Direction
- com.jitterted.mobreg.adapter.in.web.member uses com.jitterted.mobreg.domain, so a change to com.jitterted.mobreg.domain can break com.jitterted.mobreg.adapter.in.web.member, while a change to com.jitterted.mobreg.adapter.in.web.member can't break com.jitterted.mobreg.domain.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.in.web.member uses a module listed above it, which is the healthy direction.
19→6 com.jitterted.mobreg.adapter.in.web.member uses com.jitterted.mobreg.application✕
- Connections
- 9 pairs of types, where a type in com.jitterted.mobreg.adapter.in.web.member uses a type in com.jitterted.mobreg.application.
- The types involved
com.jitterted.mobreg.adapter.in.web.member.EnsembleSummaryView→com.jitterted.mobreg.application.MemberServicecom.jitterted.mobreg.adapter.in.web.member.EnsembleTimerController→com.jitterted.mobreg.application.EnsembleTimerHoldercom.jitterted.mobreg.adapter.in.web.member.InProgressEnsembleView→com.jitterted.mobreg.application.EnsembleTimerHoldercom.jitterted.mobreg.adapter.in.web.member.InProgressEnsembleView→com.jitterted.mobreg.application.MemberServicecom.jitterted.mobreg.adapter.in.web.member.MemberController→com.jitterted.mobreg.application.EnsembleServicecom.jitterted.mobreg.adapter.in.web.member.MemberController→com.jitterted.mobreg.application.EnsembleTimerHoldercom.jitterted.mobreg.adapter.in.web.member.MemberController→com.jitterted.mobreg.application.MemberServicecom.jitterted.mobreg.adapter.in.web.member.MemberLookup→com.jitterted.mobreg.application.MemberServicecom.jitterted.mobreg.adapter.in.web.member.MemberProfileController→com.jitterted.mobreg.application.MemberService
- Direction
- com.jitterted.mobreg.adapter.in.web.member uses com.jitterted.mobreg.application, so a change to com.jitterted.mobreg.application can break com.jitterted.mobreg.adapter.in.web.member, while a change to com.jitterted.mobreg.adapter.in.web.member can't break com.jitterted.mobreg.application.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.in.web.member uses a module listed above it, which is the healthy direction.
19→7 com.jitterted.mobreg.adapter.in.web.member uses com.jitterted.mobreg.application.port✕
- Connections
- 2 pairs of types, where a type in com.jitterted.mobreg.adapter.in.web.member uses a type in com.jitterted.mobreg.application.port.
- The types involved
com.jitterted.mobreg.adapter.in.web.member.InviteProcessController→com.jitterted.mobreg.application.port.InviteRepositorycom.jitterted.mobreg.adapter.in.web.member.InviteProcessController→com.jitterted.mobreg.application.port.MemberRepository
- Direction
- com.jitterted.mobreg.adapter.in.web.member uses com.jitterted.mobreg.application.port, so a change to com.jitterted.mobreg.application.port can break com.jitterted.mobreg.adapter.in.web.member, while a change to com.jitterted.mobreg.adapter.in.web.member can't break com.jitterted.mobreg.application.port.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.in.web.member uses a module listed above it, which is the healthy direction.
19→18 com.jitterted.mobreg.adapter.in.web.member uses com.jitterted.mobreg.adapter.in.web.admin✕
- Connections
- 1 pair of types, where a type in com.jitterted.mobreg.adapter.in.web.member uses a type in com.jitterted.mobreg.adapter.in.web.admin.
- The types involved
com.jitterted.mobreg.adapter.in.web.member.EnsembleSummaryView→com.jitterted.mobreg.adapter.in.web.admin.MemberView
- Direction
- com.jitterted.mobreg.adapter.in.web.member uses com.jitterted.mobreg.adapter.in.web.admin, so a change to com.jitterted.mobreg.adapter.in.web.admin can break com.jitterted.mobreg.adapter.in.web.member, while a change to com.jitterted.mobreg.adapter.in.web.member can't break com.jitterted.mobreg.adapter.in.web.admin.
- Position
- Below the diagonal: com.jitterted.mobreg.adapter.in.web.member uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 9 | High / Critical |
| A05:2025 — Injection | 4 | High / Critical |
| A02:2025 — Security Misconfiguration | 3 | Medium |
| A01:2025 — Broken Access Control | 1 | Medium |
Roadmap
Top priorities: Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video; Resolve the 52 No assertions finding(s) in Test Quality — start with EnsembleTimerHolderTest.java (14), AdminEndpointConfigurationTest.java (7), EnsembleTimerControllerMvcTest.java (6); Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +6.6 pts | Medium | Text alternatives |
| Resolve the 1 Assertions commented out finding(s) in Test Quality — start with ThymeleafTemplateTest.java. | +2.5 pts | Low | Test Quality |
| Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with MemberEndpointHtmlTest.java. | +2.5 pts | Low | Test Quality |
| Resolve the 52 No assertions finding(s) in Test Quality — start with EnsembleTimerHolderTest.java (14), AdminEndpointConfigurationTest.java (7), EnsembleTimerControllerMvcTest.java (6). | +3.5 pts | Medium | Test Quality |
| Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge. | +3.4 pts | Medium | A11y enforcement |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.3 pts | Low | ADR Quality |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +2.3 pts | Medium | Forms & labels |
| 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. | +2.2 pts | Medium | Security & performance tooling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| src/test/java/com/jitterted/mobreg/adapter/in/web/admin/AdminEndpointConfigurationTest.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/test/java/com/jitterted/mobreg/adapter/in/web/member/MemberEndpointConfigurationTest.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java | 7.0 | Mixed | Test Quality: No assertions: secondsTickerStoppedWhenHandleTickForNonExistentTimer |
| src/test/java/com/jitterted/mobreg/adapter/in/web/member/EnsembleTimerControllerMvcTest.java | 7.1 | Mixed | Test Quality: No assertions: getForTimerViewEndpointReturns200OK |
| src/test/java/com/jitterted/mobreg/domain/CountdownTimerTest.java | 7.1 | Mixed | Test Quality: No assertions: exceptionThrownIfStartTimerWhenFinished |
| src/test/java/com/jitterted/mobreg/HexagonalArchitectureTest.java | 7.1 | Mixed | Test Quality: No assertions: adaptersMustNotDependOnEachOther |
| src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerLifecycleControllerMvcTest.java | 7.2 | Mixed | Test Quality: No assertions: htmxGetEndpointReturns200Ok |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/test/java/com/jitterted/mobreg/adapter/in/web/TestAdminConfiguration.java | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/main/java/com/jitterted/mobreg/application/EnsembleService.java | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/main/java/com/jitterted/mobreg/adapter/out/membership/GitHubCollaboratorFinder.java | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/test/java/com/jitterted/mobreg/domain/EnsembleTimerTest.java | 7.8 | Mixed | Test Quality: No assertions: rotateTimerWhenTimerNotStartedThrowsException |
| REDACTED | 7.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.9 | Mixed | Data Compliance (PII/GDPR): Medium: REDACTED |
| src/test/java/com/jitterted/mobreg/adapter/in/web/admin/ThymeleafTemplateTest.java | 8.0 | Near-clean | Test Quality: Assertions commented out: template |
| src/test/java/com/jitterted/mobreg/adapter/in/web/member/MemberEndpointHtmlTest.java | 8.0 | Near-clean | Test Quality: No assertions (empty test): html |
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 77 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 — 77 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, 158 of 305 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.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 693 commit(s) sampled, automation and bot accounts excluded). One of them holds 95% of the history; the other 2 hold 2.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- 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.
- 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.
- 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 (.). the service did not build — `sh ./mvnw -B -q -DskipTests compile` exited 1: e/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1632) at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:223…; 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.
- 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.
- 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.
- 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.
- 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.
- D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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
1 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with Ensemble.java. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
0 duplicated block group(s) detected.
D6 · Cohesion (LCOM4)
0 of 28 classes have LCOM4 above 3.
D9 · Test Distribution
282 test methods: 282 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
8 skipped (8 with a documented reason), 54 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 282 tests.
What to do
- Resolve the 52 No assertions finding(s) in Test Quality — start with EnsembleTimerHolderTest.java (14), AdminEndpointConfigurationTest.java (7), EnsembleTimerControllerMvcTest.java (6). — One of this dimension's main actionable groups (52 warning-level).
- Resolve the 1 Assertions commented out finding(s) in Test Quality — start with ThymeleafTemplateTest.java. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with MemberEndpointHtmlTest.java. — One of this dimension's main actionable groups (1 issue-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
140 outdated artifact(s) of 165 resolved by the build, graded against Maven Central. The poms themselves state a version for only 5 of 25 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 5 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 1 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. 20 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
12 deducted task-comment markers across 4521 LoC (0.2/KLoC) → score 9.6. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 12 TodoComment finding(s) in Explicit Debt — start with MemberEndpointConfigurationTest.java (3), TestAdminConfiguration.java (2), AdminEndpointConfigurationTest.java (2). — One of this dimension's main actionable groups (12 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 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).
D26 · Project Cohesion
0 of 1 build units (Maven) flagged as possibly oversized/incoherent.
D27 · Navigability
66 % of calls cross a namespace and 11 % 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)
4 finding(s): 0 critical, 4 high, 0 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` (lines 204–205, line 257) — 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-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
9 finding(s): 2 critical, 5 high, 2 medium, 0 low.
What to do
- Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
3 finding(s): 0 critical, 0 high, 3 medium, 0 low.
What to do
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
D32 · Data Compliance (PII/GDPR)
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 25 of the 108 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 7 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×8) — src/main/resources/templates/member-register.html:147, src/main/resources/templates/member-register.html:158, src/main/resources/templates/member-register.html:185, …
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×14) — src/main/resources/templates/dashboard.html:203, src/main/resources/templates/dashboard.html:213, src/main/resources/templates/dashboard.html:223, …
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×10) — src/main/resources/static/index.html:2, src/main/resources/templates/dashboard.html:2, src/main/resources/templates/ensemble-detail.html:2, …
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. (×4) — src/main/resources/static/index.html:48, src/main/resources/templates/ensemble-detail.html:62, src/main/resources/templates/ensemble-detail.html:84, …
- <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — src/main/resources/templates/member-profile.html:122
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 10 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
- `WebSocketBroadcaster` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (currentTextMessage; e.g. `currentTextMessage` in `sendHtml` at line 39). — src/main/java/com/jitterted/mobreg/adapter/out/websocket/WebSocketBroadcaster.java:21
What to do
- Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
- `EnsemblerApplication.ensembleRepository` saves `Ensemble`, `Member` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — src/main/java/com/jitterted/mobreg/EnsemblerApplication.java:28
What to do
- Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
DM11 · Constructible invalid state
- `Ensemble`'s public constructor takes `name` 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 `Ensemble` 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. — src/main/java/com/jitterted/mobreg/domain/Ensemble.java:32
- `EnsembleTimer`'s public constructor takes `ensembleName` 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 `EnsembleTimer` 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. — src/main/java/com/jitterted/mobreg/domain/EnsembleTimer.java:23
- `Member`'s public constructor takes `firstName`, `githubUsername` 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 `Member` 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. — src/main/java/com/jitterted/mobreg/domain/Member.java:19
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
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM7 · Repository granularity
DM9 · Scattered domain decisions
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×14) — src/test/java/com/jitterted/mobreg/adapter/in/web/admin/AdminMembershipEndpointTest.java:40, src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:370, src/test/java/com/jitterted/mobreg/adapter/in/web/admin/ThymeleafTemplateTest.java:19, …
What to do
- Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
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
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 404 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
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.
- Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- 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.
P7 · Outbound HTTP resilience
- `RestClient.create(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — src/main/java/com/jitterted/mobreg/adapter/out/conductor/ConductorHttpBroadcaster.java:17, src/main/java/com/jitterted/mobreg/adapter/out/email/BrevoEmailer.java:26
- `new RestTemplate(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×3) — src/main/java/com/jitterted/mobreg/adapter/out/notification/pushover/PushoverNotifier.java:52, src/main/java/com/jitterted/mobreg/adapter/out/zoom/ZoomScheduler.java:35, src/main/java/com/jitterted/mobreg/adapter/out/zoom/ZoomScheduler.java:77
What to do
- Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
P8 · Schema migrations
S1 · Web-Security Posture
- `https://kit.fontawesome.com/3ae2c56324.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 4 such include(s) across the repository's markup. — src/main/resources/templates/dashboard.html:13
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
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
- `error` at line 112 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jitterted/mobreg/adapter/out/zoom/ZoomScheduler.java:112
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 0/17 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).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 68% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 73% | Strong | Solid. |
| Maturity | 65% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 52% | Adequate — gated by P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 85% | Strong | Strongest area. |
| Domain Modelling | 79% | Adequate — gated by DM11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 40% | Weak — gated by AC1 | 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 — 1 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 — 47 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 — `sh ./mvnw -B -q -DskipTests compile` exited 1: e/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1632) at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:223…; 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-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, html not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (domain), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .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
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Maven build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- 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 none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — Not applicable: the 4 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- 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.
- 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 — 35 finding(s)
- <input> without a programmatic label src/main/resources/templates/dashboard.html:203
- <input> without a programmatic label src/main/resources/templates/dashboard.html:213
- <input> without a programmatic label src/main/resources/templates/dashboard.html:223
- <input> without a programmatic label src/main/resources/templates/dashboard.html:234
- <input> without a programmatic label src/main/resources/templates/ensemble-detail.html:108
- <input> without a programmatic label src/main/resources/templates/ensemble-detail.html:118
- <input> without a programmatic label src/main/resources/templates/ensemble-detail.html:128
- <input> without a programmatic label src/main/resources/templates/ensemble-detail.html:139
- <input> without a programmatic label src/main/resources/templates/ensemble-detail.html:180
- <input> without a programmatic label src/main/resources/templates/member-profile.html:91
- <input> without a programmatic label src/main/resources/templates/member-profile.html:101
- <input> without a programmatic label src/main/resources/templates/member-profile.html:112
- <input> without a programmatic label src/main/resources/templates/members.html:33
- <img> without a text alternative src/main/resources/templates/member-register.html:147
- <img> without a text alternative src/main/resources/templates/member-register.html:158
- <img> without a text alternative src/main/resources/templates/member-register.html:185
- <img> without a text alternative src/main/resources/templates/member-register.html:195
- <img> without a text alternative src/main/resources/templates/member-register.html:301
- <img> without a text alternative src/main/resources/templates/member-register.html:312
- <img> without a text alternative src/main/resources/templates/member-register.html:324
- <img> without a text alternative src/main/resources/templates/member-register.html:334
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <select> without a programmatic label src/main/resources/templates/member-profile.html:122
- Assertions commented out: template src/test/java/com/jitterted/mobreg/adapter/in/web/admin/ThymeleafTemplateTest.java:42
- No assertions (empty test): html src/test/java/com/jitterted/mobreg/adapter/in/web/member/MemberEndpointHtmlTest.java:81
- REDACTED
- REDACTED
Serious — 99 finding(s)
- No assertions: getOfDashboardEndpointReturns200Ok src/test/java/com/jitterted/mobreg/adapter/in/web/admin/AdminEndpointConfigurationTest.java:54
- No assertions: getOfEnsembleDetailEndpointReturns200Ok src/test/java/com/jitterted/mobreg/adapter/in/web/admin/AdminEndpointConfigurationTest.java:63
- No assertions: postToCancelEndpointRedirects src/test/java/com/jitterted/mobreg/adapter/in/web/admin/AdminEndpointConfigurationTest.java:117
- No assertions: postToChangeEnsembleEndpointRedirects src/test/java/com/jitterted/mobreg/adapter/in/web/admin/AdminEndpointConfigurationTest.java:83
- No assertions: postToCompleteEndpointRedirects src/test/java/com/jitterted/mobreg/adapter/in/web/admin/AdminEndpointConfigurationTest.java:108
- No assertions: postToRegisterParticipantEndpointRedirects src/test/java/com/jitterted/mobreg/adapter/in/web/admin/AdminEndpointConfigurationTest.java:96
- No assertions: postToScheduleEnsembleEndpointRedirects src/test/java/com/jitterted/mobreg/adapter/in/web/admin/AdminEndpointConfigurationTest.java:71
- No assertions: getOfMemberAdminPageIsStatus200Ok src/test/java/com/jitterted/mobreg/adapter/in/web/admin/AdminMembershipEndpointTest.java:35
- No assertions: secondsTickerStoppedWhenHandleTickForNonExistentTimer src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:180
- No assertions: timerDeletedStopsSecondsTicker src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:167
- No assertions: timerFinishedStopsSecondsTicker src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:151
- No assertions: timerRunningNotFinishedDoesNotStopTicker src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:109
- No assertions: askForTimerButNoTimerExists src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:225
- No assertions: queryIfTimerStartedButNoTimerExists src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:235
- No assertions: startTimerButNoTimerExists src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:244
- No assertions: finishedTimerOnRotateThenTimerMovesToWaitingToStart src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:338
- No assertions: onTickWhenFinishedBroadcastsTimerFinishedWithFinishedEvent src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:323
- No assertions: onTickWhileRunningBroadcastsCurrentTimerState src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:270
- No assertions: onTimerCreationBroadcastsTimerWaitingToStart src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:257
- No assertions: onTimerPauseBroadcastsPauseStateAndPausedEvent src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:283
- No assertions: onTimerResumeBroadcastsRunningStateAndSendsResumedEvent src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:302
- No assertions: resetTimerBroadcastsTimerWaitingToStart src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:356
- No assertions: htmxGetEndpointReturns200Ok src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerLifecycleControllerMvcTest.java:67
- No assertions: postToCreateTimerRedirects src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerLifecycleControllerMvcTest.java:42
- No assertions: postToCreateTimerWithDurationRedirects src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerLifecycleControllerMvcTest.java:49
- TodoComment src/test/java/com/jitterted/mobreg/adapter/in/web/TestAdminConfiguration.java:61
- TodoComment src/test/java/com/jitterted/mobreg/adapter/in/web/TestAdminConfiguration.java:65
- TodoComment src/main/java/com/jitterted/mobreg/EnsemblerConfiguration.java:73
- TodoComment src/test/java/com/jitterted/mobreg/adapter/in/web/member/MemberEndpointConfigurationTest.java:56
- TodoComment src/test/java/com/jitterted/mobreg/adapter/in/web/member/MemberEndpointConfigurationTest.java:66
- TodoComment src/test/java/com/jitterted/mobreg/adapter/in/web/member/MemberEndpointConfigurationTest.java:97
- TodoComment src/test/java/com/jitterted/mobreg/adapter/in/web/admin/AdminEndpointConfigurationTest.java:30
- TodoComment src/test/java/com/jitterted/mobreg/adapter/in/web/admin/AdminEndpointConfigurationTest.java:34
- TodoComment src/main/java/com/jitterted/mobreg/application/EnsembleService.java:97
- TodoComment src/main/java/com/jitterted/mobreg/application/EnsembleService.java:194
- TodoComment src/main/java/com/jitterted/mobreg/adapter/out/membership/GitHubCollaboratorFinder.java:10
- TodoComment src/main/java/com/jitterted/mobreg/adapter/out/membership/GitHubCollaboratorFinder.java:15
- Page without a main landmark src/main/resources/static/index.html:2
- Page without a main landmark src/main/resources/templates/dashboard.html:2
- Page without a main landmark src/main/resources/templates/ensemble-detail.html:2
- Page without a main landmark src/main/resources/templates/ensemble-timer.html:2
- Page without a main landmark src/main/resources/templates/invite-invalid.html:2
- Page without a main landmark src/main/resources/templates/invites.html:2
- Page without a main landmark src/main/resources/templates/member-profile.html:2
- Page without a main landmark src/main/resources/templates/member-register.html:2
- Page without a main landmark src/main/resources/templates/members.html:2
- Page without a main landmark src/main/resources/templates/user.html:2
- Outbound HTTP without resilience src/main/java/com/jitterted/mobreg/adapter/out/conductor/ConductorHttpBroadcaster.java:17
- Outbound HTTP without resilience src/main/java/com/jitterted/mobreg/adapter/out/email/BrevoEmailer.java:26
- Outbound HTTP without resilience src/main/java/com/jitterted/mobreg/adapter/out/notification/pushover/PushoverNotifier.java:52
- Outbound HTTP without resilience src/main/java/com/jitterted/mobreg/adapter/out/zoom/ZoomScheduler.java:35
- Outbound HTTP without resilience src/main/java/com/jitterted/mobreg/adapter/out/zoom/ZoomScheduler.java:77
- Low contrast Tailwind colour pair (3.8:1) src/main/resources/templates/ensemble-detail.html:62
- Low contrast Tailwind colour pair (3.8:1) src/main/resources/templates/ensemble-detail.html:84
- Low contrast Tailwind colour pair (3.8:1) src/main/resources/templates/ensemble-timer.html:150
- REDACTED
- REDACTED
- REDACTED
- Constructible in an invalid state: Ensemble src/main/java/com/jitterted/mobreg/domain/Ensemble.java:32
- Constructible in an invalid state: EnsembleTimer src/main/java/com/jitterted/mobreg/domain/EnsembleTimer.java:23
- Constructible in an invalid state: Member src/main/java/com/jitterted/mobreg/domain/Member.java:19
- REDACTED
- REDACTED
- Low contrast Tailwind colour pair (3.3:1) src/main/resources/static/index.html:48
- Focus outline removed inline src/main/resources/templates/member-profile.html:122
- Accessibility enforcement below the top rung
- Stateful singleton: WebSocketBroadcaster src/main/java/com/jitterted/mobreg/adapter/out/websocket/WebSocketBroadcaster.java:21
- TooManyMethods: Ensemble src/main/java/com/jitterted/mobreg/domain/Ensemble.java:13
- REDACTED
- REDACTED
- One operation mutates 2 aggregates: EnsemblerApplication.ensembleRepository src/main/java/com/jitterted/mobreg/EnsemblerApplication.java:28
- Third-party script without Subresource Integrity src/main/resources/templates/dashboard.html:13
Minor — 23 finding(s)
- Disabled test src/test/java/com/jitterted/mobreg/adapter/in/web/admin/AdminMembershipEndpointTest.java:40
- Disabled test src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:370
- Disabled test src/test/java/com/jitterted/mobreg/adapter/in/web/admin/ThymeleafTemplateTest.java:19
- Disabled test src/test/java/com/jitterted/mobreg/adapter/in/web/member/MemberEndpointConfigurationTest.java:26
- Disabled test src/test/java/com/jitterted/mobreg/adapter/in/web/member/MemberEndpointHtmlTest.java:41
- Disabled test src/test/java/com/jitterted/mobreg/adapter/out/email/BrevoEmailerManualTest.java:16
- Disabled test src/test/java/com/jitterted/mobreg/adapter/out/membership/GitHubApiTest.java:19
- Disabled test src/test/java/com/jitterted/mobreg/adapter/out/notification/pushover/PushoverNotificationTest.java:30
- Disabled test src/test/java/com/jitterted/mobreg/domain/CountdownTimerTest.java:72
- Disabled test src/test/java/com/jitterted/mobreg/domain/CountdownTimerTest.java:78
- Disabled test src/test/java/com/jitterted/mobreg/domain/CountdownTimerTest.java:140
- Disabled test src/test/java/com/jitterted/mobreg/domain/CountdownTimerTest.java:146
- Disabled test src/test/java/com/jitterted/mobreg/domain/CountdownTimerTest.java:152
- Disabled test src/test/java/com/jitterted/mobreg/domain/CountdownTimerTest.java:158
- No ADRs found
- No ADRs
- No SAST
- Dependabot does not watch github-actions REDACTED:2
- No rollback/health safety
- No changelog
- Duplicated predicate src/main/java/com/jitterted/mobreg/adapter/in/web/member/EnsembleSummaryView.java:183
- Interpolated log message defeats structured logging src/main/java/com/jitterted/mobreg/adapter/out/zoom/ZoomScheduler.java:112
- Java packages are not null-marked everywhere
Minor — 148 finding(s)
- Skipped (documented): postToAddMemberRedirects src/test/java/com/jitterted/mobreg/adapter/in/web/admin/AdminMembershipEndpointTest.java:42
- Skipped (documented): onEnsembleEndedRemoveAssociatedTimer src/test/java/com/jitterted/mobreg/adapter/in/web/admin/EnsembleTimerHolderTest.java:372
- Skipped (documented): pauseAlreadyPausedTimerIsNoOp src/test/java/com/jitterted/mobreg/domain/CountdownTimerTest.java:73
- Skipped (documented): resumeRunningTimerIsNoOp src/test/java/com/jitterted/mobreg/domain/CountdownTimerTest.java:79
- Skipped (documented): exceptionThrownOnPauseWhenTimerFinished src/test/java/com/jitterted/mobreg/domain/CountdownTimerTest.java:147
- Skipped (documented): exceptionThrownOnPauseWhenTimerNotStarted src/test/java/com/jitterted/mobreg/domain/CountdownTimerTest.java:141
- Skipped (documented): exceptionThrownOnResumeWhenTimerFinished src/test/java/com/jitterted/mobreg/domain/CountdownTimerTest.java:159
- Skipped (documented): exceptionThrownOnResumeWhenTimerNotStarted src/test/java/com/jitterted/mobreg/domain/CountdownTimerTest.java:153
- Outdated (compile -- module org.zalando.logbook.spring.boot.starter [auto]): org.zalando:logbook-spring-boot-starter
- Outdated (compile -- module org.zalando.logbook.spring.boot.autoconfigure [auto]): org.zalando:logbook-spring-boot-autoconfigure
- Outdated (compile -- module org.zalando.logbook.core [auto]): org.zalando:logbook-core
- Outdated (compile -- module org.zalando.logbook [auto]): org.zalando:logbook-api
- Outdated (compile -- module org.zalando.logbook.common [auto]): org.zalando:logbook-common
- Outdated (compile -- module org.zalando.logbook.json [auto]): org.zalando:logbook-json
- Outdated (compile -- module org.zalando.logbook.spring [auto]): org.zalando:logbook-spring
- Outdated (compile -- module org.zalando.logbook.servlet [auto]): org.zalando:logbook-servlet
- Outdated (compile -- module org.slf4j): org.slf4j:slf4j-api
- Outdated (compile (optional) -- module spring.boot.docker.compose [auto]): org.springframework.boot:spring-boot-docker-compose
- Outdated (compile -- module spring.boot [auto]): org.springframework.boot:spring-boot
- Outdated (compile -- module spring.context [auto]): org.springframework:spring-context
- 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 com.fasterxml.jackson.module.paramnames): com.fasterxml.jackson.module:jackson-module-parameter-names
- Outdated (compile -- module spring.boot.starter.actuator [auto]): org.springframework.boot:spring-boot-starter-actuator
- 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 jakarta.annotation): jakarta.annotation:jakarta.annotation-api
- Outdated (compile -- module org.yaml.snakeyaml): org.yaml:snakeyaml
- 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 micrometer.observation [auto]): io.micrometer:micrometer-observation
- Outdated (compile -- module micrometer.commons [auto]): io.micrometer:micrometer-commons
- Outdated (compile -- module micrometer.jakarta9 [auto]): io.micrometer:micrometer-jakarta9
- Outdated (compile -- module spring.boot.starter.thymeleaf [auto]): org.springframework.boot:spring-boot-starter-thymeleaf
- Outdated (compile -- module attoparser [auto]): org.attoparser:attoparser
- Outdated (compile -- module unbescape [auto]): org.unbescape:unbescape
- Outdated (compile -- module spring.boot.starter.validation [auto]): org.springframework.boot:spring-boot-starter-validation
- Outdated (compile -- module org.apache.tomcat.embed.el): org.apache.tomcat.embed:tomcat-embed-el
- Outdated (compile -- module org.hibernate.validator [auto]): org.hibernate.validator:hibernate-validator
- Outdated (compile -- module jakarta.validation): jakarta.validation:jakarta.validation-api
- Outdated (compile -- module com.fasterxml.classmate): com.fasterxml:classmate
- Outdated (compile -- module spring.boot.starter.web [auto]): org.springframework.boot:spring-boot-starter-web
- Outdated (compile -- module spring.boot.starter.json [auto]): org.springframework.boot:spring-boot-starter-json
- Outdated (compile -- module spring.boot.starter.tomcat [auto]): org.springframework.boot:spring-boot-starter-tomcat
- 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.web [auto]): org.springframework:spring-web
- Outdated (compile -- module spring.beans [auto]): org.springframework:spring-beans
- Outdated (compile -- module spring.webmvc [auto]): org.springframework:spring-webmvc
- Outdated (compile -- module spring.expression [auto]): org.springframework:spring-expression
- Outdated (compile -- module spring.boot.starter.websocket [auto]): org.springframework.boot:spring-boot-starter-websocket
- Outdated (compile -- module spring.messaging [auto]): org.springframework:spring-messaging
- Outdated (compile -- module spring.websocket [auto]): org.springframework:spring-websocket
- Outdated (compile (optional) -- module spring.boot.configuration.processor [auto]): org.springframework.boot:spring-boot-configuration-processor
- Outdated (runtime (optional) -- module spring.boot.devtools [auto]): org.springframework.boot:spring-boot-devtools
- Outdated (compile -- module spring.boot.autoconfigure [auto]): org.springframework.boot:spring-boot-autoconfigure
- Outdated (runtime -- module micrometer.registry.prometheus [auto]): io.micrometer:micrometer-registry-prometheus
- Outdated (compile -- module micrometer.core [auto]): io.micrometer:micrometer-core
- Outdated (runtime -- module io.prometheus.metrics.core [auto]): io.prometheus:prometheus-metrics-core
- Outdated (runtime -- module io.prometheus.metrics.model [auto]): io.prometheus:prometheus-metrics-model
- Outdated (runtime -- module io.prometheus.metrics.config [auto]): io.prometheus:prometheus-metrics-config
- Outdated (runtime -- module io.prometheus.metrics.tracer.common [auto]): io.prometheus:prometheus-metrics-tracer-common
- Outdated (runtime -- module io.prometheus.metrics.expositionformats [auto]): io.prometheus:prometheus-metrics-exposition-formats
- Outdated (runtime -- module io.prometheus.writer.text [auto]): io.prometheus:prometheus-metrics-exposition-textformats
- Outdated (compile -- module spring.boot.starter.security [auto]): org.springframework.boot:spring-boot-starter-security
- Outdated (compile -- module spring.aop [auto]): org.springframework:spring-aop
- Outdated (compile -- module spring.security.config [auto]): org.springframework.security:spring-security-config
- Outdated (compile -- module spring.security.web [auto]): org.springframework.security:spring-security-web
- Outdated (compile -- module spring.security.test [auto]): org.springframework.security:spring-security-test
- Outdated (compile -- module spring.security.core [auto]): org.springframework.security:spring-security-core
- Outdated (compile -- module spring.security.crypto [auto]): org.springframework.security:spring-security-crypto
- Outdated (compile -- module spring.core [auto]): org.springframework:spring-core
- Outdated (compile -- module spring.test [auto]): org.springframework:spring-test
- Outdated (compile -- module spring.boot.starter.oauth2.client [auto]): org.springframework.boot:spring-boot-starter-oauth2-client
- Outdated (compile -- module spring.security.oauth2.client [auto]): org.springframework.security:spring-security-oauth2-client
- Outdated (compile -- module spring.security.oauth2.core [auto]): org.springframework.security:spring-security-oauth2-core
- Outdated (compile -- module oauth2.oidc.sdk (auto)): com.nimbusds:oauth2-oidc-sdk
- Outdated (compile -- module content.type (auto)): com.nimbusds:content-type
- Outdated (compile -- module spring.security.oauth2.jose [auto]): org.springframework.security:spring-security-oauth2-jose
- Outdated (compile -- module com.nimbusds.jose.jwt [auto]): com.nimbusds:nimbus-jose-jwt
- Outdated (compile -- module github.client (auto)): com.spotify:github-client
- Outdated (compile -- module com.google.common [auto]): com.google.guava:guava
- Outdated (compile -- module failureaccess (auto)): com.google.guava:failureaccess
- Outdated (compile -- module org.checkerframework.checker.qual [auto]): org.checkerframework:checker-qual
- Outdated (compile -- module com.google.errorprone.annotations [auto]): com.google.errorprone:error_prone_annotations
- Outdated (compile -- module j2objc.annotations (auto)): com.google.j2objc:j2objc-annotations
- Outdated (compile -- module com.fasterxml.jackson.annotation): com.fasterxml.jackson.core:jackson-annotations
- Outdated (compile -- module com.fasterxml.jackson.datatype.jdk8): com.fasterxml.jackson.datatype:jackson-datatype-jdk8
- Outdated (compile -- module com.fasterxml.jackson.datatype.jsr310): com.fasterxml.jackson.datatype:jackson-datatype-jsr310
- Outdated (compile -- module jjwt.api (auto)): io.jsonwebtoken:jjwt-api
- Outdated (compile -- module opencensus.api (auto)): io.opencensus:opencensus-api
- Outdated (compile -- module grpc.context (auto)): io.grpc:grpc-context
- Outdated (runtime -- module jjwt.impl (auto)): io.jsonwebtoken:jjwt-impl
- Outdated (runtime -- module jjwt.jackson (auto)): io.jsonwebtoken:jjwt-jackson
- Outdated (compile -- module org.apache.commons.io [auto]): commons-io:commons-io
- Outdated (compile -- module spring.boot.starter.data.jdbc [auto]): org.springframework.boot:spring-boot-starter-data-jdbc
- 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.jdbc [auto]): org.springframework:spring-jdbc
- Outdated (compile -- module spring.data.jdbc [auto]): org.springframework.data:spring-data-jdbc
- Outdated (compile -- module spring.data.relational [auto]): org.springframework.data:spring-data-relational
- Outdated (compile -- module spring.data.commons [auto]): org.springframework.data:spring-data-commons
- Outdated (compile -- module spring.tx [auto]): org.springframework:spring-tx
- Outdated (runtime -- module org.postgresql.jdbc [auto]): org.postgresql:postgresql
- Outdated (compile -- module flyway.core (auto)): org.flywaydb:flyway-core
- Outdated (compile -- module com.fasterxml.jackson.dataformat.toml): com.fasterxml.jackson.dataformat:jackson-dataformat-toml
- Outdated (compile -- module flyway.database.postgresql (auto)): org.flywaydb:flyway-database-postgresql
- 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 (compile -- module json.path [auto]): com.jayway.jsonpath:json-path
- Outdated (compile -- module json.smart (auto)): net.minidev:json-smart
- Outdated (compile -- module accessors.smart (auto)): net.minidev:accessors-smart
- Outdated (compile -- module org.objectweb.asm): org.ow2.asm:asm
- Outdated (test -- module net.bytebuddy): net.bytebuddy:byte-buddy
- Outdated (test -- module awaitility (auto)): org.awaitility:awaitility
- 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 org.xmlunit [auto]): org.xmlunit:xmlunit-core
- Outdated (test -- module junit.jupiter (auto)): org.testcontainers:junit-jupiter
- Outdated (test -- module testcontainers (auto)): org.testcontainers:testcontainers
- Outdated (test -- module org.apache.commons.compress): org.apache.commons:commons-compress
- 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 postgresql (auto)): org.testcontainers:postgresql
- Outdated (test -- module jdbc (auto)): org.testcontainers:jdbc
- Outdated (test -- module database.commons (auto)): org.testcontainers:database-commons
- Outdated (compile -- module org.jetbrains.annotations): org.jetbrains:annotations
- Outdated (test -- module com.tngtech.archunit.junit5 [auto]): com.tngtech.archunit:archunit-junit5
- Outdated (test -- module com.tngtech.archunit.junit5.api [auto]): com.tngtech.archunit:archunit-junit5-api
- Outdated (test -- module com.tngtech.archunit [auto]): com.tngtech.archunit:archunit
- Outdated (test -- module com.tngtech.archunit.junit5.engine [auto]): com.tngtech.archunit:archunit-junit5-engine
- Outdated (test -- module com.tngtech.archunit.junit5.engineapi [auto]): com.tngtech.archunit:archunit-junit5-engine-api
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-01f8d5ad95b34b47b5bb8984dd47ab0f/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-01f8d5ad95b34b47b5bb8984dd47ab0f/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 . | 4 | 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 . | 9 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 3 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep --config /opt/semgrep-rules/gdpr.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 . | 1 | artifacts/raw/semgrep-gdpr.json |
| 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 |