Executive summary
holunda-io/camunda-bpm-taskpool falls short of our standard for production, held back most by its Domain Modelling lens, the way the code models the business it serves. It scores 59 out of 100 and is rated Adequate, and 30 of its 33 critical findings are security problems.
Domain Modelling, at 52, is the weakest lens and counts most in the score. The best first steps are introducing dedicated id types and protecting the business objects' state, each worth about 5 points. Raising Domain Modelling to 70 would lift the score to about 64.
Fifteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seven secrets can leak from the build pipeline, and three known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, limiting each secret to its own step and updating the vulnerable packages would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the two pipeline steps that run downloads without checking them need each download checked against a known checksum first. The two inner parts of the code that depend on an outer part need turning around so they point inward.
The product code is 19,762 lines, about €51,000 to rebuild.
If Domain Modelling rose from 52 to 70, the lowest score rated Strong, the score would rise from 59 to about 64.
New since the last survey: 7 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 1 finding
- Documentation (README) · README may be stale
Rebuild cost: about €51,000 · Estimate
| Cost to rebuild | €17,000 to €85,000, for 282 to 896 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 19,762 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 camunda.taskpool.api.business | 2 camunda.taskpool.upcast | 3 camunda.variable.serializer | 4 polyflow.view.auth | 5 polyflow.view.jpa.auth | 6 polyflow.view.query | 7 camunda.taskpool.api.task | 8 polyflow.datapool.sender | 9 polyflow.taskpool.collector.task.enricher | 10 polyflow.taskpool.sender.gateway | 11 polyflow.view.filter | 12 polyflow.view.query.process | 13 polyflow.view.query.process.variable | 14 polyflow.view.query.task | 15 camunda.taskpool.api.process.definition | 16 camunda.taskpool.api.process.instance | 17 camunda.taskpool.api.process.variable | 18 camunda.taskpool.model | 19 polyflow.datapool | 20 polyflow.view.query.data | 21 camunda.taskpool.mapper.process | 22 polyflow.taskpool.core.process | 23 polyflow.taskpool.sender.process.definition | 24 polyflow.taskpool.sender.process.instance | 25 polyflow.taskpool.sender.process.variable | 26 polyflow.view | 27 polyflow.taskpool.sender | 28 polyflow.view.jpa.data | 29 polyflow.view.jpa.process | 30 polyflow.view.mongo.data | 31 polyflow.view.simple.service | 32 polyflow.taskpool.sender.task | 33 polyflow.view.jpa.task | 34 polyflow.view.mongo.task | 35 polyflow.taskpool.collector.task | 36 polyflow.view.jpa | 37 polyflow.view.mongo | 38 polyflow.taskpool.collector.task.assigner | 39 polyflow.taskpool.collector | 40 polyflow.taskpool.collector.process.instance |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 camunda.taskpool.api.business | ||||||||||||||||||||||||||||||||||||||||
| 2 camunda.taskpool.upcast | ||||||||||||||||||||||||||||||||||||||||
| 3 camunda.variable.serializer | ||||||||||||||||||||||||||||||||||||||||
| 4 polyflow.view.auth | ||||||||||||||||||||||||||||||||||||||||
| 5 polyflow.view.jpa.auth | ||||||||||||||||||||||||||||||||||||||||
| 6 polyflow.view.query | ||||||||||||||||||||||||||||||||||||||||
| 7 camunda.taskpool.api.task | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 polyflow.datapool.sender | 12 | 4 | ||||||||||||||||||||||||||||||||||||||
| 9 polyflow.taskpool.collector.task.enricher | 3 | |||||||||||||||||||||||||||||||||||||||
| 10 polyflow.taskpool.sender.gateway | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 polyflow.view.filter | 3 | |||||||||||||||||||||||||||||||||||||||
| 12 polyflow.view.query.process | 1 | 4 | 6 | |||||||||||||||||||||||||||||||||||||
| 13 polyflow.view.query.process.variable | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 14 polyflow.view.query.task | 7 | 21 | 18 | |||||||||||||||||||||||||||||||||||||
| 15 camunda.taskpool.api.process.definition | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 camunda.taskpool.api.process.instance | 2 | 13 | ||||||||||||||||||||||||||||||||||||||
| 17 camunda.taskpool.api.process.variable | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 camunda.taskpool.model | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 polyflow.datapool | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 polyflow.view.query.data | 2 | 1 | 9 | 2 | 7 | |||||||||||||||||||||||||||||||||||
| 21 camunda.taskpool.mapper.process | 4 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 polyflow.taskpool.core.process | 9 | 6 | 3 | |||||||||||||||||||||||||||||||||||||
| 23 polyflow.taskpool.sender.process.definition | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 polyflow.taskpool.sender.process.instance | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 polyflow.taskpool.sender.process.variable | 4 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 26 polyflow.view | 6 | 10 | 6 | 4 | 36 | 1 | 10 | |||||||||||||||||||||||||||||||||
| 27 polyflow.taskpool.sender | 13 | 5 | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 28 polyflow.view.jpa.data | 6 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 29 polyflow.view.jpa.process | 1 | 4 | 4 | |||||||||||||||||||||||||||||||||||||
| 30 polyflow.view.mongo.data | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 polyflow.view.simple.service | 8 | 8 | 5 | 3 | 20 | 4 | 5 | 1 | 6 | 11 | ||||||||||||||||||||||||||||||
| 32 polyflow.taskpool.sender.task | 4 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 33 polyflow.view.jpa.task | 1 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 34 polyflow.view.mongo.task | 2 | 4 | 2 | 3 | 4 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 35 polyflow.taskpool.collector.task | 9 | 2 | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 36 polyflow.view.jpa | 4 | 1 | 2 | 7 | 5 | 19 | 4 | 5 | 6 | 5 | 5 | 4 | 3 | |||||||||||||||||||||||||||
| 37 polyflow.view.mongo | 5 | 7 | 10 | 6 | 4 | 5 | 6 | |||||||||||||||||||||||||||||||||
| 38 polyflow.taskpool.collector.task.assigner | 4 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 39 polyflow.taskpool.collector | 8 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 polyflow.taskpool.collector.process.instance | 4 | 4 | 2 | 2 |
7→1 camunda.taskpool.api.task uses camunda.taskpool.api.business✕
- Connections
- 2 pairs of types, where a type in camunda.taskpool.api.task uses a type in camunda.taskpool.api.business.
- The types involved
io.holunda.camunda.taskpool.api.task.TaskEngineEvent→io.holunda.camunda.taskpool.api.business.WithCorrelationsio.holunda.camunda.taskpool.api.task.TaskIdentityWithPayloadAndCorrelations→io.holunda.camunda.taskpool.api.business.WithCorrelations
- Direction
- camunda.taskpool.api.task uses camunda.taskpool.api.business, so a change to camunda.taskpool.api.business can break camunda.taskpool.api.task, while a change to camunda.taskpool.api.task can't break camunda.taskpool.api.business.
- Position
- Below the diagonal: camunda.taskpool.api.task uses a module listed above it, which is the healthy direction.
8→1 polyflow.datapool.sender uses camunda.taskpool.api.business✕
- Connections
- 12 pairs of types, where a type in polyflow.datapool.sender uses a type in camunda.taskpool.api.business.
- The types involved
io.holunda.polyflow.datapool.sender.AbstractDataEntryCommandSender→io.holunda.camunda.taskpool.api.business.AnonymizeDataEntryCommandio.holunda.polyflow.datapool.sender.AbstractDataEntryCommandSender→io.holunda.camunda.taskpool.api.business.AuthorizationChangeio.holunda.polyflow.datapool.sender.AbstractDataEntryCommandSender→io.holunda.camunda.taskpool.api.business.CreateOrUpdateDataEntryCommandio.holunda.polyflow.datapool.sender.AbstractDataEntryCommandSender→io.holunda.camunda.taskpool.api.business.DataEntryStateio.holunda.polyflow.datapool.sender.AbstractDataEntryCommandSender→io.holunda.camunda.taskpool.api.business.DeleteDataEntryCommandio.holunda.polyflow.datapool.sender.AbstractDataEntryCommandSender→io.holunda.camunda.taskpool.api.business.Modificationio.holunda.polyflow.datapool.sender.DataEntryCommandSender→io.holunda.camunda.taskpool.api.business.AnonymizeDataEntryCommandio.holunda.polyflow.datapool.sender.DataEntryCommandSender→io.holunda.camunda.taskpool.api.business.AuthorizationChangeio.holunda.polyflow.datapool.sender.DataEntryCommandSender→io.holunda.camunda.taskpool.api.business.CreateOrUpdateDataEntryCommandio.holunda.polyflow.datapool.sender.DataEntryCommandSender→io.holunda.camunda.taskpool.api.business.DataEntryStateio.holunda.polyflow.datapool.sender.DataEntryCommandSender→io.holunda.camunda.taskpool.api.business.DeleteDataEntryCommandio.holunda.polyflow.datapool.sender.DataEntryCommandSender→io.holunda.camunda.taskpool.api.business.Modification
- Direction
- polyflow.datapool.sender uses camunda.taskpool.api.business, so a change to camunda.taskpool.api.business can break polyflow.datapool.sender, while a change to polyflow.datapool.sender can't break camunda.taskpool.api.business.
- Position
- Below the diagonal: polyflow.datapool.sender uses a module listed above it, which is the healthy direction.
8→19 polyflow.datapool.sender uses polyflow.datapool part of a loop✕
- Connections
- 4 pairs of types, where a type in polyflow.datapool.sender uses a type in polyflow.datapool.
- The types involved
io.holunda.polyflow.datapool.sender.AbstractDataEntryCommandSender→io.holunda.polyflow.datapool.DataEntrySenderPropertiesio.holunda.polyflow.datapool.sender.AbstractTxAwareAccumulatingDataEntryCommandSender→io.holunda.polyflow.datapool.DataEntrySenderPropertiesio.holunda.polyflow.datapool.sender.DirectTxAwareAccumulatingDataEntryCommandSender→io.holunda.polyflow.datapool.DataEntrySenderPropertiesio.holunda.polyflow.datapool.sender.SimpleDataEntryCommandSender→io.holunda.polyflow.datapool.DataEntrySenderProperties
- Direction
- polyflow.datapool.sender uses polyflow.datapool, so a change to polyflow.datapool can break polyflow.datapool.sender, while a change to polyflow.datapool.sender can't break polyflow.datapool.
- 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→35 polyflow.taskpool.collector.task.enricher uses polyflow.taskpool.collector.task part of a loop✕
- Connections
- 3 pairs of types, where a type in polyflow.taskpool.collector.task.enricher uses a type in polyflow.taskpool.collector.task.
- The types involved
io.holunda.polyflow.taskpool.collector.task.enricher.EmptyTaskCommandEnricher→io.holunda.polyflow.taskpool.collector.task.VariablesEnricherio.holunda.polyflow.taskpool.collector.task.enricher.ProcessVariablesTaskCommandEnricher→io.holunda.polyflow.taskpool.collector.task.TaskVariableLoaderio.holunda.polyflow.taskpool.collector.task.enricher.ProcessVariablesTaskCommandEnricher→io.holunda.polyflow.taskpool.collector.task.VariablesEnricher
- Direction
- polyflow.taskpool.collector.task.enricher uses polyflow.taskpool.collector.task, so a change to polyflow.taskpool.collector.task can break polyflow.taskpool.collector.task.enricher, while a change to polyflow.taskpool.collector.task.enricher can't break polyflow.taskpool.collector.task.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→27 polyflow.taskpool.sender.gateway uses polyflow.taskpool.sender part of a loop✕
- Connections
- 1 pair of types, where a type in polyflow.taskpool.sender.gateway uses a type in polyflow.taskpool.sender.
- The types involved
io.holunda.polyflow.taskpool.sender.gateway.AxonCommandListGateway→io.holunda.polyflow.taskpool.sender.SenderProperties
- Direction
- polyflow.taskpool.sender.gateway uses polyflow.taskpool.sender, so a change to polyflow.taskpool.sender can break polyflow.taskpool.sender.gateway, while a change to polyflow.taskpool.sender.gateway can't break polyflow.taskpool.sender.
- 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→26 polyflow.view.filter uses polyflow.view part of a loop✕
- Connections
- 3 pairs of types, where a type in polyflow.view.filter uses a type in polyflow.view.
- The types involved
io.holunda.polyflow.view.filter.FilterKt→io.holunda.polyflow.view.DataEntryio.holunda.polyflow.view.filter.FilterKt→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.filter.FilterKt→io.holunda.polyflow.view.TaskWithDataEntries
- Direction
- polyflow.view.filter uses polyflow.view, so a change to polyflow.view can break polyflow.view.filter, while a change to polyflow.view.filter can't break polyflow.view.
- 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.
12→4 polyflow.view.query.process uses polyflow.view.auth✕
- Connections
- 1 pair of types, where a type in polyflow.view.query.process uses a type in polyflow.view.auth.
- The types involved
io.holunda.polyflow.view.query.process.ProcessDefinitionsStartableByUserQuery→io.holunda.polyflow.view.auth.User
- Direction
- polyflow.view.query.process uses polyflow.view.auth, so a change to polyflow.view.auth can break polyflow.view.query.process, while a change to polyflow.view.query.process can't break polyflow.view.auth.
- Position
- Below the diagonal: polyflow.view.query.process uses a module listed above it, which is the healthy direction.
12→6 polyflow.view.query.process uses polyflow.view.query✕
- Connections
- 4 pairs of types, where a type in polyflow.view.query.process uses a type in polyflow.view.query.
- The types involved
io.holunda.polyflow.view.query.process.ProcessDefinitionsStartableByUserQuery→io.holunda.polyflow.view.query.FilterQueryio.holunda.polyflow.view.query.process.ProcessInstanceQueryResult→io.holunda.polyflow.view.query.PageableSortableQueryio.holunda.polyflow.view.query.process.ProcessInstanceQueryResult→io.holunda.polyflow.view.query.QueryResultio.holunda.polyflow.view.query.process.ProcessInstancesByStateQuery→io.holunda.polyflow.view.query.FilterQuery
- Direction
- polyflow.view.query.process uses polyflow.view.query, so a change to polyflow.view.query can break polyflow.view.query.process, while a change to polyflow.view.query.process can't break polyflow.view.query.
- Position
- Below the diagonal: polyflow.view.query.process uses a module listed above it, which is the healthy direction.
12→26 polyflow.view.query.process uses polyflow.view part of a loop✕
- Connections
- 6 pairs of types, where a type in polyflow.view.query.process uses a type in polyflow.view.
- The types involved
io.holunda.polyflow.view.query.process.ProcessDefinitionApi→io.holunda.polyflow.view.ProcessDefinitionio.holunda.polyflow.view.query.process.ProcessDefinitionsStartableByUserQuery→io.holunda.polyflow.view.ProcessDefinitionio.holunda.polyflow.view.query.process.ProcessInstanceQueryResult→io.holunda.polyflow.view.ProcessInstanceio.holunda.polyflow.view.query.process.ProcessInstancesByStateQuery→io.holunda.polyflow.view.ProcessInstanceio.holunda.polyflow.view.query.process.ProcessInstancesByStateQuery→io.holunda.polyflow.view.ProcessInstanceStateio.holunda.polyflow.view.query.process.ReactiveProcessDefinitionApi→io.holunda.polyflow.view.ProcessDefinition
- Direction
- polyflow.view.query.process uses polyflow.view, so a change to polyflow.view can break polyflow.view.query.process, while a change to polyflow.view.query.process can't break polyflow.view.
- 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.
13→6 polyflow.view.query.process.variable uses polyflow.view.query✕
- Connections
- 1 pair of types, where a type in polyflow.view.query.process.variable uses a type in polyflow.view.query.
- The types involved
io.holunda.polyflow.view.query.process.variable.ProcessVariablesForInstanceQuery→io.holunda.polyflow.view.query.FilterQuery
- Direction
- polyflow.view.query.process.variable uses polyflow.view.query, so a change to polyflow.view.query can break polyflow.view.query.process.variable, while a change to polyflow.view.query.process.variable can't break polyflow.view.query.
- Position
- Below the diagonal: polyflow.view.query.process.variable uses a module listed above it, which is the healthy direction.
13→26 polyflow.view.query.process.variable uses polyflow.view part of a loop✕
- Connections
- 2 pairs of types, where a type in polyflow.view.query.process.variable uses a type in polyflow.view.
- The types involved
io.holunda.polyflow.view.query.process.variable.ProcessVariableQueryResult→io.holunda.polyflow.view.ProcessVariableio.holunda.polyflow.view.query.process.variable.ProcessVariablesForInstanceQuery→io.holunda.polyflow.view.ProcessVariable
- Direction
- polyflow.view.query.process.variable uses polyflow.view, so a change to polyflow.view can break polyflow.view.query.process.variable, while a change to polyflow.view.query.process.variable can't break polyflow.view.
- 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→4 polyflow.view.query.task uses polyflow.view.auth✕
- Connections
- 7 pairs of types, where a type in polyflow.view.query.task uses a type in polyflow.view.auth.
- The types involved
io.holunda.polyflow.view.query.task.TaskAttributeNamesQuery→io.holunda.polyflow.view.auth.Userio.holunda.polyflow.view.query.task.TaskAttributeValuesQuery→io.holunda.polyflow.view.auth.Userio.holunda.polyflow.view.query.task.TasksForCandidateUserAndGroupQuery→io.holunda.polyflow.view.auth.Userio.holunda.polyflow.view.query.task.TasksForGroupQuery→io.holunda.polyflow.view.auth.Userio.holunda.polyflow.view.query.task.TasksForUserQuery→io.holunda.polyflow.view.auth.Userio.holunda.polyflow.view.query.task.TasksWithDataEntriesForGroupQuery→io.holunda.polyflow.view.auth.Userio.holunda.polyflow.view.query.task.TasksWithDataEntriesForUserQuery→io.holunda.polyflow.view.auth.User
- Direction
- polyflow.view.query.task uses polyflow.view.auth, so a change to polyflow.view.auth can break polyflow.view.query.task, while a change to polyflow.view.query.task can't break polyflow.view.auth.
- Position
- Below the diagonal: polyflow.view.query.task uses a module listed above it, which is the healthy direction.
14→6 polyflow.view.query.task uses polyflow.view.query✕
- Connections
- 21 pairs of types, where a type in polyflow.view.query.task uses a type in polyflow.view.query.
- The types involved
io.holunda.polyflow.view.query.task.AllTasksWithDataEntriesQuery→io.holunda.polyflow.view.query.FilterQueryio.holunda.polyflow.view.query.task.AllTasksWithDataEntriesQuery→io.holunda.polyflow.view.query.PageableSortableQueryio.holunda.polyflow.view.query.task.PageableSortableFilteredTaskQuery→io.holunda.polyflow.view.query.FilterQueryio.holunda.polyflow.view.query.task.PageableSortableFilteredTaskQuery→io.holunda.polyflow.view.query.PageableSortableQueryio.holunda.polyflow.view.query.task.TaskAttributeNamesQuery→io.holunda.polyflow.view.query.FilterQueryio.holunda.polyflow.view.query.task.TaskAttributeNamesQueryResult→io.holunda.polyflow.view.query.PageableSortableQueryio.holunda.polyflow.view.query.task.TaskAttributeNamesQueryResult→io.holunda.polyflow.view.query.QueryResultio.holunda.polyflow.view.query.task.TaskAttributeValuesQuery→io.holunda.polyflow.view.query.FilterQueryio.holunda.polyflow.view.query.task.TaskAttributeValuesQueryResult→io.holunda.polyflow.view.query.PageableSortableQueryio.holunda.polyflow.view.query.task.TaskAttributeValuesQueryResult→io.holunda.polyflow.view.query.QueryResultio.holunda.polyflow.view.query.task.TaskForIdQuery→io.holunda.polyflow.view.query.FilterQueryio.holunda.polyflow.view.query.task.TaskQueryResult→io.holunda.polyflow.view.query.PageableSortableQueryio.holunda.polyflow.view.query.task.TaskQueryResult→io.holunda.polyflow.view.query.QueryResultio.holunda.polyflow.view.query.task.TaskWithDataEntriesForIdQuery→io.holunda.polyflow.view.query.FilterQueryio.holunda.polyflow.view.query.task.TasksForApplicationQuery→io.holunda.polyflow.view.query.FilterQueryio.holunda.polyflow.view.query.task.TasksWithDataEntriesForGroupQuery→io.holunda.polyflow.view.query.FilterQueryio.holunda.polyflow.view.query.task.TasksWithDataEntriesForGroupQuery→io.holunda.polyflow.view.query.PageableSortableQueryio.holunda.polyflow.view.query.task.TasksWithDataEntriesForUserQuery→io.holunda.polyflow.view.query.FilterQueryio.holunda.polyflow.view.query.task.TasksWithDataEntriesForUserQuery→io.holunda.polyflow.view.query.PageableSortableQueryio.holunda.polyflow.view.query.task.TasksWithDataEntriesQueryResult→io.holunda.polyflow.view.query.PageableSortableQueryio.holunda.polyflow.view.query.task.TasksWithDataEntriesQueryResult→io.holunda.polyflow.view.query.QueryResult
- Direction
- polyflow.view.query.task uses polyflow.view.query, so a change to polyflow.view.query can break polyflow.view.query.task, while a change to polyflow.view.query.task can't break polyflow.view.query.
- Position
- Below the diagonal: polyflow.view.query.task uses a module listed above it, which is the healthy direction.
14→26 polyflow.view.query.task uses polyflow.view part of a loop✕
- Connections
- 18 pairs of types, where a type in polyflow.view.query.task uses a type in polyflow.view.
- The types involved
io.holunda.polyflow.view.query.task.AllTasksQuery→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.query.task.AllTasksWithDataEntriesQuery→io.holunda.polyflow.view.TaskWithDataEntriesio.holunda.polyflow.view.query.task.ReactiveTaskApi→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.query.task.ReactiveTaskApi→io.holunda.polyflow.view.TaskWithDataEntriesio.holunda.polyflow.view.query.task.TaskApi→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.query.task.TaskApi→io.holunda.polyflow.view.TaskWithDataEntriesio.holunda.polyflow.view.query.task.TaskAttributeNamesQuery→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.query.task.TaskAttributeValuesQuery→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.query.task.TaskForIdQuery→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.query.task.TaskQueryResult→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.query.task.TaskWithDataEntriesForIdQuery→io.holunda.polyflow.view.TaskWithDataEntriesio.holunda.polyflow.view.query.task.TasksForApplicationQuery→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.query.task.TasksForCandidateUserAndGroupQuery→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.query.task.TasksForGroupQuery→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.query.task.TasksForUserQuery→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.query.task.TasksWithDataEntriesForGroupQuery→io.holunda.polyflow.view.TaskWithDataEntriesio.holunda.polyflow.view.query.task.TasksWithDataEntriesForUserQuery→io.holunda.polyflow.view.TaskWithDataEntriesio.holunda.polyflow.view.query.task.TasksWithDataEntriesQueryResult→io.holunda.polyflow.view.TaskWithDataEntries
- Direction
- polyflow.view.query.task uses polyflow.view, so a change to polyflow.view can break polyflow.view.query.task, while a change to polyflow.view.query.task can't break polyflow.view.
- 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.
15→7 camunda.taskpool.api.process.definition uses camunda.taskpool.api.task✕
- Connections
- 1 pair of types, where a type in camunda.taskpool.api.process.definition uses a type in camunda.taskpool.api.task.
- The types involved
io.holunda.camunda.taskpool.api.process.definition.RegisterProcessDefinitionCommand→io.holunda.camunda.taskpool.api.task.WithFormKey
- Direction
- camunda.taskpool.api.process.definition uses camunda.taskpool.api.task, so a change to camunda.taskpool.api.task can break camunda.taskpool.api.process.definition, while a change to camunda.taskpool.api.process.definition can't break camunda.taskpool.api.task.
- Position
- Below the diagonal: camunda.taskpool.api.process.definition uses a module listed above it, which is the healthy direction.
16→1 camunda.taskpool.api.process.instance uses camunda.taskpool.api.business✕
- Connections
- 2 pairs of types, where a type in camunda.taskpool.api.process.instance uses a type in camunda.taskpool.api.business.
- The types involved
io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceCommand→io.holunda.camunda.taskpool.api.business.WithCorrelationsio.holunda.camunda.taskpool.api.process.instance.ProcessInstanceEvent→io.holunda.camunda.taskpool.api.business.WithCorrelations
- Direction
- camunda.taskpool.api.process.instance uses camunda.taskpool.api.business, so a change to camunda.taskpool.api.business can break camunda.taskpool.api.process.instance, while a change to camunda.taskpool.api.process.instance can't break camunda.taskpool.api.business.
- Position
- Below the diagonal: camunda.taskpool.api.process.instance uses a module listed above it, which is the healthy direction.
16→7 camunda.taskpool.api.process.instance uses camunda.taskpool.api.task✕
- Connections
- 13 pairs of types, where a type in camunda.taskpool.api.process.instance uses a type in camunda.taskpool.api.task.
- The types involved
io.holunda.camunda.taskpool.api.process.instance.CancelProcessInstanceCommand→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.camunda.taskpool.api.process.instance.FinishProcessInstanceCommand→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.camunda.taskpool.api.process.instance.ProcessInstanceCancelledEvent→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.camunda.taskpool.api.process.instance.ProcessInstanceCommand→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.camunda.taskpool.api.process.instance.ProcessInstanceCommand→io.holunda.camunda.taskpool.api.task.WithPayloadio.holunda.camunda.taskpool.api.process.instance.ProcessInstanceEndedEvent→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.camunda.taskpool.api.process.instance.ProcessInstanceEvent→io.holunda.camunda.taskpool.api.task.WithPayloadio.holunda.camunda.taskpool.api.process.instance.ProcessInstanceResumedEvent→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.camunda.taskpool.api.process.instance.ProcessInstanceStartedEvent→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.camunda.taskpool.api.process.instance.ProcessInstanceSuspendedEvent→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.camunda.taskpool.api.process.instance.ResumeProcessInstanceCommand→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.camunda.taskpool.api.process.instance.StartProcessInstanceCommand→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.camunda.taskpool.api.process.instance.SuspendProcessInstanceCommand→io.holunda.camunda.taskpool.api.task.SourceReference
- Direction
- camunda.taskpool.api.process.instance uses camunda.taskpool.api.task, so a change to camunda.taskpool.api.task can break camunda.taskpool.api.process.instance, while a change to camunda.taskpool.api.process.instance can't break camunda.taskpool.api.task.
- Position
- Below the diagonal: camunda.taskpool.api.process.instance uses a module listed above it, which is the healthy direction.
17→7 camunda.taskpool.api.process.variable uses camunda.taskpool.api.task✕
- Connections
- 2 pairs of types, where a type in camunda.taskpool.api.process.variable uses a type in camunda.taskpool.api.task.
- The types involved
io.holunda.camunda.taskpool.api.process.variable.ChangeProcessVariablesForExecutionCommand→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.camunda.taskpool.api.process.variable.ProcessVariablesChangedEvent→io.holunda.camunda.taskpool.api.task.SourceReference
- Direction
- camunda.taskpool.api.process.variable uses camunda.taskpool.api.task, so a change to camunda.taskpool.api.task can break camunda.taskpool.api.process.variable, while a change to camunda.taskpool.api.process.variable can't break camunda.taskpool.api.task.
- Position
- Below the diagonal: camunda.taskpool.api.process.variable uses a module listed above it, which is the healthy direction.
18→7 camunda.taskpool.model uses camunda.taskpool.api.task✕
- Connections
- 1 pair of types, where a type in camunda.taskpool.model uses a type in camunda.taskpool.api.task.
- The types involved
io.holunda.camunda.taskpool.model.Task→io.holunda.camunda.taskpool.api.task.SourceReference
- Direction
- camunda.taskpool.model uses camunda.taskpool.api.task, so a change to camunda.taskpool.api.task can break camunda.taskpool.model, while a change to camunda.taskpool.model can't break camunda.taskpool.api.task.
- Position
- Below the diagonal: camunda.taskpool.model uses a module listed above it, which is the healthy direction.
19→8 polyflow.datapool uses polyflow.datapool.sender✕
- Connections
- 1 pair of types, where a type in polyflow.datapool uses a type in polyflow.datapool.sender.
- The types involved
io.holunda.polyflow.datapool.DataEntrySenderConfiguration→io.holunda.polyflow.datapool.sender.AbstractDataEntryCommandSender
- Direction
- polyflow.datapool uses polyflow.datapool.sender, so a change to polyflow.datapool.sender can break polyflow.datapool, while a change to polyflow.datapool can't break polyflow.datapool.sender.
- Position
- Below the diagonal: polyflow.datapool uses a module listed above it, which is the healthy direction.
20→1 polyflow.view.query.data uses camunda.taskpool.api.business✕
- Connections
- 2 pairs of types, where a type in polyflow.view.query.data uses a type in camunda.taskpool.api.business.
- The types involved
io.holunda.polyflow.view.query.data.DataEntryForIdentityQuery→io.holunda.camunda.taskpool.api.business.DataIdentityio.holunda.polyflow.view.query.data.QueryDataIdentity→io.holunda.camunda.taskpool.api.business.DataIdentity
- Direction
- polyflow.view.query.data uses camunda.taskpool.api.business, so a change to camunda.taskpool.api.business can break polyflow.view.query.data, while a change to polyflow.view.query.data can't break camunda.taskpool.api.business.
- Position
- Below the diagonal: polyflow.view.query.data uses a module listed above it, which is the healthy direction.
20→4 polyflow.view.query.data uses polyflow.view.auth✕
- Connections
- 1 pair of types, where a type in polyflow.view.query.data uses a type in polyflow.view.auth.
- The types involved
io.holunda.polyflow.view.query.data.DataEntriesForUserQuery→io.holunda.polyflow.view.auth.User
- Direction
- polyflow.view.query.data uses polyflow.view.auth, so a change to polyflow.view.auth can break polyflow.view.query.data, while a change to polyflow.view.query.data can't break polyflow.view.auth.
- Position
- Below the diagonal: polyflow.view.query.data uses a module listed above it, which is the healthy direction.
20→6 polyflow.view.query.data uses polyflow.view.query✕
- Connections
- 9 pairs of types, where a type in polyflow.view.query.data uses a type in polyflow.view.query.
- The types involved
io.holunda.polyflow.view.query.data.DataEntriesForDataEntryTypeQuery→io.holunda.polyflow.view.query.FilterQueryio.holunda.polyflow.view.query.data.DataEntriesForDataEntryTypeQuery→io.holunda.polyflow.view.query.PageableSortableQueryio.holunda.polyflow.view.query.data.DataEntriesForUserQuery→io.holunda.polyflow.view.query.FilterQueryio.holunda.polyflow.view.query.data.DataEntriesForUserQuery→io.holunda.polyflow.view.query.PageableSortableQueryio.holunda.polyflow.view.query.data.DataEntriesQuery→io.holunda.polyflow.view.query.FilterQueryio.holunda.polyflow.view.query.data.DataEntriesQuery→io.holunda.polyflow.view.query.PageableSortableQueryio.holunda.polyflow.view.query.data.DataEntriesQueryResult→io.holunda.polyflow.view.query.PageableSortableQueryio.holunda.polyflow.view.query.data.DataEntriesQueryResult→io.holunda.polyflow.view.query.QueryResultio.holunda.polyflow.view.query.data.DataEntryForIdentityQuery→io.holunda.polyflow.view.query.FilterQuery
- Direction
- polyflow.view.query.data uses polyflow.view.query, so a change to polyflow.view.query can break polyflow.view.query.data, while a change to polyflow.view.query.data can't break polyflow.view.query.
- Position
- Below the diagonal: polyflow.view.query.data uses a module listed above it, which is the healthy direction.
20→11 polyflow.view.query.data uses polyflow.view.filter✕
- Connections
- 2 pairs of types, where a type in polyflow.view.query.data uses a type in polyflow.view.filter.
- The types involved
io.holunda.polyflow.view.query.data.DataEntriesForUserQuery→io.holunda.polyflow.view.filter.DataEntryPredicateWrapperio.holunda.polyflow.view.query.data.DataEntriesQuery→io.holunda.polyflow.view.filter.DataEntryPredicateWrapper
- Direction
- polyflow.view.query.data uses polyflow.view.filter, so a change to polyflow.view.filter can break polyflow.view.query.data, while a change to polyflow.view.query.data can't break polyflow.view.filter.
- Position
- Below the diagonal: polyflow.view.query.data uses a module listed above it, which is the healthy direction.
20→26 polyflow.view.query.data uses polyflow.view part of a loop✕
- Connections
- 7 pairs of types, where a type in polyflow.view.query.data uses a type in polyflow.view.
- The types involved
io.holunda.polyflow.view.query.data.DataEntriesForDataEntryTypeQuery→io.holunda.polyflow.view.DataEntryio.holunda.polyflow.view.query.data.DataEntriesForUserQuery→io.holunda.polyflow.view.DataEntryio.holunda.polyflow.view.query.data.DataEntriesQuery→io.holunda.polyflow.view.DataEntryio.holunda.polyflow.view.query.data.DataEntriesQueryResult→io.holunda.polyflow.view.DataEntryio.holunda.polyflow.view.query.data.DataEntryApi→io.holunda.polyflow.view.DataEntryio.holunda.polyflow.view.query.data.DataEntryForIdentityQuery→io.holunda.polyflow.view.DataEntryio.holunda.polyflow.view.query.data.ReactiveDataEntryApi→io.holunda.polyflow.view.DataEntry
- Direction
- polyflow.view.query.data uses polyflow.view, so a change to polyflow.view can break polyflow.view.query.data, while a change to polyflow.view.query.data can't break polyflow.view.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→15 camunda.taskpool.mapper.process uses camunda.taskpool.api.process.definition✕
- Connections
- 4 pairs of types, where a type in camunda.taskpool.mapper.process uses a type in camunda.taskpool.api.process.definition.
- The types involved
io.holunda.camunda.taskpool.mapper.process.ProcessDefinitionMapperKt→io.holunda.camunda.taskpool.api.process.definition.ProcessDefinitionActivatedEventio.holunda.camunda.taskpool.mapper.process.ProcessDefinitionMapperKt→io.holunda.camunda.taskpool.api.process.definition.ProcessDefinitionRegisteredEventio.holunda.camunda.taskpool.mapper.process.ProcessDefinitionMapperKt→io.holunda.camunda.taskpool.api.process.definition.ProcessDefinitionSuspendedEventio.holunda.camunda.taskpool.mapper.process.ProcessDefinitionMapperKt→io.holunda.camunda.taskpool.api.process.definition.ProcessDefinitionUnregisteredEvent
- Direction
- camunda.taskpool.mapper.process uses camunda.taskpool.api.process.definition, so a change to camunda.taskpool.api.process.definition can break camunda.taskpool.mapper.process, while a change to camunda.taskpool.mapper.process can't break camunda.taskpool.api.process.definition.
- Position
- Below the diagonal: camunda.taskpool.mapper.process uses a module listed above it, which is the healthy direction.
21→16 camunda.taskpool.mapper.process uses camunda.taskpool.api.process.instance✕
- Connections
- 5 pairs of types, where a type in camunda.taskpool.mapper.process uses a type in camunda.taskpool.api.process.instance.
- The types involved
io.holunda.camunda.taskpool.mapper.process.ProcessInstanceMapperKt→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceCancelledEventio.holunda.camunda.taskpool.mapper.process.ProcessInstanceMapperKt→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceEndedEventio.holunda.camunda.taskpool.mapper.process.ProcessInstanceMapperKt→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceResumedEventio.holunda.camunda.taskpool.mapper.process.ProcessInstanceMapperKt→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceStartedEventio.holunda.camunda.taskpool.mapper.process.ProcessInstanceMapperKt→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceSuspendedEvent
- Direction
- camunda.taskpool.mapper.process uses camunda.taskpool.api.process.instance, so a change to camunda.taskpool.api.process.instance can break camunda.taskpool.mapper.process, while a change to camunda.taskpool.mapper.process can't break camunda.taskpool.api.process.instance.
- Position
- Below the diagonal: camunda.taskpool.mapper.process uses a module listed above it, which is the healthy direction.
21→17 camunda.taskpool.mapper.process uses camunda.taskpool.api.process.variable✕
- Connections
- 1 pair of types, where a type in camunda.taskpool.mapper.process uses a type in camunda.taskpool.api.process.variable.
- The types involved
io.holunda.camunda.taskpool.mapper.process.ProcessInstanceMapperKt→io.holunda.camunda.taskpool.api.process.variable.ProcessVariablesChangedEvent
- Direction
- camunda.taskpool.mapper.process uses camunda.taskpool.api.process.variable, so a change to camunda.taskpool.api.process.variable can break camunda.taskpool.mapper.process, while a change to camunda.taskpool.mapper.process can't break camunda.taskpool.api.process.variable.
- Position
- Below the diagonal: camunda.taskpool.mapper.process uses a module listed above it, which is the healthy direction.
22→15 polyflow.taskpool.core.process uses camunda.taskpool.api.process.definition✕
- Connections
- 9 pairs of types, where a type in polyflow.taskpool.core.process uses a type in camunda.taskpool.api.process.definition.
- The types involved
io.holunda.polyflow.taskpool.core.process.ProcessDefinitionAggregate→io.holunda.camunda.taskpool.api.process.definition.ActivateProcessDefinitionCommandio.holunda.polyflow.taskpool.core.process.ProcessDefinitionAggregate→io.holunda.camunda.taskpool.api.process.definition.ProcessDefinitionRegisteredEventio.holunda.polyflow.taskpool.core.process.ProcessDefinitionAggregate→io.holunda.camunda.taskpool.api.process.definition.RegisterProcessDefinitionCommandio.holunda.polyflow.taskpool.core.process.ProcessDefinitionAggregate→io.holunda.camunda.taskpool.api.process.definition.SuspendProcessDefinitionCommandio.holunda.polyflow.taskpool.core.process.ProcessDefinitionAggregate→io.holunda.camunda.taskpool.api.process.definition.UnregisterProcessDefinitionCommandio.holunda.polyflow.taskpool.core.process.ProcessDefinitionRegisterCommandHandler→io.holunda.camunda.taskpool.api.process.definition.ActivateProcessDefinitionCommandio.holunda.polyflow.taskpool.core.process.ProcessDefinitionRegisterCommandHandler→io.holunda.camunda.taskpool.api.process.definition.RegisterProcessDefinitionCommandio.holunda.polyflow.taskpool.core.process.ProcessDefinitionRegisterCommandHandler→io.holunda.camunda.taskpool.api.process.definition.SuspendProcessDefinitionCommandio.holunda.polyflow.taskpool.core.process.ProcessDefinitionRegisterCommandHandler→io.holunda.camunda.taskpool.api.process.definition.UnregisterProcessDefinitionCommand
- Direction
- polyflow.taskpool.core.process uses camunda.taskpool.api.process.definition, so a change to camunda.taskpool.api.process.definition can break polyflow.taskpool.core.process, while a change to polyflow.taskpool.core.process can't break camunda.taskpool.api.process.definition.
- Position
- Below the diagonal: polyflow.taskpool.core.process uses a module listed above it, which is the healthy direction.
22→16 polyflow.taskpool.core.process uses camunda.taskpool.api.process.instance✕
- Connections
- 6 pairs of types, where a type in polyflow.taskpool.core.process uses a type in camunda.taskpool.api.process.instance.
- The types involved
io.holunda.polyflow.taskpool.core.process.ProcessInstanceAggregate→io.holunda.camunda.taskpool.api.process.instance.CancelProcessInstanceCommandio.holunda.polyflow.taskpool.core.process.ProcessInstanceAggregate→io.holunda.camunda.taskpool.api.process.instance.FinishProcessInstanceCommandio.holunda.polyflow.taskpool.core.process.ProcessInstanceAggregate→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceStartedEventio.holunda.polyflow.taskpool.core.process.ProcessInstanceAggregate→io.holunda.camunda.taskpool.api.process.instance.ResumeProcessInstanceCommandio.holunda.polyflow.taskpool.core.process.ProcessInstanceAggregate→io.holunda.camunda.taskpool.api.process.instance.StartProcessInstanceCommandio.holunda.polyflow.taskpool.core.process.ProcessInstanceAggregate→io.holunda.camunda.taskpool.api.process.instance.SuspendProcessInstanceCommand
- Direction
- polyflow.taskpool.core.process uses camunda.taskpool.api.process.instance, so a change to camunda.taskpool.api.process.instance can break polyflow.taskpool.core.process, while a change to polyflow.taskpool.core.process can't break camunda.taskpool.api.process.instance.
- Position
- Below the diagonal: polyflow.taskpool.core.process uses a module listed above it, which is the healthy direction.
22→17 polyflow.taskpool.core.process uses camunda.taskpool.api.process.variable✕
- Connections
- 3 pairs of types, where a type in polyflow.taskpool.core.process uses a type in camunda.taskpool.api.process.variable.
- The types involved
io.holunda.polyflow.taskpool.core.process.ProcessInstanceAggregate→io.holunda.camunda.taskpool.api.process.variable.ChangeProcessVariablesForExecutionCommandio.holunda.polyflow.taskpool.core.process.ProcessInstanceAggregate→io.holunda.camunda.taskpool.api.process.variable.ProcessVariablesChangedEventio.holunda.polyflow.taskpool.core.process.ProcessInstanceVariablesChangeHandler→io.holunda.camunda.taskpool.api.process.variable.ChangeProcessVariablesForExecutionCommand
- Direction
- polyflow.taskpool.core.process uses camunda.taskpool.api.process.variable, so a change to camunda.taskpool.api.process.variable can break polyflow.taskpool.core.process, while a change to polyflow.taskpool.core.process can't break camunda.taskpool.api.process.variable.
- Position
- Below the diagonal: polyflow.taskpool.core.process uses a module listed above it, which is the healthy direction.
23→10 polyflow.taskpool.sender.process.definition uses polyflow.taskpool.sender.gateway✕
- Connections
- 1 pair of types, where a type in polyflow.taskpool.sender.process.definition uses a type in polyflow.taskpool.sender.gateway.
- The types involved
io.holunda.polyflow.taskpool.sender.process.definition.SimpleProcessDefinitionCommandSender→io.holunda.polyflow.taskpool.sender.gateway.CommandListGateway
- Direction
- polyflow.taskpool.sender.process.definition uses polyflow.taskpool.sender.gateway, so a change to polyflow.taskpool.sender.gateway can break polyflow.taskpool.sender.process.definition, while a change to polyflow.taskpool.sender.process.definition can't break polyflow.taskpool.sender.gateway.
- Position
- Below the diagonal: polyflow.taskpool.sender.process.definition uses a module listed above it, which is the healthy direction.
23→15 polyflow.taskpool.sender.process.definition uses camunda.taskpool.api.process.definition✕
- Connections
- 2 pairs of types, where a type in polyflow.taskpool.sender.process.definition uses a type in camunda.taskpool.api.process.definition.
- The types involved
io.holunda.polyflow.taskpool.sender.process.definition.ProcessDefinitionCommandSender→io.holunda.camunda.taskpool.api.process.definition.ProcessDefinitionCommandio.holunda.polyflow.taskpool.sender.process.definition.SimpleProcessDefinitionCommandSender→io.holunda.camunda.taskpool.api.process.definition.ProcessDefinitionCommand
- Direction
- polyflow.taskpool.sender.process.definition uses camunda.taskpool.api.process.definition, so a change to camunda.taskpool.api.process.definition can break polyflow.taskpool.sender.process.definition, while a change to polyflow.taskpool.sender.process.definition can't break camunda.taskpool.api.process.definition.
- Position
- Below the diagonal: polyflow.taskpool.sender.process.definition uses a module listed above it, which is the healthy direction.
23→27 polyflow.taskpool.sender.process.definition uses polyflow.taskpool.sender part of a loop✕
- Connections
- 1 pair of types, where a type in polyflow.taskpool.sender.process.definition uses a type in polyflow.taskpool.sender.
- The types involved
io.holunda.polyflow.taskpool.sender.process.definition.SimpleProcessDefinitionCommandSender→io.holunda.polyflow.taskpool.sender.SenderProperties
- Direction
- polyflow.taskpool.sender.process.definition uses polyflow.taskpool.sender, so a change to polyflow.taskpool.sender can break polyflow.taskpool.sender.process.definition, while a change to polyflow.taskpool.sender.process.definition can't break polyflow.taskpool.sender.
- 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.
24→10 polyflow.taskpool.sender.process.instance uses polyflow.taskpool.sender.gateway✕
- Connections
- 1 pair of types, where a type in polyflow.taskpool.sender.process.instance uses a type in polyflow.taskpool.sender.gateway.
- The types involved
io.holunda.polyflow.taskpool.sender.process.instance.SimpleProcessInstanceCommandSender→io.holunda.polyflow.taskpool.sender.gateway.CommandListGateway
- Direction
- polyflow.taskpool.sender.process.instance uses polyflow.taskpool.sender.gateway, so a change to polyflow.taskpool.sender.gateway can break polyflow.taskpool.sender.process.instance, while a change to polyflow.taskpool.sender.process.instance can't break polyflow.taskpool.sender.gateway.
- Position
- Below the diagonal: polyflow.taskpool.sender.process.instance uses a module listed above it, which is the healthy direction.
24→16 polyflow.taskpool.sender.process.instance uses camunda.taskpool.api.process.instance✕
- Connections
- 2 pairs of types, where a type in polyflow.taskpool.sender.process.instance uses a type in camunda.taskpool.api.process.instance.
- The types involved
io.holunda.polyflow.taskpool.sender.process.instance.ProcessInstanceCommandSender→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceCommandio.holunda.polyflow.taskpool.sender.process.instance.SimpleProcessInstanceCommandSender→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceCommand
- Direction
- polyflow.taskpool.sender.process.instance uses camunda.taskpool.api.process.instance, so a change to camunda.taskpool.api.process.instance can break polyflow.taskpool.sender.process.instance, while a change to polyflow.taskpool.sender.process.instance can't break camunda.taskpool.api.process.instance.
- Position
- Below the diagonal: polyflow.taskpool.sender.process.instance uses a module listed above it, which is the healthy direction.
24→27 polyflow.taskpool.sender.process.instance uses polyflow.taskpool.sender part of a loop✕
- Connections
- 1 pair of types, where a type in polyflow.taskpool.sender.process.instance uses a type in polyflow.taskpool.sender.
- The types involved
io.holunda.polyflow.taskpool.sender.process.instance.SimpleProcessInstanceCommandSender→io.holunda.polyflow.taskpool.sender.SenderProperties
- Direction
- polyflow.taskpool.sender.process.instance uses polyflow.taskpool.sender, so a change to polyflow.taskpool.sender can break polyflow.taskpool.sender.process.instance, while a change to polyflow.taskpool.sender.process.instance can't break polyflow.taskpool.sender.
- 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.
25→7 polyflow.taskpool.sender.process.variable uses camunda.taskpool.api.task✕
- Connections
- 4 pairs of types, where a type in polyflow.taskpool.sender.process.variable uses a type in camunda.taskpool.api.task.
- The types involved
io.holunda.polyflow.taskpool.sender.process.variable.CreateSingleProcessVariableCommand→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.polyflow.taskpool.sender.process.variable.DeleteSingleProcessVariableCommand→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.polyflow.taskpool.sender.process.variable.SingleProcessVariableCommand→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.polyflow.taskpool.sender.process.variable.UpdateSingleProcessVariableCommand→io.holunda.camunda.taskpool.api.task.SourceReference
- Direction
- polyflow.taskpool.sender.process.variable uses camunda.taskpool.api.task, so a change to camunda.taskpool.api.task can break polyflow.taskpool.sender.process.variable, while a change to polyflow.taskpool.sender.process.variable can't break camunda.taskpool.api.task.
- Position
- Below the diagonal: polyflow.taskpool.sender.process.variable uses a module listed above it, which is the healthy direction.
25→10 polyflow.taskpool.sender.process.variable uses polyflow.taskpool.sender.gateway✕
- Connections
- 2 pairs of types, where a type in polyflow.taskpool.sender.process.variable uses a type in polyflow.taskpool.sender.gateway.
- The types involved
io.holunda.polyflow.taskpool.sender.process.variable.SimpleProcessVariableCommandSender→io.holunda.polyflow.taskpool.sender.gateway.CommandListGatewayio.holunda.polyflow.taskpool.sender.process.variable.TxAwareAccumulatingProcessVariableCommandSender→io.holunda.polyflow.taskpool.sender.gateway.CommandListGateway
- Direction
- polyflow.taskpool.sender.process.variable uses polyflow.taskpool.sender.gateway, so a change to polyflow.taskpool.sender.gateway can break polyflow.taskpool.sender.process.variable, while a change to polyflow.taskpool.sender.process.variable can't break polyflow.taskpool.sender.gateway.
- Position
- Below the diagonal: polyflow.taskpool.sender.process.variable uses a module listed above it, which is the healthy direction.
25→17 polyflow.taskpool.sender.process.variable uses camunda.taskpool.api.process.variable✕
- Connections
- 2 pairs of types, where a type in polyflow.taskpool.sender.process.variable uses a type in camunda.taskpool.api.process.variable.
- The types involved
io.holunda.polyflow.taskpool.sender.process.variable.CreateSingleProcessVariableCommand→io.holunda.camunda.taskpool.api.process.variable.ProcessVariableValueio.holunda.polyflow.taskpool.sender.process.variable.UpdateSingleProcessVariableCommand→io.holunda.camunda.taskpool.api.process.variable.ProcessVariableValue
- Direction
- polyflow.taskpool.sender.process.variable uses camunda.taskpool.api.process.variable, so a change to camunda.taskpool.api.process.variable can break polyflow.taskpool.sender.process.variable, while a change to polyflow.taskpool.sender.process.variable can't break camunda.taskpool.api.process.variable.
- Position
- Below the diagonal: polyflow.taskpool.sender.process.variable uses a module listed above it, which is the healthy direction.
25→27 polyflow.taskpool.sender.process.variable uses polyflow.taskpool.sender part of a loop✕
- Connections
- 2 pairs of types, where a type in polyflow.taskpool.sender.process.variable uses a type in polyflow.taskpool.sender.
- The types involved
io.holunda.polyflow.taskpool.sender.process.variable.SimpleProcessVariableCommandSender→io.holunda.polyflow.taskpool.sender.SenderPropertiesio.holunda.polyflow.taskpool.sender.process.variable.TxAwareAccumulatingProcessVariableCommandSender→io.holunda.polyflow.taskpool.sender.SenderProperties
- Direction
- polyflow.taskpool.sender.process.variable uses polyflow.taskpool.sender, so a change to polyflow.taskpool.sender can break polyflow.taskpool.sender.process.variable, while a change to polyflow.taskpool.sender.process.variable can't break polyflow.taskpool.sender.
- 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.
26→1 polyflow.view uses camunda.taskpool.api.business✕
- Connections
- 6 pairs of types, where a type in polyflow.view uses a type in camunda.taskpool.api.business.
- The types involved
io.holunda.polyflow.view.DataEntry→io.holunda.camunda.taskpool.api.business.DataEntryStateio.holunda.polyflow.view.DataEntry→io.holunda.camunda.taskpool.api.business.DataIdentityio.holunda.polyflow.view.ExtensionsKt→io.holunda.camunda.taskpool.api.business.DataEntryStateio.holunda.polyflow.view.ExtensionsKt→io.holunda.camunda.taskpool.api.business.Modificationio.holunda.polyflow.view.ProtocolEntry→io.holunda.camunda.taskpool.api.business.DataEntryStateio.holunda.polyflow.view.Task→io.holunda.camunda.taskpool.api.business.WithCorrelations
- Direction
- polyflow.view uses camunda.taskpool.api.business, so a change to camunda.taskpool.api.business can break polyflow.view, while a change to polyflow.view can't break camunda.taskpool.api.business.
- Position
- Below the diagonal: polyflow.view uses a module listed above it, which is the healthy direction.
26→7 polyflow.view uses camunda.taskpool.api.task✕
- Connections
- 10 pairs of types, where a type in polyflow.view uses a type in camunda.taskpool.api.task.
- The types involved
io.holunda.polyflow.view.ExtensionsKt→io.holunda.camunda.taskpool.api.task.TaskAssignedEngineEventio.holunda.polyflow.view.ExtensionsKt→io.holunda.camunda.taskpool.api.task.TaskAttributeUpdatedEngineEventio.holunda.polyflow.view.ExtensionsKt→io.holunda.camunda.taskpool.api.task.TaskCandidateGroupChangedio.holunda.polyflow.view.ExtensionsKt→io.holunda.camunda.taskpool.api.task.TaskCandidateUserChangedio.holunda.polyflow.view.ExtensionsKt→io.holunda.camunda.taskpool.api.task.TaskCreatedEngineEventio.holunda.polyflow.view.ProcessInstance→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.polyflow.view.ProcessVariable→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.polyflow.view.Task→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.polyflow.view.Task→io.holunda.camunda.taskpool.api.task.TaskIdentityio.holunda.polyflow.view.Task→io.holunda.camunda.taskpool.api.task.WithPayload
- Direction
- polyflow.view uses camunda.taskpool.api.task, so a change to camunda.taskpool.api.task can break polyflow.view, while a change to polyflow.view can't break camunda.taskpool.api.task.
- Position
- Below the diagonal: polyflow.view uses a module listed above it, which is the healthy direction.
26→12 polyflow.view uses polyflow.view.query.process✕
- Connections
- 6 pairs of types, where a type in polyflow.view uses a type in polyflow.view.query.process.
- The types involved
io.holunda.polyflow.view.ProcessDefinitionQueryClient→io.holunda.polyflow.view.query.process.ProcessDefinitionsStartableByUserQueryio.holunda.polyflow.view.ProcessInstanceQueryClient→io.holunda.polyflow.view.query.process.ProcessInstanceQueryResultio.holunda.polyflow.view.ProcessInstanceQueryClient→io.holunda.polyflow.view.query.process.ProcessInstancesByStateQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.process.ProcessDefinitionsStartableByUserQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.process.ProcessInstanceQueryResultio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.process.ProcessInstancesByStateQuery
- Direction
- polyflow.view uses polyflow.view.query.process, so a change to polyflow.view.query.process can break polyflow.view, while a change to polyflow.view can't break polyflow.view.query.process.
- Position
- Below the diagonal: polyflow.view uses a module listed above it, which is the healthy direction.
26→13 polyflow.view uses polyflow.view.query.process.variable✕
- Connections
- 4 pairs of types, where a type in polyflow.view uses a type in polyflow.view.query.process.variable.
- The types involved
io.holunda.polyflow.view.ProcessVariableQueryClient→io.holunda.polyflow.view.query.process.variable.ProcessVariableQueryResultio.holunda.polyflow.view.ProcessVariableQueryClient→io.holunda.polyflow.view.query.process.variable.ProcessVariablesForInstanceQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.process.variable.ProcessVariableQueryResultio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.process.variable.ProcessVariablesForInstanceQuery
- Direction
- polyflow.view uses polyflow.view.query.process.variable, so a change to polyflow.view.query.process.variable can break polyflow.view, while a change to polyflow.view can't break polyflow.view.query.process.variable.
- Position
- Below the diagonal: polyflow.view uses a module listed above it, which is the healthy direction.
26→14 polyflow.view uses polyflow.view.query.task✕
- Connections
- 36 pairs of types, where a type in polyflow.view uses a type in polyflow.view.query.task. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.AllTasksQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.AllTasksWithDataEntriesQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.ApplicationWithTaskCountio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.TaskAttributeNamesQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.TaskAttributeNamesQueryResultio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.TaskAttributeValuesQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.TaskAttributeValuesQueryResultio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.TaskCountByApplicationQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.TaskForIdQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.TaskQueryResultio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.TaskWithDataEntriesForIdQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.TasksForApplicationQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.TasksForCandidateUserAndGroupQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.TasksForGroupQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.TasksForUserQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.TasksWithDataEntriesForGroupQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.TasksWithDataEntriesForUserQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.task.TasksWithDataEntriesQueryResultio.holunda.polyflow.view.TaskQueryClient→io.holunda.polyflow.view.query.task.AllTasksQueryio.holunda.polyflow.view.TaskQueryClient→io.holunda.polyflow.view.query.task.AllTasksWithDataEntriesQueryio.holunda.polyflow.view.TaskQueryClient→io.holunda.polyflow.view.query.task.ApplicationWithTaskCountio.holunda.polyflow.view.TaskQueryClient→io.holunda.polyflow.view.query.task.TaskAttributeNamesQueryio.holunda.polyflow.view.TaskQueryClient→io.holunda.polyflow.view.query.task.TaskAttributeNamesQueryResultio.holunda.polyflow.view.TaskQueryClient→io.holunda.polyflow.view.query.task.TaskAttributeValuesQueryio.holunda.polyflow.view.TaskQueryClient→io.holunda.polyflow.view.query.task.TaskAttributeValuesQueryResult
- Direction
- polyflow.view uses polyflow.view.query.task, so a change to polyflow.view.query.task can break polyflow.view, while a change to polyflow.view can't break polyflow.view.query.task.
- Position
- Below the diagonal: polyflow.view uses a module listed above it, which is the healthy direction.
26→17 polyflow.view uses camunda.taskpool.api.process.variable✕
- Connections
- 1 pair of types, where a type in polyflow.view uses a type in camunda.taskpool.api.process.variable.
- The types involved
io.holunda.polyflow.view.ProcessVariable→io.holunda.camunda.taskpool.api.process.variable.ProcessVariableValue
- Direction
- polyflow.view uses camunda.taskpool.api.process.variable, so a change to camunda.taskpool.api.process.variable can break polyflow.view, while a change to polyflow.view can't break camunda.taskpool.api.process.variable.
- Position
- Below the diagonal: polyflow.view uses a module listed above it, which is the healthy direction.
26→20 polyflow.view uses polyflow.view.query.data✕
- Connections
- 10 pairs of types, where a type in polyflow.view uses a type in polyflow.view.query.data.
- The types involved
io.holunda.polyflow.view.DataEntryQueryClient→io.holunda.polyflow.view.query.data.DataEntriesForDataEntryTypeQueryio.holunda.polyflow.view.DataEntryQueryClient→io.holunda.polyflow.view.query.data.DataEntriesForUserQueryio.holunda.polyflow.view.DataEntryQueryClient→io.holunda.polyflow.view.query.data.DataEntriesQueryio.holunda.polyflow.view.DataEntryQueryClient→io.holunda.polyflow.view.query.data.DataEntriesQueryResultio.holunda.polyflow.view.DataEntryQueryClient→io.holunda.polyflow.view.query.data.DataEntryForIdentityQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.data.DataEntriesForDataEntryTypeQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.data.DataEntriesForUserQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.data.DataEntriesQueryio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.data.DataEntriesQueryResultio.holunda.polyflow.view.QueryGatewayExt→io.holunda.polyflow.view.query.data.DataEntryForIdentityQuery
- Direction
- polyflow.view uses polyflow.view.query.data, so a change to polyflow.view.query.data can break polyflow.view, while a change to polyflow.view can't break polyflow.view.query.data.
- Position
- Below the diagonal: polyflow.view uses a module listed above it, which is the healthy direction.
27→7 polyflow.taskpool.sender uses camunda.taskpool.api.task✕
- Connections
- 13 pairs of types, where a type in polyflow.taskpool.sender uses a type in camunda.taskpool.api.task.
- The types involved
io.holunda.polyflow.taskpool.sender.CamundaJobSenderConfiguration→io.holunda.camunda.taskpool.api.task.EngineTaskCommandio.holunda.polyflow.taskpool.sender.EngineTaskCommandsSendingJobHandler→io.holunda.camunda.taskpool.api.task.EngineTaskCommandio.holunda.polyflow.taskpool.sender.GenericTaskPublisher→io.holunda.camunda.taskpool.api.task.AddCandidateGroupsCommandio.holunda.polyflow.taskpool.sender.GenericTaskPublisher→io.holunda.camunda.taskpool.api.task.AddCandidateUsersCommandio.holunda.polyflow.taskpool.sender.GenericTaskPublisher→io.holunda.camunda.taskpool.api.task.AssignTaskCommandio.holunda.polyflow.taskpool.sender.GenericTaskPublisher→io.holunda.camunda.taskpool.api.task.CompleteTaskCommandio.holunda.polyflow.taskpool.sender.GenericTaskPublisher→io.holunda.camunda.taskpool.api.task.CreateTaskCommandio.holunda.polyflow.taskpool.sender.GenericTaskPublisher→io.holunda.camunda.taskpool.api.task.DeleteCandidateGroupsCommandio.holunda.polyflow.taskpool.sender.GenericTaskPublisher→io.holunda.camunda.taskpool.api.task.DeleteCandidateUsersCommandio.holunda.polyflow.taskpool.sender.GenericTaskPublisher→io.holunda.camunda.taskpool.api.task.DeleteTaskCommandio.holunda.polyflow.taskpool.sender.GenericTaskPublisher→io.holunda.camunda.taskpool.api.task.UpdateAttributeTaskCommandio.holunda.polyflow.taskpool.sender.SenderConfiguration→io.holunda.camunda.taskpool.api.task.EngineTaskCommandio.holunda.polyflow.taskpool.sender.TxAwareAccumulatingCamundaJobEngineTaskCommandSender→io.holunda.camunda.taskpool.api.task.EngineTaskCommand
- Direction
- polyflow.taskpool.sender uses camunda.taskpool.api.task, so a change to camunda.taskpool.api.task can break polyflow.taskpool.sender, while a change to polyflow.taskpool.sender can't break camunda.taskpool.api.task.
- Position
- Below the diagonal: polyflow.taskpool.sender uses a module listed above it, which is the healthy direction.
27→10 polyflow.taskpool.sender uses polyflow.taskpool.sender.gateway✕
- Connections
- 5 pairs of types, where a type in polyflow.taskpool.sender uses a type in polyflow.taskpool.sender.gateway.
- The types involved
io.holunda.polyflow.taskpool.sender.CamundaJobSenderConfiguration→io.holunda.polyflow.taskpool.sender.gateway.CommandListGatewayio.holunda.polyflow.taskpool.sender.EngineTaskCommandsSendingJobHandler→io.holunda.polyflow.taskpool.sender.gateway.CommandListGatewayio.holunda.polyflow.taskpool.sender.SenderConfiguration→io.holunda.polyflow.taskpool.sender.gateway.CommandErrorHandlerio.holunda.polyflow.taskpool.sender.SenderConfiguration→io.holunda.polyflow.taskpool.sender.gateway.CommandListGatewayio.holunda.polyflow.taskpool.sender.SenderConfiguration→io.holunda.polyflow.taskpool.sender.gateway.CommandSuccessHandler
- Direction
- polyflow.taskpool.sender uses polyflow.taskpool.sender.gateway, so a change to polyflow.taskpool.sender.gateway can break polyflow.taskpool.sender, while a change to polyflow.taskpool.sender can't break polyflow.taskpool.sender.gateway.
- Position
- Below the diagonal: polyflow.taskpool.sender uses a module listed above it, which is the healthy direction.
27→23 polyflow.taskpool.sender uses polyflow.taskpool.sender.process.definition✕
- Connections
- 1 pair of types, where a type in polyflow.taskpool.sender uses a type in polyflow.taskpool.sender.process.definition.
- The types involved
io.holunda.polyflow.taskpool.sender.SenderConfiguration→io.holunda.polyflow.taskpool.sender.process.definition.ProcessDefinitionCommandSender
- Direction
- polyflow.taskpool.sender uses polyflow.taskpool.sender.process.definition, so a change to polyflow.taskpool.sender.process.definition can break polyflow.taskpool.sender, while a change to polyflow.taskpool.sender can't break polyflow.taskpool.sender.process.definition.
- Position
- Below the diagonal: polyflow.taskpool.sender uses a module listed above it, which is the healthy direction.
27→24 polyflow.taskpool.sender uses polyflow.taskpool.sender.process.instance✕
- Connections
- 1 pair of types, where a type in polyflow.taskpool.sender uses a type in polyflow.taskpool.sender.process.instance.
- The types involved
io.holunda.polyflow.taskpool.sender.SenderConfiguration→io.holunda.polyflow.taskpool.sender.process.instance.ProcessInstanceCommandSender
- Direction
- polyflow.taskpool.sender uses polyflow.taskpool.sender.process.instance, so a change to polyflow.taskpool.sender.process.instance can break polyflow.taskpool.sender, while a change to polyflow.taskpool.sender can't break polyflow.taskpool.sender.process.instance.
- Position
- Below the diagonal: polyflow.taskpool.sender uses a module listed above it, which is the healthy direction.
27→25 polyflow.taskpool.sender uses polyflow.taskpool.sender.process.variable✕
- Connections
- 1 pair of types, where a type in polyflow.taskpool.sender uses a type in polyflow.taskpool.sender.process.variable.
- The types involved
io.holunda.polyflow.taskpool.sender.SenderConfiguration→io.holunda.polyflow.taskpool.sender.process.variable.ProcessVariableCommandSender
- Direction
- polyflow.taskpool.sender uses polyflow.taskpool.sender.process.variable, so a change to polyflow.taskpool.sender.process.variable can break polyflow.taskpool.sender, while a change to polyflow.taskpool.sender can't break polyflow.taskpool.sender.process.variable.
- Position
- Below the diagonal: polyflow.taskpool.sender uses a module listed above it, which is the healthy direction.
27→32 polyflow.taskpool.sender uses polyflow.taskpool.sender.task part of a loop✕
- Connections
- 3 pairs of types, where a type in polyflow.taskpool.sender uses a type in polyflow.taskpool.sender.task.
- The types involved
io.holunda.polyflow.taskpool.sender.CamundaJobSenderConfiguration→io.holunda.polyflow.taskpool.sender.task.EngineTaskCommandSenderio.holunda.polyflow.taskpool.sender.SenderConfiguration→io.holunda.polyflow.taskpool.sender.task.EngineTaskCommandSenderio.holunda.polyflow.taskpool.sender.TxAwareAccumulatingCamundaJobEngineTaskCommandSender→io.holunda.polyflow.taskpool.sender.task.AbstractTxAwareAccumulatingEngineTaskCommandSender
- Direction
- polyflow.taskpool.sender uses polyflow.taskpool.sender.task, so a change to polyflow.taskpool.sender.task can break polyflow.taskpool.sender, while a change to polyflow.taskpool.sender can't break polyflow.taskpool.sender.task.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→1 polyflow.view.jpa.data uses camunda.taskpool.api.business✕
- Connections
- 6 pairs of types, where a type in polyflow.view.jpa.data uses a type in camunda.taskpool.api.business.
- The types involved
io.holunda.polyflow.view.jpa.data.ConverterExtKt→io.holunda.camunda.taskpool.api.business.DataEntryStateio.holunda.polyflow.view.jpa.data.ConverterExtKt→io.holunda.camunda.taskpool.api.business.Modificationio.holunda.polyflow.view.jpa.data.DataEntryEventHandler→io.holunda.camunda.taskpool.api.business.DataEntryAnonymizedEventio.holunda.polyflow.view.jpa.data.DataEntryEventHandler→io.holunda.camunda.taskpool.api.business.DataEntryCreatedEventio.holunda.polyflow.view.jpa.data.DataEntryEventHandler→io.holunda.camunda.taskpool.api.business.DataEntryDeletedEventio.holunda.polyflow.view.jpa.data.DataEntryEventHandler→io.holunda.camunda.taskpool.api.business.DataEntryUpdatedEvent
- Direction
- polyflow.view.jpa.data uses camunda.taskpool.api.business, so a change to camunda.taskpool.api.business can break polyflow.view.jpa.data, while a change to polyflow.view.jpa.data can't break camunda.taskpool.api.business.
- Position
- Below the diagonal: polyflow.view.jpa.data uses a module listed above it, which is the healthy direction.
28→3 polyflow.view.jpa.data uses camunda.variable.serializer✕
- Connections
- 1 pair of types, where a type in polyflow.view.jpa.data uses a type in camunda.variable.serializer.
- The types involved
io.holunda.polyflow.view.jpa.data.ConverterExtKt→io.holunda.camunda.variable.serializer.FilterType
- Direction
- polyflow.view.jpa.data uses camunda.variable.serializer, so a change to camunda.variable.serializer can break polyflow.view.jpa.data, while a change to polyflow.view.jpa.data can't break camunda.variable.serializer.
- Position
- Below the diagonal: polyflow.view.jpa.data uses a module listed above it, which is the healthy direction.
28→26 polyflow.view.jpa.data uses polyflow.view✕
- Connections
- 2 pairs of types, where a type in polyflow.view.jpa.data uses a type in polyflow.view.
- The types involved
io.holunda.polyflow.view.jpa.data.ConverterExtKt→io.holunda.polyflow.view.DataEntryio.holunda.polyflow.view.jpa.data.ConverterExtKt→io.holunda.polyflow.view.ProtocolEntry
- Direction
- polyflow.view.jpa.data uses polyflow.view, so a change to polyflow.view can break polyflow.view.jpa.data, while a change to polyflow.view.jpa.data can't break polyflow.view.
- Position
- Below the diagonal: polyflow.view.jpa.data uses a module listed above it, which is the healthy direction.
29→7 polyflow.view.jpa.process uses camunda.taskpool.api.task✕
- Connections
- 1 pair of types, where a type in polyflow.view.jpa.process uses a type in camunda.taskpool.api.task.
- The types involved
io.holunda.polyflow.view.jpa.process.ConverterExtKt→io.holunda.camunda.taskpool.api.task.SourceReference
- Direction
- polyflow.view.jpa.process uses camunda.taskpool.api.task, so a change to camunda.taskpool.api.task can break polyflow.view.jpa.process, while a change to polyflow.view.jpa.process can't break camunda.taskpool.api.task.
- Position
- Below the diagonal: polyflow.view.jpa.process uses a module listed above it, which is the healthy direction.
29→16 polyflow.view.jpa.process uses camunda.taskpool.api.process.instance✕
- Connections
- 4 pairs of types, where a type in polyflow.view.jpa.process uses a type in camunda.taskpool.api.process.instance.
- The types involved
io.holunda.polyflow.view.jpa.process.ConverterExtKt→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceCancelledEventio.holunda.polyflow.view.jpa.process.ConverterExtKt→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceEndedEventio.holunda.polyflow.view.jpa.process.ConverterExtKt→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceResumedEventio.holunda.polyflow.view.jpa.process.ConverterExtKt→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceSuspendedEvent
- Direction
- polyflow.view.jpa.process uses camunda.taskpool.api.process.instance, so a change to camunda.taskpool.api.process.instance can break polyflow.view.jpa.process, while a change to polyflow.view.jpa.process can't break camunda.taskpool.api.process.instance.
- Position
- Below the diagonal: polyflow.view.jpa.process uses a module listed above it, which is the healthy direction.
29→26 polyflow.view.jpa.process uses polyflow.view✕
- Connections
- 4 pairs of types, where a type in polyflow.view.jpa.process uses a type in polyflow.view.
- The types involved
io.holunda.polyflow.view.jpa.process.ConverterExtKt→io.holunda.polyflow.view.ProcessDefinitionio.holunda.polyflow.view.jpa.process.ConverterExtKt→io.holunda.polyflow.view.ProcessInstanceio.holunda.polyflow.view.jpa.process.ProcessDefinitionEntity→io.holunda.polyflow.view.ProcessDefinitionStateio.holunda.polyflow.view.jpa.process.ProcessInstanceEntity→io.holunda.polyflow.view.ProcessInstanceState
- Direction
- polyflow.view.jpa.process uses polyflow.view, so a change to polyflow.view can break polyflow.view.jpa.process, while a change to polyflow.view.jpa.process can't break polyflow.view.
- Position
- Below the diagonal: polyflow.view.jpa.process uses a module listed above it, which is the healthy direction.
30→1 polyflow.view.mongo.data uses camunda.taskpool.api.business✕
- Connections
- 1 pair of types, where a type in polyflow.view.mongo.data uses a type in camunda.taskpool.api.business.
- The types involved
io.holunda.polyflow.view.mongo.data.DataEntryDocumentKt→io.holunda.camunda.taskpool.api.business.DataEntryState
- Direction
- polyflow.view.mongo.data uses camunda.taskpool.api.business, so a change to camunda.taskpool.api.business can break polyflow.view.mongo.data, while a change to polyflow.view.mongo.data can't break camunda.taskpool.api.business.
- Position
- Below the diagonal: polyflow.view.mongo.data uses a module listed above it, which is the healthy direction.
30→26 polyflow.view.mongo.data uses polyflow.view✕
- Connections
- 3 pairs of types, where a type in polyflow.view.mongo.data uses a type in polyflow.view.
- The types involved
io.holunda.polyflow.view.mongo.data.DataEntryChangeTracker→io.holunda.polyflow.view.DataEntryio.holunda.polyflow.view.mongo.data.DataEntryDocumentKt→io.holunda.polyflow.view.DataEntryio.holunda.polyflow.view.mongo.data.ProtocolElement→io.holunda.polyflow.view.ProtocolEntry
- Direction
- polyflow.view.mongo.data uses polyflow.view, so a change to polyflow.view can break polyflow.view.mongo.data, while a change to polyflow.view.mongo.data can't break polyflow.view.
- Position
- Below the diagonal: polyflow.view.mongo.data uses a module listed above it, which is the healthy direction.
30→37 polyflow.view.mongo.data uses polyflow.view.mongo part of a loop✕
- Connections
- 1 pair of types, where a type in polyflow.view.mongo.data uses a type in polyflow.view.mongo.
- The types involved
io.holunda.polyflow.view.mongo.data.DataEntryChangeTracker→io.holunda.polyflow.view.mongo.TaskPoolMongoViewProperties
- Direction
- polyflow.view.mongo.data uses polyflow.view.mongo, so a change to polyflow.view.mongo can break polyflow.view.mongo.data, while a change to polyflow.view.mongo.data can't break polyflow.view.mongo.
- 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.
31→1 polyflow.view.simple.service uses camunda.taskpool.api.business✕
- Connections
- 8 pairs of types, where a type in polyflow.view.simple.service uses a type in camunda.taskpool.api.business.
- The types involved
io.holunda.polyflow.view.simple.service.SimpleDataEntryService→io.holunda.camunda.taskpool.api.business.DataEntryAnonymizedEventio.holunda.polyflow.view.simple.service.SimpleDataEntryService→io.holunda.camunda.taskpool.api.business.DataEntryCreatedEventio.holunda.polyflow.view.simple.service.SimpleDataEntryService→io.holunda.camunda.taskpool.api.business.DataEntryDeletedEventio.holunda.polyflow.view.simple.service.SimpleDataEntryService→io.holunda.camunda.taskpool.api.business.DataEntryUpdatedEventio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.camunda.taskpool.api.business.DataEntryAnonymizedEventio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.camunda.taskpool.api.business.DataEntryCreatedEventio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.camunda.taskpool.api.business.DataEntryDeletedEventio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.camunda.taskpool.api.business.DataEntryUpdatedEvent
- Direction
- polyflow.view.simple.service uses camunda.taskpool.api.business, so a change to camunda.taskpool.api.business can break polyflow.view.simple.service, while a change to polyflow.view.simple.service can't break camunda.taskpool.api.business.
- Position
- Below the diagonal: polyflow.view.simple.service uses a module listed above it, which is the healthy direction.
31→7 polyflow.view.simple.service uses camunda.taskpool.api.task✕
- Connections
- 8 pairs of types, where a type in polyflow.view.simple.service uses a type in camunda.taskpool.api.task.
- The types involved
io.holunda.polyflow.view.simple.service.ConvertersKt→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.camunda.taskpool.api.task.TaskAssignedEngineEventio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.camunda.taskpool.api.task.TaskAttributeUpdatedEngineEventio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.camunda.taskpool.api.task.TaskCandidateGroupChangedio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.camunda.taskpool.api.task.TaskCandidateUserChangedio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.camunda.taskpool.api.task.TaskCompletedEngineEventio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.camunda.taskpool.api.task.TaskCreatedEngineEventio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.camunda.taskpool.api.task.TaskDeletedEngineEvent
- Direction
- polyflow.view.simple.service uses camunda.taskpool.api.task, so a change to camunda.taskpool.api.task can break polyflow.view.simple.service, while a change to polyflow.view.simple.service can't break camunda.taskpool.api.task.
- Position
- Below the diagonal: polyflow.view.simple.service uses a module listed above it, which is the healthy direction.
31→12 polyflow.view.simple.service uses polyflow.view.query.process✕
- Connections
- 5 pairs of types, where a type in polyflow.view.simple.service uses a type in polyflow.view.query.process.
- The types involved
io.holunda.polyflow.view.simple.service.SimpleProcessDefinitionService→io.holunda.polyflow.view.query.process.ProcessDefinitionApiio.holunda.polyflow.view.simple.service.SimpleProcessDefinitionService→io.holunda.polyflow.view.query.process.ProcessDefinitionsStartableByUserQueryio.holunda.polyflow.view.simple.service.SimpleProcessInstanceService→io.holunda.polyflow.view.query.process.ProcessInstanceApiio.holunda.polyflow.view.simple.service.SimpleProcessInstanceService→io.holunda.polyflow.view.query.process.ProcessInstanceQueryResultio.holunda.polyflow.view.simple.service.SimpleProcessInstanceService→io.holunda.polyflow.view.query.process.ProcessInstancesByStateQuery
- Direction
- polyflow.view.simple.service uses polyflow.view.query.process, so a change to polyflow.view.query.process can break polyflow.view.simple.service, while a change to polyflow.view.simple.service can't break polyflow.view.query.process.
- Position
- Below the diagonal: polyflow.view.simple.service uses a module listed above it, which is the healthy direction.
31→13 polyflow.view.simple.service uses polyflow.view.query.process.variable✕
- Connections
- 3 pairs of types, where a type in polyflow.view.simple.service uses a type in polyflow.view.query.process.variable.
- The types involved
io.holunda.polyflow.view.simple.service.SimpleProcessVariableService→io.holunda.polyflow.view.query.process.variable.ProcessVariableApiio.holunda.polyflow.view.simple.service.SimpleProcessVariableService→io.holunda.polyflow.view.query.process.variable.ProcessVariableQueryResultio.holunda.polyflow.view.simple.service.SimpleProcessVariableService→io.holunda.polyflow.view.query.process.variable.ProcessVariablesForInstanceQuery
- Direction
- polyflow.view.simple.service uses polyflow.view.query.process.variable, so a change to polyflow.view.query.process.variable can break polyflow.view.simple.service, while a change to polyflow.view.simple.service can't break polyflow.view.query.process.variable.
- Position
- Below the diagonal: polyflow.view.simple.service uses a module listed above it, which is the healthy direction.
31→14 polyflow.view.simple.service uses polyflow.view.query.task✕
- Connections
- 20 pairs of types, where a type in polyflow.view.simple.service uses a type in polyflow.view.query.task.
- The types involved
io.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.AllTasksQueryio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.AllTasksWithDataEntriesQueryio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.ApplicationWithTaskCountio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.PageableSortableFilteredTaskQueryio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.TaskApiio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.TaskAttributeNamesQueryio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.TaskAttributeNamesQueryResultio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.TaskAttributeValuesQueryio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.TaskAttributeValuesQueryResultio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.TaskCountByApplicationQueryio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.TaskForIdQueryio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.TaskQueryResultio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.TaskWithDataEntriesForIdQueryio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.TasksForApplicationQueryio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.TasksForCandidateUserAndGroupQueryio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.TasksForGroupQueryio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.TasksForUserQueryio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.TasksWithDataEntriesForGroupQueryio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.TasksWithDataEntriesForUserQueryio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.query.task.TasksWithDataEntriesQueryResult
- Direction
- polyflow.view.simple.service uses polyflow.view.query.task, so a change to polyflow.view.query.task can break polyflow.view.simple.service, while a change to polyflow.view.simple.service can't break polyflow.view.query.task.
- Position
- Below the diagonal: polyflow.view.simple.service uses a module listed above it, which is the healthy direction.
31→15 polyflow.view.simple.service uses camunda.taskpool.api.process.definition✕
- Connections
- 4 pairs of types, where a type in polyflow.view.simple.service uses a type in camunda.taskpool.api.process.definition.
- The types involved
io.holunda.polyflow.view.simple.service.SimpleProcessDefinitionService→io.holunda.camunda.taskpool.api.process.definition.ProcessDefinitionActivatedEventio.holunda.polyflow.view.simple.service.SimpleProcessDefinitionService→io.holunda.camunda.taskpool.api.process.definition.ProcessDefinitionRegisteredEventio.holunda.polyflow.view.simple.service.SimpleProcessDefinitionService→io.holunda.camunda.taskpool.api.process.definition.ProcessDefinitionSuspendedEventio.holunda.polyflow.view.simple.service.SimpleProcessDefinitionService→io.holunda.camunda.taskpool.api.process.definition.ProcessDefinitionUnregisteredEvent
- Direction
- polyflow.view.simple.service uses camunda.taskpool.api.process.definition, so a change to camunda.taskpool.api.process.definition can break polyflow.view.simple.service, while a change to polyflow.view.simple.service can't break camunda.taskpool.api.process.definition.
- Position
- Below the diagonal: polyflow.view.simple.service uses a module listed above it, which is the healthy direction.
31→16 polyflow.view.simple.service uses camunda.taskpool.api.process.instance✕
- Connections
- 5 pairs of types, where a type in polyflow.view.simple.service uses a type in camunda.taskpool.api.process.instance.
- The types involved
io.holunda.polyflow.view.simple.service.SimpleProcessInstanceService→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceCancelledEventio.holunda.polyflow.view.simple.service.SimpleProcessInstanceService→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceEndedEventio.holunda.polyflow.view.simple.service.SimpleProcessInstanceService→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceResumedEventio.holunda.polyflow.view.simple.service.SimpleProcessInstanceService→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceStartedEventio.holunda.polyflow.view.simple.service.SimpleProcessInstanceService→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceSuspendedEvent
- Direction
- polyflow.view.simple.service uses camunda.taskpool.api.process.instance, so a change to camunda.taskpool.api.process.instance can break polyflow.view.simple.service, while a change to polyflow.view.simple.service can't break camunda.taskpool.api.process.instance.
- Position
- Below the diagonal: polyflow.view.simple.service uses a module listed above it, which is the healthy direction.
31→17 polyflow.view.simple.service uses camunda.taskpool.api.process.variable✕
- Connections
- 1 pair of types, where a type in polyflow.view.simple.service uses a type in camunda.taskpool.api.process.variable.
- The types involved
io.holunda.polyflow.view.simple.service.SimpleProcessVariableService→io.holunda.camunda.taskpool.api.process.variable.ProcessVariablesChangedEvent
- Direction
- polyflow.view.simple.service uses camunda.taskpool.api.process.variable, so a change to camunda.taskpool.api.process.variable can break polyflow.view.simple.service, while a change to polyflow.view.simple.service can't break camunda.taskpool.api.process.variable.
- Position
- Below the diagonal: polyflow.view.simple.service uses a module listed above it, which is the healthy direction.
31→20 polyflow.view.simple.service uses polyflow.view.query.data✕
- Connections
- 6 pairs of types, where a type in polyflow.view.simple.service uses a type in polyflow.view.query.data.
- The types involved
io.holunda.polyflow.view.simple.service.SimpleDataEntryService→io.holunda.polyflow.view.query.data.DataEntriesForDataEntryTypeQueryio.holunda.polyflow.view.simple.service.SimpleDataEntryService→io.holunda.polyflow.view.query.data.DataEntriesForUserQueryio.holunda.polyflow.view.simple.service.SimpleDataEntryService→io.holunda.polyflow.view.query.data.DataEntriesQueryio.holunda.polyflow.view.simple.service.SimpleDataEntryService→io.holunda.polyflow.view.query.data.DataEntriesQueryResultio.holunda.polyflow.view.simple.service.SimpleDataEntryService→io.holunda.polyflow.view.query.data.DataEntryApiio.holunda.polyflow.view.simple.service.SimpleDataEntryService→io.holunda.polyflow.view.query.data.DataEntryForIdentityQuery
- Direction
- polyflow.view.simple.service uses polyflow.view.query.data, so a change to polyflow.view.query.data can break polyflow.view.simple.service, while a change to polyflow.view.simple.service can't break polyflow.view.query.data.
- Position
- Below the diagonal: polyflow.view.simple.service uses a module listed above it, which is the healthy direction.
31→26 polyflow.view.simple.service uses polyflow.view✕
- Connections
- 11 pairs of types, where a type in polyflow.view.simple.service uses a type in polyflow.view.
- The types involved
io.holunda.polyflow.view.simple.service.ConvertersKt→io.holunda.polyflow.view.DataEntryio.holunda.polyflow.view.simple.service.ConvertersKt→io.holunda.polyflow.view.ProcessInstanceio.holunda.polyflow.view.simple.service.ConvertersKt→io.holunda.polyflow.view.ProcessVariableio.holunda.polyflow.view.simple.service.SimpleDataEntryService→io.holunda.polyflow.view.DataEntryio.holunda.polyflow.view.simple.service.SimpleProcessDefinitionService→io.holunda.polyflow.view.ProcessDefinitionio.holunda.polyflow.view.simple.service.SimpleProcessDefinitionService→io.holunda.polyflow.view.ProcessDefinitionStateio.holunda.polyflow.view.simple.service.SimpleProcessInstanceService→io.holunda.polyflow.view.ProcessInstanceio.holunda.polyflow.view.simple.service.SimpleProcessVariableService→io.holunda.polyflow.view.ProcessVariableio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.DataEntryio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.simple.service.SimpleTaskPoolService→io.holunda.polyflow.view.TaskWithDataEntries
- Direction
- polyflow.view.simple.service uses polyflow.view, so a change to polyflow.view can break polyflow.view.simple.service, while a change to polyflow.view.simple.service can't break polyflow.view.
- Position
- Below the diagonal: polyflow.view.simple.service uses a module listed above it, which is the healthy direction.
32→7 polyflow.taskpool.sender.task uses camunda.taskpool.api.task✕
- Connections
- 4 pairs of types, where a type in polyflow.taskpool.sender.task uses a type in camunda.taskpool.api.task.
- The types involved
io.holunda.polyflow.taskpool.sender.task.AbstractTxAwareAccumulatingEngineTaskCommandSender→io.holunda.camunda.taskpool.api.task.EngineTaskCommandio.holunda.polyflow.taskpool.sender.task.DirectTxAwareAccumulatingEngineTaskCommandSender→io.holunda.camunda.taskpool.api.task.EngineTaskCommandio.holunda.polyflow.taskpool.sender.task.EngineTaskCommandSender→io.holunda.camunda.taskpool.api.task.EngineTaskCommandio.holunda.polyflow.taskpool.sender.task.SimpleEngineTaskCommandSender→io.holunda.camunda.taskpool.api.task.EngineTaskCommand
- Direction
- polyflow.taskpool.sender.task uses camunda.taskpool.api.task, so a change to camunda.taskpool.api.task can break polyflow.taskpool.sender.task, while a change to polyflow.taskpool.sender.task can't break camunda.taskpool.api.task.
- Position
- Below the diagonal: polyflow.taskpool.sender.task uses a module listed above it, which is the healthy direction.
32→10 polyflow.taskpool.sender.task uses polyflow.taskpool.sender.gateway✕
- Connections
- 2 pairs of types, where a type in polyflow.taskpool.sender.task uses a type in polyflow.taskpool.sender.gateway.
- The types involved
io.holunda.polyflow.taskpool.sender.task.DirectTxAwareAccumulatingEngineTaskCommandSender→io.holunda.polyflow.taskpool.sender.gateway.CommandListGatewayio.holunda.polyflow.taskpool.sender.task.SimpleEngineTaskCommandSender→io.holunda.polyflow.taskpool.sender.gateway.CommandListGateway
- Direction
- polyflow.taskpool.sender.task uses polyflow.taskpool.sender.gateway, so a change to polyflow.taskpool.sender.gateway can break polyflow.taskpool.sender.task, while a change to polyflow.taskpool.sender.task can't break polyflow.taskpool.sender.gateway.
- Position
- Below the diagonal: polyflow.taskpool.sender.task uses a module listed above it, which is the healthy direction.
32→27 polyflow.taskpool.sender.task uses polyflow.taskpool.sender✕
- Connections
- 3 pairs of types, where a type in polyflow.taskpool.sender.task uses a type in polyflow.taskpool.sender.
- The types involved
io.holunda.polyflow.taskpool.sender.task.AbstractTxAwareAccumulatingEngineTaskCommandSender→io.holunda.polyflow.taskpool.sender.SenderPropertiesio.holunda.polyflow.taskpool.sender.task.DirectTxAwareAccumulatingEngineTaskCommandSender→io.holunda.polyflow.taskpool.sender.SenderPropertiesio.holunda.polyflow.taskpool.sender.task.SimpleEngineTaskCommandSender→io.holunda.polyflow.taskpool.sender.SenderProperties
- Direction
- polyflow.taskpool.sender.task uses polyflow.taskpool.sender, so a change to polyflow.taskpool.sender can break polyflow.taskpool.sender.task, while a change to polyflow.taskpool.sender.task can't break polyflow.taskpool.sender.
- Position
- Below the diagonal: polyflow.taskpool.sender.task uses a module listed above it, which is the healthy direction.
33→3 polyflow.view.jpa.task uses camunda.variable.serializer✕
- Connections
- 1 pair of types, where a type in polyflow.view.jpa.task uses a type in camunda.variable.serializer.
- The types involved
io.holunda.polyflow.view.jpa.task.ConverterExtKt→io.holunda.camunda.variable.serializer.FilterType
- Direction
- polyflow.view.jpa.task uses camunda.variable.serializer, so a change to camunda.variable.serializer can break polyflow.view.jpa.task, while a change to polyflow.view.jpa.task can't break camunda.variable.serializer.
- Position
- Below the diagonal: polyflow.view.jpa.task uses a module listed above it, which is the healthy direction.
33→7 polyflow.view.jpa.task uses camunda.taskpool.api.task✕
- Connections
- 1 pair of types, where a type in polyflow.view.jpa.task uses a type in camunda.taskpool.api.task.
- The types involved
io.holunda.polyflow.view.jpa.task.ConverterExtKt→io.holunda.camunda.taskpool.api.task.TaskAttributeUpdatedEngineEvent
- Direction
- polyflow.view.jpa.task uses camunda.taskpool.api.task, so a change to camunda.taskpool.api.task can break polyflow.view.jpa.task, while a change to polyflow.view.jpa.task can't break camunda.taskpool.api.task.
- Position
- Below the diagonal: polyflow.view.jpa.task uses a module listed above it, which is the healthy direction.
33→26 polyflow.view.jpa.task uses polyflow.view✕
- Connections
- 1 pair of types, where a type in polyflow.view.jpa.task uses a type in polyflow.view.
- The types involved
io.holunda.polyflow.view.jpa.task.ConverterExtKt→io.holunda.polyflow.view.Task
- Direction
- polyflow.view.jpa.task uses polyflow.view, so a change to polyflow.view can break polyflow.view.jpa.task, while a change to polyflow.view.jpa.task can't break polyflow.view.
- Position
- Below the diagonal: polyflow.view.jpa.task uses a module listed above it, which is the healthy direction.
33→28 polyflow.view.jpa.task uses polyflow.view.jpa.data✕
- Connections
- 2 pairs of types, where a type in polyflow.view.jpa.task uses a type in polyflow.view.jpa.data.
- The types involved
io.holunda.polyflow.view.jpa.task.TaskEntity→io.holunda.polyflow.view.jpa.data.DataEntryEntityio.holunda.polyflow.view.jpa.task.TaskEntity→io.holunda.polyflow.view.jpa.data.DataEntryId
- Direction
- polyflow.view.jpa.task uses polyflow.view.jpa.data, so a change to polyflow.view.jpa.data can break polyflow.view.jpa.task, while a change to polyflow.view.jpa.task can't break polyflow.view.jpa.data.
- Position
- Below the diagonal: polyflow.view.jpa.task uses a module listed above it, which is the healthy direction.
33→29 polyflow.view.jpa.task uses polyflow.view.jpa.process✕
- Connections
- 1 pair of types, where a type in polyflow.view.jpa.task uses a type in polyflow.view.jpa.process.
- The types involved
io.holunda.polyflow.view.jpa.task.TaskEntity→io.holunda.polyflow.view.jpa.process.SourceReferenceEmbeddable
- Direction
- polyflow.view.jpa.task uses polyflow.view.jpa.process, so a change to polyflow.view.jpa.process can break polyflow.view.jpa.task, while a change to polyflow.view.jpa.task can't break polyflow.view.jpa.process.
- Position
- Below the diagonal: polyflow.view.jpa.task uses a module listed above it, which is the healthy direction.
33→36 polyflow.view.jpa.task uses polyflow.view.jpa part of a loop✕
- Connections
- 1 pair of types, where a type in polyflow.view.jpa.task uses a type in polyflow.view.jpa.
- The types involved
io.holunda.polyflow.view.jpa.task.TaskRepository→io.holunda.polyflow.view.jpa.CountByApplication
- Direction
- polyflow.view.jpa.task uses polyflow.view.jpa, so a change to polyflow.view.jpa can break polyflow.view.jpa.task, while a change to polyflow.view.jpa.task can't break polyflow.view.jpa.
- 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 polyflow.view.mongo.task uses polyflow.view.auth✕
- Connections
- 2 pairs of types, where a type in polyflow.view.mongo.task uses a type in polyflow.view.auth.
- The types involved
io.holunda.polyflow.view.mongo.task.TaskWithDataEntriesRepositoryExtension→io.holunda.polyflow.view.auth.Userio.holunda.polyflow.view.mongo.task.TaskWithDataEntriesRepositoryExtensionImpl→io.holunda.polyflow.view.auth.User
- Direction
- polyflow.view.mongo.task uses polyflow.view.auth, so a change to polyflow.view.auth can break polyflow.view.mongo.task, while a change to polyflow.view.mongo.task can't break polyflow.view.auth.
- Position
- Below the diagonal: polyflow.view.mongo.task uses a module listed above it, which is the healthy direction.
34→7 polyflow.view.mongo.task uses camunda.taskpool.api.task✕
- Connections
- 4 pairs of types, where a type in polyflow.view.mongo.task uses a type in camunda.taskpool.api.task.
- The types involved
io.holunda.polyflow.view.mongo.task.CaseReferenceDocument→io.holunda.camunda.taskpool.api.task.CaseReferenceio.holunda.polyflow.view.mongo.task.GenericReferenceDocument→io.holunda.camunda.taskpool.api.task.GenericReferenceio.holunda.polyflow.view.mongo.task.ProcessReferenceDocument→io.holunda.camunda.taskpool.api.task.ProcessReferenceio.holunda.polyflow.view.mongo.task.ReferenceDocumentKt→io.holunda.camunda.taskpool.api.task.SourceReference
- Direction
- polyflow.view.mongo.task uses camunda.taskpool.api.task, so a change to camunda.taskpool.api.task can break polyflow.view.mongo.task, while a change to polyflow.view.mongo.task can't break camunda.taskpool.api.task.
- Position
- Below the diagonal: polyflow.view.mongo.task uses a module listed above it, which is the healthy direction.
34→11 polyflow.view.mongo.task uses polyflow.view.filter✕
- Connections
- 2 pairs of types, where a type in polyflow.view.mongo.task uses a type in polyflow.view.filter.
- The types involved
io.holunda.polyflow.view.mongo.task.TaskWithDataEntriesRepositoryExtension→io.holunda.polyflow.view.filter.Criterionio.holunda.polyflow.view.mongo.task.TaskWithDataEntriesRepositoryExtensionImpl→io.holunda.polyflow.view.filter.Criterion
- Direction
- polyflow.view.mongo.task uses polyflow.view.filter, so a change to polyflow.view.filter can break polyflow.view.mongo.task, while a change to polyflow.view.mongo.task can't break polyflow.view.filter.
- Position
- Below the diagonal: polyflow.view.mongo.task uses a module listed above it, which is the healthy direction.
34→14 polyflow.view.mongo.task uses polyflow.view.query.task✕
- Connections
- 3 pairs of types, where a type in polyflow.view.mongo.task uses a type in polyflow.view.query.task.
- The types involved
io.holunda.polyflow.view.mongo.task.TaskChangeTracker→io.holunda.polyflow.view.query.task.ApplicationWithTaskCountio.holunda.polyflow.view.mongo.task.TaskCountByApplicationRepositoryExtension→io.holunda.polyflow.view.query.task.ApplicationWithTaskCountio.holunda.polyflow.view.mongo.task.TaskRepositoryExtensionImpl→io.holunda.polyflow.view.query.task.ApplicationWithTaskCount
- Direction
- polyflow.view.mongo.task uses polyflow.view.query.task, so a change to polyflow.view.query.task can break polyflow.view.mongo.task, while a change to polyflow.view.mongo.task can't break polyflow.view.query.task.
- Position
- Below the diagonal: polyflow.view.mongo.task uses a module listed above it, which is the healthy direction.
34→26 polyflow.view.mongo.task uses polyflow.view✕
- Connections
- 4 pairs of types, where a type in polyflow.view.mongo.task uses a type in polyflow.view.
- The types involved
io.holunda.polyflow.view.mongo.task.TaskChangeTracker→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.mongo.task.TaskChangeTracker→io.holunda.polyflow.view.TaskWithDataEntriesio.holunda.polyflow.view.mongo.task.TaskDocumentKt→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.mongo.task.TaskWithDataEntriesDocumentKt→io.holunda.polyflow.view.Task
- Direction
- polyflow.view.mongo.task uses polyflow.view, so a change to polyflow.view can break polyflow.view.mongo.task, while a change to polyflow.view.mongo.task can't break polyflow.view.
- Position
- Below the diagonal: polyflow.view.mongo.task uses a module listed above it, which is the healthy direction.
34→30 polyflow.view.mongo.task uses polyflow.view.mongo.data✕
- Connections
- 2 pairs of types, where a type in polyflow.view.mongo.task uses a type in polyflow.view.mongo.data.
- The types involved
io.holunda.polyflow.view.mongo.task.TaskChangeTracker→io.holunda.polyflow.view.mongo.data.DataEntryRepositoryio.holunda.polyflow.view.mongo.task.TaskWithDataEntriesDocument→io.holunda.polyflow.view.mongo.data.DataEntryDocument
- Direction
- polyflow.view.mongo.task uses polyflow.view.mongo.data, so a change to polyflow.view.mongo.data can break polyflow.view.mongo.task, while a change to polyflow.view.mongo.task can't break polyflow.view.mongo.data.
- Position
- Below the diagonal: polyflow.view.mongo.task uses a module listed above it, which is the healthy direction.
34→37 polyflow.view.mongo.task uses polyflow.view.mongo part of a loop✕
- Connections
- 1 pair of types, where a type in polyflow.view.mongo.task uses a type in polyflow.view.mongo.
- The types involved
io.holunda.polyflow.view.mongo.task.TaskChangeTracker→io.holunda.polyflow.view.mongo.TaskPoolMongoViewProperties
- Direction
- polyflow.view.mongo.task uses polyflow.view.mongo, so a change to polyflow.view.mongo can break polyflow.view.mongo.task, while a change to polyflow.view.mongo.task can't break polyflow.view.mongo.
- 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.
35→7 polyflow.taskpool.collector.task uses camunda.taskpool.api.task✕
- Connections
- 9 pairs of types, where a type in polyflow.taskpool.collector.task uses a type in camunda.taskpool.api.task.
- The types involved
io.holunda.polyflow.taskpool.collector.task.TaskAssigner→io.holunda.camunda.taskpool.api.task.EngineTaskCommandio.holunda.polyflow.taskpool.collector.task.TaskCollectorConfiguration→io.holunda.camunda.taskpool.api.task.EngineTaskCommandFilterio.holunda.polyflow.taskpool.collector.task.TaskCommandProcessor→io.holunda.camunda.taskpool.api.task.EngineTaskCommandio.holunda.polyflow.taskpool.collector.task.TaskEventCollectorService→io.holunda.camunda.taskpool.api.task.CompleteTaskCommandio.holunda.polyflow.taskpool.collector.task.TaskEventCollectorService→io.holunda.camunda.taskpool.api.task.CreateTaskCommandio.holunda.polyflow.taskpool.collector.task.TaskEventCollectorService→io.holunda.camunda.taskpool.api.task.DeleteTaskCommandio.holunda.polyflow.taskpool.collector.task.TaskEventCollectorService→io.holunda.camunda.taskpool.api.task.UpdateAttributeTaskCommandio.holunda.polyflow.taskpool.collector.task.TaskEventCollectorService→io.holunda.camunda.taskpool.api.task.UpdateAttributesHistoricTaskCommandio.holunda.polyflow.taskpool.collector.task.TaskServiceCollectorService→io.holunda.camunda.taskpool.api.task.EngineTaskCommandFilter
- Direction
- polyflow.taskpool.collector.task uses camunda.taskpool.api.task, so a change to camunda.taskpool.api.task can break polyflow.taskpool.collector.task, while a change to polyflow.taskpool.collector.task can't break camunda.taskpool.api.task.
- Position
- Below the diagonal: polyflow.taskpool.collector.task uses a module listed above it, which is the healthy direction.
35→9 polyflow.taskpool.collector.task uses polyflow.taskpool.collector.task.enricher✕
- Connections
- 2 pairs of types, where a type in polyflow.taskpool.collector.task uses a type in polyflow.taskpool.collector.task.enricher.
- The types involved
io.holunda.polyflow.taskpool.collector.task.TaskCollectorConfiguration→io.holunda.polyflow.taskpool.collector.task.enricher.ProcessVariablesCorrelatorio.holunda.polyflow.taskpool.collector.task.TaskCollectorConfiguration→io.holunda.polyflow.taskpool.collector.task.enricher.ProcessVariablesFilter
- Direction
- polyflow.taskpool.collector.task uses polyflow.taskpool.collector.task.enricher, so a change to polyflow.taskpool.collector.task.enricher can break polyflow.taskpool.collector.task, while a change to polyflow.taskpool.collector.task can't break polyflow.taskpool.collector.task.enricher.
- Position
- Below the diagonal: polyflow.taskpool.collector.task uses a module listed above it, which is the healthy direction.
35→32 polyflow.taskpool.collector.task uses polyflow.taskpool.sender.task✕
- Connections
- 2 pairs of types, where a type in polyflow.taskpool.collector.task uses a type in polyflow.taskpool.sender.task.
- The types involved
io.holunda.polyflow.taskpool.collector.task.TaskCollectorConfiguration→io.holunda.polyflow.taskpool.sender.task.EngineTaskCommandSenderio.holunda.polyflow.taskpool.collector.task.TaskCommandProcessor→io.holunda.polyflow.taskpool.sender.task.EngineTaskCommandSender
- Direction
- polyflow.taskpool.collector.task uses polyflow.taskpool.sender.task, so a change to polyflow.taskpool.sender.task can break polyflow.taskpool.collector.task, while a change to polyflow.taskpool.collector.task can't break polyflow.taskpool.sender.task.
- Position
- Below the diagonal: polyflow.taskpool.collector.task uses a module listed above it, which is the healthy direction.
35→38 polyflow.taskpool.collector.task uses polyflow.taskpool.collector.task.assigner part of a loop✕
- Connections
- 1 pair of types, where a type in polyflow.taskpool.collector.task uses a type in polyflow.taskpool.collector.task.assigner.
- The types involved
io.holunda.polyflow.taskpool.collector.task.TaskCollectorConfiguration→io.holunda.polyflow.taskpool.collector.task.assigner.ProcessVariableChangeAssigningService
- Direction
- polyflow.taskpool.collector.task uses polyflow.taskpool.collector.task.assigner, so a change to polyflow.taskpool.collector.task.assigner can break polyflow.taskpool.collector.task, while a change to polyflow.taskpool.collector.task can't break polyflow.taskpool.collector.task.assigner.
- 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.
35→39 polyflow.taskpool.collector.task uses polyflow.taskpool.collector part of a loop✕
- Connections
- 3 pairs of types, where a type in polyflow.taskpool.collector.task uses a type in polyflow.taskpool.collector.
- The types involved
io.holunda.polyflow.taskpool.collector.task.TaskCollectorConfiguration→io.holunda.polyflow.taskpool.collector.CamundaTaskpoolCollectorPropertiesio.holunda.polyflow.taskpool.collector.task.TaskEventCollectorService→io.holunda.polyflow.taskpool.collector.CamundaTaskpoolCollectorPropertiesio.holunda.polyflow.taskpool.collector.task.TaskServiceCollectorService→io.holunda.polyflow.taskpool.collector.CamundaTaskpoolCollectorProperties
- Direction
- polyflow.taskpool.collector.task uses polyflow.taskpool.collector, so a change to polyflow.taskpool.collector can break polyflow.taskpool.collector.task, while a change to polyflow.taskpool.collector.task can't break polyflow.taskpool.collector.
- 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.
36→1 polyflow.view.jpa uses camunda.taskpool.api.business✕
- Connections
- 4 pairs of types, where a type in polyflow.view.jpa uses a type in camunda.taskpool.api.business.
- The types involved
io.holunda.polyflow.view.jpa.JpaPolyflowViewDataEntryService→io.holunda.camunda.taskpool.api.business.DataEntryAnonymizedEventio.holunda.polyflow.view.jpa.JpaPolyflowViewDataEntryService→io.holunda.camunda.taskpool.api.business.DataEntryCreatedEventio.holunda.polyflow.view.jpa.JpaPolyflowViewDataEntryService→io.holunda.camunda.taskpool.api.business.DataEntryDeletedEventio.holunda.polyflow.view.jpa.JpaPolyflowViewDataEntryService→io.holunda.camunda.taskpool.api.business.DataEntryUpdatedEvent
- Direction
- polyflow.view.jpa uses camunda.taskpool.api.business, so a change to camunda.taskpool.api.business can break polyflow.view.jpa, while a change to polyflow.view.jpa can't break camunda.taskpool.api.business.
- Position
- Below the diagonal: polyflow.view.jpa uses a module listed above it, which is the healthy direction.
36→3 polyflow.view.jpa uses camunda.variable.serializer✕
- Connections
- 1 pair of types, where a type in polyflow.view.jpa uses a type in camunda.variable.serializer.
- The types involved
io.holunda.polyflow.view.jpa.PolyflowJpaViewProperties→io.holunda.camunda.variable.serializer.FilterType
- Direction
- polyflow.view.jpa uses camunda.variable.serializer, so a change to camunda.variable.serializer can break polyflow.view.jpa, while a change to polyflow.view.jpa can't break camunda.variable.serializer.
- Position
- Below the diagonal: polyflow.view.jpa uses a module listed above it, which is the healthy direction.
36→6 polyflow.view.jpa uses polyflow.view.query✕
- Connections
- 2 pairs of types, where a type in polyflow.view.jpa uses a type in polyflow.view.query.
- The types involved
io.holunda.polyflow.view.jpa.JpaPolyflowViewDataEntryService→io.holunda.polyflow.view.query.PageableSortableQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.PageableSortableQuery
- Direction
- polyflow.view.jpa uses polyflow.view.query, so a change to polyflow.view.query can break polyflow.view.jpa, while a change to polyflow.view.jpa can't break polyflow.view.query.
- Position
- Below the diagonal: polyflow.view.jpa uses a module listed above it, which is the healthy direction.
36→7 polyflow.view.jpa uses camunda.taskpool.api.task✕
- Connections
- 7 pairs of types, where a type in polyflow.view.jpa uses a type in camunda.taskpool.api.task.
- The types involved
io.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.camunda.taskpool.api.task.TaskAssignedEngineEventio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.camunda.taskpool.api.task.TaskAttributeUpdatedEngineEventio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.camunda.taskpool.api.task.TaskCandidateGroupChangedio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.camunda.taskpool.api.task.TaskCandidateUserChangedio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.camunda.taskpool.api.task.TaskCompletedEngineEventio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.camunda.taskpool.api.task.TaskCreatedEngineEventio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.camunda.taskpool.api.task.TaskDeletedEngineEvent
- Direction
- polyflow.view.jpa uses camunda.taskpool.api.task, so a change to camunda.taskpool.api.task can break polyflow.view.jpa, while a change to polyflow.view.jpa can't break camunda.taskpool.api.task.
- Position
- Below the diagonal: polyflow.view.jpa uses a module listed above it, which is the healthy direction.
36→12 polyflow.view.jpa uses polyflow.view.query.process✕
- Connections
- 5 pairs of types, where a type in polyflow.view.jpa uses a type in polyflow.view.query.process.
- The types involved
io.holunda.polyflow.view.jpa.JpaPolyflowViewProcessDefinitionService→io.holunda.polyflow.view.query.process.ProcessDefinitionApiio.holunda.polyflow.view.jpa.JpaPolyflowViewProcessDefinitionService→io.holunda.polyflow.view.query.process.ProcessDefinitionsStartableByUserQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewProcessInstanceService→io.holunda.polyflow.view.query.process.ProcessInstanceApiio.holunda.polyflow.view.jpa.JpaPolyflowViewProcessInstanceService→io.holunda.polyflow.view.query.process.ProcessInstanceQueryResultio.holunda.polyflow.view.jpa.JpaPolyflowViewProcessInstanceService→io.holunda.polyflow.view.query.process.ProcessInstancesByStateQuery
- Direction
- polyflow.view.jpa uses polyflow.view.query.process, so a change to polyflow.view.query.process can break polyflow.view.jpa, while a change to polyflow.view.jpa can't break polyflow.view.query.process.
- Position
- Below the diagonal: polyflow.view.jpa uses a module listed above it, which is the healthy direction.
36→14 polyflow.view.jpa uses polyflow.view.query.task✕
- Connections
- 19 pairs of types, where a type in polyflow.view.jpa uses a type in polyflow.view.query.task.
- The types involved
io.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.AllTasksQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.AllTasksWithDataEntriesQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.ApplicationWithTaskCountio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.TaskApiio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.TaskAttributeNamesQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.TaskAttributeNamesQueryResultio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.TaskAttributeValuesQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.TaskAttributeValuesQueryResultio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.TaskCountByApplicationQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.TaskForIdQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.TaskQueryResultio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.TaskWithDataEntriesForIdQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.TasksForApplicationQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.TasksForCandidateUserAndGroupQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.TasksForGroupQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.TasksForUserQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.TasksWithDataEntriesForGroupQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.TasksWithDataEntriesForUserQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.query.task.TasksWithDataEntriesQueryResult
- Direction
- polyflow.view.jpa uses polyflow.view.query.task, so a change to polyflow.view.query.task can break polyflow.view.jpa, while a change to polyflow.view.jpa can't break polyflow.view.query.task.
- Position
- Below the diagonal: polyflow.view.jpa uses a module listed above it, which is the healthy direction.
36→15 polyflow.view.jpa uses camunda.taskpool.api.process.definition✕
- Connections
- 4 pairs of types, where a type in polyflow.view.jpa uses a type in camunda.taskpool.api.process.definition.
- The types involved
io.holunda.polyflow.view.jpa.JpaPolyflowViewProcessDefinitionService→io.holunda.camunda.taskpool.api.process.definition.ProcessDefinitionActivatedEventio.holunda.polyflow.view.jpa.JpaPolyflowViewProcessDefinitionService→io.holunda.camunda.taskpool.api.process.definition.ProcessDefinitionRegisteredEventio.holunda.polyflow.view.jpa.JpaPolyflowViewProcessDefinitionService→io.holunda.camunda.taskpool.api.process.definition.ProcessDefinitionSuspendedEventio.holunda.polyflow.view.jpa.JpaPolyflowViewProcessDefinitionService→io.holunda.camunda.taskpool.api.process.definition.ProcessDefinitionUnregisteredEvent
- Direction
- polyflow.view.jpa uses camunda.taskpool.api.process.definition, so a change to camunda.taskpool.api.process.definition can break polyflow.view.jpa, while a change to polyflow.view.jpa can't break camunda.taskpool.api.process.definition.
- Position
- Below the diagonal: polyflow.view.jpa uses a module listed above it, which is the healthy direction.
36→16 polyflow.view.jpa uses camunda.taskpool.api.process.instance✕
- Connections
- 5 pairs of types, where a type in polyflow.view.jpa uses a type in camunda.taskpool.api.process.instance.
- The types involved
io.holunda.polyflow.view.jpa.JpaPolyflowViewProcessInstanceService→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceCancelledEventio.holunda.polyflow.view.jpa.JpaPolyflowViewProcessInstanceService→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceEndedEventio.holunda.polyflow.view.jpa.JpaPolyflowViewProcessInstanceService→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceResumedEventio.holunda.polyflow.view.jpa.JpaPolyflowViewProcessInstanceService→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceStartedEventio.holunda.polyflow.view.jpa.JpaPolyflowViewProcessInstanceService→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceSuspendedEvent
- Direction
- polyflow.view.jpa uses camunda.taskpool.api.process.instance, so a change to camunda.taskpool.api.process.instance can break polyflow.view.jpa, while a change to polyflow.view.jpa can't break camunda.taskpool.api.process.instance.
- Position
- Below the diagonal: polyflow.view.jpa uses a module listed above it, which is the healthy direction.
36→20 polyflow.view.jpa uses polyflow.view.query.data✕
- Connections
- 6 pairs of types, where a type in polyflow.view.jpa uses a type in polyflow.view.query.data.
- The types involved
io.holunda.polyflow.view.jpa.JpaPolyflowViewDataEntryService→io.holunda.polyflow.view.query.data.DataEntriesForDataEntryTypeQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewDataEntryService→io.holunda.polyflow.view.query.data.DataEntriesForUserQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewDataEntryService→io.holunda.polyflow.view.query.data.DataEntriesQueryio.holunda.polyflow.view.jpa.JpaPolyflowViewDataEntryService→io.holunda.polyflow.view.query.data.DataEntriesQueryResultio.holunda.polyflow.view.jpa.JpaPolyflowViewDataEntryService→io.holunda.polyflow.view.query.data.DataEntryApiio.holunda.polyflow.view.jpa.JpaPolyflowViewDataEntryService→io.holunda.polyflow.view.query.data.DataEntryForIdentityQuery
- Direction
- polyflow.view.jpa uses polyflow.view.query.data, so a change to polyflow.view.query.data can break polyflow.view.jpa, while a change to polyflow.view.jpa can't break polyflow.view.query.data.
- Position
- Below the diagonal: polyflow.view.jpa uses a module listed above it, which is the healthy direction.
36→26 polyflow.view.jpa uses polyflow.view✕
- Connections
- 5 pairs of types, where a type in polyflow.view.jpa uses a type in polyflow.view.
- The types involved
io.holunda.polyflow.view.jpa.JpaPolyflowViewDataEntryService→io.holunda.polyflow.view.DataEntryio.holunda.polyflow.view.jpa.JpaPolyflowViewProcessDefinitionService→io.holunda.polyflow.view.ProcessDefinitionio.holunda.polyflow.view.jpa.JpaPolyflowViewProcessDefinitionService→io.holunda.polyflow.view.ProcessDefinitionStateio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.TaskWithDataEntries
- Direction
- polyflow.view.jpa uses polyflow.view, so a change to polyflow.view can break polyflow.view.jpa, while a change to polyflow.view.jpa can't break polyflow.view.
- Position
- Below the diagonal: polyflow.view.jpa uses a module listed above it, which is the healthy direction.
36→28 polyflow.view.jpa uses polyflow.view.jpa.data✕
- Connections
- 5 pairs of types, where a type in polyflow.view.jpa uses a type in polyflow.view.jpa.data.
- The types involved
io.holunda.polyflow.view.jpa.JpaPolyflowViewDataEntryService→io.holunda.polyflow.view.jpa.data.DataEntryEntityio.holunda.polyflow.view.jpa.JpaPolyflowViewDataEntryService→io.holunda.polyflow.view.jpa.data.DataEntryEventHandlerio.holunda.polyflow.view.jpa.JpaPolyflowViewDataEntryService→io.holunda.polyflow.view.jpa.data.DataEntryRepositoryio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.jpa.data.DataEntryRepositoryio.holunda.polyflow.view.jpa.SpecificationExtKt→io.holunda.polyflow.view.jpa.data.DataEntryEntity
- Direction
- polyflow.view.jpa uses polyflow.view.jpa.data, so a change to polyflow.view.jpa.data can break polyflow.view.jpa, while a change to polyflow.view.jpa can't break polyflow.view.jpa.data.
- Position
- Below the diagonal: polyflow.view.jpa uses a module listed above it, which is the healthy direction.
36→29 polyflow.view.jpa uses polyflow.view.jpa.process✕
- Connections
- 4 pairs of types, where a type in polyflow.view.jpa uses a type in polyflow.view.jpa.process.
- The types involved
io.holunda.polyflow.view.jpa.JpaPolyflowViewProcessDefinitionService→io.holunda.polyflow.view.jpa.process.ProcessDefinitionEntityio.holunda.polyflow.view.jpa.JpaPolyflowViewProcessDefinitionService→io.holunda.polyflow.view.jpa.process.ProcessDefinitionRepositoryio.holunda.polyflow.view.jpa.JpaPolyflowViewProcessInstanceService→io.holunda.polyflow.view.jpa.process.ProcessInstanceEntityio.holunda.polyflow.view.jpa.JpaPolyflowViewProcessInstanceService→io.holunda.polyflow.view.jpa.process.ProcessInstanceRepository
- Direction
- polyflow.view.jpa uses polyflow.view.jpa.process, so a change to polyflow.view.jpa.process can break polyflow.view.jpa, while a change to polyflow.view.jpa can't break polyflow.view.jpa.process.
- Position
- Below the diagonal: polyflow.view.jpa uses a module listed above it, which is the healthy direction.
36→33 polyflow.view.jpa uses polyflow.view.jpa.task✕
- Connections
- 3 pairs of types, where a type in polyflow.view.jpa uses a type in polyflow.view.jpa.task.
- The types involved
io.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.jpa.task.TaskEntityio.holunda.polyflow.view.jpa.JpaPolyflowViewTaskService→io.holunda.polyflow.view.jpa.task.TaskRepositoryio.holunda.polyflow.view.jpa.SpecificationExtKt→io.holunda.polyflow.view.jpa.task.TaskEntity
- Direction
- polyflow.view.jpa uses polyflow.view.jpa.task, so a change to polyflow.view.jpa.task can break polyflow.view.jpa, while a change to polyflow.view.jpa can't break polyflow.view.jpa.task.
- Position
- Below the diagonal: polyflow.view.jpa uses a module listed above it, which is the healthy direction.
37→1 polyflow.view.mongo uses camunda.taskpool.api.business✕
- Connections
- 5 pairs of types, where a type in polyflow.view.mongo uses a type in camunda.taskpool.api.business.
- The types involved
io.holunda.polyflow.view.mongo.MongoViewService→io.holunda.camunda.taskpool.api.business.DataEntryAnonymizedEventio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.camunda.taskpool.api.business.DataEntryCreatedEventio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.camunda.taskpool.api.business.DataEntryDeletedEventio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.camunda.taskpool.api.business.DataEntryUpdatedEventio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.camunda.taskpool.api.business.DataIdentity
- Direction
- polyflow.view.mongo uses camunda.taskpool.api.business, so a change to camunda.taskpool.api.business can break polyflow.view.mongo, while a change to polyflow.view.mongo can't break camunda.taskpool.api.business.
- Position
- Below the diagonal: polyflow.view.mongo uses a module listed above it, which is the healthy direction.
37→7 polyflow.view.mongo uses camunda.taskpool.api.task✕
- Connections
- 7 pairs of types, where a type in polyflow.view.mongo uses a type in camunda.taskpool.api.task.
- The types involved
io.holunda.polyflow.view.mongo.MongoViewService→io.holunda.camunda.taskpool.api.task.TaskAssignedEngineEventio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.camunda.taskpool.api.task.TaskAttributeUpdatedEngineEventio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.camunda.taskpool.api.task.TaskCandidateGroupChangedio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.camunda.taskpool.api.task.TaskCandidateUserChangedio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.camunda.taskpool.api.task.TaskCompletedEngineEventio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.camunda.taskpool.api.task.TaskCreatedEngineEventio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.camunda.taskpool.api.task.TaskDeletedEngineEvent
- Direction
- polyflow.view.mongo uses camunda.taskpool.api.task, so a change to camunda.taskpool.api.task can break polyflow.view.mongo, while a change to polyflow.view.mongo can't break camunda.taskpool.api.task.
- Position
- Below the diagonal: polyflow.view.mongo uses a module listed above it, which is the healthy direction.
37→14 polyflow.view.mongo uses polyflow.view.query.task✕
- Connections
- 10 pairs of types, where a type in polyflow.view.mongo uses a type in polyflow.view.query.task.
- The types involved
io.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.query.task.ApplicationWithTaskCountio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.query.task.ReactiveTaskApiio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.query.task.TaskCountByApplicationQueryio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.query.task.TaskForIdQueryio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.query.task.TaskQueryResultio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.query.task.TaskWithDataEntriesForIdQueryio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.query.task.TasksForApplicationQueryio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.query.task.TasksForUserQueryio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.query.task.TasksWithDataEntriesForUserQueryio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.query.task.TasksWithDataEntriesQueryResult
- Direction
- polyflow.view.mongo uses polyflow.view.query.task, so a change to polyflow.view.query.task can break polyflow.view.mongo, while a change to polyflow.view.mongo can't break polyflow.view.query.task.
- Position
- Below the diagonal: polyflow.view.mongo uses a module listed above it, which is the healthy direction.
37→20 polyflow.view.mongo uses polyflow.view.query.data✕
- Connections
- 6 pairs of types, where a type in polyflow.view.mongo uses a type in polyflow.view.query.data.
- The types involved
io.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.query.data.DataEntriesForDataEntryTypeQueryio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.query.data.DataEntriesForUserQueryio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.query.data.DataEntriesQueryio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.query.data.DataEntriesQueryResultio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.query.data.DataEntryForIdentityQueryio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.query.data.ReactiveDataEntryApi
- Direction
- polyflow.view.mongo uses polyflow.view.query.data, so a change to polyflow.view.query.data can break polyflow.view.mongo, while a change to polyflow.view.mongo can't break polyflow.view.query.data.
- Position
- Below the diagonal: polyflow.view.mongo uses a module listed above it, which is the healthy direction.
37→26 polyflow.view.mongo uses polyflow.view✕
- Connections
- 4 pairs of types, where a type in polyflow.view.mongo uses a type in polyflow.view.
- The types involved
io.holunda.polyflow.view.mongo.ConvertersKt→io.holunda.polyflow.view.TaskWithDataEntriesio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.DataEntryio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.Taskio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.TaskWithDataEntries
- Direction
- polyflow.view.mongo uses polyflow.view, so a change to polyflow.view can break polyflow.view.mongo, while a change to polyflow.view.mongo can't break polyflow.view.
- Position
- Below the diagonal: polyflow.view.mongo uses a module listed above it, which is the healthy direction.
37→30 polyflow.view.mongo uses polyflow.view.mongo.data✕
- Connections
- 5 pairs of types, where a type in polyflow.view.mongo uses a type in polyflow.view.mongo.data.
- The types involved
io.holunda.polyflow.view.mongo.ConvertersKt→io.holunda.polyflow.view.mongo.data.DataEntryDocumentio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.mongo.data.DataEntryChangeTrackerio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.mongo.data.DataEntryRepositoryio.holunda.polyflow.view.mongo.MongoViewServiceConfiguration→io.holunda.polyflow.view.mongo.data.DataEntryChangeTrackerio.holunda.polyflow.view.mongo.MongoViewServiceConfiguration→io.holunda.polyflow.view.mongo.data.DataEntryRepository
- Direction
- polyflow.view.mongo uses polyflow.view.mongo.data, so a change to polyflow.view.mongo.data can break polyflow.view.mongo, while a change to polyflow.view.mongo can't break polyflow.view.mongo.data.
- Position
- Below the diagonal: polyflow.view.mongo uses a module listed above it, which is the healthy direction.
37→34 polyflow.view.mongo uses polyflow.view.mongo.task✕
- Connections
- 6 pairs of types, where a type in polyflow.view.mongo uses a type in polyflow.view.mongo.task.
- The types involved
io.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.mongo.task.TaskChangeTrackerio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.mongo.task.TaskRepositoryio.holunda.polyflow.view.mongo.MongoViewService→io.holunda.polyflow.view.mongo.task.TaskWithDataEntriesRepositoryio.holunda.polyflow.view.mongo.MongoViewServiceConfiguration→io.holunda.polyflow.view.mongo.task.TaskChangeTrackerio.holunda.polyflow.view.mongo.MongoViewServiceConfiguration→io.holunda.polyflow.view.mongo.task.TaskRepositoryio.holunda.polyflow.view.mongo.MongoViewServiceConfiguration→io.holunda.polyflow.view.mongo.task.TaskWithDataEntriesRepository
- Direction
- polyflow.view.mongo uses polyflow.view.mongo.task, so a change to polyflow.view.mongo.task can break polyflow.view.mongo, while a change to polyflow.view.mongo can't break polyflow.view.mongo.task.
- Position
- Below the diagonal: polyflow.view.mongo uses a module listed above it, which is the healthy direction.
38→7 polyflow.taskpool.collector.task.assigner uses camunda.taskpool.api.task✕
- Connections
- 4 pairs of types, where a type in polyflow.taskpool.collector.task.assigner uses a type in camunda.taskpool.api.task.
- The types involved
io.holunda.polyflow.taskpool.collector.task.assigner.EmptyTaskAssigner→io.holunda.camunda.taskpool.api.task.EngineTaskCommandio.holunda.polyflow.taskpool.collector.task.assigner.ProcessVariableChangeAssigningService→io.holunda.camunda.taskpool.api.task.EngineTaskCommandio.holunda.polyflow.taskpool.collector.task.assigner.ProcessVariableChangeAssigningService→io.holunda.camunda.taskpool.api.task.SourceReferenceio.holunda.polyflow.taskpool.collector.task.assigner.ProcessVariablesTaskAssigner→io.holunda.camunda.taskpool.api.task.EngineTaskCommand
- Direction
- polyflow.taskpool.collector.task.assigner uses camunda.taskpool.api.task, so a change to camunda.taskpool.api.task can break polyflow.taskpool.collector.task.assigner, while a change to polyflow.taskpool.collector.task.assigner can't break camunda.taskpool.api.task.
- Position
- Below the diagonal: polyflow.taskpool.collector.task.assigner uses a module listed above it, which is the healthy direction.
38→25 polyflow.taskpool.collector.task.assigner uses polyflow.taskpool.sender.process.variable✕
- Connections
- 2 pairs of types, where a type in polyflow.taskpool.collector.task.assigner uses a type in polyflow.taskpool.sender.process.variable.
- The types involved
io.holunda.polyflow.taskpool.collector.task.assigner.ProcessVariableChangeAssigningService→io.holunda.polyflow.taskpool.sender.process.variable.CreateSingleProcessVariableCommandio.holunda.polyflow.taskpool.collector.task.assigner.ProcessVariableChangeAssigningService→io.holunda.polyflow.taskpool.sender.process.variable.UpdateSingleProcessVariableCommand
- Direction
- polyflow.taskpool.collector.task.assigner uses polyflow.taskpool.sender.process.variable, so a change to polyflow.taskpool.sender.process.variable can break polyflow.taskpool.collector.task.assigner, while a change to polyflow.taskpool.collector.task.assigner can't break polyflow.taskpool.sender.process.variable.
- Position
- Below the diagonal: polyflow.taskpool.collector.task.assigner uses a module listed above it, which is the healthy direction.
38→35 polyflow.taskpool.collector.task.assigner uses polyflow.taskpool.collector.task✕
- Connections
- 3 pairs of types, where a type in polyflow.taskpool.collector.task.assigner uses a type in polyflow.taskpool.collector.task.
- The types involved
io.holunda.polyflow.taskpool.collector.task.assigner.EmptyTaskAssigner→io.holunda.polyflow.taskpool.collector.task.TaskAssignerio.holunda.polyflow.taskpool.collector.task.assigner.ProcessVariablesTaskAssigner→io.holunda.polyflow.taskpool.collector.task.TaskAssignerio.holunda.polyflow.taskpool.collector.task.assigner.ProcessVariablesTaskAssigner→io.holunda.polyflow.taskpool.collector.task.TaskVariableLoader
- Direction
- polyflow.taskpool.collector.task.assigner uses polyflow.taskpool.collector.task, so a change to polyflow.taskpool.collector.task can break polyflow.taskpool.collector.task.assigner, while a change to polyflow.taskpool.collector.task.assigner can't break polyflow.taskpool.collector.task.
- Position
- Below the diagonal: polyflow.taskpool.collector.task.assigner uses a module listed above it, which is the healthy direction.
39→9 polyflow.taskpool.collector uses polyflow.taskpool.collector.task.enricher✕
- Connections
- 8 pairs of types, where a type in polyflow.taskpool.collector uses a type in polyflow.taskpool.collector.task.enricher.
- The types involved
io.holunda.polyflow.taskpool.collector.FallbackProcessVariablesCorrelatorConfiguration→io.holunda.polyflow.taskpool.collector.task.enricher.ProcessVariablesCorrelatorio.holunda.polyflow.taskpool.collector.FallbackProcessVariablesFilterConfiguration→io.holunda.polyflow.taskpool.collector.task.enricher.ProcessVariablesFilterio.holunda.polyflow.taskpool.collector.ProcessVariableFilterProperties→io.holunda.polyflow.taskpool.collector.task.enricher.FilterTypeio.holunda.polyflow.taskpool.collector.ProcessVariableFilterProperties→io.holunda.polyflow.taskpool.collector.task.enricher.VariableFilterio.holunda.polyflow.taskpool.collector.ProcessVariablesCorrelatorConfiguration→io.holunda.polyflow.taskpool.collector.task.enricher.ProcessVariablesCorrelatorio.holunda.polyflow.taskpool.collector.ProcessVariablesCorrelatorProperties→io.holunda.polyflow.taskpool.collector.task.enricher.ProcessVariableCorrelationio.holunda.polyflow.taskpool.collector.ProcessVariablesFilterConfiguration→io.holunda.polyflow.taskpool.collector.task.enricher.ProcessVariablesFilterio.holunda.polyflow.taskpool.collector.ProcessVariablesFilterProperties→io.holunda.polyflow.taskpool.collector.task.enricher.VariableFilter
- Direction
- polyflow.taskpool.collector uses polyflow.taskpool.collector.task.enricher, so a change to polyflow.taskpool.collector.task.enricher can break polyflow.taskpool.collector, while a change to polyflow.taskpool.collector can't break polyflow.taskpool.collector.task.enricher.
- Position
- Below the diagonal: polyflow.taskpool.collector uses a module listed above it, which is the healthy direction.
39→38 polyflow.taskpool.collector uses polyflow.taskpool.collector.task.assigner✕
- Connections
- 1 pair of types, where a type in polyflow.taskpool.collector uses a type in polyflow.taskpool.collector.task.assigner.
- The types involved
io.holunda.polyflow.taskpool.collector.TaskAssignerProperties→io.holunda.polyflow.taskpool.collector.task.assigner.ProcessVariableTaskAssignerMapping
- Direction
- polyflow.taskpool.collector uses polyflow.taskpool.collector.task.assigner, so a change to polyflow.taskpool.collector.task.assigner can break polyflow.taskpool.collector, while a change to polyflow.taskpool.collector can't break polyflow.taskpool.collector.task.assigner.
- Position
- Below the diagonal: polyflow.taskpool.collector uses a module listed above it, which is the healthy direction.
40→9 polyflow.taskpool.collector.process.instance uses polyflow.taskpool.collector.task.enricher✕
- Connections
- 4 pairs of types, where a type in polyflow.taskpool.collector.process.instance uses a type in polyflow.taskpool.collector.task.enricher.
- The types involved
io.holunda.polyflow.taskpool.collector.process.instance.ProcessInstanceCollectorConfiguration→io.holunda.polyflow.taskpool.collector.task.enricher.ProcessVariablesCorrelatorio.holunda.polyflow.taskpool.collector.process.instance.ProcessInstanceCollectorConfiguration→io.holunda.polyflow.taskpool.collector.task.enricher.ProcessVariablesFilterio.holunda.polyflow.taskpool.collector.process.instance.ProcessVariablesProcessInstanceCommandEnricher→io.holunda.polyflow.taskpool.collector.task.enricher.ProcessVariablesCorrelatorio.holunda.polyflow.taskpool.collector.process.instance.ProcessVariablesProcessInstanceCommandEnricher→io.holunda.polyflow.taskpool.collector.task.enricher.ProcessVariablesFilter
- Direction
- polyflow.taskpool.collector.process.instance uses polyflow.taskpool.collector.task.enricher, so a change to polyflow.taskpool.collector.task.enricher can break polyflow.taskpool.collector.process.instance, while a change to polyflow.taskpool.collector.process.instance can't break polyflow.taskpool.collector.task.enricher.
- Position
- Below the diagonal: polyflow.taskpool.collector.process.instance uses a module listed above it, which is the healthy direction.
40→16 polyflow.taskpool.collector.process.instance uses camunda.taskpool.api.process.instance✕
- Connections
- 4 pairs of types, where a type in polyflow.taskpool.collector.process.instance uses a type in camunda.taskpool.api.process.instance.
- The types involved
io.holunda.polyflow.taskpool.collector.process.instance.ProcessInstanceEventCollectorService→io.holunda.camunda.taskpool.api.process.instance.EndProcessInstanceCommandio.holunda.polyflow.taskpool.collector.process.instance.ProcessInstanceEventCollectorService→io.holunda.camunda.taskpool.api.process.instance.StartProcessInstanceCommandio.holunda.polyflow.taskpool.collector.process.instance.ProcessInstanceEventCollectorService→io.holunda.camunda.taskpool.api.process.instance.UpdateProcessInstanceCommandio.holunda.polyflow.taskpool.collector.process.instance.ProcessInstanceProcessor→io.holunda.camunda.taskpool.api.process.instance.ProcessInstanceCommand
- Direction
- polyflow.taskpool.collector.process.instance uses camunda.taskpool.api.process.instance, so a change to camunda.taskpool.api.process.instance can break polyflow.taskpool.collector.process.instance, while a change to polyflow.taskpool.collector.process.instance can't break camunda.taskpool.api.process.instance.
- Position
- Below the diagonal: polyflow.taskpool.collector.process.instance uses a module listed above it, which is the healthy direction.
40→24 polyflow.taskpool.collector.process.instance uses polyflow.taskpool.sender.process.instance✕
- Connections
- 2 pairs of types, where a type in polyflow.taskpool.collector.process.instance uses a type in polyflow.taskpool.sender.process.instance.
- The types involved
io.holunda.polyflow.taskpool.collector.process.instance.ProcessInstanceCollectorConfiguration→io.holunda.polyflow.taskpool.sender.process.instance.ProcessInstanceCommandSenderio.holunda.polyflow.taskpool.collector.process.instance.ProcessInstanceProcessor→io.holunda.polyflow.taskpool.sender.process.instance.ProcessInstanceCommandSender
- Direction
- polyflow.taskpool.collector.process.instance uses polyflow.taskpool.sender.process.instance, so a change to polyflow.taskpool.sender.process.instance can break polyflow.taskpool.collector.process.instance, while a change to polyflow.taskpool.collector.process.instance can't break polyflow.taskpool.sender.process.instance.
- Position
- Below the diagonal: polyflow.taskpool.collector.process.instance uses a module listed above it, which is the healthy direction.
40→39 polyflow.taskpool.collector.process.instance uses polyflow.taskpool.collector✕
- Connections
- 2 pairs of types, where a type in polyflow.taskpool.collector.process.instance uses a type in polyflow.taskpool.collector.
- The types involved
io.holunda.polyflow.taskpool.collector.process.instance.ProcessInstanceCollectorConfiguration→io.holunda.polyflow.taskpool.collector.CamundaTaskpoolCollectorPropertiesio.holunda.polyflow.taskpool.collector.process.instance.ProcessInstanceEventCollectorService→io.holunda.polyflow.taskpool.collector.CamundaTaskpoolCollectorProperties
- Direction
- polyflow.taskpool.collector.process.instance uses polyflow.taskpool.collector, so a change to polyflow.taskpool.collector can break polyflow.taskpool.collector.process.instance, while a change to polyflow.taskpool.collector.process.instance can't break polyflow.taskpool.collector.
- Position
- Below the diagonal: polyflow.taskpool.collector.process.instance uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event Sourcing
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 29 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 11 | High / Critical |
| A02:2025 — Security Misconfiguration | 1 | Medium |
Roadmap
Top priorities: Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs; Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters); Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs. | +5.0 pts | Medium | Strongly-typed ids |
| Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters). | +4.7 pts | Medium | Encapsulated state |
| Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. | +2.2 pts | Low | Vulnerability-disclosure Policy |
| Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure. | +1.8 pts | Medium | Constructible invalid state |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. | +0.9 pts | Low | Static Analysis (SAST) |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). | +0.7 pts | Low | Dependency Vulnerabilities |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.7 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.5 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| view/mongo/src/main/kotlin/io/holunda/polyflow/view/mongo/MongoViewService.kt | 6.0 | Mixed | Explicit Debt: FixmeComment |
| view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/JpaPolyflowViewTaskService.kt | 6.0 | Mixed | Explicit Debt: FixmeComment |
| integration/camunda-bpm/taskpool-collector/src/main/kotlin/io/holunda/polyflow/taskpool/collector/task/TaskEventCollectorService.kt | 6.3 | Mixed | Cyclomatic Complexity: TaskEventCollectorService.update (cyclomatic 17) |
| integration/common/variable-serializer/src/main/kotlin/VariableSerializer.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| integration/common/taskpool-sender/src/main/kotlin/io/holunda/polyflow/taskpool/sender/task/accumulator/ProjectingCommandAccumulator.kt | 6.7 | Mixed | Explicit Debt: FixmeComment |
| view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/SpecificationExt.kt | 7.2 | Mixed | Cyclomatic Complexity: SpecificationExtKt.toTaskSpecification (cyclomatic 23) |
| view/simple/src/main/kotlin/io/holunda/polyflow/view/simple/service/SimpleTaskPoolService.kt | 7.2 | Mixed | God Classes: TooManyMethods: SimpleTaskPoolService |
| view/mongo/src/main/kotlin/io/holunda/polyflow/view/mongo/Converters.kt | 7.2 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| view/mongo/src/test/kotlin/io/holunda/polyflow/view/mongo/service/PolyflowMongoServiceTestBase.kt | 7.3 | Mixed | Explicit Debt: TodoComment |
| view/mongo/src/main/kotlin/io/holunda/polyflow/view/mongo/task/TaskWithDataEntriesRepositoryExtensionImpl.kt | 7.3 | Mixed | Explicit Debt: FixmeComment |
| core/taskpool/taskpool-event/src/main/kotlin/io/holunda/camunda/taskpool/upcast/AnnotationBasedSingleEventUpcaster.kt | 7.3 | 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 65 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 65 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, 118 of 131 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ 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 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 (.kt), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.kt), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — a Maven build resolved 31 artifact(s) (13 behind a shipped release, reported), but the build resolved only part of the graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- 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 a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (28 contributor(s) across 2600 commit(s) sampled, automation and bot accounts excluded). One of them holds 81% of the history; the other 27 hold 0.7% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (REDACTED), but 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.
- 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `core/taskpool/taskpool-core/src/main/kotlin/io/holunda/polyflow/taskpool/core/process/ProcessDefinitionRegisterCommandHandler.kt`, `core/taskpool/taskpool-core/src/main/kotlin/io/holunda/polyflow/taskpool/core/process/ProcessInstanceAggregate.kt`, `view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/PolyflowJpaViewConfiguration.kt`, `view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/process/ProcessDefinitionEntity.kt`, `view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/task/TaskEntity.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 84 commits in the last 90 days, yet 97 of 105 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
- 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.
- DM8 Value-object opportunities — 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 finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — 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. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- ED5 Idempotency — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- ES3 PII in the event store — 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 finds persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- GD1 Unfinished & placeholder code — 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 C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin is not read 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.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin is not read 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.
- S1 Web-Security Posture — 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 web-security 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 web-security controls.
- X24 Document value interpolated into markup unescaped — 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 C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- 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.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SpecificationExtKt.toTaskSpecification at 23.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SpecificationExtKt.toTaskSpecification (cyclomatic 23), SpecificationExtKt.toTaskSpecification (cyclomatic 23), FilterKt.compareOperator (cyclomatic 19). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 9.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was SpecificationExtKt.toTaskSpecification at 17.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with SpecificationExtKt.toTaskSpecification (cognitive 17), SpecificationExtKt.toTaskSpecification (cognitive 17), VariableSerializerKt.toJsonPathWithValue (cognitive 16). — 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 4 together lifts Cognitive Complexity from 9.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 3 TooManyMethods finding(s) in God Classes — start with MongoViewService.kt, BuiltInPublishDelegateParseListener.kt, SimpleTaskPoolService.kt. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
27 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 4 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with TaskEventMappers.kt, Converters.kt, MongoViewService.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with JpaPolyflowViewTaskService.kt, Converters.kt, ProcessDefinitionMongoService.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with DataEntryComparator.kt, TaskComparator.kt. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
24 production modules (Maven), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence, with abstractness counted on 23 of the 24 (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 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
D6 · Cohesion (LCOM4)
2 of 44 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with ProcessInstanceAggregate.kt, TaskEventCollectorService.kt. — One of this dimension's main actionable groups (2 warning-level).
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 2 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 33 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. 250 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), 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.
D17 · Explicit Debt
18 deducted task-comment markers across 19762 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 9 TodoComment finding(s) in Explicit Debt — start with PolyflowMongoServiceTestBase.kt (2), AnnotationBasedSingleEventUpcaster.kt (2), VariableSerializer.kt. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 9 FixmeComment finding(s) in Explicit Debt — start with TaskWithDataEntriesRepositoryExtensionImpl.kt (2), MongoViewService.kt, TaskDocument.kt. — 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. 38 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
0 of 13 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D26 · Project Cohesion
0 of 23 build units (Maven) flagged as possibly oversized/incoherent.
D27 · Navigability
52 % of calls cross a namespace and 10 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
29 finding(s): 0 critical, 27 high, 2 medium, 0 low. 14 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. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- No action in Static Analysis (SAST) — all 14 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (14 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
7 finding(s): 0 critical, 3 high, 4 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (REDACTED) is present but lists no reporting contact.
What to do
- Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-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 38 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
AX1 · Captive dependencies
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
- `SimpleProcessDefinitionService` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (processDefinitions; e.g. `processDefinitions` in `on` at line 37). — view/simple/src/main/kotlin/io/holunda/polyflow/view/simple/service/SimpleProcessDefinitionService.kt:27
- `ProcessDefinitionService` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (processDefinitions; e.g. `processDefinitions` in `getProcessDefinitions` at line 33). — integration/camunda-bpm/taskpool-collector/src/main/kotlin/io/holunda/polyflow/taskpool/collector/process/definition/ProcessDefinitionService.kt:19
What to do
- Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
AX3 · Project dependency cycles
AX4 · Dependency direction
- `polyflow-datapool-core` is a Domain project but references `polyflow-datapool-api`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
- `polyflow-taskpool-core` is a Domain project but references `polyflow-taskpool-api`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
What to do
- Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
DM1 · Aggregate boundaries
DM11 · Constructible invalid state
- `DataEntryPayloadAttributeEntity`'s public constructor takes `entryType`, `entryId`, `path`, `value` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `DataEntryPayloadAttributeEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/data/DataEntryPayloadAttributeEntity.kt:18
- `TaskAndDataEntryPayloadAttributeEntity`'s public constructor takes `taskId`, `path`, `value` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `TaskAndDataEntryPayloadAttributeEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/task/TaskAndDataEntryPayloadAttributeEntity.kt:16
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM2 · Strongly-typed ids
- `TaskAssignmentUpdatedEngineEvent.taskDefinitionKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core/taskpool/taskpool-event/src/main/kotlin/io/holunda/camunda/taskpool/api/task/TaskEvents.kt:160
- `ProcessDefinitionAggregate.processDefinitionId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core/taskpool/taskpool-core/src/main/kotlin/io/holunda/polyflow/taskpool/core/process/ProcessDefinitionAggregate.kt:26
- `ProcessInstanceAggregate.processInstanceId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — core/taskpool/taskpool-core/src/main/kotlin/io/holunda/polyflow/taskpool/core/process/ProcessInstanceAggregate.kt:24
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM5 · Encapsulated state
- `ProcessDefinitionAggregate` exposes publicly writable state (processDefinitionId). — core/taskpool/taskpool-core/src/main/kotlin/io/holunda/polyflow/taskpool/core/process/ProcessDefinitionAggregate.kt:23
- `ProcessInstanceAggregate` exposes publicly writable state (processInstanceId). — core/taskpool/taskpool-core/src/main/kotlin/io/holunda/polyflow/taskpool/core/process/ProcessInstanceAggregate.kt:21
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
ES1 · Fold determinism
ES2 · Immutable events
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Describe the projects a newcomer cannot place from the root README: 32 of 32 have no README of their own, in their folder or in their family's project (`view`, `bom/datapool-dependencies`, `bom/parent`, `bom/taskpool-dependencies`, `core/bus-jackson` and 27 more).
M2 · Architecture documentation
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
- 675/682 types (99%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Kotlin: `internal`) so internals can change without breaking consumers.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `pip`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `pip` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P8 · Schema migrations
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — view/view-api/src/main/kotlin/sort/DataEntryComparator.kt:28, view/view-api/src/main/kotlin/sort/TaskComparator.kt:26, view/view-api/src/main/kotlin/sort/TasksWithDataEntriesComparator.kt:26
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82% | Strong | Solid. |
| Architecture | 73% | Strong | Solid. |
| Maturity | 85% | Strong | Solid. |
| Readiness | 68% | Adequate | Acceptable, with room to improve. |
| Security | 55% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 52% | Adequate — gated by DM2, DM5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D11 Test Reliability — 1 observation(s) recorded · This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.kt), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- P12 CI test-gate honesty — 2 observation(s) recorded · 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.
- X10 Duplicated predicate — 4 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 — 64 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- 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
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- 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 Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) 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 Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) 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 Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~14581 lines of test source are present (.kt) 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.
- D12 Dependency Hygiene — Not scored — a Maven build resolved 31 artifact(s) (13 behind a shipped release, reported), but the build resolved only part of the graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Kotlin not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (polyflow), which is a layered codebase, not two contexts. 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 — this repository's production source is .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — None of 13 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 5 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (20 event handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 20 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES3 PII in the event store — This check finds persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — 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
- M4 Documentation accuracy — Not applicable: the 38 current-state document(s) make no claim of a kind M4 checks. 17 claim(s) of kinds M4 does not check were not checked (path 2, environment variable 13, setting 2); M4 checks only links and versions and artefact counts.
- P2 Observability — This repository's JVM source (23 module(s), 336 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a 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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security 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 web-security 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.
- X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
- X24 Document value interpolated into markup unescaped — 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
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 33 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
- Dependency-rule violation: polyflow-datapool-core (Domain) → polyflow-datapool-api (Web)
- Dependency-rule violation: polyflow-taskpool-core (Domain) → polyflow-taskpool-api (Web)
- REDACTED
- REDACTED
- Test declared unreliable: integration/camunda-bpm/taskpool-collector/src/test/kotlin/io/holunda/polyflow/taskpool/itest/txjob/TaskTxJobSenderITest.kt integration/camunda-bpm/taskpool-collector/src/test/kotlin/io/holunda/polyflow/taskpool/itest/txjob/TaskTxJobSenderITest.kt:45
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 84 finding(s)
- TodoComment view/mongo/src/test/kotlin/io/holunda/polyflow/view/mongo/service/PolyflowMongoServiceTestBase.kt:160
- TodoComment view/mongo/src/test/kotlin/io/holunda/polyflow/view/mongo/service/PolyflowMongoServiceTestBase.kt:190
- TodoComment integration/common/variable-serializer/src/main/kotlin/VariableSerializer.kt:112
- TodoComment integration/common/taskpool-sender/src/main/kotlin/io/holunda/polyflow/taskpool/sender/task/accumulator/projectProperties.kt:83
- TodoComment integration/camunda-bpm/taskpool-collector/src/main/kotlin/io/holunda/polyflow/taskpool/collector/process/variable/ProcessVariableProcessor.kt:31
- TodoComment core/taskpool/taskpool-event/src/test/kotlin/io/holunda/camunda/taskpool/upcast/TaskEventSourceReferenceUpcasterTest.kt:25
- TodoComment core/taskpool/taskpool-event/src/main/kotlin/io/holunda/camunda/taskpool/upcast/AnnotationBasedSingleEventUpcaster.kt:19
- TodoComment core/taskpool/taskpool-event/src/main/kotlin/io/holunda/camunda/taskpool/upcast/AnnotationBasedSingleEventUpcaster.kt:47
- TodoComment core/taskpool/taskpool-core/src/main/kotlin/io/holunda/polyflow/taskpool/core/task/TaskAggregateEngineTaskCommandFilter.kt:33
- FixmeComment view/mongo/src/main/kotlin/io/holunda/polyflow/view/mongo/MongoViewService.kt:275
- FixmeComment view/mongo/src/main/kotlin/io/holunda/polyflow/view/mongo/task/TaskDocument.kt:78
- FixmeComment view/mongo/src/main/kotlin/io/holunda/polyflow/view/mongo/task/TaskWithDataEntriesRepositoryExtensionImpl.kt:66
- FixmeComment view/mongo/src/main/kotlin/io/holunda/polyflow/view/mongo/task/TaskWithDataEntriesRepositoryExtensionImpl.kt:67
- FixmeComment view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/JpaPolyflowViewTaskService.kt:491
- FixmeComment integration/common/taskpool-sender/src/main/kotlin/io/holunda/polyflow/taskpool/sender/task/accumulator/ProjectingCommandAccumulator.kt:131
- FixmeComment integration/common/taskpool-sender/src/main/kotlin/io/holunda/polyflow/taskpool/sender/task/accumulator/SimpleEngineTaskCommandIntentDetector.kt:60
- FixmeComment integration/common/datapool-sender/src/main/kotlin/io/holunda/polyflow/datapool/sender/AbstractDataEntryCommandSender.kt:14
- FixmeComment core/datapool/datapool-core/src/test/kotlin/io/holunda/polyflow/datapool/core/business/upcaster/DataEntryCreatedEventUpcasterTest.kt:44
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) core/taskpool/taskpool-event/src/main/kotlin/io/holunda/camunda/taskpool/mapper/task/TaskEventMappers.kt:13
- Members sharing a duplicated core (4 members, 50+ identical tokens) view/mongo/src/main/kotlin/io/holunda/polyflow/view/mongo/Converters.kt:112
- Members sharing a duplicated core (4 members, 50+ identical tokens) view/mongo/src/main/kotlin/io/holunda/polyflow/view/mongo/MongoViewService.kt:307
- Members sharing a duplicated core (4 members, 50+ identical tokens) view/simple/src/main/kotlin/io/holunda/polyflow/view/simple/service/SimpleTaskPoolService.kt:281
- Duplicated block (11 lines × 2) view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/JpaPolyflowViewTaskService.kt:91
- Duplicated block (11 lines × 2) view/mongo/src/main/kotlin/io/holunda/polyflow/view/mongo/Converters.kt:19
- Duplicated block (11 lines × 2) view/mongo/src/main/kotlin/io/holunda/polyflow/view/mongo/process/ProcessDefinitionMongoService.kt:40
- Duplicated block (11 lines × 2) view/view-api/src/main/kotlin/query/task/TaskAttributeValuesQuery.kt:20
- TooManyMethods: MongoViewService view/mongo/src/main/kotlin/io/holunda/polyflow/view/mongo/MongoViewService.kt:84
- TooManyMethods: BuiltInPublishDelegateParseListener integration/camunda-bpm/taskpool-collector/src/main/kotlin/io/holunda/polyflow/taskpool/collector/task/BuiltInPublishDelegateParseListener.kt:19
- TooManyMethods: SimpleTaskPoolService view/simple/src/main/kotlin/io/holunda/polyflow/view/simple/service/SimpleTaskPoolService.kt:33
- Off the main sequence: polyflow-spring-utils
- Off the main sequence: polyflow-variable-serializer
- Off the main sequence: polyflow-datapool-api
- Swallowed exception (caught, then discarded) view/view-api/src/main/kotlin/sort/DataEntryComparator.kt:28
- Swallowed exception (caught, then discarded) view/view-api/src/main/kotlin/sort/TaskComparator.kt:26
- Swallowed exception (caught, then discarded) view/view-api/src/main/kotlin/sort/TasksWithDataEntriesComparator.kt:26
- Stateful singleton: SimpleProcessDefinitionService view/simple/src/main/kotlin/io/holunda/polyflow/view/simple/service/SimpleProcessDefinitionService.kt:27
- Stateful singleton: ProcessDefinitionService integration/camunda-bpm/taskpool-collector/src/main/kotlin/io/holunda/polyflow/taskpool/collector/process/definition/ProcessDefinitionService.kt:19
- SpecificationExtKt.toTaskSpecification (cyclomatic 23) view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/SpecificationExt.kt:64
- SpecificationExtKt.toTaskSpecification (cyclomatic 23) view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/SpecificationExt.kt:237
- SpecificationExtKt.toTaskSpecification (cognitive 17) view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/SpecificationExt.kt:64
- SpecificationExtKt.toTaskSpecification (cognitive 17) view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/SpecificationExt.kt:237
- Duplicated block (8 lines × 2) view/view-api/src/main/kotlin/sort/DataEntryComparator.kt:17
- Duplicated block (8 lines × 2) view/view-api/src/main/kotlin/sort/TaskComparator.kt:22
- Low cohesion: ProcessInstanceAggregate (LCOM4 6) core/taskpool/taskpool-core/src/main/kotlin/io/holunda/polyflow/taskpool/core/process/ProcessInstanceAggregate.kt:21
- Low cohesion: TaskEventCollectorService (LCOM4 4) integration/camunda-bpm/taskpool-collector/src/main/kotlin/io/holunda/polyflow/taskpool/collector/task/TaskEventCollectorService.kt:21
- Constructible in an invalid state: DataEntryPayloadAttributeEntity view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/data/DataEntryPayloadAttributeEntity.kt:18
- Constructible in an invalid state: TaskAndDataEntryPayloadAttributeEntity view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/task/TaskAndDataEntryPayloadAttributeEntity.kt:16
- Mutable entity: ProcessDefinitionAggregate core/taskpool/taskpool-core/src/main/kotlin/io/holunda/polyflow/taskpool/core/process/ProcessDefinitionAggregate.kt:23
- Mutable entity: ProcessInstanceAggregate core/taskpool/taskpool-core/src/main/kotlin/io/holunda/polyflow/taskpool/core/process/ProcessInstanceAggregate.kt:21
- FilterKt.compareOperator (cyclomatic 19) view/view-api/src/main/kotlin/filter/Filter.kt:34
- TaskEventCollectorService.update (cyclomatic 17) integration/camunda-bpm/taskpool-collector/src/main/kotlin/io/holunda/polyflow/taskpool/collector/task/TaskEventCollectorService.kt:155
- VariableSerializerKt.toJsonPathWithValue (cognitive 16) integration/common/variable-serializer/src/main/kotlin/VariableSerializer.kt:58
- TaskEventCollectorService.update (cognitive 16) integration/camunda-bpm/taskpool-collector/src/main/kotlin/io/holunda/polyflow/taskpool/collector/task/TaskEventCollectorService.kt:155
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (27 lines × 2) integration/camunda-bpm/taskpool-collector/src/main/kotlin/io/holunda/polyflow/taskpool/collector/task/assigner/ProcessVariableChangeAssigningService.kt:30
- Duplicated block (21 lines × 2) integration/camunda-bpm/taskpool-collector/src/main/kotlin/io/holunda/polyflow/taskpool/HistoricProcessInstanceEventExtensions.kt:17
- Duplicated block (14–20 lines × 2) integration/camunda-bpm/taskpool-collector/src/main/kotlin/io/holunda/polyflow/taskpool/collector/task/TaskServiceCollectorService.kt:38
- Duplicated block (18–20 lines × 2) view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/JpaPolyflowViewTaskService.kt:199
- Duplicated block (16–17 lines × 3) core/taskpool/taskpool-event/src/main/kotlin/io/holunda/camunda/taskpool/mapper/task/TaskEventMappers.kt:14
- Duplicated block (14–15 lines × 3) view/simple/src/main/kotlin/io/holunda/polyflow/view/simple/service/SimpleTaskPoolService.kt:108
- Duplicated block (15 lines × 2) integration/common/datapool-sender/src/main/kotlin/io/holunda/polyflow/datapool/sender/gateway/AxonCommandListGateway.kt:24
- Duplicated block (14 lines × 2) view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/data/DataEntryRepository.kt:109
- Duplicated block (13–14 lines × 2) view/mongo/src/main/kotlin/io/holunda/polyflow/view/mongo/Converters.kt:114
- Duplicated block (13 lines × 2) view/simple/src/main/kotlin/io/holunda/polyflow/view/simple/service/Converters.kt:20
- Duplicated block (11–13 lines × 2) view/simple/src/main/kotlin/io/holunda/polyflow/view/simple/service/SimpleDataEntryService.kt:98
- Duplicated block (12 lines × 4) core/taskpool/taskpool-event/src/main/kotlin/io/holunda/camunda/taskpool/mapper/task/TaskEventMappers.kt:14
- Duplicated block (11–12 lines × 4) view/mongo/src/main/kotlin/io/holunda/polyflow/view/mongo/Converters.kt:118
- Duplicated block (10 lines × 2) view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/JpaPolyflowViewDataEntryService.kt:113
- Duplicated block (9 lines × 2) core/datapool/datapool-event/src/main/kotlin/io/holunda/camunda/taskpool/api/business/Mappers.kt:7
- Duplicated block (8–9 lines × 2) integration/camunda-bpm/taskpool-collector/src/main/kotlin/io/holunda/polyflow/taskpool/collector/process/instance/ProcessInstanceEventCollectorService.kt:89
- Duplicated block (7 lines × 2) integration/common/taskpool-sender/src/main/kotlin/io/holunda/polyflow/taskpool/sender/task/accumulator/ProjectingCommandAccumulator.kt:68
- Duplicated block (6 lines × 3) view/view-api/src/main/kotlin/sort/DataEntryComparator.kt:23
- Duplicated block (5 lines × 2) view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/data/ConverterExt.kt:82
- Duplicated block (10 lines × 4) view/mongo/src/main/kotlin/io/holunda/polyflow/view/mongo/MongoViewService.kt:308
- Duplicated block (6 lines × 4) view/simple/src/main/kotlin/io/holunda/polyflow/view/simple/service/SimpleTaskPoolService.kt:282
- Coverage collected but not gated
- Test suite runs only after the merge
Minor — 14 finding(s)
- Duplicated predicate integration/camunda-bpm/taskpool-collector/src/main/kotlin/io/holunda/polyflow/taskpool/TaskEntityExtensions.kt:39
- Duplicated predicate view/mongo/src/main/kotlin/io/holunda/polyflow/view/mongo/Converters.kt:93
- Duplicated predicate integration/common/taskpool-sender/src/main/kotlin/io/holunda/polyflow/taskpool/sender/process/variable/SimpleProcessVariableCommandSender.kt:25
- Duplicated predicate integration/camunda-bpm/taskpool-job-sender/src/main/kotlin/io/holunda/polyflow/taskpool/sender/TxAwareAccumulatingCamundaJobEngineTaskCommandSender.kt:38
- Primitive id on a domain type: TaskAssignmentUpdatedEngineEvent.taskDefinitionKey core/taskpool/taskpool-event/src/main/kotlin/io/holunda/camunda/taskpool/api/task/TaskEvents.kt:160
- Primitive id on a domain type: ProcessDefinitionAggregate.processDefinitionId core/taskpool/taskpool-core/src/main/kotlin/io/holunda/polyflow/taskpool/core/process/ProcessDefinitionAggregate.kt:26
- Primitive id on a domain type: ProcessInstanceAggregate.processInstanceId core/taskpool/taskpool-core/src/main/kotlin/io/holunda/polyflow/taskpool/core/process/ProcessInstanceAggregate.kt:24
- Documentation: no build, run or usage example README.md:1
- REDACTED
- REDACTED
- REDACTED
- Large public API surface
- Dependabot does not watch pip REDACTED:2
- No changelog
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-45a3b51dbedf4b378d20bcc48d8739bf/history.json --exit-code 0 --source . | 0 | 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-45a3b51dbedf4b378d20bcc48d8739bf/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 . | 29 | 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 . | 7 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 5 file(s) — `core/taskpool/taskpool-core/src/main/kotlin/io/holunda/polyflow/taskpool/core/process/ProcessDefinitionRegisterCommandHandler.kt`, `core/taskpool/taskpool-core/src/main/kotlin/io/holunda/polyflow/taskpool/core/process/ProcessInstanceAggregate.kt`, `view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/PolyflowJpaViewConfiguration.kt`, `view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/process/ProcessDefinitionEntity.kt`, `view/jpa/src/main/kotlin/io/holunda/polyflow/view/jpa/task/TaskEntity.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |