Executive summary
guardian/riff-raff falls short of our standard for production, in part because it has images with no text description. It scores 45 out of 100 and is rated Weak, and 21 of its 28 critical findings are security problems.
Accessibility, at 33, is the weakest lens and counts most in the score. The best first step for the work it takes is replacing the three exposed passwords or keys and switching the old ones off, worth about 4 points. Adding text alternatives would lift Accessibility itself, worth about 6 points. Raising Accessibility to 70 would lift the score to about 55.
Six passwords or keys in the code's history and three in the code are open to anyone who can read the repository. Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two secrets can leak from the build pipeline. Replacing each exposed password or key, pinning each tool to an exact version and limiting each secret to its own step would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the two unsafe settings in infrastructure or container files need changing to safe values. The two form fields without a label need a label.
The product code is 17,956 lines, about €23,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Accessibility rose from 33 to 70, the lowest score rated Strong, the score would rise from 45 to about 55.
New since the last survey: 1 finding
- Cognitive Complexity · d3.v2.d3.format.<returned closure> (cognitive 16) REDACTED
Fixed since the last survey: 5 findings
- Cyclomatic Complexity · d3.v2.d3.format (cyclomatic 24) REDACTED
- Cyclomatic Complexity · d3.v2.d3_svg_area (cyclomatic 21) REDACTED
- Cyclomatic Complexity · d3.v2.d3.svg.axis (cyclomatic 21) REDACTED
- Cyclomatic Complexity · d3.v2.d3.interpolateTransform (cyclomatic 16) REDACTED
- Cognitive Complexity · d3.v2.d3.format (cognitive 26) REDACTED
Rebuild cost: about €23,000 · Estimate
| Cost to rebuild | €7,800 to €39,000, for 129 to 410 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 45. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 17,956 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 magenta.artifact | 2 magenta.graph.Graph | 3 magenta.input | 4 magenta.tasks.ASG | 5 magenta.tasks.S3 | 6 magenta.ContextMessage | 7 magenta.Message | 8 magenta.deployment_type | 9 magenta.tasks.autoscaling | 10 schedule | 11 AppComponents | 12 controllers.ScheduleController | 13 magenta.tasks | 14 magenta.graph | 15 magenta | 16 controllers.forms | 17 deployment.actors.DeployGroupRunner | 18 deployment.actors.TasksRunner | 19 deployment.preview | 20 docs | 21 lifecycle | 22 magenta.RunState | 23 magenta.Strategy | 24 magenta.input.resolver | 25 magenta.tasks.stackSetPolicy | 26 views.html.helper.magenta | 27 deployment | 28 utils | 29 deployment.actors.DeployCoordinator | 30 housekeeping | 31 restrictions | 32 persistence | 33 notification | 34 controllers | 35 ci | 36 conf | 37 controllers.Api | 38 deployment.actors | 39 resources | 40 (global) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 magenta.artifact | ||||||||||||||||||||||||||||||||||||||||
| 2 magenta.graph.Graph | ||||||||||||||||||||||||||||||||||||||||
| 3 magenta.input | ||||||||||||||||||||||||||||||||||||||||
| 4 magenta.tasks.ASG | ||||||||||||||||||||||||||||||||||||||||
| 5 magenta.tasks.S3 | ||||||||||||||||||||||||||||||||||||||||
| 6 magenta.ContextMessage | 6 | |||||||||||||||||||||||||||||||||||||||
| 7 magenta.Message | 13 | |||||||||||||||||||||||||||||||||||||||
| 8 magenta.deployment_type | 2 | 3 | 33 | |||||||||||||||||||||||||||||||||||||
| 9 magenta.tasks.autoscaling | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 schedule | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 AppComponents | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 controllers.ScheduleController | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 magenta.tasks | 7 | 3 | 1 | 15 | 1 | 122 | ||||||||||||||||||||||||||||||||||
| 14 magenta.graph | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 magenta | 1 | 1 | 6 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 16 controllers.forms | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 deployment.actors.DeployGroupRunner | 4 | 6 | ||||||||||||||||||||||||||||||||||||||
| 18 deployment.actors.TasksRunner | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 deployment.preview | 2 | 1 | 1 | 5 | ||||||||||||||||||||||||||||||||||||
| 20 docs | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 lifecycle | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 magenta.RunState | 5 | |||||||||||||||||||||||||||||||||||||||
| 23 magenta.Strategy | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 magenta.input.resolver | 2 | 15 | 3 | 5 | 5 | |||||||||||||||||||||||||||||||||||
| 25 magenta.tasks.stackSetPolicy | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 26 views.html.helper.magenta | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 deployment | 1 | 7 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 28 utils | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 deployment.actors.DeployCoordinator | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 housekeeping | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 restrictions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 persistence | 1 | 38 | 1 | 7 | 2 | 2 | 1 | 8 | 3 | |||||||||||||||||||||||||||||||
| 33 notification | 1 | 4 | 3 | 2 | 1 | 4 | 3 | |||||||||||||||||||||||||||||||||
| 34 controllers | 1 | 2 | 2 | 1 | 5 | 1 | ||||||||||||||||||||||||||||||||||
| 35 ci | 3 | 1 | 1 | 2 | 2 | 1 | 6 | |||||||||||||||||||||||||||||||||
| 36 conf | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 controllers.Api | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 deployment.actors | 3 | 2 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 39 resources | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 (global) | 1 | 1 | 3 | 1 |
6→15 magenta.ContextMessage uses magenta part of a loop✕
- Connections
- 6 pairs of types, where a type in magenta.ContextMessage uses a type in magenta.
- The types involved
magenta.ContextMessage.FailContext→magenta.ContextMessagemagenta.ContextMessage.FailContext→magenta.Messagemagenta.ContextMessage.FinishContext→magenta.ContextMessagemagenta.ContextMessage.FinishContext→magenta.Messagemagenta.ContextMessage.StartContext→magenta.ContextMessagemagenta.ContextMessage.StartContext→magenta.Message
- Direction
- magenta.ContextMessage uses magenta, so a change to magenta can break magenta.ContextMessage, while a change to magenta.ContextMessage can't break magenta.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→15 magenta.Message uses magenta part of a loop✕
- Connections
- 13 pairs of types, where a type in magenta.Message uses a type in magenta.
- The types involved
magenta.Message.CommandError→magenta.Messagemagenta.Message.CommandOutput→magenta.Messagemagenta.Message.Deploy→magenta.DeployParametersmagenta.Message.Deploy→magenta.Messagemagenta.Message.Fail→magenta.Messagemagenta.Message.Fail→magenta.ThrowableDetailmagenta.Message.Info→magenta.Messagemagenta.Message.TaskList→magenta.Messagemagenta.Message.TaskList→magenta.TaskDetailmagenta.Message.TaskRun→magenta.Messagemagenta.Message.TaskRun→magenta.TaskDetailmagenta.Message.Verbose→magenta.Messagemagenta.Message.Warning→magenta.Message
- Direction
- magenta.Message uses magenta, so a change to magenta can break magenta.Message, while a change to magenta.Message can't break magenta.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→4 magenta.deployment_type uses magenta.tasks.ASG✕
- Connections
- 2 pairs of types, where a type in magenta.deployment_type uses a type in magenta.tasks.ASG.
- The types involved
magenta.deployment_type.AutoScalingGroupInfo→magenta.tasks.ASG.TagRequirementmagenta.deployment_type.AutoScalingGroupLookup→magenta.tasks.ASG.TagRequirement
- Direction
- magenta.deployment_type uses magenta.tasks.ASG, so a change to magenta.tasks.ASG can break magenta.deployment_type, while a change to magenta.deployment_type can't break magenta.tasks.ASG.
- Position
- Below the diagonal: magenta.deployment_type uses a module listed above it, which is the healthy direction.
8→5 magenta.deployment_type uses magenta.tasks.S3✕
- Connections
- 3 pairs of types, where a type in magenta.deployment_type uses a type in magenta.tasks.S3.
- The types involved
magenta.deployment_type.BucketParameters→magenta.tasks.S3.Bucketmagenta.deployment_type.UpdateLambdaFunction→magenta.tasks.S3.Bucketmagenta.deployment_type.UpdateLambdaLayer→magenta.tasks.S3.Bucket
- Direction
- magenta.deployment_type uses magenta.tasks.S3, so a change to magenta.tasks.S3 can break magenta.deployment_type, while a change to magenta.deployment_type can't break magenta.tasks.S3.
- Position
- Below the diagonal: magenta.deployment_type uses a module listed above it, which is the healthy direction.
8→15 magenta.deployment_type uses magenta part of a loop✕
- Connections
- 33 pairs of types, where a type in magenta.deployment_type uses a type in magenta. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
magenta.deployment_type.AutoScaling→magenta.DeploymentResourcesmagenta.deployment_type.AutoScaling→magenta.KeyRingmagenta.deployment_type.AutoScaling→magenta.Regionmagenta.deployment_type.AutoScalingGroupLookup→magenta.Appmagenta.deployment_type.AutoScalingGroupLookup→magenta.DeployTargetmagenta.deployment_type.AutoScalingGroupLookup→magenta.DeploymentPackagemagenta.deployment_type.AutoScalingGroupLookup→magenta.DeploymentResourcesmagenta.deployment_type.AutoScalingGroupLookup→magenta.KeyRingmagenta.deployment_type.AutoScalingGroupLookup→magenta.Stackmagenta.deployment_type.AutoScalingGroupLookup→magenta.Stagemagenta.deployment_type.BucketParameters→magenta.DeployReportermagenta.deployment_type.BucketParameters→magenta.DeployTargetmagenta.deployment_type.BucketParameters→magenta.DeploymentPackagemagenta.deployment_type.CloudFormation→magenta.Loggablemagenta.deployment_type.DeploymentType→magenta.DeploymentPackagemagenta.deployment_type.DeploymentType→magenta.DeploymentStepmagenta.deployment_type.FastlyCompute→magenta.DeploymentResourcesmagenta.deployment_type.FastlyCompute→magenta.KeyRingmagenta.deployment_type.FastlyCompute→magenta.Regionmagenta.deployment_type.LambdaLayer→magenta.DeployReportermagenta.deployment_type.LambdaLayer→magenta.DeployTargetmagenta.deployment_type.LambdaLayer→magenta.DeploymentPackagemagenta.deployment_type.LambdaLayer→magenta.DeploymentResourcesmagenta.deployment_type.LambdaLayer→magenta.KeyRingmagenta.deployment_type.LambdaLayer→magenta.Region
- Direction
- magenta.deployment_type uses magenta, so a change to magenta can break magenta.deployment_type, while a change to magenta.deployment_type can't break magenta.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→15 magenta.tasks.autoscaling uses magenta part of a loop✕
- Connections
- 2 pairs of types, where a type in magenta.tasks.autoscaling uses a type in magenta.
- The types involved
magenta.tasks.autoscaling.CullSummary→magenta.DeployReportermagenta.tasks.autoscaling.CullSummary→magenta.Loggable
- Direction
- magenta.tasks.autoscaling uses magenta, so a change to magenta can break magenta.tasks.autoscaling, while a change to magenta.tasks.autoscaling can't break magenta.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→34 schedule uses controllers part of a loop✕
- Connections
- 2 pairs of types, where a type in schedule uses a type in controllers.
- The types involved
schedule.DeployJob→controllers.Loggingschedule.DeployScheduler→controllers.Logging
- Direction
- schedule uses controllers, so a change to controllers can break schedule, while a change to schedule can't break controllers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→35 schedule uses ci part of a loop✕
- Connections
- 1 pair of types, where a type in schedule uses a type in ci.
- The types involved
schedule.DeployJob→ci.Job
- Direction
- schedule uses ci, so a change to ci can break schedule, while a change to schedule can't break ci.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→8 AppComponents uses magenta.deployment_type✕
- Connections
- 1 pair of types, where a type in AppComponents uses a type in magenta.deployment_type.
- The types involved
AppComponents.DefaultBuildTags→magenta.deployment_type.BuildTags
- Direction
- AppComponents uses magenta.deployment_type, so a change to magenta.deployment_type can break AppComponents, while a change to AppComponents can't break magenta.deployment_type.
- Position
- Below the diagonal: AppComponents uses a module listed above it, which is the healthy direction.
12→10 controllers.ScheduleController uses schedule✕
- Connections
- 1 pair of types, where a type in controllers.ScheduleController uses a type in schedule.
- The types involved
controllers.ScheduleController.ScheduleForm→schedule.ScheduleConfig
- Direction
- controllers.ScheduleController uses schedule, so a change to schedule can break controllers.ScheduleController, while a change to controllers.ScheduleController can't break schedule.
- Position
- Below the diagonal: controllers.ScheduleController uses a module listed above it, which is the healthy direction.
13→1 magenta.tasks uses magenta.artifact✕
- Connections
- 7 pairs of types, where a type in magenta.tasks uses a type in magenta.artifact.
- The types involved
magenta.tasks.FastlyComputeTasks→magenta.artifact.S3Objectmagenta.tasks.FastlyComputeTasks→magenta.artifact.S3Pathmagenta.tasks.PutReq→magenta.artifact.S3Objectmagenta.tasks.PutReq→magenta.artifact.S3Pathmagenta.tasks.S3Upload→magenta.artifact.S3Locationmagenta.tasks.S3Upload→magenta.artifact.S3Objectmagenta.tasks.UpdateFastlyConfig→magenta.artifact.S3Path
- Direction
- magenta.tasks uses magenta.artifact, so a change to magenta.artifact can break magenta.tasks, while a change to magenta.tasks can't break magenta.artifact.
- Position
- Below the diagonal: magenta.tasks uses a module listed above it, which is the healthy direction.
13→4 magenta.tasks uses magenta.tasks.ASG✕
- Connections
- 3 pairs of types, where a type in magenta.tasks uses a type in magenta.tasks.ASG.
- The types involved
magenta.tasks.ASG→magenta.tasks.ASG.TagMatchmagenta.tasks.ASG→magenta.tasks.ASG.TagRequirementmagenta.tasks.CloudFormationParameters→magenta.tasks.ASG.TagMatch
- Direction
- magenta.tasks uses magenta.tasks.ASG, so a change to magenta.tasks.ASG can break magenta.tasks, while a change to magenta.tasks can't break magenta.tasks.ASG.
- Position
- Below the diagonal: magenta.tasks uses a module listed above it, which is the healthy direction.
13→5 magenta.tasks uses magenta.tasks.S3✕
- Connections
- 1 pair of types, where a type in magenta.tasks uses a type in magenta.tasks.S3.
- The types involved
magenta.tasks.S3→magenta.tasks.S3.Bucket
- Direction
- magenta.tasks uses magenta.tasks.S3, so a change to magenta.tasks.S3 can break magenta.tasks, while a change to magenta.tasks can't break magenta.tasks.S3.
- Position
- Below the diagonal: magenta.tasks uses a module listed above it, which is the healthy direction.
13→8 magenta.tasks uses magenta.deployment_type✕
- Connections
- 15 pairs of types, where a type in magenta.tasks uses a type in magenta.deployment_type.
- The types involved
magenta.tasks.ASGTask→magenta.deployment_type.AutoScalingGroupInfomagenta.tasks.CheckGroupSize→magenta.deployment_type.AutoScalingGroupInfomagenta.tasks.CullInstancesWithTerminationTag→magenta.deployment_type.AutoScalingGroupInfomagenta.tasks.DoubleSize→magenta.deployment_type.AutoScalingGroupInfomagenta.tasks.HealthcheckGrace→magenta.deployment_type.AutoScalingGroupInfomagenta.tasks.ProtectCurrentInstances→magenta.deployment_type.AutoScalingGroupInfomagenta.tasks.ResumeAlarmNotifications→magenta.deployment_type.AutoScalingGroupInfomagenta.tasks.SuspendAlarmNotifications→magenta.deployment_type.AutoScalingGroupInfomagenta.tasks.TagCurrentInstancesWithTerminationTag→magenta.deployment_type.AutoScalingGroupInfomagenta.tasks.TerminationGrace→magenta.deployment_type.AutoScalingGroupInfomagenta.tasks.UpdateS3Lambda→magenta.deployment_type.LambdaFunctionmagenta.tasks.UpdateS3LambdaLayer→magenta.deployment_type.LambdaLayerNamemagenta.tasks.WaitForCullToComplete→magenta.deployment_type.AutoScalingGroupInfomagenta.tasks.WaitForStabilization→magenta.deployment_type.AutoScalingGroupInfomagenta.tasks.WarmupGrace→magenta.deployment_type.AutoScalingGroupInfo
- Direction
- magenta.tasks uses magenta.deployment_type, so a change to magenta.deployment_type can break magenta.tasks, while a change to magenta.tasks can't break magenta.deployment_type.
- Position
- Below the diagonal: magenta.tasks uses a module listed above it, which is the healthy direction.
13→9 magenta.tasks uses magenta.tasks.autoscaling✕
- Connections
- 1 pair of types, where a type in magenta.tasks uses a type in magenta.tasks.autoscaling.
- The types involved
magenta.tasks.CullInstancesWithTerminationTag→magenta.tasks.autoscaling.CullSummary
- Direction
- magenta.tasks uses magenta.tasks.autoscaling, so a change to magenta.tasks.autoscaling can break magenta.tasks, while a change to magenta.tasks can't break magenta.tasks.autoscaling.
- Position
- Below the diagonal: magenta.tasks uses a module listed above it, which is the healthy direction.
13→15 magenta.tasks uses magenta part of a loop✕
- Connections
- 122 pairs of types, where a type in magenta.tasks uses a type in magenta. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
magenta.tasks.ASG→magenta.DeployReportermagenta.tasks.ASG→magenta.DeploymentResourcesmagenta.tasks.ASG→magenta.KeyRingmagenta.tasks.ASG→magenta.Regionmagenta.tasks.ASG→magenta.Strategymagenta.tasks.ASGTask→magenta.DeploymentResourcesmagenta.tasks.ASGTask→magenta.Regionmagenta.tasks.AWS→magenta.DeploymentResourcesmagenta.tasks.AWS→magenta.KeyRingmagenta.tasks.AWS→magenta.Loggablemagenta.tasks.AWS→magenta.StsDeploymentResourcesmagenta.tasks.CheckChangeSetCreatedTask→magenta.DeployReportermagenta.tasks.CheckChangeSetCreatedTask→magenta.DeploymentResourcesmagenta.tasks.CheckChangeSetCreatedTask→magenta.KeyRingmagenta.tasks.CheckGroupSize→magenta.DeploymentResourcesmagenta.tasks.CheckGroupSize→magenta.KeyRingmagenta.tasks.CheckGroupSize→magenta.Regionmagenta.tasks.CloudFormation→magenta.DeployReportermagenta.tasks.CloudFormation→magenta.DeploymentResourcesmagenta.tasks.CloudFormation→magenta.KeyRingmagenta.tasks.CloudFormation→magenta.Regionmagenta.tasks.CloudFormationParameterLogger→magenta.DeployReportermagenta.tasks.CloudFormationParameters→magenta.DeployTargetmagenta.tasks.CloudFormationStackEventPoller→magenta.DeployReportermagenta.tasks.CloudFormationStackEventPoller→magenta.Loggable
- Direction
- magenta.tasks uses magenta, so a change to magenta can break magenta.tasks, while a change to magenta.tasks can't break magenta.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→13 magenta.graph uses magenta.tasks✕
- Connections
- 2 pairs of types, where a type in magenta.graph uses a type in magenta.tasks.
- The types involved
magenta.graph.DeploymentGraph→magenta.tasks.Taskmagenta.graph.DeploymentTasks→magenta.tasks.Task
- Direction
- magenta.graph uses magenta.tasks, so a change to magenta.tasks can break magenta.graph, while a change to magenta.graph can't break magenta.tasks.
- Position
- Below the diagonal: magenta.graph uses a module listed above it, which is the healthy direction.
15→1 magenta uses magenta.artifact✕
- Connections
- 1 pair of types, where a type in magenta uses a type in magenta.artifact.
- The types involved
magenta.DeploymentPackage→magenta.artifact.S3Path
- Direction
- magenta uses magenta.artifact, so a change to magenta.artifact can break magenta, while a change to magenta can't break magenta.artifact.
- Position
- Below the diagonal: magenta uses a module listed above it, which is the healthy direction.
15→3 magenta uses magenta.input✕
- Connections
- 1 pair of types, where a type in magenta uses a type in magenta.input.
- The types involved
magenta.DeployParameters→magenta.input.DeploymentSelector
- Direction
- magenta uses magenta.input, so a change to magenta.input can break magenta, while a change to magenta can't break magenta.input.
- Position
- Below the diagonal: magenta uses a module listed above it, which is the healthy direction.
15→6 magenta uses magenta.ContextMessage✕
- Connections
- 6 pairs of types, where a type in magenta uses a type in magenta.ContextMessage.
- The types involved
magenta.FailMessageState→magenta.ContextMessage.FailContextmagenta.FailMessageState→magenta.ContextMessage.StartContextmagenta.FinishMessageState→magenta.ContextMessage.FinishContextmagenta.FinishMessageState→magenta.ContextMessage.StartContextmagenta.MessageState→magenta.ContextMessage.StartContextmagenta.StartMessageState→magenta.ContextMessage.StartContext
- Direction
- magenta uses magenta.ContextMessage, so a change to magenta.ContextMessage can break magenta, while a change to magenta can't break magenta.ContextMessage.
- Position
- Below the diagonal: magenta uses a module listed above it, which is the healthy direction.
15→7 magenta uses magenta.Message✕
- Connections
- 1 pair of types, where a type in magenta uses a type in magenta.Message.
- The types involved
magenta.DeployReport→magenta.Message.Fail
- Direction
- magenta uses magenta.Message, so a change to magenta.Message can break magenta, while a change to magenta can't break magenta.Message.
- Position
- Below the diagonal: magenta uses a module listed above it, which is the healthy direction.
15→8 magenta uses magenta.deployment_type✕
- Connections
- 1 pair of types, where a type in magenta uses a type in magenta.deployment_type.
- The types involved
magenta.DeploymentPackage→magenta.deployment_type.DeploymentType
- Direction
- magenta uses magenta.deployment_type, so a change to magenta.deployment_type can break magenta, while a change to magenta can't break magenta.deployment_type.
- Position
- Below the diagonal: magenta uses a module listed above it, which is the healthy direction.
15→13 magenta uses magenta.tasks✕
- Connections
- 2 pairs of types, where a type in magenta uses a type in magenta.tasks.
- The types involved
magenta.DeployReporter→magenta.tasks.Taskmagenta.DeploymentStep→magenta.tasks.Task
- Direction
- magenta uses magenta.tasks, so a change to magenta.tasks can break magenta, while a change to magenta can't break magenta.tasks.
- Position
- Below the diagonal: magenta uses a module listed above it, which is the healthy direction.
15→14 magenta uses magenta.graph✕
- Connections
- 2 pairs of types, where a type in magenta uses a type in magenta.graph.
- The types involved
magenta.DeployContext→magenta.graph.DeploymentTasksmagenta.DeployContext→magenta.graph.Graph
- Direction
- magenta uses magenta.graph, so a change to magenta.graph can break magenta, while a change to magenta can't break magenta.graph.
- Position
- Below the diagonal: magenta uses a module listed above it, which is the healthy direction.
16→3 controllers.forms uses magenta.input✕
- Connections
- 2 pairs of types, where a type in controllers.forms uses a type in magenta.input.
- The types involved
controllers.forms.DeployParameterForm→magenta.input.DeploymentKeycontrollers.forms.DeployParameterForm→magenta.input.DeploymentSelector
- Direction
- controllers.forms uses magenta.input, so a change to magenta.input can break controllers.forms, while a change to controllers.forms can't break magenta.input.
- Position
- Below the diagonal: controllers.forms uses a module listed above it, which is the healthy direction.
16→15 controllers.forms uses magenta✕
- Connections
- 1 pair of types, where a type in controllers.forms uses a type in magenta.
- The types involved
controllers.forms.DeployParameterForm→magenta.Strategy
- Direction
- controllers.forms uses magenta, so a change to magenta can break controllers.forms, while a change to controllers.forms can't break magenta.
- Position
- Below the diagonal: controllers.forms uses a module listed above it, which is the healthy direction.
17→14 deployment.actors.DeployGroupRunner uses magenta.graph✕
- Connections
- 4 pairs of types, where a type in deployment.actors.DeployGroupRunner uses a type in magenta.graph.
- The types involved
deployment.actors.DeployGroupRunner.DeploymentCompleted→magenta.graph.DeploymentTasksdeployment.actors.DeployGroupRunner.DeploymentFailed→magenta.graph.DeploymentTasksdeployment.actors.DeployGroupRunner.NextTasks→magenta.graph.DeploymentTasksdeployment.actors.DeployGroupRunner.NextTasks→magenta.graph.ValueNode
- Direction
- deployment.actors.DeployGroupRunner uses magenta.graph, so a change to magenta.graph can break deployment.actors.DeployGroupRunner, while a change to deployment.actors.DeployGroupRunner can't break magenta.graph.
- Position
- Below the diagonal: deployment.actors.DeployGroupRunner uses a module listed above it, which is the healthy direction.
17→15 deployment.actors.DeployGroupRunner uses magenta✕
- Connections
- 6 pairs of types, where a type in deployment.actors.DeployGroupRunner uses a type in magenta.
- The types involved
deployment.actors.DeployGroupRunner.ContextCreated→magenta.DeployContextdeployment.actors.DeployGroupRunner.ContextCreated→magenta.Messagedeployment.actors.DeployGroupRunner.DeploymentCompleted→magenta.Messagedeployment.actors.DeployGroupRunner.DeploymentFailed→magenta.Messagedeployment.actors.DeployGroupRunner.Start→magenta.Messagedeployment.actors.DeployGroupRunner.StartDeployment→magenta.Message
- Direction
- deployment.actors.DeployGroupRunner uses magenta, so a change to magenta can break deployment.actors.DeployGroupRunner, while a change to deployment.actors.DeployGroupRunner can't break magenta.
- Position
- Below the diagonal: deployment.actors.DeployGroupRunner uses a module listed above it, which is the healthy direction.
18→14 deployment.actors.TasksRunner uses magenta.graph✕
- Connections
- 1 pair of types, where a type in deployment.actors.TasksRunner uses a type in magenta.graph.
- The types involved
deployment.actors.TasksRunner.RunDeployment→magenta.graph.DeploymentTasks
- Direction
- deployment.actors.TasksRunner uses magenta.graph, so a change to magenta.graph can break deployment.actors.TasksRunner, while a change to deployment.actors.TasksRunner can't break magenta.graph.
- Position
- Below the diagonal: deployment.actors.TasksRunner uses a module listed above it, which is the healthy direction.
18→15 deployment.actors.TasksRunner uses magenta✕
- Connections
- 2 pairs of types, where a type in deployment.actors.TasksRunner uses a type in magenta.
- The types involved
deployment.actors.TasksRunner.RunDeployment→magenta.DeploymentResourcesdeployment.actors.TasksRunner.RunDeployment→magenta.Message
- Direction
- deployment.actors.TasksRunner uses magenta, so a change to magenta can break deployment.actors.TasksRunner, while a change to deployment.actors.TasksRunner can't break magenta.
- Position
- Below the diagonal: deployment.actors.TasksRunner uses a module listed above it, which is the healthy direction.
19→1 deployment.preview uses magenta.artifact✕
- Connections
- 2 pairs of types, where a type in deployment.preview uses a type in magenta.artifact.
- The types involved
deployment.preview.Preview→magenta.artifact.S3YamlArtifactdeployment.preview.PreviewCoordinator→magenta.artifact.S3Error
- Direction
- deployment.preview uses magenta.artifact, so a change to magenta.artifact can break deployment.preview, while a change to deployment.preview can't break magenta.artifact.
- Position
- Below the diagonal: deployment.preview uses a module listed above it, which is the healthy direction.
19→8 deployment.preview uses magenta.deployment_type✕
- Connections
- 1 pair of types, where a type in deployment.preview uses a type in magenta.deployment_type.
- The types involved
deployment.preview.Preview→magenta.deployment_type.DeploymentType
- Direction
- deployment.preview uses magenta.deployment_type, so a change to magenta.deployment_type can break deployment.preview, while a change to deployment.preview can't break magenta.deployment_type.
- Position
- Below the diagonal: deployment.preview uses a module listed above it, which is the healthy direction.
19→14 deployment.preview uses magenta.graph✕
- Connections
- 1 pair of types, where a type in deployment.preview uses a type in magenta.graph.
- The types involved
deployment.preview.Preview→magenta.graph.Graph
- Direction
- deployment.preview uses magenta.graph, so a change to magenta.graph can break deployment.preview, while a change to deployment.preview can't break magenta.graph.
- Position
- Below the diagonal: deployment.preview uses a module listed above it, which is the healthy direction.
19→15 deployment.preview uses magenta✕
- Connections
- 5 pairs of types, where a type in deployment.preview uses a type in magenta.
- The types involved
deployment.preview.Preview→magenta.DeployParametersdeployment.preview.Preview→magenta.DeploymentResourcesdeployment.preview.Preview→magenta.Loggabledeployment.preview.PreviewCoordinator→magenta.DeployParametersdeployment.preview.PreviewCoordinator→magenta.Loggable
- Direction
- deployment.preview uses magenta, so a change to magenta can break deployment.preview, while a change to deployment.preview can't break magenta.
- Position
- Below the diagonal: deployment.preview uses a module listed above it, which is the healthy direction.
20→15 docs uses magenta✕
- Connections
- 1 pair of types, where a type in docs uses a type in magenta.
- The types involved
docs.MarkDownParser→magenta.Loggable
- Direction
- docs uses magenta, so a change to magenta can break docs, while a change to docs can't break magenta.
- Position
- Below the diagonal: docs uses a module listed above it, which is the healthy direction.
21→15 lifecycle uses magenta✕
- Connections
- 1 pair of types, where a type in lifecycle uses a type in magenta.
- The types involved
lifecycle.WhenInactive→magenta.DefaultSwitch
- Direction
- lifecycle uses magenta, so a change to magenta can break lifecycle, while a change to lifecycle can't break magenta.
- Position
- Below the diagonal: lifecycle uses a module listed above it, which is the healthy direction.
21→27 lifecycle uses deployment part of a loop✕
- Connections
- 3 pairs of types, where a type in lifecycle uses a type in deployment.
- The types involved
lifecycle.ShutdownWhenInactive→deployment.Deploymentslifecycle.TerminateInstanceWhenInactive→deployment.Deploymentslifecycle.WhenInactive→deployment.Deployments
- Direction
- lifecycle uses deployment, so a change to deployment can break lifecycle, while a change to lifecycle can't break deployment.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→34 lifecycle uses controllers part of a loop✕
- Connections
- 1 pair of types, where a type in lifecycle uses a type in controllers.
- The types involved
lifecycle.WhenInactive→controllers.Logging
- Direction
- lifecycle uses controllers, so a change to controllers can break lifecycle, while a change to lifecycle can't break controllers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→15 magenta.RunState uses magenta✕
- Connections
- 5 pairs of types, where a type in magenta.RunState uses a type in magenta.
- The types involved
magenta.RunState.ChildRunning→magenta.RunStatemagenta.RunState.Completed→magenta.RunStatemagenta.RunState.Failed→magenta.RunStatemagenta.RunState.NotRunning→magenta.RunStatemagenta.RunState.Running→magenta.RunState
- Direction
- magenta.RunState uses magenta, so a change to magenta can break magenta.RunState, while a change to magenta.RunState can't break magenta.
- Position
- Below the diagonal: magenta.RunState uses a module listed above it, which is the healthy direction.
23→15 magenta.Strategy uses magenta✕
- Connections
- 2 pairs of types, where a type in magenta.Strategy uses a type in magenta.
- The types involved
magenta.Strategy.Dangerous→magenta.Strategymagenta.Strategy.MostlyHarmless→magenta.Strategy
- Direction
- magenta.Strategy uses magenta, so a change to magenta can break magenta.Strategy, while a change to magenta.Strategy can't break magenta.
- Position
- Below the diagonal: magenta.Strategy uses a module listed above it, which is the healthy direction.
24→1 magenta.input.resolver uses magenta.artifact✕
- Connections
- 2 pairs of types, where a type in magenta.input.resolver uses a type in magenta.artifact.
- The types involved
magenta.input.resolver.Resolver→magenta.artifact.S3Artifactmagenta.input.resolver.TaskResolver→magenta.artifact.S3Artifact
- Direction
- magenta.input.resolver uses magenta.artifact, so a change to magenta.artifact can break magenta.input.resolver, while a change to magenta.input.resolver can't break magenta.artifact.
- Position
- Below the diagonal: magenta.input.resolver uses a module listed above it, which is the healthy direction.
24→3 magenta.input.resolver uses magenta.input✕
- Connections
- 15 pairs of types, where a type in magenta.input.resolver uses a type in magenta.input.
- The types involved
magenta.input.resolver.DeploymentGraphActionFlattening→magenta.input.Deploymentmagenta.input.resolver.DeploymentGraphBuilder→magenta.input.Deploymentmagenta.input.resolver.DeploymentPruner→magenta.input.Deploymentmagenta.input.resolver.DeploymentPruner→magenta.input.DeploymentKeymagenta.input.resolver.DeploymentPruner→magenta.input.DeploymentSelectormagenta.input.resolver.DeploymentResolver→magenta.input.ConfigErrorsmagenta.input.resolver.DeploymentResolver→magenta.input.DeploymentOrTemplatemagenta.input.resolver.DeploymentResolver→magenta.input.RiffRaffDeployConfigmagenta.input.resolver.DeploymentTypeResolver→magenta.input.ConfigErrorsmagenta.input.resolver.DeploymentTypeResolver→magenta.input.Deploymentmagenta.input.resolver.Resolver→magenta.input.ConfigErrorsmagenta.input.resolver.Resolver→magenta.input.Deploymentmagenta.input.resolver.Resolver→magenta.input.DeploymentSelectormagenta.input.resolver.TaskResolver→magenta.input.ConfigErrorsmagenta.input.resolver.TaskResolver→magenta.input.Deployment
- Direction
- magenta.input.resolver uses magenta.input, so a change to magenta.input can break magenta.input.resolver, while a change to magenta.input.resolver can't break magenta.input.
- Position
- Below the diagonal: magenta.input.resolver uses a module listed above it, which is the healthy direction.
24→8 magenta.input.resolver uses magenta.deployment_type✕
- Connections
- 3 pairs of types, where a type in magenta.input.resolver uses a type in magenta.deployment_type.
- The types involved
magenta.input.resolver.DeploymentTypeResolver→magenta.deployment_type.DeploymentTypemagenta.input.resolver.Resolver→magenta.deployment_type.DeploymentTypemagenta.input.resolver.TaskResolver→magenta.deployment_type.DeploymentType
- Direction
- magenta.input.resolver uses magenta.deployment_type, so a change to magenta.deployment_type can break magenta.input.resolver, while a change to magenta.input.resolver can't break magenta.deployment_type.
- Position
- Below the diagonal: magenta.input.resolver uses a module listed above it, which is the healthy direction.
24→14 magenta.input.resolver uses magenta.graph✕
- Connections
- 5 pairs of types, where a type in magenta.input.resolver uses a type in magenta.graph.
- The types involved
magenta.input.resolver.DeploymentGraphActionFlattening→magenta.graph.Graphmagenta.input.resolver.DeploymentGraphBuilder→magenta.graph.Graphmagenta.input.resolver.Resolver→magenta.graph.DeploymentTasksmagenta.input.resolver.Resolver→magenta.graph.Graphmagenta.input.resolver.TaskResolver→magenta.graph.DeploymentTasks
- Direction
- magenta.input.resolver uses magenta.graph, so a change to magenta.graph can break magenta.input.resolver, while a change to magenta.input.resolver can't break magenta.graph.
- Position
- Below the diagonal: magenta.input.resolver uses a module listed above it, which is the healthy direction.
24→15 magenta.input.resolver uses magenta✕
- Connections
- 5 pairs of types, where a type in magenta.input.resolver uses a type in magenta.
- The types involved
magenta.input.resolver.Resolver→magenta.DeployParametersmagenta.input.resolver.Resolver→magenta.DeploymentResourcesmagenta.input.resolver.TaskResolver→magenta.DeployParametersmagenta.input.resolver.TaskResolver→magenta.DeploymentPackagemagenta.input.resolver.TaskResolver→magenta.DeploymentResources
- Direction
- magenta.input.resolver uses magenta, so a change to magenta can break magenta.input.resolver, while a change to magenta.input.resolver can't break magenta.
- Position
- Below the diagonal: magenta.input.resolver uses a module listed above it, which is the healthy direction.
25→13 magenta.tasks.stackSetPolicy uses magenta.tasks✕
- Connections
- 1 pair of types, where a type in magenta.tasks.stackSetPolicy uses a type in magenta.tasks.
- The types involved
magenta.tasks.stackSetPolicy.SetStackPolicyTask→magenta.tasks.Task
- Direction
- magenta.tasks.stackSetPolicy uses magenta.tasks, so a change to magenta.tasks can break magenta.tasks.stackSetPolicy, while a change to magenta.tasks.stackSetPolicy can't break magenta.tasks.
- Position
- Below the diagonal: magenta.tasks.stackSetPolicy uses a module listed above it, which is the healthy direction.
25→15 magenta.tasks.stackSetPolicy uses magenta✕
- Connections
- 2 pairs of types, where a type in magenta.tasks.stackSetPolicy uses a type in magenta.
- The types involved
magenta.tasks.stackSetPolicy.SetStackPolicyTask→magenta.DeploymentResourcesmagenta.tasks.stackSetPolicy.SetStackPolicyTask→magenta.KeyRing
- Direction
- magenta.tasks.stackSetPolicy uses magenta, so a change to magenta can break magenta.tasks.stackSetPolicy, while a change to magenta.tasks.stackSetPolicy can't break magenta.
- Position
- Below the diagonal: magenta.tasks.stackSetPolicy uses a module listed above it, which is the healthy direction.
26→14 views.html.helper.magenta uses magenta.graph✕
- Connections
- 1 pair of types, where a type in views.html.helper.magenta uses a type in magenta.graph.
- The types involved
views.html.helper.magenta.PreviewHelper→magenta.graph.Graph
- Direction
- views.html.helper.magenta uses magenta.graph, so a change to magenta.graph can break views.html.helper.magenta, while a change to views.html.helper.magenta can't break magenta.graph.
- Position
- Below the diagonal: views.html.helper.magenta uses a module listed above it, which is the healthy direction.
26→15 views.html.helper.magenta uses magenta✕
- Connections
- 1 pair of types, where a type in views.html.helper.magenta uses a type in magenta.
- The types involved
views.html.helper.magenta.MessageHelper→magenta.DeployReport
- Direction
- views.html.helper.magenta uses magenta, so a change to magenta can break views.html.helper.magenta, while a change to views.html.helper.magenta can't break magenta.
- Position
- Below the diagonal: views.html.helper.magenta uses a module listed above it, which is the healthy direction.
27→2 deployment uses magenta.graph.Graph✕
- Connections
- 1 pair of types, where a type in deployment uses a type in magenta.graph.Graph.
- The types involved
deployment.Deployments→magenta.graph.Graph.Error
- Direction
- deployment uses magenta.graph.Graph, so a change to magenta.graph.Graph can break deployment, while a change to deployment can't break magenta.graph.Graph.
- Position
- Below the diagonal: deployment uses a module listed above it, which is the healthy direction.
27→15 deployment uses magenta✕
- Connections
- 7 pairs of types, where a type in deployment uses a type in magenta.
- The types involved
deployment.DeployFilter→magenta.RunStatedeployment.DeployFilterPagination→magenta.RunStatedeployment.DeployRecord→magenta.DeployParametersdeployment.DeployRecord→magenta.MessageWrapperdeployment.DeployRecord→magenta.RunStatedeployment.Deployments→magenta.DeployParametersdeployment.Deployments→magenta.MessageWrapper
- Direction
- deployment uses magenta, so a change to magenta can break deployment, while a change to deployment can't break magenta.
- Position
- Below the diagonal: deployment uses a module listed above it, which is the healthy direction.
27→21 deployment uses lifecycle✕
- Connections
- 1 pair of types, where a type in deployment uses a type in lifecycle.
- The types involved
deployment.Deployments→lifecycle.Lifecycle
- Direction
- deployment uses lifecycle, so a change to lifecycle can break deployment, while a change to deployment can't break lifecycle.
- Position
- Below the diagonal: deployment uses a module listed above it, which is the healthy direction.
27→34 deployment uses controllers part of a loop✕
- Connections
- 3 pairs of types, where a type in deployment uses a type in controllers.
- The types involved
deployment.ApiRequestSource→controllers.ApiKeydeployment.DeploymentEngine→controllers.Loggingdeployment.Deployments→controllers.Logging
- Direction
- deployment uses controllers, so a change to controllers can break deployment, while a change to deployment can't break controllers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→15 utils uses magenta✕
- Connections
- 2 pairs of types, where a type in utils uses a type in magenta.
- The types involved
utils.Forms→magenta.Loggableutils.PathBindables→magenta.Strategy
- Direction
- utils uses magenta, so a change to magenta can break utils, while a change to utils can't break magenta.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
28→21 utils uses lifecycle✕
- Connections
- 1 pair of types, where a type in utils uses a type in lifecycle.
- The types involved
utils.ScheduledAgent→lifecycle.Lifecycle
- Direction
- utils uses lifecycle, so a change to lifecycle can break utils, while a change to utils can't break lifecycle.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
29→15 deployment.actors.DeployCoordinator uses magenta✕
- Connections
- 2 pairs of types, where a type in deployment.actors.DeployCoordinator uses a type in magenta.
- The types involved
deployment.actors.DeployCoordinator.CleanupDeploy→magenta.Messagedeployment.actors.DeployCoordinator.StartDeploy→magenta.Message
- Direction
- deployment.actors.DeployCoordinator uses magenta, so a change to magenta can break deployment.actors.DeployCoordinator, while a change to deployment.actors.DeployCoordinator can't break magenta.
- Position
- Below the diagonal: deployment.actors.DeployCoordinator uses a module listed above it, which is the healthy direction.
29→27 deployment.actors.DeployCoordinator uses deployment✕
- Connections
- 1 pair of types, where a type in deployment.actors.DeployCoordinator uses a type in deployment.
- The types involved
deployment.actors.DeployCoordinator.StartDeploy→deployment.Record
- Direction
- deployment.actors.DeployCoordinator uses deployment, so a change to deployment can break deployment.actors.DeployCoordinator, while a change to deployment.actors.DeployCoordinator can't break deployment.
- Position
- Below the diagonal: deployment.actors.DeployCoordinator uses a module listed above it, which is the healthy direction.
30→1 housekeeping uses magenta.artifact✕
- Connections
- 1 pair of types, where a type in housekeeping uses a type in magenta.artifact.
- The types involved
housekeeping.ArtifactHousekeeping→magenta.artifact.S3Object
- Direction
- housekeeping uses magenta.artifact, so a change to magenta.artifact can break housekeeping, while a change to housekeeping can't break magenta.artifact.
- Position
- Below the diagonal: housekeeping uses a module listed above it, which is the healthy direction.
30→27 housekeeping uses deployment✕
- Connections
- 1 pair of types, where a type in housekeeping uses a type in deployment.
- The types involved
housekeeping.ArtifactHousekeeping→deployment.Deployments
- Direction
- housekeeping uses deployment, so a change to deployment can break housekeeping, while a change to housekeeping can't break deployment.
- Position
- Below the diagonal: housekeeping uses a module listed above it, which is the healthy direction.
31→2 restrictions uses magenta.graph.Graph✕
- Connections
- 1 pair of types, where a type in restrictions uses a type in magenta.graph.Graph.
- The types involved
restrictions.RestrictionChecker→magenta.graph.Graph.Error
- Direction
- restrictions uses magenta.graph.Graph, so a change to magenta.graph.Graph can break restrictions, while a change to restrictions can't break magenta.graph.Graph.
- Position
- Below the diagonal: restrictions uses a module listed above it, which is the healthy direction.
31→27 restrictions uses deployment✕
- Connections
- 1 pair of types, where a type in restrictions uses a type in deployment.
- The types involved
restrictions.RestrictionChecker→deployment.RequestSource
- Direction
- restrictions uses deployment, so a change to deployment can break restrictions, while a change to restrictions can't break deployment.
- Position
- Below the diagonal: restrictions uses a module listed above it, which is the healthy direction.
32→10 persistence uses schedule✕
- Connections
- 1 pair of types, where a type in persistence uses a type in schedule.
- The types involved
persistence.ScheduleRepository→schedule.ScheduleConfig
- Direction
- persistence uses schedule, so a change to schedule can break persistence, while a change to persistence can't break schedule.
- Position
- Below the diagonal: persistence uses a module listed above it, which is the healthy direction.
32→15 persistence uses magenta✕
- Connections
- 38 pairs of types, where a type in persistence uses a type in magenta. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
persistence.CommandErrorDocument→magenta.DeployParameterspersistence.CommandErrorDocument→magenta.Messagepersistence.CommandOutputDocument→magenta.DeployParameterspersistence.CommandOutputDocument→magenta.Messagepersistence.DeployDocument→magenta.DeployParameterspersistence.DeployDocument→magenta.Messagepersistence.DeployRecordDocument→magenta.RunStatepersistence.DocumentConverter→magenta.Messagepersistence.DocumentConverter→magenta.MessageStackpersistence.DocumentConverter→magenta.MessageWrapperpersistence.DocumentStore→magenta.RunStatepersistence.DocumentStoreConverter→magenta.MessageWrapperpersistence.DocumentStoreConverter→magenta.RunStatepersistence.FailContextDocument→magenta.DeployParameterspersistence.FailContextDocument→magenta.Messagepersistence.FailDocument→magenta.DeployParameterspersistence.FailDocument→magenta.Messagepersistence.FailDocument→magenta.ThrowableDetailpersistence.FinishContextDocument→magenta.DeployParameterspersistence.FinishContextDocument→magenta.Messagepersistence.InfoDocument→magenta.DeployParameterspersistence.InfoDocument→magenta.Messagepersistence.MessageDocument→magenta.DeployParameterspersistence.MessageDocument→magenta.Messagepersistence.ParametersDocument→magenta.Strategy
- Direction
- persistence uses magenta, so a change to magenta can break persistence, while a change to persistence can't break magenta.
- Position
- Below the diagonal: persistence uses a module listed above it, which is the healthy direction.
32→21 persistence uses lifecycle✕
- Connections
- 1 pair of types, where a type in persistence uses a type in lifecycle.
- The types involved
persistence.SummariseDeploysHousekeeping→lifecycle.Lifecycle
- Direction
- persistence uses lifecycle, so a change to lifecycle can break persistence, while a change to persistence can't break lifecycle.
- Position
- Below the diagonal: persistence uses a module listed above it, which is the healthy direction.
32→27 persistence uses deployment✕
- Connections
- 7 pairs of types, where a type in persistence uses a type in deployment.
- The types involved
persistence.DocumentStore→deployment.DeployFilterpersistence.DocumentStore→deployment.PaginationViewpersistence.DocumentStoreConverter→deployment.DeployFilterpersistence.DocumentStoreConverter→deployment.DeployRecordpersistence.DocumentStoreConverter→deployment.PaginationViewpersistence.PostgresDatastore→deployment.DeployFilterpersistence.PostgresDatastore→deployment.PaginationView
- Direction
- persistence uses deployment, so a change to deployment can break persistence, while a change to persistence can't break deployment.
- Position
- Below the diagonal: persistence uses a module listed above it, which is the healthy direction.
32→28 persistence uses utils✕
- Connections
- 2 pairs of types, where a type in persistence uses a type in utils.
- The types involved
persistence.DataStore→utils.Retriablepersistence.SummariseDeploysHousekeeping→utils.ScheduledAgent
- Direction
- persistence uses utils, so a change to utils can break persistence, while a change to persistence can't break utils.
- Position
- Below the diagonal: persistence uses a module listed above it, which is the healthy direction.
32→31 persistence uses restrictions✕
- Connections
- 2 pairs of types, where a type in persistence uses a type in restrictions.
- The types involved
persistence.RestrictionConfigDynamoRepository→restrictions.RestrictionConfigpersistence.RestrictionConfigDynamoRepository→restrictions.RestrictionsConfigRepository
- Direction
- persistence uses restrictions, so a change to restrictions can break persistence, while a change to persistence can't break restrictions.
- Position
- Below the diagonal: persistence uses a module listed above it, which is the healthy direction.
32→33 persistence uses notification part of a loop✕
- Connections
- 1 pair of types, where a type in persistence uses a type in notification.
- The types involved
persistence.HookConfigRepository→notification.HookConfig
- Direction
- persistence uses notification, so a change to notification can break persistence, while a change to persistence can't break notification.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→34 persistence uses controllers part of a loop✕
- Connections
- 8 pairs of types, where a type in persistence uses a type in controllers.
- The types involved
persistence.DataStore→controllers.ApiKeypersistence.DocumentStore→controllers.SimpleDeployDetailpersistence.DocumentStoreConverter→controllers.Loggingpersistence.PostgresDatastore→controllers.ApiKeypersistence.PostgresDatastore→controllers.Loggingpersistence.PostgresDatastore→controllers.SimpleDeployDetailpersistence.RecordConverter→controllers.Loggingpersistence.SummariseDeploysHousekeeping→controllers.Logging
- Direction
- persistence uses controllers, so a change to controllers can break persistence, while a change to persistence can't break controllers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→35 persistence uses ci part of a loop✕
- Connections
- 3 pairs of types, where a type in persistence uses a type in ci.
- The types involved
persistence.ContinuousDeploymentConfigRepository→ci.ContinuousDeploymentConfigpersistence.TargetDynamoRepository→ci.Targetpersistence.TargetId→ci.Target
- Direction
- persistence uses ci, so a change to ci can break persistence, while a change to persistence can't break ci.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→8 notification uses magenta.deployment_type✕
- Connections
- 1 pair of types, where a type in notification uses a type in magenta.deployment_type.
- The types involved
notification.NotificationContents→magenta.deployment_type.Action
- Direction
- notification uses magenta.deployment_type, so a change to magenta.deployment_type can break notification, while a change to notification can't break magenta.deployment_type.
- Position
- Below the diagonal: notification uses a module listed above it, which is the healthy direction.
33→15 notification uses magenta✕
- Connections
- 4 pairs of types, where a type in notification uses a type in magenta.
- The types involved
notification.DeployFailureNotifications→magenta.DeployParametersnotification.FailureNotificationContents→magenta.DeployParametersnotification.GrafanaAnnotationLogger→magenta.DeployParametersnotification.HooksClient→magenta.DeployParameters
- Direction
- notification uses magenta, so a change to magenta can break notification, while a change to notification can't break magenta.
- Position
- Below the diagonal: notification uses a module listed above it, which is the healthy direction.
33→21 notification uses lifecycle✕
- Connections
- 3 pairs of types, where a type in notification uses a type in lifecycle.
- The types involved
notification.DeployFailureNotifications→lifecycle.Lifecyclenotification.GrafanaAnnotationLogger→lifecycle.Lifecyclenotification.HooksClient→lifecycle.Lifecycle
- Direction
- notification uses lifecycle, so a change to lifecycle can break notification, while a change to notification can't break lifecycle.
- Position
- Below the diagonal: notification uses a module listed above it, which is the healthy direction.
33→27 notification uses deployment✕
- Connections
- 2 pairs of types, where a type in notification uses a type in deployment.
- The types involved
notification.DeployFailureNotifications→deployment.ScheduledDeployNotificationErrornotification.FailureNotificationContents→deployment.ScheduledDeployNotificationError
- Direction
- notification uses deployment, so a change to deployment can break notification, while a change to notification can't break deployment.
- Position
- Below the diagonal: notification uses a module listed above it, which is the healthy direction.
33→32 notification uses persistence✕
- Connections
- 1 pair of types, where a type in notification uses a type in persistence.
- The types involved
notification.HookConfig→persistence.DeployRecordDocument
- Direction
- notification uses persistence, so a change to persistence can break notification, while a change to notification can't break persistence.
- Position
- Below the diagonal: notification uses a module listed above it, which is the healthy direction.
33→34 notification uses controllers part of a loop✕
- Connections
- 4 pairs of types, where a type in notification uses a type in controllers.
- The types involved
notification.DeployFailureNotifications→controllers.Loggingnotification.GrafanaAnnotationLogger→controllers.Loggingnotification.HookConfig→controllers.Loggingnotification.HooksClient→controllers.Logging
- Direction
- notification uses controllers, so a change to controllers can break notification, while a change to notification can't break controllers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→35 notification uses ci part of a loop✕
- Connections
- 3 pairs of types, where a type in notification uses a type in ci.
- The types involved
notification.DeployFailureNotifications→ci.Targetnotification.FailureNotificationContents→ci.Targetnotification.NotificationContentsWithTargets→ci.Target
- Direction
- notification uses ci, so a change to ci can break notification, while a change to notification can't break ci.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→8 controllers uses magenta.deployment_type✕
- Connections
- 1 pair of types, where a type in controllers uses a type in magenta.deployment_type.
- The types involved
controllers.Management→magenta.deployment_type.Action
- Direction
- controllers uses magenta.deployment_type, so a change to magenta.deployment_type can break controllers, while a change to controllers can't break magenta.deployment_type.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
34→15 controllers uses magenta✕
- Connections
- 2 pairs of types, where a type in controllers uses a type in magenta.
- The types involved
controllers.PreviewController→magenta.Loggablecontrollers.PreviewController→magenta.Strategy
- Direction
- controllers uses magenta, so a change to magenta can break controllers, while a change to controllers can't break magenta.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
34→21 controllers uses lifecycle✕
- Connections
- 2 pairs of types, where a type in controllers uses a type in lifecycle.
- The types involved
controllers.Management→lifecycle.ShutdownWhenInactivecontrollers.Management→lifecycle.TerminateInstanceWhenInactive
- Direction
- controllers uses lifecycle, so a change to lifecycle can break controllers, while a change to controllers can't break lifecycle.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
34→27 controllers uses deployment✕
- Connections
- 1 pair of types, where a type in controllers uses a type in deployment.
- The types involved
controllers.Api→deployment.Record
- Direction
- controllers uses deployment, so a change to deployment can break controllers, while a change to controllers can't break deployment.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
34→28 controllers uses utils✕
- Connections
- 5 pairs of types, where a type in controllers uses a type in utils.
- The types involved
controllers.Api→utils.LogAndSquashBehaviourcontrollers.DeployController→utils.LogAndSquashBehaviourcontrollers.Login→utils.LogAndSquashBehaviourcontrollers.TargetController→utils.LogAndSquashBehaviourcontrollers.Testing→utils.LogAndSquashBehaviour
- Direction
- controllers uses utils, so a change to utils can break controllers, while a change to controllers can't break utils.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
34→33 controllers uses notification✕
- Connections
- 1 pair of types, where a type in controllers uses a type in notification.
- The types involved
controllers.HookForm→notification.HttpMethod
- Direction
- controllers uses notification, so a change to notification can break controllers, while a change to controllers can't break notification.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
35→1 ci uses magenta.artifact✕
- Connections
- 3 pairs of types, where a type in ci uses a type in magenta.artifact.
- The types involved
ci.CIBuildPoller→magenta.artifact.S3Objectci.S3BuildOps→magenta.artifact.S3Objectci.S3BuildRetrievalError→magenta.artifact.S3Error
- Direction
- ci uses magenta.artifact, so a change to magenta.artifact can break ci, while a change to ci can't break magenta.artifact.
- Position
- Below the diagonal: ci uses a module listed above it, which is the healthy direction.
35→3 ci uses magenta.input✕
- Connections
- 1 pair of types, where a type in ci uses a type in magenta.input.
- The types involved
ci.TargetResolver→magenta.input.Deployment
- Direction
- ci uses magenta.input, so a change to magenta.input can break ci, while a change to ci can't break magenta.input.
- Position
- Below the diagonal: ci uses a module listed above it, which is the healthy direction.
35→14 ci uses magenta.graph✕
- Connections
- 1 pair of types, where a type in ci uses a type in magenta.graph.
- The types involved
ci.TargetResolver→magenta.graph.Graph
- Direction
- ci uses magenta.graph, so a change to magenta.graph can break ci, while a change to ci can't break magenta.graph.
- Position
- Below the diagonal: ci uses a module listed above it, which is the healthy direction.
35→15 ci uses magenta✕
- Connections
- 2 pairs of types, where a type in ci uses a type in magenta.
- The types involved
ci.CIBuild→magenta.Buildci.ContinuousDeployment→magenta.DeployParameters
- Direction
- ci uses magenta, so a change to magenta can break ci, while a change to ci can't break magenta.
- Position
- Below the diagonal: ci uses a module listed above it, which is the healthy direction.
35→21 ci uses lifecycle✕
- Connections
- 2 pairs of types, where a type in ci uses a type in lifecycle.
- The types involved
ci.Builds→lifecycle.Lifecycleci.ContinuousDeployment→lifecycle.Lifecycle
- Direction
- ci uses lifecycle, so a change to lifecycle can break ci, while a change to ci can't break lifecycle.
- Position
- Below the diagonal: ci uses a module listed above it, which is the healthy direction.
35→24 ci uses magenta.input.resolver✕
- Connections
- 1 pair of types, where a type in ci uses a type in magenta.input.resolver.
- The types involved
ci.TargetResolver→magenta.input.resolver.PartiallyResolvedDeployment
- Direction
- ci uses magenta.input.resolver, so a change to magenta.input.resolver can break ci, while a change to ci can't break magenta.input.resolver.
- Position
- Below the diagonal: ci uses a module listed above it, which is the healthy direction.
35→34 ci uses controllers✕
- Connections
- 6 pairs of types, where a type in ci uses a type in controllers.
- The types involved
ci.Builds→controllers.Loggingci.CIBuildPoller→controllers.Loggingci.ContinuousDeployment→controllers.Loggingci.Every→controllers.Loggingci.FailSafeObservable→controllers.Loggingci.S3BuildOps→controllers.Logging
- Direction
- ci uses controllers, so a change to controllers can break ci, while a change to ci can't break controllers.
- Position
- Below the diagonal: ci uses a module listed above it, which is the healthy direction.
36→15 conf uses magenta✕
- Connections
- 1 pair of types, where a type in conf uses a type in magenta.
- The types involved
conf.Secrets→magenta.SecretProvider
- Direction
- conf uses magenta, so a change to magenta can break conf, while a change to conf can't break magenta.
- Position
- Below the diagonal: conf uses a module listed above it, which is the healthy direction.
36→34 conf uses controllers✕
- Connections
- 2 pairs of types, where a type in conf uses a type in controllers.
- The types involved
conf.Config→controllers.Loggingconf.Secrets→controllers.Logging
- Direction
- conf uses controllers, so a change to controllers can break conf, while a change to conf can't break controllers.
- Position
- Below the diagonal: conf uses a module listed above it, which is the healthy direction.
37→8 controllers.Api uses magenta.deployment_type✕
- Connections
- 1 pair of types, where a type in controllers.Api uses a type in magenta.deployment_type.
- The types involved
controllers.Api.ApiJsonEndpoint→magenta.deployment_type.Action
- Direction
- controllers.Api uses magenta.deployment_type, so a change to magenta.deployment_type can break controllers.Api, while a change to controllers.Api can't break magenta.deployment_type.
- Position
- Below the diagonal: controllers.Api uses a module listed above it, which is the healthy direction.
37→34 controllers.Api uses controllers✕
- Connections
- 1 pair of types, where a type in controllers.Api uses a type in controllers.
- The types involved
controllers.Api.ApiJsonEndpoint→controllers.ApiRequest
- Direction
- controllers.Api uses controllers, so a change to controllers can break controllers.Api, while a change to controllers.Api can't break controllers.
- Position
- Below the diagonal: controllers.Api uses a module listed above it, which is the healthy direction.
38→14 deployment.actors uses magenta.graph✕
- Connections
- 3 pairs of types, where a type in deployment.actors uses a type in magenta.graph.
- The types involved
deployment.actors.DeployGroupRunner→magenta.graph.DeploymentTasksdeployment.actors.DeployGroupRunner→magenta.graph.Graphdeployment.actors.DeployGroupRunner→magenta.graph.ValueNode
- Direction
- deployment.actors uses magenta.graph, so a change to magenta.graph can break deployment.actors, while a change to deployment.actors can't break magenta.graph.
- Position
- Below the diagonal: deployment.actors uses a module listed above it, which is the healthy direction.
38→15 deployment.actors uses magenta✕
- Connections
- 2 pairs of types, where a type in deployment.actors uses a type in magenta.
- The types involved
deployment.actors.DeployGroupRunner→magenta.DeployContextdeployment.actors.DeployGroupRunner→magenta.DeployReporter
- Direction
- deployment.actors uses magenta, so a change to magenta can break deployment.actors, while a change to deployment.actors can't break magenta.
- Position
- Below the diagonal: deployment.actors uses a module listed above it, which is the healthy direction.
38→17 deployment.actors uses deployment.actors.DeployGroupRunner✕
- Connections
- 1 pair of types, where a type in deployment.actors uses a type in deployment.actors.DeployGroupRunner.
- The types involved
deployment.actors.DeployGroupRunner→deployment.actors.DeployGroupRunner.NextResult
- Direction
- deployment.actors uses deployment.actors.DeployGroupRunner, so a change to deployment.actors.DeployGroupRunner can break deployment.actors, while a change to deployment.actors can't break deployment.actors.DeployGroupRunner.
- Position
- Below the diagonal: deployment.actors uses a module listed above it, which is the healthy direction.
38→27 deployment.actors uses deployment✕
- Connections
- 1 pair of types, where a type in deployment.actors uses a type in deployment.
- The types involved
deployment.actors.DeployCoordinator→deployment.Record
- Direction
- deployment.actors uses deployment, so a change to deployment can break deployment.actors, while a change to deployment.actors can't break deployment.
- Position
- Below the diagonal: deployment.actors uses a module listed above it, which is the healthy direction.
38→34 deployment.actors uses controllers✕
- Connections
- 3 pairs of types, where a type in deployment.actors uses a type in controllers.
- The types involved
deployment.actors.DeployCoordinator→controllers.Loggingdeployment.actors.DeployGroupRunner→controllers.Loggingdeployment.actors.TasksRunner→controllers.Logging
- Direction
- deployment.actors uses controllers, so a change to controllers can break deployment.actors, while a change to deployment.actors can't break controllers.
- Position
- Below the diagonal: deployment.actors uses a module listed above it, which is the healthy direction.
39→15 resources uses magenta✕
- Connections
- 5 pairs of types, where a type in resources uses a type in magenta.
- The types involved
resources.PrismLookup→magenta.Appresources.PrismLookup→magenta.KeyRingresources.PrismLookup→magenta.Lookupresources.PrismLookup→magenta.Stackresources.PrismLookup→magenta.Stage
- Direction
- resources uses magenta, so a change to magenta can break resources, while a change to resources can't break magenta.
- Position
- Below the diagonal: resources uses a module listed above it, which is the healthy direction.
39→34 resources uses controllers✕
- Connections
- 1 pair of types, where a type in resources uses a type in controllers.
- The types involved
resources.PrismLookup→controllers.Logging
- Direction
- resources uses controllers, so a change to controllers can break resources, while a change to resources can't break controllers.
- Position
- Below the diagonal: resources uses a module listed above it, which is the healthy direction.
40→21 (global) uses lifecycle✕
- Connections
- 1 pair of types, where a type in (global) uses a type in lifecycle.
- The types involved
AppComponents→lifecycle.Lifecycle
- Direction
- (global) uses lifecycle, so a change to lifecycle can break (global), while a change to (global) can't break lifecycle.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
40→32 (global) uses persistence✕
- Connections
- 1 pair of types, where a type in (global) uses a type in persistence.
- The types involved
AppComponents→persistence.DataStore
- Direction
- (global) uses persistence, so a change to persistence can break (global), while a change to (global) can't break persistence.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
40→34 (global) uses controllers✕
- Connections
- 3 pairs of types, where a type in (global) uses a type in controllers.
- The types involved
AppComponents→controllers.LoggingAppLoader→controllers.ApplicationAppLoader→controllers.Logging
- Direction
- (global) uses controllers, so a change to controllers can break (global), while a change to (global) can't break controllers.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
40→35 (global) uses ci✕
- Connections
- 1 pair of types, where a type in (global) uses a type in ci.
- The types involved
AppLoader→ci.Context
- Direction
- (global) uses ci, so a change to ci can break (global), while a change to (global) can't break ci.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 17 | High / Critical |
| A07:2025 — Authentication Failures | 10 | High / Critical |
| A02:2025 — Security Misconfiguration | 3 | High / Critical |
Roadmap
Top priorities: Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3). | +3.8 pts | Low | REDACTED Scanning |
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +5.7 pts | Medium | Text alternatives |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +5.7 pts | Medium | Keyboard semantics |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.0 pts | Low | ADR Quality |
| 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. | +2.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.8 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.7 pts | Medium | Architecture documentation |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +1.5 pts | Medium | Nullable reference types |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| riff-raff/public/javascripts/rickshaw.js | 7.0 | Mixed | Cyclomatic Complexity: rickshaw.Rickshaw.Graph (cyclomatic 41) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| riff-raff/app/AppComponents.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| riff-raff/app/persistence/postgresdb.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| project/Helpers.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| magenta-lib/src/test/scala/magenta/tasks/ASGTasksTest.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| magenta-lib/src/test/scala/magenta/tasks/ASGTest.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| magenta-lib/src/main/scala/magenta/tasks/UpdateCloudFormationTask.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| magenta-lib/src/main/scala/magenta/deployment_type/AutoScaling.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| magenta-lib/src/main/scala/magenta/deployment_type/FastlyCompute.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 68 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 68 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, 143 of 155 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) 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 (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) 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 (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 53 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because repo1.maven.org — the registry that answers it — was asked and did not reply (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/adrianhurt/play-bootstrap_2.13/maven-metadata.xml). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add repo1.maven.org to the allowlist and re-run — not to build anything.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 45 commits in the last 90 days, yet 60 of 71 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.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 55 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 REDACTED (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
25 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was d3.v2.d3_voronoi_tessellate at 60. A further 3 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 d3.v2.d3.layout.force at 48 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: riff-raff/app/persistence/representation.scala (MessageDocument.formats at 23). 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 5 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with d3.v2.d3_voronoi_tessellate (cyclomatic 60), d3.v2.d3.svg.brush (cyclomatic 60), d3.v2.d3.layout.treemap (cyclomatic 45). — 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 5 together lifts Cyclomatic Complexity from 6.5 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- 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
31 method(s) exceeded the cognitive complexity threshold of 15; the worst was d3.v2.d3_voronoi_tessellate at 91.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with d3.v2.d3_voronoi_tessellate (cognitive 91). — Refactoring it lifts Cognitive Complexity from 6.1 to about 6.5/10.
- 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 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 3 FileTooLong finding(s) in God Classes — start with REDACTED, rickshaw.js, AWS.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with rickshaw.js (2). — One of this dimension's main actionable groups (2 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
1 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with FailureNotificationContents.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
3 production modules (sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 1 module(s) off the main sequence, with abstractness counted on 2 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
4 of 36 classes have LCOM4 above 3.
What to do
- Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with DeployController.scala, Testing.scala, api.scala. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
344 test methods: 344 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 344 test case(s) across 49 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D13 · REDACTED Scanning
3 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is magenta-lib/src/main/scala/magenta/tasks/UpdateCloudFormationTask.scala. Counted over 71 of the 148 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
8 deducted task-comment markers across 17956 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 8 TodoComment finding(s) in Explicit Debt — start with AppComponents.scala, postgresdb.scala, Helpers.scala. — One of this dimension's main actionable groups (8 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
18 finding(s): 0 critical, 10 high, 8 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 35 file(s) — `riff-raff/app/views/api/form.scala.html` (lines 1–5, lines 10–12, lines 17–18), `riff-raff/app/views/api/list.scala.html` (lines 1–5, line 26, lines 35–36, …), `riff-raff/app/views/artifact/listFiles.scala.html` (lines 1–5, line 22), `riff-raff/app/views/continuousDeployment/form.scala.html` (lines 1–6, lines 11–15, line 19, …), `riff-raff/app/views/continuousDeployment/list.scala.html` (lines 1–8, line 10, line 15, …), … (+30 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
3 finding(s): 0 critical, 2 high, 1 medium, 0 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×2) — riff-raff/app/views/deploy/dashboard.scala.html:9, riff-raff/app/views/preview/yaml/loading.scala.html:3
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — riff-raff/app/views/deploy/historyFilter.scala.html:31, riff-raff/app/views/validation/validationForm.scala.html:12
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — riff-raff/app/views/snippets/recordTable.scala.html:95
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×4) — riff-raff/app/views/artifact/listFiles.scala.html:12, riff-raff/app/views/auth/profile.scala.html:8, riff-raff/app/views/deploy/deployConfirmation.scala.html:20, …
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×4) — riff-raff/app/views/continuousDeployment/form.scala.html:17, riff-raff/app/views/continuousDeployment/list.scala.html:12, riff-raff/app/views/deploy/deployConfirmation.scala.html:10, …
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — riff-raff/app/views/page.scala.html:6
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — riff-raff/app/views/snippets/changeFreezeDialog.scala.html:6
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
- aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden. — riff-raff/app/views/snippets/changeFreezeDialog.scala.html:6
- aria-hidden="true" hides the element from assistive tech but leaves it keyboard-focusable — a confusing dead stop. Remove aria-hidden or make the element non-focusable. — riff-raff/app/views/snippets/changeFreezeDialog.scala.html:8
What to do
- Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
AC6 · Visual & motion safety
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 59 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.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×5) — magenta-lib/src/test/scala/magenta/tasks/ASGTasksTest.scala:36, magenta-lib/src/test/scala/magenta/tasks/ASGTest.scala:273, magenta-lib/src/test/scala/magenta/tasks/ASGTest.scala:296, …
- A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead. — riff-raff/app/utils/Retriable.scala:14
What to do
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
P3 · Security & performance tooling
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- Set: Strict-Transport-Security. Missing: Content-Security-Policy, X-Content-Type-Options, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−1.5 on this card.) The server: build.sbt:90 — the `PlayScala` plugin.
What to do
- Add Content-Security-Policy, X-Content-Type-Options, X-Frame-Options beside the headers the Scala server already sets.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `v==null?"":v` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:3692
- `value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:3696
- `box.content` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — riff-raff/public/javascripts/rickshaw.js:1145
- `o.unit.formatter(new Date(o.value*1000))` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — riff-raff/public/javascripts/rickshaw.js:1260
- `formattedXValue` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — riff-raff/public/javascripts/rickshaw.js:1884
- `this.formatter(point.series,point.value.x,point.value.y,formattedXValue,formattedYValue,point)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — riff-raff/public/javascripts/rickshaw.js:1890
- `series.name` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — riff-raff/public/javascripts/rickshaw.js:1992
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
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
- 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. — riff-raff/public/javascripts/rickshaw.js:185
- `case e: Exception` 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. — riff-raff/app/controllers/DeployController.scala:160
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `info` at line 35 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — riff-raff/app/deployment/preview/PreviewCoordinator.scala:35
- `info` at line 54 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — riff-raff/app/deployment/preview/PreviewCoordinator.scala:54
- `info` at line 77 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — riff-raff/app/controllers/PreviewController.scala:77
- `warn` at line 62 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — magenta-lib/src/main/scala/magenta/package.scala:62
- `info` at line 1083 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — magenta-lib/src/main/scala/magenta/tasks/AWS.scala:1083
- `info` at line 1120 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — magenta-lib/src/main/scala/magenta/tasks/AWS.scala:1120
- `info` at line 1123 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — magenta-lib/src/main/scala/magenta/tasks/AWS.scala:1123
- `warn` at line 1151 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — magenta-lib/src/main/scala/magenta/tasks/AWS.scala:1151
- `info` at line 409 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — magenta-lib/src/main/scala/magenta/tasks/UpdateCloudFormationTask.scala:409
- `debug` at line 458 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — magenta-lib/src/main/scala/magenta/tasks/UpdateCloudFormationTask.scala:458
- `debug` at line 117 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — REDACTED:117
- `debug` at line 168 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — REDACTED:168
- `warn` at line 30 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — magenta-lib/src/main/scala/magenta/tasks/autoscaling/CullSummary.scala:30
- `info` at line 203 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — magenta-lib/src/main/scala/magenta/deployment_type/CloudFormation.scala:203
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- No build over this repository's 144 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 52% | Adequate — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 85% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 58% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 48% | Weak — gated by D13 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 74% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 33% | Weak — gated by AC1, AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — a Slick table, a case class or a SQL migration's table named for it — Hibernate Envers' @Audited, a JPA entity listener, Hibernate event listener or jOOQ RecordListener that records each change, or an event-sourced journal beside one) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 46 check(s) not relevant to this codebase
- AX1 Captive dependencies — Not applicable: this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~8340 lines of test source are present (.scala) 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 .scala suite was found but not re-run
- D12 Dependency Hygiene — Dependency currency not established — repo1.maven.org did not answer
- D14 License Compliance — Not scored — this repository's 45 pinned sbt dependency coordinate(s) were read from its 4 sbt build file(s), but Maven Central could not be asked for the licence of 40 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/ch/qos/logback/logback-classic/1.6.3/logback-classic-1.6.3.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- 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 — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, Scala, html not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .scala source were not judged.
- 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 (.scala), 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.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- 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
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 153 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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 JVM, JavaScript/TypeScript 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 (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) 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 `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, 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: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Scala code has 19,878 production line(s), 5 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala was read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter
- 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.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 28 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <img> without a text alternative riff-raff/app/views/deploy/dashboard.scala.html:9
- <img> without a text alternative riff-raff/app/views/preview/yaml/loading.scala.html:3
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label riff-raff/app/views/deploy/historyFilter.scala.html:31
- <button> with no accessible text riff-raff/app/views/snippets/recordTable.scala.html:95
- <textarea> without a programmatic label riff-raff/app/views/validation/validationForm.scala.html:12
- aria-hidden hides a focusable element riff-raff/app/views/snippets/changeFreezeDialog.scala.html:6
- aria-hidden on a focusable element riff-raff/app/views/snippets/changeFreezeDialog.scala.html:8
- REDACTED
- REDACTED
Serious — 97 finding(s)
- TodoComment riff-raff/app/AppComponents.scala:253
- TodoComment riff-raff/app/persistence/postgresdb.scala:271
- TodoComment project/Helpers.scala:3
- TodoComment magenta-lib/src/test/scala/magenta/tasks/ASGTasksTest.scala:32
- TodoComment magenta-lib/src/test/scala/magenta/tasks/ASGTest.scala:269
- TodoComment magenta-lib/src/main/scala/magenta/tasks/UpdateCloudFormationTask.scala:171
- TodoComment magenta-lib/src/main/scala/magenta/deployment_type/AutoScaling.scala:250
- TodoComment magenta-lib/src/main/scala/magenta/deployment_type/FastlyCompute.scala:32
- Untrusted text written into markup unescaped REDACTED:3692
- Untrusted text written into markup unescaped REDACTED:3696
- Untrusted text written into markup unescaped riff-raff/public/javascripts/rickshaw.js:1145
- Untrusted text written into markup unescaped riff-raff/public/javascripts/rickshaw.js:1260
- Untrusted text written into markup unescaped riff-raff/public/javascripts/rickshaw.js:1884
- Untrusted text written into markup unescaped riff-raff/public/javascripts/rickshaw.js:1890
- Untrusted text written into markup unescaped riff-raff/public/javascripts/rickshaw.js:1992
- Data table has no header cells riff-raff/app/views/artifact/listFiles.scala.html:12
- Data table has no header cells riff-raff/app/views/auth/profile.scala.html:8
- Data table has no header cells riff-raff/app/views/deploy/deployConfirmation.scala.html:20
- Data table has no header cells riff-raff/app/views/snippets/pimpedBuildId.scala.html:5
- Heading level jumps from h2 to h4 riff-raff/app/views/continuousDeployment/form.scala.html:17
- Heading level jumps from h2 to h4 riff-raff/app/views/continuousDeployment/list.scala.html:12
- Heading level jumps from h2 to h4 riff-raff/app/views/deploy/deployConfirmation.scala.html:10
- Heading level jumps from h2 to h4 riff-raff/app/views/schedule/form.scala.html:16
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Low cohesion: DeployController (LCOM4 15) riff-raff/app/controllers/DeployController.scala:36
- Low cohesion: Testing (LCOM4 8) riff-raff/app/controllers/Testing.scala:47
- Low cohesion: Api (LCOM4 8) riff-raff/app/controllers/api.scala:71
- Low cohesion: Application (LCOM4 4) riff-raff/app/controllers/Application.scala:107
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: REDACTED REDACTED
- FileTooLong: javascripts/rickshaw.js riff-raff/public/javascripts/rickshaw.js
- FileTooLong: tasks/AWS.scala magenta-lib/src/main/scala/magenta/tasks/AWS.scala
- FunctionTooLong: rickshaw.Rickshaw.Graph riff-raff/public/javascripts/rickshaw.js:382
- FunctionTooLong: rickshaw.Rickshaw.Fixtures.Color riff-raff/public/javascripts/rickshaw.js:637
- Page without a main landmark riff-raff/app/views/page.scala.html:6
- Modal dialog does not manage focus riff-raff/app/views/snippets/changeFreezeDialog.scala.html:6
- Accessibility enforcement below the top rung
- d3.v2.d3_voronoi_tessellate (cyclomatic 60) REDACTED:2032
- d3.v2.d3.svg.brush (cyclomatic 60) REDACTED:4506
- d3.v2.d3.layout.treemap (cyclomatic 45) REDACTED:5737
- rickshaw.Rickshaw.Graph (cyclomatic 41) riff-raff/public/javascripts/rickshaw.js:382
- d3.v2.d3.geo.circle (cyclomatic 28) REDACTED:6254
- d3.v2.d3.geo.path (cyclomatic 23) REDACTED:6080
- d3.v2.d3.layout.chord (cyclomatic 22) REDACTED:4928
- rickshaw.Rickshaw.Graph.Axis.X (cyclomatic 22) riff-raff/public/javascripts/rickshaw.js:1274
- d3.v2.d3.layout.tree (cyclomatic 21) REDACTED:5636
- rickshaw.Rickshaw.Compat.ClassList (cyclomatic 21) riff-raff/public/javascripts/rickshaw.js:247
- rickshaw.Rickshaw.Graph.Axis.Y (cyclomatic 20) riff-raff/public/javascripts/rickshaw.js:1385
- d3.v2.d3.layout.hierarchy (cyclomatic 19) REDACTED:5504
- d3.v2.d3.geom.quadtree (cyclomatic 19) REDACTED:6601
- update (cyclomatic 19) riff-raff/public/javascripts/rickshaw.js:1759
- d3.v2.d3_selectionPrototype.data (cyclomatic 18) REDACTED:3725
- d3.v2.d3.interpolateString (cyclomatic 17) REDACTED:3169
- d3.v2.d3.behavior.zoom (cyclomatic 17) REDACTED:4793
- d3.v2.d3.geom.hull (cyclomatic 17) REDACTED:6422
- d3.v2.d3_layout_packSiblings (cyclomatic 16) REDACTED:1620
- d3.v2.d3.extent (cyclomatic 16) REDACTED:2690
- d3.v2.d3.geo.azimuthal (cyclomatic 16) REDACTED:5883
- d3.v2.d3_voronoi_tessellate (cognitive 91) REDACTED:2032
- d3.v2.d3.svg.brush (cognitive 48) REDACTED:4506
- d3.v2.d3.layout.treemap (cognitive 48) REDACTED:5737
- d3.v2.d3_layout_packSiblings (cognitive 46) REDACTED:1620
- d3.v2.d3.interpolateString (cognitive 45) REDACTED:3169
- d3.v2.d3.geom.quadtree (cognitive 45) REDACTED:6601
- Graph (cognitive 40) riff-raff/public/javascripts/rickshaw.js:382
- ClassList (cognitive 37) riff-raff/public/javascripts/rickshaw.js:247
- d3.v2.d3.extent (cognitive 36) REDACTED:2690
- d3.v2.d3_selectionPrototype.classed (cognitive 31) REDACTED:3640
- d3.v2.d3_selectionPrototype.data::bind (cognitive 29) REDACTED:3726
- d3.v2.d3.layout.tree (cognitive 28) REDACTED:5636
- d3.v2.d3.geo.circle (cognitive 28) REDACTED:6254
- d3.v2.d3.geo.path (cognitive 26) REDACTED:6080
- d3.v2.d3.geom.hull (cognitive 25) REDACTED:6422
- d3.v2.d3.min (cognitive 22) REDACTED:2668
- d3.v2.d3.max (cognitive 22) REDACTED:2679
- X (cognitive 22) riff-raff/public/javascripts/rickshaw.js:1274
- update (cognitive 22) riff-raff/public/javascripts/rickshaw.js:1759
- d3.v2.d3.layout.chord::relayout (cognitive 20) REDACTED:4929
- Toggle (cognitive 20) riff-raff/public/javascripts/rickshaw.js:1602
- Y (cognitive 19) riff-raff/public/javascripts/rickshaw.js:1385
- d3.v2.d3.layout.hierarchy (cognitive 18) REDACTED:5504
- d3.v2.d3.geom.contour (cognitive 18) REDACTED:6393
- d3.v2.d3.format.<returned closure> (cognitive 16) REDACTED:3040
- d3.v2.d3.interpolateTransform (cognitive 16) REDACTED:3231
- Annotate (cognitive 16) riff-raff/public/javascripts/rickshaw.js:1084
- configure (cognitive 16) riff-raff/public/javascripts/rickshaw.js:2195
- initialize (cognitive 16) riff-raff/public/javascripts/rickshaw.js:2823
- REDACTED
- Duplicated block (11 lines × 2) riff-raff/app/notification/FailureNotificationContents.scala:66
- Off the main sequence: lib
- Swallowed exception (empty catch) riff-raff/public/javascripts/rickshaw.js:185
- Swallowed exception (caught, then discarded) riff-raff/app/controllers/DeployController.scala:160
Minor — 30 finding(s)
- Interpolated log message defeats structured logging riff-raff/app/deployment/preview/PreviewCoordinator.scala:35
- Interpolated log message defeats structured logging riff-raff/app/deployment/preview/PreviewCoordinator.scala:54
- Interpolated log message defeats structured logging riff-raff/app/controllers/PreviewController.scala:77
- Interpolated log message defeats structured logging magenta-lib/src/main/scala/magenta/package.scala:62
- Interpolated log message defeats structured logging magenta-lib/src/main/scala/magenta/tasks/AWS.scala:1083
- Interpolated log message defeats structured logging magenta-lib/src/main/scala/magenta/tasks/AWS.scala:1120
- Interpolated log message defeats structured logging magenta-lib/src/main/scala/magenta/tasks/AWS.scala:1123
- Interpolated log message defeats structured logging magenta-lib/src/main/scala/magenta/tasks/AWS.scala:1151
- Interpolated log message defeats structured logging magenta-lib/src/main/scala/magenta/tasks/UpdateCloudFormationTask.scala:409
- Interpolated log message defeats structured logging magenta-lib/src/main/scala/magenta/tasks/UpdateCloudFormationTask.scala:458
- Interpolated log message defeats structured logging REDACTED:117
- Interpolated log message defeats structured logging REDACTED:168
- Interpolated log message defeats structured logging magenta-lib/src/main/scala/magenta/tasks/autoscaling/CullSummary.scala:30
- Interpolated log message defeats structured logging magenta-lib/src/main/scala/magenta/deployment_type/CloudFormation.scala:203
- Disabled test magenta-lib/src/test/scala/magenta/tasks/ASGTasksTest.scala:36
- Disabled test magenta-lib/src/test/scala/magenta/tasks/ASGTest.scala:273
- Disabled test magenta-lib/src/test/scala/magenta/tasks/ASGTest.scala:296
- Disabled test magenta-lib/src/test/scala/magenta/tasks/ASGTest.scala:319
- Disabled test magenta-lib/src/test/scala/magenta/tasks/ASGTest.scala:352
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Blanket warning suppression riff-raff/app/utils/Retriable.scala:14
- No ADRs
- No architecture diagram/doc
- No changelog
- Security headers incomplete
- Scala's null is not held to the type system 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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-7ff5396968404fb29e68135670c651af/history.json --exit-code 0 --source . | 6 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-7ff5396968404fb29e68135670c651af/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 18 | 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 . /tmp/codehealth-osv-sbom-b5dc5e75e126491d85e06c59f2652b54 | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 3 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| 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 . /tmp/codehealth-osv-sbom-b5dc5e75e126491d85e06c59f2652b54 | 0 | artifacts/raw/osv-scanner.json |