Executive summary
GoogleContainerTools/jib falls short of our standard for production because 191 files are no longer known to anyone active in the project and the project keeps no record of its design decisions. It scores 67 out of 100 and is rated Adequate, and all 32 of its critical findings are security problems in the build pipeline and in its automatic dependency updates.
Maturity, at 56, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 11 points. Having someone learn and document the 191 files no active contributor knows is another step, also worth about 11. Raising Maturity to 70 would lift the score to about 74.
Twenty-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five secrets can leak from the build pipeline, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, limiting each secret to its own step and setting a waiting period for automatic updates would close these risks.
The product code is 38,034 lines, about €93,000 to rebuild.
If Maturity rose from 56 to 70, the lowest score rated Strong, the score would rise from 67 to about 74.
New since the last survey: 33 findings
- Code Duplication · Edited copies of one member (3 members, 109+ corresponding lines) jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/BuildDockerMojo.java
- Code Duplication · Edited copies of one member (3 members, 90+ corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/BuildDockerTask.java
- Code Duplication · Edited copies of one member (3 members, 57+ corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/Build.java
- Code Duplication · Edited copy of a member (35 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/tar/TarExtractor.java
- Code Duplication · Edited copy of a member (28 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/cache/CacheStorageReader.java
- Code Duplication · Edited copy of a member (27 corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/GradleProjectProperties.java
- Code Duplication · Edited copy of a member (21 corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/jar/JarFiles.java
- Code Duplication · Edited copy of a member (24 corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/ContainerBuilders.java
- Code Duplication · Edited copy of a member (24 corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/GradleProjectProperties.java
- Code Duplication · Edited copy of a member (26 corresponding lines) jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/PluginConfigurationProcessor.java
- Code Duplication · Edited copy of a member (29 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/cache/CacheStorageWriter.java
- Code Duplication · Edited copies of one member (4 members, 22+ corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/builder/steps/StepsRunner.java
- Code Duplication · Edited copy of a member (17 corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/jar/StandardExplodedProcessor.java
- Code Duplication · Edited copy of a member (18 corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/JibPlugin.java
- Code Duplication · Edited copy of a member (13 corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/GradleProjectProperties.java
- Code Duplication · Edited copy of a member (20 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/cache/CacheStorageWriter.java
- Code Duplication · Edited copy of a member (12 corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/CommonCliOptions.java
- Code Duplication · Edited copy of a member (14 corresponding lines) jib-build-plan/src/main/java/com/google/cloud/tools/jib/api/buildplan/FileEntry.java
- Code Duplication · Edited copy of a member (23 corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/Credentials.java
- Code Duplication · Edited copy of a member (11 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/tar/TarExtractor.java
- Code Duplication · Edited copy of a member (13 corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/GradleProjectProperties.java
- Code Duplication · Edited copy of a member (16 corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/Containerizers.java
- Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/JibCli.java
- Code Duplication · Edited copy of a member (18 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/registry/BlobChecker.java
- Code Duplication · Edited copy of a member (10 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/image/json/OciIndexTemplate.java
- Code Duplication · Edited copy of a member (12 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/api/JibContainer.java
- Code Duplication · Edited copy of a member (11 corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/ContainerParameters.java
- Code Duplication · Edited copy of a member (9 corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/CommonCliOptions.java
- Code Duplication · Edited copy of a member (5 corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/OutputPathsParameters.java
- Code Duplication · Edited copy of a member (8 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/builder/steps/PushBlobStep.java
- Code Duplication · Edited copy of a member (7 corresponding lines) jib-build-plan/src/main/java/com/google/cloud/tools/jib/api/buildplan/AbsoluteUnixPath.java
- Code Duplication · Edited copy of a member (7 corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/ContainerParameters.java
- Code Duplication · Edited copy of a member (7 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/registry/RegistryAuthenticator.java
Fixed since the last survey: 1 finding
- Cohesion (LCOM4) · Low cohesion: ConsoleLoggerBuilder (LCOM4 6) jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/logging/ConsoleLoggerBuilder.java
Rebuild cost: about €93,000 · Estimate
| Cost to rebuild | €31,000 to €150,000, for 514 to 1,630 hours of work, about 0.6 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.9 at a score of 67. 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: 38,034 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 jib | 2 jib.api.buildplan | 3 jib.filesystem | 4 jib.json | 5 jib.plugins.extension | 6 jib.docker.json | 7 jib.event | 8 jib.event.progress | 9 jib.gradle.extension | 10 jib.hash | 11 jib.maven.extension | 12 jib.plugins.common.globalconfig | 13 jib.registry.credentials.json | 14 jib.registry.json | 15 jib.blob | 16 jib.event.events | 17 jib.builder | 18 jib.http | 19 jib.image.json | 20 jib.tar | 21 jib.registry | 22 jib.configuration | 23 jib.image | 24 jib.cache | 25 jib.builder.steps | 26 jib.api | 27 jib.docker | 28 jib.plugins.common.logging | 29 jib.registry.credentials | 30 jib.cli.jar | 31 jib.cli.logging | 32 jib.frontend | 33 jib.cli | 34 jib.plugins.common | 35 jib.cli.buildfile | 36 jib.cli.war | 37 jib.gradle.skaffold | 38 jib.maven | 39 jib.gradle | 40 jib.maven.skaffold |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 jib | ||||||||||||||||||||||||||||||||||||||||
| 2 jib.api.buildplan | ||||||||||||||||||||||||||||||||||||||||
| 3 jib.filesystem | ||||||||||||||||||||||||||||||||||||||||
| 4 jib.json | ||||||||||||||||||||||||||||||||||||||||
| 5 jib.plugins.extension | ||||||||||||||||||||||||||||||||||||||||
| 6 jib.docker.json | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 jib.event | 3 | |||||||||||||||||||||||||||||||||||||||
| 8 jib.event.progress | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 jib.gradle.extension | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 jib.hash | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 11 jib.maven.extension | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 jib.plugins.common.globalconfig | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 jib.registry.credentials.json | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 jib.registry.json | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 jib.blob | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 jib.event.events | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 17 jib.builder | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 18 jib.http | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 jib.image.json | 4 | 13 | 2 | 4 | 14 | |||||||||||||||||||||||||||||||||||
| 20 jib.tar | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 jib.registry | 3 | 4 | 1 | 4 | 39 | 2 | 13 | |||||||||||||||||||||||||||||||||
| 22 jib.configuration | 6 | 2 | 1 | 2 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||
| 23 jib.image | 5 | 9 | 4 | 2 | 5 | |||||||||||||||||||||||||||||||||||
| 24 jib.cache | 3 | 2 | 5 | 10 | 1 | 12 | ||||||||||||||||||||||||||||||||||
| 25 jib.builder.steps | 2 | 2 | 2 | 1 | 9 | 18 | 12 | 14 | 19 | 14 | 1 | 11 | ||||||||||||||||||||||||||||
| 26 jib.api | 24 | 1 | 3 | 1 | 6 | 1 | 3 | |||||||||||||||||||||||||||||||||
| 27 jib.docker | 2 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 28 jib.plugins.common.logging | 4 | |||||||||||||||||||||||||||||||||||||||
| 29 jib.registry.credentials | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 30 jib.cli.jar | 7 | 1 | 1 | 8 | ||||||||||||||||||||||||||||||||||||
| 31 jib.cli.logging | 2 | |||||||||||||||||||||||||||||||||||||||
| 32 jib.frontend | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 33 jib.cli | 8 | 1 | 5 | 3 | 1 | 4 | ||||||||||||||||||||||||||||||||||
| 34 jib.plugins.common | 10 | 4 | 2 | 1 | 2 | 25 | 1 | |||||||||||||||||||||||||||||||||
| 35 jib.cli.buildfile | 7 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 36 jib.cli.war | 2 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 37 jib.gradle.skaffold | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 38 jib.maven | 4 | 1 | 3 | 1 | 5 | 2 | 20 | |||||||||||||||||||||||||||||||||
| 39 jib.gradle | 5 | 1 | 1 | 1 | 4 | 2 | 16 | 1 | ||||||||||||||||||||||||||||||||
| 40 jib.maven.skaffold | 1 | 2 |
6→4 jib.docker.json uses jib.json✕
- Connections
- 1 pair of types, where a type in jib.docker.json uses a type in jib.json.
- The types involved
com.google.cloud.tools.jib.docker.json.DockerManifestEntryTemplate→com.google.cloud.tools.jib.json.JsonTemplate
- Direction
- jib.docker.json uses jib.json, so a change to jib.json can break jib.docker.json, while a change to jib.docker.json can't break jib.json.
- Position
- Below the diagonal: jib.docker.json uses a module listed above it, which is the healthy direction.
7→26 jib.event uses jib.api part of a loop✕
- Connections
- 3 pairs of types, where a type in jib.event uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.event.Builder→com.google.cloud.tools.jib.api.JibEventcom.google.cloud.tools.jib.event.EventHandlers→com.google.cloud.tools.jib.api.JibEventcom.google.cloud.tools.jib.event.Handler→com.google.cloud.tools.jib.api.JibEvent
- Direction
- jib.event uses jib.api, so a change to jib.api can break jib.event, while a change to jib.event can't break jib.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→16 jib.event.progress uses jib.event.events part of a loop✕
- Connections
- 1 pair of types, where a type in jib.event.progress uses a type in jib.event.events.
- The types involved
com.google.cloud.tools.jib.event.progress.ProgressEventHandler→com.google.cloud.tools.jib.event.events.ProgressEvent
- Direction
- jib.event.progress uses jib.event.events, so a change to jib.event.events can break jib.event.progress, while a change to jib.event.progress can't break jib.event.events.
- 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→2 jib.gradle.extension uses jib.api.buildplan✕
- Connections
- 1 pair of types, where a type in jib.gradle.extension uses a type in jib.api.buildplan.
- The types involved
com.google.cloud.tools.jib.gradle.extension.JibGradlePluginExtension→com.google.cloud.tools.jib.api.buildplan.ContainerBuildPlan
- Direction
- jib.gradle.extension uses jib.api.buildplan, so a change to jib.api.buildplan can break jib.gradle.extension, while a change to jib.gradle.extension can't break jib.api.buildplan.
- Position
- Below the diagonal: jib.gradle.extension uses a module listed above it, which is the healthy direction.
9→5 jib.gradle.extension uses jib.plugins.extension✕
- Connections
- 2 pairs of types, where a type in jib.gradle.extension uses a type in jib.plugins.extension.
- The types involved
com.google.cloud.tools.jib.gradle.extension.JibGradlePluginExtension→com.google.cloud.tools.jib.plugins.extension.ExtensionLoggercom.google.cloud.tools.jib.gradle.extension.JibGradlePluginExtension→com.google.cloud.tools.jib.plugins.extension.JibPluginExtension
- Direction
- jib.gradle.extension uses jib.plugins.extension, so a change to jib.plugins.extension can break jib.gradle.extension, while a change to jib.gradle.extension can't break jib.plugins.extension.
- Position
- Below the diagonal: jib.gradle.extension uses a module listed above it, which is the healthy direction.
10→4 jib.hash uses jib.json✕
- Connections
- 1 pair of types, where a type in jib.hash uses a type in jib.json.
- The types involved
com.google.cloud.tools.jib.hash.Digests→com.google.cloud.tools.jib.json.JsonTemplate
- Direction
- jib.hash uses jib.json, so a change to jib.json can break jib.hash, while a change to jib.hash can't break jib.json.
- Position
- Below the diagonal: jib.hash uses a module listed above it, which is the healthy direction.
10→15 jib.hash uses jib.blob part of a loop✕
- Connections
- 2 pairs of types, where a type in jib.hash uses a type in jib.blob.
- The types involved
com.google.cloud.tools.jib.hash.CountingDigestOutputStream→com.google.cloud.tools.jib.blob.BlobDescriptorcom.google.cloud.tools.jib.hash.Digests→com.google.cloud.tools.jib.blob.BlobDescriptor
- Direction
- jib.hash uses jib.blob, so a change to jib.blob can break jib.hash, while a change to jib.hash can't break jib.blob.
- 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→26 jib.hash uses jib.api part of a loop✕
- Connections
- 1 pair of types, where a type in jib.hash uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.hash.Digests→com.google.cloud.tools.jib.api.DescriptorDigest
- Direction
- jib.hash uses jib.api, so a change to jib.api can break jib.hash, while a change to jib.hash can't break jib.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→2 jib.maven.extension uses jib.api.buildplan✕
- Connections
- 1 pair of types, where a type in jib.maven.extension uses a type in jib.api.buildplan.
- The types involved
com.google.cloud.tools.jib.maven.extension.JibMavenPluginExtension→com.google.cloud.tools.jib.api.buildplan.ContainerBuildPlan
- Direction
- jib.maven.extension uses jib.api.buildplan, so a change to jib.api.buildplan can break jib.maven.extension, while a change to jib.maven.extension can't break jib.api.buildplan.
- Position
- Below the diagonal: jib.maven.extension uses a module listed above it, which is the healthy direction.
11→5 jib.maven.extension uses jib.plugins.extension✕
- Connections
- 2 pairs of types, where a type in jib.maven.extension uses a type in jib.plugins.extension.
- The types involved
com.google.cloud.tools.jib.maven.extension.JibMavenPluginExtension→com.google.cloud.tools.jib.plugins.extension.ExtensionLoggercom.google.cloud.tools.jib.maven.extension.JibMavenPluginExtension→com.google.cloud.tools.jib.plugins.extension.JibPluginExtension
- Direction
- jib.maven.extension uses jib.plugins.extension, so a change to jib.plugins.extension can break jib.maven.extension, while a change to jib.maven.extension can't break jib.plugins.extension.
- Position
- Below the diagonal: jib.maven.extension uses a module listed above it, which is the healthy direction.
12→4 jib.plugins.common.globalconfig uses jib.json✕
- Connections
- 2 pairs of types, where a type in jib.plugins.common.globalconfig uses a type in jib.json.
- The types involved
com.google.cloud.tools.jib.plugins.common.globalconfig.GlobalConfigTemplate→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.plugins.common.globalconfig.RegistryMirrorsTemplate→com.google.cloud.tools.jib.json.JsonTemplate
- Direction
- jib.plugins.common.globalconfig uses jib.json, so a change to jib.json can break jib.plugins.common.globalconfig, while a change to jib.plugins.common.globalconfig can't break jib.json.
- Position
- Below the diagonal: jib.plugins.common.globalconfig uses a module listed above it, which is the healthy direction.
13→4 jib.registry.credentials.json uses jib.json✕
- Connections
- 2 pairs of types, where a type in jib.registry.credentials.json uses a type in jib.json.
- The types involved
com.google.cloud.tools.jib.registry.credentials.json.AuthTemplate→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.registry.credentials.json.DockerConfigTemplate→com.google.cloud.tools.jib.json.JsonTemplate
- Direction
- jib.registry.credentials.json uses jib.json, so a change to jib.json can break jib.registry.credentials.json, while a change to jib.registry.credentials.json can't break jib.json.
- Position
- Below the diagonal: jib.registry.credentials.json uses a module listed above it, which is the healthy direction.
14→4 jib.registry.json uses jib.json✕
- Connections
- 2 pairs of types, where a type in jib.registry.json uses a type in jib.json.
- The types involved
com.google.cloud.tools.jib.registry.json.ErrorEntryTemplate→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.registry.json.ErrorResponseTemplate→com.google.cloud.tools.jib.json.JsonTemplate
- Direction
- jib.registry.json uses jib.json, so a change to jib.json can break jib.registry.json, while a change to jib.registry.json can't break jib.json.
- Position
- Below the diagonal: jib.registry.json uses a module listed above it, which is the healthy direction.
15→4 jib.blob uses jib.json✕
- Connections
- 2 pairs of types, where a type in jib.blob uses a type in jib.json.
- The types involved
com.google.cloud.tools.jib.blob.Blobs→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.blob.JsonBlob→com.google.cloud.tools.jib.json.JsonTemplate
- Direction
- jib.blob uses jib.json, so a change to jib.json can break jib.blob, while a change to jib.blob can't break jib.json.
- Position
- Below the diagonal: jib.blob uses a module listed above it, which is the healthy direction.
15→10 jib.blob uses jib.hash✕
- Connections
- 2 pairs of types, where a type in jib.blob uses a type in jib.hash.
- The types involved
com.google.cloud.tools.jib.blob.Blobs→com.google.cloud.tools.jib.hash.WritableContentscom.google.cloud.tools.jib.blob.WritableContentsBlob→com.google.cloud.tools.jib.hash.WritableContents
- Direction
- jib.blob uses jib.hash, so a change to jib.hash can break jib.blob, while a change to jib.blob can't break jib.hash.
- Position
- Below the diagonal: jib.blob uses a module listed above it, which is the healthy direction.
15→26 jib.blob uses jib.api part of a loop✕
- Connections
- 1 pair of types, where a type in jib.blob uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.blob.BlobDescriptor→com.google.cloud.tools.jib.api.DescriptorDigest
- Direction
- jib.blob uses jib.api, so a change to jib.api can break jib.blob, while a change to jib.blob can't break jib.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→8 jib.event.events uses jib.event.progress✕
- Connections
- 1 pair of types, where a type in jib.event.events uses a type in jib.event.progress.
- The types involved
com.google.cloud.tools.jib.event.events.ProgressEvent→com.google.cloud.tools.jib.event.progress.Allocation
- Direction
- jib.event.events uses jib.event.progress, so a change to jib.event.progress can break jib.event.events, while a change to jib.event.events can't break jib.event.progress.
- Position
- Below the diagonal: jib.event.events uses a module listed above it, which is the healthy direction.
16→26 jib.event.events uses jib.api part of a loop✕
- Connections
- 2 pairs of types, where a type in jib.event.events uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.event.events.ProgressEvent→com.google.cloud.tools.jib.api.JibEventcom.google.cloud.tools.jib.event.events.TimerEvent→com.google.cloud.tools.jib.api.JibEvent
- Direction
- jib.event.events uses jib.api, so a change to jib.api can break jib.event.events, while a change to jib.event.events can't break jib.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→7 jib.builder uses jib.event✕
- Connections
- 2 pairs of types, where a type in jib.builder uses a type in jib.event.
- The types involved
com.google.cloud.tools.jib.builder.ProgressEventDispatcher→com.google.cloud.tools.jib.event.EventHandlerscom.google.cloud.tools.jib.builder.TimerEventDispatcher→com.google.cloud.tools.jib.event.EventHandlers
- Direction
- jib.builder uses jib.event, so a change to jib.event can break jib.builder, while a change to jib.builder can't break jib.event.
- Position
- Below the diagonal: jib.builder uses a module listed above it, which is the healthy direction.
17→8 jib.builder uses jib.event.progress✕
- Connections
- 1 pair of types, where a type in jib.builder uses a type in jib.event.progress.
- The types involved
com.google.cloud.tools.jib.builder.ProgressEventDispatcher→com.google.cloud.tools.jib.event.progress.Allocation
- Direction
- jib.builder uses jib.event.progress, so a change to jib.event.progress can break jib.builder, while a change to jib.builder can't break jib.event.progress.
- Position
- Below the diagonal: jib.builder uses a module listed above it, which is the healthy direction.
17→16 jib.builder uses jib.event.events✕
- Connections
- 2 pairs of types, where a type in jib.builder uses a type in jib.event.events.
- The types involved
com.google.cloud.tools.jib.builder.Timer→com.google.cloud.tools.jib.event.events.Timercom.google.cloud.tools.jib.builder.TimerEventDispatcher→com.google.cloud.tools.jib.event.events.State
- Direction
- jib.builder uses jib.event.events, so a change to jib.event.events can break jib.builder, while a change to jib.builder can't break jib.event.events.
- Position
- Below the diagonal: jib.builder uses a module listed above it, which is the healthy direction.
18→15 jib.http uses jib.blob✕
- Connections
- 1 pair of types, where a type in jib.http uses a type in jib.blob.
- The types involved
com.google.cloud.tools.jib.http.BlobHttpContent→com.google.cloud.tools.jib.blob.Blob
- Direction
- jib.http uses jib.blob, so a change to jib.blob can break jib.http, while a change to jib.http can't break jib.blob.
- Position
- Below the diagonal: jib.http uses a module listed above it, which is the healthy direction.
18→26 jib.http uses jib.api part of a loop✕
- Connections
- 1 pair of types, where a type in jib.http uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.http.FailoverHttpClient→com.google.cloud.tools.jib.api.LogEvent
- Direction
- jib.http uses jib.api, so a change to jib.api can break jib.http, while a change to jib.http can't break jib.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→2 jib.image.json uses jib.api.buildplan✕
- Connections
- 4 pairs of types, where a type in jib.image.json uses a type in jib.api.buildplan.
- The types involved
com.google.cloud.tools.jib.image.json.ImageToJsonTranslator→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.image.json.ImageToJsonTranslator→com.google.cloud.tools.jib.api.buildplan.Portcom.google.cloud.tools.jib.image.json.JsonToImageTranslator→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.image.json.JsonToImageTranslator→com.google.cloud.tools.jib.api.buildplan.Port
- Direction
- jib.image.json uses jib.api.buildplan, so a change to jib.api.buildplan can break jib.image.json, while a change to jib.image.json can't break jib.api.buildplan.
- Position
- Below the diagonal: jib.image.json uses a module listed above it, which is the healthy direction.
19→4 jib.image.json uses jib.json✕
- Connections
- 13 pairs of types, where a type in jib.image.json uses a type in jib.json.
- The types involved
com.google.cloud.tools.jib.image.json.ConfigurationObjectTemplate→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.image.json.ContainerConfigurationTemplate→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.image.json.ContentDescriptorTemplate→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.image.json.HealthCheckObjectTemplate→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.image.json.HistoryEntry→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.image.json.HistoryObjectTemplate→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.image.json.ImageMetadataTemplate→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.image.json.ImageToJsonTranslator→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.image.json.LayerObjectTemplate→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.image.json.ManifestAndConfigTemplate→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.image.json.ManifestTemplate→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.image.json.Platform→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.image.json.RootFilesystemObjectTemplate→com.google.cloud.tools.jib.json.JsonTemplate
- Direction
- jib.image.json uses jib.json, so a change to jib.json can break jib.image.json, while a change to jib.image.json can't break jib.json.
- Position
- Below the diagonal: jib.image.json uses a module listed above it, which is the healthy direction.
19→15 jib.image.json uses jib.blob✕
- Connections
- 2 pairs of types, where a type in jib.image.json uses a type in jib.blob.
- The types involved
com.google.cloud.tools.jib.image.json.ImageToJsonTranslator→com.google.cloud.tools.jib.blob.BlobDescriptorcom.google.cloud.tools.jib.image.json.OciIndexTemplate→com.google.cloud.tools.jib.blob.BlobDescriptor
- Direction
- jib.image.json uses jib.blob, so a change to jib.blob can break jib.image.json, while a change to jib.image.json can't break jib.blob.
- Position
- Below the diagonal: jib.image.json uses a module listed above it, which is the healthy direction.
19→23 jib.image.json uses jib.image part of a loop✕
- Connections
- 4 pairs of types, where a type in jib.image.json uses a type in jib.image.
- The types involved
com.google.cloud.tools.jib.image.json.ImageToJsonTranslator→com.google.cloud.tools.jib.image.Imagecom.google.cloud.tools.jib.image.json.JsonToImageTranslator→com.google.cloud.tools.jib.image.Buildercom.google.cloud.tools.jib.image.json.JsonToImageTranslator→com.google.cloud.tools.jib.image.Imagecom.google.cloud.tools.jib.image.json.ManifestListGenerator→com.google.cloud.tools.jib.image.Image
- Direction
- jib.image.json uses jib.image, so a change to jib.image can break jib.image.json, while a change to jib.image.json can't break jib.image.
- 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.
19→26 jib.image.json uses jib.api part of a loop✕
- Connections
- 14 pairs of types, where a type in jib.image.json uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.image.json.BuildableManifestTemplate→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.image.json.ContainerConfigurationTemplate→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.image.json.ContentDescriptorTemplate→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.image.json.DescriptorDigestDeserializer→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.image.json.DescriptorDigestSerializer→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.image.json.LayerObjectTemplate→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.image.json.ManifestDescriptorTemplate→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.image.json.OciManifestTemplate→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.image.json.PlatformNotFoundInBaseImageException→com.google.cloud.tools.jib.api.RegistryExceptioncom.google.cloud.tools.jib.image.json.RootFilesystemObjectTemplate→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.image.json.UnknownManifestFormatException→com.google.cloud.tools.jib.api.RegistryExceptioncom.google.cloud.tools.jib.image.json.UnlistedPlatformInManifestListException→com.google.cloud.tools.jib.api.RegistryExceptioncom.google.cloud.tools.jib.image.json.V21ManifestTemplate→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.image.json.V22ManifestTemplate→com.google.cloud.tools.jib.api.DescriptorDigest
- Direction
- jib.image.json uses jib.api, so a change to jib.api can break jib.image.json, while a change to jib.image.json can't break jib.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→15 jib.tar uses jib.blob✕
- Connections
- 1 pair of types, where a type in jib.tar uses a type in jib.blob.
- The types involved
com.google.cloud.tools.jib.tar.TarStreamBuilder→com.google.cloud.tools.jib.blob.Blob
- Direction
- jib.tar uses jib.blob, so a change to jib.blob can break jib.tar, while a change to jib.tar can't break jib.blob.
- Position
- Below the diagonal: jib.tar uses a module listed above it, which is the healthy direction.
21→4 jib.registry uses jib.json✕
- Connections
- 3 pairs of types, where a type in jib.registry uses a type in jib.json.
- The types involved
com.google.cloud.tools.jib.registry.AccessClaim→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.registry.AuthenticationResponseTemplate→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.registry.TokenPayloadTemplate→com.google.cloud.tools.jib.json.JsonTemplate
- Direction
- jib.registry uses jib.json, so a change to jib.json can break jib.registry, while a change to jib.registry can't break jib.json.
- Position
- Below the diagonal: jib.registry uses a module listed above it, which is the healthy direction.
21→7 jib.registry uses jib.event✕
- Connections
- 4 pairs of types, where a type in jib.registry uses a type in jib.event.
- The types involved
com.google.cloud.tools.jib.registry.Factory→com.google.cloud.tools.jib.event.EventHandlerscom.google.cloud.tools.jib.registry.ManifestPusher→com.google.cloud.tools.jib.event.EventHandlerscom.google.cloud.tools.jib.registry.RegistryClient→com.google.cloud.tools.jib.event.EventHandlerscom.google.cloud.tools.jib.registry.RegistryEndpointCaller→com.google.cloud.tools.jib.event.EventHandlers
- Direction
- jib.registry uses jib.event, so a change to jib.event can break jib.registry, while a change to jib.registry can't break jib.event.
- Position
- Below the diagonal: jib.registry uses a module listed above it, which is the healthy direction.
21→14 jib.registry uses jib.registry.json✕
- Connections
- 1 pair of types, where a type in jib.registry uses a type in jib.registry.json.
- The types involved
com.google.cloud.tools.jib.registry.RegistryErrorExceptionBuilder→com.google.cloud.tools.jib.registry.json.ErrorEntryTemplate
- Direction
- jib.registry uses jib.registry.json, so a change to jib.registry.json can break jib.registry, while a change to jib.registry can't break jib.registry.json.
- Position
- Below the diagonal: jib.registry uses a module listed above it, which is the healthy direction.
21→15 jib.registry uses jib.blob✕
- Connections
- 4 pairs of types, where a type in jib.registry uses a type in jib.blob.
- The types involved
com.google.cloud.tools.jib.registry.BlobChecker→com.google.cloud.tools.jib.blob.BlobDescriptorcom.google.cloud.tools.jib.registry.BlobPusher→com.google.cloud.tools.jib.blob.Blobcom.google.cloud.tools.jib.registry.RegistryClient→com.google.cloud.tools.jib.blob.Blobcom.google.cloud.tools.jib.registry.RegistryClient→com.google.cloud.tools.jib.blob.BlobDescriptor
- Direction
- jib.registry uses jib.blob, so a change to jib.blob can break jib.registry, while a change to jib.registry can't break jib.blob.
- Position
- Below the diagonal: jib.registry uses a module listed above it, which is the healthy direction.
21→18 jib.registry uses jib.http✕
- Connections
- 39 pairs of types, where a type in jib.registry uses a type in jib.http. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.cloud.tools.jib.registry.AbstractManifestPuller→com.google.cloud.tools.jib.http.BlobHttpContentcom.google.cloud.tools.jib.registry.AbstractManifestPuller→com.google.cloud.tools.jib.http.Responsecom.google.cloud.tools.jib.registry.AbstractManifestPuller→com.google.cloud.tools.jib.http.ResponseExceptioncom.google.cloud.tools.jib.registry.AuthenticationMethodRetriever→com.google.cloud.tools.jib.http.BlobHttpContentcom.google.cloud.tools.jib.registry.AuthenticationMethodRetriever→com.google.cloud.tools.jib.http.FailoverHttpClientcom.google.cloud.tools.jib.registry.AuthenticationMethodRetriever→com.google.cloud.tools.jib.http.Responsecom.google.cloud.tools.jib.registry.AuthenticationMethodRetriever→com.google.cloud.tools.jib.http.ResponseExceptioncom.google.cloud.tools.jib.registry.BlobChecker→com.google.cloud.tools.jib.http.BlobHttpContentcom.google.cloud.tools.jib.registry.BlobChecker→com.google.cloud.tools.jib.http.Responsecom.google.cloud.tools.jib.registry.BlobChecker→com.google.cloud.tools.jib.http.ResponseExceptioncom.google.cloud.tools.jib.registry.BlobPuller→com.google.cloud.tools.jib.http.BlobHttpContentcom.google.cloud.tools.jib.registry.BlobPuller→com.google.cloud.tools.jib.http.Responsecom.google.cloud.tools.jib.registry.BlobPuller→com.google.cloud.tools.jib.http.ResponseExceptioncom.google.cloud.tools.jib.registry.BlobPusher→com.google.cloud.tools.jib.http.Responsecom.google.cloud.tools.jib.registry.Committer→com.google.cloud.tools.jib.http.BlobHttpContentcom.google.cloud.tools.jib.registry.Committer→com.google.cloud.tools.jib.http.Responsecom.google.cloud.tools.jib.registry.Committer→com.google.cloud.tools.jib.http.ResponseExceptioncom.google.cloud.tools.jib.registry.ErrorResponseUtil→com.google.cloud.tools.jib.http.ResponseExceptioncom.google.cloud.tools.jib.registry.Factory→com.google.cloud.tools.jib.http.FailoverHttpClientcom.google.cloud.tools.jib.registry.Initializer→com.google.cloud.tools.jib.http.BlobHttpContentcom.google.cloud.tools.jib.registry.Initializer→com.google.cloud.tools.jib.http.Responsecom.google.cloud.tools.jib.registry.Initializer→com.google.cloud.tools.jib.http.ResponseExceptioncom.google.cloud.tools.jib.registry.ManifestChecker→com.google.cloud.tools.jib.http.ResponseExceptioncom.google.cloud.tools.jib.registry.ManifestPusher→com.google.cloud.tools.jib.http.BlobHttpContentcom.google.cloud.tools.jib.registry.ManifestPusher→com.google.cloud.tools.jib.http.Response
- Direction
- jib.registry uses jib.http, so a change to jib.http can break jib.registry, while a change to jib.registry can't break jib.http.
- Position
- Below the diagonal: jib.registry uses a module listed above it, which is the healthy direction.
21→19 jib.registry uses jib.image.json✕
- Connections
- 2 pairs of types, where a type in jib.registry uses a type in jib.image.json.
- The types involved
com.google.cloud.tools.jib.registry.ManifestPusher→com.google.cloud.tools.jib.image.json.ManifestTemplatecom.google.cloud.tools.jib.registry.RegistryClient→com.google.cloud.tools.jib.image.json.ManifestTemplate
- Direction
- jib.registry uses jib.image.json, so a change to jib.image.json can break jib.registry, while a change to jib.registry can't break jib.image.json.
- Position
- Below the diagonal: jib.registry uses a module listed above it, which is the healthy direction.
21→26 jib.registry uses jib.api part of a loop✕
- Connections
- 13 pairs of types, where a type in jib.registry uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.registry.BlobChecker→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.registry.BlobPuller→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.registry.BlobPusher→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.registry.Factory→com.google.cloud.tools.jib.api.Credentialcom.google.cloud.tools.jib.registry.ManifestAndDigest→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.registry.ManifestPusher→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.registry.RegistryAuthenticator→com.google.cloud.tools.jib.api.Credentialcom.google.cloud.tools.jib.registry.RegistryAuthenticator→com.google.cloud.tools.jib.api.RegistryAuthenticationFailedExceptioncom.google.cloud.tools.jib.registry.RegistryClient→com.google.cloud.tools.jib.api.Credentialcom.google.cloud.tools.jib.registry.RegistryClient→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.registry.RegistryCredentialsNotSentException→com.google.cloud.tools.jib.api.RegistryExceptioncom.google.cloud.tools.jib.registry.RegistryErrorException→com.google.cloud.tools.jib.api.RegistryExceptioncom.google.cloud.tools.jib.registry.UnexpectedBlobDigestException→com.google.cloud.tools.jib.api.RegistryException
- Direction
- jib.registry uses jib.api, so a change to jib.api can break jib.registry, while a change to jib.registry can't break jib.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→2 jib.configuration uses jib.api.buildplan✕
- Connections
- 6 pairs of types, where a type in jib.configuration uses a type in jib.api.buildplan.
- The types involved
com.google.cloud.tools.jib.configuration.BuildContext→com.google.cloud.tools.jib.api.buildplan.FileEntriesLayercom.google.cloud.tools.jib.configuration.Builder→com.google.cloud.tools.jib.api.buildplan.FileEntriesLayercom.google.cloud.tools.jib.configuration.Builder→com.google.cloud.tools.jib.api.buildplan.ImageFormatcom.google.cloud.tools.jib.configuration.ContainerConfiguration→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.configuration.ContainerConfiguration→com.google.cloud.tools.jib.api.buildplan.Platformcom.google.cloud.tools.jib.configuration.ContainerConfiguration→com.google.cloud.tools.jib.api.buildplan.Port
- Direction
- jib.configuration uses jib.api.buildplan, so a change to jib.api.buildplan can break jib.configuration, while a change to jib.configuration can't break jib.api.buildplan.
- Position
- Below the diagonal: jib.configuration uses a module listed above it, which is the healthy direction.
22→7 jib.configuration uses jib.event✕
- Connections
- 2 pairs of types, where a type in jib.configuration uses a type in jib.event.
- The types involved
com.google.cloud.tools.jib.configuration.BuildContext→com.google.cloud.tools.jib.event.EventHandlerscom.google.cloud.tools.jib.configuration.Builder→com.google.cloud.tools.jib.event.EventHandlers
- Direction
- jib.configuration uses jib.event, so a change to jib.event can break jib.configuration, while a change to jib.configuration can't break jib.event.
- Position
- Below the diagonal: jib.configuration uses a module listed above it, which is the healthy direction.
22→18 jib.configuration uses jib.http✕
- Connections
- 1 pair of types, where a type in jib.configuration uses a type in jib.http.
- The types involved
com.google.cloud.tools.jib.configuration.BuildContext→com.google.cloud.tools.jib.http.FailoverHttpClient
- Direction
- jib.configuration uses jib.http, so a change to jib.http can break jib.configuration, while a change to jib.configuration can't break jib.http.
- Position
- Below the diagonal: jib.configuration uses a module listed above it, which is the healthy direction.
22→19 jib.configuration uses jib.image.json✕
- Connections
- 2 pairs of types, where a type in jib.configuration uses a type in jib.image.json.
- The types involved
com.google.cloud.tools.jib.configuration.BuildContext→com.google.cloud.tools.jib.image.json.BuildableManifestTemplatecom.google.cloud.tools.jib.configuration.Builder→com.google.cloud.tools.jib.image.json.BuildableManifestTemplate
- Direction
- jib.configuration uses jib.image.json, so a change to jib.image.json can break jib.configuration, while a change to jib.configuration can't break jib.image.json.
- Position
- Below the diagonal: jib.configuration uses a module listed above it, which is the healthy direction.
22→21 jib.configuration uses jib.registry✕
- Connections
- 1 pair of types, where a type in jib.configuration uses a type in jib.registry.
- The types involved
com.google.cloud.tools.jib.configuration.BuildContext→com.google.cloud.tools.jib.registry.Factory
- Direction
- jib.configuration uses jib.registry, so a change to jib.registry can break jib.configuration, while a change to jib.configuration can't break jib.registry.
- Position
- Below the diagonal: jib.configuration uses a module listed above it, which is the healthy direction.
22→24 jib.configuration uses jib.cache part of a loop✕
- Connections
- 1 pair of types, where a type in jib.configuration uses a type in jib.cache.
- The types involved
com.google.cloud.tools.jib.configuration.BuildContext→com.google.cloud.tools.jib.cache.Cache
- Direction
- jib.configuration uses jib.cache, so a change to jib.cache can break jib.configuration, while a change to jib.configuration can't break jib.cache.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→26 jib.configuration uses jib.api part of a loop✕
- Connections
- 3 pairs of types, where a type in jib.configuration uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.configuration.ImageConfiguration→com.google.cloud.tools.jib.api.CredentialRetrievercom.google.cloud.tools.jib.configuration.ImageConfiguration→com.google.cloud.tools.jib.api.DockerClientcom.google.cloud.tools.jib.configuration.ImageConfiguration→com.google.cloud.tools.jib.api.ImageReference
- Direction
- jib.configuration uses jib.api, so a change to jib.api can break jib.configuration, while a change to jib.configuration can't break jib.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→2 jib.image uses jib.api.buildplan✕
- Connections
- 5 pairs of types, where a type in jib.image uses a type in jib.api.buildplan.
- The types involved
com.google.cloud.tools.jib.image.Builder→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.image.Builder→com.google.cloud.tools.jib.api.buildplan.Portcom.google.cloud.tools.jib.image.Image→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.image.Image→com.google.cloud.tools.jib.api.buildplan.Portcom.google.cloud.tools.jib.image.ReproducibleLayerBuilder→com.google.cloud.tools.jib.api.buildplan.FileEntry
- Direction
- jib.image uses jib.api.buildplan, so a change to jib.api.buildplan can break jib.image, while a change to jib.image can't break jib.api.buildplan.
- Position
- Below the diagonal: jib.image uses a module listed above it, which is the healthy direction.
23→15 jib.image uses jib.blob✕
- Connections
- 9 pairs of types, where a type in jib.image uses a type in jib.blob.
- The types involved
com.google.cloud.tools.jib.image.DigestOnlyLayer→com.google.cloud.tools.jib.blob.Blobcom.google.cloud.tools.jib.image.DigestOnlyLayer→com.google.cloud.tools.jib.blob.BlobDescriptorcom.google.cloud.tools.jib.image.Layer→com.google.cloud.tools.jib.blob.Blobcom.google.cloud.tools.jib.image.Layer→com.google.cloud.tools.jib.blob.BlobDescriptorcom.google.cloud.tools.jib.image.ReferenceLayer→com.google.cloud.tools.jib.blob.Blobcom.google.cloud.tools.jib.image.ReferenceLayer→com.google.cloud.tools.jib.blob.BlobDescriptorcom.google.cloud.tools.jib.image.ReferenceNoDiffIdLayer→com.google.cloud.tools.jib.blob.Blobcom.google.cloud.tools.jib.image.ReferenceNoDiffIdLayer→com.google.cloud.tools.jib.blob.BlobDescriptorcom.google.cloud.tools.jib.image.ReproducibleLayerBuilder→com.google.cloud.tools.jib.blob.Blob
- Direction
- jib.image uses jib.blob, so a change to jib.blob can break jib.image, while a change to jib.image can't break jib.blob.
- Position
- Below the diagonal: jib.image uses a module listed above it, which is the healthy direction.
23→19 jib.image uses jib.image.json✕
- Connections
- 4 pairs of types, where a type in jib.image uses a type in jib.image.json.
- The types involved
com.google.cloud.tools.jib.image.Builder→com.google.cloud.tools.jib.image.json.HistoryEntrycom.google.cloud.tools.jib.image.Builder→com.google.cloud.tools.jib.image.json.ManifestTemplatecom.google.cloud.tools.jib.image.Image→com.google.cloud.tools.jib.image.json.HistoryEntrycom.google.cloud.tools.jib.image.Image→com.google.cloud.tools.jib.image.json.ManifestTemplate
- Direction
- jib.image uses jib.image.json, so a change to jib.image.json can break jib.image, while a change to jib.image can't break jib.image.json.
- Position
- Below the diagonal: jib.image uses a module listed above it, which is the healthy direction.
23→22 jib.image uses jib.configuration✕
- Connections
- 2 pairs of types, where a type in jib.image uses a type in jib.configuration.
- The types involved
com.google.cloud.tools.jib.image.Builder→com.google.cloud.tools.jib.configuration.DockerHealthCheckcom.google.cloud.tools.jib.image.Image→com.google.cloud.tools.jib.configuration.DockerHealthCheck
- Direction
- jib.image uses jib.configuration, so a change to jib.configuration can break jib.image, while a change to jib.image can't break jib.configuration.
- Position
- Below the diagonal: jib.image uses a module listed above it, which is the healthy direction.
23→26 jib.image uses jib.api part of a loop✕
- Connections
- 5 pairs of types, where a type in jib.image uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.image.DigestOnlyLayer→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.image.ImageTarball→com.google.cloud.tools.jib.api.ImageReferencecom.google.cloud.tools.jib.image.Layer→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.image.ReferenceLayer→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.image.ReferenceNoDiffIdLayer→com.google.cloud.tools.jib.api.DescriptorDigest
- Direction
- jib.image uses jib.api, so a change to jib.api can break jib.image, while a change to jib.image can't break jib.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→2 jib.cache uses jib.api.buildplan✕
- Connections
- 3 pairs of types, where a type in jib.cache uses a type in jib.api.buildplan.
- The types involved
com.google.cloud.tools.jib.cache.Cache→com.google.cloud.tools.jib.api.buildplan.FileEntrycom.google.cloud.tools.jib.cache.LayerEntriesSelector→com.google.cloud.tools.jib.api.buildplan.FileEntrycom.google.cloud.tools.jib.cache.LayerEntryTemplate→com.google.cloud.tools.jib.api.buildplan.FileEntry
- Direction
- jib.cache uses jib.api.buildplan, so a change to jib.api.buildplan can break jib.cache, while a change to jib.cache can't break jib.api.buildplan.
- Position
- Below the diagonal: jib.cache uses a module listed above it, which is the healthy direction.
24→4 jib.cache uses jib.json✕
- Connections
- 2 pairs of types, where a type in jib.cache uses a type in jib.json.
- The types involved
com.google.cloud.tools.jib.cache.CacheStorageWriter→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.cache.LayerEntryTemplate→com.google.cloud.tools.jib.json.JsonTemplate
- Direction
- jib.cache uses jib.json, so a change to jib.json can break jib.cache, while a change to jib.cache can't break jib.json.
- Position
- Below the diagonal: jib.cache uses a module listed above it, which is the healthy direction.
24→15 jib.cache uses jib.blob✕
- Connections
- 5 pairs of types, where a type in jib.cache uses a type in jib.blob.
- The types involved
com.google.cloud.tools.jib.cache.Builder→com.google.cloud.tools.jib.blob.Blobcom.google.cloud.tools.jib.cache.Cache→com.google.cloud.tools.jib.blob.Blobcom.google.cloud.tools.jib.cache.CacheStorageWriter→com.google.cloud.tools.jib.blob.Blobcom.google.cloud.tools.jib.cache.CachedLayer→com.google.cloud.tools.jib.blob.Blobcom.google.cloud.tools.jib.cache.CachedLayer→com.google.cloud.tools.jib.blob.BlobDescriptor
- Direction
- jib.cache uses jib.blob, so a change to jib.blob can break jib.cache, while a change to jib.cache can't break jib.blob.
- Position
- Below the diagonal: jib.cache uses a module listed above it, which is the healthy direction.
24→19 jib.cache uses jib.image.json✕
- Connections
- 10 pairs of types, where a type in jib.cache uses a type in jib.image.json.
- The types involved
com.google.cloud.tools.jib.cache.Cache→com.google.cloud.tools.jib.image.json.BuildableManifestTemplatecom.google.cloud.tools.jib.cache.Cache→com.google.cloud.tools.jib.image.json.ContainerConfigurationTemplatecom.google.cloud.tools.jib.cache.Cache→com.google.cloud.tools.jib.image.json.ImageMetadataTemplatecom.google.cloud.tools.jib.cache.Cache→com.google.cloud.tools.jib.image.json.ManifestTemplatecom.google.cloud.tools.jib.cache.Cache→com.google.cloud.tools.jib.image.json.V21ManifestTemplatecom.google.cloud.tools.jib.cache.CacheStorageReader→com.google.cloud.tools.jib.image.json.ContainerConfigurationTemplatecom.google.cloud.tools.jib.cache.CacheStorageReader→com.google.cloud.tools.jib.image.json.ImageMetadataTemplatecom.google.cloud.tools.jib.cache.CacheStorageReader→com.google.cloud.tools.jib.image.json.ManifestTemplatecom.google.cloud.tools.jib.cache.CacheStorageWriter→com.google.cloud.tools.jib.image.json.ContainerConfigurationTemplatecom.google.cloud.tools.jib.cache.CacheStorageWriter→com.google.cloud.tools.jib.image.json.ImageMetadataTemplate
- Direction
- jib.cache uses jib.image.json, so a change to jib.image.json can break jib.cache, while a change to jib.cache can't break jib.image.json.
- Position
- Below the diagonal: jib.cache uses a module listed above it, which is the healthy direction.
24→23 jib.cache uses jib.image✕
- Connections
- 1 pair of types, where a type in jib.cache uses a type in jib.image.
- The types involved
com.google.cloud.tools.jib.cache.CachedLayer→com.google.cloud.tools.jib.image.Layer
- Direction
- jib.cache uses jib.image, so a change to jib.image can break jib.cache, while a change to jib.cache can't break jib.image.
- Position
- Below the diagonal: jib.cache uses a module listed above it, which is the healthy direction.
24→26 jib.cache uses jib.api part of a loop✕
- Connections
- 12 pairs of types, where a type in jib.cache uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.cache.Builder→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.cache.Cache→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.cache.Cache→com.google.cloud.tools.jib.api.ImageReferencecom.google.cloud.tools.jib.cache.CacheStorageFiles→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.cache.CacheStorageFiles→com.google.cloud.tools.jib.api.ImageReferencecom.google.cloud.tools.jib.cache.CacheStorageReader→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.cache.CacheStorageReader→com.google.cloud.tools.jib.api.ImageReferencecom.google.cloud.tools.jib.cache.CacheStorageWriter→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.cache.CacheStorageWriter→com.google.cloud.tools.jib.api.ImageReferencecom.google.cloud.tools.jib.cache.CachedLayer→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.cache.LayerEntriesSelector→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.cache.WrittenLayer→com.google.cloud.tools.jib.api.DescriptorDigest
- Direction
- jib.cache uses jib.api, so a change to jib.api can break jib.cache, while a change to jib.cache can't break jib.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→2 jib.builder.steps uses jib.api.buildplan✕
- Connections
- 2 pairs of types, where a type in jib.builder.steps uses a type in jib.api.buildplan.
- The types involved
com.google.cloud.tools.jib.builder.steps.BuildAndCacheApplicationLayerStep→com.google.cloud.tools.jib.api.buildplan.FileEntriesLayercom.google.cloud.tools.jib.builder.steps.PullBaseImageStep→com.google.cloud.tools.jib.api.buildplan.Platform
- Direction
- jib.builder.steps uses jib.api.buildplan, so a change to jib.api.buildplan can break jib.builder.steps, while a change to jib.builder.steps can't break jib.api.buildplan.
- Position
- Below the diagonal: jib.builder.steps uses a module listed above it, which is the healthy direction.
25→3 jib.builder.steps uses jib.filesystem✕
- Connections
- 2 pairs of types, where a type in jib.builder.steps uses a type in jib.filesystem.
- The types involved
com.google.cloud.tools.jib.builder.steps.LocalBaseImageSteps→com.google.cloud.tools.jib.filesystem.TempDirectoryProvidercom.google.cloud.tools.jib.builder.steps.StepsRunner→com.google.cloud.tools.jib.filesystem.TempDirectoryProvider
- Direction
- jib.builder.steps uses jib.filesystem, so a change to jib.filesystem can break jib.builder.steps, while a change to jib.builder.steps can't break jib.filesystem.
- Position
- Below the diagonal: jib.builder.steps uses a module listed above it, which is the healthy direction.
25→7 jib.builder.steps uses jib.event✕
- Connections
- 2 pairs of types, where a type in jib.builder.steps uses a type in jib.event.
- The types involved
com.google.cloud.tools.jib.builder.steps.RegistryCredentialRetriever→com.google.cloud.tools.jib.event.EventHandlerscom.google.cloud.tools.jib.builder.steps.StepsRunner→com.google.cloud.tools.jib.event.EventHandlers
- Direction
- jib.builder.steps uses jib.event, so a change to jib.event can break jib.builder.steps, while a change to jib.builder.steps can't break jib.event.
- Position
- Below the diagonal: jib.builder.steps uses a module listed above it, which is the healthy direction.
25→8 jib.builder.steps uses jib.event.progress✕
- Connections
- 1 pair of types, where a type in jib.builder.steps uses a type in jib.event.progress.
- The types involved
com.google.cloud.tools.jib.builder.steps.ThrottledProgressEventDispatcherWrapper→com.google.cloud.tools.jib.event.progress.ThrottledAccumulatingConsumer
- Direction
- jib.builder.steps uses jib.event.progress, so a change to jib.event.progress can break jib.builder.steps, while a change to jib.builder.steps can't break jib.event.progress.
- Position
- Below the diagonal: jib.builder.steps uses a module listed above it, which is the healthy direction.
25→15 jib.builder.steps uses jib.blob✕
- Connections
- 9 pairs of types, where a type in jib.builder.steps uses a type in jib.blob.
- The types involved
com.google.cloud.tools.jib.builder.steps.PreparedLayer→com.google.cloud.tools.jib.blob.Blobcom.google.cloud.tools.jib.builder.steps.PreparedLayer→com.google.cloud.tools.jib.blob.BlobDescriptorcom.google.cloud.tools.jib.builder.steps.PushBlobStep→com.google.cloud.tools.jib.blob.Blobcom.google.cloud.tools.jib.builder.steps.PushBlobStep→com.google.cloud.tools.jib.blob.BlobDescriptorcom.google.cloud.tools.jib.builder.steps.PushContainerConfigurationStep→com.google.cloud.tools.jib.blob.BlobDescriptorcom.google.cloud.tools.jib.builder.steps.PushImageStep→com.google.cloud.tools.jib.blob.BlobDescriptorcom.google.cloud.tools.jib.builder.steps.PushLayerStep→com.google.cloud.tools.jib.blob.BlobDescriptorcom.google.cloud.tools.jib.builder.steps.StepResults→com.google.cloud.tools.jib.blob.BlobDescriptorcom.google.cloud.tools.jib.builder.steps.StepsRunner→com.google.cloud.tools.jib.blob.BlobDescriptor
- Direction
- jib.builder.steps uses jib.blob, so a change to jib.blob can break jib.builder.steps, while a change to jib.builder.steps can't break jib.blob.
- Position
- Below the diagonal: jib.builder.steps uses a module listed above it, which is the healthy direction.
25→17 jib.builder.steps uses jib.builder✕
- Connections
- 18 pairs of types, where a type in jib.builder.steps uses a type in jib.builder.
- The types involved
com.google.cloud.tools.jib.builder.steps.AuthenticatePushStep→com.google.cloud.tools.jib.builder.Factorycom.google.cloud.tools.jib.builder.steps.BuildAndCacheApplicationLayerStep→com.google.cloud.tools.jib.builder.Factorycom.google.cloud.tools.jib.builder.steps.BuildImageStep→com.google.cloud.tools.jib.builder.Factorycom.google.cloud.tools.jib.builder.steps.BuildManifestListOrSingleManifestStep→com.google.cloud.tools.jib.builder.Factorycom.google.cloud.tools.jib.builder.steps.CheckManifestStep→com.google.cloud.tools.jib.builder.Factorycom.google.cloud.tools.jib.builder.steps.LoadDockerStep→com.google.cloud.tools.jib.builder.Factorycom.google.cloud.tools.jib.builder.steps.LocalBaseImageSteps→com.google.cloud.tools.jib.builder.Factorycom.google.cloud.tools.jib.builder.steps.ObtainBaseImageLayerStep→com.google.cloud.tools.jib.builder.Factorycom.google.cloud.tools.jib.builder.steps.PullBaseImageStep→com.google.cloud.tools.jib.builder.Factorycom.google.cloud.tools.jib.builder.steps.PullBaseImageStep→com.google.cloud.tools.jib.builder.ProgressEventDispatchercom.google.cloud.tools.jib.builder.steps.PushBlobStep→com.google.cloud.tools.jib.builder.Factorycom.google.cloud.tools.jib.builder.steps.PushContainerConfigurationStep→com.google.cloud.tools.jib.builder.Factorycom.google.cloud.tools.jib.builder.steps.PushImageStep→com.google.cloud.tools.jib.builder.Factorycom.google.cloud.tools.jib.builder.steps.PushLayerStep→com.google.cloud.tools.jib.builder.Factorycom.google.cloud.tools.jib.builder.steps.StepsRunner→com.google.cloud.tools.jib.builder.Factorycom.google.cloud.tools.jib.builder.steps.ThrottledProgressEventDispatcherWrapper→com.google.cloud.tools.jib.builder.Factorycom.google.cloud.tools.jib.builder.steps.ThrottledProgressEventDispatcherWrapper→com.google.cloud.tools.jib.builder.ProgressEventDispatchercom.google.cloud.tools.jib.builder.steps.WriteTarFileStep→com.google.cloud.tools.jib.builder.Factory
- Direction
- jib.builder.steps uses jib.builder, so a change to jib.builder can break jib.builder.steps, while a change to jib.builder.steps can't break jib.builder.
- Position
- Below the diagonal: jib.builder.steps uses a module listed above it, which is the healthy direction.
25→19 jib.builder.steps uses jib.image.json✕
- Connections
- 12 pairs of types, where a type in jib.builder.steps uses a type in jib.image.json.
- The types involved
com.google.cloud.tools.jib.builder.steps.BuildManifestListOrSingleManifestStep→com.google.cloud.tools.jib.image.json.ManifestTemplatecom.google.cloud.tools.jib.builder.steps.BuildResult→com.google.cloud.tools.jib.image.json.BuildableManifestTemplatecom.google.cloud.tools.jib.builder.steps.CheckManifestStep→com.google.cloud.tools.jib.image.json.ManifestTemplatecom.google.cloud.tools.jib.builder.steps.LocalBaseImageSteps→com.google.cloud.tools.jib.image.json.ContainerConfigurationTemplatecom.google.cloud.tools.jib.builder.steps.LocalImage→com.google.cloud.tools.jib.image.json.ContainerConfigurationTemplatecom.google.cloud.tools.jib.builder.steps.PlatformChecker→com.google.cloud.tools.jib.image.json.ContainerConfigurationTemplatecom.google.cloud.tools.jib.builder.steps.PullBaseImageStep→com.google.cloud.tools.jib.image.json.ContainerConfigurationTemplatecom.google.cloud.tools.jib.builder.steps.PullBaseImageStep→com.google.cloud.tools.jib.image.json.ManifestAndConfigTemplatecom.google.cloud.tools.jib.builder.steps.PullBaseImageStep→com.google.cloud.tools.jib.image.json.ManifestListTemplatecom.google.cloud.tools.jib.builder.steps.PushImageStep→com.google.cloud.tools.jib.image.json.ManifestTemplatecom.google.cloud.tools.jib.builder.steps.StepResults→com.google.cloud.tools.jib.image.json.ManifestTemplatecom.google.cloud.tools.jib.builder.steps.StepsRunner→com.google.cloud.tools.jib.image.json.ManifestTemplate
- Direction
- jib.builder.steps uses jib.image.json, so a change to jib.image.json can break jib.builder.steps, while a change to jib.builder.steps can't break jib.image.json.
- Position
- Below the diagonal: jib.builder.steps uses a module listed above it, which is the healthy direction.
25→21 jib.builder.steps uses jib.registry✕
- Connections
- 14 pairs of types, where a type in jib.builder.steps uses a type in jib.registry.
- The types involved
com.google.cloud.tools.jib.builder.steps.AuthenticatePushStep→com.google.cloud.tools.jib.registry.RegistryClientcom.google.cloud.tools.jib.builder.steps.CheckManifestStep→com.google.cloud.tools.jib.registry.ManifestAndDigestcom.google.cloud.tools.jib.builder.steps.CheckManifestStep→com.google.cloud.tools.jib.registry.RegistryClientcom.google.cloud.tools.jib.builder.steps.ImagesAndRegistryClient→com.google.cloud.tools.jib.registry.RegistryClientcom.google.cloud.tools.jib.builder.steps.ObtainBaseImageLayerStep→com.google.cloud.tools.jib.registry.RegistryClientcom.google.cloud.tools.jib.builder.steps.PullBaseImageStep→com.google.cloud.tools.jib.registry.ManifestAndDigestcom.google.cloud.tools.jib.builder.steps.PullBaseImageStep→com.google.cloud.tools.jib.registry.RegistryClientcom.google.cloud.tools.jib.builder.steps.PushBlobStep→com.google.cloud.tools.jib.registry.RegistryClientcom.google.cloud.tools.jib.builder.steps.PushContainerConfigurationStep→com.google.cloud.tools.jib.registry.RegistryClientcom.google.cloud.tools.jib.builder.steps.PushImageStep→com.google.cloud.tools.jib.registry.RegistryClientcom.google.cloud.tools.jib.builder.steps.PushLayerStep→com.google.cloud.tools.jib.registry.RegistryClientcom.google.cloud.tools.jib.builder.steps.StepResults→com.google.cloud.tools.jib.registry.ManifestAndDigestcom.google.cloud.tools.jib.builder.steps.StepResults→com.google.cloud.tools.jib.registry.RegistryClientcom.google.cloud.tools.jib.builder.steps.StepsRunner→com.google.cloud.tools.jib.registry.ManifestAndDigest
- Direction
- jib.builder.steps uses jib.registry, so a change to jib.registry can break jib.builder.steps, while a change to jib.builder.steps can't break jib.registry.
- Position
- Below the diagonal: jib.builder.steps uses a module listed above it, which is the healthy direction.
25→22 jib.builder.steps uses jib.configuration✕
- Connections
- 19 pairs of types, where a type in jib.builder.steps uses a type in jib.configuration.
- The types involved
com.google.cloud.tools.jib.builder.steps.AuthenticatePushStep→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.builder.steps.BuildAndCacheApplicationLayerStep→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.builder.steps.BuildImageStep→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.builder.steps.BuildImageStep→com.google.cloud.tools.jib.configuration.ContainerConfigurationcom.google.cloud.tools.jib.builder.steps.BuildManifestListOrSingleManifestStep→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.builder.steps.CheckManifestStep→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.builder.steps.LoadDockerStep→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.builder.steps.LocalBaseImageSteps→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.builder.steps.ObtainBaseImageLayerStep→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.builder.steps.PlatformChecker→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.builder.steps.PullBaseImageStep→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.builder.steps.PushBlobStep→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.builder.steps.PushContainerConfigurationStep→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.builder.steps.PushImageStep→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.builder.steps.PushLayerStep→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.builder.steps.RegistryCredentialRetriever→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.builder.steps.RegistryCredentialRetriever→com.google.cloud.tools.jib.configuration.ImageConfigurationcom.google.cloud.tools.jib.builder.steps.StepsRunner→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.builder.steps.WriteTarFileStep→com.google.cloud.tools.jib.configuration.BuildContext
- Direction
- jib.builder.steps uses jib.configuration, so a change to jib.configuration can break jib.builder.steps, while a change to jib.builder.steps can't break jib.configuration.
- Position
- Below the diagonal: jib.builder.steps uses a module listed above it, which is the healthy direction.
25→23 jib.builder.steps uses jib.image✕
- Connections
- 14 pairs of types, where a type in jib.builder.steps uses a type in jib.image.
- The types involved
com.google.cloud.tools.jib.builder.steps.BuildImageStep→com.google.cloud.tools.jib.image.Imagecom.google.cloud.tools.jib.builder.steps.BuildManifestListOrSingleManifestStep→com.google.cloud.tools.jib.image.Imagecom.google.cloud.tools.jib.builder.steps.BuildResult→com.google.cloud.tools.jib.image.Imagecom.google.cloud.tools.jib.builder.steps.Builder→com.google.cloud.tools.jib.image.Layercom.google.cloud.tools.jib.builder.steps.ImagesAndRegistryClient→com.google.cloud.tools.jib.image.Imagecom.google.cloud.tools.jib.builder.steps.LoadDockerStep→com.google.cloud.tools.jib.image.Imagecom.google.cloud.tools.jib.builder.steps.ObtainBaseImageLayerStep→com.google.cloud.tools.jib.image.Layercom.google.cloud.tools.jib.builder.steps.PreparedLayer→com.google.cloud.tools.jib.image.Layercom.google.cloud.tools.jib.builder.steps.PullBaseImageStep→com.google.cloud.tools.jib.image.Imagecom.google.cloud.tools.jib.builder.steps.PushContainerConfigurationStep→com.google.cloud.tools.jib.image.Imagecom.google.cloud.tools.jib.builder.steps.PushImageStep→com.google.cloud.tools.jib.image.Imagecom.google.cloud.tools.jib.builder.steps.StepResults→com.google.cloud.tools.jib.image.Imagecom.google.cloud.tools.jib.builder.steps.StepsRunner→com.google.cloud.tools.jib.image.Imagecom.google.cloud.tools.jib.builder.steps.WriteTarFileStep→com.google.cloud.tools.jib.image.Image
- Direction
- jib.builder.steps uses jib.image, so a change to jib.image can break jib.builder.steps, while a change to jib.builder.steps can't break jib.image.
- Position
- Below the diagonal: jib.builder.steps uses a module listed above it, which is the healthy direction.
25→24 jib.builder.steps uses jib.cache✕
- Connections
- 1 pair of types, where a type in jib.builder.steps uses a type in jib.cache.
- The types involved
com.google.cloud.tools.jib.builder.steps.LocalBaseImageSteps→com.google.cloud.tools.jib.cache.Cache
- Direction
- jib.builder.steps uses jib.cache, so a change to jib.cache can break jib.builder.steps, while a change to jib.builder.steps can't break jib.cache.
- Position
- Below the diagonal: jib.builder.steps uses a module listed above it, which is the healthy direction.
25→26 jib.builder.steps uses jib.api part of a loop✕
- Connections
- 11 pairs of types, where a type in jib.builder.steps uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.builder.steps.BlobExistenceChecker→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.builder.steps.BuildResult→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.builder.steps.LoadDockerStep→com.google.cloud.tools.jib.api.DockerClientcom.google.cloud.tools.jib.builder.steps.LocalBaseImageSteps→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.builder.steps.LocalBaseImageSteps→com.google.cloud.tools.jib.api.DockerClientcom.google.cloud.tools.jib.builder.steps.LocalBaseImageSteps→com.google.cloud.tools.jib.api.ImageDetailscom.google.cloud.tools.jib.builder.steps.PreparedLayer→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.builder.steps.PushImageStep→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.builder.steps.RegistryCredentialRetriever→com.google.cloud.tools.jib.api.Credentialcom.google.cloud.tools.jib.builder.steps.StepsRunner→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.builder.steps.StepsRunner→com.google.cloud.tools.jib.api.DockerClient
- Direction
- jib.builder.steps uses jib.api, so a change to jib.api can break jib.builder.steps, while a change to jib.builder.steps can't break jib.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→2 jib.api uses jib.api.buildplan✕
- Connections
- 24 pairs of types, where a type in jib.api uses a type in jib.api.buildplan.
- The types involved
com.google.cloud.tools.jib.api.Builder→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.api.Builder→com.google.cloud.tools.jib.api.buildplan.Buildercom.google.cloud.tools.jib.api.Builder→com.google.cloud.tools.jib.api.buildplan.FilePermissionscom.google.cloud.tools.jib.api.Builder→com.google.cloud.tools.jib.api.buildplan.FilePermissionsProvidercom.google.cloud.tools.jib.api.Builder→com.google.cloud.tools.jib.api.buildplan.ModificationTimeProvidercom.google.cloud.tools.jib.api.JavaContainerBuilder→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.api.JavaContainerBuilder→com.google.cloud.tools.jib.api.buildplan.Buildercom.google.cloud.tools.jib.api.JavaContainerBuilder→com.google.cloud.tools.jib.api.buildplan.ModificationTimeProvidercom.google.cloud.tools.jib.api.JavaContainerBuilder→com.google.cloud.tools.jib.api.buildplan.RelativeUnixPathcom.google.cloud.tools.jib.api.JibContainerBuilder→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.api.JibContainerBuilder→com.google.cloud.tools.jib.api.buildplan.Buildercom.google.cloud.tools.jib.api.JibContainerBuilder→com.google.cloud.tools.jib.api.buildplan.ContainerBuildPlancom.google.cloud.tools.jib.api.JibContainerBuilder→com.google.cloud.tools.jib.api.buildplan.FileEntriesLayercom.google.cloud.tools.jib.api.JibContainerBuilder→com.google.cloud.tools.jib.api.buildplan.ImageFormatcom.google.cloud.tools.jib.api.JibContainerBuilder→com.google.cloud.tools.jib.api.buildplan.Platformcom.google.cloud.tools.jib.api.JibContainerBuilder→com.google.cloud.tools.jib.api.buildplan.Portcom.google.cloud.tools.jib.api.JibContainerDescription→com.google.cloud.tools.jib.api.buildplan.FileEntriesLayercom.google.cloud.tools.jib.api.LayerConfiguration→com.google.cloud.tools.jib.api.buildplan.FileEntriesLayercom.google.cloud.tools.jib.api.LayerConfiguration→com.google.cloud.tools.jib.api.buildplan.FilePermissionsProvidercom.google.cloud.tools.jib.api.LayerConfiguration→com.google.cloud.tools.jib.api.buildplan.ModificationTimeProvidercom.google.cloud.tools.jib.api.LayerEntry→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.api.LayerEntry→com.google.cloud.tools.jib.api.buildplan.FileEntrycom.google.cloud.tools.jib.api.LayerEntry→com.google.cloud.tools.jib.api.buildplan.FilePermissionscom.google.cloud.tools.jib.api.Ports→com.google.cloud.tools.jib.api.buildplan.Port
- Direction
- jib.api uses jib.api.buildplan, so a change to jib.api.buildplan can break jib.api, while a change to jib.api can't break jib.api.buildplan.
- Position
- Below the diagonal: jib.api uses a module listed above it, which is the healthy direction.
26→4 jib.api uses jib.json✕
- Connections
- 1 pair of types, where a type in jib.api uses a type in jib.json.
- The types involved
com.google.cloud.tools.jib.api.DockerInfoDetails→com.google.cloud.tools.jib.json.JsonTemplate
- Direction
- jib.api uses jib.json, so a change to jib.json can break jib.api, while a change to jib.api can't break jib.json.
- Position
- Below the diagonal: jib.api uses a module listed above it, which is the healthy direction.
26→7 jib.api uses jib.event✕
- Connections
- 3 pairs of types, where a type in jib.api uses a type in jib.event.
- The types involved
com.google.cloud.tools.jib.api.Containerizer→com.google.cloud.tools.jib.event.Buildercom.google.cloud.tools.jib.api.Containerizer→com.google.cloud.tools.jib.event.EventHandlerscom.google.cloud.tools.jib.api.JibContainerBuilder→com.google.cloud.tools.jib.event.EventHandlers
- Direction
- jib.api uses jib.event, so a change to jib.event can break jib.api, while a change to jib.api can't break jib.event.
- Position
- Below the diagonal: jib.api uses a module listed above it, which is the healthy direction.
26→18 jib.api uses jib.http✕
- Connections
- 1 pair of types, where a type in jib.api uses a type in jib.http.
- The types involved
com.google.cloud.tools.jib.api.RegistryUnauthorizedException→com.google.cloud.tools.jib.http.ResponseException
- Direction
- jib.api uses jib.http, so a change to jib.http can break jib.api, while a change to jib.api can't break jib.http.
- Position
- Below the diagonal: jib.api uses a module listed above it, which is the healthy direction.
26→22 jib.api uses jib.configuration✕
- Connections
- 6 pairs of types, where a type in jib.api uses a type in jib.configuration.
- The types involved
com.google.cloud.tools.jib.api.Containerizer→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.api.Containerizer→com.google.cloud.tools.jib.configuration.ImageConfigurationcom.google.cloud.tools.jib.api.JibContainer→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.api.JibContainerBuilder→com.google.cloud.tools.jib.configuration.BuildContextcom.google.cloud.tools.jib.api.JibContainerBuilder→com.google.cloud.tools.jib.configuration.Buildercom.google.cloud.tools.jib.api.JibContainerBuilder→com.google.cloud.tools.jib.configuration.ImageConfiguration
- Direction
- jib.api uses jib.configuration, so a change to jib.configuration can break jib.api, while a change to jib.api can't break jib.configuration.
- Position
- Below the diagonal: jib.api uses a module listed above it, which is the healthy direction.
26→23 jib.api uses jib.image✕
- Connections
- 1 pair of types, where a type in jib.api uses a type in jib.image.
- The types involved
com.google.cloud.tools.jib.api.DockerClient→com.google.cloud.tools.jib.image.ImageTarball
- Direction
- jib.api uses jib.image, so a change to jib.image can break jib.api, while a change to jib.api can't break jib.image.
- Position
- Below the diagonal: jib.api uses a module listed above it, which is the healthy direction.
26→25 jib.api uses jib.builder.steps✕
- Connections
- 3 pairs of types, where a type in jib.api uses a type in jib.builder.steps.
- The types involved
com.google.cloud.tools.jib.api.Containerizer→com.google.cloud.tools.jib.builder.steps.BuildResultcom.google.cloud.tools.jib.api.Containerizer→com.google.cloud.tools.jib.builder.steps.StepsRunnercom.google.cloud.tools.jib.api.JibContainer→com.google.cloud.tools.jib.builder.steps.BuildResult
- Direction
- jib.api uses jib.builder.steps, so a change to jib.builder.steps can break jib.api, while a change to jib.api can't break jib.builder.steps.
- Position
- Below the diagonal: jib.api uses a module listed above it, which is the healthy direction.
27→4 jib.docker uses jib.json✕
- Connections
- 2 pairs of types, where a type in jib.docker uses a type in jib.json.
- The types involved
com.google.cloud.tools.jib.docker.DockerImageDetails→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.docker.RootFsTemplate→com.google.cloud.tools.jib.json.JsonTemplate
- Direction
- jib.docker uses jib.json, so a change to jib.json can break jib.docker, while a change to jib.docker can't break jib.json.
- Position
- Below the diagonal: jib.docker uses a module listed above it, which is the healthy direction.
27→23 jib.docker uses jib.image✕
- Connections
- 1 pair of types, where a type in jib.docker uses a type in jib.image.
- The types involved
com.google.cloud.tools.jib.docker.CliDockerClient→com.google.cloud.tools.jib.image.ImageTarball
- Direction
- jib.docker uses jib.image, so a change to jib.image can break jib.docker, while a change to jib.docker can't break jib.image.
- Position
- Below the diagonal: jib.docker uses a module listed above it, which is the healthy direction.
27→26 jib.docker uses jib.api✕
- Connections
- 6 pairs of types, where a type in jib.docker uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.docker.CliDockerClient→com.google.cloud.tools.jib.api.DockerClientcom.google.cloud.tools.jib.docker.CliDockerClient→com.google.cloud.tools.jib.api.DockerInfoDetailscom.google.cloud.tools.jib.docker.CliDockerClient→com.google.cloud.tools.jib.api.ImageReferencecom.google.cloud.tools.jib.docker.DockerClientResolver→com.google.cloud.tools.jib.api.DockerClientcom.google.cloud.tools.jib.docker.DockerImageDetails→com.google.cloud.tools.jib.api.DescriptorDigestcom.google.cloud.tools.jib.docker.DockerImageDetails→com.google.cloud.tools.jib.api.ImageDetails
- Direction
- jib.docker uses jib.api, so a change to jib.api can break jib.docker, while a change to jib.docker can't break jib.api.
- Position
- Below the diagonal: jib.docker uses a module listed above it, which is the healthy direction.
28→26 jib.plugins.common.logging uses jib.api✕
- Connections
- 4 pairs of types, where a type in jib.plugins.common.logging uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.plugins.common.logging.AnsiLoggerWithFooter→com.google.cloud.tools.jib.api.Levelcom.google.cloud.tools.jib.plugins.common.logging.ConsoleLogger→com.google.cloud.tools.jib.api.Levelcom.google.cloud.tools.jib.plugins.common.logging.ConsoleLoggerBuilder→com.google.cloud.tools.jib.api.Levelcom.google.cloud.tools.jib.plugins.common.logging.PlainConsoleLogger→com.google.cloud.tools.jib.api.Level
- Direction
- jib.plugins.common.logging uses jib.api, so a change to jib.api can break jib.plugins.common.logging, while a change to jib.plugins.common.logging can't break jib.api.
- Position
- Below the diagonal: jib.plugins.common.logging uses a module listed above it, which is the healthy direction.
29→4 jib.registry.credentials uses jib.json✕
- Connections
- 1 pair of types, where a type in jib.registry.credentials uses a type in jib.json.
- The types involved
com.google.cloud.tools.jib.registry.credentials.DockerCredentialsTemplate→com.google.cloud.tools.jib.json.JsonTemplate
- Direction
- jib.registry.credentials uses jib.json, so a change to jib.json can break jib.registry.credentials, while a change to jib.registry.credentials can't break jib.json.
- Position
- Below the diagonal: jib.registry.credentials uses a module listed above it, which is the healthy direction.
29→13 jib.registry.credentials uses jib.registry.credentials.json✕
- Connections
- 2 pairs of types, where a type in jib.registry.credentials uses a type in jib.registry.credentials.json.
- The types involved
com.google.cloud.tools.jib.registry.credentials.DockerConfig→com.google.cloud.tools.jib.registry.credentials.json.AuthTemplatecom.google.cloud.tools.jib.registry.credentials.DockerConfig→com.google.cloud.tools.jib.registry.credentials.json.DockerConfigTemplate
- Direction
- jib.registry.credentials uses jib.registry.credentials.json, so a change to jib.registry.credentials.json can break jib.registry.credentials, while a change to jib.registry.credentials can't break jib.registry.credentials.json.
- Position
- Below the diagonal: jib.registry.credentials uses a module listed above it, which is the healthy direction.
29→26 jib.registry.credentials uses jib.api✕
- Connections
- 3 pairs of types, where a type in jib.registry.credentials uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.registry.credentials.DockerConfigCredentialRetriever→com.google.cloud.tools.jib.api.Credentialcom.google.cloud.tools.jib.registry.credentials.DockerConfigCredentialRetriever→com.google.cloud.tools.jib.api.LogEventcom.google.cloud.tools.jib.registry.credentials.DockerCredentialHelper→com.google.cloud.tools.jib.api.Credential
- Direction
- jib.registry.credentials uses jib.api, so a change to jib.api can break jib.registry.credentials, while a change to jib.registry.credentials can't break jib.api.
- Position
- Below the diagonal: jib.registry.credentials uses a module listed above it, which is the healthy direction.
30→2 jib.cli.jar uses jib.api.buildplan✕
- Connections
- 7 pairs of types, where a type in jib.cli.jar uses a type in jib.api.buildplan.
- The types involved
com.google.cloud.tools.jib.cli.jar.JarLayers→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.cli.jar.JarLayers→com.google.cloud.tools.jib.api.buildplan.Buildercom.google.cloud.tools.jib.cli.jar.JarLayers→com.google.cloud.tools.jib.api.buildplan.FileEntriesLayercom.google.cloud.tools.jib.cli.jar.SpringBootExplodedProcessor→com.google.cloud.tools.jib.api.buildplan.FileEntriesLayercom.google.cloud.tools.jib.cli.jar.SpringBootPackagedProcessor→com.google.cloud.tools.jib.api.buildplan.FileEntriesLayercom.google.cloud.tools.jib.cli.jar.StandardExplodedProcessor→com.google.cloud.tools.jib.api.buildplan.FileEntriesLayercom.google.cloud.tools.jib.cli.jar.StandardPackagedProcessor→com.google.cloud.tools.jib.api.buildplan.FileEntriesLayer
- Direction
- jib.cli.jar uses jib.api.buildplan, so a change to jib.api.buildplan can break jib.cli.jar, while a change to jib.cli.jar can't break jib.api.buildplan.
- Position
- Below the diagonal: jib.cli.jar uses a module listed above it, which is the healthy direction.
30→26 jib.cli.jar uses jib.api✕
- Connections
- 1 pair of types, where a type in jib.cli.jar uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.cli.jar.JarFiles→com.google.cloud.tools.jib.api.JibContainerBuilder
- Direction
- jib.cli.jar uses jib.api, so a change to jib.api can break jib.cli.jar, while a change to jib.cli.jar can't break jib.api.
- Position
- Below the diagonal: jib.cli.jar uses a module listed above it, which is the healthy direction.
30→28 jib.cli.jar uses jib.plugins.common.logging✕
- Connections
- 1 pair of types, where a type in jib.cli.jar uses a type in jib.plugins.common.logging.
- The types involved
com.google.cloud.tools.jib.cli.jar.JarFiles→com.google.cloud.tools.jib.plugins.common.logging.ConsoleLogger
- Direction
- jib.cli.jar uses jib.plugins.common.logging, so a change to jib.plugins.common.logging can break jib.cli.jar, while a change to jib.cli.jar can't break jib.plugins.common.logging.
- Position
- Below the diagonal: jib.cli.jar uses a module listed above it, which is the healthy direction.
30→33 jib.cli.jar uses jib.cli part of a loop✕
- Connections
- 8 pairs of types, where a type in jib.cli.jar uses a type in jib.cli.
- The types involved
com.google.cloud.tools.jib.cli.jar.JarFiles→com.google.cloud.tools.jib.cli.ArtifactProcessorcom.google.cloud.tools.jib.cli.jar.JarFiles→com.google.cloud.tools.jib.cli.CommonCliOptionscom.google.cloud.tools.jib.cli.jar.JarFiles→com.google.cloud.tools.jib.cli.CommonContainerConfigCliOptionscom.google.cloud.tools.jib.cli.jar.JarFiles→com.google.cloud.tools.jib.cli.Jarcom.google.cloud.tools.jib.cli.jar.SpringBootExplodedProcessor→com.google.cloud.tools.jib.cli.ArtifactProcessorcom.google.cloud.tools.jib.cli.jar.SpringBootPackagedProcessor→com.google.cloud.tools.jib.cli.ArtifactProcessorcom.google.cloud.tools.jib.cli.jar.StandardExplodedProcessor→com.google.cloud.tools.jib.cli.ArtifactProcessorcom.google.cloud.tools.jib.cli.jar.StandardPackagedProcessor→com.google.cloud.tools.jib.cli.ArtifactProcessor
- Direction
- jib.cli.jar uses jib.cli, so a change to jib.cli can break jib.cli.jar, while a change to jib.cli.jar can't break jib.cli.
- 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→28 jib.cli.logging uses jib.plugins.common.logging✕
- Connections
- 2 pairs of types, where a type in jib.cli.logging uses a type in jib.plugins.common.logging.
- The types involved
com.google.cloud.tools.jib.cli.logging.CliLogger→com.google.cloud.tools.jib.plugins.common.logging.ConsoleLoggercom.google.cloud.tools.jib.cli.logging.CliLogger→com.google.cloud.tools.jib.plugins.common.logging.SingleThreadedExecutor
- Direction
- jib.cli.logging uses jib.plugins.common.logging, so a change to jib.plugins.common.logging can break jib.cli.logging, while a change to jib.cli.logging can't break jib.plugins.common.logging.
- Position
- Below the diagonal: jib.cli.logging uses a module listed above it, which is the healthy direction.
32→26 jib.frontend uses jib.api✕
- Connections
- 4 pairs of types, where a type in jib.frontend uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.frontend.CredentialRetrieverFactory→com.google.cloud.tools.jib.api.Credentialcom.google.cloud.tools.jib.frontend.CredentialRetrieverFactory→com.google.cloud.tools.jib.api.CredentialRetrievercom.google.cloud.tools.jib.frontend.CredentialRetrieverFactory→com.google.cloud.tools.jib.api.ImageReferencecom.google.cloud.tools.jib.frontend.CredentialRetrieverFactory→com.google.cloud.tools.jib.api.LogEvent
- Direction
- jib.frontend uses jib.api, so a change to jib.api can break jib.frontend, while a change to jib.frontend can't break jib.api.
- Position
- Below the diagonal: jib.frontend uses a module listed above it, which is the healthy direction.
32→29 jib.frontend uses jib.registry.credentials✕
- Connections
- 2 pairs of types, where a type in jib.frontend uses a type in jib.registry.credentials.
- The types involved
com.google.cloud.tools.jib.frontend.CredentialRetrieverFactory→com.google.cloud.tools.jib.registry.credentials.DockerConfigCredentialRetrievercom.google.cloud.tools.jib.frontend.DockerCredentialHelperFactory→com.google.cloud.tools.jib.registry.credentials.DockerCredentialHelper
- Direction
- jib.frontend uses jib.registry.credentials, so a change to jib.registry.credentials can break jib.frontend, while a change to jib.frontend can't break jib.registry.credentials.
- Position
- Below the diagonal: jib.frontend uses a module listed above it, which is the healthy direction.
33→2 jib.cli uses jib.api.buildplan✕
- Connections
- 8 pairs of types, where a type in jib.cli uses a type in jib.api.buildplan.
- The types involved
com.google.cloud.tools.jib.cli.ArtifactLayers→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.cli.ArtifactLayers→com.google.cloud.tools.jib.api.buildplan.FileEntriesLayercom.google.cloud.tools.jib.cli.ArtifactProcessor→com.google.cloud.tools.jib.api.buildplan.FileEntriesLayercom.google.cloud.tools.jib.cli.CommonContainerConfigCliOptions→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.cli.CommonContainerConfigCliOptions→com.google.cloud.tools.jib.api.buildplan.ImageFormatcom.google.cloud.tools.jib.cli.CommonContainerConfigCliOptions→com.google.cloud.tools.jib.api.buildplan.Portcom.google.cloud.tools.jib.cli.ContainerBuilders→com.google.cloud.tools.jib.api.buildplan.Platformcom.google.cloud.tools.jib.cli.War→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPath
- Direction
- jib.cli uses jib.api.buildplan, so a change to jib.api.buildplan can break jib.cli, while a change to jib.cli can't break jib.api.buildplan.
- Position
- Below the diagonal: jib.cli uses a module listed above it, which is the healthy direction.
33→12 jib.cli uses jib.plugins.common.globalconfig✕
- Connections
- 1 pair of types, where a type in jib.cli uses a type in jib.plugins.common.globalconfig.
- The types involved
com.google.cloud.tools.jib.cli.JibCli→com.google.cloud.tools.jib.plugins.common.globalconfig.GlobalConfig
- Direction
- jib.cli uses jib.plugins.common.globalconfig, so a change to jib.plugins.common.globalconfig can break jib.cli, while a change to jib.cli can't break jib.plugins.common.globalconfig.
- Position
- Below the diagonal: jib.cli uses a module listed above it, which is the healthy direction.
33→26 jib.cli uses jib.api✕
- Connections
- 5 pairs of types, where a type in jib.cli uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.cli.CommonCliOptions→com.google.cloud.tools.jib.api.Credentialcom.google.cloud.tools.jib.cli.ContainerBuilders→com.google.cloud.tools.jib.api.JibContainerBuildercom.google.cloud.tools.jib.cli.Containerizers→com.google.cloud.tools.jib.api.Containerizercom.google.cloud.tools.jib.cli.JibCli→com.google.cloud.tools.jib.api.JibContainercom.google.cloud.tools.jib.cli.JibCli→com.google.cloud.tools.jib.api.LogEvent
- Direction
- jib.cli uses jib.api, so a change to jib.api can break jib.cli, while a change to jib.cli can't break jib.api.
- Position
- Below the diagonal: jib.cli uses a module listed above it, which is the healthy direction.
33→28 jib.cli uses jib.plugins.common.logging✕
- Connections
- 3 pairs of types, where a type in jib.cli uses a type in jib.plugins.common.logging.
- The types involved
com.google.cloud.tools.jib.cli.ContainerBuilders→com.google.cloud.tools.jib.plugins.common.logging.ConsoleLoggercom.google.cloud.tools.jib.cli.Containerizers→com.google.cloud.tools.jib.plugins.common.logging.ConsoleLoggercom.google.cloud.tools.jib.cli.JibCli→com.google.cloud.tools.jib.plugins.common.logging.ConsoleLogger
- Direction
- jib.cli uses jib.plugins.common.logging, so a change to jib.plugins.common.logging can break jib.cli, while a change to jib.cli can't break jib.plugins.common.logging.
- Position
- Below the diagonal: jib.cli uses a module listed above it, which is the healthy direction.
33→30 jib.cli uses jib.cli.jar✕
- Connections
- 1 pair of types, where a type in jib.cli uses a type in jib.cli.jar.
- The types involved
com.google.cloud.tools.jib.cli.Jar→com.google.cloud.tools.jib.cli.jar.ProcessingMode
- Direction
- jib.cli uses jib.cli.jar, so a change to jib.cli.jar can break jib.cli, while a change to jib.cli can't break jib.cli.jar.
- Position
- Below the diagonal: jib.cli uses a module listed above it, which is the healthy direction.
33→31 jib.cli uses jib.cli.logging✕
- Connections
- 4 pairs of types, where a type in jib.cli uses a type in jib.cli.logging.
- The types involved
com.google.cloud.tools.jib.cli.CommonCliOptions→com.google.cloud.tools.jib.cli.logging.ConsoleOutputcom.google.cloud.tools.jib.cli.CommonCliOptions→com.google.cloud.tools.jib.cli.logging.HttpTraceLevelcom.google.cloud.tools.jib.cli.CommonCliOptions→com.google.cloud.tools.jib.cli.logging.Verbositycom.google.cloud.tools.jib.cli.JibCli→com.google.cloud.tools.jib.cli.logging.Verbosity
- Direction
- jib.cli uses jib.cli.logging, so a change to jib.cli.logging can break jib.cli, while a change to jib.cli can't break jib.cli.logging.
- Position
- Below the diagonal: jib.cli uses a module listed above it, which is the healthy direction.
34→2 jib.plugins.common uses jib.api.buildplan✕
- Connections
- 10 pairs of types, where a type in jib.plugins.common uses a type in jib.api.buildplan.
- The types involved
com.google.cloud.tools.jib.plugins.common.JavaContainerBuilderHelper→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.plugins.common.JavaContainerBuilderHelper→com.google.cloud.tools.jib.api.buildplan.FileEntriesLayercom.google.cloud.tools.jib.plugins.common.JavaContainerBuilderHelper→com.google.cloud.tools.jib.api.buildplan.FilePermissionscom.google.cloud.tools.jib.plugins.common.JavaContainerBuilderHelper→com.google.cloud.tools.jib.api.buildplan.ModificationTimeProvidercom.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor→com.google.cloud.tools.jib.api.buildplan.ModificationTimeProvidercom.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor→com.google.cloud.tools.jib.api.buildplan.Platformcom.google.cloud.tools.jib.plugins.common.RawConfiguration→com.google.cloud.tools.jib.api.buildplan.FilePermissionscom.google.cloud.tools.jib.plugins.common.RawConfiguration→com.google.cloud.tools.jib.api.buildplan.ImageFormatcom.google.cloud.tools.jib.plugins.common.SkaffoldSyncMapTemplate→com.google.cloud.tools.jib.api.buildplan.FileEntry
- Direction
- jib.plugins.common uses jib.api.buildplan, so a change to jib.api.buildplan can break jib.plugins.common, while a change to jib.plugins.common can't break jib.api.buildplan.
- Position
- Below the diagonal: jib.plugins.common uses a module listed above it, which is the healthy direction.
34→4 jib.plugins.common uses jib.json✕
- Connections
- 4 pairs of types, where a type in jib.plugins.common uses a type in jib.json.
- The types involved
com.google.cloud.tools.jib.plugins.common.FileTemplate→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.plugins.common.ImageMetadataOutput→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.plugins.common.SkaffoldSyncMapTemplate→com.google.cloud.tools.jib.json.JsonTemplatecom.google.cloud.tools.jib.plugins.common.VersionJsonTemplate→com.google.cloud.tools.jib.json.JsonTemplate
- Direction
- jib.plugins.common uses jib.json, so a change to jib.json can break jib.plugins.common, while a change to jib.plugins.common can't break jib.json.
- Position
- Below the diagonal: jib.plugins.common uses a module listed above it, which is the healthy direction.
34→5 jib.plugins.common uses jib.plugins.extension✕
- Connections
- 2 pairs of types, where a type in jib.plugins.common uses a type in jib.plugins.extension.
- The types involved
com.google.cloud.tools.jib.plugins.common.PluginExtensionLogger→com.google.cloud.tools.jib.plugins.extension.ExtensionLoggercom.google.cloud.tools.jib.plugins.common.PluginExtensionLogger→com.google.cloud.tools.jib.plugins.extension.LogLevel
- Direction
- jib.plugins.common uses jib.plugins.extension, so a change to jib.plugins.extension can break jib.plugins.common, while a change to jib.plugins.common can't break jib.plugins.extension.
- Position
- Below the diagonal: jib.plugins.common uses a module listed above it, which is the healthy direction.
34→12 jib.plugins.common uses jib.plugins.common.globalconfig✕
- Connections
- 1 pair of types, where a type in jib.plugins.common uses a type in jib.plugins.common.globalconfig.
- The types involved
com.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor→com.google.cloud.tools.jib.plugins.common.globalconfig.GlobalConfig
- Direction
- jib.plugins.common uses jib.plugins.common.globalconfig, so a change to jib.plugins.common.globalconfig can break jib.plugins.common, while a change to jib.plugins.common can't break jib.plugins.common.globalconfig.
- Position
- Below the diagonal: jib.plugins.common uses a module listed above it, which is the healthy direction.
34→16 jib.plugins.common uses jib.event.events✕
- Connections
- 2 pairs of types, where a type in jib.plugins.common uses a type in jib.event.events.
- The types involved
com.google.cloud.tools.jib.plugins.common.TimerEventHandler→com.google.cloud.tools.jib.event.events.Timercom.google.cloud.tools.jib.plugins.common.TimerEventHandler→com.google.cloud.tools.jib.event.events.TimerEvent
- Direction
- jib.plugins.common uses jib.event.events, so a change to jib.event.events can break jib.plugins.common, while a change to jib.plugins.common can't break jib.event.events.
- Position
- Below the diagonal: jib.plugins.common uses a module listed above it, which is the healthy direction.
34→26 jib.plugins.common uses jib.api✕
- Connections
- 25 pairs of types, where a type in jib.plugins.common uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.plugins.common.ConfigurationPropertyValidator→com.google.cloud.tools.jib.api.Credentialcom.google.cloud.tools.jib.plugins.common.ConfigurationPropertyValidator→com.google.cloud.tools.jib.api.ImageReferencecom.google.cloud.tools.jib.plugins.common.ConfigurationPropertyValidator→com.google.cloud.tools.jib.api.LogEventcom.google.cloud.tools.jib.plugins.common.DefaultCredentialRetrievers→com.google.cloud.tools.jib.api.Credentialcom.google.cloud.tools.jib.plugins.common.DefaultCredentialRetrievers→com.google.cloud.tools.jib.api.CredentialRetrievercom.google.cloud.tools.jib.plugins.common.ImageMetadataOutput→com.google.cloud.tools.jib.api.JibContainercom.google.cloud.tools.jib.plugins.common.JavaContainerBuilderHelper→com.google.cloud.tools.jib.api.JavaContainerBuildercom.google.cloud.tools.jib.plugins.common.JavaContainerBuilderHelper→com.google.cloud.tools.jib.api.JibContainerBuildercom.google.cloud.tools.jib.plugins.common.JibBuildRunner→com.google.cloud.tools.jib.api.Containerizercom.google.cloud.tools.jib.plugins.common.JibBuildRunner→com.google.cloud.tools.jib.api.ImageReferencecom.google.cloud.tools.jib.plugins.common.JibBuildRunner→com.google.cloud.tools.jib.api.JibContainercom.google.cloud.tools.jib.plugins.common.JibBuildRunner→com.google.cloud.tools.jib.api.JibContainerBuildercom.google.cloud.tools.jib.plugins.common.JibBuildRunner→com.google.cloud.tools.jib.api.LogEventcom.google.cloud.tools.jib.plugins.common.JibBuildRunner→com.google.cloud.tools.jib.api.RegistryUnauthorizedExceptioncom.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor→com.google.cloud.tools.jib.api.Containerizercom.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor→com.google.cloud.tools.jib.api.ImageReferencecom.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor→com.google.cloud.tools.jib.api.JavaContainerBuildercom.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor→com.google.cloud.tools.jib.api.JibContainerBuildercom.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor→com.google.cloud.tools.jib.api.RegistryImagecom.google.cloud.tools.jib.plugins.common.PluginExtensionLogger→com.google.cloud.tools.jib.api.LogEventcom.google.cloud.tools.jib.plugins.common.ProjectProperties→com.google.cloud.tools.jib.api.Containerizercom.google.cloud.tools.jib.plugins.common.ProjectProperties→com.google.cloud.tools.jib.api.JavaContainerBuildercom.google.cloud.tools.jib.plugins.common.ProjectProperties→com.google.cloud.tools.jib.api.JibContainerBuildercom.google.cloud.tools.jib.plugins.common.ProjectProperties→com.google.cloud.tools.jib.api.LogEventcom.google.cloud.tools.jib.plugins.common.UpdateChecker→com.google.cloud.tools.jib.api.LogEvent
- Direction
- jib.plugins.common uses jib.api, so a change to jib.api can break jib.plugins.common, while a change to jib.plugins.common can't break jib.api.
- Position
- Below the diagonal: jib.plugins.common uses a module listed above it, which is the healthy direction.
34→32 jib.plugins.common uses jib.frontend✕
- Connections
- 1 pair of types, where a type in jib.plugins.common uses a type in jib.frontend.
- The types involved
com.google.cloud.tools.jib.plugins.common.DefaultCredentialRetrievers→com.google.cloud.tools.jib.frontend.CredentialRetrieverFactory
- Direction
- jib.plugins.common uses jib.frontend, so a change to jib.frontend can break jib.plugins.common, while a change to jib.plugins.common can't break jib.frontend.
- Position
- Below the diagonal: jib.plugins.common uses a module listed above it, which is the healthy direction.
35→2 jib.cli.buildfile uses jib.api.buildplan✕
- Connections
- 7 pairs of types, where a type in jib.cli.buildfile uses a type in jib.api.buildplan.
- The types involved
com.google.cloud.tools.jib.cli.buildfile.BuildFileSpec→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.cli.buildfile.BuildFileSpec→com.google.cloud.tools.jib.api.buildplan.ImageFormatcom.google.cloud.tools.jib.cli.buildfile.BuildFileSpec→com.google.cloud.tools.jib.api.buildplan.Portcom.google.cloud.tools.jib.cli.buildfile.CopySpec→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.cli.buildfile.FilePropertiesSpec→com.google.cloud.tools.jib.api.buildplan.FilePermissionscom.google.cloud.tools.jib.cli.buildfile.FilePropertiesStack→com.google.cloud.tools.jib.api.buildplan.FilePermissionscom.google.cloud.tools.jib.cli.buildfile.Layers→com.google.cloud.tools.jib.api.buildplan.FileEntriesLayer
- Direction
- jib.cli.buildfile uses jib.api.buildplan, so a change to jib.api.buildplan can break jib.cli.buildfile, while a change to jib.cli.buildfile can't break jib.api.buildplan.
- Position
- Below the diagonal: jib.cli.buildfile uses a module listed above it, which is the healthy direction.
35→26 jib.cli.buildfile uses jib.api✕
- Connections
- 1 pair of types, where a type in jib.cli.buildfile uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.cli.buildfile.BuildFiles→com.google.cloud.tools.jib.api.JibContainerBuilder
- Direction
- jib.cli.buildfile uses jib.api, so a change to jib.api can break jib.cli.buildfile, while a change to jib.cli.buildfile can't break jib.api.
- Position
- Below the diagonal: jib.cli.buildfile uses a module listed above it, which is the healthy direction.
35→28 jib.cli.buildfile uses jib.plugins.common.logging✕
- Connections
- 1 pair of types, where a type in jib.cli.buildfile uses a type in jib.plugins.common.logging.
- The types involved
com.google.cloud.tools.jib.cli.buildfile.BuildFiles→com.google.cloud.tools.jib.plugins.common.logging.ConsoleLogger
- Direction
- jib.cli.buildfile uses jib.plugins.common.logging, so a change to jib.plugins.common.logging can break jib.cli.buildfile, while a change to jib.cli.buildfile can't break jib.plugins.common.logging.
- Position
- Below the diagonal: jib.cli.buildfile uses a module listed above it, which is the healthy direction.
35→33 jib.cli.buildfile uses jib.cli✕
- Connections
- 2 pairs of types, where a type in jib.cli.buildfile uses a type in jib.cli.
- The types involved
com.google.cloud.tools.jib.cli.buildfile.BuildFiles→com.google.cloud.tools.jib.cli.Buildcom.google.cloud.tools.jib.cli.buildfile.BuildFiles→com.google.cloud.tools.jib.cli.CommonCliOptions
- Direction
- jib.cli.buildfile uses jib.cli, so a change to jib.cli can break jib.cli.buildfile, while a change to jib.cli.buildfile can't break jib.cli.
- Position
- Below the diagonal: jib.cli.buildfile uses a module listed above it, which is the healthy direction.
36→2 jib.cli.war uses jib.api.buildplan✕
- Connections
- 2 pairs of types, where a type in jib.cli.war uses a type in jib.api.buildplan.
- The types involved
com.google.cloud.tools.jib.cli.war.StandardWarExplodedProcessor→com.google.cloud.tools.jib.api.buildplan.AbsoluteUnixPathcom.google.cloud.tools.jib.cli.war.StandardWarExplodedProcessor→com.google.cloud.tools.jib.api.buildplan.FileEntriesLayer
- Direction
- jib.cli.war uses jib.api.buildplan, so a change to jib.api.buildplan can break jib.cli.war, while a change to jib.cli.war can't break jib.api.buildplan.
- Position
- Below the diagonal: jib.cli.war uses a module listed above it, which is the healthy direction.
36→26 jib.cli.war uses jib.api✕
- Connections
- 1 pair of types, where a type in jib.cli.war uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.cli.war.WarFiles→com.google.cloud.tools.jib.api.JibContainerBuilder
- Direction
- jib.cli.war uses jib.api, so a change to jib.api can break jib.cli.war, while a change to jib.cli.war can't break jib.api.
- Position
- Below the diagonal: jib.cli.war uses a module listed above it, which is the healthy direction.
36→28 jib.cli.war uses jib.plugins.common.logging✕
- Connections
- 1 pair of types, where a type in jib.cli.war uses a type in jib.plugins.common.logging.
- The types involved
com.google.cloud.tools.jib.cli.war.WarFiles→com.google.cloud.tools.jib.plugins.common.logging.ConsoleLogger
- Direction
- jib.cli.war uses jib.plugins.common.logging, so a change to jib.plugins.common.logging can break jib.cli.war, while a change to jib.cli.war can't break jib.plugins.common.logging.
- Position
- Below the diagonal: jib.cli.war uses a module listed above it, which is the healthy direction.
36→33 jib.cli.war uses jib.cli✕
- Connections
- 4 pairs of types, where a type in jib.cli.war uses a type in jib.cli.
- The types involved
com.google.cloud.tools.jib.cli.war.StandardWarExplodedProcessor→com.google.cloud.tools.jib.cli.ArtifactProcessorcom.google.cloud.tools.jib.cli.war.WarFiles→com.google.cloud.tools.jib.cli.ArtifactProcessorcom.google.cloud.tools.jib.cli.war.WarFiles→com.google.cloud.tools.jib.cli.CommonCliOptionscom.google.cloud.tools.jib.cli.war.WarFiles→com.google.cloud.tools.jib.cli.CommonContainerConfigCliOptions
- Direction
- jib.cli.war uses jib.cli, so a change to jib.cli can break jib.cli.war, while a change to jib.cli.war can't break jib.cli.
- Position
- Below the diagonal: jib.cli.war uses a module listed above it, which is the healthy direction.
37→34 jib.gradle.skaffold uses jib.plugins.common✕
- Connections
- 1 pair of types, where a type in jib.gradle.skaffold uses a type in jib.plugins.common.
- The types involved
com.google.cloud.tools.jib.gradle.skaffold.FilesTaskV2→com.google.cloud.tools.jib.plugins.common.SkaffoldFilesOutput
- Direction
- jib.gradle.skaffold uses jib.plugins.common, so a change to jib.plugins.common can break jib.gradle.skaffold, while a change to jib.gradle.skaffold can't break jib.plugins.common.
- Position
- Below the diagonal: jib.gradle.skaffold uses a module listed above it, which is the healthy direction.
37→39 jib.gradle.skaffold uses jib.gradle part of a loop✕
- Connections
- 3 pairs of types, where a type in jib.gradle.skaffold uses a type in jib.gradle.
- The types involved
com.google.cloud.tools.jib.gradle.skaffold.FilesTaskV2→com.google.cloud.tools.jib.gradle.JibExtensioncom.google.cloud.tools.jib.gradle.skaffold.InitTask→com.google.cloud.tools.jib.gradle.JibExtensioncom.google.cloud.tools.jib.gradle.skaffold.SyncMapTask→com.google.cloud.tools.jib.gradle.JibExtension
- Direction
- jib.gradle.skaffold uses jib.gradle, so a change to jib.gradle can break jib.gradle.skaffold, while a change to jib.gradle.skaffold can't break jib.gradle.
- 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.
38→2 jib.maven uses jib.api.buildplan✕
- Connections
- 4 pairs of types, where a type in jib.maven uses a type in jib.api.buildplan.
- The types involved
com.google.cloud.tools.jib.maven.MavenProjectProperties→com.google.cloud.tools.jib.api.buildplan.ContainerBuildPlancom.google.cloud.tools.jib.maven.MavenRawConfiguration→com.google.cloud.tools.jib.api.buildplan.FilePermissionscom.google.cloud.tools.jib.maven.MavenRawConfiguration→com.google.cloud.tools.jib.api.buildplan.ImageFormatcom.google.cloud.tools.jib.maven.MojoCommon→com.google.cloud.tools.jib.api.buildplan.FilePermissions
- Direction
- jib.maven uses jib.api.buildplan, so a change to jib.api.buildplan can break jib.maven, while a change to jib.maven can't break jib.api.buildplan.
- Position
- Below the diagonal: jib.maven uses a module listed above it, which is the healthy direction.
38→3 jib.maven uses jib.filesystem✕
- Connections
- 1 pair of types, where a type in jib.maven uses a type in jib.filesystem.
- The types involved
com.google.cloud.tools.jib.maven.MavenProjectProperties→com.google.cloud.tools.jib.filesystem.TempDirectoryProvider
- Direction
- jib.maven uses jib.filesystem, so a change to jib.filesystem can break jib.maven, while a change to jib.maven can't break jib.filesystem.
- Position
- Below the diagonal: jib.maven uses a module listed above it, which is the healthy direction.
38→11 jib.maven uses jib.maven.extension✕
- Connections
- 3 pairs of types, where a type in jib.maven uses a type in jib.maven.extension.
- The types involved
com.google.cloud.tools.jib.maven.JibPluginConfiguration→com.google.cloud.tools.jib.maven.extension.JibMavenPluginExtensioncom.google.cloud.tools.jib.maven.MavenExtensionData→com.google.cloud.tools.jib.maven.extension.MavenDatacom.google.cloud.tools.jib.maven.MavenProjectProperties→com.google.cloud.tools.jib.maven.extension.JibMavenPluginExtension
- Direction
- jib.maven uses jib.maven.extension, so a change to jib.maven.extension can break jib.maven, while a change to jib.maven can't break jib.maven.extension.
- Position
- Below the diagonal: jib.maven uses a module listed above it, which is the healthy direction.
38→12 jib.maven uses jib.plugins.common.globalconfig✕
- Connections
- 1 pair of types, where a type in jib.maven uses a type in jib.plugins.common.globalconfig.
- The types involved
com.google.cloud.tools.jib.maven.MojoCommon→com.google.cloud.tools.jib.plugins.common.globalconfig.GlobalConfig
- Direction
- jib.maven uses jib.plugins.common.globalconfig, so a change to jib.plugins.common.globalconfig can break jib.maven, while a change to jib.maven can't break jib.plugins.common.globalconfig.
- Position
- Below the diagonal: jib.maven uses a module listed above it, which is the healthy direction.
38→26 jib.maven uses jib.api✕
- Connections
- 5 pairs of types, where a type in jib.maven uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.maven.MavenProjectProperties→com.google.cloud.tools.jib.api.Containerizercom.google.cloud.tools.jib.maven.MavenProjectProperties→com.google.cloud.tools.jib.api.JavaContainerBuildercom.google.cloud.tools.jib.maven.MavenProjectProperties→com.google.cloud.tools.jib.api.JibContainerBuildercom.google.cloud.tools.jib.maven.MavenProjectProperties→com.google.cloud.tools.jib.api.LayerTypecom.google.cloud.tools.jib.maven.MavenProjectProperties→com.google.cloud.tools.jib.api.LogEvent
- Direction
- jib.maven uses jib.api, so a change to jib.api can break jib.maven, while a change to jib.maven can't break jib.api.
- Position
- Below the diagonal: jib.maven uses a module listed above it, which is the healthy direction.
38→28 jib.maven uses jib.plugins.common.logging✕
- Connections
- 2 pairs of types, where a type in jib.maven uses a type in jib.plugins.common.logging.
- The types involved
com.google.cloud.tools.jib.maven.MavenProjectProperties→com.google.cloud.tools.jib.plugins.common.logging.ConsoleLoggercom.google.cloud.tools.jib.maven.MavenProjectProperties→com.google.cloud.tools.jib.plugins.common.logging.SingleThreadedExecutor
- Direction
- jib.maven uses jib.plugins.common.logging, so a change to jib.plugins.common.logging can break jib.maven, while a change to jib.maven can't break jib.plugins.common.logging.
- Position
- Below the diagonal: jib.maven uses a module listed above it, which is the healthy direction.
38→34 jib.maven uses jib.plugins.common✕
- Connections
- 20 pairs of types, where a type in jib.maven uses a type in jib.plugins.common.
- The types involved
com.google.cloud.tools.jib.maven.1→com.google.cloud.tools.jib.plugins.common.AuthPropertycom.google.cloud.tools.jib.maven.AuthConfiguration→com.google.cloud.tools.jib.plugins.common.AuthPropertycom.google.cloud.tools.jib.maven.CredHelperParameters→com.google.cloud.tools.jib.plugins.common.CredHelperConfigurationcom.google.cloud.tools.jib.maven.ExtensionParameters→com.google.cloud.tools.jib.plugins.common.ExtensionConfigurationcom.google.cloud.tools.jib.maven.ExtraDirectoryParameters→com.google.cloud.tools.jib.plugins.common.ExtraDirectoriesConfigurationcom.google.cloud.tools.jib.maven.JibPluginConfiguration→com.google.cloud.tools.jib.plugins.common.CredHelperConfigurationcom.google.cloud.tools.jib.maven.MavenHelpfulSuggestions→com.google.cloud.tools.jib.plugins.common.HelpfulSuggestionscom.google.cloud.tools.jib.maven.MavenProjectProperties→com.google.cloud.tools.jib.plugins.common.ContainerizingModecom.google.cloud.tools.jib.maven.MavenProjectProperties→com.google.cloud.tools.jib.plugins.common.ExtensionConfigurationcom.google.cloud.tools.jib.maven.MavenProjectProperties→com.google.cloud.tools.jib.plugins.common.ProjectPropertiescom.google.cloud.tools.jib.maven.MavenRawConfiguration→com.google.cloud.tools.jib.plugins.common.AuthPropertycom.google.cloud.tools.jib.maven.MavenRawConfiguration→com.google.cloud.tools.jib.plugins.common.CredHelperConfigurationcom.google.cloud.tools.jib.maven.MavenRawConfiguration→com.google.cloud.tools.jib.plugins.common.ExtensionConfigurationcom.google.cloud.tools.jib.maven.MavenRawConfiguration→com.google.cloud.tools.jib.plugins.common.ExtraDirectoriesConfigurationcom.google.cloud.tools.jib.maven.MavenRawConfiguration→com.google.cloud.tools.jib.plugins.common.PlatformConfigurationcom.google.cloud.tools.jib.maven.MavenRawConfiguration→com.google.cloud.tools.jib.plugins.common.RawConfigurationcom.google.cloud.tools.jib.maven.MavenSettingsServerCredentials→com.google.cloud.tools.jib.plugins.common.AuthPropertycom.google.cloud.tools.jib.maven.MavenSettingsServerCredentials→com.google.cloud.tools.jib.plugins.common.InferredAuthProvidercom.google.cloud.tools.jib.maven.MojoCommon→com.google.cloud.tools.jib.plugins.common.ProjectPropertiescom.google.cloud.tools.jib.maven.PlatformParameters→com.google.cloud.tools.jib.plugins.common.PlatformConfiguration
- Direction
- jib.maven uses jib.plugins.common, so a change to jib.plugins.common can break jib.maven, while a change to jib.maven can't break jib.plugins.common.
- Position
- Below the diagonal: jib.maven uses a module listed above it, which is the healthy direction.
39→2 jib.gradle uses jib.api.buildplan✕
- Connections
- 5 pairs of types, where a type in jib.gradle uses a type in jib.api.buildplan.
- The types involved
com.google.cloud.tools.jib.gradle.ContainerParameters→com.google.cloud.tools.jib.api.buildplan.ImageFormatcom.google.cloud.tools.jib.gradle.GradleProjectProperties→com.google.cloud.tools.jib.api.buildplan.ContainerBuildPlancom.google.cloud.tools.jib.gradle.GradleRawConfiguration→com.google.cloud.tools.jib.api.buildplan.FilePermissionscom.google.cloud.tools.jib.gradle.GradleRawConfiguration→com.google.cloud.tools.jib.api.buildplan.ImageFormatcom.google.cloud.tools.jib.gradle.TaskCommon→com.google.cloud.tools.jib.api.buildplan.FilePermissions
- Direction
- jib.gradle uses jib.api.buildplan, so a change to jib.api.buildplan can break jib.gradle, while a change to jib.gradle can't break jib.api.buildplan.
- Position
- Below the diagonal: jib.gradle uses a module listed above it, which is the healthy direction.
39→3 jib.gradle uses jib.filesystem✕
- Connections
- 1 pair of types, where a type in jib.gradle uses a type in jib.filesystem.
- The types involved
com.google.cloud.tools.jib.gradle.GradleProjectProperties→com.google.cloud.tools.jib.filesystem.TempDirectoryProvider
- Direction
- jib.gradle uses jib.filesystem, so a change to jib.filesystem can break jib.gradle, while a change to jib.gradle can't break jib.filesystem.
- Position
- Below the diagonal: jib.gradle uses a module listed above it, which is the healthy direction.
39→9 jib.gradle uses jib.gradle.extension✕
- Connections
- 1 pair of types, where a type in jib.gradle uses a type in jib.gradle.extension.
- The types involved
com.google.cloud.tools.jib.gradle.GradleProjectProperties→com.google.cloud.tools.jib.gradle.extension.JibGradlePluginExtension
- Direction
- jib.gradle uses jib.gradle.extension, so a change to jib.gradle.extension can break jib.gradle, while a change to jib.gradle can't break jib.gradle.extension.
- Position
- Below the diagonal: jib.gradle uses a module listed above it, which is the healthy direction.
39→12 jib.gradle uses jib.plugins.common.globalconfig✕
- Connections
- 1 pair of types, where a type in jib.gradle uses a type in jib.plugins.common.globalconfig.
- The types involved
com.google.cloud.tools.jib.gradle.TaskCommon→com.google.cloud.tools.jib.plugins.common.globalconfig.GlobalConfig
- Direction
- jib.gradle uses jib.plugins.common.globalconfig, so a change to jib.plugins.common.globalconfig can break jib.gradle, while a change to jib.gradle can't break jib.plugins.common.globalconfig.
- Position
- Below the diagonal: jib.gradle uses a module listed above it, which is the healthy direction.
39→26 jib.gradle uses jib.api✕
- Connections
- 4 pairs of types, where a type in jib.gradle uses a type in jib.api.
- The types involved
com.google.cloud.tools.jib.gradle.GradleProjectProperties→com.google.cloud.tools.jib.api.Containerizercom.google.cloud.tools.jib.gradle.GradleProjectProperties→com.google.cloud.tools.jib.api.JavaContainerBuildercom.google.cloud.tools.jib.gradle.GradleProjectProperties→com.google.cloud.tools.jib.api.JibContainerBuildercom.google.cloud.tools.jib.gradle.GradleProjectProperties→com.google.cloud.tools.jib.api.LogEvent
- Direction
- jib.gradle uses jib.api, so a change to jib.api can break jib.gradle, while a change to jib.gradle can't break jib.api.
- Position
- Below the diagonal: jib.gradle uses a module listed above it, which is the healthy direction.
39→28 jib.gradle uses jib.plugins.common.logging✕
- Connections
- 2 pairs of types, where a type in jib.gradle uses a type in jib.plugins.common.logging.
- The types involved
com.google.cloud.tools.jib.gradle.GradleProjectProperties→com.google.cloud.tools.jib.plugins.common.logging.ConsoleLoggercom.google.cloud.tools.jib.gradle.GradleProjectProperties→com.google.cloud.tools.jib.plugins.common.logging.SingleThreadedExecutor
- Direction
- jib.gradle uses jib.plugins.common.logging, so a change to jib.plugins.common.logging can break jib.gradle, while a change to jib.gradle can't break jib.plugins.common.logging.
- Position
- Below the diagonal: jib.gradle uses a module listed above it, which is the healthy direction.
39→34 jib.gradle uses jib.plugins.common✕
- Connections
- 16 pairs of types, where a type in jib.gradle uses a type in jib.plugins.common.
- The types involved
com.google.cloud.tools.jib.gradle.AuthParameters→com.google.cloud.tools.jib.plugins.common.AuthPropertycom.google.cloud.tools.jib.gradle.CredHelperParameters→com.google.cloud.tools.jib.plugins.common.CredHelperConfigurationcom.google.cloud.tools.jib.gradle.ExtensionParameters→com.google.cloud.tools.jib.plugins.common.ExtensionConfigurationcom.google.cloud.tools.jib.gradle.ExtraDirectoryParameters→com.google.cloud.tools.jib.plugins.common.ExtraDirectoriesConfigurationcom.google.cloud.tools.jib.gradle.GradleHelpfulSuggestions→com.google.cloud.tools.jib.plugins.common.HelpfulSuggestionscom.google.cloud.tools.jib.gradle.GradleProjectProperties→com.google.cloud.tools.jib.plugins.common.ContainerizingModecom.google.cloud.tools.jib.gradle.GradleProjectProperties→com.google.cloud.tools.jib.plugins.common.ExtensionConfigurationcom.google.cloud.tools.jib.gradle.GradleProjectProperties→com.google.cloud.tools.jib.plugins.common.ProjectPropertiescom.google.cloud.tools.jib.gradle.GradleRawConfiguration→com.google.cloud.tools.jib.plugins.common.AuthPropertycom.google.cloud.tools.jib.gradle.GradleRawConfiguration→com.google.cloud.tools.jib.plugins.common.CredHelperConfigurationcom.google.cloud.tools.jib.gradle.GradleRawConfiguration→com.google.cloud.tools.jib.plugins.common.ExtensionConfigurationcom.google.cloud.tools.jib.gradle.GradleRawConfiguration→com.google.cloud.tools.jib.plugins.common.ExtraDirectoriesConfigurationcom.google.cloud.tools.jib.gradle.GradleRawConfiguration→com.google.cloud.tools.jib.plugins.common.PlatformConfigurationcom.google.cloud.tools.jib.gradle.GradleRawConfiguration→com.google.cloud.tools.jib.plugins.common.RawConfigurationcom.google.cloud.tools.jib.gradle.PlatformParameters→com.google.cloud.tools.jib.plugins.common.PlatformConfigurationcom.google.cloud.tools.jib.gradle.TaskCommon→com.google.cloud.tools.jib.plugins.common.ProjectProperties
- Direction
- jib.gradle uses jib.plugins.common, so a change to jib.plugins.common can break jib.gradle, while a change to jib.gradle can't break jib.plugins.common.
- Position
- Below the diagonal: jib.gradle uses a module listed above it, which is the healthy direction.
39→37 jib.gradle uses jib.gradle.skaffold✕
- Connections
- 1 pair of types, where a type in jib.gradle uses a type in jib.gradle.skaffold.
- The types involved
com.google.cloud.tools.jib.gradle.JibExtension→com.google.cloud.tools.jib.gradle.skaffold.SkaffoldParameters
- Direction
- jib.gradle uses jib.gradle.skaffold, so a change to jib.gradle.skaffold can break jib.gradle, while a change to jib.gradle can't break jib.gradle.skaffold.
- Position
- Below the diagonal: jib.gradle uses a module listed above it, which is the healthy direction.
40→34 jib.maven.skaffold uses jib.plugins.common✕
- Connections
- 1 pair of types, where a type in jib.maven.skaffold uses a type in jib.plugins.common.
- The types involved
com.google.cloud.tools.jib.maven.skaffold.FilesMojoV2→com.google.cloud.tools.jib.plugins.common.SkaffoldFilesOutput
- Direction
- jib.maven.skaffold uses jib.plugins.common, so a change to jib.plugins.common can break jib.maven.skaffold, while a change to jib.maven.skaffold can't break jib.plugins.common.
- Position
- Below the diagonal: jib.maven.skaffold uses a module listed above it, which is the healthy direction.
40→38 jib.maven.skaffold uses jib.maven✕
- Connections
- 2 pairs of types, where a type in jib.maven.skaffold uses a type in jib.maven.
- The types involved
com.google.cloud.tools.jib.maven.skaffold.InitMojo→com.google.cloud.tools.jib.maven.JibPluginConfigurationcom.google.cloud.tools.jib.maven.skaffold.SyncMapMojo→com.google.cloud.tools.jib.maven.JibPluginConfiguration
- Direction
- jib.maven.skaffold uses jib.maven, so a change to jib.maven can break jib.maven.skaffold, while a change to jib.maven.skaffold can't break jib.maven.
- Position
- Below the diagonal: jib.maven.skaffold 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 42 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle; Resolve the 191 Orphaned file finding(s) in Knowledge Freshness — start with build.gradle (3), JibContainerBuilder.java, JavaContainerBuilder.java; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle. | +11.3 pts | Low | ADR Quality |
| 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. | +8.7 pts | Medium | Architecture documentation |
| Resolve the 191 Orphaned file finding(s) in Knowledge Freshness — start with build.gradle (3), JibContainerBuilder.java, JavaContainerBuilder.java. | +10.6 pts | High | Knowledge Freshness |
| Reconcile the README with reality: jib-gradle-plugin/README.md links to `docs/privacy.md`, but `jib-gradle-plugin/docs/privacy.md` does not exist; jib-maven-plugin/README.md links to `docs/privacy.md`, but `jib-maven-plugin/docs/privacy.md` does not exist. | +3.3 pts | Medium | Documentation accuracy |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.8 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2). | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +1.2 pts | Medium | Observability |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/ContainerParameters.java | 5.9 | Mixed | God Classes: TooManyMethods: ContainerParameters |
| jib-cli/src/main/java/com/google/cloud/tools/jib/cli/buildfile/Layers.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/PluginConfigurationProcessor.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| jib-core/src/main/java/com/google/cloud/tools/jib/image/json/JsonToImageTranslator.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/skaffold/FilesMojoV2.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| jib-core/src/main/java/com/google/cloud/tools/jib/builder/steps/PullBaseImageStep.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/JibPlugin.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.0 | Mixed | Explicit Debt: TodoComment |
| jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/JibPluginConfiguration.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| jib-core/src/main/java/com/google/cloud/tools/jib/api/JibContainerBuilder.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/GradleProjectProperties.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| jib-cli/src/main/java/com/google/cloud/tools/jib/cli/Containerizers.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| jib-core/src/test/java/com/google/cloud/tools/jib/image/ReproducibleLayerBuilderTest.java | 6.6 | Mixed | Explicit Debt: TodoComment |
| jib-core/src/main/java/com/google/cloud/tools/jib/image/json/ManifestAndConfigTemplate.java | 6.6 | Mixed | Explicit Debt: TodoComment |
| jib-core/src/main/java/com/google/cloud/tools/jib/registry/BlobChecker.java | 6.7 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 53 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 53 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, 447 of 458 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`jacocoTestReport`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.java), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — a Gradle build resolved 128 artifact(s) across its subprojects (109 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (build.gradle), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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. These audit 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 audit controls.
- 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. These retention 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 retention controls.
- 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. These data-subject rights 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 data-subject rights controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Layers.toLayers at 24.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Layers.toLayers (cyclomatic 24), PluginConfigurationProcessor.computeEntrypoint (cyclomatic 24), JavaContainerBuilder.toContainerBuilder (cyclomatic 17). — 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 7 together lifts Cyclomatic Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
20 method(s) exceeded the cognitive complexity threshold of 15; the worst was Layers.toLayers at 85.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with Layers.toLayers (cognitive 85), PluginConfigurationProcessor.computeEntrypoint (cognitive 34). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 6.6 to about 7.7/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
16 god class(es) detected.
What to do
- Resolve the 10 TooManyMethods finding(s) in God Classes — start with JibPluginConfiguration.java, JibContainerBuilder.java, ContainerConfigurationTemplate.java. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 4 ClassTooLong finding(s) in God Classes — start with PluginConfigurationProcessor.java, StepsRunner.java, JibPluginConfiguration.java. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with PluginConfigurationProcessor.java. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
23 duplicated block group(s) detected. A further 33 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 1 of the 56 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with ContainerBuilders.java, CliDockerClient.java, FilesMojoV2.java. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with AbsoluteUnixPath.java, ContainerParameters.java, RegistryAuthenticator.java. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with SpringBootPackagedProcessor.java, JibContainerBuilder.java, SkaffoldSyncParameters.java. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
44 production modules (Gradle+Maven), 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 11 of the 44 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
2 of 101 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with ContainerParameters.java, Containerizer.java. — One of this dimension's main actionable groups (2 warning-level).
D10 · Test Quality
6 skipped (6 with a documented reason), 31 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1376 tests.
What to do
- Resolve the 31 No assertions finding(s) in Test Quality — start with ValidatorTest.java (14), CacheStorageReaderTest.java (5), JibSystemPropertiesTest.java (3). — One of this dimension's main actionable groups (31 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 12 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 67 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 9 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. 1 of them resolve to no licence at all on Central, even through their parent POMs; that is missing data, not a violation, and none of them is charged. A further 4 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
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 jib-core/src/main/java/com/google/cloud/tools/jib/image/json/OciIndexTemplate.java. Counted over 129 of the 367 production source files in this repository: 170 are under the ~2,400-byte size floor this dimension measures over, and the remaining 68 have no attributable history left to measure.
D17 · Explicit Debt
57 deducted task-comment markers across 38034 LoC (0.1/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 57 TodoComment finding(s) in Explicit Debt — start with PullBaseImageStep.java (5), ReproducibleLayerBuilderTest.java (4), ManifestAndConfigTemplate.java (4). — One of this dimension's main actionable groups (57 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 13 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 9 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
51 % of calls cross a namespace and 6 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
42 finding(s): 0 critical, 32 high, 9 medium, 1 low. 26 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 16 file(s) — `examples/dropwizard/mvnw` (lines 217–218), `examples/dropwizard/src/main/resources/dropwizard.yml`, `examples/helloworld/gradlew` (lines 144–145, line 146, line 147, …), `examples/java-agent/gradlew` (lines 144–145, line 146, line 147, …), `examples/ktor/gradlew` (lines 144–145, line 146, line 147, …), … (+11 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 25 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 (25 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
194 of 197 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/PluginConfigurationProcessor.java. Counted over 197 of the 367 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 191 Orphaned file finding(s) in Knowledge Freshness — start with build.gradle (3), JibContainerBuilder.java, JavaContainerBuilder.java. — One of this dimension's main actionable groups (191 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with PluginConfigurationProcessor.java, StepsRunner.java, MavenProjectProperties.java. — 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
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 1 end-of-life framework(s), read from 53 platform declaration(s) and 66 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 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
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `ProjectProperties` declares 18 abstract methods: `configureEventHandlers`, `createJibContainerBuilder`, `getClassFiles`, `getDefaultCacheDirectory`, `getDependencies`, `getJarPluginName`, `getMainClassFromJarPlugin`, `getMajorJavaVersion`, `getName`, `getPluginName`, `getToolName`, `getToolVersion`, `getVersion`, `isOffline`, `isWarProject`, `log`, `runPluginExtensions`, `waitForLoggingThread`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/ProjectProperties.java:31
- `RawConfiguration` declares 36 abstract methods: `getAllowInsecureRegistries`, `getAppRoot`, `getContainerizingMode`, `getCreationTime`, `getDigestOutputPath`, `getDockerEnvironment`, `getDockerExecutable`, `getEntrypoint`, `getEnvironment`, `getExpandClasspathDependencies`, `getExtraClasspath`, `getExtraDirectories`, `getExtraDirectoryPermissions`, `getFilesModificationTime`, `getFromAuth`, `getFromCredHelper`, `getFromImage`, `getImageFormat`, `getImageIdOutputPath`, `getImageJsonOutputPath`, `getJvmFlags`, `getLabels`, `getMainClass`, `getPlatforms`, `getPluginExtensions`, `getPorts`, `getProgramArguments`, `getProperty`, `getTarOutputPath`, `getToAuth`, `getToCredHelper`, `getToImage`, `getToTags`, `getUser`, `getVolumes`, `getWorkingDirectory`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/RawConfiguration.java:31
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — jib-core/src/test/java/com/google/cloud/tools/jib/registry/DockerRegistryBearerTokenTest.java:81
What to do
- Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- jib-gradle-plugin/README.md links to `docs/privacy.md`, but `jib-gradle-plugin/docs/privacy.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. — jib-gradle-plugin/README.md:660
- jib-maven-plugin/README.md links to `docs/privacy.md`, but `jib-maven-plugin/docs/privacy.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. — jib-maven-plugin/README.md:742
What to do
- Reconcile the README with reality: jib-gradle-plugin/README.md links to `docs/privacy.md`, but `jib-gradle-plugin/docs/privacy.md` does not exist; jib-maven-plugin/README.md links to `docs/privacy.md`, but `jib-maven-plugin/docs/privacy.md` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 5/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `jib-cli/src/integration-test/resources/jarTest/spring-boot`, `jib-cli/src/integration-test/resources/warTest`, `jib-gradle-plugin/src/integration-test/resources/gradle/projects/spring-boot`, `jib-gradle-plugin/src/integration-test/resources/gradle/projects/war_servlet25`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `maven`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `maven` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
X5 · Nullable reference types
- ~1.12 nullness suppressions per 1k Java source lines — 47 across the 41839 line(s) of the 309 Java file(s) read, counting each `@SuppressWarnings` naming `NullAway`, `nullness` or `null` once however much it covers, and each `castToNonNull(…)` call. Densest: jib-cli/src/main/java/com/google/cloud/tools/jib/cli/CommonCliOptions.java (29), jib-cli/src/main/java/com/google/cloud/tools/jib/cli/Jar.java (5), jib-cli/src/main/java/com/google/cloud/tools/jib/cli/War.java (5). Each one tells the checker to trust the author about null, silencing the very warning the null-marking exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 88% | Strong | Solid. |
| Architecture | 92% | Exemplary | Strongest area. |
| Maturity | 56% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 77% | Strong | Solid. |
| Security | 72% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 5 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: these audit 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 audit 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.
- C4 Data Retention — Not assessed: these retention 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 retention 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.
- C5 Data-Subject Rights — Not assessed: these data-subject rights 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 data-subject rights 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.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 58 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — 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.
- D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
- D12 Dependency Hygiene — Not scored — a Gradle build resolved 128 artifact(s) across its subprojects (109 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, Kotlin not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .java, .kt source were not judged.
- D25 ADR Conformance — no ADRs to check
- 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.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 33 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a 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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 — 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
- X13 Undrained process stream — 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
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — 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
- X2 Cancellation propagation — no C# was loaded; this repository's Java was read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 32 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
Serious — 205 finding(s)
- TodoComment jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/PluginConfigurationProcessor.java:977
- TodoComment jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/ProjectProperties.java:36
- TodoComment jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/ProjectProperties.java:44
- TodoComment jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/JibPluginConfiguration.java:720
- TodoComment jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/skaffold/FilesMojoV2.java:121
- TodoComment jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/skaffold/FilesMojoV2.java:172
- TodoComment jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/skaffold/FilesMojoV2.java:173
- TodoComment jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/skaffold/SyncMapMojo.java:53
- TodoComment jib-gradle-plugin/src/test/java/com/google/cloud/tools/jib/gradle/TestProject.java:32
- TodoComment jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/GradleProjectProperties.java:291
- TodoComment jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/JibPlugin.java:71
- TodoComment jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/skaffold/SyncMapTask.java:62
- TodoComment jib-core/src/test/java/com/google/cloud/tools/jib/image/ReproducibleLayerBuilderTest.java:155
- TodoComment jib-core/src/test/java/com/google/cloud/tools/jib/image/ReproducibleLayerBuilderTest.java:156
- TodoComment jib-core/src/test/java/com/google/cloud/tools/jib/image/ReproducibleLayerBuilderTest.java:259
- TodoComment jib-core/src/test/java/com/google/cloud/tools/jib/image/ReproducibleLayerBuilderTest.java:261
- TodoComment jib-core/src/test/java/com/google/cloud/tools/jib/builder/steps/BuildAndCacheApplicationLayerStepTest.java:57
- TodoComment jib-core/src/main/java/com/google/cloud/tools/jib/registry/BlobChecker.java:70
- TodoComment jib-core/src/main/java/com/google/cloud/tools/jib/registry/BlobPusher.java:139
- TodoComment jib-core/src/main/java/com/google/cloud/tools/jib/registry/ManifestPusher.java:84
- TodoComment jib-core/src/main/java/com/google/cloud/tools/jib/registry/RegistryAuthenticator.java:56
- TodoComment jib-core/src/main/java/com/google/cloud/tools/jib/registry/RegistryErrorExceptionBuilder.java:78
- TodoComment jib-core/src/main/java/com/google/cloud/tools/jib/registry/json/ErrorEntryTemplate.java:23
- TodoComment jib-core/src/main/java/com/google/cloud/tools/jib/json/JsonTemplateMapper.java:34
- TodoComment jib-core/src/main/java/com/google/cloud/tools/jib/image/ImageTarball.java:125
- No assertions: testCheckEquals_pass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/buildfile/ValidatorTest.java:231
- No assertions: testCheckNotEmpty_collectionPass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/buildfile/ValidatorTest.java:79
- No assertions: testCheckNotNullAndNotEmpty_stringPass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/buildfile/ValidatorTest.java:33
- No assertions: testCheckNullNonNullNonEmptyEntries_valuesPass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/buildfile/ValidatorTest.java:176
- No assertions: testCheckNullOrNonNullEntries_emptyPass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/buildfile/ValidatorTest.java:208
- No assertions: testCheckNullOrNonNullEntries_nullPass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/buildfile/ValidatorTest.java:202
- No assertions: testCheckNullOrNonNullEntries_valuesPass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/buildfile/ValidatorTest.java:214
- No assertions: testCheckNullOrNonNullNonEmptyEntries_emptyMapPass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/buildfile/ValidatorTest.java:111
- No assertions: testCheckNullOrNonNullNonEmptyEntries_emptyPass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/buildfile/ValidatorTest.java:170
- No assertions: testCheckNullOrNonNullNonEmptyEntries_mapWithValuesPass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/buildfile/ValidatorTest.java:117
- No assertions: testCheckNullOrNonNullNonEmptyEntries_nullMapPass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/buildfile/ValidatorTest.java:105
- No assertions: testCheckNullOrNonNullNonEmptyEntries_nullPass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/buildfile/ValidatorTest.java:164
- No assertions: testCheckNullOrNotEmpty_nullPass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/buildfile/ValidatorTest.java:64
- No assertions: testCheckNullOrNotEmpty_valuePass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/buildfile/ValidatorTest.java:59
- No assertions: testLog_quiet_plainConsole jib-cli/src/test/java/com/google/cloud/tools/jib/cli/logging/CliLoggerTest.java:64
- No assertions: testLog_quiet_richConsole jib-cli/src/test/java/com/google/cloud/tools/jib/cli/logging/CliLoggerTest.java:130
- No assertions: testValidate_pass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/BuildTest.java:422
- No assertions: testValidate_pass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/JarTest.java:602
- No assertions: testValidate_pass jib-cli/src/test/java/com/google/cloud/tools/jib/cli/WarTest.java:578
- No assertions: testCheckManifestPlatform_noExceptionIfDefaultAmd64Linux jib-core/src/test/java/com/google/cloud/tools/jib/builder/steps/PlatformCheckerTest.java:73
- No assertions: testCall_ManifestList_UnknownArchitecture jib-core/src/test/java/com/google/cloud/tools/jib/builder/steps/PullBaseImageStepTest.java:655
- No assertions: testVerifyImageMetadata_validOci jib-core/src/test/java/com/google/cloud/tools/jib/cache/CacheStorageReaderTest.java:622
- No assertions: testVerifyImageMetadata_validOciImageIndex jib-core/src/test/java/com/google/cloud/tools/jib/cache/CacheStorageReaderTest.java:633
- No assertions: testVerifyImageMetadata_validV21 jib-core/src/test/java/com/google/cloud/tools/jib/cache/CacheStorageReaderTest.java:589
- No assertions: testVerifyImageMetadata_validV22 jib-core/src/test/java/com/google/cloud/tools/jib/cache/CacheStorageReaderTest.java:599
- TooManyMethods: JibPluginConfiguration jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/JibPluginConfiguration.java:57
- TooManyMethods: JibContainerBuilder jib-core/src/main/java/com/google/cloud/tools/jib/api/JibContainerBuilder.java:69
- TooManyMethods: ContainerConfigurationTemplate jib-core/src/main/java/com/google/cloud/tools/jib/image/json/ContainerConfigurationTemplate.java:81
- TooManyMethods: GradleRawConfiguration jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/GradleRawConfiguration.java:31
- TooManyMethods: MavenRawConfiguration jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/MavenRawConfiguration.java:30
- TooManyMethods: JavaContainerBuilder jib-core/src/main/java/com/google/cloud/tools/jib/api/JavaContainerBuilder.java:45
- TooManyMethods: ContainerParameters jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/ContainerParameters.java:40
- TooManyMethods: StepsRunner jib-core/src/main/java/com/google/cloud/tools/jib/builder/steps/StepsRunner.java:68
- TooManyMethods: MavenProjectProperties jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/MavenProjectProperties.java:80
- TooManyMethods: Containerizer jib-core/src/main/java/com/google/cloud/tools/jib/api/Containerizer.java:48
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- ClassTooLong: PluginConfigurationProcessor jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/PluginConfigurationProcessor.java:77
- ClassTooLong: StepsRunner jib-core/src/main/java/com/google/cloud/tools/jib/builder/steps/StepsRunner.java:68
- ClassTooLong: JibPluginConfiguration jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/JibPluginConfiguration.java:57
- ClassTooLong: MavenProjectProperties jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/MavenProjectProperties.java:80
- Duplicated block (8 lines × 2) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/ContainerBuilders.java:68
- Duplicated block (8 lines × 2) jib-core/src/main/java/com/google/cloud/tools/jib/docker/CliDockerClient.java:281
- Duplicated block (8 lines × 2) jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/skaffold/FilesMojoV2.java:237
- Duplicated block (8 lines × 2) jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/PluginConfigurationProcessor.java:151
- Edited copy of a member (7 corresponding lines) jib-build-plan/src/main/java/com/google/cloud/tools/jib/api/buildplan/AbsoluteUnixPath.java:43
- Edited copy of a member (7 corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/ContainerParameters.java:94
- Edited copy of a member (7 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/registry/RegistryAuthenticator.java:157
- Duplicated block (7 lines × 2) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/jar/SpringBootPackagedProcessor.java:54
- Duplicated block (7 lines × 2) jib-core/src/main/java/com/google/cloud/tools/jib/api/JibContainerBuilder.java:668
- Duplicated block (7 lines × 2) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/skaffold/SkaffoldSyncParameters.java:55
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (24 corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/ContainerBuilders.java:59
- Edited copy of a member (24 corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/GradleProjectProperties.java:173
- Edited copy of a member (18 corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/JibPlugin.java:70
- Edited copy of a member (18 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/registry/BlobChecker.java:64
- Edited copy of a member (13 corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/GradleProjectProperties.java:533
- Edited copy of a member (13 corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/GradleProjectProperties.java:116
- Edited copy of a member (12 corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/CommonCliOptions.java:350
- Edited copy of a member (12 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/api/JibContainer.java:108
- Edited copy of a member (11 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/tar/TarExtractor.java:118
- Edited copy of a member (11 corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/ContainerParameters.java:231
- Duplicated block (19 lines × 2) jib-core/src/main/java/com/google/cloud/tools/jib/cache/CacheStorageReader.java:152
- Duplicated block (19 lines × 2) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/GradleProjectProperties.java:469
- Duplicated block (17 lines × 3) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/Build.java:141
- Duplicated block (17 lines × 3) jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/BuildDockerMojo.java:78
- Duplicated block (15 lines × 2) jib-core/src/main/java/com/google/cloud/tools/jib/tar/TarExtractor.java:76
- Duplicated block (15 lines × 2) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/TaskCommon.java:54
- Low cohesion: ContainerParameters (LCOM4 16) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/ContainerParameters.java:40
- Low cohesion: Containerizer (LCOM4 11) jib-core/src/main/java/com/google/cloud/tools/jib/api/Containerizer.java:48
- Layers.toLayers (cyclomatic 24) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/buildfile/Layers.java:56
- PluginConfigurationProcessor.computeEntrypoint (cyclomatic 24) jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/PluginConfigurationProcessor.java:590
- JavaContainerBuilder.toContainerBuilder (cyclomatic 17) jib-core/src/main/java/com/google/cloud/tools/jib/api/JavaContainerBuilder.java:545
- BuildDockerMojo.execute (cyclomatic 17) jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/BuildDockerMojo.java:62
- BuildImageMojo.execute (cyclomatic 17) jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/BuildImageMojo.java:64
- DefaultCredentialRetrievers.asList (cyclomatic 17) jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/DefaultCredentialRetrievers.java:157
- JsonToImageTranslator.configureBuilderWithContainerConfiguration (cyclomatic 16) jib-core/src/main/java/com/google/cloud/tools/jib/image/json/JsonToImageTranslator.java:143
- Layers.toLayers (cognitive 85) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/buildfile/Layers.java:56
- PluginConfigurationProcessor.computeEntrypoint (cognitive 34) jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/PluginConfigurationProcessor.java:590
- DockerConfigCredentialRetriever.retrieve (cognitive 28) jib-core/src/main/java/com/google/cloud/tools/jib/registry/credentials/DockerConfigCredentialRetriever.java:119
- JsonToImageTranslator.configureBuilderWithContainerConfiguration (cognitive 25) jib-core/src/main/java/com/google/cloud/tools/jib/image/json/JsonToImageTranslator.java:143
- FilesMojoV2.collectWatchParameters (cognitive 25) jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/skaffold/FilesMojoV2.java:268
- FilesMojoV2.collectExtraDirectories (cognitive 23) jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/skaffold/FilesMojoV2.java:227
- DefaultCredentialRetrievers.asList (cognitive 23) jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/DefaultCredentialRetrievers.java:157
- PullBaseImageStep.call (cognitive 22) jib-core/src/main/java/com/google/cloud/tools/jib/builder/steps/PullBaseImageStep.java:96
- JibPlugin.apply (cognitive 22) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/JibPlugin.java:90
- JavaContainerBuilder.toContainerBuilder (cognitive 21) jib-core/src/main/java/com/google/cloud/tools/jib/api/JavaContainerBuilder.java:545
- FilesTaskV2.findProjectDependencies (cognitive 21) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/skaffold/FilesTaskV2.java:214
- XdgDirectories.getOsSpecificDirectory (cognitive 20) jib-core/src/main/java/com/google/cloud/tools/jib/filesystem/XdgDirectories.java:99
- AbstractManifestPuller.getManifestTemplateFromJson (cognitive 20) jib-core/src/main/java/com/google/cloud/tools/jib/registry/AbstractManifestPuller.java:136
- RegistryEndpointCaller.call (cognitive 20) jib-core/src/main/java/com/google/cloud/tools/jib/registry/RegistryEndpointCaller.java:125
- MainClassFinder.find (cognitive 17) jib-core/src/main/java/com/google/cloud/tools/jib/api/MainClassFinder.java:205
- FailoverHttpClient.call (cognitive 17) REDACTED:252
- MavenProjectProperties.getJarArtifact (cognitive 17) jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/MavenProjectProperties.java:519
- JibBuildRunner.runBuild (cognitive 17) jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/JibBuildRunner.java:223
- BuildDockerMojo.execute (cognitive 16) jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/BuildDockerMojo.java:62
- BuildImageMojo.execute (cognitive 16) jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/BuildImageMojo.java:64
- REDACTED
- FileTooLong: common/PluginConfigurationProcessor.java jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/PluginConfigurationProcessor.java
- MethodTooLong: BuildImageMojo.execute jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/BuildImageMojo.java:64
- REDACTED
- REDACTED
- Edited copies of one member (3 members, 109+ corresponding lines) jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/BuildDockerMojo.java:62
- Edited copies of one member (3 members, 90+ corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/BuildDockerTask.java:92
- Edited copies of one member (3 members, 57+ corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/Build.java:101
- Edited copy of a member (35 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/tar/TarExtractor.java:63
- Edited copy of a member (28 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/cache/CacheStorageReader.java:150
- Edited copy of a member (27 corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/GradleProjectProperties.java:461
- Edited copy of a member (21 corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/jar/JarFiles.java:57
- Edited copy of a member (26 corresponding lines) jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/PluginConfigurationProcessor.java:141
- Edited copy of a member (29 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/cache/CacheStorageWriter.java:219
- Edited copies of one member (4 members, 22+ corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/builder/steps/StepsRunner.java:376
- Edited copy of a member (17 corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/jar/StandardExplodedProcessor.java:93
- Edited copy of a member (20 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/cache/CacheStorageWriter.java:182
- Edited copy of a member (14 corresponding lines) jib-build-plan/src/main/java/com/google/cloud/tools/jib/api/buildplan/FileEntry.java:152
- Edited copy of a member (23 corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/Credentials.java:41
- Edited copy of a member (16 corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/Containerizers.java:116
- Edited copies of one member (3 members, 12+ corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/JibCli.java:89
- Edited copy of a member (10 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/image/json/OciIndexTemplate.java:110
- Edited copy of a member (9 corresponding lines) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/CommonCliOptions.java:303
- Edited copy of a member (5 corresponding lines) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/OutputPathsParameters.java:102
- Edited copy of a member (8 corresponding lines) jib-core/src/main/java/com/google/cloud/tools/jib/builder/steps/PushBlobStep.java:52
- Duplicated block (84 lines × 3) jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/BuildDockerMojo.java:97
- Duplicated block (71–72 lines × 3) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/BuildDockerTask.java:123
- Duplicated block (18 lines × 3) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/Build.java:104
- Duplicated block (13 lines × 3) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/BuildDockerTask.java:106
- Duplicated block (12 lines × 2) jib-cli/src/main/java/com/google/cloud/tools/jib/cli/jar/JarLayers.java:66
- Duplicated block (9 lines × 2) jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/PlatformParameters.java:32
- Duplicated block (5 lines × 2) jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/MavenProjectProperties.java:494
- Duplicated block (109 lines × 2) jib-core/src/main/java/com/google/cloud/tools/jib/image/json/OciManifestTemplate.java:1
- Duplicated block (6 lines × 2) jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/SkaffoldInitOutput.java:84
- Duplicated block (14 lines × 2) jib-cli/src/integration-test/resources/warTest/src/main/java/example/HelloWorld.java:34
- End-of-life framework: Spring Boot 2 examples/multi-module/build.gradle:1
- Off the main sequence: .:jib-core
- Coverage collected but not gated
Minor — 215 finding(s)
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/api/JibContainerBuilder.java:1
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/api/JavaContainerBuilder.java:1
- Orphaned file jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/JibPluginConfiguration.java:1
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/builder/steps/PullBaseImageStep.java:1
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/registry/RegistryClient.java:1
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/configuration/BuildContext.java:1
- Orphaned file jib-gradle-plugin/src/main/java/com/google/cloud/tools/jib/gradle/GradleProjectProperties.java:1
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/cache/CacheStorageWriter.java:1
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/api/ImageReference.java:1
- Orphaned file jib-build-plan/src/main/java/com/google/cloud/tools/jib/api/buildplan/ContainerBuildPlan.java:1
- Orphaned file REDACTED:1
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/api/Containerizer.java:1
- Orphaned file jib-build-plan/src/main/java/com/google/cloud/tools/jib/api/buildplan/FileEntriesLayer.java:1
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/configuration/ContainerConfiguration.java:1
- Orphaned file jib-cli/src/main/java/com/google/cloud/tools/jib/cli/CommonCliOptions.java:1
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/builder/steps/LocalBaseImageSteps.java:1
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/frontend/CredentialRetrieverFactory.java:1
- Orphaned file jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/skaffold/FilesMojoV2.java:1
- Orphaned file jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/JibBuildRunner.java:1
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/registry/RegistryAuthenticator.java:1
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/image/Image.java:1
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/image/json/ContainerConfigurationTemplate.java:1
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/image/json/JsonToImageTranslator.java:1
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/docker/CliDockerClient.java:1
- Orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/cache/Cache.java:1
- Duplicated predicate jib-core/src/main/java/com/google/cloud/tools/jib/builder/steps/AuthenticatePushStep.java:68
- Duplicated predicate jib-core/src/main/java/com/google/cloud/tools/jib/tar/TarExtractor.java:64
- Duplicated predicate jib-core/src/main/java/com/google/cloud/tools/jib/frontend/CredentialRetrieverFactory.java:200
- Duplicated predicate jib-core/src/main/java/com/google/cloud/tools/jib/image/json/OciIndexTemplate.java:114
- Duplicated predicate jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/MavenSettingsProxyProvider.java:69
- Most significant orphaned file jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/PluginConfigurationProcessor.java:1
- Most significant orphaned file jib-core/src/main/java/com/google/cloud/tools/jib/builder/steps/StepsRunner.java:1
- Most significant orphaned file jib-maven-plugin/src/main/java/com/google/cloud/tools/jib/maven/MavenProjectProperties.java:1
- Fat interface: ProjectProperties (18 abstract methods) jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/ProjectProperties.java:31
- Fat interface: RawConfiguration (36 abstract methods) jib-plugins-common/src/main/java/com/google/cloud/tools/jib/plugins/common/RawConfiguration.java:31
- README/code drift jib-gradle-plugin/README.md:660
- README/code drift jib-maven-plugin/README.md:742
- Off-boarding risk: anonymized user #1
- No ADRs found jib-plugins-extension-common/build.gradle:10
- Projects may be oversized for their cohesion
- REDACTED
- Concentrated knowledge decay
- REDACTED
- REDACTED
- Disabled test jib-core/src/test/java/com/google/cloud/tools/jib/registry/DockerRegistryBearerTokenTest.java:81
- No ADRs
- Logging is not universal
- Dependabot does not watch maven REDACTED:2
- Nullness suppressions override the null-marking checker
Minor — 6 finding(s)
- Skipped (documented): testFromPath_windows jib-build-plan/src/test/java/com/google/cloud/tools/jib/api/buildplan/AbsoluteUnixPathTest.java:47
- Skipped (documented): testDecode_invalidToken_actionsArray jib-core/src/test/java/com/google/cloud/tools/jib/registry/DockerRegistryBearerTokenTest.java:82
- Skipped (documented): testCheckGradleVersion_fail jib-gradle-plugin/src/test/java/com/google/cloud/tools/jib/gradle/JibPluginTest.java:94
- Skipped (documented): testCheckGradleVersion_pass jib-gradle-plugin/src/test/java/com/google/cloud/tools/jib/gradle/JibPluginTest.java:75
- Skipped (documented): testZipSlipVulnerability_unix jib-plugins-common/src/test/java/com/google/cloud/tools/jib/plugins/common/ZipUtilTest.java:66
- Skipped (documented): testZipSlipVulnerability_windows jib-plugins-common/src/test/java/com/google/cloud/tools/jib/plugins/common/ZipUtilTest.java:57
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-505a54dbbd5b4cb9a24ac6c2ca6673e0/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-505a54dbbd5b4cb9a24ac6c2ca6673e0/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 42 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |