Executive summary
broadinstitute/cromwell 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 eight of the dependencies have a known vulnerability. It scores 50 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 36, is the weakest lens and counts most in the score. The best first step is replacing the weak hashes, worth about 12 points. Updating the eight dependencies with a known vulnerability would lift Security and Compliance itself, worth about 3 points. Raising Security and Compliance to 70 would lift the score to about 62.
Thirty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eleven known security holes in the packages the code depends on can be used by attackers, and seven secrets can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting each secret to its own step would close these risks. The six unsafe settings in infrastructure or container files need changing to safe values. The password or key in the code needs replacing, with the old one switched off. The four sets of files in separate parts that keep changing together need that dependency made explicit.
The product code is 96,208 lines, about €160,000 to rebuild.
If Security and Compliance rose from 36 to 70, the lowest score rated Strong, the score would rise from 50 to about 62.
New since the last survey: 68 findings
- Code Duplication · Edited copy of a member (86 corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/wdlom2wom/graph/IfElementToGraphNode.scala
- Code Duplication · Edited copy of a member (40 corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/wdlom2wom/TaskDefinitionElementToWomTaskDefinition.scala
- Code Duplication · Edited copy of a member (47 corresponding lines) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/api/request/AbortRequestHandler.scala
- Code Duplication · Edited copy of a member (21 corresponding lines) cromwellApiClient/src/main/scala/cromwell/api/CromwellClient.scala
- Code Duplication · Edited copy of a member (27 corresponding lines) services/src/main/scala/cromwell/services/metadata/impl/builder/MetadataBuilderActor.scala
- Code Duplication · Edited copy of a member (25 corresponding lines) centaur/src/main/scala/centaur/api/Retry.scala
- Code Duplication · Edited copy of a member (25 corresponding lines) database/migration/src/main/scala/cromwell/database/migration/custom/PreemptedIsABackendStatus.scala
- Code Duplication · Edited copy of a member (22 corresponding lines) backend/src/main/scala/cromwell/backend/standard/StandardAsyncExecutionActor.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) wom/src/main/scala/wom/values/WomInteger.scala
- Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) backend/src/main/scala/cromwell/backend/validation/RuntimeAttributesValidation.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) wom/src/main/scala/wom/values/WomFloat.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) core/src/main/scala/cromwell/core/WorkflowOptions.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/linking/expression/values/EngineFunctionEvaluators.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) engine/src/main/scala/cromwell/webservice/routes/MetadataRouteSupport.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/WdlStandardLibraryFunctions.scala
- Code Duplication · Edited copy of a member (22 corresponding lines) services/src/main/scala/cromwell/services/metadata/impl/archiver/ArchiveMetadataSchedulerActor.scala
- Code Duplication · Edited copy of a member (19 corresponding lines) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/api/BatchApiRequestManager.scala
- Code Duplication · Edited copy of a member (13 corresponding lines) database/sql/src/main/scala/cromwell/database/slick/CallCachingSlickDatabase.scala
- Code Duplication · Edited copy of a member (17 corresponding lines) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/callcaching/BatchBackendCacheHitCopyingActor.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) womtool/src/main/scala/womtool/inputs/Inputs.scala
- Code Duplication · Edited copy of a member (24 corresponding lines) engine/src/main/scala/cromwell/engine/workflow/WorkflowActor.scala
- Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) services/src/main/scala/cromwell/services/metadata/WorkflowQueryKey.scala
- Code Duplication · Edited copy of a member (16 corresponding lines) backend/src/main/scala/cromwell/backend/dummy/DummySingletonActor.scala
- Code Duplication · Edited copy of a member (25 corresponding lines) wdl/model/draft2/src/main/scala/wdl/draft2/model/examples/ex2.scala
- Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) languageFactories/wdl-biscayne/src/main/scala/languages/wdl/biscayne/WdlBiscayneLanguageFactory.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) languageFactories/wdl-draft2/src/main/scala/languages/wdl/draft2/WdlDraft2LanguageFactory.scala
- Code Duplication · Edited copy of a member (13 corresponding lines) services/src/main/scala/cromwell/services/cost/GcpCostCatalogService.scala
- Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) wdl/transforms/biscayne/src/main/scala/wdl/transforms/biscayne/parsing/BiscayneParser.scala
- Code Duplication · Edited copy of a member (5 corresponding lines) wom/src/main/scala/wom/types/WomType.scala
- Code Duplication · Edited copy of a member (14 corresponding lines) cloud-nio/cloud-nio-spi/src/main/scala/cloud/nio/spi/UnixPath.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/linking/expression/types/BinaryOperatorEvaluators.scala
- Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/wdlom2wom/expression/renaming/BinaryOperatorEvaluators.scala
- Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) engine/src/main/scala/cromwell/engine/workflow/WorkflowActor.scala
- Code Duplication · Edited copies of one member (5 members, 11+ corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/linking/expression/files/BinaryOperatorEvaluators.scala
- Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) wom/src/main/scala/wom/values/WomFloat.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) services/src/main/scala/cromwell/services/metadata/MetadataService.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/util/GpuValidation.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) wom/src/main/scala/wom/values/WomFloat.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) wom/src/main/scala/wom/values/WomFloat.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) backend/src/main/scala/cromwell/backend/validation/InformationValidation.scala
- Code Duplication · Edited copy of a member (14 corresponding lines) supportedBackends/tes/src/main/scala/cromwell/backend/impl/tes/TesInitializationActor.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) backend/src/main/scala/cromwell/backend/io/GlobFunctions.scala
- Code Duplication · Edited copies of one member (5 members, 6+ corresponding lines) wom/src/main/scala/wom/values/WomFile.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) womtool/src/main/scala/womtool/WomtoolMain.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/wdlom2wom/expression/renaming/EngineFunctionEvaluators.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) backend/src/main/scala/cromwell/backend/validation/MaxRetriesValidation.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) wdl/model/draft2/src/main/scala/wdl/draft2/model/TaskOutput.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/ast2wdlom/AstToMetaSectionElement.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) wom/src/main/scala/wom/graph/GraphOutputNode.scala
- Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) wom/src/main/scala/wom/values/WomBoolean.scala
- Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) wom/src/main/scala/wom/values/WomBoolean.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) wom/src/main/scala/wom/types/WomFloatType.scala
- Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/actors/GcpBatchAsyncBackendJobExecutionActor.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/models/GcpBatchRuntimeAttributes.scala
- Code Duplication · Edited copy of a member (7 corresponding lines) backend/src/main/scala/cromwell/backend/BackendLifecycleActor.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) cloud-nio/cloud-nio-spi/src/main/scala/cloud/nio/spi/CloudNioFileSystem.scala
- Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/linking/expression/consumed/BinaryOperatorEvaluators.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) CromIAM/src/main/scala/cromiam/instrumentation/CromIamInstrumentation.scala
- Code Duplication · Edited copy of a member (5 corresponding lines) cloud-nio/cloud-nio-impl-ftp/src/main/scala/cloud/nio/impl/ftp/LeasedInputStream.scala
- Code Duplication · Edited copy of a member (5 corresponding lines) wom/src/main/scala/wom/types/WomBooleanType.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) cloud-nio/cloud-nio-util/src/main/scala/cloud/nio/util/VersionUtil.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/keys/ConditionalCollectorKey.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) common/src/main/scala/common/validation/ErrorOr.scala
- Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) wdl/transforms/biscayne/src/main/scala/wdl/transforms/biscayne/ast2wdlom/BiscayneGenericAstNode.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) scripts/metadata_comparison/metadata_comparison/lib/operations_digesters.py
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Change Coupling · Change coupling: JobPaths.scala ↔ StandardAsyncExecutionActor.scala backend/src/main/scala/cromwell/backend/io/JobPaths.scala
Fixed since the last survey: 14 findings
- Cognitive Complexity · comparer.error_checks (cognitive 29) scripts/metadata_comparison/metadata_comparison/comparer.py
- Code Duplication · Duplicated block (29–31 lines × 3) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/api/request/AbortRequestHandler.scala
- Code Duplication · Duplicated block (12 lines × 2) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/wdlom2wom/graph/IfElementToGraphNode.scala
- Code Duplication · Duplicated block (6 lines × 2) wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/TypeEvaluator.scala
- Code Duplication · Duplicated block (11 lines × 2) scripts/metadata_comparison/metadata_comparison/lib/operations_digesters.py
- Secrets (history) · Secret: generic-api-key 0.13/lib/jquery-ui.js
- Secrets (history) · Secret: generic-api-key 0.3/api/lib/jquery-ui.js
- Secrets (history) · Secret: generic-api-key 0.4/lib/jquery-ui.js
- Secrets (history) · Secret: generic-api-key 0.5/lib/jquery-ui.js
- Secrets (history) · Secret: generic-api-key 0.6/api/lib/jquery-ui.js
- Secrets (history) · Secret: generic-api-key 0.6/lib/jquery-ui.js
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Documentation (README) · README may be stale
Rebuild cost: about €160,000 · Estimate
| Cost to rebuild | €52,000 to €260,000, for 869 to 2,758 hours of work, about 1.1 person-years for 1 to 3 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 50. 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: 96,208 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 cromwell.core.callcaching | 2 cromwell.database.sql.tables | 3 cromwell.services.instrumentation | 4 cromwell.core.path | 5 wom.values | 6 wdl.model.draft3.elements.ExpressionElement | 7 wom.types | 8 wom.graph.GraphNodePort | 9 wom.expression | 10 wom | 11 cromwell.languages.util.ImportResolver | 12 wdl.draft2.model | 13 wom.callable | 14 wdl.model.draft3.elements | 15 wom.graph | 16 cromwell.core | 17 wdl.model.draft3.graph | 18 wom.executable | 19 cromwell.backend.async | 20 cromwell.core.io | 21 cromwell.languages | 22 cromwell.services.metadata | 23 wdl.model.draft3.graph.expression | 24 cromwell.docker | 25 wdl.transforms.base.wdlom2wom | 26 cromwell.backend | 27 cromwell.backend.standard.callcaching | 28 cromwell.backend.validation | 29 cromwell.engine | 30 cromwell.backend.standard | 31 cromwell.engine.workflow.lifecycle.execution | 32 cromwell.engine.workflow.workflowstore | 33 cromwell.backend.google.batch.models | 34 cromwell.backend.impl.aws | 35 cromwell.engine.workflow.lifecycle.execution.callcaching | 36 cromwell.engine.workflow.lifecycle.execution.job.preparation | 37 cromwell.jobstore | 38 cromwell.backend.google.batch.util | 39 cromwell.engine.workflow.lifecycle.execution.job | 40 cromwell.backend.google.batch.api |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 cromwell.core.callcaching | ||||||||||||||||||||||||||||||||||||||||
| 2 cromwell.database.sql.tables | ||||||||||||||||||||||||||||||||||||||||
| 3 cromwell.services.instrumentation | ||||||||||||||||||||||||||||||||||||||||
| 4 cromwell.core.path | 3 | |||||||||||||||||||||||||||||||||||||||
| 5 wom.values | 12 | 4 | ||||||||||||||||||||||||||||||||||||||
| 6 wdl.model.draft3.elements.ExpressionElement | 1 | 85 | ||||||||||||||||||||||||||||||||||||||
| 7 wom.types | 15 | |||||||||||||||||||||||||||||||||||||||
| 8 wom.graph.GraphNodePort | 6 | 14 | ||||||||||||||||||||||||||||||||||||||
| 9 wom.expression | 4 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 wom | 5 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 11 cromwell.languages.util.ImportResolver | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 wdl.draft2.model | 5 | 7 | 3 | 4 | ||||||||||||||||||||||||||||||||||||
| 13 wom.callable | 3 | 2 | 7 | 6 | ||||||||||||||||||||||||||||||||||||
| 14 wdl.model.draft3.elements | 2 | 1 | 5 | 2 | ||||||||||||||||||||||||||||||||||||
| 15 wom.graph | 1 | 11 | 25 | 6 | 4 | 5 | ||||||||||||||||||||||||||||||||||
| 16 cromwell.core | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 17 wdl.model.draft3.graph | 7 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 18 wom.executable | 1 | 2 | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||
| 19 cromwell.backend.async | 10 | 1 | 4 | 3 | ||||||||||||||||||||||||||||||||||||
| 20 cromwell.core.io | 2 | 15 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 cromwell.languages | 1 | 1 | 1 | 1 | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||
| 22 cromwell.services.metadata | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 23 wdl.model.draft3.graph.expression | 4 | 4 | 3 | 1 | 3 | 4 | ||||||||||||||||||||||||||||||||||
| 24 cromwell.docker | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 wdl.transforms.base.wdlom2wom | 2 | 3 | 3 | 6 | 2 | 5 | 21 | 4 | 6 | 2 | 2 | 10 | ||||||||||||||||||||||||||||
| 26 cromwell.backend | 1 | 6 | 9 | 1 | 6 | 1 | 3 | 3 | 11 | 1 | 2 | 1 | ||||||||||||||||||||||||||||
| 27 cromwell.backend.standard.callcaching | 2 | 3 | 14 | |||||||||||||||||||||||||||||||||||||
| 28 cromwell.backend.validation | 20 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 cromwell.engine | 1 | 4 | 2 | 1 | 1 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||
| 30 cromwell.backend.standard | 8 | 5 | 1 | 2 | 2 | 8 | 9 | 5 | 4 | 50 | 4 | 3 | ||||||||||||||||||||||||||||
| 31 cromwell.engine.workflow.lifecycle.execution | 1 | 1 | 3 | 1 | 1 | 16 | 1 | 3 | 3 | |||||||||||||||||||||||||||||||
| 32 cromwell.engine.workflow.workflowstore | 1 | 1 | 18 | 2 | ||||||||||||||||||||||||||||||||||||
| 33 cromwell.backend.google.batch.models | 5 | 4 | 2 | 2 | 1 | 2 | 4 | 3 | 1 | |||||||||||||||||||||||||||||||
| 34 cromwell.backend.impl.aws | 4 | 4 | 4 | 3 | 2 | 3 | 2 | 14 | 5 | 15 | ||||||||||||||||||||||||||||||
| 35 cromwell.engine.workflow.lifecycle.execution.callcaching | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 36 cromwell.engine.workflow.lifecycle.execution.job.preparation | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||
| 37 cromwell.jobstore | 2 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 cromwell.backend.google.batch.util | 2 | 1 | 2 | 6 | 1 | 12 | ||||||||||||||||||||||||||||||||||
| 39 cromwell.engine.workflow.lifecycle.execution.job | 3 | 1 | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 40 cromwell.backend.google.batch.api | 2 | 1 | 1 | 3 | 1 |
4→16 cromwell.core.path uses cromwell.core part of a loop✕
- Connections
- 3 pairs of types, where a type in cromwell.core.path uses a type in cromwell.core.
- The types involved
cromwell.core.path.DefaultPathBuilderFactory→cromwell.core.WorkflowOptionscromwell.core.path.PathBuilderFactory→cromwell.core.WorkflowOptionscromwell.core.path.PathParsingException→cromwell.core.CromwellFatalException
- Direction
- cromwell.core.path uses cromwell.core, so a change to cromwell.core can break cromwell.core.path, while a change to cromwell.core.path can't break cromwell.core.
- 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.
5→7 wom.values uses wom.types part of a loop✕
- Connections
- 12 pairs of types, where a type in wom.values uses a type in wom.types.
- The types involved
wom.values.WomArray→wom.types.WomArrayTypewom.values.WomFile→wom.types.WomFileTypewom.values.WomFile→wom.types.WomTypewom.values.WomGlobFile→wom.types.WomFileTypewom.values.WomMap→wom.types.WomMapTypewom.values.WomObject→wom.types.WomObjectTypeLikewom.values.WomObjectLike→wom.types.WomObjectTypeLikewom.values.WomOptionalValue→wom.types.WomOptionalTypewom.values.WomOptionalValue→wom.types.WomTypewom.values.WomSingleFile→wom.types.WomFileTypewom.values.WomUnlistedDirectory→wom.types.WomFileTypewom.values.WomValue→wom.types.WomType
- Direction
- wom.values uses wom.types, so a change to wom.types can break wom.values, while a change to wom.values can't break wom.types.
- 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.
5→9 wom.values uses wom.expression part of a loop✕
- Connections
- 4 pairs of types, where a type in wom.values uses a type in wom.expression.
- The types involved
wom.values.WomObjectLike→wom.expression.IoFunctionSetwom.values.WomOptionalValue→wom.expression.IoFunctionSetwom.values.WomValue→wom.expression.IoFunctionSetwom.values.WomValue→wom.expression.ValueAsAnExpression
- Direction
- wom.values uses wom.expression, so a change to wom.expression can break wom.values, while a change to wom.values can't break wom.expression.
- 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.
6→5 wdl.model.draft3.elements.ExpressionElement uses wom.values✕
- Connections
- 1 pair of types, where a type in wdl.model.draft3.elements.ExpressionElement uses a type in wom.values.
- The types involved
wdl.model.draft3.elements.ExpressionElement.PrimitiveLiteralExpressionElement→wom.values.WomPrimitive
- Direction
- wdl.model.draft3.elements.ExpressionElement uses wom.values, so a change to wom.values can break wdl.model.draft3.elements.ExpressionElement, while a change to wdl.model.draft3.elements.ExpressionElement can't break wom.values.
- Position
- Below the diagonal: wdl.model.draft3.elements.ExpressionElement uses a module listed above it, which is the healthy direction.
6→14 wdl.model.draft3.elements.ExpressionElement uses wdl.model.draft3.elements part of a loop✕
- Connections
- 85 pairs of types, where a type in wdl.model.draft3.elements.ExpressionElement uses a type in wdl.model.draft3.elements. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
wdl.model.draft3.elements.ExpressionElement.Add→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.ArrayLiteral→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.AsMap→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.AsPairs→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.Basename→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.BinaryOperation→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.Ceil→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.CollectByKey→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.Cross→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.Defined→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.Divide→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.Equals→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.ExpressionLiteralElement→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.ExpressionMemberAccess→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.Flatten→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.Floor→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.FunctionCallElement→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.Glob→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.GreaterThan→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.GreaterThanOrEquals→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.IdentifierLookup→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.IdentifierMemberAccess→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.IndexAccess→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.Keys→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.elements.ExpressionElement.KvPair→wdl.model.draft3.elements.ExpressionElement
- Direction
- wdl.model.draft3.elements.ExpressionElement uses wdl.model.draft3.elements, so a change to wdl.model.draft3.elements can break wdl.model.draft3.elements.ExpressionElement, while a change to wdl.model.draft3.elements.ExpressionElement can't break wdl.model.draft3.elements.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→5 wom.types uses wom.values✕
- Connections
- 15 pairs of types, where a type in wom.types uses a type in wom.values.
- The types involved
wom.types.WomArrayType→wom.values.WomArraywom.types.WomArrayType→wom.values.WomValuewom.types.WomCompositeType→wom.values.WomValuewom.types.WomFileType→wom.values.WomFilewom.types.WomGlobFileType→wom.values.WomGlobFilewom.types.WomNothingType→wom.values.WomValuewom.types.WomObjectType→wom.values.WomMapwom.types.WomObjectType→wom.values.WomValuewom.types.WomObjectTypeLike→wom.values.WomValuewom.types.WomOptionalType→wom.values.WomValuewom.types.WomPairType→wom.values.WomPairwom.types.WomPairType→wom.values.WomValuewom.types.WomSingleFileType→wom.values.WomSingleFilewom.types.WomType→wom.values.WomValuewom.types.WomUnlistedDirectoryType→wom.values.WomUnlistedDirectory
- Direction
- wom.types uses wom.values, so a change to wom.values can break wom.types, while a change to wom.types can't break wom.values.
- Position
- Below the diagonal: wom.types uses a module listed above it, which is the healthy direction.
8→7 wom.graph.GraphNodePort uses wom.types✕
- Connections
- 6 pairs of types, where a type in wom.graph.GraphNodePort uses a type in wom.types.
- The types involved
wom.graph.GraphNodePort.ConditionalOutputPort→wom.types.WomOptionalTypewom.graph.GraphNodePort.ConnectedInputPort→wom.types.WomTypewom.graph.GraphNodePort.GraphNodeOutputPort→wom.types.WomTypewom.graph.GraphNodePort.NodeCompletionPort→wom.types.WomTypewom.graph.GraphNodePort.ScatterGathererPort→wom.types.WomArrayTypewom.graph.GraphNodePort.SubworkflowCallOutputPort→wom.types.WomType
- Direction
- wom.graph.GraphNodePort uses wom.types, so a change to wom.types can break wom.graph.GraphNodePort, while a change to wom.graph.GraphNodePort can't break wom.types.
- Position
- Below the diagonal: wom.graph.GraphNodePort uses a module listed above it, which is the healthy direction.
8→15 wom.graph.GraphNodePort uses wom.graph part of a loop✕
- Connections
- 14 pairs of types, where a type in wom.graph.GraphNodePort uses a type in wom.graph.
- The types involved
wom.graph.GraphNodePort.ConditionalOutputPort→wom.graph.ConditionalNodewom.graph.GraphNodePort.ConditionalOutputPort→wom.graph.PortBasedGraphOutputNodewom.graph.GraphNodePort.ConditionalOutputPort→wom.graph.WomIdentifierwom.graph.GraphNodePort.GraphNodeOutputPort→wom.graph.GraphNodewom.graph.GraphNodePort.InputPort→wom.graph.GraphNodePortwom.graph.GraphNodePort.NodeCompletionPort→wom.graph.WomIdentifierwom.graph.GraphNodePort.OutputPort→wom.graph.GraphNodePortwom.graph.GraphNodePort.OutputPort→wom.graph.WomIdentifierwom.graph.GraphNodePort.ScatterGathererPort→wom.graph.PortBasedGraphOutputNodewom.graph.GraphNodePort.ScatterGathererPort→wom.graph.WomIdentifierwom.graph.GraphNodePort.SubworkflowCallOutputPort→wom.graph.GraphNodewom.graph.GraphNodePort.SubworkflowCallOutputPort→wom.graph.GraphOutputNodewom.graph.GraphNodePort.SubworkflowCallOutputPort→wom.graph.WomIdentifierwom.graph.GraphNodePort.SubworkflowCallOutputPort→wom.graph.WorkflowCallNode
- Direction
- wom.graph.GraphNodePort uses wom.graph, so a change to wom.graph can break wom.graph.GraphNodePort, while a change to wom.graph.GraphNodePort can't break wom.graph.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→5 wom.expression uses wom.values✕
- Connections
- 4 pairs of types, where a type in wom.expression uses a type in wom.values.
- The types involved
wom.expression.FileEvaluation→wom.values.WomFilewom.expression.InputPointerToWomValue→wom.values.WomValuewom.expression.ValueAsAnExpression→wom.values.WomValuewom.expression.WomExpression→wom.values.WomValue
- Direction
- wom.expression uses wom.values, so a change to wom.values can break wom.expression, while a change to wom.expression can't break wom.values.
- Position
- Below the diagonal: wom.expression uses a module listed above it, which is the healthy direction.
9→7 wom.expression uses wom.types✕
- Connections
- 2 pairs of types, where a type in wom.expression uses a type in wom.types.
- The types involved
wom.expression.ValueAsAnExpression→wom.types.WomTypewom.expression.WomExpression→wom.types.WomType
- Direction
- wom.expression uses wom.types, so a change to wom.types can break wom.expression, while a change to wom.expression can't break wom.types.
- Position
- Below the diagonal: wom.expression uses a module listed above it, which is the healthy direction.
9→8 wom.expression uses wom.graph.GraphNodePort✕
- Connections
- 1 pair of types, where a type in wom.expression uses a type in wom.graph.GraphNodePort.
- The types involved
wom.expression.InputPointerToWomValue→wom.graph.GraphNodePort.OutputPort
- Direction
- wom.expression uses wom.graph.GraphNodePort, so a change to wom.graph.GraphNodePort can break wom.expression, while a change to wom.expression can't break wom.graph.GraphNodePort.
- Position
- Below the diagonal: wom.expression uses a module listed above it, which is the healthy direction.
10→5 wom uses wom.values✕
- Connections
- 5 pairs of types, where a type in wom uses a type in wom.values.
- The types involved
wom.CommandPart→wom.values.WomValuewom.CommandSetupSideEffectFile→wom.values.WomFilewom.JobOutput→wom.values.WomValuewom.WomFileMapper→wom.values.WomFilewom.WomFileMapper→wom.values.WomValue
- Direction
- wom uses wom.values, so a change to wom.values can break wom, while a change to wom can't break wom.values.
- Position
- Below the diagonal: wom uses a module listed above it, which is the healthy direction.
10→9 wom uses wom.expression✕
- Connections
- 2 pairs of types, where a type in wom uses a type in wom.expression.
- The types involved
wom.CommandPart→wom.expression.IoFunctionSetwom.RuntimeAttributes→wom.expression.WomExpression
- Direction
- wom uses wom.expression, so a change to wom.expression can break wom, while a change to wom can't break wom.expression.
- Position
- Below the diagonal: wom uses a module listed above it, which is the healthy direction.
10→15 wom uses wom.graph part of a loop✕
- Connections
- 1 pair of types, where a type in wom uses a type in wom.graph.
- The types involved
wom.CommandPart→wom.graph.LocalName
- Direction
- wom uses wom.graph, so a change to wom.graph can break wom, while a change to wom can't break wom.graph.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→4 cromwell.languages.util.ImportResolver uses cromwell.core.path✕
- Connections
- 1 pair of types, where a type in cromwell.languages.util.ImportResolver uses a type in cromwell.core.path.
- The types involved
cromwell.languages.util.ImportResolver.DirectoryResolver→cromwell.core.path.Path
- Direction
- cromwell.languages.util.ImportResolver uses cromwell.core.path, so a change to cromwell.core.path can break cromwell.languages.util.ImportResolver, while a change to cromwell.languages.util.ImportResolver can't break cromwell.core.path.
- Position
- Below the diagonal: cromwell.languages.util.ImportResolver uses a module listed above it, which is the healthy direction.
11→10 cromwell.languages.util.ImportResolver uses wom✕
- Connections
- 1 pair of types, where a type in cromwell.languages.util.ImportResolver uses a type in wom.
- The types involved
cromwell.languages.util.ImportResolver.ResolvedImportBundle→wom.ResolvedImportRecord
- Direction
- cromwell.languages.util.ImportResolver uses wom, so a change to wom can break cromwell.languages.util.ImportResolver, while a change to cromwell.languages.util.ImportResolver can't break wom.
- Position
- Below the diagonal: cromwell.languages.util.ImportResolver uses a module listed above it, which is the healthy direction.
12→5 wdl.draft2.model uses wom.values✕
- Connections
- 5 pairs of types, where a type in wdl.draft2.model uses a type in wom.values.
- The types involved
wdl.draft2.model.NoLookup→wom.values.WomValuewdl.draft2.model.Scope→wom.values.WomValuewdl.draft2.model.WdlExpression→wom.values.WomValuewdl.draft2.model.WdlNamespace→wom.values.WomValuewdl.draft2.model.WdlWomExpression→wom.values.WomValue
- Direction
- wdl.draft2.model uses wom.values, so a change to wom.values can break wdl.draft2.model, while a change to wdl.draft2.model can't break wom.values.
- Position
- Below the diagonal: wdl.draft2.model uses a module listed above it, which is the healthy direction.
12→7 wdl.draft2.model uses wom.types✕
- Connections
- 7 pairs of types, where a type in wdl.draft2.model uses a type in wom.types.
- The types involved
wdl.draft2.model.CallOutput→wom.types.WomTypewdl.draft2.model.DeclarationInterface→wom.types.WomTypewdl.draft2.model.ReportableSymbol→wom.types.WomTypewdl.draft2.model.TaskInput→wom.types.WomTypewdl.draft2.model.WdlExpression→wom.types.WomTypewdl.draft2.model.WdlSyntaxErrorFormatter→wom.types.WomTypewdl.draft2.model.WdlWomExpression→wom.types.WomType
- Direction
- wdl.draft2.model uses wom.types, so a change to wom.types can break wdl.draft2.model, while a change to wdl.draft2.model can't break wom.types.
- Position
- Below the diagonal: wdl.draft2.model uses a module listed above it, which is the healthy direction.
12→9 wdl.draft2.model uses wom.expression✕
- Connections
- 3 pairs of types, where a type in wdl.draft2.model uses a type in wom.expression.
- The types involved
wdl.draft2.model.WdlWomExpression→wom.expression.FileEvaluationwdl.draft2.model.WdlWomExpression→wom.expression.IoFunctionSetwdl.draft2.model.WdlWomExpression→wom.expression.WomExpression
- Direction
- wdl.draft2.model uses wom.expression, so a change to wom.expression can break wdl.draft2.model, while a change to wdl.draft2.model can't break wom.expression.
- Position
- Below the diagonal: wdl.draft2.model uses a module listed above it, which is the healthy direction.
12→10 wdl.draft2.model uses wom✕
- Connections
- 4 pairs of types, where a type in wdl.draft2.model uses a type in wom.
- The types involved
wdl.draft2.model.WdlNamespace→wom.ResolvedImportRecordwdl.draft2.model.WdlNamespaceWithWorkflow→wom.ResolvedImportRecordwdl.draft2.model.WdlNamespaceWithoutWorkflow→wom.ResolvedImportRecordwdl.draft2.model.WdlTask→wom.InstantiatedCommand
- Direction
- wdl.draft2.model uses wom, so a change to wom can break wdl.draft2.model, while a change to wdl.draft2.model can't break wom.
- Position
- Below the diagonal: wdl.draft2.model uses a module listed above it, which is the healthy direction.
13→5 wom.callable uses wom.values✕
- Connections
- 3 pairs of types, where a type in wom.callable uses a type in wom.values.
- The types involved
wom.callable.AdHocValue→wom.values.WomFilewom.callable.CallableTaskDefinition→wom.values.WomGlobFilewom.callable.ContainerizedInputExpression→wom.values.WomValue
- Direction
- wom.callable uses wom.values, so a change to wom.values can break wom.callable, while a change to wom.callable can't break wom.values.
- Position
- Below the diagonal: wom.callable uses a module listed above it, which is the healthy direction.
13→9 wom.callable uses wom.expression✕
- Connections
- 2 pairs of types, where a type in wom.callable uses a type in wom.expression.
- The types involved
wom.callable.CallableTaskDefinition→wom.expression.WomExpressionwom.callable.ContainerizedInputExpression→wom.expression.IoFunctionSet
- Direction
- wom.callable uses wom.expression, so a change to wom.expression can break wom.callable, while a change to wom.callable can't break wom.expression.
- Position
- Below the diagonal: wom.callable uses a module listed above it, which is the healthy direction.
13→10 wom.callable uses wom✕
- Connections
- 7 pairs of types, where a type in wom.callable uses a type in wom.
- The types involved
wom.callable.Callable→wom.SourceFileLocationwom.callable.CallableExpressionTaskDefinition→wom.RuntimeAttributeswom.callable.CallableTaskDefinition→wom.RuntimeAttributeswom.callable.CallableTaskDefinition→wom.SourceFileLocationwom.callable.CommandTaskDefinition→wom.InstantiatedCommandwom.callable.TaskDefinition→wom.RuntimeAttributeswom.callable.WorkflowDefinition→wom.SourceFileLocation
- Direction
- wom.callable uses wom, so a change to wom can break wom.callable, while a change to wom.callable can't break wom.
- Position
- Below the diagonal: wom.callable uses a module listed above it, which is the healthy direction.
13→15 wom.callable uses wom.graph part of a loop✕
- Connections
- 6 pairs of types, where a type in wom.callable uses a type in wom.graph.
- The types involved
wom.callable.ExecutableCallable→wom.graph.CommandCallNodewom.callable.ExecutableCallable→wom.graph.Graphwom.callable.ExecutableExpressionTaskDefinition→wom.graph.Graphwom.callable.ExecutableTaskDefinition→wom.graph.Graphwom.callable.WorkflowDefinition→wom.graph.CommandCallNodewom.callable.WorkflowDefinition→wom.graph.Graph
- Direction
- wom.callable uses wom.graph, so a change to wom.graph can break wom.callable, while a change to wom.callable can't break wom.graph.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→6 wdl.model.draft3.elements uses wdl.model.draft3.elements.ExpressionElement✕
- Connections
- 2 pairs of types, where a type in wdl.model.draft3.elements uses a type in wdl.model.draft3.elements.ExpressionElement.
- The types involved
wdl.model.draft3.elements.CallBodyElement→wdl.model.draft3.elements.ExpressionElement.KvPairwdl.model.draft3.elements.RuntimeAttributesSectionElement→wdl.model.draft3.elements.ExpressionElement.KvPair
- Direction
- wdl.model.draft3.elements uses wdl.model.draft3.elements.ExpressionElement, so a change to wdl.model.draft3.elements.ExpressionElement can break wdl.model.draft3.elements, while a change to wdl.model.draft3.elements can't break wdl.model.draft3.elements.ExpressionElement.
- Position
- Below the diagonal: wdl.model.draft3.elements uses a module listed above it, which is the healthy direction.
14→7 wdl.model.draft3.elements uses wom.types✕
- Connections
- 1 pair of types, where a type in wdl.model.draft3.elements uses a type in wom.types.
- The types involved
wdl.model.draft3.elements.PrimitiveTypeElement→wom.types.WomPrimitiveType
- Direction
- wdl.model.draft3.elements uses wom.types, so a change to wom.types can break wdl.model.draft3.elements, while a change to wdl.model.draft3.elements can't break wom.types.
- Position
- Below the diagonal: wdl.model.draft3.elements uses a module listed above it, which is the healthy direction.
14→10 wdl.model.draft3.elements uses wom✕
- Connections
- 5 pairs of types, where a type in wdl.model.draft3.elements uses a type in wom.
- The types involved
wdl.model.draft3.elements.CallElement→wom.SourceFileLocationwdl.model.draft3.elements.LanguageElement→wom.SourceFileLocationwdl.model.draft3.elements.ScatterElement→wom.SourceFileLocationwdl.model.draft3.elements.TaskDefinitionElement→wom.SourceFileLocationwdl.model.draft3.elements.WorkflowDefinitionElement→wom.SourceFileLocation
- Direction
- wdl.model.draft3.elements uses wom, so a change to wom can break wdl.model.draft3.elements, while a change to wdl.model.draft3.elements can't break wom.
- Position
- Below the diagonal: wdl.model.draft3.elements uses a module listed above it, which is the healthy direction.
14→13 wdl.model.draft3.elements uses wom.callable✕
- Connections
- 2 pairs of types, where a type in wdl.model.draft3.elements uses a type in wom.callable.
- The types involved
wdl.model.draft3.elements.MetaSectionElement→wom.callable.MetaValueElementwdl.model.draft3.elements.ParameterMetaSectionElement→wom.callable.MetaValueElement
- Direction
- wdl.model.draft3.elements uses wom.callable, so a change to wom.callable can break wdl.model.draft3.elements, while a change to wdl.model.draft3.elements can't break wom.callable.
- Position
- Below the diagonal: wdl.model.draft3.elements uses a module listed above it, which is the healthy direction.
15→5 wom.graph uses wom.values✕
- Connections
- 1 pair of types, where a type in wom.graph uses a type in wom.values.
- The types involved
wom.graph.CommandCallNode→wom.values.WomValue
- Direction
- wom.graph uses wom.values, so a change to wom.values can break wom.graph, while a change to wom.graph can't break wom.values.
- Position
- Below the diagonal: wom.graph uses a module listed above it, which is the healthy direction.
15→7 wom.graph uses wom.types✕
- Connections
- 11 pairs of types, where a type in wom.graph uses a type in wom.types.
- The types involved
wom.graph.ExpressionBasedGraphOutputNode→wom.types.WomTypewom.graph.GraphInputNode→wom.types.WomTypewom.graph.GraphNodeInputExpression→wom.types.WomTypewom.graph.GraphNodePort→wom.types.WomTypewom.graph.GraphOutputNode→wom.types.WomTypewom.graph.OptionalGraphInputNode→wom.types.WomOptionalTypewom.graph.OptionalGraphInputNodeWithDefault→wom.types.WomTypewom.graph.PortBasedGraphOutputNode→wom.types.WomTypewom.graph.RequiredGraphInputNode→wom.types.WomTypewom.graph.RuntimeOverrideGraphInputNode→wom.types.WomTypewom.graph.ScatterVariableNode→wom.types.WomType
- Direction
- wom.graph uses wom.types, so a change to wom.types can break wom.graph, while a change to wom.graph can't break wom.types.
- Position
- Below the diagonal: wom.graph uses a module listed above it, which is the healthy direction.
15→8 wom.graph uses wom.graph.GraphNodePort✕
- Connections
- 25 pairs of types, where a type in wom.graph uses a type in wom.graph.GraphNodePort.
- The types involved
wom.graph.CommandCallNode→wom.graph.GraphNodePort.ExpressionBasedOutputPortwom.graph.CommandCallNode→wom.graph.GraphNodePort.InputPortwom.graph.CommandCallNode→wom.graph.GraphNodePort.OutputPortwom.graph.ConditionalNode→wom.graph.GraphNodePort.ConditionalOutputPortwom.graph.ConditionalNode→wom.graph.GraphNodePort.InputPortwom.graph.ConditionalNode→wom.graph.GraphNodePort.OutputPortwom.graph.ExpressionBasedGraphOutputNode→wom.graph.GraphNodePort.OutputPortwom.graph.ExpressionCallNode→wom.graph.GraphNodePort.ExpressionBasedOutputPortwom.graph.ExpressionCallNode→wom.graph.GraphNodePort.InputPortwom.graph.ExpressionCallNode→wom.graph.GraphNodePort.OutputPortwom.graph.ExternalGraphInputNode→wom.graph.GraphNodePort.GraphNodeOutputPortwom.graph.GraphInputNode→wom.graph.GraphNodePort.GraphNodeOutputPortwom.graph.GraphNode→wom.graph.GraphNodePort.InputPortwom.graph.GraphNode→wom.graph.GraphNodePort.OutputPortwom.graph.GraphNodeInputExpression→wom.graph.GraphNodePort.OutputPortwom.graph.GraphNodeWithSingleOutputPort→wom.graph.GraphNodePort.OutputPortwom.graph.GraphOutputNode→wom.graph.GraphNodePort.OutputPortwom.graph.PortBasedGraphOutputNode→wom.graph.GraphNodePort.InputPortwom.graph.PortBasedGraphOutputNode→wom.graph.GraphNodePort.OutputPortwom.graph.ScatterNode→wom.graph.GraphNodePort.InputPortwom.graph.ScatterNode→wom.graph.GraphNodePort.OutputPortwom.graph.ScatterNode→wom.graph.GraphNodePort.ScatterGathererPortwom.graph.WorkflowCallNode→wom.graph.GraphNodePort.InputPortwom.graph.WorkflowCallNode→wom.graph.GraphNodePort.OutputPortwom.graph.WorkflowCallNode→wom.graph.GraphNodePort.SubworkflowCallOutputPort
- Direction
- wom.graph uses wom.graph.GraphNodePort, so a change to wom.graph.GraphNodePort can break wom.graph, while a change to wom.graph can't break wom.graph.GraphNodePort.
- Position
- Below the diagonal: wom.graph uses a module listed above it, which is the healthy direction.
15→9 wom.graph uses wom.expression✕
- Connections
- 6 pairs of types, where a type in wom.graph uses a type in wom.expression.
- The types involved
wom.graph.CommandCallNode→wom.expression.IoFunctionSetwom.graph.ExpressionBasedGraphOutputNode→wom.expression.WomExpressionwom.graph.ExpressionCallNode→wom.expression.IoFunctionSetwom.graph.GraphNodeInputExpression→wom.expression.WomExpressionwom.graph.OptionalGraphInputNodeWithDefault→wom.expression.WomExpressionwom.graph.RuntimeOverrideGraphInputNode→wom.expression.WomExpression
- Direction
- wom.graph uses wom.expression, so a change to wom.expression can break wom.graph, while a change to wom.graph can't break wom.expression.
- Position
- Below the diagonal: wom.graph uses a module listed above it, which is the healthy direction.
15→10 wom.graph uses wom✕
- Connections
- 4 pairs of types, where a type in wom.graph uses a type in wom.
- The types involved
wom.graph.CallNode→wom.SourceFileLocationwom.graph.CommandCallNode→wom.SourceFileLocationwom.graph.ExpressionCallNode→wom.SourceFileLocationwom.graph.WorkflowCallNode→wom.SourceFileLocation
- Direction
- wom.graph uses wom, so a change to wom can break wom.graph, while a change to wom.graph can't break wom.
- Position
- Below the diagonal: wom.graph uses a module listed above it, which is the healthy direction.
15→13 wom.graph uses wom.callable✕
- Connections
- 5 pairs of types, where a type in wom.graph uses a type in wom.callable.
- The types involved
wom.graph.CallNode→wom.callable.Callablewom.graph.CommandCallNode→wom.callable.CommandTaskDefinitionwom.graph.ExpressionCallNode→wom.callable.ExpressionTaskDefinitionwom.graph.TaskCall→wom.callable.TaskDefinitionwom.graph.WorkflowCallNode→wom.callable.WorkflowDefinition
- Direction
- wom.graph uses wom.callable, so a change to wom.callable can break wom.graph, while a change to wom.graph can't break wom.callable.
- Position
- Below the diagonal: wom.graph uses a module listed above it, which is the healthy direction.
16→4 cromwell.core uses cromwell.core.path✕
- Connections
- 2 pairs of types, where a type in cromwell.core uses a type in cromwell.core.path.
- The types involved
cromwell.core.CallContext→cromwell.core.path.Pathcromwell.core.StandardPaths→cromwell.core.path.Path
- Direction
- cromwell.core uses cromwell.core.path, so a change to cromwell.core.path can break cromwell.core, while a change to cromwell.core can't break cromwell.core.path.
- Position
- Below the diagonal: cromwell.core uses a module listed above it, which is the healthy direction.
16→15 cromwell.core uses wom.graph✕
- Connections
- 2 pairs of types, where a type in cromwell.core uses a type in wom.graph.
- The types involved
cromwell.core.CallKey→wom.graph.CallNodecromwell.core.JobKey→wom.graph.GraphNode
- Direction
- cromwell.core uses wom.graph, so a change to wom.graph can break cromwell.core, while a change to cromwell.core can't break wom.graph.
- Position
- Below the diagonal: cromwell.core uses a module listed above it, which is the healthy direction.
17→7 wdl.model.draft3.graph uses wom.types✕
- Connections
- 7 pairs of types, where a type in wdl.model.draft3.graph uses a type in wom.types.
- The types involved
wdl.model.draft3.graph.GeneratedCallFinishedHandle→wom.types.WomTypewdl.model.draft3.graph.GeneratedCallOutputValueHandle→wom.types.WomTypewdl.model.draft3.graph.GeneratedIdentifierValueHandle→wom.types.WomTypewdl.model.draft3.graph.GeneratedValueHandle→wom.types.WomTypewdl.model.draft3.graph.GraphElementValueConsumer→wom.types.WomTypewdl.model.draft3.graph.LinkedGraph→wom.types.WomTypewdl.model.draft3.graph.UnlinkedValueGenerator→wom.types.WomType
- Direction
- wdl.model.draft3.graph uses wom.types, so a change to wom.types can break wdl.model.draft3.graph, while a change to wdl.model.draft3.graph can't break wom.types.
- Position
- Below the diagonal: wdl.model.draft3.graph uses a module listed above it, which is the healthy direction.
17→13 wdl.model.draft3.graph uses wom.callable✕
- Connections
- 2 pairs of types, where a type in wdl.model.draft3.graph uses a type in wom.callable.
- The types involved
wdl.model.draft3.graph.GraphElementValueConsumer→wom.callable.Callablewdl.model.draft3.graph.UnlinkedValueGenerator→wom.callable.Callable
- Direction
- wdl.model.draft3.graph uses wom.callable, so a change to wom.callable can break wdl.model.draft3.graph, while a change to wdl.model.draft3.graph can't break wom.callable.
- Position
- Below the diagonal: wdl.model.draft3.graph uses a module listed above it, which is the healthy direction.
17→14 wdl.model.draft3.graph uses wdl.model.draft3.elements✕
- Connections
- 4 pairs of types, where a type in wdl.model.draft3.graph uses a type in wdl.model.draft3.elements.
- The types involved
wdl.model.draft3.graph.ExpressionValueConsumer→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.graph.GraphElementValueConsumer→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.graph.LinkedGraph→wdl.model.draft3.elements.WorkflowGraphElementwdl.model.draft3.graph.LinkedGraphEdge→wdl.model.draft3.elements.WorkflowGraphElement
- Direction
- wdl.model.draft3.graph uses wdl.model.draft3.elements, so a change to wdl.model.draft3.elements can break wdl.model.draft3.graph, while a change to wdl.model.draft3.graph can't break wdl.model.draft3.elements.
- Position
- Below the diagonal: wdl.model.draft3.graph uses a module listed above it, which is the healthy direction.
18→7 wom.executable uses wom.types✕
- Connections
- 1 pair of types, where a type in wom.executable uses a type in wom.types.
- The types involved
wom.executable.WomBundle→wom.types.WomType
- Direction
- wom.executable uses wom.types, so a change to wom.types can break wom.executable, while a change to wom.executable can't break wom.types.
- Position
- Below the diagonal: wom.executable uses a module listed above it, which is the healthy direction.
18→9 wom.executable uses wom.expression✕
- Connections
- 2 pairs of types, where a type in wom.executable uses a type in wom.expression.
- The types involved
wom.executable.Executable→wom.expression.IoFunctionSetwom.executable.ExecutableValidation→wom.expression.IoFunctionSet
- Direction
- wom.executable uses wom.expression, so a change to wom.expression can break wom.executable, while a change to wom.executable can't break wom.expression.
- Position
- Below the diagonal: wom.executable uses a module listed above it, which is the healthy direction.
18→10 wom.executable uses wom✕
- Connections
- 1 pair of types, where a type in wom.executable uses a type in wom.
- The types involved
wom.executable.WomBundle→wom.ResolvedImportRecord
- Direction
- wom.executable uses wom, so a change to wom can break wom.executable, while a change to wom.executable can't break wom.
- Position
- Below the diagonal: wom.executable uses a module listed above it, which is the healthy direction.
18→13 wom.executable uses wom.callable✕
- Connections
- 4 pairs of types, where a type in wom.executable uses a type in wom.callable.
- The types involved
wom.executable.Executable→wom.callable.ExecutableCallablewom.executable.ExecutableValidation→wom.callable.ExecutableCallablewom.executable.WomBundle→wom.callable.Callablewom.executable.WomBundle→wom.callable.ExecutableCallable
- Direction
- wom.executable uses wom.callable, so a change to wom.callable can break wom.executable, while a change to wom.executable can't break wom.callable.
- Position
- Below the diagonal: wom.executable uses a module listed above it, which is the healthy direction.
18→15 wom.executable uses wom.graph✕
- Connections
- 1 pair of types, where a type in wom.executable uses a type in wom.graph.
- The types involved
wom.executable.Executable→wom.graph.Graph
- Direction
- wom.executable uses wom.graph, so a change to wom.graph can break wom.executable, while a change to wom.executable can't break wom.graph.
- Position
- Below the diagonal: wom.executable uses a module listed above it, which is the healthy direction.
19→4 cromwell.backend.async uses cromwell.core.path✕
- Connections
- 10 pairs of types, where a type in cromwell.backend.async uses a type in cromwell.core.path.
- The types involved
cromwell.backend.async.JobAlreadyFailedInJobStore→cromwell.core.path.Pathcromwell.backend.async.KnownJobFailureException→cromwell.core.path.Pathcromwell.backend.async.RetryWithMoreMemory→cromwell.core.path.Pathcromwell.backend.async.ReturnCodeIsNotAnInt→cromwell.core.path.Pathcromwell.backend.async.RuntimeAttributeValidationFailures→cromwell.core.path.Pathcromwell.backend.async.StderrNonEmpty→cromwell.core.path.Pathcromwell.backend.async.SuccessfulExecution→cromwell.core.path.Pathcromwell.backend.async.SuccessfulExecutionHandle→cromwell.core.path.Pathcromwell.backend.async.UnExpectedStatus→cromwell.core.path.Pathcromwell.backend.async.WrongReturnCode→cromwell.core.path.Path
- Direction
- cromwell.backend.async uses cromwell.core.path, so a change to cromwell.core.path can break cromwell.backend.async, while a change to cromwell.backend.async can't break cromwell.core.path.
- Position
- Below the diagonal: cromwell.backend.async uses a module listed above it, which is the healthy direction.
19→9 cromwell.backend.async uses wom.expression✕
- Connections
- 1 pair of types, where a type in cromwell.backend.async uses a type in wom.expression.
- The types involved
cromwell.backend.async.RuntimeAttributeValidationFailure→wom.expression.WomExpression
- Direction
- cromwell.backend.async uses wom.expression, so a change to wom.expression can break cromwell.backend.async, while a change to cromwell.backend.async can't break wom.expression.
- Position
- Below the diagonal: cromwell.backend.async uses a module listed above it, which is the healthy direction.
19→16 cromwell.backend.async uses cromwell.core✕
- Connections
- 4 pairs of types, where a type in cromwell.backend.async uses a type in cromwell.core.
- The types involved
cromwell.backend.async.SuccessfulExecution→cromwell.core.CallOutputscromwell.backend.async.SuccessfulExecution→cromwell.core.ExecutionEventcromwell.backend.async.SuccessfulExecutionHandle→cromwell.core.CallOutputscromwell.backend.async.SuccessfulExecutionHandle→cromwell.core.ExecutionEvent
- Direction
- cromwell.backend.async uses cromwell.core, so a change to cromwell.core can break cromwell.backend.async, while a change to cromwell.backend.async can't break cromwell.core.
- Position
- Below the diagonal: cromwell.backend.async uses a module listed above it, which is the healthy direction.
19→26 cromwell.backend.async uses cromwell.backend part of a loop✕
- Connections
- 3 pairs of types, where a type in cromwell.backend.async uses a type in cromwell.backend.
- The types involved
cromwell.backend.async.PendingExecutionHandle→cromwell.backend.BackendJobDescriptorcromwell.backend.async.SuccessfulExecution→cromwell.backend.BackendJobDescriptorcromwell.backend.async.SuccessfulExecutionHandle→cromwell.backend.BackendJobDescriptor
- Direction
- cromwell.backend.async uses cromwell.backend, so a change to cromwell.backend can break cromwell.backend.async, while a change to cromwell.backend.async can't break cromwell.backend.
- 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→1 cromwell.core.io uses cromwell.core.callcaching✕
- Connections
- 2 pairs of types, where a type in cromwell.core.io uses a type in cromwell.core.callcaching.
- The types involved
cromwell.core.io.IoCommandBuilder→cromwell.core.callcaching.FileHashStrategycromwell.core.io.IoHashCommand→cromwell.core.callcaching.FileHashStrategy
- Direction
- cromwell.core.io uses cromwell.core.callcaching, so a change to cromwell.core.callcaching can break cromwell.core.io, while a change to cromwell.core.io can't break cromwell.core.callcaching.
- Position
- Below the diagonal: cromwell.core.io uses a module listed above it, which is the healthy direction.
20→4 cromwell.core.io uses cromwell.core.path✕
- Connections
- 15 pairs of types, where a type in cromwell.core.io uses a type in cromwell.core.path.
- The types involved
cromwell.core.io.IoCommandBuilder→cromwell.core.path.Pathcromwell.core.io.IoCopyCommand→cromwell.core.path.Pathcromwell.core.io.IoDeleteCommand→cromwell.core.path.Pathcromwell.core.io.IoExistsCommand→cromwell.core.path.Pathcromwell.core.io.IoExistsOrThrowCommand→cromwell.core.path.Pathcromwell.core.io.IoHashCommand→cromwell.core.path.Pathcromwell.core.io.IoIsDirectoryCommand→cromwell.core.path.Pathcromwell.core.io.IoNoopCommand→cromwell.core.path.Pathcromwell.core.io.IoReadLinesCommand→cromwell.core.path.Pathcromwell.core.io.IoSizeCommand→cromwell.core.path.Pathcromwell.core.io.IoTouchCommand→cromwell.core.path.Pathcromwell.core.io.IoWriteCommand→cromwell.core.path.Pathcromwell.core.io.PartialIoCommandBuilder→cromwell.core.path.Pathcromwell.core.io.SingleFileIoCommand→cromwell.core.path.Pathcromwell.core.io.WorkflowCorePathFunctionSet→cromwell.core.path.PathFactory
- Direction
- cromwell.core.io uses cromwell.core.path, so a change to cromwell.core.path can break cromwell.core.io, while a change to cromwell.core.io can't break cromwell.core.path.
- Position
- Below the diagonal: cromwell.core.io uses a module listed above it, which is the healthy direction.
20→9 cromwell.core.io uses wom.expression✕
- Connections
- 1 pair of types, where a type in cromwell.core.io uses a type in wom.expression.
- The types involved
cromwell.core.io.WorkflowCorePathFunctionSet→wom.expression.PathFunctionSet
- Direction
- cromwell.core.io uses wom.expression, so a change to wom.expression can break cromwell.core.io, while a change to cromwell.core.io can't break wom.expression.
- Position
- Below the diagonal: cromwell.core.io uses a module listed above it, which is the healthy direction.
20→16 cromwell.core.io uses cromwell.core✕
- Connections
- 1 pair of types, where a type in cromwell.core.io uses a type in cromwell.core.
- The types involved
cromwell.core.io.CallCorePathFunctions→cromwell.core.CallContext
- Direction
- cromwell.core.io uses cromwell.core, so a change to cromwell.core can break cromwell.core.io, while a change to cromwell.core.io can't break cromwell.core.
- Position
- Below the diagonal: cromwell.core.io uses a module listed above it, which is the healthy direction.
21→5 cromwell.languages uses wom.values✕
- Connections
- 1 pair of types, where a type in cromwell.languages uses a type in wom.values.
- The types involved
cromwell.languages.ValidatedWomNamespace→wom.values.WomValue
- Direction
- cromwell.languages uses wom.values, so a change to wom.values can break cromwell.languages, while a change to cromwell.languages can't break wom.values.
- Position
- Below the diagonal: cromwell.languages uses a module listed above it, which is the healthy direction.
21→8 cromwell.languages uses wom.graph.GraphNodePort✕
- Connections
- 1 pair of types, where a type in cromwell.languages uses a type in wom.graph.GraphNodePort.
- The types involved
cromwell.languages.ValidatedWomNamespace→wom.graph.GraphNodePort.OutputPort
- Direction
- cromwell.languages uses wom.graph.GraphNodePort, so a change to wom.graph.GraphNodePort can break cromwell.languages, while a change to cromwell.languages can't break wom.graph.GraphNodePort.
- Position
- Below the diagonal: cromwell.languages uses a module listed above it, which is the healthy direction.
21→9 cromwell.languages uses wom.expression✕
- Connections
- 1 pair of types, where a type in cromwell.languages uses a type in wom.expression.
- The types involved
cromwell.languages.LanguageFactory→wom.expression.IoFunctionSet
- Direction
- cromwell.languages uses wom.expression, so a change to wom.expression can break cromwell.languages, while a change to cromwell.languages can't break wom.expression.
- Position
- Below the diagonal: cromwell.languages uses a module listed above it, which is the healthy direction.
21→10 cromwell.languages uses wom✕
- Connections
- 1 pair of types, where a type in cromwell.languages uses a type in wom.
- The types involved
cromwell.languages.LanguageFactory→wom.ResolvedImportRecord
- Direction
- cromwell.languages uses wom, so a change to wom can break cromwell.languages, while a change to cromwell.languages can't break wom.
- Position
- Below the diagonal: cromwell.languages uses a module listed above it, which is the healthy direction.
21→11 cromwell.languages uses cromwell.languages.util.ImportResolver✕
- Connections
- 1 pair of types, where a type in cromwell.languages uses a type in cromwell.languages.util.ImportResolver.
- The types involved
cromwell.languages.LanguageFactory→cromwell.languages.util.ImportResolver.ImportResolver
- Direction
- cromwell.languages uses cromwell.languages.util.ImportResolver, so a change to cromwell.languages.util.ImportResolver can break cromwell.languages, while a change to cromwell.languages can't break cromwell.languages.util.ImportResolver.
- Position
- Below the diagonal: cromwell.languages uses a module listed above it, which is the healthy direction.
21→16 cromwell.languages uses cromwell.core✕
- Connections
- 3 pairs of types, where a type in cromwell.languages uses a type in cromwell.core.
- The types involved
cromwell.languages.LanguageFactory→cromwell.core.WorkflowIdcromwell.languages.LanguageFactory→cromwell.core.WorkflowOptionscromwell.languages.LanguageFactory→cromwell.core.WorkflowSourceFilesCollection
- Direction
- cromwell.languages uses cromwell.core, so a change to cromwell.core can break cromwell.languages, while a change to cromwell.languages can't break cromwell.core.
- Position
- Below the diagonal: cromwell.languages uses a module listed above it, which is the healthy direction.
21→18 cromwell.languages uses wom.executable✕
- Connections
- 2 pairs of types, where a type in cromwell.languages uses a type in wom.executable.
- The types involved
cromwell.languages.LanguageFactory→wom.executable.WomBundlecromwell.languages.ValidatedWomNamespace→wom.executable.Executable
- Direction
- cromwell.languages uses wom.executable, so a change to wom.executable can break cromwell.languages, while a change to cromwell.languages can't break wom.executable.
- Position
- Below the diagonal: cromwell.languages uses a module listed above it, which is the healthy direction.
22→4 cromwell.services.metadata uses cromwell.core.path✕
- Connections
- 1 pair of types, where a type in cromwell.services.metadata uses a type in cromwell.core.path.
- The types involved
cromwell.services.metadata.MetadataService→cromwell.core.path.FileRelocationMap
- Direction
- cromwell.services.metadata uses cromwell.core.path, so a change to cromwell.core.path can break cromwell.services.metadata, while a change to cromwell.services.metadata can't break cromwell.core.path.
- Position
- Below the diagonal: cromwell.services.metadata uses a module listed above it, which is the healthy direction.
22→5 cromwell.services.metadata uses wom.values✕
- Connections
- 1 pair of types, where a type in cromwell.services.metadata uses a type in wom.values.
- The types involved
cromwell.services.metadata.MetadataService→wom.values.WomValue
- Direction
- cromwell.services.metadata uses wom.values, so a change to wom.values can break cromwell.services.metadata, while a change to cromwell.services.metadata can't break wom.values.
- Position
- Below the diagonal: cromwell.services.metadata uses a module listed above it, which is the healthy direction.
22→16 cromwell.services.metadata uses cromwell.core✕
- Connections
- 4 pairs of types, where a type in cromwell.services.metadata uses a type in cromwell.core.
- The types involved
cromwell.services.metadata.MetadataEvent→cromwell.core.WorkflowIdcromwell.services.metadata.MetadataKey→cromwell.core.WorkflowIdcromwell.services.metadata.MetadataQuery→cromwell.core.WorkflowIdcromwell.services.metadata.WorkflowQueryParameters→cromwell.core.WorkflowId
- Direction
- cromwell.services.metadata uses cromwell.core, so a change to cromwell.core can break cromwell.services.metadata, while a change to cromwell.services.metadata can't break cromwell.core.
- Position
- Below the diagonal: cromwell.services.metadata uses a module listed above it, which is the healthy direction.
23→5 wdl.model.draft3.graph.expression uses wom.values✕
- Connections
- 4 pairs of types, where a type in wdl.model.draft3.graph.expression uses a type in wom.values.
- The types involved
wdl.model.draft3.graph.expression.FileEvaluator→wom.values.WomFilewdl.model.draft3.graph.expression.FileEvaluator→wom.values.WomValuewdl.model.draft3.graph.expression.ForCommandInstantiationOptions→wom.values.WomValuewdl.model.draft3.graph.expression.ValueEvaluator→wom.values.WomValue
- Direction
- wdl.model.draft3.graph.expression uses wom.values, so a change to wom.values can break wdl.model.draft3.graph.expression, while a change to wdl.model.draft3.graph.expression can't break wom.values.
- Position
- Below the diagonal: wdl.model.draft3.graph.expression uses a module listed above it, which is the healthy direction.
23→7 wdl.model.draft3.graph.expression uses wom.types✕
- Connections
- 4 pairs of types, where a type in wdl.model.draft3.graph.expression uses a type in wom.types.
- The types involved
wdl.model.draft3.graph.expression.FileEvaluator→wom.types.WomTypewdl.model.draft3.graph.expression.TypeEvaluator→wom.types.WomTypewdl.model.draft3.graph.expression.WomExpressionMaker→wom.types.WomTypewdl.model.draft3.graph.expression.WomTypeMaker→wom.types.WomType
- Direction
- wdl.model.draft3.graph.expression uses wom.types, so a change to wom.types can break wdl.model.draft3.graph.expression, while a change to wdl.model.draft3.graph.expression can't break wom.types.
- Position
- Below the diagonal: wdl.model.draft3.graph.expression uses a module listed above it, which is the healthy direction.
23→9 wdl.model.draft3.graph.expression uses wom.expression✕
- Connections
- 3 pairs of types, where a type in wdl.model.draft3.graph.expression uses a type in wom.expression.
- The types involved
wdl.model.draft3.graph.expression.FileEvaluator→wom.expression.IoFunctionSetwdl.model.draft3.graph.expression.ValueEvaluator→wom.expression.IoFunctionSetwdl.model.draft3.graph.expression.WomExpressionMaker→wom.expression.WomExpression
- Direction
- wdl.model.draft3.graph.expression uses wom.expression, so a change to wom.expression can break wdl.model.draft3.graph.expression, while a change to wdl.model.draft3.graph.expression can't break wom.expression.
- Position
- Below the diagonal: wdl.model.draft3.graph.expression uses a module listed above it, which is the healthy direction.
23→10 wdl.model.draft3.graph.expression uses wom✕
- Connections
- 1 pair of types, where a type in wdl.model.draft3.graph.expression uses a type in wom.
- The types involved
wdl.model.draft3.graph.expression.EvaluatedValue→wom.CommandSetupSideEffectFile
- Direction
- wdl.model.draft3.graph.expression uses wom, so a change to wom can break wdl.model.draft3.graph.expression, while a change to wdl.model.draft3.graph.expression can't break wom.
- Position
- Below the diagonal: wdl.model.draft3.graph.expression uses a module listed above it, which is the healthy direction.
23→14 wdl.model.draft3.graph.expression uses wdl.model.draft3.elements✕
- Connections
- 3 pairs of types, where a type in wdl.model.draft3.graph.expression uses a type in wdl.model.draft3.elements.
- The types involved
wdl.model.draft3.graph.expression.FileEvaluator→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.graph.expression.TypeEvaluator→wdl.model.draft3.elements.ExpressionElementwdl.model.draft3.graph.expression.ValueEvaluator→wdl.model.draft3.elements.ExpressionElement
- Direction
- wdl.model.draft3.graph.expression uses wdl.model.draft3.elements, so a change to wdl.model.draft3.elements can break wdl.model.draft3.graph.expression, while a change to wdl.model.draft3.graph.expression can't break wdl.model.draft3.elements.
- Position
- Below the diagonal: wdl.model.draft3.graph.expression uses a module listed above it, which is the healthy direction.
23→17 wdl.model.draft3.graph.expression uses wdl.model.draft3.graph✕
- Connections
- 4 pairs of types, where a type in wdl.model.draft3.graph.expression uses a type in wdl.model.draft3.graph.
- The types involved
wdl.model.draft3.graph.expression.TypeEvaluator→wdl.model.draft3.graph.GeneratedValueHandlewdl.model.draft3.graph.expression.TypeEvaluator→wdl.model.draft3.graph.UnlinkedConsumedValueHookwdl.model.draft3.graph.expression.WomExpressionMaker→wdl.model.draft3.graph.GeneratedValueHandlewdl.model.draft3.graph.expression.WomExpressionMaker→wdl.model.draft3.graph.UnlinkedConsumedValueHook
- Direction
- wdl.model.draft3.graph.expression uses wdl.model.draft3.graph, so a change to wdl.model.draft3.graph can break wdl.model.draft3.graph.expression, while a change to wdl.model.draft3.graph.expression can't break wdl.model.draft3.graph.
- Position
- Below the diagonal: wdl.model.draft3.graph.expression uses a module listed above it, which is the healthy direction.
24→20 cromwell.docker uses cromwell.core.io✕
- Connections
- 1 pair of types, where a type in cromwell.docker uses a type in cromwell.core.io.
- The types involved
cromwell.docker.DockerRegistryConfig→cromwell.core.io.Throttle
- Direction
- cromwell.docker uses cromwell.core.io, so a change to cromwell.core.io can break cromwell.docker, while a change to cromwell.docker can't break cromwell.core.io.
- Position
- Below the diagonal: cromwell.docker uses a module listed above it, which is the healthy direction.
25→5 wdl.transforms.base.wdlom2wom uses wom.values✕
- Connections
- 2 pairs of types, where a type in wdl.transforms.base.wdlom2wom uses a type in wom.values.
- The types involved
wdl.transforms.base.wdlom2wom.WdlomWomPlaceholderCommandPart→wom.values.WomValuewdl.transforms.base.wdlom2wom.WdlomWomStringCommandPart→wom.values.WomValue
- Direction
- wdl.transforms.base.wdlom2wom uses wom.values, so a change to wom.values can break wdl.transforms.base.wdlom2wom, while a change to wdl.transforms.base.wdlom2wom can't break wom.values.
- Position
- Below the diagonal: wdl.transforms.base.wdlom2wom uses a module listed above it, which is the healthy direction.
25→7 wdl.transforms.base.wdlom2wom uses wom.types✕
- Connections
- 3 pairs of types, where a type in wdl.transforms.base.wdlom2wom uses a type in wom.types.
- The types involved
wdl.transforms.base.wdlom2wom.CommandPartElementToWomCommandPart→wom.types.WomTypewdl.transforms.base.wdlom2wom.StructEvaluation→wom.types.WomTypewdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wom.types.WomType
- Direction
- wdl.transforms.base.wdlom2wom uses wom.types, so a change to wom.types can break wdl.transforms.base.wdlom2wom, while a change to wdl.transforms.base.wdlom2wom can't break wom.types.
- Position
- Below the diagonal: wdl.transforms.base.wdlom2wom uses a module listed above it, which is the healthy direction.
25→9 wdl.transforms.base.wdlom2wom uses wom.expression✕
- Connections
- 3 pairs of types, where a type in wdl.transforms.base.wdlom2wom uses a type in wom.expression.
- The types involved
wdl.transforms.base.wdlom2wom.CommandPartElementToWomCommandPart→wom.expression.WomExpressionwdl.transforms.base.wdlom2wom.WdlomWomPlaceholderCommandPart→wom.expression.IoFunctionSetwdl.transforms.base.wdlom2wom.WdlomWomStringCommandPart→wom.expression.IoFunctionSet
- Direction
- wdl.transforms.base.wdlom2wom uses wom.expression, so a change to wom.expression can break wdl.transforms.base.wdlom2wom, while a change to wdl.transforms.base.wdlom2wom can't break wom.expression.
- Position
- Below the diagonal: wdl.transforms.base.wdlom2wom uses a module listed above it, which is the healthy direction.
25→10 wdl.transforms.base.wdlom2wom uses wom✕
- Connections
- 6 pairs of types, where a type in wdl.transforms.base.wdlom2wom uses a type in wom.
- The types involved
wdl.transforms.base.wdlom2wom.CommandPartElementToWomCommandPart→wom.CommandPartwdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wom.RuntimeAttributeswdl.transforms.base.wdlom2wom.WdlomWomPlaceholderCommandPart→wom.CommandPartwdl.transforms.base.wdlom2wom.WdlomWomPlaceholderCommandPart→wom.InstantiatedCommandwdl.transforms.base.wdlom2wom.WdlomWomStringCommandPart→wom.CommandPartwdl.transforms.base.wdlom2wom.WdlomWomStringCommandPart→wom.InstantiatedCommand
- Direction
- wdl.transforms.base.wdlom2wom uses wom, so a change to wom can break wdl.transforms.base.wdlom2wom, while a change to wdl.transforms.base.wdlom2wom can't break wom.
- Position
- Below the diagonal: wdl.transforms.base.wdlom2wom uses a module listed above it, which is the healthy direction.
25→11 wdl.transforms.base.wdlom2wom uses cromwell.languages.util.ImportResolver✕
- Connections
- 2 pairs of types, where a type in wdl.transforms.base.wdlom2wom uses a type in cromwell.languages.util.ImportResolver.
- The types involved
wdl.transforms.base.wdlom2wom.FileElementToWomBundle→cromwell.languages.util.ImportResolver.ImportResolverwdl.transforms.base.wdlom2wom.FileElementToWomBundleInputs→cromwell.languages.util.ImportResolver.ImportResolver
- Direction
- wdl.transforms.base.wdlom2wom uses cromwell.languages.util.ImportResolver, so a change to cromwell.languages.util.ImportResolver can break wdl.transforms.base.wdlom2wom, while a change to wdl.transforms.base.wdlom2wom can't break cromwell.languages.util.ImportResolver.
- Position
- Below the diagonal: wdl.transforms.base.wdlom2wom uses a module listed above it, which is the healthy direction.
25→13 wdl.transforms.base.wdlom2wom uses wom.callable✕
- Connections
- 5 pairs of types, where a type in wdl.transforms.base.wdlom2wom uses a type in wom.callable.
- The types involved
wdl.transforms.base.wdlom2wom.FileElementToWomBundleInputs→wom.callable.CallableTaskDefinitionwdl.transforms.base.wdlom2wom.FileElementToWomBundleInputs→wom.callable.WorkflowDefinitionwdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wom.callable.CallableTaskDefinitionwdl.transforms.base.wdlom2wom.WorkflowDefinitionElementToWomWorkflowDefinition→wom.callable.Callablewdl.transforms.base.wdlom2wom.WorkflowDefinitionElementToWomWorkflowDefinition→wom.callable.WorkflowDefinition
- Direction
- wdl.transforms.base.wdlom2wom uses wom.callable, so a change to wom.callable can break wdl.transforms.base.wdlom2wom, while a change to wdl.transforms.base.wdlom2wom can't break wom.callable.
- Position
- Below the diagonal: wdl.transforms.base.wdlom2wom uses a module listed above it, which is the healthy direction.
25→14 wdl.transforms.base.wdlom2wom uses wdl.model.draft3.elements✕
- Connections
- 21 pairs of types, where a type in wdl.transforms.base.wdlom2wom uses a type in wdl.model.draft3.elements.
- The types involved
wdl.transforms.base.wdlom2wom.CommandPartElementToWomCommandPart→wdl.model.draft3.elements.CommandPartElementwdl.transforms.base.wdlom2wom.CommandPartElementToWomCommandPart→wdl.model.draft3.elements.ExpressionElementwdl.transforms.base.wdlom2wom.CommandPartElementToWomCommandPart→wdl.model.draft3.elements.PlaceholderAttributeSetwdl.transforms.base.wdlom2wom.FileElementToWomBundle→wdl.model.draft3.elements.ImportElementwdl.transforms.base.wdlom2wom.FileElementToWomBundleInputs→wdl.model.draft3.elements.FileElementwdl.transforms.base.wdlom2wom.StructEvaluation→wdl.model.draft3.elements.StructElementwdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wdl.model.draft3.elements.CommandPartElementwdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wdl.model.draft3.elements.CommandSectionLinewdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wdl.model.draft3.elements.ExpressionElementwdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wdl.model.draft3.elements.InputDeclarationElementwdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wdl.model.draft3.elements.InputsSectionElementwdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wdl.model.draft3.elements.IntermediateValueDeclarationElementwdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wdl.model.draft3.elements.OutputDeclarationElementwdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wdl.model.draft3.elements.OutputsSectionElementwdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wdl.model.draft3.elements.ParameterMetaSectionElementwdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wdl.model.draft3.elements.RuntimeAttributesSectionElementwdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wdl.model.draft3.elements.TaskDefinitionElementwdl.transforms.base.wdlom2wom.Util→wdl.model.draft3.elements.MetaSectionElementwdl.transforms.base.wdlom2wom.Util→wdl.model.draft3.elements.ParameterMetaSectionElementwdl.transforms.base.wdlom2wom.WdlomWomPlaceholderCommandPart→wdl.model.draft3.elements.PlaceholderAttributeSetwdl.transforms.base.wdlom2wom.WorkflowDefinitionElementToWomWorkflowDefinition→wdl.model.draft3.elements.ExpressionElement
- Direction
- wdl.transforms.base.wdlom2wom uses wdl.model.draft3.elements, so a change to wdl.model.draft3.elements can break wdl.transforms.base.wdlom2wom, while a change to wdl.transforms.base.wdlom2wom can't break wdl.model.draft3.elements.
- Position
- Below the diagonal: wdl.transforms.base.wdlom2wom uses a module listed above it, which is the healthy direction.
25→15 wdl.transforms.base.wdlom2wom uses wom.graph✕
- Connections
- 4 pairs of types, where a type in wdl.transforms.base.wdlom2wom uses a type in wom.graph.
- The types involved
wdl.transforms.base.wdlom2wom.WdlomWomPlaceholderCommandPart→wom.graph.LocalNamewdl.transforms.base.wdlom2wom.WdlomWomStringCommandPart→wom.graph.LocalNamewdl.transforms.base.wdlom2wom.WorkflowDefinitionElementToWomWorkflowDefinition→wom.graph.CallNodewdl.transforms.base.wdlom2wom.WorkflowDefinitionElementToWomWorkflowDefinition→wom.graph.GraphNode
- Direction
- wdl.transforms.base.wdlom2wom uses wom.graph, so a change to wom.graph can break wdl.transforms.base.wdlom2wom, while a change to wdl.transforms.base.wdlom2wom can't break wom.graph.
- Position
- Below the diagonal: wdl.transforms.base.wdlom2wom uses a module listed above it, which is the healthy direction.
25→17 wdl.transforms.base.wdlom2wom uses wdl.model.draft3.graph✕
- Connections
- 6 pairs of types, where a type in wdl.transforms.base.wdlom2wom uses a type in wdl.model.draft3.graph.
- The types involved
wdl.transforms.base.wdlom2wom.CommandPartElementToWomCommandPart→wdl.model.draft3.graph.ExpressionValueConsumerwdl.transforms.base.wdlom2wom.CommandPartElementToWomCommandPart→wdl.model.draft3.graph.GeneratedValueHandlewdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wdl.model.draft3.graph.ExpressionValueConsumerwdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wdl.model.draft3.graph.LinkedGraphwdl.transforms.base.wdlom2wom.WorkflowDefinitionElementToWomWorkflowDefinition→wdl.model.draft3.graph.ExpressionValueConsumerwdl.transforms.base.wdlom2wom.WorkflowDefinitionElementToWomWorkflowDefinition→wdl.model.draft3.graph.LinkedGraph
- Direction
- wdl.transforms.base.wdlom2wom uses wdl.model.draft3.graph, so a change to wdl.model.draft3.graph can break wdl.transforms.base.wdlom2wom, while a change to wdl.transforms.base.wdlom2wom can't break wdl.model.draft3.graph.
- Position
- Below the diagonal: wdl.transforms.base.wdlom2wom uses a module listed above it, which is the healthy direction.
25→18 wdl.transforms.base.wdlom2wom uses wom.executable✕
- Connections
- 2 pairs of types, where a type in wdl.transforms.base.wdlom2wom uses a type in wom.executable.
- The types involved
wdl.transforms.base.wdlom2wom.FileElementToWomBundle→wom.executable.WomBundlewdl.transforms.base.wdlom2wom.WomBundleToWomExecutable→wom.executable.WomBundle
- Direction
- wdl.transforms.base.wdlom2wom uses wom.executable, so a change to wom.executable can break wdl.transforms.base.wdlom2wom, while a change to wdl.transforms.base.wdlom2wom can't break wom.executable.
- Position
- Below the diagonal: wdl.transforms.base.wdlom2wom uses a module listed above it, which is the healthy direction.
25→21 wdl.transforms.base.wdlom2wom uses cromwell.languages✕
- Connections
- 2 pairs of types, where a type in wdl.transforms.base.wdlom2wom uses a type in cromwell.languages.
- The types involved
wdl.transforms.base.wdlom2wom.FileElementToWomBundle→cromwell.languages.LanguageFactorywdl.transforms.base.wdlom2wom.FileElementToWomBundleInputs→cromwell.languages.LanguageFactory
- Direction
- wdl.transforms.base.wdlom2wom uses cromwell.languages, so a change to cromwell.languages can break wdl.transforms.base.wdlom2wom, while a change to wdl.transforms.base.wdlom2wom can't break cromwell.languages.
- Position
- Below the diagonal: wdl.transforms.base.wdlom2wom uses a module listed above it, which is the healthy direction.
25→23 wdl.transforms.base.wdlom2wom uses wdl.model.draft3.graph.expression✕
- Connections
- 10 pairs of types, where a type in wdl.transforms.base.wdlom2wom uses a type in wdl.model.draft3.graph.expression.
- The types involved
wdl.transforms.base.wdlom2wom.CommandPartElementToWomCommandPart→wdl.model.draft3.graph.expression.FileEvaluatorwdl.transforms.base.wdlom2wom.CommandPartElementToWomCommandPart→wdl.model.draft3.graph.expression.TypeEvaluatorwdl.transforms.base.wdlom2wom.CommandPartElementToWomCommandPart→wdl.model.draft3.graph.expression.ValueEvaluatorwdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wdl.model.draft3.graph.expression.FileEvaluatorwdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wdl.model.draft3.graph.expression.TypeEvaluatorwdl.transforms.base.wdlom2wom.TaskDefinitionElementToWomTaskDefinition→wdl.model.draft3.graph.expression.ValueEvaluatorwdl.transforms.base.wdlom2wom.WdlomWomPlaceholderCommandPart→wdl.model.draft3.graph.expression.EvaluatedValuewdl.transforms.base.wdlom2wom.WorkflowDefinitionElementToWomWorkflowDefinition→wdl.model.draft3.graph.expression.FileEvaluatorwdl.transforms.base.wdlom2wom.WorkflowDefinitionElementToWomWorkflowDefinition→wdl.model.draft3.graph.expression.TypeEvaluatorwdl.transforms.base.wdlom2wom.WorkflowDefinitionElementToWomWorkflowDefinition→wdl.model.draft3.graph.expression.ValueEvaluator
- Direction
- wdl.transforms.base.wdlom2wom uses wdl.model.draft3.graph.expression, so a change to wdl.model.draft3.graph.expression can break wdl.transforms.base.wdlom2wom, while a change to wdl.transforms.base.wdlom2wom can't break wdl.model.draft3.graph.expression.
- Position
- Below the diagonal: wdl.transforms.base.wdlom2wom uses a module listed above it, which is the healthy direction.
26→1 cromwell.backend uses cromwell.core.callcaching✕
- Connections
- 1 pair of types, where a type in cromwell.backend uses a type in cromwell.core.callcaching.
- The types involved
cromwell.backend.BackendJobDescriptor→cromwell.core.callcaching.MaybeCallCachingEligible
- Direction
- cromwell.backend uses cromwell.core.callcaching, so a change to cromwell.core.callcaching can break cromwell.backend, while a change to cromwell.backend can't break cromwell.core.callcaching.
- Position
- Below the diagonal: cromwell.backend uses a module listed above it, which is the healthy direction.
26→4 cromwell.backend uses cromwell.core.path✕
- Connections
- 6 pairs of types, where a type in cromwell.backend uses a type in cromwell.core.path.
- The types involved
cromwell.backend.BackendConfigurationDescriptor→cromwell.core.path.PathBuilderFactorycromwell.backend.BackendJobBreadCrumb→cromwell.core.path.Pathcromwell.backend.BackendLifecycleActorFactory→cromwell.core.path.Pathcromwell.backend.ReadLikeFunctions→cromwell.core.path.PathFactorycromwell.backend.WriteFunctions→cromwell.core.path.Pathcromwell.backend.WriteFunctions→cromwell.core.path.PathFactory
- Direction
- cromwell.backend uses cromwell.core.path, so a change to cromwell.core.path can break cromwell.backend, while a change to cromwell.backend can't break cromwell.core.path.
- Position
- Below the diagonal: cromwell.backend uses a module listed above it, which is the healthy direction.
26→5 cromwell.backend uses wom.values✕
- Connections
- 9 pairs of types, where a type in cromwell.backend uses a type in wom.values.
- The types involved
cromwell.backend.AttemptedLookupResult→wom.values.WomValuecromwell.backend.BackendJobDescriptor→wom.values.WomFilecromwell.backend.BackendJobDescriptor→wom.values.WomValuecromwell.backend.BackendWorkflowDescriptor→wom.values.WomValuecromwell.backend.BackendWorkflowInitializationActor→wom.values.WomValuecromwell.backend.Command→wom.values.WomValuecromwell.backend.OutputEvaluator→wom.values.WomValuecromwell.backend.RuntimeAttributeDefinition→wom.values.WomValuecromwell.backend.WriteFunctions→wom.values.WomSingleFile
- Direction
- cromwell.backend uses wom.values, so a change to wom.values can break cromwell.backend, while a change to cromwell.backend can't break wom.values.
- Position
- Below the diagonal: cromwell.backend uses a module listed above it, which is the healthy direction.
26→8 cromwell.backend uses wom.graph.GraphNodePort✕
- Connections
- 1 pair of types, where a type in cromwell.backend uses a type in wom.graph.GraphNodePort.
- The types involved
cromwell.backend.BackendWorkflowDescriptor→wom.graph.GraphNodePort.OutputPort
- Direction
- cromwell.backend uses wom.graph.GraphNodePort, so a change to wom.graph.GraphNodePort can break cromwell.backend, while a change to cromwell.backend can't break wom.graph.GraphNodePort.
- Position
- Below the diagonal: cromwell.backend uses a module listed above it, which is the healthy direction.
26→9 cromwell.backend uses wom.expression✕
- Connections
- 6 pairs of types, where a type in cromwell.backend uses a type in wom.expression.
- The types involved
cromwell.backend.BackendLifecycleActorFactory→wom.expression.IoFunctionSetcromwell.backend.BackendWorkflowInitializationActor→wom.expression.WomExpressioncromwell.backend.Command→wom.expression.IoFunctionSetcromwell.backend.OutputEvaluator→wom.expression.IoFunctionSetcromwell.backend.ReadLikeFunctions→wom.expression.IoFunctionSetcromwell.backend.WriteFunctions→wom.expression.IoFunctionSet
- Direction
- cromwell.backend uses wom.expression, so a change to wom.expression can break cromwell.backend, while a change to cromwell.backend can't break wom.expression.
- Position
- Below the diagonal: cromwell.backend uses a module listed above it, which is the healthy direction.
26→10 cromwell.backend uses wom✕
- Connections
- 1 pair of types, where a type in cromwell.backend uses a type in wom.
- The types involved
cromwell.backend.Command→wom.InstantiatedCommand
- Direction
- cromwell.backend uses wom, so a change to wom can break cromwell.backend, while a change to cromwell.backend can't break wom.
- Position
- Below the diagonal: cromwell.backend uses a module listed above it, which is the healthy direction.
26→13 cromwell.backend uses wom.callable✕
- Connections
- 3 pairs of types, where a type in cromwell.backend uses a type in wom.callable.
- The types involved
cromwell.backend.BackendJobBreadCrumb→wom.callable.Callablecromwell.backend.BackendJobDescriptor→wom.callable.MetaValueElementcromwell.backend.BackendWorkflowDescriptor→wom.callable.ExecutableCallable
- Direction
- cromwell.backend uses wom.callable, so a change to wom.callable can break cromwell.backend, while a change to cromwell.backend can't break wom.callable.
- Position
- Below the diagonal: cromwell.backend uses a module listed above it, which is the healthy direction.
26→15 cromwell.backend uses wom.graph✕
- Connections
- 3 pairs of types, where a type in cromwell.backend uses a type in wom.graph.
- The types involved
cromwell.backend.BackendJobDescriptorKey→wom.graph.CommandCallNodecromwell.backend.BackendLifecycleActorFactory→wom.graph.CommandCallNodecromwell.backend.BackendWorkflowLifecycleActor→wom.graph.CommandCallNode
- Direction
- cromwell.backend uses wom.graph, so a change to wom.graph can break cromwell.backend, while a change to cromwell.backend can't break wom.graph.
- Position
- Below the diagonal: cromwell.backend uses a module listed above it, which is the healthy direction.
26→16 cromwell.backend uses cromwell.core✕
- Connections
- 11 pairs of types, where a type in cromwell.backend uses a type in cromwell.core.
- The types involved
cromwell.backend.BackendConfigurationDescriptor→cromwell.core.WorkflowOptionscromwell.backend.BackendJobBreadCrumb→cromwell.core.JobKeycromwell.backend.BackendJobBreadCrumb→cromwell.core.WorkflowIdcromwell.backend.BackendJobDescriptorKey→cromwell.core.CallKeycromwell.backend.BackendJobDescriptorKey→cromwell.core.WorkflowIdcromwell.backend.BackendJobExecutionActor→cromwell.core.WorkflowIdcromwell.backend.BackendLifecycleActorFactory→cromwell.core.CallOutputscromwell.backend.BackendSingletonActorAbortWorkflow→cromwell.core.WorkflowIdcromwell.backend.BackendWorkflowDescriptor→cromwell.core.HogGroupcromwell.backend.BackendWorkflowDescriptor→cromwell.core.WorkflowIdcromwell.backend.BackendWorkflowDescriptor→cromwell.core.WorkflowOptions
- Direction
- cromwell.backend uses cromwell.core, so a change to cromwell.core can break cromwell.backend, while a change to cromwell.backend can't break cromwell.core.
- Position
- Below the diagonal: cromwell.backend uses a module listed above it, which is the healthy direction.
26→19 cromwell.backend uses cromwell.backend.async✕
- Connections
- 1 pair of types, where a type in cromwell.backend uses a type in cromwell.backend.async.
- The types involved
cromwell.backend.BackendWorkflowInitializationActor→cromwell.backend.async.RuntimeAttributeValidationFailure
- Direction
- cromwell.backend uses cromwell.backend.async, so a change to cromwell.backend.async can break cromwell.backend, while a change to cromwell.backend can't break cromwell.backend.async.
- Position
- Below the diagonal: cromwell.backend uses a module listed above it, which is the healthy direction.
26→20 cromwell.backend uses cromwell.core.io✕
- Connections
- 2 pairs of types, where a type in cromwell.backend uses a type in cromwell.core.io.
- The types involved
cromwell.backend.ReadLikeFunctions→cromwell.core.io.AsyncIoFunctionscromwell.backend.WriteFunctions→cromwell.core.io.AsyncIoFunctions
- Direction
- cromwell.backend uses cromwell.core.io, so a change to cromwell.core.io can break cromwell.backend, while a change to cromwell.backend can't break cromwell.core.io.
- Position
- Below the diagonal: cromwell.backend uses a module listed above it, which is the healthy direction.
26→24 cromwell.backend uses cromwell.docker✕
- Connections
- 1 pair of types, where a type in cromwell.backend uses a type in cromwell.docker.
- The types involved
cromwell.backend.BackendLifecycleActorFactory→cromwell.docker.DockerMirroring
- Direction
- cromwell.backend uses cromwell.docker, so a change to cromwell.docker can break cromwell.backend, while a change to cromwell.backend can't break cromwell.docker.
- Position
- Below the diagonal: cromwell.backend uses a module listed above it, which is the healthy direction.
27→1 cromwell.backend.standard.callcaching uses cromwell.core.callcaching✕
- Connections
- 2 pairs of types, where a type in cromwell.backend.standard.callcaching uses a type in cromwell.core.callcaching.
- The types involved
cromwell.backend.standard.callcaching.DefaultStandardFileHashingActor→cromwell.core.callcaching.FileHashStrategycromwell.backend.standard.callcaching.FileHashContext→cromwell.core.callcaching.HashKey
- Direction
- cromwell.backend.standard.callcaching uses cromwell.core.callcaching, so a change to cromwell.core.callcaching can break cromwell.backend.standard.callcaching, while a change to cromwell.backend.standard.callcaching can't break cromwell.core.callcaching.
- Position
- Below the diagonal: cromwell.backend.standard.callcaching uses a module listed above it, which is the healthy direction.
27→20 cromwell.backend.standard.callcaching uses cromwell.core.io✕
- Connections
- 3 pairs of types, where a type in cromwell.backend.standard.callcaching uses a type in cromwell.core.io.
- The types involved
cromwell.backend.standard.callcaching.DefaultStandardFileHashingActor→cromwell.core.io.IoCommandBuildercromwell.backend.standard.callcaching.RootWorkflowFileHashCacheActor→cromwell.core.io.IoAckcromwell.backend.standard.callcaching.RootWorkflowFileHashCacheActor→cromwell.core.io.IoClientHelper
- Direction
- cromwell.backend.standard.callcaching uses cromwell.core.io, so a change to cromwell.core.io can break cromwell.backend.standard.callcaching, while a change to cromwell.backend.standard.callcaching can't break cromwell.core.io.
- Position
- Below the diagonal: cromwell.backend.standard.callcaching uses a module listed above it, which is the healthy direction.
27→26 cromwell.backend.standard.callcaching uses cromwell.backend✕
- Connections
- 14 pairs of types, where a type in cromwell.backend.standard.callcaching uses a type in cromwell.backend.
- The types involved
cromwell.backend.standard.callcaching.DefaultStandardCacheHitCopyingActorParams→cromwell.backend.BackendConfigurationDescriptorcromwell.backend.standard.callcaching.DefaultStandardCacheHitCopyingActorParams→cromwell.backend.BackendInitializationDatacromwell.backend.standard.callcaching.DefaultStandardCacheHitCopyingActorParams→cromwell.backend.BackendJobDescriptorcromwell.backend.standard.callcaching.DefaultStandardFileHashingActorParams→cromwell.backend.BackendConfigurationDescriptorcromwell.backend.standard.callcaching.DefaultStandardFileHashingActorParams→cromwell.backend.BackendInitializationDatacromwell.backend.standard.callcaching.DefaultStandardFileHashingActorParams→cromwell.backend.BackendJobDescriptorcromwell.backend.standard.callcaching.JobCachingActorHelper→cromwell.backend.BackendConfigurationDescriptorcromwell.backend.standard.callcaching.JobCachingActorHelper→cromwell.backend.BackendJobDescriptorcromwell.backend.standard.callcaching.StandardCacheHitCopyingActorParams→cromwell.backend.BackendConfigurationDescriptorcromwell.backend.standard.callcaching.StandardCacheHitCopyingActorParams→cromwell.backend.BackendInitializationDatacromwell.backend.standard.callcaching.StandardCacheHitCopyingActorParams→cromwell.backend.BackendJobDescriptorcromwell.backend.standard.callcaching.StandardFileHashingActorParams→cromwell.backend.BackendConfigurationDescriptorcromwell.backend.standard.callcaching.StandardFileHashingActorParams→cromwell.backend.BackendInitializationDatacromwell.backend.standard.callcaching.StandardFileHashingActorParams→cromwell.backend.BackendJobDescriptor
- Direction
- cromwell.backend.standard.callcaching uses cromwell.backend, so a change to cromwell.backend can break cromwell.backend.standard.callcaching, while a change to cromwell.backend.standard.callcaching can't break cromwell.backend.
- Position
- Below the diagonal: cromwell.backend.standard.callcaching uses a module listed above it, which is the healthy direction.
28→5 cromwell.backend.validation uses wom.values✕
- Connections
- 20 pairs of types, where a type in cromwell.backend.validation uses a type in wom.values.
- The types involved
cromwell.backend.validation.BadDefaultAttribute→wom.values.WomValuecromwell.backend.validation.BooleanRuntimeAttributesValidation→wom.values.WomBooleancromwell.backend.validation.ContainersValidation→wom.values.WomValuecromwell.backend.validation.ContinueOnReturnCodeValidation→wom.values.WomValuecromwell.backend.validation.CpuValidation→wom.values.WomValuecromwell.backend.validation.FailOnStderrValidation→wom.values.WomValuecromwell.backend.validation.FloatRuntimeAttributesValidation→wom.values.WomFloatcromwell.backend.validation.GpuRequiredValidation→wom.values.WomBooleancromwell.backend.validation.InformationValidation→wom.values.WomIntegercromwell.backend.validation.InformationValidation→wom.values.WomStringcromwell.backend.validation.IntRuntimeAttributesValidation→wom.values.WomIntegercromwell.backend.validation.MaxRetriesValidation→wom.values.WomValuecromwell.backend.validation.OptionalRuntimeAttributesValidation→wom.values.WomValuecromwell.backend.validation.PositiveIntRuntimeAttributesValidation→wom.values.WomIntegercromwell.backend.validation.PrimitiveRuntimeAttributesValidation→wom.values.WomValuecromwell.backend.validation.RuntimeAttributesDefault→wom.values.WomValuecromwell.backend.validation.RuntimeAttributesValidation→wom.values.WomStringcromwell.backend.validation.RuntimeAttributesValidation→wom.values.WomValuecromwell.backend.validation.StringRuntimeAttributesValidation→wom.values.WomStringcromwell.backend.validation.ValidatedRuntimeAttributesBuilder→wom.values.WomValue
- Direction
- cromwell.backend.validation uses wom.values, so a change to wom.values can break cromwell.backend.validation, while a change to cromwell.backend.validation can't break wom.values.
- Position
- Below the diagonal: cromwell.backend.validation uses a module listed above it, which is the healthy direction.
28→7 cromwell.backend.validation uses wom.types✕
- Connections
- 4 pairs of types, where a type in cromwell.backend.validation uses a type in wom.types.
- The types involved
cromwell.backend.validation.ContainersValidation→wom.types.WomTypecromwell.backend.validation.PrimitiveRuntimeAttributesValidation→wom.types.WomPrimitiveTypecromwell.backend.validation.RuntimeAttributesDefault→wom.types.WomTypecromwell.backend.validation.ValidatedRuntimeAttributesBuilder→wom.types.WomType
- Direction
- cromwell.backend.validation uses wom.types, so a change to wom.types can break cromwell.backend.validation, while a change to cromwell.backend.validation can't break wom.types.
- Position
- Below the diagonal: cromwell.backend.validation uses a module listed above it, which is the healthy direction.
28→16 cromwell.backend.validation uses cromwell.core✕
- Connections
- 1 pair of types, where a type in cromwell.backend.validation uses a type in cromwell.core.
- The types involved
cromwell.backend.validation.RuntimeAttributesDefault→cromwell.core.WorkflowOptions
- Direction
- cromwell.backend.validation uses cromwell.core, so a change to cromwell.core can break cromwell.backend.validation, while a change to cromwell.backend.validation can't break cromwell.core.
- Position
- Below the diagonal: cromwell.backend.validation uses a module listed above it, which is the healthy direction.
28→26 cromwell.backend.validation uses cromwell.backend✕
- Connections
- 1 pair of types, where a type in cromwell.backend.validation uses a type in cromwell.backend.
- The types involved
cromwell.backend.validation.ValidatedRuntimeAttributesBuilder→cromwell.backend.RuntimeAttributeDefinition
- Direction
- cromwell.backend.validation uses cromwell.backend, so a change to cromwell.backend can break cromwell.backend.validation, while a change to cromwell.backend.validation can't break cromwell.backend.
- Position
- Below the diagonal: cromwell.backend.validation uses a module listed above it, which is the healthy direction.
29→1 cromwell.engine uses cromwell.core.callcaching✕
- Connections
- 1 pair of types, where a type in cromwell.engine uses a type in cromwell.core.callcaching.
- The types involved
cromwell.engine.EngineWorkflowDescriptor→cromwell.core.callcaching.CallCachingMode
- Direction
- cromwell.engine uses cromwell.core.callcaching, so a change to cromwell.core.callcaching can break cromwell.engine, while a change to cromwell.engine can't break cromwell.core.callcaching.
- Position
- Below the diagonal: cromwell.engine uses a module listed above it, which is the healthy direction.
29→4 cromwell.engine uses cromwell.core.path✕
- Connections
- 4 pairs of types, where a type in cromwell.engine uses a type in cromwell.core.path.
- The types involved
cromwell.engine.EngineFilesystems→cromwell.core.path.PathBuildercromwell.engine.EngineFilesystems→cromwell.core.path.PathBuilderFactorycromwell.engine.EngineIoFunctions→cromwell.core.path.PathBuildercromwell.engine.EngineWorkflowDescriptor→cromwell.core.path.PathBuilder
- Direction
- cromwell.engine uses cromwell.core.path, so a change to cromwell.core.path can break cromwell.engine, while a change to cromwell.engine can't break cromwell.core.path.
- Position
- Below the diagonal: cromwell.engine uses a module listed above it, which is the healthy direction.
29→5 cromwell.engine uses wom.values✕
- Connections
- 2 pairs of types, where a type in cromwell.engine uses a type in wom.values.
- The types involved
cromwell.engine.EngineIoFunctions→wom.values.WomSingleFilecromwell.engine.EnhancedCallOutputMap→wom.values.WomValue
- Direction
- cromwell.engine uses wom.values, so a change to wom.values can break cromwell.engine, while a change to cromwell.engine can't break wom.values.
- Position
- Below the diagonal: cromwell.engine uses a module listed above it, which is the healthy direction.
29→10 cromwell.engine uses wom✕
- Connections
- 1 pair of types, where a type in cromwell.engine uses a type in wom.
- The types involved
cromwell.engine.EnhancedCallOutputMap→wom.JobOutput
- Direction
- cromwell.engine uses wom, so a change to wom can break cromwell.engine, while a change to cromwell.engine can't break wom.
- Position
- Below the diagonal: cromwell.engine uses a module listed above it, which is the healthy direction.
29→13 cromwell.engine uses wom.callable✕
- Connections
- 1 pair of types, where a type in cromwell.engine uses a type in wom.callable.
- The types involved
cromwell.engine.EngineWorkflowDescriptor→wom.callable.Callable
- Direction
- cromwell.engine uses wom.callable, so a change to wom.callable can break cromwell.engine, while a change to cromwell.engine can't break wom.callable.
- Position
- Below the diagonal: cromwell.engine uses a module listed above it, which is the healthy direction.
29→15 cromwell.engine uses wom.graph✕
- Connections
- 1 pair of types, where a type in cromwell.engine uses a type in wom.graph.
- The types involved
cromwell.engine.EngineWorkflowDescriptor→wom.graph.CommandCallNode
- Direction
- cromwell.engine uses wom.graph, so a change to wom.graph can break cromwell.engine, while a change to cromwell.engine can't break wom.graph.
- Position
- Below the diagonal: cromwell.engine uses a module listed above it, which is the healthy direction.
29→16 cromwell.engine uses cromwell.core✕
- Connections
- 1 pair of types, where a type in cromwell.engine uses a type in cromwell.core.
- The types involved
cromwell.engine.EngineFilesystems→cromwell.core.WorkflowOptions
- Direction
- cromwell.engine uses cromwell.core, so a change to cromwell.core can break cromwell.engine, while a change to cromwell.engine can't break cromwell.core.
- Position
- Below the diagonal: cromwell.engine uses a module listed above it, which is the healthy direction.
29→20 cromwell.engine uses cromwell.core.io✕
- Connections
- 2 pairs of types, where a type in cromwell.engine uses a type in cromwell.core.io.
- The types involved
cromwell.engine.EngineIoFunctions→cromwell.core.io.AsyncIocromwell.engine.EngineIoFunctions→cromwell.core.io.WorkflowCorePathFunctions
- Direction
- cromwell.engine uses cromwell.core.io, so a change to cromwell.core.io can break cromwell.engine, while a change to cromwell.engine can't break cromwell.core.io.
- Position
- Below the diagonal: cromwell.engine uses a module listed above it, which is the healthy direction.
29→26 cromwell.engine uses cromwell.backend✕
- Connections
- 2 pairs of types, where a type in cromwell.engine uses a type in cromwell.backend.
- The types involved
cromwell.engine.EngineIoFunctions→cromwell.backend.ReadLikeFunctionscromwell.engine.EngineWorkflowDescriptor→cromwell.backend.BackendWorkflowDescriptor
- Direction
- cromwell.engine uses cromwell.backend, so a change to cromwell.backend can break cromwell.engine, while a change to cromwell.engine can't break cromwell.backend.
- Position
- Below the diagonal: cromwell.engine uses a module listed above it, which is the healthy direction.
30→4 cromwell.backend.standard uses cromwell.core.path✕
- Connections
- 8 pairs of types, where a type in cromwell.backend.standard uses a type in cromwell.core.path.
- The types involved
cromwell.backend.standard.LocalizedAdHocValue→cromwell.core.path.Pathcromwell.backend.standard.StandardAsyncExecutionActor→cromwell.core.path.Pathcromwell.backend.standard.StandardCachingActorHelper→cromwell.core.path.Pathcromwell.backend.standard.StandardExpressionFunctions→cromwell.core.path.Pathcromwell.backend.standard.StandardExpressionFunctions→cromwell.core.path.PathBuildercromwell.backend.standard.StandardFinalizationActor→cromwell.core.path.Pathcromwell.backend.standard.StandardInitializationActor→cromwell.core.path.PathBuildercromwell.backend.standard.StandardLifecycleActorFactory→cromwell.core.path.Path
- Direction
- cromwell.backend.standard uses cromwell.core.path, so a change to cromwell.core.path can break cromwell.backend.standard, while a change to cromwell.backend.standard can't break cromwell.core.path.
- Position
- Below the diagonal: cromwell.backend.standard uses a module listed above it, which is the healthy direction.
30→5 cromwell.backend.standard uses wom.values✕
- Connections
- 5 pairs of types, where a type in cromwell.backend.standard uses a type in wom.values.
- The types involved
cromwell.backend.standard.StandardAsyncExecutionActor→wom.values.WomFilecromwell.backend.standard.StandardAsyncExecutionActor→wom.values.WomGlobFilecromwell.backend.standard.StandardAsyncExecutionActor→wom.values.WomUnlistedDirectorycromwell.backend.standard.StandardAsyncExecutionActor→wom.values.WomValuecromwell.backend.standard.StandardInitializationActor→wom.values.WomValue
- Direction
- cromwell.backend.standard uses wom.values, so a change to wom.values can break cromwell.backend.standard, while a change to cromwell.backend.standard can't break wom.values.
- Position
- Below the diagonal: cromwell.backend.standard uses a module listed above it, which is the healthy direction.
30→9 cromwell.backend.standard uses wom.expression✕
- Connections
- 1 pair of types, where a type in cromwell.backend.standard uses a type in wom.expression.
- The types involved
cromwell.backend.standard.StandardLifecycleActorFactory→wom.expression.IoFunctionSet
- Direction
- cromwell.backend.standard uses wom.expression, so a change to wom.expression can break cromwell.backend.standard, while a change to cromwell.backend.standard can't break wom.expression.
- Position
- Below the diagonal: cromwell.backend.standard uses a module listed above it, which is the healthy direction.
30→10 cromwell.backend.standard uses wom✕
- Connections
- 2 pairs of types, where a type in cromwell.backend.standard uses a type in wom.
- The types involved
cromwell.backend.standard.StandardAsyncExecutionActor→wom.CommandSetupSideEffectFilecromwell.backend.standard.StandardAsyncExecutionActor→wom.InstantiatedCommand
- Direction
- cromwell.backend.standard uses wom, so a change to wom can break cromwell.backend.standard, while a change to cromwell.backend.standard can't break wom.
- Position
- Below the diagonal: cromwell.backend.standard uses a module listed above it, which is the healthy direction.
30→13 cromwell.backend.standard uses wom.callable✕
- Connections
- 2 pairs of types, where a type in cromwell.backend.standard uses a type in wom.callable.
- The types involved
cromwell.backend.standard.LocalizedAdHocValue→wom.callable.AdHocValuecromwell.backend.standard.StandardAsyncExecutionActor→wom.callable.AdHocValue
- Direction
- cromwell.backend.standard uses wom.callable, so a change to wom.callable can break cromwell.backend.standard, while a change to cromwell.backend.standard can't break wom.callable.
- Position
- Below the diagonal: cromwell.backend.standard uses a module listed above it, which is the healthy direction.
30→15 cromwell.backend.standard uses wom.graph✕
- Connections
- 8 pairs of types, where a type in cromwell.backend.standard uses a type in wom.graph.
- The types involved
cromwell.backend.standard.DefaultInitializationActorParams→wom.graph.CommandCallNodecromwell.backend.standard.DefaultStandardFinalizationActorParams→wom.graph.CommandCallNodecromwell.backend.standard.StandardCachingActorHelper→wom.graph.CommandCallNodecromwell.backend.standard.StandardFinalizationActor→wom.graph.CommandCallNodecromwell.backend.standard.StandardFinalizationActorParams→wom.graph.CommandCallNodecromwell.backend.standard.StandardInitializationActor→wom.graph.CommandCallNodecromwell.backend.standard.StandardInitializationActorParams→wom.graph.CommandCallNodecromwell.backend.standard.StandardLifecycleActorFactory→wom.graph.CommandCallNode
- Direction
- cromwell.backend.standard uses wom.graph, so a change to wom.graph can break cromwell.backend.standard, while a change to cromwell.backend.standard can't break wom.graph.
- Position
- Below the diagonal: cromwell.backend.standard uses a module listed above it, which is the healthy direction.
30→16 cromwell.backend.standard uses cromwell.core✕
- Connections
- 9 pairs of types, where a type in cromwell.backend.standard uses a type in cromwell.core.
- The types involved
cromwell.backend.standard.DefaultStandardExpressionFunctionsParams→cromwell.core.CallContextcromwell.backend.standard.DefaultStandardFinalizationActorParams→cromwell.core.CallOutputscromwell.backend.standard.StandardAsyncExecutionActor→cromwell.core.ExecutionEventcromwell.backend.standard.StandardExpressionFunctions→cromwell.core.CallContextcromwell.backend.standard.StandardExpressionFunctionsParams→cromwell.core.CallContextcromwell.backend.standard.StandardFinalizationActor→cromwell.core.CallOutputscromwell.backend.standard.StandardFinalizationActorParams→cromwell.core.CallOutputscromwell.backend.standard.StandardInitializationActor→cromwell.core.WorkflowOptionscromwell.backend.standard.StandardLifecycleActorFactory→cromwell.core.CallOutputs
- Direction
- cromwell.backend.standard uses cromwell.core, so a change to cromwell.core can break cromwell.backend.standard, while a change to cromwell.backend.standard can't break cromwell.core.
- Position
- Below the diagonal: cromwell.backend.standard uses a module listed above it, which is the healthy direction.
30→19 cromwell.backend.standard uses cromwell.backend.async✕
- Connections
- 5 pairs of types, where a type in cromwell.backend.standard uses a type in cromwell.backend.async.
- The types involved
cromwell.backend.standard.StandardAsyncExecutionActor→cromwell.backend.async.AsyncBackendJobExecutionActorcromwell.backend.standard.StandardAsyncExecutionActor→cromwell.backend.async.ExecutionHandlecromwell.backend.standard.StandardAsyncExecutionActor→cromwell.backend.async.FailedExecutionHandlecromwell.backend.standard.StandardAsyncExecutionActor→cromwell.backend.async.FailedNonRetryableExecutionHandlecromwell.backend.standard.StandardAsyncExecutionActor→cromwell.backend.async.FailedRetryableExecutionHandle
- Direction
- cromwell.backend.standard uses cromwell.backend.async, so a change to cromwell.backend.async can break cromwell.backend.standard, while a change to cromwell.backend.standard can't break cromwell.backend.async.
- Position
- Below the diagonal: cromwell.backend.standard uses a module listed above it, which is the healthy direction.
30→20 cromwell.backend.standard uses cromwell.core.io✕
- Connections
- 4 pairs of types, where a type in cromwell.backend.standard uses a type in cromwell.core.io.
- The types involved
cromwell.backend.standard.StandardAsyncExecutionActor→cromwell.core.io.AsyncIoActorClientcromwell.backend.standard.StandardAsyncExecutionActor→cromwell.core.io.IoCommandBuildercromwell.backend.standard.StandardExpressionFunctions→cromwell.core.io.CallCorePathFunctionscromwell.backend.standard.StandardExpressionFunctions→cromwell.core.io.IoCommandBuilder
- Direction
- cromwell.backend.standard uses cromwell.core.io, so a change to cromwell.core.io can break cromwell.backend.standard, while a change to cromwell.backend.standard can't break cromwell.core.io.
- Position
- Below the diagonal: cromwell.backend.standard uses a module listed above it, which is the healthy direction.
30→26 cromwell.backend.standard uses cromwell.backend✕
- Connections
- 50 pairs of types, where a type in cromwell.backend.standard uses a type in cromwell.backend. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
cromwell.backend.standard.DefaultInitializationActorParams→cromwell.backend.BackendConfigurationDescriptorcromwell.backend.standard.DefaultInitializationActorParams→cromwell.backend.BackendWorkflowDescriptorcromwell.backend.standard.DefaultStandardAsyncExecutionActorParams→cromwell.backend.BackendConfigurationDescriptorcromwell.backend.standard.DefaultStandardAsyncExecutionActorParams→cromwell.backend.BackendInitializationDatacromwell.backend.standard.DefaultStandardAsyncExecutionActorParams→cromwell.backend.BackendJobDescriptorcromwell.backend.standard.DefaultStandardAsyncExecutionActorParams→cromwell.backend.MinimumRuntimeSettingscromwell.backend.standard.DefaultStandardFinalizationActorParams→cromwell.backend.BackendConfigurationDescriptorcromwell.backend.standard.DefaultStandardFinalizationActorParams→cromwell.backend.BackendInitializationDatacromwell.backend.standard.DefaultStandardFinalizationActorParams→cromwell.backend.BackendWorkflowDescriptorcromwell.backend.standard.DefaultStandardSyncExecutionActorParams→cromwell.backend.BackendConfigurationDescriptorcromwell.backend.standard.DefaultStandardSyncExecutionActorParams→cromwell.backend.BackendInitializationDatacromwell.backend.standard.DefaultStandardSyncExecutionActorParams→cromwell.backend.BackendJobDescriptorcromwell.backend.standard.DefaultStandardSyncExecutionActorParams→cromwell.backend.MinimumRuntimeSettingscromwell.backend.standard.StandardAsyncExecutionActor→cromwell.backend.BackendConfigurationDescriptorcromwell.backend.standard.StandardAsyncExecutionActor→cromwell.backend.BackendInitializationDatacromwell.backend.standard.StandardAsyncExecutionActor→cromwell.backend.BackendJobDescriptorcromwell.backend.standard.StandardAsyncExecutionActor→cromwell.backend.PlatformSpecificcromwell.backend.standard.StandardAsyncExecutionActor→cromwell.backend.SlowJobWarningcromwell.backend.standard.StandardCachingActorHelper→cromwell.backend.BackendInitializationDatacromwell.backend.standard.StandardCachingActorHelper→cromwell.backend.BackendWorkflowDescriptorcromwell.backend.standard.StandardExpressionFunctions→cromwell.backend.ReadLikeFunctionscromwell.backend.standard.StandardExpressionFunctions→cromwell.backend.WriteFunctionscromwell.backend.standard.StandardFinalizationActor→cromwell.backend.BackendConfigurationDescriptorcromwell.backend.standard.StandardFinalizationActor→cromwell.backend.BackendInitializationDatacromwell.backend.standard.StandardFinalizationActor→cromwell.backend.BackendWorkflowDescriptor
- Direction
- cromwell.backend.standard uses cromwell.backend, so a change to cromwell.backend can break cromwell.backend.standard, while a change to cromwell.backend.standard can't break cromwell.backend.
- Position
- Below the diagonal: cromwell.backend.standard uses a module listed above it, which is the healthy direction.
30→27 cromwell.backend.standard uses cromwell.backend.standard.callcaching✕
- Connections
- 4 pairs of types, where a type in cromwell.backend.standard uses a type in cromwell.backend.standard.callcaching.
- The types involved
cromwell.backend.standard.StandardCachingActorHelper→cromwell.backend.standard.callcaching.JobCachingActorHelpercromwell.backend.standard.StandardLifecycleActorFactory→cromwell.backend.standard.callcaching.BlacklistCachecromwell.backend.standard.StandardLifecycleActorFactory→cromwell.backend.standard.callcaching.StandardCacheHitCopyingActorParamscromwell.backend.standard.StandardLifecycleActorFactory→cromwell.backend.standard.callcaching.StandardFileHashingActorParams
- Direction
- cromwell.backend.standard uses cromwell.backend.standard.callcaching, so a change to cromwell.backend.standard.callcaching can break cromwell.backend.standard, while a change to cromwell.backend.standard can't break cromwell.backend.standard.callcaching.
- Position
- Below the diagonal: cromwell.backend.standard uses a module listed above it, which is the healthy direction.
30→28 cromwell.backend.standard uses cromwell.backend.validation✕
- Connections
- 3 pairs of types, where a type in cromwell.backend.standard uses a type in cromwell.backend.validation.
- The types involved
cromwell.backend.standard.StandardAsyncExecutionActor→cromwell.backend.validation.ContinueOnReturnCodecromwell.backend.standard.StandardCachingActorHelper→cromwell.backend.validation.ValidatedRuntimeAttributescromwell.backend.standard.StandardValidatedRuntimeAttributesBuilder→cromwell.backend.validation.RuntimeAttributesValidation
- Direction
- cromwell.backend.standard uses cromwell.backend.validation, so a change to cromwell.backend.validation can break cromwell.backend.standard, while a change to cromwell.backend.standard can't break cromwell.backend.validation.
- Position
- Below the diagonal: cromwell.backend.standard uses a module listed above it, which is the healthy direction.
31→3 cromwell.engine.workflow.lifecycle.execution uses cromwell.services.instrumentation✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution uses a type in cromwell.services.instrumentation.
- The types involved
cromwell.engine.workflow.lifecycle.execution.WorkflowExecutionActor→cromwell.services.instrumentation.CromwellInstrumentation
- Direction
- cromwell.engine.workflow.lifecycle.execution uses cromwell.services.instrumentation, so a change to cromwell.services.instrumentation can break cromwell.engine.workflow.lifecycle.execution, while a change to cromwell.engine.workflow.lifecycle.execution can't break cromwell.services.instrumentation.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution uses a module listed above it, which is the healthy direction.
31→4 cromwell.engine.workflow.lifecycle.execution uses cromwell.core.path✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution uses a type in cromwell.core.path.
- The types involved
cromwell.engine.workflow.lifecycle.execution.CallMetadataHelper→cromwell.core.path.FileRelocationMap
- Direction
- cromwell.engine.workflow.lifecycle.execution uses cromwell.core.path, so a change to cromwell.core.path can break cromwell.engine.workflow.lifecycle.execution, while a change to cromwell.engine.workflow.lifecycle.execution can't break cromwell.core.path.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution uses a module listed above it, which is the healthy direction.
31→5 cromwell.engine.workflow.lifecycle.execution uses wom.values✕
- Connections
- 3 pairs of types, where a type in cromwell.engine.workflow.lifecycle.execution uses a type in wom.values.
- The types involved
cromwell.engine.workflow.lifecycle.execution.CallMetadataHelper→wom.values.WomValuecromwell.engine.workflow.lifecycle.execution.WorkflowExecutionActor→wom.values.WomValuecromwell.engine.workflow.lifecycle.execution.keys→wom.values.WomOptionalValue
- Direction
- cromwell.engine.workflow.lifecycle.execution uses wom.values, so a change to wom.values can break cromwell.engine.workflow.lifecycle.execution, while a change to cromwell.engine.workflow.lifecycle.execution can't break wom.values.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution uses a module listed above it, which is the healthy direction.
31→8 cromwell.engine.workflow.lifecycle.execution uses wom.graph.GraphNodePort✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution uses a type in wom.graph.GraphNodePort.
- The types involved
cromwell.engine.workflow.lifecycle.execution.WorkflowExecutionActor→wom.graph.GraphNodePort.OutputPort
- Direction
- cromwell.engine.workflow.lifecycle.execution uses wom.graph.GraphNodePort, so a change to wom.graph.GraphNodePort can break cromwell.engine.workflow.lifecycle.execution, while a change to cromwell.engine.workflow.lifecycle.execution can't break wom.graph.GraphNodePort.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution uses a module listed above it, which is the healthy direction.
31→15 cromwell.engine.workflow.lifecycle.execution uses wom.graph✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution uses a type in wom.graph.
- The types involved
cromwell.engine.workflow.lifecycle.execution.WorkflowExecutionActor→wom.graph.CommandCallNode
- Direction
- cromwell.engine.workflow.lifecycle.execution uses wom.graph, so a change to wom.graph can break cromwell.engine.workflow.lifecycle.execution, while a change to cromwell.engine.workflow.lifecycle.execution can't break wom.graph.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution uses a module listed above it, which is the healthy direction.
31→16 cromwell.engine.workflow.lifecycle.execution uses cromwell.core✕
- Connections
- 16 pairs of types, where a type in cromwell.engine.workflow.lifecycle.execution uses a type in cromwell.core.
- The types involved
cromwell.engine.workflow.lifecycle.execution.CallMetadataHelper→cromwell.core.CallKeycromwell.engine.workflow.lifecycle.execution.CallMetadataHelper→cromwell.core.CallOutputscromwell.engine.workflow.lifecycle.execution.CallMetadataHelper→cromwell.core.ExecutionEventcromwell.engine.workflow.lifecycle.execution.CallMetadataHelper→cromwell.core.ExecutionStatuscromwell.engine.workflow.lifecycle.execution.CallMetadataHelper→cromwell.core.JobKeycromwell.engine.workflow.lifecycle.execution.CallMetadataHelper→cromwell.core.WorkflowIdcromwell.engine.workflow.lifecycle.execution.JobRunning→cromwell.core.CallKeycromwell.engine.workflow.lifecycle.execution.JobStarting→cromwell.core.CallKeycromwell.engine.workflow.lifecycle.execution.SubWorkflowExecutionActor→cromwell.core.ExecutionEventcromwell.engine.workflow.lifecycle.execution.SubWorkflowExecutionActor→cromwell.core.WorkflowIdcromwell.engine.workflow.lifecycle.execution.WorkflowExecutionActor→cromwell.core.CallOutputscromwell.engine.workflow.lifecycle.execution.WorkflowExecutionActor→cromwell.core.JobKeycromwell.engine.workflow.lifecycle.execution.WorkflowExecutionActor→cromwell.core.PossiblyNotRootWorkflowIdcromwell.engine.workflow.lifecycle.execution.WorkflowExecutionActor→cromwell.core.RootWorkflowIdcromwell.engine.workflow.lifecycle.execution.WorkflowExecutionActor→cromwell.core.WorkflowIdcromwell.engine.workflow.lifecycle.execution.keys→cromwell.core.JobKey
- Direction
- cromwell.engine.workflow.lifecycle.execution uses cromwell.core, so a change to cromwell.core can break cromwell.engine.workflow.lifecycle.execution, while a change to cromwell.engine.workflow.lifecycle.execution can't break cromwell.core.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution uses a module listed above it, which is the healthy direction.
31→20 cromwell.engine.workflow.lifecycle.execution uses cromwell.core.io✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution uses a type in cromwell.core.io.
- The types involved
cromwell.engine.workflow.lifecycle.execution.WorkflowExecutionActorData→cromwell.core.io.AsyncIo
- Direction
- cromwell.engine.workflow.lifecycle.execution uses cromwell.core.io, so a change to cromwell.core.io can break cromwell.engine.workflow.lifecycle.execution, while a change to cromwell.engine.workflow.lifecycle.execution can't break cromwell.core.io.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution uses a module listed above it, which is the healthy direction.
31→26 cromwell.engine.workflow.lifecycle.execution uses cromwell.backend✕
- Connections
- 3 pairs of types, where a type in cromwell.engine.workflow.lifecycle.execution uses a type in cromwell.backend.
- The types involved
cromwell.engine.workflow.lifecycle.execution.SubWorkflowExecutionActor→cromwell.backend.BackendWorkflowDescriptorcromwell.engine.workflow.lifecycle.execution.WorkflowExecutionActor→cromwell.backend.BackendJobDescriptorKeycromwell.engine.workflow.lifecycle.execution.WorkflowExecutionActor→cromwell.backend.BackendLifecycleActorFactory
- Direction
- cromwell.engine.workflow.lifecycle.execution uses cromwell.backend, so a change to cromwell.backend can break cromwell.engine.workflow.lifecycle.execution, while a change to cromwell.engine.workflow.lifecycle.execution can't break cromwell.backend.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution uses a module listed above it, which is the healthy direction.
31→29 cromwell.engine.workflow.lifecycle.execution uses cromwell.engine✕
- Connections
- 3 pairs of types, where a type in cromwell.engine.workflow.lifecycle.execution uses a type in cromwell.engine.
- The types involved
cromwell.engine.workflow.lifecycle.execution.SubWorkflowExecutionActor→cromwell.engine.EngineWorkflowDescriptorcromwell.engine.workflow.lifecycle.execution.WorkflowExecutionActor→cromwell.engine.EngineWorkflowDescriptorcromwell.engine.workflow.lifecycle.execution.WorkflowExecutionActorData→cromwell.engine.EngineWorkflowDescriptor
- Direction
- cromwell.engine.workflow.lifecycle.execution uses cromwell.engine, so a change to cromwell.engine can break cromwell.engine.workflow.lifecycle.execution, while a change to cromwell.engine.workflow.lifecycle.execution can't break cromwell.engine.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution uses a module listed above it, which is the healthy direction.
32→2 cromwell.engine.workflow.workflowstore uses cromwell.database.sql.tables✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.workflowstore uses a type in cromwell.database.sql.tables.
- The types involved
cromwell.engine.workflow.workflowstore.InMemorySubWorkflowStore→cromwell.database.sql.tables.SubWorkflowStoreEntry
- Direction
- cromwell.engine.workflow.workflowstore uses cromwell.database.sql.tables, so a change to cromwell.database.sql.tables can break cromwell.engine.workflow.workflowstore, while a change to cromwell.engine.workflow.workflowstore can't break cromwell.database.sql.tables.
- Position
- Below the diagonal: cromwell.engine.workflow.workflowstore uses a module listed above it, which is the healthy direction.
32→3 cromwell.engine.workflow.workflowstore uses cromwell.services.instrumentation✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.workflowstore uses a type in cromwell.services.instrumentation.
- The types involved
cromwell.engine.workflow.workflowstore.WorkflowStoreEngineActor→cromwell.services.instrumentation.CromwellInstrumentationScheduler
- Direction
- cromwell.engine.workflow.workflowstore uses cromwell.services.instrumentation, so a change to cromwell.services.instrumentation can break cromwell.engine.workflow.workflowstore, while a change to cromwell.engine.workflow.workflowstore can't break cromwell.services.instrumentation.
- Position
- Below the diagonal: cromwell.engine.workflow.workflowstore uses a module listed above it, which is the healthy direction.
32→16 cromwell.engine.workflow.workflowstore uses cromwell.core✕
- Connections
- 18 pairs of types, where a type in cromwell.engine.workflow.workflowstore uses a type in cromwell.core.
- The types involved
cromwell.engine.workflow.workflowstore.CoordinatedWorkflowStoreAccess→cromwell.core.WorkflowIdcromwell.engine.workflow.workflowstore.InMemoryWorkflowStore→cromwell.core.WorkflowIdcromwell.engine.workflow.workflowstore.InMemoryWorkflowStore→cromwell.core.WorkflowSourceFilesCollectioncromwell.engine.workflow.workflowstore.UncoordinatedWorkflowStoreAccess→cromwell.core.WorkflowIdcromwell.engine.workflow.workflowstore.WorkflowIdAndSources→cromwell.core.WorkflowIdcromwell.engine.workflow.workflowstore.WorkflowIdAndSources→cromwell.core.WorkflowSourceFilesCollectioncromwell.engine.workflow.workflowstore.WorkflowStore→cromwell.core.WorkflowIdcromwell.engine.workflow.workflowstore.WorkflowStore→cromwell.core.WorkflowSourceFilesCollectioncromwell.engine.workflow.workflowstore.WorkflowStoreAccess→cromwell.core.WorkflowIdcromwell.engine.workflow.workflowstore.WorkflowStoreSubmitActor→cromwell.core.MonitoringCompanionHelpercromwell.engine.workflow.workflowstore.WorkflowStoreSubmitActor→cromwell.core.WorkflowIdcromwell.engine.workflow.workflowstore.WorkflowStoreSubmitActor→cromwell.core.WorkflowOptionscromwell.engine.workflow.workflowstore.WorkflowStoreSubmitActor→cromwell.core.WorkflowSourceFilesCollectioncromwell.engine.workflow.workflowstore.WorkflowStoreSubmitActor→cromwell.core.WorkflowStatecromwell.engine.workflow.workflowstore.WorkflowToStart→cromwell.core.HasWorkflowIdAndSourcescromwell.engine.workflow.workflowstore.WorkflowToStart→cromwell.core.HogGroupcromwell.engine.workflow.workflowstore.WorkflowToStart→cromwell.core.WorkflowIdcromwell.engine.workflow.workflowstore.WorkflowToStart→cromwell.core.WorkflowSourceFilesCollection
- Direction
- cromwell.engine.workflow.workflowstore uses cromwell.core, so a change to cromwell.core can break cromwell.engine.workflow.workflowstore, while a change to cromwell.engine.workflow.workflowstore can't break cromwell.core.
- Position
- Below the diagonal: cromwell.engine.workflow.workflowstore uses a module listed above it, which is the healthy direction.
32→29 cromwell.engine.workflow.workflowstore uses cromwell.engine✕
- Connections
- 2 pairs of types, where a type in cromwell.engine.workflow.workflowstore uses a type in cromwell.engine.
- The types involved
cromwell.engine.workflow.workflowstore.WorkflowStoreActor→cromwell.engine.CromwellTerminatorcromwell.engine.workflow.workflowstore.WorkflowStoreHeartbeatWriteActor→cromwell.engine.CromwellTerminator
- Direction
- cromwell.engine.workflow.workflowstore uses cromwell.engine, so a change to cromwell.engine can break cromwell.engine.workflow.workflowstore, while a change to cromwell.engine.workflow.workflowstore can't break cromwell.engine.
- Position
- Below the diagonal: cromwell.engine.workflow.workflowstore uses a module listed above it, which is the healthy direction.
33→4 cromwell.backend.google.batch.models uses cromwell.core.path✕
- Connections
- 5 pairs of types, where a type in cromwell.backend.google.batch.models uses a type in cromwell.core.path.
- The types involved
cromwell.backend.google.batch.models.BatchParameter→cromwell.core.path.Pathcromwell.backend.google.batch.models.GcpBatchDirectoryInput→cromwell.core.path.Pathcromwell.backend.google.batch.models.GcpBatchDirectoryOutput→cromwell.core.path.Pathcromwell.backend.google.batch.models.GcpBatchFileInput→cromwell.core.path.Pathcromwell.backend.google.batch.models.GcpBatchFileOutput→cromwell.core.path.Path
- Direction
- cromwell.backend.google.batch.models uses cromwell.core.path, so a change to cromwell.core.path can break cromwell.backend.google.batch.models, while a change to cromwell.backend.google.batch.models can't break cromwell.core.path.
- Position
- Below the diagonal: cromwell.backend.google.batch.models uses a module listed above it, which is the healthy direction.
33→5 cromwell.backend.google.batch.models uses wom.values✕
- Connections
- 4 pairs of types, where a type in cromwell.backend.google.batch.models uses a type in wom.values.
- The types involved
cromwell.backend.google.batch.models.BootDiskSizeValidation→wom.values.WomIntegercromwell.backend.google.batch.models.BootDiskSizeValidation→wom.values.WomValuecromwell.backend.google.batch.models.DisksValidation→wom.values.WomValuecromwell.backend.google.batch.models.ZonesValidation→wom.values.WomValue
- Direction
- cromwell.backend.google.batch.models uses wom.values, so a change to wom.values can break cromwell.backend.google.batch.models, while a change to cromwell.backend.google.batch.models can't break wom.values.
- Position
- Below the diagonal: cromwell.backend.google.batch.models uses a module listed above it, which is the healthy direction.
33→7 cromwell.backend.google.batch.models uses wom.types✕
- Connections
- 2 pairs of types, where a type in cromwell.backend.google.batch.models uses a type in wom.types.
- The types involved
cromwell.backend.google.batch.models.DisksValidation→wom.types.WomTypecromwell.backend.google.batch.models.ZonesValidation→wom.types.WomType
- Direction
- cromwell.backend.google.batch.models uses wom.types, so a change to wom.types can break cromwell.backend.google.batch.models, while a change to cromwell.backend.google.batch.models can't break wom.types.
- Position
- Below the diagonal: cromwell.backend.google.batch.models uses a module listed above it, which is the healthy direction.
33→16 cromwell.backend.google.batch.models uses cromwell.core✕
- Connections
- 2 pairs of types, where a type in cromwell.backend.google.batch.models uses a type in cromwell.core.
- The types involved
cromwell.backend.google.batch.models.GcpBatchRequest→cromwell.core.WorkflowIdcromwell.backend.google.batch.models.RunStatus→cromwell.core.ExecutionEvent
- Direction
- cromwell.backend.google.batch.models uses cromwell.core, so a change to cromwell.core can break cromwell.backend.google.batch.models, while a change to cromwell.backend.google.batch.models can't break cromwell.core.
- Position
- Below the diagonal: cromwell.backend.google.batch.models uses a module listed above it, which is the healthy direction.
33→24 cromwell.backend.google.batch.models uses cromwell.docker✕
- Connections
- 1 pair of types, where a type in cromwell.backend.google.batch.models uses a type in cromwell.docker.
- The types involved
cromwell.backend.google.batch.models.GcpBatchConfigurationAttributes→cromwell.docker.DockerMirroring
- Direction
- cromwell.backend.google.batch.models uses cromwell.docker, so a change to cromwell.docker can break cromwell.backend.google.batch.models, while a change to cromwell.backend.google.batch.models can't break cromwell.docker.
- Position
- Below the diagonal: cromwell.backend.google.batch.models uses a module listed above it, which is the healthy direction.
33→26 cromwell.backend.google.batch.models uses cromwell.backend✕
- Connections
- 2 pairs of types, where a type in cromwell.backend.google.batch.models uses a type in cromwell.backend.
- The types involved
cromwell.backend.google.batch.models.CreateGcpBatchParameters→cromwell.backend.BackendJobDescriptorcromwell.backend.google.batch.models.GcpBatchConfiguration→cromwell.backend.BackendConfigurationDescriptor
- Direction
- cromwell.backend.google.batch.models uses cromwell.backend, so a change to cromwell.backend can break cromwell.backend.google.batch.models, while a change to cromwell.backend.google.batch.models can't break cromwell.backend.
- Position
- Below the diagonal: cromwell.backend.google.batch.models uses a module listed above it, which is the healthy direction.
33→28 cromwell.backend.google.batch.models uses cromwell.backend.validation✕
- Connections
- 4 pairs of types, where a type in cromwell.backend.google.batch.models uses a type in cromwell.backend.validation.
- The types involved
cromwell.backend.google.batch.models.BootDiskSizeValidation→cromwell.backend.validation.IntRuntimeAttributesValidationcromwell.backend.google.batch.models.DisksValidation→cromwell.backend.validation.RuntimeAttributesValidationcromwell.backend.google.batch.models.GcpBatchRuntimeAttributes→cromwell.backend.validation.ContinueOnReturnCodecromwell.backend.google.batch.models.ZonesValidation→cromwell.backend.validation.RuntimeAttributesValidation
- Direction
- cromwell.backend.google.batch.models uses cromwell.backend.validation, so a change to cromwell.backend.validation can break cromwell.backend.google.batch.models, while a change to cromwell.backend.google.batch.models can't break cromwell.backend.validation.
- Position
- Below the diagonal: cromwell.backend.google.batch.models uses a module listed above it, which is the healthy direction.
33→30 cromwell.backend.google.batch.models uses cromwell.backend.standard✕
- Connections
- 3 pairs of types, where a type in cromwell.backend.google.batch.models uses a type in cromwell.backend.standard.
- The types involved
cromwell.backend.google.batch.models.GcpBackendInitializationData→cromwell.backend.standard.StandardInitializationDatacromwell.backend.google.batch.models.GcpBackendInitializationData→cromwell.backend.standard.StandardValidatedRuntimeAttributesBuildercromwell.backend.google.batch.models.Run→cromwell.backend.standard.StandardAsyncJob
- Direction
- cromwell.backend.google.batch.models uses cromwell.backend.standard, so a change to cromwell.backend.standard can break cromwell.backend.google.batch.models, while a change to cromwell.backend.google.batch.models can't break cromwell.backend.standard.
- Position
- Below the diagonal: cromwell.backend.google.batch.models uses a module listed above it, which is the healthy direction.
33→40 cromwell.backend.google.batch.models uses cromwell.backend.google.batch.api part of a loop✕
- Connections
- 1 pair of types, where a type in cromwell.backend.google.batch.models uses a type in cromwell.backend.google.batch.api.
- The types involved
cromwell.backend.google.batch.models.GcpBackendInitializationData→cromwell.backend.google.batch.api.GcpBatchRequestFactory
- Direction
- cromwell.backend.google.batch.models uses cromwell.backend.google.batch.api, so a change to cromwell.backend.google.batch.api can break cromwell.backend.google.batch.models, while a change to cromwell.backend.google.batch.models can't break cromwell.backend.google.batch.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→4 cromwell.backend.impl.aws uses cromwell.core.path✕
- Connections
- 4 pairs of types, where a type in cromwell.backend.impl.aws uses a type in cromwell.core.path.
- The types involved
cromwell.backend.impl.aws.AwsBatchExpressionFunctionsForFS→cromwell.core.path.Pathcromwell.backend.impl.aws.AwsBatchFileInput→cromwell.core.path.Pathcromwell.backend.impl.aws.AwsBatchFileOutput→cromwell.core.path.Pathcromwell.backend.impl.aws.AwsBatchJobCachingActorHelper→cromwell.core.path.Path
- Direction
- cromwell.backend.impl.aws uses cromwell.core.path, so a change to cromwell.core.path can break cromwell.backend.impl.aws, while a change to cromwell.backend.impl.aws can't break cromwell.core.path.
- Position
- Below the diagonal: cromwell.backend.impl.aws uses a module listed above it, which is the healthy direction.
34→5 cromwell.backend.impl.aws uses wom.values✕
- Connections
- 4 pairs of types, where a type in cromwell.backend.impl.aws uses a type in wom.values.
- The types involved
cromwell.backend.impl.aws.AwsBatchEvaluateOnExitValidation→wom.values.WomValuecromwell.backend.impl.aws.DisksValidation→wom.values.WomValuecromwell.backend.impl.aws.UlimitsValidation→wom.values.WomValuecromwell.backend.impl.aws.ZonesValidation→wom.values.WomValue
- Direction
- cromwell.backend.impl.aws uses wom.values, so a change to wom.values can break cromwell.backend.impl.aws, while a change to cromwell.backend.impl.aws can't break wom.values.
- Position
- Below the diagonal: cromwell.backend.impl.aws uses a module listed above it, which is the healthy direction.
34→7 cromwell.backend.impl.aws uses wom.types✕
- Connections
- 4 pairs of types, where a type in cromwell.backend.impl.aws uses a type in wom.types.
- The types involved
cromwell.backend.impl.aws.AwsBatchEvaluateOnExitValidation→wom.types.WomTypecromwell.backend.impl.aws.DisksValidation→wom.types.WomTypecromwell.backend.impl.aws.UlimitsValidation→wom.types.WomTypecromwell.backend.impl.aws.ZonesValidation→wom.types.WomType
- Direction
- cromwell.backend.impl.aws uses wom.types, so a change to wom.types can break cromwell.backend.impl.aws, while a change to cromwell.backend.impl.aws can't break wom.types.
- Position
- Below the diagonal: cromwell.backend.impl.aws uses a module listed above it, which is the healthy direction.
34→15 cromwell.backend.impl.aws uses wom.graph✕
- Connections
- 3 pairs of types, where a type in cromwell.backend.impl.aws uses a type in wom.graph.
- The types involved
cromwell.backend.impl.aws.AwsBatchBackendLifecycleActorFactory→wom.graph.CommandCallNodecromwell.backend.impl.aws.AwsBatchFinalizationActorParams→wom.graph.CommandCallNodecromwell.backend.impl.aws.AwsBatchInitializationActorParams→wom.graph.CommandCallNode
- Direction
- cromwell.backend.impl.aws uses wom.graph, so a change to wom.graph can break cromwell.backend.impl.aws, while a change to cromwell.backend.impl.aws can't break wom.graph.
- Position
- Below the diagonal: cromwell.backend.impl.aws uses a module listed above it, which is the healthy direction.
34→16 cromwell.backend.impl.aws uses cromwell.core✕
- Connections
- 2 pairs of types, where a type in cromwell.backend.impl.aws uses a type in cromwell.core.
- The types involved
cromwell.backend.impl.aws.AwsBatchBackendLifecycleActorFactory→cromwell.core.CallOutputscromwell.backend.impl.aws.AwsBatchFinalizationActorParams→cromwell.core.CallOutputs
- Direction
- cromwell.backend.impl.aws uses cromwell.core, so a change to cromwell.core can break cromwell.backend.impl.aws, while a change to cromwell.backend.impl.aws can't break cromwell.core.
- Position
- Below the diagonal: cromwell.backend.impl.aws uses a module listed above it, which is the healthy direction.
34→20 cromwell.backend.impl.aws uses cromwell.core.io✕
- Connections
- 3 pairs of types, where a type in cromwell.backend.impl.aws uses a type in cromwell.core.io.
- The types involved
cromwell.backend.impl.aws.AwsBatchExpressionFunctions→cromwell.core.io.IoCommandBuildercromwell.backend.impl.aws.AwsBatchFinalizationActor→cromwell.core.io.AsyncIoActorClientcromwell.backend.impl.aws.AwsBatchInitializationActor→cromwell.core.io.AsyncIoActorClient
- Direction
- cromwell.backend.impl.aws uses cromwell.core.io, so a change to cromwell.core.io can break cromwell.backend.impl.aws, while a change to cromwell.backend.impl.aws can't break cromwell.core.io.
- Position
- Below the diagonal: cromwell.backend.impl.aws uses a module listed above it, which is the healthy direction.
34→24 cromwell.backend.impl.aws uses cromwell.docker✕
- Connections
- 2 pairs of types, where a type in cromwell.backend.impl.aws uses a type in cromwell.docker.
- The types involved
cromwell.backend.impl.aws.AwsBatchBackendLifecycleActorFactory→cromwell.docker.DockerMirroringcromwell.backend.impl.aws.AwsBatchConfiguration→cromwell.docker.DockerMirroring
- Direction
- cromwell.backend.impl.aws uses cromwell.docker, so a change to cromwell.docker can break cromwell.backend.impl.aws, while a change to cromwell.backend.impl.aws can't break cromwell.docker.
- Position
- Below the diagonal: cromwell.backend.impl.aws uses a module listed above it, which is the healthy direction.
34→26 cromwell.backend.impl.aws uses cromwell.backend✕
- Connections
- 14 pairs of types, where a type in cromwell.backend.impl.aws uses a type in cromwell.backend.
- The types involved
cromwell.backend.impl.aws.AwsBatchBackendLifecycleActorFactory→cromwell.backend.AwsPlatformcromwell.backend.impl.aws.AwsBatchBackendLifecycleActorFactory→cromwell.backend.BackendConfigurationDescriptorcromwell.backend.impl.aws.AwsBatchBackendLifecycleActorFactory→cromwell.backend.BackendInitializationDatacromwell.backend.impl.aws.AwsBatchBackendLifecycleActorFactory→cromwell.backend.BackendWorkflowDescriptorcromwell.backend.impl.aws.AwsBatchConfiguration→cromwell.backend.BackendConfigurationDescriptorcromwell.backend.impl.aws.AwsBatchFinalizationActorParams→cromwell.backend.BackendConfigurationDescriptorcromwell.backend.impl.aws.AwsBatchFinalizationActorParams→cromwell.backend.BackendInitializationDatacromwell.backend.impl.aws.AwsBatchFinalizationActorParams→cromwell.backend.BackendWorkflowDescriptorcromwell.backend.impl.aws.AwsBatchInitializationActor→cromwell.backend.BackendInitializationDatacromwell.backend.impl.aws.AwsBatchInitializationActorParams→cromwell.backend.BackendConfigurationDescriptorcromwell.backend.impl.aws.AwsBatchInitializationActorParams→cromwell.backend.BackendWorkflowDescriptorcromwell.backend.impl.aws.AwsBatchJob→cromwell.backend.Awscromwell.backend.impl.aws.AwsBatchJob→cromwell.backend.BackendJobDescriptorcromwell.backend.impl.aws.AwsReadLikeFunctions→cromwell.backend.ReadLikeFunctions
- Direction
- cromwell.backend.impl.aws uses cromwell.backend, so a change to cromwell.backend can break cromwell.backend.impl.aws, while a change to cromwell.backend.impl.aws can't break cromwell.backend.
- Position
- Below the diagonal: cromwell.backend.impl.aws uses a module listed above it, which is the healthy direction.
34→28 cromwell.backend.impl.aws uses cromwell.backend.validation✕
- Connections
- 5 pairs of types, where a type in cromwell.backend.impl.aws uses a type in cromwell.backend.validation.
- The types involved
cromwell.backend.impl.aws.AwsBatchEvaluateOnExitValidation→cromwell.backend.validation.RuntimeAttributesValidationcromwell.backend.impl.aws.AwsBatchRuntimeAttributes→cromwell.backend.validation.ContinueOnReturnCodecromwell.backend.impl.aws.DisksValidation→cromwell.backend.validation.RuntimeAttributesValidationcromwell.backend.impl.aws.UlimitsValidation→cromwell.backend.validation.RuntimeAttributesValidationcromwell.backend.impl.aws.ZonesValidation→cromwell.backend.validation.RuntimeAttributesValidation
- Direction
- cromwell.backend.impl.aws uses cromwell.backend.validation, so a change to cromwell.backend.validation can break cromwell.backend.impl.aws, while a change to cromwell.backend.impl.aws can't break cromwell.backend.validation.
- Position
- Below the diagonal: cromwell.backend.impl.aws uses a module listed above it, which is the healthy direction.
34→30 cromwell.backend.impl.aws uses cromwell.backend.standard✕
- Connections
- 15 pairs of types, where a type in cromwell.backend.impl.aws uses a type in cromwell.backend.standard.
- The types involved
cromwell.backend.impl.aws.AwsBatchBackendInitializationData→cromwell.backend.standard.StandardInitializationDatacromwell.backend.impl.aws.AwsBatchBackendInitializationData→cromwell.backend.standard.StandardValidatedRuntimeAttributesBuildercromwell.backend.impl.aws.AwsBatchBackendLifecycleActorFactory→cromwell.backend.standard.StandardFinalizationActorParamscromwell.backend.impl.aws.AwsBatchBackendLifecycleActorFactory→cromwell.backend.standard.StandardInitializationActorParamscromwell.backend.impl.aws.AwsBatchBackendLifecycleActorFactory→cromwell.backend.standard.StandardLifecycleActorFactorycromwell.backend.impl.aws.AwsBatchExpressionFunctions→cromwell.backend.standard.StandardExpressionFunctionscromwell.backend.impl.aws.AwsBatchExpressionFunctions→cromwell.backend.standard.StandardExpressionFunctionsParamscromwell.backend.impl.aws.AwsBatchExpressionFunctionsForFS→cromwell.backend.standard.StandardExpressionFunctionscromwell.backend.impl.aws.AwsBatchFinalizationActor→cromwell.backend.standard.StandardFinalizationActorcromwell.backend.impl.aws.AwsBatchFinalizationActorParams→cromwell.backend.standard.StandardFinalizationActorParamscromwell.backend.impl.aws.AwsBatchInitializationActor→cromwell.backend.standard.StandardInitializationActorcromwell.backend.impl.aws.AwsBatchInitializationActor→cromwell.backend.standard.StandardValidatedRuntimeAttributesBuildercromwell.backend.impl.aws.AwsBatchInitializationActorParams→cromwell.backend.standard.StandardInitializationActorParamscromwell.backend.impl.aws.AwsBatchJobCachingActorHelper→cromwell.backend.standard.StandardCachingActorHelpercromwell.backend.impl.aws.AwsReadLikeFunctions→cromwell.backend.standard.StandardExpressionFunctionsParams
- Direction
- cromwell.backend.impl.aws uses cromwell.backend.standard, so a change to cromwell.backend.standard can break cromwell.backend.impl.aws, while a change to cromwell.backend.impl.aws can't break cromwell.backend.standard.
- Position
- Below the diagonal: cromwell.backend.impl.aws uses a module listed above it, which is the healthy direction.
35→1 cromwell.engine.workflow.lifecycle.execution.callcaching uses cromwell.core.callcaching✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution.callcaching uses a type in cromwell.core.callcaching.
- The types involved
cromwell.engine.workflow.lifecycle.execution.callcaching.CallCacheHashingJobActor→cromwell.core.callcaching.HashResult
- Direction
- cromwell.engine.workflow.lifecycle.execution.callcaching uses cromwell.core.callcaching, so a change to cromwell.core.callcaching can break cromwell.engine.workflow.lifecycle.execution.callcaching, while a change to cromwell.engine.workflow.lifecycle.execution.callcaching can't break cromwell.core.callcaching.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.callcaching uses a module listed above it, which is the healthy direction.
35→2 cromwell.engine.workflow.lifecycle.execution.callcaching uses cromwell.database.sql.tables✕
- Connections
- 2 pairs of types, where a type in cromwell.engine.workflow.lifecycle.execution.callcaching uses a type in cromwell.database.sql.tables.
- The types involved
cromwell.engine.workflow.lifecycle.execution.callcaching.CallCache→cromwell.database.sql.tables.CallCachingEntrycromwell.engine.workflow.lifecycle.execution.callcaching.CallCacheInvalidatedSuccess→cromwell.database.sql.tables.CallCachingEntry
- Direction
- cromwell.engine.workflow.lifecycle.execution.callcaching uses cromwell.database.sql.tables, so a change to cromwell.database.sql.tables can break cromwell.engine.workflow.lifecycle.execution.callcaching, while a change to cromwell.engine.workflow.lifecycle.execution.callcaching can't break cromwell.database.sql.tables.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.callcaching uses a module listed above it, which is the healthy direction.
35→4 cromwell.engine.workflow.lifecycle.execution.callcaching uses cromwell.core.path✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution.callcaching uses a type in cromwell.core.path.
- The types involved
cromwell.engine.workflow.lifecycle.execution.callcaching.CallCache→cromwell.core.path.Path
- Direction
- cromwell.engine.workflow.lifecycle.execution.callcaching uses cromwell.core.path, so a change to cromwell.core.path can break cromwell.engine.workflow.lifecycle.execution.callcaching, while a change to cromwell.engine.workflow.lifecycle.execution.callcaching can't break cromwell.core.path.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.callcaching uses a module listed above it, which is the healthy direction.
35→16 cromwell.engine.workflow.lifecycle.execution.callcaching uses cromwell.core✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution.callcaching uses a type in cromwell.core.
- The types involved
cromwell.engine.workflow.lifecycle.execution.callcaching.EngineJobHashingActor→cromwell.core.WorkflowId
- Direction
- cromwell.engine.workflow.lifecycle.execution.callcaching uses cromwell.core, so a change to cromwell.core can break cromwell.engine.workflow.lifecycle.execution.callcaching, while a change to cromwell.engine.workflow.lifecycle.execution.callcaching can't break cromwell.core.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.callcaching uses a module listed above it, which is the healthy direction.
35→22 cromwell.engine.workflow.lifecycle.execution.callcaching uses cromwell.services.metadata✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution.callcaching uses a type in cromwell.services.metadata.
- The types involved
cromwell.engine.workflow.lifecycle.execution.callcaching.CallCacheDiffActor→cromwell.services.metadata.MetadataQuery
- Direction
- cromwell.engine.workflow.lifecycle.execution.callcaching uses cromwell.services.metadata, so a change to cromwell.services.metadata can break cromwell.engine.workflow.lifecycle.execution.callcaching, while a change to cromwell.engine.workflow.lifecycle.execution.callcaching can't break cromwell.services.metadata.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.callcaching uses a module listed above it, which is the healthy direction.
35→31 cromwell.engine.workflow.lifecycle.execution.callcaching uses cromwell.engine.workflow.lifecycle.execution✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution.callcaching uses a type in cromwell.engine.workflow.lifecycle.execution.
- The types involved
cromwell.engine.workflow.lifecycle.execution.callcaching.EngineJobHashingActor→cromwell.engine.workflow.lifecycle.execution.CallMetadataHelper
- Direction
- cromwell.engine.workflow.lifecycle.execution.callcaching uses cromwell.engine.workflow.lifecycle.execution, so a change to cromwell.engine.workflow.lifecycle.execution can break cromwell.engine.workflow.lifecycle.execution.callcaching, while a change to cromwell.engine.workflow.lifecycle.execution.callcaching can't break cromwell.engine.workflow.lifecycle.execution.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.callcaching uses a module listed above it, which is the healthy direction.
36→1 cromwell.engine.workflow.lifecycle.execution.job.preparation uses cromwell.core.callcaching✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution.job.preparation uses a type in cromwell.core.callcaching.
- The types involved
cromwell.engine.workflow.lifecycle.execution.job.preparation.JobPreparationActor→cromwell.core.callcaching.MaybeCallCachingEligible
- Direction
- cromwell.engine.workflow.lifecycle.execution.job.preparation uses cromwell.core.callcaching, so a change to cromwell.core.callcaching can break cromwell.engine.workflow.lifecycle.execution.job.preparation, while a change to cromwell.engine.workflow.lifecycle.execution.job.preparation can't break cromwell.core.callcaching.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.job.preparation uses a module listed above it, which is the healthy direction.
36→5 cromwell.engine.workflow.lifecycle.execution.job.preparation uses wom.values✕
- Connections
- 2 pairs of types, where a type in cromwell.engine.workflow.lifecycle.execution.job.preparation uses a type in wom.values.
- The types involved
cromwell.engine.workflow.lifecycle.execution.job.preparation.JobPreparationActor→wom.values.WomValuecromwell.engine.workflow.lifecycle.execution.job.preparation.SubWorkflowPreparationActor→wom.values.WomValue
- Direction
- cromwell.engine.workflow.lifecycle.execution.job.preparation uses wom.values, so a change to wom.values can break cromwell.engine.workflow.lifecycle.execution.job.preparation, while a change to cromwell.engine.workflow.lifecycle.execution.job.preparation can't break wom.values.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.job.preparation uses a module listed above it, which is the healthy direction.
36→8 cromwell.engine.workflow.lifecycle.execution.job.preparation uses wom.graph.GraphNodePort✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution.job.preparation uses a type in wom.graph.GraphNodePort.
- The types involved
cromwell.engine.workflow.lifecycle.execution.job.preparation.SubWorkflowPreparationActor→wom.graph.GraphNodePort.OutputPort
- Direction
- cromwell.engine.workflow.lifecycle.execution.job.preparation uses wom.graph.GraphNodePort, so a change to wom.graph.GraphNodePort can break cromwell.engine.workflow.lifecycle.execution.job.preparation, while a change to cromwell.engine.workflow.lifecycle.execution.job.preparation can't break wom.graph.GraphNodePort.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.job.preparation uses a module listed above it, which is the healthy direction.
36→9 cromwell.engine.workflow.lifecycle.execution.job.preparation uses wom.expression✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution.job.preparation uses a type in wom.expression.
- The types involved
cromwell.engine.workflow.lifecycle.execution.job.preparation.CallPreparation→wom.expression.IoFunctionSet
- Direction
- cromwell.engine.workflow.lifecycle.execution.job.preparation uses wom.expression, so a change to wom.expression can break cromwell.engine.workflow.lifecycle.execution.job.preparation, while a change to cromwell.engine.workflow.lifecycle.execution.job.preparation can't break wom.expression.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.job.preparation uses a module listed above it, which is the healthy direction.
36→15 cromwell.engine.workflow.lifecycle.execution.job.preparation uses wom.graph✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution.job.preparation uses a type in wom.graph.
- The types involved
cromwell.engine.workflow.lifecycle.execution.job.preparation.SubWorkflowPreparationActor→wom.graph.GraphInputNode
- Direction
- cromwell.engine.workflow.lifecycle.execution.job.preparation uses wom.graph, so a change to wom.graph can break cromwell.engine.workflow.lifecycle.execution.job.preparation, while a change to cromwell.engine.workflow.lifecycle.execution.job.preparation can't break wom.graph.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.job.preparation uses a module listed above it, which is the healthy direction.
36→16 cromwell.engine.workflow.lifecycle.execution.job.preparation uses cromwell.core✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution.job.preparation uses a type in cromwell.core.
- The types involved
cromwell.engine.workflow.lifecycle.execution.job.preparation.CallPreparation→cromwell.core.CallKey
- Direction
- cromwell.engine.workflow.lifecycle.execution.job.preparation uses cromwell.core, so a change to cromwell.core can break cromwell.engine.workflow.lifecycle.execution.job.preparation, while a change to cromwell.engine.workflow.lifecycle.execution.job.preparation can't break cromwell.core.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.job.preparation uses a module listed above it, which is the healthy direction.
36→24 cromwell.engine.workflow.lifecycle.execution.job.preparation uses cromwell.docker✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution.job.preparation uses a type in cromwell.docker.
- The types involved
cromwell.engine.workflow.lifecycle.execution.job.preparation.JobPreparationActor→cromwell.docker.DockerHashResult
- Direction
- cromwell.engine.workflow.lifecycle.execution.job.preparation uses cromwell.docker, so a change to cromwell.docker can break cromwell.engine.workflow.lifecycle.execution.job.preparation, while a change to cromwell.engine.workflow.lifecycle.execution.job.preparation can't break cromwell.docker.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.job.preparation uses a module listed above it, which is the healthy direction.
36→26 cromwell.engine.workflow.lifecycle.execution.job.preparation uses cromwell.backend✕
- Connections
- 2 pairs of types, where a type in cromwell.engine.workflow.lifecycle.execution.job.preparation uses a type in cromwell.backend.
- The types involved
cromwell.engine.workflow.lifecycle.execution.job.preparation.JobPreparationActor→cromwell.backend.BackendInitializationDatacromwell.engine.workflow.lifecycle.execution.job.preparation.JobPreparationActor→cromwell.backend.BackendJobDescriptor
- Direction
- cromwell.engine.workflow.lifecycle.execution.job.preparation uses cromwell.backend, so a change to cromwell.backend can break cromwell.engine.workflow.lifecycle.execution.job.preparation, while a change to cromwell.engine.workflow.lifecycle.execution.job.preparation can't break cromwell.backend.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.job.preparation uses a module listed above it, which is the healthy direction.
36→31 cromwell.engine.workflow.lifecycle.execution.job.preparation uses cromwell.engine.workflow.lifecycle.execution✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution.job.preparation uses a type in cromwell.engine.workflow.lifecycle.execution.
- The types involved
cromwell.engine.workflow.lifecycle.execution.job.preparation.JobPreparationActor→cromwell.engine.workflow.lifecycle.execution.CallMetadataHelper
- Direction
- cromwell.engine.workflow.lifecycle.execution.job.preparation uses cromwell.engine.workflow.lifecycle.execution, so a change to cromwell.engine.workflow.lifecycle.execution can break cromwell.engine.workflow.lifecycle.execution.job.preparation, while a change to cromwell.engine.workflow.lifecycle.execution.job.preparation can't break cromwell.engine.workflow.lifecycle.execution.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.job.preparation uses a module listed above it, which is the healthy direction.
37→8 cromwell.jobstore uses wom.graph.GraphNodePort✕
- Connections
- 2 pairs of types, where a type in cromwell.jobstore uses a type in wom.graph.GraphNodePort.
- The types involved
cromwell.jobstore.JobStore→wom.graph.GraphNodePort.OutputPortcromwell.jobstore.SqlJobStore→wom.graph.GraphNodePort.OutputPort
- Direction
- cromwell.jobstore uses wom.graph.GraphNodePort, so a change to wom.graph.GraphNodePort can break cromwell.jobstore, while a change to cromwell.jobstore can't break wom.graph.GraphNodePort.
- Position
- Below the diagonal: cromwell.jobstore uses a module listed above it, which is the healthy direction.
37→16 cromwell.jobstore uses cromwell.core✕
- Connections
- 4 pairs of types, where a type in cromwell.jobstore uses a type in cromwell.core.
- The types involved
cromwell.jobstore.EnhancedJobKey→cromwell.core.JobKeycromwell.jobstore.EnhancedJobKey→cromwell.core.WorkflowIdcromwell.jobstore.JobResultSuccess→cromwell.core.CallOutputscromwell.jobstore.JobStoreKey→cromwell.core.WorkflowId
- Direction
- cromwell.jobstore uses cromwell.core, so a change to cromwell.core can break cromwell.jobstore, while a change to cromwell.jobstore can't break cromwell.core.
- Position
- Below the diagonal: cromwell.jobstore uses a module listed above it, which is the healthy direction.
37→26 cromwell.jobstore uses cromwell.backend✕
- Connections
- 1 pair of types, where a type in cromwell.jobstore uses a type in cromwell.backend.
- The types involved
cromwell.jobstore.JobResult→cromwell.backend.BackendJobDescriptorKey
- Direction
- cromwell.jobstore uses cromwell.backend, so a change to cromwell.backend can break cromwell.jobstore, while a change to cromwell.jobstore can't break cromwell.backend.
- Position
- Below the diagonal: cromwell.jobstore uses a module listed above it, which is the healthy direction.
37→32 cromwell.jobstore uses cromwell.engine.workflow.workflowstore✕
- Connections
- 1 pair of types, where a type in cromwell.jobstore uses a type in cromwell.engine.workflow.workflowstore.
- The types involved
cromwell.jobstore.JobStoreWriterActor→cromwell.engine.workflow.workflowstore.WorkflowStoreAccess
- Direction
- cromwell.jobstore uses cromwell.engine.workflow.workflowstore, so a change to cromwell.engine.workflow.workflowstore can break cromwell.jobstore, while a change to cromwell.jobstore can't break cromwell.engine.workflow.workflowstore.
- Position
- Below the diagonal: cromwell.jobstore uses a module listed above it, which is the healthy direction.
38→4 cromwell.backend.google.batch.util uses cromwell.core.path✕
- Connections
- 2 pairs of types, where a type in cromwell.backend.google.batch.util uses a type in cromwell.core.path.
- The types involved
cromwell.backend.google.batch.util.BatchExpressionFunctions→cromwell.core.path.Pathcromwell.backend.google.batch.util.RuntimeOutputMapping→cromwell.core.path.Path
- Direction
- cromwell.backend.google.batch.util uses cromwell.core.path, so a change to cromwell.core.path can break cromwell.backend.google.batch.util, while a change to cromwell.backend.google.batch.util can't break cromwell.core.path.
- Position
- Below the diagonal: cromwell.backend.google.batch.util uses a module listed above it, which is the healthy direction.
38→5 cromwell.backend.google.batch.util uses wom.values✕
- Connections
- 1 pair of types, where a type in cromwell.backend.google.batch.util uses a type in wom.values.
- The types involved
cromwell.backend.google.batch.util.GpuValidation→wom.values.WomValue
- Direction
- cromwell.backend.google.batch.util uses wom.values, so a change to wom.values can break cromwell.backend.google.batch.util, while a change to cromwell.backend.google.batch.util can't break wom.values.
- Position
- Below the diagonal: cromwell.backend.google.batch.util uses a module listed above it, which is the healthy direction.
38→20 cromwell.backend.google.batch.util uses cromwell.core.io✕
- Connections
- 2 pairs of types, where a type in cromwell.backend.google.batch.util uses a type in cromwell.core.io.
- The types involved
cromwell.backend.google.batch.util.BatchExpressionFunctions→cromwell.core.io.IoCommandBuildercromwell.backend.google.batch.util.BatchPathFunctions→cromwell.core.io.CallCorePathFunctionSet
- Direction
- cromwell.backend.google.batch.util uses cromwell.core.io, so a change to cromwell.core.io can break cromwell.backend.google.batch.util, while a change to cromwell.backend.google.batch.util can't break cromwell.core.io.
- Position
- Below the diagonal: cromwell.backend.google.batch.util uses a module listed above it, which is the healthy direction.
38→28 cromwell.backend.google.batch.util uses cromwell.backend.validation✕
- Connections
- 6 pairs of types, where a type in cromwell.backend.google.batch.util uses a type in cromwell.backend.validation.
- The types involved
cromwell.backend.google.batch.util.GpuTypeValidation→cromwell.backend.validation.OptionalRuntimeAttributesValidationcromwell.backend.google.batch.util.GpuTypeValidation→cromwell.backend.validation.RuntimeAttributesValidationcromwell.backend.google.batch.util.GpuValidation→cromwell.backend.validation.OptionalRuntimeAttributesValidationcromwell.backend.google.batch.util.GpuValidation→cromwell.backend.validation.RuntimeAttributesValidationcromwell.backend.google.batch.util.MachineTypeValidation→cromwell.backend.validation.OptionalRuntimeAttributesValidationcromwell.backend.google.batch.util.MachineTypeValidation→cromwell.backend.validation.RuntimeAttributesValidation
- Direction
- cromwell.backend.google.batch.util uses cromwell.backend.validation, so a change to cromwell.backend.validation can break cromwell.backend.google.batch.util, while a change to cromwell.backend.google.batch.util can't break cromwell.backend.validation.
- Position
- Below the diagonal: cromwell.backend.google.batch.util uses a module listed above it, which is the healthy direction.
38→30 cromwell.backend.google.batch.util uses cromwell.backend.standard✕
- Connections
- 1 pair of types, where a type in cromwell.backend.google.batch.util uses a type in cromwell.backend.standard.
- The types involved
cromwell.backend.google.batch.util.BatchExpressionFunctions→cromwell.backend.standard.StandardExpressionFunctions
- Direction
- cromwell.backend.google.batch.util uses cromwell.backend.standard, so a change to cromwell.backend.standard can break cromwell.backend.google.batch.util, while a change to cromwell.backend.google.batch.util can't break cromwell.backend.standard.
- Position
- Below the diagonal: cromwell.backend.google.batch.util uses a module listed above it, which is the healthy direction.
38→33 cromwell.backend.google.batch.util uses cromwell.backend.google.batch.models✕
- Connections
- 12 pairs of types, where a type in cromwell.backend.google.batch.util uses a type in cromwell.backend.google.batch.models.
- The types involved
cromwell.backend.google.batch.util.BatchUtilityConversions→cromwell.backend.google.batch.models.GcpBatchRuntimeAttributescromwell.backend.google.batch.util.BatchUtilityConversions→cromwell.backend.google.batch.models.GpuResourcecromwell.backend.google.batch.util.GcpBatchParameterConversions→cromwell.backend.google.batch.models.GcpBatchDirectoryInputcromwell.backend.google.batch.util.GcpBatchParameterConversions→cromwell.backend.google.batch.models.GcpBatchDirectoryOutputcromwell.backend.google.batch.util.GcpBatchParameterConversions→cromwell.backend.google.batch.models.GcpBatchFileInputcromwell.backend.google.batch.util.GcpBatchParameterConversions→cromwell.backend.google.batch.models.GcpBatchFileOutputcromwell.backend.google.batch.util.GcpBatchParameterConversions→cromwell.backend.google.batch.models.GcpBatchInputcromwell.backend.google.batch.util.GcpBatchParameterConversions→cromwell.backend.google.batch.models.GcpBatchOutputcromwell.backend.google.batch.util.GcpBatchReferenceFilesMappingOperations→cromwell.backend.google.batch.models.GcpBatchInputcromwell.backend.google.batch.util.GcpBatchReferenceFilesMappingOperations→cromwell.backend.google.batch.models.ManifestFilecromwell.backend.google.batch.util.GcpBatchReferenceFilesMappingOperations→cromwell.backend.google.batch.models.ReferenceFilecromwell.backend.google.batch.util.MachineTypeValidation→cromwell.backend.google.batch.models.MachineType
- Direction
- cromwell.backend.google.batch.util uses cromwell.backend.google.batch.models, so a change to cromwell.backend.google.batch.models can break cromwell.backend.google.batch.util, while a change to cromwell.backend.google.batch.util can't break cromwell.backend.google.batch.models.
- Position
- Below the diagonal: cromwell.backend.google.batch.util uses a module listed above it, which is the healthy direction.
39→1 cromwell.engine.workflow.lifecycle.execution.job uses cromwell.core.callcaching✕
- Connections
- 3 pairs of types, where a type in cromwell.engine.workflow.lifecycle.execution.job uses a type in cromwell.core.callcaching.
- The types involved
cromwell.engine.workflow.lifecycle.execution.job.EngineJobExecutionActor→cromwell.core.callcaching.CallCachingActivitycromwell.engine.workflow.lifecycle.execution.job.EngineJobExecutionActor→cromwell.core.callcaching.CallCachingEligiblecromwell.engine.workflow.lifecycle.execution.job.EngineJobExecutionActor→cromwell.core.callcaching.HashResult
- Direction
- cromwell.engine.workflow.lifecycle.execution.job uses cromwell.core.callcaching, so a change to cromwell.core.callcaching can break cromwell.engine.workflow.lifecycle.execution.job, while a change to cromwell.engine.workflow.lifecycle.execution.job can't break cromwell.core.callcaching.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.job uses a module listed above it, which is the healthy direction.
39→3 cromwell.engine.workflow.lifecycle.execution.job uses cromwell.services.instrumentation✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution.job uses a type in cromwell.services.instrumentation.
- The types involved
cromwell.engine.workflow.lifecycle.execution.job.EngineJobExecutionActor→cromwell.services.instrumentation.CromwellInstrumentation
- Direction
- cromwell.engine.workflow.lifecycle.execution.job uses cromwell.services.instrumentation, so a change to cromwell.services.instrumentation can break cromwell.engine.workflow.lifecycle.execution.job, while a change to cromwell.engine.workflow.lifecycle.execution.job can't break cromwell.services.instrumentation.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.job uses a module listed above it, which is the healthy direction.
39→16 cromwell.engine.workflow.lifecycle.execution.job uses cromwell.core✕
- Connections
- 3 pairs of types, where a type in cromwell.engine.workflow.lifecycle.execution.job uses a type in cromwell.core.
- The types involved
cromwell.engine.workflow.lifecycle.execution.job.EngineJobExecutionActor→cromwell.core.CallOutputscromwell.engine.workflow.lifecycle.execution.job.EngineJobExecutionActor→cromwell.core.ExecutionEventcromwell.engine.workflow.lifecycle.execution.job.EngineJobExecutionActor→cromwell.core.JobKey
- Direction
- cromwell.engine.workflow.lifecycle.execution.job uses cromwell.core, so a change to cromwell.core can break cromwell.engine.workflow.lifecycle.execution.job, while a change to cromwell.engine.workflow.lifecycle.execution.job can't break cromwell.core.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.job uses a module listed above it, which is the healthy direction.
39→26 cromwell.engine.workflow.lifecycle.execution.job uses cromwell.backend✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution.job uses a type in cromwell.backend.
- The types involved
cromwell.engine.workflow.lifecycle.execution.job.EngineJobExecutionActor→cromwell.backend.BackendJobDescriptor
- Direction
- cromwell.engine.workflow.lifecycle.execution.job uses cromwell.backend, so a change to cromwell.backend can break cromwell.engine.workflow.lifecycle.execution.job, while a change to cromwell.engine.workflow.lifecycle.execution.job can't break cromwell.backend.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.job uses a module listed above it, which is the healthy direction.
39→31 cromwell.engine.workflow.lifecycle.execution.job uses cromwell.engine.workflow.lifecycle.execution✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution.job uses a type in cromwell.engine.workflow.lifecycle.execution.
- The types involved
cromwell.engine.workflow.lifecycle.execution.job.EngineJobExecutionActor→cromwell.engine.workflow.lifecycle.execution.CallMetadataHelper
- Direction
- cromwell.engine.workflow.lifecycle.execution.job uses cromwell.engine.workflow.lifecycle.execution, so a change to cromwell.engine.workflow.lifecycle.execution can break cromwell.engine.workflow.lifecycle.execution.job, while a change to cromwell.engine.workflow.lifecycle.execution.job can't break cromwell.engine.workflow.lifecycle.execution.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.job uses a module listed above it, which is the healthy direction.
39→35 cromwell.engine.workflow.lifecycle.execution.job uses cromwell.engine.workflow.lifecycle.execution.callcaching✕
- Connections
- 1 pair of types, where a type in cromwell.engine.workflow.lifecycle.execution.job uses a type in cromwell.engine.workflow.lifecycle.execution.callcaching.
- The types involved
cromwell.engine.workflow.lifecycle.execution.job.EngineJobExecutionActor→cromwell.engine.workflow.lifecycle.execution.callcaching.CallCacheInvalidatedResponse
- Direction
- cromwell.engine.workflow.lifecycle.execution.job uses cromwell.engine.workflow.lifecycle.execution.callcaching, so a change to cromwell.engine.workflow.lifecycle.execution.callcaching can break cromwell.engine.workflow.lifecycle.execution.job, while a change to cromwell.engine.workflow.lifecycle.execution.job can't break cromwell.engine.workflow.lifecycle.execution.callcaching.
- Position
- Below the diagonal: cromwell.engine.workflow.lifecycle.execution.job uses a module listed above it, which is the healthy direction.
40→3 cromwell.backend.google.batch.api uses cromwell.services.instrumentation✕
- Connections
- 2 pairs of types, where a type in cromwell.backend.google.batch.api uses a type in cromwell.services.instrumentation.
- The types involved
cromwell.backend.google.batch.api.BatchApiRequestManager→cromwell.services.instrumentation.CromwellInstrumentationSchedulercromwell.backend.google.batch.api.BatchApiRequestWorker→cromwell.services.instrumentation.CromwellInstrumentationActor
- Direction
- cromwell.backend.google.batch.api uses cromwell.services.instrumentation, so a change to cromwell.services.instrumentation can break cromwell.backend.google.batch.api, while a change to cromwell.backend.google.batch.api can't break cromwell.services.instrumentation.
- Position
- Below the diagonal: cromwell.backend.google.batch.api uses a module listed above it, which is the healthy direction.
40→16 cromwell.backend.google.batch.api uses cromwell.core✕
- Connections
- 1 pair of types, where a type in cromwell.backend.google.batch.api uses a type in cromwell.core.
- The types involved
cromwell.backend.google.batch.api.BatchApiRequestManager→cromwell.core.WorkflowId
- Direction
- cromwell.backend.google.batch.api uses cromwell.core, so a change to cromwell.core can break cromwell.backend.google.batch.api, while a change to cromwell.backend.google.batch.api can't break cromwell.core.
- Position
- Below the diagonal: cromwell.backend.google.batch.api uses a module listed above it, which is the healthy direction.
40→30 cromwell.backend.google.batch.api uses cromwell.backend.standard✕
- Connections
- 1 pair of types, where a type in cromwell.backend.google.batch.api uses a type in cromwell.backend.standard.
- The types involved
cromwell.backend.google.batch.api.BatchApiRequestManager→cromwell.backend.standard.StandardAsyncJob
- Direction
- cromwell.backend.google.batch.api uses cromwell.backend.standard, so a change to cromwell.backend.standard can break cromwell.backend.google.batch.api, while a change to cromwell.backend.google.batch.api can't break cromwell.backend.standard.
- Position
- Below the diagonal: cromwell.backend.google.batch.api uses a module listed above it, which is the healthy direction.
40→33 cromwell.backend.google.batch.api uses cromwell.backend.google.batch.models✕
- Connections
- 3 pairs of types, where a type in cromwell.backend.google.batch.api uses a type in cromwell.backend.google.batch.models.
- The types involved
cromwell.backend.google.batch.api.GcpBatchRequestFactory→cromwell.backend.google.batch.models.GcpBatchRequestcromwell.backend.google.batch.api.GcpBatchRequestFactoryImpl→cromwell.backend.google.batch.models.GcpBatchRequestcromwell.backend.google.batch.api.GcpBatchRequestFactoryImpl→cromwell.backend.google.batch.models.VpcAndSubnetworkProjectLabelValues
- Direction
- cromwell.backend.google.batch.api uses cromwell.backend.google.batch.models, so a change to cromwell.backend.google.batch.models can break cromwell.backend.google.batch.api, while a change to cromwell.backend.google.batch.api can't break cromwell.backend.google.batch.models.
- Position
- Below the diagonal: cromwell.backend.google.batch.api uses a module listed above it, which is the healthy direction.
40→38 cromwell.backend.google.batch.api uses cromwell.backend.google.batch.util✕
- Connections
- 1 pair of types, where a type in cromwell.backend.google.batch.api uses a type in cromwell.backend.google.batch.util.
- The types involved
cromwell.backend.google.batch.api.GcpBatchRequestFactoryImpl→cromwell.backend.google.batch.util.BatchUtilityConversions
- Direction
- cromwell.backend.google.batch.api uses cromwell.backend.google.batch.util, so a change to cromwell.backend.google.batch.util can break cromwell.backend.google.batch.api, while a change to cromwell.backend.google.batch.api can't break cromwell.backend.google.batch.util.
- Position
- Below the diagonal: cromwell.backend.google.batch.api 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 | 45 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 28 | High / Critical |
| A02:2025 — Security Misconfiguration | 15 | High / Critical |
| A07:2025 — Authentication Failures | 1 | High / Critical |
Roadmap
Top priorities: Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 18 sites, not one: `engine/src/main/scala/cromwell/engine/io/nio/NioHashing.scala:66` (DigestUtils.md5Hex), `engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheHashingJobActor.scala:141` (MessageDigest.getInstance("MD5")), `engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheHashingJobActor.scala:293` (MessageDigest.getInstance("MD5")), `engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheHashingJobActor.scala:360` (MessageDigest.getInstance("MD5")), `filesystems/gcs/src/main/scala/cromwell/filesystems/gcs/GcsPathBuilder.scala:314` (DigestUtils.md5Hex), `languageFactories/language-factory-core/src/main/scala/cromwell/languages/util/ImportResolver.scala:180` (MessageDigest.getInstance("MD5")), `supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:787` (MessageDigest.getInstance("MD5")), `supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJobDefinition.scala:374` (MessageDigest.getInstance("SHA-1")), and 10 further site(s). Each is a separate decision — fixing only the line this row cites leaves the others in place; Resolve the 10 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8), REDACTED (2); Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 18 sites, not one: `engine/src/main/scala/cromwell/engine/io/nio/NioHashing.scala:66` (DigestUtils.md5Hex), `engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheHashingJobActor.scala:141` (MessageDigest.getInstance("MD5")), `engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheHashingJobActor.scala:293` (MessageDigest.getInstance("MD5")), `engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheHashingJobActor.scala:360` (MessageDigest.getInstance("MD5")), `filesystems/gcs/src/main/scala/cromwell/filesystems/gcs/GcsPathBuilder.scala:314` (DigestUtils.md5Hex), `languageFactories/language-factory-core/src/main/scala/cromwell/languages/util/ImportResolver.scala:180` (MessageDigest.getInstance("MD5")), `supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:787` (MessageDigest.getInstance("MD5")), `supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJobDefinition.scala:374` (MessageDigest.getInstance("SHA-1")), and 10 further site(s). Each is a separate decision — fixing only the line this row cites leaves the others in place. | +12.0 pts | Medium | Web-Security Posture |
| Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED (2). | +2.6 pts | Low | Static Analysis (SAST) |
| Resolve the 8 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED (2). | +2.5 pts | Low | Dependency Vulnerabilities |
| Resolve the 5 REDACTED finding(s) charged to Static Analysis (SAST) — the other 29 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. | +1.8 pts | Low | Static Analysis (SAST) |
| Resolve the 10 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8), REDACTED (2). | +3.1 pts | Medium | Dependency Vulnerabilities |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +1.5 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +1.5 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.3 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.1 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | 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 | 2.7 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.7 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| wdl/model/draft2/src/main/scala/wdl/draft2/model/AstTools.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| backend/src/main/scala/cromwell/backend/standard/StandardAsyncExecutionActor.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| engine/src/main/scala/cromwell/webservice/routes/wes/WesRouteSupport.scala | 6.0 | Mixed | Explicit Debt: FixmeComment |
| engine/src/main/scala/cromwell/engine/workflow/lifecycle/materialization/MaterializeWorkflowDescriptorActor.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/actors/GcpBatchAsyncBackendJobExecutionActor.scala | 6.0 | 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 60 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 60 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, 716 of 744 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a Codecov configuration (codecov.yml, target 0%) and a coverage step in CI (`codecov/codecov-action`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.scala, .py), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
- 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, .py) and this repository declares an sbt build (repository root, 493 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — 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. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Maven tree, and its score reflects currency alone.
- 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 an sbt build (build.sbt), but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its sbt 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.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/actors/GcpBatchAsyncBackendJobExecutionActor.scala, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c ./docker-setup.sh" did not complete successfully: exit code: 4; runtime evidence skipped.
- 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.
- X4 Structured logging — 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. 11 further occurrence(s) are not listed individually; the score already reflects all 51.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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
23 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ValueEvaluator.evaluate at 85. A further 1 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 WdlExpression.toString at 29 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: wdl/model/draft2/src/main/scala/wdl/draft2/model/WdlExpression.scala (WdlExpression.toString at 29). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 5 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with ValueEvaluator.evaluate (cyclomatic 85), TypeEvaluator.evaluate (cyclomatic 84), WdlNamespace.apply (cyclomatic 54). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 6.3 to about 7.4/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
31 method(s) exceeded the cognitive complexity threshold of 15; the worst was ValueEvaluator.evaluate at 157.
What to do
- Bring the 5 bodies over 60 down to 60 or less in Cognitive Complexity — start with ValueEvaluator.evaluate (cognitive 157), TypeEvaluator.evaluate (cognitive 147), FileEvaluator.evaluateRecursive (cognitive 79). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 5.5 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
13 god class(es) detected.
What to do
- Resolve the 7 FileTooLong finding(s) in God Classes — start with GcpBatchAsyncBackendJobExecutionActor.scala, EngineJobExecutionActor.scala, StandardAsyncExecutionActor.scala. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 6 TooManyMethods finding(s) in God Classes — start with WdlStandardLibraryFunctions.scala (2), BetterFileMethods.scala, StandardAsyncExecutionActor.scala. — One of this dimension's main actionable groups (6 warning-level).
D4 · Code Duplication
49 duplicated block group(s) detected. 2.9 % of the production lines (2,780 of 96,208) are in a reported copy. A further 69 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 2 of the 118 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 8 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with WomFloat.scala (2), EngineFunctionEvaluators.scala, TaskOutput.scala. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 6 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with EngineFunctionEvaluators.scala, GlobFunctions.scala, WomtoolMain.scala. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with WomInteger.scala, MetadataRouteSupport.scala, BinaryOperatorEvaluators.scala. — One of this dimension's main actionable groups (5 warning-level).
D5 · Coupling
51 production modules (Maven+sbt), 0 dependency cycle(s), 2 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 6 module(s) off the main sequence, with abstractness counted on 23 of the 51 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 5 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 Unstable project engine finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Unstable project googlePipelinesCommon finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
6 of 105 classes have LCOM4 above 3.
What to do
- Resolve the 6 Low cohesion finding(s) in Cohesion (LCOM4) — start with TesAsyncBackendJobExecutionActor.scala, WorkflowDockerLookupActor.scala, SubWorkflowExecutionActor.scala. — One of this dimension's main actionable groups (6 warning-level).
D12 · Dependency Hygiene
7 outdated artifact(s) of 8 resolved by the build, graded against Maven Central. Whether any of these is DEPRECATED is not graded — Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Known CVEs in this graph are D30's question, read from the manifest there.
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D14 · License Compliance
0 of 5 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 1 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares an sbt build (build.sbt), 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.
D16 · Bus Factor
13 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/stores/ExecutionStore.scala. Counted over 488 of the 1152 production source files in this repository: 651 are under the ~2,400-byte size floor this dimension measures over, and the remaining 13 have no attributable history left to measure.
D17 · Explicit Debt
87 deducted task-comment markers across 96208 LoC (0.1/KLoC) → score 9.8. 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 78 TodoComment finding(s) in Explicit Debt — start with TesTask.scala (4), MetadataEntryComponent.scala (4), S3PathBuilderSpec.scala (3). — One of this dimension's main actionable groups (78 warning-level).
- Resolve the 9 FixmeComment finding(s) in Explicit Debt — start with SubmissionSupport.scala (3), WesRouteSupport.scala (2), WorkflowDefinition.scala. — One of this dimension's main actionable groups (9 warning-level).
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 94 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with plugins.sbt. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
6 naming inconsistencies among 305 declarations measured against a convention their peers follow.
What to do
- Resolve the 3 `dockerImageID` spells `ID` where 309 names in the project spell it `Id` finding(s) in Naming Consistency — start with DockerRegistryV2Abstract.scala (3). — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 `validateURL` spells `URL` where 25 names in the project spell it `Url` finding(s) in Naming Consistency — start with ConfigUtil.scala. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `generateEnvironmentKVPairs` spells `KV` where 21 names in the project… finding(s) in Naming Consistency — start with AwsBatchJob.scala. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 5 build units (Maven, Python, sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
45 finding(s): 0 critical, 41 high, 3 medium, 1 low. 29 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 3 file(s) — `scripts/reference_disks/create_images.sh` (lines 100–390), `src/ci/bin/test-deadlock.sh` (line 56), `src/ci/bin/test_slurm.inc.sh` (line 55) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 5 REDACTED finding(s) charged to Static Analysis (SAST) — the other 29 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (34 issue-level, 5 of them charged here).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D30 · Dependency Vulnerabilities
19 finding(s): 1 critical, 10 high, 8 medium, 0 low.
What to do
- Resolve the 10 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8), REDACTED (2). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 8 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED (2). — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
15 finding(s): 0 critical, 6 high, 7 medium, 2 low.
What to do
- Resolve the 6 High IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 7 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D34 · Knowledge Freshness
257 of 501 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is engine/src/main/scala/cromwell/engine/workflow/WorkflowActor.scala. Counted over 501 of the 1152 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 254 Orphaned file finding(s) in Knowledge Freshness — start with package.scala (8), BinaryOperatorEvaluators.scala (2), VersionUtil.scala (2). — One of this dimension's main actionable groups (254 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with WorkflowActor.scala, S3FileSystemProvider.java, BetterFileMethods.scala. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: MetadataSqlDatabase.scala↔MetadataDatabaseAccess.scala 100%; REDACTED↔Merging.scala 90%; CallCachingSlickDatabase.scala↔CallCache.scala 64%
What to do
- Resolve the 4 Boundary-crossing change coupling finding(s) in Change Coupling — start with MetadataSqlDatabase.scala (2), CallCachingSlickDatabase.scala, MetadataRouteSupport.scala. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with REDACTED, GcpBatchAsyncBackendJobExecutionActor.scala, JobPaths.scala. — One of this dimension's main actionable groups (3 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 2 platform declaration(s) and 9 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
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `MetadataSqlDatabase` declares 27 abstract members: `existsMetadataEntries`, `addMetadataEntries`, `metadataSummaryEntryExists`, `queryMetadataEntries`, `streamMetadataEntries`, `queryMetadataEntries`, `queryMetadataEntries`, `queryMetadataEntries`, `queryMetadataEntryWithKeyConstraints`, `summarizeIncreasing`, `summarizeDecreasing`, `updateMetadataArchiveStatus`, `getWorkflowStatus`, `getWorkflowLabels`, `getRootAndSubworkflowLabels`, `queryWorkflowSummaries`, `countWorkflowSummaries`, `deleteAllMetadataForWorkflowAndUpdateArchiveStatus`, `getRootWorkflowId`, `queryWorkflowIdsByArchiveStatusAndEndedOnOrBeforeThresholdTimestamp`, `getSummaryQueueSize`, `getMetadataArchiveStatusAndEndTime`, `queryWorkflowsToArchiveThatEndedOnOrBeforeThresholdTimestamp`, `countWorkflowsLeftToArchiveThatEndedOnOrBeforeThresholdTimestamp`, `countWorkflowsLeftToDeleteThatEndedOnOrBeforeThresholdTimestamp`, `getMetadataTableSizeInformation`, `getFailedJobsMetadataWithWorkflowId`. 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. Those 27 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — database/sql/src/main/scala/cromwell/database/sql/MetadataSqlDatabase.scala:12
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code
- `glob` is a shipped member whose whole body is still a "not implemented" error, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — engine/src/main/scala/cromwell/engine/EngineIoFunctions.scala:16
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
- `throwableToFalse` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×3) — centaur/src/main/scala/centaur/api/Retry.scala:47, common/src/main/scala/common/util/IORetry.scala:67, core/src/main/scala/cromwell/core/path/CustomRetryParams.scala:19
- `glob` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — engine/src/main/scala/cromwell/engine/EngineIoFunctions.scala:16
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×5) — server/src/test/scala/cromwell/engine/WorkflowAbortSpec.scala:10, supportedBackends/tes/src/test/scala/cromwell/backend/impl/tes/TesRuntimeAttributesSpec.scala:257, wdl/transforms/biscayne/src/test/scala/wdl/transforms/biscayne/linking/expression/values/BiscayneValueEvaluatorSpec.scala:72, …
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)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- 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 8 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:4
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
P6 · Release Hygiene
P8 · Schema migrations
PF3 · Async & latency hygiene
- `resolveWithRetries` 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. — cromwell-drs-localizer/src/main/scala/drs/localizer/DrsLocalizerMain.scala:213
- `downloadWithRetries` 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. — cromwell-drs-localizer/src/main/scala/drs/localizer/downloaders/GcsUriDownloader.scala:55
- `runActionInternal` is async and calls Await.result — 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. — database/sql/src/main/scala/cromwell/database/slick/SlickDatabase.scala:212
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
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×18) — engine/src/main/scala/cromwell/engine/io/nio/NioHashing.scala:66, engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheHashingJobActor.scala:141, engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheHashingJobActor.scala:293, …
- `https://www.gstatic.com/charts/loader.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 2 such include(s) across the repository's markup. — REDACTED:4
- 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: CromIAM/src/main/scala/cromiam/server/CromIamServer.scala:18 — `HttpApp`.
- 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: CromIAM/src/main/scala/cromiam/server/CromIamServer.scala:18 — `HttpApp`.
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 18 sites, not one: `engine/src/main/scala/cromwell/engine/io/nio/NioHashing.scala:66` (DigestUtils.md5Hex), `engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheHashingJobActor.scala:141` (MessageDigest.getInstance("MD5")), `engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheHashingJobActor.scala:293` (MessageDigest.getInstance("MD5")), `engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheHashingJobActor.scala:360` (MessageDigest.getInstance("MD5")), `filesystems/gcs/src/main/scala/cromwell/filesystems/gcs/GcsPathBuilder.scala:314` (DigestUtils.md5Hex), `languageFactories/language-factory-core/src/main/scala/cromwell/languages/util/ImportResolver.scala:180` (MessageDigest.getInstance("MD5")), `supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:787` (MessageDigest.getInstance("MD5")), `supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJobDefinition.scala:374` (MessageDigest.getInstance("SHA-1")), and 10 further site(s). Each is a separate decision — fixing only the line this row cites leaves the others in place.
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
- 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.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `WomValueJsonFormat.read` is public and takes `value: JsValue` from its caller, and it calls itself at line 32 with a piece of `value` (and at line 35), not as a tail call the compiler turns into a loop — and nowhere in `WomValueJsonFormat.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 `WomValueJsonFormat.read` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — core/src/main/scala/cromwell/util/JsonFormatting/WomValueJsonFormatter.scala:32
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
- `Files.walk(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.iterator` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.walk(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. — cloud-nio/cloud-nio-util/src/main/scala/cloud/nio/util/CloudNioFiles.scala:16
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
X4 · Structured logging
- `warn` at line 38 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/sfs/src/main/scala/cromwell/backend/impl/sfs/config/ConfigHashingStrategy.scala:38
- `warn` at line 118 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/util/GcpBatchReferenceFilesMappingOperations.scala:118
- `info` at line 288 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:288
- `debug` at line 860 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:860
- `debug` at line 882 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:882
- `info` at line 909 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:909
- `debug` at line 929 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:929
- `warn` at line 945 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:945
- `debug` at line 962 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:962
- `debug` at line 1013 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:1013
- `warn` at line 1042 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:1042
- `debug` at line 1049 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:1049
- `info` at line 1054 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:1054
- `info` at line 1150 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:1150
- `warn` at line 1229 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:1229
- `warn` at line 127 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAttributes.scala:127
- `info` at line 122 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchInitializationActor.scala:122
- `info` at line 132 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchInitializationActor.scala:132
- `debug` at line 190 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:190
- `debug` at line 194 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:194
- `debug` at line 195 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:195
- `debug` at line 515 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:515
- `debug` at line 559 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:559
- `debug` at line 677 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:677
- `info` at line 678 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:678
- `debug` at line 792 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:792
- `debug` at line 809 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:809
- `debug` at line 820 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:820
- `debug` at line 866 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:866
- `debug` at line 895 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:895
- `warn` at line 83 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — services/src/main/scala/cromwell/services/metadata/MetadataQuery.scala:83
- `error` at line 469 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — services/src/main/scala/cromwell/services/metadata/impl/builder/MetadataBuilderActor.scala:469
- `error` at line 472 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — services/src/main/scala/cromwell/services/metadata/impl/builder/MetadataBuilderActor.scala:472
- `error` at line 476 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — services/src/main/scala/cromwell/services/metadata/impl/builder/MetadataBuilderActor.scala:476
- `debug` at line 18 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — services/src/main/scala/cromwell/services/instrumentation/impl/statsd/CromwellStatsD.scala:18
- `info` at line 106 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — server/src/main/scala/cromwell/CromwellEntryPoint.scala:106
- `error` at line 111 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — server/src/main/scala/cromwell/CromwellEntryPoint.scala:111
- `error` at line 116 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — server/src/main/scala/cromwell/CromwellEntryPoint.scala:116
- `info` at line 199 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — filesystems/gcs/src/main/scala/cromwell/filesystems/gcs/batch/GcsBatchIoCommand.scala:199
- `info` at line 103 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — engine/src/main/scala/cromwell/server/CromwellShutdown.scala:103
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- No build over this repository's 1150 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 | 57% | Adequate — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 94% | Exemplary | Strongest area. |
| Maturity | 69% | Adequate | Acceptable, with room to improve. |
| Readiness | 66% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 36% | Weak — gated by D29, D36, S1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Adequate | Acceptable, with room to improve. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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 — 54 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (8 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (8 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (8 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (8 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (8 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (8 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 — compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c ./docker-setup.sh" did not complete successfully: exit code: 4; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — 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 — ~72285 lines of test source are present (.scala, .py) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- 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.
- 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 .java, .py, .scala source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- 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.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 856 value object(s); 19 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
- M4 Documentation accuracy — Not applicable: the 94 current-state document(s) make no claim of a kind M4 checks. 29 claim(s) of kinds M4 does not check were not checked (path 1, command argument 3, environment variable 16, setting 7, route 2); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — 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 REDACTED, 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.
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Scala, Java and Python were 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; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 63 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: MetadataSqlDatabase.scala ↔ MetadataDatabaseAccess.scala database/sql/src/main/scala/cromwell/database/sql/MetadataSqlDatabase.scala:1
- Boundary-crossing change coupling: CallCachingSlickDatabase.scala ↔ CallCache.scala database/sql/src/main/scala/cromwell/database/slick/CallCachingSlickDatabase.scala:1
- Boundary-crossing change coupling: MetadataSqlDatabase.scala ↔ ReadDatabaseMetadataWorkerActor.scala database/sql/src/main/scala/cromwell/database/sql/MetadataSqlDatabase.scala:1
- Boundary-crossing change coupling: MetadataRouteSupport.scala ↔ ReadDatabaseMetadataWorkerActor.scala engine/src/main/scala/cromwell/webservice/routes/MetadataRouteSupport.scala:1
- REDACTED
- REDACTED
Serious — 340 finding(s)
- TodoComment wom/src/main/scala/wom/values/WomObject.scala:73
- TodoComment wom/src/main/scala/wom/graph/GraphNode.scala:117
- TodoComment wom/src/main/scala/wom/graph/GraphNodePort.scala:18
- TodoComment wom/src/main/scala/wom/graph/GraphNodePort.scala:19
- TodoComment wom/src/main/scala/wom/graph/expression/ExpressionNode.scala:30
- TodoComment wom/src/main/scala/wom/callable/CommandTaskDefinition.scala:86
- TodoComment wdl/transforms/new-base/src/main/scala/wdl/transforms/base/linking/graph/package.scala:105
- TodoComment wdl/transforms/draft3/src/main/scala/wdl/draft3/transforms/linking/expression/consumed/package.scala:98
- TodoComment wdl/transforms/draft3/src/main/scala/wdl/draft3/transforms/parsing/WdlDraft3SyntaxErrorFormatter.scala:58
- TodoComment wdl/transforms/cascades/src/main/scala/wdl/transforms/cascades/parsing/WdlCascadesSyntaxErrorFormatter.scala:59
- TodoComment wdl/transforms/biscayne/src/main/scala/wdl/transforms/biscayne/parsing/WdlBiscayneSyntaxErrorFormatter.scala:59
- TodoComment wdl/model/draft2/src/main/scala/wdl/draft2/model/WdlSyntaxErrorFormatter.scala:67
- TodoComment wdl/transforms/cascades/src/test/scala/wdl/transforms/cascades/linking/expression/values/CascadesValueEvaluatorSpec.scala:70
- TodoComment wdl/transforms/biscayne/src/test/scala/wdl/transforms/biscayne/linking/expression/values/BiscayneValueEvaluatorSpec.scala:70
- TodoComment wdl/model/draft2/src/test/scala/wdl/expression/WdlStandardLibraryFunctionsSpec.scala:54
- TodoComment wdl/model/draft2/src/main/scala/wdl/draft2/model/AstTools.scala:248
- TodoComment wdl/model/draft2/src/main/scala/wdl/draft2/model/AstTools.scala:295
- TodoComment wdl/model/draft2/src/main/scala/wdl/draft2/model/WdlTask.scala:154
- TodoComment wdl/model/draft2/src/main/scala/wdl/draft2/model/types/WdlFlavoredWomType.scala:23
- TodoComment supportedBackends/tes/src/test/scala/cromwell/backend/impl/tes/TesInitializationActorSpec.scala:82
- TodoComment supportedBackends/tes/src/test/scala/cromwell/backend/impl/tes/TesInitializationActorSpec.scala:175
- TodoComment supportedBackends/google/batch/src/test/scala/cromwell/backend/google/batch/actors/GcpBatchInitializationActorSpec.scala:92
- TodoComment supportedBackends/tes/src/main/scala/cromwell/backend/impl/tes/TesInitializationActor.scala:74
- TodoComment supportedBackends/tes/src/main/scala/cromwell/backend/impl/tes/TesJobPaths.scala:54
- TodoComment supportedBackends/tes/src/main/scala/cromwell/backend/impl/tes/TesTask.scala:50
- Weak hash algorithm engine/src/main/scala/cromwell/engine/io/nio/NioHashing.scala:66
- Weak hash algorithm engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheHashingJobActor.scala:141
- Weak hash algorithm engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheHashingJobActor.scala:293
- Weak hash algorithm engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheHashingJobActor.scala:360
- Weak hash algorithm filesystems/gcs/src/main/scala/cromwell/filesystems/gcs/GcsPathBuilder.scala:314
- Weak hash algorithm languageFactories/language-factory-core/src/main/scala/cromwell/languages/util/ImportResolver.scala:180
- Weak hash algorithm supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:787
- Weak hash algorithm supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJobDefinition.scala:374
- Weak hash algorithm supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/actors/GcpBatchAsyncBackendJobExecutionActor.scala:345
- Weak hash algorithm supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/actors/GcpBatchAsyncBackendJobExecutionActor.scala:363
- Weak hash algorithm supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/actors/GcpBatchAsyncBackendJobExecutionActor.scala:384
- Weak hash algorithm supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/actors/GcpBatchAsyncBackendJobExecutionActor.scala:426
- Weak hash algorithm supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/actors/GcpBatchAsyncBackendJobExecutionActor.scala:902
- Weak hash algorithm supportedBackends/sfs/src/main/scala/cromwell/backend/impl/sfs/config/ConfigBackendFileHashing.scala:18
- Weak hash algorithm supportedBackends/sfs/src/main/scala/cromwell/backend/impl/sfs/config/ConfigHashingStrategy.scala:85
- Weak hash algorithm supportedBackends/sfs/src/main/scala/cromwell/backend/impl/sfs/config/ConfigHashingStrategy.scala:93
- Weak hash algorithm supportedBackends/sfs/src/main/scala/cromwell/backend/impl/sfs/config/ConfigHashingStrategy.scala:100
- Weak hash algorithm wom/src/main/scala/wom/package.scala:37
- FixmeComment wom/src/main/scala/wom/callable/WorkflowDefinition.scala:17
- FixmeComment wdl/model/draft2/src/test/scala/wdl/SampleWdl.scala:8
- FixmeComment engine/src/main/scala/cromwell/webservice/routes/wes/WesRouteSupport.scala:241
- FixmeComment engine/src/main/scala/cromwell/webservice/routes/wes/WesRouteSupport.scala:242
- FixmeComment backend/src/main/scala/cromwell/backend/BackendWorkflowInitializationActor.scala:139
- FixmeComment CromIAM/src/main/scala/cromiam/webservice/CromIamApiService.scala:61
- FixmeComment CromIAM/src/main/scala/cromiam/webservice/SubmissionSupport.scala:31
- FixmeComment CromIAM/src/main/scala/cromiam/webservice/SubmissionSupport.scala:115
- FixmeComment CromIAM/src/main/scala/cromiam/webservice/SubmissionSupport.scala:183
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (6 corresponding lines) wom/src/main/scala/wom/values/WomFloat.scala:19
- Edited copy of a member (6 corresponding lines) wom/src/main/scala/wom/values/WomFloat.scala:26
- Edited copy of a member (6 corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/wdlom2wom/expression/renaming/EngineFunctionEvaluators.scala:57
- Edited copy of a member (6 corresponding lines) wdl/model/draft2/src/main/scala/wdl/draft2/model/TaskOutput.scala:10
- Edited copy of a member (6 corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/ast2wdlom/AstToMetaSectionElement.scala:10
- Edited copy of a member (6 corresponding lines) wom/src/main/scala/wom/types/WomFloatType.scala:24
- Edited copy of a member (6 corresponding lines) engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/keys/ConditionalCollectorKey.scala:23
- Edited copy of a member (6 corresponding lines) scripts/metadata_comparison/metadata_comparison/lib/operations_digesters.py:219
- FileTooLong: actors/GcpBatchAsyncBackendJobExecutionActor.scala supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/actors/GcpBatchAsyncBackendJobExecutionActor.scala
- FileTooLong: job/EngineJobExecutionActor.scala engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/job/EngineJobExecutionActor.scala
- FileTooLong: standard/StandardAsyncExecutionActor.scala backend/src/main/scala/cromwell/backend/standard/StandardAsyncExecutionActor.scala
- FileTooLong: execution/WorkflowExecutionActor.scala engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/WorkflowExecutionActor.scala
- FileTooLong: values/EngineFunctionEvaluators.scala wdl/transforms/new-base/src/main/scala/wdl/transforms/base/linking/expression/values/EngineFunctionEvaluators.scala
- FileTooLong: workflow/WorkflowActor.scala engine/src/main/scala/cromwell/engine/workflow/WorkflowActor.scala
- FileTooLong: model/WdlNamespace.scala wdl/model/draft2/src/main/scala/wdl/draft2/model/WdlNamespace.scala
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TooManyMethods: BetterFileMethods core/src/main/scala/cromwell/core/path/BetterFileMethods.scala:25
- TooManyMethods: StandardAsyncExecutionActor backend/src/main/scala/cromwell/backend/standard/StandardAsyncExecutionActor.scala:86
- TooManyMethods: EngineJobExecutionActor engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/job/EngineJobExecutionActor.scala:64
- TooManyMethods: WdlStandardLibraryFunctions wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/WdlStandardLibraryFunctions.scala:24
- TooManyMethods: WdlStandardLibraryFunctionsType wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/WdlStandardLibraryFunctions.scala:526
- TooManyMethods: GcpBatchAsyncBackendJobExecutionActor supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/actors/GcpBatchAsyncBackendJobExecutionActor.scala:153
- Edited copy of a member (10 corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/linking/expression/values/EngineFunctionEvaluators.scala:840
- Edited copy of a member (10 corresponding lines) backend/src/main/scala/cromwell/backend/io/GlobFunctions.scala:20
- Edited copy of a member (10 corresponding lines) womtool/src/main/scala/womtool/WomtoolMain.scala:77
- Edited copy of a member (10 corresponding lines) backend/src/main/scala/cromwell/backend/validation/MaxRetriesValidation.scala:30
- Edited copy of a member (10 corresponding lines) wom/src/main/scala/wom/graph/GraphOutputNode.scala:33
- Edited copy of a member (10 corresponding lines) CromIAM/src/main/scala/cromiam/instrumentation/CromIamInstrumentation.scala:30
- Low cohesion: TesAsyncBackendJobExecutionActor (LCOM4 7) supportedBackends/tes/src/main/scala/cromwell/backend/impl/tes/TesAsyncBackendJobExecutionActor.scala:222
- Low cohesion: WorkflowDockerLookupActor (LCOM4 6) engine/src/main/scala/cromwell/engine/workflow/WorkflowDockerLookupActor.scala:46
- Low cohesion: SubWorkflowExecutionActor (LCOM4 6) engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/SubWorkflowExecutionActor.scala:32
- Low cohesion: CloudNioFileSystemProvider (LCOM4 4) cloud-nio/cloud-nio-spi/src/main/scala/cloud/nio/spi/CloudNioFileSystemProvider.scala:18
- Low cohesion: CallCacheHashingJobActor (LCOM4 4) engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheHashingJobActor.scala:34
- Low cohesion: EngineJobExecutionActor (LCOM4 4) engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/job/EngineJobExecutionActor.scala:64
- Edited copy of a member (9 corresponding lines) wom/src/main/scala/wom/values/WomInteger.scala:33
- Edited copy of a member (9 corresponding lines) engine/src/main/scala/cromwell/webservice/routes/MetadataRouteSupport.scala:252
- Edited copy of a member (9 corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/linking/expression/types/BinaryOperatorEvaluators.scala:30
- Edited copy of a member (9 corresponding lines) services/src/main/scala/cromwell/services/metadata/MetadataService.scala:61
- Edited copy of a member (9 corresponding lines) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/util/GpuValidation.scala:29
- Edited copy of a member (4 corresponding lines) backend/src/main/scala/cromwell/backend/validation/InformationValidation.scala:49
- Edited copy of a member (4 corresponding lines) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/models/GcpBatchRuntimeAttributes.scala:300
- Edited copy of a member (4 corresponding lines) cloud-nio/cloud-nio-spi/src/main/scala/cloud/nio/spi/CloudNioFileSystem.scala:60
- Edited copy of a member (4 corresponding lines) cloud-nio/cloud-nio-util/src/main/scala/cloud/nio/util/VersionUtil.scala:39
- Edited copy of a member (4 corresponding lines) common/src/main/scala/common/validation/ErrorOr.scala:19
- Duplicated block (7 lines × 2) cloudSupport/src/main/scala/cromwell/cloudsupport/gcp/GoogleConfiguration.scala:107
- Duplicated block (7 lines × 2) cromwellApiClient/src/main/scala/cromwell/api/CromwellClient.scala:254
- Duplicated block (7 lines × 2) engine/src/main/scala/cromwell/webservice/routes/CromwellApiService.scala:261
- Duplicated block (7 lines × 2) wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/FileEvaluator.scala:84
- Duplicated block (7 lines × 2) wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/TypeEvaluator.scala:138
- Off the main sequence: cromwellApiClient
- Off the main sequence: httpFileSystem
- Off the main sequence: databaseSql
- Off the main sequence: sraFileSystem
- Off the main sequence: cloudSupport
- Duplicated block (11 lines × 2) backend/src/main/scala/cromwell/backend/standard/StandardAsyncExecutionActor.scala:1073
- Duplicated block (11 lines × 2) backend/src/main/scala/cromwell/backend/validation/RuntimeAttributesValidation.scala:92
- Duplicated block (11 lines × 2) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/wdlom2wom/TaskDefinitionElementToWomTaskDefinition.scala:135
- Duplicated block (11 lines × 2) wdl/transforms/biscayne/src/main/scala/wdl/transforms/biscayne/ast2wdlom/BiscayneAstNodeToKvPair.scala:11
- Duplicated block (8 lines × 2) engine/src/main/scala/cromwell/webservice/routes/CromwellApiService.scala:225
- Duplicated block (8 lines × 2) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/monitoring/BatchInstrumentation.scala:41
- Duplicated block (8 lines × 2) wdl/transforms/biscayne/src/main/scala/wdl/transforms/biscayne/linking/expression/types/BiscayneTypeEvaluators.scala:73
- Duplicated block (8 lines × 2) wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/FileEvaluator.scala:163
- Duplicated block (6 lines × 2) wdl/model/draft2/src/main/scala/wdl/draft2/model/WdlExpression.scala:178
- Duplicated block (6 lines × 2) wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/TypeEvaluator.scala:71
- Duplicated block (6 lines × 2) cloudSupport/src/main/scala/cromwell/cloudsupport/gcp/GoogleConfiguration.scala:22
- Duplicated block (6 lines × 2) wom/src/main/scala/wom/types/WomFloatType.scala:31
- Duplicated block (5 lines × 2) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/actors/GcpBatchAsyncBackendJobExecutionActor.scala:1145
- Duplicated block (5 lines × 2) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/models/GcpBatchRuntimeAttributes.scala:271
- Duplicated block (5 lines × 2) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/models/GcpBatchRuntimeAttributes.scala:286
- Duplicated block (5 lines × 2) wom/src/main/scala/wom/types/WomFloatType.scala:38
- Change coupling: REDACTED ↔ Merging.scala REDACTED:1
- Change coupling: GcpBatchAsyncBackendJobExecutionActor.scala ↔ BatchRequestExecutor.scala supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/actors/GcpBatchAsyncBackendJobExecutionActor.scala:1
- Change coupling: JobPaths.scala ↔ StandardAsyncExecutionActor.scala backend/src/main/scala/cromwell/backend/io/JobPaths.scala:1
- Edited copy of a member (19 corresponding lines) wdl/model/draft2/src/main/scala/wdl/draft2/model/WdlExpression.scala:260
- Edited copy of a member (19 corresponding lines) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/api/BatchApiRequestManager.scala:139
- Edited copy of a member (19 corresponding lines) scripts/metadata_comparison/metadata_comparison/lib/operations_digesters.py:192
- Edited copy of a member (25 corresponding lines) centaur/src/main/scala/centaur/api/Retry.scala:21
- Edited copy of a member (25 corresponding lines) database/migration/src/main/scala/cromwell/database/migration/custom/PreemptedIsABackendStatus.scala:40
- Edited copy of a member (25 corresponding lines) wdl/model/draft2/src/main/scala/wdl/draft2/model/examples/ex2.scala:8
- Edited copy of a member (8 corresponding lines) wom/src/main/scala/wom/values/WomFloat.scala:33
- Edited copy of a member (8 corresponding lines) core/src/main/scala/cromwell/core/WorkflowOptions.scala:143
- Edited copy of a member (8 corresponding lines) womtool/src/main/scala/womtool/inputs/Inputs.scala:16
- Edited copy of a member (5 corresponding lines) wom/src/main/scala/wom/types/WomType.scala:82
- Edited copy of a member (5 corresponding lines) cloud-nio/cloud-nio-impl-ftp/src/main/scala/cloud/nio/impl/ftp/LeasedInputStream.scala:18
- Edited copy of a member (5 corresponding lines) wom/src/main/scala/wom/types/WomBooleanType.scala:21
- Hollow method — returns a constant without doing the work centaur/src/main/scala/centaur/api/Retry.scala:47
- Hollow method — returns a constant without doing the work common/src/main/scala/common/util/IORetry.scala:67
- Hollow method — returns a constant without doing the work core/src/main/scala/cromwell/core/path/CustomRetryParams.scala:19
- Sync-over-async blocking cromwell-drs-localizer/src/main/scala/drs/localizer/DrsLocalizerMain.scala:213
- Sync-over-async blocking cromwell-drs-localizer/src/main/scala/drs/localizer/downloaders/GcsUriDownloader.scala:55
- Sync-over-async blocking database/sql/src/main/scala/cromwell/database/slick/SlickDatabase.scala:212
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (22 corresponding lines) backend/src/main/scala/cromwell/backend/standard/StandardAsyncExecutionActor.scala:1317
- Edited copy of a member (22 corresponding lines) services/src/main/scala/cromwell/services/metadata/impl/archiver/ArchiveMetadataSchedulerActor.scala:125
- Edited copy of a member (15 corresponding lines) wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/WdlStandardLibraryFunctions.scala:344
- Edited copy of a member (15 corresponding lines) languageFactories/wdl-draft2/src/main/scala/languages/wdl/draft2/WdlDraft2LanguageFactory.scala:115
- Edited copy of a member (13 corresponding lines) database/sql/src/main/scala/cromwell/database/slick/CallCachingSlickDatabase.scala:94
- Edited copy of a member (13 corresponding lines) services/src/main/scala/cromwell/services/cost/GcpCostCatalogService.scala:88
- Edited copies of one member (3 members, 7+ corresponding lines) wdl/transforms/biscayne/src/main/scala/wdl/transforms/biscayne/parsing/BiscayneParser.scala:15
- Edited copies of one member (3 members, 7+ corresponding lines) wom/src/main/scala/wom/values/WomFloat.scala:11
- Edited copy of a member (14 corresponding lines) cloud-nio/cloud-nio-spi/src/main/scala/cloud/nio/spi/UnixPath.scala:260
- Edited copy of a member (14 corresponding lines) supportedBackends/tes/src/main/scala/cromwell/backend/impl/tes/TesInitializationActor.scala:66
- Edited copies of one member (4 members, 5+ corresponding lines) wom/src/main/scala/wom/values/WomBoolean.scala:26
- Edited copies of one member (4 members, 5+ corresponding lines) wom/src/main/scala/wom/values/WomBoolean.scala:32
- Duplicated block (16 lines × 2) cloud-nio/cloud-nio-util/src/main/scala/cloud/nio/util/VersionUtil.scala:64
- Duplicated block (16 lines × 2) wdl/model/draft2/src/main/scala/wdl/draft2/model/WdlExpression.scala:263
- Duplicated block (13–14 lines × 2) backend/src/main/scala/cromwell/backend/standard/StandardAsyncExecutionActor.scala:1497
- Duplicated block (13–14 lines × 2) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/wdlom2wom/graph/IfElementToGraphNode.scala:75
- Duplicated block (12 lines × 2) wdl/transforms/draft2/src/main/scala/wdl/transforms/draft2/wdlom2wom/WdlDraft2WomCallNodeMaker.scala:108
- Duplicated block (12 lines × 2) wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/TypeEvaluator.scala:44
- Duplicated block (10 lines × 2) engine/src/main/scala/cromwell/webservice/routes/CromwellApiService.scala:250
- Duplicated block (10 lines × 2) wdl/transforms/biscayne/src/main/scala/wdl/transforms/biscayne/linking/expression/values/BiscayneValueEvaluators.scala:151
- Duplicated block (9 lines × 2) engine/src/main/scala/cromwell/webservice/routes/CromwellApiService.scala:240
- Duplicated block (9 lines × 2) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/callcaching/BatchBackendCacheHitCopyingActor.scala:55
- ValueEvaluator.evaluate (cyclomatic 85) wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/ValueEvaluator.scala:51
- TypeEvaluator.evaluate (cyclomatic 84) wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/TypeEvaluator.scala:20
- WdlNamespace.apply (cyclomatic 54) wdl/model/draft2/src/main/scala/wdl/draft2/model/WdlNamespace.scala:198
- CallElementToGraphNode.convert (cyclomatic 36) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/wdlom2wom/graph/CallElementToGraphNode.scala:31
- FileEvaluator.evaluateRecursive (cyclomatic 35) wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/FileEvaluator.scala:71
- REDACTED.parseMetadata (cyclomatic 28) REDACTED:25
- EnhancedAstNode.womValue (cyclomatic 27) wdl/model/draft2/src/main/scala/wdl/draft2/model/AstTools.scala:179
- AstNodeToExpressionElement.convert (cyclomatic 27) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/ast2wdlom/AstNodeToExpressionElement.scala:26
- WomArrayType.coercion (cyclomatic 26) wom/src/main/scala/wom/types/WomArrayType.scala:24
- StandardAsyncExecutionActor.handleExecutionResult (cyclomatic 25) backend/src/main/scala/cromwell/backend/standard/StandardAsyncExecutionActor.scala:1388
- PartialWorkflowSources.fromSubmitRoute (cyclomatic 24) engine/src/main/scala/cromwell/webservice/PartialWorkflowSources.scala:80
- Scope.lookupFunction (cyclomatic 21) wdl/model/draft2/src/main/scala/wdl/draft2/model/Scope.scala:234
- WdlDraft2WomCallNodeMaker.toWomCallNode (cyclomatic 21) wdl/transforms/draft2/src/main/scala/wdl/transforms/draft2/wdlom2wom/WdlDraft2WomCallNodeMaker.scala:33
- GcpBatchConfigurationAttributes.apply (cyclomatic 20) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/models/GcpBatchConfigurationAttributes.scala:138
- EnhancedAstNode.womType (cyclomatic 19) wdl/model/draft2/src/main/scala/wdl/draft2/model/AstTools.scala:125
- WdlCall.lookupFunction (cyclomatic 18) wdl/model/draft2/src/main/scala/wdl/draft2/model/WdlCall.scala:143
- WdlNamespace.validateCallInputSection (cyclomatic 18) wdl/model/draft2/src/main/scala/wdl/draft2/model/WdlNamespace.scala:600
- WorkflowExecutionActor.startRunnableNodes (cyclomatic 17) engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/WorkflowExecutionActor.scala:620
- CromwellApiService.submitRequest (cyclomatic 17) engine/src/main/scala/cromwell/webservice/routes/CromwellApiService.scala:217
- WesRouteSupport.wesSubmitRequest (cyclomatic 17) engine/src/main/scala/cromwell/webservice/routes/wes/WesRouteSupport.scala:139
- OutputEvaluator.evaluateOutputs (cyclomatic 16) backend/src/main/scala/cromwell/backend/OutputEvaluator.scala:27
- WomValueBuilder.toWomValue (cyclomatic 16) core/src/main/scala/cromwell/core/simpleton/WomValueBuilder.scala:90
- ParameterCommandPart.instantiate (cyclomatic 16) wdl/model/draft2/src/main/scala/wdl/draft2/model/command/ParameterCommandPart.scala:43
- ValueEvaluator.evaluate (cognitive 157) wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/ValueEvaluator.scala:51
- TypeEvaluator.evaluate (cognitive 147) wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/TypeEvaluator.scala:20
- FileEvaluator.evaluateRecursive (cognitive 79) wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/FileEvaluator.scala:71
- REDACTED.parseMetadata (cognitive 69) REDACTED:25
- WdlNamespace.apply (cognitive 61) wdl/model/draft2/src/main/scala/wdl/draft2/model/WdlNamespace.scala:198
- MaterializeWorkflowDescriptorActor.buildWorkflowDescriptor (cognitive 53) engine/src/main/scala/cromwell/engine/workflow/lifecycle/materialization/MaterializeWorkflowDescriptorActor.scala:304
- CallElementToGraphNode.convert (cognitive 52) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/wdlom2wom/graph/CallElementToGraphNode.scala:31
- GcpBatchAsyncBackendJobExecutionActor.executeAsync (cognitive 46) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/actors/GcpBatchAsyncBackendJobExecutionActor.scala:928
- CallCacheDiffActor.extractCallMetadata (cognitive 45) engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheDiffActor.scala:170
- ArchiveMetadataConfig.parseConfig (cognitive 45) services/src/main/scala/cromwell/services/metadata/impl/archiver/ArchiveMetadataConfig.scala:28
- WdlCall.lookupFunction (cognitive 34) wdl/model/draft2/src/main/scala/wdl/draft2/model/WdlCall.scala:143
- StandardAsyncExecutionActor.handleExecutionResult (cognitive 33) backend/src/main/scala/cromwell/backend/standard/StandardAsyncExecutionActor.scala:1388
- MetadataSlickDatabase.summarizeDecreasing (cognitive 26) database/sql/src/main/scala/cromwell/database/slick/MetadataSlickDatabase.scala:318
- MetadataBuilderActor.computeCost (cognitive 24) services/src/main/scala/cromwell/services/metadata/impl/builder/MetadataBuilderActor.scala:355
- WdlDraft2LanguageFactory.validateNamespace (cognitive 23) languageFactories/wdl-draft2/src/main/scala/languages/wdl/draft2/WdlDraft2LanguageFactory.scala:45
- CostCatalogKey.apply (cognitive 21) services/src/main/scala/cromwell/services/cost/GcpCostCatalogService.scala:43
- GcpCostCatalogService.calculateVmCostPerHour (cognitive 21) services/src/main/scala/cromwell/services/cost/GcpCostCatalogService.scala:215
- MetadataBuilderActor.buildCostAndStop (cognitive 21) services/src/main/scala/cromwell/services/metadata/impl/builder/MetadataBuilderActor.scala:624
- JobStoreWriterActor.process (cognitive 20) engine/src/main/scala/cromwell/jobstore/JobStoreWriterActor.scala:27
- AstNodeToExpressionElement.convert (cognitive 19) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/ast2wdlom/AstNodeToExpressionElement.scala:26
- EnhancedAstNode.womValue (cognitive 18) wdl/model/draft2/src/main/scala/wdl/draft2/model/AstTools.scala:179
- WdlDraft2WomCallNodeMaker.toWomCallNode (cognitive 18) wdl/transforms/draft2/src/main/scala/wdl/transforms/draft2/wdlom2wom/WdlDraft2WomCallNodeMaker.scala:33
- ReadMetadataRegulatorActor.receive (cognitive 17) services/src/main/scala/cromwell/services/metadata/impl/ReadMetadataRegulatorActor.scala:38
- ArchiveMetadataSchedulerActor.streamMetadataToGcs (cognitive 17) services/src/main/scala/cromwell/services/metadata/impl/archiver/ArchiveMetadataSchedulerActor.scala:257
- GcpBatchAsyncBackendJobExecutionActor.createBatchParameters (cognitive 17) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/actors/GcpBatchAsyncBackendJobExecutionActor.scala:600
- Scope.lookupFunction (cognitive 17) wdl/model/draft2/src/main/scala/wdl/draft2/model/Scope.scala:234
- UnixPath.normalize (cognitive 16) cloud-nio/cloud-nio-spi/src/main/scala/cloud/nio/spi/UnixPath.scala:201
- DrsPathBuilder.maybeCreateOtherPath (cognitive 16) filesystems/drs/src/main/scala/cromwell/filesystems/drs/DrsPathBuilder.scala:36
- ArchiveMetadataSchedulerActor.receive (cognitive 16) services/src/main/scala/cromwell/services/metadata/impl/archiver/ArchiveMetadataSchedulerActor.scala:86
- GcpLabel.safeGoogleName (cognitive 16) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/models/GcpLabel.scala:28
- WomArrayType.coercion (cognitive 16) wom/src/main/scala/wom/types/WomArrayType.scala:24
- REDACTED
- REDACTED
- Near-duplicate member pair (34 shared lines) engine/src/main/scala/cromwell/webservice/routes/CromwellApiService.scala:217
- Members sharing a duplicated core (4 members, 50+ identical tokens) wom/src/main/scala/wom/expression/WomExpression.scala:38
- Edited copy of a member (86 corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/wdlom2wom/graph/IfElementToGraphNode.scala:31
- Edited copy of a member (40 corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/wdlom2wom/TaskDefinitionElementToWomTaskDefinition.scala:127
- Edited copy of a member (47 corresponding lines) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/api/request/AbortRequestHandler.scala:29
- Edited copy of a member (21 corresponding lines) cromwellApiClient/src/main/scala/cromwell/api/CromwellClient.scala:236
- Edited copy of a member (27 corresponding lines) services/src/main/scala/cromwell/services/metadata/impl/builder/MetadataBuilderActor.scala:482
- Edited copies of one member (3 members, 20+ corresponding lines) backend/src/main/scala/cromwell/backend/validation/RuntimeAttributesValidation.scala:86
- Edited copy of a member (17 corresponding lines) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/callcaching/BatchBackendCacheHitCopyingActor.scala:51
- Edited copy of a member (24 corresponding lines) engine/src/main/scala/cromwell/engine/workflow/WorkflowActor.scala:230
- Edited copies of one member (3 members, 11+ corresponding lines) services/src/main/scala/cromwell/services/metadata/WorkflowQueryKey.scala:185
- Edited copy of a member (16 corresponding lines) backend/src/main/scala/cromwell/backend/dummy/DummySingletonActor.scala:38
- Edited copies of one member (3 members, 17+ corresponding lines) languageFactories/wdl-biscayne/src/main/scala/languages/wdl/biscayne/WdlBiscayneLanguageFactory.scala:42
- Edited copies of one member (4 members, 9+ corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/wdlom2wom/expression/renaming/BinaryOperatorEvaluators.scala:25
- Edited copies of one member (3 members, 23+ corresponding lines) engine/src/main/scala/cromwell/engine/workflow/WorkflowActor.scala:440
- Edited copies of one member (5 members, 11+ corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/linking/expression/files/BinaryOperatorEvaluators.scala:30
- Edited copies of one member (5 members, 6+ corresponding lines) wom/src/main/scala/wom/values/WomFile.scala:109
- Edited copies of one member (3 members, 4+ corresponding lines) supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/actors/GcpBatchAsyncBackendJobExecutionActor.scala:456
- Edited copy of a member (7 corresponding lines) backend/src/main/scala/cromwell/backend/BackendLifecycleActor.scala:43
- Edited copies of one member (3 members, 5+ corresponding lines) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/linking/expression/consumed/BinaryOperatorEvaluators.scala:24
- Edited copies of one member (3 members, 3+ corresponding lines) wdl/transforms/biscayne/src/main/scala/wdl/transforms/biscayne/ast2wdlom/BiscayneGenericAstNode.scala:10
- Duplicated block (29 lines × 2) wdl/transforms/biscayne/src/main/scala/wdl/transforms/biscayne/wdlom2wom/package.scala:49
- Duplicated block (28 lines × 2) languageFactories/wdl-biscayne/src/main/scala/languages/wdl/biscayne/WdlBiscayneLanguageFactory.scala:69
- Duplicated block (26 lines × 2) cloud-nio/cloud-nio-util/src/main/scala/cloud/nio/util/TryWithResource.scala:10
- Duplicated block (24–25 lines × 2) CromIAM/src/main/scala/cromiam/webservice/SwaggerUiHttpService.scala:45
- Duplicated block (19–22 lines × 4) wom/src/main/scala/wom/expression/WomExpression.scala:39
- Duplicated block (20 lines × 2) services/src/main/scala/cromwell/services/metadata/impl/builder/MetadataBuilderActor.scala:489
- Duplicated block (18 lines × 2) engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/SubWorkflowExecutionActor.scala:428
- Duplicated block (10–17 lines × 2) backend/src/main/scala/cromwell/backend/standard/StandardAsyncExecutionActor.scala:1440
- Duplicated block (15–16 lines × 3) languageFactories/wdl-biscayne/src/main/scala/languages/wdl/biscayne/WdlBiscayneLanguageFactory.scala:44
- Duplicated block (15 lines × 2) backend/src/main/scala/cromwell/backend/validation/RuntimeAttributesValidation.scala:86
- Duplicated block (14 lines × 2) database/sql/src/main/scala/cromwell/database/slick/tables/CallCachingAggregationEntryComponent.scala:88
- Duplicated block (12–13 lines × 2) services/src/main/scala/cromwell/services/metadata/impl/MetadataDatabaseAccess.scala:264
- Duplicated block (23 lines × 2) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/wdlom2wom/graph/IfElementToGraphNode.scala:49
- Duplicated block (10–11 lines × 2) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/linking/expression/files/EngineFunctionEvaluators.scala:204
- Duplicated block (9 lines × 3) backend/src/main/scala/cromwell/backend/validation/RuntimeAttributesValidation.scala:92
- Duplicated block (6–7 lines × 2) wdl/transforms/new-base/src/main/scala/wdl/transforms/base/wdlom2wom/expression/renaming/EngineFunctionEvaluators.scala:80
- Duplicated block (58 lines × 3) wdl/transforms/biscayne/src/main/scala/wdl/transforms/biscayne/parsing/WdlBiscayneSyntaxErrorFormatter.scala:10
- Duplicated block (5 lines × 3) languageFactories/wdl-biscayne/src/main/scala/languages/wdl/biscayne/WdlBiscayneLanguageFactory.scala:102
- Unstable project engine
- Unstable project googlePipelinesCommon
- Unfinished stub — body is a "not implemented" error engine/src/main/scala/cromwell/engine/EngineIoFunctions.scala:16
- Unfinished stub — throws a "not implemented" exception engine/src/main/scala/cromwell/engine/EngineIoFunctions.scala:16
- Third-party script without Subresource Integrity REDACTED:4
- Recursive walk over a caller-supplied document has no depth cap core/src/main/scala/cromwell/util/JsonFormatting/WomValueJsonFormatter.scala:32
- Disposable created and abandoned in the function that made it cloud-nio/cloud-nio-util/src/main/scala/cloud/nio/util/CloudNioFiles.scala:16
Minor — 333 finding(s)
- Orphaned file backend/src/main/scala/cromwell/backend/validation/RuntimeAttributesValidation.scala:1
- Orphaned file scripts/metadata_comparison/metadata_comparison/comparer.py:1
- Orphaned file supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/api/BatchApiRequestManager.scala:1
- Orphaned file engine/src/main/scala/cromwell/engine/workflow/WorkflowManagerActor.scala:1
- Orphaned file services/src/main/scala/cromwell/services/metadata/impl/archiver/ArchiveMetadataSchedulerActor.scala:1
- Orphaned file engine/src/main/scala/cromwell/engine/workflow/lifecycle/deletion/DeleteWorkflowFilesActor.scala:1
- Orphaned file engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheHashingJobActor.scala:1
- Orphaned file filesystems/s3/src/main/java/org/lerch/s3fs/S3Path.java:1
- Orphaned file engine/src/main/scala/cromwell/webservice/routes/CromwellApiService.scala:1
- Orphaned file supportedBackends/sfs/src/main/scala/cromwell/backend/impl/sfs/config/ConfigAsyncJobExecutionActor.scala:1
- Orphaned file supportedBackends/sfs/src/main/scala/cromwell/backend/sfs/SharedFileSystem.scala:1
- Orphaned file build.sbt:1
- Orphaned file engine/src/main/scala/cromwell/engine/workflow/lifecycle/execution/callcaching/CallCacheDiffActor.scala:1
- Orphaned file filesystems/gcs/src/main/scala/cromwell/filesystems/gcs/GcsPathBuilder.scala:1
- Orphaned file wdl/model/draft3/src/main/scala/wdl/model/draft3/elements/ExpressionElement.scala:1
- Orphaned file database/sql/src/main/scala/cromwell/database/slick/SlickDatabase.scala:1
- Orphaned file languageFactories/language-factory-core/src/main/scala/cromwell/languages/util/ImportResolver.scala:1
- Orphaned file engine/src/main/scala/cromwell/engine/io/gcs/GcsBatchFlow.scala:1
- Orphaned file engine/src/main/scala/cromwell/engine/io/IoActor.scala:1
- Orphaned file wdl/transforms/new-base/src/main/scala/wdl/transforms/base/linking/expression/files/EngineFunctionEvaluators.scala:1
- Orphaned file engine/src/main/scala/cromwell/engine/workflow/SingleWorkflowRunnerActor.scala:1
- Orphaned file supportedBackends/sfs/src/main/scala/cromwell/backend/sfs/SharedFileSystemAsyncJobExecutionActor.scala:1
- Orphaned file database/sql/src/main/scala/cromwell/database/slick/tables/WorkflowStoreEntryComponent.scala:1
- Orphaned file scripts/metadata_comparison/metadata_comparison/lib/operations_digesters.py:1
- Orphaned file dockerHashing/src/main/scala/cromwell/docker/DockerInfoActor.scala:1
- Interpolated log message defeats structured logging supportedBackends/sfs/src/main/scala/cromwell/backend/impl/sfs/config/ConfigHashingStrategy.scala:38
- Interpolated log message defeats structured logging supportedBackends/google/batch/src/main/scala/cromwell/backend/google/batch/util/GcpBatchReferenceFilesMappingOperations.scala:118
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:288
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:860
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:882
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:909
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:929
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:945
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:962
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:1013
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:1042
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:1049
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:1054
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:1150
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:1229
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAttributes.scala:127
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchInitializationActor.scala:122
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchInitializationActor.scala:132
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:190
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:194
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:195
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:515
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:559
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:677
- Interpolated log message defeats structured logging supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:678
- Disabled test server/src/test/scala/cromwell/engine/WorkflowAbortSpec.scala:10
- Disabled test supportedBackends/tes/src/test/scala/cromwell/backend/impl/tes/TesRuntimeAttributesSpec.scala:257
- Disabled test wdl/transforms/biscayne/src/test/scala/wdl/transforms/biscayne/linking/expression/values/BiscayneValueEvaluatorSpec.scala:72
- Disabled test wdl/transforms/cascades/src/test/scala/wdl/transforms/cascades/linking/expression/values/CascadesValueEvaluatorSpec.scala:72
- Disabled test womtool/src/test/scala/womtool/WomtoolValidateSpec.scala:48
- Duplicated predicate wdl/transforms/biscayne/src/main/scala/wdl/transforms/biscayne/ast2wdlom/BiscayneAstNodeToKvPair.scala:19
- Duplicated predicate wdl/model/draft2/src/main/scala/wdl/draft2/model/expression/WdlStandardLibraryFunctions.scala:429
- Duplicated predicate supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchAsyncBackendJobExecutionActor.scala:312
- Duplicated predicate engine/src/main/scala/cromwell/webservice/routes/CromwellApiService.scala:247
- Duplicated predicate wdl/transforms/biscayne/src/main/scala/wdl/transforms/biscayne/wdlom2wom/package.scala:57
- `dockerImageID` spells `ID` where 309 names in the project spell it `Id` dockerHashing/src/main/scala/cromwell/docker/registryv2/DockerRegistryV2Abstract.scala:205
- `dockerImageID` spells `ID` where 309 names in the project spell it `Id` dockerHashing/src/main/scala/cromwell/docker/registryv2/DockerRegistryV2Abstract.scala:211
- `dockerImageID` spells `ID` where 309 names in the project spell it `Id` dockerHashing/src/main/scala/cromwell/docker/registryv2/DockerRegistryV2Abstract.scala:245
- Most significant orphaned file engine/src/main/scala/cromwell/engine/workflow/WorkflowActor.scala:1
- Most significant orphaned file filesystems/s3/src/main/java/org/lerch/s3fs/S3FileSystemProvider.java:1
- Most significant orphaned file core/src/main/scala/cromwell/core/path/BetterFileMethods.scala:1
- REDACTED
- REDACTED
- Fat interface: MetadataSqlDatabase (27 abstract members) database/sql/src/main/scala/cromwell/database/sql/MetadataSqlDatabase.scala:12
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Documentation: no build, run or usage example README.md:1
- No ADRs found project/plugins.sbt:1
- `validateURL` spells `URL` where 25 names in the project spell it `Url` core/src/main/scala/cromwell/core/ConfigUtil.scala:33
- `generateEnvironmentKVPairs` spells `KV` where 21 names in the project spell it `Kv` supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/AwsBatchJob.scala:638
- `buildKVPair` spells `KV` where 21 names in the project spell it `Kv` supportedBackends/aws/src/main/scala/cromwell/backend/impl/aws/package.scala:40
- Projects may be oversized for their cohesion
- REDACTED
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:4
- No app-layer HTTPS enforcement detected
- No security response headers detected
- Scala's null is not held to the type system everywhere
- Silent fallback default in catch wom/src/main/scala/wom/graph/expression/ExpressionNode.scala:76
Minor — 8 finding(s)
- Outdated (compile): com.fasterxml.jackson.core:jackson-annotations
- Outdated (compile): com.fasterxml.jackson.core:jackson-core
- Outdated (compile): com.fasterxml.jackson.core:jackson-databind
- Outdated (compile): org.apache.logging.log4j:log4j-api
- Outdated (compile): org.apache.logging.log4j:log4j-core
- Outdated (test): org.hamcrest:hamcrest-core
- Outdated (test): junit:junit
- Off the main sequence: common
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-82f1aabffc8748eb8127f26148600096/history.json --exit-code 0 --source . | 6 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-82f1aabffc8748eb8127f26148600096/tree.json --exit-code 0 --source . | 0 | 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 wdl/model/draft2/src/main/java --exclude wdl/transforms/biscayne/src/main/java --exclude wdl/transforms/cascades/src/main/java --exclude wdl/transforms/draft3/src/main/java . | 45 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-60da3360aeb440e69b50ecf594e5f879 | 19 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 15 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-60da3360aeb440e69b50ecf594e5f879 | 0 | artifacts/raw/osv-scanner.json |