Executive summary
FidelityFramework/Fidelity.CloudEdge falls short of our standard for a preview release because its Git mining dimensions are rated Critical, and we found no automated security scanning of the code, its secrets or its dependencies. It scores 56 out of 100, which alone would earn Adequate, but it is rated Weak: a rating can't sit more than one step above its weakest group.
Production Readiness, at 51, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 4 points. Writing design decisions down in full comes next, worth about 3 points. Raising Production Readiness to 62 would lift the score to about 59.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two secrets can leak from the build pipeline, and one known security hole in a package the code depends on can be used by attackers. Pinning each tool to an exact version, limiting each secret to its own step and updating the vulnerable packages would close these risks. The pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions.
The product code is 96 lines, too few for a meaningful rebuild estimate.
If Production Readiness rose from 51 to 62, the lowest score rated Strong, the score would rise from 56 to about 59.
Fixed since the last survey: 175 findings
- God Classes · FileTooLong: Generated-AI/Client.fs generators/hawaii/Generated-AI/Client.fs
- God Classes · FileTooLong: CloudEdge.Management.AI/Client.fs src/Management/CloudEdge.Management.AI/Client.fs
- God Classes · FileTooLong: Generated-Magic/Client.fs generators/hawaii/Generated-Magic/Client.fs
- God Classes · FileTooLong: CloudEdge.Management.Magic/Client.fs src/Management/CloudEdge.Management.Magic/Client.fs
- God Classes · TooManyMethods: AIClient generators/hawaii/Generated-AI/Client.fs
- God Classes · TooManyMethods: AIClient src/Management/CloudEdge.Management.AI/Client.fs
- God Classes · TooManyMethods: MagicClient generators/hawaii/Generated-Magic/Client.fs
- God Classes · TooManyMethods: MagicClient src/Management/CloudEdge.Management.Magic/Client.fs
- God Classes · FileTooLong: Generated-AISearch/Types.fs generators/hawaii/Generated-AISearch/Types.fs
- God Classes · FileTooLong: CloudEdge.Management.AISearch/Types.fs src/Management/CloudEdge.Management.AISearch/Types.fs
- God Classes · FileTooLong: Generated-AIGateway/Types.fs generators/hawaii/Generated-AIGateway/Types.fs
- God Classes · FileTooLong: CloudEdge.Management.AIGateway/Types.fs src/Management/CloudEdge.Management.AIGateway/Types.fs
- God Classes · FileTooLong: Generated-Access/Client.fs generators/hawaii/Generated-Access/Client.fs
- God Classes · FileTooLong: CloudEdge.Management.Access/Client.fs src/Management/CloudEdge.Management.Access/Client.fs
- God Classes · TooManyMethods: AccessClient generators/hawaii/Generated-Access/Client.fs
- God Classes · TooManyMethods: AccessClient src/Management/CloudEdge.Management.Access/Client.fs
- God Classes · FileTooLong: Generated-Email/Client.fs generators/hawaii/Generated-Email/Client.fs
- God Classes · FileTooLong: CloudEdge.Management.Email/Client.fs src/Management/CloudEdge.Management.Email/Client.fs
- God Classes · FileTooLong: Generated-Stream/Client.fs generators/hawaii/Generated-Stream/Client.fs
- God Classes · FileTooLong: CloudEdge.Management.Stream/Client.fs src/Management/CloudEdge.Management.Stream/Client.fs
- God Classes · FileTooLong: Generated-Builds/Types.fs generators/hawaii/Generated-Builds/Types.fs
- God Classes · FileTooLong: CloudEdge.Management.Builds/Types.fs src/Management/CloudEdge.Management.Builds/Types.fs
- God Classes · FileTooLong: Generated-AIGateway/Client.fs generators/hawaii/Generated-AIGateway/Client.fs
- God Classes · FileTooLong: CloudEdge.Management.AIGateway/Client.fs src/Management/CloudEdge.Management.AIGateway/Client.fs
- God Classes · FileTooLong: Generated-Gateway/Client.fs generators/hawaii/Generated-Gateway/Client.fs
- God Classes · FileTooLong: CloudEdge.Management.Gateway/Client.fs src/Management/CloudEdge.Management.Gateway/Client.fs
- God Classes · TooManyMethods: GatewayClient generators/hawaii/Generated-Gateway/Client.fs
- God Classes · TooManyMethods: GatewayClient src/Management/CloudEdge.Management.Gateway/Client.fs
- God Classes · TooManyMethods: StreamClient generators/hawaii/Generated-Stream/Client.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.AI/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.AIGateway/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.AISearch/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Access/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Analytics/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.AutoRAG/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.BrowserRendering/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Builds/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Calls/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Containers/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.D1/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.DurableObjects/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Email/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.EventNotifications/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.EventSubscriptions/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Gateway/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Hyperdrive/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Images/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.KV/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.LoadBalancers/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Logs/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Magic/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Mesh/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.MoQ/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Pages/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Pipelines/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Queues/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.R2/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.R2Catalog/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Registrar/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.ResourceLibrary/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.SecretsStore/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.SecurityCenter/OpenApiHttp.fs
- God Classes · TooManyMethods: StreamClient src/Management/CloudEdge.Management.Stream/Client.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Stream/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Tunnels/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Vectorize/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.VulnScanner/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.WaitingRooms/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Workers/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Management/CloudEdge.Management.Workflows/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Tenancy/CloudEdge.Tenancy.Organizations/OpenApiHttp.fs
- God Classes · TooManyMethods: RequestPart src/Tenancy/CloudEdge.Tenancy.Tenants/OpenApiHttp.fs
- God Classes · FileTooLong: Generated-Workflows/Types.fs generators/hawaii/Generated-Workflows/Types.fs
- God Classes · FileTooLong: CloudEdge.Management.Workflows/Types.fs src/Management/CloudEdge.Management.Workflows/Types.fs
- God Classes · TooManyMethods: EmailClient generators/hawaii/Generated-Email/Client.fs
- God Classes · TooManyMethods: EmailClient src/Management/CloudEdge.Management.Email/Client.fs
- God Classes · TooManyMethods: AIGatewayClient generators/hawaii/Generated-AIGateway/Client.fs
- God Classes · TooManyMethods: AIGatewayClient src/Management/CloudEdge.Management.AIGateway/Client.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.AI/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.AIGateway/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.AISearch/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.Access/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.Analytics/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.AutoRAG/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.BrowserRendering/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.Builds/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.Calls/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.Containers/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.D1/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.DurableObjects/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.Email/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.EventNotifications/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.EventSubscriptions/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.Gateway/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.Hyperdrive/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.Images/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.KV/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.LoadBalancers/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.Logs/OpenApiHttp.fs
- God Classes · TooManyFunctions: OpenApiHttp src/Management/CloudEdge.Management.Magic/OpenApiHttp.fs
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 D1 | 2 Hyperdrive | 3 KV | 4 Management.AI.Http | 5 Management.AI.Types | 6 Management.AIGateway.Http | 7 Management.AIGateway.Types | 8 Management.AISearch.Http | 9 Management.AISearch.Types | 10 Management.Access.Http | 11 Management.Access.Types | 12 Management.Analytics.Http | 13 Management.Analytics.Types | 14 Management.AutoRAG.Http | 15 Management.AutoRAG.Types | 16 Management.BrowserRendering | 17 Management.BrowserRendering.Http | 18 Queues | 19 Worker.Context | 20 D1.Helpers | 21 DurableObjects | 22 Hyperdrive.Helpers | 23 Hyperdrive.Helpers.DatabaseAdapters | 24 KV.Helpers | 25 Management.AI | 26 Management.AI.Http.OpenApiHttp | 27 Management.AIGateway | 28 Management.AIGateway.Http.OpenApiHttp | 29 Management.AISearch | 30 Management.AISearch.Http.OpenApiHttp | 31 Management.Access | 32 Management.Access.Http.OpenApiHttp | 33 Management.Analytics | 34 Management.Analytics.Http.OpenApiHttp | 35 Management.AutoRAG | 36 Management.AutoRAG.Http.OpenApiHttp | 37 Management.BrowserRendering.Http.OpenApiHttp | 38 DurableObjects.Helpers | 39 DurableObjects.Helpers.Storage | 40 DurableObjects.Helpers.WebSocket |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 D1 | ||||||||||||||||||||||||||||||||||||||||
| 2 Hyperdrive | ||||||||||||||||||||||||||||||||||||||||
| 3 KV | ||||||||||||||||||||||||||||||||||||||||
| 4 Management.AI.Http | ||||||||||||||||||||||||||||||||||||||||
| 5 Management.AI.Types | ||||||||||||||||||||||||||||||||||||||||
| 6 Management.AIGateway.Http | ||||||||||||||||||||||||||||||||||||||||
| 7 Management.AIGateway.Types | ||||||||||||||||||||||||||||||||||||||||
| 8 Management.AISearch.Http | ||||||||||||||||||||||||||||||||||||||||
| 9 Management.AISearch.Types | ||||||||||||||||||||||||||||||||||||||||
| 10 Management.Access.Http | ||||||||||||||||||||||||||||||||||||||||
| 11 Management.Access.Types | ||||||||||||||||||||||||||||||||||||||||
| 12 Management.Analytics.Http | ||||||||||||||||||||||||||||||||||||||||
| 13 Management.Analytics.Types | ||||||||||||||||||||||||||||||||||||||||
| 14 Management.AutoRAG.Http | ||||||||||||||||||||||||||||||||||||||||
| 15 Management.AutoRAG.Types | ||||||||||||||||||||||||||||||||||||||||
| 16 Management.BrowserRendering | ||||||||||||||||||||||||||||||||||||||||
| 17 Management.BrowserRendering.Http | ||||||||||||||||||||||||||||||||||||||||
| 18 Queues | ||||||||||||||||||||||||||||||||||||||||
| 19 Worker.Context | ||||||||||||||||||||||||||||||||||||||||
| 20 D1.Helpers | 3 | |||||||||||||||||||||||||||||||||||||||
| 21 DurableObjects | 6 | |||||||||||||||||||||||||||||||||||||||
| 22 Hyperdrive.Helpers | 7 | |||||||||||||||||||||||||||||||||||||||
| 23 Hyperdrive.Helpers.DatabaseAdapters | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 KV.Helpers | 3 | |||||||||||||||||||||||||||||||||||||||
| 25 Management.AI | 226 | |||||||||||||||||||||||||||||||||||||||
| 26 Management.AI.Http.OpenApiHttp | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 Management.AIGateway | 48 | |||||||||||||||||||||||||||||||||||||||
| 28 Management.AIGateway.Http.OpenApiHttp | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 Management.AISearch | 26 | |||||||||||||||||||||||||||||||||||||||
| 30 Management.AISearch.Http.OpenApiHttp | 2 | |||||||||||||||||||||||||||||||||||||||
| 31 Management.Access | 112 | |||||||||||||||||||||||||||||||||||||||
| 32 Management.Access.Http.OpenApiHttp | 2 | |||||||||||||||||||||||||||||||||||||||
| 33 Management.Analytics | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 Management.Analytics.Http.OpenApiHttp | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 Management.AutoRAG | 9 | |||||||||||||||||||||||||||||||||||||||
| 36 Management.AutoRAG.Http.OpenApiHttp | 2 | |||||||||||||||||||||||||||||||||||||||
| 37 Management.BrowserRendering.Http.OpenApiHttp | 2 | |||||||||||||||||||||||||||||||||||||||
| 38 DurableObjects.Helpers | 5 | 13 | ||||||||||||||||||||||||||||||||||||||
| 39 DurableObjects.Helpers.Storage | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 DurableObjects.Helpers.WebSocket | 2 |
20→1 D1.Helpers uses D1✕
- Connections
- 3 pairs of types, where a type in D1.Helpers uses a type in D1.
- The types involved
Fidelity.CloudEdge.D1.Helpers.Helpers→Fidelity.CloudEdge.D1.D1DatabaseFidelity.CloudEdge.D1.Helpers.Helpers→Fidelity.CloudEdge.D1.D1ExecResultFidelity.CloudEdge.D1.Helpers.Helpers→Fidelity.CloudEdge.D1.D1Result`1
- Direction
- D1.Helpers uses D1, so a change to D1 can break D1.Helpers, while a change to D1.Helpers can't break D1.
- Position
- Below the diagonal: D1.Helpers uses a module listed above it, which is the healthy direction.
21→19 DurableObjects uses Worker.Context✕
- Connections
- 6 pairs of types, where a type in DurableObjects uses a type in Worker.Context.
- The types involved
Fidelity.CloudEdge.DurableObjects.DurableObject→Fidelity.CloudEdge.Worker.Context.RequestFidelity.CloudEdge.DurableObjects.DurableObject→Fidelity.CloudEdge.Worker.Context.ResponseFidelity.CloudEdge.DurableObjects.DurableObjectStub→Fidelity.CloudEdge.Worker.Context.RequestFidelity.CloudEdge.DurableObjects.DurableObjectStub→Fidelity.CloudEdge.Worker.Context.ResponseFidelity.CloudEdge.DurableObjects.ServiceBinding→Fidelity.CloudEdge.Worker.Context.RequestFidelity.CloudEdge.DurableObjects.ServiceBinding→Fidelity.CloudEdge.Worker.Context.Response
- Direction
- DurableObjects uses Worker.Context, so a change to Worker.Context can break DurableObjects, while a change to DurableObjects can't break Worker.Context.
- Position
- Below the diagonal: DurableObjects uses a module listed above it, which is the healthy direction.
22→2 Hyperdrive.Helpers uses Hyperdrive✕
- Connections
- 7 pairs of types, where a type in Hyperdrive.Helpers uses a type in Hyperdrive.
- The types involved
Fidelity.CloudEdge.Hyperdrive.Helpers.Helpers→Fidelity.CloudEdge.Hyperdrive.ConnectionPoolSettingsFidelity.CloudEdge.Hyperdrive.Helpers.Helpers→Fidelity.CloudEdge.Hyperdrive.HyperdriveFidelity.CloudEdge.Hyperdrive.Helpers.Helpers→Fidelity.CloudEdge.Hyperdrive.HyperdriveCachingFidelity.CloudEdge.Hyperdrive.Helpers.Helpers→Fidelity.CloudEdge.Hyperdrive.HyperdriveConfigFidelity.CloudEdge.Hyperdrive.Helpers.Helpers→Fidelity.CloudEdge.Hyperdrive.SocketFidelity.CloudEdge.Hyperdrive.Helpers.HyperdriveBuilder→Fidelity.CloudEdge.Hyperdrive.HyperdriveFidelity.CloudEdge.Hyperdrive.Helpers.HyperdriveBuilder→Fidelity.CloudEdge.Hyperdrive.Socket
- Direction
- Hyperdrive.Helpers uses Hyperdrive, so a change to Hyperdrive can break Hyperdrive.Helpers, while a change to Hyperdrive.Helpers can't break Hyperdrive.
- Position
- Below the diagonal: Hyperdrive.Helpers uses a module listed above it, which is the healthy direction.
23→2 Hyperdrive.Helpers.DatabaseAdapters uses Hyperdrive✕
- Connections
- 1 pair of types, where a type in Hyperdrive.Helpers.DatabaseAdapters uses a type in Hyperdrive.
- The types involved
Fidelity.CloudEdge.Hyperdrive.Helpers.DatabaseAdapters.DatabaseAdapters→Fidelity.CloudEdge.Hyperdrive.Hyperdrive
- Direction
- Hyperdrive.Helpers.DatabaseAdapters uses Hyperdrive, so a change to Hyperdrive can break Hyperdrive.Helpers.DatabaseAdapters, while a change to Hyperdrive.Helpers.DatabaseAdapters can't break Hyperdrive.
- Position
- Below the diagonal: Hyperdrive.Helpers.DatabaseAdapters uses a module listed above it, which is the healthy direction.
24→3 KV.Helpers uses KV✕
- Connections
- 3 pairs of types, where a type in KV.Helpers uses a type in KV.
- The types involved
Fidelity.CloudEdge.KV.Helpers.Helpers→Fidelity.CloudEdge.KV.KVKeyFidelity.CloudEdge.KV.Helpers.Helpers→Fidelity.CloudEdge.KV.KVListResultFidelity.CloudEdge.KV.Helpers.Helpers→Fidelity.CloudEdge.KV.KVNamespace
- Direction
- KV.Helpers uses KV, so a change to KV can break KV.Helpers, while a change to KV.Helpers can't break KV.
- Position
- Below the diagonal: KV.Helpers uses a module listed above it, which is the healthy direction.
25→5 Management.AI uses Management.AI.Types✕
- Connections
- 226 pairs of types, where a type in Management.AI uses a type in Management.AI.Types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Fidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchCreateInstancesFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchCreateInstancesPayloadFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchCreateTokensFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchCreateTokensPayloadFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchDeleteInstancesFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchDeleteTokensFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchFetchInstancesFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchFetchTokensFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchInstanceChangeJobStatusFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchInstanceChangeJobStatusPayloadFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchInstanceChatCompletionFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchInstanceChatCompletionPayloadFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchInstanceCreateJobFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchInstanceCreateJobPayloadFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchInstanceGetJobFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchInstanceListJobLogsFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchInstanceListJobsFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchInstanceSearchFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchInstanceSearchPayloadFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchListInstancesFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchListTokensFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchStatsFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchUpdateInstancesFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchUpdateInstancesPayloadFidelity.CloudEdge.Management.AI.AIClient→Fidelity.CloudEdge.Management.AI.Types.AiSearchUpdateTokens
- Direction
- Management.AI uses Management.AI.Types, so a change to Management.AI.Types can break Management.AI, while a change to Management.AI can't break Management.AI.Types.
- Position
- Below the diagonal: Management.AI uses a module listed above it, which is the healthy direction.
26→4 Management.AI.Http.OpenApiHttp uses Management.AI.Http✕
- Connections
- 2 pairs of types, where a type in Management.AI.Http.OpenApiHttp uses a type in Management.AI.Http.
- The types involved
Fidelity.CloudEdge.Management.AI.Http.OpenApiHttp.OpenApiHttp→Fidelity.CloudEdge.Management.AI.Http.OpenApiValueFidelity.CloudEdge.Management.AI.Http.OpenApiHttp.OpenApiHttp→Fidelity.CloudEdge.Management.AI.Http.RequestPart
- Direction
- Management.AI.Http.OpenApiHttp uses Management.AI.Http, so a change to Management.AI.Http can break Management.AI.Http.OpenApiHttp, while a change to Management.AI.Http.OpenApiHttp can't break Management.AI.Http.
- Position
- Below the diagonal: Management.AI.Http.OpenApiHttp uses a module listed above it, which is the healthy direction.
27→7 Management.AIGateway uses Management.AIGateway.Types✕
- Connections
- 48 pairs of types, where a type in Management.AIGateway uses a type in Management.AIGateway.Types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Fidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigCreateDatasetFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigCreateDatasetPayloadFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigCreateEvaluationsFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigCreateEvaluationsPayloadFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigCreateGatewayFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigCreateGatewayPayloadFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigCreateProvidersFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigCreateProvidersPayloadFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigDeleteDatasetFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigDeleteEvaluationsFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigDeleteGatewayFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigDeleteGatewayDynamicRouteFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigDeleteGatewayLogsFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigDeleteProvidersFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigFetchDatasetFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigFetchEvaluationsFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigFetchGatewayFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigGetGatewayDynamicRouteFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigGetGatewayDynamicRouteVersionFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigGetGatewayLogDetailFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigGetGatewayLogRequestFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigGetGatewayLogResponseFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigGetGatewayUrlFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigListDatasetFidelity.CloudEdge.Management.AIGateway.AIGatewayClient→Fidelity.CloudEdge.Management.AIGateway.Types.AigConfigListEvaluations
- Direction
- Management.AIGateway uses Management.AIGateway.Types, so a change to Management.AIGateway.Types can break Management.AIGateway, while a change to Management.AIGateway can't break Management.AIGateway.Types.
- Position
- Below the diagonal: Management.AIGateway uses a module listed above it, which is the healthy direction.
28→6 Management.AIGateway.Http.OpenApiHttp uses Management.AIGateway.Http✕
- Connections
- 2 pairs of types, where a type in Management.AIGateway.Http.OpenApiHttp uses a type in Management.AIGateway.Http.
- The types involved
Fidelity.CloudEdge.Management.AIGateway.Http.OpenApiHttp.OpenApiHttp→Fidelity.CloudEdge.Management.AIGateway.Http.OpenApiValueFidelity.CloudEdge.Management.AIGateway.Http.OpenApiHttp.OpenApiHttp→Fidelity.CloudEdge.Management.AIGateway.Http.RequestPart
- Direction
- Management.AIGateway.Http.OpenApiHttp uses Management.AIGateway.Http, so a change to Management.AIGateway.Http can break Management.AIGateway.Http.OpenApiHttp, while a change to Management.AIGateway.Http.OpenApiHttp can't break Management.AIGateway.Http.
- Position
- Below the diagonal: Management.AIGateway.Http.OpenApiHttp uses a module listed above it, which is the healthy direction.
29→9 Management.AISearch uses Management.AISearch.Types✕
- Connections
- 26 pairs of types, where a type in Management.AISearch uses a type in Management.AISearch.Types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Fidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchCreateInstancesFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchCreateInstancesPayloadFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchCreateTokensFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchCreateTokensPayloadFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchDeleteInstancesFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchDeleteTokensFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchFetchInstancesFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchFetchTokensFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchInstanceChangeJobStatusFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchInstanceChangeJobStatusPayloadFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchInstanceChatCompletionFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchInstanceChatCompletionPayloadFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchInstanceCreateJobFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchInstanceCreateJobPayloadFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchInstanceGetJobFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchInstanceListJobLogsFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchInstanceListJobsFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchInstanceSearchFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchInstanceSearchPayloadFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchListInstancesFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchListTokensFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchStatsFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchUpdateInstancesFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchUpdateInstancesPayloadFidelity.CloudEdge.Management.AISearch.AISearchClient→Fidelity.CloudEdge.Management.AISearch.Types.AiSearchUpdateTokens
- Direction
- Management.AISearch uses Management.AISearch.Types, so a change to Management.AISearch.Types can break Management.AISearch, while a change to Management.AISearch can't break Management.AISearch.Types.
- Position
- Below the diagonal: Management.AISearch uses a module listed above it, which is the healthy direction.
30→8 Management.AISearch.Http.OpenApiHttp uses Management.AISearch.Http✕
- Connections
- 2 pairs of types, where a type in Management.AISearch.Http.OpenApiHttp uses a type in Management.AISearch.Http.
- The types involved
Fidelity.CloudEdge.Management.AISearch.Http.OpenApiHttp.OpenApiHttp→Fidelity.CloudEdge.Management.AISearch.Http.OpenApiValueFidelity.CloudEdge.Management.AISearch.Http.OpenApiHttp.OpenApiHttp→Fidelity.CloudEdge.Management.AISearch.Http.RequestPart
- Direction
- Management.AISearch.Http.OpenApiHttp uses Management.AISearch.Http, so a change to Management.AISearch.Http can break Management.AISearch.Http.OpenApiHttp, while a change to Management.AISearch.Http.OpenApiHttp can't break Management.AISearch.Http.
- Position
- Below the diagonal: Management.AISearch.Http.OpenApiHttp uses a module listed above it, which is the healthy direction.
31→11 Management.Access uses Management.Access.Types✕
- Connections
- 112 pairs of types, where a type in Management.Access uses a type in Management.Access.Types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Fidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessApplicationsAddAnApplicationFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessApplicationsDeleteAnAccessApplicationFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessApplicationsGetAnAccessApplicationFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessApplicationsListAccessApplicationsFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessApplicationsPatchUpdateAccessApplicationSettingsFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessApplicationsPutUpdateAccessApplicationSettingsFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessApplicationsRevokeServiceTokensFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessApplicationsTestAccessPoliciesFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessApplicationsUpdateAnAccessApplicationFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessAuthenticationLogsGetAccessAuthenticationLogsFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessCustomPagesCreateACustomPageFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessCustomPagesDeleteACustomPageFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessCustomPagesGetACustomPageFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessCustomPagesListCustomPagesFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessCustomPagesUpdateACustomPageFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessGatewayCaAddAnSSHCaFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessGatewayCaDeleteAnSSHCaFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessGatewayCaListSSHCaFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessGroupsCreateAnAccessGroupFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessGroupsDeleteAnAccessGroupFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessGroupsGetAnAccessGroupFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessGroupsListAccessGroupsFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessGroupsUpdateAnAccessGroupFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessIdentityProvidersAddAnAccessIdentityProviderFidelity.CloudEdge.Management.Access.AccessClient→Fidelity.CloudEdge.Management.Access.Types.AccessIdentityProvidersDeleteAnAccessIdentityProvider
- Direction
- Management.Access uses Management.Access.Types, so a change to Management.Access.Types can break Management.Access, while a change to Management.Access can't break Management.Access.Types.
- Position
- Below the diagonal: Management.Access uses a module listed above it, which is the healthy direction.
32→10 Management.Access.Http.OpenApiHttp uses Management.Access.Http✕
- Connections
- 2 pairs of types, where a type in Management.Access.Http.OpenApiHttp uses a type in Management.Access.Http.
- The types involved
Fidelity.CloudEdge.Management.Access.Http.OpenApiHttp.OpenApiHttp→Fidelity.CloudEdge.Management.Access.Http.OpenApiValueFidelity.CloudEdge.Management.Access.Http.OpenApiHttp.OpenApiHttp→Fidelity.CloudEdge.Management.Access.Http.RequestPart
- Direction
- Management.Access.Http.OpenApiHttp uses Management.Access.Http, so a change to Management.Access.Http can break Management.Access.Http.OpenApiHttp, while a change to Management.Access.Http.OpenApiHttp can't break Management.Access.Http.
- Position
- Below the diagonal: Management.Access.Http.OpenApiHttp uses a module listed above it, which is the healthy direction.
33→13 Management.Analytics uses Management.Analytics.Types✕
- Connections
- 1 pair of types, where a type in Management.Analytics uses a type in Management.Analytics.Types.
- The types involved
Fidelity.CloudEdge.Management.Analytics.AnalyticsClient→Fidelity.CloudEdge.Management.Analytics.Types.ArgoAnalyticsForZoneArgoAnalyticsForAZone
- Direction
- Management.Analytics uses Management.Analytics.Types, so a change to Management.Analytics.Types can break Management.Analytics, while a change to Management.Analytics can't break Management.Analytics.Types.
- Position
- Below the diagonal: Management.Analytics uses a module listed above it, which is the healthy direction.
34→12 Management.Analytics.Http.OpenApiHttp uses Management.Analytics.Http✕
- Connections
- 2 pairs of types, where a type in Management.Analytics.Http.OpenApiHttp uses a type in Management.Analytics.Http.
- The types involved
Fidelity.CloudEdge.Management.Analytics.Http.OpenApiHttp.OpenApiHttp→Fidelity.CloudEdge.Management.Analytics.Http.OpenApiValueFidelity.CloudEdge.Management.Analytics.Http.OpenApiHttp.OpenApiHttp→Fidelity.CloudEdge.Management.Analytics.Http.RequestPart
- Direction
- Management.Analytics.Http.OpenApiHttp uses Management.Analytics.Http, so a change to Management.Analytics.Http can break Management.Analytics.Http.OpenApiHttp, while a change to Management.Analytics.Http.OpenApiHttp can't break Management.Analytics.Http.
- Position
- Below the diagonal: Management.Analytics.Http.OpenApiHttp uses a module listed above it, which is the healthy direction.
35→15 Management.AutoRAG uses Management.AutoRAG.Types✕
- Connections
- 9 pairs of types, where a type in Management.AutoRAG uses a type in Management.AutoRAG.Types.
- The types involved
Fidelity.CloudEdge.Management.AutoRAG.AutoRAGClient→Fidelity.CloudEdge.Management.AutoRAG.Types.AutoragConfigAiSearchFidelity.CloudEdge.Management.AutoRAG.AutoRAGClient→Fidelity.CloudEdge.Management.AutoRAG.Types.AutoragConfigAiSearchPayloadFidelity.CloudEdge.Management.AutoRAG.AutoRAGClient→Fidelity.CloudEdge.Management.AutoRAG.Types.AutoragConfigFilesFidelity.CloudEdge.Management.AutoRAG.AutoRAGClient→Fidelity.CloudEdge.Management.AutoRAG.Types.AutoragConfigGetJobFidelity.CloudEdge.Management.AutoRAG.AutoRAGClient→Fidelity.CloudEdge.Management.AutoRAG.Types.AutoragConfigListJobLogsFidelity.CloudEdge.Management.AutoRAG.AutoRAGClient→Fidelity.CloudEdge.Management.AutoRAG.Types.AutoragConfigListJobsFidelity.CloudEdge.Management.AutoRAG.AutoRAGClient→Fidelity.CloudEdge.Management.AutoRAG.Types.AutoragConfigSearchFidelity.CloudEdge.Management.AutoRAG.AutoRAGClient→Fidelity.CloudEdge.Management.AutoRAG.Types.AutoragConfigSearchPayloadFidelity.CloudEdge.Management.AutoRAG.AutoRAGClient→Fidelity.CloudEdge.Management.AutoRAG.Types.AutoragConfigSync
- Direction
- Management.AutoRAG uses Management.AutoRAG.Types, so a change to Management.AutoRAG.Types can break Management.AutoRAG, while a change to Management.AutoRAG can't break Management.AutoRAG.Types.
- Position
- Below the diagonal: Management.AutoRAG uses a module listed above it, which is the healthy direction.
36→14 Management.AutoRAG.Http.OpenApiHttp uses Management.AutoRAG.Http✕
- Connections
- 2 pairs of types, where a type in Management.AutoRAG.Http.OpenApiHttp uses a type in Management.AutoRAG.Http.
- The types involved
Fidelity.CloudEdge.Management.AutoRAG.Http.OpenApiHttp.OpenApiHttp→Fidelity.CloudEdge.Management.AutoRAG.Http.OpenApiValueFidelity.CloudEdge.Management.AutoRAG.Http.OpenApiHttp.OpenApiHttp→Fidelity.CloudEdge.Management.AutoRAG.Http.RequestPart
- Direction
- Management.AutoRAG.Http.OpenApiHttp uses Management.AutoRAG.Http, so a change to Management.AutoRAG.Http can break Management.AutoRAG.Http.OpenApiHttp, while a change to Management.AutoRAG.Http.OpenApiHttp can't break Management.AutoRAG.Http.
- Position
- Below the diagonal: Management.AutoRAG.Http.OpenApiHttp uses a module listed above it, which is the healthy direction.
37→17 Management.BrowserRendering.Http.OpenApiHttp uses Management.BrowserRendering.Http✕
- Connections
- 2 pairs of types, where a type in Management.BrowserRendering.Http.OpenApiHttp uses a type in Management.BrowserRendering.Http.
- The types involved
Fidelity.CloudEdge.Management.BrowserRendering.Http.OpenApiHttp.OpenApiHttp→Fidelity.CloudEdge.Management.BrowserRendering.Http.OpenApiValueFidelity.CloudEdge.Management.BrowserRendering.Http.OpenApiHttp.OpenApiHttp→Fidelity.CloudEdge.Management.BrowserRendering.Http.RequestPart
- Direction
- Management.BrowserRendering.Http.OpenApiHttp uses Management.BrowserRendering.Http, so a change to Management.BrowserRendering.Http can break Management.BrowserRendering.Http.OpenApiHttp, while a change to Management.BrowserRendering.Http.OpenApiHttp can't break Management.BrowserRendering.Http.
- Position
- Below the diagonal: Management.BrowserRendering.Http.OpenApiHttp uses a module listed above it, which is the healthy direction.
38→19 DurableObjects.Helpers uses Worker.Context✕
- Connections
- 5 pairs of types, where a type in DurableObjects.Helpers uses a type in Worker.Context.
- The types involved
Fidelity.CloudEdge.DurableObjects.Helpers.CounterDurableObject→Fidelity.CloudEdge.Worker.Context.RequestFidelity.CloudEdge.DurableObjects.Helpers.CounterDurableObject→Fidelity.CloudEdge.Worker.Context.ResponseFidelity.CloudEdge.DurableObjects.Helpers.Helpers→Fidelity.CloudEdge.Worker.Context.RequestFidelity.CloudEdge.DurableObjects.Helpers.NamespaceBuilder→Fidelity.CloudEdge.Worker.Context.RequestFidelity.CloudEdge.DurableObjects.Helpers.NamespaceBuilder→Fidelity.CloudEdge.Worker.Context.Response
- Direction
- DurableObjects.Helpers uses Worker.Context, so a change to Worker.Context can break DurableObjects.Helpers, while a change to DurableObjects.Helpers can't break Worker.Context.
- Position
- Below the diagonal: DurableObjects.Helpers uses a module listed above it, which is the healthy direction.
38→21 DurableObjects.Helpers uses DurableObjects✕
- Connections
- 13 pairs of types, where a type in DurableObjects.Helpers uses a type in DurableObjects.
- The types involved
Fidelity.CloudEdge.DurableObjects.Helpers.CounterDurableObject→Fidelity.CloudEdge.DurableObjects.DurableObjectFidelity.CloudEdge.DurableObjects.Helpers.CounterDurableObject→Fidelity.CloudEdge.DurableObjects.DurableObjectState`1Fidelity.CloudEdge.DurableObjects.Helpers.CounterDurableObject→Fidelity.CloudEdge.DurableObjects.WebSocketFidelity.CloudEdge.DurableObjects.Helpers.DurableObjectBuilder→Fidelity.CloudEdge.DurableObjects.DurableObjectState`1Fidelity.CloudEdge.DurableObjects.Helpers.DurableObjectBuilder→Fidelity.CloudEdge.DurableObjects.DurableObjectStorageFidelity.CloudEdge.DurableObjects.Helpers.Helpers→Fidelity.CloudEdge.DurableObjects.DurableObjectGetOptionsFidelity.CloudEdge.DurableObjects.Helpers.Helpers→Fidelity.CloudEdge.DurableObjects.DurableObjectListOptionsFidelity.CloudEdge.DurableObjects.Helpers.Helpers→Fidelity.CloudEdge.DurableObjects.DurableObjectNamespaceFidelity.CloudEdge.DurableObjects.Helpers.Helpers→Fidelity.CloudEdge.DurableObjects.DurableObjectPutOptionsFidelity.CloudEdge.DurableObjects.Helpers.Helpers→Fidelity.CloudEdge.DurableObjects.DurableObjectState`1Fidelity.CloudEdge.DurableObjects.Helpers.NamespaceBuilder→Fidelity.CloudEdge.DurableObjects.DurableObjectIdFidelity.CloudEdge.DurableObjects.Helpers.NamespaceBuilder→Fidelity.CloudEdge.DurableObjects.DurableObjectNamespaceFidelity.CloudEdge.DurableObjects.Helpers.NamespaceBuilder→Fidelity.CloudEdge.DurableObjects.DurableObjectStub
- Direction
- DurableObjects.Helpers uses DurableObjects, so a change to DurableObjects can break DurableObjects.Helpers, while a change to DurableObjects.Helpers can't break DurableObjects.
- Position
- Below the diagonal: DurableObjects.Helpers uses a module listed above it, which is the healthy direction.
39→21 DurableObjects.Helpers.Storage uses DurableObjects✕
- Connections
- 1 pair of types, where a type in DurableObjects.Helpers.Storage uses a type in DurableObjects.
- The types involved
Fidelity.CloudEdge.DurableObjects.Helpers.Storage.Storage→Fidelity.CloudEdge.DurableObjects.DurableObjectStorage
- Direction
- DurableObjects.Helpers.Storage uses DurableObjects, so a change to DurableObjects can break DurableObjects.Helpers.Storage, while a change to DurableObjects.Helpers.Storage can't break DurableObjects.
- Position
- Below the diagonal: DurableObjects.Helpers.Storage uses a module listed above it, which is the healthy direction.
40→21 DurableObjects.Helpers.WebSocket uses DurableObjects✕
- Connections
- 2 pairs of types, where a type in DurableObjects.Helpers.WebSocket uses a type in DurableObjects.
- The types involved
Fidelity.CloudEdge.DurableObjects.Helpers.WebSocket.WebSocket→Fidelity.CloudEdge.DurableObjects.DurableObjectState`1Fidelity.CloudEdge.DurableObjects.Helpers.WebSocket.WebSocket→Fidelity.CloudEdge.DurableObjects.WebSocket
- Direction
- DurableObjects.Helpers.WebSocket uses DurableObjects, so a change to DurableObjects can break DurableObjects.Helpers.WebSocket, while a change to DurableObjects.Helpers.WebSocket can't break DurableObjects.
- Position
- Below the diagonal: DurableObjects.Helpers.WebSocket 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 14 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 11 | High / Critical |
| A07:2025 — Authentication Failures | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED; 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 <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. | +4.3 pts | Low | Secret Scanning |
| Resolve the 1 ADR has no Decision section finding(s) in ADR Quality — start with 00_architecture_decisions.md. | +2.6 pts | Low | ADR Quality |
| 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. | +4.2 pts | Medium | Security & performance tooling |
| Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`. | +3.7 pts | Medium | Nullable reference types |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.8 pts | Medium | Release Hygiene |
| Resolve the 197 Orphaned file finding(s) in Knowledge Freshness — start with OpenApiHttp.fs (84), Client.fs (82), Types.fs (26). | +2.6 pts | High | Knowledge Freshness |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +1.1 pts | Medium | Deployment & Rollback |
| Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with Client.fs (2), REDACTED. | +0.2 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Near-clean | Dependency Vulnerabilities: High CVE: REDACTED |
| docs/00_architecture_decisions.md | 9.5 | Near-clean | ADR Quality: ADR has no Decision section |
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 35 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 35 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, 232 of 253 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D1 Cyclomatic Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.fs) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.fs) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D3 God Classes — 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. God Classes couldn't be assessed within its 5-minute budget on a solution this large — not included in this run.
- D4 Code Duplication — 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. Code Duplication couldn't be assessed within its 13-minute budget on a solution this large — not included in this run.
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the test suite could not be built/run in-image (commonly external-service dependencies — a database, a broker — we won't provision). To have it measured, make the suite runnable without them. For context only, test code is ≈ 1% of production LoC (2,772 test / 248,263 production) — a rough proxy, NOT a coverage measurement, so it is excluded from the score. You can widen what we reach: optional: make the suite runnable without a database, broker or other service we do not provision, and real coverage is measured on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares npm dependencies as well as NuGet ones — manifests: package.json, samples/AskAI/Worker/package.json, samples/HelloWorker/package.json, samples/R2WebDAV/package.json, samples/SecureChat.UI/package.json, and others — and the counts on this row cover the NuGet side ONLY. This dimension reads dependency currency from `<PackageReference>` elements via `dotnet list package`; it does not read them, so the npm packages declared there were not checked for newer, deprecated or unmaintained releases. Their absence from the counts above is a gap in this analyzer's ecosystem coverage — not a finding that those dependencies are current.
- 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.
- D15 Churn × Complexity Hotspots — 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. A hotspot is churn × complexity. Churn was measured (137885 line(s) across the 90-day window), but no complexity could be computed for .fs, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 100 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 1 hold 4% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — 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 C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'src/Core/CloudEdge.Core/CloudEdge.Core.fsproj' because the file extension '.fsproj' is not associated with a language.
- D17 Explicit Debt — 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 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (248,263 lines, 100% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D20 ADR 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. ADR Quality ran out of its 5-minute budget before it had finished, so what it reports here is a floor rather than a complete count. The rows above are real and stand; what is not known is how many more there are. This is a limit of the analysis run, not a finding about this repository.
- D21 Naming Consistency — evaluation did not complete — Naming Consistency not included (check did not complete) — excluded from the score.
- 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. The loaded project set declares no packable project and no `.Contracts` project, so 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. 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.
- D26 Project Cohesion — 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. `CloudEdge.R2.fable-temp` (96 LoC, 7847 public types across 269 namespaces) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- 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 DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (the repository): package.json has no "dev" script, so `npm run dev` could not start the app. Last output: "npm error Missing script: "dev" / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- 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.
- 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.
- P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- 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.
- Production source was not modelled — run is Degraded — No code model read .fs, so the complexity, duplication and architecture dimensions were scored over a minority of this repository rather than its product, and dimensions that abstained did so for want of a model rather than for want of findings. The grade is NOT representative of this repository; diagnostics.md records the exact cause.
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
- 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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 47 classes have LCOM4 above 3.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Cycles found: 0.
D12 · Dependency Hygiene
9 outdated, 0 vulnerable, 0 deprecated packages. NuGet only — this repository also declares npm dependencies, which are not read for currency here.
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D14 · License Compliance
0 of 270 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 15 direct `PackageReference`(s), and 105 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.
D17 · Explicit Debt
0 deducted debt markers + unmeasured dead symbols across 96 LoC in the .NET projects (0.0/KLoC) → score 10.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (100% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 22 document(s) read across 2 unit(s).
D20 · ADR Quality
1 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What to do
- Resolve the 1 ADR has no Decision section finding(s) in ADR Quality — start with 00_architecture_decisions.md. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
97 % of calls cross a namespace and 1 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
14 finding(s): 0 critical, 13 high, 1 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `generators/scripts/lib.sh` (line 162) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 10 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 (10 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
200 of 200 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 200 of the 358 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 197 Orphaned file finding(s) in Knowledge Freshness — start with OpenApiHttp.fs (84), Client.fs (82), Types.fs (26). — One of this dimension's main actionable groups (197 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with Client.fs (2), REDACTED. — 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 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 104 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- A placeholder string ("REPLACE_ME_WITH_MODULE_NAME") is still in shipped code — typical of generated boilerplate that was never filled in. (×3) — generators/glutinum/temp-ai-generated.fs:10, generators/glutinum/temp-ai-generated.fs:12, generators/glutinum/temp-ai-generated.fs:14
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
M1 · Documentation (README)
M2 · Architecture documentation
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
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 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `generators/hawaii/Generated-AI/Fidelity.CloudEdge.Management.AI.fsproj` 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`. — generators/hawaii/Generated-AI/Fidelity.CloudEdge.Management.AI.fsproj:13
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
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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
X5 · Nullable reference types
- 0/1 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 54% | Checked 2 of 6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 65% | Adequate — gated by AX10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 59% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 51% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 71% | Checked 5 of 11 | 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 — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 77 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — no public interfaces
- 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 — the dev server (`npm run dev`) exited before it served a page. Likely cause (the repository): package.json has no "dev" script, so `npm run dev` could not start the app. Last output: "npm error Missing script: "dev" / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. 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.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .fs exposed no member bodies
- D10 Test Quality — ~2772 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D15 Churn × Complexity Hotspots — complexity unreadable for .fs — churn × complexity hotspots could not be measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D2 Cognitive Complexity — cognitive complexity not measured — .fs exposed no member bodies
- D21 Naming Consistency — Naming Consistency not included (check did not complete)
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .fs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D26 Project Cohesion — D26 could not read how the parts of this repository's one project reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D3 God Classes — God Classes not included (time budget)
- 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.
- D4 Code Duplication — Code Duplication not included (time budget)
- 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.
- D8 Code Coverage — Coverage not measured
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 10369 value object(s); 247 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — reported, not scored — this repository's C# declares no analysable method bodies (a constants, record or DTO assembly), and this score is a density of unfinished work per method, which has no denominator here. The file-level signals below were still collected and are shown in full
- 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'.
- P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- 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.
- 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no async method does work a token could cancel
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 15 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 14 finding(s)
- JavaScript dependencies are not locked package.json:20
- JavaScript dependencies are not locked samples/AskAI/Worker/package.json:10
- JavaScript dependencies are not locked samples/HelloWorker/package.json:11
- JavaScript dependencies are not locked samples/R2WebDAV/package.json:10
- JavaScript dependencies are not locked samples/SecureChat.UI/package.json:13
- JavaScript dependencies are not locked samples/SecureChat/package.json:12
- JavaScript dependencies are not locked tests/CloudEdge.Tests/package.json:13
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NuGet dependencies are not locked
Minor — 215 finding(s)
- Orphaned file src/Management/CloudEdge.Management.Magic/Client.fs:1
- Orphaned file generators/hawaii/Generated-Magic/Client.fs:1
- Orphaned file generators/hawaii/Generated-AISearch/Types.fs:1
- Orphaned file src/Management/CloudEdge.Management.AISearch/Types.fs:1
- Orphaned file src/Management/CloudEdge.Management.Access/Client.fs:1
- Orphaned file generators/hawaii/Generated-Access/Client.fs:1
- Orphaned file generators/hawaii/Generated-AIGateway/Types.fs:1
- Orphaned file src/Management/CloudEdge.Management.AIGateway/Types.fs:1
- Orphaned file src/Management/CloudEdge.Management.Email/Client.fs:1
- Orphaned file generators/hawaii/Generated-Email/Client.fs:1
- Orphaned file src/Management/CloudEdge.Management.Stream/Client.fs:1
- Orphaned file generators/hawaii/Generated-Stream/Client.fs:1
- Orphaned file src/Management/CloudEdge.Management.Gateway/Client.fs:1
- Orphaned file generators/hawaii/Generated-Gateway/Client.fs:1
- Orphaned file generators/hawaii/Generated-Builds/Types.fs:1
- Orphaned file src/Management/CloudEdge.Management.Builds/Types.fs:1
- Orphaned file src/Management/CloudEdge.Management.AIGateway/Client.fs:1
- Orphaned file generators/hawaii/Generated-AIGateway/Client.fs:1
- Orphaned file generators/hawaii/Generated-Workflows/Types.fs:1
- Orphaned file src/Management/CloudEdge.Management.Workflows/Types.fs:1
- Orphaned file src/Management/CloudEdge.Management.LoadBalancers/Client.fs:1
- Orphaned file generators/hawaii/Generated-LoadBalancers/Client.fs:1
- Orphaned file generators/hawaii/Generated-Calls/Types.fs:1
- Orphaned file src/Management/CloudEdge.Management.Calls/Types.fs:1
- Orphaned file src/Management/CloudEdge.Management.VulnScanner/Client.fs:1
- Most significant orphaned file REDACTED:1
- Most significant orphaned file generators/hawaii/Generated-AI/Client.fs:1
- Most significant orphaned file src/Management/CloudEdge.Management.AI/Client.fs:1
- Placeholder literal left in code generators/glutinum/temp-ai-generated.fs:10
- Placeholder literal left in code generators/glutinum/temp-ai-generated.fs:12
- Placeholder literal left in code generators/glutinum/temp-ai-generated.fs:14
- ADR has no Decision section docs/00_architecture_decisions.md:1
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No SAST REDACTED:6
- No dependency-update automation generators/hawaii/Generated-AI/Fidelity.CloudEdge.Management.AI.fsproj:13
- No release approval gate
- No changelog
- Nullable reference types not enabled everywhere
Minor — 9 finding(s)
- Outdated: Fable.Core
- Outdated: FSharp.Core
- Outdated: Fable.Promise
- Outdated: FSharp.SystemTextJson
- Outdated: Expecto
- Outdated: Expecto.FsCheck
- Outdated: Fable.Remoting.Json
- Outdated: FsCheck
- Outdated: Newtonsoft.Json
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-20a57770d2b740ab896759d90a7e909d/history.json --exit-code 0 --source . | 10 | 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-20a57770d2b740ab896759d90a7e909d/tree.json --exit-code 0 --source . | 9 | 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 . | 14 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Fidelity.CloudEdge.sln package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | 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/** . | 0 | artifacts/raw/trivy-fs.json |