Executive summary
apache/openwhisk falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 41 out of 100 and is rated Weak, and 77 of its 82 critical findings are security problems.
Code Health, at 35, is the weakest lens and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 3 points. Adding type checking would lift Code Health itself, also worth about 3. Raising Code Health to 70 would lift the score to about 45.
Twenty-one settings leave the servers or containers unsafe. Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and three passwords or keys in the code's history and two in the code are open to anyone who can read the repository. Correcting the unsafe settings, pinning each tool to an exact version and replacing each exposed password or key would close these risks. Correcting the flagged pipeline settings would fix the 40 weaknesses in the build pipeline's configuration, and fixing the weaknesses the scanner points to would deal with the three security weaknesses in the code. The three form fields without a label need a label.
The product code is 48,374 lines, about €96,000 to rebuild.
If Code Health rose from 35 to 70, the lowest score rated Strong, the score would rise from 41 to about 45.
New since the last survey: 8 findings
- Code Duplication · Edited copy of a member (40 corresponding lines) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerPool.scala
- Code Duplication · Edited copy of a member (38 corresponding lines) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerPool.scala
- Code Duplication · Edited copy of a member (20 corresponding lines) core/invoker/src/main/scala/org/apache/openwhisk/core/invoker/InvokerReactive.scala
- Code Duplication · Edited copy of a member (16 corresponding lines) core/controller/src/main/scala/org/apache/openwhisk/core/loadBalancer/InvokerSupervision.scala
- Code Duplication · Edited copy of a member (30 corresponding lines) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/kubernetes/KubernetesClient.scala
- Code Duplication · Edited copy of a member (16 corresponding lines) common/scala/src/main/scala/org/apache/openwhisk/http/PoolingRestClient.scala
- Code Duplication · Edited copy of a member (24 corresponding lines) core/controller/src/main/scala/org/apache/openwhisk/core/loadBalancer/CommonLoadBalancer.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) REDACTED
Fixed since the last survey: 3 findings
- Cognitive Complexity · wskutil.request (cognitive 22) tools/admin/wskutil.py
- Cognitive Complexity · replicateDbs.replicateDatabases (cognitive 16) tools/db/replicateDbs.py
- Code Coverage · Coverage not measured — no coverage collector is wired up
Rebuild cost: about €96,000 · Estimate
| Cost to rebuild | €32,000 to €160,000, for 534 to 1,693 hours of work, about 0.7 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 41. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 48,374 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 spi | 2 core.entity.Attachments | 3 http | 4 core.database | 5 core.entity.ExecManifest | 6 core.scheduler | 7 core.containerpool | 8 core.loadBalancer | 9 core.entitlement | 10 core.entity | 11 core | 12 core.entity.ActivationId | 13 core.etcd | 14 core.connector | 15 common | 16 connector.kafka | 17 connector.lean | 18 core.ack | 19 core.containerpool.logging | 20 core.containerpool.v2 | 21 core.controller.actions | 22 core.database.azblob | 23 core.database.cosmosdb | 24 core.database.elasticsearch | 25 core.database.memory | 26 core.database.mongodb | 27 core.database.s3 | 28 core.invoker.Invoker | 29 core.scheduler.message | 30 core.scheduler.queue | 31 core.yarn | 32 core.containerpool.docker | 33 core.controller | 34 core.invoker | 35 core.monitoring.metrics | 36 core.scheduler.container | 37 core.scheduler.grpc | 38 core.containerpool.kubernetes | 39 core.controller.RestAPIVersion | 40 standalone |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 spi | ||||||||||||||||||||||||||||||||||||||||
| 2 core.entity.Attachments | 4 | |||||||||||||||||||||||||||||||||||||||
| 3 http | 5 | 3 | ||||||||||||||||||||||||||||||||||||||
| 4 core.database | 3 | 3 | 1 | 30 | 1 | 28 | ||||||||||||||||||||||||||||||||||
| 5 core.entity.ExecManifest | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 6 core.scheduler | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 7 core.containerpool | 1 | 1 | 1 | 35 | 2 | 1 | 9 | |||||||||||||||||||||||||||||||||
| 8 core.loadBalancer | 1 | 2 | 1 | 46 | 1 | 17 | 22 | |||||||||||||||||||||||||||||||||
| 9 core.entitlement | 1 | 3 | 14 | 3 | 9 | |||||||||||||||||||||||||||||||||||
| 10 core.entity | 5 | 4 | 8 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||
| 11 core | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 core.entity.ActivationId | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 core.etcd | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 core.connector | 1 | 34 | 1 | 10 | ||||||||||||||||||||||||||||||||||||
| 15 common | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 connector.kafka | 1 | 1 | 7 | 2 | ||||||||||||||||||||||||||||||||||||
| 17 connector.lean | 1 | 1 | 7 | 1 | ||||||||||||||||||||||||||||||||||||
| 18 core.ack | 9 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 19 core.containerpool.logging | 1 | 1 | 4 | 3 | 20 | 3 | ||||||||||||||||||||||||||||||||||
| 20 core.containerpool.v2 | 1 | 12 | 32 | 7 | 9 | |||||||||||||||||||||||||||||||||||
| 21 core.controller.actions | 3 | 22 | 5 | |||||||||||||||||||||||||||||||||||||
| 22 core.database.azblob | 4 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 23 core.database.cosmosdb | 1 | 10 | 4 | 8 | ||||||||||||||||||||||||||||||||||||
| 24 core.database.elasticsearch | 6 | 4 | 3 | |||||||||||||||||||||||||||||||||||||
| 25 core.database.memory | 1 | 17 | 8 | 8 | ||||||||||||||||||||||||||||||||||||
| 26 core.database.mongodb | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 core.database.s3 | 4 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 28 core.invoker.Invoker | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 core.scheduler.message | 19 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 core.scheduler.queue | 1 | 23 | 2 | 13 | 6 | 1 | ||||||||||||||||||||||||||||||||||
| 31 core.yarn | 1 | 7 | 3 | 2 | 6 | |||||||||||||||||||||||||||||||||||
| 32 core.containerpool.docker | 1 | 26 | 10 | 5 | 17 | 3 | ||||||||||||||||||||||||||||||||||
| 33 core.controller | 1 | 2 | 9 | 2 | 13 | 46 | 4 | 2 | 23 | 1 | ||||||||||||||||||||||||||||||
| 34 core.invoker | 2 | 3 | 4 | 11 | 3 | 3 | 10 | 2 | 1 | |||||||||||||||||||||||||||||||
| 35 core.monitoring.metrics | 8 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 core.scheduler.container | 9 | 6 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 37 core.scheduler.grpc | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 core.containerpool.kubernetes | 1 | 4 | 8 | 2 | 9 | 1 | ||||||||||||||||||||||||||||||||||
| 39 core.controller.RestAPIVersion | 8 | 5 | 7 | 2 | 6 | 5 | 6 | 1 | 14 | |||||||||||||||||||||||||||||||
| 40 standalone | 2 | 2 | 2 | 1 | 1 | 7 | 3 |
2→10 core.entity.Attachments uses core.entity part of a loop✕
- Connections
- 4 pairs of types, where a type in core.entity.Attachments uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.entity.Attachments.OptionSizeAttachment→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.entity.Attachments.OptionSizeAttachment→org.apache.openwhisk.core.entity.SizeConversionorg.apache.openwhisk.core.entity.Attachments.SizeAttachment→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.entity.Attachments.SizeAttachment→org.apache.openwhisk.core.entity.SizeConversion
- Direction
- core.entity.Attachments uses core.entity, so a change to core.entity can break core.entity.Attachments, while a change to core.entity.Attachments can't break core.entity.
- 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.
3→10 http uses core.entity part of a loop✕
- Connections
- 5 pairs of types, where a type in http uses a type in core.entity.
- The types involved
org.apache.openwhisk.http.Messages→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.http.Messages→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.http.Messages→org.apache.openwhisk.core.entity.Execorg.apache.openwhisk.http.Messages→org.apache.openwhisk.core.entity.ExecMetaDataBaseorg.apache.openwhisk.http.Messages→org.apache.openwhisk.core.entity.SizeError
- Direction
- http uses core.entity, so a change to core.entity can break http, while a change to http can't break core.entity.
- 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.
3→15 http uses common part of a loop✕
- Connections
- 3 pairs of types, where a type in http uses a type in common.
- The types involved
org.apache.openwhisk.http.BasicHttpService→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.http.BasicRasService→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.http.ErrorResponse→org.apache.openwhisk.common.TransactionId
- Direction
- http uses common, so a change to common can break http, while a change to http can't break common.
- 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.
4→1 core.database uses spi✕
- Connections
- 3 pairs of types, where a type in core.database uses a type in spi.
- The types involved
org.apache.openwhisk.core.database.ActivationStoreProvider→org.apache.openwhisk.spi.Spiorg.apache.openwhisk.core.database.ArtifactStoreProvider→org.apache.openwhisk.spi.Spiorg.apache.openwhisk.core.database.AttachmentStoreProvider→org.apache.openwhisk.spi.Spi
- Direction
- core.database uses spi, so a change to spi can break core.database, while a change to core.database can't break spi.
- Position
- Below the diagonal: core.database uses a module listed above it, which is the healthy direction.
4→2 core.database uses core.entity.Attachments✕
- Connections
- 3 pairs of types, where a type in core.database uses a type in core.entity.Attachments.
- The types involved
org.apache.openwhisk.core.database.ArtifactStore→org.apache.openwhisk.core.entity.Attachments.Attachedorg.apache.openwhisk.core.database.CouchDbRestStore→org.apache.openwhisk.core.entity.Attachments.Attachedorg.apache.openwhisk.core.database.DocumentFactory→org.apache.openwhisk.core.entity.Attachments.Attached
- Direction
- core.database uses core.entity.Attachments, so a change to core.entity.Attachments can break core.database, while a change to core.database can't break core.entity.Attachments.
- Position
- Below the diagonal: core.database uses a module listed above it, which is the healthy direction.
4→3 core.database uses http✕
- Connections
- 1 pair of types, where a type in core.database uses a type in http.
- The types involved
org.apache.openwhisk.core.database.CouchDbRestClient→org.apache.openwhisk.http.PoolingRestClient
- Direction
- core.database uses http, so a change to http can break core.database, while a change to core.database can't break http.
- Position
- Below the diagonal: core.database uses a module listed above it, which is the healthy direction.
4→10 core.database uses core.entity part of a loop✕
- Connections
- 30 pairs of types, where a type in core.database uses a type in core.entity. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.apache.openwhisk.core.database.ActivationFileStorage→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.database.ActivationStore→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.database.ActivationStore→org.apache.openwhisk.core.entity.ActivationResponseorg.apache.openwhisk.core.database.ActivationStore→org.apache.openwhisk.core.entity.DocInfoorg.apache.openwhisk.core.database.ActivationStore→org.apache.openwhisk.core.entity.EntityPathorg.apache.openwhisk.core.database.ActivationStore→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.database.ArtifactActivationStore→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.database.ArtifactActivationStore→org.apache.openwhisk.core.entity.DocInfoorg.apache.openwhisk.core.database.ArtifactActivationStore→org.apache.openwhisk.core.entity.EntityPathorg.apache.openwhisk.core.database.ArtifactActivationStore→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.database.ArtifactStore→org.apache.openwhisk.core.entity.DocInfoorg.apache.openwhisk.core.database.ArtifactStoreProvider→org.apache.openwhisk.core.entity.DocumentReaderorg.apache.openwhisk.core.database.ArtifactWithFileStorageActivationStore→org.apache.openwhisk.core.entity.DocInfoorg.apache.openwhisk.core.database.ArtifactWithFileStorageActivationStore→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.database.AttachmentStore→org.apache.openwhisk.core.entity.DocIdorg.apache.openwhisk.core.database.CacheChangeNotification→org.apache.openwhisk.core.entity.CacheKeyorg.apache.openwhisk.core.database.CacheInvalidationMessage→org.apache.openwhisk.core.entity.CacheKeyorg.apache.openwhisk.core.database.CouchDbRestStore→org.apache.openwhisk.core.entity.DocInfoorg.apache.openwhisk.core.database.CouchDbStoreProvider→org.apache.openwhisk.core.entity.DocumentReaderorg.apache.openwhisk.core.database.DocumentFactory→org.apache.openwhisk.core.entity.DocIdorg.apache.openwhisk.core.database.DocumentFactory→org.apache.openwhisk.core.entity.DocInfoorg.apache.openwhisk.core.database.DocumentFactory→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.database.DocumentProvider→org.apache.openwhisk.core.entity.DocIdorg.apache.openwhisk.core.database.DocumentRevisionProvider→org.apache.openwhisk.core.entity.DocInfoorg.apache.openwhisk.core.database.DocumentRevisionProvider→org.apache.openwhisk.core.entity.DocRevision
- Direction
- core.database uses core.entity, so a change to core.entity can break core.database, while a change to core.database can't break core.entity.
- 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.
4→14 core.database uses core.connector part of a loop✕
- Connections
- 1 pair of types, where a type in core.database uses a type in core.connector.
- The types involved
org.apache.openwhisk.core.database.CacheInvalidationMessage→org.apache.openwhisk.core.connector.Message
- Direction
- core.database uses core.connector, so a change to core.connector can break core.database, while a change to core.database can't break core.connector.
- 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.
4→15 core.database uses common part of a loop✕
- Connections
- 28 pairs of types, where a type in core.database uses a type in common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.apache.openwhisk.core.database.ActivationStore→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.ActivationStore→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.ActivationStoreProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.ArtifactActivationStore→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.ArtifactActivationStore→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.ArtifactActivationStoreProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.ArtifactStore→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.ArtifactStore→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.ArtifactStoreProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.ArtifactWithFileStorageActivationStore→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.ArtifactWithFileStorageActivationStoreProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.AttachmentStore→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.AttachmentStoreProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.CouchDbRestStore→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.CouchDbRestStore→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.CouchDbStoreProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.DocumentFactory→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.DocumentHandler→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.DocumentProvider→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.LimitsCommand→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.LimitsCommand→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.SimpleHandler→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.StoreUtils→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.StoreUtils→org.apache.openwhisk.common.StartMarkerorg.apache.openwhisk.core.database.StoreUtils→org.apache.openwhisk.common.TransactionId
- Direction
- core.database uses common, so a change to common can break core.database, while a change to core.database can't break common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→2 core.entity.ExecManifest uses core.entity.Attachments✕
- Connections
- 1 pair of types, where a type in core.entity.ExecManifest uses a type in core.entity.Attachments.
- The types involved
org.apache.openwhisk.core.entity.ExecManifest.RuntimeManifest→org.apache.openwhisk.core.entity.Attachments.Attached
- Direction
- core.entity.ExecManifest uses core.entity.Attachments, so a change to core.entity.Attachments can break core.entity.ExecManifest, while a change to core.entity.ExecManifest can't break core.entity.Attachments.
- Position
- Below the diagonal: core.entity.ExecManifest uses a module listed above it, which is the healthy direction.
5→10 core.entity.ExecManifest uses core.entity part of a loop✕
- Connections
- 1 pair of types, where a type in core.entity.ExecManifest uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.entity.ExecManifest.StemCell→org.apache.openwhisk.core.entity.ByteSize
- Direction
- core.entity.ExecManifest uses core.entity, so a change to core.entity can break core.entity.ExecManifest, while a change to core.entity.ExecManifest can't break core.entity.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→3 core.scheduler uses http✕
- Connections
- 1 pair of types, where a type in core.scheduler uses a type in http.
- The types involved
org.apache.openwhisk.core.scheduler.FPCSchedulerServer→org.apache.openwhisk.http.BasicRasService
- Direction
- core.scheduler uses http, so a change to http can break core.scheduler, while a change to core.scheduler can't break http.
- Position
- Below the diagonal: core.scheduler uses a module listed above it, which is the healthy direction.
6→10 core.scheduler uses core.entity part of a loop✕
- Connections
- 1 pair of types, where a type in core.scheduler uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.scheduler.SchedulerStates→org.apache.openwhisk.core.entity.SchedulerInstanceId
- Direction
- core.scheduler uses core.entity, so a change to core.entity can break core.scheduler, while a change to core.scheduler can't break core.entity.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→14 core.scheduler uses core.connector part of a loop✕
- Connections
- 2 pairs of types, where a type in core.scheduler uses a type in core.connector.
- The types involved
org.apache.openwhisk.core.scheduler.Scheduler→org.apache.openwhisk.core.connector.StatusDataorg.apache.openwhisk.core.scheduler.SchedulerCore→org.apache.openwhisk.core.connector.StatusData
- Direction
- core.scheduler uses core.connector, so a change to core.connector can break core.scheduler, while a change to core.scheduler can't break core.connector.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→15 core.scheduler uses common part of a loop✕
- Connections
- 2 pairs of types, where a type in core.scheduler uses a type in common.
- The types involved
org.apache.openwhisk.core.scheduler.FPCSchedulerServer→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.scheduler.FPCSchedulerServer→org.apache.openwhisk.common.TransactionId
- Direction
- core.scheduler uses common, so a change to common can break core.scheduler, while a change to core.scheduler can't break common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→1 core.containerpool uses spi✕
- Connections
- 1 pair of types, where a type in core.containerpool uses a type in spi.
- The types involved
org.apache.openwhisk.core.containerpool.ContainerFactoryProvider→org.apache.openwhisk.spi.Spi
- Direction
- core.containerpool uses spi, so a change to spi can break core.containerpool, while a change to core.containerpool can't break spi.
- Position
- Below the diagonal: core.containerpool uses a module listed above it, which is the healthy direction.
7→3 core.containerpool uses http✕
- Connections
- 1 pair of types, where a type in core.containerpool uses a type in http.
- The types involved
org.apache.openwhisk.core.containerpool.PekkoContainerClient→org.apache.openwhisk.http.PoolingRestClient
- Direction
- core.containerpool uses http, so a change to http can break core.containerpool, while a change to core.containerpool can't break http.
- Position
- Below the diagonal: core.containerpool uses a module listed above it, which is the healthy direction.
7→5 core.containerpool uses core.entity.ExecManifest✕
- Connections
- 1 pair of types, where a type in core.containerpool uses a type in core.entity.ExecManifest.
- The types involved
org.apache.openwhisk.core.containerpool.PrewarmingConfig→org.apache.openwhisk.core.entity.ExecManifest.ReactivePrewarmingConfig
- Direction
- core.containerpool uses core.entity.ExecManifest, so a change to core.entity.ExecManifest can break core.containerpool, while a change to core.containerpool can't break core.entity.ExecManifest.
- Position
- Below the diagonal: core.containerpool uses a module listed above it, which is the healthy direction.
7→10 core.containerpool uses core.entity part of a loop✕
- Connections
- 35 pairs of types, where a type in core.containerpool uses a type in core.entity. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.apache.openwhisk.core.containerpool.ActivationError→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.containerpool.ActivationLogReadingError→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.containerpool.ActivationUnsuccessfulError→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.containerpool.ApacheBlockingContainerClient→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.ColdStartKey→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.ContainerClient→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.ContainerData→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.ContainerFactory→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.ContainerFactory→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.containerpool.ContainerFactoryProvider→org.apache.openwhisk.core.entity.InvokerInstanceIdorg.apache.openwhisk.core.containerpool.ContainerInUse→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.containerpool.ContainerNotStarted→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.ContainerPool→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.ContainerPool→org.apache.openwhisk.core.entity.CodeExecorg.apache.openwhisk.core.containerpool.ContainerPool→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.containerpool.ContainerPoolConfig→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.ContainerProxy→org.apache.openwhisk.core.entity.ActivationResponseorg.apache.openwhisk.core.containerpool.ContainerProxy→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.containerpool.ContainerProxy→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.containerpool.ContainerStarted→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.InitializationError→org.apache.openwhisk.core.entity.ActivationResponseorg.apache.openwhisk.core.containerpool.MemoryData→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.PekkoContainerClient→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.PreWarmedData→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.PrewarmingConfig→org.apache.openwhisk.core.entity.ByteSize
- Direction
- core.containerpool uses core.entity, so a change to core.entity can break core.containerpool, while a change to core.containerpool can't break core.entity.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→11 core.containerpool uses core part of a loop✕
- Connections
- 2 pairs of types, where a type in core.containerpool uses a type in core.
- The types involved
org.apache.openwhisk.core.containerpool.ContainerFactory→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.containerpool.ContainerFactoryProvider→org.apache.openwhisk.core.WhiskConfig
- Direction
- core.containerpool uses core, so a change to core can break core.containerpool, while a change to core.containerpool can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→14 core.containerpool uses core.connector part of a loop✕
- Connections
- 1 pair of types, where a type in core.containerpool uses a type in core.connector.
- The types involved
org.apache.openwhisk.core.containerpool.Run→org.apache.openwhisk.core.connector.ActivationMessage
- Direction
- core.containerpool uses core.connector, so a change to core.connector can break core.containerpool, while a change to core.containerpool can't break core.connector.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→15 core.containerpool uses common part of a loop✕
- Connections
- 9 pairs of types, where a type in core.containerpool uses a type in common.
- The types involved
org.apache.openwhisk.core.containerpool.ApacheBlockingContainerClient→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.ContainerClient→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.ContainerFactory→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.containerpool.ContainerFactory→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.ContainerFactoryProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.containerpool.ContainerHealthError→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.ContainerPool→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.containerpool.ContainerProxy→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.PekkoContainerClient→org.apache.openwhisk.common.TransactionId
- Direction
- core.containerpool uses common, so a change to common can break core.containerpool, while a change to core.containerpool can't break common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→1 core.loadBalancer uses spi✕
- Connections
- 1 pair of types, where a type in core.loadBalancer uses a type in spi.
- The types involved
org.apache.openwhisk.core.loadBalancer.LoadBalancerProvider→org.apache.openwhisk.spi.Spi
- Direction
- core.loadBalancer uses spi, so a change to spi can break core.loadBalancer, while a change to core.loadBalancer can't break spi.
- Position
- Below the diagonal: core.loadBalancer uses a module listed above it, which is the healthy direction.
8→6 core.loadBalancer uses core.scheduler✕
- Connections
- 2 pairs of types, where a type in core.loadBalancer uses a type in core.scheduler.
- The types involved
org.apache.openwhisk.core.loadBalancer.FPCPoolBalancer→org.apache.openwhisk.core.scheduler.SchedulerEndpointsorg.apache.openwhisk.core.loadBalancer.FPCPoolBalancer→org.apache.openwhisk.core.scheduler.SchedulerStates
- Direction
- core.loadBalancer uses core.scheduler, so a change to core.scheduler can break core.loadBalancer, while a change to core.loadBalancer can't break core.scheduler.
- Position
- Below the diagonal: core.loadBalancer uses a module listed above it, which is the healthy direction.
8→7 core.loadBalancer uses core.containerpool✕
- Connections
- 1 pair of types, where a type in core.loadBalancer uses a type in core.containerpool.
- The types involved
org.apache.openwhisk.core.loadBalancer.LeanBalancer→org.apache.openwhisk.core.containerpool.ContainerPoolConfig
- Direction
- core.loadBalancer uses core.containerpool, so a change to core.containerpool can break core.loadBalancer, while a change to core.loadBalancer can't break core.containerpool.
- Position
- Below the diagonal: core.loadBalancer uses a module listed above it, which is the healthy direction.
8→10 core.loadBalancer uses core.entity part of a loop✕
- Connections
- 46 pairs of types, where a type in core.loadBalancer uses a type in core.entity. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.apache.openwhisk.core.loadBalancer.ActivationEntry→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.loadBalancer.ActivationEntry→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.loadBalancer.ActivationEntry→org.apache.openwhisk.core.entity.ControllerInstanceIdorg.apache.openwhisk.core.loadBalancer.ActivationEntry→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.loadBalancer.ActivationEntry→org.apache.openwhisk.core.entity.InvokerInstanceIdorg.apache.openwhisk.core.loadBalancer.ActivationEntry→org.apache.openwhisk.core.entity.UUIDorg.apache.openwhisk.core.loadBalancer.ActivationRequest→org.apache.openwhisk.core.entity.InvokerInstanceIdorg.apache.openwhisk.core.loadBalancer.CommonLoadBalancer→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.loadBalancer.CommonLoadBalancer→org.apache.openwhisk.core.entity.ExecutableWhiskActionMetaDataorg.apache.openwhisk.core.loadBalancer.CommonLoadBalancer→org.apache.openwhisk.core.entity.InstanceIdorg.apache.openwhisk.core.loadBalancer.CommonLoadBalancer→org.apache.openwhisk.core.entity.InvokerInstanceIdorg.apache.openwhisk.core.loadBalancer.CommonLoadBalancer→org.apache.openwhisk.core.entity.UUIDorg.apache.openwhisk.core.loadBalancer.CommonLoadBalancer→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.loadBalancer.DistributedActivationEntry→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.loadBalancer.DistributedActivationEntry→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.loadBalancer.DistributedActivationEntry→org.apache.openwhisk.core.entity.ControllerInstanceIdorg.apache.openwhisk.core.loadBalancer.DistributedActivationEntry→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.loadBalancer.DistributedActivationEntry→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.loadBalancer.DistributedActivationEntry→org.apache.openwhisk.core.entity.UUIDorg.apache.openwhisk.core.loadBalancer.FPCPoolBalancer→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.loadBalancer.FPCPoolBalancer→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.loadBalancer.FPCPoolBalancer→org.apache.openwhisk.core.entity.EntityPathorg.apache.openwhisk.core.loadBalancer.FPCPoolBalancer→org.apache.openwhisk.core.entity.ExecutableWhiskActionMetaDataorg.apache.openwhisk.core.loadBalancer.FPCPoolBalancer→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.loadBalancer.FPCPoolBalancer→org.apache.openwhisk.core.entity.SchedulerInstanceId
- Direction
- core.loadBalancer uses core.entity, so a change to core.entity can break core.loadBalancer, while a change to core.loadBalancer can't break core.entity.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→11 core.loadBalancer uses core part of a loop✕
- Connections
- 1 pair of types, where a type in core.loadBalancer uses a type in core.
- The types involved
org.apache.openwhisk.core.loadBalancer.LoadBalancerProvider→org.apache.openwhisk.core.WhiskConfig
- Direction
- core.loadBalancer uses core, so a change to core can break core.loadBalancer, while a change to core.loadBalancer can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→14 core.loadBalancer uses core.connector part of a loop✕
- Connections
- 17 pairs of types, where a type in core.loadBalancer uses a type in core.connector.
- The types involved
org.apache.openwhisk.core.loadBalancer.ActivationRequest→org.apache.openwhisk.core.connector.ActivationMessageorg.apache.openwhisk.core.loadBalancer.CommonLoadBalancer→org.apache.openwhisk.core.connector.ActivationMessageorg.apache.openwhisk.core.loadBalancer.CommonLoadBalancer→org.apache.openwhisk.core.connector.MessageProducerorg.apache.openwhisk.core.loadBalancer.CommonLoadBalancer→org.apache.openwhisk.core.connector.ResultMetadataorg.apache.openwhisk.core.loadBalancer.FPCPoolBalancer→org.apache.openwhisk.core.connector.ActivationMessageorg.apache.openwhisk.core.loadBalancer.FPCPoolBalancer→org.apache.openwhisk.core.connector.MessageProducerorg.apache.openwhisk.core.loadBalancer.FPCPoolBalancer→org.apache.openwhisk.core.connector.MessagingProviderorg.apache.openwhisk.core.loadBalancer.FPCPoolBalancer→org.apache.openwhisk.core.connector.ResultMetadataorg.apache.openwhisk.core.loadBalancer.FeedFactory→org.apache.openwhisk.core.connector.MessagingProviderorg.apache.openwhisk.core.loadBalancer.InvokerActor→org.apache.openwhisk.core.connector.PingMessageorg.apache.openwhisk.core.loadBalancer.InvokerPoolFactory→org.apache.openwhisk.core.connector.MessageProducerorg.apache.openwhisk.core.loadBalancer.InvokerPoolFactory→org.apache.openwhisk.core.connector.MessagingProviderorg.apache.openwhisk.core.loadBalancer.LeanBalancer→org.apache.openwhisk.core.connector.ActivationMessageorg.apache.openwhisk.core.loadBalancer.LeanBalancer→org.apache.openwhisk.core.connector.MessagingProviderorg.apache.openwhisk.core.loadBalancer.LoadBalancer→org.apache.openwhisk.core.connector.ActivationMessageorg.apache.openwhisk.core.loadBalancer.ShardingContainerPoolBalancer→org.apache.openwhisk.core.connector.ActivationMessageorg.apache.openwhisk.core.loadBalancer.ShardingContainerPoolBalancer→org.apache.openwhisk.core.connector.MessagingProvider
- Direction
- core.loadBalancer uses core.connector, so a change to core.connector can break core.loadBalancer, while a change to core.loadBalancer can't break core.connector.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→15 core.loadBalancer uses common part of a loop✕
- Connections
- 22 pairs of types, where a type in core.loadBalancer uses a type in common.
- The types involved
org.apache.openwhisk.core.loadBalancer.CommonLoadBalancer→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.loadBalancer.CurrentInvokerPoolState→org.apache.openwhisk.common.InvokerHealthorg.apache.openwhisk.core.loadBalancer.DistributedActivationEntry→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.loadBalancer.FPCPoolBalancer→org.apache.openwhisk.common.InvokerHealthorg.apache.openwhisk.core.loadBalancer.FPCPoolBalancer→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.loadBalancer.InvokerActor→org.apache.openwhisk.common.InvokerStateorg.apache.openwhisk.core.loadBalancer.InvokerActor→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.loadBalancer.InvokerActor→org.apache.openwhisk.common.RingBufferorg.apache.openwhisk.core.loadBalancer.InvokerActor→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.loadBalancer.InvokerInfo→org.apache.openwhisk.common.RingBufferorg.apache.openwhisk.core.loadBalancer.InvokerPool→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.loadBalancer.InvokerPool→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.loadBalancer.LeanBalancer→org.apache.openwhisk.common.InvokerHealthorg.apache.openwhisk.core.loadBalancer.LeanBalancer→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.loadBalancer.LoadBalancer→org.apache.openwhisk.common.InvokerHealthorg.apache.openwhisk.core.loadBalancer.LoadBalancer→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.loadBalancer.LoadBalancerProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.loadBalancer.ShardingContainerPoolBalancer→org.apache.openwhisk.common.InvokerHealthorg.apache.openwhisk.core.loadBalancer.ShardingContainerPoolBalancer→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.loadBalancer.ShardingContainerPoolBalancerState→org.apache.openwhisk.common.InvokerHealthorg.apache.openwhisk.core.loadBalancer.ShardingContainerPoolBalancerState→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.loadBalancer.ShardingContainerPoolBalancerState→org.apache.openwhisk.common.NestedSemaphore
- Direction
- core.loadBalancer uses common, so a change to common can break core.loadBalancer, while a change to core.loadBalancer can't break common.
- 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→1 core.entitlement uses spi✕
- Connections
- 1 pair of types, where a type in core.entitlement uses a type in spi.
- The types involved
org.apache.openwhisk.core.entitlement.EntitlementSpiProvider→org.apache.openwhisk.spi.Spi
- Direction
- core.entitlement uses spi, so a change to spi can break core.entitlement, while a change to core.entitlement can't break spi.
- Position
- Below the diagonal: core.entitlement uses a module listed above it, which is the healthy direction.
9→8 core.entitlement uses core.loadBalancer✕
- Connections
- 3 pairs of types, where a type in core.entitlement uses a type in core.loadBalancer.
- The types involved
org.apache.openwhisk.core.entitlement.EntitlementSpiProvider→org.apache.openwhisk.core.loadBalancer.LoadBalancerorg.apache.openwhisk.core.entitlement.FPCEntitlementProvider→org.apache.openwhisk.core.loadBalancer.LoadBalancerorg.apache.openwhisk.core.entitlement.LocalEntitlementProvider→org.apache.openwhisk.core.loadBalancer.LoadBalancer
- Direction
- core.entitlement uses core.loadBalancer, so a change to core.loadBalancer can break core.entitlement, while a change to core.entitlement can't break core.loadBalancer.
- Position
- Below the diagonal: core.entitlement uses a module listed above it, which is the healthy direction.
9→10 core.entitlement uses core.entity part of a loop✕
- Connections
- 14 pairs of types, where a type in core.entitlement uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.entitlement.ActionCollection→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.entitlement.ActivationThrottler→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.entitlement.Collection→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.entitlement.EntitlementSpiProvider→org.apache.openwhisk.core.entity.ControllerInstanceIdorg.apache.openwhisk.core.entitlement.FPCEntitlementProvider→org.apache.openwhisk.core.entity.ControllerInstanceIdorg.apache.openwhisk.core.entitlement.FPCEntitlementProvider→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.entitlement.KindRestrictor→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.entitlement.LocalEntitlementProvider→org.apache.openwhisk.core.entity.ControllerInstanceIdorg.apache.openwhisk.core.entitlement.LocalEntitlementProvider→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.entitlement.PackageCollection→org.apache.openwhisk.core.entity.DocIdorg.apache.openwhisk.core.entitlement.PackageCollection→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.entitlement.RateThrottler→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.entitlement.Resource→org.apache.openwhisk.core.entity.EntityPathorg.apache.openwhisk.core.entitlement.Resource→org.apache.openwhisk.core.entity.Parameters
- Direction
- core.entitlement uses core.entity, so a change to core.entity can break core.entitlement, while a change to core.entitlement can't break core.entity.
- 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→11 core.entitlement uses core part of a loop✕
- Connections
- 3 pairs of types, where a type in core.entitlement uses a type in core.
- The types involved
org.apache.openwhisk.core.entitlement.EntitlementSpiProvider→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.entitlement.FPCEntitlementProvider→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.entitlement.LocalEntitlementProvider→org.apache.openwhisk.core.WhiskConfig
- Direction
- core.entitlement uses core, so a change to core can break core.entitlement, while a change to core.entitlement can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→15 core.entitlement uses common part of a loop✕
- Connections
- 9 pairs of types, where a type in core.entitlement uses a type in common.
- The types involved
org.apache.openwhisk.core.entitlement.ActionCollection→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.entitlement.ActivationThrottler→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.entitlement.Collection→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.entitlement.EntitlementSpiProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.entitlement.FPCEntitlementProvider→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.entitlement.KindRestrictor→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.entitlement.LocalEntitlementProvider→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.entitlement.PackageCollection→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.entitlement.RateThrottler→org.apache.openwhisk.common.TransactionId
- Direction
- core.entitlement uses common, so a change to common can break core.entitlement, while a change to core.entitlement can't break common.
- 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→2 core.entity uses core.entity.Attachments✕
- Connections
- 5 pairs of types, where a type in core.entity uses a type in core.entity.Attachments.
- The types involved
org.apache.openwhisk.core.entity.AttachedCode→org.apache.openwhisk.core.entity.Attachments.Attachedorg.apache.openwhisk.core.entity.BlackBoxExec→org.apache.openwhisk.core.entity.Attachments.Attachedorg.apache.openwhisk.core.entity.BlackBoxExec→org.apache.openwhisk.core.entity.Attachments.Attachmentorg.apache.openwhisk.core.entity.CodeExecAsAttachment→org.apache.openwhisk.core.entity.Attachments.Attachedorg.apache.openwhisk.core.entity.CodeExecAsAttachment→org.apache.openwhisk.core.entity.Attachments.Attachment
- Direction
- core.entity uses core.entity.Attachments, so a change to core.entity.Attachments can break core.entity, while a change to core.entity can't break core.entity.Attachments.
- Position
- Below the diagonal: core.entity uses a module listed above it, which is the healthy direction.
10→4 core.entity uses core.database✕
- Connections
- 4 pairs of types, where a type in core.entity uses a type in core.database.
- The types involved
org.apache.openwhisk.core.entity.WhiskDocument→org.apache.openwhisk.core.database.DocumentRevisionProviderorg.apache.openwhisk.core.entity.WhiskDocument→org.apache.openwhisk.core.database.DocumentSerializerorg.apache.openwhisk.core.entity.WhiskEntityQueries→org.apache.openwhisk.core.database.ArtifactStoreorg.apache.openwhisk.core.entity.WhiskEntityQueries→org.apache.openwhisk.core.database.StaleParameter
- Direction
- core.entity uses core.database, so a change to core.database can break core.entity, while a change to core.entity can't break core.database.
- Position
- Below the diagonal: core.entity uses a module listed above it, which is the healthy direction.
10→5 core.entity uses core.entity.ExecManifest✕
- Connections
- 8 pairs of types, where a type in core.entity uses a type in core.entity.ExecManifest.
- The types involved
org.apache.openwhisk.core.entity.BlackBoxExec→org.apache.openwhisk.core.entity.ExecManifest.ImageNameorg.apache.openwhisk.core.entity.BlackBoxExecMetaData→org.apache.openwhisk.core.entity.ExecManifest.ImageNameorg.apache.openwhisk.core.entity.CodeExec→org.apache.openwhisk.core.entity.ExecManifest.ImageNameorg.apache.openwhisk.core.entity.CodeExecAsAttachment→org.apache.openwhisk.core.entity.ExecManifest.RuntimeManifestorg.apache.openwhisk.core.entity.CodeExecAsString→org.apache.openwhisk.core.entity.ExecManifest.RuntimeManifestorg.apache.openwhisk.core.entity.CodeExecMetaDataAsAttachment→org.apache.openwhisk.core.entity.ExecManifest.RuntimeManifestorg.apache.openwhisk.core.entity.CodeExecMetaDataAsString→org.apache.openwhisk.core.entity.ExecManifest.RuntimeManifestorg.apache.openwhisk.core.entity.ExecMetaData→org.apache.openwhisk.core.entity.ExecManifest.ImageName
- Direction
- core.entity uses core.entity.ExecManifest, so a change to core.entity.ExecManifest can break core.entity, while a change to core.entity can't break core.entity.ExecManifest.
- Position
- Below the diagonal: core.entity uses a module listed above it, which is the healthy direction.
10→9 core.entity uses core.entitlement✕
- Connections
- 1 pair of types, where a type in core.entity uses a type in core.entitlement.
- The types involved
org.apache.openwhisk.core.entity.Identity→org.apache.openwhisk.core.entitlement.Privilege
- Direction
- core.entity uses core.entitlement, so a change to core.entitlement can break core.entity, while a change to core.entity can't break core.entitlement.
- Position
- Below the diagonal: core.entity uses a module listed above it, which is the healthy direction.
10→11 core.entity uses core part of a loop✕
- Connections
- 1 pair of types, where a type in core.entity uses a type in core.
- The types involved
org.apache.openwhisk.core.entity.ExecManifest→org.apache.openwhisk.core.WhiskConfig
- Direction
- core.entity uses core, so a change to core can break core.entity, while a change to core.entity can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→15 core.entity uses common part of a loop✕
- Connections
- 4 pairs of types, where a type in core.entity uses a type in common.
- The types involved
org.apache.openwhisk.core.entity.WhiskActivationStore→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.entity.WhiskAuthStore→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.entity.WhiskEntityQueries→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.entity.WhiskEntityStore→org.apache.openwhisk.common.Logging
- Direction
- core.entity uses common, so a change to common can break core.entity, while a change to core.entity can't break common.
- 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→10 core uses core.entity✕
- Connections
- 3 pairs of types, where a type in core uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.WarmUp→org.apache.openwhisk.core.entity.ControllerInstanceIdorg.apache.openwhisk.core.WarmUp→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.WarmUp→org.apache.openwhisk.core.entity.SchedulerInstanceId
- Direction
- core uses core.entity, so a change to core.entity can break core, while a change to core can't break core.entity.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
11→15 core uses common part of a loop✕
- Connections
- 1 pair of types, where a type in core uses a type in common.
- The types involved
org.apache.openwhisk.core.WhiskConfig→org.apache.openwhisk.common.Config
- Direction
- core uses common, so a change to common can break core, while a change to core can't break common.
- 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→10 core.entity.ActivationId uses core.entity✕
- Connections
- 1 pair of types, where a type in core.entity.ActivationId uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.entity.ActivationId.ActivationIdGenerator→org.apache.openwhisk.core.entity.ActivationId
- Direction
- core.entity.ActivationId uses core.entity, so a change to core.entity can break core.entity.ActivationId, while a change to core.entity.ActivationId can't break core.entity.
- Position
- Below the diagonal: core.entity.ActivationId uses a module listed above it, which is the healthy direction.
13→10 core.etcd uses core.entity✕
- Connections
- 1 pair of types, where a type in core.etcd uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.etcd.EtcdType→org.apache.openwhisk.core.entity.ByteSize
- Direction
- core.etcd uses core.entity, so a change to core.entity can break core.etcd, while a change to core.etcd can't break core.entity.
- Position
- Below the diagonal: core.etcd uses a module listed above it, which is the healthy direction.
14→1 core.connector uses spi✕
- Connections
- 1 pair of types, where a type in core.connector uses a type in spi.
- The types involved
org.apache.openwhisk.core.connector.MessagingProvider→org.apache.openwhisk.spi.Spi
- Direction
- core.connector uses spi, so a change to spi can break core.connector, while a change to core.connector can't break spi.
- Position
- Below the diagonal: core.connector uses a module listed above it, which is the healthy direction.
14→10 core.connector uses core.entity✕
- Connections
- 34 pairs of types, where a type in core.connector uses a type in core.entity. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.apache.openwhisk.core.connector.AcknowledgementMessage→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.connector.AcknowledgementMessage→org.apache.openwhisk.core.entity.InstanceIdorg.apache.openwhisk.core.connector.AcknowledgementMessage→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.connector.Activation→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.connector.ActivationMessage→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.connector.ActivationMessage→org.apache.openwhisk.core.entity.ControllerInstanceIdorg.apache.openwhisk.core.connector.ActivationMessage→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.connector.ActivationMessage→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.connector.ActivationMessage→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.connector.CombinedCompletionAndResultMessage→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.connector.CombinedCompletionAndResultMessage→org.apache.openwhisk.core.entity.InstanceIdorg.apache.openwhisk.core.connector.CombinedCompletionAndResultMessage→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.connector.CompletionMessage→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.connector.CompletionMessage→org.apache.openwhisk.core.entity.InstanceIdorg.apache.openwhisk.core.connector.ContainerCreationAckMessage→org.apache.openwhisk.core.entity.CreationIdorg.apache.openwhisk.core.connector.ContainerCreationAckMessage→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.connector.ContainerCreationAckMessage→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.connector.ContainerCreationAckMessage→org.apache.openwhisk.core.entity.InvokerInstanceIdorg.apache.openwhisk.core.connector.ContainerCreationAckMessage→org.apache.openwhisk.core.entity.WhiskActionMetaDataorg.apache.openwhisk.core.connector.ContainerCreationMessage→org.apache.openwhisk.core.entity.CreationIdorg.apache.openwhisk.core.connector.ContainerCreationMessage→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.connector.ContainerCreationMessage→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.connector.ContainerCreationMessage→org.apache.openwhisk.core.entity.SchedulerInstanceIdorg.apache.openwhisk.core.connector.ContainerCreationMessage→org.apache.openwhisk.core.entity.WhiskActionMetaDataorg.apache.openwhisk.core.connector.ContainerDeletionMessage→org.apache.openwhisk.core.entity.DocRevision
- Direction
- core.connector uses core.entity, so a change to core.entity can break core.connector, while a change to core.connector can't break core.entity.
- Position
- Below the diagonal: core.connector uses a module listed above it, which is the healthy direction.
14→11 core.connector uses core✕
- Connections
- 1 pair of types, where a type in core.connector uses a type in core.
- The types involved
org.apache.openwhisk.core.connector.MessagingProvider→org.apache.openwhisk.core.WhiskConfig
- Direction
- core.connector uses core, so a change to core can break core.connector, while a change to core.connector can't break core.
- Position
- Below the diagonal: core.connector uses a module listed above it, which is the healthy direction.
14→15 core.connector uses common part of a loop✕
- Connections
- 10 pairs of types, where a type in core.connector uses a type in common.
- The types involved
org.apache.openwhisk.core.connector.AcknowledgementMessage→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.connector.ActivationMessage→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.connector.CombinedCompletionAndResultMessage→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.connector.CompletionMessage→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.connector.ContainerCreationAckMessage→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.connector.ContainerCreationMessage→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.connector.ContainerDeletionMessage→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.connector.ContainerMessage→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.connector.MessagingProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.connector.ResultMessage→org.apache.openwhisk.common.TransactionId
- Direction
- core.connector uses common, so a change to common can break core.connector, while a change to core.connector can't break common.
- 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→10 common uses core.entity✕
- Connections
- 2 pairs of types, where a type in common uses a type in core.entity.
- The types involved
org.apache.openwhisk.common.InvokerHealth→org.apache.openwhisk.core.entity.InvokerInstanceIdorg.apache.openwhisk.common.LoggingMarkers→org.apache.openwhisk.core.entity.ControllerInstanceId
- Direction
- common uses core.entity, so a change to core.entity can break common, while a change to common can't break core.entity.
- Position
- Below the diagonal: common uses a module listed above it, which is the healthy direction.
15→14 common uses core.connector✕
- Connections
- 1 pair of types, where a type in common uses a type in core.connector.
- The types involved
org.apache.openwhisk.common.UserEvents→org.apache.openwhisk.core.connector.MessageProducer
- Direction
- common uses core.connector, so a change to core.connector can break common, while a change to common can't break core.connector.
- Position
- Below the diagonal: common uses a module listed above it, which is the healthy direction.
16→10 connector.kafka uses core.entity✕
- Connections
- 1 pair of types, where a type in connector.kafka uses a type in core.entity.
- The types involved
org.apache.openwhisk.connector.kafka.KafkaMessagingProvider→org.apache.openwhisk.core.entity.ByteSize
- Direction
- connector.kafka uses core.entity, so a change to core.entity can break connector.kafka, while a change to connector.kafka can't break core.entity.
- Position
- Below the diagonal: connector.kafka uses a module listed above it, which is the healthy direction.
16→11 connector.kafka uses core✕
- Connections
- 1 pair of types, where a type in connector.kafka uses a type in core.
- The types involved
org.apache.openwhisk.connector.kafka.KafkaMessagingProvider→org.apache.openwhisk.core.WhiskConfig
- Direction
- connector.kafka uses core, so a change to core can break connector.kafka, while a change to connector.kafka can't break core.
- Position
- Below the diagonal: connector.kafka uses a module listed above it, which is the healthy direction.
16→14 connector.kafka uses core.connector✕
- Connections
- 7 pairs of types, where a type in connector.kafka uses a type in core.connector.
- The types involved
org.apache.openwhisk.connector.kafka.KafkaConsumerConnector→org.apache.openwhisk.core.connector.MessageConsumerorg.apache.openwhisk.connector.kafka.KafkaMessagingProvider→org.apache.openwhisk.core.connector.MessageConsumerorg.apache.openwhisk.connector.kafka.KafkaMessagingProvider→org.apache.openwhisk.core.connector.MessageProducerorg.apache.openwhisk.connector.kafka.KafkaMessagingProvider→org.apache.openwhisk.core.connector.MessagingProviderorg.apache.openwhisk.connector.kafka.KafkaProducerConnector→org.apache.openwhisk.core.connector.Messageorg.apache.openwhisk.connector.kafka.KafkaProducerConnector→org.apache.openwhisk.core.connector.MessageProducerorg.apache.openwhisk.connector.kafka.KafkaProducerConnector→org.apache.openwhisk.core.connector.ResultMetadata
- Direction
- connector.kafka uses core.connector, so a change to core.connector can break connector.kafka, while a change to connector.kafka can't break core.connector.
- Position
- Below the diagonal: connector.kafka uses a module listed above it, which is the healthy direction.
16→15 connector.kafka uses common✕
- Connections
- 2 pairs of types, where a type in connector.kafka uses a type in common.
- The types involved
org.apache.openwhisk.connector.kafka.KafkaConfiguration→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.connector.kafka.KafkaMessagingProvider→org.apache.openwhisk.common.Logging
- Direction
- connector.kafka uses common, so a change to common can break connector.kafka, while a change to connector.kafka can't break common.
- Position
- Below the diagonal: connector.kafka uses a module listed above it, which is the healthy direction.
17→10 connector.lean uses core.entity✕
- Connections
- 1 pair of types, where a type in connector.lean uses a type in core.entity.
- The types involved
org.apache.openwhisk.connector.lean.LeanMessagingProvider→org.apache.openwhisk.core.entity.ByteSize
- Direction
- connector.lean uses core.entity, so a change to core.entity can break connector.lean, while a change to connector.lean can't break core.entity.
- Position
- Below the diagonal: connector.lean uses a module listed above it, which is the healthy direction.
17→11 connector.lean uses core✕
- Connections
- 1 pair of types, where a type in connector.lean uses a type in core.
- The types involved
org.apache.openwhisk.connector.lean.LeanMessagingProvider→org.apache.openwhisk.core.WhiskConfig
- Direction
- connector.lean uses core, so a change to core can break connector.lean, while a change to connector.lean can't break core.
- Position
- Below the diagonal: connector.lean uses a module listed above it, which is the healthy direction.
17→14 connector.lean uses core.connector✕
- Connections
- 7 pairs of types, where a type in connector.lean uses a type in core.connector.
- The types involved
org.apache.openwhisk.connector.lean.LeanConsumer→org.apache.openwhisk.core.connector.MessageConsumerorg.apache.openwhisk.connector.lean.LeanMessagingProvider→org.apache.openwhisk.core.connector.MessageConsumerorg.apache.openwhisk.connector.lean.LeanMessagingProvider→org.apache.openwhisk.core.connector.MessageProducerorg.apache.openwhisk.connector.lean.LeanMessagingProvider→org.apache.openwhisk.core.connector.MessagingProviderorg.apache.openwhisk.connector.lean.LeanProducer→org.apache.openwhisk.core.connector.Messageorg.apache.openwhisk.connector.lean.LeanProducer→org.apache.openwhisk.core.connector.MessageProducerorg.apache.openwhisk.connector.lean.LeanProducer→org.apache.openwhisk.core.connector.ResultMetadata
- Direction
- connector.lean uses core.connector, so a change to core.connector can break connector.lean, while a change to connector.lean can't break core.connector.
- Position
- Below the diagonal: connector.lean uses a module listed above it, which is the healthy direction.
17→15 connector.lean uses common✕
- Connections
- 1 pair of types, where a type in connector.lean uses a type in common.
- The types involved
org.apache.openwhisk.connector.lean.LeanMessagingProvider→org.apache.openwhisk.common.Logging
- Direction
- connector.lean uses common, so a change to common can break connector.lean, while a change to connector.lean can't break common.
- Position
- Below the diagonal: connector.lean uses a module listed above it, which is the healthy direction.
18→10 core.ack uses core.entity✕
- Connections
- 9 pairs of types, where a type in core.ack uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.ack.ActiveAck→org.apache.openwhisk.core.entity.ControllerInstanceIdorg.apache.openwhisk.core.ack.ActiveAck→org.apache.openwhisk.core.entity.UUIDorg.apache.openwhisk.core.ack.ActiveAck→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.ack.HealthActionAck→org.apache.openwhisk.core.entity.ControllerInstanceIdorg.apache.openwhisk.core.ack.HealthActionAck→org.apache.openwhisk.core.entity.UUIDorg.apache.openwhisk.core.ack.HealthActionAck→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.ack.MessagingActiveAck→org.apache.openwhisk.core.entity.ControllerInstanceIdorg.apache.openwhisk.core.ack.MessagingActiveAck→org.apache.openwhisk.core.entity.UUIDorg.apache.openwhisk.core.ack.MessagingActiveAck→org.apache.openwhisk.core.entity.WhiskActivation
- Direction
- core.ack uses core.entity, so a change to core.entity can break core.ack, while a change to core.ack can't break core.entity.
- Position
- Below the diagonal: core.ack uses a module listed above it, which is the healthy direction.
18→14 core.ack uses core.connector✕
- Connections
- 3 pairs of types, where a type in core.ack uses a type in core.connector.
- The types involved
org.apache.openwhisk.core.ack.ActiveAck→org.apache.openwhisk.core.connector.AcknowledgementMessageorg.apache.openwhisk.core.ack.HealthActionAck→org.apache.openwhisk.core.connector.AcknowledgementMessageorg.apache.openwhisk.core.ack.MessagingActiveAck→org.apache.openwhisk.core.connector.AcknowledgementMessage
- Direction
- core.ack uses core.connector, so a change to core.connector can break core.ack, while a change to core.ack can't break core.connector.
- Position
- Below the diagonal: core.ack uses a module listed above it, which is the healthy direction.
18→15 core.ack uses common✕
- Connections
- 3 pairs of types, where a type in core.ack uses a type in common.
- The types involved
org.apache.openwhisk.core.ack.ActiveAck→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.ack.HealthActionAck→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.ack.MessagingActiveAck→org.apache.openwhisk.common.TransactionId
- Direction
- core.ack uses common, so a change to common can break core.ack, while a change to core.ack can't break common.
- Position
- Below the diagonal: core.ack uses a module listed above it, which is the healthy direction.
19→1 core.containerpool.logging uses spi✕
- Connections
- 1 pair of types, where a type in core.containerpool.logging uses a type in spi.
- The types involved
org.apache.openwhisk.core.containerpool.logging.LogStoreProvider→org.apache.openwhisk.spi.Spi
- Direction
- core.containerpool.logging uses spi, so a change to spi can break core.containerpool.logging, while a change to core.containerpool.logging can't break spi.
- Position
- Below the diagonal: core.containerpool.logging uses a module listed above it, which is the healthy direction.
19→3 core.containerpool.logging uses http✕
- Connections
- 1 pair of types, where a type in core.containerpool.logging uses a type in http.
- The types involved
org.apache.openwhisk.core.containerpool.logging.ElasticSearchRestClient→org.apache.openwhisk.http.PoolingRestClient
- Direction
- core.containerpool.logging uses http, so a change to http can break core.containerpool.logging, while a change to core.containerpool.logging can't break http.
- Position
- Below the diagonal: core.containerpool.logging uses a module listed above it, which is the healthy direction.
19→4 core.containerpool.logging uses core.database✕
- Connections
- 4 pairs of types, where a type in core.containerpool.logging uses a type in core.database.
- The types involved
org.apache.openwhisk.core.containerpool.logging.ElasticSearchLogStore→org.apache.openwhisk.core.database.UserContextorg.apache.openwhisk.core.containerpool.logging.LogDriverLogStore→org.apache.openwhisk.core.database.UserContextorg.apache.openwhisk.core.containerpool.logging.LogStore→org.apache.openwhisk.core.database.UserContextorg.apache.openwhisk.core.containerpool.logging.SplunkLogStore→org.apache.openwhisk.core.database.UserContext
- Direction
- core.containerpool.logging uses core.database, so a change to core.database can break core.containerpool.logging, while a change to core.containerpool.logging can't break core.database.
- Position
- Below the diagonal: core.containerpool.logging uses a module listed above it, which is the healthy direction.
19→7 core.containerpool.logging uses core.containerpool✕
- Connections
- 3 pairs of types, where a type in core.containerpool.logging uses a type in core.containerpool.
- The types involved
org.apache.openwhisk.core.containerpool.logging.DockerToActivationFileLogStore→org.apache.openwhisk.core.containerpool.Containerorg.apache.openwhisk.core.containerpool.logging.LogDriverLogStore→org.apache.openwhisk.core.containerpool.Containerorg.apache.openwhisk.core.containerpool.logging.LogStore→org.apache.openwhisk.core.containerpool.Container
- Direction
- core.containerpool.logging uses core.containerpool, so a change to core.containerpool can break core.containerpool.logging, while a change to core.containerpool.logging can't break core.containerpool.
- Position
- Below the diagonal: core.containerpool.logging uses a module listed above it, which is the healthy direction.
19→10 core.containerpool.logging uses core.entity✕
- Connections
- 20 pairs of types, where a type in core.containerpool.logging uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.containerpool.logging.DockerToActivationFileLogStore→org.apache.openwhisk.core.entity.ActivationLogsorg.apache.openwhisk.core.containerpool.logging.DockerToActivationFileLogStore→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.containerpool.logging.DockerToActivationFileLogStore→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.containerpool.logging.DockerToActivationFileLogStore→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.containerpool.logging.ElasticSearchLogStore→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.containerpool.logging.ElasticSearchLogStore→org.apache.openwhisk.core.entity.ActivationLogsorg.apache.openwhisk.core.containerpool.logging.ElasticSearchLogStore→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.containerpool.logging.LogCollectingException→org.apache.openwhisk.core.entity.ActivationLogsorg.apache.openwhisk.core.containerpool.logging.LogDriverLogStore→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.containerpool.logging.LogDriverLogStore→org.apache.openwhisk.core.entity.ActivationLogsorg.apache.openwhisk.core.containerpool.logging.LogDriverLogStore→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.containerpool.logging.LogDriverLogStore→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.containerpool.logging.LogDriverLogStore→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.containerpool.logging.LogStore→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.containerpool.logging.LogStore→org.apache.openwhisk.core.entity.ActivationLogsorg.apache.openwhisk.core.containerpool.logging.LogStore→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.containerpool.logging.LogStore→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.containerpool.logging.LogStore→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.containerpool.logging.SplunkLogStore→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.containerpool.logging.SplunkLogStore→org.apache.openwhisk.core.entity.ActivationLogs
- Direction
- core.containerpool.logging uses core.entity, so a change to core.entity can break core.containerpool.logging, while a change to core.containerpool.logging can't break core.entity.
- Position
- Below the diagonal: core.containerpool.logging uses a module listed above it, which is the healthy direction.
19→15 core.containerpool.logging uses common✕
- Connections
- 3 pairs of types, where a type in core.containerpool.logging uses a type in common.
- The types involved
org.apache.openwhisk.core.containerpool.logging.DockerToActivationFileLogStore→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.logging.LogDriverLogStore→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.logging.LogStore→org.apache.openwhisk.common.TransactionId
- Direction
- core.containerpool.logging uses common, so a change to common can break core.containerpool.logging, while a change to core.containerpool.logging can't break common.
- Position
- Below the diagonal: core.containerpool.logging uses a module listed above it, which is the healthy direction.
20→6 core.containerpool.v2 uses core.scheduler✕
- Connections
- 1 pair of types, where a type in core.containerpool.v2 uses a type in core.scheduler.
- The types involved
org.apache.openwhisk.core.containerpool.v2.RequestActivation→org.apache.openwhisk.core.scheduler.SchedulerEndpoints
- Direction
- core.containerpool.v2 uses core.scheduler, so a change to core.scheduler can break core.containerpool.v2, while a change to core.containerpool.v2 can't break core.scheduler.
- Position
- Below the diagonal: core.containerpool.v2 uses a module listed above it, which is the healthy direction.
20→7 core.containerpool.v2 uses core.containerpool✕
- Connections
- 12 pairs of types, where a type in core.containerpool.v2 uses a type in core.containerpool.
- The types involved
org.apache.openwhisk.core.containerpool.v2.ClientCreationFailed→org.apache.openwhisk.core.containerpool.Containerorg.apache.openwhisk.core.containerpool.v2.ContainerCreatedData→org.apache.openwhisk.core.containerpool.Containerorg.apache.openwhisk.core.containerpool.v2.ContainerPoolV2→org.apache.openwhisk.core.containerpool.ColdStartKeyorg.apache.openwhisk.core.containerpool.v2.ContainerPoolV2→org.apache.openwhisk.core.containerpool.ContainerPoolConfigorg.apache.openwhisk.core.containerpool.v2.ContainerPoolV2→org.apache.openwhisk.core.containerpool.PrewarmingConfigorg.apache.openwhisk.core.containerpool.v2.Data→org.apache.openwhisk.core.containerpool.Containerorg.apache.openwhisk.core.containerpool.v2.FunctionPullingContainerProxy→org.apache.openwhisk.core.containerpool.Containerorg.apache.openwhisk.core.containerpool.v2.InitializedData→org.apache.openwhisk.core.containerpool.Containerorg.apache.openwhisk.core.containerpool.v2.PreWarmData→org.apache.openwhisk.core.containerpool.Containerorg.apache.openwhisk.core.containerpool.v2.ReschedulingData→org.apache.openwhisk.core.containerpool.Containerorg.apache.openwhisk.core.containerpool.v2.RunActivationCompleted→org.apache.openwhisk.core.containerpool.Containerorg.apache.openwhisk.core.containerpool.v2.WarmData→org.apache.openwhisk.core.containerpool.Container
- Direction
- core.containerpool.v2 uses core.containerpool, so a change to core.containerpool can break core.containerpool.v2, while a change to core.containerpool.v2 can't break core.containerpool.
- Position
- Below the diagonal: core.containerpool.v2 uses a module listed above it, which is the healthy direction.
20→10 core.containerpool.v2 uses core.entity✕
- Connections
- 32 pairs of types, where a type in core.containerpool.v2 uses a type in core.entity. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.apache.openwhisk.core.containerpool.v2.ActivationClientProxy→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.containerpool.v2.ActivationClientProxy→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.containerpool.v2.ClientCreationFailed→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.containerpool.v2.ContainerCreatedData→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.containerpool.v2.ContainerPoolV2→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.v2.ContainerPoolV2→org.apache.openwhisk.core.entity.InvokerInstanceIdorg.apache.openwhisk.core.containerpool.v2.CreationContainer→org.apache.openwhisk.core.entity.WhiskActionorg.apache.openwhisk.core.containerpool.v2.Data→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.v2.FunctionPullingContainerPool→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.v2.FunctionPullingContainerPool→org.apache.openwhisk.core.entity.CodeExecorg.apache.openwhisk.core.containerpool.v2.FunctionPullingContainerPool→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.containerpool.v2.FunctionPullingContainerPool→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.containerpool.v2.FunctionPullingContainerPool→org.apache.openwhisk.core.entity.WhiskActionorg.apache.openwhisk.core.containerpool.v2.FunctionPullingContainerProxy→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.containerpool.v2.FunctionPullingContainerProxy→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.containerpool.v2.FunctionPullingContainerProxy→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.containerpool.v2.FunctionPullingContainerProxy→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.containerpool.v2.Initialize→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.containerpool.v2.Initialize→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.containerpool.v2.InitializedData→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.containerpool.v2.MemoryData→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.v2.PreWarmData→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.v2.RecreateClient→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.containerpool.v2.RescheduleActivation→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.containerpool.v2.RescheduleActivation→org.apache.openwhisk.core.entity.FullyQualifiedEntityName
- Direction
- core.containerpool.v2 uses core.entity, so a change to core.entity can break core.containerpool.v2, while a change to core.containerpool.v2 can't break core.entity.
- Position
- Below the diagonal: core.containerpool.v2 uses a module listed above it, which is the healthy direction.
20→14 core.containerpool.v2 uses core.connector✕
- Connections
- 7 pairs of types, where a type in core.containerpool.v2 uses a type in core.connector.
- The types involved
org.apache.openwhisk.core.containerpool.v2.CreationContainer→org.apache.openwhisk.core.connector.ContainerCreationMessageorg.apache.openwhisk.core.containerpool.v2.DeletionContainer→org.apache.openwhisk.core.connector.ContainerDeletionMessageorg.apache.openwhisk.core.containerpool.v2.FunctionPullingContainerPool→org.apache.openwhisk.core.connector.ContainerCreationMessageorg.apache.openwhisk.core.containerpool.v2.FunctionPullingContainerProxy→org.apache.openwhisk.core.connector.ActivationMessageorg.apache.openwhisk.core.containerpool.v2.InvokerInfo→org.apache.openwhisk.core.connector.InvokerResourceMessageorg.apache.openwhisk.core.containerpool.v2.RescheduleActivation→org.apache.openwhisk.core.connector.ActivationMessageorg.apache.openwhisk.core.containerpool.v2.RunActivation→org.apache.openwhisk.core.connector.ActivationMessage
- Direction
- core.containerpool.v2 uses core.connector, so a change to core.connector can break core.containerpool.v2, while a change to core.containerpool.v2 can't break core.connector.
- Position
- Below the diagonal: core.containerpool.v2 uses a module listed above it, which is the healthy direction.
20→15 core.containerpool.v2 uses common✕
- Connections
- 9 pairs of types, where a type in core.containerpool.v2 uses a type in common.
- The types involved
org.apache.openwhisk.core.containerpool.v2.ContainerHealthErrorWithResumedRun→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.v2.ContainerPoolV2→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.containerpool.v2.FunctionPullingContainerPool→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.containerpool.v2.FunctionPullingContainerProxy→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.v2.Initialize→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.v2.InvokerHealthManager→org.apache.openwhisk.common.InvokerStateorg.apache.openwhisk.core.containerpool.v2.InvokerHealthManager→org.apache.openwhisk.common.RingBufferorg.apache.openwhisk.core.containerpool.v2.InvokerHealthManager→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.v2.InvokerInfo→org.apache.openwhisk.common.RingBuffer
- Direction
- core.containerpool.v2 uses common, so a change to common can break core.containerpool.v2, while a change to core.containerpool.v2 can't break common.
- Position
- Below the diagonal: core.containerpool.v2 uses a module listed above it, which is the healthy direction.
21→4 core.controller.actions uses core.database✕
- Connections
- 3 pairs of types, where a type in core.controller.actions uses a type in core.database.
- The types involved
org.apache.openwhisk.core.controller.actions.PrimitiveActions→org.apache.openwhisk.core.database.ActivationStoreorg.apache.openwhisk.core.controller.actions.PrimitiveActions→org.apache.openwhisk.core.database.UserContextorg.apache.openwhisk.core.controller.actions.SequenceActions→org.apache.openwhisk.core.database.ActivationStore
- Direction
- core.controller.actions uses core.database, so a change to core.database can break core.controller.actions, while a change to core.controller.actions can't break core.database.
- Position
- Below the diagonal: core.controller.actions uses a module listed above it, which is the healthy direction.
21→10 core.controller.actions uses core.entity✕
- Connections
- 22 pairs of types, where a type in core.controller.actions uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.controller.actions.PostActionActivation→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.controller.actions.PostActionActivation→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.controller.actions.PostActionActivation→org.apache.openwhisk.core.entity.WhiskActionMetaDataorg.apache.openwhisk.core.controller.actions.PostActionActivation→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.controller.actions.PrimitiveActions→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.controller.actions.PrimitiveActions→org.apache.openwhisk.core.entity.ActivationResponseorg.apache.openwhisk.core.controller.actions.PrimitiveActions→org.apache.openwhisk.core.entity.ControllerInstanceIdorg.apache.openwhisk.core.controller.actions.PrimitiveActions→org.apache.openwhisk.core.entity.DocIdorg.apache.openwhisk.core.controller.actions.PrimitiveActions→org.apache.openwhisk.core.entity.ExecutableWhiskActionMetaDataorg.apache.openwhisk.core.controller.actions.PrimitiveActions→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.controller.actions.PrimitiveActions→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.controller.actions.PrimitiveActions→org.apache.openwhisk.core.entity.WhiskActionMetaDataorg.apache.openwhisk.core.controller.actions.PrimitiveActions→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.controller.actions.SequenceAccounting→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.controller.actions.SequenceAccounting→org.apache.openwhisk.core.entity.ActivationResponseorg.apache.openwhisk.core.controller.actions.SequenceAccounting→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.controller.actions.SequenceActions→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.controller.actions.SequenceActions→org.apache.openwhisk.core.entity.ControllerInstanceIdorg.apache.openwhisk.core.controller.actions.SequenceActions→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.controller.actions.SequenceActions→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.controller.actions.SequenceActions→org.apache.openwhisk.core.entity.WhiskActionMetaDataorg.apache.openwhisk.core.controller.actions.SequenceActions→org.apache.openwhisk.core.entity.WhiskActivation
- Direction
- core.controller.actions uses core.entity, so a change to core.entity can break core.controller.actions, while a change to core.controller.actions can't break core.entity.
- Position
- Below the diagonal: core.controller.actions uses a module listed above it, which is the healthy direction.
21→15 core.controller.actions uses common✕
- Connections
- 5 pairs of types, where a type in core.controller.actions uses a type in common.
- The types involved
org.apache.openwhisk.core.controller.actions.PostActionActivation→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.actions.PrimitiveActions→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.controller.actions.PrimitiveActions→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.actions.SequenceActions→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.controller.actions.SequenceActions→org.apache.openwhisk.common.TransactionId
- Direction
- core.controller.actions uses common, so a change to common can break core.controller.actions, while a change to core.controller.actions can't break common.
- Position
- Below the diagonal: core.controller.actions uses a module listed above it, which is the healthy direction.
22→4 core.database.azblob uses core.database✕
- Connections
- 4 pairs of types, where a type in core.database.azblob uses a type in core.database.
- The types involved
org.apache.openwhisk.core.database.azblob.AzureBlobAttachmentStore→org.apache.openwhisk.core.database.AttachResultorg.apache.openwhisk.core.database.azblob.AzureBlobAttachmentStore→org.apache.openwhisk.core.database.AttachmentStoreorg.apache.openwhisk.core.database.azblob.AzureBlobAttachmentStoreProvider→org.apache.openwhisk.core.database.AttachmentStoreorg.apache.openwhisk.core.database.azblob.AzureBlobAttachmentStoreProvider→org.apache.openwhisk.core.database.AttachmentStoreProvider
- Direction
- core.database.azblob uses core.database, so a change to core.database can break core.database.azblob, while a change to core.database.azblob can't break core.database.
- Position
- Below the diagonal: core.database.azblob uses a module listed above it, which is the healthy direction.
22→10 core.database.azblob uses core.entity✕
- Connections
- 1 pair of types, where a type in core.database.azblob uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.database.azblob.AzureBlobAttachmentStore→org.apache.openwhisk.core.entity.DocId
- Direction
- core.database.azblob uses core.entity, so a change to core.entity can break core.database.azblob, while a change to core.database.azblob can't break core.entity.
- Position
- Below the diagonal: core.database.azblob uses a module listed above it, which is the healthy direction.
22→15 core.database.azblob uses common✕
- Connections
- 2 pairs of types, where a type in core.database.azblob uses a type in common.
- The types involved
org.apache.openwhisk.core.database.azblob.AzureBlobAttachmentStore→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.azblob.AzureBlobAttachmentStoreProvider→org.apache.openwhisk.common.Logging
- Direction
- core.database.azblob uses common, so a change to common can break core.database.azblob, while a change to core.database.azblob can't break common.
- Position
- Below the diagonal: core.database.azblob uses a module listed above it, which is the healthy direction.
23→2 core.database.cosmosdb uses core.entity.Attachments✕
- Connections
- 1 pair of types, where a type in core.database.cosmosdb uses a type in core.entity.Attachments.
- The types involved
org.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStore→org.apache.openwhisk.core.entity.Attachments.Attached
- Direction
- core.database.cosmosdb uses core.entity.Attachments, so a change to core.entity.Attachments can break core.database.cosmosdb, while a change to core.database.cosmosdb can't break core.entity.Attachments.
- Position
- Below the diagonal: core.database.cosmosdb uses a module listed above it, which is the healthy direction.
23→4 core.database.cosmosdb uses core.database✕
- Connections
- 10 pairs of types, where a type in core.database.cosmosdb uses a type in core.database.
- The types involved
org.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStore→org.apache.openwhisk.core.database.ArtifactStoreorg.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStore→org.apache.openwhisk.core.database.AttachmentStoreorg.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStore→org.apache.openwhisk.core.database.AttachmentSupportorg.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStore→org.apache.openwhisk.core.database.DocumentProviderorg.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStore→org.apache.openwhisk.core.database.InliningConfigorg.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStore→org.apache.openwhisk.core.database.StaleParameterorg.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStoreProvider→org.apache.openwhisk.core.database.ArtifactStoreorg.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStoreProvider→org.apache.openwhisk.core.database.ArtifactStoreProviderorg.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStoreProvider→org.apache.openwhisk.core.database.AttachmentStoreorg.apache.openwhisk.core.database.cosmosdb.CosmosDBViewMapper→org.apache.openwhisk.core.database.DocumentHandler
- Direction
- core.database.cosmosdb uses core.database, so a change to core.database can break core.database.cosmosdb, while a change to core.database.cosmosdb can't break core.database.
- Position
- Below the diagonal: core.database.cosmosdb uses a module listed above it, which is the healthy direction.
23→10 core.database.cosmosdb uses core.entity✕
- Connections
- 4 pairs of types, where a type in core.database.cosmosdb uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.database.cosmosdb.CollectionResourceUsage→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStore→org.apache.openwhisk.core.entity.DocIdorg.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStore→org.apache.openwhisk.core.entity.DocInfoorg.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStoreProvider→org.apache.openwhisk.core.entity.DocumentReader
- Direction
- core.database.cosmosdb uses core.entity, so a change to core.entity can break core.database.cosmosdb, while a change to core.database.cosmosdb can't break core.entity.
- Position
- Below the diagonal: core.database.cosmosdb uses a module listed above it, which is the healthy direction.
23→15 core.database.cosmosdb uses common✕
- Connections
- 8 pairs of types, where a type in core.database.cosmosdb uses a type in common.
- The types involved
org.apache.openwhisk.core.database.cosmosdb.ActivationViewMapper→org.apache.openwhisk.common.WhiskInstantsorg.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStore→org.apache.openwhisk.common.LogMarkerTokenorg.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStore→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStore→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.cosmosdb.CosmosDBArtifactStoreProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.cosmosdb.CosmosDBSupport→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.cosmosdb.RetryMetricsCollector→org.apache.openwhisk.common.Counterorg.apache.openwhisk.core.database.cosmosdb.RetryMetricsCollector→org.apache.openwhisk.common.LogMarkerToken
- Direction
- core.database.cosmosdb uses common, so a change to common can break core.database.cosmosdb, while a change to core.database.cosmosdb can't break common.
- Position
- Below the diagonal: core.database.cosmosdb uses a module listed above it, which is the healthy direction.
24→4 core.database.elasticsearch uses core.database✕
- Connections
- 6 pairs of types, where a type in core.database.elasticsearch uses a type in core.database.
- The types involved
org.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore→org.apache.openwhisk.core.database.ActivationStoreorg.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore→org.apache.openwhisk.core.database.ArtifactStoreExceptionorg.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore→org.apache.openwhisk.core.database.Batcherorg.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore→org.apache.openwhisk.core.database.CacheChangeNotificationorg.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore→org.apache.openwhisk.core.database.UserContextorg.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStoreProvider→org.apache.openwhisk.core.database.ActivationStoreProvider
- Direction
- core.database.elasticsearch uses core.database, so a change to core.database can break core.database.elasticsearch, while a change to core.database.elasticsearch can't break core.database.
- Position
- Below the diagonal: core.database.elasticsearch uses a module listed above it, which is the healthy direction.
24→10 core.database.elasticsearch uses core.entity✕
- Connections
- 4 pairs of types, where a type in core.database.elasticsearch uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore→org.apache.openwhisk.core.entity.DocInfoorg.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore→org.apache.openwhisk.core.entity.EntityPathorg.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore→org.apache.openwhisk.core.entity.WhiskActivation
- Direction
- core.database.elasticsearch uses core.entity, so a change to core.entity can break core.database.elasticsearch, while a change to core.database.elasticsearch can't break core.entity.
- Position
- Below the diagonal: core.database.elasticsearch uses a module listed above it, which is the healthy direction.
24→15 core.database.elasticsearch uses common✕
- Connections
- 3 pairs of types, where a type in core.database.elasticsearch uses a type in common.
- The types involved
org.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStoreProvider→org.apache.openwhisk.common.Logging
- Direction
- core.database.elasticsearch uses common, so a change to common can break core.database.elasticsearch, while a change to core.database.elasticsearch can't break common.
- Position
- Below the diagonal: core.database.elasticsearch uses a module listed above it, which is the healthy direction.
25→2 core.database.memory uses core.entity.Attachments✕
- Connections
- 1 pair of types, where a type in core.database.memory uses a type in core.entity.Attachments.
- The types involved
org.apache.openwhisk.core.database.memory.MemoryArtifactStore→org.apache.openwhisk.core.entity.Attachments.Attached
- Direction
- core.database.memory uses core.entity.Attachments, so a change to core.entity.Attachments can break core.database.memory, while a change to core.database.memory can't break core.entity.Attachments.
- Position
- Below the diagonal: core.database.memory uses a module listed above it, which is the healthy direction.
25→4 core.database.memory uses core.database✕
- Connections
- 17 pairs of types, where a type in core.database.memory uses a type in core.database.
- The types involved
org.apache.openwhisk.core.database.memory.MemoryArtifactStore→org.apache.openwhisk.core.database.ArtifactStoreorg.apache.openwhisk.core.database.memory.MemoryArtifactStore→org.apache.openwhisk.core.database.AttachmentStoreorg.apache.openwhisk.core.database.memory.MemoryArtifactStore→org.apache.openwhisk.core.database.AttachmentSupportorg.apache.openwhisk.core.database.memory.MemoryArtifactStore→org.apache.openwhisk.core.database.DocumentProviderorg.apache.openwhisk.core.database.memory.MemoryArtifactStore→org.apache.openwhisk.core.database.InliningConfigorg.apache.openwhisk.core.database.memory.MemoryArtifactStore→org.apache.openwhisk.core.database.StaleParameterorg.apache.openwhisk.core.database.memory.MemoryArtifactStoreProvider→org.apache.openwhisk.core.database.ArtifactStoreorg.apache.openwhisk.core.database.memory.MemoryArtifactStoreProvider→org.apache.openwhisk.core.database.ArtifactStoreProviderorg.apache.openwhisk.core.database.memory.MemoryArtifactStoreProvider→org.apache.openwhisk.core.database.AttachmentStoreorg.apache.openwhisk.core.database.memory.MemoryAttachmentStore→org.apache.openwhisk.core.database.AttachResultorg.apache.openwhisk.core.database.memory.MemoryAttachmentStore→org.apache.openwhisk.core.database.AttachmentStoreorg.apache.openwhisk.core.database.memory.MemoryAttachmentStoreProvider→org.apache.openwhisk.core.database.AttachmentStoreorg.apache.openwhisk.core.database.memory.MemoryAttachmentStoreProvider→org.apache.openwhisk.core.database.AttachmentStoreProviderorg.apache.openwhisk.core.database.memory.NoopActivationStore→org.apache.openwhisk.core.database.ActivationStoreorg.apache.openwhisk.core.database.memory.NoopActivationStore→org.apache.openwhisk.core.database.CacheChangeNotificationorg.apache.openwhisk.core.database.memory.NoopActivationStore→org.apache.openwhisk.core.database.UserContextorg.apache.openwhisk.core.database.memory.NoopActivationStoreProvider→org.apache.openwhisk.core.database.ActivationStoreProvider
- Direction
- core.database.memory uses core.database, so a change to core.database can break core.database.memory, while a change to core.database.memory can't break core.database.
- Position
- Below the diagonal: core.database.memory uses a module listed above it, which is the healthy direction.
25→10 core.database.memory uses core.entity✕
- Connections
- 8 pairs of types, where a type in core.database.memory uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.database.memory.MemoryArtifactStore→org.apache.openwhisk.core.entity.DocIdorg.apache.openwhisk.core.database.memory.MemoryArtifactStore→org.apache.openwhisk.core.entity.DocInfoorg.apache.openwhisk.core.database.memory.MemoryArtifactStoreProvider→org.apache.openwhisk.core.entity.DocumentReaderorg.apache.openwhisk.core.database.memory.MemoryAttachmentStore→org.apache.openwhisk.core.entity.DocIdorg.apache.openwhisk.core.database.memory.NoopActivationStore→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.database.memory.NoopActivationStore→org.apache.openwhisk.core.entity.DocInfoorg.apache.openwhisk.core.database.memory.NoopActivationStore→org.apache.openwhisk.core.entity.EntityPathorg.apache.openwhisk.core.database.memory.NoopActivationStore→org.apache.openwhisk.core.entity.WhiskActivation
- Direction
- core.database.memory uses core.entity, so a change to core.entity can break core.database.memory, while a change to core.database.memory can't break core.entity.
- Position
- Below the diagonal: core.database.memory uses a module listed above it, which is the healthy direction.
25→15 core.database.memory uses common✕
- Connections
- 8 pairs of types, where a type in core.database.memory uses a type in common.
- The types involved
org.apache.openwhisk.core.database.memory.MemoryArtifactStore→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.memory.MemoryArtifactStore→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.memory.MemoryArtifactStoreProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.memory.MemoryAttachmentStore→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.memory.MemoryAttachmentStoreProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.database.memory.NoopActivationStore→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.memory.NoopActivationStore→org.apache.openwhisk.common.WhiskInstantsorg.apache.openwhisk.core.database.memory.NoopActivationStoreProvider→org.apache.openwhisk.common.Logging
- Direction
- core.database.memory uses common, so a change to common can break core.database.memory, while a change to core.database.memory can't break common.
- Position
- Below the diagonal: core.database.memory uses a module listed above it, which is the healthy direction.
26→4 core.database.mongodb uses core.database✕
- Connections
- 3 pairs of types, where a type in core.database.mongodb uses a type in core.database.
- The types involved
org.apache.openwhisk.core.database.mongodb.MongoDBArtifactStoreProvider→org.apache.openwhisk.core.database.ArtifactStoreorg.apache.openwhisk.core.database.mongodb.MongoDBArtifactStoreProvider→org.apache.openwhisk.core.database.ArtifactStoreProviderorg.apache.openwhisk.core.database.mongodb.MongoDBArtifactStoreProvider→org.apache.openwhisk.core.database.AttachmentStore
- Direction
- core.database.mongodb uses core.database, so a change to core.database can break core.database.mongodb, while a change to core.database.mongodb can't break core.database.
- Position
- Below the diagonal: core.database.mongodb uses a module listed above it, which is the healthy direction.
26→10 core.database.mongodb uses core.entity✕
- Connections
- 1 pair of types, where a type in core.database.mongodb uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.database.mongodb.MongoDBArtifactStoreProvider→org.apache.openwhisk.core.entity.DocumentReader
- Direction
- core.database.mongodb uses core.entity, so a change to core.entity can break core.database.mongodb, while a change to core.database.mongodb can't break core.entity.
- Position
- Below the diagonal: core.database.mongodb uses a module listed above it, which is the healthy direction.
26→15 core.database.mongodb uses common✕
- Connections
- 1 pair of types, where a type in core.database.mongodb uses a type in common.
- The types involved
org.apache.openwhisk.core.database.mongodb.MongoDBArtifactStoreProvider→org.apache.openwhisk.common.Logging
- Direction
- core.database.mongodb uses common, so a change to common can break core.database.mongodb, while a change to core.database.mongodb can't break common.
- Position
- Below the diagonal: core.database.mongodb uses a module listed above it, which is the healthy direction.
27→4 core.database.s3 uses core.database✕
- Connections
- 4 pairs of types, where a type in core.database.s3 uses a type in core.database.
- The types involved
org.apache.openwhisk.core.database.s3.S3AttachmentStore→org.apache.openwhisk.core.database.AttachResultorg.apache.openwhisk.core.database.s3.S3AttachmentStore→org.apache.openwhisk.core.database.AttachmentStoreorg.apache.openwhisk.core.database.s3.S3AttachmentStoreProvider→org.apache.openwhisk.core.database.AttachmentStoreorg.apache.openwhisk.core.database.s3.S3AttachmentStoreProvider→org.apache.openwhisk.core.database.AttachmentStoreProvider
- Direction
- core.database.s3 uses core.database, so a change to core.database can break core.database.s3, while a change to core.database.s3 can't break core.database.
- Position
- Below the diagonal: core.database.s3 uses a module listed above it, which is the healthy direction.
27→10 core.database.s3 uses core.entity✕
- Connections
- 1 pair of types, where a type in core.database.s3 uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.database.s3.S3AttachmentStore→org.apache.openwhisk.core.entity.DocId
- Direction
- core.database.s3 uses core.entity, so a change to core.entity can break core.database.s3, while a change to core.database.s3 can't break core.entity.
- Position
- Below the diagonal: core.database.s3 uses a module listed above it, which is the healthy direction.
27→15 core.database.s3 uses common✕
- Connections
- 2 pairs of types, where a type in core.database.s3 uses a type in common.
- The types involved
org.apache.openwhisk.core.database.s3.S3AttachmentStore→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.database.s3.S3AttachmentStoreProvider→org.apache.openwhisk.common.Logging
- Direction
- core.database.s3 uses common, so a change to common can break core.database.s3, while a change to core.database.s3 can't break common.
- Position
- Below the diagonal: core.database.s3 uses a module listed above it, which is the healthy direction.
28→7 core.invoker.Invoker uses core.containerpool✕
- Connections
- 1 pair of types, where a type in core.invoker.Invoker uses a type in core.containerpool.
- The types involved
org.apache.openwhisk.core.invoker.Invoker.LogsCollector→org.apache.openwhisk.core.containerpool.Container
- Direction
- core.invoker.Invoker uses core.containerpool, so a change to core.containerpool can break core.invoker.Invoker, while a change to core.invoker.Invoker can't break core.containerpool.
- Position
- Below the diagonal: core.invoker.Invoker uses a module listed above it, which is the healthy direction.
28→10 core.invoker.Invoker uses core.entity✕
- Connections
- 4 pairs of types, where a type in core.invoker.Invoker uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.invoker.Invoker.LogsCollector→org.apache.openwhisk.core.entity.ActivationLogsorg.apache.openwhisk.core.invoker.Invoker.LogsCollector→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.invoker.Invoker.LogsCollector→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.invoker.Invoker.LogsCollector→org.apache.openwhisk.core.entity.WhiskActivation
- Direction
- core.invoker.Invoker uses core.entity, so a change to core.entity can break core.invoker.Invoker, while a change to core.invoker.Invoker can't break core.entity.
- Position
- Below the diagonal: core.invoker.Invoker uses a module listed above it, which is the healthy direction.
28→15 core.invoker.Invoker uses common✕
- Connections
- 1 pair of types, where a type in core.invoker.Invoker uses a type in common.
- The types involved
org.apache.openwhisk.core.invoker.Invoker.LogsCollector→org.apache.openwhisk.common.TransactionId
- Direction
- core.invoker.Invoker uses common, so a change to common can break core.invoker.Invoker, while a change to core.invoker.Invoker can't break common.
- Position
- Below the diagonal: core.invoker.Invoker uses a module listed above it, which is the healthy direction.
29→10 core.scheduler.message uses core.entity✕
- Connections
- 19 pairs of types, where a type in core.scheduler.message uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.scheduler.message.ContainerCreation→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.scheduler.message.ContainerDeletion→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.scheduler.message.ContainerDeletion→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.scheduler.message.ContainerDeletion→org.apache.openwhisk.core.entity.WhiskActionMetaDataorg.apache.openwhisk.core.scheduler.message.ContainerKeyMeta→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.scheduler.message.CreationJobState→org.apache.openwhisk.core.entity.CreationIdorg.apache.openwhisk.core.scheduler.message.CreationJobState→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.scheduler.message.CreationJobState→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.scheduler.message.FailedCreationJob→org.apache.openwhisk.core.entity.CreationIdorg.apache.openwhisk.core.scheduler.message.FailedCreationJob→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.scheduler.message.FailedCreationJob→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.scheduler.message.ReschedulingCreationJob→org.apache.openwhisk.core.entity.CreationIdorg.apache.openwhisk.core.scheduler.message.ReschedulingCreationJob→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.scheduler.message.ReschedulingCreationJob→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.scheduler.message.ReschedulingCreationJob→org.apache.openwhisk.core.entity.SchedulerInstanceIdorg.apache.openwhisk.core.scheduler.message.ReschedulingCreationJob→org.apache.openwhisk.core.entity.WhiskActionMetaDataorg.apache.openwhisk.core.scheduler.message.SuccessfulCreationJob→org.apache.openwhisk.core.entity.CreationIdorg.apache.openwhisk.core.scheduler.message.SuccessfulCreationJob→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.scheduler.message.SuccessfulCreationJob→org.apache.openwhisk.core.entity.FullyQualifiedEntityName
- Direction
- core.scheduler.message uses core.entity, so a change to core.entity can break core.scheduler.message, while a change to core.scheduler.message can't break core.entity.
- Position
- Below the diagonal: core.scheduler.message uses a module listed above it, which is the healthy direction.
29→14 core.scheduler.message uses core.connector✕
- Connections
- 5 pairs of types, where a type in core.scheduler.message uses a type in core.connector.
- The types involved
org.apache.openwhisk.core.scheduler.message.ContainerCreation→org.apache.openwhisk.core.connector.ContainerCreationMessageorg.apache.openwhisk.core.scheduler.message.FailedCreationJob→org.apache.openwhisk.core.connector.ContainerCreationErrororg.apache.openwhisk.core.scheduler.message.FinishCreationJob→org.apache.openwhisk.core.connector.ContainerCreationAckMessageorg.apache.openwhisk.core.scheduler.message.RegisterCreationJob→org.apache.openwhisk.core.connector.ContainerCreationMessageorg.apache.openwhisk.core.scheduler.message.ReschedulingCreationJob→org.apache.openwhisk.core.connector.ContainerCreationMessage
- Direction
- core.scheduler.message uses core.connector, so a change to core.connector can break core.scheduler.message, while a change to core.scheduler.message can't break core.connector.
- Position
- Below the diagonal: core.scheduler.message uses a module listed above it, which is the healthy direction.
29→15 core.scheduler.message uses common✕
- Connections
- 1 pair of types, where a type in core.scheduler.message uses a type in common.
- The types involved
org.apache.openwhisk.core.scheduler.message.ReschedulingCreationJob→org.apache.openwhisk.common.TransactionId
- Direction
- core.scheduler.message uses common, so a change to common can break core.scheduler.message, while a change to core.scheduler.message can't break common.
- Position
- Below the diagonal: core.scheduler.message uses a module listed above it, which is the healthy direction.
30→1 core.scheduler.queue uses spi✕
- Connections
- 1 pair of types, where a type in core.scheduler.queue uses a type in spi.
- The types involved
org.apache.openwhisk.core.scheduler.queue.DurationCheckerProvider→org.apache.openwhisk.spi.Spi
- Direction
- core.scheduler.queue uses spi, so a change to spi can break core.scheduler.queue, while a change to core.scheduler.queue can't break spi.
- Position
- Below the diagonal: core.scheduler.queue uses a module listed above it, which is the healthy direction.
30→10 core.scheduler.queue uses core.entity✕
- Connections
- 23 pairs of types, where a type in core.scheduler.queue uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.scheduler.queue.ContainerKeyMeta→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.scheduler.queue.CreateNewQueue→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.scheduler.queue.CreateNewQueue→org.apache.openwhisk.core.entity.WhiskActionMetaDataorg.apache.openwhisk.core.scheduler.queue.CreateQueue→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.scheduler.queue.CreateQueue→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.scheduler.queue.CreateQueue→org.apache.openwhisk.core.entity.WhiskActionMetaDataorg.apache.openwhisk.core.scheduler.queue.CreateQueueResponse→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.scheduler.queue.DurationChecker→org.apache.openwhisk.core.entity.WhiskActionMetaDataorg.apache.openwhisk.core.scheduler.queue.MemoryQueue→org.apache.openwhisk.core.entity.ActivationResponseorg.apache.openwhisk.core.scheduler.queue.MemoryQueue→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.scheduler.queue.MemoryQueue→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.scheduler.queue.MemoryQueueKey→org.apache.openwhisk.core.entity.DocInfoorg.apache.openwhisk.core.scheduler.queue.QueueManager→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.scheduler.queue.QueueManager→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.scheduler.queue.QueueManager→org.apache.openwhisk.core.entity.WhiskActionMetaDataorg.apache.openwhisk.core.scheduler.queue.QueueManager→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.scheduler.queue.QueueReactivated→org.apache.openwhisk.core.entity.DocInfoorg.apache.openwhisk.core.scheduler.queue.QueueReactivated→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.scheduler.queue.QueueRemoved→org.apache.openwhisk.core.entity.DocInfoorg.apache.openwhisk.core.scheduler.queue.RecoverQueue→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.scheduler.queue.RecoverQueue→org.apache.openwhisk.core.entity.WhiskActionMetaDataorg.apache.openwhisk.core.scheduler.queue.UpdateMemoryQueue→org.apache.openwhisk.core.entity.DocInfoorg.apache.openwhisk.core.scheduler.queue.UpdateMemoryQueue→org.apache.openwhisk.core.entity.FullyQualifiedEntityName
- Direction
- core.scheduler.queue uses core.entity, so a change to core.entity can break core.scheduler.queue, while a change to core.scheduler.queue can't break core.entity.
- Position
- Below the diagonal: core.scheduler.queue uses a module listed above it, which is the healthy direction.
30→13 core.scheduler.queue uses core.etcd✕
- Connections
- 2 pairs of types, where a type in core.scheduler.queue uses a type in core.etcd.
- The types involved
org.apache.openwhisk.core.scheduler.queue.MemoryQueue→org.apache.openwhisk.core.etcd.EtcdClientorg.apache.openwhisk.core.scheduler.queue.NamespaceContainerCount→org.apache.openwhisk.core.etcd.EtcdClient
- Direction
- core.scheduler.queue uses core.etcd, so a change to core.etcd can break core.scheduler.queue, while a change to core.scheduler.queue can't break core.etcd.
- Position
- Below the diagonal: core.scheduler.queue uses a module listed above it, which is the healthy direction.
30→14 core.scheduler.queue uses core.connector✕
- Connections
- 13 pairs of types, where a type in core.scheduler.queue uses a type in core.connector.
- The types involved
org.apache.openwhisk.core.scheduler.queue.ActionMismatch→org.apache.openwhisk.core.connector.Messageorg.apache.openwhisk.core.scheduler.queue.BufferedRequest→org.apache.openwhisk.core.connector.ActivationMessageorg.apache.openwhisk.core.scheduler.queue.CancelPoll→org.apache.openwhisk.core.connector.ActivationMessageorg.apache.openwhisk.core.scheduler.queue.CreateNewQueue→org.apache.openwhisk.core.connector.ActivationMessageorg.apache.openwhisk.core.scheduler.queue.FlushingData→org.apache.openwhisk.core.connector.ContainerCreationErrororg.apache.openwhisk.core.scheduler.queue.MemoryQueue→org.apache.openwhisk.core.connector.ActivationMessageorg.apache.openwhisk.core.scheduler.queue.MemoryQueue→org.apache.openwhisk.core.connector.ContainerCreationErrororg.apache.openwhisk.core.scheduler.queue.NoActivationMessage→org.apache.openwhisk.core.connector.Messageorg.apache.openwhisk.core.scheduler.queue.NoMemoryQueue→org.apache.openwhisk.core.connector.Messageorg.apache.openwhisk.core.scheduler.queue.QueueManager→org.apache.openwhisk.core.connector.ActivationMessageorg.apache.openwhisk.core.scheduler.queue.RecoverQueue→org.apache.openwhisk.core.connector.ActivationMessageorg.apache.openwhisk.core.scheduler.queue.TimeSeriesActivationEntry→org.apache.openwhisk.core.connector.ActivationMessageorg.apache.openwhisk.core.scheduler.queue.UpdateMemoryQueue→org.apache.openwhisk.core.connector.ActivationMessage
- Direction
- core.scheduler.queue uses core.connector, so a change to core.connector can break core.scheduler.queue, while a change to core.scheduler.queue can't break core.connector.
- Position
- Below the diagonal: core.scheduler.queue uses a module listed above it, which is the healthy direction.
30→15 core.scheduler.queue uses common✕
- Connections
- 6 pairs of types, where a type in core.scheduler.queue uses a type in common.
- The types involved
org.apache.openwhisk.core.scheduler.queue.DurationCheckerProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.scheduler.queue.ElasticSearchDurationCheckerProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.scheduler.queue.MemoryQueue→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.scheduler.queue.NamespaceContainerCount→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.scheduler.queue.NoopDurationCheckerProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.scheduler.queue.QueueManager→org.apache.openwhisk.common.TransactionId
- Direction
- core.scheduler.queue uses common, so a change to common can break core.scheduler.queue, while a change to core.scheduler.queue can't break common.
- Position
- Below the diagonal: core.scheduler.queue uses a module listed above it, which is the healthy direction.
30→37 core.scheduler.queue uses core.scheduler.grpc part of a loop✕
- Connections
- 1 pair of types, where a type in core.scheduler.queue uses a type in core.scheduler.grpc.
- The types involved
org.apache.openwhisk.core.scheduler.queue.MemoryQueue→org.apache.openwhisk.core.scheduler.grpc.GetActivation
- Direction
- core.scheduler.queue uses core.scheduler.grpc, so a change to core.scheduler.grpc can break core.scheduler.queue, while a change to core.scheduler.queue can't break core.scheduler.grpc.
- 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→5 core.yarn uses core.entity.ExecManifest✕
- Connections
- 1 pair of types, where a type in core.yarn uses a type in core.entity.ExecManifest.
- The types involved
org.apache.openwhisk.core.yarn.YARNContainerFactory→org.apache.openwhisk.core.entity.ExecManifest.ImageName
- Direction
- core.yarn uses core.entity.ExecManifest, so a change to core.entity.ExecManifest can break core.yarn, while a change to core.yarn can't break core.entity.ExecManifest.
- Position
- Below the diagonal: core.yarn uses a module listed above it, which is the healthy direction.
31→7 core.yarn uses core.containerpool✕
- Connections
- 7 pairs of types, where a type in core.yarn uses a type in core.containerpool.
- The types involved
org.apache.openwhisk.core.yarn.YARNContainerFactory→org.apache.openwhisk.core.containerpool.Containerorg.apache.openwhisk.core.yarn.YARNContainerFactory→org.apache.openwhisk.core.containerpool.ContainerFactoryorg.apache.openwhisk.core.yarn.YARNContainerFactoryProvider→org.apache.openwhisk.core.containerpool.ContainerFactoryorg.apache.openwhisk.core.yarn.YARNContainerFactoryProvider→org.apache.openwhisk.core.containerpool.ContainerFactoryProviderorg.apache.openwhisk.core.yarn.YARNTask→org.apache.openwhisk.core.containerpool.Containerorg.apache.openwhisk.core.yarn.YARNTask→org.apache.openwhisk.core.containerpool.ContainerAddressorg.apache.openwhisk.core.yarn.YARNTask→org.apache.openwhisk.core.containerpool.ContainerId
- Direction
- core.yarn uses core.containerpool, so a change to core.containerpool can break core.yarn, while a change to core.yarn can't break core.containerpool.
- Position
- Below the diagonal: core.yarn uses a module listed above it, which is the healthy direction.
31→10 core.yarn uses core.entity✕
- Connections
- 3 pairs of types, where a type in core.yarn uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.yarn.YARNContainerFactory→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.yarn.YARNContainerFactoryProvider→org.apache.openwhisk.core.entity.InvokerInstanceIdorg.apache.openwhisk.core.yarn.YARNTask→org.apache.openwhisk.core.entity.ByteSize
- Direction
- core.yarn uses core.entity, so a change to core.entity can break core.yarn, while a change to core.yarn can't break core.entity.
- Position
- Below the diagonal: core.yarn uses a module listed above it, which is the healthy direction.
31→11 core.yarn uses core✕
- Connections
- 2 pairs of types, where a type in core.yarn uses a type in core.
- The types involved
org.apache.openwhisk.core.yarn.YARNContainerFactory→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.yarn.YARNContainerFactoryProvider→org.apache.openwhisk.core.WhiskConfig
- Direction
- core.yarn uses core, so a change to core can break core.yarn, while a change to core.yarn can't break core.
- Position
- Below the diagonal: core.yarn uses a module listed above it, which is the healthy direction.
31→15 core.yarn uses common✕
- Connections
- 6 pairs of types, where a type in core.yarn uses a type in common.
- The types involved
org.apache.openwhisk.core.yarn.YARNContainerFactory→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.yarn.YARNContainerFactory→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.yarn.YARNContainerFactoryProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.yarn.YARNRESTUtil→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.yarn.YARNTask→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.yarn.YARNTask→org.apache.openwhisk.common.TransactionId
- Direction
- core.yarn uses common, so a change to common can break core.yarn, while a change to core.yarn can't break common.
- Position
- Below the diagonal: core.yarn uses a module listed above it, which is the healthy direction.
32→5 core.containerpool.docker uses core.entity.ExecManifest✕
- Connections
- 1 pair of types, where a type in core.containerpool.docker uses a type in core.entity.ExecManifest.
- The types involved
org.apache.openwhisk.core.containerpool.docker.DockerContainer→org.apache.openwhisk.core.entity.ExecManifest.ImageName
- Direction
- core.containerpool.docker uses core.entity.ExecManifest, so a change to core.entity.ExecManifest can break core.containerpool.docker, while a change to core.containerpool.docker can't break core.entity.ExecManifest.
- Position
- Below the diagonal: core.containerpool.docker uses a module listed above it, which is the healthy direction.
32→7 core.containerpool.docker uses core.containerpool✕
- Connections
- 26 pairs of types, where a type in core.containerpool.docker uses a type in core.containerpool. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.apache.openwhisk.core.containerpool.docker.BrokenDockerContainer→org.apache.openwhisk.core.containerpool.ContainerIdorg.apache.openwhisk.core.containerpool.docker.DockerApi→org.apache.openwhisk.core.containerpool.ContainerAddressorg.apache.openwhisk.core.containerpool.docker.DockerApi→org.apache.openwhisk.core.containerpool.ContainerIdorg.apache.openwhisk.core.containerpool.docker.DockerApiWithFileAccess→org.apache.openwhisk.core.containerpool.ContainerIdorg.apache.openwhisk.core.containerpool.docker.DockerCliLogStore→org.apache.openwhisk.core.containerpool.Containerorg.apache.openwhisk.core.containerpool.docker.DockerClient→org.apache.openwhisk.core.containerpool.ContainerAddressorg.apache.openwhisk.core.containerpool.docker.DockerClient→org.apache.openwhisk.core.containerpool.ContainerIdorg.apache.openwhisk.core.containerpool.docker.DockerClientWithFileAccess→org.apache.openwhisk.core.containerpool.ContainerAddressorg.apache.openwhisk.core.containerpool.docker.DockerClientWithFileAccess→org.apache.openwhisk.core.containerpool.ContainerIdorg.apache.openwhisk.core.containerpool.docker.DockerContainer→org.apache.openwhisk.core.containerpool.RuntimesRegistryConfigorg.apache.openwhisk.core.containerpool.docker.DockerContainerFactory→org.apache.openwhisk.core.containerpool.Containerorg.apache.openwhisk.core.containerpool.docker.DockerContainerFactory→org.apache.openwhisk.core.containerpool.ContainerFactoryorg.apache.openwhisk.core.containerpool.docker.DockerContainerFactory→org.apache.openwhisk.core.containerpool.RuntimesRegistryConfigorg.apache.openwhisk.core.containerpool.docker.DockerContainerFactoryProvider→org.apache.openwhisk.core.containerpool.ContainerFactoryorg.apache.openwhisk.core.containerpool.docker.DockerContainerFactoryProvider→org.apache.openwhisk.core.containerpool.ContainerFactoryProviderorg.apache.openwhisk.core.containerpool.docker.DockerContainerId→org.apache.openwhisk.core.containerpool.ContainerIdorg.apache.openwhisk.core.containerpool.docker.DockerForMacClient→org.apache.openwhisk.core.containerpool.ContainerAddressorg.apache.openwhisk.core.containerpool.docker.DockerForMacClient→org.apache.openwhisk.core.containerpool.ContainerIdorg.apache.openwhisk.core.containerpool.docker.DockerForMacContainerFactoryProvider→org.apache.openwhisk.core.containerpool.ContainerFactoryorg.apache.openwhisk.core.containerpool.docker.DockerForMacContainerFactoryProvider→org.apache.openwhisk.core.containerpool.ContainerFactoryProviderorg.apache.openwhisk.core.containerpool.docker.ExtendedDockerClient→org.apache.openwhisk.core.containerpool.ContainerIdorg.apache.openwhisk.core.containerpool.docker.RuncApi→org.apache.openwhisk.core.containerpool.ContainerIdorg.apache.openwhisk.core.containerpool.docker.RuncClient→org.apache.openwhisk.core.containerpool.ContainerIdorg.apache.openwhisk.core.containerpool.docker.StandaloneDockerContainerFactory→org.apache.openwhisk.core.containerpool.Containerorg.apache.openwhisk.core.containerpool.docker.StandaloneDockerContainerFactoryProvider→org.apache.openwhisk.core.containerpool.ContainerFactory
- Direction
- core.containerpool.docker uses core.containerpool, so a change to core.containerpool can break core.containerpool.docker, while a change to core.containerpool.docker can't break core.containerpool.
- Position
- Below the diagonal: core.containerpool.docker uses a module listed above it, which is the healthy direction.
32→10 core.containerpool.docker uses core.entity✕
- Connections
- 10 pairs of types, where a type in core.containerpool.docker uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.containerpool.docker.DockerCliLogStore→org.apache.openwhisk.core.entity.ActivationLogsorg.apache.openwhisk.core.containerpool.docker.DockerCliLogStore→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.containerpool.docker.DockerCliLogStore→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.containerpool.docker.DockerCliLogStore→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.containerpool.docker.DockerContainer→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.docker.DockerContainerFactory→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.docker.DockerContainerFactoryProvider→org.apache.openwhisk.core.entity.InvokerInstanceIdorg.apache.openwhisk.core.containerpool.docker.DockerForMacContainerFactoryProvider→org.apache.openwhisk.core.entity.InvokerInstanceIdorg.apache.openwhisk.core.containerpool.docker.StandaloneDockerContainerFactory→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.docker.StandaloneDockerContainerFactoryProvider→org.apache.openwhisk.core.entity.InvokerInstanceId
- Direction
- core.containerpool.docker uses core.entity, so a change to core.entity can break core.containerpool.docker, while a change to core.containerpool.docker can't break core.entity.
- Position
- Below the diagonal: core.containerpool.docker uses a module listed above it, which is the healthy direction.
32→11 core.containerpool.docker uses core✕
- Connections
- 5 pairs of types, where a type in core.containerpool.docker uses a type in core.
- The types involved
org.apache.openwhisk.core.containerpool.docker.DockerContainerFactory→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.containerpool.docker.DockerContainerFactoryProvider→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.containerpool.docker.DockerForMacContainerFactoryProvider→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.containerpool.docker.StandaloneDockerContainerFactory→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.containerpool.docker.StandaloneDockerContainerFactoryProvider→org.apache.openwhisk.core.WhiskConfig
- Direction
- core.containerpool.docker uses core, so a change to core can break core.containerpool.docker, while a change to core.containerpool.docker can't break core.
- Position
- Below the diagonal: core.containerpool.docker uses a module listed above it, which is the healthy direction.
32→15 core.containerpool.docker uses common✕
- Connections
- 17 pairs of types, where a type in core.containerpool.docker uses a type in common.
- The types involved
org.apache.openwhisk.core.containerpool.docker.DockerApi→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.docker.DockerCliLogStore→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.docker.DockerClient→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.docker.DockerClientWithFileAccess→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.docker.DockerContainer→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.containerpool.docker.DockerContainer→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.docker.DockerContainerFactory→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.containerpool.docker.DockerContainerFactory→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.docker.DockerContainerFactoryProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.containerpool.docker.DockerForMacClient→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.docker.DockerForMacContainerFactoryProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.containerpool.docker.ExtendedDockerClient→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.docker.RuncApi→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.docker.RuncClient→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.docker.StandaloneDockerContainerFactory→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.containerpool.docker.StandaloneDockerContainerFactory→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.docker.StandaloneDockerContainerFactoryProvider→org.apache.openwhisk.common.Logging
- Direction
- core.containerpool.docker uses common, so a change to common can break core.containerpool.docker, while a change to core.containerpool.docker can't break common.
- Position
- Below the diagonal: core.containerpool.docker uses a module listed above it, which is the healthy direction.
32→19 core.containerpool.docker uses core.containerpool.logging✕
- Connections
- 3 pairs of types, where a type in core.containerpool.docker uses a type in core.containerpool.logging.
- The types involved
org.apache.openwhisk.core.containerpool.docker.DockerCliLogStore→org.apache.openwhisk.core.containerpool.logging.DockerToActivationLogStoreorg.apache.openwhisk.core.containerpool.docker.DockerCliLogStoreProvider→org.apache.openwhisk.core.containerpool.logging.LogStoreorg.apache.openwhisk.core.containerpool.docker.DockerCliLogStoreProvider→org.apache.openwhisk.core.containerpool.logging.LogStoreProvider
- Direction
- core.containerpool.docker uses core.containerpool.logging, so a change to core.containerpool.logging can break core.containerpool.docker, while a change to core.containerpool.docker can't break core.containerpool.logging.
- Position
- Below the diagonal: core.containerpool.docker uses a module listed above it, which is the healthy direction.
33→1 core.controller uses spi✕
- Connections
- 1 pair of types, where a type in core.controller uses a type in spi.
- The types involved
org.apache.openwhisk.core.controller.AuthenticationDirectiveProvider→org.apache.openwhisk.spi.Spi
- Direction
- core.controller uses spi, so a change to spi can break core.controller, while a change to core.controller can't break spi.
- Position
- Below the diagonal: core.controller uses a module listed above it, which is the healthy direction.
33→3 core.controller uses http✕
- Connections
- 2 pairs of types, where a type in core.controller uses a type in http.
- The types involved
org.apache.openwhisk.core.controller.Controller→org.apache.openwhisk.http.BasicRasServiceorg.apache.openwhisk.core.controller.RejectRequest→org.apache.openwhisk.http.ErrorResponse
- Direction
- core.controller uses http, so a change to http can break core.controller, while a change to core.controller can't break http.
- Position
- Below the diagonal: core.controller uses a module listed above it, which is the healthy direction.
33→4 core.controller uses core.database✕
- Connections
- 9 pairs of types, where a type in core.controller uses a type in core.database.
- The types involved
org.apache.openwhisk.core.controller.RestAPIVersion→org.apache.openwhisk.core.database.ActivationStoreorg.apache.openwhisk.core.controller.RestAPIVersion→org.apache.openwhisk.core.database.CacheChangeNotificationorg.apache.openwhisk.core.controller.WhiskPackagesApi→org.apache.openwhisk.core.database.CacheChangeNotificationorg.apache.openwhisk.core.controller.WhiskRulesApi→org.apache.openwhisk.core.database.CacheChangeNotificationorg.apache.openwhisk.core.controller.WhiskTriggersApi→org.apache.openwhisk.core.database.ActivationStoreorg.apache.openwhisk.core.controller.WhiskTriggersApi→org.apache.openwhisk.core.database.CacheChangeNotificationorg.apache.openwhisk.core.controller.WriteOps→org.apache.openwhisk.core.database.ArtifactStoreorg.apache.openwhisk.core.controller.WriteOps→org.apache.openwhisk.core.database.CacheChangeNotificationorg.apache.openwhisk.core.controller.WriteOps→org.apache.openwhisk.core.database.DocumentFactory
- Direction
- core.controller uses core.database, so a change to core.database can break core.controller, while a change to core.controller can't break core.database.
- Position
- Below the diagonal: core.controller uses a module listed above it, which is the healthy direction.
33→8 core.controller uses core.loadBalancer✕
- Connections
- 2 pairs of types, where a type in core.controller uses a type in core.loadBalancer.
- The types involved
org.apache.openwhisk.core.controller.RestAPIVersion→org.apache.openwhisk.core.loadBalancer.LoadBalancerorg.apache.openwhisk.core.controller.WhiskServices→org.apache.openwhisk.core.loadBalancer.LoadBalancer
- Direction
- core.controller uses core.loadBalancer, so a change to core.loadBalancer can break core.controller, while a change to core.controller can't break core.loadBalancer.
- Position
- Below the diagonal: core.controller uses a module listed above it, which is the healthy direction.
33→9 core.controller uses core.entitlement✕
- Connections
- 13 pairs of types, where a type in core.controller uses a type in core.entitlement.
- The types involved
org.apache.openwhisk.core.controller.BasicAuthorizedRouteProvider→org.apache.openwhisk.core.entitlement.Collectionorg.apache.openwhisk.core.controller.BasicAuthorizedRouteProvider→org.apache.openwhisk.core.entitlement.EntitlementProviderorg.apache.openwhisk.core.controller.BasicAuthorizedRouteProvider→org.apache.openwhisk.core.entitlement.Privilegeorg.apache.openwhisk.core.controller.BasicAuthorizedRouteProvider→org.apache.openwhisk.core.entitlement.Resourceorg.apache.openwhisk.core.controller.RestAPIVersion→org.apache.openwhisk.core.entitlement.EntitlementProviderorg.apache.openwhisk.core.controller.RestApiCommons→org.apache.openwhisk.core.entitlement.Collectionorg.apache.openwhisk.core.controller.WhiskCollectionAPI→org.apache.openwhisk.core.entitlement.Privilegeorg.apache.openwhisk.core.controller.WhiskCollectionAPI→org.apache.openwhisk.core.entitlement.Resourceorg.apache.openwhisk.core.controller.WhiskLimitsApi→org.apache.openwhisk.core.entitlement.Privilegeorg.apache.openwhisk.core.controller.WhiskLimitsApi→org.apache.openwhisk.core.entitlement.Resourceorg.apache.openwhisk.core.controller.WhiskPackagesApi→org.apache.openwhisk.core.entitlement.ReferencedEntitiesorg.apache.openwhisk.core.controller.WhiskRulesApi→org.apache.openwhisk.core.entitlement.ReferencedEntitiesorg.apache.openwhisk.core.controller.WhiskServices→org.apache.openwhisk.core.entitlement.EntitlementProvider
- Direction
- core.controller uses core.entitlement, so a change to core.entitlement can break core.controller, while a change to core.controller can't break core.entitlement.
- Position
- Below the diagonal: core.controller uses a module listed above it, which is the healthy direction.
33→10 core.controller uses core.entity✕
- Connections
- 46 pairs of types, where a type in core.controller uses a type in core.entity. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.apache.openwhisk.core.controller.AuthenticatedRouteProvider→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.controller.AuthenticationDirectiveProvider→org.apache.openwhisk.core.entity.EntityNameorg.apache.openwhisk.core.controller.AuthenticationDirectiveProvider→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.controller.AuthorizedRouteProvider→org.apache.openwhisk.core.entity.EntityPathorg.apache.openwhisk.core.controller.AuthorizedRouteProvider→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.controller.BasicAuthenticationDirective→org.apache.openwhisk.core.entity.EntityNameorg.apache.openwhisk.core.controller.BasicAuthenticationDirective→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.controller.BasicAuthorizedRouteProvider→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.controller.Context→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.controller.Controller→org.apache.openwhisk.core.entity.ControllerInstanceIdorg.apache.openwhisk.core.controller.CustomHeaders→org.apache.openwhisk.core.entity.ActivationIdorg.apache.openwhisk.core.controller.ReadOps→org.apache.openwhisk.core.entity.DocIdorg.apache.openwhisk.core.controller.RestAPIVersion→org.apache.openwhisk.core.entity.ControllerInstanceIdorg.apache.openwhisk.core.controller.ValidateRequestSize→org.apache.openwhisk.core.entity.UserLimitsorg.apache.openwhisk.core.controller.WhiskActionsApi→org.apache.openwhisk.core.entity.Execorg.apache.openwhisk.core.controller.WhiskActionsApi→org.apache.openwhisk.core.entity.Parametersorg.apache.openwhisk.core.controller.WhiskActivationsApi→org.apache.openwhisk.core.entity.EntityPathorg.apache.openwhisk.core.controller.WhiskCollectionAPI→org.apache.openwhisk.core.entity.EntityPathorg.apache.openwhisk.core.controller.WhiskCollectionAPI→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.controller.WhiskCollectionAPI→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.controller.WhiskCollectionAPI→org.apache.openwhisk.core.entity.Parametersorg.apache.openwhisk.core.controller.WhiskLimitsApi→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.controller.WhiskNamespacesApi→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.controller.WhiskPackagesApi→org.apache.openwhisk.core.entity.Bindingorg.apache.openwhisk.core.controller.WhiskPackagesApi→org.apache.openwhisk.core.entity.EntityPath
- Direction
- core.controller uses core.entity, so a change to core.entity can break core.controller, while a change to core.controller can't break core.entity.
- Position
- Below the diagonal: core.controller uses a module listed above it, which is the healthy direction.
33→11 core.controller uses core✕
- Connections
- 4 pairs of types, where a type in core.controller uses a type in core.
- The types involved
org.apache.openwhisk.core.controller.Controller→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.controller.RestAPIVersion→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.controller.WhiskLimitsApi→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.controller.WhiskServices→org.apache.openwhisk.core.WhiskConfig
- Direction
- core.controller uses core, so a change to core can break core.controller, while a change to core.controller can't break core.
- Position
- Below the diagonal: core.controller uses a module listed above it, which is the healthy direction.
33→12 core.controller uses core.entity.ActivationId✕
- Connections
- 2 pairs of types, where a type in core.controller uses a type in core.entity.ActivationId.
- The types involved
org.apache.openwhisk.core.controller.RestAPIVersion→org.apache.openwhisk.core.entity.ActivationId.ActivationIdGeneratororg.apache.openwhisk.core.controller.WhiskServices→org.apache.openwhisk.core.entity.ActivationId.ActivationIdGenerator
- Direction
- core.controller uses core.entity.ActivationId, so a change to core.entity.ActivationId can break core.controller, while a change to core.controller can't break core.entity.ActivationId.
- Position
- Below the diagonal: core.controller uses a module listed above it, which is the healthy direction.
33→15 core.controller uses common✕
- Connections
- 23 pairs of types, where a type in core.controller uses a type in common.
- The types involved
org.apache.openwhisk.core.controller.AuthenticatedRouteProvider→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.AuthenticationDirectiveProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.controller.AuthenticationDirectiveProvider→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.AuthorizedRouteProvider→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.BasicAuthenticationDirective→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.controller.BasicAuthenticationDirective→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.BasicAuthorizedRouteProvider→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.Controller→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.controller.Controller→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.ReadOps→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.controller.ReadOps→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.RestAPIVersion→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.controller.RestAPIVersion→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.ValidateRequestSize→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.WhiskCollectionAPI→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.WhiskLimitsApi→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.WhiskNamespacesApi→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.WhiskPackagesApi→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.WhiskRulesApi→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.WhiskTriggersApi→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.WhiskWebActionsApi→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.controller.WriteOps→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.controller.WriteOps→org.apache.openwhisk.common.TransactionId
- Direction
- core.controller uses common, so a change to common can break core.controller, while a change to core.controller can't break common.
- Position
- Below the diagonal: core.controller uses a module listed above it, which is the healthy direction.
33→19 core.controller uses core.containerpool.logging✕
- Connections
- 1 pair of types, where a type in core.controller uses a type in core.containerpool.logging.
- The types involved
org.apache.openwhisk.core.controller.RestAPIVersion→org.apache.openwhisk.core.containerpool.logging.LogStore
- Direction
- core.controller uses core.containerpool.logging, so a change to core.containerpool.logging can break core.controller, while a change to core.controller can't break core.containerpool.logging.
- Position
- Below the diagonal: core.controller uses a module listed above it, which is the healthy direction.
34→1 core.invoker uses spi✕
- Connections
- 2 pairs of types, where a type in core.invoker uses a type in spi.
- The types involved
org.apache.openwhisk.core.invoker.InvokerProvider→org.apache.openwhisk.spi.Spiorg.apache.openwhisk.core.invoker.InvokerServerProvider→org.apache.openwhisk.spi.Spi
- Direction
- core.invoker uses spi, so a change to spi can break core.invoker, while a change to core.invoker can't break spi.
- Position
- Below the diagonal: core.invoker uses a module listed above it, which is the healthy direction.
34→3 core.invoker uses http✕
- Connections
- 3 pairs of types, where a type in core.invoker uses a type in http.
- The types involved
org.apache.openwhisk.core.invoker.DefaultInvokerServer→org.apache.openwhisk.http.BasicRasServiceorg.apache.openwhisk.core.invoker.FPCInvokerServer→org.apache.openwhisk.http.BasicRasServiceorg.apache.openwhisk.core.invoker.InvokerServerProvider→org.apache.openwhisk.http.BasicRasService
- Direction
- core.invoker uses http, so a change to http can break core.invoker, while a change to core.invoker can't break http.
- Position
- Below the diagonal: core.invoker uses a module listed above it, which is the healthy direction.
34→7 core.invoker uses core.containerpool✕
- Connections
- 4 pairs of types, where a type in core.invoker uses a type in core.containerpool.
- The types involved
org.apache.openwhisk.core.invoker.FPCInvokerReactive→org.apache.openwhisk.core.containerpool.ContainerPoolConfigorg.apache.openwhisk.core.invoker.InvokerProvider→org.apache.openwhisk.core.containerpool.ContainerPoolConfigorg.apache.openwhisk.core.invoker.InvokerReactive→org.apache.openwhisk.core.containerpool.ContainerPoolConfigorg.apache.openwhisk.core.invoker.LogStoreCollector→org.apache.openwhisk.core.containerpool.Container
- Direction
- core.invoker uses core.containerpool, so a change to core.containerpool can break core.invoker, while a change to core.invoker can't break core.containerpool.
- Position
- Below the diagonal: core.invoker uses a module listed above it, which is the healthy direction.
34→10 core.invoker uses core.entity✕
- Connections
- 11 pairs of types, where a type in core.invoker uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.invoker.FPCInvokerReactive→org.apache.openwhisk.core.entity.IntraConcurrencyLimitConfigorg.apache.openwhisk.core.invoker.FPCInvokerReactive→org.apache.openwhisk.core.entity.InvokerInstanceIdorg.apache.openwhisk.core.invoker.InvokerProvider→org.apache.openwhisk.core.entity.IntraConcurrencyLimitConfigorg.apache.openwhisk.core.invoker.InvokerProvider→org.apache.openwhisk.core.entity.InvokerInstanceIdorg.apache.openwhisk.core.invoker.InvokerReactive→org.apache.openwhisk.core.entity.IntraConcurrencyLimitConfigorg.apache.openwhisk.core.invoker.InvokerReactive→org.apache.openwhisk.core.entity.InvokerInstanceIdorg.apache.openwhisk.core.invoker.LogStoreCollector→org.apache.openwhisk.core.entity.ActivationLogsorg.apache.openwhisk.core.invoker.LogStoreCollector→org.apache.openwhisk.core.entity.ExecutableWhiskActionorg.apache.openwhisk.core.invoker.LogStoreCollector→org.apache.openwhisk.core.entity.Identityorg.apache.openwhisk.core.invoker.LogStoreCollector→org.apache.openwhisk.core.entity.WhiskActivationorg.apache.openwhisk.core.invoker.NamespaceBlacklist→org.apache.openwhisk.core.entity.Identity
- Direction
- core.invoker uses core.entity, so a change to core.entity can break core.invoker, while a change to core.invoker can't break core.entity.
- Position
- Below the diagonal: core.invoker uses a module listed above it, which is the healthy direction.
34→11 core.invoker uses core✕
- Connections
- 3 pairs of types, where a type in core.invoker uses a type in core.
- The types involved
org.apache.openwhisk.core.invoker.FPCInvokerReactive→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.invoker.InvokerProvider→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.invoker.InvokerReactive→org.apache.openwhisk.core.WhiskConfig
- Direction
- core.invoker uses core, so a change to core can break core.invoker, while a change to core.invoker can't break core.
- Position
- Below the diagonal: core.invoker uses a module listed above it, which is the healthy direction.
34→14 core.invoker uses core.connector✕
- Connections
- 3 pairs of types, where a type in core.invoker uses a type in core.connector.
- The types involved
org.apache.openwhisk.core.invoker.FPCInvokerReactive→org.apache.openwhisk.core.connector.MessageProducerorg.apache.openwhisk.core.invoker.InvokerProvider→org.apache.openwhisk.core.connector.MessageProducerorg.apache.openwhisk.core.invoker.InvokerReactive→org.apache.openwhisk.core.connector.MessageProducer
- Direction
- core.invoker uses core.connector, so a change to core.connector can break core.invoker, while a change to core.invoker can't break core.connector.
- Position
- Below the diagonal: core.invoker uses a module listed above it, which is the healthy direction.
34→15 core.invoker uses common✕
- Connections
- 10 pairs of types, where a type in core.invoker uses a type in common.
- The types involved
org.apache.openwhisk.core.invoker.DefaultInvokerServer→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.invoker.DefaultInvokerServer→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.invoker.FPCInvokerReactive→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.invoker.FPCInvokerServer→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.invoker.FPCInvokerServer→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.invoker.InvokerProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.invoker.InvokerReactive→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.invoker.InvokerServerProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.invoker.LogStoreCollector→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.invoker.NamespaceBlacklist→org.apache.openwhisk.common.TransactionId
- Direction
- core.invoker uses common, so a change to common can break core.invoker, while a change to core.invoker can't break common.
- Position
- Below the diagonal: core.invoker uses a module listed above it, which is the healthy direction.
34→20 core.invoker uses core.containerpool.v2✕
- Connections
- 2 pairs of types, where a type in core.invoker uses a type in core.containerpool.v2.
- The types involved
org.apache.openwhisk.core.invoker.InvokerCore→org.apache.openwhisk.core.containerpool.v2.NotSupportedPoolStateorg.apache.openwhisk.core.invoker.InvokerCore→org.apache.openwhisk.core.containerpool.v2.TotalContainerPoolState
- Direction
- core.invoker uses core.containerpool.v2, so a change to core.containerpool.v2 can break core.invoker, while a change to core.invoker can't break core.containerpool.v2.
- Position
- Below the diagonal: core.invoker uses a module listed above it, which is the healthy direction.
34→28 core.invoker uses core.invoker.Invoker✕
- Connections
- 1 pair of types, where a type in core.invoker uses a type in core.invoker.Invoker.
- The types involved
org.apache.openwhisk.core.invoker.LogStoreCollector→org.apache.openwhisk.core.invoker.Invoker.LogsCollector
- Direction
- core.invoker uses core.invoker.Invoker, so a change to core.invoker.Invoker can break core.invoker, while a change to core.invoker can't break core.invoker.Invoker.
- Position
- Below the diagonal: core.invoker uses a module listed above it, which is the healthy direction.
35→14 core.monitoring.metrics uses core.connector✕
- Connections
- 8 pairs of types, where a type in core.monitoring.metrics uses a type in core.connector.
- The types involved
org.apache.openwhisk.core.monitoring.metrics.EventConsumer→org.apache.openwhisk.core.connector.Activationorg.apache.openwhisk.core.monitoring.metrics.EventConsumer→org.apache.openwhisk.core.connector.Metricorg.apache.openwhisk.core.monitoring.metrics.KamonRecorder→org.apache.openwhisk.core.connector.Activationorg.apache.openwhisk.core.monitoring.metrics.KamonRecorder→org.apache.openwhisk.core.connector.Metricorg.apache.openwhisk.core.monitoring.metrics.MetricRecorder→org.apache.openwhisk.core.connector.Activationorg.apache.openwhisk.core.monitoring.metrics.MetricRecorder→org.apache.openwhisk.core.connector.Metricorg.apache.openwhisk.core.monitoring.metrics.PrometheusRecorder→org.apache.openwhisk.core.connector.Activationorg.apache.openwhisk.core.monitoring.metrics.PrometheusRecorder→org.apache.openwhisk.core.connector.Metric
- Direction
- core.monitoring.metrics uses core.connector, so a change to core.connector can break core.monitoring.metrics, while a change to core.monitoring.metrics can't break core.connector.
- Position
- Below the diagonal: core.monitoring.metrics uses a module listed above it, which is the healthy direction.
35→16 core.monitoring.metrics uses connector.kafka✕
- Connections
- 1 pair of types, where a type in core.monitoring.metrics uses a type in connector.kafka.
- The types involved
org.apache.openwhisk.core.monitoring.metrics.EventConsumer→org.apache.openwhisk.connector.kafka.KafkaMetricsProvider
- Direction
- core.monitoring.metrics uses connector.kafka, so a change to connector.kafka can break core.monitoring.metrics, while a change to core.monitoring.metrics can't break connector.kafka.
- Position
- Below the diagonal: core.monitoring.metrics uses a module listed above it, which is the healthy direction.
36→10 core.scheduler.container uses core.entity✕
- Connections
- 9 pairs of types, where a type in core.scheduler.container uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.scheduler.container.ContainerManager→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.scheduler.container.ContainerManager→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.scheduler.container.ContainerManager→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.scheduler.container.ContainerManager→org.apache.openwhisk.core.entity.InvokerInstanceIdorg.apache.openwhisk.core.scheduler.container.CreationJobManager→org.apache.openwhisk.core.entity.CreationIdorg.apache.openwhisk.core.scheduler.container.CreationJobManager→org.apache.openwhisk.core.entity.DocRevisionorg.apache.openwhisk.core.scheduler.container.CreationJobManager→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.scheduler.container.JobEntry→org.apache.openwhisk.core.entity.FullyQualifiedEntityNameorg.apache.openwhisk.core.scheduler.container.ScheduledPair→org.apache.openwhisk.core.entity.InvokerInstanceId
- Direction
- core.scheduler.container uses core.entity, so a change to core.entity can break core.scheduler.container, while a change to core.scheduler.container can't break core.entity.
- Position
- Below the diagonal: core.scheduler.container uses a module listed above it, which is the healthy direction.
36→14 core.scheduler.container uses core.connector✕
- Connections
- 6 pairs of types, where a type in core.scheduler.container uses a type in core.connector.
- The types involved
org.apache.openwhisk.core.scheduler.container.ContainerManager→org.apache.openwhisk.core.connector.ContainerCreationMessageorg.apache.openwhisk.core.scheduler.container.ContainerManager→org.apache.openwhisk.core.connector.ContainerDeletionMessageorg.apache.openwhisk.core.scheduler.container.ContainerManager→org.apache.openwhisk.core.connector.MessageProducerorg.apache.openwhisk.core.scheduler.container.ContainerManager→org.apache.openwhisk.core.connector.ResultMetadataorg.apache.openwhisk.core.scheduler.container.ScheduledPair→org.apache.openwhisk.core.connector.ContainerCreationErrororg.apache.openwhisk.core.scheduler.container.ScheduledPair→org.apache.openwhisk.core.connector.ContainerCreationMessage
- Direction
- core.scheduler.container uses core.connector, so a change to core.connector can break core.scheduler.container, while a change to core.scheduler.container can't break core.connector.
- Position
- Below the diagonal: core.scheduler.container uses a module listed above it, which is the healthy direction.
36→15 core.scheduler.container uses common✕
- Connections
- 1 pair of types, where a type in core.scheduler.container uses a type in common.
- The types involved
org.apache.openwhisk.core.scheduler.container.ContainerManager→org.apache.openwhisk.common.Logging
- Direction
- core.scheduler.container uses common, so a change to common can break core.scheduler.container, while a change to core.scheduler.container can't break common.
- Position
- Below the diagonal: core.scheduler.container uses a module listed above it, which is the healthy direction.
36→29 core.scheduler.container uses core.scheduler.message✕
- Connections
- 2 pairs of types, where a type in core.scheduler.container uses a type in core.scheduler.message.
- The types involved
org.apache.openwhisk.core.scheduler.container.ContainerManager→org.apache.openwhisk.core.scheduler.message.ContainerKeyMetaorg.apache.openwhisk.core.scheduler.container.CreationJobManager→org.apache.openwhisk.core.scheduler.message.CreationJobState
- Direction
- core.scheduler.container uses core.scheduler.message, so a change to core.scheduler.message can break core.scheduler.container, while a change to core.scheduler.container can't break core.scheduler.message.
- Position
- Below the diagonal: core.scheduler.container uses a module listed above it, which is the healthy direction.
37→10 core.scheduler.grpc uses core.entity✕
- Connections
- 1 pair of types, where a type in core.scheduler.grpc uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.scheduler.grpc.GetActivation→org.apache.openwhisk.core.entity.FullyQualifiedEntityName
- Direction
- core.scheduler.grpc uses core.entity, so a change to core.entity can break core.scheduler.grpc, while a change to core.scheduler.grpc can't break core.entity.
- Position
- Below the diagonal: core.scheduler.grpc uses a module listed above it, which is the healthy direction.
37→14 core.scheduler.grpc uses core.connector✕
- Connections
- 2 pairs of types, where a type in core.scheduler.grpc uses a type in core.connector.
- The types involved
org.apache.openwhisk.core.scheduler.grpc.ActivationResponse→org.apache.openwhisk.core.connector.ActivationMessageorg.apache.openwhisk.core.scheduler.grpc.ActivationResponse→org.apache.openwhisk.core.connector.Message
- Direction
- core.scheduler.grpc uses core.connector, so a change to core.connector can break core.scheduler.grpc, while a change to core.scheduler.grpc can't break core.connector.
- Position
- Below the diagonal: core.scheduler.grpc uses a module listed above it, which is the healthy direction.
37→15 core.scheduler.grpc uses common✕
- Connections
- 1 pair of types, where a type in core.scheduler.grpc uses a type in common.
- The types involved
org.apache.openwhisk.core.scheduler.grpc.GetActivation→org.apache.openwhisk.common.TransactionId
- Direction
- core.scheduler.grpc uses common, so a change to common can break core.scheduler.grpc, while a change to core.scheduler.grpc can't break common.
- Position
- Below the diagonal: core.scheduler.grpc uses a module listed above it, which is the healthy direction.
37→30 core.scheduler.grpc uses core.scheduler.queue✕
- Connections
- 1 pair of types, where a type in core.scheduler.grpc uses a type in core.scheduler.queue.
- The types involved
org.apache.openwhisk.core.scheduler.grpc.ActivationResponse→org.apache.openwhisk.core.scheduler.queue.MemoryQueueError
- Direction
- core.scheduler.grpc uses core.scheduler.queue, so a change to core.scheduler.queue can break core.scheduler.grpc, while a change to core.scheduler.grpc can't break core.scheduler.queue.
- Position
- Below the diagonal: core.scheduler.grpc uses a module listed above it, which is the healthy direction.
38→5 core.containerpool.kubernetes uses core.entity.ExecManifest✕
- Connections
- 1 pair of types, where a type in core.containerpool.kubernetes uses a type in core.entity.ExecManifest.
- The types involved
org.apache.openwhisk.core.containerpool.kubernetes.KubernetesContainerFactory→org.apache.openwhisk.core.entity.ExecManifest.ImageName
- Direction
- core.containerpool.kubernetes uses core.entity.ExecManifest, so a change to core.entity.ExecManifest can break core.containerpool.kubernetes, while a change to core.containerpool.kubernetes can't break core.entity.ExecManifest.
- Position
- Below the diagonal: core.containerpool.kubernetes uses a module listed above it, which is the healthy direction.
38→7 core.containerpool.kubernetes uses core.containerpool✕
- Connections
- 4 pairs of types, where a type in core.containerpool.kubernetes uses a type in core.containerpool.
- The types involved
org.apache.openwhisk.core.containerpool.kubernetes.KubernetesContainerFactory→org.apache.openwhisk.core.containerpool.Containerorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesContainerFactory→org.apache.openwhisk.core.containerpool.ContainerFactoryorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesContainerFactoryProvider→org.apache.openwhisk.core.containerpool.ContainerFactoryorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesContainerFactoryProvider→org.apache.openwhisk.core.containerpool.ContainerFactoryProvider
- Direction
- core.containerpool.kubernetes uses core.containerpool, so a change to core.containerpool can break core.containerpool.kubernetes, while a change to core.containerpool.kubernetes can't break core.containerpool.
- Position
- Below the diagonal: core.containerpool.kubernetes uses a module listed above it, which is the healthy direction.
38→10 core.containerpool.kubernetes uses core.entity✕
- Connections
- 8 pairs of types, where a type in core.containerpool.kubernetes uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.containerpool.kubernetes.KubernetesApi→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesClient→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesContainer→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesContainerFactory→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesContainerFactoryProvider→org.apache.openwhisk.core.entity.InvokerInstanceIdorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesCpuScalingConfig→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesEphemeralStorageConfig→org.apache.openwhisk.core.entity.ByteSizeorg.apache.openwhisk.core.containerpool.kubernetes.WhiskPodBuilder→org.apache.openwhisk.core.entity.ByteSize
- Direction
- core.containerpool.kubernetes uses core.entity, so a change to core.entity can break core.containerpool.kubernetes, while a change to core.containerpool.kubernetes can't break core.entity.
- Position
- Below the diagonal: core.containerpool.kubernetes uses a module listed above it, which is the healthy direction.
38→11 core.containerpool.kubernetes uses core✕
- Connections
- 2 pairs of types, where a type in core.containerpool.kubernetes uses a type in core.
- The types involved
org.apache.openwhisk.core.containerpool.kubernetes.KubernetesContainerFactory→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesContainerFactoryProvider→org.apache.openwhisk.core.WhiskConfig
- Direction
- core.containerpool.kubernetes uses core, so a change to core can break core.containerpool.kubernetes, while a change to core.containerpool.kubernetes can't break core.
- Position
- Below the diagonal: core.containerpool.kubernetes uses a module listed above it, which is the healthy direction.
38→15 core.containerpool.kubernetes uses common✕
- Connections
- 9 pairs of types, where a type in core.containerpool.kubernetes uses a type in common.
- The types involved
org.apache.openwhisk.core.containerpool.kubernetes.KubernetesApi→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesClient→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesClientConfig→org.apache.openwhisk.common.ConfigMapValueorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesContainer→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesContainer→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesContainerFactory→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesContainerFactory→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.core.containerpool.kubernetes.KubernetesContainerFactoryProvider→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.containerpool.kubernetes.WhiskPodBuilder→org.apache.openwhisk.common.TransactionId
- Direction
- core.containerpool.kubernetes uses common, so a change to common can break core.containerpool.kubernetes, while a change to core.containerpool.kubernetes can't break common.
- Position
- Below the diagonal: core.containerpool.kubernetes uses a module listed above it, which is the healthy direction.
38→32 core.containerpool.kubernetes uses core.containerpool.docker✕
- Connections
- 1 pair of types, where a type in core.containerpool.kubernetes uses a type in core.containerpool.docker.
- The types involved
org.apache.openwhisk.core.containerpool.kubernetes.KubernetesClient→org.apache.openwhisk.core.containerpool.docker.ProcessRunner
- Direction
- core.containerpool.kubernetes uses core.containerpool.docker, so a change to core.containerpool.docker can break core.containerpool.kubernetes, while a change to core.containerpool.kubernetes can't break core.containerpool.docker.
- Position
- Below the diagonal: core.containerpool.kubernetes uses a module listed above it, which is the healthy direction.
39→4 core.controller.RestAPIVersion uses core.database✕
- Connections
- 8 pairs of types, where a type in core.controller.RestAPIVersion uses a type in core.database.
- The types involved
org.apache.openwhisk.core.controller.RestAPIVersion.ActionsApi→org.apache.openwhisk.core.database.ActivationStoreorg.apache.openwhisk.core.controller.RestAPIVersion.ActionsApi→org.apache.openwhisk.core.database.CacheChangeNotificationorg.apache.openwhisk.core.controller.RestAPIVersion.ActivationsApi→org.apache.openwhisk.core.database.ActivationStoreorg.apache.openwhisk.core.controller.RestAPIVersion.PackagesApi→org.apache.openwhisk.core.database.CacheChangeNotificationorg.apache.openwhisk.core.controller.RestAPIVersion.RulesApi→org.apache.openwhisk.core.database.CacheChangeNotificationorg.apache.openwhisk.core.controller.RestAPIVersion.TriggersApi→org.apache.openwhisk.core.database.ActivationStoreorg.apache.openwhisk.core.controller.RestAPIVersion.TriggersApi→org.apache.openwhisk.core.database.CacheChangeNotificationorg.apache.openwhisk.core.controller.RestAPIVersion.WebActionsApi→org.apache.openwhisk.core.database.ActivationStore
- Direction
- core.controller.RestAPIVersion uses core.database, so a change to core.database can break core.controller.RestAPIVersion, while a change to core.controller.RestAPIVersion can't break core.database.
- Position
- Below the diagonal: core.controller.RestAPIVersion uses a module listed above it, which is the healthy direction.
39→8 core.controller.RestAPIVersion uses core.loadBalancer✕
- Connections
- 5 pairs of types, where a type in core.controller.RestAPIVersion uses a type in core.loadBalancer.
- The types involved
org.apache.openwhisk.core.controller.RestAPIVersion.ActionsApi→org.apache.openwhisk.core.loadBalancer.LoadBalancerorg.apache.openwhisk.core.controller.RestAPIVersion.PackagesApi→org.apache.openwhisk.core.loadBalancer.LoadBalancerorg.apache.openwhisk.core.controller.RestAPIVersion.RulesApi→org.apache.openwhisk.core.loadBalancer.LoadBalancerorg.apache.openwhisk.core.controller.RestAPIVersion.TriggersApi→org.apache.openwhisk.core.loadBalancer.LoadBalancerorg.apache.openwhisk.core.controller.RestAPIVersion.WebActionsApi→org.apache.openwhisk.core.loadBalancer.LoadBalancer
- Direction
- core.controller.RestAPIVersion uses core.loadBalancer, so a change to core.loadBalancer can break core.controller.RestAPIVersion, while a change to core.controller.RestAPIVersion can't break core.loadBalancer.
- Position
- Below the diagonal: core.controller.RestAPIVersion uses a module listed above it, which is the healthy direction.
39→9 core.controller.RestAPIVersion uses core.entitlement✕
- Connections
- 7 pairs of types, where a type in core.controller.RestAPIVersion uses a type in core.entitlement.
- The types involved
org.apache.openwhisk.core.controller.RestAPIVersion.ActionsApi→org.apache.openwhisk.core.entitlement.EntitlementProviderorg.apache.openwhisk.core.controller.RestAPIVersion.ActivationsApi→org.apache.openwhisk.core.entitlement.EntitlementProviderorg.apache.openwhisk.core.controller.RestAPIVersion.LimitsApi→org.apache.openwhisk.core.entitlement.EntitlementProviderorg.apache.openwhisk.core.controller.RestAPIVersion.PackagesApi→org.apache.openwhisk.core.entitlement.EntitlementProviderorg.apache.openwhisk.core.controller.RestAPIVersion.RulesApi→org.apache.openwhisk.core.entitlement.EntitlementProviderorg.apache.openwhisk.core.controller.RestAPIVersion.TriggersApi→org.apache.openwhisk.core.entitlement.EntitlementProviderorg.apache.openwhisk.core.controller.RestAPIVersion.WebActionsApi→org.apache.openwhisk.core.entitlement.EntitlementProvider
- Direction
- core.controller.RestAPIVersion uses core.entitlement, so a change to core.entitlement can break core.controller.RestAPIVersion, while a change to core.controller.RestAPIVersion can't break core.entitlement.
- Position
- Below the diagonal: core.controller.RestAPIVersion uses a module listed above it, which is the healthy direction.
39→10 core.controller.RestAPIVersion uses core.entity✕
- Connections
- 2 pairs of types, where a type in core.controller.RestAPIVersion uses a type in core.entity.
- The types involved
org.apache.openwhisk.core.controller.RestAPIVersion.ActionsApi→org.apache.openwhisk.core.entity.ControllerInstanceIdorg.apache.openwhisk.core.controller.RestAPIVersion.WebActionsApi→org.apache.openwhisk.core.entity.ControllerInstanceId
- Direction
- core.controller.RestAPIVersion uses core.entity, so a change to core.entity can break core.controller.RestAPIVersion, while a change to core.controller.RestAPIVersion can't break core.entity.
- Position
- Below the diagonal: core.controller.RestAPIVersion uses a module listed above it, which is the healthy direction.
39→11 core.controller.RestAPIVersion uses core✕
- Connections
- 6 pairs of types, where a type in core.controller.RestAPIVersion uses a type in core.
- The types involved
org.apache.openwhisk.core.controller.RestAPIVersion.ActionsApi→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.controller.RestAPIVersion.LimitsApi→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.controller.RestAPIVersion.PackagesApi→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.controller.RestAPIVersion.RulesApi→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.controller.RestAPIVersion.TriggersApi→org.apache.openwhisk.core.WhiskConfigorg.apache.openwhisk.core.controller.RestAPIVersion.WebActionsApi→org.apache.openwhisk.core.WhiskConfig
- Direction
- core.controller.RestAPIVersion uses core, so a change to core can break core.controller.RestAPIVersion, while a change to core.controller.RestAPIVersion can't break core.
- Position
- Below the diagonal: core.controller.RestAPIVersion uses a module listed above it, which is the healthy direction.
39→12 core.controller.RestAPIVersion uses core.entity.ActivationId✕
- Connections
- 5 pairs of types, where a type in core.controller.RestAPIVersion uses a type in core.entity.ActivationId.
- The types involved
org.apache.openwhisk.core.controller.RestAPIVersion.ActionsApi→org.apache.openwhisk.core.entity.ActivationId.ActivationIdGeneratororg.apache.openwhisk.core.controller.RestAPIVersion.PackagesApi→org.apache.openwhisk.core.entity.ActivationId.ActivationIdGeneratororg.apache.openwhisk.core.controller.RestAPIVersion.RulesApi→org.apache.openwhisk.core.entity.ActivationId.ActivationIdGeneratororg.apache.openwhisk.core.controller.RestAPIVersion.TriggersApi→org.apache.openwhisk.core.entity.ActivationId.ActivationIdGeneratororg.apache.openwhisk.core.controller.RestAPIVersion.WebActionsApi→org.apache.openwhisk.core.entity.ActivationId.ActivationIdGenerator
- Direction
- core.controller.RestAPIVersion uses core.entity.ActivationId, so a change to core.entity.ActivationId can break core.controller.RestAPIVersion, while a change to core.controller.RestAPIVersion can't break core.entity.ActivationId.
- Position
- Below the diagonal: core.controller.RestAPIVersion uses a module listed above it, which is the healthy direction.
39→15 core.controller.RestAPIVersion uses common✕
- Connections
- 6 pairs of types, where a type in core.controller.RestAPIVersion uses a type in common.
- The types involved
org.apache.openwhisk.core.controller.RestAPIVersion.ActionsApi→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.controller.RestAPIVersion.ActivationsApi→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.controller.RestAPIVersion.PackagesApi→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.controller.RestAPIVersion.RulesApi→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.controller.RestAPIVersion.TriggersApi→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.core.controller.RestAPIVersion.WebActionsApi→org.apache.openwhisk.common.Logging
- Direction
- core.controller.RestAPIVersion uses common, so a change to common can break core.controller.RestAPIVersion, while a change to core.controller.RestAPIVersion can't break common.
- Position
- Below the diagonal: core.controller.RestAPIVersion uses a module listed above it, which is the healthy direction.
39→19 core.controller.RestAPIVersion uses core.containerpool.logging✕
- Connections
- 1 pair of types, where a type in core.controller.RestAPIVersion uses a type in core.containerpool.logging.
- The types involved
org.apache.openwhisk.core.controller.RestAPIVersion.ActivationsApi→org.apache.openwhisk.core.containerpool.logging.LogStore
- Direction
- core.controller.RestAPIVersion uses core.containerpool.logging, so a change to core.containerpool.logging can break core.controller.RestAPIVersion, while a change to core.controller.RestAPIVersion can't break core.containerpool.logging.
- Position
- Below the diagonal: core.controller.RestAPIVersion uses a module listed above it, which is the healthy direction.
39→33 core.controller.RestAPIVersion uses core.controller✕
- Connections
- 14 pairs of types, where a type in core.controller.RestAPIVersion uses a type in core.controller.
- The types involved
org.apache.openwhisk.core.controller.RestAPIVersion.ActionsApi→org.apache.openwhisk.core.controller.WhiskActionsApiorg.apache.openwhisk.core.controller.RestAPIVersion.ActionsApi→org.apache.openwhisk.core.controller.WhiskServicesorg.apache.openwhisk.core.controller.RestAPIVersion.ActivationsApi→org.apache.openwhisk.core.controller.WhiskActivationsApiorg.apache.openwhisk.core.controller.RestAPIVersion.LimitsApi→org.apache.openwhisk.core.controller.WhiskLimitsApiorg.apache.openwhisk.core.controller.RestAPIVersion.NamespacesApi→org.apache.openwhisk.core.controller.WhiskNamespacesApiorg.apache.openwhisk.core.controller.RestAPIVersion.PackagesApi→org.apache.openwhisk.core.controller.WhiskPackagesApiorg.apache.openwhisk.core.controller.RestAPIVersion.PackagesApi→org.apache.openwhisk.core.controller.WhiskServicesorg.apache.openwhisk.core.controller.RestAPIVersion.RulesApi→org.apache.openwhisk.core.controller.WhiskRulesApiorg.apache.openwhisk.core.controller.RestAPIVersion.RulesApi→org.apache.openwhisk.core.controller.WhiskServicesorg.apache.openwhisk.core.controller.RestAPIVersion.TriggersApi→org.apache.openwhisk.core.controller.WhiskServicesorg.apache.openwhisk.core.controller.RestAPIVersion.TriggersApi→org.apache.openwhisk.core.controller.WhiskTriggersApiorg.apache.openwhisk.core.controller.RestAPIVersion.WebActionsApi→org.apache.openwhisk.core.controller.WebApiDirectivesorg.apache.openwhisk.core.controller.RestAPIVersion.WebActionsApi→org.apache.openwhisk.core.controller.WhiskServicesorg.apache.openwhisk.core.controller.RestAPIVersion.WebActionsApi→org.apache.openwhisk.core.controller.WhiskWebActionsApi
- Direction
- core.controller.RestAPIVersion uses core.controller, so a change to core.controller can break core.controller.RestAPIVersion, while a change to core.controller.RestAPIVersion can't break core.controller.
- Position
- Below the diagonal: core.controller.RestAPIVersion uses a module listed above it, which is the healthy direction.
40→4 standalone uses core.database✕
- Connections
- 2 pairs of types, where a type in standalone uses a type in core.database.
- The types involved
org.apache.openwhisk.standalone.CouchDBLauncher→org.apache.openwhisk.core.database.CouchDbRestClientorg.apache.openwhisk.standalone.NonEscapingClient→org.apache.openwhisk.core.database.CouchDbRestClient
- Direction
- standalone uses core.database, so a change to core.database can break standalone, while a change to standalone can't break core.database.
- Position
- Below the diagonal: standalone uses a module listed above it, which is the healthy direction.
40→7 standalone uses core.containerpool✕
- Connections
- 2 pairs of types, where a type in standalone uses a type in core.containerpool.
- The types involved
org.apache.openwhisk.standalone.StandaloneDockerContainer→org.apache.openwhisk.core.containerpool.ContainerAddressorg.apache.openwhisk.standalone.StandaloneDockerContainer→org.apache.openwhisk.core.containerpool.ContainerId
- Direction
- standalone uses core.containerpool, so a change to core.containerpool can break standalone, while a change to standalone can't break core.containerpool.
- Position
- Below the diagonal: standalone uses a module listed above it, which is the healthy direction.
40→8 standalone uses core.loadBalancer✕
- Connections
- 2 pairs of types, where a type in standalone uses a type in core.loadBalancer.
- The types involved
org.apache.openwhisk.standalone.KafkaAwareLeanBalancer→org.apache.openwhisk.core.loadBalancer.LoadBalancerorg.apache.openwhisk.standalone.KafkaAwareLeanBalancer→org.apache.openwhisk.core.loadBalancer.LoadBalancerProvider
- Direction
- standalone uses core.loadBalancer, so a change to core.loadBalancer can break standalone, while a change to standalone can't break core.loadBalancer.
- Position
- Below the diagonal: standalone uses a module listed above it, which is the healthy direction.
40→10 standalone uses core.entity✕
- Connections
- 1 pair of types, where a type in standalone uses a type in core.entity.
- The types involved
org.apache.openwhisk.standalone.KafkaAwareLeanBalancer→org.apache.openwhisk.core.entity.ControllerInstanceId
- Direction
- standalone uses core.entity, so a change to core.entity can break standalone, while a change to standalone can't break core.entity.
- Position
- Below the diagonal: standalone uses a module listed above it, which is the healthy direction.
40→11 standalone uses core✕
- Connections
- 1 pair of types, where a type in standalone uses a type in core.
- The types involved
org.apache.openwhisk.standalone.KafkaAwareLeanBalancer→org.apache.openwhisk.core.WhiskConfig
- Direction
- standalone uses core, so a change to core can break standalone, while a change to standalone can't break core.
- Position
- Below the diagonal: standalone uses a module listed above it, which is the healthy direction.
40→15 standalone uses common✕
- Connections
- 7 pairs of types, where a type in standalone uses a type in common.
- The types involved
org.apache.openwhisk.standalone.ColoredPekkoLogging→org.apache.openwhisk.common.PekkoLoggingorg.apache.openwhisk.standalone.ColoredPekkoLogging→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.standalone.InstallRouteMgmt→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.standalone.InstallRouteMgmt→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.standalone.KafkaAwareLeanBalancer→org.apache.openwhisk.common.Loggingorg.apache.openwhisk.standalone.StandaloneDockerClient→org.apache.openwhisk.common.TransactionIdorg.apache.openwhisk.standalone.StandaloneOpenWhisk→org.apache.openwhisk.common.Logging
- Direction
- standalone uses common, so a change to common can break standalone, while a change to standalone can't break common.
- Position
- Below the diagonal: standalone uses a module listed above it, which is the healthy direction.
40→32 standalone uses core.containerpool.docker✕
- Connections
- 3 pairs of types, where a type in standalone uses a type in core.containerpool.docker.
- The types involved
org.apache.openwhisk.standalone.StandaloneDockerClient→org.apache.openwhisk.core.containerpool.docker.DockerClientorg.apache.openwhisk.standalone.StandaloneDockerClient→org.apache.openwhisk.core.containerpool.docker.DockerClientConfigorg.apache.openwhisk.standalone.StandaloneDockerClient→org.apache.openwhisk.core.containerpool.docker.WindowsDockerClient
- Direction
- standalone uses core.containerpool.docker, so a change to core.containerpool.docker can break standalone, while a change to standalone can't break core.containerpool.docker.
- Position
- Below the diagonal: standalone uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 108 | High / Critical |
| A05:2025 — Injection | 59 | High / Critical |
| A07:2025 — Authentication Failures | 6 | High / Critical |
Roadmap
Top priorities: Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package; Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED. | +2.5 pts | Low | REDACTED Scanning |
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +3.1 pts | Medium | Type Safety |
| Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package. | +3.1 pts | Medium | Large Files |
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +2.2 pts | Medium | Text alternatives |
| Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5. | +2.1 pts | Medium | Cyclomatic Complexity |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +1.8 pts | Medium | Page structure |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +1.6 pts | Medium | Forms & labels |
| Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge. | +1.6 pts | Medium | A11y enforcement |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 0.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.9 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.2 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/FunctionPullingContainerProxy.scala | 5.6 | Mixed | Cyclomatic Complexity: FunctionPullingContainerProxy.initializeAndRunActivation (cyclomatic 19) |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
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 57 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 — 57 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, 611 of 627 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — 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. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- 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 — 17 Maven/Gradle manifest(s) were read, stating a version for 76 dependency(ies) and leaving 97 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. 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 Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D17 Explicit Debt — 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. The 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .scala (47,081 lines, 96% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 33 task marker(s) (TODO/FIXME/HACK/XXX) across 25 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- 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 — 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. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — 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 source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D31 IaC & Container Security — 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. Tools/actionProxy/Dockerfile carries no `FROM` instruction, so it declares no build stage and every REDACTED rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 42 of 43 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
- D39 IL Efficiency — 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. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in core/standalone/src/main/scala/org/apache/openwhisk/standalone/StandaloneDockerSupport.scala, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — -------------------- 16 | # 17 | ARG BASE=scala 18 | >>> FROM ${BASE} 19 | ARG OPENWHISK_JAR 20 | ARG TARGETPLATFORM -------------------- ERROR: failed to solve: scala: failed to resolve source metadata for docker.io/library/scala:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — 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. 'com.sksamuel.elastic4s' is imported (core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/ElasticSearchDurationChecker.scala:20), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — 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. 'com.sksamuel.elastic4s' is imported (core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/ElasticSearchDurationChecker.scala:20), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — 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. 'com.sksamuel.elastic4s' is imported (core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/ElasticSearchDurationChecker.scala:20), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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 this repository's Python, Scala is most of its product and 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X1 Async correctness — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X12 Unreachable branch — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X13 Undrained process stream — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X14 Bypassable address classification — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X15 Unvalidated length from an untrusted reader — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X16 Unfloored truncation loop — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X17 Uncapped recursion over a caller-supplied document — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X18 Disposal-pattern correctness — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X19 Unrestored process-global state — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X2 Cancellation propagation — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X21 Side-effecting pattern guard — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X22 Contradicted release guard — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X25 Inert configuration knob — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X26 Unsynchronised callback handoff — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X29 Per-element action decided by a fixed element — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X3 Exception handling — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X30 Support guard that admits what it rejects — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X32 Type resolved by simple name across every loaded assembly — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X4 Structured logging — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
- X5 Nullable reference types — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
23 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SchedulingDecisionMaker.decide at 33.
What to do
- Bring the 16 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SchedulingDecisionMaker.decide (cyclomatic 33), FunctionPullingContainerPool.receive (cyclomatic 31), QueueManager.receive (cyclomatic 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 16 together lifts Cyclomatic Complexity from 7.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
59 method(s) exceeded the cognitive complexity threshold of 15; the worst was SchedulingDecisionMaker.decide at 77.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with SchedulingDecisionMaker.decide (cognitive 77). — Refactoring it lifts Cognitive Complexity from 6.3 to about 6.5/10.
D3 · God Classes
10 god class(es) detected.
What to do
- Resolve the 6 FileTooLong finding(s) in God Classes — start with FunctionPullingContainerProxy.scala, MemoryQueue.scala, ContainerProxy.scala. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with ErrorResponse.scala, StandaloneOpenWhisk.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with createApi.js, deleteApi.js. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
44 duplicated block group(s) detected. A further 8 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 5 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with WhiskAction.scala, InvokerSupervision.scala, FunctionPullingContainerProxy.scala. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with ApiUtils.scala, CommonLoadBalancer.scala, ContainerPool.scala. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with CouchDbRestStore.scala, WhiskAction.scala, PoolingRestClient.scala. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
18 production modules (Gradle+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 10 of the 18 (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).
D6 · Cohesion (LCOM4)
2 of 98 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with FunctionPullingContainerProxy.scala, InvokerHealthManager.scala. — One of this dimension's main actionable groups (2 warning-level).
D9 · Test Distribution
1883 test methods: 1882 unit, 0 integration, 0 BDD, 1 e2e. The Scala suite contributes 1883 test case(s) across 192 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D13 · REDACTED Scanning
2 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
D14 · License Compliance
0 of 86 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 1 direct `PackageReference`(s), and 85 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Gradle build (build.gradle/build.gradle.kts), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is core/standalone/src/main/scala/org/apache/openwhisk/standalone/LogbackConfigurator.scala. Counted over 192 of the 295 production source files in this repository: 67 are under the ~2,400-byte size floor this dimension measures over, and the remaining 36 have no attributable history left to measure.
D17 · Explicit Debt
0 deducted debt markers + 0 dead symbols across 0 LoC in the .NET projects (0.0/KLoC) → score 10.0. Measured on the .NET source only: .scala (96% of production source) was not read, and carries at least 33 uncounted task marker(s) in 25 file(s).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 68 document(s) read across 2 unit(s).
D24 · Comment Value
4 of 271 judged comments only repeat the code they sit on (1.5 %). 8 comment(s) in another language or script were not judged.
What to do
- Resolve the 4 redundant comment finding(s) in Comment Value — start with REDACTED (2), apigw-utils.js, owperf.js. — One of this dimension's main actionable groups (4 recommendation-level).
D28 · Secrets (history)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
59 finding(s): 0 critical, 51 high, 5 medium, 3 low. 7 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `core/standalone/start.sh` (lines 27–30), `gradlew` (line 177) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 7 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 39 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (9), REDACTED (6), REDACTED (6). — One of this dimension's main actionable groups (39 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 7 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 (7 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
108 finding(s): 0 critical, 21 high, 70 medium, 17 low.
What to do
- Resolve the 70 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (29), REDACTED (13), REDACTED (6). — One of this dimension's main actionable groups (70 warning-level).
- Resolve the 21 High IaC finding(s) in IaC & Container Security — start with REDACTED (12), REDACTED (5), REDACTED (3). — One of this dimension's main actionable groups (21 issue-level).
- Resolve the 17 Low IaC finding(s) in IaC & Container Security — start with REDACTED (11), REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (17 recommendation-level).
D34 · Knowledge Freshness
214 of 228 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/FunctionPullingContainerProxy.scala. Counted over 228 of the 295 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 211 Orphaned file finding(s) in Knowledge Freshness — start with Message.scala (2), Scheduler.scala (2), build.gradle (2). — One of this dimension's main actionable groups (211 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with FunctionPullingContainerProxy.scala, MemoryQueue.scala, ContainerProxy.scala. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: Packages.scala↔PackageCollection.scala 60%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with Packages.scala. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 1 end-of-life framework(s), read from 2 platform declaration(s) and 83 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.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with Apache.OpenWhisk.UnicodeTests.Dotnet.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 End-of-life framework finding(s) in Platform End-of-Life — start with build.gradle. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — REDACTED:786
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×3) — core/standalone/src/main/resources/playground/ui/index.html:87, core/standalone/src/main/resources/playground/ui/index.html:93, core/standalone/src/main/resources/playground/ui/index.html:121
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — core/standalone/src/main/resources/playground/ui/index.html:21
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — core/standalone/src/main/resources/playground/ui/index.html:21
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 2 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
M1 · Documentation (README)
What to do
- Describe the projects a newcomer cannot place from the root README: 7 of 15 have no README of their own, in their folder or in their family's project (`core/routemgmt/createApi`, `core/routemgmt/deleteApi`, `core/routemgmt/getApi`, `common/scala`, `core/controller` and 2 more).
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- CONTRIBUTING.md links to `dev@openwhisk.apache.org`, but `dev@openwhisk.apache.org` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:59
- ansible/README.md links to `ansible/README.md#deploying-using-cloudant`, but `ansible/ansible/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — ansible/README.md:447
What to do
- Reconcile the README with reality: CONTRIBUTING.md links to `dev@openwhisk.apache.org`, but `dev@openwhisk.apache.org` does not exist; ansible/README.md links to `ansible/README.md#deploying-using-cloudant`, but `ansible/ansible/README.md` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 7/8 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 8 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:23
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `nuget`, `npm`, `gradle`, 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 entries to the `updates:` list. — REDACTED:4
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `nuget`, `npm`, `gradle` — add those `package-ecosystem` entries 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
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
- 0 typed · 8 plain JS — the untyped files are core/routemgmt/common/apigw-utils.js, core/routemgmt/common/utils.js, core/routemgmt/createApi/createApi.js, core/routemgmt/deleteApi/deleteApi.js, core/routemgmt/getApi/getApi.js, tests/dat/actions/zippedaction/index.js (+2 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- core/routemgmt/deleteApi/deleteApi.js:53 · core/routemgmt/getApi/getApi.js:58 — the two spans are one implementation copied and then locally edited — 736 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — core/routemgmt/deleteApi/deleteApi.js:53
- core/routemgmt/common/apigw-utils.js:346 · core/routemgmt/common/utils.js:334 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/common/apigw-utils.js:346
- core/routemgmt/deleteApi/deleteApi.js:102 · core/routemgmt/deleteApi/deleteApi.js:171 — the two spans are one implementation copied and then locally edited — 292 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — core/routemgmt/deleteApi/deleteApi.js:102
- core/routemgmt/common/apigw-utils.js:274 · core/routemgmt/common/utils.js:261 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/common/apigw-utils.js:274
- core/routemgmt/common/utils.js:121 · core/routemgmt/common/utils.js:317 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/common/utils.js:121
- core/routemgmt/createApi/createApi.js:149 · core/routemgmt/createApi/createApi.js:206 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/createApi/createApi.js:149
- core/routemgmt/common/apigw-utils.js:671 · core/routemgmt/common/utils.js:631 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/common/apigw-utils.js:671
- core/routemgmt/common/apigw-utils.js:866 · core/routemgmt/common/utils.js:737 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/common/apigw-utils.js:866
- core/routemgmt/common/utils.js:56 · core/routemgmt/common/utils.js:110 · core/routemgmt/common/utils.js:200 · core/routemgmt/common/utils.js:250 · +1 more site(s) not listed — all 5 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/common/utils.js:56
- core/routemgmt/common/apigw-utils.js:221 · core/routemgmt/common/utils.js:211 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/common/apigw-utils.js:221
- tools/owperf/owperf.js:205 · tools/owperf/owperf.js:226 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — tools/owperf/owperf.js:205
- core/routemgmt/createApi/createApi.js:99 · core/routemgmt/deleteApi/deleteApi.js:66 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — core/routemgmt/createApi/createApi.js:99
- core/routemgmt/common/apigw-utils.js:609 · core/routemgmt/common/utils.js:585 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/common/apigw-utils.js:609
- core/routemgmt/common/apigw-utils.js:1037 · core/routemgmt/common/utils.js:763 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — core/routemgmt/common/apigw-utils.js:1037
- core/routemgmt/common/apigw-utils.js:639 · core/routemgmt/common/utils.js:612 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/common/apigw-utils.js:639
- core/routemgmt/common/apigw-utils.js:311 · core/routemgmt/common/utils.js:296 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/common/apigw-utils.js:311
- core/routemgmt/common/apigw-utils.js:826 · core/routemgmt/common/apigw-utils.js:837 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/common/apigw-utils.js:826
- core/routemgmt/common/apigw-utils.js:254 · core/routemgmt/common/utils.js:47 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/common/apigw-utils.js:254
- core/routemgmt/common/apigw-utils.js:334 · core/routemgmt/common/utils.js:67 · core/routemgmt/common/utils.js:120 · core/routemgmt/common/utils.js:316 — the 4 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/common/apigw-utils.js:334
- core/routemgmt/common/apigw-utils.js:708 · core/routemgmt/common/utils.js:669 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — core/routemgmt/common/apigw-utils.js:708
- core/routemgmt/createApi/createApi.js:230 · core/routemgmt/deleteApi/deleteApi.js:205 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — core/routemgmt/createApi/createApi.js:230
- core/routemgmt/getApi/getApi.js:100 · core/routemgmt/getApi/getApi.js:136 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/getApi/getApi.js:100
- core/routemgmt/createApi/createApi.js:139 · core/routemgmt/createApi/createApi.js:194 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/createApi/createApi.js:139
- core/standalone/src/main/resources/playground/actions/playground-delete.js:21 · core/standalone/src/main/resources/playground/actions/playground-fetch.js:21 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/standalone/src/main/resources/playground/actions/playground-delete.js:21
- core/routemgmt/common/apigw-utils.js:210 · core/routemgmt/common/apigw-utils.js:263 · core/routemgmt/common/apigw-utils.js:321 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/routemgmt/common/apigw-utils.js:210
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- validateArgs has cyclomatic complexity 27 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/routemgmt/createApi/createApi.js:246
- (anonymous) has cyclomatic complexity 21 and cognitive complexity 56; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/routemgmt/common/apigw-utils.js:97
- main has cyclomatic complexity 16 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/routemgmt/createApi/createApi.js:58
- processSample has cyclomatic complexity 15 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — tools/owperf/owperf.js:540
- mainLoop has cyclomatic complexity 14 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — tools/owperf/owperf.js:337
- (anonymous) has cyclomatic complexity 13 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/routemgmt/common/apigw-utils.js:321
- (anonymous) has cyclomatic complexity 12 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — core/routemgmt/common/utils.js:110, core/routemgmt/common/utils.js:306
- (anonymous) has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — core/routemgmt/common/apigw-utils.js:210, core/routemgmt/common/apigw-utils.js:263
- main has cyclomatic complexity 12 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/routemgmt/getApi/getApi.js:48
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/routemgmt/common/utils.js:56
- main has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/routemgmt/deleteApi/deleteApi.js:46
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- core/routemgmt/common/apigw-utils.js has 997 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/routemgmt/common/apigw-utils.js:1
- core/routemgmt/common/utils.js has 734 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/routemgmt/common/utils.js:1
- tools/owperf/owperf.js has 713 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools/owperf/owperf.js:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
- test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add a test runner (vitest / jest / playwright) and eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code
- This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×15) — core/routemgmt/common/apigw-utils.js:757, core/routemgmt/common/apigw-utils.js:823, core/standalone/src/main/resources/playground/actions/playground-delete.js:21, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in tools/owperf/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Web-Security Posture
- `https://cdnjs.cloudflare.com/ajax/libs/ace/1.4.2/ace.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 3 such include(s) across the repository's markup. — core/standalone/src/main/resources/playground/ui/index.html:28
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Scala server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: common/scala/src/main/scala/org/apache/openwhisk/http/BasicHttpService.scala:175 — `newServerAt`.
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
- Set security response headers on what the server sends — keep Play's `SecurityHeadersFilter` enabled, wrap akka/pekko-http routes in `respondWithHeaders(RawHeader("X-Content-Type-Options", "nosniff"), …)`, or add an http4s middleware that sets `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 35% | Weak — gated by R1, R3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 71% | Adequate — gated by AX10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 71% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 45% | Weak — gated by D13, R6, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 42% | Weak — gated by D29, D31 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 38% | Weak — gated by AC1, AC2, AC3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 4 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 7 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- SC1 Supply-chain hygiene — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 15 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'com.sksamuel.elastic4s' (core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/ElasticSearchDurationChecker.scala:20) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'com.sksamuel.elastic4s' (core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/ElasticSearchDurationChecker.scala:20) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'com.sksamuel.elastic4s' (core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/ElasticSearchDurationChecker.scala:20) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 66 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — -------------------- 16 | # 17 | ARG BASE=scala 18 | >>> FROM ${BASE} 19 | ARG OPENWHISK_JAR 20 | ARG TARGETPLATFORM -------------------- ERROR: failed to solve: scala: failed to resolve source metadata for docker.io/library/scala:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~64861 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D12 Dependency Hygiene — Not scored — 17 Maven/Gradle manifest(s) were read, stating a version for 76 dependency(ies) and leaving 97 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D18 Solution Shape — D18 scores the shape of a .NET solution, but this repository's production source is mostly .groovy, .py, .scala — the .NET project files present are an immaterial minority — so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, JavaScript, Python, Scala not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one project, `Apache.OpenWhisk.UnicodeTests.Dotnet` (0 LoC, 1 public types across 1 namespaces), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM1 Domain Modelling — applicable but not scored (3 signals for this style, 2 needed — the count is met but a required primary signal is absent): 3 strongly-typed id(s); 363 value object(s); 5 domain event(s); its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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 — reported, not scored — this repository's C# declares no analysable method bodies (a constants, record or DTO assembly), and this score is a density of unfinished work per method, which has no denominator here. The file-level signals below were still collected and are shown in full
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — 1 test file(s) reach none of 12 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
- X1 Async correctness — 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
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — 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
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — 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
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — 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
- X5 Nullable reference types — 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
- 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 — 82 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <select> without a programmatic label core/standalone/src/main/resources/playground/ui/index.html:87
- <select> without a programmatic label core/standalone/src/main/resources/playground/ui/index.html:93
- REDACTED
- REDACTED
- <img> without a text alternative REDACTED:786
- <textarea> without a programmatic label core/standalone/src/main/resources/playground/ui/index.html:121
- <html> without a lang core/standalone/src/main/resources/playground/ui/index.html:21
- REDACTED
- REDACTED
Serious — 264 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: v2/FunctionPullingContainerProxy.scala core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/FunctionPullingContainerProxy.scala
- FileTooLong: queue/MemoryQueue.scala core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/MemoryQueue.scala
- FileTooLong: containerpool/ContainerProxy.scala core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerProxy.scala
- FileTooLong: v2/FunctionPullingContainerPool.scala core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/FunctionPullingContainerPool.scala
- FileTooLong: queue/QueueManager.scala core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/QueueManager.scala
- FileTooLong: common/apigw-utils.js core/routemgmt/common/apigw-utils.js
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (8 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/core/entity/WhiskAction.scala:551
- Duplicated block (8 lines × 2) core/controller/src/main/scala/org/apache/openwhisk/core/loadBalancer/InvokerSupervision.scala:191
- Duplicated block (8 lines × 2) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/FunctionPullingContainerProxy.scala:1371
- Duplicated block (8 lines × 2) core/invoker/src/main/scala/org/apache/openwhisk/core/invoker/DefaultInvokerServer.scala:47
- Duplicated block (8 lines × 2) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerProxy.scala:1025
- Duplicated block (10 lines × 2) core/controller/src/main/scala/org/apache/openwhisk/core/controller/ApiUtils.scala:351
- Duplicated block (10 lines × 2) core/controller/src/main/scala/org/apache/openwhisk/core/loadBalancer/CommonLoadBalancer.scala:149
- Duplicated block (10 lines × 2) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerPool.scala:583
- Duplicated block (10 lines × 2) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerProxy.scala:748
- JavaScript dependencies are not locked core/routemgmt/createApi/package.json:3
- JavaScript dependencies are not locked core/routemgmt/deleteApi/package.json:3
- JavaScript dependencies are not locked core/routemgmt/getApi/package.json:3
- JavaScript dependencies are not locked tools/owperf/package.json:14
- Duplicated block (13 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/core/database/CouchDbRestStore.scala:315
- Duplicated block (13 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/core/entity/WhiskAction.scala:522
- Duplicated block (13 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/http/PoolingRestClient.scala:121
- Duplicated block (12 lines × 2) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerPool.scala:389
- Duplicated block (12 lines × 2) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/FunctionPullingContainerPool.scala:358
- Duplicated block (12 lines × 2) core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/MemoryQueue.scala:875
- Duplicated block (9 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/core/containerpool/PekkoContainerClient.scala:241
- Duplicated block (9 lines × 2) core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/QueueManager.scala:187
- Duplicated block (9 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/common/ForcibleSemaphore.scala:63
- Duplicated block (28 lines × 2 locations) core/routemgmt/common/apigw-utils.js:274
- Duplicated block (28 lines × 2 locations) core/routemgmt/common/utils.js:121
- Duplicated block (28 lines × 2 locations) core/routemgmt/createApi/createApi.js:149
- Duplicated block (8 lines × 2 locations) core/routemgmt/common/apigw-utils.js:708
- Duplicated block (8 lines × 2 locations) core/routemgmt/createApi/createApi.js:230
- Duplicated block (8 lines × 2 locations) core/routemgmt/getApi/getApi.js:100
- TooManyMethods: Messages common/scala/src/main/scala/org/apache/openwhisk/http/ErrorResponse.scala:38
- TooManyMethods: StandaloneOpenWhisk core/standalone/src/main/scala/org/apache/openwhisk/standalone/StandaloneOpenWhisk.scala:162
- FunctionTooLong: createApi.main core/routemgmt/createApi/createApi.js:58
- FunctionTooLong: deleteApi.main core/routemgmt/deleteApi/deleteApi.js:46
- Edited copy of a member (16 corresponding lines) core/controller/src/main/scala/org/apache/openwhisk/core/loadBalancer/InvokerSupervision.scala:189
- Edited copy of a member (16 corresponding lines) common/scala/src/main/scala/org/apache/openwhisk/http/PoolingRestClient.scala:118
- Duplicated block (16–17 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/core/service/DataManagementService.scala:107
- Duplicated block (16–17 lines × 2) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerPool.scala:663
- Duplicated block (17 lines × 2) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/FunctionPullingContainerPool.scala:303
- Duplicated block (17 lines × 2) core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/container/ContainerManager.scala:264
- Duplicated block (11 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/core/containerpool/Container.scala:133
- Duplicated block (11 lines × 2) core/controller/src/main/scala/org/apache/openwhisk/core/loadBalancer/CommonLoadBalancer.scala:233
- Duplicated block (6 lines × 2) core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/ElasticSearchDurationChecker.scala:208
- Duplicated block (6 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/core/database/DocumentHandler.scala:151
- Duplicated block (5 lines × 2) REDACTED:154
- Duplicated block (5 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/core/database/azblob/AzureBlobAttachmentStore.scala:311
- Duplicated block (7 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/core/database/DocumentHandler.scala:257
- Duplicated block (7 lines × 2) core/controller/src/main/scala/org/apache/openwhisk/core/loadBalancer/CommonLoadBalancer.scala:252
- Low cohesion: FunctionPullingContainerProxy (LCOM4 5) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/FunctionPullingContainerProxy.scala:181
- Low cohesion: InvokerHealthManager (LCOM4 4) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/InvokerHealthManager.scala:39
- Duplicated block (16 lines × 2 locations) core/routemgmt/common/apigw-utils.js:221
- Duplicated block (16 lines × 2 locations) tools/owperf/owperf.js:205
- Duplicated block (13 lines × 2 locations) core/routemgmt/common/apigw-utils.js:609
- Duplicated block (13 lines × 2 locations) core/routemgmt/common/apigw-utils.js:1037
- Duplicated block (10 lines × 2 locations) core/routemgmt/common/apigw-utils.js:311
- Duplicated block (10 lines × 2 locations) core/routemgmt/common/apigw-utils.js:826
- Duplicated block (7 lines × 2 locations) core/routemgmt/createApi/createApi.js:139
- Duplicated block (7 lines × 2 locations) core/standalone/src/main/resources/playground/actions/playground-delete.js:21
- Complex function (anonymous) (cyclomatic 12, cognitive 23) core/routemgmt/common/utils.js:110
- Complex function (anonymous) (cyclomatic 12, cognitive 23) core/routemgmt/common/utils.js:306
- Complex function (anonymous) (cyclomatic 12, cognitive 16) core/routemgmt/common/apigw-utils.js:210
- Complex function (anonymous) (cyclomatic 12, cognitive 16) core/routemgmt/common/apigw-utils.js:263
- Page without a main landmark core/standalone/src/main/resources/playground/ui/index.html:21
- Accessibility enforcement below the top rung
- SchedulingDecisionMaker.decide (cyclomatic 33) core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/SchedulingDecisionMaker.scala:49
- FunctionPullingContainerPool.receive (cyclomatic 31) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/FunctionPullingContainerPool.scala:197
- QueueManager.receive (cyclomatic 31) core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/QueueManager.scala:103
- EtcdWorker.receive (cyclomatic 27) common/scala/src/main/scala/org/apache/openwhisk/core/etcd/EtcdWorker.scala:53
- createApi.validateArgs (cyclomatic 27) core/routemgmt/createApi/createApi.js:246
- ContainerPool.receive (cyclomatic 26) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerPool.scala:116
- ContainerProxy.initializeAndRun (cyclomatic 24) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerProxy.scala:776
- DataManagementService.receive (cyclomatic 23) common/scala/src/main/scala/org/apache/openwhisk/core/service/DataManagementService.scala:69
- main (cyclomatic 22) core/routemgmt/deleteApi/deleteApi.js:46
- apigw-utils.validateFinalSwagger (cyclomatic 21) core/routemgmt/common/apigw-utils.js:96
- main (cyclomatic 21) core/routemgmt/createApi/createApi.js:58
- FunctionPullingContainerProxy.initializeAndRunActivation (cyclomatic 19) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/FunctionPullingContainerProxy.scala:1044
- main (cyclomatic 18) core/routemgmt/getApi/getApi.js:48
- apigw-utils.getApis (cyclomatic 17) core/routemgmt/common/apigw-utils.js:290
- Invoker.main (cyclomatic 16) core/invoker/src/main/scala/org/apache/openwhisk/core/invoker/Invoker.scala:105
- utils.getApis (cyclomatic 16) core/routemgmt/common/utils.js:277
- SchedulingDecisionMaker.decide (cognitive 77) core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/SchedulingDecisionMaker.scala:49
- ContainerPool.receive (cognitive 57) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerPool.scala:116
- apigw-utils.validateFinalSwagger (cognitive 56) core/routemgmt/common/apigw-utils.js:96
- createApi.validateArgs (cognitive 46) core/routemgmt/createApi/createApi.js:246
- QueueManager.receive (cognitive 38) core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/QueueManager.scala:103
- main (cognitive 37) core/routemgmt/deleteApi/deleteApi.js:46
- EtcdWorker.receive (cognitive 35) common/scala/src/main/scala/org/apache/openwhisk/core/etcd/EtcdWorker.scala:53
- CouchDbRestStore.attachToCouch (cognitive 33) common/scala/src/main/scala/org/apache/openwhisk/core/database/CouchDbRestStore.scala:378
- ContainerProxy.initializeAndRun (cognitive 33) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerProxy.scala:776
- main (cognitive 32) core/routemgmt/createApi/createApi.js:58
- DataManagementService.receive (cognitive 31) common/scala/src/main/scala/org/apache/openwhisk/core/service/DataManagementService.scala:69
- FunctionPullingContainerPool.receive (cognitive 31) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/FunctionPullingContainerPool.scala:197
- CouchDBLauncher.run (cognitive 30) core/standalone/src/main/scala/org/apache/openwhisk/standalone/CouchDBLauncher.scala:72
- utils.getApis (cognitive 29) core/routemgmt/common/utils.js:277
- FunctionPullingContainerProxy.initializeAndRunActivation (cognitive 28) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/FunctionPullingContainerProxy.scala:1044
- apigw-utils.getApis (cognitive 28) core/routemgmt/common/apigw-utils.js:290
- utils.getTenants (cognitive 25) core/routemgmt/common/utils.js:90
- owperf.mainLoop (cognitive 25) tools/owperf/owperf.js:337
- main (cognitive 25) core/routemgmt/getApi/getApi.js:48
- YARNContainerInfoActor.receive (cognitive 24) common/scala/src/main/scala/org/apache/openwhisk/core/yarn/YARNContainerInfoActor.scala:50
- ContainerManager.schedule (cognitive 24) core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/container/ContainerManager.scala:441
- PrimitiveActions.invokeConductor (cognitive 22) core/controller/src/main/scala/org/apache/openwhisk/core/controller/actions/PrimitiveActions.scala:329
- CommonLoadBalancer.processCompletion (cognitive 22) core/controller/src/main/scala/org/apache/openwhisk/core/loadBalancer/CommonLoadBalancer.scala:275
- PackageCollection.checkPackageReadPermission (cognitive 21) core/controller/src/main/scala/org/apache/openwhisk/core/entitlement/PackageCollection.scala:84
- CallbackModule.emit (cognitive 21) ansible/callbacks/logformatter.py:35
- WhiskWebActionsApi.handleMatch (cognitive 19) core/controller/src/main/scala/org/apache/openwhisk/core/controller/WebActions.scala:477
- WhiskWebActionsApi.extractEntityAndProcessRequest (cognitive 19) core/controller/src/main/scala/org/apache/openwhisk/core/controller/WebActions.scala:579
- apigw-utils.addApiToGateway (cognitive 19) core/routemgmt/common/apigw-utils.js:181
- utils.createTenant (cognitive 19) core/routemgmt/common/utils.js:37
- WatcherService.watchBehavior (cognitive 18) common/scala/src/main/scala/org/apache/openwhisk/core/service/WatcherService.scala:126
- ActivationServiceImpl.fetchActivation (cognitive 18) core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/grpc/ActivationServiceImpl.scala:64
- WhiskConfig.readPropertiesFromFile (cognitive 17) common/scala/src/main/scala/org/apache/openwhisk/core/WhiskConfig.scala:126
- AttachmentSupport.attachToExternalStore (cognitive 17) common/scala/src/main/scala/org/apache/openwhisk/core/database/AttachmentSupport.scala:139
- MongoDBArtifactStore.attachToMongo (cognitive 17) common/scala/src/main/scala/org/apache/openwhisk/core/database/mongodb/MongoDBArtifactStore.scala:375
- WhiskWebActionsApi.completeRequest (cognitive 17) core/controller/src/main/scala/org/apache/openwhisk/core/controller/WebActions.scala:661
- ShardingContainerPoolBalancer.publish (cognitive 17) core/controller/src/main/scala/org/apache/openwhisk/core/loadBalancer/ShardingContainerPoolBalancer.scala:255
- DockerContainer.create (cognitive 17) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/docker/DockerContainer.scala:61
- FunctionPullingContainerPool.adjustPrewarmedContainer (cognitive 17) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/FunctionPullingContainerPool.scala:448
- apigw-utils.deleteApiFromGateway (cognitive 17) core/routemgmt/common/apigw-utils.js:247
- apigw-utils.removeEndpointFromSwaggerApi (cognitive 17) core/routemgmt/common/apigw-utils.js:623
- utils.addApiToGateway (cognitive 17) core/routemgmt/common/utils.js:165
- ActivationResponse.processRunResponseContent (cognitive 16) common/scala/src/main/scala/org/apache/openwhisk/core/entity/ActivationResult.scala:199
- StandaloneOpenWhisk.main (cognitive 16) core/standalone/src/main/scala/org/apache/openwhisk/standalone/StandaloneOpenWhisk.scala:212
- owperf.processSample (cognitive 16) tools/owperf/owperf.js:540
- Change coupling: Packages.scala ↔ PackageCollection.scala core/controller/src/main/scala/org/apache/openwhisk/core/controller/Packages.scala:1
- REDACTED
- Edited copy of a member (40 corresponding lines) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerPool.scala:582
- Edited copy of a member (38 corresponding lines) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerPool.scala:641
- Edited copy of a member (20 corresponding lines) core/invoker/src/main/scala/org/apache/openwhisk/core/invoker/InvokerReactive.scala:272
- Edited copy of a member (30 corresponding lines) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/kubernetes/KubernetesClient.scala:229
- Edited copy of a member (24 corresponding lines) core/controller/src/main/scala/org/apache/openwhisk/core/loadBalancer/CommonLoadBalancer.scala:220
- Edited copy of a member (6 corresponding lines) REDACTED:154
- Duplicated block (26–27 lines × 2) core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/container/ContainerManager.scala:593
- Duplicated block (23–26 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/core/database/azblob/AzureBlobAttachmentStore.scala:167
- Duplicated block (24 lines × 2) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerProxy.scala:904
- Duplicated block (20 lines × 2) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerPool.scala:602
- Duplicated block (16–18 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/core/etcd/EtcdWorker.scala:74
- Duplicated block (15 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/core/etcd/EtcdClient.scala:196
- Duplicated block (13 lines × 4) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/FunctionPullingContainerProxy.scala:1252
- Duplicated block (11–13 lines × 2) core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/container/ContainerManager.scala:498
- Duplicated block (11 lines × 4) core/controller/src/main/scala/org/apache/openwhisk/core/controller/ApiUtils.scala:149
- Duplicated block (8–11 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/core/database/CouchDbRestStore.scala:538
- Duplicated block (10–11 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/core/database/mongodb/MongoDBAsyncStreamSink.scala:88
- Duplicated block (9–10 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/core/database/cosmosdb/CosmosDBArtifactStore.scala:320
- Duplicated block (8–9 lines × 2) common/scala/src/main/scala/org/apache/openwhisk/core/database/AttachmentSupport.scala:153
- Duplicated block (7–9 lines × 2) core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerProxy.scala:802
- End-of-life runtime: .NET netcoreapp2.2 tests/dat/actions/unicode.tests/src/dotnet2.2/Apache.OpenWhisk.UnicodeTests.Dotnet/Apache.OpenWhisk.UnicodeTests.Dotnet.csproj:20
- End-of-life framework: Spring Boot 2 core/standalone/build.gradle:1
- Type Safety
- Duplicated block with local edits (89 matched lines × 2 locations) core/routemgmt/deleteApi/deleteApi.js:53
- Duplicated block (76 lines × 2 locations) core/routemgmt/common/apigw-utils.js:346
- Duplicated block with local edits (33 matched lines × 2 locations) core/routemgmt/deleteApi/deleteApi.js:102
- Duplicated block (21 lines × 2 locations) core/routemgmt/common/apigw-utils.js:671
- Duplicated block (18 lines × 2 locations) core/routemgmt/common/apigw-utils.js:866
- Duplicated block (17 lines × 5 locations) core/routemgmt/common/utils.js:56
- Duplicated block (14 lines × 2 locations) core/routemgmt/createApi/createApi.js:99
- Duplicated block (12 lines × 2 locations) core/routemgmt/common/apigw-utils.js:639
- Duplicated block (9 lines × 2 locations) core/routemgmt/common/apigw-utils.js:254
- Duplicated block (8 lines × 4 locations) core/routemgmt/common/apigw-utils.js:334
- Duplicated block (5 lines × 3 locations) core/routemgmt/common/apigw-utils.js:210
- Complex function validateArgs (cyclomatic 27, cognitive 46) core/routemgmt/createApi/createApi.js:246
- Complex function (anonymous) (cyclomatic 21, cognitive 56) core/routemgmt/common/apigw-utils.js:97
- Complex function main (cyclomatic 16, cognitive 20) core/routemgmt/createApi/createApi.js:58
- Complex function processSample (cyclomatic 15, cognitive 16) tools/owperf/owperf.js:540
- Complex function mainLoop (cyclomatic 14, cognitive 25) tools/owperf/owperf.js:337
- Complex function (anonymous) (cyclomatic 13, cognitive 22) core/routemgmt/common/apigw-utils.js:321
- Complex function main (cyclomatic 12, cognitive 14) core/routemgmt/getApi/getApi.js:48
- Complex function (anonymous) (cyclomatic 11, cognitive 17) core/routemgmt/common/utils.js:56
- Complex function main (cyclomatic 11, cognitive 13) core/routemgmt/deleteApi/deleteApi.js:46
- core/routemgmt/common/apigw-utils.js: 997 lines of code core/routemgmt/common/apigw-utils.js:1
- core/routemgmt/common/utils.js: 734 lines of code core/routemgmt/common/utils.js:1
- tools/owperf/owperf.js: 713 lines of code tools/owperf/owperf.js:1
- No test, lint or typecheck script
- Unused dependency 'btoa'
- Unused dependency 'child-process-promise'
- Unused dependency 'cluster'
- Third-party script without Subresource Integrity core/standalone/src/main/resources/playground/ui/index.html:28
- NuGet dependencies are not locked
Minor — 280 finding(s)
- Orphaned file core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/FunctionPullingContainerPool.scala:1
- Orphaned file core/controller/src/main/scala/org/apache/openwhisk/core/controller/Actions.scala:1
- Orphaned file core/controller/src/main/scala/org/apache/openwhisk/core/controller/WebActions.scala:1
- Orphaned file core/controller/src/main/scala/org/apache/openwhisk/core/loadBalancer/FPCPoolBalancer.scala:1
- Orphaned file core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/QueueManager.scala:1
- Orphaned file core/controller/src/main/scala/org/apache/openwhisk/core/controller/actions/PrimitiveActions.scala:1
- Orphaned file core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerPool.scala:1
- Orphaned file core/controller/src/main/scala/org/apache/openwhisk/core/loadBalancer/ShardingContainerPoolBalancer.scala:1
- Orphaned file core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/container/ContainerManager.scala:1
- Orphaned file common/scala/src/main/scala/org/apache/openwhisk/core/connector/Message.scala:1
- Orphaned file common/scala/src/main/scala/org/apache/openwhisk/common/Logging.scala:1
- Orphaned file common/scala/src/main/scala/org/apache/openwhisk/core/database/mongodb/MongoDBArtifactStore.scala:1
- Orphaned file core/controller/src/main/scala/org/apache/openwhisk/core/controller/actions/SequenceActions.scala:1
- Orphaned file common/scala/src/main/scala/org/apache/openwhisk/core/entity/WhiskAction.scala:1
- Orphaned file common/scala/src/main/scala/org/apache/openwhisk/core/database/cosmosdb/CosmosDBArtifactStore.scala:1
- Orphaned file core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/kubernetes/KubernetesClient.scala:1
- Orphaned file common/scala/src/main/scala/org/apache/openwhisk/core/database/CouchDbRestStore.scala:1
- Orphaned file core/standalone/src/main/scala/org/apache/openwhisk/standalone/StandaloneOpenWhisk.scala:1
- Orphaned file core/controller/src/main/scala/org/apache/openwhisk/core/entitlement/Entitlement.scala:1
- Orphaned file common/scala/src/main/scala/org/apache/openwhisk/core/entity/Exec.scala:1
- Orphaned file common/scala/src/main/scala/org/apache/openwhisk/core/database/elasticsearch/ElasticSearchActivationStore.scala:1
- Orphaned file common/scala/src/main/scala/org/apache/openwhisk/core/database/MultipleReadersSingleWriterCache.scala:1
- Orphaned file core/invoker/src/main/scala/org/apache/openwhisk/core/invoker/FPCInvokerReactive.scala:1
- Orphaned file core/controller/src/main/scala/org/apache/openwhisk/core/loadBalancer/CommonLoadBalancer.scala:1
- Orphaned file core/controller/src/main/scala/org/apache/openwhisk/core/loadBalancer/InvokerSupervision.scala:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated predicate core/routemgmt/deleteApi/deleteApi.js:225
- Duplicated predicate core/routemgmt/createApi/createApi.js:78
- Duplicated predicate core/routemgmt/common/apigw-utils.js:645
- Duplicated predicate common/scala/src/main/scala/org/apache/openwhisk/core/database/CouchDbRestStore.scala:466
- Duplicated predicate common/scala/src/main/scala/org/apache/openwhisk/core/entity/ActivationId.scala:50
- Duplicated predicate core/controller/src/main/scala/org/apache/openwhisk/core/controller/Actions.scala:402
- Duplicated predicate core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerProxy.scala:602
- Duplicated predicate core/controller/src/main/scala/org/apache/openwhisk/core/entitlement/ActionCollection.scala:50
- Duplicated predicate core/controller/src/main/scala/org/apache/openwhisk/core/loadBalancer/FPCPoolBalancer.scala:495
- Duplicated predicate core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerPool.scala:391
- Duplicated predicate common/scala/src/main/scala/org/apache/openwhisk/core/database/DocumentHandler.scala:349
- Duplicated predicate core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerPool.scala:430
- Duplicated predicate common/scala/src/main/scala/org/apache/openwhisk/common/ForcibleSemaphore.scala:66
- Duplicated predicate common/scala/src/main/scala/org/apache/openwhisk/core/database/azblob/AzureBlobAttachmentStore.scala:313
- Duplicated predicate core/invoker/src/main/scala/org/apache/openwhisk/core/invoker/DefaultInvokerServer.scala:47
- redundant comment core/routemgmt/common/apigw-utils.js:552
- redundant comment REDACTED:134
- redundant comment REDACTED:254
- redundant comment tools/owperf/owperf.js:76
- Unused module-local declaration 'main' core/standalone/src/main/resources/playground/actions/playground-delete.js:21
- Unused module-local declaration 'main' core/standalone/src/main/resources/playground/actions/playground-fetch.js:21
- Unused module-local declaration 'main' core/standalone/src/main/resources/playground/actions/playground-run.js:31
- Unused module-local declaration 'main' core/standalone/src/main/resources/playground/actions/playground-userpackage.js:25
- Most significant orphaned file core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/v2/FunctionPullingContainerProxy.scala:1
- Most significant orphaned file core/scheduler/src/main/scala/org/apache/openwhisk/core/scheduler/queue/MemoryQueue.scala:1
- Most significant orphaned file core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerProxy.scala:1
- REDACTED
- REDACTED
- README/code drift CONTRIBUTING.md:59
- README/code drift ansible/README.md:447
- Off-boarding risk: anonymized user #1
- REDACTED
- REDACTED
- Concentrated knowledge decay
- No ADRs
- Logging is not universal
- No SAST REDACTED:23
- Dependabot does not watch nuget/npm/gradle REDACTED:4
- No rollback/health safety
- Unused module-local declaration 'getPackageNameFromActionUrl' core/routemgmt/common/apigw-utils.js:757
- Unused module-local declaration 'getNamespaceFromFqActionName' core/routemgmt/common/apigw-utils.js:823
- Unused module-local declaration 'languageChanged' REDACTED:309
- Unused module-local declaration 'actionChanged' REDACTED:327
- Unused module-local declaration 'themeClicked' REDACTED:550
- Unused module-local declaration 'publishClicked' REDACTED:684
- Unused module-local declaration 'processNewName' REDACTED:692
- Unused module-local declaration 'runClicked' REDACTED:758
- Unused module-local declaration 'RULE' tools/owperf/owperf.js:32
- Unused module-local declaration 'ACTIVATION' tools/owperf/owperf.js:34
- Unused module-local declaration 'getRandomInt' tools/owperf/owperf.js:804
- No security response headers detected
- Silent fallback default in catch core/standalone/src/main/scala/org/apache/openwhisk/standalone/StandaloneOpenWhisk.scala:387
Minor — 1 finding(s)
- Off the main sequence: openwhisk:common:scala
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-21c1668b567b4a96b1e8eae56f6aed54/history.json --exit-code 0 --source . | 2 | 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-21c1668b567b4a96b1e8eae56f6aed54/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude tests/dat/actions/unicode.tests/src/dotnet2.2/Apache.OpenWhisk.UnicodeTests.Dotnet/obj . | 59 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 108 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |