Executive summary
VirtusLab/besom is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back in part because three of the dependencies have a known vulnerability. It scores 55 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Security and Compliance, at 49, is the weakest lens and counts most in the score. The best first step is serving traffic only over an encrypted connection, worth about 6 points. Fixing the password or key in the code comes next, worth about 3 points. Raising Security and Compliance to 68 would lift the score to about 60.
Thirty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five known security holes in the packages the code depends on can be used by attackers, and four passwords or keys in the code's history and one in the code are open to anyone who can read the repository. Replacing each exposed password or key, pinning each tool to an exact version and updating the vulnerable packages would close these risks. Correcting the flagged pipeline settings would fix the three weaknesses in the build pipeline's configuration, and limiting each secret to its own step would deal with the secret exposed to more of the pipeline than needed.
The product code is 29,068 lines, about €43,000 to rebuild.
If Security and Compliance rose from 49 to 68, the lowest score rated Strong, the score would rise from 55 to about 60.
Rebuild cost: about €43,000 · Estimate
| Cost to rebuild | €14,000 to €73,000, for 241 to 764 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 55. 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 | Medium: 29,068 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 besom.cfg | 2 besom.json | 3 besom.model | 4 besom.types | 5 besom.util.Validated | 6 pulumirpc.alias.Alias | 7 pulumirpc.callback | 8 pulumirpc.codegen.hcl | 9 pulumirpc.engine | 10 pulumirpc.language.RuntimeOptionPrompt | 11 pulumirpc.plugin | 12 pulumirpc.provider.PropertyDiff | 13 pulumirpc.source | 14 besom.codegen | 15 besom.internal.logging | 16 besom.util | 17 pulumirpc.alias | 18 pulumirpc.language | 19 pulumirpc.provider.CallResponse | 20 pulumirpc.provider.DiffResponse | 21 pulumirpc.resource.RegisterResourceResponse | 22 pulumirpc.resource.ResourceCallRequest | 23 besom.auto.internal | 24 pulumirpc.language.LanguageRuntimeGrpc | 25 pulumirpc.provider | 26 pulumirpc.resource.RegisterResourceRequest | 27 besom.auto.internal.EngineEvent | 28 besom.auto.internal.GitAuth | 29 besom.auto.internal.LocalWorkspace | 30 besom.auto.internal.LoginOption | 31 besom.auto.internal.LogoutOption | 32 besom.auto.internal.OpType | 33 besom.auto.internal.SummaryEvent | 34 besom.auto.internal.shell | 35 pulumirpc.resource | 36 besom.auto.internal.shell.ShellOption | 37 pulumirpc.resource.ResourceMonitorGrpc | 38 besom.internal | 39 besom.aliases | 40 besom.internal.ResourceDecoder |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 besom.cfg | ||||||||||||||||||||||||||||||||||||||||
| 2 besom.json | ||||||||||||||||||||||||||||||||||||||||
| 3 besom.model | ||||||||||||||||||||||||||||||||||||||||
| 4 besom.types | ||||||||||||||||||||||||||||||||||||||||
| 5 besom.util.Validated | ||||||||||||||||||||||||||||||||||||||||
| 6 pulumirpc.alias.Alias | ||||||||||||||||||||||||||||||||||||||||
| 7 pulumirpc.callback | ||||||||||||||||||||||||||||||||||||||||
| 8 pulumirpc.codegen.hcl | ||||||||||||||||||||||||||||||||||||||||
| 9 pulumirpc.engine | ||||||||||||||||||||||||||||||||||||||||
| 10 pulumirpc.language.RuntimeOptionPrompt | ||||||||||||||||||||||||||||||||||||||||
| 11 pulumirpc.plugin | ||||||||||||||||||||||||||||||||||||||||
| 12 pulumirpc.provider.PropertyDiff | ||||||||||||||||||||||||||||||||||||||||
| 13 pulumirpc.source | ||||||||||||||||||||||||||||||||||||||||
| 14 besom.codegen | 6 | |||||||||||||||||||||||||||||||||||||||
| 15 besom.internal.logging | 3 | 9 | ||||||||||||||||||||||||||||||||||||||
| 16 besom.util | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 17 pulumirpc.alias | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 pulumirpc.language | 3 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 19 pulumirpc.provider.CallResponse | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 pulumirpc.provider.DiffResponse | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 pulumirpc.resource.RegisterResourceResponse | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 pulumirpc.resource.ResourceCallRequest | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 besom.auto.internal | 6 | 12 | ||||||||||||||||||||||||||||||||||||||
| 24 pulumirpc.language.LanguageRuntimeGrpc | 4 | 88 | ||||||||||||||||||||||||||||||||||||||
| 25 pulumirpc.provider | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 pulumirpc.resource.RegisterResourceRequest | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 besom.auto.internal.EngineEvent | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 besom.auto.internal.GitAuth | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 29 besom.auto.internal.LocalWorkspace | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 30 besom.auto.internal.LoginOption | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 31 besom.auto.internal.LogoutOption | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 32 besom.auto.internal.OpType | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 besom.auto.internal.SummaryEvent | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 besom.auto.internal.shell | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 35 pulumirpc.resource | 2 | 4 | 2 | 1 | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||
| 36 besom.auto.internal.shell.ShellOption | 1 | 10 | ||||||||||||||||||||||||||||||||||||||
| 37 pulumirpc.resource.ResourceMonitorGrpc | 4 | 8 | 44 | |||||||||||||||||||||||||||||||||||||
| 38 besom.internal | 4 | 56 | 2 | 2 | 11 | 1 | 3 | 24 | 22 | 1 | 4 | 18 | 1 | |||||||||||||||||||||||||||
| 39 besom.aliases | 1 | 10 | ||||||||||||||||||||||||||||||||||||||
| 40 besom.internal.ResourceDecoder | 1 | 1 | 1 | 4 |
14→3 besom.codegen uses besom.model✕
- Connections
- 6 pairs of types, where a type in besom.codegen uses a type in besom.model.
- The types involved
besom.codegen.ExactRange→besom.model.SemanticVersionbesom.codegen.FromVersion→besom.model.SemanticVersionbesom.codegen.Hotfix→besom.model.SemanticVersionbesom.codegen.SingleVersion→besom.model.SemanticVersionbesom.codegen.VersionRange→besom.model.SemanticVersionbesom.codegen.WildcardVersion→besom.model.SemanticVersion
- Direction
- besom.codegen uses besom.model, so a change to besom.model can break besom.codegen, while a change to besom.codegen can't break besom.model.
- Position
- Below the diagonal: besom.codegen uses a module listed above it, which is the healthy direction.
15→4 besom.internal.logging uses besom.types✕
- Connections
- 3 pairs of types, where a type in besom.internal.logging uses a type in besom.types.
- The types involved
besom.internal.logging.BesomLogger→besom.types.URNbesom.internal.logging.DualBesomLogger→besom.types.URNbesom.internal.logging.LocalBesomLogger→besom.types.URN
- Direction
- besom.internal.logging uses besom.types, so a change to besom.types can break besom.internal.logging, while a change to besom.internal.logging can't break besom.types.
- Position
- Below the diagonal: besom.internal.logging uses a module listed above it, which is the healthy direction.
15→38 besom.internal.logging uses besom.internal part of a loop✕
- Connections
- 9 pairs of types, where a type in besom.internal.logging uses a type in besom.internal.
- The types involved
besom.internal.logging.BesomLogger→besom.internal.Contextbesom.internal.logging.BesomLogger→besom.internal.Resourcebesom.internal.logging.BesomLogger→besom.internal.Resultbesom.internal.logging.DualBesomLogger→besom.internal.Fiberbesom.internal.logging.DualBesomLogger→besom.internal.Queuebesom.internal.logging.DualBesomLogger→besom.internal.Resultbesom.internal.logging.LocalBesomLogger→besom.internal.Resultbesom.internal.logging.UserLoggerFactory→besom.internal.Outputbesom.internal.logging.UserLoggerFactory→besom.internal.Resource
- Direction
- besom.internal.logging uses besom.internal, so a change to besom.internal can break besom.internal.logging, while a change to besom.internal.logging can't break besom.internal.
- 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.
16→2 besom.util uses besom.json✕
- Connections
- 2 pairs of types, where a type in besom.util uses a type in besom.json.
- The types involved
besom.util.JsonInterpolator→besom.json.JsValuebesom.util.JsonReaderInstances→besom.json.JsonReader
- Direction
- besom.util uses besom.json, so a change to besom.json can break besom.util, while a change to besom.util can't break besom.json.
- Position
- Below the diagonal: besom.util uses a module listed above it, which is the healthy direction.
16→38 besom.util uses besom.internal part of a loop✕
- Connections
- 3 pairs of types, where a type in besom.util uses a type in besom.internal.
- The types involved
besom.util.JsonInterpolator→besom.internal.Outputbesom.util.JsonReaderInstances→besom.internal.Outputbesom.util.Validated→besom.internal.Zippable
- Direction
- besom.util uses besom.internal, so a change to besom.internal can break besom.util, while a change to besom.util can't break besom.internal.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→6 pulumirpc.alias uses pulumirpc.alias.Alias✕
- Connections
- 1 pair of types, where a type in pulumirpc.alias uses a type in pulumirpc.alias.Alias.
- The types involved
pulumirpc.alias.Alias→pulumirpc.alias.Alias.Spec
- Direction
- pulumirpc.alias uses pulumirpc.alias.Alias, so a change to pulumirpc.alias.Alias can break pulumirpc.alias, while a change to pulumirpc.alias can't break pulumirpc.alias.Alias.
- Position
- Below the diagonal: pulumirpc.alias uses a module listed above it, which is the healthy direction.
18→8 pulumirpc.language uses pulumirpc.codegen.hcl✕
- Connections
- 3 pairs of types, where a type in pulumirpc.language uses a type in pulumirpc.codegen.hcl.
- The types involved
pulumirpc.language.GeneratePackageResponse→pulumirpc.codegen.hcl.Diagnosticpulumirpc.language.GenerateProgramResponse→pulumirpc.codegen.hcl.Diagnosticpulumirpc.language.GenerateProjectResponse→pulumirpc.codegen.hcl.Diagnostic
- Direction
- pulumirpc.language uses pulumirpc.codegen.hcl, so a change to pulumirpc.codegen.hcl can break pulumirpc.language, while a change to pulumirpc.language can't break pulumirpc.codegen.hcl.
- Position
- Below the diagonal: pulumirpc.language uses a module listed above it, which is the healthy direction.
18→10 pulumirpc.language uses pulumirpc.language.RuntimeOptionPrompt✕
- Connections
- 2 pairs of types, where a type in pulumirpc.language uses a type in pulumirpc.language.RuntimeOptionPrompt.
- The types involved
pulumirpc.language.RuntimeOptionPrompt→pulumirpc.language.RuntimeOptionPrompt.RuntimeOptionTypepulumirpc.language.RuntimeOptionPrompt→pulumirpc.language.RuntimeOptionPrompt.RuntimeOptionValue
- Direction
- pulumirpc.language uses pulumirpc.language.RuntimeOptionPrompt, so a change to pulumirpc.language.RuntimeOptionPrompt can break pulumirpc.language, while a change to pulumirpc.language can't break pulumirpc.language.RuntimeOptionPrompt.
- Position
- Below the diagonal: pulumirpc.language uses a module listed above it, which is the healthy direction.
18→11 pulumirpc.language uses pulumirpc.plugin✕
- Connections
- 2 pairs of types, where a type in pulumirpc.language uses a type in pulumirpc.plugin.
- The types involved
pulumirpc.language.GetRequiredPluginsResponse→pulumirpc.plugin.PluginDependencypulumirpc.language.LanguageRuntimeGrpc→pulumirpc.plugin.PluginInfo
- Direction
- pulumirpc.language uses pulumirpc.plugin, so a change to pulumirpc.plugin can break pulumirpc.language, while a change to pulumirpc.language can't break pulumirpc.plugin.
- Position
- Below the diagonal: pulumirpc.language uses a module listed above it, which is the healthy direction.
19→25 pulumirpc.provider.CallResponse uses pulumirpc.provider part of a loop✕
- Connections
- 1 pair of types, where a type in pulumirpc.provider.CallResponse uses a type in pulumirpc.provider.
- The types involved
pulumirpc.provider.CallResponse.CallResponseLens→pulumirpc.provider.CheckFailure
- Direction
- pulumirpc.provider.CallResponse uses pulumirpc.provider, so a change to pulumirpc.provider can break pulumirpc.provider.CallResponse, while a change to pulumirpc.provider.CallResponse can't break pulumirpc.provider.
- 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.
20→25 pulumirpc.provider.DiffResponse uses pulumirpc.provider part of a loop✕
- Connections
- 2 pairs of types, where a type in pulumirpc.provider.DiffResponse uses a type in pulumirpc.provider.
- The types involved
pulumirpc.provider.DiffResponse.DetailedDiffEntry→pulumirpc.provider.PropertyDiffpulumirpc.provider.DiffResponse.DiffResponseLens→pulumirpc.provider.PropertyDiff
- Direction
- pulumirpc.provider.DiffResponse uses pulumirpc.provider, so a change to pulumirpc.provider can break pulumirpc.provider.DiffResponse, while a change to pulumirpc.provider.DiffResponse can't break pulumirpc.provider.
- 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→35 pulumirpc.resource.RegisterResourceResponse uses pulumirpc.resource part of a loop✕
- Connections
- 1 pair of types, where a type in pulumirpc.resource.RegisterResourceResponse uses a type in pulumirpc.resource.
- The types involved
pulumirpc.resource.RegisterResourceResponse.RegisterResourceResponseLens→pulumirpc.resource.Result
- Direction
- pulumirpc.resource.RegisterResourceResponse uses pulumirpc.resource, so a change to pulumirpc.resource can break pulumirpc.resource.RegisterResourceResponse, while a change to pulumirpc.resource.RegisterResourceResponse can't break pulumirpc.resource.
- 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→13 pulumirpc.resource.ResourceCallRequest uses pulumirpc.source✕
- Connections
- 1 pair of types, where a type in pulumirpc.resource.ResourceCallRequest uses a type in pulumirpc.source.
- The types involved
pulumirpc.resource.ResourceCallRequest.ResourceCallRequestLens→pulumirpc.source.SourcePosition
- Direction
- pulumirpc.resource.ResourceCallRequest uses pulumirpc.source, so a change to pulumirpc.source can break pulumirpc.resource.ResourceCallRequest, while a change to pulumirpc.resource.ResourceCallRequest can't break pulumirpc.source.
- Position
- Below the diagonal: pulumirpc.resource.ResourceCallRequest uses a module listed above it, which is the healthy direction.
23→2 besom.auto.internal uses besom.json✕
- Connections
- 6 pairs of types, where a type in besom.auto.internal uses a type in besom.json.
- The types involved
besom.auto.internal.ConfigValue→besom.json.JsValuebesom.auto.internal.OutputMap→besom.json.JsValuebesom.auto.internal.PolicyRemediationEvent→besom.json.JsValuebesom.auto.internal.StartDebuggingEvent→besom.json.JsValuebesom.auto.internal.StepEventStateMetadata→besom.json.JsValuebesom.auto.internal.UntypedDeployment→besom.json.JsValue
- Direction
- besom.auto.internal uses besom.json, so a change to besom.json can break besom.auto.internal, while a change to besom.auto.internal can't break besom.json.
- Position
- Below the diagonal: besom.auto.internal uses a module listed above it, which is the healthy direction.
23→16 besom.auto.internal uses besom.util✕
- Connections
- 12 pairs of types, where a type in besom.auto.internal uses a type in besom.util.
- The types involved
besom.auto.internal.DestroyOptions→besom.util.NotProvidedOrbesom.auto.internal.GitRepo→besom.util.NotProvidedOrbesom.auto.internal.LocalWorkspace→besom.util.NotProvidedOrbesom.auto.internal.LocalWorkspaceOptions→besom.util.NotProvidedOrbesom.auto.internal.LoggingOptions→besom.util.NotProvidedOrbesom.auto.internal.LoginOptions→besom.util.NotProvidedOrbesom.auto.internal.LogoutOptions→besom.util.NotProvidedOrbesom.auto.internal.PreviewOptions→besom.util.NotProvidedOrbesom.auto.internal.RefreshOptions→besom.util.NotProvidedOrbesom.auto.internal.Stack→besom.util.NotProvidedOrbesom.auto.internal.UpOptions→besom.util.NotProvidedOrbesom.auto.internal.Workspace→besom.util.NotProvidedOr
- Direction
- besom.auto.internal uses besom.util, so a change to besom.util can break besom.auto.internal, while a change to besom.auto.internal can't break besom.util.
- Position
- Below the diagonal: besom.auto.internal uses a module listed above it, which is the healthy direction.
24→11 pulumirpc.language.LanguageRuntimeGrpc uses pulumirpc.plugin✕
- Connections
- 4 pairs of types, where a type in pulumirpc.language.LanguageRuntimeGrpc uses a type in pulumirpc.plugin.
- The types involved
pulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.plugin.PluginInfopulumirpc.language.LanguageRuntimeGrpc.LanguageRuntimeBlockingClient→pulumirpc.plugin.PluginInfopulumirpc.language.LanguageRuntimeGrpc.LanguageRuntimeBlockingStub→pulumirpc.plugin.PluginInfopulumirpc.language.LanguageRuntimeGrpc.LanguageRuntimeStub→pulumirpc.plugin.PluginInfo
- Direction
- pulumirpc.language.LanguageRuntimeGrpc uses pulumirpc.plugin, so a change to pulumirpc.plugin can break pulumirpc.language.LanguageRuntimeGrpc, while a change to pulumirpc.language.LanguageRuntimeGrpc can't break pulumirpc.plugin.
- Position
- Below the diagonal: pulumirpc.language.LanguageRuntimeGrpc uses a module listed above it, which is the healthy direction.
24→18 pulumirpc.language.LanguageRuntimeGrpc uses pulumirpc.language✕
- Connections
- 88 pairs of types, where a type in pulumirpc.language.LanguageRuntimeGrpc uses a type in pulumirpc.language. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
pulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.AboutRequestpulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.AboutResponsepulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.GeneratePackageRequestpulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.GeneratePackageResponsepulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.GenerateProgramRequestpulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.GenerateProgramResponsepulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.GenerateProjectRequestpulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.GenerateProjectResponsepulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.GetProgramDependenciesRequestpulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.GetProgramDependenciesResponsepulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.GetRequiredPluginsRequestpulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.GetRequiredPluginsResponsepulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.InstallDependenciesRequestpulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.InstallDependenciesResponsepulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.PackRequestpulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.PackResponsepulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.RunPluginRequestpulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.RunPluginResponsepulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.RunRequestpulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.RunResponsepulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.RuntimeOptionsRequestpulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime→pulumirpc.language.RuntimeOptionsResponsepulumirpc.language.LanguageRuntimeGrpc.LanguageRuntimeBlockingClient→pulumirpc.language.AboutRequestpulumirpc.language.LanguageRuntimeGrpc.LanguageRuntimeBlockingClient→pulumirpc.language.AboutResponsepulumirpc.language.LanguageRuntimeGrpc.LanguageRuntimeBlockingClient→pulumirpc.language.GeneratePackageRequest
- Direction
- pulumirpc.language.LanguageRuntimeGrpc uses pulumirpc.language, so a change to pulumirpc.language can break pulumirpc.language.LanguageRuntimeGrpc, while a change to pulumirpc.language.LanguageRuntimeGrpc can't break pulumirpc.language.
- Position
- Below the diagonal: pulumirpc.language.LanguageRuntimeGrpc uses a module listed above it, which is the healthy direction.
25→11 pulumirpc.provider uses pulumirpc.plugin✕
- Connections
- 2 pairs of types, where a type in pulumirpc.provider uses a type in pulumirpc.plugin.
- The types involved
pulumirpc.provider.ResourceProviderGrpc→pulumirpc.plugin.PluginAttachpulumirpc.provider.ResourceProviderGrpc→pulumirpc.plugin.PluginInfo
- Direction
- pulumirpc.provider uses pulumirpc.plugin, so a change to pulumirpc.plugin can break pulumirpc.provider, while a change to pulumirpc.provider can't break pulumirpc.plugin.
- Position
- Below the diagonal: pulumirpc.provider uses a module listed above it, which is the healthy direction.
25→12 pulumirpc.provider uses pulumirpc.provider.PropertyDiff✕
- Connections
- 1 pair of types, where a type in pulumirpc.provider uses a type in pulumirpc.provider.PropertyDiff.
- The types involved
pulumirpc.provider.PropertyDiff→pulumirpc.provider.PropertyDiff.Kind
- Direction
- pulumirpc.provider uses pulumirpc.provider.PropertyDiff, so a change to pulumirpc.provider.PropertyDiff can break pulumirpc.provider, while a change to pulumirpc.provider can't break pulumirpc.provider.PropertyDiff.
- Position
- Below the diagonal: pulumirpc.provider uses a module listed above it, which is the healthy direction.
25→19 pulumirpc.provider uses pulumirpc.provider.CallResponse✕
- Connections
- 1 pair of types, where a type in pulumirpc.provider uses a type in pulumirpc.provider.CallResponse.
- The types involved
pulumirpc.provider.CallResponse→pulumirpc.provider.CallResponse.ReturnDependencies
- Direction
- pulumirpc.provider uses pulumirpc.provider.CallResponse, so a change to pulumirpc.provider.CallResponse can break pulumirpc.provider, while a change to pulumirpc.provider can't break pulumirpc.provider.CallResponse.
- Position
- Below the diagonal: pulumirpc.provider uses a module listed above it, which is the healthy direction.
25→20 pulumirpc.provider uses pulumirpc.provider.DiffResponse✕
- Connections
- 1 pair of types, where a type in pulumirpc.provider uses a type in pulumirpc.provider.DiffResponse.
- The types involved
pulumirpc.provider.DiffResponse→pulumirpc.provider.DiffResponse.DiffChanges
- Direction
- pulumirpc.provider uses pulumirpc.provider.DiffResponse, so a change to pulumirpc.provider.DiffResponse can break pulumirpc.provider, while a change to pulumirpc.provider can't break pulumirpc.provider.DiffResponse.
- Position
- Below the diagonal: pulumirpc.provider uses a module listed above it, which is the healthy direction.
26→7 pulumirpc.resource.RegisterResourceRequest uses pulumirpc.callback✕
- Connections
- 1 pair of types, where a type in pulumirpc.resource.RegisterResourceRequest uses a type in pulumirpc.callback.
- The types involved
pulumirpc.resource.RegisterResourceRequest.RegisterResourceRequestLens→pulumirpc.callback.Callback
- Direction
- pulumirpc.resource.RegisterResourceRequest uses pulumirpc.callback, so a change to pulumirpc.callback can break pulumirpc.resource.RegisterResourceRequest, while a change to pulumirpc.resource.RegisterResourceRequest can't break pulumirpc.callback.
- Position
- Below the diagonal: pulumirpc.resource.RegisterResourceRequest uses a module listed above it, which is the healthy direction.
26→13 pulumirpc.resource.RegisterResourceRequest uses pulumirpc.source✕
- Connections
- 1 pair of types, where a type in pulumirpc.resource.RegisterResourceRequest uses a type in pulumirpc.source.
- The types involved
pulumirpc.resource.RegisterResourceRequest.RegisterResourceRequestLens→pulumirpc.source.SourcePosition
- Direction
- pulumirpc.resource.RegisterResourceRequest uses pulumirpc.source, so a change to pulumirpc.source can break pulumirpc.resource.RegisterResourceRequest, while a change to pulumirpc.resource.RegisterResourceRequest can't break pulumirpc.source.
- Position
- Below the diagonal: pulumirpc.resource.RegisterResourceRequest uses a module listed above it, which is the healthy direction.
26→17 pulumirpc.resource.RegisterResourceRequest uses pulumirpc.alias✕
- Connections
- 1 pair of types, where a type in pulumirpc.resource.RegisterResourceRequest uses a type in pulumirpc.alias.
- The types involved
pulumirpc.resource.RegisterResourceRequest.RegisterResourceRequestLens→pulumirpc.alias.Alias
- Direction
- pulumirpc.resource.RegisterResourceRequest uses pulumirpc.alias, so a change to pulumirpc.alias can break pulumirpc.resource.RegisterResourceRequest, while a change to pulumirpc.resource.RegisterResourceRequest can't break pulumirpc.alias.
- Position
- Below the diagonal: pulumirpc.resource.RegisterResourceRequest uses a module listed above it, which is the healthy direction.
27→2 besom.auto.internal.EngineEvent uses besom.json✕
- Connections
- 3 pairs of types, where a type in besom.auto.internal.EngineEvent uses a type in besom.json.
- The types involved
besom.auto.internal.EngineEvent.EngineEventFormat→besom.json.JsObjectbesom.auto.internal.EngineEvent.EngineEventFormat→besom.json.JsValuebesom.auto.internal.EngineEvent.EngineEventFormat→besom.json.RootJsonFormat
- Direction
- besom.auto.internal.EngineEvent uses besom.json, so a change to besom.json can break besom.auto.internal.EngineEvent, while a change to besom.auto.internal.EngineEvent can't break besom.json.
- Position
- Below the diagonal: besom.auto.internal.EngineEvent uses a module listed above it, which is the healthy direction.
27→23 besom.auto.internal.EngineEvent uses besom.auto.internal✕
- Connections
- 1 pair of types, where a type in besom.auto.internal.EngineEvent uses a type in besom.auto.internal.
- The types involved
besom.auto.internal.EngineEvent.EngineEventFormat→besom.auto.internal.EngineEvent
- Direction
- besom.auto.internal.EngineEvent uses besom.auto.internal, so a change to besom.auto.internal can break besom.auto.internal.EngineEvent, while a change to besom.auto.internal.EngineEvent can't break besom.auto.internal.
- Position
- Below the diagonal: besom.auto.internal.EngineEvent uses a module listed above it, which is the healthy direction.
28→16 besom.auto.internal.GitAuth uses besom.util✕
- Connections
- 2 pairs of types, where a type in besom.auto.internal.GitAuth uses a type in besom.util.
- The types involved
besom.auto.internal.GitAuth.SSHPrivateKey→besom.util.NotProvidedOrbesom.auto.internal.GitAuth.SSHPrivateKeyPath→besom.util.NotProvidedOr
- Direction
- besom.auto.internal.GitAuth uses besom.util, so a change to besom.util can break besom.auto.internal.GitAuth, while a change to besom.auto.internal.GitAuth can't break besom.util.
- Position
- Below the diagonal: besom.auto.internal.GitAuth uses a module listed above it, which is the healthy direction.
28→23 besom.auto.internal.GitAuth uses besom.auto.internal✕
- Connections
- 4 pairs of types, where a type in besom.auto.internal.GitAuth uses a type in besom.auto.internal.
- The types involved
besom.auto.internal.GitAuth.PersonalAccessToken→besom.auto.internal.GitAuthbesom.auto.internal.GitAuth.SSHPrivateKey→besom.auto.internal.GitAuthbesom.auto.internal.GitAuth.SSHPrivateKeyPath→besom.auto.internal.GitAuthbesom.auto.internal.GitAuth.UsernameAndPassword→besom.auto.internal.GitAuth
- Direction
- besom.auto.internal.GitAuth uses besom.auto.internal, so a change to besom.auto.internal can break besom.auto.internal.GitAuth, while a change to besom.auto.internal.GitAuth can't break besom.auto.internal.
- Position
- Below the diagonal: besom.auto.internal.GitAuth uses a module listed above it, which is the healthy direction.
29→3 besom.auto.internal.LocalWorkspace uses besom.model✕
- Connections
- 1 pair of types, where a type in besom.auto.internal.LocalWorkspace uses a type in besom.model.
- The types involved
besom.auto.internal.LocalWorkspace.InitializedLocalWorkspace→besom.model.SemanticVersion
- Direction
- besom.auto.internal.LocalWorkspace uses besom.model, so a change to besom.model can break besom.auto.internal.LocalWorkspace, while a change to besom.auto.internal.LocalWorkspace can't break besom.model.
- Position
- Below the diagonal: besom.auto.internal.LocalWorkspace uses a module listed above it, which is the healthy direction.
29→23 besom.auto.internal.LocalWorkspace uses besom.auto.internal✕
- Connections
- 5 pairs of types, where a type in besom.auto.internal.LocalWorkspace uses a type in besom.auto.internal.
- The types involved
besom.auto.internal.LocalWorkspace.InitializedLocalWorkspace→besom.auto.internal.EnvVarValuebesom.auto.internal.LocalWorkspace.InitializedLocalWorkspace→besom.auto.internal.GitRepobesom.auto.internal.LocalWorkspace.InitializedLocalWorkspace→besom.auto.internal.LocalWorkspacebesom.auto.internal.LocalWorkspace.InitializedLocalWorkspace→besom.auto.internal.Projectbesom.auto.internal.LocalWorkspace.InitializedLocalWorkspace→besom.auto.internal.ProjectStack
- Direction
- besom.auto.internal.LocalWorkspace uses besom.auto.internal, so a change to besom.auto.internal can break besom.auto.internal.LocalWorkspace, while a change to besom.auto.internal.LocalWorkspace can't break besom.auto.internal.
- Position
- Below the diagonal: besom.auto.internal.LocalWorkspace uses a module listed above it, which is the healthy direction.
30→16 besom.auto.internal.LoginOption uses besom.util✕
- Connections
- 1 pair of types, where a type in besom.auto.internal.LoginOption uses a type in besom.util.
- The types involved
besom.auto.internal.LoginOption.Local→besom.util.NotProvidedOr
- Direction
- besom.auto.internal.LoginOption uses besom.util, so a change to besom.util can break besom.auto.internal.LoginOption, while a change to besom.auto.internal.LoginOption can't break besom.util.
- Position
- Below the diagonal: besom.auto.internal.LoginOption uses a module listed above it, which is the healthy direction.
30→23 besom.auto.internal.LoginOption uses besom.auto.internal✕
- Connections
- 6 pairs of types, where a type in besom.auto.internal.LoginOption uses a type in besom.auto.internal.
- The types involved
besom.auto.internal.LoginOption.AllowInsecure→besom.auto.internal.LoginOptionbesom.auto.internal.LoginOption.Cloud→besom.auto.internal.LoginOptionbesom.auto.internal.LoginOption.DefaultOrg→besom.auto.internal.LoginOptionbesom.auto.internal.LoginOption.Local→besom.auto.internal.LoginOptionbesom.auto.internal.LoginOption.PulumiAccessToken→besom.auto.internal.LoginOptionbesom.auto.internal.LoginOption.PulumiHome→besom.auto.internal.LoginOption
- Direction
- besom.auto.internal.LoginOption uses besom.auto.internal, so a change to besom.auto.internal can break besom.auto.internal.LoginOption, while a change to besom.auto.internal.LoginOption can't break besom.auto.internal.
- Position
- Below the diagonal: besom.auto.internal.LoginOption uses a module listed above it, which is the healthy direction.
31→16 besom.auto.internal.LogoutOption uses besom.util✕
- Connections
- 1 pair of types, where a type in besom.auto.internal.LogoutOption uses a type in besom.util.
- The types involved
besom.auto.internal.LogoutOption.Local→besom.util.NotProvidedOr
- Direction
- besom.auto.internal.LogoutOption uses besom.util, so a change to besom.util can break besom.auto.internal.LogoutOption, while a change to besom.auto.internal.LogoutOption can't break besom.util.
- Position
- Below the diagonal: besom.auto.internal.LogoutOption uses a module listed above it, which is the healthy direction.
31→23 besom.auto.internal.LogoutOption uses besom.auto.internal✕
- Connections
- 4 pairs of types, where a type in besom.auto.internal.LogoutOption uses a type in besom.auto.internal.
- The types involved
besom.auto.internal.LogoutOption.All→besom.auto.internal.LogoutOptionbesom.auto.internal.LogoutOption.Cloud→besom.auto.internal.LogoutOptionbesom.auto.internal.LogoutOption.Local→besom.auto.internal.LogoutOptionbesom.auto.internal.LogoutOption.PulumiHome→besom.auto.internal.LogoutOption
- Direction
- besom.auto.internal.LogoutOption uses besom.auto.internal, so a change to besom.auto.internal can break besom.auto.internal.LogoutOption, while a change to besom.auto.internal.LogoutOption can't break besom.auto.internal.
- Position
- Below the diagonal: besom.auto.internal.LogoutOption uses a module listed above it, which is the healthy direction.
32→2 besom.auto.internal.OpType uses besom.json✕
- Connections
- 2 pairs of types, where a type in besom.auto.internal.OpType uses a type in besom.json.
- The types involved
besom.auto.internal.OpType.OpTypeFormat→besom.json.JsValuebesom.auto.internal.OpType.OpTypeFormat→besom.json.RootJsonFormat
- Direction
- besom.auto.internal.OpType uses besom.json, so a change to besom.json can break besom.auto.internal.OpType, while a change to besom.auto.internal.OpType can't break besom.json.
- Position
- Below the diagonal: besom.auto.internal.OpType uses a module listed above it, which is the healthy direction.
32→23 besom.auto.internal.OpType uses besom.auto.internal✕
- Connections
- 1 pair of types, where a type in besom.auto.internal.OpType uses a type in besom.auto.internal.
- The types involved
besom.auto.internal.OpType.OpTypeFormat→besom.auto.internal.OpType
- Direction
- besom.auto.internal.OpType uses besom.auto.internal, so a change to besom.auto.internal can break besom.auto.internal.OpType, while a change to besom.auto.internal.OpType can't break besom.auto.internal.
- Position
- Below the diagonal: besom.auto.internal.OpType uses a module listed above it, which is the healthy direction.
33→2 besom.auto.internal.SummaryEvent uses besom.json✕
- Connections
- 3 pairs of types, where a type in besom.auto.internal.SummaryEvent uses a type in besom.json.
- The types involved
besom.auto.internal.SummaryEvent.SummaryEventFormat→besom.json.JsObjectbesom.auto.internal.SummaryEvent.SummaryEventFormat→besom.json.JsValuebesom.auto.internal.SummaryEvent.SummaryEventFormat→besom.json.RootJsonFormat
- Direction
- besom.auto.internal.SummaryEvent uses besom.json, so a change to besom.json can break besom.auto.internal.SummaryEvent, while a change to besom.auto.internal.SummaryEvent can't break besom.json.
- Position
- Below the diagonal: besom.auto.internal.SummaryEvent uses a module listed above it, which is the healthy direction.
33→23 besom.auto.internal.SummaryEvent uses besom.auto.internal✕
- Connections
- 1 pair of types, where a type in besom.auto.internal.SummaryEvent uses a type in besom.auto.internal.
- The types involved
besom.auto.internal.SummaryEvent.SummaryEventFormat→besom.auto.internal.SummaryEvent
- Direction
- besom.auto.internal.SummaryEvent uses besom.auto.internal, so a change to besom.auto.internal can break besom.auto.internal.SummaryEvent, while a change to besom.auto.internal.SummaryEvent can't break besom.auto.internal.
- Position
- Below the diagonal: besom.auto.internal.SummaryEvent uses a module listed above it, which is the healthy direction.
34→16 besom.auto.internal.shell uses besom.util✕
- Connections
- 1 pair of types, where a type in besom.auto.internal.shell uses a type in besom.util.
- The types involved
besom.auto.internal.shell.ShellOptions→besom.util.NotProvidedOr
- Direction
- besom.auto.internal.shell uses besom.util, so a change to besom.util can break besom.auto.internal.shell, while a change to besom.auto.internal.shell can't break besom.util.
- Position
- Below the diagonal: besom.auto.internal.shell uses a module listed above it, which is the healthy direction.
34→23 besom.auto.internal.shell uses besom.auto.internal✕
- Connections
- 3 pairs of types, where a type in besom.auto.internal.shell uses a type in besom.auto.internal.
- The types involved
besom.auto.internal.shell.Result→besom.auto.internal.ShellAutoErrorbesom.auto.internal.shell.ShellOptions→besom.auto.internal.ChildProcessbesom.auto.internal.shell.pulumi→besom.auto.internal.ShellAutoError
- Direction
- besom.auto.internal.shell uses besom.auto.internal, so a change to besom.auto.internal can break besom.auto.internal.shell, while a change to besom.auto.internal.shell can't break besom.auto.internal.
- Position
- Below the diagonal: besom.auto.internal.shell uses a module listed above it, which is the healthy direction.
35→7 pulumirpc.resource uses pulumirpc.callback✕
- Connections
- 2 pairs of types, where a type in pulumirpc.resource uses a type in pulumirpc.callback.
- The types involved
pulumirpc.resource.RegisterResourceRequest→pulumirpc.callback.Callbackpulumirpc.resource.ResourceMonitorGrpc→pulumirpc.callback.Callback
- Direction
- pulumirpc.resource uses pulumirpc.callback, so a change to pulumirpc.callback can break pulumirpc.resource, while a change to pulumirpc.resource can't break pulumirpc.callback.
- Position
- Below the diagonal: pulumirpc.resource uses a module listed above it, which is the healthy direction.
35→13 pulumirpc.resource uses pulumirpc.source✕
- Connections
- 4 pairs of types, where a type in pulumirpc.resource uses a type in pulumirpc.source.
- The types involved
pulumirpc.resource.ReadResourceRequest→pulumirpc.source.SourcePositionpulumirpc.resource.RegisterResourceRequest→pulumirpc.source.SourcePositionpulumirpc.resource.ResourceCallRequest→pulumirpc.source.SourcePositionpulumirpc.resource.ResourceInvokeRequest→pulumirpc.source.SourcePosition
- Direction
- pulumirpc.resource uses pulumirpc.source, so a change to pulumirpc.source can break pulumirpc.resource, while a change to pulumirpc.resource can't break pulumirpc.source.
- Position
- Below the diagonal: pulumirpc.resource uses a module listed above it, which is the healthy direction.
35→17 pulumirpc.resource uses pulumirpc.alias✕
- Connections
- 2 pairs of types, where a type in pulumirpc.resource uses a type in pulumirpc.alias.
- The types involved
pulumirpc.resource.RegisterResourceRequest→pulumirpc.alias.Aliaspulumirpc.resource.TransformResourceOptions→pulumirpc.alias.Alias
- Direction
- pulumirpc.resource uses pulumirpc.alias, so a change to pulumirpc.alias can break pulumirpc.resource, while a change to pulumirpc.resource can't break pulumirpc.alias.
- Position
- Below the diagonal: pulumirpc.resource uses a module listed above it, which is the healthy direction.
35→21 pulumirpc.resource uses pulumirpc.resource.RegisterResourceResponse✕
- Connections
- 1 pair of types, where a type in pulumirpc.resource uses a type in pulumirpc.resource.RegisterResourceResponse.
- The types involved
pulumirpc.resource.RegisterResourceResponse→pulumirpc.resource.RegisterResourceResponse.PropertyDependencies
- Direction
- pulumirpc.resource uses pulumirpc.resource.RegisterResourceResponse, so a change to pulumirpc.resource.RegisterResourceResponse can break pulumirpc.resource, while a change to pulumirpc.resource can't break pulumirpc.resource.RegisterResourceResponse.
- Position
- Below the diagonal: pulumirpc.resource uses a module listed above it, which is the healthy direction.
35→22 pulumirpc.resource uses pulumirpc.resource.ResourceCallRequest✕
- Connections
- 1 pair of types, where a type in pulumirpc.resource uses a type in pulumirpc.resource.ResourceCallRequest.
- The types involved
pulumirpc.resource.ResourceCallRequest→pulumirpc.resource.ResourceCallRequest.ArgumentDependencies
- Direction
- pulumirpc.resource uses pulumirpc.resource.ResourceCallRequest, so a change to pulumirpc.resource.ResourceCallRequest can break pulumirpc.resource, while a change to pulumirpc.resource can't break pulumirpc.resource.ResourceCallRequest.
- Position
- Below the diagonal: pulumirpc.resource uses a module listed above it, which is the healthy direction.
35→25 pulumirpc.resource uses pulumirpc.provider✕
- Connections
- 2 pairs of types, where a type in pulumirpc.resource uses a type in pulumirpc.provider.
- The types involved
pulumirpc.resource.ResourceMonitorGrpc→pulumirpc.provider.CallResponsepulumirpc.resource.ResourceMonitorGrpc→pulumirpc.provider.InvokeResponse
- Direction
- pulumirpc.resource uses pulumirpc.provider, so a change to pulumirpc.provider can break pulumirpc.resource, while a change to pulumirpc.resource can't break pulumirpc.provider.
- Position
- Below the diagonal: pulumirpc.resource uses a module listed above it, which is the healthy direction.
35→26 pulumirpc.resource uses pulumirpc.resource.RegisterResourceRequest✕
- Connections
- 3 pairs of types, where a type in pulumirpc.resource uses a type in pulumirpc.resource.RegisterResourceRequest.
- The types involved
pulumirpc.resource.RegisterResourceRequest→pulumirpc.resource.RegisterResourceRequest.CustomTimeoutspulumirpc.resource.RegisterResourceRequest→pulumirpc.resource.RegisterResourceRequest.PropertyDependenciespulumirpc.resource.TransformResourceOptions→pulumirpc.resource.RegisterResourceRequest.CustomTimeouts
- Direction
- pulumirpc.resource uses pulumirpc.resource.RegisterResourceRequest, so a change to pulumirpc.resource.RegisterResourceRequest can break pulumirpc.resource, while a change to pulumirpc.resource can't break pulumirpc.resource.RegisterResourceRequest.
- Position
- Below the diagonal: pulumirpc.resource uses a module listed above it, which is the healthy direction.
36→23 besom.auto.internal.shell.ShellOption uses besom.auto.internal✕
- Connections
- 1 pair of types, where a type in besom.auto.internal.shell.ShellOption uses a type in besom.auto.internal.
- The types involved
besom.auto.internal.shell.ShellOption.OnStart→besom.auto.internal.ChildProcess
- Direction
- besom.auto.internal.shell.ShellOption uses besom.auto.internal, so a change to besom.auto.internal can break besom.auto.internal.shell.ShellOption, while a change to besom.auto.internal.shell.ShellOption can't break besom.auto.internal.
- Position
- Below the diagonal: besom.auto.internal.shell.ShellOption uses a module listed above it, which is the healthy direction.
36→34 besom.auto.internal.shell.ShellOption uses besom.auto.internal.shell✕
- Connections
- 10 pairs of types, where a type in besom.auto.internal.shell.ShellOption uses a type in besom.auto.internal.shell.
- The types involved
besom.auto.internal.shell.ShellOption.Check→besom.auto.internal.shell.ShellOptionbesom.auto.internal.shell.ShellOption.Cwd→besom.auto.internal.shell.ShellOptionbesom.auto.internal.shell.ShellOption.DontPropagateEnv→besom.auto.internal.shell.ShellOptionbesom.auto.internal.shell.ShellOption.Env→besom.auto.internal.shell.ShellOptionbesom.auto.internal.shell.ShellOption.MergeErrIntoOut→besom.auto.internal.shell.ShellOptionbesom.auto.internal.shell.ShellOption.OnStart→besom.auto.internal.shell.ShellOptionbesom.auto.internal.shell.ShellOption.Stderr→besom.auto.internal.shell.ShellOptionbesom.auto.internal.shell.ShellOption.Stdin→besom.auto.internal.shell.ShellOptionbesom.auto.internal.shell.ShellOption.Stdout→besom.auto.internal.shell.ShellOptionbesom.auto.internal.shell.ShellOption.Timeout→besom.auto.internal.shell.ShellOption
- Direction
- besom.auto.internal.shell.ShellOption uses besom.auto.internal.shell, so a change to besom.auto.internal.shell can break besom.auto.internal.shell.ShellOption, while a change to besom.auto.internal.shell.ShellOption can't break besom.auto.internal.shell.
- Position
- Below the diagonal: besom.auto.internal.shell.ShellOption uses a module listed above it, which is the healthy direction.
37→7 pulumirpc.resource.ResourceMonitorGrpc uses pulumirpc.callback✕
- Connections
- 4 pairs of types, where a type in pulumirpc.resource.ResourceMonitorGrpc uses a type in pulumirpc.callback.
- The types involved
pulumirpc.resource.ResourceMonitorGrpc.ResourceMonitor→pulumirpc.callback.Callbackpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingClient→pulumirpc.callback.Callbackpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingStub→pulumirpc.callback.Callbackpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorStub→pulumirpc.callback.Callback
- Direction
- pulumirpc.resource.ResourceMonitorGrpc uses pulumirpc.callback, so a change to pulumirpc.callback can break pulumirpc.resource.ResourceMonitorGrpc, while a change to pulumirpc.resource.ResourceMonitorGrpc can't break pulumirpc.callback.
- Position
- Below the diagonal: pulumirpc.resource.ResourceMonitorGrpc uses a module listed above it, which is the healthy direction.
37→25 pulumirpc.resource.ResourceMonitorGrpc uses pulumirpc.provider✕
- Connections
- 8 pairs of types, where a type in pulumirpc.resource.ResourceMonitorGrpc uses a type in pulumirpc.provider.
- The types involved
pulumirpc.resource.ResourceMonitorGrpc.ResourceMonitor→pulumirpc.provider.CallResponsepulumirpc.resource.ResourceMonitorGrpc.ResourceMonitor→pulumirpc.provider.InvokeResponsepulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingClient→pulumirpc.provider.CallResponsepulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingClient→pulumirpc.provider.InvokeResponsepulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingStub→pulumirpc.provider.CallResponsepulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingStub→pulumirpc.provider.InvokeResponsepulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorStub→pulumirpc.provider.CallResponsepulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorStub→pulumirpc.provider.InvokeResponse
- Direction
- pulumirpc.resource.ResourceMonitorGrpc uses pulumirpc.provider, so a change to pulumirpc.provider can break pulumirpc.resource.ResourceMonitorGrpc, while a change to pulumirpc.resource.ResourceMonitorGrpc can't break pulumirpc.provider.
- Position
- Below the diagonal: pulumirpc.resource.ResourceMonitorGrpc uses a module listed above it, which is the healthy direction.
37→35 pulumirpc.resource.ResourceMonitorGrpc uses pulumirpc.resource✕
- Connections
- 44 pairs of types, where a type in pulumirpc.resource.ResourceMonitorGrpc uses a type in pulumirpc.resource. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
pulumirpc.resource.ResourceMonitorGrpc.ResourceMonitor→pulumirpc.resource.ReadResourceRequestpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitor→pulumirpc.resource.ReadResourceResponsepulumirpc.resource.ResourceMonitorGrpc.ResourceMonitor→pulumirpc.resource.RegisterPackageRequestpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitor→pulumirpc.resource.RegisterPackageResponsepulumirpc.resource.ResourceMonitorGrpc.ResourceMonitor→pulumirpc.resource.RegisterResourceOutputsRequestpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitor→pulumirpc.resource.RegisterResourceRequestpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitor→pulumirpc.resource.RegisterResourceResponsepulumirpc.resource.ResourceMonitorGrpc.ResourceMonitor→pulumirpc.resource.ResourceCallRequestpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitor→pulumirpc.resource.ResourceInvokeRequestpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitor→pulumirpc.resource.SupportsFeatureRequestpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitor→pulumirpc.resource.SupportsFeatureResponsepulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingClient→pulumirpc.resource.ReadResourceRequestpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingClient→pulumirpc.resource.ReadResourceResponsepulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingClient→pulumirpc.resource.RegisterPackageRequestpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingClient→pulumirpc.resource.RegisterPackageResponsepulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingClient→pulumirpc.resource.RegisterResourceOutputsRequestpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingClient→pulumirpc.resource.RegisterResourceRequestpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingClient→pulumirpc.resource.RegisterResourceResponsepulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingClient→pulumirpc.resource.ResourceCallRequestpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingClient→pulumirpc.resource.ResourceInvokeRequestpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingClient→pulumirpc.resource.SupportsFeatureRequestpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingClient→pulumirpc.resource.SupportsFeatureResponsepulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingStub→pulumirpc.resource.ReadResourceRequestpulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingStub→pulumirpc.resource.ReadResourceResponsepulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorBlockingStub→pulumirpc.resource.RegisterPackageRequest
- Direction
- pulumirpc.resource.ResourceMonitorGrpc uses pulumirpc.resource, so a change to pulumirpc.resource can break pulumirpc.resource.ResourceMonitorGrpc, while a change to pulumirpc.resource.ResourceMonitorGrpc can't break pulumirpc.resource.
- Position
- Below the diagonal: pulumirpc.resource.ResourceMonitorGrpc uses a module listed above it, which is the healthy direction.
38→2 besom.internal uses besom.json✕
- Connections
- 4 pairs of types, where a type in besom.internal uses a type in besom.json.
- The types involved
besom.internal.CodegenProtocol→besom.json.DefaultJsonProtocolbesom.internal.Config→besom.json.JsValuebesom.internal.StackReference→besom.json.JsValuebesom.internal.StackReferenceFactory→besom.json.JsValue
- Direction
- besom.internal uses besom.json, so a change to besom.json can break besom.internal, while a change to besom.internal can't break besom.json.
- Position
- Below the diagonal: besom.internal uses a module listed above it, which is the healthy direction.
38→4 besom.internal uses besom.types✕
- Connections
- 56 pairs of types, where a type in besom.internal uses a type in besom.types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
besom.internal.BesomSyntax→besom.types.ResourceTypebesom.internal.BesomSyntax→besom.types.URNbesom.internal.CommonResolvedResourceOptions→besom.types.URNbesom.internal.CommonResourceOptions→besom.types.URNbesom.internal.CommonResourceOptionsImpl→besom.types.URNbesom.internal.CommonResourceState→besom.types.ResourceTypebesom.internal.ComponentBase→besom.types.URNbesom.internal.ComponentContext→besom.types.URNbesom.internal.ComponentResource→besom.types.URNbesom.internal.ComponentResourceOptionsFactory→besom.types.URNbesom.internal.Context→besom.types.FunctionTokenbesom.internal.Context→besom.types.ProviderTypebesom.internal.Context→besom.types.ResourceTypebesom.internal.Context→besom.types.URNbesom.internal.CustomResolvedResourceOptions→besom.types.ResourceIdbesom.internal.CustomResource→besom.types.ResourceIdbesom.internal.CustomResourceOptions→besom.types.ResourceIdbesom.internal.CustomResourceOptionsFactory→besom.types.ResourceIdbesom.internal.CustomResourceOptionsFactory→besom.types.URNbesom.internal.CustomResourceState→besom.types.ResourceIdbesom.internal.Decoder→besom.types.Labelbesom.internal.DecoderHelpers→besom.types.Labelbesom.internal.DecodingError→besom.types.Labelbesom.internal.DependencyResource→besom.types.URNbesom.internal.Memo→besom.types.URN
- Direction
- besom.internal uses besom.types, so a change to besom.types can break besom.internal, while a change to besom.internal can't break besom.types.
- Position
- Below the diagonal: besom.internal uses a module listed above it, which is the healthy direction.
38→5 besom.internal uses besom.util.Validated✕
- Connections
- 2 pairs of types, where a type in besom.internal uses a type in besom.util.Validated.
- The types involved
besom.internal.Decoder→besom.util.Validated.ValidatedResultbesom.internal.DecoderHelpers→besom.util.Validated.ValidatedResult
- Direction
- besom.internal uses besom.util.Validated, so a change to besom.util.Validated can break besom.internal, while a change to besom.internal can't break besom.util.Validated.
- Position
- Below the diagonal: besom.internal uses a module listed above it, which is the healthy direction.
38→7 besom.internal uses pulumirpc.callback✕
- Connections
- 2 pairs of types, where a type in besom.internal uses a type in pulumirpc.callback.
- The types involved
besom.internal.Monitor→pulumirpc.callback.Callbackbesom.internal.MonitorImpl→pulumirpc.callback.Callback
- Direction
- besom.internal uses pulumirpc.callback, so a change to pulumirpc.callback can break besom.internal, while a change to besom.internal can't break pulumirpc.callback.
- Position
- Below the diagonal: besom.internal uses a module listed above it, which is the healthy direction.
38→9 besom.internal uses pulumirpc.engine✕
- Connections
- 11 pairs of types, where a type in besom.internal uses a type in pulumirpc.engine.
- The types involved
besom.internal.Engine→pulumirpc.engine.GetRootResourceRequestbesom.internal.Engine→pulumirpc.engine.GetRootResourceResponsebesom.internal.Engine→pulumirpc.engine.LogRequestbesom.internal.Engine→pulumirpc.engine.SetRootResourceRequestbesom.internal.Engine→pulumirpc.engine.SetRootResourceResponsebesom.internal.EngineImpl→pulumirpc.engine.GetRootResourceRequestbesom.internal.EngineImpl→pulumirpc.engine.GetRootResourceResponsebesom.internal.EngineImpl→pulumirpc.engine.LogRequestbesom.internal.EngineImpl→pulumirpc.engine.SetRootResourceRequestbesom.internal.EngineImpl→pulumirpc.engine.SetRootResourceResponsebesom.internal.logging→pulumirpc.engine.LogRequest
- Direction
- besom.internal uses pulumirpc.engine, so a change to pulumirpc.engine can break besom.internal, while a change to besom.internal can't break pulumirpc.engine.
- Position
- Below the diagonal: besom.internal uses a module listed above it, which is the healthy direction.
38→11 besom.internal uses pulumirpc.plugin✕
- Connections
- 1 pair of types, where a type in besom.internal uses a type in pulumirpc.plugin.
- The types involved
besom.internal.LanguageRuntimeService→pulumirpc.plugin.PluginInfo
- Direction
- besom.internal uses pulumirpc.plugin, so a change to pulumirpc.plugin can break besom.internal, while a change to besom.internal can't break pulumirpc.plugin.
- Position
- Below the diagonal: besom.internal uses a module listed above it, which is the healthy direction.
38→15 besom.internal uses besom.internal.logging✕
- Connections
- 3 pairs of types, where a type in besom.internal uses a type in besom.internal.logging.
- The types involved
besom.internal.Context→besom.internal.logging.BesomLoggerbesom.internal.ResourceDecoder→besom.internal.logging.BesomMDCbesom.internal.StackContext→besom.internal.logging.BesomLogger
- Direction
- besom.internal uses besom.internal.logging, so a change to besom.internal.logging can break besom.internal, while a change to besom.internal can't break besom.internal.logging.
- Position
- Below the diagonal: besom.internal uses a module listed above it, which is the healthy direction.
38→16 besom.internal uses besom.util✕
- Connections
- 24 pairs of types, where a type in besom.internal uses a type in besom.util.
- The types involved
besom.internal.AggregatedDecodingError→besom.util.NonEmptyVectorbesom.internal.BesomSyntax→besom.util.NonEmptyStringbesom.internal.Codegen→besom.util.NonEmptyStringbesom.internal.CommonResourceState→besom.util.NonEmptyStringbesom.internal.ComponentResourceOptionsFactory→besom.util.NonEmptyStringbesom.internal.Config→besom.util.NonEmptyStringbesom.internal.ConfigFactory→besom.util.NonEmptyStringbesom.internal.Context→besom.util.NonEmptyStringbesom.internal.CustomResourceOptionsFactory→besom.util.NonEmptyStringbesom.internal.CustomTimeoutsFactory→besom.util.NotProvidedOrbesom.internal.Decoder→besom.util.Validatedbesom.internal.Env→besom.util.NonEmptyStringbesom.internal.OutputData→besom.util.Validatedbesom.internal.ResourceOps→besom.util.NonEmptyStringbesom.internal.ResourceState→besom.util.NonEmptyStringbesom.internal.RunInfo→besom.util.NonEmptyStringbesom.internal.StackContext→besom.util.NonEmptyStringbesom.internal.StackReference→besom.util.NonEmptyStringbesom.internal.StackReferenceArgs→besom.util.NonEmptyStringbesom.internal.StackReferenceArgsFactory→besom.util.NonEmptyStringbesom.internal.StackReferenceFactory→besom.util.NonEmptyStringbesom.internal.StackReferenceResourceOptionsFactory→besom.util.NonEmptyStringbesom.internal.TransformedResourceInfo→besom.util.NonEmptyStringbesom.internal.TransformedResourceInfoImpl→besom.util.NonEmptyString
- Direction
- besom.internal uses besom.util, so a change to besom.util can break besom.internal, while a change to besom.internal can't break besom.util.
- Position
- Below the diagonal: besom.internal uses a module listed above it, which is the healthy direction.
38→18 besom.internal uses pulumirpc.language✕
- Connections
- 22 pairs of types, where a type in besom.internal uses a type in pulumirpc.language.
- The types involved
besom.internal.LanguageRuntimeService→pulumirpc.language.AboutRequestbesom.internal.LanguageRuntimeService→pulumirpc.language.AboutResponsebesom.internal.LanguageRuntimeService→pulumirpc.language.GeneratePackageRequestbesom.internal.LanguageRuntimeService→pulumirpc.language.GeneratePackageResponsebesom.internal.LanguageRuntimeService→pulumirpc.language.GenerateProgramRequestbesom.internal.LanguageRuntimeService→pulumirpc.language.GenerateProgramResponsebesom.internal.LanguageRuntimeService→pulumirpc.language.GenerateProjectRequestbesom.internal.LanguageRuntimeService→pulumirpc.language.GenerateProjectResponsebesom.internal.LanguageRuntimeService→pulumirpc.language.GetProgramDependenciesRequestbesom.internal.LanguageRuntimeService→pulumirpc.language.GetProgramDependenciesResponsebesom.internal.LanguageRuntimeService→pulumirpc.language.GetRequiredPluginsRequestbesom.internal.LanguageRuntimeService→pulumirpc.language.GetRequiredPluginsResponsebesom.internal.LanguageRuntimeService→pulumirpc.language.InstallDependenciesRequestbesom.internal.LanguageRuntimeService→pulumirpc.language.InstallDependenciesResponsebesom.internal.LanguageRuntimeService→pulumirpc.language.PackRequestbesom.internal.LanguageRuntimeService→pulumirpc.language.PackResponsebesom.internal.LanguageRuntimeService→pulumirpc.language.RunPluginRequestbesom.internal.LanguageRuntimeService→pulumirpc.language.RunPluginResponsebesom.internal.LanguageRuntimeService→pulumirpc.language.RunRequestbesom.internal.LanguageRuntimeService→pulumirpc.language.RunResponsebesom.internal.LanguageRuntimeService→pulumirpc.language.RuntimeOptionsRequestbesom.internal.LanguageRuntimeService→pulumirpc.language.RuntimeOptionsResponse
- Direction
- besom.internal uses pulumirpc.language, so a change to pulumirpc.language can break besom.internal, while a change to besom.internal can't break pulumirpc.language.
- Position
- Below the diagonal: besom.internal uses a module listed above it, which is the healthy direction.
38→24 besom.internal uses pulumirpc.language.LanguageRuntimeGrpc✕
- Connections
- 1 pair of types, where a type in besom.internal uses a type in pulumirpc.language.LanguageRuntimeGrpc.
- The types involved
besom.internal.LanguageRuntimeService→pulumirpc.language.LanguageRuntimeGrpc.LanguageRuntime
- Direction
- besom.internal uses pulumirpc.language.LanguageRuntimeGrpc, so a change to pulumirpc.language.LanguageRuntimeGrpc can break besom.internal, while a change to besom.internal can't break pulumirpc.language.LanguageRuntimeGrpc.
- Position
- Below the diagonal: besom.internal uses a module listed above it, which is the healthy direction.
38→25 besom.internal uses pulumirpc.provider✕
- Connections
- 4 pairs of types, where a type in besom.internal uses a type in pulumirpc.provider.
- The types involved
besom.internal.Monitor→pulumirpc.provider.CallResponsebesom.internal.Monitor→pulumirpc.provider.InvokeResponsebesom.internal.MonitorImpl→pulumirpc.provider.CallResponsebesom.internal.MonitorImpl→pulumirpc.provider.InvokeResponse
- Direction
- besom.internal uses pulumirpc.provider, so a change to pulumirpc.provider can break besom.internal, while a change to besom.internal can't break pulumirpc.provider.
- Position
- Below the diagonal: besom.internal uses a module listed above it, which is the healthy direction.
38→35 besom.internal uses pulumirpc.resource✕
- Connections
- 18 pairs of types, where a type in besom.internal uses a type in pulumirpc.resource.
- The types involved
besom.internal.Monitor→pulumirpc.resource.ReadResourceRequestbesom.internal.Monitor→pulumirpc.resource.ReadResourceResponsebesom.internal.Monitor→pulumirpc.resource.RegisterResourceOutputsRequestbesom.internal.Monitor→pulumirpc.resource.RegisterResourceRequestbesom.internal.Monitor→pulumirpc.resource.RegisterResourceResponsebesom.internal.Monitor→pulumirpc.resource.ResourceCallRequestbesom.internal.Monitor→pulumirpc.resource.ResourceInvokeRequestbesom.internal.Monitor→pulumirpc.resource.SupportsFeatureRequestbesom.internal.Monitor→pulumirpc.resource.SupportsFeatureResponsebesom.internal.MonitorImpl→pulumirpc.resource.ReadResourceRequestbesom.internal.MonitorImpl→pulumirpc.resource.ReadResourceResponsebesom.internal.MonitorImpl→pulumirpc.resource.RegisterResourceOutputsRequestbesom.internal.MonitorImpl→pulumirpc.resource.RegisterResourceRequestbesom.internal.MonitorImpl→pulumirpc.resource.RegisterResourceResponsebesom.internal.MonitorImpl→pulumirpc.resource.ResourceCallRequestbesom.internal.MonitorImpl→pulumirpc.resource.ResourceInvokeRequestbesom.internal.MonitorImpl→pulumirpc.resource.SupportsFeatureRequestbesom.internal.MonitorImpl→pulumirpc.resource.SupportsFeatureResponse
- Direction
- besom.internal uses pulumirpc.resource, so a change to pulumirpc.resource can break besom.internal, while a change to besom.internal can't break pulumirpc.resource.
- Position
- Below the diagonal: besom.internal uses a module listed above it, which is the healthy direction.
38→37 besom.internal uses pulumirpc.resource.ResourceMonitorGrpc✕
- Connections
- 1 pair of types, where a type in besom.internal uses a type in pulumirpc.resource.ResourceMonitorGrpc.
- The types involved
besom.internal.MonitorImpl→pulumirpc.resource.ResourceMonitorGrpc.ResourceMonitorStub
- Direction
- besom.internal uses pulumirpc.resource.ResourceMonitorGrpc, so a change to pulumirpc.resource.ResourceMonitorGrpc can break besom.internal, while a change to besom.internal can't break pulumirpc.resource.ResourceMonitorGrpc.
- Position
- Below the diagonal: besom.internal uses a module listed above it, which is the healthy direction.
39→16 besom.aliases uses besom.util✕
- Connections
- 1 pair of types, where a type in besom.aliases uses a type in besom.util.
- The types involved
besom.aliases.NonEmptyString→besom.util.NonEmptyStringFactory
- Direction
- besom.aliases uses besom.util, so a change to besom.util can break besom.aliases, while a change to besom.aliases can't break besom.util.
- Position
- Below the diagonal: besom.aliases uses a module listed above it, which is the healthy direction.
39→38 besom.aliases uses besom.internal✕
- Connections
- 10 pairs of types, where a type in besom.aliases uses a type in besom.internal.
- The types involved
besom.aliases.ComponentResourceOptions→besom.internal.ComponentResourceOptionsFactorybesom.aliases.Config→besom.internal.ConfigFactorybesom.aliases.CustomResourceOptions→besom.internal.CustomResourceOptionsFactorybesom.aliases.CustomTimeouts→besom.internal.CustomTimeoutsFactorybesom.aliases.Output→besom.internal.OutputFactorybesom.aliases.OutputExtensions→besom.internal.OutputExtensionsFactorybesom.aliases.Stack→besom.internal.StackFactorybesom.aliases.StackReference→besom.internal.StackReferenceFactorybesom.aliases.StackReferenceArgs→besom.internal.StackReferenceArgsFactorybesom.aliases.StackReferenceResourceOptions→besom.internal.StackReferenceResourceOptionsFactory
- Direction
- besom.aliases uses besom.internal, so a change to besom.internal can break besom.aliases, while a change to besom.aliases can't break besom.internal.
- Position
- Below the diagonal: besom.aliases uses a module listed above it, which is the healthy direction.
40→4 besom.internal.ResourceDecoder uses besom.types✕
- Connections
- 1 pair of types, where a type in besom.internal.ResourceDecoder uses a type in besom.types.
- The types involved
besom.internal.ResourceDecoder.CustomPropertyExtractor→besom.types.Label
- Direction
- besom.internal.ResourceDecoder uses besom.types, so a change to besom.types can break besom.internal.ResourceDecoder, while a change to besom.internal.ResourceDecoder can't break besom.types.
- Position
- Below the diagonal: besom.internal.ResourceDecoder uses a module listed above it, which is the healthy direction.
40→5 besom.internal.ResourceDecoder uses besom.util.Validated✕
- Connections
- 1 pair of types, where a type in besom.internal.ResourceDecoder uses a type in besom.util.Validated.
- The types involved
besom.internal.ResourceDecoder.CustomPropertyExtractor→besom.util.Validated.ValidatedResult
- Direction
- besom.internal.ResourceDecoder uses besom.util.Validated, so a change to besom.util.Validated can break besom.internal.ResourceDecoder, while a change to besom.internal.ResourceDecoder can't break besom.util.Validated.
- Position
- Below the diagonal: besom.internal.ResourceDecoder uses a module listed above it, which is the healthy direction.
40→15 besom.internal.ResourceDecoder uses besom.internal.logging✕
- Connections
- 1 pair of types, where a type in besom.internal.ResourceDecoder uses a type in besom.internal.logging.
- The types involved
besom.internal.ResourceDecoder.CustomPropertyExtractor→besom.internal.logging.BesomMDC
- Direction
- besom.internal.ResourceDecoder uses besom.internal.logging, so a change to besom.internal.logging can break besom.internal.ResourceDecoder, while a change to besom.internal.ResourceDecoder can't break besom.internal.logging.
- Position
- Below the diagonal: besom.internal.ResourceDecoder uses a module listed above it, which is the healthy direction.
40→38 besom.internal.ResourceDecoder uses besom.internal✕
- Connections
- 4 pairs of types, where a type in besom.internal.ResourceDecoder uses a type in besom.internal.
- The types involved
besom.internal.ResourceDecoder.CustomPropertyExtractor→besom.internal.Contextbesom.internal.ResourceDecoder.CustomPropertyExtractor→besom.internal.DecodingErrorbesom.internal.ResourceDecoder.CustomPropertyExtractor→besom.internal.OutputDatabesom.internal.ResourceDecoder.CustomPropertyExtractor→besom.internal.Resource
- Direction
- besom.internal.ResourceDecoder uses besom.internal, so a change to besom.internal can break besom.internal.ResourceDecoder, while a change to besom.internal.ResourceDecoder can't break besom.internal.
- Position
- Below the diagonal: besom.internal.ResourceDecoder uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 41 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 22 | High / Critical |
| A07:2025 — Authentication Failures | 6 | High / Critical |
Roadmap
Top priorities: Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`); Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED; Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`). | +5.5 pts | Medium | Web-Security Posture |
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +2.5 pts | Low | REDACTED Scanning |
| Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (4). | +2.1 pts | Low | Secrets (history) |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.3 pts | Low | Static Analysis (SAST) |
| Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.3 pts | Low | Dependency Vulnerabilities |
| Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.3 pts | Low | Dependency Vulnerabilities |
| Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). | +1.3 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Secrets (history): REDACTED: REDACTED |
| REDACTED | 0.4 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.2 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| besom-cfg/k8s/src/main/scala/diffs.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| codegen/src/TypeMapper.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| codegen/src/CodeGen.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/besom/internal/Result.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/besom/internal/ResourceOps.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/besom/internal/RawResourceResult.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/besom/internal/ResourceOptions.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| auto/src/main/scala/besom/auto/internal/Stack.scala | 6.0 | Mixed | Explicit Debt: FixmeComment |
| core/src/main/scala/besom/types.scala | 6.4 | Mixed | Explicit Debt: TodoComment |
| core/src/test/scala/besom/internal/ResultSpec.scala | 6.4 | Mixed | 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 63 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 — 63 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, 319 of 342 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
- D5 Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its Go module dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- 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 a COLLECTOR gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- 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.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Project size and spread are measured over build units (a .NET project, a Maven or Gradle module, an npm, Deno or JSR package, a Go module, a Cargo crate, a Python, Composer, Bundler, RubyGems, Mix, rebar3, sbt, SwiftPM or pub package, an OTP application, an Xcode project or XcodeGen spec, or a checkout that declares no build at all) whose source a code model reads. This repository's production source is in a language no model reads, or in units whose build tool D26 does not recognise. That is a gap in this analyzer's language reach — not a finding that the repository's projects are cohesive.
- 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.
- D32 Data Compliance (PII/GDPR) — 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. `auto/src/main/scala/besom/auto/internal/Events.scala`, `auto/src/main/scala/besom/auto/internal/LocalWorkspace.scala`, `auto/src/main/scala/besom/auto/internal/Stack.scala`, `auto/src/main/scala/besom/auto/internal/Workspace.scala`, `auto/src/main/scala/besom/auto/internal/auto.scala`, … (+35 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — not measured this run — 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: 33 commits in the last 90 days, yet 77 of 95 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.
- AX2 Stateful singletons — 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. Those languages run requests on shared-memory threads, so a shared instance mutated without a lock is the same defect this card counts in C#, Java, Kotlin, Python, Go, Swift, Scala, Ruby and F#, but their singleton shapes are not read yet. That is a gap in this analyzer's language reach — not a finding that the code is free of it.
- AXB2 Runtime readiness — 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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 (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
14 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was JsonInterpolator.jsonImpl at 43. A further 4 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 Packages.main at 24 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: REDACTED (Packages.main at 24), auto/src/main/scala/besom/auto/internal/Stack.scala (UpOptions.from at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with JsonInterpolator.jsonImpl (cyclomatic 43), LocalWorkspace.apply (cyclomatic 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 7.8 to about 8.2/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
35 method(s) exceeded the cognitive complexity threshold of 15; the worst was EffectBesomModule.run at 215.
What to do
- Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with EffectBesomModule.run (cognitive 215). — Refactoring it lifts Cognitive Complexity from 4.6 to about 5.3/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
7 god class(es) detected.
What to do
- Resolve the 5 FileTooLong finding(s) in God Classes — start with REDACTED, REDACTED, Stack.scala. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with LocalWorkspace.scala, REDACTED. — 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
18 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 3 of the 20 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with Stack.scala, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Stack.scala, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Members sharing a duplicated core (6 members, 50+ identical tokens) finding(s) in Code Duplication — start with ResourceOptions.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.
D6 · Cohesion (LCOM4)
0 of 5 classes have LCOM4 above 3.
D9 · Test Distribution
634 test methods: 634 unit, 0 integration, 0 BDD, 0 e2e. The Go suite contributes 40 test case(s) across 5 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 0 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one. The Scala suite contributes 594 test case(s) across 69 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.
D12 · Dependency Hygiene
4 outdated, 1 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
What to do
- Resolve the 1 Deprecated module finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 85 required Go module(s) use a banned license. Licences were read per module version from the licence files pkg.go.dev detects (via api.deps.dev), over every module this repository's REDACTED requires, direct and indirect, at the version the build uses. Go records no test-only scope at module level, so modules only this repository's own tests import are included. 1 of them carry no licence file that matches a known SPDX licence; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's Go module dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: auto/src/main/scala/besom/auto/internal/auto.scala (3 of 3 changes were fixes)
What to do
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with auto.scala. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
14 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is auto/src/main/scala/besom/auto/internal/Stack.scala. Counted over 95 of the 193 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
155 deducted task-comment markers across 29068 LoC (0.5/KLoC) → score 9.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 143 TodoComment finding(s) in Explicit Debt — start with ResultSpec.scala (24), Stack.scala (20), ResourceOps.scala (17). — One of this dimension's main actionable groups (143 warning-level).
- Resolve the 11 FixmeComment finding(s) in Explicit Debt — start with CodeGen.test.scala (2), Stack.scala (2), Workspace.scala (2). — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with ScalaDefinitionCoordinates.scala. — One of this dimension's main actionable groups (1 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 27 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
4 finding(s): 0 critical, 4 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 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (4). — One of this dimension's main actionable groups (4 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)
41 finding(s): 0 critical, 37 high, 4 medium, 0 low. 33 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 34 file(s) — `auto/src/main/scala/besom/auto/internal/Events.scala`, `auto/src/main/scala/besom/auto/internal/LocalWorkspace.scala`, `auto/src/main/scala/besom/auto/internal/Stack.scala`, `auto/src/main/scala/besom/auto/internal/Workspace.scala`, `auto/src/main/scala/besom/auto/internal/auto.scala`, … (+29 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 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 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 33 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 (33 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
12 finding(s): 3 critical, 2 high, 7 medium, 0 low.
What to do
- Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D35 · Change Coupling
Strongest change-coupling: project.scala↔project.scala 94%; project.scala↔project.scala 53%; project.scala↔project.scala 50%
What to do
- Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with project.scala. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
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
- `scalaLanguageHost` is shared by every request (`ExecutorWithInfo` is called per request from the gRPC service method `scalaLanguageHost.GetRequiredPlugins`, on the one `scalaLanguageHost` value that handler's shared receiver holds) but writes its fields outside any lock (currentExecutor; e.g. `currentExecutor` in `ExecutorWithInfo` at line 173). Unsynchronised concurrent writes are a data race in Go: an update is lost or a value tears, and a concurrent map write aborts the process. — language-plugin/pulumi-language-scala/main.go:119
What to do
- Go: guard the state handlers share with a sync.Mutex held for the whole update (`mu.Lock(); defer mu.Unlock()`), make counters sync/atomic types (atomic.Int64) and caches a sync.Map, or keep per-request data in locals and the request context. `go test -race` over a handler test confirms the race and then its fix.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `Workspace` declares 42 abstract members: `projectSettings`, `saveProjectSettings`, `stackSettings`, `saveStackSettings`, `serializeArgsForOp`, `postCommandCallback`, `addEnvironments`, `listEnvironments`, `removeEnvironment`, `getConfig`, `getAllConfig`, `setConfig`, `setAllConfig`, `removeConfig`, `removeAllConfig`, `refreshConfig`, `getTag`, `setTag`, `removeTag`, `listTags`, `getEnvVars`, `setEnvVars`, `setEnvVar`, `unsetEnvVar`, `workDir`, `pulumiHome`, `secretsProvider`, `pulumiVersion`, `whoAmI`, `changeStackSecretsProvider`, `stack`, `createStack`, `selectStack`, `removeStack`, `listStacks`, `installPlugin`, `removePlugin`, `listPlugins`, `program`, `exportStack`, and 2 more. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — auto/src/main/scala/besom/auto/internal/Workspace.scala:92
- `ResourceProvider` declares 20 abstract members: `parameterize`, `getSchema`, `checkConfig`, `diffConfig`, `configure`, `invoke`, `streamInvoke`, `call`, `check`, `diff`, `create`, `read`, `update`, `delete`, `construct`, `cancel`, `getPluginInfo`, `attach`, `getMapping`, `getMappings`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — besom-rpc/src/main/scala/pulumirpc/provider/ResourceProviderGrpc.scala:236
- `ResourceProviderBlockingClient` declares 20 abstract members: `parameterize`, `getSchema`, `checkConfig`, `diffConfig`, `configure`, `invoke`, `streamInvoke`, `call`, `check`, `diff`, `create`, `read`, `update`, `delete`, `construct`, `cancel`, `getPluginInfo`, `attach`, `getMapping`, `getMappings`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — besom-rpc/src/main/scala/pulumirpc/provider/ResourceProviderGrpc.scala:463
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code
- `permalink` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. (×4) — auto/src/main/scala/besom/auto/internal/Stack.scala:1460, auto/src/main/scala/besom/auto/internal/Stack.scala:1496, auto/src/main/scala/besom/auto/internal/Stack.scala:1529, …
- `callInternal` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — core/src/main/scala/besom/internal/ResourceOps.scala:117
What to do
- Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `permalink` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. (×4) — auto/src/main/scala/besom/auto/internal/Stack.scala:1460, auto/src/main/scala/besom/auto/internal/Stack.scala:1496, auto/src/main/scala/besom/auto/internal/Stack.scala:1529, …
- `callInternal` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — core/src/main/scala/besom/internal/ResourceOps.scala:117
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — core/src/test/scala/besom/internal/RegistersOutputsDerivationTest.scala:54
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- Clear the softer debt: re-enable or delete `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)
- 42 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
- Add a README to the 1 of 2 project(s) that lack one — worth up to 1 pts.
- Review the README against recent changes; refresh the parts that drifted.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `language-plugin/pulumi-language-scala`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 7814 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:14
- `website/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — website/package.json:16
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
- Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
PF3 · Async & latency hygiene
- `sleep` is async and calls Thread.sleep — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — core/src/main/scala/besom/internal/Result.scala:415
What to do
- Scala: compose the Future or effect (map/flatMap, a for-comprehension) instead of Await.result or unsafeRunSync, and wrap unavoidable blocking calls in blocking { } (Future), IO.blocking or ZIO.attemptBlocking.
S1 · Web-Security Posture
- This repository runs an HTTP server and nothing in its Scala source or committed configuration secures the transport: no HTTPS served (akka/pekko-http `ConnectionContext.httpsServer`/`enableHttps`, an http4s builder's `withTLS`, Jetty's `SslContextFactory`, zio-http's `SSLConfig`, Play's `https.port`), no `Strict-Transport-Security` header, HSTS middleware or Play `RedirectHttpsFilter`, no `X-Forwarded-Proto` read or Play `play.http.forwarded.trustedProxies` for a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: core/src/main/scala/besom/internal/Language.scala:4 — `NettyServerBuilder`.
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Scala server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: core/src/main/scala/besom/internal/Language.scala:4 — `NettyServerBuilder`.
- No handler of this repository's Scala server answers 400, 413 or 422 (`BadRequest`, `StatusCodes.BadRequest`, `Status.BadRequest`, `UnprocessableEntity`), and nothing declares validation — no Play `Form(mapping(…))` or `validate[T]`, no tapir `Validator`, no akka/pekko-http `validate(…)` or `withSizeLimit`, no validation library (refined, iron, accord, cats `Validated`, Jakarta Bean Validation) — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: core/src/main/scala/besom/internal/Language.scala:4 — `NettyServerBuilder`.
What to do
- Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`).
- Set security response headers on what the server sends — keep Play's `SecurityHeadersFilter` enabled, wrap akka/pekko-http routes in `respondWithHeaders(RawHeader("X-Content-Type-Options", "nosniff"), …)`, or add an http4s middleware that sets `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
- Validate what the server reads from a request — path, query, headers, body size and shape — and answer what fails with 400 (413 for an oversized body) before a handler acts on it: a Play form or `validate[T]` answered with `BadRequest`, tapir `Validator`s on the endpoint's inputs, or akka/pekko-http's `validate(…)` and `withSizeLimit` directives.
X1 · Async correctness
- The `Future` this starts is not kept anywhere, and `scala.concurrent.Future` never reports a failure on its own: `Future { … }` catches any non-fatal exception its body throws and stores it as the future's `Failure` — not rethrown, not printed, not passed to the `ExecutionContext`'s `reportFailure` — so once nobody holds the future the error is gone, and nothing can wait for the work to finish either. Keep the future and compose it into what the caller returns (`for`/`flatMap`, `Future.sequence`), or, for genuine fire-and-forget, attach a handler that reports the failure — `Future { … }.failed.foreach(error => log.error("…", error))` or `.onComplete { case Failure(e) => report(e); case _ => }` — or catch and report inside the body itself. — core/src/main/scala/besom/internal/Result.scala:410
What to do
- Future started here is not kept
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
- `encode` is public, takes a document from its caller (line 967) and hands it to `encodeInternal`, which calls itself at line 959 with a piece of `json` (and at line 960), not as a tail call the compiler turns into a loop — and nowhere in `encodeInternal` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `encodeInternal` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — REDACTED:959
- `read` is public and takes `json: JsValue` from its caller, and it calls itself at line 69 with a piece of `json` (and at line 74, line 80), not as a tail call the compiler turns into a loop — and nowhere in `read` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `read` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — besom-cfg/lib/src/main/scala/internal/FieldType.scala:69
- `read` is public and takes `json: JsValue` from its caller, and it calls itself at line 38 with a piece of `json` (and at line 39), not as a tail call the compiler turns into a loop — and nowhere in `read` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `read` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — auto/src/main/scala/besom/auto/internal/Workspace.scala:38
- `read` is public and takes `json: JsValue` from its caller, and it calls itself at line 605 with a piece of `json`, not as a tail call the compiler turns into a loop — and nowhere in `read` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `read` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — auto/src/main/scala/besom/auto/internal/Workspace.scala:605
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
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
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. — auto/src/main/scala/besom/auto/internal/shell.scala:61
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 177 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.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 55% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 69% | Adequate — gated by AX2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 73% | Strong | Solid. |
| Readiness | 56% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 49% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Exemplary | Strongest area. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 57 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Go 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; this repository's Python 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; 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~14661 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 — no .scala test runner
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Go, JavaScript, Scala 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 .go, .py, .scala source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 measured no build unit over this repository's .py, .scala source. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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) — 40 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- 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.
- D5 Coupling — D5 reads a .NET project-reference graph only — this repository's production source is .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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): 427 value object(s); 3 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 Go, 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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Scala was read, and it logs through none that an interpolated message defeats: scala-logging takes an `s"…"` message apart into SLF4J's pattern and arguments at compile time, and log4s, grizzled-slf4j, Play's Logger, Akka's LoggingAdapter, sbt's Logger and Spark's Logging take one finished message (as log4net does in C#). Calls made straight through SLF4J (`org.slf4j.Logger`) would be judged.
- 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 — 47 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 270 finding(s)
- TodoComment model/SemanticVersion.scala:3
- TodoComment examples/azure-webserver/Main.scala:102
- TodoComment examples/azure-webserver/Main.scala:115
- TodoComment examples/azure-aci/Main.scala:41
- TodoComment core/src/test/scala/besom/internal/LoggingTest.scala:68
- TodoComment core/src/test/scala/besom/internal/ResourceDecoderTest.scala:32
- TodoComment core/src/test/scala/besom/internal/ResourceDecoderTest.scala:279
- TodoComment core/src/test/scala/besom/internal/ResultSpec.scala:287
- TodoComment besom-zio/src/test/scala/ResultSpec.scala:287
- TodoComment besom-cats/src/test/scala/ResultSpec.scala:287
- TodoComment core/src/test/scala/besom/internal/ResultSpec.scala:288
- TodoComment besom-zio/src/test/scala/ResultSpec.scala:288
- TodoComment besom-cats/src/test/scala/ResultSpec.scala:288
- TodoComment core/src/test/scala/besom/internal/ResultSpec.scala:289
- TodoComment besom-zio/src/test/scala/ResultSpec.scala:289
- TodoComment besom-cats/src/test/scala/ResultSpec.scala:289
- TodoComment core/src/test/scala/besom/internal/ResultSpec.scala:290
- TodoComment besom-zio/src/test/scala/ResultSpec.scala:290
- TodoComment besom-cats/src/test/scala/ResultSpec.scala:290
- TodoComment core/src/test/scala/besom/internal/ResultSpec.scala:291
- TodoComment core/src/test/scala/besom/internal/ResultSpec.scala:292
- TodoComment core/src/test/scala/besom/internal/ResultSpec.scala:293
- TodoComment core/src/test/scala/besom/internal/ResultSpec.scala:294
- TodoComment core/src/main/scala/besom/internal/Env.scala:31
- TodoComment besom-zio/src/test/scala/ResultSpec.scala:291
- FixmeComment integration-tests/CodegenTests.test.scala:28
- FixmeComment integration-tests/CoreTests.test.scala:79
- FixmeComment core/src/test/scala/besom/internal/OutputTest.scala:386
- FixmeComment core/src/test/scala/besom/internal/ResourceDecoderTest.scala:175
- FixmeComment codegen/src/CodeGen.test.scala:1022
- FixmeComment codegen/src/CodeGen.test.scala:1052
- FixmeComment auto/src/main/scala/besom/model/FullyQualifiedStackName.scala:127
- FixmeComment auto/src/main/scala/besom/auto/internal/Stack.scala:177
- FixmeComment auto/src/main/scala/besom/auto/internal/Stack.scala:584
- FixmeComment auto/src/main/scala/besom/auto/internal/Workspace.scala:12
- FixmeComment auto/src/main/scala/besom/auto/internal/Workspace.scala:85
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: REDACTED REDACTED
- FileTooLong: REDACTED REDACTED
- FileTooLong: internal/Stack.scala auto/src/main/scala/besom/auto/internal/Stack.scala
- FileTooLong: internal/LocalWorkspace.scala auto/src/main/scala/besom/auto/internal/LocalWorkspace.scala
- FileTooLong: internal/ResourceOps.scala core/src/main/scala/besom/internal/ResourceOps.scala
- Unfinished stub — body is `???` auto/src/main/scala/besom/auto/internal/Stack.scala:1460
- Unfinished stub — body is `???` auto/src/main/scala/besom/auto/internal/Stack.scala:1496
- Unfinished stub — body is `???` auto/src/main/scala/besom/auto/internal/Stack.scala:1529
- Unfinished stub — body is `???` auto/src/main/scala/besom/auto/internal/Stack.scala:1562
- Unfinished stub — body is `???` core/src/main/scala/besom/internal/ResourceOps.scala:117
- Unfinished stub — body is ??? / NotImplementedError auto/src/main/scala/besom/auto/internal/Stack.scala:1460
- Unfinished stub — body is ??? / NotImplementedError auto/src/main/scala/besom/auto/internal/Stack.scala:1496
- Unfinished stub — body is ??? / NotImplementedError auto/src/main/scala/besom/auto/internal/Stack.scala:1529
- Unfinished stub — body is ??? / NotImplementedError auto/src/main/scala/besom/auto/internal/Stack.scala:1562
- Unfinished stub — body is ??? / NotImplementedError core/src/main/scala/besom/internal/ResourceOps.scala:117
- Recursive walk over a caller-supplied document has no depth cap REDACTED:959
- Recursive walk over a caller-supplied document has no depth cap besom-cfg/lib/src/main/scala/internal/FieldType.scala:69
- Recursive walk over a caller-supplied document has no depth cap auto/src/main/scala/besom/auto/internal/Workspace.scala:38
- Recursive walk over a caller-supplied document has no depth cap auto/src/main/scala/besom/auto/internal/Workspace.scala:605
- REDACTED
- REDACTED
- REDACTED
- TooManyMethods: LocalWorkspace auto/src/main/scala/besom/auto/internal/LocalWorkspace.scala:22
- TooManyMethods: Packages REDACTED:22
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (10 lines × 2) auto/src/main/scala/besom/auto/internal/Stack.scala:230
- Duplicated block (10 lines × 2) REDACTED:467
- Duplicated block (8 lines × 2) auto/src/main/scala/besom/auto/internal/Stack.scala:221
- Duplicated block (8 lines × 2) REDACTED:649
- Stateful handler dependency: scalaLanguageHost language-plugin/pulumi-language-scala/main.go:119
- JsonInterpolator.jsonImpl (cyclomatic 43) core/src/main/scala/besom/util/JsonInterpolator.scala:16
- LocalWorkspace.apply (cyclomatic 31) auto/src/main/scala/besom/auto/internal/LocalWorkspace.scala:687
- NonEmptyString.fromImpl (cyclomatic 28) core/src/main/scala/besom/util/NonEmptyString.scala:69
- Diff.performDiff (cyclomatic 24) besom-cfg/k8s/src/main/scala/diffs.scala:250
- EffectBesomModule.run (cyclomatic 24) core/src/main/scala/besom/internal/BesomModule.scala:55
- TypeMapper.asScalaType (cyclomatic 22) codegen/src/TypeMapper.scala:136
- CodeGen.sourceFilesForResource (cyclomatic 20) codegen/src/CodeGen.scala:280
- Result.runF (cyclomatic 19) core/src/main/scala/besom/internal/Result.scala:225
- Result.runM (cyclomatic 19) core/src/main/scala/besom/internal/Result.scala:255
- Version.main (cyclomatic 19) scripts/Version.scala:25
- Git.setupGitRepo (cyclomatic 18) auto/src/main/scala/besom/auto/internal/Git.scala:29
- ResourceOps.readOrRegisterResourceInternal (cyclomatic 18) core/src/main/scala/besom/internal/ResourceOps.scala:51
- CodeGen.sourceFilesForConfig (cyclomatic 17) codegen/src/CodeGen.scala:686
- ResourceOps.prepareResourceInputs (cyclomatic 16) core/src/main/scala/besom/internal/ResourceOps.scala:374
- Deprecated module: github.com/golang/protobuf
- Repeated repair: auto/src/main/scala/besom/auto/internal/auto.scala auto/src/main/scala/besom/auto/internal/auto.scala:154
- HackComment codegen/src/ScalaDefinitionCoordinates.scala:72
- EffectBesomModule.run (cognitive 215) core/src/main/scala/besom/internal/BesomModule.scala:55
- ResourceOps.prepareResourceInputs (cognitive 120) core/src/main/scala/besom/internal/ResourceOps.scala:374
- ResourceOps.readOrRegisterResourceInternal (cognitive 108) core/src/main/scala/besom/internal/ResourceOps.scala:51
- JsonInterpolator.jsonImpl (cognitive 51) core/src/main/scala/besom/util/JsonInterpolator.scala:16
- NonEmptyString.fromImpl (cognitive 40) core/src/main/scala/besom/util/NonEmptyString.scala:69
- LocalWorkspace.apply (cognitive 38) auto/src/main/scala/besom/auto/internal/LocalWorkspace.scala:687
- CodeGen.sourceFilesForResource (cognitive 29) codegen/src/CodeGen.scala:280
- VersionRange.parse (cognitive 29) codegen/src/VersionRange.scala:26
- Version.main (cognitive 29) scripts/Version.scala:25
- DecoderHelpers.decodeAsPossibleSecretOrOutput (cognitive 27) REDACTED:724
- ResourceOps.executeInvoke (cognitive 25) core/src/main/scala/besom/internal/ResourceOps.scala:125
- TypeMapper.enumValue (cognitive 23) codegen/src/TypeMapper.scala:180
- ResourceOps.createResourceState (cognitive 23) core/src/main/scala/besom/internal/ResourceOps.scala:654
- JarVersions.getVersion (cognitive 23) scripts/JarVersions.scala:32
- ResourceOps.registerReadOrGetResource (cognitive 22) core/src/main/scala/besom/internal/ResourceOps.scala:180
- ResourceOps.executeRegisterResourceRequest (cognitive 21) core/src/main/scala/besom/internal/ResourceOps.scala:446
- RawResourceResult.fromValue (cognitive 20) core/src/main/scala/besom/internal/RawResourceResult.scala:56
- Packages.downloadPackagesMetadata (cognitive 20) REDACTED:746
- EventLogs.around (cognitive 19) auto/src/main/scala/besom/auto/internal/EventLogs.scala:110
- Diff.performDiff (cognitive 19) besom-cfg/k8s/src/main/scala/diffs.scala:250
- CodeGen.makeArgsCompanion (cognitive 19) codegen/src/CodeGen.scala:955
- TypeMapper.asScalaType (cognitive 19) codegen/src/TypeMapper.scala:136
- ResourceOptions.resolve (cognitive 19) core/src/main/scala/besom/internal/ResourceOptions.scala:158
- Result.runF (cognitive 19) core/src/main/scala/besom/internal/Result.scala:225
- Result.runM (cognitive 19) core/src/main/scala/besom/internal/Result.scala:255
- Packages.publishMaven (cognitive 19) REDACTED:511
- Git.setupGitRepo (cognitive 18) auto/src/main/scala/besom/auto/internal/Git.scala:29
- Stack.up (cognitive 18) auto/src/main/scala/besom/auto/internal/Stack.scala:146
- Hotfix.applyToPackage (cognitive 17) codegen/src/Hotfix.scala:153
- ResourceOps.getProvider (cognitive 17) core/src/main/scala/besom/internal/ResourceOps.scala:626
- LocalWorkspace.setAllConfig (cognitive 16) auto/src/main/scala/besom/auto/internal/LocalWorkspace.scala:248
- CodeGen.sourceFilesForConfig (cognitive 16) codegen/src/CodeGen.scala:686
- CodeGen.makeOutputClassSourceFile (cognitive 16) codegen/src/CodeGen.scala:774
- JsonReaderInstances.outputJsonReader (cognitive 16) core/src/main/scala/besom/util/JsonReaderInstances.scala:8
- Packages.publishLocal (cognitive 16) REDACTED:446
- REDACTED
- Change coupling clique: project.scala, project.scala, project.scala besom-cats/project.scala
- REDACTED
- REDACTED
- Members sharing a duplicated core (6 members, 50+ identical tokens) core/src/main/scala/besom/internal/ResourceOptions.scala:256
- Members sharing a duplicated core (4 members, 50+ identical tokens) auto/src/main/scala/besom/auto/internal/Stack.scala:67
- Duplicated block (4–16 lines × 3) auto/src/main/scala/besom/auto/internal/Stack.scala:79
- Duplicated block (15 lines × 4) core/src/main/scala/besom/internal/ResourceOptions.scala:296
- Duplicated block (14 lines × 5) core/src/main/scala/besom/internal/ResourceOptions.scala:297
- Duplicated block (12 lines × 3) codegen/src/CodeGen.scala:211
- Duplicated block (9 lines × 2) REDACTED:453
- Duplicated block (7 lines × 6) core/src/main/scala/besom/internal/ResourceOptions.scala:264
- Duplicated block (7 lines × 2) REDACTED:1177
- Duplicated block (7 lines × 3) core/src/main/scala/besom/util/NonEmptyString.scala:126
- Duplicated block (5 lines × 4) auto/src/main/scala/besom/auto/internal/Stack.scala:90
- Duplicated block (5 lines × 2) REDACTED:1193
- Duplicated block (13 lines × 2) codegen/resources/overlays/kubernetes/apiextensions/CustomResource.scala:17
- Duplicated block (18 lines × 2) examples/aws-wordpress-fargate-rds/Network.scala:88
- Duplicated block (11–12 lines × 2) examples/aws-wordpress-fargate-rds/Network.scala:83
- Duplicated block (7–8 lines × 2) examples/kubernetes-keycloak/Keycloak.scala:96
- README may be stale
- Sync-over-async blocking core/src/main/scala/besom/internal/Result.scala:415
- Future started here is not kept core/src/main/scala/besom/internal/Result.scala:410
- Swallowed exception (empty catch) auto/src/main/scala/besom/auto/internal/shell.scala:61
Minor — 21 finding(s)
- Fat interface: Workspace (42 abstract members) auto/src/main/scala/besom/auto/internal/Workspace.scala:92
- Fat interface: ResourceProvider (20 abstract members) besom-rpc/src/main/scala/pulumirpc/provider/ResourceProviderGrpc.scala:236
- Fat interface: ResourceProviderBlockingClient (20 abstract members) besom-rpc/src/main/scala/pulumirpc/provider/ResourceProviderGrpc.scala:463
- Off-boarding risk: anonymized user #1
- No ADRs found
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Disabled test core/src/test/scala/besom/internal/RegistersOutputsDerivationTest.scala:54
- No ADRs
- No src/ separation
- Logging is not universal
- No SAST REDACTED:14
- No dependency-update automation website/package.json:16
- No rollback/health safety
- No app-layer HTTPS enforcement detected
- No security response headers detected
- No inbound request validation detected
- Scala's null is not held to the type system everywhere
Minor — 4 finding(s)
- Outdated: github.com/pulumi/pulumi/sdk/v3
- Outdated: github.com/stretchr/testify
- Outdated: google.golang.org/grpc
- Outdated: google.golang.org/protobuf
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-b716fe1857b2417eadecf4b40dde186b/history.json --exit-code 0 --source . | 5 | 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-b716fe1857b2417eadecf4b40dde186b/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 --exclude besom-rpc/src . | 41 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 12 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 40 file(s) — `auto/src/main/scala/besom/auto/internal/Events.scala`, `auto/src/main/scala/besom/auto/internal/LocalWorkspace.scala`, `auto/src/main/scala/besom/auto/internal/Stack.scala`, `auto/src/main/scala/besom/auto/internal/Workspace.scala`, `auto/src/main/scala/besom/auto/internal/auto.scala`, … (+35 more) — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |