Executive summary
trustbit/Contexture falls short of our standard for a preview release because we found no automated security scanning of the code, its secrets or its dependencies, and two passwords or keys sit in the current code. It scores 53 out of 100 and is rated Adequate, and 62 of its 68 critical findings are security problems.
Production Readiness, at 50, is the weakest lens, level with Maturity, and counts most in the score. The best first step is recording design decisions, worth about 3 points. Replacing the two exposed passwords or keys and switching the old ones off comes next, worth about 2 points.
Thirty-six known security holes in the packages the code depends on can be used by attackers. Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and four secrets can leak from the build pipeline. Updating the vulnerable packages, pinning each tool to an exact version and limiting each secret to its own step would close these risks. The three unsafe settings in infrastructure or container files need changing to safe values. The two passwords or keys in the code need replacing, with the old ones switched off. The button or link with no name needs a name, even when it only shows an icon.
The product code is 18,077 lines, about €24,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 10 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net7.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net7.0 REDACTED
- Visual & motion safety · Low contrast Tailwind colour pair (3.6:1) frontend-vue/src/components/bounded-context/namespace/ContextureNamespaces.vue
- Visual & motion safety · Low contrast Tailwind colour pair (3.8:1) frontend-vue/src/components/core/navbar/ContextureNavbar.vue
- Visual & motion safety · Low contrast Tailwind colour pair (3.6:1) frontend-vue/src/components/primitives/button/ContexturePrimaryButton.vue
- Visual & motion safety · Low contrast Tailwind colour pair (3.8:1) frontend-vue/src/components/primitives/button/ContextureWhiteButton.vue
- Visual & motion safety · Low contrast Tailwind colour pair (3.8:1) frontend-vue/src/components/primitives/input/ContextureSearch.vue
- Visual & motion safety · Low contrast Tailwind colour pair (3.6:1) frontend-vue/src/pages/domain-details/DomainDetails.vue
Fixed since the last survey: 9 findings
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net7.0 REDACTED
- Code Duplication · Duplicated block (8 lines × 2 locations) frontend-vue/src/visualisations/HierarchicalEdge.js
- Code Duplication · Duplicated block (7 lines × 2 locations) frontend-vue/src/pages/domain-details/DomainDetails.vue
- Code Duplication · Duplicated block (7 lines × 2 locations) frontend-vue/src/stores/collaborations.ts
- Code Duplication · Duplicated block (7 lines × 2 locations) frontend-vue/src/visualisations/Bubble.js
- Page structure · <html> without a lang backend/Contexture.Api/Views/Views.fs
- Page structure · Document without a <title> backend/Contexture.Api/Views/Views.fs
- Page structure · Page without a main landmark backend/Contexture.Api/Views/Views.fs
Rebuild cost: about €24,000 · Estimate
| Cost to rebuild | €8,000 to €40,000, for 134 to 426 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 53. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 18,077 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 Contexture.Api.Aggregates.BoundedContext.ValueObjects | 2 Contexture.Api.Aggregates.Collaboration | 3 Contexture.Api.Aggregates.Domain | 4 Contexture.Api.Aggregates.Namespace | 5 Contexture.Api.Aggregates.NamespaceTemplate | 6 Contexture.Api.AllEvents | 7 Contexture.Api.CommandHandler | 8 Contexture.Api.ReadModels.Find | 9 frontend-vue.src.stores | 10 Contexture.Api.Aggregates.BoundedContext | 11 Contexture.Api.Aggregates.Namespace.Projections | 12 Contexture.Api.Aggregates.NamespaceTemplate.Projections | 13 Contexture.Api.Infrastructure.Subscriptions | 14 Contexture.Api.Aggregates.BoundedContext.Projections | 15 Contexture.Api.FileBased.Database.Serialization | 16 Contexture.Api.Infrastructure.Storage | 17 Contexture.Api.Apis.BoundedContexts.Results | 18 Contexture.Api.Apis.Domains.Results | 19 Contexture.Api.FileBased.Database | 20 Contexture.Api.Infrastructure | 21 Contexture.Api.FileBased.Convert.BoundedContext | 22 Contexture.Api.FileBased.Convert.Collaboration | 23 Contexture.Api.FileBased.Convert.Domain | 24 Contexture.Api.FileBased.Convert.Namespace | 25 Contexture.Api.FileBased.Convert.NamespaceTemplate | 26 Contexture.Api.Infrastructure.Projections | 27 Contexture.Api.Infrastructure.ReadModels | 28 Contexture.Api.Infrastructure.Subscriptions.PositionStorage | 29 Contexture.Api.Reactions | 30 Contexture.Api.ReadModels.BoundedContext | 31 Contexture.Api.ReadModels.Domain | 32 Contexture.Api.ReadModels.EventLog | 33 Contexture.Api.ReadModels.Find.BoundedContexts | 34 Contexture.Api.ReadModels.Find.Domains | 35 Contexture.Api.ReadModels.Find.Labels | 36 Contexture.Api.ReadModels.Find.Namespaces | 37 Contexture.Api.ReadModels.Namespace | 38 Contexture.Api.ReadModels.Templates | 39 Contexture.Api.Apis.BoundedContexts.QueryEndpoints | 40 Contexture.Api.Reactions.ReactionInitializationModule |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Contexture.Api.Aggregates.BoundedContext.ValueObjects | ||||||||||||||||||||||||||||||||||||||||
| 2 Contexture.Api.Aggregates.Collaboration | ||||||||||||||||||||||||||||||||||||||||
| 3 Contexture.Api.Aggregates.Domain | ||||||||||||||||||||||||||||||||||||||||
| 4 Contexture.Api.Aggregates.Namespace | ||||||||||||||||||||||||||||||||||||||||
| 5 Contexture.Api.Aggregates.NamespaceTemplate | ||||||||||||||||||||||||||||||||||||||||
| 6 Contexture.Api.AllEvents | ||||||||||||||||||||||||||||||||||||||||
| 7 Contexture.Api.CommandHandler | ||||||||||||||||||||||||||||||||||||||||
| 8 Contexture.Api.ReadModels.Find | ||||||||||||||||||||||||||||||||||||||||
| 9 frontend-vue.src.stores | ||||||||||||||||||||||||||||||||||||||||
| 10 Contexture.Api.Aggregates.BoundedContext | 15 | |||||||||||||||||||||||||||||||||||||||
| 11 Contexture.Api.Aggregates.Namespace.Projections | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 Contexture.Api.Aggregates.NamespaceTemplate.Projections | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 Contexture.Api.Infrastructure.Subscriptions | 5 | |||||||||||||||||||||||||||||||||||||||
| 14 Contexture.Api.Aggregates.BoundedContext.Projections | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 Contexture.Api.FileBased.Database.Serialization | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 Contexture.Api.Infrastructure.Storage | 2 | 7 | ||||||||||||||||||||||||||||||||||||||
| 17 Contexture.Api.Apis.BoundedContexts.Results | 5 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 18 Contexture.Api.Apis.Domains.Results | 5 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 Contexture.Api.FileBased.Database | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 20 Contexture.Api.Infrastructure | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Contexture.Api.FileBased.Convert.BoundedContext | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 22 Contexture.Api.FileBased.Convert.Collaboration | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 23 Contexture.Api.FileBased.Convert.Domain | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 24 Contexture.Api.FileBased.Convert.Namespace | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 25 Contexture.Api.FileBased.Convert.NamespaceTemplate | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 26 Contexture.Api.Infrastructure.Projections | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 Contexture.Api.Infrastructure.ReadModels | 2 | 5 | ||||||||||||||||||||||||||||||||||||||
| 28 Contexture.Api.Infrastructure.Subscriptions.PositionStorage | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 Contexture.Api.Reactions | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 Contexture.Api.ReadModels.BoundedContext | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 Contexture.Api.ReadModels.Domain | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 Contexture.Api.ReadModels.EventLog | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 33 Contexture.Api.ReadModels.Find.BoundedContexts | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 Contexture.Api.ReadModels.Find.Domains | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 Contexture.Api.ReadModels.Find.Labels | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 Contexture.Api.ReadModels.Find.Namespaces | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 Contexture.Api.ReadModels.Namespace | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 Contexture.Api.ReadModels.Templates | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 Contexture.Api.Apis.BoundedContexts.QueryEndpoints | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 Contexture.Api.Reactions.ReactionInitializationModule | 2 | 1 | 2 | 2 | 4 |
10→1 Contexture.Api.Aggregates.BoundedContext uses Contexture.Api.Aggregates.BoundedContext.ValueObjects✕
- Connections
- 15 pairs of types, where a type in Contexture.Api.Aggregates.BoundedContext uses a type in Contexture.Api.Aggregates.BoundedContext.ValueObjects.
- The types involved
Contexture.Api.Aggregates.BoundedContext.BoundedContextImported→Contexture.Api.Aggregates.BoundedContext.ValueObjects.BusinessDecisionContexture.Api.Aggregates.BoundedContext.BoundedContextImported→Contexture.Api.Aggregates.BoundedContext.ValueObjects.DomainRoleContexture.Api.Aggregates.BoundedContext.BoundedContextImported→Contexture.Api.Aggregates.BoundedContext.ValueObjects.MessagesContexture.Api.Aggregates.BoundedContext.BoundedContextImported→Contexture.Api.Aggregates.BoundedContext.ValueObjects.StrategicClassificationContexture.Api.Aggregates.BoundedContext.BoundedContextImported→Contexture.Api.Aggregates.BoundedContext.ValueObjects.UbiquitousLanguageTermContexture.Api.Aggregates.BoundedContext.BoundedContextReclassified→Contexture.Api.Aggregates.BoundedContext.ValueObjects.StrategicClassificationContexture.Api.Aggregates.BoundedContext.BusinessDecisionsUpdated→Contexture.Api.Aggregates.BoundedContext.ValueObjects.BusinessDecisionContexture.Api.Aggregates.BoundedContext.DomainRolesUpdated→Contexture.Api.Aggregates.BoundedContext.ValueObjects.DomainRoleContexture.Api.Aggregates.BoundedContext.MessagesUpdated→Contexture.Api.Aggregates.BoundedContext.ValueObjects.MessagesContexture.Api.Aggregates.BoundedContext.ReclassifyBoundedContext→Contexture.Api.Aggregates.BoundedContext.ValueObjects.StrategicClassificationContexture.Api.Aggregates.BoundedContext.UbiquitousLanguageUpdated→Contexture.Api.Aggregates.BoundedContext.ValueObjects.UbiquitousLanguageTermContexture.Api.Aggregates.BoundedContext.UpdateBusinessDecisions→Contexture.Api.Aggregates.BoundedContext.ValueObjects.BusinessDecisionContexture.Api.Aggregates.BoundedContext.UpdateDomainRoles→Contexture.Api.Aggregates.BoundedContext.ValueObjects.DomainRoleContexture.Api.Aggregates.BoundedContext.UpdateMessages→Contexture.Api.Aggregates.BoundedContext.ValueObjects.MessagesContexture.Api.Aggregates.BoundedContext.UpdateUbiquitousLanguage→Contexture.Api.Aggregates.BoundedContext.ValueObjects.UbiquitousLanguageTerm
- Direction
- Contexture.Api.Aggregates.BoundedContext uses Contexture.Api.Aggregates.BoundedContext.ValueObjects, so a change to Contexture.Api.Aggregates.BoundedContext.ValueObjects can break Contexture.Api.Aggregates.BoundedContext, while a change to Contexture.Api.Aggregates.BoundedContext can't break Contexture.Api.Aggregates.BoundedContext.ValueObjects.
- Position
- Below the diagonal: Contexture.Api.Aggregates.BoundedContext uses a module listed above it, which is the healthy direction.
11→4 Contexture.Api.Aggregates.Namespace.Projections uses Contexture.Api.Aggregates.Namespace✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.Aggregates.Namespace.Projections uses a type in Contexture.Api.Aggregates.Namespace.
- The types involved
Contexture.Api.Aggregates.Namespace.Projections.Projections→Contexture.Api.Aggregates.Namespace.EventContexture.Api.Aggregates.Namespace.Projections.Projections→Contexture.Api.Aggregates.Namespace.LabelDefinition
- Direction
- Contexture.Api.Aggregates.Namespace.Projections uses Contexture.Api.Aggregates.Namespace, so a change to Contexture.Api.Aggregates.Namespace can break Contexture.Api.Aggregates.Namespace.Projections, while a change to Contexture.Api.Aggregates.Namespace.Projections can't break Contexture.Api.Aggregates.Namespace.
- Position
- Below the diagonal: Contexture.Api.Aggregates.Namespace.Projections uses a module listed above it, which is the healthy direction.
12→5 Contexture.Api.Aggregates.NamespaceTemplate.Projections uses Contexture.Api.Aggregates.NamespaceTemplate✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.Aggregates.NamespaceTemplate.Projections uses a type in Contexture.Api.Aggregates.NamespaceTemplate.
- The types involved
Contexture.Api.Aggregates.NamespaceTemplate.Projections.Projections→Contexture.Api.Aggregates.NamespaceTemplate.EventContexture.Api.Aggregates.NamespaceTemplate.Projections.Projections→Contexture.Api.Aggregates.NamespaceTemplate.TemplateLabelDefinition
- Direction
- Contexture.Api.Aggregates.NamespaceTemplate.Projections uses Contexture.Api.Aggregates.NamespaceTemplate, so a change to Contexture.Api.Aggregates.NamespaceTemplate can break Contexture.Api.Aggregates.NamespaceTemplate.Projections, while a change to Contexture.Api.Aggregates.NamespaceTemplate.Projections can't break Contexture.Api.Aggregates.NamespaceTemplate.
- Position
- Below the diagonal: Contexture.Api.Aggregates.NamespaceTemplate.Projections uses a module listed above it, which is the healthy direction.
13→20 Contexture.Api.Infrastructure.Subscriptions uses Contexture.Api.Infrastructure part of a loop✕
- Connections
- 5 pairs of types, where a type in Contexture.Api.Infrastructure.Subscriptions uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.Infrastructure.Subscriptions.SubscriptionDefinition→Contexture.Api.Infrastructure.StreamIdentifierContexture.Api.Infrastructure.Subscriptions.SubscriptionDefinition→Contexture.Api.Infrastructure.StreamKindContexture.Api.Infrastructure.Subscriptions.SubscriptionDefinition→Contexture.Api.Infrastructure.VersionContexture.Api.Infrastructure.Subscriptions.SubscriptionStartingPosition→Contexture.Api.Infrastructure.PositionContexture.Api.Infrastructure.Subscriptions.SubscriptionStatus→Contexture.Api.Infrastructure.Position
- Direction
- Contexture.Api.Infrastructure.Subscriptions uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.Infrastructure.Subscriptions, while a change to Contexture.Api.Infrastructure.Subscriptions can't break Contexture.Api.Infrastructure.
- 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.
14→1 Contexture.Api.Aggregates.BoundedContext.Projections uses Contexture.Api.Aggregates.BoundedContext.ValueObjects✕
- Connections
- 5 pairs of types, where a type in Contexture.Api.Aggregates.BoundedContext.Projections uses a type in Contexture.Api.Aggregates.BoundedContext.ValueObjects.
- The types involved
Contexture.Api.Aggregates.BoundedContext.Projections.BoundedContext→Contexture.Api.Aggregates.BoundedContext.ValueObjects.BusinessDecisionContexture.Api.Aggregates.BoundedContext.Projections.BoundedContext→Contexture.Api.Aggregates.BoundedContext.ValueObjects.DomainRoleContexture.Api.Aggregates.BoundedContext.Projections.BoundedContext→Contexture.Api.Aggregates.BoundedContext.ValueObjects.MessagesContexture.Api.Aggregates.BoundedContext.Projections.BoundedContext→Contexture.Api.Aggregates.BoundedContext.ValueObjects.StrategicClassificationContexture.Api.Aggregates.BoundedContext.Projections.BoundedContext→Contexture.Api.Aggregates.BoundedContext.ValueObjects.UbiquitousLanguageTerm
- Direction
- Contexture.Api.Aggregates.BoundedContext.Projections uses Contexture.Api.Aggregates.BoundedContext.ValueObjects, so a change to Contexture.Api.Aggregates.BoundedContext.ValueObjects can break Contexture.Api.Aggregates.BoundedContext.Projections, while a change to Contexture.Api.Aggregates.BoundedContext.Projections can't break Contexture.Api.Aggregates.BoundedContext.ValueObjects.
- Position
- Below the diagonal: Contexture.Api.Aggregates.BoundedContext.Projections uses a module listed above it, which is the healthy direction.
14→10 Contexture.Api.Aggregates.BoundedContext.Projections uses Contexture.Api.Aggregates.BoundedContext✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Aggregates.BoundedContext.Projections uses a type in Contexture.Api.Aggregates.BoundedContext.
- The types involved
Contexture.Api.Aggregates.BoundedContext.Projections.Projections→Contexture.Api.Aggregates.BoundedContext.Event
- Direction
- Contexture.Api.Aggregates.BoundedContext.Projections uses Contexture.Api.Aggregates.BoundedContext, so a change to Contexture.Api.Aggregates.BoundedContext can break Contexture.Api.Aggregates.BoundedContext.Projections, while a change to Contexture.Api.Aggregates.BoundedContext.Projections can't break Contexture.Api.Aggregates.BoundedContext.
- Position
- Below the diagonal: Contexture.Api.Aggregates.BoundedContext.Projections uses a module listed above it, which is the healthy direction.
15→1 Contexture.Api.FileBased.Database.Serialization uses Contexture.Api.Aggregates.BoundedContext.ValueObjects✕
- Connections
- 5 pairs of types, where a type in Contexture.Api.FileBased.Database.Serialization uses a type in Contexture.Api.Aggregates.BoundedContext.ValueObjects.
- The types involved
Contexture.Api.FileBased.Database.Serialization.BoundedContext→Contexture.Api.Aggregates.BoundedContext.ValueObjects.BusinessDecisionContexture.Api.FileBased.Database.Serialization.BoundedContext→Contexture.Api.Aggregates.BoundedContext.ValueObjects.DomainRoleContexture.Api.FileBased.Database.Serialization.BoundedContext→Contexture.Api.Aggregates.BoundedContext.ValueObjects.MessagesContexture.Api.FileBased.Database.Serialization.BoundedContext→Contexture.Api.Aggregates.BoundedContext.ValueObjects.StrategicClassificationContexture.Api.FileBased.Database.Serialization.BoundedContext→Contexture.Api.Aggregates.BoundedContext.ValueObjects.UbiquitousLanguageTerm
- Direction
- Contexture.Api.FileBased.Database.Serialization uses Contexture.Api.Aggregates.BoundedContext.ValueObjects, so a change to Contexture.Api.Aggregates.BoundedContext.ValueObjects can break Contexture.Api.FileBased.Database.Serialization, while a change to Contexture.Api.FileBased.Database.Serialization can't break Contexture.Api.Aggregates.BoundedContext.ValueObjects.
- Position
- Below the diagonal: Contexture.Api.FileBased.Database.Serialization uses a module listed above it, which is the healthy direction.
15→11 Contexture.Api.FileBased.Database.Serialization uses Contexture.Api.Aggregates.Namespace.Projections✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Database.Serialization uses a type in Contexture.Api.Aggregates.Namespace.Projections.
- The types involved
Contexture.Api.FileBased.Database.Serialization.BoundedContext→Contexture.Api.Aggregates.Namespace.Projections.Namespace
- Direction
- Contexture.Api.FileBased.Database.Serialization uses Contexture.Api.Aggregates.Namespace.Projections, so a change to Contexture.Api.Aggregates.Namespace.Projections can break Contexture.Api.FileBased.Database.Serialization, while a change to Contexture.Api.FileBased.Database.Serialization can't break Contexture.Api.Aggregates.Namespace.Projections.
- Position
- Below the diagonal: Contexture.Api.FileBased.Database.Serialization uses a module listed above it, which is the healthy direction.
15→12 Contexture.Api.FileBased.Database.Serialization uses Contexture.Api.Aggregates.NamespaceTemplate.Projections✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Database.Serialization uses a type in Contexture.Api.Aggregates.NamespaceTemplate.Projections.
- The types involved
Contexture.Api.FileBased.Database.Serialization.Root→Contexture.Api.Aggregates.NamespaceTemplate.Projections.NamespaceTemplate
- Direction
- Contexture.Api.FileBased.Database.Serialization uses Contexture.Api.Aggregates.NamespaceTemplate.Projections, so a change to Contexture.Api.Aggregates.NamespaceTemplate.Projections can break Contexture.Api.FileBased.Database.Serialization, while a change to Contexture.Api.FileBased.Database.Serialization can't break Contexture.Api.Aggregates.NamespaceTemplate.Projections.
- Position
- Below the diagonal: Contexture.Api.FileBased.Database.Serialization uses a module listed above it, which is the healthy direction.
16→13 Contexture.Api.Infrastructure.Storage uses Contexture.Api.Infrastructure.Subscriptions✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.Infrastructure.Storage uses a type in Contexture.Api.Infrastructure.Subscriptions.
- The types involved
Contexture.Api.Infrastructure.Storage.EventStorage→Contexture.Api.Infrastructure.Subscriptions.SubscriptionContexture.Api.Infrastructure.Storage.EventStorage→Contexture.Api.Infrastructure.Subscriptions.SubscriptionDefinition
- Direction
- Contexture.Api.Infrastructure.Storage uses Contexture.Api.Infrastructure.Subscriptions, so a change to Contexture.Api.Infrastructure.Subscriptions can break Contexture.Api.Infrastructure.Storage, while a change to Contexture.Api.Infrastructure.Storage can't break Contexture.Api.Infrastructure.Subscriptions.
- Position
- Below the diagonal: Contexture.Api.Infrastructure.Storage uses a module listed above it, which is the healthy direction.
16→20 Contexture.Api.Infrastructure.Storage uses Contexture.Api.Infrastructure part of a loop✕
- Connections
- 7 pairs of types, where a type in Contexture.Api.Infrastructure.Storage uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.Infrastructure.Storage.EventDefinition→Contexture.Api.Infrastructure.StreamKindContexture.Api.Infrastructure.Storage.EventStorage→Contexture.Api.Infrastructure.AppendErrorContexture.Api.Infrastructure.Storage.EventStorage→Contexture.Api.Infrastructure.ExpectedVersionContexture.Api.Infrastructure.Storage.EventStorage→Contexture.Api.Infrastructure.NonEmptyList`1Contexture.Api.Infrastructure.Storage.EventStorage→Contexture.Api.Infrastructure.StreamIdentifierContexture.Api.Infrastructure.Storage.EventStorage→Contexture.Api.Infrastructure.StreamKindContexture.Api.Infrastructure.Storage.EventStorage→Contexture.Api.Infrastructure.Version
- Direction
- Contexture.Api.Infrastructure.Storage uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.Infrastructure.Storage, while a change to Contexture.Api.Infrastructure.Storage can't break Contexture.Api.Infrastructure.
- 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.
17→1 Contexture.Api.Apis.BoundedContexts.Results uses Contexture.Api.Aggregates.BoundedContext.ValueObjects✕
- Connections
- 5 pairs of types, where a type in Contexture.Api.Apis.BoundedContexts.Results uses a type in Contexture.Api.Aggregates.BoundedContext.ValueObjects.
- The types involved
Contexture.Api.Apis.BoundedContexts.Results.BoundedContextResult→Contexture.Api.Aggregates.BoundedContext.ValueObjects.BusinessDecisionContexture.Api.Apis.BoundedContexts.Results.BoundedContextResult→Contexture.Api.Aggregates.BoundedContext.ValueObjects.DomainRoleContexture.Api.Apis.BoundedContexts.Results.BoundedContextResult→Contexture.Api.Aggregates.BoundedContext.ValueObjects.MessagesContexture.Api.Apis.BoundedContexts.Results.BoundedContextResult→Contexture.Api.Aggregates.BoundedContext.ValueObjects.StrategicClassificationContexture.Api.Apis.BoundedContexts.Results.BoundedContextResult→Contexture.Api.Aggregates.BoundedContext.ValueObjects.UbiquitousLanguageTerm
- Direction
- Contexture.Api.Apis.BoundedContexts.Results uses Contexture.Api.Aggregates.BoundedContext.ValueObjects, so a change to Contexture.Api.Aggregates.BoundedContext.ValueObjects can break Contexture.Api.Apis.BoundedContexts.Results, while a change to Contexture.Api.Apis.BoundedContexts.Results can't break Contexture.Api.Aggregates.BoundedContext.ValueObjects.
- Position
- Below the diagonal: Contexture.Api.Apis.BoundedContexts.Results uses a module listed above it, which is the healthy direction.
17→3 Contexture.Api.Apis.BoundedContexts.Results uses Contexture.Api.Aggregates.Domain✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Apis.BoundedContexts.Results uses a type in Contexture.Api.Aggregates.Domain.
- The types involved
Contexture.Api.Apis.BoundedContexts.Results.BoundedContextResult→Contexture.Api.Aggregates.Domain.Domain
- Direction
- Contexture.Api.Apis.BoundedContexts.Results uses Contexture.Api.Aggregates.Domain, so a change to Contexture.Api.Aggregates.Domain can break Contexture.Api.Apis.BoundedContexts.Results, while a change to Contexture.Api.Apis.BoundedContexts.Results can't break Contexture.Api.Aggregates.Domain.
- Position
- Below the diagonal: Contexture.Api.Apis.BoundedContexts.Results uses a module listed above it, which is the healthy direction.
17→11 Contexture.Api.Apis.BoundedContexts.Results uses Contexture.Api.Aggregates.Namespace.Projections✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Apis.BoundedContexts.Results uses a type in Contexture.Api.Aggregates.Namespace.Projections.
- The types involved
Contexture.Api.Apis.BoundedContexts.Results.BoundedContextResult→Contexture.Api.Aggregates.Namespace.Projections.Namespace
- Direction
- Contexture.Api.Apis.BoundedContexts.Results uses Contexture.Api.Aggregates.Namespace.Projections, so a change to Contexture.Api.Aggregates.Namespace.Projections can break Contexture.Api.Apis.BoundedContexts.Results, while a change to Contexture.Api.Apis.BoundedContexts.Results can't break Contexture.Api.Aggregates.Namespace.Projections.
- Position
- Below the diagonal: Contexture.Api.Apis.BoundedContexts.Results uses a module listed above it, which is the healthy direction.
17→14 Contexture.Api.Apis.BoundedContexts.Results uses Contexture.Api.Aggregates.BoundedContext.Projections✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Apis.BoundedContexts.Results uses a type in Contexture.Api.Aggregates.BoundedContext.Projections.
- The types involved
Contexture.Api.Apis.BoundedContexts.Results.Results→Contexture.Api.Aggregates.BoundedContext.Projections.BoundedContext
- Direction
- Contexture.Api.Apis.BoundedContexts.Results uses Contexture.Api.Aggregates.BoundedContext.Projections, so a change to Contexture.Api.Aggregates.BoundedContext.Projections can break Contexture.Api.Apis.BoundedContexts.Results, while a change to Contexture.Api.Apis.BoundedContexts.Results can't break Contexture.Api.Aggregates.BoundedContext.Projections.
- Position
- Below the diagonal: Contexture.Api.Apis.BoundedContexts.Results uses a module listed above it, which is the healthy direction.
18→1 Contexture.Api.Apis.Domains.Results uses Contexture.Api.Aggregates.BoundedContext.ValueObjects✕
- Connections
- 5 pairs of types, where a type in Contexture.Api.Apis.Domains.Results uses a type in Contexture.Api.Aggregates.BoundedContext.ValueObjects.
- The types involved
Contexture.Api.Apis.Domains.Results.BoundedContextResult→Contexture.Api.Aggregates.BoundedContext.ValueObjects.BusinessDecisionContexture.Api.Apis.Domains.Results.BoundedContextResult→Contexture.Api.Aggregates.BoundedContext.ValueObjects.DomainRoleContexture.Api.Apis.Domains.Results.BoundedContextResult→Contexture.Api.Aggregates.BoundedContext.ValueObjects.MessagesContexture.Api.Apis.Domains.Results.BoundedContextResult→Contexture.Api.Aggregates.BoundedContext.ValueObjects.StrategicClassificationContexture.Api.Apis.Domains.Results.BoundedContextResult→Contexture.Api.Aggregates.BoundedContext.ValueObjects.UbiquitousLanguageTerm
- Direction
- Contexture.Api.Apis.Domains.Results uses Contexture.Api.Aggregates.BoundedContext.ValueObjects, so a change to Contexture.Api.Aggregates.BoundedContext.ValueObjects can break Contexture.Api.Apis.Domains.Results, while a change to Contexture.Api.Apis.Domains.Results can't break Contexture.Api.Aggregates.BoundedContext.ValueObjects.
- Position
- Below the diagonal: Contexture.Api.Apis.Domains.Results uses a module listed above it, which is the healthy direction.
18→3 Contexture.Api.Apis.Domains.Results uses Contexture.Api.Aggregates.Domain✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Apis.Domains.Results uses a type in Contexture.Api.Aggregates.Domain.
- The types involved
Contexture.Api.Apis.Domains.Results.Results→Contexture.Api.Aggregates.Domain.Domain
- Direction
- Contexture.Api.Apis.Domains.Results uses Contexture.Api.Aggregates.Domain, so a change to Contexture.Api.Aggregates.Domain can break Contexture.Api.Apis.Domains.Results, while a change to Contexture.Api.Apis.Domains.Results can't break Contexture.Api.Aggregates.Domain.
- Position
- Below the diagonal: Contexture.Api.Apis.Domains.Results uses a module listed above it, which is the healthy direction.
18→11 Contexture.Api.Apis.Domains.Results uses Contexture.Api.Aggregates.Namespace.Projections✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Apis.Domains.Results uses a type in Contexture.Api.Aggregates.Namespace.Projections.
- The types involved
Contexture.Api.Apis.Domains.Results.BoundedContextResult→Contexture.Api.Aggregates.Namespace.Projections.Namespace
- Direction
- Contexture.Api.Apis.Domains.Results uses Contexture.Api.Aggregates.Namespace.Projections, so a change to Contexture.Api.Aggregates.Namespace.Projections can break Contexture.Api.Apis.Domains.Results, while a change to Contexture.Api.Apis.Domains.Results can't break Contexture.Api.Aggregates.Namespace.Projections.
- Position
- Below the diagonal: Contexture.Api.Apis.Domains.Results uses a module listed above it, which is the healthy direction.
18→14 Contexture.Api.Apis.Domains.Results uses Contexture.Api.Aggregates.BoundedContext.Projections✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Apis.Domains.Results uses a type in Contexture.Api.Aggregates.BoundedContext.Projections.
- The types involved
Contexture.Api.Apis.Domains.Results.Results→Contexture.Api.Aggregates.BoundedContext.Projections.BoundedContext
- Direction
- Contexture.Api.Apis.Domains.Results uses Contexture.Api.Aggregates.BoundedContext.Projections, so a change to Contexture.Api.Aggregates.BoundedContext.Projections can break Contexture.Api.Apis.Domains.Results, while a change to Contexture.Api.Apis.Domains.Results can't break Contexture.Api.Aggregates.BoundedContext.Projections.
- Position
- Below the diagonal: Contexture.Api.Apis.Domains.Results uses a module listed above it, which is the healthy direction.
19→12 Contexture.Api.FileBased.Database uses Contexture.Api.Aggregates.NamespaceTemplate.Projections✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Database uses a type in Contexture.Api.Aggregates.NamespaceTemplate.Projections.
- The types involved
Contexture.Api.FileBased.Database.Document→Contexture.Api.Aggregates.NamespaceTemplate.Projections.NamespaceTemplate
- Direction
- Contexture.Api.FileBased.Database uses Contexture.Api.Aggregates.NamespaceTemplate.Projections, so a change to Contexture.Api.Aggregates.NamespaceTemplate.Projections can break Contexture.Api.FileBased.Database, while a change to Contexture.Api.FileBased.Database can't break Contexture.Api.Aggregates.NamespaceTemplate.Projections.
- Position
- Below the diagonal: Contexture.Api.FileBased.Database uses a module listed above it, which is the healthy direction.
19→15 Contexture.Api.FileBased.Database uses Contexture.Api.FileBased.Database.Serialization✕
- Connections
- 3 pairs of types, where a type in Contexture.Api.FileBased.Database uses a type in Contexture.Api.FileBased.Database.Serialization.
- The types involved
Contexture.Api.FileBased.Database.Document→Contexture.Api.FileBased.Database.Serialization.BoundedContextContexture.Api.FileBased.Database.Document→Contexture.Api.FileBased.Database.Serialization.CollaborationContexture.Api.FileBased.Database.Document→Contexture.Api.FileBased.Database.Serialization.Domain
- Direction
- Contexture.Api.FileBased.Database uses Contexture.Api.FileBased.Database.Serialization, so a change to Contexture.Api.FileBased.Database.Serialization can break Contexture.Api.FileBased.Database, while a change to Contexture.Api.FileBased.Database can't break Contexture.Api.FileBased.Database.Serialization.
- Position
- Below the diagonal: Contexture.Api.FileBased.Database uses a module listed above it, which is the healthy direction.
20→13 Contexture.Api.Infrastructure uses Contexture.Api.Infrastructure.Subscriptions✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.Infrastructure uses a type in Contexture.Api.Infrastructure.Subscriptions.
- The types involved
Contexture.Api.Infrastructure.EventStore→Contexture.Api.Infrastructure.Subscriptions.SubscriptionContexture.Api.Infrastructure.EventStore→Contexture.Api.Infrastructure.Subscriptions.SubscriptionStartingPosition
- Direction
- Contexture.Api.Infrastructure uses Contexture.Api.Infrastructure.Subscriptions, so a change to Contexture.Api.Infrastructure.Subscriptions can break Contexture.Api.Infrastructure, while a change to Contexture.Api.Infrastructure can't break Contexture.Api.Infrastructure.Subscriptions.
- Position
- Below the diagonal: Contexture.Api.Infrastructure uses a module listed above it, which is the healthy direction.
20→16 Contexture.Api.Infrastructure uses Contexture.Api.Infrastructure.Storage✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Infrastructure uses a type in Contexture.Api.Infrastructure.Storage.
- The types involved
Contexture.Api.Infrastructure.EventStore→Contexture.Api.Infrastructure.Storage.EventStorage
- Direction
- Contexture.Api.Infrastructure uses Contexture.Api.Infrastructure.Storage, so a change to Contexture.Api.Infrastructure.Storage can break Contexture.Api.Infrastructure, while a change to Contexture.Api.Infrastructure can't break Contexture.Api.Infrastructure.Storage.
- Position
- Below the diagonal: Contexture.Api.Infrastructure uses a module listed above it, which is the healthy direction.
21→10 Contexture.Api.FileBased.Convert.BoundedContext uses Contexture.Api.Aggregates.BoundedContext✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Convert.BoundedContext uses a type in Contexture.Api.Aggregates.BoundedContext.
- The types involved
Contexture.Api.FileBased.Convert.BoundedContext.BoundedContext→Contexture.Api.Aggregates.BoundedContext.Event
- Direction
- Contexture.Api.FileBased.Convert.BoundedContext uses Contexture.Api.Aggregates.BoundedContext, so a change to Contexture.Api.Aggregates.BoundedContext can break Contexture.Api.FileBased.Convert.BoundedContext, while a change to Contexture.Api.FileBased.Convert.BoundedContext can't break Contexture.Api.Aggregates.BoundedContext.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.BoundedContext uses a module listed above it, which is the healthy direction.
21→15 Contexture.Api.FileBased.Convert.BoundedContext uses Contexture.Api.FileBased.Database.Serialization✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Convert.BoundedContext uses a type in Contexture.Api.FileBased.Database.Serialization.
- The types involved
Contexture.Api.FileBased.Convert.BoundedContext.BoundedContext→Contexture.Api.FileBased.Database.Serialization.BoundedContext
- Direction
- Contexture.Api.FileBased.Convert.BoundedContext uses Contexture.Api.FileBased.Database.Serialization, so a change to Contexture.Api.FileBased.Database.Serialization can break Contexture.Api.FileBased.Convert.BoundedContext, while a change to Contexture.Api.FileBased.Convert.BoundedContext can't break Contexture.Api.FileBased.Database.Serialization.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.BoundedContext uses a module listed above it, which is the healthy direction.
21→19 Contexture.Api.FileBased.Convert.BoundedContext uses Contexture.Api.FileBased.Database✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Convert.BoundedContext uses a type in Contexture.Api.FileBased.Database.
- The types involved
Contexture.Api.FileBased.Convert.BoundedContext.BoundedContext→Contexture.Api.FileBased.Database.SingleFileBasedDatastore
- Direction
- Contexture.Api.FileBased.Convert.BoundedContext uses Contexture.Api.FileBased.Database, so a change to Contexture.Api.FileBased.Database can break Contexture.Api.FileBased.Convert.BoundedContext, while a change to Contexture.Api.FileBased.Convert.BoundedContext can't break Contexture.Api.FileBased.Database.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.BoundedContext uses a module listed above it, which is the healthy direction.
21→20 Contexture.Api.FileBased.Convert.BoundedContext uses Contexture.Api.Infrastructure✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.FileBased.Convert.BoundedContext uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.FileBased.Convert.BoundedContext.BoundedContext→Contexture.Api.Infrastructure.EventEnvelope`1Contexture.Api.FileBased.Convert.BoundedContext.BoundedContext→Contexture.Api.Infrastructure.Position
- Direction
- Contexture.Api.FileBased.Convert.BoundedContext uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.FileBased.Convert.BoundedContext, while a change to Contexture.Api.FileBased.Convert.BoundedContext can't break Contexture.Api.Infrastructure.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.BoundedContext uses a module listed above it, which is the healthy direction.
22→2 Contexture.Api.FileBased.Convert.Collaboration uses Contexture.Api.Aggregates.Collaboration✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Convert.Collaboration uses a type in Contexture.Api.Aggregates.Collaboration.
- The types involved
Contexture.Api.FileBased.Convert.Collaboration.Collaboration→Contexture.Api.Aggregates.Collaboration.Event
- Direction
- Contexture.Api.FileBased.Convert.Collaboration uses Contexture.Api.Aggregates.Collaboration, so a change to Contexture.Api.Aggregates.Collaboration can break Contexture.Api.FileBased.Convert.Collaboration, while a change to Contexture.Api.FileBased.Convert.Collaboration can't break Contexture.Api.Aggregates.Collaboration.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.Collaboration uses a module listed above it, which is the healthy direction.
22→15 Contexture.Api.FileBased.Convert.Collaboration uses Contexture.Api.FileBased.Database.Serialization✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Convert.Collaboration uses a type in Contexture.Api.FileBased.Database.Serialization.
- The types involved
Contexture.Api.FileBased.Convert.Collaboration.Collaboration→Contexture.Api.FileBased.Database.Serialization.Collaboration
- Direction
- Contexture.Api.FileBased.Convert.Collaboration uses Contexture.Api.FileBased.Database.Serialization, so a change to Contexture.Api.FileBased.Database.Serialization can break Contexture.Api.FileBased.Convert.Collaboration, while a change to Contexture.Api.FileBased.Convert.Collaboration can't break Contexture.Api.FileBased.Database.Serialization.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.Collaboration uses a module listed above it, which is the healthy direction.
22→19 Contexture.Api.FileBased.Convert.Collaboration uses Contexture.Api.FileBased.Database✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Convert.Collaboration uses a type in Contexture.Api.FileBased.Database.
- The types involved
Contexture.Api.FileBased.Convert.Collaboration.Collaboration→Contexture.Api.FileBased.Database.SingleFileBasedDatastore
- Direction
- Contexture.Api.FileBased.Convert.Collaboration uses Contexture.Api.FileBased.Database, so a change to Contexture.Api.FileBased.Database can break Contexture.Api.FileBased.Convert.Collaboration, while a change to Contexture.Api.FileBased.Convert.Collaboration can't break Contexture.Api.FileBased.Database.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.Collaboration uses a module listed above it, which is the healthy direction.
22→20 Contexture.Api.FileBased.Convert.Collaboration uses Contexture.Api.Infrastructure✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.FileBased.Convert.Collaboration uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.FileBased.Convert.Collaboration.Collaboration→Contexture.Api.Infrastructure.EventEnvelope`1Contexture.Api.FileBased.Convert.Collaboration.Collaboration→Contexture.Api.Infrastructure.Position
- Direction
- Contexture.Api.FileBased.Convert.Collaboration uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.FileBased.Convert.Collaboration, while a change to Contexture.Api.FileBased.Convert.Collaboration can't break Contexture.Api.Infrastructure.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.Collaboration uses a module listed above it, which is the healthy direction.
23→3 Contexture.Api.FileBased.Convert.Domain uses Contexture.Api.Aggregates.Domain✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Convert.Domain uses a type in Contexture.Api.Aggregates.Domain.
- The types involved
Contexture.Api.FileBased.Convert.Domain.Domain→Contexture.Api.Aggregates.Domain.Event
- Direction
- Contexture.Api.FileBased.Convert.Domain uses Contexture.Api.Aggregates.Domain, so a change to Contexture.Api.Aggregates.Domain can break Contexture.Api.FileBased.Convert.Domain, while a change to Contexture.Api.FileBased.Convert.Domain can't break Contexture.Api.Aggregates.Domain.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.Domain uses a module listed above it, which is the healthy direction.
23→15 Contexture.Api.FileBased.Convert.Domain uses Contexture.Api.FileBased.Database.Serialization✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Convert.Domain uses a type in Contexture.Api.FileBased.Database.Serialization.
- The types involved
Contexture.Api.FileBased.Convert.Domain.Domain→Contexture.Api.FileBased.Database.Serialization.Domain
- Direction
- Contexture.Api.FileBased.Convert.Domain uses Contexture.Api.FileBased.Database.Serialization, so a change to Contexture.Api.FileBased.Database.Serialization can break Contexture.Api.FileBased.Convert.Domain, while a change to Contexture.Api.FileBased.Convert.Domain can't break Contexture.Api.FileBased.Database.Serialization.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.Domain uses a module listed above it, which is the healthy direction.
23→19 Contexture.Api.FileBased.Convert.Domain uses Contexture.Api.FileBased.Database✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Convert.Domain uses a type in Contexture.Api.FileBased.Database.
- The types involved
Contexture.Api.FileBased.Convert.Domain.Domain→Contexture.Api.FileBased.Database.SingleFileBasedDatastore
- Direction
- Contexture.Api.FileBased.Convert.Domain uses Contexture.Api.FileBased.Database, so a change to Contexture.Api.FileBased.Database can break Contexture.Api.FileBased.Convert.Domain, while a change to Contexture.Api.FileBased.Convert.Domain can't break Contexture.Api.FileBased.Database.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.Domain uses a module listed above it, which is the healthy direction.
23→20 Contexture.Api.FileBased.Convert.Domain uses Contexture.Api.Infrastructure✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.FileBased.Convert.Domain uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.FileBased.Convert.Domain.Domain→Contexture.Api.Infrastructure.EventEnvelope`1Contexture.Api.FileBased.Convert.Domain.Domain→Contexture.Api.Infrastructure.Position
- Direction
- Contexture.Api.FileBased.Convert.Domain uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.FileBased.Convert.Domain, while a change to Contexture.Api.FileBased.Convert.Domain can't break Contexture.Api.Infrastructure.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.Domain uses a module listed above it, which is the healthy direction.
24→4 Contexture.Api.FileBased.Convert.Namespace uses Contexture.Api.Aggregates.Namespace✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Convert.Namespace uses a type in Contexture.Api.Aggregates.Namespace.
- The types involved
Contexture.Api.FileBased.Convert.Namespace.Namespace→Contexture.Api.Aggregates.Namespace.Event
- Direction
- Contexture.Api.FileBased.Convert.Namespace uses Contexture.Api.Aggregates.Namespace, so a change to Contexture.Api.Aggregates.Namespace can break Contexture.Api.FileBased.Convert.Namespace, while a change to Contexture.Api.FileBased.Convert.Namespace can't break Contexture.Api.Aggregates.Namespace.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.Namespace uses a module listed above it, which is the healthy direction.
24→15 Contexture.Api.FileBased.Convert.Namespace uses Contexture.Api.FileBased.Database.Serialization✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Convert.Namespace uses a type in Contexture.Api.FileBased.Database.Serialization.
- The types involved
Contexture.Api.FileBased.Convert.Namespace.Namespace→Contexture.Api.FileBased.Database.Serialization.BoundedContext
- Direction
- Contexture.Api.FileBased.Convert.Namespace uses Contexture.Api.FileBased.Database.Serialization, so a change to Contexture.Api.FileBased.Database.Serialization can break Contexture.Api.FileBased.Convert.Namespace, while a change to Contexture.Api.FileBased.Convert.Namespace can't break Contexture.Api.FileBased.Database.Serialization.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.Namespace uses a module listed above it, which is the healthy direction.
24→19 Contexture.Api.FileBased.Convert.Namespace uses Contexture.Api.FileBased.Database✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Convert.Namespace uses a type in Contexture.Api.FileBased.Database.
- The types involved
Contexture.Api.FileBased.Convert.Namespace.Namespace→Contexture.Api.FileBased.Database.SingleFileBasedDatastore
- Direction
- Contexture.Api.FileBased.Convert.Namespace uses Contexture.Api.FileBased.Database, so a change to Contexture.Api.FileBased.Database can break Contexture.Api.FileBased.Convert.Namespace, while a change to Contexture.Api.FileBased.Convert.Namespace can't break Contexture.Api.FileBased.Database.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.Namespace uses a module listed above it, which is the healthy direction.
24→20 Contexture.Api.FileBased.Convert.Namespace uses Contexture.Api.Infrastructure✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.FileBased.Convert.Namespace uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.FileBased.Convert.Namespace.Namespace→Contexture.Api.Infrastructure.EventEnvelope`1Contexture.Api.FileBased.Convert.Namespace.Namespace→Contexture.Api.Infrastructure.Position
- Direction
- Contexture.Api.FileBased.Convert.Namespace uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.FileBased.Convert.Namespace, while a change to Contexture.Api.FileBased.Convert.Namespace can't break Contexture.Api.Infrastructure.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.Namespace uses a module listed above it, which is the healthy direction.
25→5 Contexture.Api.FileBased.Convert.NamespaceTemplate uses Contexture.Api.Aggregates.NamespaceTemplate✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Convert.NamespaceTemplate uses a type in Contexture.Api.Aggregates.NamespaceTemplate.
- The types involved
Contexture.Api.FileBased.Convert.NamespaceTemplate.NamespaceTemplate→Contexture.Api.Aggregates.NamespaceTemplate.Event
- Direction
- Contexture.Api.FileBased.Convert.NamespaceTemplate uses Contexture.Api.Aggregates.NamespaceTemplate, so a change to Contexture.Api.Aggregates.NamespaceTemplate can break Contexture.Api.FileBased.Convert.NamespaceTemplate, while a change to Contexture.Api.FileBased.Convert.NamespaceTemplate can't break Contexture.Api.Aggregates.NamespaceTemplate.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.NamespaceTemplate uses a module listed above it, which is the healthy direction.
25→12 Contexture.Api.FileBased.Convert.NamespaceTemplate uses Contexture.Api.Aggregates.NamespaceTemplate.Projections✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Convert.NamespaceTemplate uses a type in Contexture.Api.Aggregates.NamespaceTemplate.Projections.
- The types involved
Contexture.Api.FileBased.Convert.NamespaceTemplate.NamespaceTemplate→Contexture.Api.Aggregates.NamespaceTemplate.Projections.NamespaceTemplate
- Direction
- Contexture.Api.FileBased.Convert.NamespaceTemplate uses Contexture.Api.Aggregates.NamespaceTemplate.Projections, so a change to Contexture.Api.Aggregates.NamespaceTemplate.Projections can break Contexture.Api.FileBased.Convert.NamespaceTemplate, while a change to Contexture.Api.FileBased.Convert.NamespaceTemplate can't break Contexture.Api.Aggregates.NamespaceTemplate.Projections.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.NamespaceTemplate uses a module listed above it, which is the healthy direction.
25→19 Contexture.Api.FileBased.Convert.NamespaceTemplate uses Contexture.Api.FileBased.Database✕
- Connections
- 1 pair of types, where a type in Contexture.Api.FileBased.Convert.NamespaceTemplate uses a type in Contexture.Api.FileBased.Database.
- The types involved
Contexture.Api.FileBased.Convert.NamespaceTemplate.NamespaceTemplate→Contexture.Api.FileBased.Database.SingleFileBasedDatastore
- Direction
- Contexture.Api.FileBased.Convert.NamespaceTemplate uses Contexture.Api.FileBased.Database, so a change to Contexture.Api.FileBased.Database can break Contexture.Api.FileBased.Convert.NamespaceTemplate, while a change to Contexture.Api.FileBased.Convert.NamespaceTemplate can't break Contexture.Api.FileBased.Database.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.NamespaceTemplate uses a module listed above it, which is the healthy direction.
25→20 Contexture.Api.FileBased.Convert.NamespaceTemplate uses Contexture.Api.Infrastructure✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.FileBased.Convert.NamespaceTemplate uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.FileBased.Convert.NamespaceTemplate.NamespaceTemplate→Contexture.Api.Infrastructure.EventEnvelope`1Contexture.Api.FileBased.Convert.NamespaceTemplate.NamespaceTemplate→Contexture.Api.Infrastructure.Position
- Direction
- Contexture.Api.FileBased.Convert.NamespaceTemplate uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.FileBased.Convert.NamespaceTemplate, while a change to Contexture.Api.FileBased.Convert.NamespaceTemplate can't break Contexture.Api.Infrastructure.
- Position
- Below the diagonal: Contexture.Api.FileBased.Convert.NamespaceTemplate uses a module listed above it, which is the healthy direction.
26→20 Contexture.Api.Infrastructure.Projections uses Contexture.Api.Infrastructure✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Infrastructure.Projections uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.Infrastructure.Projections.Projections→Contexture.Api.Infrastructure.EventEnvelope`1
- Direction
- Contexture.Api.Infrastructure.Projections uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.Infrastructure.Projections, while a change to Contexture.Api.Infrastructure.Projections can't break Contexture.Api.Infrastructure.
- Position
- Below the diagonal: Contexture.Api.Infrastructure.Projections uses a module listed above it, which is the healthy direction.
27→13 Contexture.Api.Infrastructure.ReadModels uses Contexture.Api.Infrastructure.Subscriptions✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.Infrastructure.ReadModels uses a type in Contexture.Api.Infrastructure.Subscriptions.
- The types involved
Contexture.Api.Infrastructure.ReadModels.ReadModelInitialization→Contexture.Api.Infrastructure.Subscriptions.SubscriptionContexture.Api.Infrastructure.ReadModels.ReadModelInitialization→Contexture.Api.Infrastructure.Subscriptions.SubscriptionStartingPosition
- Direction
- Contexture.Api.Infrastructure.ReadModels uses Contexture.Api.Infrastructure.Subscriptions, so a change to Contexture.Api.Infrastructure.Subscriptions can break Contexture.Api.Infrastructure.ReadModels, while a change to Contexture.Api.Infrastructure.ReadModels can't break Contexture.Api.Infrastructure.Subscriptions.
- Position
- Below the diagonal: Contexture.Api.Infrastructure.ReadModels uses a module listed above it, which is the healthy direction.
27→20 Contexture.Api.Infrastructure.ReadModels uses Contexture.Api.Infrastructure✕
- Connections
- 5 pairs of types, where a type in Contexture.Api.Infrastructure.ReadModels uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.Infrastructure.ReadModels.IRetrieveState`1→Contexture.Api.Infrastructure.PositionContexture.Api.Infrastructure.ReadModels.Msg`2→Contexture.Api.Infrastructure.EventEnvelope`1Contexture.Api.Infrastructure.ReadModels.Msg`2→Contexture.Api.Infrastructure.PositionContexture.Api.Infrastructure.ReadModels.ReadModel`2→Contexture.Api.Infrastructure.EventEnvelope`1Contexture.Api.Infrastructure.ReadModels.ReadModel`2→Contexture.Api.Infrastructure.Position
- Direction
- Contexture.Api.Infrastructure.ReadModels uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.Infrastructure.ReadModels, while a change to Contexture.Api.Infrastructure.ReadModels can't break Contexture.Api.Infrastructure.
- Position
- Below the diagonal: Contexture.Api.Infrastructure.ReadModels uses a module listed above it, which is the healthy direction.
28→20 Contexture.Api.Infrastructure.Subscriptions.PositionStorage uses Contexture.Api.Infrastructure✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Infrastructure.Subscriptions.PositionStorage uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.Infrastructure.Subscriptions.PositionStorage.IStorePositions→Contexture.Api.Infrastructure.Position
- Direction
- Contexture.Api.Infrastructure.Subscriptions.PositionStorage uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.Infrastructure.Subscriptions.PositionStorage, while a change to Contexture.Api.Infrastructure.Subscriptions.PositionStorage can't break Contexture.Api.Infrastructure.
- Position
- Below the diagonal: Contexture.Api.Infrastructure.Subscriptions.PositionStorage uses a module listed above it, which is the healthy direction.
29→13 Contexture.Api.Reactions uses Contexture.Api.Infrastructure.Subscriptions✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Reactions uses a type in Contexture.Api.Infrastructure.Subscriptions.
- The types involved
Contexture.Api.Reactions.ReactionInitialization→Contexture.Api.Infrastructure.Subscriptions.Subscription
- Direction
- Contexture.Api.Reactions uses Contexture.Api.Infrastructure.Subscriptions, so a change to Contexture.Api.Infrastructure.Subscriptions can break Contexture.Api.Reactions, while a change to Contexture.Api.Reactions can't break Contexture.Api.Infrastructure.Subscriptions.
- Position
- Below the diagonal: Contexture.Api.Reactions uses a module listed above it, which is the healthy direction.
29→20 Contexture.Api.Reactions uses Contexture.Api.Infrastructure✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Reactions uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.Reactions.Reaction`2→Contexture.Api.Infrastructure.EventEnvelope`1
- Direction
- Contexture.Api.Reactions uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.Reactions, while a change to Contexture.Api.Reactions can't break Contexture.Api.Infrastructure.
- Position
- Below the diagonal: Contexture.Api.Reactions uses a module listed above it, which is the healthy direction.
29→26 Contexture.Api.Reactions uses Contexture.Api.Infrastructure.Projections✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Reactions uses a type in Contexture.Api.Infrastructure.Projections.
- The types involved
Contexture.Api.Reactions.Reaction`2→Contexture.Api.Infrastructure.Projections.Projection`2
- Direction
- Contexture.Api.Reactions uses Contexture.Api.Infrastructure.Projections, so a change to Contexture.Api.Infrastructure.Projections can break Contexture.Api.Reactions, while a change to Contexture.Api.Reactions can't break Contexture.Api.Infrastructure.Projections.
- Position
- Below the diagonal: Contexture.Api.Reactions uses a module listed above it, which is the healthy direction.
30→10 Contexture.Api.ReadModels.BoundedContext uses Contexture.Api.Aggregates.BoundedContext✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.BoundedContext uses a type in Contexture.Api.Aggregates.BoundedContext.
- The types involved
Contexture.Api.ReadModels.BoundedContext.BoundedContext→Contexture.Api.Aggregates.BoundedContext.Event
- Direction
- Contexture.Api.ReadModels.BoundedContext uses Contexture.Api.Aggregates.BoundedContext, so a change to Contexture.Api.Aggregates.BoundedContext can break Contexture.Api.ReadModels.BoundedContext, while a change to Contexture.Api.ReadModels.BoundedContext can't break Contexture.Api.Aggregates.BoundedContext.
- Position
- Below the diagonal: Contexture.Api.ReadModels.BoundedContext uses a module listed above it, which is the healthy direction.
30→14 Contexture.Api.ReadModels.BoundedContext uses Contexture.Api.Aggregates.BoundedContext.Projections✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.ReadModels.BoundedContext uses a type in Contexture.Api.Aggregates.BoundedContext.Projections.
- The types involved
Contexture.Api.ReadModels.BoundedContext.BoundedContext→Contexture.Api.Aggregates.BoundedContext.Projections.BoundedContextContexture.Api.ReadModels.BoundedContext.BoundedContextState→Contexture.Api.Aggregates.BoundedContext.Projections.BoundedContext
- Direction
- Contexture.Api.ReadModels.BoundedContext uses Contexture.Api.Aggregates.BoundedContext.Projections, so a change to Contexture.Api.Aggregates.BoundedContext.Projections can break Contexture.Api.ReadModels.BoundedContext, while a change to Contexture.Api.ReadModels.BoundedContext can't break Contexture.Api.Aggregates.BoundedContext.Projections.
- Position
- Below the diagonal: Contexture.Api.ReadModels.BoundedContext uses a module listed above it, which is the healthy direction.
30→26 Contexture.Api.ReadModels.BoundedContext uses Contexture.Api.Infrastructure.Projections✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.BoundedContext uses a type in Contexture.Api.Infrastructure.Projections.
- The types involved
Contexture.Api.ReadModels.BoundedContext.BoundedContext→Contexture.Api.Infrastructure.Projections.Projection`2
- Direction
- Contexture.Api.ReadModels.BoundedContext uses Contexture.Api.Infrastructure.Projections, so a change to Contexture.Api.Infrastructure.Projections can break Contexture.Api.ReadModels.BoundedContext, while a change to Contexture.Api.ReadModels.BoundedContext can't break Contexture.Api.Infrastructure.Projections.
- Position
- Below the diagonal: Contexture.Api.ReadModels.BoundedContext uses a module listed above it, which is the healthy direction.
30→27 Contexture.Api.ReadModels.BoundedContext uses Contexture.Api.Infrastructure.ReadModels✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.BoundedContext uses a type in Contexture.Api.Infrastructure.ReadModels.
- The types involved
Contexture.Api.ReadModels.BoundedContext.BoundedContext→Contexture.Api.Infrastructure.ReadModels.ReadModel`2
- Direction
- Contexture.Api.ReadModels.BoundedContext uses Contexture.Api.Infrastructure.ReadModels, so a change to Contexture.Api.Infrastructure.ReadModels can break Contexture.Api.ReadModels.BoundedContext, while a change to Contexture.Api.ReadModels.BoundedContext can't break Contexture.Api.Infrastructure.ReadModels.
- Position
- Below the diagonal: Contexture.Api.ReadModels.BoundedContext uses a module listed above it, which is the healthy direction.
31→3 Contexture.Api.ReadModels.Domain uses Contexture.Api.Aggregates.Domain✕
- Connections
- 5 pairs of types, where a type in Contexture.Api.ReadModels.Domain uses a type in Contexture.Api.Aggregates.Domain.
- The types involved
Contexture.Api.ReadModels.Domain.AllDomainState→Contexture.Api.Aggregates.Domain.DomainContexture.Api.ReadModels.Domain.AllDomainState→Contexture.Api.Aggregates.Domain.StateContexture.Api.ReadModels.Domain.Domain→Contexture.Api.Aggregates.Domain.DomainContexture.Api.ReadModels.Domain.Domain→Contexture.Api.Aggregates.Domain.EventContexture.Api.ReadModels.Domain.Domain→Contexture.Api.Aggregates.Domain.State
- Direction
- Contexture.Api.ReadModels.Domain uses Contexture.Api.Aggregates.Domain, so a change to Contexture.Api.Aggregates.Domain can break Contexture.Api.ReadModels.Domain, while a change to Contexture.Api.ReadModels.Domain can't break Contexture.Api.Aggregates.Domain.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Domain uses a module listed above it, which is the healthy direction.
31→26 Contexture.Api.ReadModels.Domain uses Contexture.Api.Infrastructure.Projections✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Domain uses a type in Contexture.Api.Infrastructure.Projections.
- The types involved
Contexture.Api.ReadModels.Domain.Domain→Contexture.Api.Infrastructure.Projections.Projection`2
- Direction
- Contexture.Api.ReadModels.Domain uses Contexture.Api.Infrastructure.Projections, so a change to Contexture.Api.Infrastructure.Projections can break Contexture.Api.ReadModels.Domain, while a change to Contexture.Api.ReadModels.Domain can't break Contexture.Api.Infrastructure.Projections.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Domain uses a module listed above it, which is the healthy direction.
31→27 Contexture.Api.ReadModels.Domain uses Contexture.Api.Infrastructure.ReadModels✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Domain uses a type in Contexture.Api.Infrastructure.ReadModels.
- The types involved
Contexture.Api.ReadModels.Domain.Domain→Contexture.Api.Infrastructure.ReadModels.ReadModel`2
- Direction
- Contexture.Api.ReadModels.Domain uses Contexture.Api.Infrastructure.ReadModels, so a change to Contexture.Api.Infrastructure.ReadModels can break Contexture.Api.ReadModels.Domain, while a change to Contexture.Api.ReadModels.Domain can't break Contexture.Api.Infrastructure.ReadModels.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Domain uses a module listed above it, which is the healthy direction.
32→3 Contexture.Api.ReadModels.EventLog uses Contexture.Api.Aggregates.Domain✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.EventLog uses a type in Contexture.Api.Aggregates.Domain.
- The types involved
Contexture.Api.ReadModels.EventLog.EventLog→Contexture.Api.Aggregates.Domain.Event
- Direction
- Contexture.Api.ReadModels.EventLog uses Contexture.Api.Aggregates.Domain, so a change to Contexture.Api.Aggregates.Domain can break Contexture.Api.ReadModels.EventLog, while a change to Contexture.Api.ReadModels.EventLog can't break Contexture.Api.Aggregates.Domain.
- Position
- Below the diagonal: Contexture.Api.ReadModels.EventLog uses a module listed above it, which is the healthy direction.
32→6 Contexture.Api.ReadModels.EventLog uses Contexture.Api.AllEvents✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.EventLog uses a type in Contexture.Api.AllEvents.
- The types involved
Contexture.Api.ReadModels.EventLog.EventLog→Contexture.Api.AllEvents.AllEvents
- Direction
- Contexture.Api.ReadModels.EventLog uses Contexture.Api.AllEvents, so a change to Contexture.Api.AllEvents can break Contexture.Api.ReadModels.EventLog, while a change to Contexture.Api.ReadModels.EventLog can't break Contexture.Api.AllEvents.
- Position
- Below the diagonal: Contexture.Api.ReadModels.EventLog uses a module listed above it, which is the healthy direction.
32→10 Contexture.Api.ReadModels.EventLog uses Contexture.Api.Aggregates.BoundedContext✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.EventLog uses a type in Contexture.Api.Aggregates.BoundedContext.
- The types involved
Contexture.Api.ReadModels.EventLog.EventLog→Contexture.Api.Aggregates.BoundedContext.Event
- Direction
- Contexture.Api.ReadModels.EventLog uses Contexture.Api.Aggregates.BoundedContext, so a change to Contexture.Api.Aggregates.BoundedContext can break Contexture.Api.ReadModels.EventLog, while a change to Contexture.Api.ReadModels.EventLog can't break Contexture.Api.Aggregates.BoundedContext.
- Position
- Below the diagonal: Contexture.Api.ReadModels.EventLog uses a module listed above it, which is the healthy direction.
32→20 Contexture.Api.ReadModels.EventLog uses Contexture.Api.Infrastructure✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.ReadModels.EventLog uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.ReadModels.EventLog.EventLog→Contexture.Api.Infrastructure.EventEnvelope`1Contexture.Api.ReadModels.EventLog.EventLog→Contexture.Api.Infrastructure.EventMetadata
- Direction
- Contexture.Api.ReadModels.EventLog uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.ReadModels.EventLog, while a change to Contexture.Api.ReadModels.EventLog can't break Contexture.Api.Infrastructure.
- Position
- Below the diagonal: Contexture.Api.ReadModels.EventLog uses a module listed above it, which is the healthy direction.
32→27 Contexture.Api.ReadModels.EventLog uses Contexture.Api.Infrastructure.ReadModels✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.EventLog uses a type in Contexture.Api.Infrastructure.ReadModels.
- The types involved
Contexture.Api.ReadModels.EventLog.EventLog→Contexture.Api.Infrastructure.ReadModels.ReadModel`2
- Direction
- Contexture.Api.ReadModels.EventLog uses Contexture.Api.Infrastructure.ReadModels, so a change to Contexture.Api.Infrastructure.ReadModels can break Contexture.Api.ReadModels.EventLog, while a change to Contexture.Api.ReadModels.EventLog can't break Contexture.Api.Infrastructure.ReadModels.
- Position
- Below the diagonal: Contexture.Api.ReadModels.EventLog uses a module listed above it, which is the healthy direction.
33→8 Contexture.Api.ReadModels.Find.BoundedContexts uses Contexture.Api.ReadModels.Find✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.ReadModels.Find.BoundedContexts uses a type in Contexture.Api.ReadModels.Find.
- The types involved
Contexture.Api.ReadModels.Find.BoundedContexts.BoundedContexts→Contexture.Api.ReadModels.Find.SearchPhraseContexture.Api.ReadModels.Find.BoundedContexts.BoundedContexts→Contexture.Api.ReadModels.Find.SearchPhraseResult`1
- Direction
- Contexture.Api.ReadModels.Find.BoundedContexts uses Contexture.Api.ReadModels.Find, so a change to Contexture.Api.ReadModels.Find can break Contexture.Api.ReadModels.Find.BoundedContexts, while a change to Contexture.Api.ReadModels.Find.BoundedContexts can't break Contexture.Api.ReadModels.Find.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Find.BoundedContexts uses a module listed above it, which is the healthy direction.
33→10 Contexture.Api.ReadModels.Find.BoundedContexts uses Contexture.Api.Aggregates.BoundedContext✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Find.BoundedContexts uses a type in Contexture.Api.Aggregates.BoundedContext.
- The types involved
Contexture.Api.ReadModels.Find.BoundedContexts.BoundedContexts→Contexture.Api.Aggregates.BoundedContext.Event
- Direction
- Contexture.Api.ReadModels.Find.BoundedContexts uses Contexture.Api.Aggregates.BoundedContext, so a change to Contexture.Api.Aggregates.BoundedContext can break Contexture.Api.ReadModels.Find.BoundedContexts, while a change to Contexture.Api.ReadModels.Find.BoundedContexts can't break Contexture.Api.Aggregates.BoundedContext.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Find.BoundedContexts uses a module listed above it, which is the healthy direction.
33→20 Contexture.Api.ReadModels.Find.BoundedContexts uses Contexture.Api.Infrastructure✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Find.BoundedContexts uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.ReadModels.Find.BoundedContexts.BoundedContexts→Contexture.Api.Infrastructure.EventEnvelope`1
- Direction
- Contexture.Api.ReadModels.Find.BoundedContexts uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.ReadModels.Find.BoundedContexts, while a change to Contexture.Api.ReadModels.Find.BoundedContexts can't break Contexture.Api.Infrastructure.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Find.BoundedContexts uses a module listed above it, which is the healthy direction.
33→27 Contexture.Api.ReadModels.Find.BoundedContexts uses Contexture.Api.Infrastructure.ReadModels✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Find.BoundedContexts uses a type in Contexture.Api.Infrastructure.ReadModels.
- The types involved
Contexture.Api.ReadModels.Find.BoundedContexts.BoundedContexts→Contexture.Api.Infrastructure.ReadModels.ReadModel`2
- Direction
- Contexture.Api.ReadModels.Find.BoundedContexts uses Contexture.Api.Infrastructure.ReadModels, so a change to Contexture.Api.Infrastructure.ReadModels can break Contexture.Api.ReadModels.Find.BoundedContexts, while a change to Contexture.Api.ReadModels.Find.BoundedContexts can't break Contexture.Api.Infrastructure.ReadModels.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Find.BoundedContexts uses a module listed above it, which is the healthy direction.
34→3 Contexture.Api.ReadModels.Find.Domains uses Contexture.Api.Aggregates.Domain✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Find.Domains uses a type in Contexture.Api.Aggregates.Domain.
- The types involved
Contexture.Api.ReadModels.Find.Domains.Domains→Contexture.Api.Aggregates.Domain.Event
- Direction
- Contexture.Api.ReadModels.Find.Domains uses Contexture.Api.Aggregates.Domain, so a change to Contexture.Api.Aggregates.Domain can break Contexture.Api.ReadModels.Find.Domains, while a change to Contexture.Api.ReadModels.Find.Domains can't break Contexture.Api.Aggregates.Domain.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Find.Domains uses a module listed above it, which is the healthy direction.
34→8 Contexture.Api.ReadModels.Find.Domains uses Contexture.Api.ReadModels.Find✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.ReadModels.Find.Domains uses a type in Contexture.Api.ReadModels.Find.
- The types involved
Contexture.Api.ReadModels.Find.Domains.Domains→Contexture.Api.ReadModels.Find.SearchPhraseContexture.Api.ReadModels.Find.Domains.Domains→Contexture.Api.ReadModels.Find.SearchPhraseResult`1
- Direction
- Contexture.Api.ReadModels.Find.Domains uses Contexture.Api.ReadModels.Find, so a change to Contexture.Api.ReadModels.Find can break Contexture.Api.ReadModels.Find.Domains, while a change to Contexture.Api.ReadModels.Find.Domains can't break Contexture.Api.ReadModels.Find.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Find.Domains uses a module listed above it, which is the healthy direction.
34→20 Contexture.Api.ReadModels.Find.Domains uses Contexture.Api.Infrastructure✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Find.Domains uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.ReadModels.Find.Domains.Domains→Contexture.Api.Infrastructure.EventEnvelope`1
- Direction
- Contexture.Api.ReadModels.Find.Domains uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.ReadModels.Find.Domains, while a change to Contexture.Api.ReadModels.Find.Domains can't break Contexture.Api.Infrastructure.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Find.Domains uses a module listed above it, which is the healthy direction.
34→27 Contexture.Api.ReadModels.Find.Domains uses Contexture.Api.Infrastructure.ReadModels✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Find.Domains uses a type in Contexture.Api.Infrastructure.ReadModels.
- The types involved
Contexture.Api.ReadModels.Find.Domains.Domains→Contexture.Api.Infrastructure.ReadModels.ReadModel`2
- Direction
- Contexture.Api.ReadModels.Find.Domains uses Contexture.Api.Infrastructure.ReadModels, so a change to Contexture.Api.Infrastructure.ReadModels can break Contexture.Api.ReadModels.Find.Domains, while a change to Contexture.Api.ReadModels.Find.Domains can't break Contexture.Api.Infrastructure.ReadModels.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Find.Domains uses a module listed above it, which is the healthy direction.
35→4 Contexture.Api.ReadModels.Find.Labels uses Contexture.Api.Aggregates.Namespace✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Find.Labels uses a type in Contexture.Api.Aggregates.Namespace.
- The types involved
Contexture.Api.ReadModels.Find.Labels.Labels→Contexture.Api.Aggregates.Namespace.Event
- Direction
- Contexture.Api.ReadModels.Find.Labels uses Contexture.Api.Aggregates.Namespace, so a change to Contexture.Api.Aggregates.Namespace can break Contexture.Api.ReadModels.Find.Labels, while a change to Contexture.Api.ReadModels.Find.Labels can't break Contexture.Api.Aggregates.Namespace.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Find.Labels uses a module listed above it, which is the healthy direction.
35→8 Contexture.Api.ReadModels.Find.Labels uses Contexture.Api.ReadModels.Find✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.ReadModels.Find.Labels uses a type in Contexture.Api.ReadModels.Find.
- The types involved
Contexture.Api.ReadModels.Find.Labels.Labels→Contexture.Api.ReadModels.Find.SearchPhraseContexture.Api.ReadModels.Find.Labels.Labels→Contexture.Api.ReadModels.Find.SearchPhraseResult`1
- Direction
- Contexture.Api.ReadModels.Find.Labels uses Contexture.Api.ReadModels.Find, so a change to Contexture.Api.ReadModels.Find can break Contexture.Api.ReadModels.Find.Labels, while a change to Contexture.Api.ReadModels.Find.Labels can't break Contexture.Api.ReadModels.Find.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Find.Labels uses a module listed above it, which is the healthy direction.
35→20 Contexture.Api.ReadModels.Find.Labels uses Contexture.Api.Infrastructure✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Find.Labels uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.ReadModels.Find.Labels.Labels→Contexture.Api.Infrastructure.EventEnvelope`1
- Direction
- Contexture.Api.ReadModels.Find.Labels uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.ReadModels.Find.Labels, while a change to Contexture.Api.ReadModels.Find.Labels can't break Contexture.Api.Infrastructure.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Find.Labels uses a module listed above it, which is the healthy direction.
35→27 Contexture.Api.ReadModels.Find.Labels uses Contexture.Api.Infrastructure.ReadModels✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Find.Labels uses a type in Contexture.Api.Infrastructure.ReadModels.
- The types involved
Contexture.Api.ReadModels.Find.Labels.Labels→Contexture.Api.Infrastructure.ReadModels.ReadModel`2
- Direction
- Contexture.Api.ReadModels.Find.Labels uses Contexture.Api.Infrastructure.ReadModels, so a change to Contexture.Api.Infrastructure.ReadModels can break Contexture.Api.ReadModels.Find.Labels, while a change to Contexture.Api.ReadModels.Find.Labels can't break Contexture.Api.Infrastructure.ReadModels.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Find.Labels uses a module listed above it, which is the healthy direction.
36→4 Contexture.Api.ReadModels.Find.Namespaces uses Contexture.Api.Aggregates.Namespace✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Find.Namespaces uses a type in Contexture.Api.Aggregates.Namespace.
- The types involved
Contexture.Api.ReadModels.Find.Namespaces.Namespaces→Contexture.Api.Aggregates.Namespace.Event
- Direction
- Contexture.Api.ReadModels.Find.Namespaces uses Contexture.Api.Aggregates.Namespace, so a change to Contexture.Api.Aggregates.Namespace can break Contexture.Api.ReadModels.Find.Namespaces, while a change to Contexture.Api.ReadModels.Find.Namespaces can't break Contexture.Api.Aggregates.Namespace.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Find.Namespaces uses a module listed above it, which is the healthy direction.
36→8 Contexture.Api.ReadModels.Find.Namespaces uses Contexture.Api.ReadModels.Find✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.ReadModels.Find.Namespaces uses a type in Contexture.Api.ReadModels.Find.
- The types involved
Contexture.Api.ReadModels.Find.Namespaces.Namespaces→Contexture.Api.ReadModels.Find.SearchPhraseContexture.Api.ReadModels.Find.Namespaces.Namespaces→Contexture.Api.ReadModels.Find.SearchPhraseResult`1
- Direction
- Contexture.Api.ReadModels.Find.Namespaces uses Contexture.Api.ReadModels.Find, so a change to Contexture.Api.ReadModels.Find can break Contexture.Api.ReadModels.Find.Namespaces, while a change to Contexture.Api.ReadModels.Find.Namespaces can't break Contexture.Api.ReadModels.Find.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Find.Namespaces uses a module listed above it, which is the healthy direction.
36→20 Contexture.Api.ReadModels.Find.Namespaces uses Contexture.Api.Infrastructure✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Find.Namespaces uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.ReadModels.Find.Namespaces.Namespaces→Contexture.Api.Infrastructure.EventEnvelope`1
- Direction
- Contexture.Api.ReadModels.Find.Namespaces uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.ReadModels.Find.Namespaces, while a change to Contexture.Api.ReadModels.Find.Namespaces can't break Contexture.Api.Infrastructure.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Find.Namespaces uses a module listed above it, which is the healthy direction.
36→27 Contexture.Api.ReadModels.Find.Namespaces uses Contexture.Api.Infrastructure.ReadModels✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Find.Namespaces uses a type in Contexture.Api.Infrastructure.ReadModels.
- The types involved
Contexture.Api.ReadModels.Find.Namespaces.Namespaces→Contexture.Api.Infrastructure.ReadModels.ReadModel`2
- Direction
- Contexture.Api.ReadModels.Find.Namespaces uses Contexture.Api.Infrastructure.ReadModels, so a change to Contexture.Api.Infrastructure.ReadModels can break Contexture.Api.ReadModels.Find.Namespaces, while a change to Contexture.Api.ReadModels.Find.Namespaces can't break Contexture.Api.Infrastructure.ReadModels.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Find.Namespaces uses a module listed above it, which is the healthy direction.
37→4 Contexture.Api.ReadModels.Namespace uses Contexture.Api.Aggregates.Namespace✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Namespace uses a type in Contexture.Api.Aggregates.Namespace.
- The types involved
Contexture.Api.ReadModels.Namespace.Namespace→Contexture.Api.Aggregates.Namespace.Event
- Direction
- Contexture.Api.ReadModels.Namespace uses Contexture.Api.Aggregates.Namespace, so a change to Contexture.Api.Aggregates.Namespace can break Contexture.Api.ReadModels.Namespace, while a change to Contexture.Api.ReadModels.Namespace can't break Contexture.Api.Aggregates.Namespace.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Namespace uses a module listed above it, which is the healthy direction.
37→11 Contexture.Api.ReadModels.Namespace uses Contexture.Api.Aggregates.Namespace.Projections✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.ReadModels.Namespace uses a type in Contexture.Api.Aggregates.Namespace.Projections.
- The types involved
Contexture.Api.ReadModels.Namespace.Namespace→Contexture.Api.Aggregates.Namespace.Projections.NamespaceContexture.Api.ReadModels.Namespace.NamespaceState→Contexture.Api.Aggregates.Namespace.Projections.Namespace
- Direction
- Contexture.Api.ReadModels.Namespace uses Contexture.Api.Aggregates.Namespace.Projections, so a change to Contexture.Api.Aggregates.Namespace.Projections can break Contexture.Api.ReadModels.Namespace, while a change to Contexture.Api.ReadModels.Namespace can't break Contexture.Api.Aggregates.Namespace.Projections.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Namespace uses a module listed above it, which is the healthy direction.
37→26 Contexture.Api.ReadModels.Namespace uses Contexture.Api.Infrastructure.Projections✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Namespace uses a type in Contexture.Api.Infrastructure.Projections.
- The types involved
Contexture.Api.ReadModels.Namespace.Namespace→Contexture.Api.Infrastructure.Projections.Projection`2
- Direction
- Contexture.Api.ReadModels.Namespace uses Contexture.Api.Infrastructure.Projections, so a change to Contexture.Api.Infrastructure.Projections can break Contexture.Api.ReadModels.Namespace, while a change to Contexture.Api.ReadModels.Namespace can't break Contexture.Api.Infrastructure.Projections.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Namespace uses a module listed above it, which is the healthy direction.
37→27 Contexture.Api.ReadModels.Namespace uses Contexture.Api.Infrastructure.ReadModels✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Namespace uses a type in Contexture.Api.Infrastructure.ReadModels.
- The types involved
Contexture.Api.ReadModels.Namespace.Namespace→Contexture.Api.Infrastructure.ReadModels.ReadModel`2
- Direction
- Contexture.Api.ReadModels.Namespace uses Contexture.Api.Infrastructure.ReadModels, so a change to Contexture.Api.Infrastructure.ReadModels can break Contexture.Api.ReadModels.Namespace, while a change to Contexture.Api.ReadModels.Namespace can't break Contexture.Api.Infrastructure.ReadModels.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Namespace uses a module listed above it, which is the healthy direction.
38→5 Contexture.Api.ReadModels.Templates uses Contexture.Api.Aggregates.NamespaceTemplate✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Templates uses a type in Contexture.Api.Aggregates.NamespaceTemplate.
- The types involved
Contexture.Api.ReadModels.Templates.Templates→Contexture.Api.Aggregates.NamespaceTemplate.Event
- Direction
- Contexture.Api.ReadModels.Templates uses Contexture.Api.Aggregates.NamespaceTemplate, so a change to Contexture.Api.Aggregates.NamespaceTemplate can break Contexture.Api.ReadModels.Templates, while a change to Contexture.Api.ReadModels.Templates can't break Contexture.Api.Aggregates.NamespaceTemplate.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Templates uses a module listed above it, which is the healthy direction.
38→12 Contexture.Api.ReadModels.Templates uses Contexture.Api.Aggregates.NamespaceTemplate.Projections✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Templates uses a type in Contexture.Api.Aggregates.NamespaceTemplate.Projections.
- The types involved
Contexture.Api.ReadModels.Templates.Templates→Contexture.Api.Aggregates.NamespaceTemplate.Projections.NamespaceTemplate
- Direction
- Contexture.Api.ReadModels.Templates uses Contexture.Api.Aggregates.NamespaceTemplate.Projections, so a change to Contexture.Api.Aggregates.NamespaceTemplate.Projections can break Contexture.Api.ReadModels.Templates, while a change to Contexture.Api.ReadModels.Templates can't break Contexture.Api.Aggregates.NamespaceTemplate.Projections.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Templates uses a module listed above it, which is the healthy direction.
38→26 Contexture.Api.ReadModels.Templates uses Contexture.Api.Infrastructure.Projections✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Templates uses a type in Contexture.Api.Infrastructure.Projections.
- The types involved
Contexture.Api.ReadModels.Templates.Templates→Contexture.Api.Infrastructure.Projections.Projection`2
- Direction
- Contexture.Api.ReadModels.Templates uses Contexture.Api.Infrastructure.Projections, so a change to Contexture.Api.Infrastructure.Projections can break Contexture.Api.ReadModels.Templates, while a change to Contexture.Api.ReadModels.Templates can't break Contexture.Api.Infrastructure.Projections.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Templates uses a module listed above it, which is the healthy direction.
38→27 Contexture.Api.ReadModels.Templates uses Contexture.Api.Infrastructure.ReadModels✕
- Connections
- 1 pair of types, where a type in Contexture.Api.ReadModels.Templates uses a type in Contexture.Api.Infrastructure.ReadModels.
- The types involved
Contexture.Api.ReadModels.Templates.Templates→Contexture.Api.Infrastructure.ReadModels.ReadModel`2
- Direction
- Contexture.Api.ReadModels.Templates uses Contexture.Api.Infrastructure.ReadModels, so a change to Contexture.Api.Infrastructure.ReadModels can break Contexture.Api.ReadModels.Templates, while a change to Contexture.Api.ReadModels.Templates can't break Contexture.Api.Infrastructure.ReadModels.
- Position
- Below the diagonal: Contexture.Api.ReadModels.Templates uses a module listed above it, which is the healthy direction.
39→30 Contexture.Api.Apis.BoundedContexts.QueryEndpoints uses Contexture.Api.ReadModels.BoundedContext✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Apis.BoundedContexts.QueryEndpoints uses a type in Contexture.Api.ReadModels.BoundedContext.
- The types involved
Contexture.Api.Apis.BoundedContexts.QueryEndpoints.QueryEndpoints→Contexture.Api.ReadModels.BoundedContext.BoundedContextState
- Direction
- Contexture.Api.Apis.BoundedContexts.QueryEndpoints uses Contexture.Api.ReadModels.BoundedContext, so a change to Contexture.Api.ReadModels.BoundedContext can break Contexture.Api.Apis.BoundedContexts.QueryEndpoints, while a change to Contexture.Api.Apis.BoundedContexts.QueryEndpoints can't break Contexture.Api.ReadModels.BoundedContext.
- Position
- Below the diagonal: Contexture.Api.Apis.BoundedContexts.QueryEndpoints uses a module listed above it, which is the healthy direction.
39→31 Contexture.Api.Apis.BoundedContexts.QueryEndpoints uses Contexture.Api.ReadModels.Domain✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Apis.BoundedContexts.QueryEndpoints uses a type in Contexture.Api.ReadModels.Domain.
- The types involved
Contexture.Api.Apis.BoundedContexts.QueryEndpoints.QueryEndpoints→Contexture.Api.ReadModels.Domain.AllDomainState
- Direction
- Contexture.Api.Apis.BoundedContexts.QueryEndpoints uses Contexture.Api.ReadModels.Domain, so a change to Contexture.Api.ReadModels.Domain can break Contexture.Api.Apis.BoundedContexts.QueryEndpoints, while a change to Contexture.Api.Apis.BoundedContexts.QueryEndpoints can't break Contexture.Api.ReadModels.Domain.
- Position
- Below the diagonal: Contexture.Api.Apis.BoundedContexts.QueryEndpoints uses a module listed above it, which is the healthy direction.
39→37 Contexture.Api.Apis.BoundedContexts.QueryEndpoints uses Contexture.Api.ReadModels.Namespace✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Apis.BoundedContexts.QueryEndpoints uses a type in Contexture.Api.ReadModels.Namespace.
- The types involved
Contexture.Api.Apis.BoundedContexts.QueryEndpoints.QueryEndpoints→Contexture.Api.ReadModels.Namespace.NamespaceState
- Direction
- Contexture.Api.Apis.BoundedContexts.QueryEndpoints uses Contexture.Api.ReadModels.Namespace, so a change to Contexture.Api.ReadModels.Namespace can break Contexture.Api.Apis.BoundedContexts.QueryEndpoints, while a change to Contexture.Api.Apis.BoundedContexts.QueryEndpoints can't break Contexture.Api.ReadModels.Namespace.
- Position
- Below the diagonal: Contexture.Api.Apis.BoundedContexts.QueryEndpoints uses a module listed above it, which is the healthy direction.
40→6 Contexture.Api.Reactions.ReactionInitializationModule uses Contexture.Api.AllEvents✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.Reactions.ReactionInitializationModule uses a type in Contexture.Api.AllEvents.
- The types involved
Contexture.Api.Reactions.ReactionInitializationModule.ReactionInitializationModule→Contexture.Api.AllEvents.AllEventsContexture.Api.Reactions.ReactionInitializationModule.ReplayFromStartWithAllEventsReactionInitialization`1→Contexture.Api.AllEvents.AllEvents
- Direction
- Contexture.Api.Reactions.ReactionInitializationModule uses Contexture.Api.AllEvents, so a change to Contexture.Api.AllEvents can break Contexture.Api.Reactions.ReactionInitializationModule, while a change to Contexture.Api.Reactions.ReactionInitializationModule can't break Contexture.Api.AllEvents.
- Position
- Below the diagonal: Contexture.Api.Reactions.ReactionInitializationModule uses a module listed above it, which is the healthy direction.
40→13 Contexture.Api.Reactions.ReactionInitializationModule uses Contexture.Api.Infrastructure.Subscriptions✕
- Connections
- 1 pair of types, where a type in Contexture.Api.Reactions.ReactionInitializationModule uses a type in Contexture.Api.Infrastructure.Subscriptions.
- The types involved
Contexture.Api.Reactions.ReactionInitializationModule.ReplayFromStartWithAllEventsReactionInitialization`1→Contexture.Api.Infrastructure.Subscriptions.Subscription
- Direction
- Contexture.Api.Reactions.ReactionInitializationModule uses Contexture.Api.Infrastructure.Subscriptions, so a change to Contexture.Api.Infrastructure.Subscriptions can break Contexture.Api.Reactions.ReactionInitializationModule, while a change to Contexture.Api.Reactions.ReactionInitializationModule can't break Contexture.Api.Infrastructure.Subscriptions.
- Position
- Below the diagonal: Contexture.Api.Reactions.ReactionInitializationModule uses a module listed above it, which is the healthy direction.
40→20 Contexture.Api.Reactions.ReactionInitializationModule uses Contexture.Api.Infrastructure✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.Reactions.ReactionInitializationModule uses a type in Contexture.Api.Infrastructure.
- The types involved
Contexture.Api.Reactions.ReactionInitializationModule.ReactionInitializationModule→Contexture.Api.Infrastructure.EventStoreContexture.Api.Reactions.ReactionInitializationModule.ReplayFromStartWithAllEventsReactionInitialization`1→Contexture.Api.Infrastructure.EventStore
- Direction
- Contexture.Api.Reactions.ReactionInitializationModule uses Contexture.Api.Infrastructure, so a change to Contexture.Api.Infrastructure can break Contexture.Api.Reactions.ReactionInitializationModule, while a change to Contexture.Api.Reactions.ReactionInitializationModule can't break Contexture.Api.Infrastructure.
- Position
- Below the diagonal: Contexture.Api.Reactions.ReactionInitializationModule uses a module listed above it, which is the healthy direction.
40→28 Contexture.Api.Reactions.ReactionInitializationModule uses Contexture.Api.Infrastructure.Subscriptions.PositionStorage✕
- Connections
- 2 pairs of types, where a type in Contexture.Api.Reactions.ReactionInitializationModule uses a type in Contexture.Api.Infrastructure.Subscriptions.PositionStorage.
- The types involved
Contexture.Api.Reactions.ReactionInitializationModule.ReactionInitializationModule→Contexture.Api.Infrastructure.Subscriptions.PositionStorage.IStorePositionsContexture.Api.Reactions.ReactionInitializationModule.ReplayFromStartWithAllEventsReactionInitialization`1→Contexture.Api.Infrastructure.Subscriptions.PositionStorage.IStorePositions
- Direction
- Contexture.Api.Reactions.ReactionInitializationModule uses Contexture.Api.Infrastructure.Subscriptions.PositionStorage, so a change to Contexture.Api.Infrastructure.Subscriptions.PositionStorage can break Contexture.Api.Reactions.ReactionInitializationModule, while a change to Contexture.Api.Reactions.ReactionInitializationModule can't break Contexture.Api.Infrastructure.Subscriptions.PositionStorage.
- Position
- Below the diagonal: Contexture.Api.Reactions.ReactionInitializationModule uses a module listed above it, which is the healthy direction.
40→29 Contexture.Api.Reactions.ReactionInitializationModule uses Contexture.Api.Reactions✕
- Connections
- 4 pairs of types, where a type in Contexture.Api.Reactions.ReactionInitializationModule uses a type in Contexture.Api.Reactions.
- The types involved
Contexture.Api.Reactions.ReactionInitializationModule.ReactionInitializationModule→Contexture.Api.Reactions.ReactionInitializationContexture.Api.Reactions.ReactionInitializationModule.ReactionInitializationModule→Contexture.Api.Reactions.Reaction`2Contexture.Api.Reactions.ReactionInitializationModule.ReplayFromStartWithAllEventsReactionInitialization`1→Contexture.Api.Reactions.ReactionInitializationContexture.Api.Reactions.ReactionInitializationModule.ReplayFromStartWithAllEventsReactionInitialization`1→Contexture.Api.Reactions.Reaction`2
- Direction
- Contexture.Api.Reactions.ReactionInitializationModule uses Contexture.Api.Reactions, so a change to Contexture.Api.Reactions can break Contexture.Api.Reactions.ReactionInitializationModule, while a change to Contexture.Api.Reactions.ReactionInitializationModule can't break Contexture.Api.Reactions.
- Position
- Below the diagonal: Contexture.Api.Reactions.ReactionInitializationModule uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 64 | High / Critical |
| A05:2025 — Injection | 33 | High / Critical |
| A02:2025 — Security Misconfiguration | 8 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 77 Orphaned file finding(s) in Knowledge Freshness — start with Namespaces.fs (2), Types.fs (2), ApplicationReadModels.fs; Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.0 pts | Low | ADR Quality |
| Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). | +2.4 pts | Low | Secret Scanning |
| Resolve the 77 Orphaned file finding(s) in Knowledge Freshness — start with Namespaces.fs (2), Types.fs (2), ApplicationReadModels.fs. | +3.0 pts | Medium | Knowledge Freshness |
| 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. | +2.3 pts | Medium | Architecture documentation |
| Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing. | +1.8 pts | Medium | Security & performance tooling |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +0.8 pts | Low | Project Cohesion |
| Improve Test Distribution — currently 5.3/10. | +1.6 pts | Medium | Test Distribution |
| Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +0.5 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.8 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 0.8 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 0.9 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 0.9 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.1 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 6.5 | Mixed | IaC & Container Security: High IaC: REDACTED |
| frontend-vue/src/visualisations/Bubble.js | 7.1 | Near-clean | Cognitive Complexity: Bubble.showMainPage (cognitive 49) |
| backend/Contexture.Api/Filebased/Database.fs | 7.2 | Near-clean | God Classes: FileTooLong: Filebased/Database.fs |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| backend/Contexture.Api/Infrastructure/InMemory.fs | 7.8 | Near-clean | Cyclomatic Complexity: SingleWriterPipeline.singleWriterPipeline (cyclomatic 19) |
| backend/Contexture.Api/ReadModels/Find/FindReadModels.fs | 7.8 | Near-clean | Code Duplication: Duplicated block (16 lines × 2) |
| frontend-vue/src/core/filter.ts | 8.5 | Near-clean | Cognitive Complexity: filter.filter (cognitive 22) |
| frontend-vue/src/visualisations/Sunburst.js | 8.5 | Near-clean | Cognitive Complexity: Sunburst.renderSunburst (cognitive 17) |
| frontend-vue/src/stores/boundedContexts.ts | 8.5 | Near-clean | God Classes: FunctionTooLong: boundedContexts.useBoundedContextsStore |
| frontend-vue/src/stores/namespaces.ts | 8.5 | Near-clean | God Classes: FunctionTooLong: namespaces.useNamespaces |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 62 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 62 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 273 of 292 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
- D10 Test 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. The 77 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 14 test source file(s) (.fs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D12 Dependency Hygiene — 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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. All 80 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 80 of the 161 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
- 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 — 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. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- 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.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `backend/Contexture.Api/appsettings.Development.json`, `backend/Contexture.Api/appsettings.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
- D39 IL Efficiency — 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. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Microsoft.Extensions.DependencyInjection registered from F#, 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 REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:10 -------------------- 8 | ENV FileBased__Path=/data/db.json 9 | ENV GitHash=$GIT_HASH 10 | >>> RUN ["chmod", "+x", "./entrypoint.sh"] 11 | ENTRYPOINT ["./entrypoint.sh"] 12 | -------------------- ERROR: failed to solve: process "chmod +x ./entrypoint.sh" did not complete successfully: exit code: 1; 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.
- 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 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M3 Folder & project structure — 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. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
- 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.
- R10 Code Duplication — 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. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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 (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- 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
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SingleWriterPipeline.singleWriterPipeline at 19. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being CascadeDelete.project at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: backend/Contexture.Api/Reactions.fs (CascadeDelete.project at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with SingleWriterPipeline.singleWriterPipeline (cyclomatic 19). — Refactoring it lifts Cyclomatic Complexity from 9.7 to about 10.0/10.
- 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
8 method(s) exceeded the cognitive complexity threshold of 15; the worst was Bubble.showMainPage at 49.
What to do
- Bring the 8 bodies over 15 down to 15 or less in Cognitive Complexity — start with Bubble.showMainPage (cognitive 49), showMainPage (cognitive 49), Bubble.showBoundedContextConnections (cognitive 43). — 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 8 together lifts Cognitive Complexity from 8.1 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
8 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 5 FunctionTooLong finding(s) in God Classes — start with Bubble.js (2), boundedContexts.ts, namespaces.ts. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with Bubble.js, Database.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with Bubble.js. — 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
10 duplicated block group(s) detected. Measured on part of this repository only: .vue (42% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with Database.fs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with Convert.fs, Subscriptions.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with FindReadModels.fs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
2 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 3 classes have LCOM4 above 3.
D9 · Test Distribution
77 test methods: 49 unit, 0 integration, 0 BDD, 28 e2e. The JavaScript/TypeScript suite contributes 77 `it`/`test` case(s) across 10 test file(s) declaring at least one; its tier split is read from package names and paths only.
What to do
- Improve Test Distribution — currently 5.3/10. — 77 test methods: 49 unit, 0 integration, 0 BDD, 28 e2e. The JavaScript/TypeScript suite contributes 77 `it`/`test` case(s) across 10 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 77 tests. Measured on the JavaScript/TypeScript suite only — at least 14 test source file(s) (.fs) went unread, so its test quality is unmeasured and is not in these counts.
D11 · Test Reliability
0 flaky across 2 measured tier(s). integration: measured (0 flaky); JavaScript/TypeScript (vitest via `npm ci --ignore-scripts` in frontend-vue/ (51 tests)): measured (0 flaky).
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 162 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 16 direct `PackageReference`(s), and 145 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (MSBuild, 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).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
33 finding(s): 0 critical, 21 high, 12 medium, 0 low. 16 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.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 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 16 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 (16 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
54 finding(s): 4 critical, 32 high, 15 medium, 3 low.
What to do
- Resolve the 31 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (26), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (31 issue-level).
- Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 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
8 finding(s): 0 critical, 3 high, 3 medium, 2 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D34 · Knowledge Freshness
80 of 80 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is frontend-vue/src/visualisations/Bubble.js. Counted over 80 of the 161 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 77 Orphaned file finding(s) in Knowledge Freshness — start with Namespaces.fs (2), Types.fs (2), ApplicationReadModels.fs. — One of this dimension's main actionable groups (77 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with Bubble.js, Search.vue, Database.fs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 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. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 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.
What to do
- Resolve the 2 End-of-life runtime finding(s) in Platform End-of-Life — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — backend/Contexture.Api/Views/Views.fs:63
- 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. — frontend-vue/src/components/core/auth/SignIn.vue:6
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
- An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — frontend-vue/src/components/core/header/StructurizerDiscloser.vue:27
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — frontend-vue/src/components/primitives/input/ContextureSearch.vue:18
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
- These two <contexturetextlinkbutton> controls (line 18 and line 23) are the two halves of one toggle: each is rendered on a different value of "isInEditMode" and each one's own click handler writes "isInEditMode". Nothing exposes the state programmatically — no aria-pressed on a toggle button, no aria-expanded/aria-controls if it is a disclosure — and neither branch has an accessible name, so assistive tech is told nothing at all when the state changes; a screen-reader user sees only that one nameless control was replaced by another (WCAG 4.1.2). Render ONE control that stays in the DOM and carries aria-pressed="true|false" bound to "isInEditMode", or keep the two branches and give them DISTINCT accessible names (the WAI-ARIA APG name-change pattern), which announces the state through the name instead. — frontend-vue/src/components/bounded-context/canvas/ContextureBoundedContextCanvasElement.vue:18
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
- This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. (×6) — frontend-vue/src/components/bounded-context/namespace/ContextureNamespaces.vue:17, frontend-vue/src/components/core/navbar/ContextureNavbar.vue:2, frontend-vue/src/components/primitives/button/ContexturePrimaryButton.vue:2, …
- <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — frontend-vue/src/components/primitives/input/ContextureSearch.vue:9
- <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — frontend-vue/src/components/primitives/input/ContextureTextarea.vue:7
- `.dot` moves (`animation: dotSpin var(--duration) linear calc(var(--delay) * 0.155s) infinite alternate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend-vue/src/components/primitives/button/util/LoadingWrapper.vue:40
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 89 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. — frontend-vue/package.json:34
What to do
- Enforce accessibility in the toolchain: add eslint-plugin-vuejs-accessibility, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
What to do
- Add OpenTelemetry tracing/metrics (OpenTelemetry.Extensions.Hosting with the ASP.NET Core instrumentation) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 5686 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:5
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:28
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- frontend-vue/src/components/domains/ContextureCreateDomainModal.vue:17 · frontend-vue/src/components/domains/details/ContextureCreateSubdomainModal.vue:18 — these 2 files are line-for-line copies of one another — 54 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — frontend-vue/src/components/domains/ContextureCreateDomainModal.vue:17
- frontend-vue/src/components/bounded-context/canvas/BCCMessagesConsumed.vue:140 · frontend-vue/src/components/bounded-context/canvas/BCCMessagesProduced.vue:140 — these 2 files are line-for-line copies of one another — 50 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — frontend-vue/src/components/bounded-context/canvas/BCCMessagesConsumed.vue:140
- frontend-vue/src/visualisations/Bubble.js:525 · frontend-vue/src/visualisations/Bubble.js:762 — 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. — frontend-vue/src/visualisations/Bubble.js:525
- frontend-vue/src/components/bounded-context/canvas/BCCBusinessDecisions.vue:110 · frontend-vue/src/components/bounded-context/canvas/BCCUbiquitousLanguage.vue:109 — 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. — frontend-vue/src/components/bounded-context/canvas/BCCBusinessDecisions.vue:110
- frontend-vue/src/components/primitives/checkbox/ContextureCheckbox.vue:42 · frontend-vue/src/components/primitives/radio/ContextureRadio.vue:42 — the two spans are one implementation copied and then locally edited — 201 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. — frontend-vue/src/components/primitives/checkbox/ContextureCheckbox.vue:42
- frontend-vue/src/visualisations/HierarchicalEdge.js:190 · frontend-vue/src/visualisations/Sunburst.js:95 — 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. — frontend-vue/src/visualisations/HierarchicalEdge.js:190
- frontend-vue/src/components/primitives/input/ContextureInputText.vue:45 · frontend-vue/src/components/primitives/input/ContextureTextarea.vue:42 — the two spans are one implementation copied and then locally edited — 125 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. — frontend-vue/src/components/primitives/input/ContextureInputText.vue:45
- frontend-vue/src/components/primitives/button/ContexturePrimaryButton.vue:15 · frontend-vue/src/components/primitives/button/ContextureWhiteButton.vue:15 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — frontend-vue/src/components/primitives/button/ContexturePrimaryButton.vue:15
- frontend-vue/src/components/domains/details/ContextureCreateBoundedContextModal.vue:84 · frontend-vue/src/components/domains/details/ContextureCreateSubdomainModal.vue:81 — 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. — frontend-vue/src/components/domains/details/ContextureCreateBoundedContextModal.vue:84
- frontend-vue/src/components/primitives/button/ContextureSecondaryButton.vue:16 · frontend-vue/src/components/primitives/button/ContextureTextLinkButton.vue:16 — 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. — frontend-vue/src/components/primitives/button/ContextureSecondaryButton.vue:16
- frontend-vue/src/components/primitives/autocomplete/ContextureAutocomplete.vue:142 · frontend-vue/src/components/primitives/radio/ContextureRadioGroup.vue:50 — 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. — frontend-vue/src/components/primitives/autocomplete/ContextureAutocomplete.vue:142
- frontend-vue/src/stores/boundedContexts.ts:183 · frontend-vue/src/stores/boundedContexts.ts:204 — all 2 copies are in the same file, 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. — frontend-vue/src/stores/boundedContexts.ts:183
- frontend-vue/src/stores/namespaces.ts:83 · frontend-vue/src/stores/namespaces.ts:110 — all 2 copies are in the same file, 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. — frontend-vue/src/stores/namespaces.ts:83
- frontend-vue/src/visualisations/Bubble.js:214 · frontend-vue/src/visualisations/Bubble.js:368 — 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. — frontend-vue/src/visualisations/Bubble.js:214
- frontend-vue/src/components/bounded-context/namespace/NamespaceLabelAutocomplete.vue:27 · frontend-vue/src/components/bounded-context/namespace/NamespaceValueAutocomplete.vue:32 — the two spans are one implementation copied and then locally edited — 80 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. — frontend-vue/src/components/bounded-context/namespace/NamespaceLabelAutocomplete.vue:27
- frontend-vue/src/components/bounded-context/canvas/BCCDescription.vue:63 · frontend-vue/src/components/bounded-context/canvas/BCCKey.vue:67 · frontend-vue/src/components/bounded-context/canvas/BCCStrategicClassification.vue:268 — the 3 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. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — frontend-vue/src/components/bounded-context/canvas/BCCDescription.vue:63
- frontend-vue/src/components/bounded-context/ContextureMoveBoundedContextModal.vue:71 · frontend-vue/src/components/domains/ContextureMoveDomainModal.vue:101 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — frontend-vue/src/components/bounded-context/ContextureMoveBoundedContextModal.vue:71
- frontend-vue/src/components/bounded-context/canvas/BCCDescription.vue:61 · frontend-vue/src/components/bounded-context/canvas/BCCKey.vue:65 — 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. — frontend-vue/src/components/bounded-context/canvas/BCCDescription.vue:61
- frontend-vue/src/visualisations/Bubble.js:1383 · frontend-vue/src/visualisations/Bubble.js:1419 — all 2 copies are in the same file, 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. — frontend-vue/src/visualisations/Bubble.js:1383
- frontend-vue/src/components/domains/details/ContextureCreateBoundedContextModal.vue:35 · frontend-vue/src/components/domains/details/ContextureCreateSubdomainModal.vue:33 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — frontend-vue/src/components/domains/details/ContextureCreateBoundedContextModal.vue:35
- frontend-vue/src/stores/boundedContexts.ts:51 · frontend-vue/src/stores/namespace-templates.ts:10 · frontend-vue/src/stores/namespaces.ts:19 — the 3 copies are spread across 3 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. — frontend-vue/src/stores/boundedContexts.ts:51
- frontend-vue/src/stores/boundedContexts.ts:64 · frontend-vue/src/stores/domains.ts:59 — 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. — frontend-vue/src/stores/boundedContexts.ts:64
- frontend-vue/src/components/bounded-context/canvas/BCCBusinessDecisions.vue:116 · frontend-vue/src/components/bounded-context/canvas/BCCDomainRoles.vue:172 · frontend-vue/src/components/bounded-context/canvas/BCCUbiquitousLanguage.vue:115 — the 3 copies are spread across 3 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. — frontend-vue/src/components/bounded-context/canvas/BCCBusinessDecisions.vue:116
- frontend-vue/src/components/bounded-context/canvas/BCCConnection.vue:291 · frontend-vue/src/components/bounded-context/canvas/BCCConnection.vue:311 — all 2 copies are in the same file, 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. — frontend-vue/src/components/bounded-context/canvas/BCCConnection.vue:291
- frontend-vue/src/components/core/change-short-name/changeShortNameValidationSchema.ts:20 · frontend-vue/src/components/core/change-short-name/changeShortNameValidationSchema.ts:44 — all 2 copies are in the same file, 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. — frontend-vue/src/components/core/change-short-name/changeShortNameValidationSchema.ts:20
- frontend-vue/src/components/primitives/button/ContextureIconButton.vue:10 · frontend-vue/src/components/primitives/button/ContexturePrimaryButton.vue:18 · frontend-vue/src/components/primitives/button/ContextureSecondaryButton.vue:18 · frontend-vue/src/components/primitives/button/ContextureTextLinkButton.vue:18 · +1 more site(s) not listed — the 5 copies are spread across 5 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. — frontend-vue/src/components/primitives/button/ContextureIconButton.vue:10
- frontend-vue/src/composables/useFetch.ts:25 · frontend-vue/src/stores/auth.ts:37 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — frontend-vue/src/composables/useFetch.ts:25
- frontend-vue/src/stores/boundedContexts.ts:102 · frontend-vue/src/stores/boundedContexts.ts:120 — 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. — frontend-vue/src/stores/boundedContexts.ts:102
- frontend-vue/src/components/bounded-context/ContextureMoveBoundedContextModal.vue:52 · frontend-vue/src/components/domains/details/ContextureCreateBoundedContextModal.vue:35 · frontend-vue/src/components/domains/details/ContextureCreateSubdomainModal.vue:33 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — frontend-vue/src/components/bounded-context/ContextureMoveBoundedContextModal.vue:52
- frontend-vue/src/components/bounded-context/canvas/BCCDescription.vue:63 · frontend-vue/src/components/bounded-context/canvas/BCCKey.vue:67 · frontend-vue/src/components/bounded-context/canvas/BCCStrategicClassification.vue:268 · frontend-vue/src/pages/bounded-context/BoundedContextCanvas.vue:125 — the 4 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — frontend-vue/src/components/bounded-context/canvas/BCCDescription.vue:63
- frontend-vue/src/stores/namespaces.ts:162 · frontend-vue/src/stores/namespaces.ts:189 — all 2 copies are in the same file, 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. — frontend-vue/src/stores/namespaces.ts:162
- frontend-vue/src/visualisations/Bubble.js:99 · frontend-vue/src/visualisations/Bubble.js:146 — 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. — frontend-vue/src/visualisations/Bubble.js:99
- frontend-vue/src/visualisations/Bubble.js:908 · frontend-vue/src/visualisations/Bubble.js:940 — 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. — frontend-vue/src/visualisations/Bubble.js:908
- frontend-vue/src/visualisations/Bubble.js:562 · frontend-vue/src/visualisations/Bubble.js:799 — 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. — frontend-vue/src/visualisations/Bubble.js:562
- frontend-vue/src/components/bounded-context/canvas/BCCBusinessDecisions.vue:120 · frontend-vue/src/components/bounded-context/canvas/BCCDefineRelationshipModal.vue:236 · frontend-vue/src/components/bounded-context/canvas/BCCDomainRoles.vue:176 · frontend-vue/src/components/bounded-context/canvas/BCCUbiquitousLanguage.vue:119 — the 4 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. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — frontend-vue/src/components/bounded-context/canvas/BCCBusinessDecisions.vue:120
- frontend-vue/src/visualisations/Bubble.js:64 · frontend-vue/src/visualisations/Bubble.js:110 — all 2 copies are in the same file, 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. — frontend-vue/src/visualisations/Bubble.js:64
- frontend-vue/src/visualisations/Bubble.js:387 · frontend-vue/src/visualisations/Bubble.js:561 · frontend-vue/src/visualisations/Bubble.js:798 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — frontend-vue/src/visualisations/Bubble.js:387
- frontend-vue/src/visualisations/HierarchicalEdge.js:338 · frontend-vue/src/visualisations/HierarchicalEdge.js:362 — 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. — frontend-vue/src/visualisations/HierarchicalEdge.js:338
- frontend-vue/src/components/bounded-context/namespace/ContextureNamespaces.vue:227 · frontend-vue/src/components/bounded-context/namespace/ContextureNamespaces.vue:248 — 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. — frontend-vue/src/components/bounded-context/namespace/ContextureNamespaces.vue:227
- frontend-vue/src/visualisations/HierarchicalEdge.js:89 · frontend-vue/src/visualisations/HierarchicalEdge.js:105 — all 2 copies are in the same file, 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. — frontend-vue/src/visualisations/HierarchicalEdge.js:89
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
- showMainPage has cyclomatic complexity 15 and cognitive complexity 49; 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. — frontend-vue/src/visualisations/Bubble.js:241
- filter has cyclomatic complexity 12 and cognitive complexity 22; 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. — frontend-vue/src/core/filter.ts:9
- filteredColab has cyclomatic complexity 11 and cognitive complexity 14; 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. — frontend-vue/src/visualisations/HierarchicalEdge.js:246
R3 · Large Files
- frontend-vue/src/visualisations/Bubble.js has 1251 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend-vue/src/visualisations/Bubble.js:1
- frontend-vue/src/pages/analytics/Analytics.vue has 413 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend-vue/src/pages/analytics/Analytics.vue:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
R5 · Dependency Freshness
- 44 outdated package(s); JS/npm CVEs scored in D30
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
- Nothing imports this binding — it is safe to review for removal. — frontend-vue/src/types/collaboration.ts:6
R8 · Dependency Hygiene
- Declared in frontend-vue/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. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- frontend-vue/src/App.vue → frontend-vue/src/components/core/navbar/ContextureNavbar.vue → frontend-vue/src/routes.ts → frontend-vue/src/pages/bounded-context/BoundedContextCanvas.vue → frontend-vue/src/components/bounded-context/canvas/layouts/BCCV3.vue → frontend-vue/src/components/bounded-context/canvas/BCCMessagesConsumed.vue → frontend-vue/src/core/validationRules.ts → frontend-vue/src/main.ts → frontend-vue/src/App.vue (one verified cycle inside a mutually-dependent group of 15 files) — frontend-vue/src/App.vue:25
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X20 · Mistyped argument guard
- The guard on line 26 rejects `value` and line 27 reports that rejection as `nullArg` — but the condition's own test `String.IsNullOrWhiteSpace value` is true of a value that is NOT null: it is satisfied by an EMPTY `value`, and on that path `value` was already proven non-null by the very expression that decided it. So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `nullArg` to handle a real null handles the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. Raise `ArgumentException` for the empty case — `invalidArg (nameof value) "must not be empty"`, or split the guard and throw each on its own condition. — backend/Contexture.Api/Infrastructure/Types.fs:27
What to do
- Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: on the JVM `IllegalArgumentException` for a value that arrived empty (`Objects.requireNonNull(x)` for the null half, Kotlin's `require(x.isNotEmpty())` for the empty one), in Dart `ArgumentError.value(x, 'x', 'must not be empty')`, in F# `invalidArg (nameof x) "must not be empty"` (keeping `nullArg` for the null half). Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| 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 | 91% | Exemplary | Solid. |
| Architecture | 76% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 50% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 50% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 54% | Checked 5 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 51% | Adequate — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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 — 64 check(s) not relevant to this codebase
- 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
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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 — docker build failed (exit 1) — ------ REDACTED:10 -------------------- 8 | ENV FileBased__Path=/data/db.json 9 | ENV GitHash=$GIT_HASH 10 | >>> RUN ["chmod", "+x", "./entrypoint.sh"] 11 | ENTRYPOINT ["./entrypoint.sh"] 12 | -------------------- ERROR: failed to solve: process "chmod +x ./entrypoint.sh" did not complete successfully: exit code: 1; 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.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F#, JavaScript not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (Contexture.Api), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- 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 — IL not measured — the analyzer's build of the target did not succeed
- 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 dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the .NET half measured 48.9%; the JavaScript/TypeScript half could not be measured — frontend-vue/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 2 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 12 domain event(s); its domain events are published by services or handlers — no domain entity raises one; a Domain/Aggregates/ValueObjects layer; a top-level example/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 1 aggregate(s) with Apply/When folds; an append-only event-store seam (IEventStore/Append-of-events)
- 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 — not measured — the application kind could not be determined for this repo
- 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 (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — 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
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — 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
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 68 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
- 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
- <button> with no accessible text backend/Contexture.Api/Views/Views.fs:63
- <label> that labels no control frontend-vue/src/components/core/auth/SignIn.vue:6
- <iframe> without a title frontend-vue/src/components/core/header/StructurizerDiscloser.vue:27
- Click handler on a non-interactive <div> frontend-vue/src/components/primitives/input/ContextureSearch.vue:18
- Toggle state conveyed only by which <contexturetextlinkbutton> renders frontend-vue/src/components/bounded-context/canvas/ContextureBoundedContextCanvasElement.vue:18
- REDACTED
- REDACTED
- Import cycle (8 files) frontend-vue/src/App.vue:25
Serious — 124 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: Bubble.showBoundedContextConnections frontend-vue/src/visualisations/Bubble.js:814
- FunctionTooLong: boundedContexts.useBoundedContextsStore frontend-vue/src/stores/boundedContexts.ts:19
- FunctionTooLong: Bubble.showSubdomainPage frontend-vue/src/visualisations/Bubble.js:573
- FunctionTooLong: namespaces.useNamespaces frontend-vue/src/stores/namespaces.ts:15
- FunctionTooLong: domains.useDomainsStore frontend-vue/src/stores/domains.ts:7
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (18 lines × 2 locations) frontend-vue/src/components/primitives/autocomplete/ContextureAutocomplete.vue:142
- Duplicated block (18 lines × 2 locations) frontend-vue/src/stores/boundedContexts.ts:183
- Duplicated block (18 lines × 2 locations) frontend-vue/src/stores/namespaces.ts:83
- Duplicated block (18 lines × 2 locations) frontend-vue/src/visualisations/Bubble.js:214
- Duplicated block (12 lines × 2 locations) frontend-vue/src/components/bounded-context/canvas/BCCConnection.vue:291
- Duplicated block (12 lines × 2 locations) frontend-vue/src/components/core/change-short-name/changeShortNameValidationSchema.ts:20
- Duplicated block (12 lines × 2 locations) frontend-vue/src/composables/useFetch.ts:25
- Duplicated block (12 lines × 2 locations) frontend-vue/src/stores/boundedContexts.ts:102
- Low contrast Tailwind colour pair (3.6:1) frontend-vue/src/components/bounded-context/namespace/ContextureNamespaces.vue:17
- Low contrast Tailwind colour pair (3.6:1) frontend-vue/src/components/primitives/button/ContexturePrimaryButton.vue:2
- Low contrast Tailwind colour pair (3.6:1) frontend-vue/src/pages/domain-details/DomainDetails.vue:92
- Low contrast Tailwind colour pair (3.8:1) frontend-vue/src/components/core/navbar/ContextureNavbar.vue:2
- Low contrast Tailwind colour pair (3.8:1) frontend-vue/src/components/primitives/button/ContextureWhiteButton.vue:2
- Low contrast Tailwind colour pair (3.8:1) frontend-vue/src/components/primitives/input/ContextureSearch.vue:19
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (14 lines × 2 locations) frontend-vue/src/components/bounded-context/ContextureMoveBoundedContextModal.vue:71
- Duplicated block (14 lines × 2 locations) frontend-vue/src/components/bounded-context/canvas/BCCDescription.vue:61
- Duplicated block (14 lines × 2 locations) frontend-vue/src/visualisations/Bubble.js:1383
- Duplicated block (11 lines × 2 locations) frontend-vue/src/stores/namespaces.ts:162
- Duplicated block (11 lines × 2 locations) frontend-vue/src/visualisations/Bubble.js:99
- Duplicated block (11 lines × 2 locations) frontend-vue/src/visualisations/Bubble.js:908
- Focus outline removed inline frontend-vue/src/components/primitives/input/ContextureSearch.vue:9
- Focus outline removed inline frontend-vue/src/components/primitives/input/ContextureTextarea.vue:7
- FileTooLong: visualisations/Bubble.js frontend-vue/src/visualisations/Bubble.js
- FileTooLong: Filebased/Database.fs backend/Contexture.Api/Filebased/Database.fs
- Duplicated block (11 lines × 2) backend/Contexture.Api/Filebased/Database.fs:265
- Duplicated block (11 lines × 2) backend/Contexture.Api/Filebased/Database.fs:532
- Duplicated block (7 lines × 2) backend/Contexture.Api/Filebased/Convert.fs:169
- Duplicated block (7 lines × 2) backend/Contexture.Api/Infrastructure/Subscriptions.fs:134
- End-of-life runtime: .NET net7.0 REDACTED:4
- End-of-life runtime: .NET net7.0 REDACTED:4
- Duplicated block (22 lines × 2 locations) frontend-vue/src/components/domains/details/ContextureCreateBoundedContextModal.vue:84
- Duplicated block (22 lines × 2 locations) frontend-vue/src/components/primitives/button/ContextureSecondaryButton.vue:16
- Duplicated block (13 lines × 2 locations) frontend-vue/src/components/domains/details/ContextureCreateBoundedContextModal.vue:35
- Duplicated block (13 lines × 2 locations) frontend-vue/src/stores/boundedContexts.ts:64
- Duplicated block (9 lines × 2 locations) frontend-vue/src/visualisations/Bubble.js:64
- Duplicated block (9 lines × 2 locations) frontend-vue/src/visualisations/HierarchicalEdge.js:338
- Duplicated block (8 lines × 2 locations) frontend-vue/src/components/bounded-context/namespace/ContextureNamespaces.vue:227
- Duplicated block (8 lines × 2 locations) frontend-vue/src/visualisations/HierarchicalEdge.js:89
- Animation without a prefers-reduced-motion guard frontend-vue/src/components/primitives/button/util/LoadingWrapper.vue:40
- Accessibility enforcement below the top rung frontend-vue/package.json:34
- SingleWriterPipeline.singleWriterPipeline (cyclomatic 19) backend/Contexture.Api/Infrastructure/InMemory.fs:86
- Bubble.showMainPage (cognitive 49) frontend-vue/src/visualisations/Bubble.js:241
- Bubble.showBoundedContextConnections (cognitive 43) frontend-vue/src/visualisations/Bubble.js:814
- filter.filter (cognitive 22) frontend-vue/src/core/filter.ts:9
- SingleWriterPipeline.singleWriterPipeline (cognitive 17) backend/Contexture.Api/Infrastructure/InMemory.fs:86
- Sunburst.renderSunburst (cognitive 17) frontend-vue/src/visualisations/Sunburst.js:150
- MethodTooLong: Bubble.buildData frontend-vue/src/visualisations/Bubble.js:1273
- REDACTED
- REDACTED
- Duplicated block (16 lines × 2) backend/Contexture.Api/ReadModels/Find/FindReadModels.fs:151
- Duplicated block (13 lines × 2) backend/Contexture.Api/ReadModels/Find/FindReadModels.fs:252
- Duplicated block (8 lines × 2) backend/Contexture.Api/Apis/Collaborations.fs:47
- Duplicated block (2–5 lines × 7) backend/Contexture.Api/AllRoutes.fs:16
- Duplicated block (6 lines × 2) backend/Contexture.Api/Apis/BoundedContexts.fs:65
- Duplicated block (5 lines × 2) backend/Contexture.Api/Filebased/Database.fs:516
- Coverage not measured — JavaScript/TypeScript suite
- Wholesale file copy (54 identical lines × 2 files) frontend-vue/src/components/domains/ContextureCreateDomainModal.vue:17
- Wholesale file copy (50 identical lines × 2 files) frontend-vue/src/components/bounded-context/canvas/BCCMessagesConsumed.vue:140
- Duplicated block (43 lines × 2 locations) frontend-vue/src/visualisations/Bubble.js:525
- Duplicated block (41 lines × 2 locations) frontend-vue/src/components/bounded-context/canvas/BCCBusinessDecisions.vue:110
- Duplicated block with local edits (37 matched lines × 2 locations) frontend-vue/src/components/primitives/checkbox/ContextureCheckbox.vue:42
- Duplicated block (26 lines × 2 locations) frontend-vue/src/visualisations/HierarchicalEdge.js:190
- Duplicated block with local edits (25 matched lines × 2 locations) frontend-vue/src/components/primitives/input/ContextureInputText.vue:45
- Duplicated block (24 lines × 2 locations) frontend-vue/src/components/primitives/button/ContexturePrimaryButton.vue:15
- Duplicated block with local edits (16 matched lines × 2 locations) frontend-vue/src/components/bounded-context/namespace/NamespaceLabelAutocomplete.vue:27
- Duplicated block (15 lines × 3 locations) frontend-vue/src/components/bounded-context/canvas/BCCDescription.vue:63
- Duplicated block (13 lines × 3 locations) frontend-vue/src/stores/boundedContexts.ts:51
- Duplicated block (12 lines × 3 locations) frontend-vue/src/components/bounded-context/canvas/BCCBusinessDecisions.vue:116
- Duplicated block (12 lines × 5 locations) frontend-vue/src/components/primitives/button/ContextureIconButton.vue:10
- Duplicated block (11 lines × 3 locations) frontend-vue/src/components/bounded-context/ContextureMoveBoundedContextModal.vue:52
- Duplicated block (11 lines × 4 locations) frontend-vue/src/components/bounded-context/canvas/BCCDescription.vue:63
- Duplicated block (10 lines × 2 locations) frontend-vue/src/visualisations/Bubble.js:562
- Duplicated block (9 lines × 4 locations) frontend-vue/src/components/bounded-context/canvas/BCCBusinessDecisions.vue:120
- Duplicated block (9 lines × 3 locations) frontend-vue/src/visualisations/Bubble.js:387
- Complex function showMainPage (cyclomatic 15, cognitive 49) frontend-vue/src/visualisations/Bubble.js:241
- Complex function filter (cyclomatic 12, cognitive 22) frontend-vue/src/core/filter.ts:9
- Complex function filteredColab (cyclomatic 11, cognitive 14) frontend-vue/src/visualisations/HierarchicalEdge.js:246
- frontend-vue/src/visualisations/Bubble.js: 1251 lines of code frontend-vue/src/visualisations/Bubble.js:1
- frontend-vue/src/pages/analytics/Analytics.vue: 413 lines of code frontend-vue/src/pages/analytics/Analytics.vue:1
- Dependency Freshness
- Unused dependency '@iconify-json/material-symbols'
- Unused dependency '@vue/test-utils'
- Unused dependency 'vite-plugin-pages'
- NuGet dependencies are not locked
- Argument guard throws the exception its own condition disproves backend/Contexture.Api/Infrastructure/Types.fs:27
Minor — 100 finding(s)
- Orphaned file backend/Contexture.Api/ReadModels/ApplicationReadModels.fs:1
- Orphaned file backend/Contexture.Api/Program.fs:1
- Orphaned file backend/Contexture.Api/Infrastructure/NStoreBased.fs:1
- Orphaned file frontend-vue/src/pages/analytics/Analytics.vue:1
- Orphaned file backend/Contexture.Api/Infrastructure/Security.fs:1
- Orphaned file backend/Contexture.Api/Apis/BoundedContexts.fs:1
- Orphaned file frontend-vue/src/pages/domain-details/DomainDetails.vue:1
- Orphaned file frontend-vue/src/components/bounded-context/canvas/BCCConnection.vue:1
- Orphaned file backend/Contexture.Api/ReadModels/Find/FindReadModels.fs:1
- Orphaned file backend/Contexture.Api/Entities/BoundedContext.fs:1
- Orphaned file backend/Contexture.Api/Filebased/Convert.fs:1
- Orphaned file backend/Contexture.Api/Infrastructure/InMemory.fs:1
- Orphaned file frontend-vue/src/components/bounded-context/namespace/ContextureNamespaces.vue:1
- Orphaned file backend/Contexture.Api/Apis/Domains.fs:1
- Orphaned file frontend-vue/src/visualisations/HierarchicalEdge.js:1
- Orphaned file backend/Contexture.Api/Reactions.fs:1
- Orphaned file frontend-vue/src/components/bounded-context/ContextureBoundedContextCard.vue:1
- Orphaned file frontend-vue/src/components/bounded-context/canvas/BCCStrategicClassification.vue:1
- Orphaned file backend/Contexture.Api/Entities/Namespace.fs:1
- Orphaned file backend/Contexture.Api/Apis/Namespaces.fs:1
- Orphaned file frontend-vue/src/stores/boundedContexts.ts:1
- Orphaned file frontend-vue/src/components/bounded-context/canvas/BCCMessagesConsumed.vue:1
- Orphaned file frontend-vue/src/components/bounded-context/canvas/BCCMessagesProduced.vue:1
- Orphaned file backend/Contexture.Api/AllRoutes.fs:1
- Orphaned file backend/Contexture.Api/Entities/Domain.fs:1
- REDACTED
- REDACTED
- REDACTED
- Most significant orphaned file frontend-vue/src/visualisations/Bubble.js:1
- Most significant orphaned file frontend-vue/src/pages/search/Search.vue:1
- Most significant orphaned file backend/Contexture.Api/Filebased/Database.fs:1
- REDACTED
- REDACTED
- No ADRs found
- Projects may be oversized for their cohesion
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No src/ separation
- No SAST REDACTED:5
- No dependency-update automation REDACTED:28
- No rollback/health safety
- No changelog
- Unused export 'RelationshipTypes' frontend-vue/src/types/collaboration.ts:6
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-099618e8b8684233b92fdf0d0ecd0bc3/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-099618e8b8684233b92fdf0d0ecd0bc3/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 . | 33 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list backend/Contexture.sln package --vulnerable --include-transitive --format json | 54 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 8 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | 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 |