Executive summary
modernice/goes is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 57 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Code Health, at 49, is the weakest lens and counts most in the score. The best first step is removing the unused code, worth about 6 points. Turning on missing-value checks comes next, worth about 4 points. Raising Code Health to 67 would lift the score to about 63.
Eighteen known security holes in the packages the code depends on can be used by attackers. Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and four settings leave the servers or containers unsafe. Updating the vulnerable packages, pinning each tool to an exact version and correcting the unsafe settings would close these risks. Limiting each secret to its own step would fix the three secrets exposed to more of the pipeline than needed, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The four loops of files that import each other need breaking.
The product code is 26,929 lines, about €58,000 to rebuild.
If Code Health rose from 49 to 67, the lowest score rated Strong, the score would rise from 57 to about 63.
New since the last survey: 13 findings
- 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
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Visual & motion safety · Low contrast colour pair in CSS (3.5:1) ui/app/spa-loading-template.html
- Visual & motion safety · Low contrast colour pair in CSS (3.7:1) docs/.vitepress/theme/HomePage.vue
Fixed since the last survey: 71 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dead Code · Dead file (~15 LoC) ui/app/components/ui/table/TableEmpty.vue
- Dead Code · Dead file (~14 LoC) ui/app/components/ui/select/SelectScrollDownButton.vue
- Dead Code · Dead file (~14 LoC) ui/app/components/ui/select/SelectScrollUpButton.vue
- Dead Code · Dead file (~14 LoC) ui/app/middleware/auth.global.ts
- Dead Code · Dead file (~12 LoC) ui/app/components/ui/dropdown-menu/DropdownMenuSeparator.vue
- Dead Code · Dead file (~11 LoC) ui/app/components/ui/select/index.ts
- Dead Code · Dead file (~10 LoC) ui/app/components/ui/alert/Alert.vue
- Dead Code · Dead file (~10 LoC) ui/app/components/ui/card/Card.vue
- Dead Code · Dead file (~10 LoC) ui/app/components/ui/label/Label.vue
- Dead Code · Dead file (~10 LoC) ui/app/components/ui/select/SelectGroup.vue
- Dead Code · Dead file (~10 LoC) ui/app/components/ui/select/SelectSeparator.vue
- Dead Code · Dead file (~10 LoC) ui/app/components/ui/sheet/SheetDescription.vue
- Dead Code · Dead file (~10 LoC) ui/app/components/ui/sheet/SheetOverlay.vue
- Dead Code · Dead file (~10 LoC) ui/app/components/ui/sheet/SheetTitle.vue
- Dead Code · Dead file (~10 LoC) ui/app/components/ui/table/utils.ts
- Dead Code · Dead file (~9 LoC) ui/app/components/ui/dialog/DialogDescription.vue
- Dead Code · Dead file (~9 LoC) ui/app/components/ui/dialog/DialogOverlay.vue
- Dead Code · Dead file (~9 LoC) ui/app/components/ui/dialog/DialogTitle.vue
- Dead Code · Dead file (~9 LoC) ui/app/components/ui/dropdown-menu/index.ts
- Dead Code · Dead file (~9 LoC) ui/app/components/ui/skeleton/Skeleton.vue
- Dead Code · Dead file (~9 LoC) ui/app/components/ui/table/index.ts
- Dead Code · Dead file (~8 LoC) ui/app/components/EmptyState.vue
- Dead Code · Dead file (~8 LoC) ui/app/components/EventDialog.vue
- Dead Code · Dead file (~8 LoC) ui/app/components/ui/dropdown-menu/DropdownMenu.vue
- Dead Code · Dead file (~8 LoC) ui/app/components/ui/dropdown-menu/DropdownMenuRadioGroup.vue
- Dead Code · Dead file (~8 LoC) ui/app/components/ui/select/Select.vue
- Dead Code · Dead file (~8 LoC) ui/app/components/ui/sheet/Sheet.vue
- Dead Code · Dead file (~8 LoC) ui/app/components/ui/sheet/index.ts
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/alert/AlertAction.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/alert/AlertDescription.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/alert/AlertTitle.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/card/CardAction.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/card/CardContent.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/card/CardDescription.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/card/CardFooter.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/card/CardHeader.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/card/CardTitle.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/card/index.ts
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/dialog/Dialog.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/dropdown-menu/DropdownMenuGroup.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/dropdown-menu/DropdownMenuTrigger.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/select/SelectLabel.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/table/Table.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/table/TableBody.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/table/TableCaption.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/table/TableCell.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/table/TableFooter.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/table/TableHead.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/table/TableHeader.vue
- Dead Code · Dead file (~7 LoC) ui/app/components/ui/table/TableRow.vue
- Dead Code · Dead file (~7 LoC) ui/app/lib/utils.ts
- Dead Code · Dead file (~5 LoC) ui/app/components/BrandMark.vue
- Dead Code · Dead file (~5 LoC) ui/app/components/ui/dialog/index.ts
- Dead Code · Dead file (~5 LoC) ui/app/components/ui/select/SelectItemText.vue
- Dead Code · Dead file (~5 LoC) ui/app/components/ui/select/SelectValue.vue
- Dead Code · Dead file (~5 LoC) ui/app/components/ui/sheet/SheetClose.vue
- Dead Code · Dead file (~5 LoC) ui/app/components/ui/sheet/SheetFooter.vue
- Dead Code · Dead file (~5 LoC) ui/app/components/ui/sheet/SheetHeader.vue
- Dead Code · Dead file (~5 LoC) ui/app/components/ui/sheet/SheetTrigger.vue
- Dead Code · Dead file (~4 LoC) ui/app/utils/query.ts
- Dead Code · Dead file (~1 LoC) ui/app/components/ui/input/index.ts
- Dead Code · Dead file (~1 LoC) ui/app/components/ui/label/index.ts
- Dead Code · Dead file (~1 LoC) ui/app/components/ui/separator/index.ts
- Dead Code · Dead file (~1 LoC) ui/app/components/ui/skeleton/index.ts
- Dead Code · Dead file (~1 LoC) ui/app/components/ui/switch/index.ts
- Dead Code · Dead file (~0 LoC) ui/app/app.vue
- Dead Code · Dead file (~0 LoC) ui/app/layouts/auth.vue
Rebuild cost: about €58,000 · Estimate
| Cost to rebuild | €19,000 to €96,000, for 319 to 1,011 hours of work, about 0.4 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.8 at a score of 57. 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 | Medium: 26,929 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 github.com/modernice/goes/cli/internal/clifactory | 2 github.com/modernice/goes/codec | 3 github.com/modernice/goes/command/finish | 4 github.com/modernice/goes/event/query/time | 5 github.com/modernice/goes/event/query/version | 6 ui.app.composables | 7 github.com/modernice/goes/event | 8 github.com/modernice/goes/eventstoreui | 9 github.com/modernice/goes/aggregate/internal/softdelete | 10 github.com/modernice/goes/backend/nats | 11 github.com/modernice/goes/backend/natsjs | 12 github.com/modernice/goes/backend/postgres | 13 github.com/modernice/goes/backend/testing/eventbustest | 14 github.com/modernice/goes/command | 15 github.com/modernice/goes/event/query | 16 github.com/modernice/goes/projection | 17 github.com/modernice/goes/cli | 18 github.com/modernice/goes/command/cmdbus | 19 github.com/modernice/goes/command/handler | 20 github.com/modernice/goes/event/handler | 21 github.com/modernice/goes/internal/projectiontest | 22 github.com/modernice/goes/projection/schedule | 23 github.com/modernice/goes/aggregate | 24 github.com/modernice/goes/projection/lookup | 25 github.com/modernice/goes/aggregate/query | 26 github.com/modernice/goes/aggregate/snapshot | 27 github.com/modernice/goes/aggregate/stream | 28 github.com/modernice/goes/command/builtin | 29 github.com/modernice/goes/contrib/auth | 30 github.com/modernice/goes/saga/action | 31 github.com/modernice/goes/workflow | 32 github.com/modernice/goes/aggregate/repository | 33 github.com/modernice/goes/aggregate/snapshot/query | 34 github.com/modernice/goes/aggregate/snapshot/storetest | 35 github.com/modernice/goes/backend/mongo | 36 github.com/modernice/goes/contrib/auth/authrpc | 37 github.com/modernice/goes/contrib/auth/http/middleware | 38 github.com/modernice/goes/saga/report | 39 github.com/modernice/goes/backend/mongo/mongotest | 40 github.com/modernice/goes/saga |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 github.com/modernice/goes/cli/internal/clifactory | ||||||||||||||||||||||||||||||||||||||||
| 2 github.com/modernice/goes/codec | ||||||||||||||||||||||||||||||||||||||||
| 3 github.com/modernice/goes/command/finish | ||||||||||||||||||||||||||||||||||||||||
| 4 github.com/modernice/goes/event/query/time | ||||||||||||||||||||||||||||||||||||||||
| 5 github.com/modernice/goes/event/query/version | ||||||||||||||||||||||||||||||||||||||||
| 6 ui.app.composables | ||||||||||||||||||||||||||||||||||||||||
| 7 github.com/modernice/goes/event | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 8 github.com/modernice/goes/eventstoreui | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 github.com/modernice/goes/aggregate/internal/softdelete | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 github.com/modernice/goes/backend/nats | 2 | 6 | ||||||||||||||||||||||||||||||||||||||
| 11 github.com/modernice/goes/backend/natsjs | 2 | 7 | ||||||||||||||||||||||||||||||||||||||
| 12 github.com/modernice/goes/backend/postgres | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 13 github.com/modernice/goes/backend/testing/eventbustest | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 14 github.com/modernice/goes/command | 2 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 github.com/modernice/goes/event/query | 3 | 3 | 10 | |||||||||||||||||||||||||||||||||||||
| 16 github.com/modernice/goes/projection | 1 | 21 | ||||||||||||||||||||||||||||||||||||||
| 17 github.com/modernice/goes/cli | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 18 github.com/modernice/goes/command/cmdbus | 3 | 1 | 3 | 9 | ||||||||||||||||||||||||||||||||||||
| 19 github.com/modernice/goes/command/handler | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 20 github.com/modernice/goes/event/handler | 5 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 github.com/modernice/goes/internal/projectiontest | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 22 github.com/modernice/goes/projection/schedule | 4 | 13 | ||||||||||||||||||||||||||||||||||||||
| 23 github.com/modernice/goes/aggregate | 1 | 10 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 github.com/modernice/goes/projection/lookup | 3 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 25 github.com/modernice/goes/aggregate/query | 5 | 1 | 8 | |||||||||||||||||||||||||||||||||||||
| 26 github.com/modernice/goes/aggregate/snapshot | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 27 github.com/modernice/goes/aggregate/stream | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 28 github.com/modernice/goes/command/builtin | 1 | 4 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 github.com/modernice/goes/contrib/auth | 1 | 24 | 5 | 4 | 2 | 3 | 9 | 3 | ||||||||||||||||||||||||||||||||
| 30 github.com/modernice/goes/saga/action | 3 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 github.com/modernice/goes/workflow | 4 | 10 | 4 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||
| 32 github.com/modernice/goes/aggregate/repository | 4 | 2 | 8 | 4 | ||||||||||||||||||||||||||||||||||||
| 33 github.com/modernice/goes/aggregate/snapshot/query | 3 | 1 | 5 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 34 github.com/modernice/goes/aggregate/snapshot/storetest | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 35 github.com/modernice/goes/backend/mongo | 3 | 1 | 1 | 11 | 1 | 5 | ||||||||||||||||||||||||||||||||||
| 36 github.com/modernice/goes/contrib/auth/authrpc | 1 | 2 | 9 | |||||||||||||||||||||||||||||||||||||
| 37 github.com/modernice/goes/contrib/auth/http/middleware | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 38 github.com/modernice/goes/saga/report | 4 | |||||||||||||||||||||||||||||||||||||||
| 39 github.com/modernice/goes/backend/mongo/mongotest | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 40 github.com/modernice/goes/saga | 2 | 2 | 2 | 6 | 1 |
7→2 github.com/modernice/goes/event uses github.com/modernice/goes/codec✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/event uses a type in github.com/modernice/goes/codec.
- The types involved
github.com/modernice/goes/event.event→github.com/modernice/goes/codec.Optiongithub.com/modernice/goes/event.event→github.com/modernice/goes/codec.Registry
- Direction
- github.com/modernice/goes/event uses github.com/modernice/goes/codec, so a change to github.com/modernice/goes/codec can break github.com/modernice/goes/event, while a change to github.com/modernice/goes/event can't break github.com/modernice/goes/codec.
- Position
- Below the diagonal: github.com/modernice/goes/event uses a module listed above it, which is the healthy direction.
7→4 github.com/modernice/goes/event uses github.com/modernice/goes/event/query/time✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/event uses a type in github.com/modernice/goes/event/query/time.
- The types involved
github.com/modernice/goes/event.Query→github.com/modernice/goes/event/query/time.Constraintsgithub.com/modernice/goes/event.event→github.com/modernice/goes/event/query/time.Range
- Direction
- github.com/modernice/goes/event uses github.com/modernice/goes/event/query/time, so a change to github.com/modernice/goes/event/query/time can break github.com/modernice/goes/event, while a change to github.com/modernice/goes/event can't break github.com/modernice/goes/event/query/time.
- Position
- Below the diagonal: github.com/modernice/goes/event uses a module listed above it, which is the healthy direction.
7→5 github.com/modernice/goes/event uses github.com/modernice/goes/event/query/version✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/event uses a type in github.com/modernice/goes/event/query/version.
- The types involved
github.com/modernice/goes/event.Query→github.com/modernice/goes/event/query/version.Constraintsgithub.com/modernice/goes/event.event→github.com/modernice/goes/event/query/version.Range
- Direction
- github.com/modernice/goes/event uses github.com/modernice/goes/event/query/version, so a change to github.com/modernice/goes/event/query/version can break github.com/modernice/goes/event, while a change to github.com/modernice/goes/event can't break github.com/modernice/goes/event/query/version.
- Position
- Below the diagonal: github.com/modernice/goes/event uses a module listed above it, which is the healthy direction.
8→2 github.com/modernice/goes/eventstoreui uses github.com/modernice/goes/codec✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/eventstoreui uses a type in github.com/modernice/goes/codec.
- The types involved
github.com/modernice/goes/eventstoreui.eventstoreui→github.com/modernice/goes/codec.Encoding
- Direction
- github.com/modernice/goes/eventstoreui uses github.com/modernice/goes/codec, so a change to github.com/modernice/goes/codec can break github.com/modernice/goes/eventstoreui, while a change to github.com/modernice/goes/eventstoreui can't break github.com/modernice/goes/codec.
- Position
- Below the diagonal: github.com/modernice/goes/eventstoreui uses a module listed above it, which is the healthy direction.
9→7 github.com/modernice/goes/aggregate/internal/softdelete uses github.com/modernice/goes/event✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/aggregate/internal/softdelete uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/aggregate/internal/softdelete.softdelete→github.com/modernice/goes/event.Of
- Direction
- github.com/modernice/goes/aggregate/internal/softdelete uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/aggregate/internal/softdelete, while a change to github.com/modernice/goes/aggregate/internal/softdelete can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/internal/softdelete uses a module listed above it, which is the healthy direction.
10→2 github.com/modernice/goes/backend/nats uses github.com/modernice/goes/codec✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/backend/nats uses a type in github.com/modernice/goes/codec.
- The types involved
github.com/modernice/goes/backend/nats.EventBus→github.com/modernice/goes/codec.Encodinggithub.com/modernice/goes/backend/nats.nats→github.com/modernice/goes/codec.Encoding
- Direction
- github.com/modernice/goes/backend/nats uses github.com/modernice/goes/codec, so a change to github.com/modernice/goes/codec can break github.com/modernice/goes/backend/nats, while a change to github.com/modernice/goes/backend/nats can't break github.com/modernice/goes/codec.
- Position
- Below the diagonal: github.com/modernice/goes/backend/nats uses a module listed above it, which is the healthy direction.
10→7 github.com/modernice/goes/backend/nats uses github.com/modernice/goes/event✕
- Connections
- 6 pairs of types, where a type in github.com/modernice/goes/backend/nats uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/backend/nats.Driver→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/backend/nats.EventBus→github.com/modernice/goes/event.Busgithub.com/modernice/goes/backend/nats.EventBus→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/backend/nats.core→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/backend/nats.jetStream→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/backend/nats.recipient→github.com/modernice/goes/event.Of
- Direction
- github.com/modernice/goes/backend/nats uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/backend/nats, while a change to github.com/modernice/goes/backend/nats can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/backend/nats uses a module listed above it, which is the healthy direction.
11→2 github.com/modernice/goes/backend/natsjs uses github.com/modernice/goes/codec✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/backend/natsjs uses a type in github.com/modernice/goes/codec.
- The types involved
github.com/modernice/goes/backend/natsjs.EventStore→github.com/modernice/goes/codec.Encodinggithub.com/modernice/goes/backend/natsjs.natsjs→github.com/modernice/goes/codec.Encoding
- Direction
- github.com/modernice/goes/backend/natsjs uses github.com/modernice/goes/codec, so a change to github.com/modernice/goes/codec can break github.com/modernice/goes/backend/natsjs, while a change to github.com/modernice/goes/backend/natsjs can't break github.com/modernice/goes/codec.
- Position
- Below the diagonal: github.com/modernice/goes/backend/natsjs uses a module listed above it, which is the healthy direction.
11→7 github.com/modernice/goes/backend/natsjs uses github.com/modernice/goes/event✕
- Connections
- 7 pairs of types, where a type in github.com/modernice/goes/backend/natsjs uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/backend/natsjs.EventStore→github.com/modernice/goes/event.Busgithub.com/modernice/goes/backend/natsjs.EventStore→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/backend/natsjs.EventStore→github.com/modernice/goes/event.Querygithub.com/modernice/goes/backend/natsjs.EventStore→github.com/modernice/goes/event.Storegithub.com/modernice/goes/backend/natsjs.natsjs→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/backend/natsjs.natsjs→github.com/modernice/goes/event.Querygithub.com/modernice/goes/backend/natsjs.subscription→github.com/modernice/goes/event.Of
- Direction
- github.com/modernice/goes/backend/natsjs uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/backend/natsjs, while a change to github.com/modernice/goes/backend/natsjs can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/backend/natsjs uses a module listed above it, which is the healthy direction.
12→2 github.com/modernice/goes/backend/postgres uses github.com/modernice/goes/codec✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/backend/postgres uses a type in github.com/modernice/goes/codec.
- The types involved
github.com/modernice/goes/backend/postgres.EventStore→github.com/modernice/goes/codec.Encodinggithub.com/modernice/goes/backend/postgres.postgres→github.com/modernice/goes/codec.Encoding
- Direction
- github.com/modernice/goes/backend/postgres uses github.com/modernice/goes/codec, so a change to github.com/modernice/goes/codec can break github.com/modernice/goes/backend/postgres, while a change to github.com/modernice/goes/backend/postgres can't break github.com/modernice/goes/codec.
- Position
- Below the diagonal: github.com/modernice/goes/backend/postgres uses a module listed above it, which is the healthy direction.
12→7 github.com/modernice/goes/backend/postgres uses github.com/modernice/goes/event✕
- Connections
- 3 pairs of types, where a type in github.com/modernice/goes/backend/postgres uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/backend/postgres.EventStore→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/backend/postgres.EventStore→github.com/modernice/goes/event.Querygithub.com/modernice/goes/backend/postgres.EventStore→github.com/modernice/goes/event.Store
- Direction
- github.com/modernice/goes/backend/postgres uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/backend/postgres, while a change to github.com/modernice/goes/backend/postgres can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/backend/postgres uses a module listed above it, which is the healthy direction.
13→2 github.com/modernice/goes/backend/testing/eventbustest uses github.com/modernice/goes/codec✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/backend/testing/eventbustest uses a type in github.com/modernice/goes/codec.
- The types involved
github.com/modernice/goes/backend/testing/eventbustest.eventbustest→github.com/modernice/goes/codec.Registry
- Direction
- github.com/modernice/goes/backend/testing/eventbustest uses github.com/modernice/goes/codec, so a change to github.com/modernice/goes/codec can break github.com/modernice/goes/backend/testing/eventbustest, while a change to github.com/modernice/goes/backend/testing/eventbustest can't break github.com/modernice/goes/codec.
- Position
- Below the diagonal: github.com/modernice/goes/backend/testing/eventbustest uses a module listed above it, which is the healthy direction.
13→7 github.com/modernice/goes/backend/testing/eventbustest uses github.com/modernice/goes/event✕
- Connections
- 3 pairs of types, where a type in github.com/modernice/goes/backend/testing/eventbustest uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/backend/testing/eventbustest.Subscription→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/backend/testing/eventbustest.config→github.com/modernice/goes/event.Busgithub.com/modernice/goes/backend/testing/eventbustest.eventbustest→github.com/modernice/goes/event.Of
- Direction
- github.com/modernice/goes/backend/testing/eventbustest uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/backend/testing/eventbustest, while a change to github.com/modernice/goes/backend/testing/eventbustest can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/backend/testing/eventbustest uses a module listed above it, which is the healthy direction.
14→2 github.com/modernice/goes/command uses github.com/modernice/goes/codec✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/command uses a type in github.com/modernice/goes/codec.
- The types involved
github.com/modernice/goes/command.command→github.com/modernice/goes/codec.Optiongithub.com/modernice/goes/command.command→github.com/modernice/goes/codec.Registry
- Direction
- github.com/modernice/goes/command uses github.com/modernice/goes/codec, so a change to github.com/modernice/goes/codec can break github.com/modernice/goes/command, while a change to github.com/modernice/goes/command can't break github.com/modernice/goes/codec.
- Position
- Below the diagonal: github.com/modernice/goes/command uses a module listed above it, which is the healthy direction.
14→3 github.com/modernice/goes/command uses github.com/modernice/goes/command/finish✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/command uses a type in github.com/modernice/goes/command/finish.
- The types involved
github.com/modernice/goes/command.Ctx→github.com/modernice/goes/command/finish.Optiongithub.com/modernice/goes/command.cmdctx→github.com/modernice/goes/command/finish.Option
- Direction
- github.com/modernice/goes/command uses github.com/modernice/goes/command/finish, so a change to github.com/modernice/goes/command/finish can break github.com/modernice/goes/command, while a change to github.com/modernice/goes/command can't break github.com/modernice/goes/command/finish.
- Position
- Below the diagonal: github.com/modernice/goes/command uses a module listed above it, which is the healthy direction.
14→7 github.com/modernice/goes/command uses github.com/modernice/goes/event✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/command uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/command.Cmd→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/command.Of→github.com/modernice/goes/event.AggregateRef
- Direction
- github.com/modernice/goes/command uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/command, while a change to github.com/modernice/goes/command can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/command uses a module listed above it, which is the healthy direction.
14→19 github.com/modernice/goes/command uses github.com/modernice/goes/command/handler part of a loop✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/command uses a type in github.com/modernice/goes/command/handler.
- The types involved
github.com/modernice/goes/command.Handlers→github.com/modernice/goes/command/handler.Aggregate
- Direction
- github.com/modernice/goes/command uses github.com/modernice/goes/command/handler, so a change to github.com/modernice/goes/command/handler can break github.com/modernice/goes/command, while a change to github.com/modernice/goes/command can't break github.com/modernice/goes/command/handler.
- 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.
15→4 github.com/modernice/goes/event/query uses github.com/modernice/goes/event/query/time✕
- Connections
- 3 pairs of types, where a type in github.com/modernice/goes/event/query uses a type in github.com/modernice/goes/event/query/time.
- The types involved
github.com/modernice/goes/event/query.Query→github.com/modernice/goes/event/query/time.Constraintsgithub.com/modernice/goes/event/query.builder→github.com/modernice/goes/event/query/time.Optiongithub.com/modernice/goes/event/query.query→github.com/modernice/goes/event/query/time.Option
- Direction
- github.com/modernice/goes/event/query uses github.com/modernice/goes/event/query/time, so a change to github.com/modernice/goes/event/query/time can break github.com/modernice/goes/event/query, while a change to github.com/modernice/goes/event/query can't break github.com/modernice/goes/event/query/time.
- Position
- Below the diagonal: github.com/modernice/goes/event/query uses a module listed above it, which is the healthy direction.
15→5 github.com/modernice/goes/event/query uses github.com/modernice/goes/event/query/version✕
- Connections
- 3 pairs of types, where a type in github.com/modernice/goes/event/query uses a type in github.com/modernice/goes/event/query/version.
- The types involved
github.com/modernice/goes/event/query.Query→github.com/modernice/goes/event/query/version.Constraintsgithub.com/modernice/goes/event/query.builder→github.com/modernice/goes/event/query/version.Optiongithub.com/modernice/goes/event/query.query→github.com/modernice/goes/event/query/version.Option
- Direction
- github.com/modernice/goes/event/query uses github.com/modernice/goes/event/query/version, so a change to github.com/modernice/goes/event/query/version can break github.com/modernice/goes/event/query, while a change to github.com/modernice/goes/event/query can't break github.com/modernice/goes/event/query/version.
- Position
- Below the diagonal: github.com/modernice/goes/event/query uses a module listed above it, which is the healthy direction.
15→7 github.com/modernice/goes/event/query uses github.com/modernice/goes/event✕
- Connections
- 10 pairs of types, where a type in github.com/modernice/goes/event/query uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/event/query.Query→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/event/query.Query→github.com/modernice/goes/event.Querygithub.com/modernice/goes/event/query.Query→github.com/modernice/goes/event.SortOptionsgithub.com/modernice/goes/event/query.builder→github.com/modernice/goes/event.Querygithub.com/modernice/goes/event/query.query→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/event/query.query→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/event/query.query→github.com/modernice/goes/event.Querygithub.com/modernice/goes/event/query.query→github.com/modernice/goes/event.SortDirectiongithub.com/modernice/goes/event/query.query→github.com/modernice/goes/event.SortOptionsgithub.com/modernice/goes/event/query.query→github.com/modernice/goes/event.Sorting
- Direction
- github.com/modernice/goes/event/query uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/event/query, while a change to github.com/modernice/goes/event/query can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/event/query uses a module listed above it, which is the healthy direction.
16→2 github.com/modernice/goes/projection uses github.com/modernice/goes/codec✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/projection uses a type in github.com/modernice/goes/codec.
- The types involved
github.com/modernice/goes/projection.projection→github.com/modernice/goes/codec.Registerer
- Direction
- github.com/modernice/goes/projection uses github.com/modernice/goes/codec, so a change to github.com/modernice/goes/codec can break github.com/modernice/goes/projection, while a change to github.com/modernice/goes/projection can't break github.com/modernice/goes/codec.
- Position
- Below the diagonal: github.com/modernice/goes/projection uses a module listed above it, which is the healthy direction.
16→7 github.com/modernice/goes/projection uses github.com/modernice/goes/event✕
- Connections
- 21 pairs of types, where a type in github.com/modernice/goes/projection uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/projection.Base→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/projection.Guard→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/projection.GuardFunc→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/projection.Job→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/projection.Job→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/projection.Job→github.com/modernice/goes/event.Querygithub.com/modernice/goes/projection.QueryGuard→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/projection.Service→github.com/modernice/goes/event.Busgithub.com/modernice/goes/projection.Service→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/projection.Target→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/projection.Trigger→github.com/modernice/goes/event.Querygithub.com/modernice/goes/projection.job→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/projection.job→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/projection.job→github.com/modernice/goes/event.Querygithub.com/modernice/goes/projection.projection→github.com/modernice/goes/event.Busgithub.com/modernice/goes/projection.projection→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/projection.projection→github.com/modernice/goes/event.Querygithub.com/modernice/goes/projection.projection→github.com/modernice/goes/event.Storegithub.com/modernice/goes/projection.queryCache→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/projection.queryCache→github.com/modernice/goes/event.Querygithub.com/modernice/goes/projection.queryCache→github.com/modernice/goes/event.Store
- Direction
- github.com/modernice/goes/projection uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/projection, while a change to github.com/modernice/goes/projection can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/projection uses a module listed above it, which is the healthy direction.
17→1 github.com/modernice/goes/cli uses github.com/modernice/goes/cli/internal/clifactory✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/cli uses a type in github.com/modernice/goes/cli/internal/clifactory.
- The types involved
github.com/modernice/goes/cli.App→github.com/modernice/goes/cli/internal/clifactory.Factorygithub.com/modernice/goes/cli.cli→github.com/modernice/goes/cli/internal/clifactory.Option
- Direction
- github.com/modernice/goes/cli uses github.com/modernice/goes/cli/internal/clifactory, so a change to github.com/modernice/goes/cli/internal/clifactory can break github.com/modernice/goes/cli, while a change to github.com/modernice/goes/cli can't break github.com/modernice/goes/cli/internal/clifactory.
- Position
- Below the diagonal: github.com/modernice/goes/cli uses a module listed above it, which is the healthy direction.
17→16 github.com/modernice/goes/cli uses github.com/modernice/goes/projection✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/cli uses a type in github.com/modernice/goes/projection.
- The types involved
github.com/modernice/goes/cli.Connector→github.com/modernice/goes/projection.Servicegithub.com/modernice/goes/cli.cli→github.com/modernice/goes/projection.Service
- Direction
- github.com/modernice/goes/cli uses github.com/modernice/goes/projection, so a change to github.com/modernice/goes/projection can break github.com/modernice/goes/cli, while a change to github.com/modernice/goes/cli can't break github.com/modernice/goes/projection.
- Position
- Below the diagonal: github.com/modernice/goes/cli uses a module listed above it, which is the healthy direction.
18→2 github.com/modernice/goes/command/cmdbus uses github.com/modernice/goes/codec✕
- Connections
- 3 pairs of types, where a type in github.com/modernice/goes/command/cmdbus uses a type in github.com/modernice/goes/codec.
- The types involved
github.com/modernice/goes/command/cmdbus.Bus→github.com/modernice/goes/codec.Encodinggithub.com/modernice/goes/command/cmdbus.cmdbus→github.com/modernice/goes/codec.Encodinggithub.com/modernice/goes/command/cmdbus.cmdbus→github.com/modernice/goes/codec.Registerer
- Direction
- github.com/modernice/goes/command/cmdbus uses github.com/modernice/goes/codec, so a change to github.com/modernice/goes/codec can break github.com/modernice/goes/command/cmdbus, while a change to github.com/modernice/goes/command/cmdbus can't break github.com/modernice/goes/codec.
- Position
- Below the diagonal: github.com/modernice/goes/command/cmdbus uses a module listed above it, which is the healthy direction.
18→3 github.com/modernice/goes/command/cmdbus uses github.com/modernice/goes/command/finish✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/command/cmdbus uses a type in github.com/modernice/goes/command/finish.
- The types involved
github.com/modernice/goes/command/cmdbus.Bus→github.com/modernice/goes/command/finish.Config
- Direction
- github.com/modernice/goes/command/cmdbus uses github.com/modernice/goes/command/finish, so a change to github.com/modernice/goes/command/finish can break github.com/modernice/goes/command/cmdbus, while a change to github.com/modernice/goes/command/cmdbus can't break github.com/modernice/goes/command/finish.
- Position
- Below the diagonal: github.com/modernice/goes/command/cmdbus uses a module listed above it, which is the healthy direction.
18→7 github.com/modernice/goes/command/cmdbus uses github.com/modernice/goes/event✕
- Connections
- 3 pairs of types, where a type in github.com/modernice/goes/command/cmdbus uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/command/cmdbus.Bus→github.com/modernice/goes/event.Busgithub.com/modernice/goes/command/cmdbus.Bus→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/command/cmdbus.cmdbus→github.com/modernice/goes/event.Bus
- Direction
- github.com/modernice/goes/command/cmdbus uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/command/cmdbus, while a change to github.com/modernice/goes/command/cmdbus can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/command/cmdbus uses a module listed above it, which is the healthy direction.
18→14 github.com/modernice/goes/command/cmdbus uses github.com/modernice/goes/command✕
- Connections
- 9 pairs of types, where a type in github.com/modernice/goes/command/cmdbus uses a type in github.com/modernice/goes/command.
- The types involved
github.com/modernice/goes/command/cmdbus.Bus→github.com/modernice/goes/command.Busgithub.com/modernice/goes/command/cmdbus.Bus→github.com/modernice/goes/command.Cmdgithub.com/modernice/goes/command/cmdbus.Bus→github.com/modernice/goes/command.Ctxgithub.com/modernice/goes/command/cmdbus.Bus→github.com/modernice/goes/command.DispatchOptiongithub.com/modernice/goes/command/cmdbus.Bus→github.com/modernice/goes/command.Ofgithub.com/modernice/goes/command/cmdbus.ExecutionError→github.com/modernice/goes/command.Ofgithub.com/modernice/goes/command/cmdbus.dispatcher→github.com/modernice/goes/command.DispatchConfiggithub.com/modernice/goes/command/cmdbus.dispatcher→github.com/modernice/goes/command.Ofgithub.com/modernice/goes/command/cmdbus.subscription→github.com/modernice/goes/command.Ctx
- Direction
- github.com/modernice/goes/command/cmdbus uses github.com/modernice/goes/command, so a change to github.com/modernice/goes/command can break github.com/modernice/goes/command/cmdbus, while a change to github.com/modernice/goes/command/cmdbus can't break github.com/modernice/goes/command.
- Position
- Below the diagonal: github.com/modernice/goes/command/cmdbus uses a module listed above it, which is the healthy direction.
19→14 github.com/modernice/goes/command/handler uses github.com/modernice/goes/command✕
- Connections
- 3 pairs of types, where a type in github.com/modernice/goes/command/handler uses a type in github.com/modernice/goes/command.
- The types involved
github.com/modernice/goes/command/handler.Aggregate→github.com/modernice/goes/command.Ctxgithub.com/modernice/goes/command/handler.Of→github.com/modernice/goes/command.Handlergithub.com/modernice/goes/command/handler.handler→github.com/modernice/goes/command.Bus
- Direction
- github.com/modernice/goes/command/handler uses github.com/modernice/goes/command, so a change to github.com/modernice/goes/command can break github.com/modernice/goes/command/handler, while a change to github.com/modernice/goes/command/handler can't break github.com/modernice/goes/command.
- Position
- Below the diagonal: github.com/modernice/goes/command/handler uses a module listed above it, which is the healthy direction.
19→23 github.com/modernice/goes/command/handler uses github.com/modernice/goes/aggregate part of a loop✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/command/handler uses a type in github.com/modernice/goes/aggregate.
- The types involved
github.com/modernice/goes/command/handler.Of→github.com/modernice/goes/aggregate.Repositorygithub.com/modernice/goes/command/handler.handler→github.com/modernice/goes/aggregate.Repository
- Direction
- github.com/modernice/goes/command/handler uses github.com/modernice/goes/aggregate, so a change to github.com/modernice/goes/aggregate can break github.com/modernice/goes/command/handler, while a change to github.com/modernice/goes/command/handler can't break github.com/modernice/goes/aggregate.
- 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.
20→7 github.com/modernice/goes/event/handler uses github.com/modernice/goes/event✕
- Connections
- 5 pairs of types, where a type in github.com/modernice/goes/event/handler uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/event/handler.Handler→github.com/modernice/goes/event.Busgithub.com/modernice/goes/event/handler.Handler→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/event/handler.Handler→github.com/modernice/goes/event.Storegithub.com/modernice/goes/event/handler.handler→github.com/modernice/goes/event.Busgithub.com/modernice/goes/event/handler.handler→github.com/modernice/goes/event.Store
- Direction
- github.com/modernice/goes/event/handler uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/event/handler, while a change to github.com/modernice/goes/event/handler can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/event/handler uses a module listed above it, which is the healthy direction.
20→15 github.com/modernice/goes/event/handler uses github.com/modernice/goes/event/query✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/event/handler uses a type in github.com/modernice/goes/event/query.
- The types involved
github.com/modernice/goes/event/handler.handler→github.com/modernice/goes/event/query.Optiongithub.com/modernice/goes/event/handler.handler→github.com/modernice/goes/event/query.Query
- Direction
- github.com/modernice/goes/event/handler uses github.com/modernice/goes/event/query, so a change to github.com/modernice/goes/event/query can break github.com/modernice/goes/event/handler, while a change to github.com/modernice/goes/event/handler can't break github.com/modernice/goes/event/query.
- Position
- Below the diagonal: github.com/modernice/goes/event/handler uses a module listed above it, which is the healthy direction.
21→7 github.com/modernice/goes/internal/projectiontest uses github.com/modernice/goes/event✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/internal/projectiontest uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/internal/projectiontest.MockProjection→github.com/modernice/goes/event.Of
- Direction
- github.com/modernice/goes/internal/projectiontest uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/internal/projectiontest, while a change to github.com/modernice/goes/internal/projectiontest can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/internal/projectiontest uses a module listed above it, which is the healthy direction.
21→16 github.com/modernice/goes/internal/projectiontest uses github.com/modernice/goes/projection✕
- Connections
- 3 pairs of types, where a type in github.com/modernice/goes/internal/projectiontest uses a type in github.com/modernice/goes/projection.
- The types involved
github.com/modernice/goes/internal/projectiontest.MockProgressor→github.com/modernice/goes/projection.ProgressAwaregithub.com/modernice/goes/internal/projectiontest.MockResetProjection→github.com/modernice/goes/projection.ProgressAwaregithub.com/modernice/goes/internal/projectiontest.projectiontest→github.com/modernice/goes/projection.QueryGuard
- Direction
- github.com/modernice/goes/internal/projectiontest uses github.com/modernice/goes/projection, so a change to github.com/modernice/goes/projection can break github.com/modernice/goes/internal/projectiontest, while a change to github.com/modernice/goes/internal/projectiontest can't break github.com/modernice/goes/projection.
- Position
- Below the diagonal: github.com/modernice/goes/internal/projectiontest uses a module listed above it, which is the healthy direction.
22→7 github.com/modernice/goes/projection/schedule uses github.com/modernice/goes/event✕
- Connections
- 4 pairs of types, where a type in github.com/modernice/goes/projection/schedule uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/projection/schedule.Continuous→github.com/modernice/goes/event.Busgithub.com/modernice/goes/projection/schedule.Continuous→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/projection/schedule.schedule→github.com/modernice/goes/event.Querygithub.com/modernice/goes/projection/schedule.schedule→github.com/modernice/goes/event.Store
- Direction
- github.com/modernice/goes/projection/schedule uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/projection/schedule, while a change to github.com/modernice/goes/projection/schedule can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/projection/schedule uses a module listed above it, which is the healthy direction.
22→16 github.com/modernice/goes/projection/schedule uses github.com/modernice/goes/projection✕
- Connections
- 13 pairs of types, where a type in github.com/modernice/goes/projection/schedule uses a type in github.com/modernice/goes/projection.
- The types involved
github.com/modernice/goes/projection/schedule.Continuous→github.com/modernice/goes/projection.Jobgithub.com/modernice/goes/projection/schedule.Continuous→github.com/modernice/goes/projection.Schedulegithub.com/modernice/goes/projection/schedule.Continuous→github.com/modernice/goes/projection.SubscribeOptiongithub.com/modernice/goes/projection/schedule.Continuous→github.com/modernice/goes/projection.Subscriptiongithub.com/modernice/goes/projection/schedule.Periodic→github.com/modernice/goes/projection.Jobgithub.com/modernice/goes/projection/schedule.Periodic→github.com/modernice/goes/projection.Schedulegithub.com/modernice/goes/projection/schedule.Periodic→github.com/modernice/goes/projection.SubscribeOptiongithub.com/modernice/goes/projection/schedule.Periodic→github.com/modernice/goes/projection.Subscriptiongithub.com/modernice/goes/projection/schedule.schedule→github.com/modernice/goes/projection.Jobgithub.com/modernice/goes/projection/schedule.schedule→github.com/modernice/goes/projection.JobOptiongithub.com/modernice/goes/projection/schedule.schedule→github.com/modernice/goes/projection.Subscriptiongithub.com/modernice/goes/projection/schedule.schedule→github.com/modernice/goes/projection.Triggergithub.com/modernice/goes/projection/schedule.schedule→github.com/modernice/goes/projection.TriggerOption
- Direction
- github.com/modernice/goes/projection/schedule uses github.com/modernice/goes/projection, so a change to github.com/modernice/goes/projection can break github.com/modernice/goes/projection/schedule, while a change to github.com/modernice/goes/projection/schedule can't break github.com/modernice/goes/projection.
- Position
- Below the diagonal: github.com/modernice/goes/projection/schedule uses a module listed above it, which is the healthy direction.
23→5 github.com/modernice/goes/aggregate uses github.com/modernice/goes/event/query/version✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/aggregate uses a type in github.com/modernice/goes/event/query/version.
- The types involved
github.com/modernice/goes/aggregate.Query→github.com/modernice/goes/event/query/version.Constraints
- Direction
- github.com/modernice/goes/aggregate uses github.com/modernice/goes/event/query/version, so a change to github.com/modernice/goes/event/query/version can break github.com/modernice/goes/aggregate, while a change to github.com/modernice/goes/aggregate can't break github.com/modernice/goes/event/query/version.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate uses a module listed above it, which is the healthy direction.
23→7 github.com/modernice/goes/aggregate uses github.com/modernice/goes/event✕
- Connections
- 10 pairs of types, where a type in github.com/modernice/goes/aggregate uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/aggregate.Base→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/aggregate.Base→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/aggregate.Committer→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/aggregate.ConsistencyError→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/aggregate.ConsistencyError→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/aggregate.History→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/aggregate.Of→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/aggregate.aggregate→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/aggregate.aggregate→github.com/modernice/goes/event.Evtgithub.com/modernice/goes/aggregate.aggregate→github.com/modernice/goes/event.Option
- Direction
- github.com/modernice/goes/aggregate uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/aggregate, while a change to github.com/modernice/goes/aggregate can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate uses a module listed above it, which is the healthy direction.
23→19 github.com/modernice/goes/aggregate uses github.com/modernice/goes/command/handler✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/aggregate uses a type in github.com/modernice/goes/command/handler.
- The types involved
github.com/modernice/goes/aggregate.Base→github.com/modernice/goes/command/handler.Aggregate
- Direction
- github.com/modernice/goes/aggregate uses github.com/modernice/goes/command/handler, so a change to github.com/modernice/goes/command/handler can break github.com/modernice/goes/aggregate, while a change to github.com/modernice/goes/aggregate can't break github.com/modernice/goes/command/handler.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate uses a module listed above it, which is the healthy direction.
24→7 github.com/modernice/goes/projection/lookup uses github.com/modernice/goes/event✕
- Connections
- 3 pairs of types, where a type in github.com/modernice/goes/projection/lookup uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/projection/lookup.Lookup→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/projection/lookup.lookup→github.com/modernice/goes/event.Busgithub.com/modernice/goes/projection/lookup.lookup→github.com/modernice/goes/event.Store
- Direction
- github.com/modernice/goes/projection/lookup uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/projection/lookup, while a change to github.com/modernice/goes/projection/lookup can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/projection/lookup uses a module listed above it, which is the healthy direction.
24→16 github.com/modernice/goes/projection/lookup uses github.com/modernice/goes/projection✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/projection/lookup uses a type in github.com/modernice/goes/projection.
- The types involved
github.com/modernice/goes/projection/lookup.Lookup→github.com/modernice/goes/projection.Job
- Direction
- github.com/modernice/goes/projection/lookup uses github.com/modernice/goes/projection, so a change to github.com/modernice/goes/projection can break github.com/modernice/goes/projection/lookup, while a change to github.com/modernice/goes/projection/lookup can't break github.com/modernice/goes/projection.
- Position
- Below the diagonal: github.com/modernice/goes/projection/lookup uses a module listed above it, which is the healthy direction.
24→22 github.com/modernice/goes/projection/lookup uses github.com/modernice/goes/projection/schedule✕
- Connections
- 3 pairs of types, where a type in github.com/modernice/goes/projection/lookup uses a type in github.com/modernice/goes/projection/schedule.
- The types involved
github.com/modernice/goes/projection/lookup.Lookup→github.com/modernice/goes/projection/schedule.Continuousgithub.com/modernice/goes/projection/lookup.Lookup→github.com/modernice/goes/projection/schedule.ContinuousOptiongithub.com/modernice/goes/projection/lookup.lookup→github.com/modernice/goes/projection/schedule.ContinuousOption
- Direction
- github.com/modernice/goes/projection/lookup uses github.com/modernice/goes/projection/schedule, so a change to github.com/modernice/goes/projection/schedule can break github.com/modernice/goes/projection/lookup, while a change to github.com/modernice/goes/projection/lookup can't break github.com/modernice/goes/projection/schedule.
- Position
- Below the diagonal: github.com/modernice/goes/projection/lookup uses a module listed above it, which is the healthy direction.
25→5 github.com/modernice/goes/aggregate/query uses github.com/modernice/goes/event/query/version✕
- Connections
- 5 pairs of types, where a type in github.com/modernice/goes/aggregate/query uses a type in github.com/modernice/goes/event/query/version.
- The types involved
github.com/modernice/goes/aggregate/query.Q→github.com/modernice/goes/event/query/version.Constraintsgithub.com/modernice/goes/aggregate/query.Query→github.com/modernice/goes/event/query/version.Constraintsgithub.com/modernice/goes/aggregate/query.Query→github.com/modernice/goes/event/query/version.Optiongithub.com/modernice/goes/aggregate/query.query→github.com/modernice/goes/event/query/version.Optiongithub.com/modernice/goes/aggregate/query.query→github.com/modernice/goes/event/query/version.Range
- Direction
- github.com/modernice/goes/aggregate/query uses github.com/modernice/goes/event/query/version, so a change to github.com/modernice/goes/event/query/version can break github.com/modernice/goes/aggregate/query, while a change to github.com/modernice/goes/aggregate/query can't break github.com/modernice/goes/event/query/version.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/query uses a module listed above it, which is the healthy direction.
25→15 github.com/modernice/goes/aggregate/query uses github.com/modernice/goes/event/query✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/aggregate/query uses a type in github.com/modernice/goes/event/query.
- The types involved
github.com/modernice/goes/aggregate/query.query→github.com/modernice/goes/event/query.Option
- Direction
- github.com/modernice/goes/aggregate/query uses github.com/modernice/goes/event/query, so a change to github.com/modernice/goes/event/query can break github.com/modernice/goes/aggregate/query, while a change to github.com/modernice/goes/aggregate/query can't break github.com/modernice/goes/event/query.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/query uses a module listed above it, which is the healthy direction.
25→23 github.com/modernice/goes/aggregate/query uses github.com/modernice/goes/aggregate✕
- Connections
- 8 pairs of types, where a type in github.com/modernice/goes/aggregate/query uses a type in github.com/modernice/goes/aggregate.
- The types involved
github.com/modernice/goes/aggregate/query.Q→github.com/modernice/goes/aggregate.SortOptionsgithub.com/modernice/goes/aggregate/query.Query→github.com/modernice/goes/aggregate.Querygithub.com/modernice/goes/aggregate/query.Query→github.com/modernice/goes/aggregate.SortOptionsgithub.com/modernice/goes/aggregate/query.query→github.com/modernice/goes/aggregate.Querygithub.com/modernice/goes/aggregate/query.query→github.com/modernice/goes/aggregate.SortDirectiongithub.com/modernice/goes/aggregate/query.query→github.com/modernice/goes/aggregate.SortOptionsgithub.com/modernice/goes/aggregate/query.query→github.com/modernice/goes/aggregate.Sortinggithub.com/modernice/goes/aggregate/query.queryWithTags→github.com/modernice/goes/aggregate.Query
- Direction
- github.com/modernice/goes/aggregate/query uses github.com/modernice/goes/aggregate, so a change to github.com/modernice/goes/aggregate can break github.com/modernice/goes/aggregate/query, while a change to github.com/modernice/goes/aggregate/query can't break github.com/modernice/goes/aggregate.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/query uses a module listed above it, which is the healthy direction.
26→4 github.com/modernice/goes/aggregate/snapshot uses github.com/modernice/goes/event/query/time✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/aggregate/snapshot uses a type in github.com/modernice/goes/event/query/time.
- The types involved
github.com/modernice/goes/aggregate/snapshot.Query→github.com/modernice/goes/event/query/time.Constraintsgithub.com/modernice/goes/aggregate/snapshot.snapshot→github.com/modernice/goes/event/query/time.Range
- Direction
- github.com/modernice/goes/aggregate/snapshot uses github.com/modernice/goes/event/query/time, so a change to github.com/modernice/goes/event/query/time can break github.com/modernice/goes/aggregate/snapshot, while a change to github.com/modernice/goes/aggregate/snapshot can't break github.com/modernice/goes/event/query/time.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/snapshot uses a module listed above it, which is the healthy direction.
26→23 github.com/modernice/goes/aggregate/snapshot uses github.com/modernice/goes/aggregate✕
- Connections
- 4 pairs of types, where a type in github.com/modernice/goes/aggregate/snapshot uses a type in github.com/modernice/goes/aggregate.
- The types involved
github.com/modernice/goes/aggregate/snapshot.Query→github.com/modernice/goes/aggregate.Querygithub.com/modernice/goes/aggregate/snapshot.snapshot→github.com/modernice/goes/aggregate.SortDirectiongithub.com/modernice/goes/aggregate/snapshot.snapshot→github.com/modernice/goes/aggregate.SortOptionsgithub.com/modernice/goes/aggregate/snapshot.snapshot→github.com/modernice/goes/aggregate.Sorting
- Direction
- github.com/modernice/goes/aggregate/snapshot uses github.com/modernice/goes/aggregate, so a change to github.com/modernice/goes/aggregate can break github.com/modernice/goes/aggregate/snapshot, while a change to github.com/modernice/goes/aggregate/snapshot can't break github.com/modernice/goes/aggregate.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/snapshot uses a module listed above it, which is the healthy direction.
27→7 github.com/modernice/goes/aggregate/stream uses github.com/modernice/goes/event✕
- Connections
- 4 pairs of types, where a type in github.com/modernice/goes/aggregate/stream uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/aggregate/stream.applier→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/aggregate/stream.groupRequest→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/aggregate/stream.stream→github.com/modernice/goes/event.Evtgithub.com/modernice/goes/aggregate/stream.stream→github.com/modernice/goes/event.Of
- Direction
- github.com/modernice/goes/aggregate/stream uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/aggregate/stream, while a change to github.com/modernice/goes/aggregate/stream can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/stream uses a module listed above it, which is the healthy direction.
27→23 github.com/modernice/goes/aggregate/stream uses github.com/modernice/goes/aggregate✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/aggregate/stream uses a type in github.com/modernice/goes/aggregate.
- The types involved
github.com/modernice/goes/aggregate/stream.applier→github.com/modernice/goes/aggregate.Historygithub.com/modernice/goes/aggregate/stream.stream→github.com/modernice/goes/aggregate.History
- Direction
- github.com/modernice/goes/aggregate/stream uses github.com/modernice/goes/aggregate, so a change to github.com/modernice/goes/aggregate can break github.com/modernice/goes/aggregate/stream, while a change to github.com/modernice/goes/aggregate/stream can't break github.com/modernice/goes/aggregate.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/stream uses a module listed above it, which is the healthy direction.
28→2 github.com/modernice/goes/command/builtin uses github.com/modernice/goes/codec✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/command/builtin uses a type in github.com/modernice/goes/codec.
- The types involved
github.com/modernice/goes/command/builtin.builtin→github.com/modernice/goes/codec.Registerer
- Direction
- github.com/modernice/goes/command/builtin uses github.com/modernice/goes/codec, so a change to github.com/modernice/goes/codec can break github.com/modernice/goes/command/builtin, while a change to github.com/modernice/goes/command/builtin can't break github.com/modernice/goes/codec.
- Position
- Below the diagonal: github.com/modernice/goes/command/builtin uses a module listed above it, which is the healthy direction.
28→7 github.com/modernice/goes/command/builtin uses github.com/modernice/goes/event✕
- Connections
- 4 pairs of types, where a type in github.com/modernice/goes/command/builtin uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/command/builtin.builtin→github.com/modernice/goes/event.Busgithub.com/modernice/goes/command/builtin.builtin→github.com/modernice/goes/event.Storegithub.com/modernice/goes/command/builtin.handleConfig→github.com/modernice/goes/event.Busgithub.com/modernice/goes/command/builtin.handleConfig→github.com/modernice/goes/event.Store
- Direction
- github.com/modernice/goes/command/builtin uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/command/builtin, while a change to github.com/modernice/goes/command/builtin can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/command/builtin uses a module listed above it, which is the healthy direction.
28→14 github.com/modernice/goes/command/builtin uses github.com/modernice/goes/command✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/command/builtin uses a type in github.com/modernice/goes/command.
- The types involved
github.com/modernice/goes/command/builtin.builtin→github.com/modernice/goes/command.Busgithub.com/modernice/goes/command/builtin.builtin→github.com/modernice/goes/command.Cmd
- Direction
- github.com/modernice/goes/command/builtin uses github.com/modernice/goes/command, so a change to github.com/modernice/goes/command can break github.com/modernice/goes/command/builtin, while a change to github.com/modernice/goes/command/builtin can't break github.com/modernice/goes/command.
- Position
- Below the diagonal: github.com/modernice/goes/command/builtin uses a module listed above it, which is the healthy direction.
28→23 github.com/modernice/goes/command/builtin uses github.com/modernice/goes/aggregate✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/command/builtin uses a type in github.com/modernice/goes/aggregate.
- The types involved
github.com/modernice/goes/command/builtin.builtin→github.com/modernice/goes/aggregate.Repository
- Direction
- github.com/modernice/goes/command/builtin uses github.com/modernice/goes/aggregate, so a change to github.com/modernice/goes/aggregate can break github.com/modernice/goes/command/builtin, while a change to github.com/modernice/goes/command/builtin can't break github.com/modernice/goes/aggregate.
- Position
- Below the diagonal: github.com/modernice/goes/command/builtin uses a module listed above it, which is the healthy direction.
29→2 github.com/modernice/goes/contrib/auth uses github.com/modernice/goes/codec✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/contrib/auth uses a type in github.com/modernice/goes/codec.
- The types involved
github.com/modernice/goes/contrib/auth.auth→github.com/modernice/goes/codec.Registerer
- Direction
- github.com/modernice/goes/contrib/auth uses github.com/modernice/goes/codec, so a change to github.com/modernice/goes/codec can break github.com/modernice/goes/contrib/auth, while a change to github.com/modernice/goes/contrib/auth can't break github.com/modernice/goes/codec.
- Position
- Below the diagonal: github.com/modernice/goes/contrib/auth uses a module listed above it, which is the healthy direction.
29→7 github.com/modernice/goes/contrib/auth uses github.com/modernice/goes/event✕
- Connections
- 24 pairs of types, where a type in github.com/modernice/goes/contrib/auth uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/contrib/auth.Actions→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/contrib/auth.Actions→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/contrib/auth.Actor→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/contrib/auth.Actor→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/contrib/auth.CommandClient→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/contrib/auth.Granter→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/contrib/auth.PermissionGrantedData→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/contrib/auth.PermissionRevokedData→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/contrib/auth.Permissions→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/contrib/auth.PermissionsDTO→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/contrib/auth.QueryClient→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/contrib/auth.Role→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/contrib/auth.Role→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/contrib/auth.TargetedGranter→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/contrib/auth.auth→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/contrib/auth.auth→github.com/modernice/goes/event.Busgithub.com/modernice/goes/contrib/auth.auth→github.com/modernice/goes/event.Storegithub.com/modernice/goes/contrib/auth.commandBusClient→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/contrib/auth.grantActorPayload→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/contrib/auth.grantRolePayload→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/contrib/auth.repositoryCommandClient→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/contrib/auth.revokeActorPayload→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/contrib/auth.revokeRolePayload→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/contrib/auth.targetedGranter→github.com/modernice/goes/event.AggregateRef
- Direction
- github.com/modernice/goes/contrib/auth uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/contrib/auth, while a change to github.com/modernice/goes/contrib/auth can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/contrib/auth uses a module listed above it, which is the healthy direction.
29→14 github.com/modernice/goes/contrib/auth uses github.com/modernice/goes/command✕
- Connections
- 5 pairs of types, where a type in github.com/modernice/goes/contrib/auth uses a type in github.com/modernice/goes/command.
- The types involved
github.com/modernice/goes/contrib/auth.auth→github.com/modernice/goes/command.Busgithub.com/modernice/goes/contrib/auth.auth→github.com/modernice/goes/command.Cmdgithub.com/modernice/goes/contrib/auth.auth→github.com/modernice/goes/command.DispatchOptiongithub.com/modernice/goes/contrib/auth.commandBusClient→github.com/modernice/goes/command.Busgithub.com/modernice/goes/contrib/auth.commandBusClient→github.com/modernice/goes/command.DispatchOption
- Direction
- github.com/modernice/goes/contrib/auth uses github.com/modernice/goes/command, so a change to github.com/modernice/goes/command can break github.com/modernice/goes/contrib/auth, while a change to github.com/modernice/goes/contrib/auth can't break github.com/modernice/goes/command.
- Position
- Below the diagonal: github.com/modernice/goes/contrib/auth uses a module listed above it, which is the healthy direction.
29→16 github.com/modernice/goes/contrib/auth uses github.com/modernice/goes/projection✕
- Connections
- 4 pairs of types, where a type in github.com/modernice/goes/contrib/auth uses a type in github.com/modernice/goes/projection.
- The types involved
github.com/modernice/goes/contrib/auth.Granter→github.com/modernice/goes/projection.Jobgithub.com/modernice/goes/contrib/auth.PermissionProjector→github.com/modernice/goes/projection.Jobgithub.com/modernice/goes/contrib/auth.Permissions→github.com/modernice/goes/projection.ProgressAwaregithub.com/modernice/goes/contrib/auth.mongoPermissions→github.com/modernice/goes/projection.ProgressAware
- Direction
- github.com/modernice/goes/contrib/auth uses github.com/modernice/goes/projection, so a change to github.com/modernice/goes/projection can break github.com/modernice/goes/contrib/auth, while a change to github.com/modernice/goes/contrib/auth can't break github.com/modernice/goes/projection.
- Position
- Below the diagonal: github.com/modernice/goes/contrib/auth uses a module listed above it, which is the healthy direction.
29→19 github.com/modernice/goes/contrib/auth uses github.com/modernice/goes/command/handler✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/contrib/auth uses a type in github.com/modernice/goes/command/handler.
- The types involved
github.com/modernice/goes/contrib/auth.Actor→github.com/modernice/goes/command/handler.Aggregategithub.com/modernice/goes/contrib/auth.Role→github.com/modernice/goes/command/handler.Aggregate
- Direction
- github.com/modernice/goes/contrib/auth uses github.com/modernice/goes/command/handler, so a change to github.com/modernice/goes/command/handler can break github.com/modernice/goes/contrib/auth, while a change to github.com/modernice/goes/contrib/auth can't break github.com/modernice/goes/command/handler.
- Position
- Below the diagonal: github.com/modernice/goes/contrib/auth uses a module listed above it, which is the healthy direction.
29→22 github.com/modernice/goes/contrib/auth uses github.com/modernice/goes/projection/schedule✕
- Connections
- 3 pairs of types, where a type in github.com/modernice/goes/contrib/auth uses a type in github.com/modernice/goes/projection/schedule.
- The types involved
github.com/modernice/goes/contrib/auth.Granter→github.com/modernice/goes/projection/schedule.Continuousgithub.com/modernice/goes/contrib/auth.PermissionProjector→github.com/modernice/goes/projection/schedule.Continuousgithub.com/modernice/goes/contrib/auth.auth→github.com/modernice/goes/projection/schedule.ContinuousOption
- Direction
- github.com/modernice/goes/contrib/auth uses github.com/modernice/goes/projection/schedule, so a change to github.com/modernice/goes/projection/schedule can break github.com/modernice/goes/contrib/auth, while a change to github.com/modernice/goes/contrib/auth can't break github.com/modernice/goes/projection/schedule.
- Position
- Below the diagonal: github.com/modernice/goes/contrib/auth uses a module listed above it, which is the healthy direction.
29→23 github.com/modernice/goes/contrib/auth uses github.com/modernice/goes/aggregate✕
- Connections
- 9 pairs of types, where a type in github.com/modernice/goes/contrib/auth uses a type in github.com/modernice/goes/aggregate.
- The types involved
github.com/modernice/goes/contrib/auth.Actor→github.com/modernice/goes/aggregate.Committergithub.com/modernice/goes/contrib/auth.ActorRepositories→github.com/modernice/goes/aggregate.TypedRepositorygithub.com/modernice/goes/contrib/auth.ActorRepositoryRegistry→github.com/modernice/goes/aggregate.TypedRepositorygithub.com/modernice/goes/contrib/auth.PermissionProjector→github.com/modernice/goes/aggregate.TypedRepositorygithub.com/modernice/goes/contrib/auth.Permissions→github.com/modernice/goes/aggregate.TypedRepositorygithub.com/modernice/goes/contrib/auth.Role→github.com/modernice/goes/aggregate.Committergithub.com/modernice/goes/contrib/auth.auth→github.com/modernice/goes/aggregate.Repositorygithub.com/modernice/goes/contrib/auth.auth→github.com/modernice/goes/aggregate.TypedRepositorygithub.com/modernice/goes/contrib/auth.repositoryCommandClient→github.com/modernice/goes/aggregate.TypedRepository
- Direction
- github.com/modernice/goes/contrib/auth uses github.com/modernice/goes/aggregate, so a change to github.com/modernice/goes/aggregate can break github.com/modernice/goes/contrib/auth, while a change to github.com/modernice/goes/contrib/auth can't break github.com/modernice/goes/aggregate.
- Position
- Below the diagonal: github.com/modernice/goes/contrib/auth uses a module listed above it, which is the healthy direction.
29→24 github.com/modernice/goes/contrib/auth uses github.com/modernice/goes/projection/lookup✕
- Connections
- 3 pairs of types, where a type in github.com/modernice/goes/contrib/auth uses a type in github.com/modernice/goes/projection/lookup.
- The types involved
github.com/modernice/goes/contrib/auth.ActorIdentifiedData→github.com/modernice/goes/projection/lookup.Providergithub.com/modernice/goes/contrib/auth.RoleIdentifiedData→github.com/modernice/goes/projection/lookup.Providergithub.com/modernice/goes/contrib/auth.auth→github.com/modernice/goes/projection/lookup.Option
- Direction
- github.com/modernice/goes/contrib/auth uses github.com/modernice/goes/projection/lookup, so a change to github.com/modernice/goes/projection/lookup can break github.com/modernice/goes/contrib/auth, while a change to github.com/modernice/goes/contrib/auth can't break github.com/modernice/goes/projection/lookup.
- Position
- Below the diagonal: github.com/modernice/goes/contrib/auth uses a module listed above it, which is the healthy direction.
30→7 github.com/modernice/goes/saga/action uses github.com/modernice/goes/event✕
- Connections
- 3 pairs of types, where a type in github.com/modernice/goes/saga/action uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/saga/action.Context→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/saga/action.actionContext→github.com/modernice/goes/event.Busgithub.com/modernice/goes/saga/action.actionContext→github.com/modernice/goes/event.Of
- Direction
- github.com/modernice/goes/saga/action uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/saga/action, while a change to github.com/modernice/goes/saga/action can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/saga/action uses a module listed above it, which is the healthy direction.
30→14 github.com/modernice/goes/saga/action uses github.com/modernice/goes/command✕
- Connections
- 5 pairs of types, where a type in github.com/modernice/goes/saga/action uses a type in github.com/modernice/goes/command.
- The types involved
github.com/modernice/goes/saga/action.Context→github.com/modernice/goes/command.DispatchOptiongithub.com/modernice/goes/saga/action.Context→github.com/modernice/goes/command.Ofgithub.com/modernice/goes/saga/action.actionContext→github.com/modernice/goes/command.Busgithub.com/modernice/goes/saga/action.actionContext→github.com/modernice/goes/command.DispatchOptiongithub.com/modernice/goes/saga/action.actionContext→github.com/modernice/goes/command.Of
- Direction
- github.com/modernice/goes/saga/action uses github.com/modernice/goes/command, so a change to github.com/modernice/goes/command can break github.com/modernice/goes/saga/action, while a change to github.com/modernice/goes/saga/action can't break github.com/modernice/goes/command.
- Position
- Below the diagonal: github.com/modernice/goes/saga/action uses a module listed above it, which is the healthy direction.
30→23 github.com/modernice/goes/saga/action uses github.com/modernice/goes/aggregate✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/saga/action uses a type in github.com/modernice/goes/aggregate.
- The types involved
github.com/modernice/goes/saga/action.actionContext→github.com/modernice/goes/aggregate.Repository
- Direction
- github.com/modernice/goes/saga/action uses github.com/modernice/goes/aggregate, so a change to github.com/modernice/goes/aggregate can break github.com/modernice/goes/saga/action, while a change to github.com/modernice/goes/saga/action can't break github.com/modernice/goes/aggregate.
- Position
- Below the diagonal: github.com/modernice/goes/saga/action uses a module listed above it, which is the healthy direction.
31→2 github.com/modernice/goes/workflow uses github.com/modernice/goes/codec✕
- Connections
- 4 pairs of types, where a type in github.com/modernice/goes/workflow uses a type in github.com/modernice/goes/codec.
- The types involved
github.com/modernice/goes/workflow.Config→github.com/modernice/goes/codec.Encodinggithub.com/modernice/goes/workflow.Service→github.com/modernice/goes/codec.Encodinggithub.com/modernice/goes/workflow.handlerRuntime→github.com/modernice/goes/codec.Encodinggithub.com/modernice/goes/workflow.workflow→github.com/modernice/goes/codec.Registerer
- Direction
- github.com/modernice/goes/workflow uses github.com/modernice/goes/codec, so a change to github.com/modernice/goes/codec can break github.com/modernice/goes/workflow, while a change to github.com/modernice/goes/workflow can't break github.com/modernice/goes/codec.
- Position
- Below the diagonal: github.com/modernice/goes/workflow uses a module listed above it, which is the healthy direction.
31→7 github.com/modernice/goes/workflow uses github.com/modernice/goes/event✕
- Connections
- 10 pairs of types, where a type in github.com/modernice/goes/workflow uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/workflow.Base→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/workflow.Config→github.com/modernice/goes/event.Busgithub.com/modernice/goes/workflow.Config→github.com/modernice/goes/event.Storegithub.com/modernice/goes/workflow.Ctx→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/workflow.Service→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/workflow.Service→github.com/modernice/goes/event.Storegithub.com/modernice/goes/workflow.effectState→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/workflow.handlerContext→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/workflow.handlerRuntime→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/workflow.workflow→github.com/modernice/goes/event.Of
- Direction
- github.com/modernice/goes/workflow uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/workflow, while a change to github.com/modernice/goes/workflow can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/workflow uses a module listed above it, which is the healthy direction.
31→14 github.com/modernice/goes/workflow uses github.com/modernice/goes/command✕
- Connections
- 4 pairs of types, where a type in github.com/modernice/goes/workflow uses a type in github.com/modernice/goes/command.
- The types involved
github.com/modernice/goes/workflow.Config→github.com/modernice/goes/command.Busgithub.com/modernice/goes/workflow.Ctx→github.com/modernice/goes/command.Ofgithub.com/modernice/goes/workflow.Service→github.com/modernice/goes/command.Busgithub.com/modernice/goes/workflow.handlerContext→github.com/modernice/goes/command.Of
- Direction
- github.com/modernice/goes/workflow uses github.com/modernice/goes/command, so a change to github.com/modernice/goes/command can break github.com/modernice/goes/workflow, while a change to github.com/modernice/goes/workflow can't break github.com/modernice/goes/command.
- Position
- Below the diagonal: github.com/modernice/goes/workflow uses a module listed above it, which is the healthy direction.
31→19 github.com/modernice/goes/workflow uses github.com/modernice/goes/command/handler✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/workflow uses a type in github.com/modernice/goes/command/handler.
- The types involved
github.com/modernice/goes/workflow.Base→github.com/modernice/goes/command/handler.Aggregate
- Direction
- github.com/modernice/goes/workflow uses github.com/modernice/goes/command/handler, so a change to github.com/modernice/goes/command/handler can break github.com/modernice/goes/workflow, while a change to github.com/modernice/goes/workflow can't break github.com/modernice/goes/command/handler.
- Position
- Below the diagonal: github.com/modernice/goes/workflow uses a module listed above it, which is the healthy direction.
31→20 github.com/modernice/goes/workflow uses github.com/modernice/goes/event/handler✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/workflow uses a type in github.com/modernice/goes/event/handler.
- The types involved
github.com/modernice/goes/workflow.Service→github.com/modernice/goes/event/handler.Handler
- Direction
- github.com/modernice/goes/workflow uses github.com/modernice/goes/event/handler, so a change to github.com/modernice/goes/event/handler can break github.com/modernice/goes/workflow, while a change to github.com/modernice/goes/workflow can't break github.com/modernice/goes/event/handler.
- Position
- Below the diagonal: github.com/modernice/goes/workflow uses a module listed above it, which is the healthy direction.
31→23 github.com/modernice/goes/workflow uses github.com/modernice/goes/aggregate✕
- Connections
- 4 pairs of types, where a type in github.com/modernice/goes/workflow uses a type in github.com/modernice/goes/aggregate.
- The types involved
github.com/modernice/goes/workflow.Base→github.com/modernice/goes/aggregate.Committergithub.com/modernice/goes/workflow.Service→github.com/modernice/goes/aggregate.Repositorygithub.com/modernice/goes/workflow.Workflow→github.com/modernice/goes/aggregate.TypedAggregategithub.com/modernice/goes/workflow.workflow→github.com/modernice/goes/aggregate.TypedRepository
- Direction
- github.com/modernice/goes/workflow uses github.com/modernice/goes/aggregate, so a change to github.com/modernice/goes/aggregate can break github.com/modernice/goes/workflow, while a change to github.com/modernice/goes/workflow can't break github.com/modernice/goes/aggregate.
- Position
- Below the diagonal: github.com/modernice/goes/workflow uses a module listed above it, which is the healthy direction.
32→7 github.com/modernice/goes/aggregate/repository uses github.com/modernice/goes/event✕
- Connections
- 4 pairs of types, where a type in github.com/modernice/goes/aggregate/repository uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/aggregate/repository.Repository→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/aggregate/repository.Repository→github.com/modernice/goes/event.Querygithub.com/modernice/goes/aggregate/repository.Repository→github.com/modernice/goes/event.Storegithub.com/modernice/goes/aggregate/repository.repository→github.com/modernice/goes/event.Store
- Direction
- github.com/modernice/goes/aggregate/repository uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/aggregate/repository, while a change to github.com/modernice/goes/aggregate/repository can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/repository uses a module listed above it, which is the healthy direction.
32→15 github.com/modernice/goes/aggregate/repository uses github.com/modernice/goes/event/query✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/aggregate/repository uses a type in github.com/modernice/goes/event/query.
- The types involved
github.com/modernice/goes/aggregate/repository.Repository→github.com/modernice/goes/event/query.Optiongithub.com/modernice/goes/aggregate/repository.Repository→github.com/modernice/goes/event/query.Query
- Direction
- github.com/modernice/goes/aggregate/repository uses github.com/modernice/goes/event/query, so a change to github.com/modernice/goes/event/query can break github.com/modernice/goes/aggregate/repository, while a change to github.com/modernice/goes/aggregate/repository can't break github.com/modernice/goes/event/query.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/repository uses a module listed above it, which is the healthy direction.
32→23 github.com/modernice/goes/aggregate/repository uses github.com/modernice/goes/aggregate✕
- Connections
- 8 pairs of types, where a type in github.com/modernice/goes/aggregate/repository uses a type in github.com/modernice/goes/aggregate.
- The types involved
github.com/modernice/goes/aggregate/repository.CachedRepository→github.com/modernice/goes/aggregate.TypedRepositorygithub.com/modernice/goes/aggregate/repository.Repository→github.com/modernice/goes/aggregate.Historygithub.com/modernice/goes/aggregate/repository.Repository→github.com/modernice/goes/aggregate.Querygithub.com/modernice/goes/aggregate/repository.Repository→github.com/modernice/goes/aggregate.Repositorygithub.com/modernice/goes/aggregate/repository.TypedRepository→github.com/modernice/goes/aggregate.Querygithub.com/modernice/goes/aggregate/repository.TypedRepository→github.com/modernice/goes/aggregate.Repositorygithub.com/modernice/goes/aggregate/repository.repository→github.com/modernice/goes/aggregate.Repositorygithub.com/modernice/goes/aggregate/repository.repository→github.com/modernice/goes/aggregate.TypedRepository
- Direction
- github.com/modernice/goes/aggregate/repository uses github.com/modernice/goes/aggregate, so a change to github.com/modernice/goes/aggregate can break github.com/modernice/goes/aggregate/repository, while a change to github.com/modernice/goes/aggregate/repository can't break github.com/modernice/goes/aggregate.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/repository uses a module listed above it, which is the healthy direction.
32→26 github.com/modernice/goes/aggregate/repository uses github.com/modernice/goes/aggregate/snapshot✕
- Connections
- 4 pairs of types, where a type in github.com/modernice/goes/aggregate/repository uses a type in github.com/modernice/goes/aggregate/snapshot.
- The types involved
github.com/modernice/goes/aggregate/repository.Repository→github.com/modernice/goes/aggregate/snapshot.Schedulegithub.com/modernice/goes/aggregate/repository.Repository→github.com/modernice/goes/aggregate/snapshot.Storegithub.com/modernice/goes/aggregate/repository.repository→github.com/modernice/goes/aggregate/snapshot.Schedulegithub.com/modernice/goes/aggregate/repository.repository→github.com/modernice/goes/aggregate/snapshot.Store
- Direction
- github.com/modernice/goes/aggregate/repository uses github.com/modernice/goes/aggregate/snapshot, so a change to github.com/modernice/goes/aggregate/snapshot can break github.com/modernice/goes/aggregate/repository, while a change to github.com/modernice/goes/aggregate/repository can't break github.com/modernice/goes/aggregate/snapshot.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/repository uses a module listed above it, which is the healthy direction.
33→4 github.com/modernice/goes/aggregate/snapshot/query uses github.com/modernice/goes/event/query/time✕
- Connections
- 3 pairs of types, where a type in github.com/modernice/goes/aggregate/snapshot/query uses a type in github.com/modernice/goes/event/query/time.
- The types involved
github.com/modernice/goes/aggregate/snapshot/query.Query→github.com/modernice/goes/event/query/time.Constraintsgithub.com/modernice/goes/aggregate/snapshot/query.builder→github.com/modernice/goes/event/query/time.Optiongithub.com/modernice/goes/aggregate/snapshot/query.query→github.com/modernice/goes/event/query/time.Option
- Direction
- github.com/modernice/goes/aggregate/snapshot/query uses github.com/modernice/goes/event/query/time, so a change to github.com/modernice/goes/event/query/time can break github.com/modernice/goes/aggregate/snapshot/query, while a change to github.com/modernice/goes/aggregate/snapshot/query can't break github.com/modernice/goes/event/query/time.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/snapshot/query uses a module listed above it, which is the healthy direction.
33→5 github.com/modernice/goes/aggregate/snapshot/query uses github.com/modernice/goes/event/query/version✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/aggregate/snapshot/query uses a type in github.com/modernice/goes/event/query/version.
- The types involved
github.com/modernice/goes/aggregate/snapshot/query.query→github.com/modernice/goes/event/query/version.Option
- Direction
- github.com/modernice/goes/aggregate/snapshot/query uses github.com/modernice/goes/event/query/version, so a change to github.com/modernice/goes/event/query/version can break github.com/modernice/goes/aggregate/snapshot/query, while a change to github.com/modernice/goes/aggregate/snapshot/query can't break github.com/modernice/goes/event/query/version.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/snapshot/query uses a module listed above it, which is the healthy direction.
33→23 github.com/modernice/goes/aggregate/snapshot/query uses github.com/modernice/goes/aggregate✕
- Connections
- 5 pairs of types, where a type in github.com/modernice/goes/aggregate/snapshot/query uses a type in github.com/modernice/goes/aggregate.
- The types involved
github.com/modernice/goes/aggregate/snapshot/query.Query→github.com/modernice/goes/aggregate.Querygithub.com/modernice/goes/aggregate/snapshot/query.builder→github.com/modernice/goes/aggregate.Querygithub.com/modernice/goes/aggregate/snapshot/query.query→github.com/modernice/goes/aggregate.SortDirectiongithub.com/modernice/goes/aggregate/snapshot/query.query→github.com/modernice/goes/aggregate.SortOptionsgithub.com/modernice/goes/aggregate/snapshot/query.query→github.com/modernice/goes/aggregate.Sorting
- Direction
- github.com/modernice/goes/aggregate/snapshot/query uses github.com/modernice/goes/aggregate, so a change to github.com/modernice/goes/aggregate can break github.com/modernice/goes/aggregate/snapshot/query, while a change to github.com/modernice/goes/aggregate/snapshot/query can't break github.com/modernice/goes/aggregate.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/snapshot/query uses a module listed above it, which is the healthy direction.
33→25 github.com/modernice/goes/aggregate/snapshot/query uses github.com/modernice/goes/aggregate/query✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/aggregate/snapshot/query uses a type in github.com/modernice/goes/aggregate/query.
- The types involved
github.com/modernice/goes/aggregate/snapshot/query.builder→github.com/modernice/goes/aggregate/query.Option
- Direction
- github.com/modernice/goes/aggregate/snapshot/query uses github.com/modernice/goes/aggregate/query, so a change to github.com/modernice/goes/aggregate/query can break github.com/modernice/goes/aggregate/snapshot/query, while a change to github.com/modernice/goes/aggregate/snapshot/query can't break github.com/modernice/goes/aggregate/query.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/snapshot/query uses a module listed above it, which is the healthy direction.
33→26 github.com/modernice/goes/aggregate/snapshot/query uses github.com/modernice/goes/aggregate/snapshot✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/aggregate/snapshot/query uses a type in github.com/modernice/goes/aggregate/snapshot.
- The types involved
github.com/modernice/goes/aggregate/snapshot/query.Query→github.com/modernice/goes/aggregate/snapshot.Querygithub.com/modernice/goes/aggregate/snapshot/query.builder→github.com/modernice/goes/aggregate/snapshot.Query
- Direction
- github.com/modernice/goes/aggregate/snapshot/query uses github.com/modernice/goes/aggregate/snapshot, so a change to github.com/modernice/goes/aggregate/snapshot can break github.com/modernice/goes/aggregate/snapshot/query, while a change to github.com/modernice/goes/aggregate/snapshot/query can't break github.com/modernice/goes/aggregate/snapshot.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/snapshot/query uses a module listed above it, which is the healthy direction.
34→19 github.com/modernice/goes/aggregate/snapshot/storetest uses github.com/modernice/goes/command/handler✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/aggregate/snapshot/storetest uses a type in github.com/modernice/goes/command/handler.
- The types involved
github.com/modernice/goes/aggregate/snapshot/storetest.snapshotter→github.com/modernice/goes/command/handler.Aggregate
- Direction
- github.com/modernice/goes/aggregate/snapshot/storetest uses github.com/modernice/goes/command/handler, so a change to github.com/modernice/goes/command/handler can break github.com/modernice/goes/aggregate/snapshot/storetest, while a change to github.com/modernice/goes/aggregate/snapshot/storetest can't break github.com/modernice/goes/command/handler.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/snapshot/storetest uses a module listed above it, which is the healthy direction.
34→23 github.com/modernice/goes/aggregate/snapshot/storetest uses github.com/modernice/goes/aggregate✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/aggregate/snapshot/storetest uses a type in github.com/modernice/goes/aggregate.
- The types involved
github.com/modernice/goes/aggregate/snapshot/storetest.snapshotter→github.com/modernice/goes/aggregate.Committer
- Direction
- github.com/modernice/goes/aggregate/snapshot/storetest uses github.com/modernice/goes/aggregate, so a change to github.com/modernice/goes/aggregate can break github.com/modernice/goes/aggregate/snapshot/storetest, while a change to github.com/modernice/goes/aggregate/snapshot/storetest can't break github.com/modernice/goes/aggregate.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/snapshot/storetest uses a module listed above it, which is the healthy direction.
34→26 github.com/modernice/goes/aggregate/snapshot/storetest uses github.com/modernice/goes/aggregate/snapshot✕
- Connections
- 3 pairs of types, where a type in github.com/modernice/goes/aggregate/snapshot/storetest uses a type in github.com/modernice/goes/aggregate/snapshot.
- The types involved
github.com/modernice/goes/aggregate/snapshot/storetest.storetest→github.com/modernice/goes/aggregate/snapshot.Querygithub.com/modernice/goes/aggregate/snapshot/storetest.storetest→github.com/modernice/goes/aggregate/snapshot.Snapshotgithub.com/modernice/goes/aggregate/snapshot/storetest.storetest→github.com/modernice/goes/aggregate/snapshot.Store
- Direction
- github.com/modernice/goes/aggregate/snapshot/storetest uses github.com/modernice/goes/aggregate/snapshot, so a change to github.com/modernice/goes/aggregate/snapshot can break github.com/modernice/goes/aggregate/snapshot/storetest, while a change to github.com/modernice/goes/aggregate/snapshot/storetest can't break github.com/modernice/goes/aggregate/snapshot.
- Position
- Below the diagonal: github.com/modernice/goes/aggregate/snapshot/storetest uses a module listed above it, which is the healthy direction.
35→2 github.com/modernice/goes/backend/mongo uses github.com/modernice/goes/codec✕
- Connections
- 3 pairs of types, where a type in github.com/modernice/goes/backend/mongo uses a type in github.com/modernice/goes/codec.
- The types involved
github.com/modernice/goes/backend/mongo.EventStore→github.com/modernice/goes/codec.Encodinggithub.com/modernice/goes/backend/mongo.entry→github.com/modernice/goes/codec.Encodinggithub.com/modernice/goes/backend/mongo.mongo→github.com/modernice/goes/codec.Encoding
- Direction
- github.com/modernice/goes/backend/mongo uses github.com/modernice/goes/codec, so a change to github.com/modernice/goes/codec can break github.com/modernice/goes/backend/mongo, while a change to github.com/modernice/goes/backend/mongo can't break github.com/modernice/goes/codec.
- Position
- Below the diagonal: github.com/modernice/goes/backend/mongo uses a module listed above it, which is the healthy direction.
35→4 github.com/modernice/goes/backend/mongo uses github.com/modernice/goes/event/query/time✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/backend/mongo uses a type in github.com/modernice/goes/event/query/time.
- The types involved
github.com/modernice/goes/backend/mongo.mongo→github.com/modernice/goes/event/query/time.Constraints
- Direction
- github.com/modernice/goes/backend/mongo uses github.com/modernice/goes/event/query/time, so a change to github.com/modernice/goes/event/query/time can break github.com/modernice/goes/backend/mongo, while a change to github.com/modernice/goes/backend/mongo can't break github.com/modernice/goes/event/query/time.
- Position
- Below the diagonal: github.com/modernice/goes/backend/mongo uses a module listed above it, which is the healthy direction.
35→5 github.com/modernice/goes/backend/mongo uses github.com/modernice/goes/event/query/version✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/backend/mongo uses a type in github.com/modernice/goes/event/query/version.
- The types involved
github.com/modernice/goes/backend/mongo.mongo→github.com/modernice/goes/event/query/version.Constraints
- Direction
- github.com/modernice/goes/backend/mongo uses github.com/modernice/goes/event/query/version, so a change to github.com/modernice/goes/event/query/version can break github.com/modernice/goes/backend/mongo, while a change to github.com/modernice/goes/backend/mongo can't break github.com/modernice/goes/event/query/version.
- Position
- Below the diagonal: github.com/modernice/goes/backend/mongo uses a module listed above it, which is the healthy direction.
35→7 github.com/modernice/goes/backend/mongo uses github.com/modernice/goes/event✕
- Connections
- 11 pairs of types, where a type in github.com/modernice/goes/backend/mongo uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/backend/mongo.EventStore→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/backend/mongo.EventStore→github.com/modernice/goes/event.Querygithub.com/modernice/goes/backend/mongo.EventStore→github.com/modernice/goes/event.Storegithub.com/modernice/goes/backend/mongo.Transaction→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/backend/mongo.VersionError→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/backend/mongo.entry→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/backend/mongo.mongo→github.com/modernice/goes/event.AggregateRefgithub.com/modernice/goes/backend/mongo.mongo→github.com/modernice/goes/event.Ofgithub.com/modernice/goes/backend/mongo.mongo→github.com/modernice/goes/event.Querygithub.com/modernice/goes/backend/mongo.mongo→github.com/modernice/goes/event.SortOptionsgithub.com/modernice/goes/backend/mongo.transaction→github.com/modernice/goes/event.Of
- Direction
- github.com/modernice/goes/backend/mongo uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/backend/mongo, while a change to github.com/modernice/goes/backend/mongo can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/backend/mongo uses a module listed above it, which is the healthy direction.
35→23 github.com/modernice/goes/backend/mongo uses github.com/modernice/goes/aggregate✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/backend/mongo uses a type in github.com/modernice/goes/aggregate.
- The types involved
github.com/modernice/goes/backend/mongo.mongo→github.com/modernice/goes/aggregate.SortOptions
- Direction
- github.com/modernice/goes/backend/mongo uses github.com/modernice/goes/aggregate, so a change to github.com/modernice/goes/aggregate can break github.com/modernice/goes/backend/mongo, while a change to github.com/modernice/goes/backend/mongo can't break github.com/modernice/goes/aggregate.
- Position
- Below the diagonal: github.com/modernice/goes/backend/mongo uses a module listed above it, which is the healthy direction.
35→26 github.com/modernice/goes/backend/mongo uses github.com/modernice/goes/aggregate/snapshot✕
- Connections
- 5 pairs of types, where a type in github.com/modernice/goes/backend/mongo uses a type in github.com/modernice/goes/aggregate/snapshot.
- The types involved
github.com/modernice/goes/backend/mongo.SnapshotStore→github.com/modernice/goes/aggregate/snapshot.Querygithub.com/modernice/goes/backend/mongo.SnapshotStore→github.com/modernice/goes/aggregate/snapshot.Snapshotgithub.com/modernice/goes/backend/mongo.SnapshotStore→github.com/modernice/goes/aggregate/snapshot.Storegithub.com/modernice/goes/backend/mongo.mongo→github.com/modernice/goes/aggregate/snapshot.Querygithub.com/modernice/goes/backend/mongo.snapshotEntry→github.com/modernice/goes/aggregate/snapshot.Snapshot
- Direction
- github.com/modernice/goes/backend/mongo uses github.com/modernice/goes/aggregate/snapshot, so a change to github.com/modernice/goes/aggregate/snapshot can break github.com/modernice/goes/backend/mongo, while a change to github.com/modernice/goes/backend/mongo can't break github.com/modernice/goes/aggregate/snapshot.
- Position
- Below the diagonal: github.com/modernice/goes/backend/mongo uses a module listed above it, which is the healthy direction.
36→7 github.com/modernice/goes/contrib/auth/authrpc uses github.com/modernice/goes/event✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/contrib/auth/authrpc uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/contrib/auth/authrpc.Client→github.com/modernice/goes/event.AggregateRef
- Direction
- github.com/modernice/goes/contrib/auth/authrpc uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/contrib/auth/authrpc, while a change to github.com/modernice/goes/contrib/auth/authrpc can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/contrib/auth/authrpc uses a module listed above it, which is the healthy direction.
36→23 github.com/modernice/goes/contrib/auth/authrpc uses github.com/modernice/goes/aggregate✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/contrib/auth/authrpc uses a type in github.com/modernice/goes/aggregate.
- The types involved
github.com/modernice/goes/contrib/auth/authrpc.Server→github.com/modernice/goes/aggregate.TypedRepositorygithub.com/modernice/goes/contrib/auth/authrpc.authrpc→github.com/modernice/goes/aggregate.TypedRepository
- Direction
- github.com/modernice/goes/contrib/auth/authrpc uses github.com/modernice/goes/aggregate, so a change to github.com/modernice/goes/aggregate can break github.com/modernice/goes/contrib/auth/authrpc, while a change to github.com/modernice/goes/contrib/auth/authrpc can't break github.com/modernice/goes/aggregate.
- Position
- Below the diagonal: github.com/modernice/goes/contrib/auth/authrpc uses a module listed above it, which is the healthy direction.
36→29 github.com/modernice/goes/contrib/auth/authrpc uses github.com/modernice/goes/contrib/auth✕
- Connections
- 9 pairs of types, where a type in github.com/modernice/goes/contrib/auth/authrpc uses a type in github.com/modernice/goes/contrib/auth.
- The types involved
github.com/modernice/goes/contrib/auth/authrpc.Client→github.com/modernice/goes/contrib/auth.CommandClientgithub.com/modernice/goes/contrib/auth/authrpc.Client→github.com/modernice/goes/contrib/auth.PermissionsDTOgithub.com/modernice/goes/contrib/auth/authrpc.Client→github.com/modernice/goes/contrib/auth.QueryClientgithub.com/modernice/goes/contrib/auth/authrpc.Server→github.com/modernice/goes/contrib/auth.ActorRepositoriesgithub.com/modernice/goes/contrib/auth/authrpc.Server→github.com/modernice/goes/contrib/auth.Lookupgithub.com/modernice/goes/contrib/auth/authrpc.Server→github.com/modernice/goes/contrib/auth.Rolegithub.com/modernice/goes/contrib/auth/authrpc.authrpc→github.com/modernice/goes/contrib/auth.ActorRepositoriesgithub.com/modernice/goes/contrib/auth/authrpc.authrpc→github.com/modernice/goes/contrib/auth.Lookupgithub.com/modernice/goes/contrib/auth/authrpc.authrpc→github.com/modernice/goes/contrib/auth.Role
- Direction
- github.com/modernice/goes/contrib/auth/authrpc uses github.com/modernice/goes/contrib/auth, so a change to github.com/modernice/goes/contrib/auth can break github.com/modernice/goes/contrib/auth/authrpc, while a change to github.com/modernice/goes/contrib/auth/authrpc can't break github.com/modernice/goes/contrib/auth.
- Position
- Below the diagonal: github.com/modernice/goes/contrib/auth/authrpc uses a module listed above it, which is the healthy direction.
37→7 github.com/modernice/goes/contrib/auth/http/middleware uses github.com/modernice/goes/event✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/contrib/auth/http/middleware uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/contrib/auth/http/middleware.middleware→github.com/modernice/goes/event.AggregateRef
- Direction
- github.com/modernice/goes/contrib/auth/http/middleware uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/contrib/auth/http/middleware, while a change to github.com/modernice/goes/contrib/auth/http/middleware can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/contrib/auth/http/middleware uses a module listed above it, which is the healthy direction.
37→29 github.com/modernice/goes/contrib/auth/http/middleware uses github.com/modernice/goes/contrib/auth✕
- Connections
- 5 pairs of types, where a type in github.com/modernice/goes/contrib/auth/http/middleware uses a type in github.com/modernice/goes/contrib/auth.
- The types involved
github.com/modernice/goes/contrib/auth/http/middleware.Factory→github.com/modernice/goes/contrib/auth.Lookupgithub.com/modernice/goes/contrib/auth/http/middleware.Factory→github.com/modernice/goes/contrib/auth.PermissionFetchergithub.com/modernice/goes/contrib/auth/http/middleware.authorizer→github.com/modernice/goes/contrib/auth.Lookupgithub.com/modernice/goes/contrib/auth/http/middleware.middleware→github.com/modernice/goes/contrib/auth.Lookupgithub.com/modernice/goes/contrib/auth/http/middleware.middleware→github.com/modernice/goes/contrib/auth.PermissionFetcher
- Direction
- github.com/modernice/goes/contrib/auth/http/middleware uses github.com/modernice/goes/contrib/auth, so a change to github.com/modernice/goes/contrib/auth can break github.com/modernice/goes/contrib/auth/http/middleware, while a change to github.com/modernice/goes/contrib/auth/http/middleware can't break github.com/modernice/goes/contrib/auth.
- Position
- Below the diagonal: github.com/modernice/goes/contrib/auth/http/middleware uses a module listed above it, which is the healthy direction.
38→30 github.com/modernice/goes/saga/report uses github.com/modernice/goes/saga/action✕
- Connections
- 4 pairs of types, where a type in github.com/modernice/goes/saga/report uses a type in github.com/modernice/goes/saga/action.
- The types involved
github.com/modernice/goes/saga/report.Report→github.com/modernice/goes/saga/action.Reportgithub.com/modernice/goes/saga/report.report→github.com/modernice/goes/saga/action.Actiongithub.com/modernice/goes/saga/report.report→github.com/modernice/goes/saga/action.Optiongithub.com/modernice/goes/saga/report.report→github.com/modernice/goes/saga/action.Report
- Direction
- github.com/modernice/goes/saga/report uses github.com/modernice/goes/saga/action, so a change to github.com/modernice/goes/saga/action can break github.com/modernice/goes/saga/report, while a change to github.com/modernice/goes/saga/report can't break github.com/modernice/goes/saga/action.
- Position
- Below the diagonal: github.com/modernice/goes/saga/report uses a module listed above it, which is the healthy direction.
39→2 github.com/modernice/goes/backend/mongo/mongotest uses github.com/modernice/goes/codec✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/backend/mongo/mongotest uses a type in github.com/modernice/goes/codec.
- The types involved
github.com/modernice/goes/backend/mongo/mongotest.mongotest→github.com/modernice/goes/codec.Encoding
- Direction
- github.com/modernice/goes/backend/mongo/mongotest uses github.com/modernice/goes/codec, so a change to github.com/modernice/goes/codec can break github.com/modernice/goes/backend/mongo/mongotest, while a change to github.com/modernice/goes/backend/mongo/mongotest can't break github.com/modernice/goes/codec.
- Position
- Below the diagonal: github.com/modernice/goes/backend/mongo/mongotest uses a module listed above it, which is the healthy direction.
39→35 github.com/modernice/goes/backend/mongo/mongotest uses github.com/modernice/goes/backend/mongo✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/backend/mongo/mongotest uses a type in github.com/modernice/goes/backend/mongo.
- The types involved
github.com/modernice/goes/backend/mongo/mongotest.mongotest→github.com/modernice/goes/backend/mongo.EventStoregithub.com/modernice/goes/backend/mongo/mongotest.mongotest→github.com/modernice/goes/backend/mongo.EventStoreOption
- Direction
- github.com/modernice/goes/backend/mongo/mongotest uses github.com/modernice/goes/backend/mongo, so a change to github.com/modernice/goes/backend/mongo can break github.com/modernice/goes/backend/mongo/mongotest, while a change to github.com/modernice/goes/backend/mongo/mongotest can't break github.com/modernice/goes/backend/mongo.
- Position
- Below the diagonal: github.com/modernice/goes/backend/mongo/mongotest uses a module listed above it, which is the healthy direction.
40→7 github.com/modernice/goes/saga uses github.com/modernice/goes/event✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/saga uses a type in github.com/modernice/goes/event.
- The types involved
github.com/modernice/goes/saga.Executor→github.com/modernice/goes/event.Busgithub.com/modernice/goes/saga.saga→github.com/modernice/goes/event.Bus
- Direction
- github.com/modernice/goes/saga uses github.com/modernice/goes/event, so a change to github.com/modernice/goes/event can break github.com/modernice/goes/saga, while a change to github.com/modernice/goes/saga can't break github.com/modernice/goes/event.
- Position
- Below the diagonal: github.com/modernice/goes/saga uses a module listed above it, which is the healthy direction.
40→14 github.com/modernice/goes/saga uses github.com/modernice/goes/command✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/saga uses a type in github.com/modernice/goes/command.
- The types involved
github.com/modernice/goes/saga.Executor→github.com/modernice/goes/command.Busgithub.com/modernice/goes/saga.saga→github.com/modernice/goes/command.Bus
- Direction
- github.com/modernice/goes/saga uses github.com/modernice/goes/command, so a change to github.com/modernice/goes/command can break github.com/modernice/goes/saga, while a change to github.com/modernice/goes/saga can't break github.com/modernice/goes/command.
- Position
- Below the diagonal: github.com/modernice/goes/saga uses a module listed above it, which is the healthy direction.
40→23 github.com/modernice/goes/saga uses github.com/modernice/goes/aggregate✕
- Connections
- 2 pairs of types, where a type in github.com/modernice/goes/saga uses a type in github.com/modernice/goes/aggregate.
- The types involved
github.com/modernice/goes/saga.Executor→github.com/modernice/goes/aggregate.Repositorygithub.com/modernice/goes/saga.saga→github.com/modernice/goes/aggregate.Repository
- Direction
- github.com/modernice/goes/saga uses github.com/modernice/goes/aggregate, so a change to github.com/modernice/goes/aggregate can break github.com/modernice/goes/saga, while a change to github.com/modernice/goes/saga can't break github.com/modernice/goes/aggregate.
- Position
- Below the diagonal: github.com/modernice/goes/saga uses a module listed above it, which is the healthy direction.
40→30 github.com/modernice/goes/saga uses github.com/modernice/goes/saga/action✕
- Connections
- 6 pairs of types, where a type in github.com/modernice/goes/saga uses a type in github.com/modernice/goes/saga/action.
- The types involved
github.com/modernice/goes/saga.Executor→github.com/modernice/goes/saga/action.Actiongithub.com/modernice/goes/saga.Executor→github.com/modernice/goes/saga/action.Contextgithub.com/modernice/goes/saga.Executor→github.com/modernice/goes/saga/action.Reportgithub.com/modernice/goes/saga.Setup→github.com/modernice/goes/saga/action.Actiongithub.com/modernice/goes/saga.saga→github.com/modernice/goes/saga/action.Actiongithub.com/modernice/goes/saga.setup→github.com/modernice/goes/saga/action.Action
- Direction
- github.com/modernice/goes/saga uses github.com/modernice/goes/saga/action, so a change to github.com/modernice/goes/saga/action can break github.com/modernice/goes/saga, while a change to github.com/modernice/goes/saga can't break github.com/modernice/goes/saga/action.
- Position
- Below the diagonal: github.com/modernice/goes/saga uses a module listed above it, which is the healthy direction.
40→38 github.com/modernice/goes/saga uses github.com/modernice/goes/saga/report✕
- Connections
- 1 pair of types, where a type in github.com/modernice/goes/saga uses a type in github.com/modernice/goes/saga/report.
- The types involved
github.com/modernice/goes/saga.Reporter→github.com/modernice/goes/saga/report.Report
- Direction
- github.com/modernice/goes/saga uses github.com/modernice/goes/saga/report, so a change to github.com/modernice/goes/saga/report can break github.com/modernice/goes/saga, while a change to github.com/modernice/goes/saga can't break github.com/modernice/goes/saga/report.
- Position
- Below the diagonal: github.com/modernice/goes/saga 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 — Event-Driven
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 38 | High / Critical |
| A05:2025 — Injection | 23 | High / Critical |
| A02:2025 — Security Misconfiguration | 13 | High / Critical |
Roadmap
Top priorities: Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value; The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`); Bring the 29 bodies over 15 down to 15 or less in Cognitive Complexity — start with event.Test (cognitive 45), EventStore.buildQuery (cognitive 44), query.Test (cognitive 38).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value. | +5.7 pts | Medium | Dead Code |
| The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`). | +4.4 pts | Medium | Nullable reference types |
| Enforce accessibility in the toolchain: add eslint-plugin-vuejs-accessibility, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI. | +2.8 pts | Medium | A11y enforcement |
| Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element. | +1.6 pts | Medium | ARIA correctness |
| 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. | +1.6 pts | Medium | Visual & motion safety |
| Bring the 29 bodies over 15 down to 15 or less in Cognitive Complexity — start with event.Test (cognitive 45), EventStore.buildQuery (cognitive 44), query.Test (cognitive 38). | +3.2 pts | High | Cognitive Complexity |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +0.8 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. | +1.4 pts | Medium | Forms & labels |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.9 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| event/eventstore/store.go | 6.7 | Mixed | Explicit Debt: TodoComment |
| workflow/workflow.go | 7.0 | Near-clean | God Classes: TooManyMethods: Base |
| backend/mongo/store.go | 7.0 | Near-clean | Cyclomatic Complexity: EventStore.Insert (cyclomatic 17) |
| internal/eventstoreui/mongo.go | 7.1 | Near-clean | Cyclomatic Complexity: mongoReader.Events (cyclomatic 16) |
| backend/mongo/snapshot.go | 7.1 | Near-clean | Code Duplication: Duplicated block (26 lines × 2) |
| backend/postgres/store.go | 7.2 | Near-clean | Cyclomatic Complexity: EventStore.buildQuery (cyclomatic 28) |
| backend/natsjs/query.go | 7.2 | Near-clean | Cyclomatic Complexity: EventStore.Query (cyclomatic 18) |
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 79 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 79 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, 239 of 257 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 (.go) 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 (`go test -coverprofile=coverage.out ./...`) 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 (`go test -coverprofile=coverage.out ./...`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (8 contributor(s) across 1292 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 7 hold 0.1% 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 a COLLECTOR gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D32 Data Compliance (PII/GDPR) — 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. `aggregate/consistency.go`, `aggregate/history.go`, `aggregate/repository.go`, `aggregate/repository/cached.go`, `backend/postgres/store.go`, … (+7 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in codec/registry.go, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (examples/todo/.docker/compose.yml). compose up failed (exit 15 — the compose project is invalid) — time="2026-11-08T03:28:18Z" level=warning msg="The \"TODO_DEBOUNCE\" variable is not set. Defaulting to a blank string." service "server" depends on undefined service "eventstore_init": invalid compose project; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- 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.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Go, Vue components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Go, Vue components is most of its product and 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.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- R7 Dead Code — 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. 67 further occurrence(s) are not listed individually; the score already reflects all 107.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, 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.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
12 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was event.Test at 34.
What to do
- Bring the 12 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with event.Test (cyclomatic 34), EventStore.buildQuery (cyclomatic 28), eventstoreui.LoadConfig (cyclomatic 25). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 12 together lifts Cyclomatic Complexity from 8.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
29 method(s) exceeded the cognitive complexity threshold of 15; the worst was event.Test at 45.
What to do
- Bring the 29 bodies over 15 down to 15 or less in Cognitive Complexity — start with event.Test (cognitive 45), EventStore.buildQuery (cognitive 44), query.Test (cognitive 38). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 29 together lifts Cognitive Complexity from 6.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
2 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with workflow.go. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with store.go. — 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
41 duplicated block group(s) detected. 3 of the 41 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 4 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with mongo.go (2), expect.go, postgres.go. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with snapshot.go (2), expect.go, commands.go. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with core.go, granter.go, store.go. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
2 production modules (npm+Go), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
4 of 82 classes have LCOM4 above 3.
What to do
- Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with context.go (2), REDACTED, workflow.go. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
440 test methods: 438 unit, 2 integration, 0 BDD, 0 e2e. The Go suite contributes 440 test case(s) across 110 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 93 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Go (2 modules): measured (0 flaky).
D12 · Dependency Hygiene
5 outdated, 0 author-deprecated direct Go module(s), 1 pinning or checksum defect(s). 18 of 18 direct requirement(s) were graded against proxy.golang.org (0 not served there, 2 publishing no tagged release to be behind). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
What to do
- Resolve the 1 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
8 deducted task-comment markers across 26929 LoC (0.0/KLoC) → score 9.9. 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 8 TodoComment finding(s) in Explicit Debt — start with job.go, xtime.go, etree.go. — One of this dimension's main actionable groups (8 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. 60 document(s) read across 3 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (3 contexts). Contexts: aggregate, contrib, workflow.
D26 · Project Cohesion
1 of 3 build units (Go, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
60 % of calls cross a namespace and 38 % go through an interface, but 62 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
23 finding(s): 0 critical, 13 high, 8 medium, 2 low. 9 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 12 file(s) — `aggregate/consistency.go` (line 90), `aggregate/history.go` (line 28), `aggregate/repository.go` (lines 73–74, line 76, line 84), `aggregate/repository/cached.go` (line 22), `backend/postgres/store.go` (line 853, line 861, line 869), … (+7 more) — 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 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 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 9 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 (9 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
32 finding(s): 3 critical, 15 high, 12 medium, 2 low.
What to do
- Resolve the 14 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12), REDACTED (2). — One of this dimension's main actionable groups (14 issue-level).
- Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
13 finding(s): 0 critical, 4 high, 9 medium, 0 low.
What to do
- Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 9 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (9 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 98 of the 197 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.
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
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 3 platform declaration(s) and 0 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
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. (×2) — ui/app/components/ui/input/Input.vue:23, ui/app/layouts/default.vue:67
- This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. — ui/app/pages/events.vue:73
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
AC5 · ARIA correctness
- aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden. — ui/app/pages/login.vue:28
What to do
- Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
AC6 · Visual & motion safety
- `.goes-boot-mark` sets color: #fafafa on background-color: #0891b2 — 3.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — ui/app/spa-loading-template.html:13
- `html:not(.dark) .action-button.primary` sets color: #ffffff on background-color: #0891b2 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — docs/.vitepress/theme/HomePage.vue:292
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 a11y linter (eslint-plugin-vuejs-accessibility) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 78 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. — ui/package.json:24
What to do
- Enforce accessibility in the toolchain: add eslint-plugin-vuejs-accessibility, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
ED1 · Handler temporal coupling
ED4 · Outbox / dual-write
- `storeWithBus.Insert` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — event/eventstore/decorators.go:38
What to do
- Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 2 of 4 project(s) that lack one — worth up to 1 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `ui`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (go.opentelemetry.io/otel) and a health-check endpoint (a /healthz handler) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add gosec / govulncheck (or golangci-lint) (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 5013 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `npm`, 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 entries to the `updates:` list. — REDACTED:2
What to do
- Add a SAST step to CI running what this repository's stack ships: gosec / govulncheck (or golangci-lint) — 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`, `npm` — add those `package-ecosystem` entries 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 automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- ui/app/composables/useEventsExplorer.ts:23 · ui/app/composables/useStreamsExplorer.ts:12 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/app/composables/useEventsExplorer.ts:23
- ui/app/pages/events.vue:25 · ui/app/pages/streams.vue:24 — the two spans are one implementation copied and then locally edited — 177 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — ui/app/pages/events.vue:25
- ui/app/composables/useEventsExplorer.ts:55 · ui/app/composables/useStreamsExplorer.ts:38 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ui/app/composables/useEventsExplorer.ts:55
- ui/app/utils/format.ts:9 · ui/app/utils/format.ts:18 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — ui/app/utils/format.ts:9
- ui/app/pages/events.vue:57 · ui/app/pages/index.vue:41 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — ui/app/pages/events.vue:57
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- load has cyclomatic complexity 13 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/app/components/StreamDialog.vue:17
R3 · Large Files
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
- test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add eslint as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 1 application, 1 tooling and 0 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×22) — ui/app/composables/useOverview.ts, ui/app/composables/useEventsExplorer.ts, ui/app/pages/streams.vue, …
- no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (ui/app/components/ui/button/Button.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/app/components/ui/button/index.ts
- no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/app/components/ui/sheet/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/app/components/ui/sheet/SheetContent.vue
- no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/app/components/ui/select/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×3) — ui/app/components/ui/select/SelectContent.vue, ui/app/components/ui/select/SelectItem.vue, ui/app/components/ui/select/SelectTrigger.vue
- no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/app/components/ui/dropdown-menu/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×4) — ui/app/components/ui/dropdown-menu/DropdownMenuContent.vue, ui/app/components/ui/dropdown-menu/DropdownMenuItem.vue, ui/app/components/ui/dropdown-menu/DropdownMenuRadioItem.vue, …
- no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (ui/app/components/ui/badge/Badge.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/app/components/ui/badge/index.ts
- no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/app/components/ui/switch/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/app/components/ui/switch/Switch.vue
- no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (ui/app/components/ui/alert/Alert.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/app/components/ui/alert/index.ts
- no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/app/components/ui/dialog/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/app/components/ui/dialog/DialogContent.vue
- no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/app/components/ui/input/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/app/components/ui/input/Input.vue
- no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/app/components/ui/button/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/app/components/ui/button/Button.vue
- no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/app/components/ui/badge/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/app/components/ui/badge/Badge.vue
- no import path from any entry point (1 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/app/components/ui/separator/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — ui/app/components/ui/separator/Separator.vue
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in ui/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- ui/app/components/ui/alert/Alert.vue → ui/app/components/ui/alert/index.ts → ui/app/components/ui/alert/Alert.vue — ui/app/components/ui/alert/Alert.vue:5
- ui/app/components/ui/badge/Badge.vue → ui/app/components/ui/badge/index.ts → ui/app/components/ui/badge/Badge.vue — ui/app/components/ui/badge/Badge.vue:8
- ui/app/components/ui/button/Button.vue → ui/app/components/ui/button/index.ts → ui/app/components/ui/button/Button.vue — ui/app/components/ui/button/Button.vue:7
- ui/app/components/ui/select/SelectContent.vue → ui/app/components/ui/select/index.ts → ui/app/components/ui/select/SelectContent.vue — ui/app/components/ui/select/SelectContent.vue:12
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `vercel.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — vercel.json:1
What to do
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 1/2 functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial) accept a context.Context or an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` (Go: `ctx context.Context`) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `execute` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — docs/.vitepress/theme/composables/useTourRunner.ts:29
What to do
- Thread a context.Context or an AbortSignal through functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `html` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — ui/app/components/JsonView.vue:54
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `if err := json.NewEncoder(w).Encode(value); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — internal/eventstoreui/app.go:567
- `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×7) — internal/eventstoreui/auth.go:95, internal/eventstoreui/auth.go:109, contrib/auth/actor.go:200, …
- `if err := a.validateID(id); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — contrib/auth/actor.go:204
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- This repository commits no tsconfig, so whatever type-checks it uses tsc's own defaults, in which `strict` and `strictNullChecks` are OFF: `string` admits `null` and `undefined`, and a value that is null is compiled through to the property access that throws. If the build passes `--strict` on a command line instead, put it in a committed tsconfig — this check reads configuration, and configuration is all it can read.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| 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 | 49% | Adequate — gated by R7, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 73% | Adequate — gated by D26, R9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 70% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 67% | Strong | Solid. |
| Security | 75% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 87% | Exemplary | Solid. |
| Accessibility | 55% | Adequate | Acceptable, with room to improve. |
| Performance | 100% | Exemplary | Strongest area. |
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 — 51 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 15 — the compose project is invalid) — time="2026-11-08T03:28:18Z" level=warning msg="The \"TODO_DEBOUNCE\" variable is not set. Defaulting to a blank string." service "server" depends on undefined service "eventstore_init": invalid compose project; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — 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.
- D10 Test Quality — ~17969 lines of test source are present (.go) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D14 License Compliance — Not scored — this repository's 676 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 86 of them (registry returned 429), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- 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; Go not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .go source were not judged.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 12 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (4 signals for this style, 2 needed — the count is met but a required primary signal is absent): 5 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 3 value object(s); a Domain/Aggregates/ValueObjects layer; 3 aggregate-constrained repository/repositories (IRepository<T> where T : IAggregateRoot); a top-level examples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
- ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
- ED3 Event naming — no domain or integration events detected — event-naming check not applicable
- ED5 Idempotency — Not assessed, and this one is on us: 2 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 3 aggregate(s) with Apply/When folds; 13 Go aggregate(s) recording domain events (own events-slice append / raise-record)
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Go, JavaScript/TypeScript source (service entry point: eventstoreui/app.go:65 (http.Server{))
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`go test -coverprofile=coverage.out ./...`) 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
- 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — the JS/TS workspace (94 production file(s)) has no JavaScript/TypeScript test, but it is 13.25% of this repository's production source and the other 86.75% carries 17,969 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 44 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Import cycle (2 files) ui/app/components/ui/alert/Alert.vue:5
- Import cycle (2 files) ui/app/components/ui/badge/Badge.vue:8
- Import cycle (2 files) ui/app/components/ui/button/Button.vue:7
- Import cycle (2 files) ui/app/components/ui/select/SelectContent.vue:12
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label ui/app/components/ui/input/Input.vue:23
- <select> without a programmatic label ui/app/layouts/default.vue:67
- <label> that labels no control ui/app/pages/events.vue:73
- aria-hidden hides a focusable element ui/app/pages/login.vue:28
- REDACTED
- REDACTED
- Dual write (no outbox): storeWithBus.Insert event/eventstore/decorators.go:38
Serious — 192 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Swallowed exception (caught, then discarded) internal/eventstoreui/app.go:567
- Swallowed exception (caught, then discarded) internal/eventstoreui/auth.go:95
- Swallowed exception (caught, then discarded) internal/eventstoreui/auth.go:109
- Swallowed exception (caught, then discarded) contrib/auth/actor.go:200
- Swallowed exception (caught, then discarded) contrib/auth/actor.go:204
- Swallowed exception (caught, then discarded) contrib/auth/adapters.go:51
- Swallowed exception (caught, then discarded) contrib/auth/adapters.go:62
- Swallowed exception (caught, then discarded) contrib/auth/http/middleware/middleware.go:239
- Swallowed exception (caught, then discarded) command/error.go:233
- TodoComment projection/job.go:496
- TodoComment internal/xtime/xtime.go:34
- TodoComment internal/xevent/etree/etree.go:3
- TodoComment event/eventstore/decorators.go:20
- TodoComment event/eventstore/store.go:25
- TodoComment contrib/auth/lookup_test.go:61
- TodoComment contrib/auth/repos.go:75
- TodoComment aggregate/snapshot/encode.go:76
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (11 lines × 2) backend/testing/eventbustest/expect.go:130
- Duplicated block (11 lines × 2) internal/eventstoreui/mongo.go:412
- Duplicated block (11 lines × 2) internal/eventstoreui/mongo.go:516
- Duplicated block (11 lines × 2) internal/eventstoreui/postgres.go:284
- Duplicated block (8 lines × 2) backend/testing/eventbustest/expect.go:119
- Duplicated block (8 lines × 2) contrib/auth/commands.go:147
- Duplicated block (8 lines × 2) backend/mongo/snapshot.go:336
- Duplicated block (8 lines × 2) backend/mongo/snapshot.go:346
- Duplicated block (6 lines × 2) backend/testing/eventbustest/core.go:102
- Duplicated block (6 lines × 2) contrib/auth/granter.go:248
- Duplicated block (6 lines × 2) backend/mongo/store.go:1041
- Duplicated block (6 lines × 2) examples/workflow/basic/main.go:65
- Low cohesion: handlerContext (LCOM4 8) workflow/context.go:92
- Low cohesion: InvoiceWorkflow (LCOM4 5) examples/workflow/timeouts/main.go:56
- Low cohesion: actionContext (LCOM4 4) saga/action/context.go:50
- Low cohesion: Base (LCOM4 4) workflow/workflow.go:82
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (14 lines × 2) contrib/auth/authrpc/rpc.go:140
- Duplicated block (14 lines × 2) event/eventstore/store.go:147
- Duplicated block (14 lines × 2) internal/eventstoreui/app.go:173
- Duplicated block (13 lines × 2) projection/schedule/continuous.go:165
- Duplicated block (13 lines × 2) event/query/time/constraint.go:192
- Duplicated block (13 lines × 2) backend/natsjs/delete.go:18
- Duplicated block (10 lines × 2) event/eventbus/bus.go:266
- Duplicated block (10 lines × 2) projection/schedule/continuous.go:180
- Duplicated block (10 lines × 2) contrib/auth/projector.go:46
- Duplicated block (9 lines × 2) backend/mongo/snapshot.go:413
- Duplicated block (9 lines × 2) contrib/auth/authrpc/rpc.go:164
- Duplicated block (9 lines × 2) internal/eventstoreui/mongo.go:344
- Dead file (~21 LoC) ui/app/components/ui/alert/index.ts
- Dead file (~21 LoC) ui/app/components/ui/dialog/DialogContent.vue
- Dead file (~21 LoC) ui/app/components/ui/dropdown-menu/DropdownMenuItem.vue
- Dead file (~19 LoC) ui/app/components/EventTable.vue
- Dead file (~19 LoC) ui/app/components/ui/input/Input.vue
- Dead file (~19 LoC) ui/app/components/ui/select/SelectItem.vue
- Dead file (~15 LoC) ui/app/components/ui/badge/Badge.vue
- Dead file (~15 LoC) ui/app/components/ui/dropdown-menu/DropdownMenuLabel.vue
- Dead file (~15 LoC) ui/app/components/ui/separator/Separator.vue
- Duplicated block (20 lines × 2) contrib/auth/actor.go:253
- Duplicated block (20 lines × 2) contrib/auth/actor.go:309
- Duplicated block (17 lines × 2) aggregate/query/query.go:211
- Duplicated block (17 lines × 2) backend/mongo/store.go:407
- Duplicated block (7 lines × 2) backend/mongo/snapshot.go:120
- Duplicated block (7 lines × 2) REDACTED:13
- Dead file (~47 LoC) ui/app/components/StreamDialog.vue
- Dead file (~47 LoC) ui/app/composables/useAuth.ts
- Dead file (~46 LoC) ui/app/composables/useStores.ts
- Dead file (~46 LoC) ui/app/composables/useTheme.ts
- Dead file (~35 LoC) ui/app/components/ui/button/index.ts
- Dead file (~35 LoC) ui/app/components/ui/sheet/SheetContent.vue
- Dead file (~24 LoC) ui/app/components/CopyButton.vue
- Dead file (~24 LoC) ui/app/components/ui/badge/index.ts
- Dead file (~23 LoC) ui/app/components/ui/switch/Switch.vue
- Dead file (~23 LoC) ui/app/pages/login.vue
- Dead file (~18 LoC) ui/app/components/ui/dropdown-menu/DropdownMenuRadioItem.vue
- Dead file (~18 LoC) ui/app/composables/useLiveRefresh.ts
- Low contrast colour pair in CSS (3.5:1) ui/app/spa-loading-template.html:13
- Low contrast colour pair in CSS (3.7:1) docs/.vitepress/theme/HomePage.vue:292
- Accessibility enforcement below the top rung ui/package.json:24
- event.Test (cyclomatic 34) event/event.go:300
- EventStore.buildQuery (cyclomatic 28) backend/postgres/store.go:691
- eventstoreui.LoadConfig (cyclomatic 25) internal/eventstoreui/config.go:67
- query.Test (cyclomatic 20) aggregate/query/query.go:195
- Handler.handle (cyclomatic 20) command/handler.go:72
- Service.processOnce (cyclomatic 20) REDACTED:345
- EventStore.Query (cyclomatic 18) backend/natsjs/query.go:30
- effectState.apply (cyclomatic 18) workflow/effects.go:71
- EventStore.Insert (cyclomatic 17) backend/mongo/store.go:390
- EventStore.Query (cyclomatic 17) backend/mongo/store.go:731
- EventStore.drainConsumer (cyclomatic 16) backend/natsjs/query.go:100
- mongoReader.Events (cyclomatic 16) internal/eventstoreui/mongo.go:363
- Dependency pinned to a stale untagged commit: golang.org/x/exp
- event.Test (cognitive 45) event/event.go:300
- EventStore.buildQuery (cognitive 44) backend/postgres/store.go:691
- query.Test (cognitive 38) aggregate/query/query.go:195
- Handler.handle (cognitive 36) command/handler.go:72
- EventStore.drainConsumer (cognitive 35) backend/natsjs/query.go:100
- Expectations.Events (cognitive 35) backend/testing/eventbustest/expect.go:143
- eventstoreui.LoadConfig (cognitive 33) internal/eventstoreui/config.go:67
- EventStore.Query (cognitive 28) backend/natsjs/query.go:30
- Service.processOnce (cognitive 25) REDACTED:345
- subscription.work (cognitive 23) backend/nats/subscription.go:65
- effectState.apply (cognitive 22) workflow/effects.go:71
- Repository.Save (cognitive 21) aggregate/repository/repository.go:148
- EventStore.Query (cognitive 21) backend/mongo/store.go:731
- aggregate.ValidateConsistency (cognitive 20) aggregate/consistency.go:90
- Repository.Use (cognitive 20) aggregate/repository/repository.go:443
- EventStore.Insert (cognitive 20) backend/mongo/store.go:390
- mongoReader.Events (cognitive 20) internal/eventstoreui/mongo.go:363
- streamCatalog.page (cognitive 20) internal/eventstoreui/streams.go:87
- Repository.Delete (cognitive 19) aggregate/repository/repository.go:352
- stream.acceptEvents (cognitive 19) aggregate/stream/stream.go:219
- Service.dispatchCommand (cognitive 19) workflow/effects.go:260
- subscription.addStream (cognitive 18) backend/natsjs/bus.go:103
- EventStore.Query (cognitive 18) backend/postgres/store.go:635
- workflow.NewService (cognitive 18) REDACTED:150
- EventStore.Insert (cognitive 17) backend/postgres/store.go:505
- eventSubscription.work (cognitive 17) event/eventbus/bus.go:237
- postgresReader.Events (cognitive 17) internal/eventstoreui/postgres.go:243
- ModelRepository.Use (cognitive 16) backend/mongo/model_repository.go:179
- Expectations.Event (cognitive 16) backend/testing/eventbustest/expect.go:108
- REDACTED
- TooManyMethods: Base workflow/workflow.go:82
- FileTooLong: mongo/store.go backend/mongo/store.go
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (26 lines × 2) backend/mongo/snapshot.go:386
- Duplicated block (21 lines × 2) backend/nats/core.go:85
- Duplicated block (19–20 lines × 2) aggregate/snapshot/store.go:69
- Duplicated block (19 lines × 2) backend/nats/core.go:64
- Duplicated block (18 lines × 2) event/query/time/constraint.go:114
- Duplicated block (10–11 lines × 2) internal/eventstoreui/mongo.go:403
- Duplicated block (9–10 lines × 2) backend/mongo/snapshot.go:375
- Duplicated block (7 lines × 3) contrib/auth/http/middleware/middleware.go:47
- Duplicated block (5 lines × 2) internal/eventstoreui/postgres.go:277
- Duplicated block (12 lines × 2) examples/workflow/cluster/main.go:127
- Duplicated block (10 lines × 6) examples/workflow/basic/main.go:189
- Duplicated block (24 lines × 2 locations) ui/app/composables/useEventsExplorer.ts:23
- Duplicated block with local edits (20 matched lines × 2 locations) ui/app/pages/events.vue:25
- Duplicated block (13 lines × 2 locations) ui/app/composables/useEventsExplorer.ts:55
- Duplicated block (8 lines × 2 locations) ui/app/utils/format.ts:9
- Duplicated block (5 lines × 2 locations) ui/app/pages/events.vue:57
- Complex function load (cyclomatic 13, cognitive 15) ui/app/components/StreamDialog.vue:17
- No lint script
- Dead file (~79 LoC) ui/app/composables/useOverview.ts
- Dead file (~74 LoC) ui/app/composables/useEventsExplorer.ts
- Dead file (~70 LoC) ui/app/pages/streams.vue
- Dead file (~65 LoC) ui/app/types/api.ts
- Dead file (~61 LoC) ui/app/pages/events.vue
- Dead file (~57 LoC) ui/app/composables/useStreamsExplorer.ts
- Dead file (~54 LoC) ui/app/utils/format.ts
- Dead file (~53 LoC) ui/app/layouts/default.vue
- Dead file (~49 LoC) ui/app/components/JsonView.vue
- Dead file (~45 LoC) ui/app/pages/index.vue
- Dead file (~40 LoC) ui/app/composables/useEventStoreAPI.ts
- Dead file (~33 LoC) ui/app/composables/useStoreFacets.ts
- Dead file (~29 LoC) ui/app/components/ui/select/SelectContent.vue
- Dead file (~27 LoC) ui/app/components/FacetMultiSelect.vue
- Dead file (~26 LoC) ui/app/components/ui/dropdown-menu/DropdownMenuContent.vue
- Dead file (~25 LoC) ui/app/components/FacetList.vue
- Dead file (~17 LoC) ui/app/components/ui/button/Button.vue
- Dead file (~16 LoC) ui/app/components/ui/select/SelectTrigger.vue
- Unused dependency 'vue-tsc'
- Async function without AbortSignal: execute docs/.vitepress/theme/composables/useTourRunner.ts:29
- Untrusted text written into markup unescaped ui/app/components/JsonView.vue:54
Minor — 16 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs found
- Projects may be oversized for their cohesion
- High interface indirection
- REDACTED
- No ADRs
- Logging is not universal
- No SAST REDACTED:6
- Dependabot does not watch github-actions/npm REDACTED:2
- No release approval gate
- No security response headers detected vercel.json:1
- Not all functions that make a request accept a context.Context or an AbortSignal
- Strict null checking is not enabled everywhere the repository type-checks
Minor — 5 finding(s)
- Outdated: github.com/jackc/pgx/v5
- Outdated: github.com/nats-io/nats.go
- Outdated: go.mongodb.org/mongo-driver/v2
- Outdated: golang.org/x/sync
- Outdated: google.golang.org/grpc
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-778e1c4819384d84bd979cb240d8055a/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-778e1c4819384d84bd979cb240d8055a/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 --exclude aggregate/snapshot/mocks --exclude api/proto/gen/projection --exclude test/mock_test . | 23 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 32 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 13 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 12 file(s) — `aggregate/consistency.go`, `aggregate/history.go`, `aggregate/repository.go`, `aggregate/repository/cached.go`, `backend/postgres/store.go`, … (+7 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |