Executive summary
aws/aws-sdk-ruby falls short of our standard for production, in part because 190 passwords or keys sit in the current code. It scores 62 out of 100 and is rated Adequate, and 201 of its 204 critical findings are security problems.
Production Readiness, at 56, is the weakest lens and counts most in the score. The best first step is adding automated security scanning, worth about 4 points. Documenting the recovery plan comes next, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 66.
190 passwords or keys are open to anyone who can read the repository. Eleven weaknesses in the code could be used by an attacker. Replacing each exposed password or key and fixing the weaknesses the scanner points to would close both risks. The two pages or frames without a title need a descriptive title.
The product code is 5,064,543 lines, about €8,000,000 to rebuild.
If Production Readiness rose from 56 to 70, the lowest score rated Strong, the score would rise from 62 to about 66.
New since the last survey: 131 findings
- Cohesion (LCOM4) · Low cohesion: HttpsLoopback (LCOM4 4) benchmarks/ops_cpu_sec/lib/https_loopback.rb
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
Rebuild cost: about €8,000,000 · Estimate
| Cost to rebuild | €2,700,000 to €13,000,000, for 44,303 to 140,548 hours of work, about 55.0 person-years for 32 to 105 engineers |
|---|---|
| Difficulty of the problem | High, 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.9 at a score of 62. 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 | Very large: 5,064,543 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 Aws.Errors | 2 Aws.Structure | 3 Aws.Waiters | 4 Seahorse | 5 Seahorse.Client | 6 Seahorse.Model | 7 Aws | 8 Aws.ACM.Types | 9 Aws.AccessAnalyzer.Types | 10 Aws.AppMesh.Types | 11 Aws.Bedrock.Types | 12 Aws.BedrockAgent.Types | 13 Aws.BedrockAgentCore.Types | 14 Aws.BedrockAgentCoreControl.Types | 15 Aws.BedrockAgentRuntime.Types | 16 Aws.BedrockRuntime.Types | 17 Aws.CleanRooms.Types | 18 Aws.Connect.Types | 19 Aws.ConnectCampaignsV2.Types | 20 Aws.ConnectCases.Types | 21 Aws.DataZone.Types | 22 Aws.Deadline.Types | 23 Aws.DevOpsAgent.Types | 24 Aws.GroundStation.Types | 25 Aws.MailManager.Types | 26 Aws.MainframeModernization.Types | 27 Aws.MediaConnect.Types | 28 Aws.NetworkSecurityManager.Types | 29 Aws.PaymentCryptographyData.Types | 30 Aws.QBusiness.Types | 31 Aws.QConnect.Types | 32 Aws.QuickSight.Types | 33 Aws.Resiliencehubv2.Types | 34 Aws.Resources | 35 Aws.SSMIncidents.Types | 36 Aws.SageMaker.Types | 37 Aws.SecurityAgent.Types | 38 Aws.SecurityHub.Types | 39 Aws.Transfer.Types | 40 Aws.VerifiedPermissions.Types |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Aws.Errors | ||||||||||||||||||||||||||||||||||||||||
| 2 Aws.Structure | ||||||||||||||||||||||||||||||||||||||||
| 3 Aws.Waiters | ||||||||||||||||||||||||||||||||||||||||
| 4 Seahorse | ||||||||||||||||||||||||||||||||||||||||
| 5 Seahorse.Client | ||||||||||||||||||||||||||||||||||||||||
| 6 Seahorse.Model | ||||||||||||||||||||||||||||||||||||||||
| 7 Aws | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 8 Aws.ACM.Types | 12 | 136 | ||||||||||||||||||||||||||||||||||||||
| 9 Aws.AccessAnalyzer.Types | 10 | 168 | ||||||||||||||||||||||||||||||||||||||
| 10 Aws.AppMesh.Types | 20 | 228 | ||||||||||||||||||||||||||||||||||||||
| 11 Aws.Bedrock.Types | 32 | 484 | ||||||||||||||||||||||||||||||||||||||
| 12 Aws.BedrockAgent.Types | 21 | 439 | ||||||||||||||||||||||||||||||||||||||
| 13 Aws.BedrockAgentCore.Types | 58 | 411 | ||||||||||||||||||||||||||||||||||||||
| 14 Aws.BedrockAgentCoreControl.Types | 85 | 780 | ||||||||||||||||||||||||||||||||||||||
| 15 Aws.BedrockAgentRuntime.Types | 39 | 372 | ||||||||||||||||||||||||||||||||||||||
| 16 Aws.BedrockRuntime.Types | 30 | 189 | ||||||||||||||||||||||||||||||||||||||
| 17 Aws.CleanRooms.Types | 40 | 447 | ||||||||||||||||||||||||||||||||||||||
| 18 Aws.Connect.Types | 20 | 1361 | ||||||||||||||||||||||||||||||||||||||
| 19 Aws.ConnectCampaignsV2.Types | 13 | 130 | ||||||||||||||||||||||||||||||||||||||
| 20 Aws.ConnectCases.Types | 19 | 174 | ||||||||||||||||||||||||||||||||||||||
| 21 Aws.DataZone.Types | 51 | 746 | ||||||||||||||||||||||||||||||||||||||
| 22 Aws.Deadline.Types | 18 | 429 | ||||||||||||||||||||||||||||||||||||||
| 23 Aws.DevOpsAgent.Types | 22 | 287 | ||||||||||||||||||||||||||||||||||||||
| 24 Aws.GroundStation.Types | 13 | 164 | ||||||||||||||||||||||||||||||||||||||
| 25 Aws.MailManager.Types | 21 | 208 | ||||||||||||||||||||||||||||||||||||||
| 26 Aws.MainframeModernization.Types | 10 | 133 | ||||||||||||||||||||||||||||||||||||||
| 27 Aws.MediaConnect.Types | 34 | 437 | ||||||||||||||||||||||||||||||||||||||
| 28 Aws.NetworkSecurityManager.Types | 10 | 143 | ||||||||||||||||||||||||||||||||||||||
| 29 Aws.PaymentCryptographyData.Types | 18 | 105 | ||||||||||||||||||||||||||||||||||||||
| 30 Aws.QBusiness.Types | 16 | 325 | ||||||||||||||||||||||||||||||||||||||
| 31 Aws.QConnect.Types | 31 | 415 | ||||||||||||||||||||||||||||||||||||||
| 32 Aws.QuickSight.Types | 13 | 1770 | ||||||||||||||||||||||||||||||||||||||
| 33 Aws.Resiliencehubv2.Types | 10 | 285 | ||||||||||||||||||||||||||||||||||||||
| 34 Aws.Resources | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 Aws.SSMIncidents.Types | 13 | 109 | ||||||||||||||||||||||||||||||||||||||
| 36 Aws.SageMaker.Types | 15 | 1580 | ||||||||||||||||||||||||||||||||||||||
| 37 Aws.SecurityAgent.Types | 11 | 333 | ||||||||||||||||||||||||||||||||||||||
| 38 Aws.SecurityHub.Types | 15 | 1056 | ||||||||||||||||||||||||||||||||||||||
| 39 Aws.Transfer.Types | 10 | 215 | ||||||||||||||||||||||||||||||||||||||
| 40 Aws.VerifiedPermissions.Types | 20 | 156 |
7→5 Aws uses Seahorse.Client✕
- Connections
- 1 pair of types, where a type in Aws uses a type in Seahorse.Client.
- The types involved
Aws.ErrorHandler→Seahorse.Client.Handler
- Direction
- Aws uses Seahorse.Client, so a change to Seahorse.Client can break Aws, while a change to Aws can't break Seahorse.Client.
- Position
- Below the diagonal: Aws uses a module listed above it, which is the healthy direction.
7→6 Aws uses Seahorse.Model✕
- Connections
- 2 pairs of types, where a type in Aws uses a type in Seahorse.Model.
- The types involved
Aws.ParamConverter→Seahorse.Model.ShapesAws.ParamValidator→Seahorse.Model.Shapes
- Direction
- Aws uses Seahorse.Model, so a change to Seahorse.Model can break Aws, while a change to Aws can't break Seahorse.Model.
- Position
- Below the diagonal: Aws uses a module listed above it, which is the healthy direction.
8→2 Aws.ACM.Types uses Aws.Structure✕
- Connections
- 12 pairs of types, where a type in Aws.ACM.Types uses a type in Aws.Structure.
- The types involved
Aws.ACM.Types.AcmCertificateMetadataFilter→Aws.Structure.UnionAws.ACM.Types.CertificateAuthority→Aws.Structure.UnionAws.ACM.Types.CertificateFilter→Aws.Structure.UnionAws.ACM.Types.CertificateFilterStatement→Aws.Structure.UnionAws.ACM.Types.CertificateMetadata→Aws.Structure.UnionAws.ACM.Types.GeneralName→Aws.Structure.UnionAws.ACM.Types.PrevalidationDetails→Aws.Structure.UnionAws.ACM.Types.PrevalidationOptions→Aws.Structure.UnionAws.ACM.Types.SubjectAlternativeNameFilter→Aws.Structure.UnionAws.ACM.Types.SubjectFilter→Aws.Structure.UnionAws.ACM.Types.ValidationChallenge→Aws.Structure.UnionAws.ACM.Types.X509AttributeFilter→Aws.Structure.Union
- Direction
- Aws.ACM.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.ACM.Types, while a change to Aws.ACM.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.ACM.Types uses a module listed above it, which is the healthy direction.
8→7 Aws.ACM.Types uses Aws✕
- Connections
- 136 pairs of types, where a type in Aws.ACM.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.ACM.Types.AccessDeniedException→Aws.StructureAws.ACM.Types.AcmCertificateMetadata→Aws.StructureAws.ACM.Types.AcmCertificateMetadataFilter→Aws.StructureAws.ACM.Types.AcmeAccount→Aws.StructureAws.ACM.Types.AcmeAccountSummary→Aws.StructureAws.ACM.Types.AcmeDomainValidation→Aws.StructureAws.ACM.Types.AcmeDomainValidationSummary→Aws.StructureAws.ACM.Types.AcmeEndpoint→Aws.StructureAws.ACM.Types.AcmeEndpointSummary→Aws.StructureAws.ACM.Types.AcmeExternalAccountBinding→Aws.StructureAws.ACM.Types.AcmeExternalAccountBindingSummary→Aws.StructureAws.ACM.Types.AddTagsToCertificateRequest→Aws.StructureAws.ACM.Types.CertificateAuthority→Aws.StructureAws.ACM.Types.CertificateDetail→Aws.StructureAws.ACM.Types.CertificateFilter→Aws.StructureAws.ACM.Types.CertificateFilterStatement→Aws.StructureAws.ACM.Types.CertificateMetadata→Aws.StructureAws.ACM.Types.CertificateOptions→Aws.StructureAws.ACM.Types.CertificateSearchResult→Aws.StructureAws.ACM.Types.CertificateSummary→Aws.StructureAws.ACM.Types.CommonNameFilter→Aws.StructureAws.ACM.Types.ConflictException→Aws.StructureAws.ACM.Types.CreateAcmeDomainValidationRequest→Aws.StructureAws.ACM.Types.CreateAcmeDomainValidationResponse→Aws.StructureAws.ACM.Types.CreateAcmeEndpointRequest→Aws.Structure
- Direction
- Aws.ACM.Types uses Aws, so a change to Aws can break Aws.ACM.Types, while a change to Aws.ACM.Types can't break Aws.
- Position
- Below the diagonal: Aws.ACM.Types uses a module listed above it, which is the healthy direction.
9→2 Aws.AccessAnalyzer.Types uses Aws.Structure✕
- Connections
- 10 pairs of types, where a type in Aws.AccessAnalyzer.Types uses a type in Aws.Structure.
- The types involved
Aws.AccessAnalyzer.Types.AclGrantee→Aws.Structure.UnionAws.AccessAnalyzer.Types.AnalyzerConfiguration→Aws.Structure.UnionAws.AccessAnalyzer.Types.Configuration→Aws.Structure.UnionAws.AccessAnalyzer.Types.FindingDetails→Aws.Structure.UnionAws.AccessAnalyzer.Types.FindingsStatistics→Aws.Structure.UnionAws.AccessAnalyzer.Types.NetworkOriginConfiguration→Aws.Structure.UnionAws.AccessAnalyzer.Types.PathElement→Aws.Structure.UnionAws.AccessAnalyzer.Types.RdsDbClusterSnapshotAttributeValue→Aws.Structure.UnionAws.AccessAnalyzer.Types.RdsDbSnapshotAttributeValue→Aws.Structure.UnionAws.AccessAnalyzer.Types.RecommendedStep→Aws.Structure.Union
- Direction
- Aws.AccessAnalyzer.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.AccessAnalyzer.Types, while a change to Aws.AccessAnalyzer.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.AccessAnalyzer.Types uses a module listed above it, which is the healthy direction.
9→7 Aws.AccessAnalyzer.Types uses Aws✕
- Connections
- 168 pairs of types, where a type in Aws.AccessAnalyzer.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.AccessAnalyzer.Types.Access→Aws.StructureAws.AccessAnalyzer.Types.AccessDeniedException→Aws.StructureAws.AccessAnalyzer.Types.AccessPreview→Aws.StructureAws.AccessAnalyzer.Types.AccessPreviewFinding→Aws.StructureAws.AccessAnalyzer.Types.AccessPreviewStatusReason→Aws.StructureAws.AccessAnalyzer.Types.AccessPreviewSummary→Aws.StructureAws.AccessAnalyzer.Types.AclGrantee→Aws.StructureAws.AccessAnalyzer.Types.AnalysisRule→Aws.StructureAws.AccessAnalyzer.Types.AnalysisRuleCriteria→Aws.StructureAws.AccessAnalyzer.Types.AnalyzedResource→Aws.StructureAws.AccessAnalyzer.Types.AnalyzedResourceSummary→Aws.StructureAws.AccessAnalyzer.Types.AnalyzerConfiguration→Aws.StructureAws.AccessAnalyzer.Types.AnalyzerSummary→Aws.StructureAws.AccessAnalyzer.Types.ApplyArchiveRuleRequest→Aws.StructureAws.AccessAnalyzer.Types.ArchiveRuleSummary→Aws.StructureAws.AccessAnalyzer.Types.CancelPolicyGenerationRequest→Aws.StructureAws.AccessAnalyzer.Types.CancelPolicyGenerationResponse→Aws.EmptyStructureAws.AccessAnalyzer.Types.CheckAccessNotGrantedRequest→Aws.StructureAws.AccessAnalyzer.Types.CheckAccessNotGrantedResponse→Aws.StructureAws.AccessAnalyzer.Types.CheckNoNewAccessRequest→Aws.StructureAws.AccessAnalyzer.Types.CheckNoNewAccessResponse→Aws.StructureAws.AccessAnalyzer.Types.CheckNoPublicAccessRequest→Aws.StructureAws.AccessAnalyzer.Types.CheckNoPublicAccessResponse→Aws.StructureAws.AccessAnalyzer.Types.CloudTrailDetails→Aws.StructureAws.AccessAnalyzer.Types.CloudTrailProperties→Aws.Structure
- Direction
- Aws.AccessAnalyzer.Types uses Aws, so a change to Aws can break Aws.AccessAnalyzer.Types, while a change to Aws.AccessAnalyzer.Types can't break Aws.
- Position
- Below the diagonal: Aws.AccessAnalyzer.Types uses a module listed above it, which is the healthy direction.
10→2 Aws.AppMesh.Types uses Aws.Structure✕
- Connections
- 20 pairs of types, where a type in Aws.AppMesh.Types uses a type in Aws.Structure.
- The types involved
Aws.AppMesh.Types.AccessLog→Aws.Structure.UnionAws.AppMesh.Types.Backend→Aws.Structure.UnionAws.AppMesh.Types.ClientTlsCertificate→Aws.Structure.UnionAws.AppMesh.Types.GrpcMetadataMatchMethod→Aws.Structure.UnionAws.AppMesh.Types.GrpcRouteMetadataMatchMethod→Aws.Structure.UnionAws.AppMesh.Types.HeaderMatchMethod→Aws.Structure.UnionAws.AppMesh.Types.ListenerTimeout→Aws.Structure.UnionAws.AppMesh.Types.ListenerTlsCertificate→Aws.Structure.UnionAws.AppMesh.Types.ListenerTlsValidationContextTrust→Aws.Structure.UnionAws.AppMesh.Types.LoggingFormat→Aws.Structure.UnionAws.AppMesh.Types.ServiceDiscovery→Aws.Structure.UnionAws.AppMesh.Types.TlsValidationContextTrust→Aws.Structure.UnionAws.AppMesh.Types.VirtualGatewayAccessLog→Aws.Structure.UnionAws.AppMesh.Types.VirtualGatewayClientTlsCertificate→Aws.Structure.UnionAws.AppMesh.Types.VirtualGatewayConnectionPool→Aws.Structure.UnionAws.AppMesh.Types.VirtualGatewayListenerTlsCertificate→Aws.Structure.UnionAws.AppMesh.Types.VirtualGatewayListenerTlsValidationContextTrust→Aws.Structure.UnionAws.AppMesh.Types.VirtualGatewayTlsValidationContextTrust→Aws.Structure.UnionAws.AppMesh.Types.VirtualNodeConnectionPool→Aws.Structure.UnionAws.AppMesh.Types.VirtualServiceProvider→Aws.Structure.Union
- Direction
- Aws.AppMesh.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.AppMesh.Types, while a change to Aws.AppMesh.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.AppMesh.Types uses a module listed above it, which is the healthy direction.
10→7 Aws.AppMesh.Types uses Aws✕
- Connections
- 228 pairs of types, where a type in Aws.AppMesh.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.AppMesh.Types.AccessLog→Aws.StructureAws.AppMesh.Types.AwsCloudMapInstanceAttribute→Aws.StructureAws.AppMesh.Types.AwsCloudMapServiceDiscovery→Aws.StructureAws.AppMesh.Types.Backend→Aws.StructureAws.AppMesh.Types.BackendDefaults→Aws.StructureAws.AppMesh.Types.BadRequestException→Aws.StructureAws.AppMesh.Types.ClientPolicy→Aws.StructureAws.AppMesh.Types.ClientPolicyTls→Aws.StructureAws.AppMesh.Types.ClientTlsCertificate→Aws.StructureAws.AppMesh.Types.ConflictException→Aws.StructureAws.AppMesh.Types.CreateGatewayRouteInput→Aws.StructureAws.AppMesh.Types.CreateGatewayRouteOutput→Aws.StructureAws.AppMesh.Types.CreateMeshInput→Aws.StructureAws.AppMesh.Types.CreateMeshOutput→Aws.StructureAws.AppMesh.Types.CreateRouteInput→Aws.StructureAws.AppMesh.Types.CreateRouteOutput→Aws.StructureAws.AppMesh.Types.CreateVirtualGatewayInput→Aws.StructureAws.AppMesh.Types.CreateVirtualGatewayOutput→Aws.StructureAws.AppMesh.Types.CreateVirtualNodeInput→Aws.StructureAws.AppMesh.Types.CreateVirtualNodeOutput→Aws.StructureAws.AppMesh.Types.CreateVirtualRouterInput→Aws.StructureAws.AppMesh.Types.CreateVirtualRouterOutput→Aws.StructureAws.AppMesh.Types.CreateVirtualServiceInput→Aws.StructureAws.AppMesh.Types.CreateVirtualServiceOutput→Aws.StructureAws.AppMesh.Types.DeleteGatewayRouteInput→Aws.Structure
- Direction
- Aws.AppMesh.Types uses Aws, so a change to Aws can break Aws.AppMesh.Types, while a change to Aws.AppMesh.Types can't break Aws.
- Position
- Below the diagonal: Aws.AppMesh.Types uses a module listed above it, which is the healthy direction.
11→2 Aws.Bedrock.Types uses Aws.Structure✕
- Connections
- 32 pairs of types, where a type in Aws.Bedrock.Types uses a type in Aws.Structure. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.Bedrock.Types.AutomatedEvaluationCustomMetricSource→Aws.Structure.UnionAws.Bedrock.Types.AutomatedReasoningCheckFinding→Aws.Structure.UnionAws.Bedrock.Types.AutomatedReasoningPolicyAnnotatedContent→Aws.Structure.UnionAws.Bedrock.Types.AutomatedReasoningPolicyAnnotation→Aws.Structure.UnionAws.Bedrock.Types.AutomatedReasoningPolicyBuildResultAssets→Aws.Structure.UnionAws.Bedrock.Types.AutomatedReasoningPolicyBuildStepContext→Aws.Structure.UnionAws.Bedrock.Types.AutomatedReasoningPolicyDefinitionElement→Aws.Structure.UnionAws.Bedrock.Types.AutomatedReasoningPolicyGenerateFidelityReportContent→Aws.Structure.UnionAws.Bedrock.Types.AutomatedReasoningPolicyMutation→Aws.Structure.UnionAws.Bedrock.Types.AutomatedReasoningPolicyTypeValueAnnotation→Aws.Structure.UnionAws.Bedrock.Types.AutomatedReasoningPolicyWorkflowTypeContent→Aws.Structure.UnionAws.Bedrock.Types.CustomModelDataSource→Aws.Structure.UnionAws.Bedrock.Types.CustomizationConfig→Aws.Structure.UnionAws.Bedrock.Types.EndpointConfig→Aws.Structure.UnionAws.Bedrock.Types.EvaluationConfig→Aws.Structure.UnionAws.Bedrock.Types.EvaluationDatasetLocation→Aws.Structure.UnionAws.Bedrock.Types.EvaluationInferenceConfig→Aws.Structure.UnionAws.Bedrock.Types.EvaluationModelConfig→Aws.Structure.UnionAws.Bedrock.Types.EvaluationPrecomputedRagSourceConfig→Aws.Structure.UnionAws.Bedrock.Types.EvaluatorModelConfig→Aws.Structure.UnionAws.Bedrock.Types.GraderConfig→Aws.Structure.UnionAws.Bedrock.Types.InferenceProfileModelSource→Aws.Structure.UnionAws.Bedrock.Types.InvocationLogSource→Aws.Structure.UnionAws.Bedrock.Types.KnowledgeBaseConfig→Aws.Structure.UnionAws.Bedrock.Types.ModelDataSource→Aws.Structure.Union
- Direction
- Aws.Bedrock.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.Bedrock.Types, while a change to Aws.Bedrock.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.Bedrock.Types uses a module listed above it, which is the healthy direction.
11→7 Aws.Bedrock.Types uses Aws✕
- Connections
- 484 pairs of types, where a type in Aws.Bedrock.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.Bedrock.Types.AccessDeniedException→Aws.StructureAws.Bedrock.Types.AccountEnforcedGuardrailInferenceInputConfiguration→Aws.StructureAws.Bedrock.Types.AccountEnforcedGuardrailOutputConfiguration→Aws.StructureAws.Bedrock.Types.AdvancedPromptOptimizationInputConfig→Aws.StructureAws.Bedrock.Types.AdvancedPromptOptimizationJobSummary→Aws.StructureAws.Bedrock.Types.AdvancedPromptOptimizationOutputConfig→Aws.StructureAws.Bedrock.Types.AgreementAvailability→Aws.StructureAws.Bedrock.Types.AutomatedEvaluationConfig→Aws.StructureAws.Bedrock.Types.AutomatedEvaluationCustomMetricConfig→Aws.StructureAws.Bedrock.Types.AutomatedEvaluationCustomMetricSource→Aws.StructureAws.Bedrock.Types.AutomatedReasoningCheckFinding→Aws.StructureAws.Bedrock.Types.AutomatedReasoningCheckImpossibleFinding→Aws.StructureAws.Bedrock.Types.AutomatedReasoningCheckInputTextReference→Aws.StructureAws.Bedrock.Types.AutomatedReasoningCheckInvalidFinding→Aws.StructureAws.Bedrock.Types.AutomatedReasoningCheckLogicWarning→Aws.StructureAws.Bedrock.Types.AutomatedReasoningCheckNoTranslationsFinding→Aws.EmptyStructureAws.Bedrock.Types.AutomatedReasoningCheckRule→Aws.StructureAws.Bedrock.Types.AutomatedReasoningCheckSatisfiableFinding→Aws.StructureAws.Bedrock.Types.AutomatedReasoningCheckScenario→Aws.StructureAws.Bedrock.Types.AutomatedReasoningCheckTooComplexFinding→Aws.EmptyStructureAws.Bedrock.Types.AutomatedReasoningCheckTranslation→Aws.StructureAws.Bedrock.Types.AutomatedReasoningCheckTranslationAmbiguousFinding→Aws.StructureAws.Bedrock.Types.AutomatedReasoningCheckTranslationOption→Aws.StructureAws.Bedrock.Types.AutomatedReasoningCheckValidFinding→Aws.StructureAws.Bedrock.Types.AutomatedReasoningLogicStatement→Aws.Structure
- Direction
- Aws.Bedrock.Types uses Aws, so a change to Aws can break Aws.Bedrock.Types, while a change to Aws.Bedrock.Types can't break Aws.
- Position
- Below the diagonal: Aws.Bedrock.Types uses a module listed above it, which is the healthy direction.
12→2 Aws.BedrockAgent.Types uses Aws.Structure✕
- Connections
- 21 pairs of types, where a type in Aws.BedrockAgent.Types uses a type in Aws.Structure.
- The types involved
Aws.BedrockAgent.Types.APISchema→Aws.Structure.UnionAws.BedrockAgent.Types.ActionGroupExecutor→Aws.Structure.UnionAws.BedrockAgent.Types.ContentBlock→Aws.Structure.UnionAws.BedrockAgent.Types.DayOfMonth→Aws.Structure.UnionAws.BedrockAgent.Types.FlowConnectionConfiguration→Aws.Structure.UnionAws.BedrockAgent.Types.FlowNodeConfiguration→Aws.Structure.UnionAws.BedrockAgent.Types.FlowValidationDetails→Aws.Structure.UnionAws.BedrockAgent.Types.FunctionSchema→Aws.Structure.UnionAws.BedrockAgent.Types.OrchestrationExecutor→Aws.Structure.UnionAws.BedrockAgent.Types.PromptFlowNodeSourceConfiguration→Aws.Structure.UnionAws.BedrockAgent.Types.PromptGenAiResource→Aws.Structure.UnionAws.BedrockAgent.Types.PromptInferenceConfiguration→Aws.Structure.UnionAws.BedrockAgent.Types.PromptTemplateConfiguration→Aws.Structure.UnionAws.BedrockAgent.Types.RerankingMetadataSelectiveModeConfiguration→Aws.Structure.UnionAws.BedrockAgent.Types.RetrievalFlowNodeServiceConfiguration→Aws.Structure.UnionAws.BedrockAgent.Types.StorageFlowNodeServiceConfiguration→Aws.Structure.UnionAws.BedrockAgent.Types.SyncSchedule→Aws.Structure.UnionAws.BedrockAgent.Types.SystemContentBlock→Aws.Structure.UnionAws.BedrockAgent.Types.Tool→Aws.Structure.UnionAws.BedrockAgent.Types.ToolChoice→Aws.Structure.UnionAws.BedrockAgent.Types.ToolInputSchema→Aws.Structure.Union
- Direction
- Aws.BedrockAgent.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.BedrockAgent.Types, while a change to Aws.BedrockAgent.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.BedrockAgent.Types uses a module listed above it, which is the healthy direction.
12→7 Aws.BedrockAgent.Types uses Aws✕
- Connections
- 439 pairs of types, where a type in Aws.BedrockAgent.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.BedrockAgent.Types.APISchema→Aws.StructureAws.BedrockAgent.Types.AccessDeniedException→Aws.StructureAws.BedrockAgent.Types.ActionGroupExecutor→Aws.StructureAws.BedrockAgent.Types.ActionGroupSummary→Aws.StructureAws.BedrockAgent.Types.Agent→Aws.StructureAws.BedrockAgent.Types.AgentActionGroup→Aws.StructureAws.BedrockAgent.Types.AgentAlias→Aws.StructureAws.BedrockAgent.Types.AgentAliasHistoryEvent→Aws.StructureAws.BedrockAgent.Types.AgentAliasRoutingConfigurationListItem→Aws.StructureAws.BedrockAgent.Types.AgentAliasSummary→Aws.StructureAws.BedrockAgent.Types.AgentCollaborator→Aws.StructureAws.BedrockAgent.Types.AgentCollaboratorSummary→Aws.StructureAws.BedrockAgent.Types.AgentDescriptor→Aws.StructureAws.BedrockAgent.Types.AgentFlowNodeConfiguration→Aws.StructureAws.BedrockAgent.Types.AgentKnowledgeBase→Aws.StructureAws.BedrockAgent.Types.AgentKnowledgeBaseSummary→Aws.StructureAws.BedrockAgent.Types.AgentSummary→Aws.StructureAws.BedrockAgent.Types.AgentVersion→Aws.StructureAws.BedrockAgent.Types.AgentVersionSummary→Aws.StructureAws.BedrockAgent.Types.AnyToolChoice→Aws.EmptyStructureAws.BedrockAgent.Types.AssociateAgentCollaboratorRequest→Aws.StructureAws.BedrockAgent.Types.AssociateAgentCollaboratorResponse→Aws.StructureAws.BedrockAgent.Types.AssociateAgentKnowledgeBaseRequest→Aws.StructureAws.BedrockAgent.Types.AssociateAgentKnowledgeBaseResponse→Aws.StructureAws.BedrockAgent.Types.AudioConfiguration→Aws.Structure
- Direction
- Aws.BedrockAgent.Types uses Aws, so a change to Aws can break Aws.BedrockAgent.Types, while a change to Aws.BedrockAgent.Types can't break Aws.
- Position
- Below the diagonal: Aws.BedrockAgent.Types uses a module listed above it, which is the healthy direction.
13→2 Aws.BedrockAgentCore.Types uses Aws.Structure✕
- Connections
- 58 pairs of types, where a type in Aws.BedrockAgentCore.Types uses a type in Aws.Structure. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.BedrockAgentCore.Types.ABTestEvaluationConfig→Aws.Structure.UnionAws.BedrockAgentCore.Types.AgentTracesConfig→Aws.Structure.UnionAws.BedrockAgentCore.Types.BrowserAction→Aws.Structure.UnionAws.BedrockAgentCore.Types.BrowserActionResult→Aws.Structure.UnionAws.BedrockAgentCore.Types.CertificateLocation→Aws.Structure.UnionAws.BedrockAgentCore.Types.Content→Aws.Structure.UnionAws.BedrockAgentCore.Types.ContentSource→Aws.Structure.UnionAws.BedrockAgentCore.Types.Context→Aws.Structure.UnionAws.BedrockAgentCore.Types.DataSourceConfig→Aws.Structure.UnionAws.BedrockAgentCore.Types.EvaluationContent→Aws.Structure.UnionAws.BedrockAgentCore.Types.EvaluationInput→Aws.Structure.UnionAws.BedrockAgentCore.Types.EvaluationMetadata→Aws.Structure.UnionAws.BedrockAgentCore.Types.EvaluationTarget→Aws.Structure.UnionAws.BedrockAgentCore.Types.ExtractionJobMessages→Aws.Structure.UnionAws.BedrockAgentCore.Types.FilterValue→Aws.Structure.UnionAws.BedrockAgentCore.Types.GroundTruthSource→Aws.Structure.UnionAws.BedrockAgentCore.Types.GroundTruthTurnInput→Aws.Structure.UnionAws.BedrockAgentCore.Types.HarnessContentBlock→Aws.Structure.UnionAws.BedrockAgentCore.Types.HarnessContentBlockDelta→Aws.Structure.UnionAws.BedrockAgentCore.Types.HarnessContentBlockStart→Aws.Structure.UnionAws.BedrockAgentCore.Types.HarnessGatewayOutboundAuth→Aws.Structure.UnionAws.BedrockAgentCore.Types.HarnessModelConfiguration→Aws.Structure.UnionAws.BedrockAgentCore.Types.HarnessReasoningContentBlock→Aws.Structure.UnionAws.BedrockAgentCore.Types.HarnessReasoningContentBlockDelta→Aws.Structure.UnionAws.BedrockAgentCore.Types.HarnessSkill→Aws.Structure.Union
- Direction
- Aws.BedrockAgentCore.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.BedrockAgentCore.Types, while a change to Aws.BedrockAgentCore.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.BedrockAgentCore.Types uses a module listed above it, which is the healthy direction.
13→7 Aws.BedrockAgentCore.Types uses Aws✕
- Connections
- 411 pairs of types, where a type in Aws.BedrockAgentCore.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.BedrockAgentCore.Types.A2aDescriptor→Aws.StructureAws.BedrockAgentCore.Types.ABTestEvaluationConfig→Aws.StructureAws.BedrockAgentCore.Types.ABTestResults→Aws.StructureAws.BedrockAgentCore.Types.ABTestSummary→Aws.StructureAws.BedrockAgentCore.Types.AccessDeniedException→Aws.StructureAws.BedrockAgentCore.Types.ActorSummary→Aws.StructureAws.BedrockAgentCore.Types.AffectedSession→Aws.StructureAws.BedrockAgentCore.Types.AgentCardDefinition→Aws.StructureAws.BedrockAgentCore.Types.AgentSkillsDescriptor→Aws.StructureAws.BedrockAgentCore.Types.AgentTracesConfig→Aws.StructureAws.BedrockAgentCore.Types.Amount→Aws.StructureAws.BedrockAgentCore.Types.AutomationStream→Aws.StructureAws.BedrockAgentCore.Types.AutomationStreamUpdate→Aws.StructureAws.BedrockAgentCore.Types.AvailableLimits→Aws.StructureAws.BedrockAgentCore.Types.BasicAuth→Aws.StructureAws.BedrockAgentCore.Types.BatchCreateMemoryRecordsInput→Aws.StructureAws.BedrockAgentCore.Types.BatchCreateMemoryRecordsOutput→Aws.StructureAws.BedrockAgentCore.Types.BatchDeleteMemoryRecordsInput→Aws.StructureAws.BedrockAgentCore.Types.BatchDeleteMemoryRecordsOutput→Aws.StructureAws.BedrockAgentCore.Types.BatchEvaluationSummary→Aws.StructureAws.BedrockAgentCore.Types.BatchEvaluationTraceConfig→Aws.StructureAws.BedrockAgentCore.Types.BatchUpdateMemoryRecordsInput→Aws.StructureAws.BedrockAgentCore.Types.BatchUpdateMemoryRecordsOutput→Aws.StructureAws.BedrockAgentCore.Types.Branch→Aws.StructureAws.BedrockAgentCore.Types.BranchFilter→Aws.Structure
- Direction
- Aws.BedrockAgentCore.Types uses Aws, so a change to Aws can break Aws.BedrockAgentCore.Types, while a change to Aws.BedrockAgentCore.Types can't break Aws.
- Position
- Below the diagonal: Aws.BedrockAgentCore.Types uses a module listed above it, which is the healthy direction.
14→2 Aws.BedrockAgentCoreControl.Types uses Aws.Structure✕
- Connections
- 85 pairs of types, where a type in Aws.BedrockAgentCoreControl.Types uses a type in Aws.Structure. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.BedrockAgentCoreControl.Types.Action→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.AgentRuntimeArtifact→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.ApiSchemaConfiguration→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.AuthorizationData→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.AuthorizerConfiguration→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.CertificateConfiguration→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.CertificateLocation→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.ClaimMatchValueType→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.Code→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.CodeBasedEvaluatorConfig→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.ComputeConfiguration→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.Condition→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.ConfigurationBundleAction→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.ConsolidationConfiguration→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.Content→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.CredentialProvider→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.CredentialRotationConfig→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.CredentialsProviderConfiguration→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.CustomConfigurationInput→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.CustomConsolidationConfiguration→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.CustomConsolidationConfigurationInput→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.CustomExtractionConfiguration→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.CustomExtractionConfigurationInput→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.CustomReflectionConfiguration→Aws.Structure.UnionAws.BedrockAgentCoreControl.Types.CustomReflectionConfigurationInput→Aws.Structure.Union
- Direction
- Aws.BedrockAgentCoreControl.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.BedrockAgentCoreControl.Types, while a change to Aws.BedrockAgentCoreControl.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.BedrockAgentCoreControl.Types uses a module listed above it, which is the healthy direction.
14→7 Aws.BedrockAgentCoreControl.Types uses Aws✕
- Connections
- 780 pairs of types, where a type in Aws.BedrockAgentCoreControl.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.BedrockAgentCoreControl.Types.A2aDescriptor→Aws.StructureAws.BedrockAgentCoreControl.Types.AccessDeniedException→Aws.StructureAws.BedrockAgentCoreControl.Types.Action→Aws.StructureAws.BedrockAgentCoreControl.Types.AddDatasetExamplesRequest→Aws.StructureAws.BedrockAgentCoreControl.Types.AddDatasetExamplesResponse→Aws.StructureAws.BedrockAgentCoreControl.Types.AgentCardDefinition→Aws.StructureAws.BedrockAgentCoreControl.Types.AgentRuntime→Aws.StructureAws.BedrockAgentCoreControl.Types.AgentRuntimeArtifact→Aws.StructureAws.BedrockAgentCoreControl.Types.AgentRuntimeEndpoint→Aws.StructureAws.BedrockAgentCoreControl.Types.AgentRuntimeVersionSummary→Aws.StructureAws.BedrockAgentCoreControl.Types.AgentSkillsDescriptor→Aws.StructureAws.BedrockAgentCoreControl.Types.AllowedWorkloadConfiguration→Aws.StructureAws.BedrockAgentCoreControl.Types.ApiGatewayTargetConfiguration→Aws.StructureAws.BedrockAgentCoreControl.Types.ApiGatewayToolConfiguration→Aws.StructureAws.BedrockAgentCoreControl.Types.ApiGatewayToolFilter→Aws.StructureAws.BedrockAgentCoreControl.Types.ApiGatewayToolOverride→Aws.StructureAws.BedrockAgentCoreControl.Types.ApiKeyCredentialProvider→Aws.StructureAws.BedrockAgentCoreControl.Types.ApiKeyCredentialProviderItem→Aws.StructureAws.BedrockAgentCoreControl.Types.ApiSchemaConfiguration→Aws.StructureAws.BedrockAgentCoreControl.Types.ApprovalConfiguration→Aws.StructureAws.BedrockAgentCoreControl.Types.AtlassianOauth2ProviderConfigInput→Aws.StructureAws.BedrockAgentCoreControl.Types.AtlassianOauth2ProviderConfigOutput→Aws.StructureAws.BedrockAgentCoreControl.Types.AuthorizationData→Aws.StructureAws.BedrockAgentCoreControl.Types.AuthorizerConfiguration→Aws.StructureAws.BedrockAgentCoreControl.Types.AuthorizingClaimMatchValueType→Aws.Structure
- Direction
- Aws.BedrockAgentCoreControl.Types uses Aws, so a change to Aws can break Aws.BedrockAgentCoreControl.Types, while a change to Aws.BedrockAgentCoreControl.Types can't break Aws.
- Position
- Below the diagonal: Aws.BedrockAgentCoreControl.Types uses a module listed above it, which is the healthy direction.
15→2 Aws.BedrockAgentRuntime.Types uses Aws.Structure✕
- Connections
- 39 pairs of types, where a type in Aws.BedrockAgentRuntime.Types uses a type in Aws.Structure. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.BedrockAgentRuntime.Types.APISchema→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.ActionGroupExecutor→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.AgenticRetrieveMemoryMetadataFilterLeft→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.AgenticRetrieveMemoryMetadataFilterRight→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.AgenticRetrieveMemoryMetadataValue→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.AgenticRetrieveWarning→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.BedrockSessionContentBlock→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.Caller→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.ContentBlock→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.FlowExecutionContent→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.FlowExecutionEvent→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.FlowInputContent→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.FlowMultiTurnInputContent→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.FlowOutputContent→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.FlowTrace→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.FlowTraceNodeInputContent→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.FlowTraceNodeOutputContent→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.FunctionSchema→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.ImageInputSource→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.ImageSource→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.InputPrompt→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.InvocationInputMember→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.InvocationResultMember→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.InvocationStepPayload→Aws.Structure.UnionAws.BedrockAgentRuntime.Types.Memory→Aws.Structure.Union
- Direction
- Aws.BedrockAgentRuntime.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.BedrockAgentRuntime.Types, while a change to Aws.BedrockAgentRuntime.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.BedrockAgentRuntime.Types uses a module listed above it, which is the healthy direction.
15→7 Aws.BedrockAgentRuntime.Types uses Aws✕
- Connections
- 372 pairs of types, where a type in Aws.BedrockAgentRuntime.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.BedrockAgentRuntime.Types.APISchema→Aws.StructureAws.BedrockAgentRuntime.Types.AccessDeniedException→Aws.StructureAws.BedrockAgentRuntime.Types.ActionGroupExecutor→Aws.StructureAws.BedrockAgentRuntime.Types.ActionGroupInvocationInput→Aws.StructureAws.BedrockAgentRuntime.Types.ActionGroupInvocationOutput→Aws.StructureAws.BedrockAgentRuntime.Types.AgentActionGroup→Aws.StructureAws.BedrockAgentRuntime.Types.AgentCollaboratorInputPayload→Aws.StructureAws.BedrockAgentRuntime.Types.AgentCollaboratorInvocationInput→Aws.StructureAws.BedrockAgentRuntime.Types.AgentCollaboratorInvocationOutput→Aws.StructureAws.BedrockAgentRuntime.Types.AgentCollaboratorOutputPayload→Aws.StructureAws.BedrockAgentRuntime.Types.AgenticRetrieveAction→Aws.StructureAws.BedrockAgentRuntime.Types.AgenticRetrieveActionDetails→Aws.StructureAws.BedrockAgentRuntime.Types.AgenticRetrieveAppliedInstruction→Aws.StructureAws.BedrockAgentRuntime.Types.AgenticRetrieveBedrockGuardrailConfiguration→Aws.StructureAws.BedrockAgentRuntime.Types.AgenticRetrieveBedrockRerankingConfiguration→Aws.StructureAws.BedrockAgentRuntime.Types.AgenticRetrieveBedrockRerankingModelConfiguration→Aws.StructureAws.BedrockAgentRuntime.Types.AgenticRetrieveCitation→Aws.StructureAws.BedrockAgentRuntime.Types.AgenticRetrieveCitationReference→Aws.StructureAws.BedrockAgentRuntime.Types.AgenticRetrieveConfiguration→Aws.StructureAws.BedrockAgentRuntime.Types.AgenticRetrieveFailure→Aws.StructureAws.BedrockAgentRuntime.Types.AgenticRetrieveFullDocExpansionDetails→Aws.StructureAws.BedrockAgentRuntime.Types.AgenticRetrieveGeneratedResponse→Aws.StructureAws.BedrockAgentRuntime.Types.AgenticRetrieveGuardrailWarning→Aws.StructureAws.BedrockAgentRuntime.Types.AgenticRetrieveInstructionConfiguration→Aws.StructureAws.BedrockAgentRuntime.Types.AgenticRetrieveMemoryConfiguration→Aws.Structure
- Direction
- Aws.BedrockAgentRuntime.Types uses Aws, so a change to Aws can break Aws.BedrockAgentRuntime.Types, while a change to Aws.BedrockAgentRuntime.Types can't break Aws.
- Position
- Below the diagonal: Aws.BedrockAgentRuntime.Types uses a module listed above it, which is the healthy direction.
16→2 Aws.BedrockRuntime.Types uses Aws.Structure✕
- Connections
- 30 pairs of types, where a type in Aws.BedrockRuntime.Types uses a type in Aws.Structure. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.BedrockRuntime.Types.AsyncInvokeOutputDataConfig→Aws.Structure.UnionAws.BedrockRuntime.Types.AudioSource→Aws.Structure.UnionAws.BedrockRuntime.Types.CitationGeneratedContent→Aws.Structure.UnionAws.BedrockRuntime.Types.CitationLocation→Aws.Structure.UnionAws.BedrockRuntime.Types.CitationSourceContent→Aws.Structure.UnionAws.BedrockRuntime.Types.ContentBlock→Aws.Structure.UnionAws.BedrockRuntime.Types.ContentBlockDelta→Aws.Structure.UnionAws.BedrockRuntime.Types.ContentBlockStart→Aws.Structure.UnionAws.BedrockRuntime.Types.ConverseOutput→Aws.Structure.UnionAws.BedrockRuntime.Types.CountTokensInput→Aws.Structure.UnionAws.BedrockRuntime.Types.DocumentContentBlock→Aws.Structure.UnionAws.BedrockRuntime.Types.DocumentSource→Aws.Structure.UnionAws.BedrockRuntime.Types.GuardrailAutomatedReasoningFinding→Aws.Structure.UnionAws.BedrockRuntime.Types.GuardrailChecksContentBlock→Aws.Structure.UnionAws.BedrockRuntime.Types.GuardrailContentBlock→Aws.Structure.UnionAws.BedrockRuntime.Types.GuardrailConverseContentBlock→Aws.Structure.UnionAws.BedrockRuntime.Types.GuardrailConverseImageSource→Aws.Structure.UnionAws.BedrockRuntime.Types.GuardrailImageSource→Aws.Structure.UnionAws.BedrockRuntime.Types.ImageSource→Aws.Structure.UnionAws.BedrockRuntime.Types.OutputFormatStructure→Aws.Structure.UnionAws.BedrockRuntime.Types.PromptVariableValues→Aws.Structure.UnionAws.BedrockRuntime.Types.ReasoningContentBlock→Aws.Structure.UnionAws.BedrockRuntime.Types.ReasoningContentBlockDelta→Aws.Structure.UnionAws.BedrockRuntime.Types.SystemContentBlock→Aws.Structure.UnionAws.BedrockRuntime.Types.Tool→Aws.Structure.Union
- Direction
- Aws.BedrockRuntime.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.BedrockRuntime.Types, while a change to Aws.BedrockRuntime.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.BedrockRuntime.Types uses a module listed above it, which is the healthy direction.
16→7 Aws.BedrockRuntime.Types uses Aws✕
- Connections
- 189 pairs of types, where a type in Aws.BedrockRuntime.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.BedrockRuntime.Types.AccessDeniedException→Aws.StructureAws.BedrockRuntime.Types.AnyToolChoice→Aws.EmptyStructureAws.BedrockRuntime.Types.AppliedGuardrailDetails→Aws.StructureAws.BedrockRuntime.Types.ApplyGuardrailRequest→Aws.StructureAws.BedrockRuntime.Types.ApplyGuardrailResponse→Aws.StructureAws.BedrockRuntime.Types.AsyncInvokeOutputDataConfig→Aws.StructureAws.BedrockRuntime.Types.AsyncInvokeS3OutputDataConfig→Aws.StructureAws.BedrockRuntime.Types.AsyncInvokeSummary→Aws.StructureAws.BedrockRuntime.Types.AudioBlock→Aws.StructureAws.BedrockRuntime.Types.AudioSource→Aws.StructureAws.BedrockRuntime.Types.AutoToolChoice→Aws.EmptyStructureAws.BedrockRuntime.Types.BidirectionalInputPayloadPart→Aws.StructureAws.BedrockRuntime.Types.BidirectionalOutputPayloadPart→Aws.StructureAws.BedrockRuntime.Types.CacheDetail→Aws.StructureAws.BedrockRuntime.Types.CachePointBlock→Aws.StructureAws.BedrockRuntime.Types.Citation→Aws.StructureAws.BedrockRuntime.Types.CitationGeneratedContent→Aws.StructureAws.BedrockRuntime.Types.CitationLocation→Aws.StructureAws.BedrockRuntime.Types.CitationSourceContent→Aws.StructureAws.BedrockRuntime.Types.CitationSourceContentDelta→Aws.StructureAws.BedrockRuntime.Types.CitationsConfig→Aws.StructureAws.BedrockRuntime.Types.CitationsContentBlock→Aws.StructureAws.BedrockRuntime.Types.CitationsDelta→Aws.StructureAws.BedrockRuntime.Types.ConflictException→Aws.StructureAws.BedrockRuntime.Types.ContentBlock→Aws.Structure
- Direction
- Aws.BedrockRuntime.Types uses Aws, so a change to Aws can break Aws.BedrockRuntime.Types, while a change to Aws.BedrockRuntime.Types can't break Aws.
- Position
- Below the diagonal: Aws.BedrockRuntime.Types uses a module listed above it, which is the healthy direction.
17→2 Aws.CleanRooms.Types uses Aws.Structure✕
- Connections
- 40 pairs of types, where a type in Aws.CleanRooms.Types uses a type in Aws.Structure. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.CleanRooms.Types.AnalysisRulePolicy→Aws.Structure.UnionAws.CleanRooms.Types.AnalysisRulePolicyV1→Aws.Structure.UnionAws.CleanRooms.Types.AnalysisSource→Aws.Structure.UnionAws.CleanRooms.Types.AnalysisSourceMetadata→Aws.Structure.UnionAws.CleanRooms.Types.ChangeSpecification→Aws.Structure.UnionAws.CleanRooms.Types.ComputeConfiguration→Aws.Structure.UnionAws.CleanRooms.Types.ConfigurationDetails→Aws.Structure.UnionAws.CleanRooms.Types.ConfiguredTableAnalysisRulePolicy→Aws.Structure.UnionAws.CleanRooms.Types.ConfiguredTableAnalysisRulePolicyV1→Aws.Structure.UnionAws.CleanRooms.Types.ConfiguredTableAssociationAnalysisRulePolicy→Aws.Structure.UnionAws.CleanRooms.Types.ConfiguredTableAssociationAnalysisRulePolicyV1→Aws.Structure.UnionAws.CleanRooms.Types.ConsolidatedPolicy→Aws.Structure.UnionAws.CleanRooms.Types.ConsolidatedPolicyV1→Aws.Structure.UnionAws.CleanRooms.Types.DatabricksConnectionType→Aws.Structure.UnionAws.CleanRooms.Types.IntermediateTableAnalysisRulePolicy→Aws.Structure.UnionAws.CleanRooms.Types.IntermediateTableAnalysisRulePolicyV1→Aws.Structure.UnionAws.CleanRooms.Types.IntermediateTableComputeConfiguration→Aws.Structure.UnionAws.CleanRooms.Types.MembershipProtectedJobOutputConfiguration→Aws.Structure.UnionAws.CleanRooms.Types.MembershipProtectedQueryOutputConfiguration→Aws.Structure.UnionAws.CleanRooms.Types.PopulationAnalysisConfiguration→Aws.Structure.UnionAws.CleanRooms.Types.PreviewPrivacyImpactParametersInput→Aws.Structure.UnionAws.CleanRooms.Types.PrivacyBudget→Aws.Structure.UnionAws.CleanRooms.Types.PrivacyBudgetTemplateParametersInput→Aws.Structure.UnionAws.CleanRooms.Types.PrivacyBudgetTemplateParametersOutput→Aws.Structure.UnionAws.CleanRooms.Types.PrivacyBudgetTemplateUpdateParameters→Aws.Structure.Union
- Direction
- Aws.CleanRooms.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.CleanRooms.Types, while a change to Aws.CleanRooms.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.CleanRooms.Types uses a module listed above it, which is the healthy direction.
17→7 Aws.CleanRooms.Types uses Aws✕
- Connections
- 447 pairs of types, where a type in Aws.CleanRooms.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.CleanRooms.Types.AccessBudget→Aws.StructureAws.CleanRooms.Types.AccessBudgetDetails→Aws.StructureAws.CleanRooms.Types.AccessBudgetsPrivacyTemplateParametersInput→Aws.StructureAws.CleanRooms.Types.AccessBudgetsPrivacyTemplateParametersOutput→Aws.StructureAws.CleanRooms.Types.AccessBudgetsPrivacyTemplateUpdateParameters→Aws.StructureAws.CleanRooms.Types.AccessDeniedException→Aws.StructureAws.CleanRooms.Types.AggregateColumn→Aws.StructureAws.CleanRooms.Types.AggregationConstraint→Aws.StructureAws.CleanRooms.Types.AggregationThreshold→Aws.StructureAws.CleanRooms.Types.AnalysisLogExport→Aws.StructureAws.CleanRooms.Types.AnalysisLogExportError→Aws.StructureAws.CleanRooms.Types.AnalysisLogExportOutputConfiguration→Aws.StructureAws.CleanRooms.Types.AnalysisLogExportResultConfiguration→Aws.StructureAws.CleanRooms.Types.AnalysisLogExportS3OutputConfiguration→Aws.StructureAws.CleanRooms.Types.AnalysisLogExportSummary→Aws.StructureAws.CleanRooms.Types.AnalysisParameter→Aws.StructureAws.CleanRooms.Types.AnalysisRule→Aws.StructureAws.CleanRooms.Types.AnalysisRuleAggregation→Aws.StructureAws.CleanRooms.Types.AnalysisRuleCustom→Aws.StructureAws.CleanRooms.Types.AnalysisRuleIdMappingTable→Aws.StructureAws.CleanRooms.Types.AnalysisRuleList→Aws.StructureAws.CleanRooms.Types.AnalysisRulePolicy→Aws.StructureAws.CleanRooms.Types.AnalysisRulePolicyV1→Aws.StructureAws.CleanRooms.Types.AnalysisSchema→Aws.StructureAws.CleanRooms.Types.AnalysisSource→Aws.Structure
- Direction
- Aws.CleanRooms.Types uses Aws, so a change to Aws can break Aws.CleanRooms.Types, while a change to Aws.CleanRooms.Types can't break Aws.
- Position
- Below the diagonal: Aws.CleanRooms.Types uses a module listed above it, which is the healthy direction.
18→2 Aws.Connect.Types uses Aws.Structure✕
- Connections
- 20 pairs of types, where a type in Aws.Connect.Types uses a type in Aws.Structure.
- The types involved
Aws.Connect.Types.ContactMetricValue→Aws.Structure.UnionAws.Connect.Types.CreatedByInfo→Aws.Structure.UnionAws.Connect.Types.EvaluationAnswerData→Aws.Structure.UnionAws.Connect.Types.EvaluationFormItem→Aws.Structure.UnionAws.Connect.Types.EvaluationFormItemEnablementConditionOperand→Aws.Structure.UnionAws.Connect.Types.EvaluationFormMultiSelectQuestionAutomationOption→Aws.Structure.UnionAws.Connect.Types.EvaluationFormNumericQuestionAutomation→Aws.Structure.UnionAws.Connect.Types.EvaluationFormQuestionTypeProperties→Aws.Structure.UnionAws.Connect.Types.EvaluationFormSingleSelectQuestionAutomationOption→Aws.Structure.UnionAws.Connect.Types.EvaluationQuestionAnswerAnalysisDetails→Aws.Structure.UnionAws.Connect.Types.EvaluatorUserUnion→Aws.Structure.UnionAws.Connect.Types.InvalidRequestExceptionReason→Aws.Structure.UnionAws.Connect.Types.NextContactMetadata→Aws.Structure.UnionAws.Connect.Types.ParticipantTimerValue→Aws.Structure.UnionAws.Connect.Types.PredefinedAttributeValues→Aws.Structure.UnionAws.Connect.Types.RealTimeContactAnalysisTimeData→Aws.Structure.UnionAws.Connect.Types.RealtimeContactAnalysisSegment→Aws.Structure.UnionAws.Connect.Types.ReferenceSummary→Aws.Structure.UnionAws.Connect.Types.ServiceQuotaExceededExceptionReason→Aws.Structure.UnionAws.Connect.Types.UpdateParticipantRoleConfigChannelInfo→Aws.Structure.Union
- Direction
- Aws.Connect.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.Connect.Types, while a change to Aws.Connect.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.Connect.Types uses a module listed above it, which is the healthy direction.
18→7 Aws.Connect.Types uses Aws✕
- Connections
- 1361 pairs of types, where a type in Aws.Connect.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.Connect.Types.AIAgent→Aws.StructureAws.Connect.Types.AccessDeniedException→Aws.StructureAws.Connect.Types.ActionSummary→Aws.StructureAws.Connect.Types.ActivateEvaluationFormRequest→Aws.StructureAws.Connect.Types.ActivateEvaluationFormResponse→Aws.StructureAws.Connect.Types.AdditionalEmailRecipients→Aws.StructureAws.Connect.Types.AfterContactWorkConfig→Aws.StructureAws.Connect.Types.AfterContactWorkConfigPerChannel→Aws.StructureAws.Connect.Types.AgentConfig→Aws.StructureAws.Connect.Types.AgentContactReference→Aws.StructureAws.Connect.Types.AgentFirst→Aws.StructureAws.Connect.Types.AgentHierarchyGroup→Aws.StructureAws.Connect.Types.AgentHierarchyGroups→Aws.StructureAws.Connect.Types.AgentInfo→Aws.StructureAws.Connect.Types.AgentQualityMetrics→Aws.StructureAws.Connect.Types.AgentStatus→Aws.StructureAws.Connect.Types.AgentStatusIdentifier→Aws.StructureAws.Connect.Types.AgentStatusReference→Aws.StructureAws.Connect.Types.AgentStatusSearchCriteria→Aws.StructureAws.Connect.Types.AgentStatusSearchFilter→Aws.StructureAws.Connect.Types.AgentStatusSummary→Aws.StructureAws.Connect.Types.AgentsCriteria→Aws.StructureAws.Connect.Types.AiAgentInfo→Aws.StructureAws.Connect.Types.AiAgentInput→Aws.StructureAws.Connect.Types.AiAgentSearchCriteria→Aws.Structure
- Direction
- Aws.Connect.Types uses Aws, so a change to Aws can break Aws.Connect.Types, while a change to Aws.Connect.Types can't break Aws.
- Position
- Below the diagonal: Aws.Connect.Types uses a module listed above it, which is the healthy direction.
19→2 Aws.ConnectCampaignsV2.Types uses Aws.Structure✕
- Connections
- 13 pairs of types, where a type in Aws.ConnectCampaignsV2.Types uses a type in Aws.Structure.
- The types involved
Aws.ConnectCampaignsV2.Types.ChannelSubtypeParameters→Aws.Structure.UnionAws.ConnectCampaignsV2.Types.CommunicationLimits→Aws.Structure.UnionAws.ConnectCampaignsV2.Types.EmailOutboundMode→Aws.Structure.UnionAws.ConnectCampaignsV2.Types.IntegrationConfig→Aws.Structure.UnionAws.ConnectCampaignsV2.Types.IntegrationIdentifier→Aws.Structure.UnionAws.ConnectCampaignsV2.Types.IntegrationSummary→Aws.Structure.UnionAws.ConnectCampaignsV2.Types.OpenHours→Aws.Structure.UnionAws.ConnectCampaignsV2.Types.PacingStrategy→Aws.Structure.UnionAws.ConnectCampaignsV2.Types.RestrictedPeriods→Aws.Structure.UnionAws.ConnectCampaignsV2.Types.SmsOutboundMode→Aws.Structure.UnionAws.ConnectCampaignsV2.Types.Source→Aws.Structure.UnionAws.ConnectCampaignsV2.Types.TelephonyOutboundMode→Aws.Structure.UnionAws.ConnectCampaignsV2.Types.WhatsAppOutboundMode→Aws.Structure.Union
- Direction
- Aws.ConnectCampaignsV2.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.ConnectCampaignsV2.Types, while a change to Aws.ConnectCampaignsV2.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.ConnectCampaignsV2.Types uses a module listed above it, which is the healthy direction.
19→7 Aws.ConnectCampaignsV2.Types uses Aws✕
- Connections
- 130 pairs of types, where a type in Aws.ConnectCampaignsV2.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.ConnectCampaignsV2.Types.AbandonmentRatePacingConfig→Aws.StructureAws.ConnectCampaignsV2.Types.AccessDeniedException→Aws.StructureAws.ConnectCampaignsV2.Types.AgentlessConfig→Aws.EmptyStructureAws.ConnectCampaignsV2.Types.AnswerMachineDetectionConfig→Aws.StructureAws.ConnectCampaignsV2.Types.Campaign→Aws.StructureAws.ConnectCampaignsV2.Types.CampaignFilters→Aws.StructureAws.ConnectCampaignsV2.Types.CampaignSummary→Aws.StructureAws.ConnectCampaignsV2.Types.ChannelContext→Aws.StructureAws.ConnectCampaignsV2.Types.ChannelSubtypeConfig→Aws.StructureAws.ConnectCampaignsV2.Types.ChannelSubtypeParameters→Aws.StructureAws.ConnectCampaignsV2.Types.CommunicationLimit→Aws.StructureAws.ConnectCampaignsV2.Types.CommunicationLimits→Aws.StructureAws.ConnectCampaignsV2.Types.CommunicationLimitsConfig→Aws.StructureAws.ConnectCampaignsV2.Types.CommunicationTimeConfig→Aws.StructureAws.ConnectCampaignsV2.Types.ConflictException→Aws.StructureAws.ConnectCampaignsV2.Types.CreateCampaignRequest→Aws.StructureAws.ConnectCampaignsV2.Types.CreateCampaignResponse→Aws.StructureAws.ConnectCampaignsV2.Types.CustomerProfilesIntegrationConfig→Aws.StructureAws.ConnectCampaignsV2.Types.CustomerProfilesIntegrationIdentifier→Aws.StructureAws.ConnectCampaignsV2.Types.CustomerProfilesIntegrationSummary→Aws.StructureAws.ConnectCampaignsV2.Types.DeleteCampaignChannelSubtypeConfigRequest→Aws.StructureAws.ConnectCampaignsV2.Types.DeleteCampaignCommunicationLimitsRequest→Aws.StructureAws.ConnectCampaignsV2.Types.DeleteCampaignCommunicationTimeRequest→Aws.StructureAws.ConnectCampaignsV2.Types.DeleteCampaignEntryLimitsRequest→Aws.StructureAws.ConnectCampaignsV2.Types.DeleteCampaignRequest→Aws.Structure
- Direction
- Aws.ConnectCampaignsV2.Types uses Aws, so a change to Aws can break Aws.ConnectCampaignsV2.Types, while a change to Aws.ConnectCampaignsV2.Types can't break Aws.
- Position
- Below the diagonal: Aws.ConnectCampaignsV2.Types uses a module listed above it, which is the healthy direction.
20→2 Aws.ConnectCases.Types uses Aws.Structure✕
- Connections
- 19 pairs of types, where a type in Aws.ConnectCases.Types uses a type in Aws.Structure.
- The types involved
Aws.ConnectCases.Types.AuditEventFieldValueUnion→Aws.Structure.UnionAws.ConnectCases.Types.BooleanCondition→Aws.Structure.UnionAws.ConnectCases.Types.CaseFilter→Aws.Structure.UnionAws.ConnectCases.Types.CaseRuleDetails→Aws.Structure.UnionAws.ConnectCases.Types.CustomFieldsFilter→Aws.Structure.UnionAws.ConnectCases.Types.FieldAttributes→Aws.Structure.UnionAws.ConnectCases.Types.FieldFilter→Aws.Structure.UnionAws.ConnectCases.Types.FieldValueUnion→Aws.Structure.UnionAws.ConnectCases.Types.LayoutContent→Aws.Structure.UnionAws.ConnectCases.Types.OperandOne→Aws.Structure.UnionAws.ConnectCases.Types.OperandTwo→Aws.Structure.UnionAws.ConnectCases.Types.RelatedItemContent→Aws.Structure.UnionAws.ConnectCases.Types.RelatedItemInputContent→Aws.Structure.UnionAws.ConnectCases.Types.RelatedItemTypeFilter→Aws.Structure.UnionAws.ConnectCases.Types.RelatedItemUpdateContent→Aws.Structure.UnionAws.ConnectCases.Types.Section→Aws.Structure.UnionAws.ConnectCases.Types.SlaInputContent→Aws.Structure.UnionAws.ConnectCases.Types.TagFilter→Aws.Structure.UnionAws.ConnectCases.Types.UserUnion→Aws.Structure.Union
- Direction
- Aws.ConnectCases.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.ConnectCases.Types, while a change to Aws.ConnectCases.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.ConnectCases.Types uses a module listed above it, which is the healthy direction.
20→7 Aws.ConnectCases.Types uses Aws✕
- Connections
- 174 pairs of types, where a type in Aws.ConnectCases.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.ConnectCases.Types.AccessDeniedException→Aws.StructureAws.ConnectCases.Types.AuditEvent→Aws.StructureAws.ConnectCases.Types.AuditEventField→Aws.StructureAws.ConnectCases.Types.AuditEventFieldValueUnion→Aws.StructureAws.ConnectCases.Types.AuditEventPerformedBy→Aws.StructureAws.ConnectCases.Types.BasicLayout→Aws.StructureAws.ConnectCases.Types.BatchGetCaseRuleRequest→Aws.StructureAws.ConnectCases.Types.BatchGetCaseRuleResponse→Aws.StructureAws.ConnectCases.Types.BatchGetFieldRequest→Aws.StructureAws.ConnectCases.Types.BatchGetFieldResponse→Aws.StructureAws.ConnectCases.Types.BatchPutFieldOptionsRequest→Aws.StructureAws.ConnectCases.Types.BatchPutFieldOptionsResponse→Aws.StructureAws.ConnectCases.Types.BooleanCondition→Aws.StructureAws.ConnectCases.Types.BooleanOperands→Aws.StructureAws.ConnectCases.Types.CaseEventIncludedData→Aws.StructureAws.ConnectCases.Types.CaseFilter→Aws.StructureAws.ConnectCases.Types.CaseRuleDetails→Aws.StructureAws.ConnectCases.Types.CaseRuleError→Aws.StructureAws.ConnectCases.Types.CaseRuleIdentifier→Aws.StructureAws.ConnectCases.Types.CaseRuleSummary→Aws.StructureAws.ConnectCases.Types.CaseSummary→Aws.StructureAws.ConnectCases.Types.CommentContent→Aws.StructureAws.ConnectCases.Types.CommentFilter→Aws.EmptyStructureAws.ConnectCases.Types.CommentUpdateContent→Aws.StructureAws.ConnectCases.Types.CompoundCondition→Aws.Structure
- Direction
- Aws.ConnectCases.Types uses Aws, so a change to Aws can break Aws.ConnectCases.Types, while a change to Aws.ConnectCases.Types can't break Aws.
- Position
- Below the diagonal: Aws.ConnectCases.Types uses a module listed above it, which is the healthy direction.
21→2 Aws.DataZone.Types uses Aws.Structure✕
- Connections
- 51 pairs of types, where a type in Aws.DataZone.Types uses a type in Aws.Structure. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.DataZone.Types.AccountSource→Aws.Structure.UnionAws.DataZone.Types.ActionParameters→Aws.Structure.UnionAws.DataZone.Types.AssetFilterConfiguration→Aws.Structure.UnionAws.DataZone.Types.AwsAccount→Aws.Structure.UnionAws.DataZone.Types.ConnectionPropertiesInput→Aws.Structure.UnionAws.DataZone.Types.ConnectionPropertiesOutput→Aws.Structure.UnionAws.DataZone.Types.ConnectionPropertiesPatch→Aws.Structure.UnionAws.DataZone.Types.DataSourceConfigurationInput→Aws.Structure.UnionAws.DataZone.Types.DataSourceConfigurationOutput→Aws.Structure.UnionAws.DataZone.Types.DomainUnitGrantFilter→Aws.Structure.UnionAws.DataZone.Types.DomainUnitOwnerProperties→Aws.Structure.UnionAws.DataZone.Types.EventSummary→Aws.Structure.UnionAws.DataZone.Types.FilterClause→Aws.Structure.UnionAws.DataZone.Types.GrantedEntity→Aws.Structure.UnionAws.DataZone.Types.GrantedEntityInput→Aws.Structure.UnionAws.DataZone.Types.GroupPolicyGrantPrincipal→Aws.Structure.UnionAws.DataZone.Types.JobRunDetails→Aws.Structure.UnionAws.DataZone.Types.ListingItem→Aws.Structure.UnionAws.DataZone.Types.MatchClause→Aws.Structure.UnionAws.DataZone.Types.MatchRationaleItem→Aws.Structure.UnionAws.DataZone.Types.Member→Aws.Structure.UnionAws.DataZone.Types.MemberDetails→Aws.Structure.UnionAws.DataZone.Types.Model→Aws.Structure.UnionAws.DataZone.Types.OutputLocation→Aws.Structure.UnionAws.DataZone.Types.OwnerProperties→Aws.Structure.Union
- Direction
- Aws.DataZone.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.DataZone.Types, while a change to Aws.DataZone.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.DataZone.Types uses a module listed above it, which is the healthy direction.
21→7 Aws.DataZone.Types uses Aws✕
- Connections
- 746 pairs of types, where a type in Aws.DataZone.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.DataZone.Types.AcceptChoice→Aws.StructureAws.DataZone.Types.AcceptPredictionsInput→Aws.StructureAws.DataZone.Types.AcceptPredictionsOutput→Aws.StructureAws.DataZone.Types.AcceptRule→Aws.StructureAws.DataZone.Types.AcceptSubscriptionRequestInput→Aws.StructureAws.DataZone.Types.AcceptSubscriptionRequestOutput→Aws.StructureAws.DataZone.Types.AcceptedAssetScope→Aws.StructureAws.DataZone.Types.AccessDeniedException→Aws.StructureAws.DataZone.Types.AccountInfo→Aws.StructureAws.DataZone.Types.AccountPoolSummary→Aws.StructureAws.DataZone.Types.AccountSource→Aws.StructureAws.DataZone.Types.ActionParameters→Aws.StructureAws.DataZone.Types.AddEntityOwnerInput→Aws.StructureAws.DataZone.Types.AddEntityOwnerOutput→Aws.EmptyStructureAws.DataZone.Types.AddPolicyGrantInput→Aws.StructureAws.DataZone.Types.AddPolicyGrantOutput→Aws.StructureAws.DataZone.Types.AddToProjectMemberPoolPolicyGrantDetail→Aws.StructureAws.DataZone.Types.AdditionalAttributes→Aws.StructureAws.DataZone.Types.AggregationListItem→Aws.StructureAws.DataZone.Types.AggregationOutput→Aws.StructureAws.DataZone.Types.AggregationOutputItem→Aws.StructureAws.DataZone.Types.AllDomainUnitsGrantFilter→Aws.EmptyStructureAws.DataZone.Types.AllUsersGrantFilter→Aws.EmptyStructureAws.DataZone.Types.AmazonQPropertiesInput→Aws.StructureAws.DataZone.Types.AmazonQPropertiesOutput→Aws.Structure
- Direction
- Aws.DataZone.Types uses Aws, so a change to Aws can break Aws.DataZone.Types, while a change to Aws.DataZone.Types can't break Aws.
- Position
- Below the diagonal: Aws.DataZone.Types uses a module listed above it, which is the healthy direction.
22→2 Aws.Deadline.Types uses Aws.Structure✕
- Connections
- 18 pairs of types, where a type in Aws.Deadline.Types uses a type in Aws.Structure.
- The types involved
Aws.Deadline.Types.AssignedSessionActionDefinition→Aws.Structure.UnionAws.Deadline.Types.BudgetSchedule→Aws.Structure.UnionAws.Deadline.Types.FleetConfiguration→Aws.Structure.UnionAws.Deadline.Types.GetJobEntityError→Aws.Structure.UnionAws.Deadline.Types.JobEntity→Aws.Structure.UnionAws.Deadline.Types.JobEntityIdentifiersUnion→Aws.Structure.UnionAws.Deadline.Types.JobParameter→Aws.Structure.UnionAws.Deadline.Types.MembershipSummary→Aws.Structure.UnionAws.Deadline.Types.SchedulingConfiguration→Aws.Structure.UnionAws.Deadline.Types.SchedulingMaxPriorityOverride→Aws.Structure.UnionAws.Deadline.Types.SchedulingMinPriorityOverride→Aws.Structure.UnionAws.Deadline.Types.SearchFilterExpression→Aws.Structure.UnionAws.Deadline.Types.SearchSortExpression→Aws.Structure.UnionAws.Deadline.Types.SessionActionDefinition→Aws.Structure.UnionAws.Deadline.Types.SessionActionDefinitionSummary→Aws.Structure.UnionAws.Deadline.Types.SessionsStatisticsResources→Aws.Structure.UnionAws.Deadline.Types.TaskParameterValue→Aws.Structure.UnionAws.Deadline.Types.UsageTrackingResource→Aws.Structure.Union
- Direction
- Aws.Deadline.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.Deadline.Types, while a change to Aws.Deadline.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.Deadline.Types uses a module listed above it, which is the healthy direction.
22→7 Aws.Deadline.Types uses Aws✕
- Connections
- 429 pairs of types, where a type in Aws.Deadline.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.Deadline.Types.AcceleratorCapabilities→Aws.StructureAws.Deadline.Types.AcceleratorCountRange→Aws.StructureAws.Deadline.Types.AcceleratorSelection→Aws.StructureAws.Deadline.Types.AcceleratorTotalMemoryMiBRange→Aws.StructureAws.Deadline.Types.AccessDeniedException→Aws.StructureAws.Deadline.Types.AcquiredLimit→Aws.StructureAws.Deadline.Types.AssignedEnvironmentEnterSessionActionDefinition→Aws.StructureAws.Deadline.Types.AssignedEnvironmentExitSessionActionDefinition→Aws.StructureAws.Deadline.Types.AssignedSession→Aws.StructureAws.Deadline.Types.AssignedSessionAction→Aws.StructureAws.Deadline.Types.AssignedSessionActionDefinition→Aws.StructureAws.Deadline.Types.AssignedSyncInputJobAttachmentsSessionActionDefinition→Aws.StructureAws.Deadline.Types.AssignedTaskRunSessionActionDefinition→Aws.StructureAws.Deadline.Types.AssociateMemberToFarmRequest→Aws.StructureAws.Deadline.Types.AssociateMemberToFarmResponse→Aws.EmptyStructureAws.Deadline.Types.AssociateMemberToFleetRequest→Aws.StructureAws.Deadline.Types.AssociateMemberToFleetResponse→Aws.EmptyStructureAws.Deadline.Types.AssociateMemberToJobRequest→Aws.StructureAws.Deadline.Types.AssociateMemberToJobResponse→Aws.EmptyStructureAws.Deadline.Types.AssociateMemberToQueueRequest→Aws.StructureAws.Deadline.Types.AssociateMemberToQueueResponse→Aws.EmptyStructureAws.Deadline.Types.AssumeFleetRoleForReadRequest→Aws.StructureAws.Deadline.Types.AssumeFleetRoleForReadResponse→Aws.StructureAws.Deadline.Types.AssumeFleetRoleForWorkerRequest→Aws.StructureAws.Deadline.Types.AssumeFleetRoleForWorkerResponse→Aws.Structure
- Direction
- Aws.Deadline.Types uses Aws, so a change to Aws can break Aws.Deadline.Types, while a change to Aws.Deadline.Types can't break Aws.
- Position
- Below the diagonal: Aws.Deadline.Types uses a module listed above it, which is the healthy direction.
23→2 Aws.DevOpsAgent.Types uses Aws.Structure✕
- Connections
- 22 pairs of types, where a type in Aws.DevOpsAgent.Types uses a type in Aws.Structure.
- The types involved
Aws.DevOpsAgent.Types.AdditionalServiceDetails→Aws.Structure.UnionAws.DevOpsAgent.Types.AdditionalServiceRegistrationStep→Aws.Structure.UnionAws.DevOpsAgent.Types.AssetContent→Aws.Structure.UnionAws.DevOpsAgent.Types.AssetFileBody→Aws.Structure.UnionAws.DevOpsAgent.Types.AssistantMessageBlock→Aws.Structure.UnionAws.DevOpsAgent.Types.DatadogAuthorizationConfig→Aws.Structure.UnionAws.DevOpsAgent.Types.DynatraceServiceAuthorizationConfig→Aws.Structure.UnionAws.DevOpsAgent.Types.MCPServerAuthorizationConfig→Aws.Structure.UnionAws.DevOpsAgent.Types.Message→Aws.Structure.UnionAws.DevOpsAgent.Types.NetworkAccessConfiguration→Aws.Structure.UnionAws.DevOpsAgent.Types.NewRelicServiceAuthorizationConfig→Aws.Structure.UnionAws.DevOpsAgent.Types.PagerDutyAuthorizationConfig→Aws.Structure.UnionAws.DevOpsAgent.Types.PrivateConnectionMode→Aws.Structure.UnionAws.DevOpsAgent.Types.Recurrence→Aws.Structure.UnionAws.DevOpsAgent.Types.RemoteAgentAuthorizationConfig→Aws.Structure.UnionAws.DevOpsAgent.Types.ScheduleSpec→Aws.Structure.UnionAws.DevOpsAgent.Types.SendMessageContentBlockDelta→Aws.Structure.UnionAws.DevOpsAgent.Types.ServiceConfiguration→Aws.Structure.UnionAws.DevOpsAgent.Types.ServiceDetails→Aws.Structure.UnionAws.DevOpsAgent.Types.ServiceNowServiceAuthorizationConfig→Aws.Structure.UnionAws.DevOpsAgent.Types.TriggerCondition→Aws.Structure.UnionAws.DevOpsAgent.Types.UserMessageBlock→Aws.Structure.Union
- Direction
- Aws.DevOpsAgent.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.DevOpsAgent.Types, while a change to Aws.DevOpsAgent.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.DevOpsAgent.Types uses a module listed above it, which is the healthy direction.
23→7 Aws.DevOpsAgent.Types uses Aws✕
- Connections
- 287 pairs of types, where a type in Aws.DevOpsAgent.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.DevOpsAgent.Types.AWSConfiguration→Aws.StructureAws.DevOpsAgent.Types.AccessDeniedException→Aws.StructureAws.DevOpsAgent.Types.AdditionalServiceDetails→Aws.StructureAws.DevOpsAgent.Types.AdditionalServiceRegistrationStep→Aws.StructureAws.DevOpsAgent.Types.AgentSpace→Aws.StructureAws.DevOpsAgent.Types.ApprovalAction→Aws.StructureAws.DevOpsAgent.Types.ApprovalPattern→Aws.StructureAws.DevOpsAgent.Types.Asset→Aws.StructureAws.DevOpsAgent.Types.AssetContent→Aws.StructureAws.DevOpsAgent.Types.AssetFile→Aws.StructureAws.DevOpsAgent.Types.AssetFileBody→Aws.StructureAws.DevOpsAgent.Types.AssetFileContent→Aws.StructureAws.DevOpsAgent.Types.AssetFileSummary→Aws.StructureAws.DevOpsAgent.Types.AssetSourceUrlContent→Aws.StructureAws.DevOpsAgent.Types.AssetTypeSummary→Aws.StructureAws.DevOpsAgent.Types.AssetVersionMetadata→Aws.StructureAws.DevOpsAgent.Types.AssetZipContent→Aws.StructureAws.DevOpsAgent.Types.AssistantMessageBlock→Aws.StructureAws.DevOpsAgent.Types.AssociateServiceInput→Aws.StructureAws.DevOpsAgent.Types.AssociateServiceOutput→Aws.StructureAws.DevOpsAgent.Types.Association→Aws.StructureAws.DevOpsAgent.Types.AzureConfiguration→Aws.StructureAws.DevOpsAgent.Types.AzureDevOpsConfiguration→Aws.StructureAws.DevOpsAgent.Types.CapabilityConfiguration→Aws.StructureAws.DevOpsAgent.Types.ChatExecution→Aws.Structure
- Direction
- Aws.DevOpsAgent.Types uses Aws, so a change to Aws can break Aws.DevOpsAgent.Types, while a change to Aws.DevOpsAgent.Types can't break Aws.
- Position
- Below the diagonal: Aws.DevOpsAgent.Types uses a module listed above it, which is the healthy direction.
24→2 Aws.GroundStation.Types uses Aws.Structure✕
- Connections
- 13 pairs of types, where a type in Aws.GroundStation.Types uses a type in Aws.Structure.
- The types involved
Aws.GroundStation.Types.AzElSegmentsData→Aws.Structure.UnionAws.GroundStation.Types.ConfigDetails→Aws.Structure.UnionAws.GroundStation.Types.ConfigTypeData→Aws.Structure.UnionAws.GroundStation.Types.CreateEndpointDetails→Aws.Structure.UnionAws.GroundStation.Types.DownlinkDataflowDetails→Aws.Structure.UnionAws.GroundStation.Types.EphemerisData→Aws.Structure.UnionAws.GroundStation.Types.EphemerisFilter→Aws.Structure.UnionAws.GroundStation.Types.EphemerisTypeDescription→Aws.Structure.UnionAws.GroundStation.Types.KmsKey→Aws.Structure.UnionAws.GroundStation.Types.ProgramTrackSettings→Aws.Structure.UnionAws.GroundStation.Types.ReservationDetails→Aws.Structure.UnionAws.GroundStation.Types.TelemetrySinkData→Aws.Structure.UnionAws.GroundStation.Types.UplinkDataflowDetails→Aws.Structure.Union
- Direction
- Aws.GroundStation.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.GroundStation.Types, while a change to Aws.GroundStation.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.GroundStation.Types uses a module listed above it, which is the healthy direction.
24→7 Aws.GroundStation.Types uses Aws✕
- Connections
- 164 pairs of types, where a type in Aws.GroundStation.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.GroundStation.Types.AgentDetails→Aws.StructureAws.GroundStation.Types.AggregateStatus→Aws.StructureAws.GroundStation.Types.AntennaDemodDecodeDetails→Aws.StructureAws.GroundStation.Types.AntennaDownlinkConfig→Aws.StructureAws.GroundStation.Types.AntennaDownlinkDemodDecodeConfig→Aws.StructureAws.GroundStation.Types.AntennaListItem→Aws.StructureAws.GroundStation.Types.AntennaUplinkConfig→Aws.StructureAws.GroundStation.Types.AwsGroundStationAgentEndpoint→Aws.StructureAws.GroundStation.Types.AzElEphemeris→Aws.StructureAws.GroundStation.Types.AzElEphemerisFilter→Aws.StructureAws.GroundStation.Types.AzElProgramTrackSettings→Aws.StructureAws.GroundStation.Types.AzElSegment→Aws.StructureAws.GroundStation.Types.AzElSegments→Aws.StructureAws.GroundStation.Types.AzElSegmentsData→Aws.StructureAws.GroundStation.Types.CancelContactRequest→Aws.StructureAws.GroundStation.Types.ComponentStatusData→Aws.StructureAws.GroundStation.Types.ComponentVersion→Aws.StructureAws.GroundStation.Types.ConfigDetails→Aws.StructureAws.GroundStation.Types.ConfigIdResponse→Aws.StructureAws.GroundStation.Types.ConfigListItem→Aws.StructureAws.GroundStation.Types.ConfigTypeData→Aws.StructureAws.GroundStation.Types.ConnectionDetails→Aws.StructureAws.GroundStation.Types.ContactData→Aws.StructureAws.GroundStation.Types.ContactIdResponse→Aws.StructureAws.GroundStation.Types.ContactReservationDetails→Aws.Structure
- Direction
- Aws.GroundStation.Types uses Aws, so a change to Aws can break Aws.GroundStation.Types, while a change to Aws.GroundStation.Types can't break Aws.
- Position
- Below the diagonal: Aws.GroundStation.Types uses a module listed above it, which is the healthy direction.
25→2 Aws.MailManager.Types uses Aws.Structure✕
- Connections
- 21 pairs of types, where a type in Aws.MailManager.Types uses a type in Aws.Structure.
- The types involved
Aws.MailManager.Types.ArchiveBooleanToEvaluate→Aws.Structure.UnionAws.MailManager.Types.ArchiveFilterCondition→Aws.Structure.UnionAws.MailManager.Types.ArchiveRetention→Aws.Structure.UnionAws.MailManager.Types.ArchiveStringToEvaluate→Aws.Structure.UnionAws.MailManager.Types.ExportDestinationConfiguration→Aws.Structure.UnionAws.MailManager.Types.IngressBooleanToEvaluate→Aws.Structure.UnionAws.MailManager.Types.IngressIpToEvaluate→Aws.Structure.UnionAws.MailManager.Types.IngressIpv6ToEvaluate→Aws.Structure.UnionAws.MailManager.Types.IngressPointConfiguration→Aws.Structure.UnionAws.MailManager.Types.IngressStringToEvaluate→Aws.Structure.UnionAws.MailManager.Types.IngressTlsProtocolToEvaluate→Aws.Structure.UnionAws.MailManager.Types.NetworkConfiguration→Aws.Structure.UnionAws.MailManager.Types.PolicyCondition→Aws.Structure.UnionAws.MailManager.Types.RelayAuthentication→Aws.Structure.UnionAws.MailManager.Types.RuleAction→Aws.Structure.UnionAws.MailManager.Types.RuleBooleanToEvaluate→Aws.Structure.UnionAws.MailManager.Types.RuleCondition→Aws.Structure.UnionAws.MailManager.Types.RuleIpToEvaluate→Aws.Structure.UnionAws.MailManager.Types.RuleNumberToEvaluate→Aws.Structure.UnionAws.MailManager.Types.RuleStringToEvaluate→Aws.Structure.UnionAws.MailManager.Types.RuleVerdictToEvaluate→Aws.Structure.Union
- Direction
- Aws.MailManager.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.MailManager.Types, while a change to Aws.MailManager.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.MailManager.Types uses a module listed above it, which is the healthy direction.
25→7 Aws.MailManager.Types uses Aws✕
- Connections
- 208 pairs of types, where a type in Aws.MailManager.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.MailManager.Types.AccessDeniedException→Aws.StructureAws.MailManager.Types.AddHeaderAction→Aws.StructureAws.MailManager.Types.AddonInstance→Aws.StructureAws.MailManager.Types.AddonSubscription→Aws.StructureAws.MailManager.Types.AddressFilter→Aws.StructureAws.MailManager.Types.AddressList→Aws.StructureAws.MailManager.Types.Analysis→Aws.StructureAws.MailManager.Types.Archive→Aws.StructureAws.MailManager.Types.ArchiveAction→Aws.StructureAws.MailManager.Types.ArchiveBooleanExpression→Aws.StructureAws.MailManager.Types.ArchiveBooleanToEvaluate→Aws.StructureAws.MailManager.Types.ArchiveFilterCondition→Aws.StructureAws.MailManager.Types.ArchiveFilters→Aws.StructureAws.MailManager.Types.ArchiveRetention→Aws.StructureAws.MailManager.Types.ArchiveStringExpression→Aws.StructureAws.MailManager.Types.ArchiveStringToEvaluate→Aws.StructureAws.MailManager.Types.BounceAction→Aws.StructureAws.MailManager.Types.ConflictException→Aws.StructureAws.MailManager.Types.CreateAddonInstanceRequest→Aws.StructureAws.MailManager.Types.CreateAddonInstanceResponse→Aws.StructureAws.MailManager.Types.CreateAddonSubscriptionRequest→Aws.StructureAws.MailManager.Types.CreateAddonSubscriptionResponse→Aws.StructureAws.MailManager.Types.CreateAddressListImportJobRequest→Aws.StructureAws.MailManager.Types.CreateAddressListImportJobResponse→Aws.StructureAws.MailManager.Types.CreateAddressListRequest→Aws.Structure
- Direction
- Aws.MailManager.Types uses Aws, so a change to Aws can break Aws.MailManager.Types, while a change to Aws.MailManager.Types can't break Aws.
- Position
- Below the diagonal: Aws.MailManager.Types uses a module listed above it, which is the healthy direction.
26→2 Aws.MainframeModernization.Types uses Aws.Structure✕
- Connections
- 10 pairs of types, where a type in Aws.MainframeModernization.Types uses a type in Aws.Structure.
- The types involved
Aws.MainframeModernization.Types.BatchJobDefinition→Aws.Structure.UnionAws.MainframeModernization.Types.BatchJobIdentifier→Aws.Structure.UnionAws.MainframeModernization.Types.DataSetExportConfig→Aws.Structure.UnionAws.MainframeModernization.Types.DataSetImportConfig→Aws.Structure.UnionAws.MainframeModernization.Types.DatasetDetailOrgAttributes→Aws.Structure.UnionAws.MainframeModernization.Types.DatasetOrgAttributes→Aws.Structure.UnionAws.MainframeModernization.Types.Definition→Aws.Structure.UnionAws.MainframeModernization.Types.ExternalLocation→Aws.Structure.UnionAws.MainframeModernization.Types.JobIdentifier→Aws.Structure.UnionAws.MainframeModernization.Types.StorageConfiguration→Aws.Structure.Union
- Direction
- Aws.MainframeModernization.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.MainframeModernization.Types, while a change to Aws.MainframeModernization.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.MainframeModernization.Types uses a module listed above it, which is the healthy direction.
26→7 Aws.MainframeModernization.Types uses Aws✕
- Connections
- 133 pairs of types, where a type in Aws.MainframeModernization.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.MainframeModernization.Types.AccessDeniedException→Aws.StructureAws.MainframeModernization.Types.AlternateKey→Aws.StructureAws.MainframeModernization.Types.ApplicationSummary→Aws.StructureAws.MainframeModernization.Types.ApplicationVersionSummary→Aws.StructureAws.MainframeModernization.Types.BatchJobDefinition→Aws.StructureAws.MainframeModernization.Types.BatchJobExecutionSummary→Aws.StructureAws.MainframeModernization.Types.BatchJobIdentifier→Aws.StructureAws.MainframeModernization.Types.CancelBatchJobExecutionRequest→Aws.StructureAws.MainframeModernization.Types.CancelBatchJobExecutionResponse→Aws.EmptyStructureAws.MainframeModernization.Types.ConflictException→Aws.StructureAws.MainframeModernization.Types.CreateApplicationRequest→Aws.StructureAws.MainframeModernization.Types.CreateApplicationResponse→Aws.StructureAws.MainframeModernization.Types.CreateDataSetExportTaskRequest→Aws.StructureAws.MainframeModernization.Types.CreateDataSetExportTaskResponse→Aws.StructureAws.MainframeModernization.Types.CreateDataSetImportTaskRequest→Aws.StructureAws.MainframeModernization.Types.CreateDataSetImportTaskResponse→Aws.StructureAws.MainframeModernization.Types.CreateDeploymentRequest→Aws.StructureAws.MainframeModernization.Types.CreateDeploymentResponse→Aws.StructureAws.MainframeModernization.Types.CreateEnvironmentRequest→Aws.StructureAws.MainframeModernization.Types.CreateEnvironmentResponse→Aws.StructureAws.MainframeModernization.Types.DataSet→Aws.StructureAws.MainframeModernization.Types.DataSetExportConfig→Aws.StructureAws.MainframeModernization.Types.DataSetExportItem→Aws.StructureAws.MainframeModernization.Types.DataSetExportSummary→Aws.StructureAws.MainframeModernization.Types.DataSetExportTask→Aws.Structure
- Direction
- Aws.MainframeModernization.Types uses Aws, so a change to Aws can break Aws.MainframeModernization.Types, while a change to Aws.MainframeModernization.Types can't break Aws.
- Position
- Below the diagonal: Aws.MainframeModernization.Types uses a module listed above it, which is the healthy direction.
27→2 Aws.MediaConnect.Types uses Aws.Structure✕
- Connections
- 34 pairs of types, where a type in Aws.MediaConnect.Types uses a type in Aws.Structure. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.MediaConnect.Types.DestinationEndpointAssociatedResourceDetails→Aws.Structure.UnionAws.MediaConnect.Types.DestinationEndpointConfiguration→Aws.Structure.UnionAws.MediaConnect.Types.DestinationEndpointConnectionDetails→Aws.Structure.UnionAws.MediaConnect.Types.DestinationEndpointFilter→Aws.Structure.UnionAws.MediaConnect.Types.EndpointEncryptionConfiguration→Aws.Structure.UnionAws.MediaConnect.Types.FailoverRouterInputProtocolConfiguration→Aws.Structure.UnionAws.MediaConnect.Types.FlowTransitEncryptionKeyConfiguration→Aws.Structure.UnionAws.MediaConnect.Types.MaintenanceConfiguration→Aws.Structure.UnionAws.MediaConnect.Types.MaintenanceSchedule→Aws.Structure.UnionAws.MediaConnect.Types.MediaLiveTransitEncryptionKeyConfiguration→Aws.Structure.UnionAws.MediaConnect.Types.MergeRouterInputProtocolConfiguration→Aws.Structure.UnionAws.MediaConnect.Types.ResourceShareDetails→Aws.Structure.UnionAws.MediaConnect.Types.RouterContentQualityAnalysisConfiguration→Aws.Structure.UnionAws.MediaConnect.Types.RouterInputConfiguration→Aws.Structure.UnionAws.MediaConnect.Types.RouterInputFilter→Aws.Structure.UnionAws.MediaConnect.Types.RouterInputMetadata→Aws.Structure.UnionAws.MediaConnect.Types.RouterInputProtocolConfiguration→Aws.Structure.UnionAws.MediaConnect.Types.RouterInputStreamDetails→Aws.Structure.UnionAws.MediaConnect.Types.RouterInputTransitEncryptionKeyConfiguration→Aws.Structure.UnionAws.MediaConnect.Types.RouterNetworkInterfaceConfiguration→Aws.Structure.UnionAws.MediaConnect.Types.RouterNetworkInterfaceFilter→Aws.Structure.UnionAws.MediaConnect.Types.RouterOutputConfiguration→Aws.Structure.UnionAws.MediaConnect.Types.RouterOutputFilter→Aws.Structure.UnionAws.MediaConnect.Types.RouterOutputProtocolConfiguration→Aws.Structure.UnionAws.MediaConnect.Types.RouterOutputStreamDetails→Aws.Structure.Union
- Direction
- Aws.MediaConnect.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.MediaConnect.Types, while a change to Aws.MediaConnect.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.MediaConnect.Types uses a module listed above it, which is the healthy direction.
27→7 Aws.MediaConnect.Types uses Aws✕
- Connections
- 437 pairs of types, where a type in Aws.MediaConnect.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.MediaConnect.Types.AddBridgeFlowSourceRequest→Aws.StructureAws.MediaConnect.Types.AddBridgeNetworkOutputRequest→Aws.StructureAws.MediaConnect.Types.AddBridgeNetworkSourceRequest→Aws.StructureAws.MediaConnect.Types.AddBridgeOutputRequest→Aws.StructureAws.MediaConnect.Types.AddBridgeOutputsRequest→Aws.StructureAws.MediaConnect.Types.AddBridgeOutputsResponse→Aws.StructureAws.MediaConnect.Types.AddBridgeSourceRequest→Aws.StructureAws.MediaConnect.Types.AddBridgeSourcesRequest→Aws.StructureAws.MediaConnect.Types.AddBridgeSourcesResponse→Aws.StructureAws.MediaConnect.Types.AddEgressGatewayBridgeRequest→Aws.StructureAws.MediaConnect.Types.AddFlowMediaStreamsRequest→Aws.StructureAws.MediaConnect.Types.AddFlowMediaStreamsResponse→Aws.StructureAws.MediaConnect.Types.AddFlowOutputs420Exception→Aws.StructureAws.MediaConnect.Types.AddFlowOutputsRequest→Aws.StructureAws.MediaConnect.Types.AddFlowOutputsResponse→Aws.StructureAws.MediaConnect.Types.AddFlowSourcesRequest→Aws.StructureAws.MediaConnect.Types.AddFlowSourcesResponse→Aws.StructureAws.MediaConnect.Types.AddFlowVpcInterfacesRequest→Aws.StructureAws.MediaConnect.Types.AddFlowVpcInterfacesResponse→Aws.StructureAws.MediaConnect.Types.AddIngressGatewayBridgeRequest→Aws.StructureAws.MediaConnect.Types.AddMaintenance→Aws.StructureAws.MediaConnect.Types.AddMediaStreamRequest→Aws.StructureAws.MediaConnect.Types.AddOutputRequest→Aws.StructureAws.MediaConnect.Types.AudioMonitoringSetting→Aws.StructureAws.MediaConnect.Types.AutomaticEncryptionKeyConfiguration→Aws.EmptyStructure
- Direction
- Aws.MediaConnect.Types uses Aws, so a change to Aws can break Aws.MediaConnect.Types, while a change to Aws.MediaConnect.Types can't break Aws.
- Position
- Below the diagonal: Aws.MediaConnect.Types uses a module listed above it, which is the healthy direction.
28→2 Aws.NetworkSecurityManager.Types uses Aws.Structure✕
- Connections
- 10 pairs of types, where a type in Aws.NetworkSecurityManager.Types uses a type in Aws.Structure.
- The types involved
Aws.NetworkSecurityManager.Types.AccountFilter→Aws.Structure.UnionAws.NetworkSecurityManager.Types.AdminScopeFilter→Aws.Structure.UnionAws.NetworkSecurityManager.Types.AdminScopeFilterInput→Aws.Structure.UnionAws.NetworkSecurityManager.Types.AssociatedTemplateOrRule→Aws.Structure.UnionAws.NetworkSecurityManager.Types.FirewallSyncReason→Aws.Structure.UnionAws.NetworkSecurityManager.Types.OutOfSyncReasonsView→Aws.Structure.UnionAws.NetworkSecurityManager.Types.RemediationIssuesView→Aws.Structure.UnionAws.NetworkSecurityManager.Types.ResourceCriteria→Aws.Structure.UnionAws.NetworkSecurityManager.Types.ResourceLogicalExpression→Aws.Structure.UnionAws.NetworkSecurityManager.Types.TemplateOrRuleReference→Aws.Structure.Union
- Direction
- Aws.NetworkSecurityManager.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.NetworkSecurityManager.Types, while a change to Aws.NetworkSecurityManager.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.NetworkSecurityManager.Types uses a module listed above it, which is the healthy direction.
28→7 Aws.NetworkSecurityManager.Types uses Aws✕
- Connections
- 143 pairs of types, where a type in Aws.NetworkSecurityManager.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.NetworkSecurityManager.Types.AccessDeniedException→Aws.StructureAws.NetworkSecurityManager.Types.AccountFilter→Aws.StructureAws.NetworkSecurityManager.Types.AccountReference→Aws.StructureAws.NetworkSecurityManager.Types.AccountSet→Aws.StructureAws.NetworkSecurityManager.Types.AdminAccountDetails→Aws.StructureAws.NetworkSecurityManager.Types.AdminAccountSummary→Aws.StructureAws.NetworkSecurityManager.Types.AdminFirewallTypeScope→Aws.StructureAws.NetworkSecurityManager.Types.AdminScope→Aws.StructureAws.NetworkSecurityManager.Types.AdminScopeFilter→Aws.StructureAws.NetworkSecurityManager.Types.AdminScopeFilterInput→Aws.StructureAws.NetworkSecurityManager.Types.AdminScopeInput→Aws.StructureAws.NetworkSecurityManager.Types.AdminScopeSelection→Aws.StructureAws.NetworkSecurityManager.Types.AdminScopeSelectionInput→Aws.StructureAws.NetworkSecurityManager.Types.AlbConfiguration→Aws.StructureAws.NetworkSecurityManager.Types.AssociatedPolicy→Aws.StructureAws.NetworkSecurityManager.Types.AssociatedRule→Aws.StructureAws.NetworkSecurityManager.Types.AssociatedScope→Aws.StructureAws.NetworkSecurityManager.Types.AssociatedTemplateOrRule→Aws.StructureAws.NetworkSecurityManager.Types.ConfigurationIssue→Aws.StructureAws.NetworkSecurityManager.Types.ConflictException→Aws.StructureAws.NetworkSecurityManager.Types.CreateDeploymentInput→Aws.StructureAws.NetworkSecurityManager.Types.CreateDeploymentOutput→Aws.StructureAws.NetworkSecurityManager.Types.CreateDeploymentSnapshotInput→Aws.StructureAws.NetworkSecurityManager.Types.CreateDeploymentSnapshotOutput→Aws.StructureAws.NetworkSecurityManager.Types.CreatePolicyInput→Aws.Structure
- Direction
- Aws.NetworkSecurityManager.Types uses Aws, so a change to Aws can break Aws.NetworkSecurityManager.Types, while a change to Aws.NetworkSecurityManager.Types can't break Aws.
- Position
- Below the diagonal: Aws.NetworkSecurityManager.Types uses a module listed above it, which is the healthy direction.
29→2 Aws.PaymentCryptographyData.Types uses Aws.Structure✕
- Connections
- 18 pairs of types, where a type in Aws.PaymentCryptographyData.Types uses a type in Aws.Structure.
- The types involved
Aws.PaymentCryptographyData.Types.As2805KekValidationType→Aws.Structure.UnionAws.PaymentCryptographyData.Types.CardGenerationAttributes→Aws.Structure.UnionAws.PaymentCryptographyData.Types.CardVerificationAttributes→Aws.Structure.UnionAws.PaymentCryptographyData.Types.CryptogramAuthResponse→Aws.Structure.UnionAws.PaymentCryptographyData.Types.DerivationMethodAttributes→Aws.Structure.UnionAws.PaymentCryptographyData.Types.DiffieHellmanDerivationData→Aws.Structure.UnionAws.PaymentCryptographyData.Types.EncryptionDecryptionAttributes→Aws.Structure.UnionAws.PaymentCryptographyData.Types.IncomingKeyMaterial→Aws.Structure.UnionAws.PaymentCryptographyData.Types.MacAttributes→Aws.Structure.UnionAws.PaymentCryptographyData.Types.OutgoingKeyMaterial→Aws.Structure.UnionAws.PaymentCryptographyData.Types.PinData→Aws.Structure.UnionAws.PaymentCryptographyData.Types.PinGenerationAttributes→Aws.Structure.UnionAws.PaymentCryptographyData.Types.PinVerificationAttributes→Aws.Structure.UnionAws.PaymentCryptographyData.Types.ReEncryptionAttributes→Aws.Structure.UnionAws.PaymentCryptographyData.Types.SessionKeyDerivation→Aws.Structure.UnionAws.PaymentCryptographyData.Types.SessionKeyDerivationValue→Aws.Structure.UnionAws.PaymentCryptographyData.Types.TranslationIsoFormats→Aws.Structure.UnionAws.PaymentCryptographyData.Types.WrappedKeyMaterial→Aws.Structure.Union
- Direction
- Aws.PaymentCryptographyData.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.PaymentCryptographyData.Types, while a change to Aws.PaymentCryptographyData.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.PaymentCryptographyData.Types uses a module listed above it, which is the healthy direction.
29→7 Aws.PaymentCryptographyData.Types uses Aws✕
- Connections
- 105 pairs of types, where a type in Aws.PaymentCryptographyData.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.PaymentCryptographyData.Types.AccessDeniedException→Aws.StructureAws.PaymentCryptographyData.Types.AmexAttributes→Aws.StructureAws.PaymentCryptographyData.Types.AmexCardSecurityCodeVersion1→Aws.StructureAws.PaymentCryptographyData.Types.AmexCardSecurityCodeVersion2→Aws.StructureAws.PaymentCryptographyData.Types.As2805KekValidationType→Aws.StructureAws.PaymentCryptographyData.Types.As2805PekDerivationAttributes→Aws.StructureAws.PaymentCryptographyData.Types.AsymmetricEncryptionAttributes→Aws.StructureAws.PaymentCryptographyData.Types.CardGenerationAttributes→Aws.StructureAws.PaymentCryptographyData.Types.CardHolderVerificationValue→Aws.StructureAws.PaymentCryptographyData.Types.CardVerificationAttributes→Aws.StructureAws.PaymentCryptographyData.Types.CardVerificationValue1→Aws.StructureAws.PaymentCryptographyData.Types.CardVerificationValue2→Aws.StructureAws.PaymentCryptographyData.Types.CryptogramAuthResponse→Aws.StructureAws.PaymentCryptographyData.Types.CryptogramVerificationArpcMethod1→Aws.StructureAws.PaymentCryptographyData.Types.CryptogramVerificationArpcMethod2→Aws.StructureAws.PaymentCryptographyData.Types.CurrentPinAttributes→Aws.StructureAws.PaymentCryptographyData.Types.DecryptDataInput→Aws.StructureAws.PaymentCryptographyData.Types.DecryptDataOutput→Aws.StructureAws.PaymentCryptographyData.Types.DerivationMethodAttributes→Aws.StructureAws.PaymentCryptographyData.Types.DiffieHellmanDerivationData→Aws.StructureAws.PaymentCryptographyData.Types.DiscoverDynamicCardVerificationCode→Aws.StructureAws.PaymentCryptographyData.Types.DukptAttributes→Aws.StructureAws.PaymentCryptographyData.Types.DukptDerivationAttributes→Aws.StructureAws.PaymentCryptographyData.Types.DukptEncryptionAttributes→Aws.StructureAws.PaymentCryptographyData.Types.DynamicCardVerificationCode→Aws.Structure
- Direction
- Aws.PaymentCryptographyData.Types uses Aws, so a change to Aws can break Aws.PaymentCryptographyData.Types, while a change to Aws.PaymentCryptographyData.Types can't break Aws.
- Position
- Below the diagonal: Aws.PaymentCryptographyData.Types uses a module listed above it, which is the healthy direction.
30→2 Aws.QBusiness.Types uses Aws.Structure✕
- Connections
- 16 pairs of types, where a type in Aws.QBusiness.Types uses a type in Aws.Structure.
- The types involved
Aws.QBusiness.Types.APISchema→Aws.Structure.UnionAws.QBusiness.Types.ChatModeConfiguration→Aws.Structure.UnionAws.QBusiness.Types.ContentSource→Aws.Structure.UnionAws.QBusiness.Types.CopyFromSource→Aws.Structure.UnionAws.QBusiness.Types.DataAccessorAuthenticationConfiguration→Aws.Structure.UnionAws.QBusiness.Types.DocumentAttributeBoostingConfiguration→Aws.Structure.UnionAws.QBusiness.Types.DocumentAttributeValue→Aws.Structure.UnionAws.QBusiness.Types.DocumentContent→Aws.Structure.UnionAws.QBusiness.Types.IdentityProviderConfiguration→Aws.Structure.UnionAws.QBusiness.Types.PluginAuthConfiguration→Aws.Structure.UnionAws.QBusiness.Types.Principal→Aws.Structure.UnionAws.QBusiness.Types.RetrieverConfiguration→Aws.Structure.UnionAws.QBusiness.Types.RuleConfiguration→Aws.Structure.UnionAws.QBusiness.Types.SourceDetails→Aws.Structure.UnionAws.QBusiness.Types.SubscriptionPrincipal→Aws.Structure.UnionAws.QBusiness.Types.WebExperienceAuthConfiguration→Aws.Structure.Union
- Direction
- Aws.QBusiness.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.QBusiness.Types, while a change to Aws.QBusiness.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.QBusiness.Types uses a module listed above it, which is the healthy direction.
30→7 Aws.QBusiness.Types uses Aws✕
- Connections
- 325 pairs of types, where a type in Aws.QBusiness.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.QBusiness.Types.APISchema→Aws.StructureAws.QBusiness.Types.AccessConfiguration→Aws.StructureAws.QBusiness.Types.AccessControl→Aws.StructureAws.QBusiness.Types.AccessDeniedException→Aws.StructureAws.QBusiness.Types.ActionConfiguration→Aws.StructureAws.QBusiness.Types.ActionExecution→Aws.StructureAws.QBusiness.Types.ActionExecutionEvent→Aws.StructureAws.QBusiness.Types.ActionExecutionPayloadField→Aws.StructureAws.QBusiness.Types.ActionFilterConfiguration→Aws.StructureAws.QBusiness.Types.ActionReview→Aws.StructureAws.QBusiness.Types.ActionReviewEvent→Aws.StructureAws.QBusiness.Types.ActionReviewPayloadField→Aws.StructureAws.QBusiness.Types.ActionReviewPayloadFieldAllowedValue→Aws.StructureAws.QBusiness.Types.ActionSummary→Aws.StructureAws.QBusiness.Types.Application→Aws.StructureAws.QBusiness.Types.AppliedAttachmentsConfiguration→Aws.StructureAws.QBusiness.Types.AppliedCreatorModeConfiguration→Aws.StructureAws.QBusiness.Types.AppliedOrchestrationConfiguration→Aws.StructureAws.QBusiness.Types.AssociatePermissionRequest→Aws.StructureAws.QBusiness.Types.AssociatePermissionResponse→Aws.StructureAws.QBusiness.Types.AssociatedGroup→Aws.StructureAws.QBusiness.Types.AssociatedUser→Aws.StructureAws.QBusiness.Types.Attachment→Aws.StructureAws.QBusiness.Types.AttachmentInput→Aws.StructureAws.QBusiness.Types.AttachmentInputEvent→Aws.Structure
- Direction
- Aws.QBusiness.Types uses Aws, so a change to Aws can break Aws.QBusiness.Types, while a change to Aws.QBusiness.Types can't break Aws.
- Position
- Below the diagonal: Aws.QBusiness.Types uses a module listed above it, which is the healthy direction.
31→2 Aws.QConnect.Types uses Aws.Structure✕
- Connections
- 31 pairs of types, where a type in Aws.QConnect.Types uses a type in Aws.Structure. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.QConnect.Types.AIAgentConfiguration→Aws.Structure.UnionAws.QConnect.Types.AIPromptTemplateConfiguration→Aws.Structure.UnionAws.QConnect.Types.AgentTarget→Aws.Structure.UnionAws.QConnect.Types.AssistantAssociationInputData→Aws.Structure.UnionAws.QConnect.Types.AssistantAssociationOutputData→Aws.Structure.UnionAws.QConnect.Types.AssociationConfigurationData→Aws.Structure.UnionAws.QConnect.Types.Configuration→Aws.Structure.UnionAws.QConnect.Types.ContentAssociationContents→Aws.Structure.UnionAws.QConnect.Types.ContentFeedbackData→Aws.Structure.UnionAws.QConnect.Types.DataDetails→Aws.Structure.UnionAws.QConnect.Types.DataReference→Aws.Structure.UnionAws.QConnect.Types.KnowledgeSource→Aws.Structure.UnionAws.QConnect.Types.ManagedSourceConfiguration→Aws.Structure.UnionAws.QConnect.Types.MessageData→Aws.Structure.UnionAws.QConnect.Types.MessageTemplateBodyContentProvider→Aws.Structure.UnionAws.QConnect.Types.MessageTemplateContentProvider→Aws.Structure.UnionAws.QConnect.Types.MessageTemplateSourceConfiguration→Aws.Structure.UnionAws.QConnect.Types.MessageTemplateSourceConfigurationSummary→Aws.Structure.UnionAws.QConnect.Types.MultiAgentConfiguration→Aws.Structure.UnionAws.QConnect.Types.OrCondition→Aws.Structure.UnionAws.QConnect.Types.QueryCondition→Aws.Structure.UnionAws.QConnect.Types.QueryInputData→Aws.Structure.UnionAws.QConnect.Types.QuickResponseContentProvider→Aws.Structure.UnionAws.QConnect.Types.QuickResponseDataProvider→Aws.Structure.UnionAws.QConnect.Types.RecommendationTriggerData→Aws.Structure.Union
- Direction
- Aws.QConnect.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.QConnect.Types, while a change to Aws.QConnect.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.QConnect.Types uses a module listed above it, which is the healthy direction.
31→7 Aws.QConnect.Types uses Aws✕
- Connections
- 415 pairs of types, where a type in Aws.QConnect.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.QConnect.Types.AIAgentConfiguration→Aws.StructureAws.QConnect.Types.AIAgentConfigurationData→Aws.StructureAws.QConnect.Types.AIAgentData→Aws.StructureAws.QConnect.Types.AIAgentSummary→Aws.StructureAws.QConnect.Types.AIAgentVersionSummary→Aws.StructureAws.QConnect.Types.AIGuardrailAssessment→Aws.StructureAws.QConnect.Types.AIGuardrailContentPolicyConfig→Aws.StructureAws.QConnect.Types.AIGuardrailContextualGroundingPolicyConfig→Aws.StructureAws.QConnect.Types.AIGuardrailData→Aws.StructureAws.QConnect.Types.AIGuardrailSensitiveInformationPolicyConfig→Aws.StructureAws.QConnect.Types.AIGuardrailSummary→Aws.StructureAws.QConnect.Types.AIGuardrailTopicPolicyConfig→Aws.StructureAws.QConnect.Types.AIGuardrailVersionSummary→Aws.StructureAws.QConnect.Types.AIGuardrailWordPolicyConfig→Aws.StructureAws.QConnect.Types.AIPromptData→Aws.StructureAws.QConnect.Types.AIPromptInferenceConfiguration→Aws.StructureAws.QConnect.Types.AIPromptSummary→Aws.StructureAws.QConnect.Types.AIPromptTemplateConfiguration→Aws.StructureAws.QConnect.Types.AIPromptVersionSummary→Aws.StructureAws.QConnect.Types.AccessDeniedException→Aws.StructureAws.QConnect.Types.ActivateMessageTemplateRequest→Aws.StructureAws.QConnect.Types.ActivateMessageTemplateResponse→Aws.StructureAws.QConnect.Types.AgentAttributes→Aws.StructureAws.QConnect.Types.AgentTarget→Aws.StructureAws.QConnect.Types.AmazonConnectGuideAssociationData→Aws.Structure
- Direction
- Aws.QConnect.Types uses Aws, so a change to Aws can break Aws.QConnect.Types, while a change to Aws.QConnect.Types can't break Aws.
- Position
- Below the diagonal: Aws.QConnect.Types uses a module listed above it, which is the healthy direction.
32→2 Aws.QuickSight.Types uses Aws.Structure✕
- Connections
- 13 pairs of types, where a type in Aws.QuickSight.Types uses a type in Aws.Structure.
- The types involved
Aws.QuickSight.Types.AuthenticationMetadata→Aws.Structure.UnionAws.QuickSight.Types.AuthorizationCodeGrantCredentialsDetails→Aws.Structure.UnionAws.QuickSight.Types.ClientCredentialsDetails→Aws.Structure.UnionAws.QuickSight.Types.CustomPromptInput→Aws.Structure.UnionAws.QuickSight.Types.GeocodePreferenceValue→Aws.Structure.UnionAws.QuickSight.Types.ImageSource→Aws.Structure.UnionAws.QuickSight.Types.ProviderConfig→Aws.Structure.UnionAws.QuickSight.Types.ReadAuthenticationMetadata→Aws.Structure.UnionAws.QuickSight.Types.ReadAuthorizationCodeGrantCredentialsDetails→Aws.Structure.UnionAws.QuickSight.Types.ReadClientCredentialsDetails→Aws.Structure.UnionAws.QuickSight.Types.SpaceQuickSightResourceDetails→Aws.Structure.UnionAws.QuickSight.Types.UserIdentifier→Aws.Structure.UnionAws.QuickSight.Types.UserIndexCapacityFilter→Aws.Structure.Union
- Direction
- Aws.QuickSight.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.QuickSight.Types, while a change to Aws.QuickSight.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.QuickSight.Types uses a module listed above it, which is the healthy direction.
32→7 Aws.QuickSight.Types uses Aws✕
- Connections
- 1770 pairs of types, where a type in Aws.QuickSight.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.QuickSight.Types.APIKeyConnectionMetadata→Aws.StructureAws.QuickSight.Types.AccessControlConfiguration→Aws.StructureAws.QuickSight.Types.AccessDeniedException→Aws.StructureAws.QuickSight.Types.AccountCustomization→Aws.StructureAws.QuickSight.Types.AccountInfo→Aws.StructureAws.QuickSight.Types.AccountSettings→Aws.StructureAws.QuickSight.Types.ActionConnector→Aws.StructureAws.QuickSight.Types.ActionConnectorError→Aws.StructureAws.QuickSight.Types.ActionConnectorSearchFilter→Aws.StructureAws.QuickSight.Types.ActionConnectorSummary→Aws.StructureAws.QuickSight.Types.ActiveIAMPolicyAssignment→Aws.StructureAws.QuickSight.Types.AdHocFilteringOption→Aws.StructureAws.QuickSight.Types.AdditionalNotes→Aws.StructureAws.QuickSight.Types.Agent→Aws.StructureAws.QuickSight.Types.AgentSearchFilter→Aws.StructureAws.QuickSight.Types.AgentSummary→Aws.StructureAws.QuickSight.Types.AggFunction→Aws.StructureAws.QuickSight.Types.AggregateOperation→Aws.StructureAws.QuickSight.Types.Aggregation→Aws.StructureAws.QuickSight.Types.AggregationFunction→Aws.StructureAws.QuickSight.Types.AggregationPartitionBy→Aws.StructureAws.QuickSight.Types.AggregationSortConfiguration→Aws.StructureAws.QuickSight.Types.AllSheetsFilterScopeConfiguration→Aws.EmptyStructureAws.QuickSight.Types.AmazonElasticsearchParameters→Aws.StructureAws.QuickSight.Types.AmazonOpenSearchParameters→Aws.Structure
- Direction
- Aws.QuickSight.Types uses Aws, so a change to Aws can break Aws.QuickSight.Types, while a change to Aws.QuickSight.Types can't break Aws.
- Position
- Below the diagonal: Aws.QuickSight.Types uses a module listed above it, which is the healthy direction.
33→2 Aws.Resiliencehubv2.Types uses Aws.Structure✕
- Connections
- 10 pairs of types, where a type in Aws.Resiliencehubv2.Types uses a type in Aws.Structure.
- The types involved
Aws.Resiliencehubv2.Types.PolicyEventMetadata→Aws.Structure.UnionAws.Resiliencehubv2.Types.ReportOutput→Aws.Structure.UnionAws.Resiliencehubv2.Types.ReportOutputConfiguration→Aws.Structure.UnionAws.Resiliencehubv2.Types.ResourceConfiguration→Aws.Structure.UnionAws.Resiliencehubv2.Types.ServiceEventMetadata→Aws.Structure.UnionAws.Resiliencehubv2.Types.SystemEventMetadata→Aws.Structure.UnionAws.Resiliencehubv2.Types.TestRunSourceEventDetail→Aws.Structure.UnionAws.Resiliencehubv2.Types.TestRunSourceSummary→Aws.Structure.UnionAws.Resiliencehubv2.Types.TestSourceInput→Aws.Structure.UnionAws.Resiliencehubv2.Types.TestSourceSummary→Aws.Structure.Union
- Direction
- Aws.Resiliencehubv2.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.Resiliencehubv2.Types, while a change to Aws.Resiliencehubv2.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.Resiliencehubv2.Types uses a module listed above it, which is the healthy direction.
33→7 Aws.Resiliencehubv2.Types uses Aws✕
- Connections
- 285 pairs of types, where a type in Aws.Resiliencehubv2.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.Resiliencehubv2.Types.AccessDeniedException→Aws.StructureAws.Resiliencehubv2.Types.Achievability→Aws.StructureAws.Resiliencehubv2.Types.AlarmStateChangeDetail→Aws.StructureAws.Resiliencehubv2.Types.Assertion→Aws.StructureAws.Resiliencehubv2.Types.AssertionCreatedMetadata→Aws.StructureAws.Resiliencehubv2.Types.AssertionDeletedMetadata→Aws.StructureAws.Resiliencehubv2.Types.AssertionUpdatedMetadata→Aws.StructureAws.Resiliencehubv2.Types.AssessmentCost→Aws.StructureAws.Resiliencehubv2.Types.AssessmentSummary→Aws.StructureAws.Resiliencehubv2.Types.AssociatedSystem→Aws.StructureAws.Resiliencehubv2.Types.AvailabilitySlo→Aws.StructureAws.Resiliencehubv2.Types.ConflictException→Aws.StructureAws.Resiliencehubv2.Types.CreateAssertionRequest→Aws.StructureAws.Resiliencehubv2.Types.CreateAssertionResponse→Aws.StructureAws.Resiliencehubv2.Types.CreateInputSourceRequest→Aws.StructureAws.Resiliencehubv2.Types.CreateInputSourceResponse→Aws.StructureAws.Resiliencehubv2.Types.CreatePolicyRequest→Aws.StructureAws.Resiliencehubv2.Types.CreatePolicyResponse→Aws.StructureAws.Resiliencehubv2.Types.CreateReportRequest→Aws.StructureAws.Resiliencehubv2.Types.CreateReportResponse→Aws.StructureAws.Resiliencehubv2.Types.CreateServiceFunctionRequest→Aws.StructureAws.Resiliencehubv2.Types.CreateServiceFunctionResourcesRequest→Aws.StructureAws.Resiliencehubv2.Types.CreateServiceFunctionResourcesResponse→Aws.StructureAws.Resiliencehubv2.Types.CreateServiceFunctionResponse→Aws.StructureAws.Resiliencehubv2.Types.CreateServiceRequest→Aws.Structure
- Direction
- Aws.Resiliencehubv2.Types uses Aws, so a change to Aws can break Aws.Resiliencehubv2.Types, while a change to Aws.Resiliencehubv2.Types can't break Aws.
- Position
- Below the diagonal: Aws.Resiliencehubv2.Types uses a module listed above it, which is the healthy direction.
34→7 Aws.Resources uses Aws✕
- Connections
- 1 pair of types, where a type in Aws.Resources uses a type in Aws.
- The types involved
Aws.Resources.Collection→Aws.Deprecations
- Direction
- Aws.Resources uses Aws, so a change to Aws can break Aws.Resources, while a change to Aws.Resources can't break Aws.
- Position
- Below the diagonal: Aws.Resources uses a module listed above it, which is the healthy direction.
35→2 Aws.SSMIncidents.Types uses Aws.Structure✕
- Connections
- 13 pairs of types, where a type in Aws.SSMIncidents.Types uses a type in Aws.Structure.
- The types involved
Aws.SSMIncidents.Types.Action→Aws.Structure.UnionAws.SSMIncidents.Types.AttributeValueList→Aws.Structure.UnionAws.SSMIncidents.Types.AutomationExecution→Aws.Structure.UnionAws.SSMIncidents.Types.ChatChannel→Aws.Structure.UnionAws.SSMIncidents.Types.Condition→Aws.Structure.UnionAws.SSMIncidents.Types.DynamicSsmParameterValue→Aws.Structure.UnionAws.SSMIncidents.Types.EventReference→Aws.Structure.UnionAws.SSMIncidents.Types.FindingDetails→Aws.Structure.UnionAws.SSMIncidents.Types.Integration→Aws.Structure.UnionAws.SSMIncidents.Types.ItemValue→Aws.Structure.UnionAws.SSMIncidents.Types.NotificationTargetItem→Aws.Structure.UnionAws.SSMIncidents.Types.RelatedItemsUpdate→Aws.Structure.UnionAws.SSMIncidents.Types.UpdateReplicationSetAction→Aws.Structure.Union
- Direction
- Aws.SSMIncidents.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.SSMIncidents.Types, while a change to Aws.SSMIncidents.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.SSMIncidents.Types uses a module listed above it, which is the healthy direction.
35→7 Aws.SSMIncidents.Types uses Aws✕
- Connections
- 109 pairs of types, where a type in Aws.SSMIncidents.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.SSMIncidents.Types.AccessDeniedException→Aws.StructureAws.SSMIncidents.Types.Action→Aws.StructureAws.SSMIncidents.Types.AddRegionAction→Aws.StructureAws.SSMIncidents.Types.AttributeValueList→Aws.StructureAws.SSMIncidents.Types.AutomationExecution→Aws.StructureAws.SSMIncidents.Types.BatchGetIncidentFindingsError→Aws.StructureAws.SSMIncidents.Types.BatchGetIncidentFindingsInput→Aws.StructureAws.SSMIncidents.Types.BatchGetIncidentFindingsOutput→Aws.StructureAws.SSMIncidents.Types.ChatChannel→Aws.StructureAws.SSMIncidents.Types.CloudFormationStackUpdate→Aws.StructureAws.SSMIncidents.Types.CodeDeployDeployment→Aws.StructureAws.SSMIncidents.Types.Condition→Aws.StructureAws.SSMIncidents.Types.ConflictException→Aws.StructureAws.SSMIncidents.Types.CreateReplicationSetInput→Aws.StructureAws.SSMIncidents.Types.CreateReplicationSetOutput→Aws.StructureAws.SSMIncidents.Types.CreateResponsePlanInput→Aws.StructureAws.SSMIncidents.Types.CreateResponsePlanOutput→Aws.StructureAws.SSMIncidents.Types.CreateTimelineEventInput→Aws.StructureAws.SSMIncidents.Types.CreateTimelineEventOutput→Aws.StructureAws.SSMIncidents.Types.DeleteIncidentRecordInput→Aws.StructureAws.SSMIncidents.Types.DeleteIncidentRecordOutput→Aws.EmptyStructureAws.SSMIncidents.Types.DeleteRegionAction→Aws.StructureAws.SSMIncidents.Types.DeleteReplicationSetInput→Aws.StructureAws.SSMIncidents.Types.DeleteReplicationSetOutput→Aws.EmptyStructureAws.SSMIncidents.Types.DeleteResourcePolicyInput→Aws.Structure
- Direction
- Aws.SSMIncidents.Types uses Aws, so a change to Aws can break Aws.SSMIncidents.Types, while a change to Aws.SSMIncidents.Types can't break Aws.
- Position
- Below the diagonal: Aws.SSMIncidents.Types uses a module listed above it, which is the healthy direction.
36→2 Aws.SageMaker.Types uses Aws.Structure✕
- Connections
- 15 pairs of types, where a type in Aws.SageMaker.Types uses a type in Aws.Structure.
- The types involved
Aws.SageMaker.Types.AIAdapterSource→Aws.Structure.UnionAws.SageMaker.Types.AIBenchmarkTarget→Aws.Structure.UnionAws.SageMaker.Types.AIDatasetConfig→Aws.Structure.UnionAws.SageMaker.Types.AIModelSource→Aws.Structure.UnionAws.SageMaker.Types.AutoMLProblemTypeConfig→Aws.Structure.UnionAws.SageMaker.Types.AutoMLProblemTypeResolvedAttributes→Aws.Structure.UnionAws.SageMaker.Types.ClusterInstanceStorageConfig→Aws.Structure.UnionAws.SageMaker.Types.CollectionConfig→Aws.Structure.UnionAws.SageMaker.Types.CustomFileSystem→Aws.Structure.UnionAws.SageMaker.Types.CustomFileSystemConfig→Aws.Structure.UnionAws.SageMaker.Types.EventMetadata→Aws.Structure.UnionAws.SageMaker.Types.MetricSpecification→Aws.Structure.UnionAws.SageMaker.Types.OptimizationConfig→Aws.Structure.UnionAws.SageMaker.Types.ScalingPolicy→Aws.Structure.UnionAws.SageMaker.Types.WorkloadSpec→Aws.Structure.Union
- Direction
- Aws.SageMaker.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.SageMaker.Types, while a change to Aws.SageMaker.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.SageMaker.Types uses a module listed above it, which is the healthy direction.
36→7 Aws.SageMaker.Types uses Aws✕
- Connections
- 1580 pairs of types, where a type in Aws.SageMaker.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.SageMaker.Types.AIAdapterModelPackageEntry→Aws.StructureAws.SageMaker.Types.AIAdapterS3Entry→Aws.StructureAws.SageMaker.Types.AIAdapterSource→Aws.StructureAws.SageMaker.Types.AIBenchmarkEndpoint→Aws.StructureAws.SageMaker.Types.AIBenchmarkInferenceComponent→Aws.StructureAws.SageMaker.Types.AIBenchmarkJobSummary→Aws.StructureAws.SageMaker.Types.AIBenchmarkNetworkConfig→Aws.StructureAws.SageMaker.Types.AIBenchmarkOutputConfig→Aws.StructureAws.SageMaker.Types.AIBenchmarkOutputResult→Aws.StructureAws.SageMaker.Types.AIBenchmarkTarget→Aws.StructureAws.SageMaker.Types.AICapacityReservationConfig→Aws.StructureAws.SageMaker.Types.AICloudWatchLogs→Aws.StructureAws.SageMaker.Types.AIDatasetConfig→Aws.StructureAws.SageMaker.Types.AIMlflowConfig→Aws.StructureAws.SageMaker.Types.AIModelSource→Aws.StructureAws.SageMaker.Types.AIModelSourceS3→Aws.StructureAws.SageMaker.Types.AIRecommendation→Aws.StructureAws.SageMaker.Types.AIRecommendationAdapterDetails→Aws.StructureAws.SageMaker.Types.AIRecommendationComputeSpec→Aws.StructureAws.SageMaker.Types.AIRecommendationConstraint→Aws.StructureAws.SageMaker.Types.AIRecommendationDeploymentConfiguration→Aws.StructureAws.SageMaker.Types.AIRecommendationDeploymentS3Channel→Aws.StructureAws.SageMaker.Types.AIRecommendationInferenceSpecification→Aws.StructureAws.SageMaker.Types.AIRecommendationInstanceDetail→Aws.StructureAws.SageMaker.Types.AIRecommendationJobSummary→Aws.Structure
- Direction
- Aws.SageMaker.Types uses Aws, so a change to Aws can break Aws.SageMaker.Types, while a change to Aws.SageMaker.Types can't break Aws.
- Position
- Below the diagonal: Aws.SageMaker.Types uses a module listed above it, which is the healthy direction.
37→2 Aws.SecurityAgent.Types uses Aws.Structure✕
- Connections
- 11 pairs of types, where a type in Aws.SecurityAgent.Types uses a type in Aws.Structure.
- The types involved
Aws.SecurityAgent.Types.CaCertificateSource→Aws.Structure.UnionAws.SecurityAgent.Types.DiffSource→Aws.Structure.UnionAws.SecurityAgent.Types.ImportSource→Aws.Structure.UnionAws.SecurityAgent.Types.IntegratedResource→Aws.Structure.UnionAws.SecurityAgent.Types.IntegratedResourceMetadata→Aws.Structure.UnionAws.SecurityAgent.Types.IntegrationFilter→Aws.Structure.UnionAws.SecurityAgent.Types.MemberMetadata→Aws.Structure.UnionAws.SecurityAgent.Types.MembershipConfig→Aws.Structure.UnionAws.SecurityAgent.Types.PrivateConnectionMode→Aws.Structure.UnionAws.SecurityAgent.Types.ProviderInput→Aws.Structure.UnionAws.SecurityAgent.Types.ProviderResourceCapabilities→Aws.Structure.Union
- Direction
- Aws.SecurityAgent.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.SecurityAgent.Types, while a change to Aws.SecurityAgent.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.SecurityAgent.Types uses a module listed above it, which is the healthy direction.
37→7 Aws.SecurityAgent.Types uses Aws✕
- Connections
- 333 pairs of types, where a type in Aws.SecurityAgent.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.SecurityAgent.Types.AWSResources→Aws.StructureAws.SecurityAgent.Types.AccessDeniedException→Aws.StructureAws.SecurityAgent.Types.Actor→Aws.StructureAws.SecurityAgent.Types.ActorMessage→Aws.StructureAws.SecurityAgent.Types.AddArtifactInput→Aws.StructureAws.SecurityAgent.Types.AddArtifactOutput→Aws.StructureAws.SecurityAgent.Types.AgentSpace→Aws.StructureAws.SecurityAgent.Types.AgentSpaceSummary→Aws.StructureAws.SecurityAgent.Types.ApplicationSummary→Aws.StructureAws.SecurityAgent.Types.Artifact→Aws.StructureAws.SecurityAgent.Types.ArtifactMetadataItem→Aws.StructureAws.SecurityAgent.Types.ArtifactSummary→Aws.StructureAws.SecurityAgent.Types.Assets→Aws.StructureAws.SecurityAgent.Types.Authentication→Aws.StructureAws.SecurityAgent.Types.AzureDevOpsIntegrationInput→Aws.StructureAws.SecurityAgent.Types.AzureDevOpsRepositoryMetadata→Aws.StructureAws.SecurityAgent.Types.AzureDevOpsRepositoryResource→Aws.StructureAws.SecurityAgent.Types.AzureDevOpsResourceCapabilities→Aws.StructureAws.SecurityAgent.Types.BatchCreateSecurityRequirementResult→Aws.StructureAws.SecurityAgent.Types.BatchCreateSecurityRequirementsInput→Aws.StructureAws.SecurityAgent.Types.BatchCreateSecurityRequirementsOutput→Aws.StructureAws.SecurityAgent.Types.BatchDeleteCodeReviewsInput→Aws.StructureAws.SecurityAgent.Types.BatchDeleteCodeReviewsOutput→Aws.StructureAws.SecurityAgent.Types.BatchDeletePentestsInput→Aws.StructureAws.SecurityAgent.Types.BatchDeletePentestsOutput→Aws.Structure
- Direction
- Aws.SecurityAgent.Types uses Aws, so a change to Aws can break Aws.SecurityAgent.Types, while a change to Aws.SecurityAgent.Types can't break Aws.
- Position
- Below the diagonal: Aws.SecurityAgent.Types uses a module listed above it, which is the healthy direction.
38→2 Aws.SecurityHub.Types uses Aws.Structure✕
- Connections
- 15 pairs of types, where a type in Aws.SecurityHub.Types uses a type in Aws.Structure.
- The types involved
Aws.SecurityHub.Types.ConfigurationOptions→Aws.Structure.UnionAws.SecurityHub.Types.Criteria→Aws.Structure.UnionAws.SecurityHub.Types.CspmProviderConfiguration→Aws.Structure.UnionAws.SecurityHub.Types.CspmProviderDetail→Aws.Structure.UnionAws.SecurityHub.Types.CspmProviderUpdateConfiguration→Aws.Structure.UnionAws.SecurityHub.Types.ExportDestination→Aws.Structure.UnionAws.SecurityHub.Types.ExportOutput→Aws.Structure.UnionAws.SecurityHub.Types.ExportOutputSummary→Aws.Structure.UnionAws.SecurityHub.Types.ParameterValue→Aws.Structure.UnionAws.SecurityHub.Types.Policy→Aws.Structure.UnionAws.SecurityHub.Types.ProviderConfiguration→Aws.Structure.UnionAws.SecurityHub.Types.ProviderDetail→Aws.Structure.UnionAws.SecurityHub.Types.ProviderUpdateConfiguration→Aws.Structure.UnionAws.SecurityHub.Types.RecommendationStep→Aws.Structure.UnionAws.SecurityHub.Types.Target→Aws.Structure.Union
- Direction
- Aws.SecurityHub.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.SecurityHub.Types, while a change to Aws.SecurityHub.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.SecurityHub.Types uses a module listed above it, which is the healthy direction.
38→7 Aws.SecurityHub.Types uses Aws✕
- Connections
- 1056 pairs of types, where a type in Aws.SecurityHub.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.SecurityHub.Types.AIDetails→Aws.StructureAws.SecurityHub.Types.AcceptAdministratorInvitationRequest→Aws.StructureAws.SecurityHub.Types.AcceptAdministratorInvitationResponse→Aws.EmptyStructureAws.SecurityHub.Types.AcceptInvitationRequest→Aws.StructureAws.SecurityHub.Types.AcceptInvitationResponse→Aws.EmptyStructureAws.SecurityHub.Types.AccessDeniedException→Aws.StructureAws.SecurityHub.Types.AccountDetails→Aws.StructureAws.SecurityHub.Types.AccountFreeTrialStatus→Aws.StructureAws.SecurityHub.Types.Action→Aws.StructureAws.SecurityHub.Types.ActionLocalIpDetails→Aws.StructureAws.SecurityHub.Types.ActionLocalPortDetails→Aws.StructureAws.SecurityHub.Types.ActionRemoteIpDetails→Aws.StructureAws.SecurityHub.Types.ActionRemotePortDetails→Aws.StructureAws.SecurityHub.Types.ActionTarget→Aws.StructureAws.SecurityHub.Types.Actor→Aws.StructureAws.SecurityHub.Types.ActorSession→Aws.StructureAws.SecurityHub.Types.ActorUser→Aws.StructureAws.SecurityHub.Types.Adjustment→Aws.StructureAws.SecurityHub.Types.AdminAccount→Aws.StructureAws.SecurityHub.Types.AggregatorV2→Aws.StructureAws.SecurityHub.Types.AssociatedStandard→Aws.StructureAws.SecurityHub.Types.AssociationFilters→Aws.StructureAws.SecurityHub.Types.AssociationSetDetails→Aws.StructureAws.SecurityHub.Types.AssociationStateDetails→Aws.StructureAws.SecurityHub.Types.AutomationRulesAction→Aws.Structure
- Direction
- Aws.SecurityHub.Types uses Aws, so a change to Aws can break Aws.SecurityHub.Types, while a change to Aws.SecurityHub.Types can't break Aws.
- Position
- Below the diagonal: Aws.SecurityHub.Types uses a module listed above it, which is the healthy direction.
39→2 Aws.Transfer.Types uses Aws.Structure✕
- Connections
- 10 pairs of types, where a type in Aws.Transfer.Types uses a type in Aws.Structure.
- The types involved
Aws.Transfer.Types.ConnectorEgressConfig→Aws.Structure.UnionAws.Transfer.Types.DescribedConnectorEgressConfig→Aws.Structure.UnionAws.Transfer.Types.DescribedWebAppEndpointDetails→Aws.Structure.UnionAws.Transfer.Types.DescribedWebAppIdentityProviderDetails→Aws.Structure.UnionAws.Transfer.Types.UpdateConnectorEgressConfig→Aws.Structure.UnionAws.Transfer.Types.UpdateWebAppEndpointDetails→Aws.Structure.UnionAws.Transfer.Types.UpdateWebAppIdentityProviderDetails→Aws.Structure.UnionAws.Transfer.Types.WebAppEndpointDetails→Aws.Structure.UnionAws.Transfer.Types.WebAppIdentityProviderDetails→Aws.Structure.UnionAws.Transfer.Types.WebAppUnits→Aws.Structure.Union
- Direction
- Aws.Transfer.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.Transfer.Types, while a change to Aws.Transfer.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.Transfer.Types uses a module listed above it, which is the healthy direction.
39→7 Aws.Transfer.Types uses Aws✕
- Connections
- 215 pairs of types, where a type in Aws.Transfer.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.Transfer.Types.AccessDeniedException→Aws.StructureAws.Transfer.Types.As2AsyncMdnConnectorConfig→Aws.StructureAws.Transfer.Types.As2ConnectorConfig→Aws.StructureAws.Transfer.Types.ConflictException→Aws.StructureAws.Transfer.Types.ConnectorEgressConfig→Aws.StructureAws.Transfer.Types.ConnectorFileTransferResult→Aws.StructureAws.Transfer.Types.ConnectorVpcLatticeEgressConfig→Aws.StructureAws.Transfer.Types.CopyStepDetails→Aws.StructureAws.Transfer.Types.CreateAccessRequest→Aws.StructureAws.Transfer.Types.CreateAccessResponse→Aws.StructureAws.Transfer.Types.CreateAgreementRequest→Aws.StructureAws.Transfer.Types.CreateAgreementResponse→Aws.StructureAws.Transfer.Types.CreateConnectorRequest→Aws.StructureAws.Transfer.Types.CreateConnectorResponse→Aws.StructureAws.Transfer.Types.CreateProfileRequest→Aws.StructureAws.Transfer.Types.CreateProfileResponse→Aws.StructureAws.Transfer.Types.CreateServerRequest→Aws.StructureAws.Transfer.Types.CreateServerResponse→Aws.StructureAws.Transfer.Types.CreateUserRequest→Aws.StructureAws.Transfer.Types.CreateUserResponse→Aws.StructureAws.Transfer.Types.CreateWebAppRequest→Aws.StructureAws.Transfer.Types.CreateWebAppResponse→Aws.StructureAws.Transfer.Types.CreateWorkflowRequest→Aws.StructureAws.Transfer.Types.CreateWorkflowResponse→Aws.StructureAws.Transfer.Types.CustomDirectoriesType→Aws.Structure
- Direction
- Aws.Transfer.Types uses Aws, so a change to Aws can break Aws.Transfer.Types, while a change to Aws.Transfer.Types can't break Aws.
- Position
- Below the diagonal: Aws.Transfer.Types uses a module listed above it, which is the healthy direction.
40→2 Aws.VerifiedPermissions.Types uses Aws.Structure✕
- Connections
- 20 pairs of types, where a type in Aws.VerifiedPermissions.Types uses a type in Aws.Structure.
- The types involved
Aws.VerifiedPermissions.Types.AttributeValue→Aws.Structure.UnionAws.VerifiedPermissions.Types.CedarTagValue→Aws.Structure.UnionAws.VerifiedPermissions.Types.Configuration→Aws.Structure.UnionAws.VerifiedPermissions.Types.ConfigurationDetail→Aws.Structure.UnionAws.VerifiedPermissions.Types.ConfigurationItem→Aws.Structure.UnionAws.VerifiedPermissions.Types.ContextDefinition→Aws.Structure.UnionAws.VerifiedPermissions.Types.EncryptionSettings→Aws.Structure.UnionAws.VerifiedPermissions.Types.EncryptionState→Aws.Structure.UnionAws.VerifiedPermissions.Types.EntitiesDefinition→Aws.Structure.UnionAws.VerifiedPermissions.Types.EntityReference→Aws.Structure.UnionAws.VerifiedPermissions.Types.OpenIdConnectTokenSelection→Aws.Structure.UnionAws.VerifiedPermissions.Types.OpenIdConnectTokenSelectionDetail→Aws.Structure.UnionAws.VerifiedPermissions.Types.OpenIdConnectTokenSelectionItem→Aws.Structure.UnionAws.VerifiedPermissions.Types.PolicyDefinition→Aws.Structure.UnionAws.VerifiedPermissions.Types.PolicyDefinitionDetail→Aws.Structure.UnionAws.VerifiedPermissions.Types.PolicyDefinitionItem→Aws.Structure.UnionAws.VerifiedPermissions.Types.SchemaDefinition→Aws.Structure.UnionAws.VerifiedPermissions.Types.UpdateConfiguration→Aws.Structure.UnionAws.VerifiedPermissions.Types.UpdateOpenIdConnectTokenSelection→Aws.Structure.UnionAws.VerifiedPermissions.Types.UpdatePolicyDefinition→Aws.Structure.Union
- Direction
- Aws.VerifiedPermissions.Types uses Aws.Structure, so a change to Aws.Structure can break Aws.VerifiedPermissions.Types, while a change to Aws.VerifiedPermissions.Types can't break Aws.Structure.
- Position
- Below the diagonal: Aws.VerifiedPermissions.Types uses a module listed above it, which is the healthy direction.
40→7 Aws.VerifiedPermissions.Types uses Aws✕
- Connections
- 156 pairs of types, where a type in Aws.VerifiedPermissions.Types uses a type in Aws. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Aws.VerifiedPermissions.Types.AccessDeniedException→Aws.StructureAws.VerifiedPermissions.Types.ActionIdentifier→Aws.StructureAws.VerifiedPermissions.Types.AttributeValue→Aws.StructureAws.VerifiedPermissions.Types.BatchGetPolicyErrorItem→Aws.StructureAws.VerifiedPermissions.Types.BatchGetPolicyInput→Aws.StructureAws.VerifiedPermissions.Types.BatchGetPolicyInputItem→Aws.StructureAws.VerifiedPermissions.Types.BatchGetPolicyOutput→Aws.StructureAws.VerifiedPermissions.Types.BatchGetPolicyOutputItem→Aws.StructureAws.VerifiedPermissions.Types.BatchIsAuthorizedInput→Aws.StructureAws.VerifiedPermissions.Types.BatchIsAuthorizedInputItem→Aws.StructureAws.VerifiedPermissions.Types.BatchIsAuthorizedOutput→Aws.StructureAws.VerifiedPermissions.Types.BatchIsAuthorizedOutputItem→Aws.StructureAws.VerifiedPermissions.Types.BatchIsAuthorizedWithTokenInput→Aws.StructureAws.VerifiedPermissions.Types.BatchIsAuthorizedWithTokenInputItem→Aws.StructureAws.VerifiedPermissions.Types.BatchIsAuthorizedWithTokenOutput→Aws.StructureAws.VerifiedPermissions.Types.BatchIsAuthorizedWithTokenOutputItem→Aws.StructureAws.VerifiedPermissions.Types.CedarTagValue→Aws.StructureAws.VerifiedPermissions.Types.CognitoGroupConfiguration→Aws.StructureAws.VerifiedPermissions.Types.CognitoGroupConfigurationDetail→Aws.StructureAws.VerifiedPermissions.Types.CognitoGroupConfigurationItem→Aws.StructureAws.VerifiedPermissions.Types.CognitoUserPoolConfiguration→Aws.StructureAws.VerifiedPermissions.Types.CognitoUserPoolConfigurationDetail→Aws.StructureAws.VerifiedPermissions.Types.CognitoUserPoolConfigurationItem→Aws.StructureAws.VerifiedPermissions.Types.Configuration→Aws.StructureAws.VerifiedPermissions.Types.ConfigurationDetail→Aws.Structure
- Direction
- Aws.VerifiedPermissions.Types uses Aws, so a change to Aws can break Aws.VerifiedPermissions.Types, while a change to Aws.VerifiedPermissions.Types can't break Aws.
- Position
- Below the diagonal: Aws.VerifiedPermissions.Types uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 262 | High / Critical |
| A07:2025 — Authentication Failures | 190 | High / Critical |
Roadmap
Immediately resolve the 190 leaked secrets, prioritizing the identified high-risk files, and integrate automated security scanning into the CI pipeline to prevent regressions. Document disaster recovery procedures with tested restore steps and implement a release gate to allow manual intervention before deployments go live. Finally, enforce accessibility standards by adding invariant checks to the existing test suite to block merges that introduce violations.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a SAST step to CI running what this repository's stack ships: brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — so a security regression fails the build instead of landing. | +3.6 pts | Medium | Security & performance tooling |
| Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery). | +3.2 pts | Medium | DR & Backup |
| Resolve the 190 Leaked secret finding(s) in Secret Scanning — start with REDACTED (92), REDACTED (86), REDACTED (12). | +5.3 pts | High | Secret Scanning |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +2.6 pts | Medium | Deployment & Rollback |
| Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge. | +1.7 pts | Medium | A11y enforcement |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +1.6 pts | Medium | Page structure |
| 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. | +1.5 pts | Medium | Architecture documentation |
| Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive. | +1.4 pts | Medium | Nullable reference types |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.5 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.5 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.5 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.6 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.6 | Mixed | Secret Scanning: Leaked secret: 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
Watchdog 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. 67 of 67 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 67 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, 717 of 724 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D4 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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 79 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .rb (5,064,530 lines, 100% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rb) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (SimpleCov — `require "simplecov"` in your `REDACTED`/`test_helper.rb`, which writes `coverage/.resultset.json` (or lcov via `simplecov-lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (SimpleCov — `require "simplecov"` in your `REDACTED`/`test_helper.rb`, which writes `coverage/.resultset.json` (or lcov via `simplecov-lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rb) and this repository declares a Ruby test suite (RSpec: 437 bundle roots), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D19 Documentation Quality — not measured this run — Watchdog 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 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.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D28 Secrets (history) — not measured this run — Watchdog 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. `gitleaks` TIMED OUT after 430.9s against a 430.9s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows. Nothing about this repository is asserted by the absence of a result; the budget is ours to raise, and raising it is our backlog item, not an action for this repository's owner.
- D31 IaC & Container Security — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. Checkov ran but its report could not be read (checkov produced no output — not a clean result). Every misconfiguration only checkov reports — most of its Terraform, CloudFormation, Bicep and Ansible policies — is absent from this card, so its absence here is not evidence those resources are configured correctly.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog 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. `gems/aws-sdk-bedrockagent/lib/aws-sdk-bedrockagent/client_api.rb`, `gems/aws-sdk-bedrockagentcorecontrol/lib/aws-sdk-bedrockagentcorecontrol/client_api.rb`, `gems/aws-sdk-cloudfront/lib/aws-sdk-cloudfront/client_api.rb`, `gems/aws-sdk-datazone/lib/aws-sdk-datazone/client_api.rb`, `gems/aws-sdk-deadline/lib/aws-sdk-deadline/client_api.rb`, … (+7 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — not measured this run — Watchdog 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. File-level freshness contradicts repo activity: 99 commits in the last 90 days, yet 181 of 222 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in gems/aws-sdk-servicediscovery/lib/aws-sdk-servicediscovery/client.rb, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog 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. Subject: 8 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- DM8 Value-object opportunities — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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 frontend declares that it computes whether a construction is produced or passed, yet 2 of 2 constructions arrived without the answer. Arm two skipped them; it did not clear them.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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). 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.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- 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.
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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
13 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ClientOperationList.initialize at 23. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being SmokeTest.config_map at 16 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/features/smoke.rb (SmokeTest.config_map at 16), gems/aws-sdk-core/lib/aws-sdk-core/endpoints/function.rb (Function.call at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 13 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ClientOperationList.initialize (cyclomatic 23), ParamValidator.shape (cyclomatic 20), Decoder.peek_type (cyclomatic 19). — 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 13 together lifts Cyclomatic Complexity from 8.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
22 method(s) exceeded the cognitive complexity threshold of 15; the worst was ClientOperationList.initialize at 33.
What to do
- Bring the 22 bodies over 15 down to 15 or less in Cognitive Complexity — start with ClientOperationList.initialize (cognitive 33), ParamValidator.structure (cognitive 28), app.generateTOC (cognitive 25). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 22 together lifts Cognitive Complexity from 7.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
5 god class(es) detected.
What to do
- Resolve the 4 TooManyMethods finding(s) in God Classes — start with signer.rb, REDACTED, client_api_module.rb. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with client_api_module.rb. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
79 duplicated block group(s) detected. Measured on part of this repository only: .rb (100% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
What to do
- Resolve the 9 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with simple_attributes.rb (2), ecs_credentials.rb, REDACTED. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 5 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with async_client_class.rb, types_module.rb, auth_token_generator.rb. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with error_handler.rb, io_encrypter.rb, attribute_value.rb. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
445 production modules (RubyGems), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations, and main-sequence distance (abstractness) is not computed for these modules yet.
D6 · Cohesion (LCOM4)
48 of 325 classes have LCOM4 above 3.
What to do
- Resolve the 48 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (48 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D12 · Dependency Hygiene
0 outdated direct gem(s), 0 pinning defect(s). 1367 declaration(s) graded against rubygems.org, 8 of them against a version resolved in a committed Gemfile.lock. 6 declaration(s) carry a requirement that EXCLUDES the current release; that is a deliberate constraint (a supported-version ceiling or a held-back CI pin) and is counted, not charged. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.
D13 · Secret Scanning
80 secret(s) detected.
What to do
- Resolve the 190 Leaked secret finding(s) in Secret Scanning — start with REDACTED (92), REDACTED (86), REDACTED (12). — One of this dimension's main actionable groups (190 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 466 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 466 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed Gemfile.lock. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 1 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
7 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is gems/aws-partitions/lib/aws-partitions.rb. Counted over 196 of the 6519 production source files in this repository: 6297 are under the ~2,400-byte size floor this dimension measures over, and the remaining 26 have no attributable history left to measure.
D17 · Explicit Debt
34 deducted task-comment markers across 5064543 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 28 TodoComment finding(s) in Explicit Debt — start with retry_errors.rb (7), retry_quota.rb (3), client_operation_documentation.rb (3). — One of this dimension's main actionable groups (28 warning-level).
- Resolve the 4 HackComment finding(s) in Explicit Debt — start with ecs_credentials_spec.rb, matchers.rb, plugin_list.rb. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with types_module.rb, keyword_argument_builder.rb. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D26 · Project Cohesion
237 of 446 build units (Bundler, RubyGems) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
262 finding(s): 0 critical, 11 high, 251 medium, 0 low. semgrep hit a parse error in 17 file(s) — `apis/accessanalyzer/2019-11-01/waiters-2.json`, `apis/codebuild/2016-10-06/docs-2.json`, `doc-src/templates/default/fulldoc/html/js/jquery.js`, `gems/aws-sdk-bedrockagentcorecontrol/lib/aws-sdk-bedrockagentcorecontrol/client_api.rb`, `gems/aws-sdk-cloudfront/lib/aws-sdk-cloudfront/client_api.rb`, … (+12 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 208 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (10), REDACTED (7), REDACTED (6). — One of this dimension's main actionable groups (208 warning-level).
- Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
trivy found no infrastructure-as-code or container misconfigurations.
D35 · Change Coupling
Strongest change-coupling: assume_role_credentials.rb↔REDACTED 64%; client_api_module.rb↔types_module.rb 60%; services.rb↔user_agent.rb 53%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with services.rb. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with assume_role_credentials.rb, client_api_module.rb, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 1367 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — doc-src/templates/default/fulldoc/html/full_list.erb:3, doc-src/templates/default/layout/html/layout.erb:2
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — doc-src/templates/default/layout/html/layout.erb:2
- An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — doc-src/templates/default/layout/html/layout.erb:13
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 8 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `ial_for_element` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/helper.rb:9
- `xmldecl` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — gems/aws-sdk-core/lib/aws-sdk-core/xml/parser/nokogiri_engine.rb:18
- `comment` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — gems/aws-sdk-core/lib/aws-sdk-core/xml/parser/nokogiri_engine.rb:21
- `start_document` has an empty body — confirm it's an intentional no-op and not an unfinished method. — gems/aws-sdk-core/lib/aws-sdk-core/xml/parser/nokogiri_engine.rb:19
- `end_document` has an empty body — confirm it's an intentional no-op and not an unfinished method. — gems/aws-sdk-core/lib/aws-sdk-core/xml/parser/nokogiri_engine.rb:20
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×2) — gems/aws-sdk-core/spec/aws/xml/parser_spec.rb:15, gems/aws-sdk-s3/spec/protocols_spec.rb:276
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- Clear the softer debt: re-enable or delete `xit`/`skip`ped tests, decide whether each empty method or NotImplementedError refusal is deliberate (and say so in a comment), and replace `# rubocop:disable all` with targeted, justified disables.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P11 · BDD / executable specs
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack as a CI step. What was searched, so you can tell an absence from a miss: the 13351 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `bundler`, `gitsubmodule` — add those `package-ecosystem` entries to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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
S1 · Web-Security Posture
- MD5/SHA1 is computed 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+ (`Digest::SHA256` or `OpenSSL::Digest.new("SHA256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×12) — REDACTED:87, REDACTED:30, REDACTED:32, …
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 (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 12 sites, not one: `REDACTED:87` (::Digest::SHA1.new), `REDACTED:30` (OpenSSL::Digest::MD5.file), `REDACTED:32` (OpenSSL::Digest::MD5.new), `REDACTED:36` (OpenSSL::Digest::MD5.digest), `REDACTED:168` (OpenSSL::Digest::SHA1.hexdigest), `REDACTED:115` (OpenSSL::Digest::SHA1.hexdigest), `REDACTED:59` (OpenSSL::Digest::MD5.digest), `REDACTED:594` (OpenSSL::Digest::MD5.digest), and 4 further site(s). Each is a separate decision — fixing only the line this row cites leaves the others in place.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `format` is public and takes `obj` — which it walks as a `Hash` — from its caller, and it calls itself at line 33 (`self.format`) with a piece of `obj` (and at line 37, line 48) — and nowhere in `format` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `format` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — gems/aws-sdk-dynamodb/lib/aws-sdk-dynamodb/attribute_value.rb:33
- `deep_merge` is public and takes `left` — which it walks as a `Hash` — from its caller, and it calls itself at line 13 (`self.deep_merge`) with a piece of `left` — and nowhere in `deep_merge` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `deep_merge` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — gems/aws-sdk-core/lib/aws-sdk-core/util.rb:13
- `deep_copy` is public and takes `obj` — which it walks as a `Hash` — from its caller, and it calls itself at line 34 (`self.deep_copy`) with a piece of `obj` (and at line 38) — and nowhere in `deep_copy` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `deep_copy` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — gems/aws-sdk-core/lib/aws-sdk-core/util.rb:34
- `add` is public and takes `value` — which it walks as a `Hash` — from its caller, and it calls itself at line 29 (`self.add`) with a piece of `value` (and at line 38, line 42, line 43) — and nowhere in `add` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `add` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — gems/aws-sdk-core/lib/aws-sdk-core/cbor/encoder.rb:29
- `deep_copy` is public and takes `obj` — which it walks as a `Hash` — from its caller, and it calls itself at line 164 (`self.deep_copy`) with a piece of `obj` (and at line 165) — and nowhere in `deep_copy` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `deep_copy` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/helper.rb:164
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
- `UDPSocket.new` is called here without a block, so it hands back an open descriptor the caller must close — and it is held in `socket`, and every later use of `socket` in `send_datagram` reads a member through it — it is never closed, returned, passed, yielded or stored. Nothing closes it: it stays open until the garbage collector happens to finalize it, which is one leaked descriptor per call (a child process too, for `IO.popen`), `Errno::EMFILE` under load, and for a written file data that is not flushed when the program next reads it. Use the block form, which closes on every path including a raise (`UDPSocket.new(…) { |io| … }`), or the one-call reader/writer (`File.read`, `File.write`, `File.foreach`). — gems/aws-sdk-core/lib/aws-sdk-core/client_side_monitoring/publisher.rb:40
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — gems/aws-sdk-core/lib/aws-sdk-core/rest/response/headers.rb:58
- `rescue StandardError` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — gems/aws-sdk-core/lib/aws-sdk-core/plugins/retries/clock_skew.rb:115
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — REDACTED:4, REDACTED:5
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 5639 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
What to do
- Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 90% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 65% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 56% | Adequate — gated by D13, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 80% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Accessibility | 63% | Adequate | Acceptable, with room to improve. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X6 Hand-rolled structured-format parsing — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 63 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Ruby code is a Rails controller, a Sinatra, Grape or Roda app, a Hanami action or a Rack app (an instance `call(env)`), so no request handler shares state between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, a db/schema.rb table or a Mongoid document — and no database or data-store client (an ActiveRecord model, Sequel, pg, mysql2, sqlite3, Mongo, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository draws no route and defines no request handler (no Rails routes.draw or controller, no Sinatra, Roda or Grape application, no Hanami action). Access control is therefore N/A here — a gem is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential in an ActiveRecord or Sequel migration, db/schema.rb or a Mongoid document — and no database client (an ActiveRecord model, Sequel, pg, mysql2, Mongo) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, db/schema.rb or a Mongoid document — and no database client (ActiveRecord, Sequel, pg, mysql2, mongo, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, a db/schema.rb table or a Mongoid document — and no database or data-store client (an ActiveRecord model, Sequel, pg, mysql2, sqlite3, Mongo, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~235249 lines of test source are present (.rb) 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 included — the .rb suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — D19 withholds "Documentation: no overview": 1 candidate(s) were measured and not published.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# only; Java, JavaScript, Ruby not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Ruby surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. 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# and Visual Basic comments only — this repository's production source is .java, .rb, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rb), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D28 Secrets (history) — gitleaks killed before it finished — this repository's git history not scanned
- D32 Data Compliance (PII/GDPR) — 12 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.rb) 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 its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Ruby source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (SimpleCov — `require "simplecov"` in your `REDACTED`/`test_helper.rb`, which writes `coverage/.resultset.json` (or lcov via `simplecov-lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `x.report(…)` entries in a `Benchmark.ips`/`bm`/`bmbm`/`benchmark`/`memory` block, `benchmark:` entries in a benchmark-driver YAML under a bench* directory, rspec-benchmark `perform_*` expectations where the gem is installed, or benchmark-ips, benchmark-memory, rspec-benchmark or benchmark-driver in a Gemfile or gemspec, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: Ruby runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
- PF3 Async & latency hygiene — Not applicable: Ruby has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- X2 Cancellation propagation — no C# was loaded; this repository's Ruby was read, and no request in it can be cancelled by a caller — a Ruby request takes no token: Net::HTTP, Faraday and async-http are stopped from outside the call (Async::Task#stop, Thread#raise, Timeout), not through a parameter
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-logger would be judged.
- 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 — 204 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Document without a <title> doc-src/templates/default/layout/html/layout.erb:2
- <iframe> without a title doc-src/templates/default/layout/html/layout.erb:13
- REDACTED
- Boundary-crossing change coupling: services.rb ↔ user_agent.rb build_tools/services.rb:1
Serious — 481 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
- Low cohesion: ResourceClientRequest (LCOM4 10) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/rbs/resource_client_request.rb:5
- Low cohesion: SyntaxExample (LCOM4 10) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/syntax_example.rb:6
- Low cohesion: KeywordArgumentBuilder (LCOM4 9) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/rbs/keyword_argument_builder.rb:6
- Low cohesion: SyntaxExampleHash (LCOM4 9) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/syntax_example_hash.rb:6
- Low cohesion: NotificationConfiguration (LCOM4 6) REDACTED:12
- Low cohesion: CookieSigner (LCOM4 6) REDACTED:29
- Low cohesion: CredentialProviderChain (LCOM4 6) REDACTED:5
- Low cohesion: Archive (LCOM4 6) REDACTED:12
- Low cohesion: MultipartUpload (LCOM4 6) REDACTED:12
- Low cohesion: AccessKeyPair (LCOM4 6) REDACTED:12
- Low cohesion: MultipartUpload (LCOM4 6) REDACTED:12
- Low cohesion: ObjectVersion (LCOM4 6) REDACTED:12
- Low cohesion: LoadBalancer (LCOM4 5) REDACTED:12
- Low cohesion: Tag (LCOM4 5) REDACTED:12
- Low cohesion: UrlSigner (LCOM4 5) gems/aws-sdk-cloudfront/lib/aws-sdk-cloudfront/url_signer.rb:29
- Low cohesion: InstanceProfileCredentials (LCOM4 5) gems/aws-sdk-core/lib/aws-sdk-core/instance_profile_credentials.rb:24
- Low cohesion: Base (LCOM4 5) gems/aws-sdk-core/lib/seahorse/client/base.rb:5
- Low cohesion: Tag (LCOM4 5) REDACTED:12
- Low cohesion: AccessKey (LCOM4 5) REDACTED:12
- Low cohesion: MfaDevice (LCOM4 5) REDACTED:12
- Low cohesion: SigningCertificate (LCOM4 5) REDACTED:12
- Low cohesion: DBLogFile (LCOM4 5) REDACTED:12
- Low cohesion: DBSnapshotAttribute (LCOM4 5) REDACTED:12
- Low cohesion: PendingMaintenanceAction (LCOM4 5) REDACTED:12
- Low cohesion: ObjectSummary (LCOM4 5) REDACTED:12
- TodoComment gems/aws-sdk-s3/spec/client_spec.rb:766
- TodoComment gems/aws-sdk-core/spec/aws/client_spec.rb:49
- TodoComment gems/aws-sdk-s3/lib/aws-sdk-s3/plugins/accelerate.rb:35
- TodoComment gems/aws-sdk-s3/lib/aws-sdk-s3/customizations/types/list_object_versions_output.rb:5
- TodoComment gems/aws-sdk-dynamodbstreams/lib/aws-sdk-dynamodbstreams/attribute_translator.rb:27
- TodoComment gems/aws-sdk-core/spec/aws/plugins/retry_errors_legacy_spec.rb:27
- TodoComment gems/aws-sdk-core/lib/aws-sdk-core/plugins/retries/retry_quota.rb:12
- TodoComment gems/aws-sdk-core/lib/aws-sdk-core/plugins/retries/retry_quota.rb:15
- TodoComment gems/aws-sdk-core/spec/aws/plugins/retry_errors_spec.rb:420
- TodoComment gems/aws-sdk-core/spec/aws/plugins/retry_errors_spec.rb:688
- TodoComment gems/aws-sdk-core/spec/aws/plugins/retries/retry_quota_spec.rb:51
- TodoComment gems/aws-sdk-core/lib/aws-sdk-core/rest/response/parser.rb:9
- TodoComment gems/aws-sdk-core/lib/aws-sdk-core/plugins/retry_errors.rb:99
- TodoComment gems/aws-sdk-core/lib/aws-sdk-core/plugins/retry_errors.rb:180
- TodoComment gems/aws-sdk-core/lib/aws-sdk-core/plugins/retry_errors.rb:200
- TodoComment gems/aws-sdk-core/lib/aws-sdk-core/plugins/retry_errors.rb:228
- TodoComment gems/aws-sdk-core/lib/aws-sdk-core/plugins/retry_errors.rb:330
- TodoComment gems/aws-sdk-core/lib/aws-sdk-core/plugins/retry_errors.rb:285
- TodoComment gems/aws-sdk-core/lib/aws-sdk-core/plugins/retry_errors.rb:419
- TodoComment gems/aws-sdk-core/lib/aws-sdk-core/plugins/retries/retry_quota.rb:29
- TodoComment build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/client_operation_documentation.rb:238
- TodoComment build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/client_operation_documentation.rb:251
- TodoComment build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/client_operation_documentation.rb:262
- TodoComment REDACTED:116
- TodoComment build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/eventstream_example.rb:188
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Weak hash algorithm REDACTED:87
- Weak hash algorithm REDACTED:30
- Weak hash algorithm REDACTED:32
- Weak hash algorithm REDACTED:36
- Weak hash algorithm REDACTED:168
- Weak hash algorithm REDACTED:115
- Weak hash algorithm REDACTED:59
- Weak hash algorithm REDACTED:594
- Weak hash algorithm REDACTED:121
- Weak hash algorithm REDACTED:107
- Weak hash algorithm REDACTED:134
- Weak hash algorithm REDACTED:157
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (5 lines × 2) gems/aws-sdk-core/lib/aws-sdk-core/ecs_credentials.rb:185
- Duplicated block (5 lines × 2) REDACTED:168
- Duplicated block (5 lines × 2) gems/aws-sdk-dynamodb/lib/aws-sdk-dynamodb/plugins/simple_attributes.rb:220
- Duplicated block (5 lines × 2) gems/aws-sdk-dynamodb/lib/aws-sdk-dynamodb/plugins/simple_attributes.rb:228
- Duplicated block (5 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/directory_downloader.rb:20
- Duplicated block (5 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/decrypt_handler.rb:102
- Duplicated block (5 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryptionV2/io_encrypter.rb:49
- Duplicated block (5 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryptionV2/utils.rb:14
- Duplicated block (5 lines × 2) gems/aws-sigv2/lib/aws-sigv2/signer.rb:161
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (16 lines × 2) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/async_client_class.rb:20
- Duplicated block (16 lines × 2) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/rbs/types_module.rb:135
- Duplicated block (16 lines × 2) gems/aws-sdk-dsql/lib/aws-sdk-dsql/customizations/auth_token_generator.rb:51
- Duplicated block (16 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/decrypt_handler.rb:145
- Duplicated block (16 lines × 2) tasks/gems/aws-sdk-cloudwatchlogs.rb:21
- Duplicated block (10 lines × 2) gems/aws-sdk-core/lib/aws-sdk-core/json/error_handler.rb:77
- Duplicated block (10 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryptionV2/io_encrypter.rb:60
- Duplicated block (10 lines × 2) gems/aws-sdk-dynamodb/lib/aws-sdk-dynamodb/attribute_value.rb:102
- Duplicated block (10 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/decrypt_handler.rb:89
- Duplicated block (10 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/directory_downloader.rb:69
- Duplicated block (9 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/multipart_file_uploader.rb:76
- Duplicated block (9 lines × 2) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/rbs/types_module.rb:160
- Duplicated block (9 lines × 2) gems/aws-sdk-core/lib/aws-sdk-core/stubbing/protocols/json.rb:19
- Duplicated block (9 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryptionV2/encrypt_handler.rb:12
- Duplicated block (9 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/access_grants_credentials.rb:13
- Duplicated block (8 lines × 2) gems/aws-sdk-core/lib/aws-sdk-core/json/builder.rb:26
- Duplicated block (8 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/decrypt_handler.rb:120
- Duplicated block (8 lines × 2) tasks/gems/aws-sdk-dynamodb.rb:21
- Duplicated block (8 lines × 2) REDACTED:367
- Duplicated block (8 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryptionV2/kms_cipher_provider.rb:121
- Recursive walk over a caller-supplied document has no depth cap gems/aws-sdk-dynamodb/lib/aws-sdk-dynamodb/attribute_value.rb:33
- Recursive walk over a caller-supplied document has no depth cap gems/aws-sdk-core/lib/aws-sdk-core/util.rb:13
- Recursive walk over a caller-supplied document has no depth cap gems/aws-sdk-core/lib/aws-sdk-core/util.rb:34
- Recursive walk over a caller-supplied document has no depth cap gems/aws-sdk-core/lib/aws-sdk-core/cbor/encoder.rb:29
- Recursive walk over a caller-supplied document has no depth cap build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/helper.rb:164
- HackComment gems/aws-sdk-core/spec/aws/ecs_credentials_spec.rb:395
- HackComment gems/aws-sdk-core/lib/aws-sdk-core/endpoints/matchers.rb:105
- HackComment build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/plugin_list.rb:136
- HackComment build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/endpoints_plugin.rb:11
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TooManyMethods: Signer gems/aws-sigv4/lib/aws-sigv4/signer.rb:77
- TooManyMethods: SharedConfig REDACTED:5
- TooManyMethods: ClientApiModule build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/client_api_module.rb:5
- TooManyMethods: Formatter gems/aws-sdk-core/lib/seahorse/client/logging/formatter.rb:75
- Duplicated block (12 lines × 2) gems/aws-sdk-dynamodb/lib/aws-sdk-dynamodb/plugins/simple_attributes.rb:205
- Duplicated block (12 lines × 2) gems/aws-sdk-bedrock/lib/aws-sdk-bedrock/plugins/bearer_authorization.rb:8
- Duplicated block (12 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/utils.rb:28
- Duplicated block (12 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/plugins/arn.rb:38
- Duplicated block (7 lines × 2) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/eventstream_example.rb:206
- Duplicated block (7 lines × 2) gems/aws-sdk-core/lib/aws-sdk-core/ec2_metadata.rb:185
- Duplicated block (7 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/utils.rb:84
- Duplicated block (7 lines × 2) gems/aws-sdk-core/lib/aws-sdk-core/binary/event_stream_decoder.rb:46
- REDACTED
- REDACTED
- REDACTED
- Change coupling: assume_role_credentials.rb ↔ REDACTED gems/aws-sdk-core/lib/aws-sdk-core/assume_role_credentials.rb:1
- Change coupling: client_api_module.rb ↔ types_module.rb build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/client_api_module.rb:1
- Change coupling: REDACTED ↔ REDACTED REDACTED:1
- Duplicated block (6 lines × 2) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/rbs/keyword_argument_builder.rb:132
- Duplicated block (6 lines × 2) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/rbs/keyword_argument_builder.rb:141
- Duplicated block (6 lines × 2) gems/aws-sdk-dynamodb/lib/aws-sdk-dynamodb/plugins/simple_attributes.rb:244
- Empty method body — does nothing with its inputs build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/helper.rb:9
- Empty method body — does nothing with its inputs gems/aws-sdk-core/lib/aws-sdk-core/xml/parser/nokogiri_engine.rb:18
- Empty method body — does nothing with its inputs gems/aws-sdk-core/lib/aws-sdk-core/xml/parser/nokogiri_engine.rb:21
- Page without a main landmark doc-src/templates/default/fulldoc/html/full_list.erb:3
- Page without a main landmark doc-src/templates/default/layout/html/layout.erb:2
- FixmeComment build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/rbs/types_module.rb:197
- FixmeComment build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/rbs/keyword_argument_builder.rb:49
- REDACTED
- REDACTED
- Duplicated block (33 lines × 2) gems/aws-sdk-core/lib/aws-sdk-core/json/parser.rb:28
- Duplicated block (33 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/io_auth_decrypter.rb:20
- Duplicated block (20 lines × 2) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/resource_batch_action_code.rb:29
- Duplicated block (20 lines × 2) REDACTED:115
- Duplicated block (18 lines × 2) gems/aws-sdk-dynamodb/lib/aws-sdk-dynamodb/attribute_value.rb:79
- Duplicated block (18 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryptionV2/default_cipher_provider.rb:121
- Duplicated block (15 lines × 2) gems/aws-partitions/lib/aws-partitions.rb:669
- Duplicated block (15 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/decrypt_handler.rb:71
- Duplicated block (13 lines × 2) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/rbs/input_type_alias_collector.rb:86
- Duplicated block (13 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/plugins/dualstack.rb:9
- Duplicated block (6 lines × 3) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/utils.rb:47
- Duplicated block (6 lines × 3) REDACTED:18
- Duplicated block (11 lines × 2) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/rbs/types_module.rb:67
- Duplicated block (11 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/decrypt_handler.rb:197
- Duplicated block (7 lines × 3) REDACTED:357
- Duplicated block (7 lines × 3) gems/aws-sdk-core/lib/aws-sdk-core/endpoints/endpoint_rule.rb:25
- Swallowed exception (caught, then discarded) gems/aws-sdk-core/lib/aws-sdk-core/rest/response/headers.rb:58
- Swallowed exception (caught, then discarded) gems/aws-sdk-core/lib/aws-sdk-core/plugins/retries/clock_skew.rb:115
- Swallowed exception (empty catch) REDACTED:4
- Swallowed exception (empty catch) REDACTED:5
- Accessibility enforcement below the top rung
- ClientOperationList.initialize (cyclomatic 23) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/client_operation_list.rb:8
- ParamValidator.shape (cyclomatic 20) gems/aws-sdk-core/lib/aws-sdk-core/param_validator.rb:153
- Decoder.peek_type (cyclomatic 19) gems/aws-sdk-core/lib/aws-sdk-core/cbor/decoder.rb:88
- Api.ruby_input_type (cyclomatic 18) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/api.rb:50
- RBS.to_type (cyclomatic 18) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/rbs.rb:6
- Api.ruby_type (cyclomatic 17) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/api.rb:92
- EndpointParameter.built_in_param_value (cyclomatic 17) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/endpoint_parameter.rb:112
- KeywordArgumentBuilder.ref_value (cyclomatic 17) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/rbs/keyword_argument_builder.rb:75
- ClientApiModule.operations (cyclomatic 17) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/client_api_module.rb:207
- Decoder.decode_item (cyclomatic 17) gems/aws-sdk-core/lib/aws-sdk-core/cbor/decoder.rb:33
- ParamValidator.structure (cyclomatic 17) gems/aws-sdk-core/lib/aws-sdk-core/param_validator.rb:40
- app.generateTOC (cyclomatic 17) REDACTED:168
- ClientOperationList.initialize (cognitive 33) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/client_operation_list.rb:8
- ParamValidator.structure (cognitive 28) gems/aws-sdk-core/lib/aws-sdk-core/param_validator.rb:40
- app.generateTOC (cognitive 25) REDACTED:168
- ParamValidator.shape (cognitive 22) gems/aws-sdk-core/lib/aws-sdk-core/param_validator.rb:153
- Handler._discover_endpoint (cognitive 22) gems/aws-sdk-core/lib/aws-sdk-core/plugins/endpoint_discovery.rb:106
- SharedConfig.assume_role_from_profile (cognitive 22) REDACTED:263
- ConnectionPool.start_session (cognitive 22) REDACTED:276
- ClientApiModule.operation_ref (cognitive 20) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/client_api_module.rb:522
- ClientApiModule.operations (cognitive 19) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/client_api_module.rb:207
- Connection.start (cognitive 19) REDACTED:98
- DefaultCipherProvider.decryption_cipher (cognitive 18) gems/aws-sdk-s3/lib/aws-sdk-s3/encryptionV2/default_cipher_provider.rb:59
- ClientOperationDocumentation.option_tags (cognitive 17) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/client_operation_documentation.rb:91
- ClientApiModule.shape_definitions (cognitive 17) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/client_api_module.rb:136
- RefreshingCredentials.refresh_if_near_expiration! (cognitive 17) REDACTED:59
- IniParser.ini_parse (cognitive 16) gems/aws-sdk-core/lib/aws-sdk-core/ini_parser.rb:8
- SharedConfig.resolve_source_profile (cognitive 16) REDACTED:336
- SharedConfig.sso_credentials_from_profile (cognitive 16) REDACTED:424
- DefaultCipherProvider.decryption_cipher (cognitive 16) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/default_cipher_provider.rb:31
- Presigner.sign_but_dont_send (cognitive 16) REDACTED:192
- Signer.sign_request (cognitive 16) gems/aws-sigv4/lib/aws-sigv4/signer.rb:223
- partialSearch (cognitive 16) REDACTED:147
- REDACTED
- REDACTED
- FileTooLong: views/client_api_module.rb build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/client_api_module.rb
- Duplicated block (35 lines × 2) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/rbs/types_module.rb:28
- Duplicated block (29–32 lines × 2) gems/aws-sdk-s3control/lib/aws-sdk-s3control/arn/outpost_access_point_arn.rb:32
- Duplicated block (20–28 lines × 2) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/client_operation_list.rb:33
- Duplicated block (25–27 lines × 2) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/rbs/keyword_argument_builder.rb:86
- Duplicated block (25 lines × 2) gems/aws-sdk-core/lib/aws-sdk-core/json/handler.rb:45
- Duplicated block (24 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/default_cipher_provider.rb:35
- Duplicated block (21–22 lines × 2) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/rbs/async_client_class.rb:169
- Duplicated block (13–20 lines × 3) tasks/gems/aws-sdk-cloudwatchlogs.rb:55
- Duplicated block (17 lines × 3) REDACTED:41
- Duplicated block (15–17 lines × 2) REDACTED:455
- Duplicated block (14–15 lines × 2) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/rbs/async_client_class.rb:79
- Duplicated block (14 lines × 2) gems/aws-sdk-s3/lib/aws-sdk-s3/encryptionV2/decrypt_handler.rb:37
- Duplicated block (9–11 lines × 2) gems/aws-partitions/lib/aws-partitions/endpoint_provider.rb:96
- Duplicated block (9 lines × 3) REDACTED:30
- Duplicated block (21 lines × 2) gems/aws-sdk-core/lib/aws-sdk-core/plugins/logging.rb:34
- Duplicated block (20 lines × 3) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/io_decrypter.rb:12
- Duplicated block (37 lines × 3) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/materials.rb:18
- Duplicated block (38 lines × 2) gems/aws-sigv2/lib/aws-sigv2/credentials.rb:11
- Duplicated block (6 lines × 4) build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/resource_data_method.rb:23
- Duplicated block (7 lines × 4) gems/aws-sdk-core/lib/aws-sdk-core/query/ec2_param_builder.rb:72
- Duplicated block (13 lines × 3) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/decrypt_handler.rb:47
- Duplicated block (5 lines × 6) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/decrypt_handler.rb:211
- Duplicated block (5 lines × 3) gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/utils.rb:58
- Disposable created and abandoned in the function that made it gems/aws-sdk-core/lib/aws-sdk-core/client_side_monitoring/publisher.rb:40
Minor — 39 finding(s)
- Duplicated predicate gems/aws-sdk-core/lib/aws-sdk-core/credentials.rb:45
- Duplicated predicate gems/aws-sdk-core/lib/aws-sdk-core/plugins/sign.rb:214
- Duplicated predicate gems/aws-sdk-core/lib/aws-sdk-core/binary/event_builder.rb:57
- Duplicated predicate REDACTED:91
- Duplicated predicate gems/aws-sdk-s3/lib/aws-sdk-s3/encryptionV2/io_encrypter.rb:28
- Duplicated predicate gems/aws-sdk-s3control/lib/aws-sdk-s3control/arn/outpost_access_point_arn.rb:41
- Duplicated predicate gems/aws-sdk-core/lib/aws-sdk-core/rest/request/body.rb:75
- Duplicated predicate build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/client_api_module.rb:334
- Duplicated predicate gems/aws-sdk-core/lib/seahorse/client/plugins/h2.rb:36
- Duplicated predicate gems/aws-sdk-s3/lib/aws-sdk-s3/plugins/arn.rb:38
- Duplicated predicate REDACTED:130
- Duplicated predicate gems/aws-sdk-s3/lib/aws-sdk-s3/directory_downloader.rb:169
- Duplicated predicate gems/aws-sdk-core/lib/aws-sdk-core/plugins/client_metrics_plugin.rb:62
- Duplicated predicate gems/aws-sdk-core/lib/aws-sdk-core/plugins/retries/error_inspector.rb:139
- Duplicated predicate gems/aws-sdk-core/lib/aws-sdk-core/json/error_handler.rb:49
- Duplicated predicate gems/aws-sdk-core/lib/aws-sdk-core/plugins/sign.rb:193
- Duplicated predicate gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/decrypt_handler.rb:50
- Duplicated predicate gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/decrypt_handler.rb:105
- Duplicated predicate gems/aws-sdk-s3/lib/aws-sdk-s3/encryption/decrypt_handler.rb:103
- Duplicated predicate REDACTED:150
- Duplicated predicate gems/aws-sdk-s3/lib/aws-sdk-s3/encryptionV2/kms_cipher_provider.rb:156
- Duplicated predicate build_tools/aws-sdk-code-generator/lib/aws-sdk-code-generator/views/rbs/types_module.rb:127
- Duplicated predicate REDACTED:325
- Duplicated predicate gems/aws-sigv2/lib/aws-sigv2/signer.rb:183
- Duplicated predicate gems/aws-sigv2/lib/aws-sigv2/credentials.rb:11
- Hand-rolled JSON/XML parsing via regex gems/aws-sdk-core/lib/aws-sdk-core/xml/error_handler.rb:54
- Hand-rolled JSON/XML parsing via regex gems/aws-sdk-core/lib/aws-sdk-core/xml/error_handler.rb:67
- Hand-rolled JSON/XML parsing via regex gems/aws-sdk-core/lib/aws-sdk-core/xml/error_handler.rb:83
- Hand-rolled JSON/XML parsing via regex gems/aws-sdk-core/lib/aws-sdk-core/xml/error_handler.rb:91
- Empty method body gems/aws-sdk-core/lib/aws-sdk-core/xml/parser/nokogiri_engine.rb:19
- Empty method body gems/aws-sdk-core/lib/aws-sdk-core/xml/parser/nokogiri_engine.rb:20
- Disabled test gems/aws-sdk-core/spec/aws/xml/parser_spec.rb:15
- Disabled test gems/aws-sdk-s3/spec/protocols_spec.rb:276
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- No ADRs
- No SAST
- Ruby's type checker does not check nil everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a55829919cfa4828a64cec958a949dbf/history.json --exit-code 0 --source . | 0 | — |
| 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/watchdog-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 . | 262 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 12 file(s) — `gems/aws-sdk-bedrockagent/lib/aws-sdk-bedrockagent/client_api.rb`, `gems/aws-sdk-bedrockagentcorecontrol/lib/aws-sdk-bedrockagentcorecontrol/client_api.rb`, `gems/aws-sdk-cloudfront/lib/aws-sdk-cloudfront/client_api.rb`, `gems/aws-sdk-datazone/lib/aws-sdk-datazone/client_api.rb`, `gems/aws-sdk-deadline/lib/aws-sdk-deadline/client_api.rb`, … (+7 more) — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |