Executive summary
Triple-T/gradle-play-publisher falls short of our standard for production because its Security dimensions are rated Critical, and three passwords or keys sit in the current code. It scores 52 out of 100, which alone would earn Adequate, but it is rated Weak: a rating can't sit more than one step above its weakest group.
Production Readiness, at 31, is the weakest lens and counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 20 points. Recording design decisions comes next, worth about 8 points. Raising Production Readiness to 70 would lift the score to about 67.
Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three passwords or keys in the code and two in the code's history are open to anyone who can read the repository. Pinning each tool to an exact version and replacing each exposed password or key would close both risks.
The product code is 5,037 lines, about €11,000 to rebuild.
If Production Readiness rose from 31 to 70, the lowest score rated Strong, the score would rise from 52 to about 67.
New since the last survey: 9 findings
- Code Duplication · Edited copy of a member (16 corresponding lines) play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishProducts.kt
- Code Duplication · Edited copy of a member (21 corresponding lines) play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishProducts.kt
- Code Duplication · Edited copy of a member (18 corresponding lines) play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/DefaultPlayPublisher.kt
- Code Duplication · Edited copy of a member (19 corresponding lines) play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/DefaultPlayPublisher.kt
- Code Duplication · Edited copy of a member (8 corresponding lines) play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishBundle.kt
- Code Duplication · Edited copy of a member (5 corresponding lines) play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/DefaultEditManager.kt
- Code Duplication · Duplicated block (20 lines × 2) play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishApk.kt
- Code Duplication · Duplicated block (7 lines × 2) play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishProducts.kt
- Code Duplication · Duplicated block (10 lines × 2) play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishInternalSharingApk.kt
Fixed since the last survey: 1 finding
- Code Duplication · Duplicated block (20 lines × 2) play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishApk.kt
Rebuild cost: about €11,000 · Estimate
| Cost to rebuild | €3,700 to €19,000, for 61 to 195 hours of work, under 0.1 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.7 at a score of 52. 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,037 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 androidpublisher | 2 play.PlayPublisherExtension | 3 play.tasks.GenerateResources | 4 play.tasks.InstallInternalSharingArtifact | 5 androidpublisher.CommitResponse | 6 androidpublisher.EditManager | 7 androidpublisher.EditResponse | 8 androidpublisher.PlayPublisher | 9 androidpublisher.ReleaseStatus | 10 androidpublisher.ResolutionStrategy | 11 androidpublisher.internal.DefaultTrackManager | 12 androidpublisher.internal.TrackManager | 13 play | 14 play.tasks.InstallInternalSharingArtifact.AdbShell | 15 play.tasks.internal.BootstrapOptions | 16 androidpublisher.internal | 17 androidpublisher.internal.DefaultPlayPublisher | 18 play.tasks.InstallInternalSharingArtifact.DefaultAdbShell | 19 play.tasks.internal | 20 androidpublisher.internal.DefaultEditManager | 21 play.tasks | 22 play.internal | 23 play.internal.AppDetail | 24 play.internal.ImageType | 25 play.internal.ListingDetail | 26 play.tasks.internal.workers.PlayWorkerBase | 27 play.tasks.CommitEdit.Committer | 28 play.tasks.internal.workers.EditWorkerBase | 29 play.tasks.Bootstrap.DetailsDownloader | 30 play.tasks.Bootstrap.ImageFetcher | 31 play.tasks.Bootstrap.ListingsDownloader | 32 play.tasks.Bootstrap.ProductsDownloader | 33 play.tasks.Bootstrap.ReleaseNotesDownloader | 34 play.tasks.Bootstrap.SubscriptionsDownloader | 35 play.tasks.PublishListings.MediaUploader | 36 play.tasks.PublishListings.Publisher | 37 play.tasks.internal.workers.PublishArtifactWorkerBase | 38 play.tasks.internal.workers | 39 play.tasks.Bootstrap | 40 play.tasks.CommitEdit |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 androidpublisher | ||||||||||||||||||||||||||||||||||||||||
| 2 play.PlayPublisherExtension | ||||||||||||||||||||||||||||||||||||||||
| 3 play.tasks.GenerateResources | ||||||||||||||||||||||||||||||||||||||||
| 4 play.tasks.InstallInternalSharingArtifact | ||||||||||||||||||||||||||||||||||||||||
| 5 androidpublisher.CommitResponse | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 androidpublisher.EditManager | 4 | |||||||||||||||||||||||||||||||||||||||
| 7 androidpublisher.EditResponse | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 androidpublisher.PlayPublisher | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 androidpublisher.ReleaseStatus | 4 | |||||||||||||||||||||||||||||||||||||||
| 10 androidpublisher.ResolutionStrategy | 4 | |||||||||||||||||||||||||||||||||||||||
| 11 androidpublisher.internal.DefaultTrackManager | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 androidpublisher.internal.TrackManager | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 play | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 play.tasks.InstallInternalSharingArtifact.AdbShell | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 play.tasks.internal.BootstrapOptions | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 androidpublisher.internal | 16 | 5 | ||||||||||||||||||||||||||||||||||||||
| 17 androidpublisher.internal.DefaultPlayPublisher | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 play.tasks.InstallInternalSharingArtifact.DefaultAdbShell | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 play.tasks.internal | 6 | 1 | 9 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 androidpublisher.internal.DefaultEditManager | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 play.tasks | 11 | 1 | 18 | 2 | ||||||||||||||||||||||||||||||||||||
| 22 play.internal | 2 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 play.internal.AppDetail | 4 | |||||||||||||||||||||||||||||||||||||||
| 24 play.internal.ImageType | 8 | |||||||||||||||||||||||||||||||||||||||
| 25 play.internal.ListingDetail | 4 | |||||||||||||||||||||||||||||||||||||||
| 26 play.tasks.internal.workers.PlayWorkerBase | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 play.tasks.CommitEdit.Committer | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 play.tasks.internal.workers.EditWorkerBase | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 play.tasks.Bootstrap.DetailsDownloader | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 play.tasks.Bootstrap.ImageFetcher | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 play.tasks.Bootstrap.ListingsDownloader | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 play.tasks.Bootstrap.ProductsDownloader | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 play.tasks.Bootstrap.ReleaseNotesDownloader | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 play.tasks.Bootstrap.SubscriptionsDownloader | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 play.tasks.PublishListings.MediaUploader | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 play.tasks.PublishListings.Publisher | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 play.tasks.internal.workers.PublishArtifactWorkerBase | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 play.tasks.internal.workers | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 play.tasks.Bootstrap | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 40 play.tasks.CommitEdit | 1 |
5→1 androidpublisher.CommitResponse uses androidpublisher✕
- Connections
- 2 pairs of types, where a type in androidpublisher.CommitResponse uses a type in androidpublisher.
- The types involved
com.github.triplet.gradle.androidpublisher.CommitResponse.Failure→com.github.triplet.gradle.androidpublisher.CommitResponsecom.github.triplet.gradle.androidpublisher.CommitResponse.Success→com.github.triplet.gradle.androidpublisher.CommitResponse
- Direction
- androidpublisher.CommitResponse uses androidpublisher, so a change to androidpublisher can break androidpublisher.CommitResponse, while a change to androidpublisher.CommitResponse can't break androidpublisher.
- Position
- Below the diagonal: androidpublisher.CommitResponse uses a module listed above it, which is the healthy direction.
6→1 androidpublisher.EditManager uses androidpublisher✕
- Connections
- 4 pairs of types, where a type in androidpublisher.EditManager uses a type in androidpublisher.
- The types involved
com.github.triplet.gradle.androidpublisher.EditManager.Companion→com.github.triplet.gradle.androidpublisher.EditManagercom.github.triplet.gradle.androidpublisher.EditManager.Companion→com.github.triplet.gradle.androidpublisher.PlayPublishercom.github.triplet.gradle.androidpublisher.EditManager.Factory→com.github.triplet.gradle.androidpublisher.EditManagercom.github.triplet.gradle.androidpublisher.EditManager.Factory→com.github.triplet.gradle.androidpublisher.PlayPublisher
- Direction
- androidpublisher.EditManager uses androidpublisher, so a change to androidpublisher can break androidpublisher.EditManager, while a change to androidpublisher.EditManager can't break androidpublisher.
- Position
- Below the diagonal: androidpublisher.EditManager uses a module listed above it, which is the healthy direction.
7→1 androidpublisher.EditResponse uses androidpublisher✕
- Connections
- 2 pairs of types, where a type in androidpublisher.EditResponse uses a type in androidpublisher.
- The types involved
com.github.triplet.gradle.androidpublisher.EditResponse.Failure→com.github.triplet.gradle.androidpublisher.EditResponsecom.github.triplet.gradle.androidpublisher.EditResponse.Success→com.github.triplet.gradle.androidpublisher.EditResponse
- Direction
- androidpublisher.EditResponse uses androidpublisher, so a change to androidpublisher can break androidpublisher.EditResponse, while a change to androidpublisher.EditResponse can't break androidpublisher.
- Position
- Below the diagonal: androidpublisher.EditResponse uses a module listed above it, which is the healthy direction.
8→1 androidpublisher.PlayPublisher uses androidpublisher✕
- Connections
- 2 pairs of types, where a type in androidpublisher.PlayPublisher uses a type in androidpublisher.
- The types involved
com.github.triplet.gradle.androidpublisher.PlayPublisher.Companion→com.github.triplet.gradle.androidpublisher.PlayPublishercom.github.triplet.gradle.androidpublisher.PlayPublisher.Factory→com.github.triplet.gradle.androidpublisher.PlayPublisher
- Direction
- androidpublisher.PlayPublisher uses androidpublisher, so a change to androidpublisher can break androidpublisher.PlayPublisher, while a change to androidpublisher.PlayPublisher can't break androidpublisher.
- Position
- Below the diagonal: androidpublisher.PlayPublisher uses a module listed above it, which is the healthy direction.
9→1 androidpublisher.ReleaseStatus uses androidpublisher✕
- Connections
- 4 pairs of types, where a type in androidpublisher.ReleaseStatus uses a type in androidpublisher.
- The types involved
com.github.triplet.gradle.androidpublisher.ReleaseStatus.COMPLETED→com.github.triplet.gradle.androidpublisher.ReleaseStatuscom.github.triplet.gradle.androidpublisher.ReleaseStatus.DRAFT→com.github.triplet.gradle.androidpublisher.ReleaseStatuscom.github.triplet.gradle.androidpublisher.ReleaseStatus.HALTED→com.github.triplet.gradle.androidpublisher.ReleaseStatuscom.github.triplet.gradle.androidpublisher.ReleaseStatus.IN_PROGRESS→com.github.triplet.gradle.androidpublisher.ReleaseStatus
- Direction
- androidpublisher.ReleaseStatus uses androidpublisher, so a change to androidpublisher can break androidpublisher.ReleaseStatus, while a change to androidpublisher.ReleaseStatus can't break androidpublisher.
- Position
- Below the diagonal: androidpublisher.ReleaseStatus uses a module listed above it, which is the healthy direction.
10→1 androidpublisher.ResolutionStrategy uses androidpublisher✕
- Connections
- 4 pairs of types, where a type in androidpublisher.ResolutionStrategy uses a type in androidpublisher.
- The types involved
com.github.triplet.gradle.androidpublisher.ResolutionStrategy.AUTO→com.github.triplet.gradle.androidpublisher.ResolutionStrategycom.github.triplet.gradle.androidpublisher.ResolutionStrategy.AUTO_OFFSET→com.github.triplet.gradle.androidpublisher.ResolutionStrategycom.github.triplet.gradle.androidpublisher.ResolutionStrategy.FAIL→com.github.triplet.gradle.androidpublisher.ResolutionStrategycom.github.triplet.gradle.androidpublisher.ResolutionStrategy.IGNORE→com.github.triplet.gradle.androidpublisher.ResolutionStrategy
- Direction
- androidpublisher.ResolutionStrategy uses androidpublisher, so a change to androidpublisher can break androidpublisher.ResolutionStrategy, while a change to androidpublisher.ResolutionStrategy can't break androidpublisher.
- Position
- Below the diagonal: androidpublisher.ResolutionStrategy uses a module listed above it, which is the healthy direction.
11→1 androidpublisher.internal.DefaultTrackManager uses androidpublisher✕
- Connections
- 1 pair of types, where a type in androidpublisher.internal.DefaultTrackManager uses a type in androidpublisher.
- The types involved
com.github.triplet.gradle.androidpublisher.internal.DefaultTrackManager.Companion→com.github.triplet.gradle.androidpublisher.ReleaseStatus
- Direction
- androidpublisher.internal.DefaultTrackManager uses androidpublisher, so a change to androidpublisher can break androidpublisher.internal.DefaultTrackManager, while a change to androidpublisher.internal.DefaultTrackManager can't break androidpublisher.
- Position
- Below the diagonal: androidpublisher.internal.DefaultTrackManager uses a module listed above it, which is the healthy direction.
12→1 androidpublisher.internal.TrackManager uses androidpublisher✕
- Connections
- 1 pair of types, where a type in androidpublisher.internal.TrackManager uses a type in androidpublisher.
- The types involved
com.github.triplet.gradle.androidpublisher.internal.TrackManager.BaseConfig→com.github.triplet.gradle.androidpublisher.ReleaseStatus
- Direction
- androidpublisher.internal.TrackManager uses androidpublisher, so a change to androidpublisher can break androidpublisher.internal.TrackManager, while a change to androidpublisher.internal.TrackManager can't break androidpublisher.
- Position
- Below the diagonal: androidpublisher.internal.TrackManager uses a module listed above it, which is the healthy direction.
13→1 play uses androidpublisher✕
- Connections
- 2 pairs of types, where a type in play uses a type in androidpublisher.
- The types involved
com.github.triplet.gradle.play.PlayPublisherExtension→com.github.triplet.gradle.androidpublisher.ReleaseStatuscom.github.triplet.gradle.play.PlayPublisherExtension→com.github.triplet.gradle.androidpublisher.ResolutionStrategy
- Direction
- play uses androidpublisher, so a change to androidpublisher can break play, while a change to play can't break androidpublisher.
- Position
- Below the diagonal: play uses a module listed above it, which is the healthy direction.
13→2 play uses play.PlayPublisherExtension✕
- Connections
- 1 pair of types, where a type in play uses a type in play.PlayPublisherExtension.
- The types involved
com.github.triplet.gradle.play.PlayPublisherExtension→com.github.triplet.gradle.play.PlayPublisherExtension.Retain
- Direction
- play uses play.PlayPublisherExtension, so a change to play.PlayPublisherExtension can break play, while a change to play can't break play.PlayPublisherExtension.
- Position
- Below the diagonal: play uses a module listed above it, which is the healthy direction.
14→4 play.tasks.InstallInternalSharingArtifact.AdbShell uses play.tasks.InstallInternalSharingArtifact✕
- Connections
- 2 pairs of types, where a type in play.tasks.InstallInternalSharingArtifact.AdbShell uses a type in play.tasks.InstallInternalSharingArtifact.
- The types involved
com.github.triplet.gradle.play.tasks.InstallInternalSharingArtifact.AdbShell.Companion→com.github.triplet.gradle.play.tasks.InstallInternalSharingArtifact.AdbShellcom.github.triplet.gradle.play.tasks.InstallInternalSharingArtifact.AdbShell.Factory→com.github.triplet.gradle.play.tasks.InstallInternalSharingArtifact.AdbShell
- Direction
- play.tasks.InstallInternalSharingArtifact.AdbShell uses play.tasks.InstallInternalSharingArtifact, so a change to play.tasks.InstallInternalSharingArtifact can break play.tasks.InstallInternalSharingArtifact.AdbShell, while a change to play.tasks.InstallInternalSharingArtifact.AdbShell can't break play.tasks.InstallInternalSharingArtifact.
- Position
- Below the diagonal: play.tasks.InstallInternalSharingArtifact.AdbShell uses a module listed above it, which is the healthy direction.
15→19 play.tasks.internal.BootstrapOptions uses play.tasks.internal part of a loop✕
- Connections
- 1 pair of types, where a type in play.tasks.internal.BootstrapOptions uses a type in play.tasks.internal.
- The types involved
com.github.triplet.gradle.play.tasks.internal.BootstrapOptions.Holder→com.github.triplet.gradle.play.tasks.internal.BootstrapOptions
- Direction
- play.tasks.internal.BootstrapOptions uses play.tasks.internal, so a change to play.tasks.internal can break play.tasks.internal.BootstrapOptions, while a change to play.tasks.internal.BootstrapOptions can't break play.tasks.internal.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→1 androidpublisher.internal uses androidpublisher✕
- Connections
- 16 pairs of types, where a type in androidpublisher.internal uses a type in androidpublisher.
- The types involved
com.github.triplet.gradle.androidpublisher.internal.DefaultEditManager→com.github.triplet.gradle.androidpublisher.EditManagercom.github.triplet.gradle.androidpublisher.internal.DefaultEditManager→com.github.triplet.gradle.androidpublisher.GppAppDetailscom.github.triplet.gradle.androidpublisher.internal.DefaultEditManager→com.github.triplet.gradle.androidpublisher.GppImagecom.github.triplet.gradle.androidpublisher.internal.DefaultEditManager→com.github.triplet.gradle.androidpublisher.GppListingcom.github.triplet.gradle.androidpublisher.internal.DefaultEditManager→com.github.triplet.gradle.androidpublisher.ReleaseNotecom.github.triplet.gradle.androidpublisher.internal.DefaultEditManager→com.github.triplet.gradle.androidpublisher.ReleaseStatuscom.github.triplet.gradle.androidpublisher.internal.DefaultEditManager→com.github.triplet.gradle.androidpublisher.ResolutionStrategycom.github.triplet.gradle.androidpublisher.internal.DefaultPlayPublisher→com.github.triplet.gradle.androidpublisher.CommitResponsecom.github.triplet.gradle.androidpublisher.internal.DefaultPlayPublisher→com.github.triplet.gradle.androidpublisher.EditResponsecom.github.triplet.gradle.androidpublisher.internal.DefaultPlayPublisher→com.github.triplet.gradle.androidpublisher.GppProductcom.github.triplet.gradle.androidpublisher.internal.DefaultPlayPublisher→com.github.triplet.gradle.androidpublisher.GppSubscriptioncom.github.triplet.gradle.androidpublisher.internal.DefaultPlayPublisher→com.github.triplet.gradle.androidpublisher.UpdateProductResponsecom.github.triplet.gradle.androidpublisher.internal.DefaultPlayPublisher→com.github.triplet.gradle.androidpublisher.UpdateSubscriptionResponsecom.github.triplet.gradle.androidpublisher.internal.DefaultPlayPublisher→com.github.triplet.gradle.androidpublisher.UploadInternalSharingArtifactResponsecom.github.triplet.gradle.androidpublisher.internal.DefaultTrackManager→com.github.triplet.gradle.androidpublisher.ReleaseStatuscom.github.triplet.gradle.androidpublisher.internal.InternalPlayPublisher→com.github.triplet.gradle.androidpublisher.PlayPublisher
- Direction
- androidpublisher.internal uses androidpublisher, so a change to androidpublisher can break androidpublisher.internal, while a change to androidpublisher.internal can't break androidpublisher.
- Position
- Below the diagonal: androidpublisher.internal uses a module listed above it, which is the healthy direction.
16→12 androidpublisher.internal uses androidpublisher.internal.TrackManager✕
- Connections
- 5 pairs of types, where a type in androidpublisher.internal uses a type in androidpublisher.internal.TrackManager.
- The types involved
com.github.triplet.gradle.androidpublisher.internal.DefaultTrackManager→com.github.triplet.gradle.androidpublisher.internal.TrackManager.BaseConfigcom.github.triplet.gradle.androidpublisher.internal.DefaultTrackManager→com.github.triplet.gradle.androidpublisher.internal.TrackManager.PromoteConfigcom.github.triplet.gradle.androidpublisher.internal.DefaultTrackManager→com.github.triplet.gradle.androidpublisher.internal.TrackManager.UpdateConfigcom.github.triplet.gradle.androidpublisher.internal.TrackManager→com.github.triplet.gradle.androidpublisher.internal.TrackManager.PromoteConfigcom.github.triplet.gradle.androidpublisher.internal.TrackManager→com.github.triplet.gradle.androidpublisher.internal.TrackManager.UpdateConfig
- Direction
- androidpublisher.internal uses androidpublisher.internal.TrackManager, so a change to androidpublisher.internal.TrackManager can break androidpublisher.internal, while a change to androidpublisher.internal can't break androidpublisher.internal.TrackManager.
- Position
- Below the diagonal: androidpublisher.internal uses a module listed above it, which is the healthy direction.
17→1 androidpublisher.internal.DefaultPlayPublisher uses androidpublisher✕
- Connections
- 1 pair of types, where a type in androidpublisher.internal.DefaultPlayPublisher uses a type in androidpublisher.
- The types involved
com.github.triplet.gradle.androidpublisher.internal.DefaultPlayPublisher.Factory→com.github.triplet.gradle.androidpublisher.PlayPublisher
- Direction
- androidpublisher.internal.DefaultPlayPublisher uses androidpublisher, so a change to androidpublisher can break androidpublisher.internal.DefaultPlayPublisher, while a change to androidpublisher.internal.DefaultPlayPublisher can't break androidpublisher.
- Position
- Below the diagonal: androidpublisher.internal.DefaultPlayPublisher uses a module listed above it, which is the healthy direction.
17→8 androidpublisher.internal.DefaultPlayPublisher uses androidpublisher.PlayPublisher✕
- Connections
- 1 pair of types, where a type in androidpublisher.internal.DefaultPlayPublisher uses a type in androidpublisher.PlayPublisher.
- The types involved
com.github.triplet.gradle.androidpublisher.internal.DefaultPlayPublisher.Factory→com.github.triplet.gradle.androidpublisher.PlayPublisher.Factory
- Direction
- androidpublisher.internal.DefaultPlayPublisher uses androidpublisher.PlayPublisher, so a change to androidpublisher.PlayPublisher can break androidpublisher.internal.DefaultPlayPublisher, while a change to androidpublisher.internal.DefaultPlayPublisher can't break androidpublisher.PlayPublisher.
- Position
- Below the diagonal: androidpublisher.internal.DefaultPlayPublisher uses a module listed above it, which is the healthy direction.
18→4 play.tasks.InstallInternalSharingArtifact.DefaultAdbShell uses play.tasks.InstallInternalSharingArtifact✕
- Connections
- 1 pair of types, where a type in play.tasks.InstallInternalSharingArtifact.DefaultAdbShell uses a type in play.tasks.InstallInternalSharingArtifact.
- The types involved
com.github.triplet.gradle.play.tasks.InstallInternalSharingArtifact.DefaultAdbShell.Companion→com.github.triplet.gradle.play.tasks.InstallInternalSharingArtifact.AdbShell
- Direction
- play.tasks.InstallInternalSharingArtifact.DefaultAdbShell uses play.tasks.InstallInternalSharingArtifact, so a change to play.tasks.InstallInternalSharingArtifact can break play.tasks.InstallInternalSharingArtifact.DefaultAdbShell, while a change to play.tasks.InstallInternalSharingArtifact.DefaultAdbShell can't break play.tasks.InstallInternalSharingArtifact.
- Position
- Below the diagonal: play.tasks.InstallInternalSharingArtifact.DefaultAdbShell uses a module listed above it, which is the healthy direction.
18→14 play.tasks.InstallInternalSharingArtifact.DefaultAdbShell uses play.tasks.InstallInternalSharingArtifact.AdbShell✕
- Connections
- 1 pair of types, where a type in play.tasks.InstallInternalSharingArtifact.DefaultAdbShell uses a type in play.tasks.InstallInternalSharingArtifact.AdbShell.
- The types involved
com.github.triplet.gradle.play.tasks.InstallInternalSharingArtifact.DefaultAdbShell.Companion→com.github.triplet.gradle.play.tasks.InstallInternalSharingArtifact.AdbShell.Factory
- Direction
- play.tasks.InstallInternalSharingArtifact.DefaultAdbShell uses play.tasks.InstallInternalSharingArtifact.AdbShell, so a change to play.tasks.InstallInternalSharingArtifact.AdbShell can break play.tasks.InstallInternalSharingArtifact.DefaultAdbShell, while a change to play.tasks.InstallInternalSharingArtifact.DefaultAdbShell can't break play.tasks.InstallInternalSharingArtifact.AdbShell.
- Position
- Below the diagonal: play.tasks.InstallInternalSharingArtifact.DefaultAdbShell uses a module listed above it, which is the healthy direction.
19→1 play.tasks.internal uses androidpublisher✕
- Connections
- 6 pairs of types, where a type in play.tasks.internal uses a type in androidpublisher.
- The types involved
com.github.triplet.gradle.play.tasks.internal.CliOptionsImpl→com.github.triplet.gradle.androidpublisher.ReleaseStatuscom.github.triplet.gradle.play.tasks.internal.CliOptionsImpl→com.github.triplet.gradle.androidpublisher.ResolutionStrategycom.github.triplet.gradle.play.tasks.internal.PlayApiService→com.github.triplet.gradle.androidpublisher.EditManagercom.github.triplet.gradle.play.tasks.internal.PlayApiService→com.github.triplet.gradle.androidpublisher.PlayPublishercom.github.triplet.gradle.play.tasks.internal.PublishableTrackExtensionOptions→com.github.triplet.gradle.androidpublisher.ResolutionStrategycom.github.triplet.gradle.play.tasks.internal.TrackExtensionOptions→com.github.triplet.gradle.androidpublisher.ReleaseStatus
- Direction
- play.tasks.internal uses androidpublisher, so a change to androidpublisher can break play.tasks.internal, while a change to play.tasks.internal can't break androidpublisher.
- Position
- Below the diagonal: play.tasks.internal uses a module listed above it, which is the healthy direction.
19→7 play.tasks.internal uses androidpublisher.EditResponse✕
- Connections
- 1 pair of types, where a type in play.tasks.internal uses a type in androidpublisher.EditResponse.
- The types involved
com.github.triplet.gradle.play.tasks.internal.PlayApiService→com.github.triplet.gradle.androidpublisher.EditResponse.Failure
- Direction
- play.tasks.internal uses androidpublisher.EditResponse, so a change to androidpublisher.EditResponse can break play.tasks.internal, while a change to play.tasks.internal can't break androidpublisher.EditResponse.
- Position
- Below the diagonal: play.tasks.internal uses a module listed above it, which is the healthy direction.
19→13 play.tasks.internal uses play✕
- Connections
- 9 pairs of types, where a type in play.tasks.internal uses a type in play.
- The types involved
com.github.triplet.gradle.play.tasks.internal.CliOptionsImpl→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.internal.GlobalPublishableArtifactLifecycleTask→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.internal.GlobalUploadableArtifactLifecycleTask→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.internal.PlayTaskBase→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.internal.PublishArtifactTaskBase→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.internal.PublishTaskBase→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.internal.PublishableTrackLifecycleTask→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.internal.UpdatableTrackLifecycleTask→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.internal.WriteTrackLifecycleTask→com.github.triplet.gradle.play.PlayPublisherExtension
- Direction
- play.tasks.internal uses play, so a change to play can break play.tasks.internal, while a change to play.tasks.internal can't break play.
- Position
- Below the diagonal: play.tasks.internal uses a module listed above it, which is the healthy direction.
19→15 play.tasks.internal uses play.tasks.internal.BootstrapOptions✕
- Connections
- 1 pair of types, where a type in play.tasks.internal uses a type in play.tasks.internal.BootstrapOptions.
- The types involved
com.github.triplet.gradle.play.tasks.internal.BootstrapLifecycleTask→com.github.triplet.gradle.play.tasks.internal.BootstrapOptions.Holder
- Direction
- play.tasks.internal uses play.tasks.internal.BootstrapOptions, so a change to play.tasks.internal.BootstrapOptions can break play.tasks.internal, while a change to play.tasks.internal can't break play.tasks.internal.BootstrapOptions.
- Position
- Below the diagonal: play.tasks.internal uses a module listed above it, which is the healthy direction.
20→1 androidpublisher.internal.DefaultEditManager uses androidpublisher✕
- Connections
- 1 pair of types, where a type in androidpublisher.internal.DefaultEditManager uses a type in androidpublisher.
- The types involved
com.github.triplet.gradle.androidpublisher.internal.DefaultEditManager.Factory→com.github.triplet.gradle.androidpublisher.PlayPublisher
- Direction
- androidpublisher.internal.DefaultEditManager uses androidpublisher, so a change to androidpublisher can break androidpublisher.internal.DefaultEditManager, while a change to androidpublisher.internal.DefaultEditManager can't break androidpublisher.
- Position
- Below the diagonal: androidpublisher.internal.DefaultEditManager uses a module listed above it, which is the healthy direction.
20→6 androidpublisher.internal.DefaultEditManager uses androidpublisher.EditManager✕
- Connections
- 1 pair of types, where a type in androidpublisher.internal.DefaultEditManager uses a type in androidpublisher.EditManager.
- The types involved
com.github.triplet.gradle.androidpublisher.internal.DefaultEditManager.Factory→com.github.triplet.gradle.androidpublisher.EditManager.Factory
- Direction
- androidpublisher.internal.DefaultEditManager uses androidpublisher.EditManager, so a change to androidpublisher.EditManager can break androidpublisher.internal.DefaultEditManager, while a change to androidpublisher.internal.DefaultEditManager can't break androidpublisher.EditManager.
- Position
- Below the diagonal: androidpublisher.internal.DefaultEditManager uses a module listed above it, which is the healthy direction.
20→16 androidpublisher.internal.DefaultEditManager uses androidpublisher.internal✕
- Connections
- 1 pair of types, where a type in androidpublisher.internal.DefaultEditManager uses a type in androidpublisher.internal.
- The types involved
com.github.triplet.gradle.androidpublisher.internal.DefaultEditManager.Factory→com.github.triplet.gradle.androidpublisher.internal.DefaultEditManager
- Direction
- androidpublisher.internal.DefaultEditManager uses androidpublisher.internal, so a change to androidpublisher.internal can break androidpublisher.internal.DefaultEditManager, while a change to androidpublisher.internal.DefaultEditManager can't break androidpublisher.internal.
- Position
- Below the diagonal: androidpublisher.internal.DefaultEditManager uses a module listed above it, which is the healthy direction.
21→13 play.tasks uses play✕
- Connections
- 11 pairs of types, where a type in play.tasks uses a type in play.
- The types involved
com.github.triplet.gradle.play.tasks.Bootstrap→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.CommitEdit→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.ProcessArtifactVersionCodes→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.PromoteRelease→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.PublishApk→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.PublishBundle→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.PublishInternalSharingApk→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.PublishInternalSharingBundle→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.PublishListings→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.PublishProducts→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.tasks.PublishSubscriptions→com.github.triplet.gradle.play.PlayPublisherExtension
- Direction
- play.tasks uses play, so a change to play can break play.tasks, while a change to play.tasks can't break play.
- Position
- Below the diagonal: play.tasks uses a module listed above it, which is the healthy direction.
21→15 play.tasks uses play.tasks.internal.BootstrapOptions✕
- Connections
- 1 pair of types, where a type in play.tasks uses a type in play.tasks.internal.BootstrapOptions.
- The types involved
com.github.triplet.gradle.play.tasks.Bootstrap→com.github.triplet.gradle.play.tasks.internal.BootstrapOptions.Holder
- Direction
- play.tasks uses play.tasks.internal.BootstrapOptions, so a change to play.tasks.internal.BootstrapOptions can break play.tasks, while a change to play.tasks can't break play.tasks.internal.BootstrapOptions.
- Position
- Below the diagonal: play.tasks uses a module listed above it, which is the healthy direction.
21→19 play.tasks uses play.tasks.internal✕
- Connections
- 18 pairs of types, where a type in play.tasks uses a type in play.tasks.internal.
- The types involved
com.github.triplet.gradle.play.tasks.Bootstrap→com.github.triplet.gradle.play.tasks.internal.BootstrapOptionscom.github.triplet.gradle.play.tasks.Bootstrap→com.github.triplet.gradle.play.tasks.internal.PublishTaskBasecom.github.triplet.gradle.play.tasks.CommitEdit→com.github.triplet.gradle.play.tasks.internal.PublishTaskBasecom.github.triplet.gradle.play.tasks.ProcessArtifactVersionCodes→com.github.triplet.gradle.play.tasks.internal.PublishTaskBasecom.github.triplet.gradle.play.tasks.PromoteRelease→com.github.triplet.gradle.play.tasks.internal.PublishArtifactTaskBasecom.github.triplet.gradle.play.tasks.PromoteRelease→com.github.triplet.gradle.play.tasks.internal.UpdatableTrackExtensionOptionscom.github.triplet.gradle.play.tasks.PublishApk→com.github.triplet.gradle.play.tasks.internal.PublishArtifactTaskBasecom.github.triplet.gradle.play.tasks.PublishApk→com.github.triplet.gradle.play.tasks.internal.PublishableTrackExtensionOptionscom.github.triplet.gradle.play.tasks.PublishBundle→com.github.triplet.gradle.play.tasks.internal.PublishArtifactTaskBasecom.github.triplet.gradle.play.tasks.PublishBundle→com.github.triplet.gradle.play.tasks.internal.PublishableTrackExtensionOptionscom.github.triplet.gradle.play.tasks.PublishInternalSharingApk→com.github.triplet.gradle.play.tasks.internal.ArtifactExtensionOptionscom.github.triplet.gradle.play.tasks.PublishInternalSharingApk→com.github.triplet.gradle.play.tasks.internal.PublishTaskBasecom.github.triplet.gradle.play.tasks.PublishInternalSharingBundle→com.github.triplet.gradle.play.tasks.internal.ArtifactExtensionOptionscom.github.triplet.gradle.play.tasks.PublishInternalSharingBundle→com.github.triplet.gradle.play.tasks.internal.PublishTaskBasecom.github.triplet.gradle.play.tasks.PublishListings→com.github.triplet.gradle.play.tasks.internal.PublishTaskBasecom.github.triplet.gradle.play.tasks.PublishListings→com.github.triplet.gradle.play.tasks.internal.WriteTrackExtensionOptionscom.github.triplet.gradle.play.tasks.PublishProducts→com.github.triplet.gradle.play.tasks.internal.PublishTaskBasecom.github.triplet.gradle.play.tasks.PublishSubscriptions→com.github.triplet.gradle.play.tasks.internal.PublishTaskBase
- Direction
- play.tasks uses play.tasks.internal, so a change to play.tasks.internal can break play.tasks, while a change to play.tasks can't break play.tasks.internal.
- Position
- Below the diagonal: play.tasks uses a module listed above it, which is the healthy direction.
21→22 play.tasks uses play.internal part of a loop✕
- Connections
- 2 pairs of types, where a type in play.tasks uses a type in play.internal.
- The types involved
com.github.triplet.gradle.play.tasks.PublishApk→com.github.triplet.gradle.play.internal.ApkSpeccom.github.triplet.gradle.play.tasks.PublishInternalSharingApk→com.github.triplet.gradle.play.internal.ApkSpec
- Direction
- play.tasks uses play.internal, so a change to play.internal can break play.tasks, while a change to play.tasks can't break play.internal.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→1 play.internal uses androidpublisher✕
- Connections
- 2 pairs of types, where a type in play.internal uses a type in androidpublisher.
- The types involved
com.github.triplet.gradle.play.internal.PlayExtensionConfig→com.github.triplet.gradle.androidpublisher.ReleaseStatuscom.github.triplet.gradle.play.internal.PlayExtensionConfig→com.github.triplet.gradle.androidpublisher.ResolutionStrategy
- Direction
- play.internal uses androidpublisher, so a change to androidpublisher can break play.internal, while a change to play.internal can't break androidpublisher.
- Position
- Below the diagonal: play.internal uses a module listed above it, which is the healthy direction.
22→13 play.internal uses play✕
- Connections
- 4 pairs of types, where a type in play.internal uses a type in play.
- The types involved
com.github.triplet.gradle.play.internal.CliPlayPublisherExtension→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.internal.ExtensionMergeHolder→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.internal.ExtensionsKt→com.github.triplet.gradle.play.PlayPublisherExtensioncom.github.triplet.gradle.play.internal.PluginsKt→com.github.triplet.gradle.play.PlayPublisherExtension
- Direction
- play.internal uses play, so a change to play can break play.internal, while a change to play.internal can't break play.
- Position
- Below the diagonal: play.internal uses a module listed above it, which is the healthy direction.
22→19 play.internal uses play.tasks.internal✕
- Connections
- 1 pair of types, where a type in play.internal uses a type in play.tasks.internal.
- The types involved
com.github.triplet.gradle.play.internal.PluginsKt→com.github.triplet.gradle.play.tasks.internal.PlayApiService
- Direction
- play.internal uses play.tasks.internal, so a change to play.tasks.internal can break play.internal, while a change to play.internal can't break play.tasks.internal.
- Position
- Below the diagonal: play.internal uses a module listed above it, which is the healthy direction.
22→21 play.internal uses play.tasks✕
- Connections
- 1 pair of types, where a type in play.internal uses a type in play.tasks.
- The types involved
com.github.triplet.gradle.play.internal.PluginsKt→com.github.triplet.gradle.play.tasks.CommitEdit
- Direction
- play.internal uses play.tasks, so a change to play.tasks can break play.internal, while a change to play.internal can't break play.tasks.
- Position
- Below the diagonal: play.internal uses a module listed above it, which is the healthy direction.
23→22 play.internal.AppDetail uses play.internal✕
- Connections
- 4 pairs of types, where a type in play.internal.AppDetail uses a type in play.internal.
- The types involved
com.github.triplet.gradle.play.internal.AppDetail.CONTACT_EMAIL→com.github.triplet.gradle.play.internal.AppDetailcom.github.triplet.gradle.play.internal.AppDetail.CONTACT_PHONE→com.github.triplet.gradle.play.internal.AppDetailcom.github.triplet.gradle.play.internal.AppDetail.CONTACT_WEBSITE→com.github.triplet.gradle.play.internal.AppDetailcom.github.triplet.gradle.play.internal.AppDetail.DEFAULT_LANGUAGE→com.github.triplet.gradle.play.internal.AppDetail
- Direction
- play.internal.AppDetail uses play.internal, so a change to play.internal can break play.internal.AppDetail, while a change to play.internal.AppDetail can't break play.internal.
- Position
- Below the diagonal: play.internal.AppDetail uses a module listed above it, which is the healthy direction.
24→22 play.internal.ImageType uses play.internal✕
- Connections
- 8 pairs of types, where a type in play.internal.ImageType uses a type in play.internal.
- The types involved
com.github.triplet.gradle.play.internal.ImageType.FEATURE_GRAPHIC→com.github.triplet.gradle.play.internal.ImageTypecom.github.triplet.gradle.play.internal.ImageType.ICON→com.github.triplet.gradle.play.internal.ImageTypecom.github.triplet.gradle.play.internal.ImageType.PHONE_SCREENSHOTS→com.github.triplet.gradle.play.internal.ImageTypecom.github.triplet.gradle.play.internal.ImageType.SEVEN_INCH_SCREENSHOTS→com.github.triplet.gradle.play.internal.ImageTypecom.github.triplet.gradle.play.internal.ImageType.TEN_INCH_SCREENSHOTS→com.github.triplet.gradle.play.internal.ImageTypecom.github.triplet.gradle.play.internal.ImageType.TV_BANNER→com.github.triplet.gradle.play.internal.ImageTypecom.github.triplet.gradle.play.internal.ImageType.TV_SCREENSHOTS→com.github.triplet.gradle.play.internal.ImageTypecom.github.triplet.gradle.play.internal.ImageType.WEAR_SCREENSHOTS→com.github.triplet.gradle.play.internal.ImageType
- Direction
- play.internal.ImageType uses play.internal, so a change to play.internal can break play.internal.ImageType, while a change to play.internal.ImageType can't break play.internal.
- Position
- Below the diagonal: play.internal.ImageType uses a module listed above it, which is the healthy direction.
25→22 play.internal.ListingDetail uses play.internal✕
- Connections
- 4 pairs of types, where a type in play.internal.ListingDetail uses a type in play.internal.
- The types involved
com.github.triplet.gradle.play.internal.ListingDetail.FULL_DESCRIPTION→com.github.triplet.gradle.play.internal.ListingDetailcom.github.triplet.gradle.play.internal.ListingDetail.SHORT_DESCRIPTION→com.github.triplet.gradle.play.internal.ListingDetailcom.github.triplet.gradle.play.internal.ListingDetail.TITLE→com.github.triplet.gradle.play.internal.ListingDetailcom.github.triplet.gradle.play.internal.ListingDetail.VIDEO→com.github.triplet.gradle.play.internal.ListingDetail
- Direction
- play.internal.ListingDetail uses play.internal, so a change to play.internal can break play.internal.ListingDetail, while a change to play.internal.ListingDetail can't break play.internal.
- Position
- Below the diagonal: play.internal.ListingDetail uses a module listed above it, which is the healthy direction.
26→19 play.tasks.internal.workers.PlayWorkerBase uses play.tasks.internal✕
- Connections
- 1 pair of types, where a type in play.tasks.internal.workers.PlayWorkerBase uses a type in play.tasks.internal.
- The types involved
com.github.triplet.gradle.play.tasks.internal.workers.PlayWorkerBase.PlayPublishingParams→com.github.triplet.gradle.play.tasks.internal.PlayApiService
- Direction
- play.tasks.internal.workers.PlayWorkerBase uses play.tasks.internal, so a change to play.tasks.internal can break play.tasks.internal.workers.PlayWorkerBase, while a change to play.tasks.internal.workers.PlayWorkerBase can't break play.tasks.internal.
- Position
- Below the diagonal: play.tasks.internal.workers.PlayWorkerBase uses a module listed above it, which is the healthy direction.
26→22 play.tasks.internal.workers.PlayWorkerBase uses play.internal✕
- Connections
- 1 pair of types, where a type in play.tasks.internal.workers.PlayWorkerBase uses a type in play.internal.
- The types involved
com.github.triplet.gradle.play.tasks.internal.workers.PlayWorkerBase.PlayPublishingParams→com.github.triplet.gradle.play.internal.PlayExtensionConfig
- Direction
- play.tasks.internal.workers.PlayWorkerBase uses play.internal, so a change to play.internal can break play.tasks.internal.workers.PlayWorkerBase, while a change to play.tasks.internal.workers.PlayWorkerBase can't break play.internal.
- Position
- Below the diagonal: play.tasks.internal.workers.PlayWorkerBase uses a module listed above it, which is the healthy direction.
27→26 play.tasks.CommitEdit.Committer uses play.tasks.internal.workers.PlayWorkerBase✕
- Connections
- 1 pair of types, where a type in play.tasks.CommitEdit.Committer uses a type in play.tasks.internal.workers.PlayWorkerBase.
- The types involved
com.github.triplet.gradle.play.tasks.CommitEdit.Committer.Params→com.github.triplet.gradle.play.tasks.internal.workers.PlayWorkerBase.PlayPublishingParams
- Direction
- play.tasks.CommitEdit.Committer uses play.tasks.internal.workers.PlayWorkerBase, so a change to play.tasks.internal.workers.PlayWorkerBase can break play.tasks.CommitEdit.Committer, while a change to play.tasks.CommitEdit.Committer can't break play.tasks.internal.workers.PlayWorkerBase.
- Position
- Below the diagonal: play.tasks.CommitEdit.Committer uses a module listed above it, which is the healthy direction.
28→26 play.tasks.internal.workers.EditWorkerBase uses play.tasks.internal.workers.PlayWorkerBase✕
- Connections
- 1 pair of types, where a type in play.tasks.internal.workers.EditWorkerBase uses a type in play.tasks.internal.workers.PlayWorkerBase.
- The types involved
com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBase.EditPublishingParams→com.github.triplet.gradle.play.tasks.internal.workers.PlayWorkerBase.PlayPublishingParams
- Direction
- play.tasks.internal.workers.EditWorkerBase uses play.tasks.internal.workers.PlayWorkerBase, so a change to play.tasks.internal.workers.PlayWorkerBase can break play.tasks.internal.workers.EditWorkerBase, while a change to play.tasks.internal.workers.EditWorkerBase can't break play.tasks.internal.workers.PlayWorkerBase.
- Position
- Below the diagonal: play.tasks.internal.workers.EditWorkerBase uses a module listed above it, which is the healthy direction.
29→28 play.tasks.Bootstrap.DetailsDownloader uses play.tasks.internal.workers.EditWorkerBase✕
- Connections
- 1 pair of types, where a type in play.tasks.Bootstrap.DetailsDownloader uses a type in play.tasks.internal.workers.EditWorkerBase.
- The types involved
com.github.triplet.gradle.play.tasks.Bootstrap.DetailsDownloader.Params→com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBase.EditPublishingParams
- Direction
- play.tasks.Bootstrap.DetailsDownloader uses play.tasks.internal.workers.EditWorkerBase, so a change to play.tasks.internal.workers.EditWorkerBase can break play.tasks.Bootstrap.DetailsDownloader, while a change to play.tasks.Bootstrap.DetailsDownloader can't break play.tasks.internal.workers.EditWorkerBase.
- Position
- Below the diagonal: play.tasks.Bootstrap.DetailsDownloader uses a module listed above it, which is the healthy direction.
30→22 play.tasks.Bootstrap.ImageFetcher uses play.internal✕
- Connections
- 1 pair of types, where a type in play.tasks.Bootstrap.ImageFetcher uses a type in play.internal.
- The types involved
com.github.triplet.gradle.play.tasks.Bootstrap.ImageFetcher.Params→com.github.triplet.gradle.play.internal.ImageType
- Direction
- play.tasks.Bootstrap.ImageFetcher uses play.internal, so a change to play.internal can break play.tasks.Bootstrap.ImageFetcher, while a change to play.tasks.Bootstrap.ImageFetcher can't break play.internal.
- Position
- Below the diagonal: play.tasks.Bootstrap.ImageFetcher uses a module listed above it, which is the healthy direction.
30→28 play.tasks.Bootstrap.ImageFetcher uses play.tasks.internal.workers.EditWorkerBase✕
- Connections
- 1 pair of types, where a type in play.tasks.Bootstrap.ImageFetcher uses a type in play.tasks.internal.workers.EditWorkerBase.
- The types involved
com.github.triplet.gradle.play.tasks.Bootstrap.ImageFetcher.Params→com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBase.EditPublishingParams
- Direction
- play.tasks.Bootstrap.ImageFetcher uses play.tasks.internal.workers.EditWorkerBase, so a change to play.tasks.internal.workers.EditWorkerBase can break play.tasks.Bootstrap.ImageFetcher, while a change to play.tasks.Bootstrap.ImageFetcher can't break play.tasks.internal.workers.EditWorkerBase.
- Position
- Below the diagonal: play.tasks.Bootstrap.ImageFetcher uses a module listed above it, which is the healthy direction.
31→28 play.tasks.Bootstrap.ListingsDownloader uses play.tasks.internal.workers.EditWorkerBase✕
- Connections
- 1 pair of types, where a type in play.tasks.Bootstrap.ListingsDownloader uses a type in play.tasks.internal.workers.EditWorkerBase.
- The types involved
com.github.triplet.gradle.play.tasks.Bootstrap.ListingsDownloader.Params→com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBase.EditPublishingParams
- Direction
- play.tasks.Bootstrap.ListingsDownloader uses play.tasks.internal.workers.EditWorkerBase, so a change to play.tasks.internal.workers.EditWorkerBase can break play.tasks.Bootstrap.ListingsDownloader, while a change to play.tasks.Bootstrap.ListingsDownloader can't break play.tasks.internal.workers.EditWorkerBase.
- Position
- Below the diagonal: play.tasks.Bootstrap.ListingsDownloader uses a module listed above it, which is the healthy direction.
32→28 play.tasks.Bootstrap.ProductsDownloader uses play.tasks.internal.workers.EditWorkerBase✕
- Connections
- 1 pair of types, where a type in play.tasks.Bootstrap.ProductsDownloader uses a type in play.tasks.internal.workers.EditWorkerBase.
- The types involved
com.github.triplet.gradle.play.tasks.Bootstrap.ProductsDownloader.Params→com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBase.EditPublishingParams
- Direction
- play.tasks.Bootstrap.ProductsDownloader uses play.tasks.internal.workers.EditWorkerBase, so a change to play.tasks.internal.workers.EditWorkerBase can break play.tasks.Bootstrap.ProductsDownloader, while a change to play.tasks.Bootstrap.ProductsDownloader can't break play.tasks.internal.workers.EditWorkerBase.
- Position
- Below the diagonal: play.tasks.Bootstrap.ProductsDownloader uses a module listed above it, which is the healthy direction.
33→28 play.tasks.Bootstrap.ReleaseNotesDownloader uses play.tasks.internal.workers.EditWorkerBase✕
- Connections
- 1 pair of types, where a type in play.tasks.Bootstrap.ReleaseNotesDownloader uses a type in play.tasks.internal.workers.EditWorkerBase.
- The types involved
com.github.triplet.gradle.play.tasks.Bootstrap.ReleaseNotesDownloader.Params→com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBase.EditPublishingParams
- Direction
- play.tasks.Bootstrap.ReleaseNotesDownloader uses play.tasks.internal.workers.EditWorkerBase, so a change to play.tasks.internal.workers.EditWorkerBase can break play.tasks.Bootstrap.ReleaseNotesDownloader, while a change to play.tasks.Bootstrap.ReleaseNotesDownloader can't break play.tasks.internal.workers.EditWorkerBase.
- Position
- Below the diagonal: play.tasks.Bootstrap.ReleaseNotesDownloader uses a module listed above it, which is the healthy direction.
34→28 play.tasks.Bootstrap.SubscriptionsDownloader uses play.tasks.internal.workers.EditWorkerBase✕
- Connections
- 1 pair of types, where a type in play.tasks.Bootstrap.SubscriptionsDownloader uses a type in play.tasks.internal.workers.EditWorkerBase.
- The types involved
com.github.triplet.gradle.play.tasks.Bootstrap.SubscriptionsDownloader.Params→com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBase.EditPublishingParams
- Direction
- play.tasks.Bootstrap.SubscriptionsDownloader uses play.tasks.internal.workers.EditWorkerBase, so a change to play.tasks.internal.workers.EditWorkerBase can break play.tasks.Bootstrap.SubscriptionsDownloader, while a change to play.tasks.Bootstrap.SubscriptionsDownloader can't break play.tasks.internal.workers.EditWorkerBase.
- Position
- Below the diagonal: play.tasks.Bootstrap.SubscriptionsDownloader uses a module listed above it, which is the healthy direction.
35→22 play.tasks.PublishListings.MediaUploader uses play.internal✕
- Connections
- 1 pair of types, where a type in play.tasks.PublishListings.MediaUploader uses a type in play.internal.
- The types involved
com.github.triplet.gradle.play.tasks.PublishListings.MediaUploader.Params→com.github.triplet.gradle.play.internal.ImageType
- Direction
- play.tasks.PublishListings.MediaUploader uses play.internal, so a change to play.internal can break play.tasks.PublishListings.MediaUploader, while a change to play.tasks.PublishListings.MediaUploader can't break play.internal.
- Position
- Below the diagonal: play.tasks.PublishListings.MediaUploader uses a module listed above it, which is the healthy direction.
35→28 play.tasks.PublishListings.MediaUploader uses play.tasks.internal.workers.EditWorkerBase✕
- Connections
- 1 pair of types, where a type in play.tasks.PublishListings.MediaUploader uses a type in play.tasks.internal.workers.EditWorkerBase.
- The types involved
com.github.triplet.gradle.play.tasks.PublishListings.MediaUploader.Params→com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBase.EditPublishingParams
- Direction
- play.tasks.PublishListings.MediaUploader uses play.tasks.internal.workers.EditWorkerBase, so a change to play.tasks.internal.workers.EditWorkerBase can break play.tasks.PublishListings.MediaUploader, while a change to play.tasks.PublishListings.MediaUploader can't break play.tasks.internal.workers.EditWorkerBase.
- Position
- Below the diagonal: play.tasks.PublishListings.MediaUploader uses a module listed above it, which is the healthy direction.
36→22 play.tasks.PublishListings.Publisher uses play.internal✕
- Connections
- 1 pair of types, where a type in play.tasks.PublishListings.Publisher uses a type in play.internal.
- The types involved
com.github.triplet.gradle.play.tasks.PublishListings.Publisher.Media→com.github.triplet.gradle.play.internal.ImageType
- Direction
- play.tasks.PublishListings.Publisher uses play.internal, so a change to play.internal can break play.tasks.PublishListings.Publisher, while a change to play.tasks.PublishListings.Publisher can't break play.internal.
- Position
- Below the diagonal: play.tasks.PublishListings.Publisher uses a module listed above it, which is the healthy direction.
36→28 play.tasks.PublishListings.Publisher uses play.tasks.internal.workers.EditWorkerBase✕
- Connections
- 1 pair of types, where a type in play.tasks.PublishListings.Publisher uses a type in play.tasks.internal.workers.EditWorkerBase.
- The types involved
com.github.triplet.gradle.play.tasks.PublishListings.Publisher.Params→com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBase.EditPublishingParams
- Direction
- play.tasks.PublishListings.Publisher uses play.tasks.internal.workers.EditWorkerBase, so a change to play.tasks.internal.workers.EditWorkerBase can break play.tasks.PublishListings.Publisher, while a change to play.tasks.PublishListings.Publisher can't break play.tasks.internal.workers.EditWorkerBase.
- Position
- Below the diagonal: play.tasks.PublishListings.Publisher uses a module listed above it, which is the healthy direction.
37→28 play.tasks.internal.workers.PublishArtifactWorkerBase uses play.tasks.internal.workers.EditWorkerBase✕
- Connections
- 1 pair of types, where a type in play.tasks.internal.workers.PublishArtifactWorkerBase uses a type in play.tasks.internal.workers.EditWorkerBase.
- The types involved
com.github.triplet.gradle.play.tasks.internal.workers.PublishArtifactWorkerBase.ArtifactPublishingParams→com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBase.EditPublishingParams
- Direction
- play.tasks.internal.workers.PublishArtifactWorkerBase uses play.tasks.internal.workers.EditWorkerBase, so a change to play.tasks.internal.workers.EditWorkerBase can break play.tasks.internal.workers.PublishArtifactWorkerBase, while a change to play.tasks.internal.workers.PublishArtifactWorkerBase can't break play.tasks.internal.workers.EditWorkerBase.
- Position
- Below the diagonal: play.tasks.internal.workers.PublishArtifactWorkerBase uses a module listed above it, which is the healthy direction.
38→26 play.tasks.internal.workers uses play.tasks.internal.workers.PlayWorkerBase✕
- Connections
- 1 pair of types, where a type in play.tasks.internal.workers uses a type in play.tasks.internal.workers.PlayWorkerBase.
- The types involved
com.github.triplet.gradle.play.tasks.internal.workers.ParamsKt→com.github.triplet.gradle.play.tasks.internal.workers.PlayWorkerBase.PlayPublishingParams
- Direction
- play.tasks.internal.workers uses play.tasks.internal.workers.PlayWorkerBase, so a change to play.tasks.internal.workers.PlayWorkerBase can break play.tasks.internal.workers, while a change to play.tasks.internal.workers can't break play.tasks.internal.workers.PlayWorkerBase.
- Position
- Below the diagonal: play.tasks.internal.workers uses a module listed above it, which is the healthy direction.
38→28 play.tasks.internal.workers uses play.tasks.internal.workers.EditWorkerBase✕
- Connections
- 1 pair of types, where a type in play.tasks.internal.workers uses a type in play.tasks.internal.workers.EditWorkerBase.
- The types involved
com.github.triplet.gradle.play.tasks.internal.workers.ParamsKt→com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBase.EditPublishingParams
- Direction
- play.tasks.internal.workers uses play.tasks.internal.workers.EditWorkerBase, so a change to play.tasks.internal.workers.EditWorkerBase can break play.tasks.internal.workers, while a change to play.tasks.internal.workers can't break play.tasks.internal.workers.EditWorkerBase.
- Position
- Below the diagonal: play.tasks.internal.workers uses a module listed above it, which is the healthy direction.
38→37 play.tasks.internal.workers uses play.tasks.internal.workers.PublishArtifactWorkerBase✕
- Connections
- 1 pair of types, where a type in play.tasks.internal.workers uses a type in play.tasks.internal.workers.PublishArtifactWorkerBase.
- The types involved
com.github.triplet.gradle.play.tasks.internal.workers.ParamsKt→com.github.triplet.gradle.play.tasks.internal.workers.PublishArtifactWorkerBase.ArtifactPublishingParams
- Direction
- play.tasks.internal.workers uses play.tasks.internal.workers.PublishArtifactWorkerBase, so a change to play.tasks.internal.workers.PublishArtifactWorkerBase can break play.tasks.internal.workers, while a change to play.tasks.internal.workers can't break play.tasks.internal.workers.PublishArtifactWorkerBase.
- Position
- Below the diagonal: play.tasks.internal.workers uses a module listed above it, which is the healthy direction.
39→22 play.tasks.Bootstrap uses play.internal✕
- Connections
- 1 pair of types, where a type in play.tasks.Bootstrap uses a type in play.internal.
- The types involved
com.github.triplet.gradle.play.tasks.Bootstrap.DetailsDownloader→com.github.triplet.gradle.play.internal.AppDetail
- Direction
- play.tasks.Bootstrap uses play.internal, so a change to play.internal can break play.tasks.Bootstrap, while a change to play.tasks.Bootstrap can't break play.internal.
- Position
- Below the diagonal: play.tasks.Bootstrap uses a module listed above it, which is the healthy direction.
39→38 play.tasks.Bootstrap uses play.tasks.internal.workers✕
- Connections
- 6 pairs of types, where a type in play.tasks.Bootstrap uses a type in play.tasks.internal.workers.
- The types involved
com.github.triplet.gradle.play.tasks.Bootstrap.DetailsDownloader→com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBasecom.github.triplet.gradle.play.tasks.Bootstrap.ImageFetcher→com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBasecom.github.triplet.gradle.play.tasks.Bootstrap.ListingsDownloader→com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBasecom.github.triplet.gradle.play.tasks.Bootstrap.ProductsDownloader→com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBasecom.github.triplet.gradle.play.tasks.Bootstrap.ReleaseNotesDownloader→com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBasecom.github.triplet.gradle.play.tasks.Bootstrap.SubscriptionsDownloader→com.github.triplet.gradle.play.tasks.internal.workers.EditWorkerBase
- Direction
- play.tasks.Bootstrap uses play.tasks.internal.workers, so a change to play.tasks.internal.workers can break play.tasks.Bootstrap, while a change to play.tasks.Bootstrap can't break play.tasks.internal.workers.
- Position
- Below the diagonal: play.tasks.Bootstrap uses a module listed above it, which is the healthy direction.
40→38 play.tasks.CommitEdit uses play.tasks.internal.workers✕
- Connections
- 1 pair of types, where a type in play.tasks.CommitEdit uses a type in play.tasks.internal.workers.
- The types involved
com.github.triplet.gradle.play.tasks.CommitEdit.Committer→com.github.triplet.gradle.play.tasks.internal.workers.PlayWorkerBase
- Direction
- play.tasks.CommitEdit uses play.tasks.internal.workers, so a change to play.tasks.internal.workers can break play.tasks.CommitEdit, while a change to play.tasks.CommitEdit can't break play.tasks.internal.workers.
- Position
- Below the diagonal: play.tasks.CommitEdit 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 | 18 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
| A07:2025 — Authentication Failures | 6 | High / Critical |
Roadmap
Top priorities: Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED. | +19.9 pts | Low | REDACTED Scanning |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. | +8.3 pts | Low | ADR Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +7.2 pts | Medium | Architecture documentation |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +2.3 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.3 pts | Medium | Release Hygiene |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.0 pts | Low | Supply-chain Provenance & Signing |
| 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. | +1.9 pts | Medium | Documentation (README) |
| Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. | +0.7 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| play/plugin/src/main/kotlin/com/github/triplet/gradle/play/PlayPublisherPlugin.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishProducts.kt | 7.4 | Mixed | Code Duplication: Edited copy of a member (16 corresponding lines) |
| play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/DefaultPlayPublisher.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (18 corresponding lines) |
| play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/Extensions.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishBundle.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (8 corresponding lines) |
| play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/DefaultEditManager.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (5 corresponding lines) |
| play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishApk.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (20 lines × 2) |
| play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishInternalSharingApk.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| REDACTED | 9.0 | Near-clean | Static Analysis (SAST): Low: REDACTED |
| testapp/build.gradle.kts | 9.5 | Near-clean | ADR Quality: No ADRs found |
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.8, 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, 57 of 176 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.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not included — the Java/Kotlin suite (repository root, Gradle) did not finish re-running within its budget: the JVM suite did not finish re-running within its tier budget.
- 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.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's 7 Maven/Gradle manifest(s) were read and none of the dependency coordinates they declare carries a version resolvable from the manifest itself: every one is inherited from a parent POM, a <dependencyManagement> block, an imported BOM or a Gradle version reference the catalogue does not define. Licences are resolved from the POMs Maven Central publishes, which requires a version to ask about, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `common/validation/src/main/kotlin/com/github/triplet/gradle/common/validation/RuntimeValidator.kt`, `common/validation/src/main/kotlin/com/github/triplet/gradle/common/validation/Validation.kt`, `play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/Bootstrap.kt`, `play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/GenerateResources.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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (testapp). the Android app did not build — `./gradlew assembleDebug` exited 1: FAILURE: Build failed with an exception. * What went wrong: Could not determine the dependencies of task ':assembleDebug'. > Could not create task ':validateBuildReadiness'. > Included build 'grad…; runtime evidence skipped (launch chosen because testapp/build.gradle.kts applies the Android application plugin and testapp/gradlew builds it).
- 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.
- 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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's Java or Kotlin uses SLF4J, log4j 2 or kotlin-logging but logs through a logger the reading cannot trace to it — a field of a superclass outside the repository, or a logger read off another object — so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PlayPublisherPlugin.applyInternal at 24.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with PlayPublisherPlugin.applyInternal (cyclomatic 24). — Refactoring it lifts Cyclomatic Complexity from 9.4 to about 10.0/10.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was PlayPublisherPlugin.applyInternal at 33.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with PlayPublisherPlugin.applyInternal (cognitive 33). — Refactoring it lifts Cognitive Complexity from 9.1 to about 10.0/10.
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with PlayPublisherPlugin.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with PlayPublisherPlugin.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with PlayPublisherPlugin.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
3 duplicated block group(s) detected. 4.2 % of the production lines (214 of 5,037) are in a reported copy. A further 6 rows report 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 (16 corresponding lines) finding(s) in Code Duplication — start with PublishProducts.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (21 corresponding lines) finding(s) in Code Duplication — start with PublishProducts.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (18 corresponding lines) finding(s) in Code Duplication — start with DefaultPlayPublisher.kt. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
6 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 3 module(s) off the main sequence, with abstractness counted on 4 of the 6 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 9 classes have LCOM4 above 3.
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 156 artifact(s) resolved, 138 of them gradable against Maven Central, and 105 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 · REDACTED Scanning
3 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
No source file's living knowledge is concentrated in a single author. Counted over 29 of the 55 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
2 deducted task-comment markers across 5037 LoC (0.0/KLoC) → score 9.9. 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 2 TodoComment finding(s) in Explicit Debt — start with PlayPublisherPlugin.kt, Extensions.kt. — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 5 build units (Gradle) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
18 finding(s): 0 critical, 16 high, 0 medium, 2 low. 16 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `REDACTED` (line 7, line 10), `gradlew` (line 74, line 178), `testapp/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.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
- No action in Static Analysis (SAST) — all 16 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 (16 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
1 of 29 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishSubscriptions.kt. Counted over 29 of the 55 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: PlayPublisherPlugin.kt↔Plugins.kt 93%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with PlayPublisherPlugin.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 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 0 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
- 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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
- 1 public type in `com.github.triplet.gradle.androidpublisher.internal` is marked as implementation by its own namespace, folder or name: `AndroidPublisherKt` (play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/AndroidPublisher.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/AndroidPublisher.kt:1
- 1 public type in `com.github.triplet.gradle.androidpublisher.internal.DefaultEditManager` is marked as implementation by its own namespace, folder or name: `Factory` (play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/DefaultEditManager.kt:247, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/DefaultEditManager.kt:247
- 1 public type in `com.github.triplet.gradle.androidpublisher.internal.DefaultPlayPublisher` is marked as implementation by its own namespace, folder or name: `Factory` (play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/DefaultPlayPublisher.kt:308, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/DefaultPlayPublisher.kt:308
- 3 public types in `com.github.triplet.gradle.androidpublisher.internal.TrackManager` are marked as implementation by their own namespace, folder or name: `BaseConfig` (play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/TrackManager.kt:17, `internal`), `UpdateConfig` (play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/TrackManager.kt:26, `internal`), `PromoteConfig` (play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/TrackManager.kt:33, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/TrackManager.kt:17
- 5 public types in `com.github.triplet.gradle.play.internal` are marked as implementation by their own namespace, folder or name: `ConstantsKt` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/Constants.kt:1, `internal`), `ExtensionsKt` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/Extensions.kt:1, `internal`), `ListingModelsKt` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:1, `internal`), `PluginsKt` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/Plugins.kt:1, `internal`), `ValidationKt` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/Validation.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/Constants.kt:1
- 4 public types in `com.github.triplet.gradle.play.internal.ListingDetail` are marked as implementation by their own namespace, folder or name: `TITLE` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:11, `internal`), `SHORT_DESCRIPTION` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:12, `internal`), `FULL_DESCRIPTION` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:13, `internal`), `VIDEO` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:14, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:11
- 4 public types in `com.github.triplet.gradle.play.internal.AppDetail` are marked as implementation by their own namespace, folder or name: `CONTACT_EMAIL` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:18, `internal`), `CONTACT_PHONE` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:19, `internal`), `CONTACT_WEBSITE` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:20, `internal`), `DEFAULT_LANGUAGE` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:21, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:18
- 8 public types in `com.github.triplet.gradle.play.internal.ImageType` are marked as implementation by their own namespace, folder or name: `ICON` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:29, `internal`), `FEATURE_GRAPHIC` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:30, `internal`), `PHONE_SCREENSHOTS` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:32, `internal`), `SEVEN_INCH_SCREENSHOTS` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:33, `internal`), `TEN_INCH_SCREENSHOTS` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:34, `internal`), `TV_BANNER` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:35, `internal`), `TV_SCREENSHOTS` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:36, `internal`), `WEAR_SCREENSHOTS` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:37, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:29
- 1 public type in `com.github.triplet.gradle.play.tasks.internal.BootstrapOptions` is marked as implementation by its own namespace, folder or name: `Holder` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/internal/CliOptions.kt:261, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/internal/CliOptions.kt:261
- 1 public type in `com.github.triplet.gradle.play.tasks.internal.PlayApiService` is marked as implementation by its own namespace, folder or name: `Params` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/internal/PlayApiService.kt:170, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/internal/PlayApiService.kt:170
- 1 public type in `com.github.triplet.gradle.play.tasks.internal.workers` is marked as implementation by its own namespace, folder or name: `ParamsKt` (play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/internal/workers/Params.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/internal/workers/Params.kt:1
What to do
- Hide `com.github.triplet.gradle.androidpublisher.internal` (`AndroidPublisherKt`) (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.triplet.gradle.androidpublisher.internal.DefaultEditManager` (`Factory`) (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.triplet.gradle.androidpublisher.internal.DefaultPlayPublisher` (`Factory`) (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.triplet.gradle.androidpublisher.internal.TrackManager` (`BaseConfig`, `UpdateConfig`, `PromoteConfig`) (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.triplet.gradle.play.internal` (`ConstantsKt`, `ExtensionsKt`, `ListingModelsKt`, `PluginsKt`, `ValidationKt`) (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.triplet.gradle.play.internal.ListingDetail` (`TITLE`, `SHORT_DESCRIPTION`, `FULL_DESCRIPTION`, `VIDEO`) (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.triplet.gradle.play.internal.AppDetail` (`CONTACT_EMAIL`, `CONTACT_PHONE`, `CONTACT_WEBSITE`, `DEFAULT_LANGUAGE`) (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.triplet.gradle.play.internal.ImageType` (`ICON`, `FEATURE_GRAPHIC`, `PHONE_SCREENSHOTS`, `SEVEN_INCH_SCREENSHOTS`, `TEN_INCH_SCREENSHOTS`, `TV_BANNER`, `TV_SCREENSHOTS`, `WEAR_SCREENSHOTS`) (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.triplet.gradle.play.tasks.internal.BootstrapOptions` (`Holder`) (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.triplet.gradle.play.tasks.internal.PlayApiService` (`Params`) (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.triplet.gradle.play.tasks.internal.workers` (`ParamsKt`) (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 3 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:3
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
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
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 | 98% | Exemplary | Strongest area. |
| Maturity | 56% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 31% | Weak — gated by D13, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 76% | 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 — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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.
- 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 — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Android app did not build — `./gradlew assembleDebug` exited 1: FAILURE: Build failed with an exception. * What went wrong: Could not determine the dependencies of task ':assembleDebug'. > Could not create task ':validateBuildReadiness'. > Included build 'grad…; runtime evidence skipped (launch chosen because testapp/build.gradle.kts applies the Android application plugin and testapp/gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
- 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 — ~6534 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.
- D11 Test Reliability — Test reliability not included
- D14 License Compliance — JVM licences not graded — no declared coordinate carries a version the manifest itself resolves
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 2 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — 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
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- 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) — 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) — 4 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) — not scanned yet).
- 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 (16 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 2 current-state document(s) make no claim of a kind M4 checks. 7 claim(s) of kinds M4 does not check were not checked (path 6, environment variable 1); 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 (5 module(s), 46 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
- 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 — 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
- 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 — 21 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 23 finding(s)
- REDACTED
- REDACTED
- REDACTED
- TodoComment play/plugin/src/main/kotlin/com/github/triplet/gradle/play/PlayPublisherPlugin.kt:731
- TodoComment play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/Extensions.kt:108
- PlayPublisherPlugin.applyInternal (cyclomatic 24) play/plugin/src/main/kotlin/com/github/triplet/gradle/play/PlayPublisherPlugin.kt:96
- PlayPublisherPlugin.applyInternal (cognitive 33) play/plugin/src/main/kotlin/com/github/triplet/gradle/play/PlayPublisherPlugin.kt:96
- MethodTooLong: PlayPublisherPlugin.applyInternal play/plugin/src/main/kotlin/com/github/triplet/gradle/play/PlayPublisherPlugin.kt:96
- ClassTooLong: PlayPublisherPlugin play/plugin/src/main/kotlin/com/github/triplet/gradle/play/PlayPublisherPlugin.kt:68
- FileTooLong: play/PlayPublisherPlugin.kt play/plugin/src/main/kotlin/com/github/triplet/gradle/play/PlayPublisherPlugin.kt
- Change coupling: PlayPublisherPlugin.kt ↔ Plugins.kt play/plugin/src/main/kotlin/com/github/triplet/gradle/play/PlayPublisherPlugin.kt:1
- REDACTED
- REDACTED
- Edited copy of a member (16 corresponding lines) play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishProducts.kt:77
- Edited copy of a member (21 corresponding lines) play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishProducts.kt:54
- Edited copy of a member (18 corresponding lines) play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/DefaultPlayPublisher.kt:177
- Edited copy of a member (19 corresponding lines) play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/DefaultPlayPublisher.kt:207
- Edited copy of a member (8 corresponding lines) play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishBundle.kt:50
- Edited copy of a member (5 corresponding lines) play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/DefaultEditManager.kt:50
- Duplicated block (20 lines × 2) play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishApk.kt:92
- Duplicated block (7 lines × 2) play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishProducts.kt:78
- Duplicated block (10 lines × 2) play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishInternalSharingApk.kt:50
- Off the main sequence: .:play:play-publisher
Minor — 25 finding(s)
- Implementation type on the public API play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/AndroidPublisher.kt:1
- Implementation type on the public API play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/DefaultEditManager.kt:247
- Implementation type on the public API play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/DefaultPlayPublisher.kt:308
- Implementation type on the public API play/android-publisher/src/main/kotlin/com/github/triplet/gradle/androidpublisher/internal/TrackManager.kt:17
- Implementation type on the public API play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/Constants.kt:1
- Implementation type on the public API play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:11
- Implementation type on the public API play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:18
- Implementation type on the public API play/plugin/src/main/kotlin/com/github/triplet/gradle/play/internal/ListingModels.kt:29
- Implementation type on the public API play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/internal/CliOptions.kt:261
- Implementation type on the public API play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/internal/PlayApiService.kt:170
- Implementation type on the public API play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/internal/workers/Params.kt:1
- REDACTED
- REDACTED
- No ADRs found testapp/build.gradle.kts:47
- REDACTED
- Orphaned files with no living knowledge
- Orphaned file play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/PublishSubscriptions.kt:1
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:3
- No release approval gate
- No changelog
Minor — 107 finding(s)
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): org.jetbrains:annotations
- Outdated (compile): org.jetbrains.kotlin:kotlin-reflect
- Outdated (compile): com.squareup:javawriter
- Outdated (compile): org.ow2.asm:asm
- Outdated (compile): org.jetbrains.kotlin:kotlin-gradle-plugin-api
- Outdated (compile): org.jetbrains.kotlin:kotlin-gradle-plugins-bom
- Outdated (compile): org.jetbrains.kotlin:kotlin-gradle-plugin-annotations
- Outdated (compile): org.jetbrains.kotlin:kotlin-native-utils
- Outdated (compile): org.jetbrains.kotlin:kotlin-tooling-core
- Outdated (compile): org.jetbrains.kotlin:kotlin-util-io
- Outdated (compile): org.jetbrains.kotlin:kotlin-build-tools-api
- 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): org.jetbrains.kotlin:kotlin-scripting-compiler-embeddable
- Outdated (compile): org.jetbrains.kotlin:kotlin-scripting-common
- Outdated (compile): org.jetbrains.kotlin:kotlin-scripting-jvm
- Outdated (compile): org.jetbrains.kotlin:kotlin-script-runtime
- Outdated (compile): org.jetbrains.kotlin:kotlin-scripting-compiler-impl-embeddable
- Outdated (compile): org.bouncycastle:bcpkix-jdk18on
- Outdated (compile): org.bouncycastle:bcutil-jdk18on
- Outdated (compile): org.bouncycastle:bcprov-jdk18on
- Off the main sequence: .:common:utils
- Off the main sequence: .:common:validation
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-e33096bdc8ff4a59a4cdcea13705ce88/history.json --exit-code 0 --source . | 1 | 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-e33096bdc8ff4a59a4cdcea13705ce88/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 18 | 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) — 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 4 file(s) — `common/validation/src/main/kotlin/com/github/triplet/gradle/common/validation/RuntimeValidator.kt`, `common/validation/src/main/kotlin/com/github/triplet/gradle/common/validation/Validation.kt`, `play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/Bootstrap.kt`, `play/plugin/src/main/kotlin/com/github/triplet/gradle/play/tasks/GenerateResources.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) — not scanned yet). | 0 | — |