Executive summary
GradleUp/shadow falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 65 out of 100 and is rated Adequate, and all 23 of its critical findings are security problems in the build pipeline.
Production Readiness, at 59, is the weakest lens, level with Maturity, and counts most in the score. The best first step for the work it takes is fixing the part of the code only one person knows, worth about 4 points. Adding automated security scanning would lift Production Readiness itself, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 68.
Nineteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two pipeline steps install packages that can change without warning. Pinning each tool to an exact version and pinning what the pipeline installs would close both risks. Passing outside input through environment variables would fix the two pipeline steps that put outside input straight into a shell command.
The product code is 5,247 lines, about €22,000 to rebuild.
If Production Readiness rose from 59 to 70, the lowest score rated Strong, the score would rise from 65 to about 68.
New since the last survey: 13 findings
- Cyclomatic Complexity · SimpleRelocator.isValidSourceContext (cyclomatic 25) src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/relocation/SimpleRelocator.kt
- Cognitive Complexity · SimpleRelocator.isValidSourceContext (cognitive 40) src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/relocation/SimpleRelocator.kt
- Cognitive Complexity · ShadowedSourcesJarKt.generateSourcesJar (cognitive 16) src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/ShadowedSourcesJar.kt
- God Classes · ClassTooLong: ShadowJar src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/tasks/ShadowJar.kt
- God Classes · FileTooLong: tasks/ShadowJar.kt src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/tasks/ShadowJar.kt
- Code Duplication · Edited copy of a member (14 corresponding lines) src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/transformers/PropertiesFileTransformer.kt
- Code Duplication · Duplicated block (5 lines × 2) src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/transformers/AppendingTransformer.kt
- Explicit Debt · TodoComment src/testKit/kotlin/com/github/jengelman/gradle/plugins/shadow/testkit/AssertK.kt
- Explicit Debt · TodoComment src/testKit/kotlin/com/github/jengelman/gradle/plugins/shadow/testkit/GradleRunner.kt
- Explicit Debt · TodoComment src/testKit/kotlin/com/github/jengelman/gradle/plugins/shadow/testkit/GradleRunner.kt
- Explicit Debt · TodoComment src/testKit/kotlin/com/github/jengelman/gradle/plugins/shadow/testkit/GradleRunner.kt
- Explicit Debt · TodoComment src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/ShadowJavaPlugin.kt
- Change Coupling · Change coupling: R8Minimizer.kt ↔ Zip.kt src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/R8Minimizer.kt
Fixed since the last survey: 4 findings
- Code Duplication · Duplicated block (5 lines × 2) src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/transformers/AppendingTransformer.kt
- Explicit Debt · TodoComment src/testKit/kotlin/com/github/jengelman/gradle/plugins/shadow/testkit/GradleRunner.kt
- Explicit Debt · TodoComment src/testKit/kotlin/com/github/jengelman/gradle/plugins/shadow/testkit/GradleRunner.kt
- Change Coupling · Change coupling: ShadowPlugin.kt ↔ ShadowJar.kt src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/ShadowPlugin.kt
Rebuild cost: about €22,000 · Estimate
| Cost to rebuild | €7,300 to €37,000, for 122 to 389 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 65. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 5,247 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 .github.scripts | 2 com.github.jengelman.gradle.plugins.shadow.ShadowApplicationPlugin | 3 com.github.jengelman.gradle.plugins.shadow.ShadowJavaPlugin | 4 com.github.jengelman.gradle.plugins.shadow.ShadowPlugin | 5 com.github.jengelman.gradle.plugins.shadow.buildlogic | 6 com.github.jengelman.gradle.plugins.shadow.internal.DefaultR8Spec | 7 com.github.jengelman.gradle.plugins.shadow.legacy | 8 com.github.jengelman.gradle.plugins.shadow.relocation | 9 com.github.jengelman.gradle.plugins.shadow.relocation.SimpleRelocator | 10 com.github.jengelman.gradle.plugins.shadow.transformers.ApacheLicenseResourceTransformer | 11 com.github.jengelman.gradle.plugins.shadow.transformers.ApacheNoticeResourceTransformer | 12 com.github.jengelman.gradle.plugins.shadow.transformers.AppendingTransformer | 13 com.github.jengelman.gradle.plugins.shadow.transformers.ComponentsXmlResourceTransformer | 14 com.github.jengelman.gradle.plugins.shadow.transformers.DeduplicatingResourceTransformer | 15 com.github.jengelman.gradle.plugins.shadow.transformers.GroovyExtensionModuleTransformer | 16 com.github.jengelman.gradle.plugins.shadow.transformers.Log4j2PluginsCacheFileTransformer | 17 com.github.jengelman.gradle.plugins.shadow.transformers.ManifestAppenderTransformer | 18 com.github.jengelman.gradle.plugins.shadow.transformers.ManifestResourceTransformer | 19 com.github.jengelman.gradle.plugins.shadow.transformers.ProGuardFilesResourceTransformer | 20 com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer | 21 com.github.jengelman.gradle.plugins.shadow.transformers.ServiceFileTransformer | 22 com.github.jengelman.gradle.plugins.shadow.tasks.DependencyFilter | 23 com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategy | 24 com.github.jengelman.gradle.plugins.shadow.internal | 25 com.github.jengelman.gradle.plugins.shadow.internal.UnixMode | 26 com.github.jengelman.gradle.plugins.shadow.tasks.ShadowCopyAction | 27 com.github.jengelman.gradle.plugins.shadow.transformers | 28 com.github.jengelman.gradle.plugins.shadow.tasks | 29 com.github.jengelman.gradle.plugins.shadow.transformers.ResourceTransformer | 30 com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext | 31 com.github.jengelman.gradle.plugins.shadow | 32 com.github.jengelman.gradle.plugins.shadow.tasks.MinimizeTool | 33 com.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar | 34 com.github.jengelman.gradle.plugins.shadow.ShadowBasePlugin |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 .github.scripts | ||||||||||||||||||||||||||||||||||
| 2 com.github.jengelman.gradle.plugins.shadow.ShadowApplicationPlugin | ||||||||||||||||||||||||||||||||||
| 3 com.github.jengelman.gradle.plugins.shadow.ShadowJavaPlugin | ||||||||||||||||||||||||||||||||||
| 4 com.github.jengelman.gradle.plugins.shadow.ShadowPlugin | ||||||||||||||||||||||||||||||||||
| 5 com.github.jengelman.gradle.plugins.shadow.buildlogic | ||||||||||||||||||||||||||||||||||
| 6 com.github.jengelman.gradle.plugins.shadow.internal.DefaultR8Spec | ||||||||||||||||||||||||||||||||||
| 7 com.github.jengelman.gradle.plugins.shadow.legacy | ||||||||||||||||||||||||||||||||||
| 8 com.github.jengelman.gradle.plugins.shadow.relocation | ||||||||||||||||||||||||||||||||||
| 9 com.github.jengelman.gradle.plugins.shadow.relocation.SimpleRelocator | ||||||||||||||||||||||||||||||||||
| 10 com.github.jengelman.gradle.plugins.shadow.transformers.ApacheLicenseResourceTransformer | ||||||||||||||||||||||||||||||||||
| 11 com.github.jengelman.gradle.plugins.shadow.transformers.ApacheNoticeResourceTransformer | ||||||||||||||||||||||||||||||||||
| 12 com.github.jengelman.gradle.plugins.shadow.transformers.AppendingTransformer | ||||||||||||||||||||||||||||||||||
| 13 com.github.jengelman.gradle.plugins.shadow.transformers.ComponentsXmlResourceTransformer | ||||||||||||||||||||||||||||||||||
| 14 com.github.jengelman.gradle.plugins.shadow.transformers.DeduplicatingResourceTransformer | ||||||||||||||||||||||||||||||||||
| 15 com.github.jengelman.gradle.plugins.shadow.transformers.GroovyExtensionModuleTransformer | ||||||||||||||||||||||||||||||||||
| 16 com.github.jengelman.gradle.plugins.shadow.transformers.Log4j2PluginsCacheFileTransformer | ||||||||||||||||||||||||||||||||||
| 17 com.github.jengelman.gradle.plugins.shadow.transformers.ManifestAppenderTransformer | ||||||||||||||||||||||||||||||||||
| 18 com.github.jengelman.gradle.plugins.shadow.transformers.ManifestResourceTransformer | ||||||||||||||||||||||||||||||||||
| 19 com.github.jengelman.gradle.plugins.shadow.transformers.ProGuardFilesResourceTransformer | ||||||||||||||||||||||||||||||||||
| 20 com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer | ||||||||||||||||||||||||||||||||||
| 21 com.github.jengelman.gradle.plugins.shadow.transformers.ServiceFileTransformer | ||||||||||||||||||||||||||||||||||
| 22 com.github.jengelman.gradle.plugins.shadow.tasks.DependencyFilter | 1 | |||||||||||||||||||||||||||||||||
| 23 com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategy | 5 | |||||||||||||||||||||||||||||||||
| 24 com.github.jengelman.gradle.plugins.shadow.internal | 4 | 2 | 5 | |||||||||||||||||||||||||||||||
| 25 com.github.jengelman.gradle.plugins.shadow.internal.UnixMode | 1 | |||||||||||||||||||||||||||||||||
| 26 com.github.jengelman.gradle.plugins.shadow.tasks.ShadowCopyAction | 1 | |||||||||||||||||||||||||||||||||
| 27 com.github.jengelman.gradle.plugins.shadow.transformers | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 28 com.github.jengelman.gradle.plugins.shadow.tasks | 3 | 3 | ||||||||||||||||||||||||||||||||
| 29 com.github.jengelman.gradle.plugins.shadow.transformers.ResourceTransformer | 2 | |||||||||||||||||||||||||||||||||
| 30 com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext | 1 | 1 | ||||||||||||||||||||||||||||||||
| 31 com.github.jengelman.gradle.plugins.shadow | 1 | |||||||||||||||||||||||||||||||||
| 32 com.github.jengelman.gradle.plugins.shadow.tasks.MinimizeTool | 2 | |||||||||||||||||||||||||||||||||
| 33 com.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar | 1 | |||||||||||||||||||||||||||||||||
| 34 com.github.jengelman.gradle.plugins.shadow.ShadowBasePlugin | 1 |
22→28 com.github.jengelman.gradle.plugins.shadow.tasks.DependencyFilter uses com.github.jengelman.gradle.plugins.shadow.tasks part of a loop✕
- Connections
- 1 pair of types, where a type in com.github.jengelman.gradle.plugins.shadow.tasks.DependencyFilter uses a type in com.github.jengelman.gradle.plugins.shadow.tasks.
- The types involved
com.github.jengelman.gradle.plugins.shadow.tasks.DependencyFilter.AbstractDependencyFilter→com.github.jengelman.gradle.plugins.shadow.tasks.DependencyFilter
- Direction
- com.github.jengelman.gradle.plugins.shadow.tasks.DependencyFilter uses com.github.jengelman.gradle.plugins.shadow.tasks, so a change to com.github.jengelman.gradle.plugins.shadow.tasks can break com.github.jengelman.gradle.plugins.shadow.tasks.DependencyFilter, while a change to com.github.jengelman.gradle.plugins.shadow.tasks.DependencyFilter can't break com.github.jengelman.gradle.plugins.shadow.tasks.
- 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→20 com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategy uses com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer✕
- Connections
- 5 pairs of types, where a type in com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategy uses a type in com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.
- The types involved
com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategy.Append→com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategycom.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategy.Companion→com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategycom.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategy.Fail→com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategycom.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategy.First→com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategycom.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategy.Latest→com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategy
- Direction
- com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategy uses com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer, so a change to com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer can break com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategy, while a change to com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategy can't break com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategy uses a module listed above it, which is the healthy direction.
24→8 com.github.jengelman.gradle.plugins.shadow.internal uses com.github.jengelman.gradle.plugins.shadow.relocation✕
- Connections
- 4 pairs of types, where a type in com.github.jengelman.gradle.plugins.shadow.internal uses a type in com.github.jengelman.gradle.plugins.shadow.relocation.
- The types involved
com.github.jengelman.gradle.plugins.shadow.internal.R8MinimizerKt→com.github.jengelman.gradle.plugins.shadow.relocation.Relocatorcom.github.jengelman.gradle.plugins.shadow.internal.RelocatorRemapper→com.github.jengelman.gradle.plugins.shadow.relocation.Relocatorcom.github.jengelman.gradle.plugins.shadow.internal.RelocatorRemapperKt→com.github.jengelman.gradle.plugins.shadow.relocation.Relocatorcom.github.jengelman.gradle.plugins.shadow.internal.ShadowedSourcesJarKt→com.github.jengelman.gradle.plugins.shadow.relocation.Relocator
- Direction
- com.github.jengelman.gradle.plugins.shadow.internal uses com.github.jengelman.gradle.plugins.shadow.relocation, so a change to com.github.jengelman.gradle.plugins.shadow.relocation can break com.github.jengelman.gradle.plugins.shadow.internal, while a change to com.github.jengelman.gradle.plugins.shadow.internal can't break com.github.jengelman.gradle.plugins.shadow.relocation.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.internal uses a module listed above it, which is the healthy direction.
24→22 com.github.jengelman.gradle.plugins.shadow.internal uses com.github.jengelman.gradle.plugins.shadow.tasks.DependencyFilter✕
- Connections
- 2 pairs of types, where a type in com.github.jengelman.gradle.plugins.shadow.internal uses a type in com.github.jengelman.gradle.plugins.shadow.tasks.DependencyFilter.
- The types involved
com.github.jengelman.gradle.plugins.shadow.internal.DefaultDependencyFilter→com.github.jengelman.gradle.plugins.shadow.tasks.DependencyFilter.AbstractDependencyFiltercom.github.jengelman.gradle.plugins.shadow.internal.MinimizeDependencyFilter→com.github.jengelman.gradle.plugins.shadow.tasks.DependencyFilter.AbstractDependencyFilter
- Direction
- com.github.jengelman.gradle.plugins.shadow.internal uses com.github.jengelman.gradle.plugins.shadow.tasks.DependencyFilter, so a change to com.github.jengelman.gradle.plugins.shadow.tasks.DependencyFilter can break com.github.jengelman.gradle.plugins.shadow.internal, while a change to com.github.jengelman.gradle.plugins.shadow.internal can't break com.github.jengelman.gradle.plugins.shadow.tasks.DependencyFilter.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.internal uses a module listed above it, which is the healthy direction.
24→28 com.github.jengelman.gradle.plugins.shadow.internal uses com.github.jengelman.gradle.plugins.shadow.tasks part of a loop✕
- Connections
- 5 pairs of types, where a type in com.github.jengelman.gradle.plugins.shadow.internal uses a type in com.github.jengelman.gradle.plugins.shadow.tasks.
- The types involved
com.github.jengelman.gradle.plugins.shadow.internal.DefaultInheritManifest→com.github.jengelman.gradle.plugins.shadow.tasks.InheritManifestcom.github.jengelman.gradle.plugins.shadow.internal.DefaultMinimizeSpec→com.github.jengelman.gradle.plugins.shadow.tasks.MinimizeSpeccom.github.jengelman.gradle.plugins.shadow.internal.DefaultMinimizeSpec→com.github.jengelman.gradle.plugins.shadow.tasks.MinimizeToolcom.github.jengelman.gradle.plugins.shadow.internal.DefaultMinimizeSpec→com.github.jengelman.gradle.plugins.shadow.tasks.R8Speccom.github.jengelman.gradle.plugins.shadow.internal.DefaultR8Spec→com.github.jengelman.gradle.plugins.shadow.tasks.R8Spec
- Direction
- com.github.jengelman.gradle.plugins.shadow.internal uses com.github.jengelman.gradle.plugins.shadow.tasks, so a change to com.github.jengelman.gradle.plugins.shadow.tasks can break com.github.jengelman.gradle.plugins.shadow.internal, while a change to com.github.jengelman.gradle.plugins.shadow.internal can't break com.github.jengelman.gradle.plugins.shadow.tasks.
- 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→24 com.github.jengelman.gradle.plugins.shadow.internal.UnixMode uses com.github.jengelman.gradle.plugins.shadow.internal✕
- Connections
- 1 pair of types, where a type in com.github.jengelman.gradle.plugins.shadow.internal.UnixMode uses a type in com.github.jengelman.gradle.plugins.shadow.internal.
- The types involved
com.github.jengelman.gradle.plugins.shadow.internal.UnixMode.Companion→com.github.jengelman.gradle.plugins.shadow.internal.UnixMode
- Direction
- com.github.jengelman.gradle.plugins.shadow.internal.UnixMode uses com.github.jengelman.gradle.plugins.shadow.internal, so a change to com.github.jengelman.gradle.plugins.shadow.internal can break com.github.jengelman.gradle.plugins.shadow.internal.UnixMode, while a change to com.github.jengelman.gradle.plugins.shadow.internal.UnixMode can't break com.github.jengelman.gradle.plugins.shadow.internal.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.internal.UnixMode uses a module listed above it, which is the healthy direction.
26→24 com.github.jengelman.gradle.plugins.shadow.tasks.ShadowCopyAction uses com.github.jengelman.gradle.plugins.shadow.internal✕
- Connections
- 1 pair of types, where a type in com.github.jengelman.gradle.plugins.shadow.tasks.ShadowCopyAction uses a type in com.github.jengelman.gradle.plugins.shadow.internal.
- The types involved
com.github.jengelman.gradle.plugins.shadow.tasks.ShadowCopyAction.StreamAction→com.github.jengelman.gradle.plugins.shadow.internal.OrderedParallelWriter
- Direction
- com.github.jengelman.gradle.plugins.shadow.tasks.ShadowCopyAction uses com.github.jengelman.gradle.plugins.shadow.internal, so a change to com.github.jengelman.gradle.plugins.shadow.internal can break com.github.jengelman.gradle.plugins.shadow.tasks.ShadowCopyAction, while a change to com.github.jengelman.gradle.plugins.shadow.tasks.ShadowCopyAction can't break com.github.jengelman.gradle.plugins.shadow.internal.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.tasks.ShadowCopyAction uses a module listed above it, which is the healthy direction.
27→8 com.github.jengelman.gradle.plugins.shadow.transformers uses com.github.jengelman.gradle.plugins.shadow.relocation✕
- Connections
- 2 pairs of types, where a type in com.github.jengelman.gradle.plugins.shadow.transformers uses a type in com.github.jengelman.gradle.plugins.shadow.relocation.
- The types involved
com.github.jengelman.gradle.plugins.shadow.transformers.Log4j2PluginsCacheFileTransformer→com.github.jengelman.gradle.plugins.shadow.relocation.Relocatorcom.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext→com.github.jengelman.gradle.plugins.shadow.relocation.Relocator
- Direction
- com.github.jengelman.gradle.plugins.shadow.transformers uses com.github.jengelman.gradle.plugins.shadow.relocation, so a change to com.github.jengelman.gradle.plugins.shadow.relocation can break com.github.jengelman.gradle.plugins.shadow.transformers, while a change to com.github.jengelman.gradle.plugins.shadow.transformers can't break com.github.jengelman.gradle.plugins.shadow.relocation.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.transformers uses a module listed above it, which is the healthy direction.
27→14 com.github.jengelman.gradle.plugins.shadow.transformers uses com.github.jengelman.gradle.plugins.shadow.transformers.DeduplicatingResourceTransformer✕
- Connections
- 1 pair of types, where a type in com.github.jengelman.gradle.plugins.shadow.transformers uses a type in com.github.jengelman.gradle.plugins.shadow.transformers.DeduplicatingResourceTransformer.
- The types involved
com.github.jengelman.gradle.plugins.shadow.transformers.DeduplicatingResourceTransformer→com.github.jengelman.gradle.plugins.shadow.transformers.DeduplicatingResourceTransformer.PathInfos
- Direction
- com.github.jengelman.gradle.plugins.shadow.transformers uses com.github.jengelman.gradle.plugins.shadow.transformers.DeduplicatingResourceTransformer, so a change to com.github.jengelman.gradle.plugins.shadow.transformers.DeduplicatingResourceTransformer can break com.github.jengelman.gradle.plugins.shadow.transformers, while a change to com.github.jengelman.gradle.plugins.shadow.transformers can't break com.github.jengelman.gradle.plugins.shadow.transformers.DeduplicatingResourceTransformer.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.transformers uses a module listed above it, which is the healthy direction.
27→16 com.github.jengelman.gradle.plugins.shadow.transformers uses com.github.jengelman.gradle.plugins.shadow.transformers.Log4j2PluginsCacheFileTransformer✕
- Connections
- 1 pair of types, where a type in com.github.jengelman.gradle.plugins.shadow.transformers uses a type in com.github.jengelman.gradle.plugins.shadow.transformers.Log4j2PluginsCacheFileTransformer.
- The types involved
com.github.jengelman.gradle.plugins.shadow.transformers.Log4j2PluginsCacheFileTransformer→com.github.jengelman.gradle.plugins.shadow.transformers.Log4j2PluginsCacheFileTransformer.PluginEntry
- Direction
- com.github.jengelman.gradle.plugins.shadow.transformers uses com.github.jengelman.gradle.plugins.shadow.transformers.Log4j2PluginsCacheFileTransformer, so a change to com.github.jengelman.gradle.plugins.shadow.transformers.Log4j2PluginsCacheFileTransformer can break com.github.jengelman.gradle.plugins.shadow.transformers, while a change to com.github.jengelman.gradle.plugins.shadow.transformers can't break com.github.jengelman.gradle.plugins.shadow.transformers.Log4j2PluginsCacheFileTransformer.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.transformers uses a module listed above it, which is the healthy direction.
27→20 com.github.jengelman.gradle.plugins.shadow.transformers uses com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer✕
- Connections
- 1 pair of types, where a type in com.github.jengelman.gradle.plugins.shadow.transformers uses a type in com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.
- The types involved
com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer→com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.MergeStrategy
- Direction
- com.github.jengelman.gradle.plugins.shadow.transformers uses com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer, so a change to com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer can break com.github.jengelman.gradle.plugins.shadow.transformers, while a change to com.github.jengelman.gradle.plugins.shadow.transformers can't break com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.transformers uses a module listed above it, which is the healthy direction.
27→24 com.github.jengelman.gradle.plugins.shadow.transformers uses com.github.jengelman.gradle.plugins.shadow.internal✕
- Connections
- 1 pair of types, where a type in com.github.jengelman.gradle.plugins.shadow.transformers uses a type in com.github.jengelman.gradle.plugins.shadow.internal.
- The types involved
com.github.jengelman.gradle.plugins.shadow.transformers.PropertiesFileTransformer→com.github.jengelman.gradle.plugins.shadow.internal.ReproducibleProperties
- Direction
- com.github.jengelman.gradle.plugins.shadow.transformers uses com.github.jengelman.gradle.plugins.shadow.internal, so a change to com.github.jengelman.gradle.plugins.shadow.internal can break com.github.jengelman.gradle.plugins.shadow.transformers, while a change to com.github.jengelman.gradle.plugins.shadow.transformers can't break com.github.jengelman.gradle.plugins.shadow.internal.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.transformers uses a module listed above it, which is the healthy direction.
28→8 com.github.jengelman.gradle.plugins.shadow.tasks uses com.github.jengelman.gradle.plugins.shadow.relocation✕
- Connections
- 3 pairs of types, where a type in com.github.jengelman.gradle.plugins.shadow.tasks uses a type in com.github.jengelman.gradle.plugins.shadow.relocation.
- The types involved
com.github.jengelman.gradle.plugins.shadow.tasks.ShadowCopyAction→com.github.jengelman.gradle.plugins.shadow.relocation.Relocatorcom.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar→com.github.jengelman.gradle.plugins.shadow.relocation.Relocatorcom.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar→com.github.jengelman.gradle.plugins.shadow.relocation.SimpleRelocator
- Direction
- com.github.jengelman.gradle.plugins.shadow.tasks uses com.github.jengelman.gradle.plugins.shadow.relocation, so a change to com.github.jengelman.gradle.plugins.shadow.relocation can break com.github.jengelman.gradle.plugins.shadow.tasks, while a change to com.github.jengelman.gradle.plugins.shadow.tasks can't break com.github.jengelman.gradle.plugins.shadow.relocation.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.tasks uses a module listed above it, which is the healthy direction.
28→27 com.github.jengelman.gradle.plugins.shadow.tasks uses com.github.jengelman.gradle.plugins.shadow.transformers✕
- Connections
- 3 pairs of types, where a type in com.github.jengelman.gradle.plugins.shadow.tasks uses a type in com.github.jengelman.gradle.plugins.shadow.transformers.
- The types involved
com.github.jengelman.gradle.plugins.shadow.tasks.ShadowCopyAction→com.github.jengelman.gradle.plugins.shadow.transformers.ResourceTransformercom.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar→com.github.jengelman.gradle.plugins.shadow.transformers.ResourceTransformercom.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar→com.github.jengelman.gradle.plugins.shadow.transformers.ServiceFileTransformer
- Direction
- com.github.jengelman.gradle.plugins.shadow.tasks uses com.github.jengelman.gradle.plugins.shadow.transformers, so a change to com.github.jengelman.gradle.plugins.shadow.transformers can break com.github.jengelman.gradle.plugins.shadow.tasks, while a change to com.github.jengelman.gradle.plugins.shadow.tasks can't break com.github.jengelman.gradle.plugins.shadow.transformers.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.tasks uses a module listed above it, which is the healthy direction.
29→27 com.github.jengelman.gradle.plugins.shadow.transformers.ResourceTransformer uses com.github.jengelman.gradle.plugins.shadow.transformers✕
- Connections
- 2 pairs of types, where a type in com.github.jengelman.gradle.plugins.shadow.transformers.ResourceTransformer uses a type in com.github.jengelman.gradle.plugins.shadow.transformers.
- The types involved
com.github.jengelman.gradle.plugins.shadow.transformers.ResourceTransformer.Companion→com.github.jengelman.gradle.plugins.shadow.transformers.ResourceTransformercom.github.jengelman.gradle.plugins.shadow.transformers.ResourceTransformer.Companion→com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext
- Direction
- com.github.jengelman.gradle.plugins.shadow.transformers.ResourceTransformer uses com.github.jengelman.gradle.plugins.shadow.transformers, so a change to com.github.jengelman.gradle.plugins.shadow.transformers can break com.github.jengelman.gradle.plugins.shadow.transformers.ResourceTransformer, while a change to com.github.jengelman.gradle.plugins.shadow.transformers.ResourceTransformer can't break com.github.jengelman.gradle.plugins.shadow.transformers.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.transformers.ResourceTransformer uses a module listed above it, which is the healthy direction.
30→8 com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext uses com.github.jengelman.gradle.plugins.shadow.relocation✕
- Connections
- 1 pair of types, where a type in com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext uses a type in com.github.jengelman.gradle.plugins.shadow.relocation.
- The types involved
com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext.Builder→com.github.jengelman.gradle.plugins.shadow.relocation.Relocator
- Direction
- com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext uses com.github.jengelman.gradle.plugins.shadow.relocation, so a change to com.github.jengelman.gradle.plugins.shadow.relocation can break com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext, while a change to com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext can't break com.github.jengelman.gradle.plugins.shadow.relocation.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext uses a module listed above it, which is the healthy direction.
30→27 com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext uses com.github.jengelman.gradle.plugins.shadow.transformers✕
- Connections
- 1 pair of types, where a type in com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext uses a type in com.github.jengelman.gradle.plugins.shadow.transformers.
- The types involved
com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext.Builder→com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext
- Direction
- com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext uses com.github.jengelman.gradle.plugins.shadow.transformers, so a change to com.github.jengelman.gradle.plugins.shadow.transformers can break com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext, while a change to com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext can't break com.github.jengelman.gradle.plugins.shadow.transformers.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.transformers.TransformerContext uses a module listed above it, which is the healthy direction.
31→28 com.github.jengelman.gradle.plugins.shadow uses com.github.jengelman.gradle.plugins.shadow.tasks✕
- Connections
- 1 pair of types, where a type in com.github.jengelman.gradle.plugins.shadow uses a type in com.github.jengelman.gradle.plugins.shadow.tasks.
- The types involved
com.github.jengelman.gradle.plugins.shadow.ShadowSourcesPublishArtifact→com.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar
- Direction
- com.github.jengelman.gradle.plugins.shadow uses com.github.jengelman.gradle.plugins.shadow.tasks, so a change to com.github.jengelman.gradle.plugins.shadow.tasks can break com.github.jengelman.gradle.plugins.shadow, while a change to com.github.jengelman.gradle.plugins.shadow can't break com.github.jengelman.gradle.plugins.shadow.tasks.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow uses a module listed above it, which is the healthy direction.
32→28 com.github.jengelman.gradle.plugins.shadow.tasks.MinimizeTool uses com.github.jengelman.gradle.plugins.shadow.tasks✕
- Connections
- 2 pairs of types, where a type in com.github.jengelman.gradle.plugins.shadow.tasks.MinimizeTool uses a type in com.github.jengelman.gradle.plugins.shadow.tasks.
- The types involved
com.github.jengelman.gradle.plugins.shadow.tasks.MinimizeTool.DEPENDENCY_ANALYZER→com.github.jengelman.gradle.plugins.shadow.tasks.MinimizeToolcom.github.jengelman.gradle.plugins.shadow.tasks.MinimizeTool.R8→com.github.jengelman.gradle.plugins.shadow.tasks.MinimizeTool
- Direction
- com.github.jengelman.gradle.plugins.shadow.tasks.MinimizeTool uses com.github.jengelman.gradle.plugins.shadow.tasks, so a change to com.github.jengelman.gradle.plugins.shadow.tasks can break com.github.jengelman.gradle.plugins.shadow.tasks.MinimizeTool, while a change to com.github.jengelman.gradle.plugins.shadow.tasks.MinimizeTool can't break com.github.jengelman.gradle.plugins.shadow.tasks.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.tasks.MinimizeTool uses a module listed above it, which is the healthy direction.
33→28 com.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar uses com.github.jengelman.gradle.plugins.shadow.tasks✕
- Connections
- 1 pair of types, where a type in com.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar uses a type in com.github.jengelman.gradle.plugins.shadow.tasks.
- The types involved
com.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar.Companion→com.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar
- Direction
- com.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar uses com.github.jengelman.gradle.plugins.shadow.tasks, so a change to com.github.jengelman.gradle.plugins.shadow.tasks can break com.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar, while a change to com.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar can't break com.github.jengelman.gradle.plugins.shadow.tasks.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar uses a module listed above it, which is the healthy direction.
34→31 com.github.jengelman.gradle.plugins.shadow.ShadowBasePlugin uses com.github.jengelman.gradle.plugins.shadow✕
- Connections
- 1 pair of types, where a type in com.github.jengelman.gradle.plugins.shadow.ShadowBasePlugin uses a type in com.github.jengelman.gradle.plugins.shadow.
- The types involved
com.github.jengelman.gradle.plugins.shadow.ShadowBasePlugin.Companion→com.github.jengelman.gradle.plugins.shadow.ShadowExtension
- Direction
- com.github.jengelman.gradle.plugins.shadow.ShadowBasePlugin uses com.github.jengelman.gradle.plugins.shadow, so a change to com.github.jengelman.gradle.plugins.shadow can break com.github.jengelman.gradle.plugins.shadow.ShadowBasePlugin, while a change to com.github.jengelman.gradle.plugins.shadow.ShadowBasePlugin can't break com.github.jengelman.gradle.plugins.shadow.
- Position
- Below the diagonal: com.github.jengelman.gradle.plugins.shadow.ShadowBasePlugin 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 | 24 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; 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; Resolve the 1 Off-boarding risk finding(s) in Bus Factor.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +3.8 pts | Low | Bus Factor |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +4.6 pts | Medium | Security & performance tooling |
| 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. | +4.0 pts | Medium | Architecture documentation |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +2.4 pts | Medium | Documentation (README) |
| 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. | +0.4 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/transformers/PropertiesFileTransformer.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/testKit/kotlin/com/github/jengelman/gradle/plugins/shadow/testkit/GradleRunner.kt | 6.9 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/transformers/ApacheNoticeResourceTransformer.kt | 7.4 | Mixed | Cyclomatic Complexity: ApacheNoticeResourceTransformer.transform (cyclomatic 17) |
| .github/scripts/update_renovate_changelog.py | 7.4 | Mixed | Cyclomatic Complexity: update_renovate_changelog.main (cyclomatic 17) |
| src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/relocation/SimpleRelocator.kt | 7.8 | Mixed | Cyclomatic Complexity: SimpleRelocator.isValidSourceContext (cyclomatic 25) |
| src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/tasks/ShadowJar.kt | 7.8 | Mixed | God Classes: ClassTooLong: ShadowJar |
| src/testKit/kotlin/com/github/jengelman/gradle/plugins/shadow/testkit/AssertK.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/test/kotlin/com/github/jengelman/gradle/plugins/shadow/tasks/ShadowCopyActionTest.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/ShadowApplicationPlugin.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/ShadowJavaPlugin.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/transformers/ComponentsXmlResourceTransformer.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/DefaultInheritManifest.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/Zip.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/functionalTest/kotlin/com/github/jengelman/gradle/plugins/shadow/KotlinPluginsTest.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/ShadowedSourcesJar.kt | 8.5 | Near-clean | Cognitive Complexity: ShadowedSourcesJarKt.generateSourcesJar (cognitive 16) |
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 40 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 — 40 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, 56 of 134 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
- 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape 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. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/GradleCompat.kt`, `src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/Zip.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is an unrecognised JSR-330 (javax.inject / jakarta.inject) container, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- 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.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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").
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SimpleRelocator.isValidSourceContext at 25.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SimpleRelocator.isValidSourceContext (cyclomatic 25), ApacheNoticeResourceTransformer.transform (cyclomatic 17), update_renovate_changelog.main (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 3 together lifts Cyclomatic Complexity from 9.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
6 method(s) exceeded the cognitive complexity threshold of 15; the worst was SimpleRelocator.isValidSourceContext at 40.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cognitive Complexity — start with SimpleRelocator.isValidSourceContext (cognitive 40), ApacheNoticeResourceTransformer.transform (cognitive 40), update_renovate_changelog.update_changelog (cognitive 22). — 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 6 together lifts Cognitive Complexity from 8.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
2 god class(es) detected.
What to do
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with ShadowJar.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with ShadowJar.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
1 duplicated block group(s) detected. 0.7 % of the production lines (36 of 5,247) are in a reported copy. One further row reports members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 1 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with PropertiesFileTransformer.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with AppendingTransformer.kt. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 21 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Java/Kotlin (repository root, Gradle): measured (0 flaky).
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 171 artifact(s) resolved, 153 of them gradable against Maven Central, and 72 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 6 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 3 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. A further 1 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
18 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/tasks/ShadowJar.kt. Counted over 31 of the 59 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
12 deducted task-comment markers across 5247 LoC (0.2/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 12 TodoComment finding(s) in Explicit Debt — start with GradleRunner.kt (3), AssertK.kt, ShadowCopyActionTest.kt. — One of this dimension's main actionable groups (12 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 19 document(s) read across 1 unit(s).
D26 · Project Cohesion
0 of 2 build units (Gradle) flagged as possibly oversized/incoherent.
D27 · Navigability
41 % of calls cross a namespace and 16 % 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)
24 finding(s): 0 critical, 23 high, 1 medium, 0 low. 19 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 1 file(s) — `gradlew` (line 74, line 178) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 19 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 (19 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 31 of the 59 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: R8Minimizer.kt↔Zip.kt 60%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with R8Minimizer.kt. — One of this dimension's main actionable groups (1 warning-level).
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).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 7 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it.
P10 · Library API & versioning
- 12 public types in `com.github.jengelman.gradle.plugins.shadow.internal` are marked as implementation by their own namespace, folder or name: `DuplicatesStrategyCheckerKt` (src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/DuplicatesStrategyChecker.kt:1, `internal`), `GradleCompatKt` (src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/GradleCompat.kt:1, `internal`), `KotlinCompatKt` (src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/KotlinCompat.kt:1, `internal`), `OrderedParallelWriterKt` (src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/OrderedParallelWriter.kt:1, `internal`), `R8MinimizerKt` (src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/R8Minimizer.kt:1, `internal`), `RelocatorRemapperKt` (src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/RelocatorRemapper.kt:1, `internal`), `RelocatorsKt` (src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/Relocators.kt:1, `internal`), `ShadowedSourcesJarKt` (src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/ShadowedSourcesJar.kt:1, `internal`), and 4 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/DuplicatesStrategyChecker.kt:1
- 1 public type in `com.github.jengelman.gradle.plugins.shadow.internal.UnixMode` is marked as implementation by its own namespace, folder or name: `Companion` (src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/Zip.kt:16, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/Zip.kt:16
What to do
- Hide `com.github.jengelman.gradle.plugins.shadow.internal` (`DuplicatesStrategyCheckerKt`, `GradleCompatKt`, `KotlinCompatKt`, `OrderedParallelWriterKt`, `R8MinimizerKt`, `RelocatorRemapperKt`, `RelocatorsKt`, `ShadowedSourcesJarKt`, and 4 more) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.github.jengelman.gradle.plugins.shadow.internal.UnixMode` (`Companion`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 5 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:7
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X3 · Exception handling
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 96% | Exemplary | Solid. |
| Architecture | 100% | Exemplary | Strongest area. |
| Maturity | 59% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 59% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 68% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 76 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.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~13582 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Kotlin surface was not measured.
- 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 — this repository's production source is .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D5 Coupling — Not applicable — this Gradle build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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 — not scored — this repository shows only 1 of the 3 signals this lens looks for (7 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 19 current-state document(s) make no claim of a kind M4 checks. 6 claim(s) of kinds M4 does not check were not checked (path 3, environment variable 3); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JVM source (2 module(s), 55 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
- 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
- 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
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — 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
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — 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 Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 23 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
Serious — 31 finding(s)
- TodoComment src/testKit/kotlin/com/github/jengelman/gradle/plugins/shadow/testkit/AssertK.kt:12
- TodoComment src/testKit/kotlin/com/github/jengelman/gradle/plugins/shadow/testkit/GradleRunner.kt:20
- TodoComment src/testKit/kotlin/com/github/jengelman/gradle/plugins/shadow/testkit/GradleRunner.kt:29
- TodoComment src/testKit/kotlin/com/github/jengelman/gradle/plugins/shadow/testkit/GradleRunner.kt:52
- TodoComment src/test/kotlin/com/github/jengelman/gradle/plugins/shadow/tasks/ShadowCopyActionTest.kt:47
- TodoComment src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/ShadowApplicationPlugin.kt:68
- TodoComment src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/ShadowJavaPlugin.kt:244
- TodoComment src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/transformers/ComponentsXmlResourceTransformer.kt:82
- TodoComment src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/transformers/PropertiesFileTransformer.kt:127
- TodoComment src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/DefaultInheritManifest.kt:1
- TodoComment src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/Zip.kt:40
- TodoComment src/functionalTest/kotlin/com/github/jengelman/gradle/plugins/shadow/KotlinPluginsTest.kt:182
- REDACTED
- REDACTED
- SimpleRelocator.isValidSourceContext (cyclomatic 25) src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/relocation/SimpleRelocator.kt:286
- ApacheNoticeResourceTransformer.transform (cyclomatic 17) src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/transformers/ApacheNoticeResourceTransformer.kt:104
- update_renovate_changelog.main (cyclomatic 17) .github/scripts/update_renovate_changelog.py:111
- SimpleRelocator.isValidSourceContext (cognitive 40) src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/relocation/SimpleRelocator.kt:286
- ApacheNoticeResourceTransformer.transform (cognitive 40) src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/transformers/ApacheNoticeResourceTransformer.kt:104
- update_renovate_changelog.update_changelog (cognitive 22) .github/scripts/update_renovate_changelog.py:49
- update_renovate_changelog.main (cognitive 19) .github/scripts/update_renovate_changelog.py:111
- ApacheNoticeResourceTransformer.modifyOutputStream (cognitive 17) src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/transformers/ApacheNoticeResourceTransformer.kt:183
- ShadowedSourcesJarKt.generateSourcesJar (cognitive 16) src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/ShadowedSourcesJar.kt:14
- REDACTED
- ClassTooLong: ShadowJar src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/tasks/ShadowJar.kt:82
- FileTooLong: tasks/ShadowJar.kt src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/tasks/ShadowJar.kt
- Change coupling: R8Minimizer.kt ↔ Zip.kt src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/R8Minimizer.kt:1
- REDACTED
- REDACTED
- Edited copy of a member (14 corresponding lines) src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/transformers/PropertiesFileTransformer.kt:176
- Duplicated block (5 lines × 2) src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/transformers/AppendingTransformer.kt:35
Minor — 8 finding(s)
- Implementation type on the public API src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/DuplicatesStrategyChecker.kt:1
- Implementation type on the public API src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/Zip.kt:16
- Off-boarding risk: anonymized user #1
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:7
Minor — 72 finding(s)
- Outdated (compile): com.google.guava:guava
- Outdated (compile): com.google.guava:failureaccess
- Outdated (compile): org.checkerframework:checker-qual
- Outdated (compile): com.google.errorprone:error_prone_annotations
- Outdated (compile): com.google.j2objc:j2objc-annotations
- Outdated (compile): net.java.dev.jna:jna-platform
- Outdated (compile): net.java.dev.jna:jna
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk8
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): org.jetbrains:annotations
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk7
- Outdated (compile): com.google.protobuf:protobuf-java
- Outdated (compile): com.google.code.gson:gson
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-bom
- Outdated (compile): com.google.jimfs:jimfs
- Outdated (compile): org.apache.commons:commons-compress
- Outdated (compile): commons-codec:commons-codec
- Outdated (compile): commons-io:commons-io
- Outdated (compile): org.apache.commons:commons-lang3
- Outdated (compile): org.glassfish.jaxb:jaxb-runtime
- Outdated (compile): jakarta.xml.bind:jakarta.xml.bind-api
- Outdated (compile): jakarta.activation:jakarta.activation-api
- Outdated (compile): org.glassfish.jaxb:txw2
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-09c4ea6f4e8d44399dc800965edf6f6e/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-09c4ea6f4e8d44399dc800965edf6f6e/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 . | 24 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/GradleCompat.kt`, `src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/Zip.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |