Executive summary
guardian/grid is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 43 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 35, is the weakest lens and counts most in the score. The best first steps are planning backups and recovery and adding tests for the code no test reaches, each worth about 4 points. Raising Production Readiness to 70 would lift the score to about 49.
Twenty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Sixteen known security holes in the packages the code depends on can be used by attackers, and seventeen form fields can't be read by a screen reader. Pinning each tool to an exact version, updating the vulnerable packages and labelling the form fields would close these risks. Limiting each secret to its own step would fix the six secrets exposed to more of the pipeline than needed, and the three unsafe settings in infrastructure or container files need changing to safe values. The ten controls that only work with a mouse need to work with the keyboard, or to become a real button.
The product code is 55,307 lines, about €61,000 to rebuild.
If Production Readiness rose from 35 to 70, the lowest score rated Strong, the score would rise from 43 to about 49.
New since the last survey: 77 findings
- Cyclomatic Complexity · (anonymous) (cyclomatic 100) kahuna/public/js/search/results.js
- Cyclomatic Complexity · (anonymous) (cyclomatic 38) kahuna/public/js/usage-rights/usage-rights-editor.js
- Cognitive Complexity · (anonymous) (cognitive 45) kahuna/public/js/usage-rights/usage-rights-editor.js
- God Classes · FileTooLong: model/UsageRights.scala common-lib/src/main/scala/com/gu/mediaservice/model/UsageRights.scala
- Code Duplication · Edited copy of a member (24 corresponding lines) thrall/app/lib/elasticsearch/ElasticSearch.scala
- Code Duplication · Edited copies of one member (4 members, 22+ corresponding lines) usage/app/controllers/UsageApi.scala
- Code Duplication · Edited copy of a member (17 corresponding lines) thrall/app/lib/elasticsearch/ElasticSearch.scala
- Code Duplication · Edited copy of a member (24 corresponding lines) thrall/app/lib/elasticsearch/ElasticSearch.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) media-api/app/lib/ImageResponse.scala
- Code Duplication · Edited copy of a member (16 corresponding lines) usage/app/model/UsageRecord.scala
- Code Duplication · Edited copy of a member (21 corresponding lines) usage/app/model/UsageGroup.scala
- Code Duplication · Edited copy of a member (13 corresponding lines) media-api/app/controllers/MediaApi.scala
- Code Duplication · Edited copy of a member (14 corresponding lines) media-api/app/controllers/UsageController.scala
- Code Duplication · Edited copies of one member (4 members, 17+ corresponding lines) thrall/app/lib/elasticsearch/ElasticSearch.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) leases/app/controllers/MediaLeaseController.scala
- Code Duplication · Edited copy of a member (14 corresponding lines) media-api/app/lib/ContentApi.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) common-lib/src/main/scala/com/gu/mediaservice/GridClient.scala
- Code Duplication · Edited copies of one member (7 members, 9+ corresponding lines) common-lib/src/main/scala/com/gu/mediaservice/GridClient.scala
- Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) common-lib/src/main/scala/com/gu/mediaservice/lib/argo/model/EmbeddedEntity.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) thrall/app/lib/elasticsearch/ElasticSearch.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) thrall/app/lib/kinesis/ThrallEventConsumer.scala
- Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) thrall/app/lib/elasticsearch/ElasticSearch.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) media-api/app/lib/ImageResponse.scala
- Code Duplication · Edited copy of a member (17 corresponding lines) common-lib/src/main/scala/com/gu/mediaservice/lib/imaging/VipsImageOperations.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) thrall/app/controllers/ReaperController.scala
- Code Duplication · Edited copy of a member (7 corresponding lines) thrall/app/lib/kinesis/MessageProcessor.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) metadata-editor/app/controllers/SyndicationController.scala
- Code Duplication · Edited copy of a member (15 corresponding lines) common-lib/src/main/scala/com/gu/mediaservice/lib/logging/Stopwatch.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) media-api/app/controllers/SuggestionController.scala
- Code Duplication · Edited copy of a member (19 corresponding lines) usage/app/lib/MediaUsageBuilder.scala
- Cohesion (LCOM4) · Low cohesion: VipsImageOperations (LCOM4 6) common-lib/src/main/scala/com/gu/mediaservice/lib/imaging/VipsImageOperations.scala
- Explicit Debt · TodoComment common-lib/src/main/scala/com/gu/mediaservice/lib/imaging/VipsImageOperations.scala
- Explicit Debt · TodoComment common-lib/src/main/scala/com/gu/mediaservice/lib/imaging/VipsImageOperations.scala
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) kahuna/public/js/upload/dnd-uploader.js
- Code Duplication · Duplicated block (12 lines × 2 locations) kahuna/public/js/services/api/loader.js
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 13, cognitive 11) kahuna/public/js/search/results.js
- Large Files · kahuna/public/js/search/results.js: 837 lines of code kahuna/public/js/search/results.js
- Large Files · e2e-tests/steps/rights-and-restrictions/right-and-restrictions.ts: 825 lines of code e2e-tests/steps/rights-and-restrictions/right-and-restrictions.ts
- Large Files · e2e-tests/setup/stack.ts: 811 lines of code e2e-tests/setup/stack.ts
- Dependency Hygiene · Unused dependency 'theseus-angular'
- Dependency Hygiene · Unused dependency 'uri-templates'
- Visual & motion safety · Low contrast colour pair in CSS (2.6:1) kahuna/public/stylesheets/main.css
- Visual & motion safety · Low contrast colour pair in CSS (2.6:1) kahuna/public/stylesheets/main.css
- Visual & motion safety · Low contrast colour pair in CSS (2.6:1) kahuna/public/stylesheets/main.css
- Visual & motion safety · Low contrast colour pair in CSS (4.0:1) kahuna/public/stylesheets/main.css
- Visual & motion safety · Low contrast colour pair in CSS (2.6:1) kahuna/public/stylesheets/main.css
- Visual & motion safety · Low contrast colour pair in CSS (2.6:1) kahuna/public/js/edits/list-editor.css
- Visual & motion safety · Low contrast colour pair in CSS (2.6:1) kahuna/public/js/edits/list-editor.css
- Visual & motion safety · Low contrast colour pair in CSS (2.6:1) kahuna/public/js/edits/list-editor.css
- Visual & motion safety · Low contrast colour pair in CSS (2.6:1) kahuna/public/js/edits/list-editor.css
- Visual & motion safety · Low contrast colour pair in CSS (3.5:1) kahuna/public/js/edits/list-editor.css
- Visual & motion safety · Low contrast colour pair in CSS (2.6:1) kahuna/public/js/components/gr-preset-labels/gr-preset-labels.css
- Visual & motion safety · Low contrast colour pair in CSS (2.6:1) kahuna/public/js/components/gr-preset-labels/gr-preset-labels.css
- Visual & motion safety · Low contrast colour pair in CSS (4.2:1) e2e-tests/feature-library/styles.css
Fixed since the last survey: 214 findings
- Cyclomatic Complexity · (anonymous) (cyclomatic 101) kahuna/public/js/search/results.js
- Cyclomatic Complexity · (anonymous) (cyclomatic 33) kahuna/public/js/usage-rights/usage-rights-editor.js
- Cyclomatic Complexity · (anonymous).link (cyclomatic 20) kahuna/public/js/components/gr-chips/gr-chip-input.js
- Cyclomatic Complexity · (anonymous) (cyclomatic 19) kahuna/public/js/components/gr-chips/gr-chips.js
- Cognitive Complexity · (anonymous) (cognitive 42) kahuna/public/js/usage-rights/usage-rights-editor.js
- Cognitive Complexity · (anonymous) (cognitive 19) kahuna/public/js/components/gr-chips/gr-chips.js
- Cognitive Complexity · (anonymous).link (cognitive 18) kahuna/public/js/components/gr-chips/gr-chip-input.js
- God Classes · ClassTooLong: ImageLoaderController image-loader/app/controllers/ImageLoaderController.scala
- Cohesion (LCOM4) · Low cohesion: ThrallController (LCOM4 7) thrall/app/controllers/ThrallController.scala
- Cohesion (LCOM4) · Low cohesion: MediaLeaseController (LCOM4 4) leases/app/controllers/MediaLeaseController.scala
- REDACTED Scanning · Leaked secret: hardcoded-credential REDACTED
- Churn × Complexity Hotspots · Hotspot: common-lib/src/main/scala/com/gu/mediaservice/model/UsageRights.scala common-lib/src/main/scala/com/gu/mediaservice/model/UsageRights.scala
- Explicit Debt · FixmeComment image-loader/app/controllers/ImageLoaderController.scala
- Explicit Debt · TodoComment cropper/app/controllers/CropperController.scala
- Secrets (history) · High secret: WD-SECRET-0005 dev-image-loader/src/main/scala/com/gu/mediaservice/Picdar.scala
- Secrets (history) · REDACTED: generic-api-key kahuna/public/jspm_packages/npm/rx@2.5.3/.coveralls.yml
- Static Analysis (SAST) · High: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) kahuna/public/js/upload/dnd-uploader.js
- Code Duplication · Duplicated block (7 lines × 2 locations) kahuna/public/js/edits/service.js
- Code Duplication · Duplicated block (7 lines × 3 locations) kahuna/public/js/image/controller.js
- Code Duplication · Duplicated block (7 lines × 2 locations) kahuna/public/js/services/image/usages.js
- Code Duplication · Duplicated block (6 lines × 2 locations) kahuna/public/js/components/gr-image-cost-message/gr-image-cost-message.js
- Code Duplication · Duplicated block (5 lines × 2 locations) kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 15, cognitive 13) kahuna/public/js/components/gr-chips/gr-chip-input.js
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 14, cognitive 12) kahuna/public/js/search/results.js
- Cyclomatic Complexity · Complex function handleKey (cyclomatic 12, cognitive 13) kahuna/public/js/components/gr-chips/gr-text-chip.js
- Large Files · kahuna/public/js/search/results.js: 841 lines of code kahuna/public/js/search/results.js
- Large Files · e2e-tests/setup/stack.ts: 766 lines of code e2e-tests/setup/stack.ts
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-chips/gr-chips.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-chips/gr-chip-input.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-usagerights-summary/gr-usagerights-summary.tsx
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-add-keyword/gr-add-keyword.js
- Test Coverage · No test reaches this file kahuna/public/js/takedown/takedown-page.tsx
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-sort-control/gr-extended-sort-control.tsx
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-cql-input/gr-cql-input.ts
- Test Coverage · No test reaches this file kahuna/public/js/takedown/index.ts
- Test Coverage · No test reaches this file kahuna/public/js/util/crop.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-chips/gr-text-chip.js
- Test Coverage · No test reaches this file kahuna/public/js/services/image/usages.js
- Test Coverage · No test reaches this file kahuna/public/js/util/constants/standThemeOverride.ts
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-photoshoot/gr-photoshoot.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-usagerights-summary/gr-usagerights-bbc.tsx
- Test Coverage · No test reaches this file kahuna/public/js/search/structured-query/structured-query.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-tab-swap/gr-tab-swap.tsx
- Test Coverage · No test reaches this file kahuna/public/js/services/image-accessor.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gu-date/gu-date.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-sort-control/gr-sort-control.tsx
- Test Coverage · No test reaches this file kahuna/public/js/services/telemetry.ts
- Test Coverage · No test reaches this file kahuna/public/js/takedown/takedown-step.tsx
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-my-uploads/gr-my-uploads.tsx
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-panels/gr-panels.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter-config.ts
- Test Coverage · No test reaches this file kahuna/public/js/services/image/downloads.js
- Test Coverage · No test reaches this file kahuna/public/js/errors/global.js
- Test Coverage · No test reaches this file kahuna/public/js/services/label.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-add-label/gr-add-label.js
- Test Coverage · No test reaches this file kahuna/public/js/util/async.js
- Test Coverage · No test reaches this file dev/script/generate-config/generate-config.js
- Test Coverage · No test reaches this file kahuna/public/js/upload/recent/recent-uploads.js
- Test Coverage · No test reaches this file kahuna/public/js/services/image-list.js
- Test Coverage · No test reaches this file kahuna/public/js/sentry/sentry.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-archiver-status/gr-archiver-status.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-chips/gr-filter-chooser-chip.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-panel-button/gr-panel-button.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-preset-labels/gr-preset-labels.js
- Test Coverage · No test reaches this file kahuna/public/js/directives/gr-image-fade-on-load.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-batch-export-original-images/gr-batch-export-original-images.js
- Test Coverage · No test reaches this file kahuna/public/js/services/api/edits-api.js
- Test Coverage · No test reaches this file kahuna/public/js/services/panel.js
- Test Coverage · No test reaches this file kahuna/public/js/upload/controller.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-info-panel/gr-info-panel.js
- Test Coverage · No test reaches this file scripts/sample-images/index.js
- Test Coverage · No test reaches this file kahuna/public/js/common/usageRightsUtils.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-chips/gr-filter-chip.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-delete-usages/gr-delete-usages.js
- Test Coverage · No test reaches this file kahuna/public/js/services/archive.js
- Test Coverage · No test reaches this file kahuna/public/js/services/photoshoot.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-image-usage-photosales/gr-image-usage-photosales.tsx
- Test Coverage · No test reaches this file kahuna/public/js/services/api/media-cropper.js
- Test Coverage · No test reaches this file kahuna/public/js/imgops/service.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-delete-crops/gr-delete-crops.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-delete-image/gr-delete-image.js
- Test Coverage · No test reaches this file kahuna/public/js/image/index.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-collection-overlay/gr-collection-overlay.js
- Test Coverage · No test reaches this file kahuna/public/js/components/gr-icon/gr-icon.js
Rebuild cost: about €61,000 · Estimate
| Cost to rebuild | €20,000 to €100,000, for 340 to 1,079 hours of work, about 0.4 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 43. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 55,307 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 com.gu.mediaservice.lib.argo.model | 2 com.gu.mediaservice.lib.dynamo | 3 com.gu.mediaservice.model.leases | 4 com.gu.mediaservice.syntax | 5 com.gu.typesafe.config | 6 image-embedder-lambda.src.embedder.imageResolver | 7 com.gu.mediaservice.lib.argo | 8 com.gu.mediaservice.lib.auth.Authentication | 9 com.gu.typesafe.config.parser | 10 com.gu.mediaservice.lib.auth | 11 com.gu.typesafe.config.impl | 12 com.gu.mediaservice.lib.logging | 13 com.gu.mediaservice.lib.json | 14 com.gu.mediaservice.lib.management | 15 com.gu.mediaservice.lib.metrics | 16 com.gu.mediaservice.model.usage | 17 com.gu.mediaservice.model | 18 com.gu.mediaservice.lib | 19 com.gu.mediaservice.lib.imaging.im4jwrapper | 20 com.gu.mediaservice.lib.metadata | 21 lib.usagerights | 22 com.gu.mediaservice.lib.aws | 23 lib.imaging | 24 lib.querysyntax | 25 model.upload | 26 com.gu.mediaservice.lib.config | 27 com.gu.mediaservice | 28 com.gu.mediaservice.lib.auth.provider | 29 com.gu.mediaservice.lib.cleanup | 30 com.gu.mediaservice.lib.elasticsearch | 31 com.gu.mediaservice.lib.imaging | 32 com.gu.mediaservice.lib.guardian.auth | 33 com.gu.mediaservice.lib.play | 34 lib.elasticsearch | 35 model | 36 auth | 37 lib | 38 (global) | 39 controllers | 40 lib.kinesis |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com.gu.mediaservice.lib.argo.model | ||||||||||||||||||||||||||||||||||||||||
| 2 com.gu.mediaservice.lib.dynamo | ||||||||||||||||||||||||||||||||||||||||
| 3 com.gu.mediaservice.model.leases | ||||||||||||||||||||||||||||||||||||||||
| 4 com.gu.mediaservice.syntax | ||||||||||||||||||||||||||||||||||||||||
| 5 com.gu.typesafe.config | ||||||||||||||||||||||||||||||||||||||||
| 6 image-embedder-lambda.src.embedder.imageResolver | ||||||||||||||||||||||||||||||||||||||||
| 7 com.gu.mediaservice.lib.argo | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 com.gu.mediaservice.lib.auth.Authentication | 4 | |||||||||||||||||||||||||||||||||||||||
| 9 com.gu.typesafe.config.parser | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 com.gu.mediaservice.lib.auth | 1 | 2 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 11 com.gu.typesafe.config.impl | 179 | 3 | ||||||||||||||||||||||||||||||||||||||
| 12 com.gu.mediaservice.lib.logging | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 com.gu.mediaservice.lib.json | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 com.gu.mediaservice.lib.management | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 com.gu.mediaservice.lib.metrics | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 com.gu.mediaservice.model.usage | 8 | 2 | ||||||||||||||||||||||||||||||||||||||
| 17 com.gu.mediaservice.model | 1 | 3 | 4 | 3 | 2 | |||||||||||||||||||||||||||||||||||
| 18 com.gu.mediaservice.lib | 6 | 8 | 6 | |||||||||||||||||||||||||||||||||||||
| 19 com.gu.mediaservice.lib.imaging.im4jwrapper | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 20 com.gu.mediaservice.lib.metadata | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 21 lib.usagerights | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 com.gu.mediaservice.lib.aws | 10 | 1 | 9 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 23 lib.imaging | 4 | 7 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 lib.querysyntax | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 model.upload | 3 | 6 | 2 | |||||||||||||||||||||||||||||||||||||
| 26 com.gu.mediaservice.lib.config | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 com.gu.mediaservice | 2 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 com.gu.mediaservice.lib.auth.provider | 1 | 7 | 3 | 4 | ||||||||||||||||||||||||||||||||||||
| 29 com.gu.mediaservice.lib.cleanup | 2 | 39 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 30 com.gu.mediaservice.lib.elasticsearch | 4 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 com.gu.mediaservice.lib.imaging | 5 | 12 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 com.gu.mediaservice.lib.guardian.auth | 1 | 3 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 33 com.gu.mediaservice.lib.play | 1 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 34 lib.elasticsearch | 3 | 1 | 2 | 5 | 1 | 1 | 7 | 6 | 7 | 5 | 7 | |||||||||||||||||||||||||||||
| 35 model | 1 | 1 | 1 | 9 | 25 | 8 | 10 | 2 | 6 | 2 | 2 | 4 | ||||||||||||||||||||||||||||
| 36 auth | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 lib | 3 | 6 | 4 | 2 | 1 | 4 | 26 | 6 | 10 | 52 | 2 | 2 | 8 | 1 | 9 | 1 | 1 | 1 | 1 | 13 | ||||||||||||||||||||
| 38 (global) | 1 | 1 | 1 | 1 | 10 | 1 | 3 | |||||||||||||||||||||||||||||||||
| 39 controllers | 3 | 1 | 5 | 15 | 4 | 6 | 6 | 3 | 1 | 6 | 1 | 1 | 1 | 1 | 4 | 1 | 2 | 6 | 13 | |||||||||||||||||||||
| 40 lib.kinesis | 1 | 5 | 1 | 24 | 1 | 1 | 1 |
7→1 com.gu.mediaservice.lib.argo uses com.gu.mediaservice.lib.argo.model✕
- Connections
- 3 pairs of types, where a type in com.gu.mediaservice.lib.argo uses a type in com.gu.mediaservice.lib.argo.model.
- The types involved
com.gu.mediaservice.lib.argo.ArgoHelpers→com.gu.mediaservice.lib.argo.model.Actioncom.gu.mediaservice.lib.argo.ArgoHelpers→com.gu.mediaservice.lib.argo.model.ExtraCountscom.gu.mediaservice.lib.argo.ArgoHelpers→com.gu.mediaservice.lib.argo.model.Link
- Direction
- com.gu.mediaservice.lib.argo uses com.gu.mediaservice.lib.argo.model, so a change to com.gu.mediaservice.lib.argo.model can break com.gu.mediaservice.lib.argo, while a change to com.gu.mediaservice.lib.argo can't break com.gu.mediaservice.lib.argo.model.
- Position
- Below the diagonal: com.gu.mediaservice.lib.argo uses a module listed above it, which is the healthy direction.
7→12 com.gu.mediaservice.lib.argo uses com.gu.mediaservice.lib.logging part of a loop✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.argo uses a type in com.gu.mediaservice.lib.logging.
- The types involved
com.gu.mediaservice.lib.argo.ArgoHelpers→com.gu.mediaservice.lib.logging.GridLogging
- Direction
- com.gu.mediaservice.lib.argo uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break com.gu.mediaservice.lib.argo, while a change to com.gu.mediaservice.lib.argo can't break com.gu.mediaservice.lib.logging.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→10 com.gu.mediaservice.lib.auth.Authentication uses com.gu.mediaservice.lib.auth part of a loop✕
- Connections
- 4 pairs of types, where a type in com.gu.mediaservice.lib.auth.Authentication uses a type in com.gu.mediaservice.lib.auth.
- The types involved
com.gu.mediaservice.lib.auth.Authentication.InnerServicePrincipal→com.gu.mediaservice.lib.auth.ApiAccessorcom.gu.mediaservice.lib.auth.Authentication.MachinePrincipal→com.gu.mediaservice.lib.auth.ApiAccessorcom.gu.mediaservice.lib.auth.Authentication.Principal→com.gu.mediaservice.lib.auth.ApiAccessorcom.gu.mediaservice.lib.auth.Authentication.UserPrincipal→com.gu.mediaservice.lib.auth.ApiAccessor
- Direction
- com.gu.mediaservice.lib.auth.Authentication uses com.gu.mediaservice.lib.auth, so a change to com.gu.mediaservice.lib.auth can break com.gu.mediaservice.lib.auth.Authentication, while a change to com.gu.mediaservice.lib.auth.Authentication can't break com.gu.mediaservice.lib.auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→5 com.gu.typesafe.config.parser uses com.gu.typesafe.config✕
- Connections
- 2 pairs of types, where a type in com.gu.typesafe.config.parser uses a type in com.gu.typesafe.config.
- The types involved
com.gu.typesafe.config.parser.ConfigDocument→com.gu.typesafe.config.ConfigValuecom.gu.typesafe.config.parser.ConfigDocumentFactory→com.gu.typesafe.config.ConfigParseOptions
- Direction
- com.gu.typesafe.config.parser uses com.gu.typesafe.config, so a change to com.gu.typesafe.config can break com.gu.typesafe.config.parser, while a change to com.gu.typesafe.config.parser can't break com.gu.typesafe.config.
- Position
- Below the diagonal: com.gu.typesafe.config.parser uses a module listed above it, which is the healthy direction.
10→1 com.gu.mediaservice.lib.auth uses com.gu.mediaservice.lib.argo.model✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.auth uses a type in com.gu.mediaservice.lib.argo.model.
- The types involved
com.gu.mediaservice.lib.auth.Authentication→com.gu.mediaservice.lib.argo.model.Link
- Direction
- com.gu.mediaservice.lib.auth uses com.gu.mediaservice.lib.argo.model, so a change to com.gu.mediaservice.lib.argo.model can break com.gu.mediaservice.lib.auth, while a change to com.gu.mediaservice.lib.auth can't break com.gu.mediaservice.lib.argo.model.
- Position
- Below the diagonal: com.gu.mediaservice.lib.auth uses a module listed above it, which is the healthy direction.
10→7 com.gu.mediaservice.lib.auth uses com.gu.mediaservice.lib.argo✕
- Connections
- 2 pairs of types, where a type in com.gu.mediaservice.lib.auth uses a type in com.gu.mediaservice.lib.argo.
- The types involved
com.gu.mediaservice.lib.auth.Authentication→com.gu.mediaservice.lib.argo.ArgoHelperscom.gu.mediaservice.lib.auth.Authorisation→com.gu.mediaservice.lib.argo.ArgoHelpers
- Direction
- com.gu.mediaservice.lib.auth uses com.gu.mediaservice.lib.argo, so a change to com.gu.mediaservice.lib.argo can break com.gu.mediaservice.lib.auth, while a change to com.gu.mediaservice.lib.auth can't break com.gu.mediaservice.lib.argo.
- Position
- Below the diagonal: com.gu.mediaservice.lib.auth uses a module listed above it, which is the healthy direction.
10→8 com.gu.mediaservice.lib.auth uses com.gu.mediaservice.lib.auth.Authentication✕
- Connections
- 3 pairs of types, where a type in com.gu.mediaservice.lib.auth uses a type in com.gu.mediaservice.lib.auth.Authentication.
- The types involved
com.gu.mediaservice.lib.auth.Authentication→com.gu.mediaservice.lib.auth.Authentication.Principalcom.gu.mediaservice.lib.auth.Authentication→com.gu.mediaservice.lib.auth.Authentication.UserPrincipalcom.gu.mediaservice.lib.auth.Authorisation→com.gu.mediaservice.lib.auth.Authentication.Principal
- Direction
- com.gu.mediaservice.lib.auth uses com.gu.mediaservice.lib.auth.Authentication, so a change to com.gu.mediaservice.lib.auth.Authentication can break com.gu.mediaservice.lib.auth, while a change to com.gu.mediaservice.lib.auth can't break com.gu.mediaservice.lib.auth.Authentication.
- Position
- Below the diagonal: com.gu.mediaservice.lib.auth uses a module listed above it, which is the healthy direction.
10→18 com.gu.mediaservice.lib.auth uses com.gu.mediaservice.lib part of a loop✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.auth uses a type in com.gu.mediaservice.lib.
- The types involved
com.gu.mediaservice.lib.auth.KeyStore→com.gu.mediaservice.lib.BaseStore
- Direction
- com.gu.mediaservice.lib.auth uses com.gu.mediaservice.lib, so a change to com.gu.mediaservice.lib can break com.gu.mediaservice.lib.auth, while a change to com.gu.mediaservice.lib.auth can't break com.gu.mediaservice.lib.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→26 com.gu.mediaservice.lib.auth uses com.gu.mediaservice.lib.config part of a loop✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.auth uses a type in com.gu.mediaservice.lib.config.
- The types involved
com.gu.mediaservice.lib.auth.BaseControllerWithLoginRedirects→com.gu.mediaservice.lib.config.Services
- Direction
- com.gu.mediaservice.lib.auth uses com.gu.mediaservice.lib.config, so a change to com.gu.mediaservice.lib.config can break com.gu.mediaservice.lib.auth, while a change to com.gu.mediaservice.lib.auth can't break com.gu.mediaservice.lib.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→5 com.gu.typesafe.config.impl uses com.gu.typesafe.config✕
- Connections
- 179 pairs of types, where a type in com.gu.typesafe.config.impl uses a type in com.gu.typesafe.config. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.gu.typesafe.config.impl.1→com.gu.typesafe.config.Configcom.gu.typesafe.config.impl.2→com.gu.typesafe.config.Configcom.gu.typesafe.config.impl.3→com.gu.typesafe.config.ConfigValuecom.gu.typesafe.config.impl.AbstractConfigObject→com.gu.typesafe.config.ConfigMergeablecom.gu.typesafe.config.impl.AbstractConfigObject→com.gu.typesafe.config.ConfigObjectcom.gu.typesafe.config.impl.AbstractConfigObject→com.gu.typesafe.config.ConfigOrigincom.gu.typesafe.config.impl.AbstractConfigObject→com.gu.typesafe.config.ConfigRenderOptionscom.gu.typesafe.config.impl.AbstractConfigObject→com.gu.typesafe.config.ConfigValuecom.gu.typesafe.config.impl.AbstractConfigObject→com.gu.typesafe.config.ConfigValueTypecom.gu.typesafe.config.impl.AbstractConfigValue→com.gu.typesafe.config.ConfigMergeablecom.gu.typesafe.config.impl.AbstractConfigValue→com.gu.typesafe.config.ConfigOrigincom.gu.typesafe.config.impl.AbstractConfigValue→com.gu.typesafe.config.ConfigRenderOptionscom.gu.typesafe.config.impl.AbstractConfigValue→com.gu.typesafe.config.ConfigValuecom.gu.typesafe.config.impl.ClasspathNameSource→com.gu.typesafe.config.ConfigParseOptionscom.gu.typesafe.config.impl.ClasspathNameSource→com.gu.typesafe.config.ConfigParseablecom.gu.typesafe.config.impl.ClasspathNameSourceWithClass→com.gu.typesafe.config.ConfigParseOptionscom.gu.typesafe.config.impl.ClasspathNameSourceWithClass→com.gu.typesafe.config.ConfigParseablecom.gu.typesafe.config.impl.Comment→com.gu.typesafe.config.ConfigOrigincom.gu.typesafe.config.impl.ConfigBeanImpl→com.gu.typesafe.config.Configcom.gu.typesafe.config.impl.ConfigBeanImpl→com.gu.typesafe.config.ConfigValueTypecom.gu.typesafe.config.impl.ConfigBoolean→com.gu.typesafe.config.ConfigOrigincom.gu.typesafe.config.impl.ConfigBoolean→com.gu.typesafe.config.ConfigValueTypecom.gu.typesafe.config.impl.ConfigConcatenation→com.gu.typesafe.config.ConfigOrigincom.gu.typesafe.config.impl.ConfigConcatenation→com.gu.typesafe.config.ConfigRenderOptionscom.gu.typesafe.config.impl.ConfigConcatenation→com.gu.typesafe.config.ConfigValueType
- Direction
- com.gu.typesafe.config.impl uses com.gu.typesafe.config, so a change to com.gu.typesafe.config can break com.gu.typesafe.config.impl, while a change to com.gu.typesafe.config.impl can't break com.gu.typesafe.config.
- Position
- Below the diagonal: com.gu.typesafe.config.impl uses a module listed above it, which is the healthy direction.
11→9 com.gu.typesafe.config.impl uses com.gu.typesafe.config.parser✕
- Connections
- 3 pairs of types, where a type in com.gu.typesafe.config.impl uses a type in com.gu.typesafe.config.parser.
- The types involved
com.gu.typesafe.config.impl.AbstractConfigNode→com.gu.typesafe.config.parser.ConfigNodecom.gu.typesafe.config.impl.Parseable→com.gu.typesafe.config.parser.ConfigDocumentcom.gu.typesafe.config.impl.SimpleConfigDocument→com.gu.typesafe.config.parser.ConfigDocument
- Direction
- com.gu.typesafe.config.impl uses com.gu.typesafe.config.parser, so a change to com.gu.typesafe.config.parser can break com.gu.typesafe.config.impl, while a change to com.gu.typesafe.config.impl can't break com.gu.typesafe.config.parser.
- Position
- Below the diagonal: com.gu.typesafe.config.impl uses a module listed above it, which is the healthy direction.
12→10 com.gu.mediaservice.lib.logging uses com.gu.mediaservice.lib.auth✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.logging uses a type in com.gu.mediaservice.lib.auth.
- The types involved
com.gu.mediaservice.lib.logging.GridLogging→com.gu.mediaservice.lib.auth.ApiAccessor
- Direction
- com.gu.mediaservice.lib.logging uses com.gu.mediaservice.lib.auth, so a change to com.gu.mediaservice.lib.auth can break com.gu.mediaservice.lib.logging, while a change to com.gu.mediaservice.lib.logging can't break com.gu.mediaservice.lib.auth.
- Position
- Below the diagonal: com.gu.mediaservice.lib.logging uses a module listed above it, which is the healthy direction.
12→18 com.gu.mediaservice.lib.logging uses com.gu.mediaservice.lib part of a loop✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.logging uses a type in com.gu.mediaservice.lib.
- The types involved
com.gu.mediaservice.lib.logging.GridLogging→com.gu.mediaservice.lib.ImageId
- Direction
- com.gu.mediaservice.lib.logging uses com.gu.mediaservice.lib, so a change to com.gu.mediaservice.lib can break com.gu.mediaservice.lib.logging, while a change to com.gu.mediaservice.lib.logging can't break com.gu.mediaservice.lib.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→26 com.gu.mediaservice.lib.logging uses com.gu.mediaservice.lib.config part of a loop✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.logging uses a type in com.gu.mediaservice.lib.config.
- The types involved
com.gu.mediaservice.lib.logging.LogConfig→com.gu.mediaservice.lib.config.CommonConfig
- Direction
- com.gu.mediaservice.lib.logging uses com.gu.mediaservice.lib.config, so a change to com.gu.mediaservice.lib.config can break com.gu.mediaservice.lib.logging, while a change to com.gu.mediaservice.lib.logging can't break com.gu.mediaservice.lib.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→12 com.gu.mediaservice.lib.json uses com.gu.mediaservice.lib.logging✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.json uses a type in com.gu.mediaservice.lib.logging.
- The types involved
com.gu.mediaservice.lib.json.JsonByteArrayUtil→com.gu.mediaservice.lib.logging.GridLogging
- Direction
- com.gu.mediaservice.lib.json uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break com.gu.mediaservice.lib.json, while a change to com.gu.mediaservice.lib.json can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: com.gu.mediaservice.lib.json uses a module listed above it, which is the healthy direction.
14→7 com.gu.mediaservice.lib.management uses com.gu.mediaservice.lib.argo✕
- Connections
- 2 pairs of types, where a type in com.gu.mediaservice.lib.management uses a type in com.gu.mediaservice.lib.argo.
- The types involved
com.gu.mediaservice.lib.management.InnerServiceStatusCheckController→com.gu.mediaservice.lib.argo.ArgoHelperscom.gu.mediaservice.lib.management.ManagementController→com.gu.mediaservice.lib.argo.ArgoHelpers
- Direction
- com.gu.mediaservice.lib.management uses com.gu.mediaservice.lib.argo, so a change to com.gu.mediaservice.lib.argo can break com.gu.mediaservice.lib.management, while a change to com.gu.mediaservice.lib.management can't break com.gu.mediaservice.lib.argo.
- Position
- Below the diagonal: com.gu.mediaservice.lib.management uses a module listed above it, which is the healthy direction.
14→12 com.gu.mediaservice.lib.management uses com.gu.mediaservice.lib.logging✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.management uses a type in com.gu.mediaservice.lib.logging.
- The types involved
com.gu.mediaservice.lib.management.ElasticSearchHealthCheck→com.gu.mediaservice.lib.logging.GridLogging
- Direction
- com.gu.mediaservice.lib.management uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break com.gu.mediaservice.lib.management, while a change to com.gu.mediaservice.lib.management can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: com.gu.mediaservice.lib.management uses a module listed above it, which is the healthy direction.
15→12 com.gu.mediaservice.lib.metrics uses com.gu.mediaservice.lib.logging✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.metrics uses a type in com.gu.mediaservice.lib.logging.
- The types involved
com.gu.mediaservice.lib.metrics.CloudWatchMetrics→com.gu.mediaservice.lib.logging.GridLogging
- Direction
- com.gu.mediaservice.lib.metrics uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break com.gu.mediaservice.lib.metrics, while a change to com.gu.mediaservice.lib.metrics can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: com.gu.mediaservice.lib.metrics uses a module listed above it, which is the healthy direction.
16→2 com.gu.mediaservice.model.usage uses com.gu.mediaservice.lib.dynamo✕
- Connections
- 8 pairs of types, where a type in com.gu.mediaservice.model.usage uses a type in com.gu.mediaservice.lib.dynamo.
- The types involved
com.gu.mediaservice.model.usage.ChildUsageMetadata→com.gu.mediaservice.lib.dynamo.DynamoElementcom.gu.mediaservice.model.usage.DigitalUsageMetadata→com.gu.mediaservice.lib.dynamo.DynamoElementcom.gu.mediaservice.model.usage.DownloadUsageMetadata→com.gu.mediaservice.lib.dynamo.DynamoElementcom.gu.mediaservice.model.usage.FrontUsageMetadata→com.gu.mediaservice.lib.dynamo.DynamoElementcom.gu.mediaservice.model.usage.PrintImageSize→com.gu.mediaservice.lib.dynamo.DynamoElementcom.gu.mediaservice.model.usage.PrintUsageMetadata→com.gu.mediaservice.lib.dynamo.DynamoElementcom.gu.mediaservice.model.usage.SyndicationUsageMetadata→com.gu.mediaservice.lib.dynamo.DynamoElementcom.gu.mediaservice.model.usage.UsageMetadata→com.gu.mediaservice.lib.dynamo.DynamoElement
- Direction
- com.gu.mediaservice.model.usage uses com.gu.mediaservice.lib.dynamo, so a change to com.gu.mediaservice.lib.dynamo can break com.gu.mediaservice.model.usage, while a change to com.gu.mediaservice.model.usage can't break com.gu.mediaservice.lib.dynamo.
- Position
- Below the diagonal: com.gu.mediaservice.model.usage uses a module listed above it, which is the healthy direction.
16→12 com.gu.mediaservice.model.usage uses com.gu.mediaservice.lib.logging✕
- Connections
- 2 pairs of types, where a type in com.gu.mediaservice.model.usage uses a type in com.gu.mediaservice.lib.logging.
- The types involved
com.gu.mediaservice.model.usage.MediaUsage→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.model.usage.MediaUsage→com.gu.mediaservice.lib.logging.LogMarker
- Direction
- com.gu.mediaservice.model.usage uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break com.gu.mediaservice.model.usage, while a change to com.gu.mediaservice.model.usage can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: com.gu.mediaservice.model.usage uses a module listed above it, which is the healthy direction.
17→1 com.gu.mediaservice.model uses com.gu.mediaservice.lib.argo.model✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.model uses a type in com.gu.mediaservice.lib.argo.model.
- The types involved
com.gu.mediaservice.model.EditsResponse→com.gu.mediaservice.lib.argo.model.EmbeddedEntity
- Direction
- com.gu.mediaservice.model uses com.gu.mediaservice.lib.argo.model, so a change to com.gu.mediaservice.lib.argo.model can break com.gu.mediaservice.model, while a change to com.gu.mediaservice.model can't break com.gu.mediaservice.lib.argo.model.
- Position
- Below the diagonal: com.gu.mediaservice.model uses a module listed above it, which is the healthy direction.
17→3 com.gu.mediaservice.model uses com.gu.mediaservice.model.leases✕
- Connections
- 3 pairs of types, where a type in com.gu.mediaservice.model uses a type in com.gu.mediaservice.model.leases.
- The types involved
com.gu.mediaservice.model.AddImageLeaseMessage→com.gu.mediaservice.model.leases.MediaLeasecom.gu.mediaservice.model.Image→com.gu.mediaservice.model.leases.LeasesByMediacom.gu.mediaservice.model.ReplaceImageLeasesMessage→com.gu.mediaservice.model.leases.MediaLease
- Direction
- com.gu.mediaservice.model uses com.gu.mediaservice.model.leases, so a change to com.gu.mediaservice.model.leases can break com.gu.mediaservice.model, while a change to com.gu.mediaservice.model can't break com.gu.mediaservice.model.leases.
- Position
- Below the diagonal: com.gu.mediaservice.model uses a module listed above it, which is the healthy direction.
17→12 com.gu.mediaservice.model uses com.gu.mediaservice.lib.logging✕
- Connections
- 4 pairs of types, where a type in com.gu.mediaservice.model uses a type in com.gu.mediaservice.lib.logging.
- The types involved
com.gu.mediaservice.model.FileMetadata→com.gu.mediaservice.lib.logging.LogMarkercom.gu.mediaservice.model.Image→com.gu.mediaservice.lib.logging.LogMarkercom.gu.mediaservice.model.ThrallMessage→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.model.ThrallMessage→com.gu.mediaservice.lib.logging.LogMarker
- Direction
- com.gu.mediaservice.model uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break com.gu.mediaservice.model, while a change to com.gu.mediaservice.model can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: com.gu.mediaservice.model uses a module listed above it, which is the healthy direction.
17→16 com.gu.mediaservice.model uses com.gu.mediaservice.model.usage✕
- Connections
- 3 pairs of types, where a type in com.gu.mediaservice.model uses a type in com.gu.mediaservice.model.usage.
- The types involved
com.gu.mediaservice.model.Image→com.gu.mediaservice.model.usage.Usagecom.gu.mediaservice.model.UpdateImageUsagesMessage→com.gu.mediaservice.model.usage.UsageNoticecom.gu.mediaservice.model.UpdateUsageStatusMessage→com.gu.mediaservice.model.usage.UsageNotice
- Direction
- com.gu.mediaservice.model uses com.gu.mediaservice.model.usage, so a change to com.gu.mediaservice.model.usage can break com.gu.mediaservice.model, while a change to com.gu.mediaservice.model can't break com.gu.mediaservice.model.usage.
- Position
- Below the diagonal: com.gu.mediaservice.model uses a module listed above it, which is the healthy direction.
17→26 com.gu.mediaservice.model uses com.gu.mediaservice.lib.config part of a loop✕
- Connections
- 2 pairs of types, where a type in com.gu.mediaservice.model uses a type in com.gu.mediaservice.lib.config.
- The types involved
com.gu.mediaservice.model.NoRights→com.gu.mediaservice.lib.config.CommonConfigcom.gu.mediaservice.model.UsageRightsSpec→com.gu.mediaservice.lib.config.CommonConfig
- Direction
- com.gu.mediaservice.model uses com.gu.mediaservice.lib.config, so a change to com.gu.mediaservice.lib.config can break com.gu.mediaservice.model, while a change to com.gu.mediaservice.model can't break com.gu.mediaservice.lib.config.
- 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.
18→12 com.gu.mediaservice.lib uses com.gu.mediaservice.lib.logging✕
- Connections
- 6 pairs of types, where a type in com.gu.mediaservice.lib uses a type in com.gu.mediaservice.lib.logging.
- The types involved
com.gu.mediaservice.lib.BaseStore→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.lib.ImageQuarantineOperations→com.gu.mediaservice.lib.logging.LogMarkercom.gu.mediaservice.lib.ImageStorage→com.gu.mediaservice.lib.logging.LogMarkercom.gu.mediaservice.lib.S3ImageStorage→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.lib.S3ImageStorage→com.gu.mediaservice.lib.logging.LogMarkercom.gu.mediaservice.lib.json→com.gu.mediaservice.lib.logging.GridLogging
- Direction
- com.gu.mediaservice.lib uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break com.gu.mediaservice.lib, while a change to com.gu.mediaservice.lib can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: com.gu.mediaservice.lib uses a module listed above it, which is the healthy direction.
18→17 com.gu.mediaservice.lib uses com.gu.mediaservice.model✕
- Connections
- 8 pairs of types, where a type in com.gu.mediaservice.lib uses a type in com.gu.mediaservice.model.
- The types involved
com.gu.mediaservice.lib.BrowserViewableImage→com.gu.mediaservice.model.MimeTypecom.gu.mediaservice.lib.ImageQuarantineOperations→com.gu.mediaservice.model.MimeTypecom.gu.mediaservice.lib.ImageStorage→com.gu.mediaservice.model.MimeTypecom.gu.mediaservice.lib.ImageWrapper→com.gu.mediaservice.model.MimeTypecom.gu.mediaservice.lib.S3ImageStorage→com.gu.mediaservice.model.MimeTypecom.gu.mediaservice.lib.StorableOptimisedImage→com.gu.mediaservice.model.MimeTypecom.gu.mediaservice.lib.StorableOriginalImage→com.gu.mediaservice.model.MimeTypecom.gu.mediaservice.lib.StorableThumbImage→com.gu.mediaservice.model.MimeType
- Direction
- com.gu.mediaservice.lib uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break com.gu.mediaservice.lib, while a change to com.gu.mediaservice.lib can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: com.gu.mediaservice.lib uses a module listed above it, which is the healthy direction.
18→22 com.gu.mediaservice.lib uses com.gu.mediaservice.lib.aws part of a loop✕
- Connections
- 6 pairs of types, where a type in com.gu.mediaservice.lib uses a type in com.gu.mediaservice.lib.aws.
- The types involved
com.gu.mediaservice.lib.ImageQuarantineOperations→com.gu.mediaservice.lib.aws.S3Objectcom.gu.mediaservice.lib.ImageStorage→com.gu.mediaservice.lib.aws.S3Objectcom.gu.mediaservice.lib.S3ImageStorage→com.gu.mediaservice.lib.aws.S3com.gu.mediaservice.lib.StorableImage→com.gu.mediaservice.lib.aws.S3Objectcom.gu.mediaservice.lib.StorableOptimisedImage→com.gu.mediaservice.lib.aws.S3Objectcom.gu.mediaservice.lib.StorableOriginalImage→com.gu.mediaservice.lib.aws.S3Object
- Direction
- com.gu.mediaservice.lib uses com.gu.mediaservice.lib.aws, so a change to com.gu.mediaservice.lib.aws can break com.gu.mediaservice.lib, while a change to com.gu.mediaservice.lib can't break com.gu.mediaservice.lib.aws.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→12 com.gu.mediaservice.lib.imaging.im4jwrapper uses com.gu.mediaservice.lib.logging✕
- Connections
- 2 pairs of types, where a type in com.gu.mediaservice.lib.imaging.im4jwrapper uses a type in com.gu.mediaservice.lib.logging.
- The types involved
com.gu.mediaservice.lib.imaging.im4jwrapper.ImageMagick→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.lib.imaging.im4jwrapper.ImageMagick→com.gu.mediaservice.lib.logging.LogMarker
- Direction
- com.gu.mediaservice.lib.imaging.im4jwrapper uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break com.gu.mediaservice.lib.imaging.im4jwrapper, while a change to com.gu.mediaservice.lib.imaging.im4jwrapper can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: com.gu.mediaservice.lib.imaging.im4jwrapper uses a module listed above it, which is the healthy direction.
19→17 com.gu.mediaservice.lib.imaging.im4jwrapper uses com.gu.mediaservice.model✕
- Connections
- 2 pairs of types, where a type in com.gu.mediaservice.lib.imaging.im4jwrapper uses a type in com.gu.mediaservice.model.
- The types involved
com.gu.mediaservice.lib.imaging.im4jwrapper.ImageMagick→com.gu.mediaservice.model.Boundscom.gu.mediaservice.lib.imaging.im4jwrapper.ImageMagick→com.gu.mediaservice.model.Dimensions
- Direction
- com.gu.mediaservice.lib.imaging.im4jwrapper uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break com.gu.mediaservice.lib.imaging.im4jwrapper, while a change to com.gu.mediaservice.lib.imaging.im4jwrapper can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: com.gu.mediaservice.lib.imaging.im4jwrapper uses a module listed above it, which is the healthy direction.
20→12 com.gu.mediaservice.lib.metadata uses com.gu.mediaservice.lib.logging✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.metadata uses a type in com.gu.mediaservice.lib.logging.
- The types involved
com.gu.mediaservice.lib.metadata.ImageMetadataConverter→com.gu.mediaservice.lib.logging.GridLogging
- Direction
- com.gu.mediaservice.lib.metadata uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break com.gu.mediaservice.lib.metadata, while a change to com.gu.mediaservice.lib.metadata can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: com.gu.mediaservice.lib.metadata uses a module listed above it, which is the healthy direction.
20→17 com.gu.mediaservice.lib.metadata uses com.gu.mediaservice.model✕
- Connections
- 6 pairs of types, where a type in com.gu.mediaservice.lib.metadata uses a type in com.gu.mediaservice.model.
- The types involved
com.gu.mediaservice.lib.metadata.FileMetadataHelper→com.gu.mediaservice.model.FileMetadatacom.gu.mediaservice.lib.metadata.ImageMetadataConverter→com.gu.mediaservice.model.FileMetadatacom.gu.mediaservice.lib.metadata.ImageMetadataConverter→com.gu.mediaservice.model.ImageMetadatacom.gu.mediaservice.lib.metadata.SoftDeletedMetadataTable→com.gu.mediaservice.model.ImageStatusRecordcom.gu.mediaservice.lib.metadata.UsageRightsMetadataMapper→com.gu.mediaservice.model.ImageMetadatacom.gu.mediaservice.lib.metadata.UsageRightsMetadataMapper→com.gu.mediaservice.model.UsageRights
- Direction
- com.gu.mediaservice.lib.metadata uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break com.gu.mediaservice.lib.metadata, while a change to com.gu.mediaservice.lib.metadata can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: com.gu.mediaservice.lib.metadata uses a module listed above it, which is the healthy direction.
21→17 lib.usagerights uses com.gu.mediaservice.model✕
- Connections
- 3 pairs of types, where a type in lib.usagerights uses a type in com.gu.mediaservice.model.
- The types involved
lib.usagerights.CostCalculator→com.gu.mediaservice.model.Agencylib.usagerights.CostCalculator→com.gu.mediaservice.model.Costlib.usagerights.CostCalculator→com.gu.mediaservice.model.UsageRights
- Direction
- lib.usagerights uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break lib.usagerights, while a change to lib.usagerights can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: lib.usagerights uses a module listed above it, which is the healthy direction.
21→37 lib.usagerights uses lib part of a loop✕
- Connections
- 1 pair of types, where a type in lib.usagerights uses a type in lib.
- The types involved
lib.usagerights.CostCalculator→lib.UsageQuota
- Direction
- lib.usagerights uses lib, so a change to lib can break lib.usagerights, while a change to lib.usagerights can't break lib.
- 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→12 com.gu.mediaservice.lib.aws uses com.gu.mediaservice.lib.logging✕
- Connections
- 10 pairs of types, where a type in com.gu.mediaservice.lib.aws uses a type in com.gu.mediaservice.lib.logging.
- The types involved
com.gu.mediaservice.lib.aws.AwsClientBuilderUtils→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.lib.aws.ContentDisposition→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.lib.aws.DynamoDB→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.lib.aws.Embedder→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.lib.aws.Embedder→com.gu.mediaservice.lib.logging.LogMarkercom.gu.mediaservice.lib.aws.Kinesis→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.lib.aws.S3→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.lib.aws.S3→com.gu.mediaservice.lib.logging.LogMarkercom.gu.mediaservice.lib.aws.SNS→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.lib.aws.UpdateMessage→com.gu.mediaservice.lib.logging.GridLogging
- Direction
- com.gu.mediaservice.lib.aws uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break com.gu.mediaservice.lib.aws, while a change to com.gu.mediaservice.lib.aws can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: com.gu.mediaservice.lib.aws uses a module listed above it, which is the healthy direction.
22→16 com.gu.mediaservice.lib.aws uses com.gu.mediaservice.model.usage✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.aws uses a type in com.gu.mediaservice.model.usage.
- The types involved
com.gu.mediaservice.lib.aws.UpdateMessage→com.gu.mediaservice.model.usage.UsageNotice
- Direction
- com.gu.mediaservice.lib.aws uses com.gu.mediaservice.model.usage, so a change to com.gu.mediaservice.model.usage can break com.gu.mediaservice.lib.aws, while a change to com.gu.mediaservice.lib.aws can't break com.gu.mediaservice.model.usage.
- Position
- Below the diagonal: com.gu.mediaservice.lib.aws uses a module listed above it, which is the healthy direction.
22→17 com.gu.mediaservice.lib.aws uses com.gu.mediaservice.model✕
- Connections
- 9 pairs of types, where a type in com.gu.mediaservice.lib.aws uses a type in com.gu.mediaservice.model.
- The types involved
com.gu.mediaservice.lib.aws.ContentDisposition→com.gu.mediaservice.model.Assetcom.gu.mediaservice.lib.aws.ContentDisposition→com.gu.mediaservice.model.Cropcom.gu.mediaservice.lib.aws.ContentDisposition→com.gu.mediaservice.model.Imagecom.gu.mediaservice.lib.aws.ContentDisposition→com.gu.mediaservice.model.ImageFileTypecom.gu.mediaservice.lib.aws.S3→com.gu.mediaservice.model.Imagecom.gu.mediaservice.lib.aws.S3→com.gu.mediaservice.model.ImageFileTypecom.gu.mediaservice.lib.aws.S3→com.gu.mediaservice.model.MimeTypecom.gu.mediaservice.lib.aws.S3ObjectMetadata→com.gu.mediaservice.model.MimeTypecom.gu.mediaservice.lib.aws.ThrallMessageSender→com.gu.mediaservice.model.ExternalThrallMessage
- Direction
- com.gu.mediaservice.lib.aws uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break com.gu.mediaservice.lib.aws, while a change to com.gu.mediaservice.lib.aws can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: com.gu.mediaservice.lib.aws uses a module listed above it, which is the healthy direction.
22→18 com.gu.mediaservice.lib.aws uses com.gu.mediaservice.lib✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.aws uses a type in com.gu.mediaservice.lib.
- The types involved
com.gu.mediaservice.lib.aws.SqsViaSnsMessageConsumer→com.gu.mediaservice.lib.ImageId
- Direction
- com.gu.mediaservice.lib.aws uses com.gu.mediaservice.lib, so a change to com.gu.mediaservice.lib can break com.gu.mediaservice.lib.aws, while a change to com.gu.mediaservice.lib.aws can't break com.gu.mediaservice.lib.
- Position
- Below the diagonal: com.gu.mediaservice.lib.aws uses a module listed above it, which is the healthy direction.
22→26 com.gu.mediaservice.lib.aws uses com.gu.mediaservice.lib.config part of a loop✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.aws uses a type in com.gu.mediaservice.lib.config.
- The types involved
com.gu.mediaservice.lib.aws.S3Ops→com.gu.mediaservice.lib.config.CommonConfig
- Direction
- com.gu.mediaservice.lib.aws uses com.gu.mediaservice.lib.config, so a change to com.gu.mediaservice.lib.config can break com.gu.mediaservice.lib.aws, while a change to com.gu.mediaservice.lib.aws can't break com.gu.mediaservice.lib.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→12 lib.imaging uses com.gu.mediaservice.lib.logging✕
- Connections
- 4 pairs of types, where a type in lib.imaging uses a type in com.gu.mediaservice.lib.logging.
- The types involved
lib.imaging.FileMetadataReader→com.gu.mediaservice.lib.logging.GridLogginglib.imaging.FileMetadataReader→com.gu.mediaservice.lib.logging.LogMarkerlib.imaging.MimeTypeDetection→com.gu.mediaservice.lib.logging.GridLogginglib.imaging.MimeTypeDetection→com.gu.mediaservice.lib.logging.LogMarker
- Direction
- lib.imaging uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break lib.imaging, while a change to lib.imaging can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: lib.imaging uses a module listed above it, which is the healthy direction.
23→17 lib.imaging uses com.gu.mediaservice.model✕
- Connections
- 7 pairs of types, where a type in lib.imaging uses a type in com.gu.mediaservice.model.
- The types involved
lib.imaging.C2paDetector→com.gu.mediaservice.model.MimeTypelib.imaging.FileMetadataReader→com.gu.mediaservice.model.Dimensionslib.imaging.FileMetadataReader→com.gu.mediaservice.model.FileMetadatalib.imaging.FileMetadataReader→com.gu.mediaservice.model.MimeTypelib.imaging.FileMetadataReader→com.gu.mediaservice.model.OrientationMetadatalib.imaging.MimeTypeDetection→com.gu.mediaservice.model.MimeTypelib.imaging.MimeTypeDetection→com.gu.mediaservice.model.UnsupportedMimeTypeException
- Direction
- lib.imaging uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break lib.imaging, while a change to lib.imaging can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: lib.imaging uses a module listed above it, which is the healthy direction.
23→18 lib.imaging uses com.gu.mediaservice.lib✕
- Connections
- 1 pair of types, where a type in lib.imaging uses a type in com.gu.mediaservice.lib.
- The types involved
lib.imaging.FileMetadataReader→com.gu.mediaservice.lib.ImageWrapper
- Direction
- lib.imaging uses com.gu.mediaservice.lib, so a change to com.gu.mediaservice.lib can break lib.imaging, while a change to lib.imaging can't break com.gu.mediaservice.lib.
- Position
- Below the diagonal: lib.imaging uses a module listed above it, which is the healthy direction.
24→17 lib.querysyntax uses com.gu.mediaservice.model✕
- Connections
- 1 pair of types, where a type in lib.querysyntax uses a type in com.gu.mediaservice.model.
- The types involved
lib.querysyntax.QuerySyntax→com.gu.mediaservice.model.MimeType
- Direction
- lib.querysyntax uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break lib.querysyntax, while a change to lib.querysyntax can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: lib.querysyntax uses a module listed above it, which is the healthy direction.
24→18 lib.querysyntax uses com.gu.mediaservice.lib✕
- Connections
- 1 pair of types, where a type in lib.querysyntax uses a type in com.gu.mediaservice.lib.
- The types involved
lib.querysyntax.QuerySyntax→com.gu.mediaservice.lib.ImageFields
- Direction
- lib.querysyntax uses com.gu.mediaservice.lib, so a change to com.gu.mediaservice.lib can break lib.querysyntax, while a change to lib.querysyntax can't break com.gu.mediaservice.lib.
- Position
- Below the diagonal: lib.querysyntax uses a module listed above it, which is the healthy direction.
25→12 model.upload uses com.gu.mediaservice.lib.logging✕
- Connections
- 3 pairs of types, where a type in model.upload uses a type in com.gu.mediaservice.lib.logging.
- The types involved
model.upload.OptimiseOps→com.gu.mediaservice.lib.logging.LogMarkermodel.upload.OptimiseWithPngQuant→com.gu.mediaservice.lib.logging.GridLoggingmodel.upload.OptimiseWithPngQuant→com.gu.mediaservice.lib.logging.LogMarker
- Direction
- model.upload uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break model.upload, while a change to model.upload can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: model.upload uses a module listed above it, which is the healthy direction.
25→17 model.upload uses com.gu.mediaservice.model✕
- Connections
- 6 pairs of types, where a type in model.upload uses a type in com.gu.mediaservice.model.
- The types involved
model.upload.OptimiseOps→com.gu.mediaservice.model.FileMetadatamodel.upload.OptimiseOps→com.gu.mediaservice.model.MimeTypemodel.upload.OptimiseWithPngQuant→com.gu.mediaservice.model.FileMetadatamodel.upload.OptimiseWithPngQuant→com.gu.mediaservice.model.MimeTypemodel.upload.UploadRequest→com.gu.mediaservice.model.MimeTypemodel.upload.UploadRequest→com.gu.mediaservice.model.UploadInfo
- Direction
- model.upload uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break model.upload, while a change to model.upload can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: model.upload uses a module listed above it, which is the healthy direction.
25→18 model.upload uses com.gu.mediaservice.lib✕
- Connections
- 2 pairs of types, where a type in model.upload uses a type in com.gu.mediaservice.lib.
- The types involved
model.upload.OptimiseOps→com.gu.mediaservice.lib.ImageWrappermodel.upload.OptimiseWithPngQuant→com.gu.mediaservice.lib.ImageWrapper
- Direction
- model.upload uses com.gu.mediaservice.lib, so a change to com.gu.mediaservice.lib can break model.upload, while a change to model.upload can't break com.gu.mediaservice.lib.
- Position
- Below the diagonal: model.upload uses a module listed above it, which is the healthy direction.
26→17 com.gu.mediaservice.lib.config uses com.gu.mediaservice.model✕
- Connections
- 2 pairs of types, where a type in com.gu.mediaservice.lib.config uses a type in com.gu.mediaservice.model.
- The types involved
com.gu.mediaservice.lib.config.CommonConfig→com.gu.mediaservice.model.UsageRightsSpeccom.gu.mediaservice.lib.config.UsageRightsConfigProvider→com.gu.mediaservice.model.Photographer
- Direction
- com.gu.mediaservice.lib.config uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break com.gu.mediaservice.lib.config, while a change to com.gu.mediaservice.lib.config can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: com.gu.mediaservice.lib.config uses a module listed above it, which is the healthy direction.
26→22 com.gu.mediaservice.lib.config uses com.gu.mediaservice.lib.aws✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.config uses a type in com.gu.mediaservice.lib.aws.
- The types involved
com.gu.mediaservice.lib.config.CommonConfig→com.gu.mediaservice.lib.aws.AwsClientBuilderUtils
- Direction
- com.gu.mediaservice.lib.config uses com.gu.mediaservice.lib.aws, so a change to com.gu.mediaservice.lib.aws can break com.gu.mediaservice.lib.config, while a change to com.gu.mediaservice.lib.config can't break com.gu.mediaservice.lib.aws.
- Position
- Below the diagonal: com.gu.mediaservice.lib.config uses a module listed above it, which is the healthy direction.
27→12 com.gu.mediaservice uses com.gu.mediaservice.lib.logging✕
- Connections
- 2 pairs of types, where a type in com.gu.mediaservice uses a type in com.gu.mediaservice.lib.logging.
- The types involved
com.gu.mediaservice.ImageDataMerger→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.ImageDataMerger→com.gu.mediaservice.lib.logging.LogMarker
- Direction
- com.gu.mediaservice uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break com.gu.mediaservice, while a change to com.gu.mediaservice can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: com.gu.mediaservice uses a module listed above it, which is the healthy direction.
27→15 com.gu.mediaservice uses com.gu.mediaservice.lib.metrics✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice uses a type in com.gu.mediaservice.lib.metrics.
- The types involved
com.gu.mediaservice.syntax→com.gu.mediaservice.lib.metrics.FutureSyntax
- Direction
- com.gu.mediaservice uses com.gu.mediaservice.lib.metrics, so a change to com.gu.mediaservice.lib.metrics can break com.gu.mediaservice, while a change to com.gu.mediaservice can't break com.gu.mediaservice.lib.metrics.
- Position
- Below the diagonal: com.gu.mediaservice uses a module listed above it, which is the healthy direction.
27→17 com.gu.mediaservice uses com.gu.mediaservice.model✕
- Connections
- 3 pairs of types, where a type in com.gu.mediaservice uses a type in com.gu.mediaservice.model.
- The types involved
com.gu.mediaservice.ImageDataMerger→com.gu.mediaservice.model.Editscom.gu.mediaservice.ImageDataMerger→com.gu.mediaservice.model.Imagecom.gu.mediaservice.ImageDataMerger→com.gu.mediaservice.model.ImageMetadata
- Direction
- com.gu.mediaservice uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break com.gu.mediaservice, while a change to com.gu.mediaservice can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: com.gu.mediaservice uses a module listed above it, which is the healthy direction.
27→26 com.gu.mediaservice uses com.gu.mediaservice.lib.config✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice uses a type in com.gu.mediaservice.lib.config.
- The types involved
com.gu.mediaservice.GridClient→com.gu.mediaservice.lib.config.Services
- Direction
- com.gu.mediaservice uses com.gu.mediaservice.lib.config, so a change to com.gu.mediaservice.lib.config can break com.gu.mediaservice, while a change to com.gu.mediaservice can't break com.gu.mediaservice.lib.config.
- Position
- Below the diagonal: com.gu.mediaservice uses a module listed above it, which is the healthy direction.
28→7 com.gu.mediaservice.lib.auth.provider uses com.gu.mediaservice.lib.argo✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.auth.provider uses a type in com.gu.mediaservice.lib.argo.
- The types involved
com.gu.mediaservice.lib.auth.provider.LocalAuthenticationProvider→com.gu.mediaservice.lib.argo.ArgoHelpers
- Direction
- com.gu.mediaservice.lib.auth.provider uses com.gu.mediaservice.lib.argo, so a change to com.gu.mediaservice.lib.argo can break com.gu.mediaservice.lib.auth.provider, while a change to com.gu.mediaservice.lib.auth.provider can't break com.gu.mediaservice.lib.argo.
- Position
- Below the diagonal: com.gu.mediaservice.lib.auth.provider uses a module listed above it, which is the healthy direction.
28→8 com.gu.mediaservice.lib.auth.provider uses com.gu.mediaservice.lib.auth.Authentication✕
- Connections
- 7 pairs of types, where a type in com.gu.mediaservice.lib.auth.provider uses a type in com.gu.mediaservice.lib.auth.Authentication.
- The types involved
com.gu.mediaservice.lib.auth.provider.Authenticated→com.gu.mediaservice.lib.auth.Authentication.Principalcom.gu.mediaservice.lib.auth.provider.AuthenticationProvider→com.gu.mediaservice.lib.auth.Authentication.Principalcom.gu.mediaservice.lib.auth.provider.AuthorisationProvider→com.gu.mediaservice.lib.auth.Authentication.Principalcom.gu.mediaservice.lib.auth.provider.Expired→com.gu.mediaservice.lib.auth.Authentication.UserPrincipalcom.gu.mediaservice.lib.auth.provider.GracePeriod→com.gu.mediaservice.lib.auth.Authentication.UserPrincipalcom.gu.mediaservice.lib.auth.provider.InnerServiceAuthenticationProvider→com.gu.mediaservice.lib.auth.Authentication.Principalcom.gu.mediaservice.lib.auth.provider.LocalAuthorisationProvider→com.gu.mediaservice.lib.auth.Authentication.Principal
- Direction
- com.gu.mediaservice.lib.auth.provider uses com.gu.mediaservice.lib.auth.Authentication, so a change to com.gu.mediaservice.lib.auth.Authentication can break com.gu.mediaservice.lib.auth.provider, while a change to com.gu.mediaservice.lib.auth.provider can't break com.gu.mediaservice.lib.auth.Authentication.
- Position
- Below the diagonal: com.gu.mediaservice.lib.auth.provider uses a module listed above it, which is the healthy direction.
28→10 com.gu.mediaservice.lib.auth.provider uses com.gu.mediaservice.lib.auth✕
- Connections
- 3 pairs of types, where a type in com.gu.mediaservice.lib.auth.provider uses a type in com.gu.mediaservice.lib.auth.
- The types involved
com.gu.mediaservice.lib.auth.provider.AuthenticationProviderResources→com.gu.mediaservice.lib.auth.Authorisationcom.gu.mediaservice.lib.auth.provider.AuthorisationProvider→com.gu.mediaservice.lib.auth.SimplePermissioncom.gu.mediaservice.lib.auth.provider.LocalAuthorisationProvider→com.gu.mediaservice.lib.auth.SimplePermission
- Direction
- com.gu.mediaservice.lib.auth.provider uses com.gu.mediaservice.lib.auth, so a change to com.gu.mediaservice.lib.auth can break com.gu.mediaservice.lib.auth.provider, while a change to com.gu.mediaservice.lib.auth.provider can't break com.gu.mediaservice.lib.auth.
- Position
- Below the diagonal: com.gu.mediaservice.lib.auth.provider uses a module listed above it, which is the healthy direction.
28→26 com.gu.mediaservice.lib.auth.provider uses com.gu.mediaservice.lib.config✕
- Connections
- 4 pairs of types, where a type in com.gu.mediaservice.lib.auth.provider uses a type in com.gu.mediaservice.lib.config.
- The types involved
com.gu.mediaservice.lib.auth.provider.AuthenticationProvider→com.gu.mediaservice.lib.config.Providercom.gu.mediaservice.lib.auth.provider.AuthenticationProviderResources→com.gu.mediaservice.lib.config.CommonConfigcom.gu.mediaservice.lib.auth.provider.AuthorisationProvider→com.gu.mediaservice.lib.config.Providercom.gu.mediaservice.lib.auth.provider.AuthorisationProviderResources→com.gu.mediaservice.lib.config.CommonConfig
- Direction
- com.gu.mediaservice.lib.auth.provider uses com.gu.mediaservice.lib.config, so a change to com.gu.mediaservice.lib.config can break com.gu.mediaservice.lib.auth.provider, while a change to com.gu.mediaservice.lib.auth.provider can't break com.gu.mediaservice.lib.config.
- Position
- Below the diagonal: com.gu.mediaservice.lib.auth.provider uses a module listed above it, which is the healthy direction.
29→12 com.gu.mediaservice.lib.cleanup uses com.gu.mediaservice.lib.logging✕
- Connections
- 2 pairs of types, where a type in com.gu.mediaservice.lib.cleanup uses a type in com.gu.mediaservice.lib.logging.
- The types involved
com.gu.mediaservice.lib.cleanup.CountryCode→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.lib.cleanup.InsertGuardianImageType→com.gu.mediaservice.lib.logging.GridLogging
- Direction
- com.gu.mediaservice.lib.cleanup uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break com.gu.mediaservice.lib.cleanup, while a change to com.gu.mediaservice.lib.cleanup can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: com.gu.mediaservice.lib.cleanup uses a module listed above it, which is the healthy direction.
29→17 com.gu.mediaservice.lib.cleanup uses com.gu.mediaservice.model✕
- Connections
- 39 pairs of types, where a type in com.gu.mediaservice.lib.cleanup uses a type in com.gu.mediaservice.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.gu.mediaservice.lib.cleanup.AapParser→com.gu.mediaservice.model.Imagecom.gu.mediaservice.lib.cleanup.ActionImagesParser→com.gu.mediaservice.model.Imagecom.gu.mediaservice.lib.cleanup.AlamyParser→com.gu.mediaservice.model.Imagecom.gu.mediaservice.lib.cleanup.ApParser→com.gu.mediaservice.model.Imagecom.gu.mediaservice.lib.cleanup.BylineCreditReorganise→com.gu.mediaservice.model.ImageMetadatacom.gu.mediaservice.lib.cleanup.CanonicalisingImageProcessor→com.gu.mediaservice.model.Imagecom.gu.mediaservice.lib.cleanup.CapitaliseByline→com.gu.mediaservice.model.ImageMetadatacom.gu.mediaservice.lib.cleanup.CapitaliseCity→com.gu.mediaservice.model.ImageMetadatacom.gu.mediaservice.lib.cleanup.CapitaliseCountry→com.gu.mediaservice.model.ImageMetadatacom.gu.mediaservice.lib.cleanup.CapitaliseState→com.gu.mediaservice.model.ImageMetadatacom.gu.mediaservice.lib.cleanup.CapitaliseSubLocation→com.gu.mediaservice.model.ImageMetadatacom.gu.mediaservice.lib.cleanup.CleanRubbishLocation→com.gu.mediaservice.model.ImageMetadatacom.gu.mediaservice.lib.cleanup.ComposeImageProcessors→com.gu.mediaservice.model.Imagecom.gu.mediaservice.lib.cleanup.CorbisParser→com.gu.mediaservice.model.Imagecom.gu.mediaservice.lib.cleanup.CountryCode→com.gu.mediaservice.model.FileMetadatacom.gu.mediaservice.lib.cleanup.CountryCode→com.gu.mediaservice.model.Imagecom.gu.mediaservice.lib.cleanup.CountryCode→com.gu.mediaservice.model.ImageMetadatacom.gu.mediaservice.lib.cleanup.DropRedundantTitle→com.gu.mediaservice.model.ImageMetadatacom.gu.mediaservice.lib.cleanup.EpaParser→com.gu.mediaservice.model.Imagecom.gu.mediaservice.lib.cleanup.ExtractGuardianCreditFromByline→com.gu.mediaservice.model.ImageMetadatacom.gu.mediaservice.lib.cleanup.GettyXmpParser→com.gu.mediaservice.model.Agencycom.gu.mediaservice.lib.cleanup.GettyXmpParser→com.gu.mediaservice.model.Imagecom.gu.mediaservice.lib.cleanup.GettyXmpParser→com.gu.mediaservice.model.ImageMetadatacom.gu.mediaservice.lib.cleanup.GuardianStyleByline→com.gu.mediaservice.model.ImageMetadatacom.gu.mediaservice.lib.cleanup.ImageProcessor→com.gu.mediaservice.model.Image
- Direction
- com.gu.mediaservice.lib.cleanup uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break com.gu.mediaservice.lib.cleanup, while a change to com.gu.mediaservice.lib.cleanup can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: com.gu.mediaservice.lib.cleanup uses a module listed above it, which is the healthy direction.
29→18 com.gu.mediaservice.lib.cleanup uses com.gu.mediaservice.lib✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.cleanup uses a type in com.gu.mediaservice.lib.
- The types involved
com.gu.mediaservice.lib.cleanup.GettyXmpParser→com.gu.mediaservice.lib.PartialDate
- Direction
- com.gu.mediaservice.lib.cleanup uses com.gu.mediaservice.lib, so a change to com.gu.mediaservice.lib can break com.gu.mediaservice.lib.cleanup, while a change to com.gu.mediaservice.lib.cleanup can't break com.gu.mediaservice.lib.
- Position
- Below the diagonal: com.gu.mediaservice.lib.cleanup uses a module listed above it, which is the healthy direction.
29→26 com.gu.mediaservice.lib.cleanup uses com.gu.mediaservice.lib.config✕
- Connections
- 3 pairs of types, where a type in com.gu.mediaservice.lib.cleanup uses a type in com.gu.mediaservice.lib.config.
- The types involved
com.gu.mediaservice.lib.cleanup.ImageProcessor→com.gu.mediaservice.lib.config.Providercom.gu.mediaservice.lib.cleanup.ImageProcessorResources→com.gu.mediaservice.lib.config.CommonConfigcom.gu.mediaservice.lib.cleanup.ReapableEligibiltyResources→com.gu.mediaservice.lib.config.CommonConfigWithElastic
- Direction
- com.gu.mediaservice.lib.cleanup uses com.gu.mediaservice.lib.config, so a change to com.gu.mediaservice.lib.config can break com.gu.mediaservice.lib.cleanup, while a change to com.gu.mediaservice.lib.cleanup can't break com.gu.mediaservice.lib.config.
- Position
- Below the diagonal: com.gu.mediaservice.lib.cleanup uses a module listed above it, which is the healthy direction.
30→12 com.gu.mediaservice.lib.elasticsearch uses com.gu.mediaservice.lib.logging✕
- Connections
- 4 pairs of types, where a type in com.gu.mediaservice.lib.elasticsearch uses a type in com.gu.mediaservice.lib.logging.
- The types involved
com.gu.mediaservice.lib.elasticsearch.ElasticSearchClient→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.lib.elasticsearch.ElasticSearchClient→com.gu.mediaservice.lib.logging.LogMarkercom.gu.mediaservice.lib.elasticsearch.ElasticSearchExecutions→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.lib.elasticsearch.ElasticSearchExecutions→com.gu.mediaservice.lib.logging.LogMarker
- Direction
- com.gu.mediaservice.lib.elasticsearch uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break com.gu.mediaservice.lib.elasticsearch, while a change to com.gu.mediaservice.lib.elasticsearch can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: com.gu.mediaservice.lib.elasticsearch uses a module listed above it, which is the healthy direction.
30→17 com.gu.mediaservice.lib.elasticsearch uses com.gu.mediaservice.model✕
- Connections
- 3 pairs of types, where a type in com.gu.mediaservice.lib.elasticsearch uses a type in com.gu.mediaservice.model.
- The types involved
com.gu.mediaservice.lib.elasticsearch.MappingTest→com.gu.mediaservice.model.Assetcom.gu.mediaservice.lib.elasticsearch.MappingTest→com.gu.mediaservice.model.Imagecom.gu.mediaservice.lib.elasticsearch.MappingTest→com.gu.mediaservice.model.ImageMetadata
- Direction
- com.gu.mediaservice.lib.elasticsearch uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break com.gu.mediaservice.lib.elasticsearch, while a change to com.gu.mediaservice.lib.elasticsearch can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: com.gu.mediaservice.lib.elasticsearch uses a module listed above it, which is the healthy direction.
30→18 com.gu.mediaservice.lib.elasticsearch uses com.gu.mediaservice.lib✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.elasticsearch uses a type in com.gu.mediaservice.lib.
- The types involved
com.gu.mediaservice.lib.elasticsearch.PersistedQueries→com.gu.mediaservice.lib.ImageFields
- Direction
- com.gu.mediaservice.lib.elasticsearch uses com.gu.mediaservice.lib, so a change to com.gu.mediaservice.lib can break com.gu.mediaservice.lib.elasticsearch, while a change to com.gu.mediaservice.lib.elasticsearch can't break com.gu.mediaservice.lib.
- Position
- Below the diagonal: com.gu.mediaservice.lib.elasticsearch uses a module listed above it, which is the healthy direction.
30→26 com.gu.mediaservice.lib.elasticsearch uses com.gu.mediaservice.lib.config✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.elasticsearch uses a type in com.gu.mediaservice.lib.config.
- The types involved
com.gu.mediaservice.lib.elasticsearch.ReapableEligibility→com.gu.mediaservice.lib.config.Provider
- Direction
- com.gu.mediaservice.lib.elasticsearch uses com.gu.mediaservice.lib.config, so a change to com.gu.mediaservice.lib.config can break com.gu.mediaservice.lib.elasticsearch, while a change to com.gu.mediaservice.lib.elasticsearch can't break com.gu.mediaservice.lib.config.
- Position
- Below the diagonal: com.gu.mediaservice.lib.elasticsearch uses a module listed above it, which is the healthy direction.
31→12 com.gu.mediaservice.lib.imaging uses com.gu.mediaservice.lib.logging✕
- Connections
- 5 pairs of types, where a type in com.gu.mediaservice.lib.imaging uses a type in com.gu.mediaservice.lib.logging.
- The types involved
com.gu.mediaservice.lib.imaging.ImageOperations→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.lib.imaging.MagickImageOperations→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.lib.imaging.MagickImageOperations→com.gu.mediaservice.lib.logging.LogMarkercom.gu.mediaservice.lib.imaging.VipsImageOperations→com.gu.mediaservice.lib.logging.GridLoggingcom.gu.mediaservice.lib.imaging.VipsImageOperations→com.gu.mediaservice.lib.logging.LogMarker
- Direction
- com.gu.mediaservice.lib.imaging uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break com.gu.mediaservice.lib.imaging, while a change to com.gu.mediaservice.lib.imaging can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: com.gu.mediaservice.lib.imaging uses a module listed above it, which is the healthy direction.
31→17 com.gu.mediaservice.lib.imaging uses com.gu.mediaservice.model✕
- Connections
- 12 pairs of types, where a type in com.gu.mediaservice.lib.imaging uses a type in com.gu.mediaservice.model.
- The types involved
com.gu.mediaservice.lib.imaging.ExportResult→com.gu.mediaservice.model.Assetcom.gu.mediaservice.lib.imaging.ImageOperations→com.gu.mediaservice.model.MimeTypecom.gu.mediaservice.lib.imaging.MagickImageOperations→com.gu.mediaservice.model.Boundscom.gu.mediaservice.lib.imaging.MagickImageOperations→com.gu.mediaservice.model.Dimensionscom.gu.mediaservice.lib.imaging.MagickImageOperations→com.gu.mediaservice.model.ImageMetadatacom.gu.mediaservice.lib.imaging.MagickImageOperations→com.gu.mediaservice.model.MimeTypecom.gu.mediaservice.lib.imaging.MagickImageOperations→com.gu.mediaservice.model.OrientationMetadatacom.gu.mediaservice.lib.imaging.VipsImageOperations→com.gu.mediaservice.model.Boundscom.gu.mediaservice.lib.imaging.VipsImageOperations→com.gu.mediaservice.model.Dimensionscom.gu.mediaservice.lib.imaging.VipsImageOperations→com.gu.mediaservice.model.ImageMetadatacom.gu.mediaservice.lib.imaging.VipsImageOperations→com.gu.mediaservice.model.MimeTypecom.gu.mediaservice.lib.imaging.VipsImageOperations→com.gu.mediaservice.model.OrientationMetadata
- Direction
- com.gu.mediaservice.lib.imaging uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break com.gu.mediaservice.lib.imaging, while a change to com.gu.mediaservice.lib.imaging can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: com.gu.mediaservice.lib.imaging uses a module listed above it, which is the healthy direction.
31→18 com.gu.mediaservice.lib.imaging uses com.gu.mediaservice.lib✕
- Connections
- 2 pairs of types, where a type in com.gu.mediaservice.lib.imaging uses a type in com.gu.mediaservice.lib.
- The types involved
com.gu.mediaservice.lib.imaging.MagickImageOperations→com.gu.mediaservice.lib.BrowserViewableImagecom.gu.mediaservice.lib.imaging.VipsImageOperations→com.gu.mediaservice.lib.BrowserViewableImage
- Direction
- com.gu.mediaservice.lib.imaging uses com.gu.mediaservice.lib, so a change to com.gu.mediaservice.lib can break com.gu.mediaservice.lib.imaging, while a change to com.gu.mediaservice.lib.imaging can't break com.gu.mediaservice.lib.
- Position
- Below the diagonal: com.gu.mediaservice.lib.imaging uses a module listed above it, which is the healthy direction.
31→26 com.gu.mediaservice.lib.imaging uses com.gu.mediaservice.lib.config✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.imaging uses a type in com.gu.mediaservice.lib.config.
- The types involved
com.gu.mediaservice.lib.imaging.ImageOperations→com.gu.mediaservice.lib.config.CommonConfig
- Direction
- com.gu.mediaservice.lib.imaging uses com.gu.mediaservice.lib.config, so a change to com.gu.mediaservice.lib.config can break com.gu.mediaservice.lib.imaging, while a change to com.gu.mediaservice.lib.imaging can't break com.gu.mediaservice.lib.config.
- Position
- Below the diagonal: com.gu.mediaservice.lib.imaging uses a module listed above it, which is the healthy direction.
32→7 com.gu.mediaservice.lib.guardian.auth uses com.gu.mediaservice.lib.argo✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.guardian.auth uses a type in com.gu.mediaservice.lib.argo.
- The types involved
com.gu.mediaservice.lib.guardian.auth.PandaAuthenticationProvider→com.gu.mediaservice.lib.argo.ArgoHelpers
- Direction
- com.gu.mediaservice.lib.guardian.auth uses com.gu.mediaservice.lib.argo, so a change to com.gu.mediaservice.lib.argo can break com.gu.mediaservice.lib.guardian.auth, while a change to com.gu.mediaservice.lib.guardian.auth can't break com.gu.mediaservice.lib.argo.
- Position
- Below the diagonal: com.gu.mediaservice.lib.guardian.auth uses a module listed above it, which is the healthy direction.
32→8 com.gu.mediaservice.lib.guardian.auth uses com.gu.mediaservice.lib.auth.Authentication✕
- Connections
- 3 pairs of types, where a type in com.gu.mediaservice.lib.guardian.auth uses a type in com.gu.mediaservice.lib.auth.Authentication.
- The types involved
com.gu.mediaservice.lib.guardian.auth.PandaAuthenticationProvider→com.gu.mediaservice.lib.auth.Authentication.Principalcom.gu.mediaservice.lib.guardian.auth.PandaAuthenticationProvider→com.gu.mediaservice.lib.auth.Authentication.UserPrincipalcom.gu.mediaservice.lib.guardian.auth.PermissionsAuthorisationProvider→com.gu.mediaservice.lib.auth.Authentication.Principal
- Direction
- com.gu.mediaservice.lib.guardian.auth uses com.gu.mediaservice.lib.auth.Authentication, so a change to com.gu.mediaservice.lib.auth.Authentication can break com.gu.mediaservice.lib.guardian.auth, while a change to com.gu.mediaservice.lib.guardian.auth can't break com.gu.mediaservice.lib.auth.Authentication.
- Position
- Below the diagonal: com.gu.mediaservice.lib.guardian.auth uses a module listed above it, which is the healthy direction.
32→10 com.gu.mediaservice.lib.guardian.auth uses com.gu.mediaservice.lib.auth✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.guardian.auth uses a type in com.gu.mediaservice.lib.auth.
- The types involved
com.gu.mediaservice.lib.guardian.auth.PermissionsAuthorisationProvider→com.gu.mediaservice.lib.auth.SimplePermission
- Direction
- com.gu.mediaservice.lib.guardian.auth uses com.gu.mediaservice.lib.auth, so a change to com.gu.mediaservice.lib.auth can break com.gu.mediaservice.lib.guardian.auth, while a change to com.gu.mediaservice.lib.guardian.auth can't break com.gu.mediaservice.lib.auth.
- Position
- Below the diagonal: com.gu.mediaservice.lib.guardian.auth uses a module listed above it, which is the healthy direction.
32→26 com.gu.mediaservice.lib.guardian.auth uses com.gu.mediaservice.lib.config✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.guardian.auth uses a type in com.gu.mediaservice.lib.config.
- The types involved
com.gu.mediaservice.lib.guardian.auth.PermissionsAuthorisationProvider→com.gu.mediaservice.lib.config.CommonConfig
- Direction
- com.gu.mediaservice.lib.guardian.auth uses com.gu.mediaservice.lib.config, so a change to com.gu.mediaservice.lib.config can break com.gu.mediaservice.lib.guardian.auth, while a change to com.gu.mediaservice.lib.guardian.auth can't break com.gu.mediaservice.lib.config.
- Position
- Below the diagonal: com.gu.mediaservice.lib.guardian.auth uses a module listed above it, which is the healthy direction.
32→28 com.gu.mediaservice.lib.guardian.auth uses com.gu.mediaservice.lib.auth.provider✕
- Connections
- 3 pairs of types, where a type in com.gu.mediaservice.lib.guardian.auth uses a type in com.gu.mediaservice.lib.auth.provider.
- The types involved
com.gu.mediaservice.lib.guardian.auth.PandaAuthenticationProvider→com.gu.mediaservice.lib.auth.provider.AuthenticationStatuscom.gu.mediaservice.lib.guardian.auth.PandaAuthenticationProvider→com.gu.mediaservice.lib.auth.provider.UserAuthenticationProvidercom.gu.mediaservice.lib.guardian.auth.PermissionsAuthorisationProvider→com.gu.mediaservice.lib.auth.provider.AuthorisationProvider
- Direction
- com.gu.mediaservice.lib.guardian.auth uses com.gu.mediaservice.lib.auth.provider, so a change to com.gu.mediaservice.lib.auth.provider can break com.gu.mediaservice.lib.guardian.auth, while a change to com.gu.mediaservice.lib.guardian.auth can't break com.gu.mediaservice.lib.auth.provider.
- Position
- Below the diagonal: com.gu.mediaservice.lib.guardian.auth uses a module listed above it, which is the healthy direction.
33→8 com.gu.mediaservice.lib.play uses com.gu.mediaservice.lib.auth.Authentication✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.play uses a type in com.gu.mediaservice.lib.auth.Authentication.
- The types involved
com.gu.mediaservice.lib.play.RequestLoggingFilter→com.gu.mediaservice.lib.auth.Authentication.Principal
- Direction
- com.gu.mediaservice.lib.play uses com.gu.mediaservice.lib.auth.Authentication, so a change to com.gu.mediaservice.lib.auth.Authentication can break com.gu.mediaservice.lib.play, while a change to com.gu.mediaservice.lib.play can't break com.gu.mediaservice.lib.auth.Authentication.
- Position
- Below the diagonal: com.gu.mediaservice.lib.play uses a module listed above it, which is the healthy direction.
33→12 com.gu.mediaservice.lib.play uses com.gu.mediaservice.lib.logging✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.play uses a type in com.gu.mediaservice.lib.logging.
- The types involved
com.gu.mediaservice.lib.play.UnknownMethodParsingErrorHandler→com.gu.mediaservice.lib.logging.GridLogging
- Direction
- com.gu.mediaservice.lib.play uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break com.gu.mediaservice.lib.play, while a change to com.gu.mediaservice.lib.play can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: com.gu.mediaservice.lib.play uses a module listed above it, which is the healthy direction.
33→14 com.gu.mediaservice.lib.play uses com.gu.mediaservice.lib.management✕
- Connections
- 1 pair of types, where a type in com.gu.mediaservice.lib.play uses a type in com.gu.mediaservice.lib.management.
- The types involved
com.gu.mediaservice.lib.play.GridComponents→com.gu.mediaservice.lib.management.BuildInfo
- Direction
- com.gu.mediaservice.lib.play uses com.gu.mediaservice.lib.management, so a change to com.gu.mediaservice.lib.management can break com.gu.mediaservice.lib.play, while a change to com.gu.mediaservice.lib.play can't break com.gu.mediaservice.lib.management.
- Position
- Below the diagonal: com.gu.mediaservice.lib.play uses a module listed above it, which is the healthy direction.
33→26 com.gu.mediaservice.lib.play uses com.gu.mediaservice.lib.config✕
- Connections
- 2 pairs of types, where a type in com.gu.mediaservice.lib.play uses a type in com.gu.mediaservice.lib.config.
- The types involved
com.gu.mediaservice.lib.play.GridComponents→com.gu.mediaservice.lib.config.GridConfigResourcescom.gu.mediaservice.lib.play.RequestMetricFilter→com.gu.mediaservice.lib.config.CommonConfig
- Direction
- com.gu.mediaservice.lib.play uses com.gu.mediaservice.lib.config, so a change to com.gu.mediaservice.lib.config can break com.gu.mediaservice.lib.play, while a change to com.gu.mediaservice.lib.play can't break com.gu.mediaservice.lib.config.
- Position
- Below the diagonal: com.gu.mediaservice.lib.play uses a module listed above it, which is the healthy direction.
33→28 com.gu.mediaservice.lib.play uses com.gu.mediaservice.lib.auth.provider✕
- Connections
- 2 pairs of types, where a type in com.gu.mediaservice.lib.play uses a type in com.gu.mediaservice.lib.auth.provider.
- The types involved
com.gu.mediaservice.lib.play.GridComponents→com.gu.mediaservice.lib.auth.provider.AuthenticationProviderscom.gu.mediaservice.lib.play.GridComponents→com.gu.mediaservice.lib.auth.provider.AuthorisationProvider
- Direction
- com.gu.mediaservice.lib.play uses com.gu.mediaservice.lib.auth.provider, so a change to com.gu.mediaservice.lib.auth.provider can break com.gu.mediaservice.lib.play, while a change to com.gu.mediaservice.lib.play can't break com.gu.mediaservice.lib.auth.provider.
- Position
- Below the diagonal: com.gu.mediaservice.lib.play uses a module listed above it, which is the healthy direction.
34→1 lib.elasticsearch uses com.gu.mediaservice.lib.argo.model✕
- Connections
- 3 pairs of types, where a type in lib.elasticsearch uses a type in com.gu.mediaservice.lib.argo.model.
- The types involved
lib.elasticsearch.ElasticSearch→com.gu.mediaservice.lib.argo.model.ExtraCountConfiglib.elasticsearch.ElasticSearch→com.gu.mediaservice.lib.argo.model.ExtraCountslib.elasticsearch.SearchResults→com.gu.mediaservice.lib.argo.model.ExtraCounts
- Direction
- lib.elasticsearch uses com.gu.mediaservice.lib.argo.model, so a change to com.gu.mediaservice.lib.argo.model can break lib.elasticsearch, while a change to lib.elasticsearch can't break com.gu.mediaservice.lib.argo.model.
- Position
- Below the diagonal: lib.elasticsearch uses a module listed above it, which is the healthy direction.
34→8 lib.elasticsearch uses com.gu.mediaservice.lib.auth.Authentication✕
- Connections
- 1 pair of types, where a type in lib.elasticsearch uses a type in com.gu.mediaservice.lib.auth.Authentication.
- The types involved
lib.elasticsearch.ElasticSearch→com.gu.mediaservice.lib.auth.Authentication.Principal
- Direction
- lib.elasticsearch uses com.gu.mediaservice.lib.auth.Authentication, so a change to com.gu.mediaservice.lib.auth.Authentication can break lib.elasticsearch, while a change to lib.elasticsearch can't break com.gu.mediaservice.lib.auth.Authentication.
- Position
- Below the diagonal: lib.elasticsearch uses a module listed above it, which is the healthy direction.
34→10 lib.elasticsearch uses com.gu.mediaservice.lib.auth✕
- Connections
- 2 pairs of types, where a type in lib.elasticsearch uses a type in com.gu.mediaservice.lib.auth.
- The types involved
lib.elasticsearch.SearchFilters→com.gu.mediaservice.lib.auth.Tierlib.elasticsearch.SearchParams→com.gu.mediaservice.lib.auth.Tier
- Direction
- lib.elasticsearch uses com.gu.mediaservice.lib.auth, so a change to com.gu.mediaservice.lib.auth can break lib.elasticsearch, while a change to lib.elasticsearch can't break com.gu.mediaservice.lib.auth.
- Position
- Below the diagonal: lib.elasticsearch uses a module listed above it, which is the healthy direction.
34→12 lib.elasticsearch uses com.gu.mediaservice.lib.logging✕
- Connections
- 5 pairs of types, where a type in lib.elasticsearch uses a type in com.gu.mediaservice.lib.logging.
- The types involved
lib.elasticsearch.ElasticSearch→com.gu.mediaservice.lib.logging.GridLogginglib.elasticsearch.ElasticSearch→com.gu.mediaservice.lib.logging.LogMarkerlib.elasticsearch.GoodToGoCheck→com.gu.mediaservice.lib.logging.LogMarkerlib.elasticsearch.QueryBuilder→com.gu.mediaservice.lib.logging.GridLogginglib.elasticsearch.ThrallMigrationClient→com.gu.mediaservice.lib.logging.LogMarker
- Direction
- lib.elasticsearch uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break lib.elasticsearch, while a change to lib.elasticsearch can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: lib.elasticsearch uses a module listed above it, which is the healthy direction.
34→15 lib.elasticsearch uses com.gu.mediaservice.lib.metrics✕
- Connections
- 1 pair of types, where a type in lib.elasticsearch uses a type in com.gu.mediaservice.lib.metrics.
- The types involved
lib.elasticsearch.ElasticSearch→com.gu.mediaservice.lib.metrics.FutureSyntax
- Direction
- lib.elasticsearch uses com.gu.mediaservice.lib.metrics, so a change to com.gu.mediaservice.lib.metrics can break lib.elasticsearch, while a change to lib.elasticsearch can't break com.gu.mediaservice.lib.metrics.
- Position
- Below the diagonal: lib.elasticsearch uses a module listed above it, which is the healthy direction.
34→16 lib.elasticsearch uses com.gu.mediaservice.model.usage✕
- Connections
- 1 pair of types, where a type in lib.elasticsearch uses a type in com.gu.mediaservice.model.usage.
- The types involved
lib.elasticsearch.SearchParams→com.gu.mediaservice.model.usage.UsageStatus
- Direction
- lib.elasticsearch uses com.gu.mediaservice.model.usage, so a change to com.gu.mediaservice.model.usage can break lib.elasticsearch, while a change to lib.elasticsearch can't break com.gu.mediaservice.model.usage.
- Position
- Below the diagonal: lib.elasticsearch uses a module listed above it, which is the healthy direction.
34→17 lib.elasticsearch uses com.gu.mediaservice.model✕
- Connections
- 7 pairs of types, where a type in lib.elasticsearch uses a type in com.gu.mediaservice.model.
- The types involved
lib.elasticsearch.ElasticSearch→com.gu.mediaservice.model.Imagelib.elasticsearch.HybridResult→com.gu.mediaservice.model.Imagelib.elasticsearch.IsUnderQuota→com.gu.mediaservice.model.Agencylib.elasticsearch.SearchFilters→com.gu.mediaservice.model.PrintUsageFilterslib.elasticsearch.SearchParams→com.gu.mediaservice.model.PrintUsageFilterslib.elasticsearch.SearchParams→com.gu.mediaservice.model.SyndicationStatuslib.elasticsearch.SyndicationFilter→com.gu.mediaservice.model.SyndicationStatus
- Direction
- lib.elasticsearch uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break lib.elasticsearch, while a change to lib.elasticsearch can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: lib.elasticsearch uses a module listed above it, which is the healthy direction.
34→18 lib.elasticsearch uses com.gu.mediaservice.lib✕
- Connections
- 6 pairs of types, where a type in lib.elasticsearch uses a type in com.gu.mediaservice.lib.
- The types involved
lib.elasticsearch.ElasticSearch→com.gu.mediaservice.lib.ImageFieldslib.elasticsearch.IsQueryFilter→com.gu.mediaservice.lib.ImageFieldslib.elasticsearch.MatchFields→com.gu.mediaservice.lib.ImageFieldslib.elasticsearch.QueryBuilder→com.gu.mediaservice.lib.ImageFieldslib.elasticsearch.SearchFilters→com.gu.mediaservice.lib.ImageFieldslib.elasticsearch.SyndicationFilter→com.gu.mediaservice.lib.ImageFields
- Direction
- lib.elasticsearch uses com.gu.mediaservice.lib, so a change to com.gu.mediaservice.lib can break lib.elasticsearch, while a change to lib.elasticsearch can't break com.gu.mediaservice.lib.
- Position
- Below the diagonal: lib.elasticsearch uses a module listed above it, which is the healthy direction.
34→24 lib.elasticsearch uses lib.querysyntax✕
- Connections
- 7 pairs of types, where a type in lib.elasticsearch uses a type in lib.querysyntax.
- The types involved
lib.elasticsearch.AggregateSearchParams→lib.querysyntax.Conditionlib.elasticsearch.AiQueryParts→lib.querysyntax.Conditionlib.elasticsearch.ElasticSearch→lib.querysyntax.Conditionlib.elasticsearch.QueryBuilder→lib.querysyntax.Conditionlib.elasticsearch.QueryBuilder→lib.querysyntax.Matchlib.elasticsearch.QueryBuilder→lib.querysyntax.Valuelib.elasticsearch.SearchParams→lib.querysyntax.Condition
- Direction
- lib.elasticsearch uses lib.querysyntax, so a change to lib.querysyntax can break lib.elasticsearch, while a change to lib.elasticsearch can't break lib.querysyntax.
- Position
- Below the diagonal: lib.elasticsearch uses a module listed above it, which is the healthy direction.
34→30 lib.elasticsearch uses com.gu.mediaservice.lib.elasticsearch✕
- Connections
- 5 pairs of types, where a type in lib.elasticsearch uses a type in com.gu.mediaservice.lib.elasticsearch.
- The types involved
lib.elasticsearch.ElasticSearch→com.gu.mediaservice.lib.elasticsearch.ElasticSearchClientlib.elasticsearch.ElasticSearch→com.gu.mediaservice.lib.elasticsearch.MigrationStatusProviderlib.elasticsearch.IsReapable→com.gu.mediaservice.lib.elasticsearch.ReapableEligibilitylib.elasticsearch.ThrallMigrationClient→com.gu.mediaservice.lib.elasticsearch.MigrationStatuslib.elasticsearch.ThrallMigrationClient→com.gu.mediaservice.lib.elasticsearch.MigrationStatusProvider
- Direction
- lib.elasticsearch uses com.gu.mediaservice.lib.elasticsearch, so a change to com.gu.mediaservice.lib.elasticsearch can break lib.elasticsearch, while a change to lib.elasticsearch can't break com.gu.mediaservice.lib.elasticsearch.
- Position
- Below the diagonal: lib.elasticsearch uses a module listed above it, which is the healthy direction.
34→37 lib.elasticsearch uses lib part of a loop✕
- Connections
- 7 pairs of types, where a type in lib.elasticsearch uses a type in lib.
- The types involved
lib.elasticsearch.ElasticSearch→lib.ImageUsagesBySupplierResultlib.elasticsearch.ElasticSearch→lib.MediaApiConfiglib.elasticsearch.ElasticSearch→lib.SupplierQuotaCountlib.elasticsearch.MatchFields→lib.MediaApiConfiglib.elasticsearch.SearchFilters→lib.PersistenceReasonlib.elasticsearch.ThrallMigrationClient→lib.FailedMigrationSummarylib.elasticsearch.ThrallMigrationClient→lib.FailedMigrationsOverview
- Direction
- lib.elasticsearch uses lib, so a change to lib can break lib.elasticsearch, while a change to lib.elasticsearch can't break lib.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→2 model uses com.gu.mediaservice.lib.dynamo✕
- Connections
- 1 pair of types, where a type in model uses a type in com.gu.mediaservice.lib.dynamo.
- The types involved
model.UsageRecord→com.gu.mediaservice.lib.dynamo.DynamoElement
- Direction
- model uses com.gu.mediaservice.lib.dynamo, so a change to com.gu.mediaservice.lib.dynamo can break model, while a change to model can't break com.gu.mediaservice.lib.dynamo.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
35→7 model uses com.gu.mediaservice.lib.argo✕
- Connections
- 1 pair of types, where a type in model uses a type in com.gu.mediaservice.lib.argo.
- The types involved
model.QuarantineUploader→com.gu.mediaservice.lib.argo.ArgoHelpers
- Direction
- model uses com.gu.mediaservice.lib.argo, so a change to com.gu.mediaservice.lib.argo can break model, while a change to model can't break com.gu.mediaservice.lib.argo.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
35→10 model uses com.gu.mediaservice.lib.auth✕
- Connections
- 1 pair of types, where a type in model uses a type in com.gu.mediaservice.lib.auth.
- The types involved
model.Projector→com.gu.mediaservice.lib.auth.Authentication
- Direction
- model uses com.gu.mediaservice.lib.auth, so a change to com.gu.mediaservice.lib.auth can break model, while a change to model can't break com.gu.mediaservice.lib.auth.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
35→12 model uses com.gu.mediaservice.lib.logging✕
- Connections
- 9 pairs of types, where a type in model uses a type in com.gu.mediaservice.lib.logging.
- The types involved
model.ImageUploadProjectionOps→com.gu.mediaservice.lib.logging.GridLoggingmodel.ImageUploadProjectionOps→com.gu.mediaservice.lib.logging.LogMarkermodel.QuarantineUploader→com.gu.mediaservice.lib.logging.LogMarkermodel.Uploader→com.gu.mediaservice.lib.logging.GridLoggingmodel.Uploader→com.gu.mediaservice.lib.logging.LogMarkermodel.UsageGroupOps→com.gu.mediaservice.lib.logging.GridLoggingmodel.UsageGroupOps→com.gu.mediaservice.lib.logging.LogMarkermodel.UsageTable→com.gu.mediaservice.lib.logging.GridLoggingmodel.UsageTable→com.gu.mediaservice.lib.logging.LogMarker
- Direction
- model uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break model, while a change to model can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
35→16 model uses com.gu.mediaservice.model.usage✕
- Connections
- 25 pairs of types, where a type in model uses a type in com.gu.mediaservice.model.usage.
- The types involved
model.ChildUsageRequest→com.gu.mediaservice.model.usage.ChildUsageMetadatamodel.ChildUsageRequest→com.gu.mediaservice.model.usage.UsageStatusmodel.ContentWrapper→com.gu.mediaservice.model.usage.UsageStatusmodel.DownloadUsageRequest→com.gu.mediaservice.model.usage.DownloadUsageMetadatamodel.DownloadUsageRequest→com.gu.mediaservice.model.usage.UsageStatusmodel.FrontUsageRequest→com.gu.mediaservice.model.usage.FrontUsageMetadatamodel.FrontUsageRequest→com.gu.mediaservice.model.usage.UsageStatusmodel.MediaWrapper→com.gu.mediaservice.model.usage.DigitalUsageMetadatamodel.MediaWrapper→com.gu.mediaservice.model.usage.UsageStatusmodel.PrintUsageRecord→com.gu.mediaservice.model.usage.PrintUsageMetadatamodel.PrintUsageRecord→com.gu.mediaservice.model.usage.UsageStatusmodel.SyndicationUsageRequest→com.gu.mediaservice.model.usage.SyndicationUsageMetadatamodel.SyndicationUsageRequest→com.gu.mediaservice.model.usage.UsageStatusmodel.UsageGroup→com.gu.mediaservice.model.usage.MediaUsagemodel.UsageGroup→com.gu.mediaservice.model.usage.UsageStatusmodel.UsageGroupOps→com.gu.mediaservice.model.usage.MediaUsagemodel.UsageGroupOps→com.gu.mediaservice.model.usage.UsageStatusmodel.UsageRecord→com.gu.mediaservice.model.usage.ChildUsageMetadatamodel.UsageRecord→com.gu.mediaservice.model.usage.DigitalUsageMetadatamodel.UsageRecord→com.gu.mediaservice.model.usage.DownloadUsageMetadatamodel.UsageRecord→com.gu.mediaservice.model.usage.FrontUsageMetadatamodel.UsageRecord→com.gu.mediaservice.model.usage.PrintUsageMetadatamodel.UsageRecord→com.gu.mediaservice.model.usage.SyndicationUsageMetadatamodel.UsageRecord→com.gu.mediaservice.model.usage.UsageTypemodel.UsageTable→com.gu.mediaservice.model.usage.MediaUsage
- Direction
- model uses com.gu.mediaservice.model.usage, so a change to com.gu.mediaservice.model.usage can break model, while a change to model can't break com.gu.mediaservice.model.usage.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
35→17 model uses com.gu.mediaservice.model✕
- Connections
- 8 pairs of types, where a type in model uses a type in com.gu.mediaservice.model.
- The types involved
model.CropRequest→com.gu.mediaservice.model.Boundsmodel.ImageUpload→com.gu.mediaservice.model.Imagemodel.ImageUploadOpsCfg→com.gu.mediaservice.model.MimeTypemodel.ImageUploadProjectionOps→com.gu.mediaservice.model.Imagemodel.Uploader→com.gu.mediaservice.model.FileMetadatamodel.Uploader→com.gu.mediaservice.model.Imagemodel.Uploader→com.gu.mediaservice.model.MimeTypemodel.Uploader→com.gu.mediaservice.model.OrientationMetadata
- Direction
- model uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break model, while a change to model can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
35→18 model uses com.gu.mediaservice.lib✕
- Connections
- 10 pairs of types, where a type in model uses a type in com.gu.mediaservice.lib.
- The types involved
model.ImageUploadOpsDependencies→com.gu.mediaservice.lib.StorableOptimisedImagemodel.ImageUploadOpsDependencies→com.gu.mediaservice.lib.StorableOriginalImagemodel.ImageUploadOpsDependencies→com.gu.mediaservice.lib.StorableThumbImagemodel.ImageUploadProjectionOps→com.gu.mediaservice.lib.StorableOptimisedImagemodel.ImageUploadProjectionOps→com.gu.mediaservice.lib.StorableOriginalImagemodel.ImageUploadProjectionOps→com.gu.mediaservice.lib.StorableThumbImagemodel.Uploader→com.gu.mediaservice.lib.BrowserViewableImagemodel.Uploader→com.gu.mediaservice.lib.StorableOptimisedImagemodel.Uploader→com.gu.mediaservice.lib.StorableOriginalImagemodel.Uploader→com.gu.mediaservice.lib.StorableThumbImage
- Direction
- model uses com.gu.mediaservice.lib, so a change to com.gu.mediaservice.lib can break model, while a change to model can't break com.gu.mediaservice.lib.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
35→22 model uses com.gu.mediaservice.lib.aws✕
- Connections
- 2 pairs of types, where a type in model uses a type in com.gu.mediaservice.lib.aws.
- The types involved
model.Projector→com.gu.mediaservice.lib.aws.Embeddermodel.Uploader→com.gu.mediaservice.lib.aws.S3Object
- Direction
- model uses com.gu.mediaservice.lib.aws, so a change to com.gu.mediaservice.lib.aws can break model, while a change to model can't break com.gu.mediaservice.lib.aws.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
35→25 model uses model.upload✕
- Connections
- 6 pairs of types, where a type in model uses a type in model.upload.
- The types involved
model.ImageUpload→model.upload.UploadRequestmodel.ImageUploadProjectionOps→model.upload.UploadRequestmodel.Projector→model.upload.OptimiseOpsmodel.QuarantineUploader→model.upload.UploadRequestmodel.Uploader→model.upload.OptimiseOpsmodel.Uploader→model.upload.UploadRequest
- Direction
- model uses model.upload, so a change to model.upload can break model, while a change to model can't break model.upload.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
35→29 model uses com.gu.mediaservice.lib.cleanup✕
- Connections
- 2 pairs of types, where a type in model uses a type in com.gu.mediaservice.lib.cleanup.
- The types involved
model.Projector→com.gu.mediaservice.lib.cleanup.ImageProcessormodel.Uploader→com.gu.mediaservice.lib.cleanup.ImageProcessor
- Direction
- model uses com.gu.mediaservice.lib.cleanup, so a change to com.gu.mediaservice.lib.cleanup can break model, while a change to model can't break com.gu.mediaservice.lib.cleanup.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
35→31 model uses com.gu.mediaservice.lib.imaging✕
- Connections
- 2 pairs of types, where a type in model uses a type in com.gu.mediaservice.lib.imaging.
- The types involved
model.ImageUploadOpsDependencies→com.gu.mediaservice.lib.imaging.ImageOperationsmodel.Projector→com.gu.mediaservice.lib.imaging.ImageOperations
- Direction
- model uses com.gu.mediaservice.lib.imaging, so a change to com.gu.mediaservice.lib.imaging can break model, while a change to model can't break com.gu.mediaservice.lib.imaging.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
35→37 model uses lib part of a loop✕
- Connections
- 4 pairs of types, where a type in model uses a type in lib.
- The types involved
model.Projector→lib.ImageLoaderConfigmodel.QuarantineUploader→lib.ImageLoaderConfigmodel.Uploader→lib.ImageLoaderConfigmodel.UsageTable→lib.WithLogMarker
- Direction
- model uses lib, so a change to lib can break model, while a change to model can't break lib.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
36→7 auth uses com.gu.mediaservice.lib.argo✕
- Connections
- 1 pair of types, where a type in auth uses a type in com.gu.mediaservice.lib.argo.
- The types involved
auth.AuthController→com.gu.mediaservice.lib.argo.ArgoHelpers
- Direction
- auth uses com.gu.mediaservice.lib.argo, so a change to com.gu.mediaservice.lib.argo can break auth, while a change to auth can't break com.gu.mediaservice.lib.argo.
- Position
- Below the diagonal: auth uses a module listed above it, which is the healthy direction.
36→26 auth uses com.gu.mediaservice.lib.config✕
- Connections
- 1 pair of types, where a type in auth uses a type in com.gu.mediaservice.lib.config.
- The types involved
auth.AuthConfig→com.gu.mediaservice.lib.config.CommonConfig
- Direction
- auth uses com.gu.mediaservice.lib.config, so a change to com.gu.mediaservice.lib.config can break auth, while a change to auth can't break com.gu.mediaservice.lib.config.
- Position
- Below the diagonal: auth uses a module listed above it, which is the healthy direction.
36→33 auth uses com.gu.mediaservice.lib.play✕
- Connections
- 1 pair of types, where a type in auth uses a type in com.gu.mediaservice.lib.play.
- The types involved
auth.AuthComponents→com.gu.mediaservice.lib.play.GridComponents
- Direction
- auth uses com.gu.mediaservice.lib.play, so a change to com.gu.mediaservice.lib.play can break auth, while a change to auth can't break com.gu.mediaservice.lib.play.
- Position
- Below the diagonal: auth uses a module listed above it, which is the healthy direction.
37→1 lib uses com.gu.mediaservice.lib.argo.model✕
- Connections
- 3 pairs of types, where a type in lib uses a type in com.gu.mediaservice.lib.argo.model.
- The types involved
lib.ImageResponse→com.gu.mediaservice.lib.argo.model.Actionlib.ImageResponse→com.gu.mediaservice.lib.argo.model.EmbeddedEntitylib.ImageResponse→com.gu.mediaservice.lib.argo.model.Link
- Direction
- lib uses com.gu.mediaservice.lib.argo.model, so a change to com.gu.mediaservice.lib.argo.model can break lib, while a change to lib can't break com.gu.mediaservice.lib.argo.model.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→3 lib uses com.gu.mediaservice.model.leases✕
- Connections
- 6 pairs of types, where a type in lib uses a type in com.gu.mediaservice.model.leases.
- The types involved
lib.ImageExtras→com.gu.mediaservice.model.leases.LeasesByMedialib.ImageExtras→com.gu.mediaservice.model.leases.MediaLeaselib.ImageResponse→com.gu.mediaservice.model.leases.LeasesByMedialib.LeaseNotifier→com.gu.mediaservice.model.leases.MediaLeaselib.LeaseStore→com.gu.mediaservice.model.leases.MediaLeaselib.LeaseStore→com.gu.mediaservice.model.leases.MediaLeaseType
- Direction
- lib uses com.gu.mediaservice.model.leases, so a change to com.gu.mediaservice.model.leases can break lib, while a change to lib can't break com.gu.mediaservice.model.leases.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→4 lib uses com.gu.mediaservice.syntax✕
- Connections
- 4 pairs of types, where a type in lib uses a type in com.gu.mediaservice.syntax.
- The types involved
lib.Edit→com.gu.mediaservice.syntax.MessageSubjectslib.LeaseNotifier→com.gu.mediaservice.syntax.MessageSubjectslib.Syndication→com.gu.mediaservice.syntax.MessageSubjectslib.UsageNotifier→com.gu.mediaservice.syntax.MessageSubjects
- Direction
- lib uses com.gu.mediaservice.syntax, so a change to com.gu.mediaservice.syntax can break lib, while a change to lib can't break com.gu.mediaservice.syntax.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→7 lib uses com.gu.mediaservice.lib.argo✕
- Connections
- 2 pairs of types, where a type in lib uses a type in com.gu.mediaservice.lib.argo.
- The types involved
lib.DigestBodyParser→com.gu.mediaservice.lib.argo.ArgoHelperslib.FailureResponse→com.gu.mediaservice.lib.argo.ArgoHelpers
- Direction
- lib uses com.gu.mediaservice.lib.argo, so a change to com.gu.mediaservice.lib.argo can break lib, while a change to lib can't break com.gu.mediaservice.lib.argo.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→8 lib uses com.gu.mediaservice.lib.auth.Authentication✕
- Connections
- 1 pair of types, where a type in lib uses a type in com.gu.mediaservice.lib.auth.Authentication.
- The types involved
lib.ImageExtras→com.gu.mediaservice.lib.auth.Authentication.Principal
- Direction
- lib uses com.gu.mediaservice.lib.auth.Authentication, so a change to com.gu.mediaservice.lib.auth.Authentication can break lib, while a change to lib can't break com.gu.mediaservice.lib.auth.Authentication.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→10 lib uses com.gu.mediaservice.lib.auth✕
- Connections
- 4 pairs of types, where a type in lib uses a type in com.gu.mediaservice.lib.auth.
- The types involved
lib.ImageExtras→com.gu.mediaservice.lib.auth.Authorisationlib.ImageResponse→com.gu.mediaservice.lib.auth.Tierlib.MediaApiMetrics→com.gu.mediaservice.lib.auth.ApiAccessorlib.ScriptToLoad→com.gu.mediaservice.lib.auth.SimplePermission
- Direction
- lib uses com.gu.mediaservice.lib.auth, so a change to com.gu.mediaservice.lib.auth can break lib, while a change to lib can't break com.gu.mediaservice.lib.auth.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→12 lib uses com.gu.mediaservice.lib.logging✕
- Connections
- 26 pairs of types, where a type in lib uses a type in com.gu.mediaservice.lib.logging. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
lib.ContentContainer→com.gu.mediaservice.lib.logging.GridLogginglib.ContentContainer→com.gu.mediaservice.lib.logging.LogMarkerlib.CrierEventProcessor→com.gu.mediaservice.lib.logging.GridLogginglib.CrierStreamReader→com.gu.mediaservice.lib.logging.GridLogginglib.CropStore→com.gu.mediaservice.lib.logging.LogMarkerlib.Crops→com.gu.mediaservice.lib.logging.GridLogginglib.Crops→com.gu.mediaservice.lib.logging.LogMarkerlib.Downloader→com.gu.mediaservice.lib.logging.GridLogginglib.Downloader→com.gu.mediaservice.lib.logging.LogMarkerlib.FailureResponse→com.gu.mediaservice.lib.logging.LogMarkerlib.ImageResponse→com.gu.mediaservice.lib.logging.GridLogginglib.ImageResponse→com.gu.mediaservice.lib.logging.LogMarkerlib.RetryHandler→com.gu.mediaservice.lib.logging.GridLogginglib.RetryHandler→com.gu.mediaservice.lib.logging.LogMarkerlib.SyncChecker→com.gu.mediaservice.lib.logging.GridLogginglib.SyncChecker→com.gu.mediaservice.lib.logging.LogMarkerlib.Syndication→com.gu.mediaservice.lib.logging.GridLogginglib.TaggedRecord→com.gu.mediaservice.lib.logging.LogMarkerlib.ThrallStreamProcessor→com.gu.mediaservice.lib.logging.GridLogginglib.UsageConfig→com.gu.mediaservice.lib.logging.GridLogginglib.UsageNotifier→com.gu.mediaservice.lib.logging.GridLogginglib.UsageNotifier→com.gu.mediaservice.lib.logging.LogMarkerlib.UsageRecorder→com.gu.mediaservice.lib.logging.GridLogginglib.UsageRecorder→com.gu.mediaservice.lib.logging.LogMarkerlib.UsageStore→com.gu.mediaservice.lib.logging.GridLogging
- Direction
- lib uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break lib, while a change to lib can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→15 lib uses com.gu.mediaservice.lib.metrics✕
- Connections
- 6 pairs of types, where a type in lib uses a type in com.gu.mediaservice.lib.metrics.
- The types involved
lib.CollectionsMetrics→com.gu.mediaservice.lib.metrics.CloudWatchMetricslib.ImageLoaderMetrics→com.gu.mediaservice.lib.metrics.CloudWatchMetricslib.MediaApiMetrics→com.gu.mediaservice.lib.metrics.CloudWatchMetricslib.MetadataEditorMetrics→com.gu.mediaservice.lib.metrics.CloudWatchMetricslib.ThrallMetrics→com.gu.mediaservice.lib.metrics.CloudWatchMetricslib.UsageMetrics→com.gu.mediaservice.lib.metrics.CloudWatchMetrics
- Direction
- lib uses com.gu.mediaservice.lib.metrics, so a change to com.gu.mediaservice.lib.metrics can break lib, while a change to lib can't break com.gu.mediaservice.lib.metrics.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→16 lib uses com.gu.mediaservice.model.usage✕
- Connections
- 10 pairs of types, where a type in lib uses a type in com.gu.mediaservice.model.usage.
- The types involved
lib.ImageResponse→com.gu.mediaservice.model.usage.Usagelib.ImageUsagesBySupplier→com.gu.mediaservice.model.usage.Usagelib.MediaUsageBuilder→com.gu.mediaservice.model.usage.MediaUsagelib.MediaUsageBuilder→com.gu.mediaservice.model.usage.UsageIdlib.UsageMetadataBuilder→com.gu.mediaservice.model.usage.DigitalUsageMetadatalib.UsageMetadataBuilder→com.gu.mediaservice.model.usage.DownloadUsageMetadatalib.UsageNotifier→com.gu.mediaservice.model.usage.UsageNoticelib.UsageRecorder→com.gu.mediaservice.model.usage.UsageNoticelib.UsageStore→com.gu.mediaservice.model.usage.UsageStatuslib.UsageStore→com.gu.mediaservice.model.usage.UsageType
- Direction
- lib uses com.gu.mediaservice.model.usage, so a change to com.gu.mediaservice.model.usage can break lib, while a change to lib can't break com.gu.mediaservice.model.usage.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→17 lib uses com.gu.mediaservice.model✕
- Connections
- 52 pairs of types, where a type in lib uses a type in com.gu.mediaservice.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
lib.AddedToPhotoshoot→com.gu.mediaservice.model.Imagelib.CollectionResponse→com.gu.mediaservice.model.ActionDatalib.CropSpecMetadata→com.gu.mediaservice.model.Croplib.CropSpecMetadata→com.gu.mediaservice.model.CropSpeclib.CropSpecMetadata→com.gu.mediaservice.model.Dimensionslib.CropStore→com.gu.mediaservice.model.Assetlib.CropStore→com.gu.mediaservice.model.Croplib.CropStore→com.gu.mediaservice.model.Dimensionslib.CropStore→com.gu.mediaservice.model.MimeTypelib.Crops→com.gu.mediaservice.model.Assetlib.Crops→com.gu.mediaservice.model.Boundslib.Crops→com.gu.mediaservice.model.Croplib.Crops→com.gu.mediaservice.model.Dimensionslib.Crops→com.gu.mediaservice.model.MimeTypelib.Crops→com.gu.mediaservice.model.OrientationMetadatalib.Crops→com.gu.mediaservice.model.SourceImagelib.DownloadMetadata→com.gu.mediaservice.model.Imagelib.Edit→com.gu.mediaservice.model.Editslib.FailureResponse→com.gu.mediaservice.model.MimeTypelib.FailureResponse→com.gu.mediaservice.model.UnsupportedMimeTypeExceptionlib.HasExports→com.gu.mediaservice.model.Imagelib.HasLabels→com.gu.mediaservice.model.Imagelib.HasLeases→com.gu.mediaservice.model.Imagelib.HasPersistenceIdentifier→com.gu.mediaservice.model.Imagelib.HasUsages→com.gu.mediaservice.model.Image
- Direction
- lib uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break lib, while a change to lib can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→18 lib uses com.gu.mediaservice.lib✕
- Connections
- 2 pairs of types, where a type in lib uses a type in com.gu.mediaservice.lib.
- The types involved
lib.CropStore→com.gu.mediaservice.lib.S3ImageStoragelib.QuotaStore→com.gu.mediaservice.lib.BaseStore
- Direction
- lib uses com.gu.mediaservice.lib, so a change to com.gu.mediaservice.lib can break lib, while a change to lib can't break com.gu.mediaservice.lib.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→21 lib uses lib.usagerights✕
- Connections
- 2 pairs of types, where a type in lib uses a type in lib.usagerights.
- The types involved
lib.ImageExtras→lib.usagerights.CostCalculatorlib.ImageResponse→lib.usagerights.CostCalculator
- Direction
- lib uses lib.usagerights, so a change to lib.usagerights can break lib, while a change to lib can't break lib.usagerights.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→22 lib uses com.gu.mediaservice.lib.aws✕
- Connections
- 8 pairs of types, where a type in lib uses a type in com.gu.mediaservice.lib.aws.
- The types involved
lib.EditsStore→com.gu.mediaservice.lib.aws.DynamoDBlib.KinesisReceiverConfig→com.gu.mediaservice.lib.aws.AwsClientBuilderUtilslib.LeaseNotifier→com.gu.mediaservice.lib.aws.ThrallMessageSenderlib.MetadataEditorNotifications→com.gu.mediaservice.lib.aws.SNSlib.MetadataSqsMessageConsumer→com.gu.mediaservice.lib.aws.SqsViaSnsMessageConsumerlib.Notifications→com.gu.mediaservice.lib.aws.ThrallMessageSenderlib.SyndicationStore→com.gu.mediaservice.lib.aws.DynamoDBlib.UsageNotifier→com.gu.mediaservice.lib.aws.ThrallMessageSender
- Direction
- lib uses com.gu.mediaservice.lib.aws, so a change to com.gu.mediaservice.lib.aws can break lib, while a change to lib can't break com.gu.mediaservice.lib.aws.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→23 lib uses lib.imaging✕
- Connections
- 1 pair of types, where a type in lib uses a type in lib.imaging.
- The types involved
lib.FailureResponse→lib.imaging.UserImageLoaderException
- Direction
- lib uses lib.imaging, so a change to lib.imaging can break lib, while a change to lib can't break lib.imaging.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→26 lib uses com.gu.mediaservice.lib.config✕
- Connections
- 9 pairs of types, where a type in lib uses a type in com.gu.mediaservice.lib.config.
- The types involved
lib.CollectionsConfig→com.gu.mediaservice.lib.config.CommonConfiglib.CropperConfig→com.gu.mediaservice.lib.config.CommonConfiglib.EditsConfig→com.gu.mediaservice.lib.config.CommonConfiglib.ImageLoaderConfig→com.gu.mediaservice.lib.config.CommonConfiglib.KahunaConfig→com.gu.mediaservice.lib.config.CommonConfiglib.LeasesConfig→com.gu.mediaservice.lib.config.CommonConfiglib.MediaApiConfig→com.gu.mediaservice.lib.config.CommonConfigWithElasticlib.ThrallConfig→com.gu.mediaservice.lib.config.CommonConfigWithElasticlib.UsageConfig→com.gu.mediaservice.lib.config.CommonConfig
- Direction
- lib uses com.gu.mediaservice.lib.config, so a change to com.gu.mediaservice.lib.config can break lib, while a change to lib can't break com.gu.mediaservice.lib.config.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→29 lib uses com.gu.mediaservice.lib.cleanup✕
- Connections
- 1 pair of types, where a type in lib uses a type in com.gu.mediaservice.lib.cleanup.
- The types involved
lib.ImageLoaderConfig→com.gu.mediaservice.lib.cleanup.ComposedImageProcessor
- Direction
- lib uses com.gu.mediaservice.lib.cleanup, so a change to com.gu.mediaservice.lib.cleanup can break lib, while a change to lib can't break com.gu.mediaservice.lib.cleanup.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→30 lib uses com.gu.mediaservice.lib.elasticsearch✕
- Connections
- 1 pair of types, where a type in lib uses a type in com.gu.mediaservice.lib.elasticsearch.
- The types involved
lib.ThrallConfig→com.gu.mediaservice.lib.elasticsearch.ReapableEligibility
- Direction
- lib uses com.gu.mediaservice.lib.elasticsearch, so a change to com.gu.mediaservice.lib.elasticsearch can break lib, while a change to lib can't break com.gu.mediaservice.lib.elasticsearch.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→31 lib uses com.gu.mediaservice.lib.imaging✕
- Connections
- 1 pair of types, where a type in lib uses a type in com.gu.mediaservice.lib.imaging.
- The types involved
lib.Crops→com.gu.mediaservice.lib.imaging.ExportResult
- Direction
- lib uses com.gu.mediaservice.lib.imaging, so a change to com.gu.mediaservice.lib.imaging can break lib, while a change to lib can't break com.gu.mediaservice.lib.imaging.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→34 lib uses lib.elasticsearch✕
- Connections
- 1 pair of types, where a type in lib uses a type in lib.elasticsearch.
- The types involved
lib.ImageResponse→lib.elasticsearch.SourceWrapper
- Direction
- lib uses lib.elasticsearch, so a change to lib.elasticsearch can break lib, while a change to lib can't break lib.elasticsearch.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
37→35 lib uses model✕
- Connections
- 13 pairs of types, where a type in lib uses a type in model.
- The types involved
lib.ContentContainer→model.UsageGrouplib.ContentContainer→model.UsageGroupOpslib.CrierUsageStream→model.UsageGrouplib.EditsConfig→model.UsageRightsLeaselib.MediaUsageBuilder→model.ChildUsageRequestlib.MediaUsageBuilder→model.DownloadUsageRequestlib.MediaUsageBuilder→model.FrontUsageRequestlib.MediaUsageBuilder→model.MediaWrapperlib.MediaUsageBuilder→model.PrintUsageRecordlib.MediaUsageBuilder→model.SyndicationUsageRequestlib.UploadStatusTable→model.UploadStatuslib.UploadStatusTable→model.UploadStatusRecordlib.UsageRecorder→model.UsageGroup
- Direction
- lib uses model, so a change to model can break lib, while a change to lib can't break model.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
38→12 (global) uses com.gu.mediaservice.lib.logging✕
- Connections
- 1 pair of types, where a type in (global) uses a type in com.gu.mediaservice.lib.logging.
- The types involved
ImageLoaderComponents→com.gu.mediaservice.lib.logging.GridLogging
- Direction
- (global) uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break (global), while a change to (global) can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
38→22 (global) uses com.gu.mediaservice.lib.aws✕
- Connections
- 1 pair of types, where a type in (global) uses a type in com.gu.mediaservice.lib.aws.
- The types involved
ImageLoaderComponents→com.gu.mediaservice.lib.aws.Embedder
- Direction
- (global) uses com.gu.mediaservice.lib.aws, so a change to com.gu.mediaservice.lib.aws can break (global), while a change to (global) can't break com.gu.mediaservice.lib.aws.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
38→26 (global) uses com.gu.mediaservice.lib.config✕
- Connections
- 1 pair of types, where a type in (global) uses a type in com.gu.mediaservice.lib.config.
- The types involved
ThrallComponents→com.gu.mediaservice.lib.config.Services
- Direction
- (global) uses com.gu.mediaservice.lib.config, so a change to com.gu.mediaservice.lib.config can break (global), while a change to (global) can't break com.gu.mediaservice.lib.config.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
38→27 (global) uses com.gu.mediaservice✕
- Connections
- 1 pair of types, where a type in (global) uses a type in com.gu.mediaservice.
- The types involved
ThrallComponents→com.gu.mediaservice.GridClient
- Direction
- (global) uses com.gu.mediaservice, so a change to com.gu.mediaservice can break (global), while a change to (global) can't break com.gu.mediaservice.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
38→33 (global) uses com.gu.mediaservice.lib.play✕
- Connections
- 10 pairs of types, where a type in (global) uses a type in com.gu.mediaservice.lib.play.
- The types involved
AppLoader→com.gu.mediaservice.lib.play.GridAppLoaderCollectionsComponents→com.gu.mediaservice.lib.play.GridComponentsCropperComponents→com.gu.mediaservice.lib.play.GridComponentsImageLoaderComponents→com.gu.mediaservice.lib.play.GridComponentsKahunaComponents→com.gu.mediaservice.lib.play.GridComponentsLeasesComponents→com.gu.mediaservice.lib.play.GridComponentsMediaApiComponents→com.gu.mediaservice.lib.play.GridComponentsMetadataEditorComponents→com.gu.mediaservice.lib.play.GridComponentsThrallComponents→com.gu.mediaservice.lib.play.GridComponentsUsageComponents→com.gu.mediaservice.lib.play.GridComponents
- Direction
- (global) uses com.gu.mediaservice.lib.play, so a change to com.gu.mediaservice.lib.play can break (global), while a change to (global) can't break com.gu.mediaservice.lib.play.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
38→35 (global) uses model✕
- Connections
- 1 pair of types, where a type in (global) uses a type in model.
- The types involved
ImageLoaderComponents→model.QuarantineUploader
- Direction
- (global) uses model, so a change to model can break (global), while a change to (global) can't break model.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
38→37 (global) uses lib✕
- Connections
- 3 pairs of types, where a type in (global) uses a type in lib.
- The types involved
KahunaSecurityConfig→lib.KahunaConfigMediaApiComponents→lib.UsageQuotaThrallComponents→lib.MigrationSourceWithSender
- Direction
- (global) uses lib, so a change to lib can break (global), while a change to (global) can't break lib.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
39→1 controllers uses com.gu.mediaservice.lib.argo.model✕
- Connections
- 3 pairs of types, where a type in controllers uses a type in com.gu.mediaservice.lib.argo.model.
- The types involved
controllers.CollectionsController→com.gu.mediaservice.lib.argo.model.EmbeddedEntitycontrollers.CollectionsController→com.gu.mediaservice.lib.argo.model.Linkcontrollers.UsageApi→com.gu.mediaservice.lib.argo.model.EntityResponse
- Direction
- controllers uses com.gu.mediaservice.lib.argo.model, so a change to com.gu.mediaservice.lib.argo.model can break controllers, while a change to controllers can't break com.gu.mediaservice.lib.argo.model.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→3 controllers uses com.gu.mediaservice.model.leases✕
- Connections
- 1 pair of types, where a type in controllers uses a type in com.gu.mediaservice.model.leases.
- The types involved
controllers.MediaLeaseController→com.gu.mediaservice.model.leases.MediaLease
- Direction
- controllers uses com.gu.mediaservice.model.leases, so a change to com.gu.mediaservice.model.leases can break controllers, while a change to controllers can't break com.gu.mediaservice.model.leases.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→4 controllers uses com.gu.mediaservice.syntax✕
- Connections
- 5 pairs of types, where a type in controllers uses a type in com.gu.mediaservice.syntax.
- The types involved
controllers.CropperController→com.gu.mediaservice.syntax.MessageSubjectscontrollers.EditsController→com.gu.mediaservice.syntax.MessageSubjectscontrollers.ImageCollectionsController→com.gu.mediaservice.syntax.MessageSubjectscontrollers.SyndicationController→com.gu.mediaservice.syntax.MessageSubjectscontrollers.UsageApi→com.gu.mediaservice.syntax.MessageSubjects
- Direction
- controllers uses com.gu.mediaservice.syntax, so a change to com.gu.mediaservice.syntax can break controllers, while a change to controllers can't break com.gu.mediaservice.syntax.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→7 controllers uses com.gu.mediaservice.lib.argo✕
- Connections
- 15 pairs of types, where a type in controllers uses a type in com.gu.mediaservice.lib.argo.
- The types involved
controllers.AggregateResponses→com.gu.mediaservice.lib.argo.ArgoHelperscontrollers.CollectionsController→com.gu.mediaservice.lib.argo.ArgoHelperscontrollers.CropperController→com.gu.mediaservice.lib.argo.ArgoHelperscontrollers.EditsApi→com.gu.mediaservice.lib.argo.ArgoHelperscontrollers.EditsController→com.gu.mediaservice.lib.argo.ArgoHelperscontrollers.HealthCheck→com.gu.mediaservice.lib.argo.ArgoHelperscontrollers.ImageCollectionsController→com.gu.mediaservice.lib.argo.ArgoHelperscontrollers.ImageLoaderController→com.gu.mediaservice.lib.argo.ArgoHelperscontrollers.KahunaController→com.gu.mediaservice.lib.argo.ArgoHelperscontrollers.MediaLeaseController→com.gu.mediaservice.lib.argo.ArgoHelperscontrollers.SuggestionController→com.gu.mediaservice.lib.argo.ArgoHelperscontrollers.SyndicationController→com.gu.mediaservice.lib.argo.ArgoHelperscontrollers.UploadStatusController→com.gu.mediaservice.lib.argo.ArgoHelperscontrollers.UsageApi→com.gu.mediaservice.lib.argo.ArgoHelperscontrollers.UsageController→com.gu.mediaservice.lib.argo.ArgoHelpers
- Direction
- controllers uses com.gu.mediaservice.lib.argo, so a change to com.gu.mediaservice.lib.argo can break controllers, while a change to controllers can't break com.gu.mediaservice.lib.argo.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→8 controllers uses com.gu.mediaservice.lib.auth.Authentication✕
- Connections
- 4 pairs of types, where a type in controllers uses a type in com.gu.mediaservice.lib.auth.Authentication.
- The types involved
controllers.CropperController→com.gu.mediaservice.lib.auth.Authentication.Principalcontrollers.EditsApi→com.gu.mediaservice.lib.auth.Authentication.Principalcontrollers.EditsController→com.gu.mediaservice.lib.auth.Authentication.Principalcontrollers.MediaLeaseController→com.gu.mediaservice.lib.auth.Authentication.Principal
- Direction
- controllers uses com.gu.mediaservice.lib.auth.Authentication, so a change to com.gu.mediaservice.lib.auth.Authentication can break controllers, while a change to controllers can't break com.gu.mediaservice.lib.auth.Authentication.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→10 controllers uses com.gu.mediaservice.lib.auth✕
- Connections
- 6 pairs of types, where a type in controllers uses a type in com.gu.mediaservice.lib.auth.
- The types involved
controllers.KahunaController→com.gu.mediaservice.lib.auth.Authenticationcontrollers.KahunaController→com.gu.mediaservice.lib.auth.BaseControllerWithLoginRedirectscontrollers.ReaperController→com.gu.mediaservice.lib.auth.Authenticationcontrollers.ReaperController→com.gu.mediaservice.lib.auth.BaseControllerWithLoginRedirectscontrollers.ThrallController→com.gu.mediaservice.lib.auth.Authenticationcontrollers.ThrallController→com.gu.mediaservice.lib.auth.BaseControllerWithLoginRedirects
- Direction
- controllers uses com.gu.mediaservice.lib.auth, so a change to com.gu.mediaservice.lib.auth can break controllers, while a change to controllers can't break com.gu.mediaservice.lib.auth.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→12 controllers uses com.gu.mediaservice.lib.logging✕
- Connections
- 6 pairs of types, where a type in controllers uses a type in com.gu.mediaservice.lib.logging.
- The types involved
controllers.CropperController→com.gu.mediaservice.lib.logging.LogMarkercontrollers.ImageLoaderController→com.gu.mediaservice.lib.logging.LogMarkercontrollers.ReaperController→com.gu.mediaservice.lib.logging.GridLoggingcontrollers.ReaperController→com.gu.mediaservice.lib.logging.MarkerMapcontrollers.ThrallController→com.gu.mediaservice.lib.logging.GridLoggingcontrollers.UsageController→com.gu.mediaservice.lib.logging.LogMarker
- Direction
- controllers uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break controllers, while a change to controllers can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→14 controllers uses com.gu.mediaservice.lib.management✕
- Connections
- 3 pairs of types, where a type in controllers uses a type in com.gu.mediaservice.lib.management.
- The types involved
controllers.HealthCheck→com.gu.mediaservice.lib.management.ElasticSearchHealthCheckcontrollers.ImageLoaderManagement→com.gu.mediaservice.lib.management.BuildInfocontrollers.ImageLoaderManagement→com.gu.mediaservice.lib.management.Management
- Direction
- controllers uses com.gu.mediaservice.lib.management, so a change to com.gu.mediaservice.lib.management can break controllers, while a change to controllers can't break com.gu.mediaservice.lib.management.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→16 controllers uses com.gu.mediaservice.model.usage✕
- Connections
- 1 pair of types, where a type in controllers uses a type in com.gu.mediaservice.model.usage.
- The types involved
controllers.UsageApi→com.gu.mediaservice.model.usage.Usage
- Direction
- controllers uses com.gu.mediaservice.model.usage, so a change to com.gu.mediaservice.model.usage can break controllers, while a change to controllers can't break com.gu.mediaservice.model.usage.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→17 controllers uses com.gu.mediaservice.model✕
- Connections
- 6 pairs of types, where a type in controllers uses a type in com.gu.mediaservice.model.
- The types involved
controllers.CollectionsController→com.gu.mediaservice.model.Collectioncontrollers.CropperController→com.gu.mediaservice.model.SourceImagecontrollers.EditsController→com.gu.mediaservice.model.EditsResponsecontrollers.EditsController→com.gu.mediaservice.model.ImageMetadatacontrollers.ImageCollectionsController→com.gu.mediaservice.model.Collectioncontrollers.SyndicationController→com.gu.mediaservice.model.EditsResponse
- Direction
- controllers uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break controllers, while a change to controllers can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→18 controllers uses com.gu.mediaservice.lib✕
- Connections
- 1 pair of types, where a type in controllers uses a type in com.gu.mediaservice.lib.
- The types involved
controllers.SuggestionController→com.gu.mediaservice.lib.ImageFields
- Direction
- controllers uses com.gu.mediaservice.lib, so a change to com.gu.mediaservice.lib can break controllers, while a change to controllers can't break com.gu.mediaservice.lib.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→22 controllers uses com.gu.mediaservice.lib.aws✕
- Connections
- 1 pair of types, where a type in controllers uses a type in com.gu.mediaservice.lib.aws.
- The types involved
controllers.ImageLoaderController→com.gu.mediaservice.lib.aws.SqsHelpers
- Direction
- controllers uses com.gu.mediaservice.lib.aws, so a change to com.gu.mediaservice.lib.aws can break controllers, while a change to controllers can't break com.gu.mediaservice.lib.aws.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→24 controllers uses lib.querysyntax✕
- Connections
- 1 pair of types, where a type in controllers uses a type in lib.querysyntax.
- The types involved
controllers.MediaApi→lib.querysyntax.Condition
- Direction
- controllers uses lib.querysyntax, so a change to lib.querysyntax can break controllers, while a change to controllers can't break lib.querysyntax.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→25 controllers uses model.upload✕
- Connections
- 1 pair of types, where a type in controllers uses a type in model.upload.
- The types involved
controllers.ImageLoaderController→model.upload.UploadRequest
- Direction
- controllers uses model.upload, so a change to model.upload can break controllers, while a change to controllers can't break model.upload.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→26 controllers uses com.gu.mediaservice.lib.config✕
- Connections
- 4 pairs of types, where a type in controllers uses a type in com.gu.mediaservice.lib.config.
- The types involved
controllers.EditsController→com.gu.mediaservice.lib.config.Servicescontrollers.KahunaController→com.gu.mediaservice.lib.config.Servicescontrollers.ReaperController→com.gu.mediaservice.lib.config.Servicescontrollers.ThrallController→com.gu.mediaservice.lib.config.Services
- Direction
- controllers uses com.gu.mediaservice.lib.config, so a change to com.gu.mediaservice.lib.config can break controllers, while a change to controllers can't break com.gu.mediaservice.lib.config.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→27 controllers uses com.gu.mediaservice✕
- Connections
- 1 pair of types, where a type in controllers uses a type in com.gu.mediaservice.
- The types involved
controllers.EditsController→com.gu.mediaservice.GridClient
- Direction
- controllers uses com.gu.mediaservice, so a change to com.gu.mediaservice can break controllers, while a change to controllers can't break com.gu.mediaservice.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→34 controllers uses lib.elasticsearch✕
- Connections
- 2 pairs of types, where a type in controllers uses a type in lib.elasticsearch.
- The types involved
controllers.AggregateResponses→lib.elasticsearch.AggregateSearchResultscontrollers.SuggestionController→lib.elasticsearch.AggregateSearchParams
- Direction
- controllers uses lib.elasticsearch, so a change to lib.elasticsearch can break controllers, while a change to controllers can't break lib.elasticsearch.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→35 controllers uses model✕
- Connections
- 6 pairs of types, where a type in controllers uses a type in model.
- The types involved
controllers.CategoryResponse→model.UsageRightsLeasecontrollers.CategoryResponse→model.UsageRightsPropertycontrollers.CollectionsController→model.Nodecontrollers.CropperController→model.ExportRequestcontrollers.ImageLoaderController→model.S3IngestObjectcontrollers.ImageLoaderController→model.UploadStatusUri
- Direction
- controllers uses model, so a change to model can break controllers, while a change to controllers can't break model.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
39→37 controllers uses lib✕
- Connections
- 13 pairs of types, where a type in controllers uses a type in lib.
- The types involved
controllers.EditsController→lib.Editcontrollers.EditsController→lib.EditsConfigcontrollers.EditsController→lib.EditsStorecontrollers.EditsController→lib.Notificationscontrollers.ImageLoaderController→lib.DigestedFilecontrollers.KahunaController→lib.KahunaConfigcontrollers.SyndicationController→lib.EditsConfigcontrollers.SyndicationController→lib.EditsStorecontrollers.SyndicationController→lib.Notificationscontrollers.SyndicationController→lib.Syndicationcontrollers.SyndicationController→lib.SyndicationStorecontrollers.UploadStatusController→lib.ImageLoaderConfigcontrollers.UsageController→lib.SupplierUsageStatus
- Direction
- controllers uses lib, so a change to lib can break controllers, while a change to controllers can't break lib.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
40→4 lib.kinesis uses com.gu.mediaservice.syntax✕
- Connections
- 1 pair of types, where a type in lib.kinesis uses a type in com.gu.mediaservice.syntax.
- The types involved
lib.kinesis.MessageProcessor→com.gu.mediaservice.syntax.MessageSubjects
- Direction
- lib.kinesis uses com.gu.mediaservice.syntax, so a change to com.gu.mediaservice.syntax can break lib.kinesis, while a change to lib.kinesis can't break com.gu.mediaservice.syntax.
- Position
- Below the diagonal: lib.kinesis uses a module listed above it, which is the healthy direction.
40→12 lib.kinesis uses com.gu.mediaservice.lib.logging✕
- Connections
- 5 pairs of types, where a type in lib.kinesis uses a type in com.gu.mediaservice.lib.logging.
- The types involved
lib.kinesis.KinesisConfig→com.gu.mediaservice.lib.logging.GridLogginglib.kinesis.MessageProcessor→com.gu.mediaservice.lib.logging.GridLogginglib.kinesis.MessageProcessor→com.gu.mediaservice.lib.logging.LogMarkerlib.kinesis.MessageTranslator→com.gu.mediaservice.lib.logging.GridLogginglib.kinesis.ThrallEventConsumer→com.gu.mediaservice.lib.logging.GridLogging
- Direction
- lib.kinesis uses com.gu.mediaservice.lib.logging, so a change to com.gu.mediaservice.lib.logging can break lib.kinesis, while a change to lib.kinesis can't break com.gu.mediaservice.lib.logging.
- Position
- Below the diagonal: lib.kinesis uses a module listed above it, which is the healthy direction.
40→13 lib.kinesis uses com.gu.mediaservice.lib.json✕
- Connections
- 1 pair of types, where a type in lib.kinesis uses a type in com.gu.mediaservice.lib.json.
- The types involved
lib.kinesis.ThrallEventConsumer→com.gu.mediaservice.lib.json.PlayJsonHelpers
- Direction
- lib.kinesis uses com.gu.mediaservice.lib.json, so a change to com.gu.mediaservice.lib.json can break lib.kinesis, while a change to lib.kinesis can't break com.gu.mediaservice.lib.json.
- Position
- Below the diagonal: lib.kinesis uses a module listed above it, which is the healthy direction.
40→17 lib.kinesis uses com.gu.mediaservice.model✕
- Connections
- 24 pairs of types, where a type in lib.kinesis uses a type in com.gu.mediaservice.model.
- The types involved
lib.kinesis.MessageProcessor→com.gu.mediaservice.model.AddImageLeaseMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.CreateMigrationIndexMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.DeleteImageExportsMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.DeleteImageMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.DeleteSingleUsageMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.DeleteUsagesMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.ImageMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.MigrateImageMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.RemoveImageLeaseMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.ReplaceImageLeasesMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.SetImageCollectionsMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.SoftDeleteImageMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.ThrallMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.UnSoftDeleteImageMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.UpdateEmbeddingMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.UpdateImageExportsMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.UpdateImagePhotoshootMetadataMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.UpdateImageSyndicationMetadataMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.UpdateImageUsagesMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.UpdateImageUserMetadataMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.UpdateUsageStatusMessagelib.kinesis.MessageProcessor→com.gu.mediaservice.model.UpsertFromProjectionMessagelib.kinesis.MessageTranslator→com.gu.mediaservice.model.ExternalThrallMessagelib.kinesis.ThrallEventConsumer→com.gu.mediaservice.model.ThrallMessage
- Direction
- lib.kinesis uses com.gu.mediaservice.model, so a change to com.gu.mediaservice.model can break lib.kinesis, while a change to lib.kinesis can't break com.gu.mediaservice.model.
- Position
- Below the diagonal: lib.kinesis uses a module listed above it, which is the healthy direction.
40→22 lib.kinesis uses com.gu.mediaservice.lib.aws✕
- Connections
- 1 pair of types, where a type in lib.kinesis uses a type in com.gu.mediaservice.lib.aws.
- The types involved
lib.kinesis.MessageTranslator→com.gu.mediaservice.lib.aws.UpdateMessage
- Direction
- lib.kinesis uses com.gu.mediaservice.lib.aws, so a change to com.gu.mediaservice.lib.aws can break lib.kinesis, while a change to lib.kinesis can't break com.gu.mediaservice.lib.aws.
- Position
- Below the diagonal: lib.kinesis uses a module listed above it, which is the healthy direction.
40→34 lib.kinesis uses lib.elasticsearch✕
- Connections
- 1 pair of types, where a type in lib.kinesis uses a type in lib.elasticsearch.
- The types involved
lib.kinesis.MessageProcessor→lib.elasticsearch.ElasticSearchUpdateResponse
- Direction
- lib.kinesis uses lib.elasticsearch, so a change to lib.elasticsearch can break lib.kinesis, while a change to lib.kinesis can't break lib.elasticsearch.
- Position
- Below the diagonal: lib.kinesis uses a module listed above it, which is the healthy direction.
40→37 lib.kinesis uses lib✕
- Connections
- 1 pair of types, where a type in lib.kinesis uses a type in lib.
- The types involved
lib.kinesis.KinesisConfig→lib.KinesisReceiverConfig
- Direction
- lib.kinesis uses lib, so a change to lib can break lib.kinesis, while a change to lib.kinesis can't break lib.
- Position
- Below the diagonal: lib.kinesis uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 124 | High / Critical |
| A05:2025 — Injection | 53 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 52 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 finding(s) in DR & Backup; Add tests that import the unreached modules (directly or through their public entry); Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 finding(s) in DR & Backup. | +4.5 pts | Medium | DR & Backup |
| Add tests that import the unreached modules (directly or through their public entry). | +3.7 pts | Medium | Test Coverage |
| Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +2.6 pts | Medium | Security & performance tooling |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +2.2 pts | Medium | Keyboard semantics |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +1.5 pts | Medium | Visual & motion safety |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.3 pts | Medium | Release Hygiene |
| Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 3 sites, not one: `common-lib/src/main/java/com/gu/mediaservice/DeprecatedHashWrapper.java:13` (Hashing.sha1), `common-lib/src/main/scala/com/gu/mediaservice/lib/MD5.scala:6` (MessageDigest.getInstance("MD5")), `image-loader/app/lib/BodyParsers.scala:39` (MessageDigest.getInstance("SHA-1")). Each is a separate decision — fixing only the line this row cites leaves the others in place. | +1.3 pts | Medium | Web-Security Posture |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. | +0.6 pts | Low | ADR Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 0.2 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 1.6 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.6 | Slop | Secrets (history): REDACTED: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.4 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 5.4 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| kahuna/public/js/search/query.js | 5.7 | Mixed | Cyclomatic Complexity: (anonymous)::watchSearchChange (cyclomatic 21) |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| kahuna/public/js/search/results.js | 5.9 | Mixed | Cyclomatic Complexity: (anonymous) (cyclomatic 100) |
| common-lib/src/main/scala/com/gu/mediaservice/lib/imaging/MagickImageOperations.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| media-api/app/controllers/MediaApi.scala | 6.0 | Mixed | Explicit Debt: FixmeComment |
| image-loader/app/model/Uploader.scala | 6.0 | Mixed | Explicit Debt: FixmeComment |
| usage/app/model/UsageGroup.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| usage/app/lib/CrierEventProcessor.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 82 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 82 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, 829 of 901 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .ts, .tsx, .scala, and our analyzer cannot run the .scala test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 71.5% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
- D10 Test 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. The 109 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 103 test source file(s) (.scala) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- 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 SCORED: this repository's production source includes .scala, and the scala executor ran against the .scala half and could not be re-run to completion inside our analyzer environment — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in cdk/ (2 tests); jest via `npm ci --ignore-scripts` in dev/oidc-provider/ (0 tests); jest via `npm ci --ignore-scripts` in image-counter-lambda/ (3 tests); jest via `npm ci --ignore-scripts` in image-embedder-lambda/ (37 tests); jest via `npm ci --ignore-scripts` in kahuna/): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The remedy is our analyzer environment, not a runner nobody has built.
- 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 for the jest suite in kahuna/ was NOT MEASURED: the dependency install for kahuna/ could not reach codeload.github.com, which the analyzer sandbox's egress allowlist does not carry (npm error 403 403 Forbidden - GET https://codeload.github.com/guardian/titip/legacy.tar.gz/refs/tags/1.1.0), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares REDACTED, but the licence verdict published here was taken over its sbt dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — 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. 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.
- D21 Naming Consistency — 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. 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.
- D21 Naming Consistency — 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. 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 (image-embedder-lambda/package.json), 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. For npm the surface is what a published REDACTED's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D31 IaC & Container Security — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. E2e-tests/images/Dockerfile.dockerignore carries no `FROM` instruction, so it declares no build stage and every REDACTED rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 7 of 8 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
- 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. `dev/oidc-provider/app.js` 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.
- AC4 Keyboard semantics — 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. 17 further occurrence(s) are not listed individually; the score already reflects all 57.
- 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 Play dependency injection, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — cerebro Pulling localstack Pulling elasticsearch Pulling elasticsearch Error Get "https://docker.elastic.co/v2/": Forbidden cerebro Error context canceled localstack Error context canceled Error response from daemon: Get "https://docker.elastic.co/v2/": Forbidden; the earlier `compose pull` step reported: oidc-provider Skipped - No image to be pulled imgops Skipped - No image to be pulled elasticsearch Pulling cerebro Pulling localstack Pulling elasticsearch Error Get "https://docker.elastic.co/v2/": Forbidden cerebro Error context canceled localstack Error context canceled Error response from daemon: Get "https://docker.elastic.co/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'software.amazon.awssdk.services.dynamodb' is imported (usage/app/model/UsageRecord.scala:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'software.amazon.awssdk.services.dynamodb' is imported (usage/app/model/UsageRecord.scala:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'software.amazon.awssdk.services.dynamodb' is imported (usage/app/model/UsageRecord.scala:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 reads a prose claim (a path, a setting, a variable, a route, a version, a project, an install, a bare project name in a command) only in text identified as English: the cues that tell a claim from an absence, the past, a plan or an example are an English lexicon, and on other text they would let a false claim through. Links, image targets, fenced commands with an explicit path or a package-manager script, and env-fence variables are checked in every language. 'und' is text the identifier could not name (too short, mixed script, no function words).
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- R10 Code Duplication — 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. 5 further occurrence(s) are not listed individually; the score already reflects all 45.
- R4 Test Coverage — 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. 117 further occurrence(s) are not listed individually; the score already reflects all 157.
- X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
26 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was (anonymous) at 100. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Subject.create at 37 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: common-lib/src/main/scala/com/gu/mediaservice/lib/metadata/Subject.scala (Subject.create at 37), common-lib/src/main/scala/com/gu/mediaservice/model/UsageRights.scala (UsageRights.jsonWrites at 32), thrall/app/lib/kinesis/MessageProcessor.scala (MessageProcessor.process at 23), common-lib/src/main/scala/com/gu/mediaservice/lib/cleanup/InsertGuardianImageType.scala (InsertGuardianImageType.toImageType at 21), metadata-editor/app/model/UsageRightsProperty.scala (UsageRightsProperty.categoryUsageRightsProperties at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with (anonymous) (cyclomatic 100), (anonymous) (cyclomatic 78). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 6.0 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D2 · Cognitive Complexity
40 method(s) exceeded the cognitive complexity threshold of 15; the worst was GoodToGoCheck.run at 148.
What to do
- Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with GoodToGoCheck.run (cognitive 148), (anonymous) (cognitive 79), Uploader.uploadAndStoreImage (cognitive 76). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 5.6 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
19 god class(es) detected.
What to do
- Resolve the 6 TooManyMethods finding(s) in God Classes — start with ElasticSearch.scala (2), REDACTED, Mappings.scala. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 FunctionTooLong finding(s) in God Classes — start with delete-from-grid-step.tsx, crops-and-usages.tsx, gr-permissions-filter.tsx. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 FileTooLong finding(s) in God Classes — start with MediaApi.scala, ElasticSearch.scala, results.js. — One of this dimension's main actionable groups (4 warning-level).
D4 · Code Duplication
14 duplicated block group(s) detected. 1.7 % of the production lines (944 of 55,307) are in a reported copy. A further 27 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .ts (21% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 3 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with ImageResponse.scala (2), MediaLeaseController.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with ElasticSearch.scala, UsageApi.scala, UsageRecord.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with MediaApi.scala (2), MagickImageOperations.scala. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
11 production modules (npm+sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 0 module(s) off the main sequence, with abstractness counted on 2 of the 11 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
9 of 59 classes have LCOM4 above 3.
What to do
- Resolve the 9 Low cohesion finding(s) in Cohesion (LCOM4) — start with UsageApi.scala, VipsImageOperations.scala, UsageController.scala. — One of this dimension's main actionable groups (9 warning-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 109 tests. Measured on the JavaScript/TypeScript suite only — at least 103 test source file(s) (.scala) went unread, so its test quality is unmeasured and is not in these counts.
D12 · Dependency Hygiene
46 outdated direct sbt declarations. An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 53 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 1 sbt build file(s) (REDACTED and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. 1 further production coordinate(s) are declared with a version the build computes rather than writes as a literal — sbt is a program, and this pass does not run it — and are NOT graded: this verdict covers what the build pins literally or through a string-literal val, not the full graph. ★ COVERAGE OF THIS VERDICT: it grades this repository's sbt dependencies and nothing else. The repository also declares REDACTED, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: kahuna/public/js/takedown/delete-from-grid-step.tsx (10×43=430); media-api/app/controllers/MediaApi.scala (12×22=264); media-api/app/lib/elasticsearch/QueryBuilder.scala (9×26=234)
What to do
- Resolve the 6 Hotspot finding(s) in Churn × Complexity Hotspots — start with delete-from-grid-step.tsx, MediaApi.scala, QueryBuilder.scala. — One of this dimension's main actionable groups (6 warning-level).
D16 · Bus Factor
46 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is common-lib/src/main/scala/com/gu/mediaservice/lib/cleanup/PhotographerRenamer.scala. Counted over 201 of the 510 production source files in this repository: 294 are under the ~2,400-byte size floor this dimension measures over, and the remaining 15 have no attributable history left to measure.
What to do
- Resolve the 5 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (5 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
140 deducted task-comment markers across 55307 LoC (0.2/KLoC) → score 9.5. 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 115 TodoComment finding(s) in Explicit Debt — start with ElasticSearch.scala (10), MetadataCleaner.scala (10), ParserTest.scala (8). — One of this dimension's main actionable groups (115 warning-level).
- Resolve the 24 FixmeComment finding(s) in Explicit Debt — start with Permissions.scala (2), ImageLoaderController.scala (2), ImageMetadataConverter.scala (2). — One of this dimension's main actionable groups (24 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with Collection.scala. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 72 document(s) read across 8 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 REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
3 naming inconsistencies among 144 declarations measured against a convention their peers follow.
What to do
- Resolve the 2 `extractFixtureID` spells `ID` where 141 names in the project spell it… finding(s) in Naming Consistency — start with SupplierProcessors.scala (2). — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 `mediaID` spells `ID` where 141 names in the project spell it `Id` finding(s) in Naming Consistency — start with UsageNotifier.scala. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
6 of 467 judged comments only repeat the code they sit on (1.3 %). 15 comment(s) in another language or script were not judged.
What to do
- Resolve the 6 redundant comment finding(s) in Comment Value — start with usageRightsUtils.js, gr-confirmation-modal.tsx, gr-image-metadata.js. — One of this dimension's main actionable groups (6 recommendation-level).
D26 · Project Cohesion
2 of 8 build units (Python, npm, sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
1 finding(s): 0 critical, 1 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 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
53 finding(s): 0 critical, 27 high, 23 medium, 3 low. 20 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 11 file(s) — `dev/oidc-provider/app.js` (line 5), `dev/script/create-root-collection.sh` (line 20, line 25, line 35), `kahuna/app/views/main.scala.html` (lines 1–20, line 35, line 36, …), `kahuna/app/views/quotas.scala.html` (line 1, line 77), `thrall/app/views/index.scala.html` (lines 1–54, lines 74–78, lines 82–84, …), … (+6 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 20 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 (20 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
47 finding(s): 0 critical, 16 high, 22 medium, 9 low.
What to do
- Resolve the 22 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (22). — One of this dimension's main actionable groups (22 warning-level).
- Resolve the 15 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (13), REDACTED, REDACTED. — One of this dimension's main actionable groups (15 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
124 finding(s): 1 critical, 2 high, 120 medium, 1 low.
What to do
- Resolve the 120 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (99), REDACTED (12), REDACTED (7). — One of this dimension's main actionable groups (120 warning-level).
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Critical IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
42 of 216 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is scripts/src/main/java/com/gu/typesafe/config/impl/ConfigNodeObject.java. Counted over 216 of the 510 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 42 Orphaned file finding(s) in Knowledge Freshness — start with ConfigNodeObject.java, ConfigBeanImpl.java, ResolveSource.java. — One of this dimension's main actionable groups (42 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: ImageLoaderController.scala↔loader.js 91%; MessageProcessor.scala↔MessageTranslator.scala 73%; ImageOperations.scala↔ImageMagick.scala 71%
What to do
- Resolve the 10 Change coupling finding(s) in Change Coupling — start with ImageLoaderController.scala, MessageProcessor.scala, ImageOperations.scala. — One of this dimension's main actionable groups (10 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 5 platform declaration(s) and 2 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
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — kahuna/public/js/upload/jobs/upload-jobs.html:14
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — kahuna/app/views/quotas.scala.html:66
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×8) — kahuna/public/js/components/gr-collections-panel/gr-collections-panel-node.html:73, kahuna/public/js/components/gu-date-range/gu-date-range.html:60, kahuna/public/js/components/gu-date-range/gu-date-range.html:71, …
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — kahuna/public/js/components/gr-feature-switch-panel/gr-feature-switch-panel.tsx:109
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×9) — kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:397, kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:444, kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:616, …
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — kahuna/app/views/main.scala.html:22, kahuna/app/views/quotas.scala.html:3
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — kahuna/app/views/main.scala.html:22, thrall/app/views/migrationFailures.scala.html:1
- A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×3) — kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:244, kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:194, kahuna/public/js/components/gr-usagerights-summary/gr-usagerights-summary.tsx:116
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — thrall/app/views/reaper.scala.html:39
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×27) — REDACTED:11, kahuna/public/js/components/gr-collections-panel/gr-collections-panel-node.html:29, kahuna/public/js/components/gr-crop-image/gr-crop-image.html:2, …
- The repo's own CSS styles .clickable with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — kahuna/public/js/components/gr-batch-export-original-images/gr-batch-export-original-images.html:1
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. — kahuna/public/js/components/gr-confirmation-modal/gr-confirmation-modal.tsx:118
- This <div> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler. Give it a role as well, so assistive tech can announce what it is. (×2) — kahuna/public/js/components/gr-confirmation-modal/gr-confirmation-modal.tsx:123, kahuna/public/js/components/gr-confirmation-modal/gr-confirmation-modal.tsx:127
- The repo's own CSS styles .custom-checkbox with `cursor: pointer`, so this <span> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler. — kahuna/public/js/components/gr-my-uploads/gr-my-uploads.tsx:89
- This <div> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler. — kahuna/public/js/components/gr-notifications-banner/gr-notifications-banner.tsx:251
- A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. (×7) — kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:236, kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:247, kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:181, …
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.button` sets color: white on background-color: #00adee — 2.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — kahuna/public/stylesheets/main.css:453
- `.button-save` sets color: white on background-color: #00adee — 2.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — kahuna/public/stylesheets/main.css:499
- `.status` sets color: white on background-color: orange — 2.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — kahuna/public/stylesheets/main.css:908
- `.image-results-count__new` sets color: white on background-color: #00adee — 2.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — kahuna/public/stylesheets/main.css:1516
- `.result-editor__save-status--error` sets color: white on background-color: red — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — kahuna/public/stylesheets/main.css:2014
- `.dnd-uploader__info` sets color: white on background-color: #00adee — 2.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — kahuna/public/stylesheets/main.css:2820
- `.element--partial .element__value, .element--partial .element__add, .element--partial .element__right-bit` sets color: #00adee on background-color: white — 2.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — kahuna/public/js/edits/list-editor.css:27
- `.element__value, .element__right-bit` sets color: white on background-color: #00adee — 2.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — kahuna/public/js/edits/list-editor.css:33
- `.element__link:hover, .element__right-bit:hover` sets color: #00adee on background-color: white — 2.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — kahuna/public/js/edits/list-editor.css:40
- `.image-info .element__right-bit:hover, .image-info .element__value:hover` sets color: #00adee on background-color: white — 2.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — kahuna/public/js/edits/list-editor.css:46
- `.element button:active gr-icon` sets color: #333 on background-color: #008fc5 — 3.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — kahuna/public/js/edits/list-editor.css:75
- `.preset-label__value, .preset-label__remove` sets color: white on background-color: #00adee — 2.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — kahuna/public/js/components/gr-preset-labels/gr-preset-labels.css:27
- `.preset-label__link:hover, .preset-label__remove:hover` sets color: #00adee on background-color: white — 2.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — kahuna/public/js/components/gr-preset-labels/gr-preset-labels.css:34
- `.search` sets color: #aaa on background-color: #444 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — e2e-tests/feature-library/styles.css:86
- `.search-query__clear` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — kahuna/public/stylesheets/main.css:1110
- `.search__advanced-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — kahuna/public/stylesheets/main.css:1212
- `.image-info__wrap .editable-wrap .image-info__editor--error` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — kahuna/public/stylesheets/main.css:2458
- `.image-info__wrap .editable-wrap .image-info__editor--saving` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — kahuna/public/stylesheets/main.css:2463
- `.gr-tab` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — kahuna/public/js/components/gr-tab-swap/gr-tab-swap.css:23
- `.search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — e2e-tests/feature-library/styles.css:89
- `.loader:after` moves (`animation-name: flipper`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — kahuna/public/stylesheets/main.css:567
- `.saving` moves (`animation-name: spin`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — kahuna/public/stylesheets/main.css:592
- `.spin` moves (`animation-name: spin`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — kahuna/public/stylesheets/main.css:603
- `.gr-panel__content` moves (`transition: width 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — kahuna/public/js/components/gr-panels/gr-panels.css:26
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `Config` declares 55 abstract methods: `atKey`, `atPath`, `checkValid`, `entrySet`, `getAnyRef`, `getAnyRefList`, `getBoolean`, `getBooleanList`, `getBytes`, `getBytesList`, `getConfig`, `getConfigList`, `getDouble`, `getDoubleList`, `getDuration`, `getDuration`, `getDurationList`, `getDurationList`, `getEnum`, `getEnumList`, `getInt`, `getIntList`, `getIsNull`, `getList`, `getLong`, `getLongList`, `getMemorySize`, `getMemorySizeList`, `getMilliseconds`, `getMillisecondsList`, `getNanoseconds`, `getNanosecondsList`, `getNumber`, `getNumberList`, `getObject`, `getObjectList`, `getPeriod`, `getString`, `getStringList`, `getTemporal`, and 15 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 55 declarations carry 51 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 51 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — scripts/src/main/java/com/gu/typesafe/config/Config.java:168
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×12) — common-lib/src/test/scala/com/gu/mediaservice/lib/imaging/MagickImageOperationsTest.scala:16, common-lib/src/test/scala/com/gu/mediaservice/lib/imaging/VipsImageOperationsTest.scala:19, image-loader/test/scala/model/ImageUploadTest.scala:116, …
What to do
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
- The root README is 106 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P11 · BDD / executable specs
P2 · Observability
- Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `e2e-tests`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 6 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. — .github/workflows/check-labels.yaml:5
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `pip`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:4
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `pip` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
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.
PF3 · Async & latency hygiene
- `projectS3ImageById` is async and calls Await.result — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — image-loader/app/model/Projector.scala:86
What to do
- Scala: compose the Future or effect (map/flatMap, a for-comprehension) instead of Await.result or unsafeRunSync, and wrap unavoidable blocking calls in blocking { } (Future), IO.blocking or ZIO.attemptBlocking.
R1 · Type Safety
- 114 typed · 140 plain JS — the untyped files are cdk/jest.setup.js, dev/oidc-provider/app.js, dev/oidc-provider/find-account.js, dev/oidc-provider/find-account.test.js, dev/oidc-provider/make-provider.js, dev/script/generate-config/generate-config.js (+134 more).
R10 · Code Duplication
- 21 duplicated blocks under kahuna/public/js/components/ have copies in at least two of the sibling directories gr-add-keyword, gr-add-label, gr-archiver, gr-archiver-status, gr-batch-export-original-images, gr-confirmation-modal (+15 more sibling(s) not listed) — 12 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 21 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 21 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 21 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:20
- 15 duplicated blocks under kahuna/public/js/ have copies in at least two of the sibling directories components, crop, edits, image, leases, metadata-templates (+4 more sibling(s) not listed) — 9 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:600
- kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:20 · kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:16 — the two spans are one implementation copied and then locally edited — 454 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:20
- kahuna/public/js/lib/data-structure/list-factory.js:12 · kahuna/public/js/lib/data-structure/ordered-set-factory.js:12 — the two spans are one implementation copied and then locally edited — 312 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — kahuna/public/js/lib/data-structure/list-factory.js:12
- kahuna/public/js/components/gr-add-keyword/gr-add-keyword.js:66 · kahuna/public/js/components/gr-add-label/gr-add-label.js:27 — the two spans are one implementation copied and then locally edited — 255 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — kahuna/public/js/components/gr-add-keyword/gr-add-keyword.js:66
- kahuna/public/js/takedown/crops-and-usages.tsx:97 · kahuna/public/js/takedown/crops-and-usages.tsx:143 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — kahuna/public/js/takedown/crops-and-usages.tsx:97
- REDACTED:166 · REDACTED:203 — the two spans are one implementation copied and then locally edited — 107 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:166
- REDACTED:69 · kahuna/public/js/takedown/delete-from-grid-step.tsx:281 — the two spans are one implementation copied and then locally edited — 64 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:69
- kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:600 · kahuna/public/js/edits/image-editor.js:243 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:600
- kahuna/public/js/takedown/crops-and-usages.tsx:173 · kahuna/public/js/takedown/crops-and-usages.tsx:236 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — kahuna/public/js/takedown/crops-and-usages.tsx:173
- kahuna/public/js/components/gr-collection-overlay/gr-collection-overlay.js:23 · kahuna/public/js/edits/image-editor.js:383 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — kahuna/public/js/components/gr-collection-overlay/gr-collection-overlay.js:23
- kahuna/public/js/upload/dnd-uploader.js:12 · kahuna/public/js/upload/file-uploader.js:11 — the two spans are one implementation copied and then locally edited — 74 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — kahuna/public/js/upload/dnd-uploader.js:12
- kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:218 · kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:105 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:218
- kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:250 · kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:200 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:250
- kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:138 · kahuna/public/js/components/gr-tab-swap/gr-tab-swap.tsx:64 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:138
- kahuna/public/js/services/api/collections-api.js:122 · kahuna/public/js/services/archive.js:10 — the two spans are one implementation copied and then locally edited — 56 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — kahuna/public/js/services/api/collections-api.js:122
- kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:299 · kahuna/public/js/edits/image-editor.js:90 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:299
- kahuna/public/js/edits/image-editor.js:327 · kahuna/public/js/edits/image-editor.js:342 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — kahuna/public/js/edits/image-editor.js:327
- kahuna/public/js/image/controller.js:244 · kahuna/public/js/upload/controller.js:59 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — kahuna/public/js/image/controller.js:244
- cdk/lib/image-embedder-lambda.ts:77 · cdk/lib/image-embedder-lambda.ts:91 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — cdk/lib/image-embedder-lambda.ts:77
- dev/script/generate-config/service-config.js:131 · dev/script/generate-config/service-config.js:200 · dev/script/generate-config/service-config.js:241 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dev/script/generate-config/service-config.js:131
- kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:477 · kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:567 — the two spans are one implementation copied and then locally edited — 101 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:477
- kahuna/public/js/components/gr-notifications-banner/gr-notifications-banner.tsx:15 · kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:16 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — kahuna/public/js/components/gr-notifications-banner/gr-notifications-banner.tsx:15
- kahuna/public/js/components/gr-sort-control/gr-extended-sort-control.tsx:92 · kahuna/public/js/components/gr-sort-control/gr-sort-control.tsx:78 · kahuna/public/js/components/gr-tab-swap/gr-tab-swap.tsx:74 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — kahuna/public/js/components/gr-sort-control/gr-extended-sort-control.tsx:92
- kahuna/public/js/search/structured-query/query-suggestions.ts:203 · kahuna/public/js/search/structured-query/query-suggestions.ts:241 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — kahuna/public/js/search/structured-query/query-suggestions.ts:203
- kahuna/public/js/services/api/loader.js:4 · kahuna/public/js/services/api/media-cropper.js:4 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — kahuna/public/js/services/api/loader.js:4
- kahuna/public/js/upload/jobs/upload-jobs.js:192 · kahuna/public/js/upload/recent/recent-uploads.js:59 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — kahuna/public/js/upload/jobs/upload-jobs.js:192
- kahuna/public/js/components/gr-archiver-status/gr-archiver-status.js:27 · kahuna/public/js/components/gr-archiver/gr-archiver.js:47 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — kahuna/public/js/components/gr-archiver-status/gr-archiver-status.js:27
- kahuna/public/js/components/gr-delete-image/gr-delete-image.js:43 · kahuna/public/js/components/gr-undelete-image/gr-un-delete-image.js:37 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — kahuna/public/js/components/gr-delete-image/gr-delete-image.js:43
- kahuna/public/js/components/gr-my-uploads/gr-my-uploads.tsx:51 · kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:199 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — kahuna/public/js/components/gr-my-uploads/gr-my-uploads.tsx:51
- kahuna/public/js/usage-rights/usage-rights-editor.js:249 · kahuna/public/js/usage-rights/usage-rights-editor.js:261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — kahuna/public/js/usage-rights/usage-rights-editor.js:249
- kahuna/public/js/components/gr-add-keyword/gr-add-keyword.js:47 · kahuna/public/js/edits/image-editor.js:114 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — kahuna/public/js/components/gr-add-keyword/gr-add-keyword.js:47
- kahuna/public/js/components/gr-collection-overlay/gr-collection-overlay.js:24 · kahuna/public/js/components/gr-collections-panel/gr-collections-panel.js:74 · kahuna/public/js/edits/image-editor.js:384 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — kahuna/public/js/components/gr-collection-overlay/gr-collection-overlay.js:24
- kahuna/public/js/components/gr-notifications-banner/gr-notifications-banner.tsx:138 · kahuna/public/js/components/gr-notifications-banner/gr-notifications-banner.tsx:165 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — kahuna/public/js/components/gr-notifications-banner/gr-notifications-banner.tsx:138
- kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter-config.ts:52 · kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter-config.ts:64 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter-config.ts:52
- kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:197 · kahuna/public/js/upload/jobs/required-metadata-editor.js:63 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:197
- kahuna/public/js/components/gr-usagerights-summary/gr-usagerights-bbc.tsx:38 · kahuna/public/js/components/gr-usagerights-summary/gr-usagerights-bbc.tsx:47 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — kahuna/public/js/components/gr-usagerights-summary/gr-usagerights-bbc.tsx:38
- kahuna/public/js/search/structured-query/query-suggestions.ts:251 · kahuna/public/js/search/structured-query/query-suggestions.ts:269 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — kahuna/public/js/search/structured-query/query-suggestions.ts:251
- kahuna/public/js/services/api/leases.js:56 · kahuna/public/js/services/api/leases.js:84 — the two spans are one implementation copied and then locally edited — 53 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — kahuna/public/js/services/api/leases.js:56
- kahuna/public/js/components/gr-confirmation-modal/gr-confirmation-modal.tsx:8 · kahuna/public/js/components/gr-notifications-banner/gr-notifications-banner.tsx:40 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — kahuna/public/js/components/gr-confirmation-modal/gr-confirmation-modal.tsx:8
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- cdk/lib/image-cache-purger.ts:2 imports @guardian/cdk/lib/constructs/core, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — cdk/lib/image-cache-purger.ts:2
- cdk/lib/image-cache-purger.ts:3 imports @guardian/cdk/lib/constructs/lambda, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — cdk/lib/image-cache-purger.ts:3
- cdk/lib/image-embedder-lambda.ts:3 imports @guardian/cdk/lib/constructs/core, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — cdk/lib/image-embedder-lambda.ts:3
- cdk/lib/image-embedder-lambda.ts:4 imports @guardian/cdk/lib/constructs/core, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — cdk/lib/image-embedder-lambda.ts:4
- cdk/lib/image-embedder-lambda.ts:5 imports @guardian/cdk/lib/constructs/ec2, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — cdk/lib/image-embedder-lambda.ts:5
- cdk/lib/image-embedder-lambda.ts:6 imports @guardian/cdk/lib/constructs/lambda, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — cdk/lib/image-embedder-lambda.ts:6
- cdk/lib/image-embedder-lambda.ts:7 imports @guardian/cdk/lib/constructs/s3, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — cdk/lib/image-embedder-lambda.ts:7
- dev/script/generate-config/generate-config.js:7 imports json5/lib/register, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — dev/script/generate-config/generate-config.js:7
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
- (anonymous) has cyclomatic complexity 28 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — e2e-tests/feature-library/serve.ts:27
- watchSearchChange has cyclomatic complexity 21 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kahuna/public/js/search/query.js:315
- createLibrary has cyclomatic complexity 15 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — e2e-tests/feature-library/library.ts:279
- structureQuery has cyclomatic complexity 15 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kahuna/public/js/search/structured-query/syntax.ts:35
- (anonymous) has cyclomatic complexity 15 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kahuna/public/js/common/usageRightsUtils.js:5
- (anonymous) has cyclomatic complexity 15 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kahuna/public/js/components/gr-usagerights-summary/gr-usagerights-bbc.tsx:56
- manageUploadedBy has cyclomatic complexity 13 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kahuna/public/js/search/query.js:162
- ScenarioDetail has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — e2e-tests/feature-library/app.tsx:294
- (anonymous) has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kahuna/public/js/search/results.js:102
- save has cyclomatic complexity 11 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kahuna/public/js/leases/leases.js:59
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kahuna/public/js/search/query.js:694
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — e2e-tests/feature-library/app.test.ts:53
- onMetadataTemplateSelected has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:588
- handleArrowKeys has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:96
- TabControl has cyclomatic complexity 11 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kahuna/public/js/components/gr-tab-swap/gr-tab-swap.tsx:16
R3 · Large Files
- kahuna/public/js/search/results.js has 837 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — kahuna/public/js/search/results.js:1
- e2e-tests/steps/rights-and-restrictions/right-and-restrictions.ts has 825 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — e2e-tests/steps/rights-and-restrictions/right-and-restrictions.ts:1
- e2e-tests/setup/stack.ts has 811 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — e2e-tests/setup/stack.ts:1
- kahuna/public/js/search/query.js has 674 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — kahuna/public/js/search/query.js:1
- kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js has 594 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:1
- image-embedder-lambda/src/backfiller/freeImagesFilter.ts has 558 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — image-embedder-lambda/src/backfiller/freeImagesFilter.ts:1
- e2e-tests/feature-library/app.tsx has 499 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — e2e-tests/feature-library/app.tsx:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — kahuna/public/js/search/results.js:1, kahuna/public/js/search/query.js:1, kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
R7 · Dead Code
- 6 file(s) (~337 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — cdk
- This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. — e2e-tests/steps/search/search-free-text.steps.ts:13
R8 · Dependency Hygiene
- Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. — image-embedder-lambda/src/embedder/embedder.ts:3
- Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×5)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Web-Security Posture
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×3) — common-lib/src/main/java/com/gu/mediaservice/DeprecatedHashWrapper.java:13, common-lib/src/main/scala/com/gu/mediaservice/lib/MD5.scala:6, image-loader/app/lib/BodyParsers.scala:39
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `REDACTED` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — REDACTED:29
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 3 sites, not one: `common-lib/src/main/java/com/gu/mediaservice/DeprecatedHashWrapper.java:13` (Hashing.sha1), `common-lib/src/main/scala/com/gu/mediaservice/lib/MD5.scala:6` (MessageDigest.getInstance("MD5")), `image-loader/app/lib/BodyParsers.scala:39` (MessageDigest.getInstance("SHA-1")). Each is a separate decision — fixing only the line this row cites leaves the others in place.
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `JsonDiff.diff` is public and takes `a: JsValue` from its caller, and it calls itself at line 24 with a piece of `a`, not as a tail call the compiler turns into a loop — and nowhere in `JsonDiff.diff` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `JsonDiff.diff` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — common-lib/src/main/scala/com/gu/mediaservice/JsonDiff.scala:24
- `DynamoDB.jsonToAttributeValue` is public and takes `json: JsValue` from its caller, and it calls itself at line 237 with a piece of `json` (and at line 238), not as a tail call the compiler turns into a loop — and nowhere in `DynamoDB.jsonToAttributeValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `DynamoDB.jsonToAttributeValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — common-lib/src/main/scala/com/gu/mediaservice/lib/aws/DynamoDB.scala:237
- `DynamoDB.mapJsValue` is public and takes `jsValue: JsValue` from its caller, and it calls itself at line 272 with a piece of `jsValue`, not as a tail call the compiler turns into a loop — and nowhere in `DynamoDB.mapJsValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `DynamoDB.mapJsValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — common-lib/src/main/scala/com/gu/mediaservice/lib/aws/DynamoDB.scala:272
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
X2 · Cancellation propagation
- Only 0/3 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `upload` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — kahuna/public/js/upload/manager.js:106
- `queryElasticSearch` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — image-embedder-lambda/src/backfiller/elasticSearch.ts:40
- `getImageCount` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — image-counter-lambda/src/handler.ts:19
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `content` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — kahuna/public/js/quotas.js:5
- `icon.svg` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:49
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — kahuna/public/js/sentry/sentry.js:33
- `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — kahuna/public/js/components/gr-downloader/gr-downloader.js:123
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — kahuna/public/js/components/gr-collections-panel/gr-collections-panel.js:40
- `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — image-loader/app/lib/imaging/C2PADetector.scala:60
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `info` at line 21 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — common-lib/src/main/scala/com/gu/mediaservice/lib/S3ImageStorage.scala:21
- `info` at line 27 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — common-lib/src/main/scala/com/gu/mediaservice/lib/S3ImageStorage.scala:27
- `info` at line 32 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — common-lib/src/main/scala/com/gu/mediaservice/lib/S3ImageStorage.scala:32
- `info` at line 40 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — common-lib/src/main/scala/com/gu/mediaservice/lib/S3ImageStorage.scala:40
- `info` at line 50 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — common-lib/src/main/scala/com/gu/mediaservice/lib/S3ImageStorage.scala:50
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- No build over this repository's 358 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 47% | Weak — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 80% | Strong | Solid. |
| Maturity | 73% | Strong | Solid. |
| Readiness | 35% | Weak — gated by R4, P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 48% | Weak — gated by D29, D31, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 43% | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Strong | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 2 observation(s) recorded · 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'.
- X10 Duplicated predicate — 13 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'software.amazon.awssdk.services.dynamodb' (usage/app/model/UsageRecord.scala:3) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'software.amazon.awssdk.services.dynamodb' (usage/app/model/UsageRecord.scala:3) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'software.amazon.awssdk.services.dynamodb' (usage/app/model/UsageRecord.scala:3) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
Not included — 42 check(s) not relevant to this codebase
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — cerebro Pulling localstack Pulling elasticsearch Pulling elasticsearch Error Get "https://docker.elastic.co/v2/": Forbidden cerebro Error context canceled localstack Error context canceled Error response from daemon: Get "https://docker.elastic.co/v2/": Forbidden; the earlier `compose pull` step reported: oidc-provider Skipped - No image to be pulled imgops Skipped - No image to be pulled elasticsearch Pulling cerebro Pulling localstack Pulling elasticsearch Error Get "https://docker.elastic.co/v2/": Forbidden cerebro Error context canceled localstack Error context canceled Error response from daemon: Get "https://docker.elastic.co/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
- 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.
- 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"]`.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 1 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.
- 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 measured — polyglot repository, one half has no runner
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 301 value object(s); 4 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no 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 data present for 11 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- 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.
- SC1 Supply-chain hygiene — 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
- 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
- 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
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 83 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label kahuna/public/js/components/gr-collections-panel/gr-collections-panel-node.html:73
- <input> without a programmatic label kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:397
- <input> without a programmatic label kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:444
- <input> without a programmatic label kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:616
- <input> without a programmatic label kahuna/public/js/components/gu-date-range/gu-date-range.html:60
- <input> without a programmatic label kahuna/public/js/components/gu-date-range/gu-date-range.html:71
- <input> without a programmatic label kahuna/public/js/components/gu-date/gu-date.html:20
- <input> without a programmatic label kahuna/public/js/crop/view.html:14
- <input> without a programmatic label kahuna/public/js/crop/view.html:25
- <input> without a programmatic label kahuna/public/js/crop/view.html:38
- <input> without a programmatic label kahuna/public/js/crop/view.html:49
- <input> without a programmatic label kahuna/public/js/leases/leases.html:98
- <input> without a programmatic label thrall/app/views/index.scala.html:32
- <input> without a programmatic label thrall/app/views/index.scala.html:121
- Click handler on a non-interactive <div> kahuna/public/js/components/gr-confirmation-modal/gr-confirmation-modal.tsx:118
- Click handler on a non-interactive <div> kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:236
- Click handler on a non-interactive <div> kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:181
- Click handler on a non-interactive <div> kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:187
- Click handler on a non-interactive <div> kahuna/public/js/components/gr-tab-swap/gr-tab-swap.tsx:92
- Click handler on a non-interactive <div> kahuna/public/js/components/gr-tab-swap/gr-tab-swap.tsx:99
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Focusable <div> isn't keyboard-operable kahuna/public/js/components/gr-confirmation-modal/gr-confirmation-modal.tsx:123
- Focusable <div> isn't keyboard-operable kahuna/public/js/components/gr-confirmation-modal/gr-confirmation-modal.tsx:127
- Focusable <div> isn't keyboard-operable kahuna/public/js/components/gr-notifications-banner/gr-notifications-banner.tsx:251
- <textarea> without a programmatic label REDACTED:90
- <textarea> without a programmatic label REDACTED:100
- <html> without a lang kahuna/app/views/main.scala.html:22
- <html> without a lang kahuna/app/views/quotas.scala.html:3
- Clickable element isn't keyboard-operable kahuna/public/js/components/gr-batch-export-original-images/gr-batch-export-original-images.html:1
- Clickable element isn't keyboard-operable kahuna/public/js/components/gr-my-uploads/gr-my-uploads.tsx:89
- Click handler on a non-interactive <tr> kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:247
- Click handler on a non-interactive <tr> kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:197
- REDACTED
- REDACTED
- <img> without a text alternative kahuna/public/js/upload/jobs/upload-jobs.html:14
- Link with no accessible name kahuna/app/views/quotas.scala.html:66
- <button> with no accessible text kahuna/public/js/components/gr-feature-switch-panel/gr-feature-switch-panel.tsx:109
- <select> without a programmatic label kahuna/public/js/leases/leases.html:38
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import '@smithy/node-http-handler' image-embedder-lambda/src/embedder/embedder.ts:3
Serious — 650 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment usage/app/model/UsageGroup.scala:148
- TodoComment usage/app/lib/CrierEventProcessor.scala:142
- TodoComment thrall/test/lib/elasticsearch/ElasticSearchTest.scala:182
- TodoComment thrall/test/lib/elasticsearch/ElasticSearchTest.scala:186
- TodoComment thrall/test/lib/elasticsearch/ElasticSearchTest.scala:290
- TodoComment thrall/test/lib/elasticsearch/ElasticSearchTest.scala:805
- TodoComment thrall/test/lib/elasticsearch/ElasticSearchTestBase.scala:82
- TodoComment thrall/app/lib/SyncChecker.scala:69
- TodoComment thrall/app/lib/SyncChecker.scala:87
- TodoComment thrall/app/lib/elasticsearch/ElasticSearch.scala:479
- TodoComment thrall/app/lib/elasticsearch/ElasticSearch.scala:495
- TodoComment thrall/app/lib/elasticsearch/ElasticSearch.scala:548
- TodoComment thrall/app/lib/elasticsearch/ElasticSearch.scala:735
- TodoComment thrall/app/lib/elasticsearch/ElasticSearch.scala:871
- TodoComment thrall/app/lib/elasticsearch/ElasticSearch.scala:881
- TodoComment thrall/app/lib/elasticsearch/ElasticSearch.scala:872
- TodoComment thrall/app/lib/elasticsearch/ElasticSearch.scala:882
- TodoComment thrall/app/lib/elasticsearch/ThrallMigrationClient.scala:28
- TodoComment rest-lib/src/main/scala/com/gu/mediaservice/lib/auth/Authentication.scala:90
- TodoComment metadata-editor/app/model/UsageRightsProperty.scala:8
- TodoComment metadata-editor/app/model/UsageRightsProperty.scala:10
- TodoComment metadata-editor/app/controllers/EditsApi.scala:26
- TodoComment metadata-editor/app/controllers/EditsController.scala:31
- TodoComment metadata-editor/app/controllers/EditsController.scala:72
- TodoComment metadata-editor/app/controllers/EditsController.scala:202
- No test reaches this file kahuna/public/js/search/results.js:1
- No test reaches this file kahuna/public/js/search/query.js:1
- No test reaches this file kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:1
- No test reaches this file kahuna/public/js/edits/image-editor.js:1
- No test reaches this file kahuna/public/js/takedown/delete-from-grid-step.tsx:1
- No test reaches this file kahuna/public/js/edits/service.js:1
- No test reaches this file kahuna/public/js/components/gu-lazy-table/gu-lazy-table.js:1
- No test reaches this file kahuna/public/js/image/controller.js:1
- No test reaches this file kahuna/public/js/search/index.js:1
- No test reaches this file kahuna/public/js/leases/leases.js:1
- No test reaches this file kahuna/public/js/components/gr-collections-panel/gr-collections-panel.js:1
- No test reaches this file kahuna/public/js/usage-rights/usage-rights-editor.js:1
- No test reaches this file kahuna/public/js/search/structured-query/query-suggestions.ts:1
- No test reaches this file kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:1
- No test reaches this file kahuna/public/js/components/gr-notifications-banner/gr-notifications-banner.tsx:1
- No test reaches this file kahuna/public/js/crop/controller.js:1
- No test reaches this file kahuna/public/js/takedown/crops-and-usages.tsx:1
- No test reaches this file REDACTED:1
- No test reaches this file kahuna/public/js/takedown/takedown-context.tsx:1
- No test reaches this file kahuna/public/js/forms/datalist.js:1
- No test reaches this file kahuna/public/js/upload/jobs/upload-jobs.js:1
- No test reaches this file image-embedder-lambda/src/embedder/localRun.ts:1
- No test reaches this file kahuna/public/js/metadata-templates/metadata-templates.js:1
- No test reaches this file kahuna/public/js/services/api/leases.js:1
- No test reaches this file kahuna/public/js/edits/list-editor.js:1
- Anchor without href REDACTED:11
- Anchor without href kahuna/public/js/components/gr-collections-panel/gr-collections-panel-node.html:29
- Anchor without href kahuna/public/js/components/gr-crop-image/gr-crop-image.html:2
- Anchor without href kahuna/public/js/components/gr-crop-image/gr-crop-image.html:10
- Anchor without href kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:179
- Anchor without href kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:188
- Anchor without href kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:429
- Anchor without href kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:478
- Anchor without href kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:507
- Anchor without href kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:648
- Anchor without href kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:670
- Anchor without href kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:826
- Anchor without href kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:857
- Anchor without href kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:921
- Anchor without href kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:958
- Anchor without href kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:995
- Anchor without href kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:1031
- Anchor without href kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:1063
- Anchor without href kahuna/public/js/components/gr-image-metadata/gr-image-metadata.html:1072
- Anchor without href kahuna/public/js/components/gr-more-like-this/gr-more-like-this.html:2
- Anchor without href kahuna/public/js/components/gr-photoshoot/gr-photoshoot.html:25
- Anchor without href kahuna/public/js/components/gr-preset-labels/gr-preset-labels.html:6
- Anchor without href kahuna/public/js/crop/view.html:3
- Anchor without href kahuna/public/js/crop/view.html:107
- Anchor without href kahuna/public/js/edits/image-editor.html:8
- FixmeComment thrall/app/controllers/ThrallController.scala:256
- FixmeComment rest-lib/src/main/scala/com/gu/mediaservice/lib/guardian/auth/Permissions.scala:16
- FixmeComment rest-lib/src/main/scala/com/gu/mediaservice/lib/auth/Permissions.scala:21
- FixmeComment metadata-editor/app/controllers/EditsController.scala:29
- FixmeComment media-api/test/lib/querysyntax/ParserTest.scala:133
- FixmeComment media-api/app/controllers/MediaApi.scala:137
- FixmeComment kahuna/app/lib/KahunaConfig.scala:71
- FixmeComment image-loader/test/scala/model/ProjectorTest.scala:50
- FixmeComment image-loader/app/model/Uploader.scala:197
- FixmeComment image-loader/app/lib/imaging/FileMetadataReader.scala:60
- FixmeComment image-loader/app/controllers/ImageLoaderController.scala:485
- FixmeComment image-loader/app/controllers/ImageLoaderController.scala:491
- FixmeComment cropper/app/lib/CropStore.scala:77
- FixmeComment common-lib/src/main/scala/com/gu/mediaservice/syntax/MessageSubjects.scala:6
- FixmeComment common-lib/src/main/scala/com/gu/mediaservice/model/Asset.scala:9
- FixmeComment common-lib/src/main/scala/com/gu/mediaservice/model/Crop.scala:9
- FixmeComment common-lib/src/main/scala/com/gu/mediaservice/model/Image.scala:79
- FixmeComment common-lib/src/main/scala/com/gu/mediaservice/lib/metadata/ImageMetadataConverter.scala:98
- FixmeComment common-lib/src/main/scala/com/gu/mediaservice/lib/metadata/ImageMetadataConverter.scala:113
- FixmeComment common-lib/src/main/scala/com/gu/mediaservice/lib/cleanup/CapitaliseProperty.scala:20
- FixmeComment common-lib/src/main/scala/com/gu/mediaservice/lib/aws/DynamoDB.scala:266
- FixmeComment common-lib/src/main/scala/com/gu/mediaservice/lib/argo/ArgoHelpers.scala:15
- FixmeComment common-lib/src/main/scala/com/gu/mediaservice/lib/argo/ArgoHelpers.scala:38
- FixmeComment common-lib/src/main/scala/com/gu/mediaservice/lib/argo/model/CollectionResponse.scala:41
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Low contrast colour pair in CSS (2.6:1) kahuna/public/stylesheets/main.css:453
- Low contrast colour pair in CSS (2.6:1) kahuna/public/stylesheets/main.css:499
- Low contrast colour pair in CSS (2.6:1) kahuna/public/stylesheets/main.css:1516
- Low contrast colour pair in CSS (2.6:1) kahuna/public/stylesheets/main.css:2820
- Low contrast colour pair in CSS (2.6:1) kahuna/public/js/edits/list-editor.css:27
- Low contrast colour pair in CSS (2.6:1) kahuna/public/js/edits/list-editor.css:33
- Low contrast colour pair in CSS (2.6:1) kahuna/public/js/edits/list-editor.css:40
- Low contrast colour pair in CSS (2.6:1) kahuna/public/js/edits/list-editor.css:46
- Low contrast colour pair in CSS (2.6:1) kahuna/public/js/components/gr-preset-labels/gr-preset-labels.css:27
- Low contrast colour pair in CSS (2.6:1) kahuna/public/js/components/gr-preset-labels/gr-preset-labels.css:34
- Change coupling: ImageLoaderController.scala ↔ loader.js image-loader/app/controllers/ImageLoaderController.scala:1
- Change coupling: MessageProcessor.scala ↔ MessageTranslator.scala thrall/app/lib/kinesis/MessageProcessor.scala:1
- Change coupling: ImageOperations.scala ↔ ImageMagick.scala common-lib/src/main/scala/com/gu/mediaservice/lib/imaging/ImageOperations.scala:1
- Change coupling: jest.integration.config.ts ↔ embedder.ts image-embedder-lambda/jest.integration.config.ts:1
- Change coupling: results.js ↔ media-api.js kahuna/public/js/search/results.js:1
- Change coupling: KahunaConfig.scala ↔ window.ts kahuna/app/lib/KahunaConfig.scala:1
- Change coupling: gr-my-uploads.tsx ↔ gr-permissions-filter.tsx kahuna/public/js/components/gr-my-uploads/gr-my-uploads.tsx:1
- Change coupling: ThrallMessage.scala ↔ MessageSubjects.scala common-lib/src/main/scala/com/gu/mediaservice/model/ThrallMessage.scala:1
- Change coupling: query.js ↔ media-api.js kahuna/public/js/search/query.js:1
- Change coupling: UploadStatusTable.scala ↔ manager.js image-loader/app/lib/UploadStatusTable.scala:1
- Low cohesion: UsageApi (LCOM4 9) usage/app/controllers/UsageApi.scala:24
- Low cohesion: VipsImageOperations (LCOM4 6) common-lib/src/main/scala/com/gu/mediaservice/lib/imaging/VipsImageOperations.scala:17
- Low cohesion: UsageController (LCOM4 6) media-api/app/controllers/UsageController.scala:20
- Low cohesion: AuthController (LCOM4 5) auth/app/auth/AuthController.scala:20
- Low cohesion: MediaApi (LCOM4 5) media-api/app/controllers/MediaApi.scala:57
- Low cohesion: PandaAuthenticationProvider (LCOM4 5) rest-lib/src/main/scala/com/gu/mediaservice/lib/guardian/auth/PandaAuthenticationProvider.scala:23
- Low cohesion: CrierEventProcessor (LCOM4 5) usage/app/lib/CrierEventProcessor.scala:69
- Low cohesion: S3ImageStorage (LCOM4 4) common-lib/src/main/scala/com/gu/mediaservice/lib/S3ImageStorage.scala:15
- Low cohesion: MagickImageOperations (LCOM4 4) common-lib/src/main/scala/com/gu/mediaservice/lib/imaging/MagickImageOperations.scala:18
- Boundary violation [package:third-party-deep-import] cdk/lib/image-cache-purger.ts:2
- Boundary violation [package:third-party-deep-import] cdk/lib/image-cache-purger.ts:3
- Boundary violation [package:third-party-deep-import] cdk/lib/image-embedder-lambda.ts:3
- Boundary violation [package:third-party-deep-import] cdk/lib/image-embedder-lambda.ts:4
- Boundary violation [package:third-party-deep-import] cdk/lib/image-embedder-lambda.ts:5
- Boundary violation [package:third-party-deep-import] cdk/lib/image-embedder-lambda.ts:6
- Boundary violation [package:third-party-deep-import] cdk/lib/image-embedder-lambda.ts:7
- Boundary violation [package:third-party-deep-import] dev/script/generate-config/generate-config.js:7
- Focus outline removed in CSS without a :focus replacement kahuna/public/stylesheets/main.css:1110
- Focus outline removed in CSS without a :focus replacement kahuna/public/stylesheets/main.css:1212
- Focus outline removed in CSS without a :focus replacement kahuna/public/stylesheets/main.css:2458
- Focus outline removed in CSS without a :focus replacement kahuna/public/stylesheets/main.css:2463
- Focus outline removed in CSS without a :focus replacement kahuna/public/js/components/gr-tab-swap/gr-tab-swap.css:23
- Focus outline removed in CSS without a :focus replacement e2e-tests/feature-library/styles.css:89
- Hotspot: kahuna/public/js/takedown/delete-from-grid-step.tsx kahuna/public/js/takedown/delete-from-grid-step.tsx:88
- Hotspot: media-api/app/controllers/MediaApi.scala media-api/app/controllers/MediaApi.scala:633
- Hotspot: media-api/app/lib/elasticsearch/QueryBuilder.scala media-api/app/lib/elasticsearch/QueryBuilder.scala:82
- Hotspot: kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:79
- Hotspot: e2e-tests/feature-library/app.tsx e2e-tests/feature-library/app.tsx:381
- Hotspot: REDACTED REDACTED:58
- TooManyMethods: QuerySyntax REDACTED:10
- TooManyMethods: ElasticSearch thrall/app/lib/elasticsearch/ElasticSearch.scala:33
- TooManyMethods: Mappings common-lib/src/main/scala/com/gu/mediaservice/lib/elasticsearch/Mappings.scala:9
- TooManyMethods: MediaApi media-api/app/controllers/MediaApi.scala:57
- TooManyMethods: ImageResponse media-api/app/lib/ImageResponse.scala:23
- TooManyMethods: ElasticSearch media-api/app/lib/elasticsearch/ElasticSearch.scala:43
- FunctionTooLong: delete-from-grid-step.DeleteFromGridStep kahuna/public/js/takedown/delete-from-grid-step.tsx:88
- FunctionTooLong: crops-and-usages.CropsAndUsages kahuna/public/js/takedown/crops-and-usages.tsx:42
- FunctionTooLong: gr-permissions-filter.PermissionsFilter kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:79
- FunctionTooLong: base-sort-control.BaseSortControl kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:67
- FunctionTooLong: gr-notifications-banner.NotificationsBanner kahuna/public/js/components/gr-notifications-banner/gr-notifications-banner.tsx:116
- Duplicated block (12 lines × 2 locations) cdk/lib/image-embedder-lambda.ts:77
- Duplicated block (12 lines × 2 locations) kahuna/public/js/components/gr-notifications-banner/gr-notifications-banner.tsx:15
- Duplicated block (12 lines × 2 locations) kahuna/public/js/search/structured-query/query-suggestions.ts:203
- Duplicated block (12 lines × 2 locations) kahuna/public/js/services/api/loader.js:4
- Duplicated block (12 lines × 2 locations) kahuna/public/js/upload/jobs/upload-jobs.js:192
- Animation without a prefers-reduced-motion guard kahuna/public/stylesheets/main.css:567
- Animation without a prefers-reduced-motion guard kahuna/public/stylesheets/main.css:592
- Animation without a prefers-reduced-motion guard kahuna/public/stylesheets/main.css:603
- Animation without a prefers-reduced-motion guard kahuna/public/js/components/gr-panels/gr-panels.css:26
- (anonymous)::watchSearchChange (cognitive 29) kahuna/public/js/search/query.js:315
- (anonymous)::$onInit::save (cognitive 23) kahuna/public/js/leases/leases.js:59
- (anonymous)::manageUploadedBy (cognitive 23) kahuna/public/js/search/query.js:162
- (anonymous)::notificationMessages (cognitive 17) kahuna/public/js/search/results.js:420
- FileTooLong: controllers/MediaApi.scala media-api/app/controllers/MediaApi.scala
- FileTooLong: elasticsearch/ElasticSearch.scala thrall/app/lib/elasticsearch/ElasticSearch.scala
- FileTooLong: search/results.js kahuna/public/js/search/results.js
- FileTooLong: model/UsageRights.scala common-lib/src/main/scala/com/gu/mediaservice/model/UsageRights.scala
- Data table has no header cells kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:244
- Data table has no header cells kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:194
- Data table has no header cells kahuna/public/js/components/gr-usagerights-summary/gr-usagerights-summary.tsx:116
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (11 corresponding lines) media-api/app/lib/ImageResponse.scala:279
- Edited copy of a member (11 corresponding lines) leases/app/controllers/MediaLeaseController.scala:105
- Edited copy of a member (11 corresponding lines) media-api/app/lib/ImageResponse.scala:334
- Duplicated block (11 lines × 2) thrall/app/lib/elasticsearch/ElasticSearch.scala:571
- Duplicated block (11 lines × 2) usage/app/controllers/UsageApi.scala:241
- Duplicated block (11 lines × 2) usage/app/model/UsageRecord.scala:127
- Duplicated block (10 lines × 2) common-lib/src/main/scala/com/gu/mediaservice/lib/imaging/MagickImageOperations.scala:249
- Duplicated block (10 lines × 2) media-api/app/controllers/MediaApi.scala:267
- Duplicated block (10 lines × 2) media-api/app/controllers/MediaApi.scala:299
- Duplicated block (14 lines × 2 locations) kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:218
- Duplicated block (14 lines × 2 locations) kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:250
- Duplicated block (14 lines × 2 locations) kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:138
- Duplicated block (13 lines × 2 locations) kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:299
- Duplicated block (13 lines × 2 locations) kahuna/public/js/edits/image-editor.js:327
- Duplicated block (13 lines × 2 locations) kahuna/public/js/image/controller.js:244
- Duplicated block (10 lines × 2 locations) kahuna/public/js/components/gr-delete-image/gr-delete-image.js:43
- Duplicated block (10 lines × 2 locations) kahuna/public/js/components/gr-my-uploads/gr-my-uploads.tsx:51
- Duplicated block (10 lines × 2 locations) kahuna/public/js/usage-rights/usage-rights-editor.js:249
- Duplicated block (8 lines × 2 locations) kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:197
- Duplicated block (8 lines × 2 locations) kahuna/public/js/components/gr-usagerights-summary/gr-usagerights-bbc.tsx:38
- Duplicated block (8 lines × 2 locations) kahuna/public/js/search/structured-query/query-suggestions.ts:251
- Weak hash algorithm common-lib/src/main/java/com/gu/mediaservice/DeprecatedHashWrapper.java:13
- Weak hash algorithm common-lib/src/main/scala/com/gu/mediaservice/lib/MD5.scala:6
- Weak hash algorithm image-loader/app/lib/BodyParsers.scala:39
- Recursive walk over a caller-supplied document has no depth cap common-lib/src/main/scala/com/gu/mediaservice/JsonDiff.scala:24
- Recursive walk over a caller-supplied document has no depth cap common-lib/src/main/scala/com/gu/mediaservice/lib/aws/DynamoDB.scala:237
- Recursive walk over a caller-supplied document has no depth cap common-lib/src/main/scala/com/gu/mediaservice/lib/aws/DynamoDB.scala:272
- Async function without AbortSignal: upload kahuna/public/js/upload/manager.js:106
- Async function without AbortSignal: queryElasticSearch image-embedder-lambda/src/backfiller/elasticSearch.ts:40
- Async function without AbortSignal: getImageCount image-counter-lambda/src/handler.ts:19
- Page without a main landmark kahuna/app/views/main.scala.html:22
- Page without a main landmark thrall/app/views/migrationFailures.scala.html:1
- (anonymous) (cyclomatic 34) kahuna/public/js/image/controller.js:91
- (anonymous) (cyclomatic 34) kahuna/public/js/leases/leases.js:31
- (anonymous) (cognitive 18) kahuna/public/js/edits/list-editor.js:26
- (anonymous) (cognitive 18) kahuna/public/js/preview/image.js:47
- MethodTooLong: MediaApi.imageSearch media-api/app/controllers/MediaApi.scala:633
- MethodTooLong: ImageEmbedder.constructor cdk/lib/image-embedder-lambda.ts:36
- ClassTooLong: ElasticSearch media-api/app/lib/elasticsearch/ElasticSearch.scala:43
- ClassTooLong: query kahuna/public/js/search/query.js:1
- Edited copy of a member (24 corresponding lines) thrall/app/lib/elasticsearch/ElasticSearch.scala:417
- Edited copy of a member (24 corresponding lines) thrall/app/lib/elasticsearch/ElasticSearch.scala:479
- Edited copy of a member (17 corresponding lines) thrall/app/lib/elasticsearch/ElasticSearch.scala:724
- Edited copy of a member (17 corresponding lines) common-lib/src/main/scala/com/gu/mediaservice/lib/imaging/VipsImageOperations.scala:240
- Edited copy of a member (14 corresponding lines) media-api/app/controllers/UsageController.scala:24
- Edited copy of a member (14 corresponding lines) media-api/app/lib/ContentApi.scala:71
- Edited copy of a member (9 corresponding lines) common-lib/src/main/scala/com/gu/mediaservice/GridClient.scala:152
- Edited copy of a member (9 corresponding lines) media-api/app/controllers/SuggestionController.scala:25
- Edited copy of a member (15 corresponding lines) thrall/app/lib/kinesis/ThrallEventConsumer.scala:87
- Edited copy of a member (15 corresponding lines) common-lib/src/main/scala/com/gu/mediaservice/lib/logging/Stopwatch.scala:37
- Duplicated block (5 lines × 2) thrall/app/lib/elasticsearch/ElasticSearch.scala:873
- Duplicated block (5 lines × 2) media-api/app/lib/elasticsearch/ElasticSearch.scala:220
- Runner config excludes tests no gate runs image-embedder-lambda/jest.config.ts:10
- Runner config excludes tests no gate runs image-embedder-lambda/jest.config.ts:11
- Duplicated block (12 lines × 3 locations) dev/script/generate-config/service-config.js:131
- Duplicated block (12 lines × 3 locations) kahuna/public/js/components/gr-sort-control/gr-extended-sort-control.tsx:92
- Duplicated block (9 lines × 2 locations) kahuna/public/js/components/gr-notifications-banner/gr-notifications-banner.tsx:138
- Duplicated block (9 lines × 2 locations) kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter-config.ts:52
- Untrusted text written into markup unescaped kahuna/public/js/quotas.js:5
- Untrusted text written into markup unescaped REDACTED:49
- Swallowed exception (caught, then discarded) kahuna/public/js/sentry/sentry.js:33
- Swallowed exception (caught, then discarded) image-loader/app/lib/imaging/C2PADetector.scala:60
- Swallowed exception (empty catch) kahuna/public/js/components/gr-downloader/gr-downloader.js:123
- Swallowed exception (empty catch) kahuna/public/js/components/gr-collections-panel/gr-collections-panel.js:40
- Heading level jumps from h1 to h3 thrall/app/views/reaper.scala.html:39
- Low contrast colour pair in CSS (2.0:1) kahuna/public/stylesheets/main.css:908
- Low contrast colour pair in CSS (4.0:1) kahuna/public/stylesheets/main.css:2014
- Low contrast colour pair in CSS (3.5:1) kahuna/public/js/edits/list-editor.css:75
- Low contrast colour pair in CSS (4.2:1) e2e-tests/feature-library/styles.css:86
- (anonymous) (cyclomatic 100) kahuna/public/js/search/results.js:102
- (anonymous) (cyclomatic 78) kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:47
- delete-from-grid-step.DeleteFromGridStep (cyclomatic 43) kahuna/public/js/takedown/delete-from-grid-step.tsx:88
- (anonymous) (cyclomatic 43) kahuna/public/js/edits/image-editor.js:49
- (anonymous) (cyclomatic 38) kahuna/public/js/usage-rights/usage-rights-editor.js:31
- base-sort-control.BaseSortControl (cyclomatic 36) kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:67
- MessageTranslator.translate (cyclomatic 35) thrall/app/lib/kinesis/MessageTranslator.scala:9
- (anonymous) (cyclomatic 35) kahuna/public/js/metadata-templates/metadata-templates.js:26
- gr-permissions-filter.PermissionsFilter (cyclomatic 33) kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:79
- QueryBuilder.makeQueryBit (cyclomatic 26) media-api/app/lib/elasticsearch/QueryBuilder.scala:82
- Controller (cyclomatic 23) kahuna/public/js/components/gr-downloader/gr-downloader.js:23
- MagickImageOperations.identifyColourModel (cyclomatic 22) common-lib/src/main/scala/com/gu/mediaservice/lib/imaging/MagickImageOperations.scala:232
- MediaApi.imageSearch (cyclomatic 22) media-api/app/controllers/MediaApi.scala:633
- (anonymous) (cyclomatic 21) kahuna/public/js/preview/image.js:47
- (anonymous)::watchSearchChange (cyclomatic 21) kahuna/public/js/search/query.js:315
- GoodToGoCheck.run (cyclomatic 20) thrall/app/lib/elasticsearch/GoodToGoCheck.scala:18
- (anonymous).link (cyclomatic 20) kahuna/public/js/forms/datalist.js:115
- (anonymous) (cyclomatic 20) kahuna/public/js/upload/jobs/upload-jobs.js:30
- gr-usagerights-summary.UsageRightsSummary (cyclomatic 18) kahuna/public/js/components/gr-usagerights-summary/gr-usagerights-summary.tsx:27
- (anonymous) (cyclomatic 18) kahuna/public/js/crop/controller.js:34
- gr-tab-swap.TabControl (cyclomatic 17) kahuna/public/js/components/gr-tab-swap/gr-tab-swap.tsx:16
- Uploader.uploadAndStoreImage (cyclomatic 16) image-loader/app/model/Uploader.scala:129
- gr-confirmation-modal.confirmationModal (cyclomatic 16) kahuna/public/js/components/gr-confirmation-modal/gr-confirmation-modal.tsx:16
- delete-from-content-step.DeleteFromContentStep (cyclomatic 16) REDACTED:58
- HackComment common-lib/src/main/scala/com/gu/mediaservice/model/Collection.scala:29
- GoodToGoCheck.run (cognitive 148) thrall/app/lib/elasticsearch/GoodToGoCheck.scala:18
- (anonymous) (cognitive 79) kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:47
- Uploader.uploadAndStoreImage (cognitive 76) image-loader/app/model/Uploader.scala:129
- MessageTranslator.translate (cognitive 53) thrall/app/lib/kinesis/MessageTranslator.scala:9
- (anonymous) (cognitive 52) kahuna/public/js/edits/image-editor.js:49
- (anonymous) (cognitive 45) kahuna/public/js/usage-rights/usage-rights-editor.js:31
- delete-from-grid-step.DeleteFromGridStep (cognitive 44) kahuna/public/js/takedown/delete-from-grid-step.tsx:88
- (anonymous) (cognitive 43) kahuna/public/js/metadata-templates/metadata-templates.js:26
- ImageDataMerger.aggregate (cognitive 36) common-lib/src/main/scala/com/gu/mediaservice/ImageDataMerger.scala:11
- UsageGroupOps.extractCartoonUniqueMediaIds (cognitive 36) usage/app/model/UsageGroup.scala:229
- gr-permissions-filter.PermissionsFilter (cognitive 36) kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:79
- base-sort-control.BaseSortControl (cognitive 35) kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:67
- (anonymous) (cognitive 34) kahuna/public/js/image/controller.js:91
- QueryBuilder.makeQueryBit (cognitive 31) media-api/app/lib/elasticsearch/QueryBuilder.scala:82
- Syndication.publishChangedSyndicationRightsForPhotoshoot (cognitive 31) metadata-editor/app/lib/Syndication.scala:28
- MediaApi.imageSearch (cognitive 30) media-api/app/controllers/MediaApi.scala:633
- gr-usagerights-summary.UsageRightsSummary (cognitive 26) kahuna/public/js/components/gr-usagerights-summary/gr-usagerights-summary.tsx:27
- (anonymous) (cognitive 25) kahuna/public/js/upload/jobs/upload-jobs.js:30
- (anonymous).link (cognitive 22) kahuna/public/js/forms/datalist.js:115
- CropperController.executeRequest (cognitive 21) cropper/app/controllers/CropperController.scala:162
- Crops.makeExport (cognitive 21) cropper/app/lib/Crops.scala:109
- MagickImageOperations.identifyColourModel (cognitive 20) common-lib/src/main/scala/com/gu/mediaservice/lib/imaging/MagickImageOperations.scala:232
- (anonymous) (cognitive 20) kahuna/public/js/crop/controller.js:34
- Controller (cognitive 20) kahuna/public/js/components/gr-downloader/gr-downloader.js:23
- QueryBuilder.makeQuery (cognitive 19) media-api/app/lib/elasticsearch/QueryBuilder.scala:155
- syntax.structureQuery (cognitive 19) kahuna/public/js/search/structured-query/syntax.ts:35
- gr-confirmation-modal.confirmationModal (cognitive 18) kahuna/public/js/components/gr-confirmation-modal/gr-confirmation-modal.tsx:16
- CropperController.getCrops (cognitive 17) cropper/app/controllers/CropperController.scala:108
- CropStore.listCrops (cognitive 16) cropper/app/lib/CropStore.scala:29
- Uploader.getStorableOptimisedImage (cognitive 16) image-loader/app/model/Uploader.scala:210
- MediaApi.downloadImageExport (cognitive 16) media-api/app/controllers/MediaApi.scala:332
- ThrallMigrationClient.completeMigration (cognitive 16) thrall/app/lib/elasticsearch/ThrallMigrationClient.scala:93
- CrierEventProcessor.processEvent (cognitive 16) usage/app/lib/CrierEventProcessor.scala:122
- takedown-context.TakedownContextProvider (cognitive 16) kahuna/public/js/takedown/takedown-context.tsx:90
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) media-api/app/controllers/MediaApi.scala:265
- Edited copies of one member (4 members, 22+ corresponding lines) usage/app/controllers/UsageApi.scala:191
- Edited copy of a member (16 corresponding lines) usage/app/model/UsageRecord.scala:123
- Edited copy of a member (21 corresponding lines) usage/app/model/UsageGroup.scala:175
- Edited copy of a member (13 corresponding lines) media-api/app/controllers/MediaApi.scala:184
- Edited copies of one member (4 members, 17+ corresponding lines) thrall/app/lib/elasticsearch/ElasticSearch.scala:244
- Edited copies of one member (7 members, 9+ corresponding lines) common-lib/src/main/scala/com/gu/mediaservice/GridClient.scala:162
- Edited copies of one member (3 members, 6+ corresponding lines) common-lib/src/main/scala/com/gu/mediaservice/lib/argo/model/EmbeddedEntity.scala:20
- Edited copy of a member (8 corresponding lines) thrall/app/lib/elasticsearch/ElasticSearch.scala:872
- Edited copies of one member (3 members, 13+ corresponding lines) thrall/app/lib/elasticsearch/ElasticSearch.scala:566
- Edited copy of a member (10 corresponding lines) thrall/app/controllers/ReaperController.scala:226
- Edited copy of a member (7 corresponding lines) thrall/app/lib/kinesis/MessageProcessor.scala:58
- Edited copy of a member (6 corresponding lines) metadata-editor/app/controllers/SyndicationController.scala:40
- Edited copy of a member (19 corresponding lines) usage/app/lib/MediaUsageBuilder.scala:84
- Duplicated block (11–13 lines × 2) media-api/app/controllers/MediaApi.scala:366
- Duplicated block (11–12 lines × 2) common-lib/src/main/scala/com/gu/mediaservice/lib/elasticsearch/Mappings.scala:83
- Duplicated block (12 lines × 2) thrall/app/lib/elasticsearch/ElasticSearch.scala:430
- Duplicated block (8–10 lines × 3) media-api/app/controllers/MediaApi.scala:431
- Duplicated block (9 lines × 4) media-api/app/controllers/MediaApi.scala:265
- Duplicated block (8 lines × 2) media-api/app/lib/elasticsearch/ElasticSearchModel.scala:117
- No DR/backup evidence
- Sync-over-async blocking image-loader/app/model/Projector.scala:86
- Type Safety
- Duplication concentrated across 21 sibling directories (21 clone groups) kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:20
- Duplication concentrated across 10 sibling directories (15 clone groups) kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:600
- Duplicated block with local edits (67 matched lines × 2 locations) kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:20
- Duplicated block with local edits (50 matched lines × 2 locations) kahuna/public/js/lib/data-structure/list-factory.js:12
- Duplicated block with local edits (44 matched lines × 2 locations) kahuna/public/js/components/gr-add-keyword/gr-add-keyword.js:66
- Duplicated block (31 lines × 2 locations) kahuna/public/js/takedown/crops-and-usages.tsx:97
- Duplicated block with local edits (29 matched lines × 2 locations) REDACTED:166
- Duplicated block with local edits (19 matched lines × 2 locations) REDACTED:69
- Duplicated block (17 lines × 2 locations) kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:600
- Duplicated block (16 lines × 2 locations) kahuna/public/js/takedown/crops-and-usages.tsx:173
- Duplicated block (15 lines × 2 locations) kahuna/public/js/components/gr-collection-overlay/gr-collection-overlay.js:23
- Duplicated block with local edits (15 matched lines × 2 locations) kahuna/public/js/upload/dnd-uploader.js:12
- Duplicated block with local edits (14 matched lines × 2 locations) kahuna/public/js/services/api/collections-api.js:122
- Duplicated block with local edits (12 matched lines × 2 locations) kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:477
- Duplicated block (11 lines × 2 locations) kahuna/public/js/components/gr-archiver-status/gr-archiver-status.js:27
- Duplicated block with local edits (9 matched lines × 2 locations) kahuna/public/js/components/gr-add-keyword/gr-add-keyword.js:47
- Duplicated block (9 lines × 3 locations) kahuna/public/js/components/gr-collection-overlay/gr-collection-overlay.js:24
- Duplicated block with local edits (8 matched lines × 2 locations) kahuna/public/js/services/api/leases.js:56
- Duplicated block (7 lines × 2 locations) kahuna/public/js/components/gr-confirmation-modal/gr-confirmation-modal.tsx:8
- Complex function (anonymous) (cyclomatic 28, cognitive 35) e2e-tests/feature-library/serve.ts:27
- Complex function watchSearchChange (cyclomatic 21, cognitive 29) kahuna/public/js/search/query.js:315
- Complex function createLibrary (cyclomatic 15, cognitive 41) e2e-tests/feature-library/library.ts:279
- Complex function structureQuery (cyclomatic 15, cognitive 19) kahuna/public/js/search/structured-query/syntax.ts:35
- Complex function (anonymous) (cyclomatic 15, cognitive 13) kahuna/public/js/common/usageRightsUtils.js:5
- Complex function (anonymous) (cyclomatic 15, cognitive 12) kahuna/public/js/components/gr-usagerights-summary/gr-usagerights-bbc.tsx:56
- Complex function manageUploadedBy (cyclomatic 13, cognitive 23) kahuna/public/js/search/query.js:162
- Complex function ScenarioDetail (cyclomatic 13, cognitive 12) e2e-tests/feature-library/app.tsx:294
- Complex function (anonymous) (cyclomatic 13, cognitive 11) kahuna/public/js/search/results.js:102
- Complex function save (cyclomatic 11, cognitive 23) kahuna/public/js/leases/leases.js:59
- Complex function (anonymous) (cyclomatic 11, cognitive 18) kahuna/public/js/search/query.js:694
- Complex function (anonymous) (cyclomatic 11, cognitive 15) e2e-tests/feature-library/app.test.ts:53
- Complex function onMetadataTemplateSelected (cyclomatic 11, cognitive 13) kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:588
- Complex function handleArrowKeys (cyclomatic 11, cognitive 13) kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:96
- Complex function TabControl (cyclomatic 11, cognitive 9) kahuna/public/js/components/gr-tab-swap/gr-tab-swap.tsx:16
- kahuna/public/js/search/results.js: 837 lines of code kahuna/public/js/search/results.js:1
- e2e-tests/steps/rights-and-restrictions/right-and-restrictions.ts: 825 lines of code e2e-tests/steps/rights-and-restrictions/right-and-restrictions.ts:1
- e2e-tests/setup/stack.ts: 811 lines of code e2e-tests/setup/stack.ts:1
- kahuna/public/js/search/query.js: 674 lines of code kahuna/public/js/search/query.js:1
- kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js: 594 lines of code kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:1
- image-embedder-lambda/src/backfiller/freeImagesFilter.ts: 558 lines of code image-embedder-lambda/src/backfiller/freeImagesFilter.ts:1
- e2e-tests/feature-library/app.tsx: 499 lines of code e2e-tests/feature-library/app.tsx:1
- Unused dependency 'angular-animate'
- Unused dependency 'imagemin-svgo'
- Unused dependency 'panda-session'
- Unused dependency 'theseus-angular'
- Unused dependency 'uri-templates'
Minor — 121 finding(s)
- Orphaned file scripts/src/main/java/com/gu/typesafe/config/impl/ConfigNodeObject.java:1
- Orphaned file scripts/src/main/java/com/gu/typesafe/config/impl/ConfigBeanImpl.java:1
- Orphaned file scripts/src/main/java/com/gu/typesafe/config/impl/ResolveSource.java:1
- Orphaned file scripts/src/main/java/com/gu/typesafe/config/impl/ConfigConcatenation.java:1
- Orphaned file scripts/src/main/java/com/gu/typesafe/config/impl/ResolveContext.java:1
- Orphaned file scripts/src/main/scala/com/gu/mediaservice/scripts/ProposeS3Changes.scala:1
- Orphaned file usage/app/model/UsageGroup.scala:1
- Orphaned file common-lib/src/main/scala/com/gu/mediaservice/lib/config/ProviderLoader.scala:1
- Orphaned file collections/app/controllers/CollectionsController.scala:1
- Orphaned file scripts/src/main/java/com/gu/typesafe/config/impl/ConfigReference.java:1
- Orphaned file thrall/app/lib/elasticsearch/GoodToGoCheck.scala:1
- Orphaned file scripts/src/main/scala/com/gu/mediaservice/scripts/BackfillEditLastModified.scala:1
- Orphaned file rest-lib/src/main/scala/com/gu/mediaservice/lib/auth/provider/AuthenticationProvider.scala:1
- Orphaned file scripts/src/main/scala/com/gu/mediaservice/scripts/EsImageMetadata.scala:1
- Orphaned file kahuna/public/js/components/gr-feature-switch-panel/gr-feature-switch-panel.tsx:1
- Orphaned file kahuna/app/lib/MetadataTemplateConfig.scala:1
- Orphaned file common-lib/src/main/scala/com/gu/mediaservice/model/FileMetadataAggregator.scala:1
- Orphaned file media-api/app/lib/ImagePersistenceReasons.scala:1
- Orphaned file media-api/app/lib/ImageExtras.scala:1
- Orphaned file scripts/src/main/java/com/gu/typesafe/config/impl/BadMap.java:1
- Orphaned file common-lib/src/main/scala/com/gu/mediaservice/model/Edits.scala:1
- Orphaned file scripts/src/main/java/com/gu/typesafe/config/parser/ConfigDocument.java:1
- Orphaned file scripts/src/main/java/com/gu/typesafe/config/impl/ConfigNodeRoot.java:1
- Orphaned file rest-lib/src/main/scala/com/gu/mediaservice/lib/auth/Authorisation.scala:1
- Orphaned file common-lib/src/main/scala/com/gu/mediaservice/lib/aws/ThrallMessageSender.scala:1
- Duplicated predicate kahuna/public/js/image/controller.js:162
- Duplicated predicate kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:247
- Duplicated predicate kahuna/public/js/components/gu-lazy-table/gu-lazy-table.js:315
- Duplicated predicate kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:211
- Duplicated predicate kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:222
- Duplicated predicate kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:98
- Duplicated predicate kahuna/public/js/components/gr-metadata-validity/gr-metadata-validity.js:27
- Duplicated predicate kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:52
- Duplicated predicate kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:56
- Duplicated predicate kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:58
- Duplicated predicate kahuna/public/js/components/gr-sort-control/base-sort-control.tsx:147
- Duplicated predicate image-embedder-lambda/src/backfiller/localRun.ts:8
- Duplicated predicate kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:64
- Disabled test common-lib/src/test/scala/com/gu/mediaservice/lib/imaging/MagickImageOperationsTest.scala:16
- Disabled test common-lib/src/test/scala/com/gu/mediaservice/lib/imaging/VipsImageOperationsTest.scala:19
- Disabled test image-loader/test/scala/model/ImageUploadTest.scala:116
- Disabled test image-loader/test/scala/model/ImageUploadTest.scala:119
- Disabled test image-loader/test/scala/model/ImageUploadTest.scala:122
- Disabled test image-loader/test/scala/model/ImageUploadTest.scala:125
- Disabled test image-loader/test/scala/model/ImageUploadTest.scala:128
- Disabled test image-loader/test/scala/model/ImageUploadTest.scala:131
- Disabled test image-loader/test/scala/model/ImageUploadTest.scala:134
- Disabled test image-loader/test/scala/model/ImageUploadTest.scala:137
- Disabled test image-loader/test/scala/model/ImageUploadTest.scala:145
- Disabled test image-loader/test/scala/model/ProjectorTest.scala:53
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- redundant comment kahuna/public/js/common/usageRightsUtils.js:29
- redundant comment kahuna/public/js/components/gr-confirmation-modal/gr-confirmation-modal.tsx:96
- redundant comment kahuna/public/js/components/gr-image-metadata/gr-image-metadata.js:470
- redundant comment kahuna/public/js/components/gr-my-uploads/gr-my-uploads.tsx:29
- redundant comment kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter-util.ts:4
- redundant comment kahuna/public/js/components/gr-permissions-filter/gr-permissions-filter.tsx:74
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- Off-boarding risk: anonymized user #4
- Off-boarding risk: anonymized user #5
- Interpolated log message defeats structured logging common-lib/src/main/scala/com/gu/mediaservice/lib/S3ImageStorage.scala:21
- Interpolated log message defeats structured logging common-lib/src/main/scala/com/gu/mediaservice/lib/S3ImageStorage.scala:27
- Interpolated log message defeats structured logging common-lib/src/main/scala/com/gu/mediaservice/lib/S3ImageStorage.scala:32
- Interpolated log message defeats structured logging common-lib/src/main/scala/com/gu/mediaservice/lib/S3ImageStorage.scala:40
- Interpolated log message defeats structured logging common-lib/src/main/scala/com/gu/mediaservice/lib/S3ImageStorage.scala:50
- `extractFixtureID` spells `ID` where 141 names in the project spell it `Id` common-lib/src/main/scala/com/gu/mediaservice/lib/cleanup/SupplierProcessors.scala:90
- `extractFixtureID` spells `ID` where 141 names in the project spell it `Id` common-lib/src/main/scala/com/gu/mediaservice/lib/cleanup/SupplierProcessors.scala:560
- Fat interface: Config (55 abstract methods) scripts/src/main/java/com/gu/typesafe/config/Config.java:168
- Further sole-owners (lower concentration)
- No ADRs found REDACTED:247
- `mediaID` spells `ID` where 141 names in the project spell it `Id` usage/app/lib/UsageNotifier.scala:18
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- Thin README README.md:1
- No ADRs
- Logging is not universal
- No SAST .github/workflows/check-labels.yaml:5
- Dependabot does not watch pip REDACTED:4
- No rollback/health safety
- No changelog
- Unused module-local declaration 'enabledDisabled' e2e-tests/steps/search/search-free-text.steps.ts:13
- No security response headers detected REDACTED:29
- Not all async functions that make a request accept an AbortSignal
- Scala's null is not held to the type system everywhere
- Pending state with no failure state REDACTED:71
- Silent fallback default in catch common-lib/src/main/scala/com/gu/mediaservice/lib/aws/SqsHelpers.scala:13
Minor — 47 finding(s)
- Outdated: app.photofox.vips-ffm:vips-ffm-core
- Outdated: at.yawk.lz4:lz4-java
- Outdated: com.amazonaws:aws-lambda-java-core
- Outdated: com.beust:jcommander
- Outdated: com.drewnoakes:metadata-extractor
- Outdated: com.fasterxml.jackson.core:jackson-annotations
- Outdated: com.fasterxml.jackson.core:jackson-databind
- Outdated: com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-core_2.13
- Outdated: com.google.guava:guava
- Outdated: com.google.protobuf:protobuf-java
- Outdated: com.gu:content-api-client-default_2.13
- Outdated: com.gu:editorial-permissions-client_2.13
- Outdated: com.gu:kcl-pekko-stream_2.13
- Outdated: com.gu:pan-domain-auth-play_3-0_2.13
- Outdated: com.typesafe.scala-logging:scala-logging_2.13
- Outdated: net.logstash.logback:logstash-logback-encoder
- Outdated: nl.gn0s1s:elastic4s-client-esjava_2.13
- Outdated: nl.gn0s1s:elastic4s-core_2.13
- Outdated: nl.gn0s1s:elastic4s-domain_2.13
- Outdated: org.apache.commons:commons-compress
- Outdated: org.apache.commons:commons-email
- Outdated: org.apache.pekko:pekko-stream_2.13
- Outdated: org.apache.tika:tika-core
- Outdated: org.codehaus.groovy:groovy-json
- Outdated: org.codehaus.janino:janino
- doc comments repeat the names kahuna/public/js/edits/service.js:218
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-83d823ac9b6c4f67afe5fa8e044f249c/history.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-83d823ac9b6c4f67afe5fa8e044f249c/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 . | 53 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 47 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 124 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `dev/oidc-provider/app.js` — 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |