Executive summary
microsoft/metered-billing-accelerator is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because we found no logging, tracing or health checks in the code. It scores 59 out of 100, which the At risk rating leaves unchanged. We judged it as a template or a sample, against a lower bar.
Production Readiness, at 50, is the weakest lens and counts most in the score. The best first steps are fixing the password or key in the code and logging through a logging library, each worth about 8 points. Raising Production Readiness to 52 would lift the score to about 60.
Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Six settings leave the servers or containers unsafe, and one password or key in the code and one in the code's history are open to anyone who can read the repository. Replacing each exposed password or key, pinning each tool to an exact version and correcting the unsafe settings would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed. The data field that is written but never read needs removing.
The product code is 7,857 lines, about €16,000 to rebuild.
If Production Readiness rose from 50 to 52, the lowest score rated Strong, the score would rise from 59 to about 60.
New since the last survey: 11 findings
- Code Duplication · Edited copy of a member (31 corresponding lines) src/Metering.EventHub/EventHubObservableClient.cs
- Code Duplication · Edited copy of a member (27 corresponding lines) src/Demos/SaaSIntegration/src/LandingPage/Controllers/HomeController.cs
- Code Duplication · Edited copy of a member (21 corresponding lines) src/Demos/SaaSIntegration/src/MeteredPage/Controllers/HomeController.cs
- Code Duplication · Edited copy of a member (9 corresponding lines) REDACTED
- Code Duplication · Edited copies of one member (3 members, 27+ corresponding lines) src/Demos/SaaSIntegration/src/LandingPage/Startup.cs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net7.0 src/Demos/Metering.BusinessLogicDemoApp/Metering.BusinessLogicDemoApp.fsproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 src/Demos/SaaSIntegration/src/PublisherPortal/PublisherPortal.csproj
Fixed since the last survey: 3 findings
- Secrets (history) · REDACTED: REDACTED src/Demos/azureblobhello/Program.cs
- Platform End-of-Life · End-of-life runtime: .NET net7.0 src/Demos/SaaSIntegration/src/PublisherPortal/PublisherPortal.csproj
- Outbound HTTP resilience · Outbound HTTP without resilience
Rebuild cost: about €16,000 · Estimate
| Cost to rebuild | €5,100 to €26,000, for 86 to 275 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 7,857 lines of product code |
| Comment lines | The estimate prices 7,434 lines. Comment lines count towards the size of 7,857 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Metering.BaseTypes.EventHub | 2 Metering.RuntimeCS | 3 AggregatorFunctionHost | 4 Metering.Aggregator | 5 Metering.BaseTypes.EventHub.PingMessageModule | 6 Metering.BaseTypes.WaterfallTypes | 7 Metering.Integration | 8 Metering.BaseTypes | 9 Metering.Integration.SnapshotIntervalConfigurationModule | 10 Metering.BaseTypes.BillingDimensionModule | 11 Metering.BaseTypes.Json.JsonInternals.BillingDimension | 12 Metering.BaseTypes.Json.JsonInternals.BillingDimensions | 13 Metering.BaseTypes.Json.JsonInternals.ConsumedQuantity | 14 Metering.BaseTypes.Json.JsonInternals.EventHubEvent_MeteringUpdateEvent | 15 Metering.BaseTypes.Json.JsonInternals.IncludedQuantity | 16 Metering.BaseTypes.Json.JsonInternals.InternalUsageEvent | 17 Metering.BaseTypes.Json.JsonInternals.Marketplace.AzureHttpResponseHeaders | 18 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchRequest | 19 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchResponseDTO | 20 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceError | 21 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceErrorDuplicate | 22 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceGenericError | 23 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceRequest | 24 Metering.BaseTypes.MeterCollectionLogic | 25 Metering.BaseTypes.MeterModule | 26 Metering.BaseTypes.MeterValueModule | 27 Metering.BaseTypes.WaterfallTypes.WaterfallMeterLogic | 28 Metering.ClientSDK | 29 Metering.EventHub.CaptureProcessor | 30 Metering.Integration.MarketplaceClient | 31 Metering.Integration.MeterCollectionStore | 32 Metering.Integration.MeteringAggregator | 33 Metering.Utils | 34 Metering.Utils.Status | 35 ReplayCaptureForPartitionProgram | 36 ReprocessLocalEventHubCaptureFilesProgram | 37 Metering.ClientSDK.MeteringEventHubExtensions | 38 Metering.Integration.MeterCollectionStore.Naming | 39 Metering.Utils.ManagementUtils | 40 Metering.Utils.ReportingOverviewModule |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Metering.BaseTypes.EventHub | ||||||||||||||||||||||||||||||||||||||||
| 2 Metering.RuntimeCS | ||||||||||||||||||||||||||||||||||||||||
| 3 AggregatorFunctionHost | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 Metering.Aggregator | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 Metering.BaseTypes.EventHub.PingMessageModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 6 Metering.BaseTypes.WaterfallTypes | 13 | |||||||||||||||||||||||||||||||||||||||
| 7 Metering.Integration | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 Metering.BaseTypes | 5 | 2 | ||||||||||||||||||||||||||||||||||||||
| 9 Metering.Integration.SnapshotIntervalConfigurationModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 Metering.BaseTypes.BillingDimensionModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 Metering.BaseTypes.Json.JsonInternals.BillingDimension | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Metering.BaseTypes.Json.JsonInternals.BillingDimensions | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 Metering.BaseTypes.Json.JsonInternals.ConsumedQuantity | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Metering.BaseTypes.Json.JsonInternals.EventHubEvent_MeteringUpdateEvent | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 Metering.BaseTypes.Json.JsonInternals.IncludedQuantity | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Metering.BaseTypes.Json.JsonInternals.InternalUsageEvent | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Metering.BaseTypes.Json.JsonInternals.Marketplace.AzureHttpResponseHeaders | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchRequest | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchResponseDTO | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceError | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceErrorDuplicate | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceGenericError | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceRequest | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 Metering.BaseTypes.MeterCollectionLogic | 3 | 9 | ||||||||||||||||||||||||||||||||||||||
| 25 Metering.BaseTypes.MeterModule | 1 | 10 | ||||||||||||||||||||||||||||||||||||||
| 26 Metering.BaseTypes.MeterValueModule | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 27 Metering.BaseTypes.WaterfallTypes.WaterfallMeterLogic | 5 | 4 | ||||||||||||||||||||||||||||||||||||||
| 28 Metering.ClientSDK | 3 | |||||||||||||||||||||||||||||||||||||||
| 29 Metering.EventHub.CaptureProcessor | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 Metering.Integration.MarketplaceClient | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 Metering.Integration.MeterCollectionStore | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 Metering.Integration.MeteringAggregator | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 33 Metering.Utils | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 Metering.Utils.Status | 4 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 ReplayCaptureForPartitionProgram | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 36 ReprocessLocalEventHubCaptureFilesProgram | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 Metering.ClientSDK.MeteringEventHubExtensions | 2 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 Metering.Integration.MeterCollectionStore.Naming | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 Metering.Utils.ManagementUtils | 3 | 2 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 Metering.Utils.ReportingOverviewModule | 2 | 1 |
3→2 AggregatorFunctionHost uses Metering.RuntimeCS✕
- Connections
- 1 pair of types, where a type in AggregatorFunctionHost uses a type in Metering.RuntimeCS.
- The types involved
AggregatorFunctionHost.AggregatorFunction→Metering.RuntimeCS.AggregationWorker
- Direction
- AggregatorFunctionHost uses Metering.RuntimeCS, so a change to Metering.RuntimeCS can break AggregatorFunctionHost, while a change to AggregatorFunctionHost can't break Metering.RuntimeCS.
- Position
- Below the diagonal: AggregatorFunctionHost uses a module listed above it, which is the healthy direction.
4→2 Metering.Aggregator uses Metering.RuntimeCS✕
- Connections
- 1 pair of types, where a type in Metering.Aggregator uses a type in Metering.RuntimeCS.
- The types involved
Metering.Aggregator.Worker→Metering.RuntimeCS.AggregationWorker
- Direction
- Metering.Aggregator uses Metering.RuntimeCS, so a change to Metering.RuntimeCS can break Metering.Aggregator, while a change to Metering.Aggregator can't break Metering.RuntimeCS.
- Position
- Below the diagonal: Metering.Aggregator uses a module listed above it, which is the healthy direction.
5→1 Metering.BaseTypes.EventHub.PingMessageModule uses Metering.BaseTypes.EventHub✕
- Connections
- 3 pairs of types, where a type in Metering.BaseTypes.EventHub.PingMessageModule uses a type in Metering.BaseTypes.EventHub.
- The types involved
Metering.BaseTypes.EventHub.PingMessageModule.PingMessageModule→Metering.BaseTypes.EventHub.PartitionIDMetering.BaseTypes.EventHub.PingMessageModule.PingMessageModule→Metering.BaseTypes.EventHub.PingMessageMetering.BaseTypes.EventHub.PingMessageModule.PingMessageModule→Metering.BaseTypes.EventHub.PingReason
- Direction
- Metering.BaseTypes.EventHub.PingMessageModule uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break Metering.BaseTypes.EventHub.PingMessageModule, while a change to Metering.BaseTypes.EventHub.PingMessageModule can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: Metering.BaseTypes.EventHub.PingMessageModule uses a module listed above it, which is the healthy direction.
6→8 Metering.BaseTypes.WaterfallTypes uses Metering.BaseTypes part of a loop✕
- Connections
- 13 pairs of types, where a type in Metering.BaseTypes.WaterfallTypes uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.WaterfallTypes.ConsumptionReport→Metering.BaseTypes.DimensionIdMetering.BaseTypes.WaterfallTypes.ConsumptionReport→Metering.BaseTypes.QuantityMetering.BaseTypes.WaterfallTypes.SubtractionAggregation→Metering.BaseTypes.DimensionIdMetering.BaseTypes.WaterfallTypes.SubtractionAggregation→Metering.BaseTypes.QuantityMetering.BaseTypes.WaterfallTypes.WaterfallBillingDimensionItem→Metering.BaseTypes.DimensionIdMetering.BaseTypes.WaterfallTypes.WaterfallBillingDimensionItem→Metering.BaseTypes.QuantityMetering.BaseTypes.WaterfallTypes.WaterfallMeterValue→Metering.BaseTypes.DimensionIdMetering.BaseTypes.WaterfallTypes.WaterfallMeterValue→Metering.BaseTypes.QuantityMetering.BaseTypes.WaterfallTypes.WaterfallModelRange→Metering.BaseTypes.DimensionIdMetering.BaseTypes.WaterfallTypes.WaterfallModelRange→Metering.BaseTypes.QuantityMetering.BaseTypes.WaterfallTypes.WaterfallModelRow→Metering.BaseTypes.QuantityMetering.BaseTypes.WaterfallTypes.WaterfallOverageOverage→Metering.BaseTypes.DimensionIdMetering.BaseTypes.WaterfallTypes.WaterfallOverageOverage→Metering.BaseTypes.Quantity
- Direction
- Metering.BaseTypes.WaterfallTypes uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.WaterfallTypes, while a change to Metering.BaseTypes.WaterfallTypes can't break Metering.BaseTypes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→1 Metering.Integration uses Metering.BaseTypes.EventHub✕
- Connections
- 2 pairs of types, where a type in Metering.Integration uses a type in Metering.BaseTypes.EventHub.
- The types involved
Metering.Integration.EventHubConfig→Metering.BaseTypes.EventHub.EventHubNameMetering.Integration.MeteringConnections→Metering.BaseTypes.EventHub.EventHubName
- Direction
- Metering.Integration uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break Metering.Integration, while a change to Metering.Integration can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: Metering.Integration uses a module listed above it, which is the healthy direction.
8→1 Metering.BaseTypes uses Metering.BaseTypes.EventHub✕
- Connections
- 5 pairs of types, where a type in Metering.BaseTypes uses a type in Metering.BaseTypes.EventHub.
- The types involved
Metering.BaseTypes.Meter→Metering.BaseTypes.EventHub.MessagePositionMetering.BaseTypes.MeterCollection→Metering.BaseTypes.EventHub.EventHubEvent`1Metering.BaseTypes.MeterCollection→Metering.BaseTypes.EventHub.MessagePositionMetering.BaseTypes.MeteringUpdateEvent→Metering.BaseTypes.EventHub.PingMessageMetering.BaseTypes.RemoveUnprocessedMessages→Metering.BaseTypes.EventHub.PartitionID
- Direction
- Metering.BaseTypes uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break Metering.BaseTypes, while a change to Metering.BaseTypes can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: Metering.BaseTypes uses a module listed above it, which is the healthy direction.
8→6 Metering.BaseTypes uses Metering.BaseTypes.WaterfallTypes✕
- Connections
- 2 pairs of types, where a type in Metering.BaseTypes uses a type in Metering.BaseTypes.WaterfallTypes.
- The types involved
Metering.BaseTypes.BillingDimension→Metering.BaseTypes.WaterfallTypes.WaterfallBillingDimensionMetering.BaseTypes.MeterValue→Metering.BaseTypes.WaterfallTypes.WaterfallMeterValue
- Direction
- Metering.BaseTypes uses Metering.BaseTypes.WaterfallTypes, so a change to Metering.BaseTypes.WaterfallTypes can break Metering.BaseTypes, while a change to Metering.BaseTypes can't break Metering.BaseTypes.WaterfallTypes.
- Position
- Below the diagonal: Metering.BaseTypes uses a module listed above it, which is the healthy direction.
9→1 Metering.Integration.SnapshotIntervalConfigurationModule uses Metering.BaseTypes.EventHub✕
- Connections
- 1 pair of types, where a type in Metering.Integration.SnapshotIntervalConfigurationModule uses a type in Metering.BaseTypes.EventHub.
- The types involved
Metering.Integration.SnapshotIntervalConfigurationModule.SnapshotIntervalConfigurationModule→Metering.BaseTypes.EventHub.MessagePosition
- Direction
- Metering.Integration.SnapshotIntervalConfigurationModule uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break Metering.Integration.SnapshotIntervalConfigurationModule, while a change to Metering.Integration.SnapshotIntervalConfigurationModule can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: Metering.Integration.SnapshotIntervalConfigurationModule uses a module listed above it, which is the healthy direction.
9→7 Metering.Integration.SnapshotIntervalConfigurationModule uses Metering.Integration✕
- Connections
- 1 pair of types, where a type in Metering.Integration.SnapshotIntervalConfigurationModule uses a type in Metering.Integration.
- The types involved
Metering.Integration.SnapshotIntervalConfigurationModule.SnapshotIntervalConfigurationModule→Metering.Integration.SnapshotIntervalConfiguration
- Direction
- Metering.Integration.SnapshotIntervalConfigurationModule uses Metering.Integration, so a change to Metering.Integration can break Metering.Integration.SnapshotIntervalConfigurationModule, while a change to Metering.Integration.SnapshotIntervalConfigurationModule can't break Metering.Integration.
- Position
- Below the diagonal: Metering.Integration.SnapshotIntervalConfigurationModule uses a module listed above it, which is the healthy direction.
10→8 Metering.BaseTypes.BillingDimensionModule uses Metering.BaseTypes✕
- Connections
- 2 pairs of types, where a type in Metering.BaseTypes.BillingDimensionModule uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.BillingDimensionModule.BillingDimensionModule→Metering.BaseTypes.BillingDimensionMetering.BaseTypes.BillingDimensionModule.BillingDimensionModule→Metering.BaseTypes.DimensionId
- Direction
- Metering.BaseTypes.BillingDimensionModule uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.BillingDimensionModule, while a change to Metering.BaseTypes.BillingDimensionModule can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.BillingDimensionModule uses a module listed above it, which is the healthy direction.
11→8 Metering.BaseTypes.Json.JsonInternals.BillingDimension uses Metering.BaseTypes✕
- Connections
- 1 pair of types, where a type in Metering.BaseTypes.Json.JsonInternals.BillingDimension uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.Json.JsonInternals.BillingDimension.BillingDimension→Metering.BaseTypes.BillingDimension
- Direction
- Metering.BaseTypes.Json.JsonInternals.BillingDimension uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.Json.JsonInternals.BillingDimension, while a change to Metering.BaseTypes.Json.JsonInternals.BillingDimension can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.Json.JsonInternals.BillingDimension uses a module listed above it, which is the healthy direction.
12→8 Metering.BaseTypes.Json.JsonInternals.BillingDimensions uses Metering.BaseTypes✕
- Connections
- 2 pairs of types, where a type in Metering.BaseTypes.Json.JsonInternals.BillingDimensions uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.Json.JsonInternals.BillingDimensions.BillingDimensions→Metering.BaseTypes.ApplicationInternalMeterNameMetering.BaseTypes.Json.JsonInternals.BillingDimensions.BillingDimensions→Metering.BaseTypes.BillingDimension
- Direction
- Metering.BaseTypes.Json.JsonInternals.BillingDimensions uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.Json.JsonInternals.BillingDimensions, while a change to Metering.BaseTypes.Json.JsonInternals.BillingDimensions can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.Json.JsonInternals.BillingDimensions uses a module listed above it, which is the healthy direction.
13→8 Metering.BaseTypes.Json.JsonInternals.ConsumedQuantity uses Metering.BaseTypes✕
- Connections
- 1 pair of types, where a type in Metering.BaseTypes.Json.JsonInternals.ConsumedQuantity uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.Json.JsonInternals.ConsumedQuantity.ConsumedQuantity→Metering.BaseTypes.ConsumedQuantity
- Direction
- Metering.BaseTypes.Json.JsonInternals.ConsumedQuantity uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.Json.JsonInternals.ConsumedQuantity, while a change to Metering.BaseTypes.Json.JsonInternals.ConsumedQuantity can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.Json.JsonInternals.ConsumedQuantity uses a module listed above it, which is the healthy direction.
14→1 Metering.BaseTypes.Json.JsonInternals.EventHubEvent_MeteringUpdateEvent uses Metering.BaseTypes.EventHub✕
- Connections
- 1 pair of types, where a type in Metering.BaseTypes.Json.JsonInternals.EventHubEvent_MeteringUpdateEvent uses a type in Metering.BaseTypes.EventHub.
- The types involved
Metering.BaseTypes.Json.JsonInternals.EventHubEvent_MeteringUpdateEvent.EventHubEvent_MeteringUpdateEvent→Metering.BaseTypes.EventHub.EventHubEvent`1
- Direction
- Metering.BaseTypes.Json.JsonInternals.EventHubEvent_MeteringUpdateEvent uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break Metering.BaseTypes.Json.JsonInternals.EventHubEvent_MeteringUpdateEvent, while a change to Metering.BaseTypes.Json.JsonInternals.EventHubEvent_MeteringUpdateEvent can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: Metering.BaseTypes.Json.JsonInternals.EventHubEvent_MeteringUpdateEvent uses a module listed above it, which is the healthy direction.
14→8 Metering.BaseTypes.Json.JsonInternals.EventHubEvent_MeteringUpdateEvent uses Metering.BaseTypes✕
- Connections
- 1 pair of types, where a type in Metering.BaseTypes.Json.JsonInternals.EventHubEvent_MeteringUpdateEvent uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.Json.JsonInternals.EventHubEvent_MeteringUpdateEvent.EventHubEvent_MeteringUpdateEvent→Metering.BaseTypes.MeteringUpdateEvent
- Direction
- Metering.BaseTypes.Json.JsonInternals.EventHubEvent_MeteringUpdateEvent uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.Json.JsonInternals.EventHubEvent_MeteringUpdateEvent, while a change to Metering.BaseTypes.Json.JsonInternals.EventHubEvent_MeteringUpdateEvent can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.Json.JsonInternals.EventHubEvent_MeteringUpdateEvent uses a module listed above it, which is the healthy direction.
15→8 Metering.BaseTypes.Json.JsonInternals.IncludedQuantity uses Metering.BaseTypes✕
- Connections
- 1 pair of types, where a type in Metering.BaseTypes.Json.JsonInternals.IncludedQuantity uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.Json.JsonInternals.IncludedQuantity.IncludedQuantity→Metering.BaseTypes.IncludedQuantity
- Direction
- Metering.BaseTypes.Json.JsonInternals.IncludedQuantity uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.Json.JsonInternals.IncludedQuantity, while a change to Metering.BaseTypes.Json.JsonInternals.IncludedQuantity can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.Json.JsonInternals.IncludedQuantity uses a module listed above it, which is the healthy direction.
16→8 Metering.BaseTypes.Json.JsonInternals.InternalUsageEvent uses Metering.BaseTypes✕
- Connections
- 1 pair of types, where a type in Metering.BaseTypes.Json.JsonInternals.InternalUsageEvent uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.Json.JsonInternals.InternalUsageEvent.InternalUsageEvent→Metering.BaseTypes.InternalUsageEvent
- Direction
- Metering.BaseTypes.Json.JsonInternals.InternalUsageEvent uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.Json.JsonInternals.InternalUsageEvent, while a change to Metering.BaseTypes.Json.JsonInternals.InternalUsageEvent can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.Json.JsonInternals.InternalUsageEvent uses a module listed above it, which is the healthy direction.
17→8 Metering.BaseTypes.Json.JsonInternals.Marketplace.AzureHttpResponseHeaders uses Metering.BaseTypes✕
- Connections
- 1 pair of types, where a type in Metering.BaseTypes.Json.JsonInternals.Marketplace.AzureHttpResponseHeaders uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.Json.JsonInternals.Marketplace.AzureHttpResponseHeaders.AzureHttpResponseHeaders→Metering.BaseTypes.AzureHttpResponseHeaders
- Direction
- Metering.BaseTypes.Json.JsonInternals.Marketplace.AzureHttpResponseHeaders uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.Json.JsonInternals.Marketplace.AzureHttpResponseHeaders, while a change to Metering.BaseTypes.Json.JsonInternals.Marketplace.AzureHttpResponseHeaders can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.Json.JsonInternals.Marketplace.AzureHttpResponseHeaders uses a module listed above it, which is the healthy direction.
18→8 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchRequest uses Metering.BaseTypes✕
- Connections
- 1 pair of types, where a type in Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchRequest uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchRequest.MarketplaceBatchRequest→Metering.BaseTypes.MarketplaceBatchRequest
- Direction
- Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchRequest uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchRequest, while a change to Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchRequest can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchRequest uses a module listed above it, which is the healthy direction.
19→8 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchResponseDTO uses Metering.BaseTypes✕
- Connections
- 1 pair of types, where a type in Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchResponseDTO uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchResponseDTO.MarketplaceBatchResponseDTO→Metering.BaseTypes.MarketplaceBatchResponseDTO
- Direction
- Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchResponseDTO uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchResponseDTO, while a change to Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchResponseDTO can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceBatchResponseDTO uses a module listed above it, which is the healthy direction.
20→8 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceError uses Metering.BaseTypes✕
- Connections
- 1 pair of types, where a type in Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceError uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceError.MarketplaceError→Metering.BaseTypes.MarketplaceError
- Direction
- Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceError uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceError, while a change to Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceError can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceError uses a module listed above it, which is the healthy direction.
21→8 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceErrorDuplicate uses Metering.BaseTypes✕
- Connections
- 1 pair of types, where a type in Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceErrorDuplicate uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceErrorDuplicate.MarketplaceErrorDuplicate→Metering.BaseTypes.MarketplaceErrorDuplicate
- Direction
- Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceErrorDuplicate uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceErrorDuplicate, while a change to Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceErrorDuplicate can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceErrorDuplicate uses a module listed above it, which is the healthy direction.
22→8 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceGenericError uses Metering.BaseTypes✕
- Connections
- 1 pair of types, where a type in Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceGenericError uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceGenericError.MarketplaceGenericError→Metering.BaseTypes.MarketplaceGenericError
- Direction
- Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceGenericError uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceGenericError, while a change to Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceGenericError can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceGenericError uses a module listed above it, which is the healthy direction.
23→8 Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceRequest uses Metering.BaseTypes✕
- Connections
- 1 pair of types, where a type in Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceRequest uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceRequest.MarketplaceRequest→Metering.BaseTypes.MarketplaceRequest
- Direction
- Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceRequest uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceRequest, while a change to Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceRequest can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.Json.JsonInternals.Marketplace.MarketplaceRequest uses a module listed above it, which is the healthy direction.
24→1 Metering.BaseTypes.MeterCollectionLogic uses Metering.BaseTypes.EventHub✕
- Connections
- 3 pairs of types, where a type in Metering.BaseTypes.MeterCollectionLogic uses a type in Metering.BaseTypes.EventHub.
- The types involved
Metering.BaseTypes.MeterCollectionLogic.MeterCollectionLogic→Metering.BaseTypes.EventHub.EventHubEvent`1Metering.BaseTypes.MeterCollectionLogic.MeterCollectionLogic→Metering.BaseTypes.EventHub.MessagePositionMetering.BaseTypes.MeterCollectionLogic.MeterCollectionLogic→Metering.BaseTypes.EventHub.StartingPosition
- Direction
- Metering.BaseTypes.MeterCollectionLogic uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break Metering.BaseTypes.MeterCollectionLogic, while a change to Metering.BaseTypes.MeterCollectionLogic can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: Metering.BaseTypes.MeterCollectionLogic uses a module listed above it, which is the healthy direction.
24→8 Metering.BaseTypes.MeterCollectionLogic uses Metering.BaseTypes✕
- Connections
- 9 pairs of types, where a type in Metering.BaseTypes.MeterCollectionLogic uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.MeterCollectionLogic.MeterCollectionLogic→Metering.BaseTypes.InternalUsageEventMetering.BaseTypes.MeterCollectionLogic.MeterCollectionLogic→Metering.BaseTypes.MarketplaceRequestMetering.BaseTypes.MeterCollectionLogic.MeterCollectionLogic→Metering.BaseTypes.MarketplaceResourceIdMetering.BaseTypes.MeterCollectionLogic.MeterCollectionLogic→Metering.BaseTypes.MarketplaceResponseMetering.BaseTypes.MeterCollectionLogic.MeterCollectionLogic→Metering.BaseTypes.MeterCollectionMetering.BaseTypes.MeterCollectionLogic.MeterCollectionLogic→Metering.BaseTypes.MeteringUpdateEventMetering.BaseTypes.MeterCollectionLogic.MeterCollectionLogic→Metering.BaseTypes.RemoveUnprocessedMessagesMetering.BaseTypes.MeterCollectionLogic.MeterCollectionLogic→Metering.BaseTypes.SubscriptionCreationInformationMetering.BaseTypes.MeterCollectionLogic.MeterCollectionLogic→Metering.BaseTypes.UnprocessableMessage
- Direction
- Metering.BaseTypes.MeterCollectionLogic uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.MeterCollectionLogic, while a change to Metering.BaseTypes.MeterCollectionLogic can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.MeterCollectionLogic uses a module listed above it, which is the healthy direction.
25→1 Metering.BaseTypes.MeterModule uses Metering.BaseTypes.EventHub✕
- Connections
- 1 pair of types, where a type in Metering.BaseTypes.MeterModule uses a type in Metering.BaseTypes.EventHub.
- The types involved
Metering.BaseTypes.MeterModule.MeterModule→Metering.BaseTypes.EventHub.MessagePosition
- Direction
- Metering.BaseTypes.MeterModule uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break Metering.BaseTypes.MeterModule, while a change to Metering.BaseTypes.MeterModule can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: Metering.BaseTypes.MeterModule uses a module listed above it, which is the healthy direction.
25→8 Metering.BaseTypes.MeterModule uses Metering.BaseTypes✕
- Connections
- 10 pairs of types, where a type in Metering.BaseTypes.MeterModule uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.MeterModule.MeterModule→Metering.BaseTypes.ApplicationInternalMeterNameMetering.BaseTypes.MeterModule.MeterModule→Metering.BaseTypes.BillingDimensionMetering.BaseTypes.MeterModule.MeterModule→Metering.BaseTypes.InternalUsageEventMetering.BaseTypes.MeterModule.MeterModule→Metering.BaseTypes.MarketplaceRequestMetering.BaseTypes.MeterModule.MeterModule→Metering.BaseTypes.MarketplaceResourceIdMetering.BaseTypes.MeterModule.MeterModule→Metering.BaseTypes.MarketplaceResponseMetering.BaseTypes.MeterModule.MeterModule→Metering.BaseTypes.MarketplaceSuccessResponseMetering.BaseTypes.MeterModule.MeterModule→Metering.BaseTypes.MeterMetering.BaseTypes.MeterModule.MeterModule→Metering.BaseTypes.QuantityMetering.BaseTypes.MeterModule.MeterModule→Metering.BaseTypes.SubscriptionCreationInformation
- Direction
- Metering.BaseTypes.MeterModule uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.MeterModule, while a change to Metering.BaseTypes.MeterModule can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.MeterModule uses a module listed above it, which is the healthy direction.
26→1 Metering.BaseTypes.MeterValueModule uses Metering.BaseTypes.EventHub✕
- Connections
- 1 pair of types, where a type in Metering.BaseTypes.MeterValueModule uses a type in Metering.BaseTypes.EventHub.
- The types involved
Metering.BaseTypes.MeterValueModule.MeterValueModule→Metering.BaseTypes.EventHub.MessagePosition
- Direction
- Metering.BaseTypes.MeterValueModule uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break Metering.BaseTypes.MeterValueModule, while a change to Metering.BaseTypes.MeterValueModule can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: Metering.BaseTypes.MeterValueModule uses a module listed above it, which is the healthy direction.
26→8 Metering.BaseTypes.MeterValueModule uses Metering.BaseTypes✕
- Connections
- 7 pairs of types, where a type in Metering.BaseTypes.MeterValueModule uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.MeterValueModule.MeterValueModule→Metering.BaseTypes.ApplicationInternalMeterNameMetering.BaseTypes.MeterValueModule.MeterValueModule→Metering.BaseTypes.BillingDimensionMetering.BaseTypes.MeterValueModule.MeterValueModule→Metering.BaseTypes.DimensionIdMetering.BaseTypes.MeterValueModule.MeterValueModule→Metering.BaseTypes.MarketplaceResourceIdMetering.BaseTypes.MeterValueModule.MeterValueModule→Metering.BaseTypes.MeterValueMetering.BaseTypes.MeterValueModule.MeterValueModule→Metering.BaseTypes.PlanIdMetering.BaseTypes.MeterValueModule.MeterValueModule→Metering.BaseTypes.Quantity
- Direction
- Metering.BaseTypes.MeterValueModule uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.MeterValueModule, while a change to Metering.BaseTypes.MeterValueModule can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.MeterValueModule uses a module listed above it, which is the healthy direction.
27→6 Metering.BaseTypes.WaterfallTypes.WaterfallMeterLogic uses Metering.BaseTypes.WaterfallTypes✕
- Connections
- 5 pairs of types, where a type in Metering.BaseTypes.WaterfallTypes.WaterfallMeterLogic uses a type in Metering.BaseTypes.WaterfallTypes.
- The types involved
Metering.BaseTypes.WaterfallTypes.WaterfallMeterLogic.WaterfallMeterLogic→Metering.BaseTypes.WaterfallTypes.SubtractionAggregationMetering.BaseTypes.WaterfallTypes.WaterfallMeterLogic.WaterfallMeterLogic→Metering.BaseTypes.WaterfallTypes.WaterfallBillingDimensionMetering.BaseTypes.WaterfallTypes.WaterfallMeterLogic.WaterfallMeterLogic→Metering.BaseTypes.WaterfallTypes.WaterfallBillingDimensionItemMetering.BaseTypes.WaterfallTypes.WaterfallMeterLogic.WaterfallMeterLogic→Metering.BaseTypes.WaterfallTypes.WaterfallMeterValueMetering.BaseTypes.WaterfallTypes.WaterfallMeterLogic.WaterfallMeterLogic→Metering.BaseTypes.WaterfallTypes.WaterfallModelRow
- Direction
- Metering.BaseTypes.WaterfallTypes.WaterfallMeterLogic uses Metering.BaseTypes.WaterfallTypes, so a change to Metering.BaseTypes.WaterfallTypes can break Metering.BaseTypes.WaterfallTypes.WaterfallMeterLogic, while a change to Metering.BaseTypes.WaterfallTypes.WaterfallMeterLogic can't break Metering.BaseTypes.WaterfallTypes.
- Position
- Below the diagonal: Metering.BaseTypes.WaterfallTypes.WaterfallMeterLogic uses a module listed above it, which is the healthy direction.
27→8 Metering.BaseTypes.WaterfallTypes.WaterfallMeterLogic uses Metering.BaseTypes✕
- Connections
- 4 pairs of types, where a type in Metering.BaseTypes.WaterfallTypes.WaterfallMeterLogic uses a type in Metering.BaseTypes.
- The types involved
Metering.BaseTypes.WaterfallTypes.WaterfallMeterLogic.WaterfallMeterLogic→Metering.BaseTypes.DimensionIdMetering.BaseTypes.WaterfallTypes.WaterfallMeterLogic.WaterfallMeterLogic→Metering.BaseTypes.MarketplaceResourceIdMetering.BaseTypes.WaterfallTypes.WaterfallMeterLogic.WaterfallMeterLogic→Metering.BaseTypes.PlanIdMetering.BaseTypes.WaterfallTypes.WaterfallMeterLogic.WaterfallMeterLogic→Metering.BaseTypes.Quantity
- Direction
- Metering.BaseTypes.WaterfallTypes.WaterfallMeterLogic uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.BaseTypes.WaterfallTypes.WaterfallMeterLogic, while a change to Metering.BaseTypes.WaterfallTypes.WaterfallMeterLogic can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.BaseTypes.WaterfallTypes.WaterfallMeterLogic uses a module listed above it, which is the healthy direction.
28→8 Metering.ClientSDK uses Metering.BaseTypes✕
- Connections
- 3 pairs of types, where a type in Metering.ClientSDK uses a type in Metering.BaseTypes.
- The types involved
Metering.ClientSDK.Consumption→Metering.BaseTypes.MarketplaceResourceIdMetering.ClientSDK.MeterValue→Metering.BaseTypes.ApplicationInternalMeterNameMetering.ClientSDK.MeterValue→Metering.BaseTypes.Quantity
- Direction
- Metering.ClientSDK uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.ClientSDK, while a change to Metering.ClientSDK can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.ClientSDK uses a module listed above it, which is the healthy direction.
29→1 Metering.EventHub.CaptureProcessor uses Metering.BaseTypes.EventHub✕
- Connections
- 4 pairs of types, where a type in Metering.EventHub.CaptureProcessor uses a type in Metering.BaseTypes.EventHub.
- The types involved
Metering.EventHub.CaptureProcessor.CaptureProcessor→Metering.BaseTypes.EventHub.EventHubEvent`1Metering.EventHub.CaptureProcessor.CaptureProcessor→Metering.BaseTypes.EventHub.EventHubNameMetering.EventHub.CaptureProcessor.CaptureProcessor→Metering.BaseTypes.EventHub.MessagePositionMetering.EventHub.CaptureProcessor.CaptureProcessor→Metering.BaseTypes.EventHub.PartitionID
- Direction
- Metering.EventHub.CaptureProcessor uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break Metering.EventHub.CaptureProcessor, while a change to Metering.EventHub.CaptureProcessor can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: Metering.EventHub.CaptureProcessor uses a module listed above it, which is the healthy direction.
29→7 Metering.EventHub.CaptureProcessor uses Metering.Integration✕
- Connections
- 1 pair of types, where a type in Metering.EventHub.CaptureProcessor uses a type in Metering.Integration.
- The types involved
Metering.EventHub.CaptureProcessor.CaptureProcessor→Metering.Integration.MeteringConnections
- Direction
- Metering.EventHub.CaptureProcessor uses Metering.Integration, so a change to Metering.Integration can break Metering.EventHub.CaptureProcessor, while a change to Metering.EventHub.CaptureProcessor can't break Metering.Integration.
- Position
- Below the diagonal: Metering.EventHub.CaptureProcessor uses a module listed above it, which is the healthy direction.
29→8 Metering.EventHub.CaptureProcessor uses Metering.BaseTypes✕
- Connections
- 1 pair of types, where a type in Metering.EventHub.CaptureProcessor uses a type in Metering.BaseTypes.
- The types involved
Metering.EventHub.CaptureProcessor.CaptureProcessor→Metering.BaseTypes.MeteringUpdateEvent
- Direction
- Metering.EventHub.CaptureProcessor uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.EventHub.CaptureProcessor, while a change to Metering.EventHub.CaptureProcessor can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.EventHub.CaptureProcessor uses a module listed above it, which is the healthy direction.
30→7 Metering.Integration.MarketplaceClient uses Metering.Integration✕
- Connections
- 1 pair of types, where a type in Metering.Integration.MarketplaceClient uses a type in Metering.Integration.
- The types involved
Metering.Integration.MarketplaceClient.MarketplaceClient→Metering.Integration.MeteringConfigurationProvider
- Direction
- Metering.Integration.MarketplaceClient uses Metering.Integration, so a change to Metering.Integration can break Metering.Integration.MarketplaceClient, while a change to Metering.Integration.MarketplaceClient can't break Metering.Integration.
- Position
- Below the diagonal: Metering.Integration.MarketplaceClient uses a module listed above it, which is the healthy direction.
30→8 Metering.Integration.MarketplaceClient uses Metering.BaseTypes✕
- Connections
- 2 pairs of types, where a type in Metering.Integration.MarketplaceClient uses a type in Metering.BaseTypes.
- The types involved
Metering.Integration.MarketplaceClient.MarketplaceClient→Metering.BaseTypes.MarketplaceBatchResponseMetering.Integration.MarketplaceClient.MarketplaceClient→Metering.BaseTypes.MarketplaceRequest
- Direction
- Metering.Integration.MarketplaceClient uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.Integration.MarketplaceClient, while a change to Metering.Integration.MarketplaceClient can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.Integration.MarketplaceClient uses a module listed above it, which is the healthy direction.
31→1 Metering.Integration.MeterCollectionStore uses Metering.BaseTypes.EventHub✕
- Connections
- 4 pairs of types, where a type in Metering.Integration.MeterCollectionStore uses a type in Metering.BaseTypes.EventHub.
- The types involved
Metering.Integration.MeterCollectionStore.MeterCollectionStore→Metering.BaseTypes.EventHub.MessagePositionMetering.Integration.MeterCollectionStore.MeterCollectionStore→Metering.BaseTypes.EventHub.PartitionIDMetering.Integration.MeterCollectionStore.SnapshotName→Metering.BaseTypes.EventHub.EventHubNameMetering.Integration.MeterCollectionStore.SnapshotName→Metering.BaseTypes.EventHub.MessagePosition
- Direction
- Metering.Integration.MeterCollectionStore uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break Metering.Integration.MeterCollectionStore, while a change to Metering.Integration.MeterCollectionStore can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: Metering.Integration.MeterCollectionStore uses a module listed above it, which is the healthy direction.
31→7 Metering.Integration.MeterCollectionStore uses Metering.Integration✕
- Connections
- 1 pair of types, where a type in Metering.Integration.MeterCollectionStore uses a type in Metering.Integration.
- The types involved
Metering.Integration.MeterCollectionStore.MeterCollectionStore→Metering.Integration.MeteringConnections
- Direction
- Metering.Integration.MeterCollectionStore uses Metering.Integration, so a change to Metering.Integration can break Metering.Integration.MeterCollectionStore, while a change to Metering.Integration.MeterCollectionStore can't break Metering.Integration.
- Position
- Below the diagonal: Metering.Integration.MeterCollectionStore uses a module listed above it, which is the healthy direction.
31→8 Metering.Integration.MeterCollectionStore uses Metering.BaseTypes✕
- Connections
- 1 pair of types, where a type in Metering.Integration.MeterCollectionStore uses a type in Metering.BaseTypes.
- The types involved
Metering.Integration.MeterCollectionStore.MeterCollectionStore→Metering.BaseTypes.MeterCollection
- Direction
- Metering.Integration.MeterCollectionStore uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.Integration.MeterCollectionStore, while a change to Metering.Integration.MeterCollectionStore can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.Integration.MeterCollectionStore uses a module listed above it, which is the healthy direction.
32→1 Metering.Integration.MeteringAggregator uses Metering.BaseTypes.EventHub✕
- Connections
- 1 pair of types, where a type in Metering.Integration.MeteringAggregator uses a type in Metering.BaseTypes.EventHub.
- The types involved
Metering.Integration.MeteringAggregator.MeteringAggregator→Metering.BaseTypes.EventHub.EventHubProcessorEvent`2
- Direction
- Metering.Integration.MeteringAggregator uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break Metering.Integration.MeteringAggregator, while a change to Metering.Integration.MeteringAggregator can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: Metering.Integration.MeteringAggregator uses a module listed above it, which is the healthy direction.
32→8 Metering.Integration.MeteringAggregator uses Metering.BaseTypes✕
- Connections
- 2 pairs of types, where a type in Metering.Integration.MeteringAggregator uses a type in Metering.BaseTypes.
- The types involved
Metering.Integration.MeteringAggregator.MeteringAggregator→Metering.BaseTypes.MeterCollectionMetering.Integration.MeteringAggregator.MeteringAggregator→Metering.BaseTypes.MeteringUpdateEvent
- Direction
- Metering.Integration.MeteringAggregator uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.Integration.MeteringAggregator, while a change to Metering.Integration.MeteringAggregator can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.Integration.MeteringAggregator uses a module listed above it, which is the healthy direction.
33→8 Metering.Utils uses Metering.BaseTypes✕
- Connections
- 1 pair of types, where a type in Metering.Utils uses a type in Metering.BaseTypes.
- The types involved
Metering.Utils.ReportingOverview→Metering.BaseTypes.Quantity
- Direction
- Metering.Utils uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.Utils, while a change to Metering.Utils can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.Utils uses a module listed above it, which is the healthy direction.
34→1 Metering.Utils.Status uses Metering.BaseTypes.EventHub✕
- Connections
- 4 pairs of types, where a type in Metering.Utils.Status uses a type in Metering.BaseTypes.EventHub.
- The types involved
Metering.Utils.Status.PartitionProps→Metering.BaseTypes.EventHub.PartitionIDMetering.Utils.Status.Status→Metering.BaseTypes.EventHub.EventsToCatchupMetering.Utils.Status.Status→Metering.BaseTypes.EventHub.MessagePositionMetering.Utils.Status.Status→Metering.BaseTypes.EventHub.PartitionID
- Direction
- Metering.Utils.Status uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break Metering.Utils.Status, while a change to Metering.Utils.Status can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: Metering.Utils.Status uses a module listed above it, which is the healthy direction.
34→7 Metering.Utils.Status uses Metering.Integration✕
- Connections
- 2 pairs of types, where a type in Metering.Utils.Status uses a type in Metering.Integration.
- The types involved
Metering.Utils.Status.Status→Metering.Integration.MeteringConfigurationProviderMetering.Utils.Status.Status→Metering.Integration.MeteringConnections
- Direction
- Metering.Utils.Status uses Metering.Integration, so a change to Metering.Integration can break Metering.Utils.Status, while a change to Metering.Utils.Status can't break Metering.Integration.
- Position
- Below the diagonal: Metering.Utils.Status uses a module listed above it, which is the healthy direction.
34→8 Metering.Utils.Status uses Metering.BaseTypes✕
- Connections
- 1 pair of types, where a type in Metering.Utils.Status uses a type in Metering.BaseTypes.
- The types involved
Metering.Utils.Status.Status→Metering.BaseTypes.MeterCollection
- Direction
- Metering.Utils.Status uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.Utils.Status, while a change to Metering.Utils.Status can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.Utils.Status uses a module listed above it, which is the healthy direction.
35→1 ReplayCaptureForPartitionProgram uses Metering.BaseTypes.EventHub✕
- Connections
- 1 pair of types, where a type in ReplayCaptureForPartitionProgram uses a type in Metering.BaseTypes.EventHub.
- The types involved
ReplayCaptureForPartitionProgram.ReplayCaptureForPartitionProgram→Metering.BaseTypes.EventHub.EventHubEvent`1
- Direction
- ReplayCaptureForPartitionProgram uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break ReplayCaptureForPartitionProgram, while a change to ReplayCaptureForPartitionProgram can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: ReplayCaptureForPartitionProgram uses a module listed above it, which is the healthy direction.
35→7 ReplayCaptureForPartitionProgram uses Metering.Integration✕
- Connections
- 1 pair of types, where a type in ReplayCaptureForPartitionProgram uses a type in Metering.Integration.
- The types involved
ReplayCaptureForPartitionProgram.ReplayCaptureForPartitionProgram→Metering.Integration.MeteringConnections
- Direction
- ReplayCaptureForPartitionProgram uses Metering.Integration, so a change to Metering.Integration can break ReplayCaptureForPartitionProgram, while a change to ReplayCaptureForPartitionProgram can't break Metering.Integration.
- Position
- Below the diagonal: ReplayCaptureForPartitionProgram uses a module listed above it, which is the healthy direction.
35→8 ReplayCaptureForPartitionProgram uses Metering.BaseTypes✕
- Connections
- 2 pairs of types, where a type in ReplayCaptureForPartitionProgram uses a type in Metering.BaseTypes.
- The types involved
ReplayCaptureForPartitionProgram.ReplayCaptureForPartitionProgram→Metering.BaseTypes.MeterCollectionReplayCaptureForPartitionProgram.ReplayCaptureForPartitionProgram→Metering.BaseTypes.MeteringUpdateEvent
- Direction
- ReplayCaptureForPartitionProgram uses Metering.BaseTypes, so a change to Metering.BaseTypes can break ReplayCaptureForPartitionProgram, while a change to ReplayCaptureForPartitionProgram can't break Metering.BaseTypes.
- Position
- Below the diagonal: ReplayCaptureForPartitionProgram uses a module listed above it, which is the healthy direction.
36→1 ReprocessLocalEventHubCaptureFilesProgram uses Metering.BaseTypes.EventHub✕
- Connections
- 2 pairs of types, where a type in ReprocessLocalEventHubCaptureFilesProgram uses a type in Metering.BaseTypes.EventHub.
- The types involved
ReprocessLocalEventHubCaptureFilesProgram.ReprocessLocalEventHubCaptureFilesProgram→Metering.BaseTypes.EventHub.EventHubEvent`1ReprocessLocalEventHubCaptureFilesProgram.ReprocessLocalEventHubCaptureFilesProgram→Metering.BaseTypes.EventHub.PartitionID
- Direction
- ReprocessLocalEventHubCaptureFilesProgram uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break ReprocessLocalEventHubCaptureFilesProgram, while a change to ReprocessLocalEventHubCaptureFilesProgram can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: ReprocessLocalEventHubCaptureFilesProgram uses a module listed above it, which is the healthy direction.
36→8 ReprocessLocalEventHubCaptureFilesProgram uses Metering.BaseTypes✕
- Connections
- 2 pairs of types, where a type in ReprocessLocalEventHubCaptureFilesProgram uses a type in Metering.BaseTypes.
- The types involved
ReprocessLocalEventHubCaptureFilesProgram.ReprocessLocalEventHubCaptureFilesProgram→Metering.BaseTypes.MarketplaceResourceIdReprocessLocalEventHubCaptureFilesProgram.ReprocessLocalEventHubCaptureFilesProgram→Metering.BaseTypes.MeterCollection
- Direction
- ReprocessLocalEventHubCaptureFilesProgram uses Metering.BaseTypes, so a change to Metering.BaseTypes can break ReprocessLocalEventHubCaptureFilesProgram, while a change to ReprocessLocalEventHubCaptureFilesProgram can't break Metering.BaseTypes.
- Position
- Below the diagonal: ReprocessLocalEventHubCaptureFilesProgram uses a module listed above it, which is the healthy direction.
37→1 Metering.ClientSDK.MeteringEventHubExtensions uses Metering.BaseTypes.EventHub✕
- Connections
- 2 pairs of types, where a type in Metering.ClientSDK.MeteringEventHubExtensions uses a type in Metering.BaseTypes.EventHub.
- The types involved
Metering.ClientSDK.MeteringEventHubExtensions.MeteringEventHubExtensions→Metering.BaseTypes.EventHub.PartitionIDMetering.ClientSDK.MeteringEventHubExtensions.MeteringEventHubExtensions→Metering.BaseTypes.EventHub.PingMessage
- Direction
- Metering.ClientSDK.MeteringEventHubExtensions uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break Metering.ClientSDK.MeteringEventHubExtensions, while a change to Metering.ClientSDK.MeteringEventHubExtensions can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: Metering.ClientSDK.MeteringEventHubExtensions uses a module listed above it, which is the healthy direction.
37→8 Metering.ClientSDK.MeteringEventHubExtensions uses Metering.BaseTypes✕
- Connections
- 5 pairs of types, where a type in Metering.ClientSDK.MeteringEventHubExtensions uses a type in Metering.BaseTypes.
- The types involved
Metering.ClientSDK.MeteringEventHubExtensions.MeteringEventHubExtensions→Metering.BaseTypes.MarketplaceBatchResponseMetering.ClientSDK.MeteringEventHubExtensions.MeteringEventHubExtensions→Metering.BaseTypes.MarketplaceResourceIdMetering.ClientSDK.MeteringEventHubExtensions.MeteringEventHubExtensions→Metering.BaseTypes.MeteringUpdateEventMetering.ClientSDK.MeteringEventHubExtensions.MeteringEventHubExtensions→Metering.BaseTypes.QuantityMetering.ClientSDK.MeteringEventHubExtensions.MeteringEventHubExtensions→Metering.BaseTypes.SubscriptionCreationInformation
- Direction
- Metering.ClientSDK.MeteringEventHubExtensions uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.ClientSDK.MeteringEventHubExtensions, while a change to Metering.ClientSDK.MeteringEventHubExtensions can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.ClientSDK.MeteringEventHubExtensions uses a module listed above it, which is the healthy direction.
37→28 Metering.ClientSDK.MeteringEventHubExtensions uses Metering.ClientSDK✕
- Connections
- 1 pair of types, where a type in Metering.ClientSDK.MeteringEventHubExtensions uses a type in Metering.ClientSDK.
- The types involved
Metering.ClientSDK.MeteringEventHubExtensions.MeteringEventHubExtensions→Metering.ClientSDK.MeterValue
- Direction
- Metering.ClientSDK.MeteringEventHubExtensions uses Metering.ClientSDK, so a change to Metering.ClientSDK can break Metering.ClientSDK.MeteringEventHubExtensions, while a change to Metering.ClientSDK.MeteringEventHubExtensions can't break Metering.ClientSDK.
- Position
- Below the diagonal: Metering.ClientSDK.MeteringEventHubExtensions uses a module listed above it, which is the healthy direction.
38→1 Metering.Integration.MeterCollectionStore.Naming uses Metering.BaseTypes.EventHub✕
- Connections
- 3 pairs of types, where a type in Metering.Integration.MeterCollectionStore.Naming uses a type in Metering.BaseTypes.EventHub.
- The types involved
Metering.Integration.MeterCollectionStore.Naming.Naming→Metering.BaseTypes.EventHub.EventHubNameMetering.Integration.MeterCollectionStore.Naming.Naming→Metering.BaseTypes.EventHub.MessagePositionMetering.Integration.MeterCollectionStore.Naming.Naming→Metering.BaseTypes.EventHub.PartitionID
- Direction
- Metering.Integration.MeterCollectionStore.Naming uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break Metering.Integration.MeterCollectionStore.Naming, while a change to Metering.Integration.MeterCollectionStore.Naming can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: Metering.Integration.MeterCollectionStore.Naming uses a module listed above it, which is the healthy direction.
38→7 Metering.Integration.MeterCollectionStore.Naming uses Metering.Integration✕
- Connections
- 1 pair of types, where a type in Metering.Integration.MeterCollectionStore.Naming uses a type in Metering.Integration.
- The types involved
Metering.Integration.MeterCollectionStore.Naming.Naming→Metering.Integration.MeteringConnections
- Direction
- Metering.Integration.MeterCollectionStore.Naming uses Metering.Integration, so a change to Metering.Integration can break Metering.Integration.MeterCollectionStore.Naming, while a change to Metering.Integration.MeterCollectionStore.Naming can't break Metering.Integration.
- Position
- Below the diagonal: Metering.Integration.MeterCollectionStore.Naming uses a module listed above it, which is the healthy direction.
38→31 Metering.Integration.MeterCollectionStore.Naming uses Metering.Integration.MeterCollectionStore✕
- Connections
- 1 pair of types, where a type in Metering.Integration.MeterCollectionStore.Naming uses a type in Metering.Integration.MeterCollectionStore.
- The types involved
Metering.Integration.MeterCollectionStore.Naming.Naming→Metering.Integration.MeterCollectionStore.SnapshotName
- Direction
- Metering.Integration.MeterCollectionStore.Naming uses Metering.Integration.MeterCollectionStore, so a change to Metering.Integration.MeterCollectionStore can break Metering.Integration.MeterCollectionStore.Naming, while a change to Metering.Integration.MeterCollectionStore.Naming can't break Metering.Integration.MeterCollectionStore.
- Position
- Below the diagonal: Metering.Integration.MeterCollectionStore.Naming uses a module listed above it, which is the healthy direction.
39→1 Metering.Utils.ManagementUtils uses Metering.BaseTypes.EventHub✕
- Connections
- 3 pairs of types, where a type in Metering.Utils.ManagementUtils uses a type in Metering.BaseTypes.EventHub.
- The types involved
Metering.Utils.ManagementUtils.ManagementUtils→Metering.BaseTypes.EventHub.EventHubEvent`1Metering.Utils.ManagementUtils.ManagementUtils→Metering.BaseTypes.EventHub.MessagePositionMetering.Utils.ManagementUtils.ManagementUtils→Metering.BaseTypes.EventHub.PartitionID
- Direction
- Metering.Utils.ManagementUtils uses Metering.BaseTypes.EventHub, so a change to Metering.BaseTypes.EventHub can break Metering.Utils.ManagementUtils, while a change to Metering.Utils.ManagementUtils can't break Metering.BaseTypes.EventHub.
- Position
- Below the diagonal: Metering.Utils.ManagementUtils uses a module listed above it, which is the healthy direction.
39→7 Metering.Utils.ManagementUtils uses Metering.Integration✕
- Connections
- 2 pairs of types, where a type in Metering.Utils.ManagementUtils uses a type in Metering.Integration.
- The types involved
Metering.Utils.ManagementUtils.ManagementUtils→Metering.Integration.MeteringConfigurationProviderMetering.Utils.ManagementUtils.ManagementUtils→Metering.Integration.MeteringConnections
- Direction
- Metering.Utils.ManagementUtils uses Metering.Integration, so a change to Metering.Integration can break Metering.Utils.ManagementUtils, while a change to Metering.Utils.ManagementUtils can't break Metering.Integration.
- Position
- Below the diagonal: Metering.Utils.ManagementUtils uses a module listed above it, which is the healthy direction.
39→8 Metering.Utils.ManagementUtils uses Metering.BaseTypes✕
- Connections
- 4 pairs of types, where a type in Metering.Utils.ManagementUtils uses a type in Metering.BaseTypes.
- The types involved
Metering.Utils.ManagementUtils.ManagementUtils→Metering.BaseTypes.MarketplaceRequestMetering.Utils.ManagementUtils.ManagementUtils→Metering.BaseTypes.MarketplaceResourceIdMetering.Utils.ManagementUtils.ManagementUtils→Metering.BaseTypes.MeterCollectionMetering.Utils.ManagementUtils.ManagementUtils→Metering.BaseTypes.MeteringUpdateEvent
- Direction
- Metering.Utils.ManagementUtils uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.Utils.ManagementUtils, while a change to Metering.Utils.ManagementUtils can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.Utils.ManagementUtils uses a module listed above it, which is the healthy direction.
39→33 Metering.Utils.ManagementUtils uses Metering.Utils✕
- Connections
- 1 pair of types, where a type in Metering.Utils.ManagementUtils uses a type in Metering.Utils.
- The types involved
Metering.Utils.ManagementUtils.ManagementUtils→Metering.Utils.ReportingOverview
- Direction
- Metering.Utils.ManagementUtils uses Metering.Utils, so a change to Metering.Utils can break Metering.Utils.ManagementUtils, while a change to Metering.Utils.ManagementUtils can't break Metering.Utils.
- Position
- Below the diagonal: Metering.Utils.ManagementUtils uses a module listed above it, which is the healthy direction.
40→8 Metering.Utils.ReportingOverviewModule uses Metering.BaseTypes✕
- Connections
- 2 pairs of types, where a type in Metering.Utils.ReportingOverviewModule uses a type in Metering.BaseTypes.
- The types involved
Metering.Utils.ReportingOverviewModule.ReportingOverviewModule→Metering.BaseTypes.ApplicationInternalMeterNameMetering.Utils.ReportingOverviewModule.ReportingOverviewModule→Metering.BaseTypes.BillingDimension
- Direction
- Metering.Utils.ReportingOverviewModule uses Metering.BaseTypes, so a change to Metering.BaseTypes can break Metering.Utils.ReportingOverviewModule, while a change to Metering.Utils.ReportingOverviewModule can't break Metering.BaseTypes.
- Position
- Below the diagonal: Metering.Utils.ReportingOverviewModule uses a module listed above it, which is the healthy direction.
40→33 Metering.Utils.ReportingOverviewModule uses Metering.Utils✕
- Connections
- 1 pair of types, where a type in Metering.Utils.ReportingOverviewModule uses a type in Metering.Utils.
- The types involved
Metering.Utils.ReportingOverviewModule.ReportingOverviewModule→Metering.Utils.ReportingOverview
- Direction
- Metering.Utils.ReportingOverviewModule uses Metering.Utils, so a change to Metering.Utils can break Metering.Utils.ReportingOverviewModule, while a change to Metering.Utils.ReportingOverviewModule can't break Metering.Utils.
- Position
- Below the diagonal: Metering.Utils.ReportingOverviewModule 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 |
|---|---|---|
| A02:2025 — Security Misconfiguration | 54 | High / Critical |
| A05:2025 — Injection | 21 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
| A07:2025 — Authentication Failures | 3 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED; Log through `ILogger` (Microsoft.Extensions.Logging, or Serilog with a JSON sink) at meaningful points in the programs and services you run; Resolve the 38 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (3), Startup.cs (3), EventHubCaptureProcessor.cs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +7.8 pts | Low | REDACTED Scanning |
| Log through `ILogger` (Microsoft.Extensions.Logging, or Serilog with a JSON sink) at meaningful points in the programs and services you run. | +7.7 pts | Medium | Observability |
| Resolve the 38 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (3), Startup.cs (3), EventHubCaptureProcessor.cs. | +4.2 pts | Medium | Knowledge Freshness |
| Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically. | +4.0 pts | Medium | Deployment & Rollback |
| Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with EventHubObservableClient.cs. | +1.3 pts | Low | Explicit Debt |
| Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Error.cshtml.cs. | +1.3 pts | Low | Explicit Debt |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.2 pts | Medium | Architecture documentation |
| Reconcile the README with reality: README.md links to `./Metering.BaseTypes/InternalUsageEvent.fs`, but `Metering.BaseTypes/InternalUsageEvent.fs` does not exist; docs/Developer-Setup.md names .NET 6, but the projects target .NET 7, 8; docs/Metering.SharedResourceBroker/README.md links to `./docs/img/main.png`, but `docs/Metering.SharedResourceBroker/docs/img/main.png` does not exist; docs/Metering.SharedResourceBroker/README.md links to `./docs/img/usage.png`, but `docs/Metering.SharedResourceBroker/docs/img/usage.png` does not exist; docs/Metering.SharedResourceBroker/README.md links to `./docs/img/deprovision.png`, but `docs/Metering.SharedResourceBroker/docs/img/deprovision.png` does not exist. | +1.9 pts | Medium | Documentation accuracy |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | IaC & Container Security: Critical IaC: REDACTED |
| REDACTED | 0.8 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Metering.EventHub/EventHubObservableClient.cs | 2.9 | Mixed | Explicit Debt: EmptyCatchBlock |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.1 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.3 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.4 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.2 | Near-clean | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| src/Metering.RuntimeCS/PartitionIDHash.cs | 7.4 | Near-clean | Cyclomatic Complexity: PartitionIDHashExtensions.DeterminePartitionId (cyclomatic 20) |
| src/Metering.Runtime/EventHubCaptureProcessor.fs | 7.4 | Near-clean | Code Duplication: Duplicated block (39 lines × 2) |
| src/Demos/DemoWebApp/Pages/Error.cshtml.cs | 7.6 | Near-clean | Explicit Debt: WriteOnlyPrivateField |
| src/Demos/SaaSIntegration/src/LandingPage/Controllers/HomeController.cs | 7.8 | Near-clean | Code Duplication: Edited copy of a member (27 corresponding lines) |
| src/Demos/SaaSIntegration/src/MeteredPage/Controllers/HomeController.cs | 7.8 | Near-clean | Code Duplication: Edited copy of a member (21 corresponding lines) |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
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 43 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 43 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, 166 of 183 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: 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 ≈ 21% of production LoC (1,648 test / 7,845 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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- 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 (12 contributor(s) across 862 commit(s) sampled, automation and bot accounts excluded). One of them holds 89% of the history; the other 11 hold 1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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/Metering.Runtime/Metering.Runtime.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 6 deducted marker(s) and the 0.6/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (4,424 lines, 56% 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.
- 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.
- 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (src/docker-compose/docker-compose.override.yml). compose up failed (exit 15 — the compose project is invalid) — empty compose file; runtime evidence skipped.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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.
- P10 Library API & versioning — 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. Library API & versioning could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
- P11 BDD / executable specs — 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. BDD / executable specs could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
- P7 Outbound HTTP resilience — 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. Outbound HTTP resilience could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
- P8 Schema migrations — 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. Schema migrations could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X23 Unguarded diagnostic materialisation — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/Demos/SaaSIntegration/src/PublisherPortal/PublisherPortal.csproj, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was EventHubObservableClient.CreateInternal at 23.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with EventHubObservableClient.CreateInternal (cyclomatic 23), PartitionIDHashExtensions.DeterminePartitionId (cyclomatic 20). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was EventHubObservableClient.CreateInternal at 27.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with EventHubObservableClient.CreateInternal (cognitive 27). — Refactoring it lifts Cognitive Complexity from 9.3 to about 10.0/10.
D3 · God Classes
3 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with EventHubObservableClient.cs, PartitionIDHash.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with Json.fs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
12 duplicated block group(s) detected. 5.9 % of the production lines (462 of 7,845) are in a reported copy. A further 5 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 8 of the 17 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Duplicated block (25 lines × 2) finding(s) in Code Duplication — start with EventHubObservableClient.cs, Plan.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with MeteringValue.fs, ClientSDK.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (31 corresponding lines) finding(s) in Code Duplication — start with EventHubObservableClient.cs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
15 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling — start with Metering.EventHub.csproj. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 8 classes have LCOM4 above 3.
D13 · REDACTED Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D14 · License Compliance
0 of 291 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 40 direct `PackageReference`(s), and 210 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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
6 deducted debt markers + unmeasured dead symbols across 3421 LoC in the .NET projects (0.6/KLoC) → score 8.9. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (56% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Error.cshtml.cs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with EventHubObservableClient.cs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 CommentedOutCode finding(s) in Explicit Debt — start with DemoClientProgram.cs, MeterModels.cs, NotificationSchemas.cs. — One of this dimension's main actionable groups (4 warning-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 27 document(s) read across 16 unit(s).
D26 · Project Cohesion
2 of 15 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Metering.RuntimeCS.csproj, Metering.EventHub.csproj. — One of this dimension's main actionable groups (2 recommendation-level).
D27 · Navigability
88 % of calls cross a namespace and 6 % go through an interface, but 75 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
21 finding(s): 0 critical, 12 high, 9 medium, 0 low. 11 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 4 file(s) — `src/Demos/SaaSIntegration/src/PublisherPortal/Services/ProcessLatestMetered.cs` (lines 17–113), `src/Metering.Tests/data/BusinessLogic/CleanUpUnprocessableMessages/001--event--2021-11-04--16-12-27--string-junk.json`, `src/Metering.Tests/data/BusinessLogic/CleanUpUnprocessableMessages/002--event--2021-11-04--16-12-28--binary-junk.json`, `src/Metering.Tests/data/BusinessLogic/CleanUpUnprocessableMessages/003--event--2021-11-04--16-12-29--binary-junk.json` — 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. In 1 of those file(s) — `src/Demos/SaaSIntegration/src/PublisherPortal/Services/ProcessLatestMetered.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 3 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 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- No action in Static Analysis (SAST) — all 11 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 (11 issue-level, 0 of them charged here).
D31 · IaC & Container Security
54 finding(s): 3 critical, 3 high, 44 medium, 4 low.
What to do
- Resolve the 44 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (21), REDACTED (6), REDACTED (5). — One of this dimension's main actionable groups (44 warning-level).
- Resolve the 3 Critical IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
D34 · Knowledge Freshness
41 of 41 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Metering.BaseTypes/Json.fs. Counted over 41 of the 111 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 38 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (3), Startup.cs (3), EventHubCaptureProcessor.cs. — One of this dimension's main actionable groups (38 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with Json.fs, EventHubObservableClient.cs, EventHubCaptureProcessor.fs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 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. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 23 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 2 End-of-life runtime finding(s) in Platform End-of-Life — start with Metering.BusinessLogicDemoApp.fsproj, PublisherPortal.csproj. — One of this dimension's main actionable groups (2 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
C2 · Access Controls
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- README.md links to `./Metering.BaseTypes/InternalUsageEvent.fs`, but `Metering.BaseTypes/InternalUsageEvent.fs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:129
- docs/Developer-Setup.md names .NET 6, but the projects target .NET 7, 8. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Developer-Setup.md:7
- docs/Metering.SharedResourceBroker/README.md links to `./docs/img/main.png`, but `docs/Metering.SharedResourceBroker/docs/img/main.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Metering.SharedResourceBroker/README.md:68
- docs/Metering.SharedResourceBroker/README.md links to `./docs/img/usage.png`, but `docs/Metering.SharedResourceBroker/docs/img/usage.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Metering.SharedResourceBroker/README.md:80
- docs/Metering.SharedResourceBroker/README.md links to `./docs/img/deprovision.png`, but `docs/Metering.SharedResourceBroker/docs/img/deprovision.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Metering.SharedResourceBroker/README.md:94
What to do
- Reconcile the README with reality: README.md links to `./Metering.BaseTypes/InternalUsageEvent.fs`, but `Metering.BaseTypes/InternalUsageEvent.fs` does not exist; docs/Developer-Setup.md names .NET 6, but the projects target .NET 7, 8; docs/Metering.SharedResourceBroker/README.md links to `./docs/img/main.png`, but `docs/Metering.SharedResourceBroker/docs/img/main.png` does not exist; docs/Metering.SharedResourceBroker/README.md links to `./docs/img/usage.png`, but `docs/Metering.SharedResourceBroker/docs/img/usage.png` does not exist; docs/Metering.SharedResourceBroker/README.md links to `./docs/img/deprovision.png`, but `docs/Metering.SharedResourceBroker/docs/img/deprovision.png` does not exist.
P1 · CI/CD gates
P2 · Observability
- No logging call was found in the 50 JavaScript/TypeScript, F# production file(s) this check read across 8 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger; F#: Microsoft.Extensions.Logging (ILogger), Serilog, NLog, log4net, Logary) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Log through `ILogger` (Microsoft.Extensions.Logging, or Serilog with a JSON sink) at meaningful points in the programs and services you run.
- Add a health-check endpoint (ASP.NET Core's MapHealthChecks, or a /health route in your Giraffe/Suave app) so orchestrators and load balancers can probe liveness/readiness.
P4 · Deployment & Rollback
- Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
- Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
What to do
- Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
PF3 · Async & latency hygiene
- 1 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
- `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — src/Metering.RuntimeCS/AggregationWorker.cs:186
What to do
- Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
S1 · Web-Security Posture
- MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. — src/Demos/DemoClient/DemoClientProgram.cs:110
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×5) — src/Demos/DemoWebApp/DemoWebAppProgram.cs:6, src/Demos/SaaSIntegration/src/LandingPage/Program.cs:14, src/Demos/SaaSIntegration/src/MeteredPage/Program.cs:14, …
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X20 · Mistyped argument guard
- The guard on line 15 rejects `subscriptionRegistrationRequest` and line 17 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(subscriptionRegistrationRequest.ManagedBy)` is true of a value that is NOT null: it reads a member of `subscriptionRegistrationRequest`, so it can only be evaluated on a non-null `subscriptionRegistrationRequest` (a null one would throw `NullReferenceException` before the guard decided anything). So a caller whose `subscriptionRegistrationRequest` is present but fails that test is told it was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Metering.SharedResourceBroker/SubscriptionRegistrationDTO.cs:17
What to do
- Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
X5 · Nullable reference types
- 7/15 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.
- ~2.0 `!` suppressions per 1k syntax nodes — 10 suppression(s) across the 4964 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
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 | 71% | Strong | Solid. |
| Architecture | 90% | Exemplary | Strongest area. |
| Maturity | 60% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 50% | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 71% | Adequate — gated by D31, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not included — 75 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 — AX1 reached only 44% of this repository's production lines — fsharp (4,424 lines), javascript (12 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — compose up failed (exit 15 — the compose project is invalid) — empty compose file; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D10 Test Quality — ~1648 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
- D12 Dependency Hygiene — Dependency hygiene not 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.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (2069 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (7,845 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
- 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.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 39 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 1 event handler(s); a message-bus package
- ED5 Idempotency — 1 mutating command handler(s)/consumer(s) detected and 1 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — IC1 reached only 44% of this repository's production lines — fsharp (4,424 lines), javascript (12 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- P10 Library API & versioning — Library API & versioning could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- P11 BDD / executable specs — BDD / executable specs could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
- P7 Outbound HTTP resilience — Outbound HTTP resilience could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- P8 Schema migrations — Schema migrations could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- 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.
- X1 Async correctness — X1 reached only 44% of this repository's production lines — fsharp (4,424 lines), javascript (12 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 44% of this repository's production lines — fsharp (4,424 lines), javascript (12 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — X16 reached only 44% of this repository's production lines — fsharp (4,424 lines), javascript (12 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — X18 reached only 44% of this repository's production lines — fsharp (4,424 lines), javascript (12 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — X2 reached only 44% of this repository's production lines — fsharp (4,424 lines), javascript (12 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — X23 reached only 44% of this repository's production lines — fsharp (4,424 lines), javascript (12 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — X27 reached only 44% of this repository's production lines — fsharp (4,424 lines), javascript (12 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — X3 reached only 44% of this repository's production lines — fsharp (4,424 lines), javascript (12 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — X4 reached only 44% of this repository's production lines — fsharp (4,424 lines), javascript (12 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 22 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- WriteOnlyPrivateField src/Demos/DemoWebApp/Pages/Error.cshtml.cs:15
- EmptyCatchBlock src/Metering.EventHub/EventHubObservableClient.cs:355
- REDACTED
- REDACTED
Serious — 91 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- CommentedOutCode src/Demos/DemoClient/DemoClientProgram.cs:37
- CommentedOutCode src/Demos/SaaSIntegration/src/MeteredPage/ViewModels/MeterModels.cs:5
- CommentedOutCode src/Metering.SharedResourceBroker/NotificationSchemas.cs:12
- CommentedOutCode src/Metering.EventHub/EventHubObservableClient.cs:118
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: EventHubObservableClient.CreateInternal src/Metering.EventHub/EventHubObservableClient.cs:32
- MethodTooLong: PartitionIDHashExtensions.DeterminePartitionId src/Metering.RuntimeCS/PartitionIDHash.cs:14
- Duplicated block (25 lines × 2) src/Metering.EventHub/EventHubObservableClient.cs:259
- Duplicated block (25 lines × 2) src/Demos/ManagedAppIntegration/src/MeteredTimerFunction/Definitions/Plan.cs:8
- Duplicated block (11 lines × 2) src/Metering.BaseTypes/MeteringValue.fs:30
- Duplicated block (11 lines × 2) src/Metering.Runtime/ClientSDK.fs:134
- End-of-life runtime: .NET net7.0 src/Demos/Metering.BusinessLogicDemoApp/Metering.BusinessLogicDemoApp.fsproj:4
- End-of-life runtime: .NET net7.0 src/Demos/SaaSIntegration/src/PublisherPortal/PublisherPortal.csproj:3
- Sync-over-async blocking
- Sync-over-async blocking src/Metering.RuntimeCS/AggregationWorker.cs:186
- EventHubObservableClient.CreateInternal (cyclomatic 23) src/Metering.EventHub/EventHubObservableClient.cs:32
- PartitionIDHashExtensions.DeterminePartitionId (cyclomatic 20) src/Metering.RuntimeCS/PartitionIDHash.cs:14
- EventHubObservableClient.CreateInternal (cognitive 27) src/Metering.EventHub/EventHubObservableClient.cs:32
- REDACTED
- REDACTED
- FileTooLong: Metering.BaseTypes/Json.fs src/Metering.BaseTypes/Json.fs
- REDACTED
- REDACTED
- Edited copy of a member (31 corresponding lines) src/Metering.EventHub/EventHubObservableClient.cs:253
- Duplicated block (39 lines × 2) src/Metering.Runtime/EventHubCaptureProcessor.fs:215
- Duplicated block (10 lines × 3) src/Metering.RuntimeCS/PartitionIDHash.cs:95
- Duplicated block (9 lines × 2) src/Metering.Runtime/EventHubCaptureProcessor.fs:82
- Duplicated block (4–7 lines × 3) src/Metering.Runtime/EventHubCaptureProcessor.fs:169
- Duplicated block (8 lines × 2) src/Metering.EventHub/EventHubObservableClient.cs:36
- Edited copy of a member (27 corresponding lines) src/Demos/SaaSIntegration/src/LandingPage/Controllers/HomeController.cs:35
- Edited copy of a member (21 corresponding lines) src/Demos/SaaSIntegration/src/MeteredPage/Controllers/HomeController.cs:37
- Edited copy of a member (9 corresponding lines) REDACTED:132
- Edited copies of one member (3 members, 27+ corresponding lines) src/Demos/SaaSIntegration/src/LandingPage/Startup.cs:74
- Duplicated block (15 lines × 2) src/Demos/SaaSIntegration/src/MeteredPage/Controllers/HomeController.cs:38
- Duplicated block (11–13 lines × 2) src/Demos/SaaSIntegration/src/LandingPage/Controllers/HomeController.cs:35
- Duplicated block (6 lines × 2) src/Demos/SaaSIntegration/src/LandingPage/Program.cs:13
- Off the main sequence: Metering.EventHub src/Metering.EventHub/Metering.EventHub.csproj:1
- No structured logging
- Weak hash algorithm src/Demos/DemoClient/DemoClientProgram.cs:110
- NuGet dependencies are not locked
- Argument guard throws the exception its own condition disproves src/Metering.SharedResourceBroker/SubscriptionRegistrationDTO.cs:17
Minor — 70 finding(s)
- Orphaned file src/Metering.RuntimeCS/EventHubCaptureProcessor.cs:1
- Orphaned file src/Demos/Metering.BusinessLogicDemoApp/BusinessLogicDemoApp.Program.fs:1
- Orphaned file src/Metering.Runtime/MeterCollectionStore.fs:1
- Orphaned file src/Metering.BaseTypes/MeterCollectionLogic.fs:1
- Orphaned file src/Metering.BaseTypes/Meter.fs:1
- Orphaned file src/Tools/ReprocessLocalEventHubCaptureFiles/ReprocessLocalEventHubCaptureFilesProgram.fs:1
- Orphaned file src/Metering.Runtime/ClientSDK.fs:1
- Orphaned file REDACTED:1
- Orphaned file src/Metering.RuntimeCS/AggregationWorker.cs:1
- Orphaned file src/Metering.SharedResourceBroker/ApplicationService.cs:1
- Orphaned file src/Metering.Runtime/MeteringConnections.fs:1
- Orphaned file src/Metering.BaseTypes/MarketplaceStructures.fs:1
- Orphaned file src/Demos/ReadEventHubCaptureSample/ReadEventHubCaptureSampleProgram.fs:1
- Orphaned file src/Demos/DemoClient/DemoClientProgram.cs:1
- Orphaned file src/Metering.BaseTypes/WaterfallBilling.fs:1
- Orphaned file src/Metering.Runtime/InstanceMetadataClient.fs:1
- Orphaned file src/Demos/ManagedAppIntegration/src/MeteredTimerFunction/CronJob.cs:1
- Orphaned file src/Metering.Runtime/Status.fs:1
- Orphaned file src/Metering.RuntimeCS/PartitionIDHash.cs:1
- Orphaned file src/Metering.Runtime/ManagementUtils.fs:1
- Orphaned file src/Metering.BaseTypes/SimpleBilling.fs:1
- Orphaned file src/Metering.BaseTypes/MarketplaceResourceId.fs:1
- Orphaned file src/Metering.BaseTypes/MeteringValue.fs:1
- Orphaned file src/Demos/SaaSIntegration/src/PublisherPortal/Startup.cs:1
- Orphaned file src/Metering.BaseTypes/Quantity.fs:1
- No security response headers detected
- No security response headers detected src/Demos/DemoWebApp/DemoWebAppProgram.cs:6
- No security response headers detected src/Demos/SaaSIntegration/src/LandingPage/Program.cs:14
- No security response headers detected src/Demos/SaaSIntegration/src/MeteredPage/Program.cs:14
- No security response headers detected src/Demos/SaaSIntegration/src/PublisherPortal/Program.cs:14
- No security response headers detected src/Metering.SharedResourceBroker/Program.cs:6
- README/code drift README.md:129
- README/code drift docs/Developer-Setup.md:7
- README/code drift docs/Metering.SharedResourceBroker/README.md:68
- README/code drift docs/Metering.SharedResourceBroker/README.md:80
- README/code drift docs/Metering.SharedResourceBroker/README.md:94
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Most significant orphaned file src/Metering.BaseTypes/Json.fs:1
- Most significant orphaned file src/Metering.EventHub/EventHubObservableClient.cs:1
- Most significant orphaned file src/Metering.Runtime/EventHubCaptureProcessor.fs:1
- Projects may be oversized for their cohesion src/Metering.RuntimeCS/Metering.RuntimeCS.csproj:1
- Projects may be oversized for their cohesion src/Metering.EventHub/Metering.EventHub.csproj:1
- REDACTED
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No rollback/health safety
- No release approval gate
- Nullable reference types not enabled everywhere
- Null-forgiving operator (`!`) suppressions override nullable warnings
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-8fa391c8b9b544188baed4f1485ebfbd/history.json --exit-code 0 --source . | 1 | 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-8fa391c8b9b544188baed4f1485ebfbd/tree.json --exit-code 0 --source . | 1 | 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 . | 21 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 54 | 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 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-8c1b50d8985e4de889cc647bdc000ae7 | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Email — 1 field(s)
- IndexViewModel.Email src/Demos/SaaSIntegration/src/LandingPage/ViewModels/Home/IndexViewModel.cs:8