Executive summary
guardian/giant falls short of our standard for production because four passwords or keys sit in the current code and we found no automated security scanning of the code, its secrets or its dependencies. It scores 43.2 out of 100 and is rated Weak, and 50 of its 91 critical findings are security problems.
Production Readiness, at 34.3, is the weakest lens and counts most in the score. The best first step is replacing the four exposed passwords or keys and switching the old ones off, worth about 8.0 points. Adding automated security scanning comes next, worth about 4.0 points. Raising Production Readiness to 70 would lift the score to about 50.5.
Twenty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fourteen known security holes in the packages the code depends on can be used by attackers, and eighteen 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 eight secrets exposed to more of the pipeline than needed, and the four passwords or keys in the code and the password or key in the code's history need replacing, with the old ones switched off. The 15 controls that only work with a mouse need to work with the keyboard, or to become a real button.
The product code is 50,413 lines, about €52,000 to rebuild.
If Production Readiness rose from 34.3 to 70, the lowest score rated Strong, the score would rise from 43.2 to about 50.5.
Rebuild cost: about €52,000 · Estimate
| Cost to rebuild | €17,000 to €87,000, for 290 to 920 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: 50,413 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.transcriptionservice.workerinterface | 2 frontend.src.js.types.Tree | 3 frontend.src.js.types.Workspaces | 4 model.user | 5 utils.attempt | 6 frontend.src.js.types | 7 model.manifest | 8 utils | 9 frontend.src.js.types.redux.GiantState | 10 services | 11 frontend.src.js.components.viewer | 12 frontend.src.js.types.redux.GiantActions | 13 frontend.src.js.util | 14 services.index | 15 services.previewing | 16 model.frontend | 17 model.frontend.user | 18 services.events | 19 model.annotations | 20 utils.auth.providers | 21 model.ingestion | 22 extraction | 23 extraction.email.mbox | 24 model.index | 25 extraction.tables | 26 model | 27 com.gu.pfi.cli.service | 28 ingestion | 29 services.annotations | 30 services.ingestion | 31 services.manifest | 32 com.gu.pfi.cli | 33 extraction.archives | 34 extraction.email.eml | 35 extraction.email.olm | 36 extraction.email.pst | 37 services.users | 38 commands | 39 utils.controller | 40 controllers.api |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com.gu.transcriptionservice.workerinterface | ||||||||||||||||||||||||||||||||||||||||
| 2 frontend.src.js.types.Tree | ||||||||||||||||||||||||||||||||||||||||
| 3 frontend.src.js.types.Workspaces | ||||||||||||||||||||||||||||||||||||||||
| 4 model.user | ||||||||||||||||||||||||||||||||||||||||
| 5 utils.attempt | ||||||||||||||||||||||||||||||||||||||||
| 6 frontend.src.js.types | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 7 model.manifest | 1 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 8 utils | 6 | 7 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 9 frontend.src.js.types.redux.GiantState | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 services | 10 | 1 | 8 | 2 | 3 | |||||||||||||||||||||||||||||||||||
| 11 frontend.src.js.components.viewer | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 12 frontend.src.js.types.redux.GiantActions | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 frontend.src.js.util | 5 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 14 services.index | 5 | 1 | 3 | 3 | 7 | 3 | 3 | 14 | 17 | |||||||||||||||||||||||||||||||
| 15 services.previewing | 3 | 1 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||
| 16 model.frontend | 1 | 4 | 2 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||
| 17 model.frontend.user | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 services.events | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 model.annotations | 1 | 6 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 utils.auth.providers | 3 | 5 | 3 | 3 | 3 | |||||||||||||||||||||||||||||||||||
| 21 model.ingestion | 1 | 1 | 1 | 9 | ||||||||||||||||||||||||||||||||||||
| 22 extraction | 10 | 9 | 9 | 5 | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||
| 23 extraction.email.mbox | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 24 model.index | 1 | 2 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 25 extraction.tables | 3 | 2 | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||
| 26 model | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 com.gu.pfi.cli.service | 1 | 4 | 2 | 2 | 1 | 6 | ||||||||||||||||||||||||||||||||||
| 28 ingestion | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 services.annotations | 3 | 1 | 1 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 30 services.ingestion | 5 | 1 | 1 | 1 | 1 | 4 | 2 | 5 | ||||||||||||||||||||||||||||||||
| 31 services.manifest | 2 | 2 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 32 com.gu.pfi.cli | 4 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 extraction.archives | 2 | 2 | 2 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||
| 34 extraction.email.eml | 1 | 1 | 2 | 1 | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 35 extraction.email.olm | 1 | 1 | 1 | 1 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 36 extraction.email.pst | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 37 services.users | 4 | 1 | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 38 commands | 13 | 5 | 4 | 1 | 4 | 4 | 2 | 3 | 12 | 2 | 7 | 2 | ||||||||||||||||||||||||||||
| 39 utils.controller | 1 | 9 | 3 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 40 controllers.api | 7 | 1 | 7 | 3 | 2 | 1 | 1 | 2 | 1 | 3 | 9 | 2 | 2 | 2 | 1 | 36 |
6→2 frontend.src.js.types uses frontend.src.js.types.Tree✕
- Connections
- 1 pair of types, where a type in frontend.src.js.types uses a type in frontend.src.js.types.Tree.
- The types involved
frontend.src.js.types.Tree→frontend.src.js.types.Tree.TreeEntry
- Direction
- frontend.src.js.types uses frontend.src.js.types.Tree, so a change to frontend.src.js.types.Tree can break frontend.src.js.types, while a change to frontend.src.js.types can't break frontend.src.js.types.Tree.
- Position
- Below the diagonal: frontend.src.js.types uses a module listed above it, which is the healthy direction.
6→3 frontend.src.js.types uses frontend.src.js.types.Workspaces✕
- Connections
- 1 pair of types, where a type in frontend.src.js.types uses a type in frontend.src.js.types.Workspaces.
- The types involved
frontend.src.js.types.Workspaces→frontend.src.js.types.Workspaces.WorkspaceEntry
- Direction
- frontend.src.js.types uses frontend.src.js.types.Workspaces, so a change to frontend.src.js.types.Workspaces can break frontend.src.js.types, while a change to frontend.src.js.types can't break frontend.src.js.types.Workspaces.
- Position
- Below the diagonal: frontend.src.js.types uses a module listed above it, which is the healthy direction.
7→4 model.manifest uses model.user✕
- Connections
- 1 pair of types, where a type in model.manifest uses a type in model.user.
- The types involved
model.manifest.UserWithCollections→model.user.UserPermissions
- Direction
- model.manifest uses model.user, so a change to model.user can break model.manifest, while a change to model.manifest can't break model.user.
- Position
- Below the diagonal: model.manifest uses a module listed above it, which is the healthy direction.
7→21 model.manifest uses model.ingestion part of a loop✕
- Connections
- 1 pair of types, where a type in model.manifest uses a type in model.ingestion.
- The types involved
model.manifest.WorkItem→model.ingestion.WorkspaceItemContext
- Direction
- model.manifest uses model.ingestion, so a change to model.ingestion can break model.manifest, while a change to model.manifest can't break model.ingestion.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→26 model.manifest uses model part of a loop✕
- Connections
- 6 pairs of types, where a type in model.manifest uses a type in model.
- The types involved
model.manifest.Blob→model.Urimodel.manifest.Collection→model.Urimodel.manifest.CollectionWithUsers→model.Urimodel.manifest.Ingestion→model.Languagemodel.manifest.WorkItem→model.Languagemodel.manifest.WorkItem→model.Uri
- Direction
- model.manifest uses model, so a change to model can break model.manifest, while a change to model.manifest can't break model.
- 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→5 utils uses utils.attempt✕
- Connections
- 6 pairs of types, where a type in utils uses a type in utils.attempt.
- The types involved
utils.AWSWorkerControl→utils.attempt.Attemptutils.Neo4jHelper→utils.attempt.Attemptutils.Neo4jHelper→utils.attempt.Failureutils.PekkoWorkerControl→utils.attempt.Attemptutils.Timing→utils.attempt.Attemptutils.WorkerControl→utils.attempt.Attempt
- Direction
- utils uses utils.attempt, so a change to utils.attempt can break utils, while a change to utils can't break utils.attempt.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
8→10 utils uses services part of a loop✕
- Connections
- 7 pairs of types, where a type in utils uses a type in services.
- The types involved
utils.AwsDiscovery→services.AWSDiscoveryConfigutils.AwsDiscovery→services.BucketConfigutils.AwsDiscovery→services.Configutils.AwsDiscovery→services.PostgresConfigutils.DiscoveryResult→services.Configutils.Ocr→services.TesseractOcrConfigutils.Whisper→services.TranscribeConfig
- Direction
- utils uses services, so a change to services can break utils, while a change to utils can't break services.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→16 utils uses model.frontend part of a loop✕
- Connections
- 2 pairs of types, where a type in utils uses a type in model.frontend.
- The types involved
utils.PDFUtil→model.frontend.HighlightableTextutils.PDFUtil→model.frontend.TextHighlight
- Direction
- utils uses model.frontend, so a change to model.frontend can break utils, while a change to utils can't break model.frontend.
- 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→21 utils uses model.ingestion part of a loop✕
- Connections
- 1 pair of types, where a type in utils uses a type in model.ingestion.
- The types involved
utils.Ocr→model.ingestion.OcrMyPdfFlag
- Direction
- utils uses model.ingestion, so a change to model.ingestion can break utils, while a change to utils can't break model.ingestion.
- 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→24 utils uses model.index part of a loop✕
- Connections
- 1 pair of types, where a type in utils uses a type in model.index.
- The types involved
utils.PDFUtil→model.index.PageHighlight
- Direction
- utils uses model.index, so a change to model.index can break utils, while a change to utils can't break model.index.
- 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→26 utils uses model part of a loop✕
- Connections
- 2 pairs of types, where a type in utils uses a type in model.
- The types involved
utils.Binders→model.Languageutils.Binders→model.Uri
- Direction
- utils uses model, so a change to model can break utils, while a change to utils can't break model.
- 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→6 frontend.src.js.types.redux.GiantState uses frontend.src.js.types✕
- Connections
- 1 pair of types, where a type in frontend.src.js.types.redux.GiantState uses a type in frontend.src.js.types.
- The types involved
frontend.src.js.types.redux.GiantState.AppState→frontend.src.js.types.Preferences
- Direction
- frontend.src.js.types.redux.GiantState uses frontend.src.js.types, so a change to frontend.src.js.types can break frontend.src.js.types.redux.GiantState, while a change to frontend.src.js.types.redux.GiantState can't break frontend.src.js.types.
- Position
- Below the diagonal: frontend.src.js.types.redux.GiantState uses a module listed above it, which is the healthy direction.
10→5 services uses utils.attempt✕
- Connections
- 10 pairs of types, where a type in services uses a type in utils.attempt.
- The types involved
services.ElasticsearchClient→utils.attempt.Attemptservices.ElasticsearchSyntax→utils.attempt.Attemptservices.IngestStorage→utils.attempt.Failureservices.ObjectStorage→utils.attempt.Failureservices.S3IngestStorage→utils.attempt.Failureservices.S3IngestStorage→utils.attempt.UnknownFailureservices.S3ObjectStorage→utils.attempt.Failureservices.ScratchSpace→utils.attempt.Attemptservices.Tika→utils.attempt.Failureservices.TypeDetector→utils.attempt.Failure
- Direction
- services uses utils.attempt, so a change to utils.attempt can break services, while a change to services can't break utils.attempt.
- Position
- Below the diagonal: services uses a module listed above it, which is the healthy direction.
10→7 services uses model.manifest✕
- Connections
- 1 pair of types, where a type in services uses a type in model.manifest.
- The types involved
services.ScratchSpace→model.manifest.Blob
- Direction
- services uses model.manifest, so a change to model.manifest can break services, while a change to services can't break model.manifest.
- Position
- Below the diagonal: services uses a module listed above it, which is the healthy direction.
10→8 services uses utils✕
- Connections
- 8 pairs of types, where a type in services uses a type in utils.
- The types involved
services.CloudwatchMetricsService→utils.Loggingservices.ElasticsearchClient→utils.Loggingservices.ExternalWorkerScheduler→utils.Loggingservices.RemoteIngestScheduler→utils.Loggingservices.S3IngestStorage→utils.Loggingservices.S3ObjectStorage→utils.Loggingservices.ScratchSpace→utils.Loggingservices.WorkerScheduler→utils.Logging
- Direction
- services uses utils, so a change to utils can break services, while a change to services can't break utils.
- Position
- Below the diagonal: services uses a module listed above it, which is the healthy direction.
10→21 services uses model.ingestion part of a loop✕
- Connections
- 2 pairs of types, where a type in services uses a type in model.ingestion.
- The types involved
services.IngestStorage→model.ingestion.FileContextservices.S3IngestStorage→model.ingestion.FileContext
- Direction
- services uses model.ingestion, so a change to model.ingestion can break services, while a change to services can't break model.ingestion.
- 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 services uses model part of a loop✕
- Connections
- 3 pairs of types, where a type in services uses a type in model.
- The types involved
services.ElasticsearchSyntax→model.Languageservices.ObjectStorage→model.ObjectMetadataservices.S3ObjectStorage→model.ObjectMetadata
- Direction
- services uses model, so a change to model can break services, while a change to services can't break model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→2 frontend.src.js.components.viewer uses frontend.src.js.types.Tree✕
- Connections
- 1 pair of types, where a type in frontend.src.js.components.viewer uses a type in frontend.src.js.types.Tree.
- The types involved
frontend.src.js.components.viewer.LazyTreeBrowser→frontend.src.js.types.Tree.TreeEntry
- Direction
- frontend.src.js.components.viewer uses frontend.src.js.types.Tree, so a change to frontend.src.js.types.Tree can break frontend.src.js.components.viewer, while a change to frontend.src.js.components.viewer can't break frontend.src.js.types.Tree.
- Position
- Below the diagonal: frontend.src.js.components.viewer uses a module listed above it, which is the healthy direction.
11→6 frontend.src.js.components.viewer uses frontend.src.js.types✕
- Connections
- 1 pair of types, where a type in frontend.src.js.components.viewer uses a type in frontend.src.js.types.
- The types involved
frontend.src.js.components.viewer.LazyTreeBrowser→frontend.src.js.types.Tree
- Direction
- frontend.src.js.components.viewer uses frontend.src.js.types, so a change to frontend.src.js.types can break frontend.src.js.components.viewer, while a change to frontend.src.js.components.viewer can't break frontend.src.js.types.
- Position
- Below the diagonal: frontend.src.js.components.viewer uses a module listed above it, which is the healthy direction.
11→9 frontend.src.js.components.viewer uses frontend.src.js.types.redux.GiantState✕
- Connections
- 4 pairs of types, where a type in frontend.src.js.components.viewer uses a type in frontend.src.js.types.redux.GiantState.
- The types involved
frontend.src.js.components.viewer.AddToWorkspaceModal→frontend.src.js.types.redux.GiantState.GiantStatefrontend.src.js.components.viewer.DeleteButtonModal→frontend.src.js.types.redux.GiantState.GiantStatefrontend.src.js.components.viewer.DownloadButton→frontend.src.js.types.redux.GiantState.GiantStatefrontend.src.js.components.viewer.Viewer→frontend.src.js.types.redux.GiantState.GiantState
- Direction
- frontend.src.js.components.viewer uses frontend.src.js.types.redux.GiantState, so a change to frontend.src.js.types.redux.GiantState can break frontend.src.js.components.viewer, while a change to frontend.src.js.components.viewer can't break frontend.src.js.types.redux.GiantState.
- Position
- Below the diagonal: frontend.src.js.components.viewer uses a module listed above it, which is the healthy direction.
12→2 frontend.src.js.types.redux.GiantActions uses frontend.src.js.types.Tree✕
- Connections
- 1 pair of types, where a type in frontend.src.js.types.redux.GiantActions uses a type in frontend.src.js.types.Tree.
- The types involved
frontend.src.js.types.redux.GiantActions.TreeNodeAction→frontend.src.js.types.Tree.TreeNode
- Direction
- frontend.src.js.types.redux.GiantActions uses frontend.src.js.types.Tree, so a change to frontend.src.js.types.Tree can break frontend.src.js.types.redux.GiantActions, while a change to frontend.src.js.types.redux.GiantActions can't break frontend.src.js.types.Tree.
- Position
- Below the diagonal: frontend.src.js.types.redux.GiantActions uses a module listed above it, which is the healthy direction.
12→3 frontend.src.js.types.redux.GiantActions uses frontend.src.js.types.Workspaces✕
- Connections
- 1 pair of types, where a type in frontend.src.js.types.redux.GiantActions uses a type in frontend.src.js.types.Workspaces.
- The types involved
frontend.src.js.types.redux.GiantActions.TreeNodeAction→frontend.src.js.types.Workspaces.WorkspaceEntry
- Direction
- frontend.src.js.types.redux.GiantActions uses frontend.src.js.types.Workspaces, so a change to frontend.src.js.types.Workspaces can break frontend.src.js.types.redux.GiantActions, while a change to frontend.src.js.types.redux.GiantActions can't break frontend.src.js.types.Workspaces.
- Position
- Below the diagonal: frontend.src.js.types.redux.GiantActions uses a module listed above it, which is the healthy direction.
12→9 frontend.src.js.types.redux.GiantActions uses frontend.src.js.types.redux.GiantState✕
- Connections
- 1 pair of types, where a type in frontend.src.js.types.redux.GiantActions uses a type in frontend.src.js.types.redux.GiantState.
- The types involved
frontend.src.js.types.redux.GiantActions.UrlParamsUpdateType→frontend.src.js.types.redux.GiantState.UrlParamsState
- Direction
- frontend.src.js.types.redux.GiantActions uses frontend.src.js.types.redux.GiantState, so a change to frontend.src.js.types.redux.GiantState can break frontend.src.js.types.redux.GiantActions, while a change to frontend.src.js.types.redux.GiantActions can't break frontend.src.js.types.redux.GiantState.
- Position
- Below the diagonal: frontend.src.js.types.redux.GiantActions uses a module listed above it, which is the healthy direction.
13→2 frontend.src.js.util uses frontend.src.js.types.Tree✕
- Connections
- 5 pairs of types, where a type in frontend.src.js.util uses a type in frontend.src.js.types.Tree.
- The types involved
frontend.src.js.util.treeUtils→frontend.src.js.types.Tree.TreeEntryfrontend.src.js.util.workspaceNavigation→frontend.src.js.types.Tree.TreeEntryfrontend.src.js.util.workspaceNavigation→frontend.src.js.types.Tree.TreeNodefrontend.src.js.util.workspaceUtils→frontend.src.js.types.Tree.TreeEntryfrontend.src.js.util.workspaceUtils→frontend.src.js.types.Tree.TreeNode
- Direction
- frontend.src.js.util uses frontend.src.js.types.Tree, so a change to frontend.src.js.types.Tree can break frontend.src.js.util, while a change to frontend.src.js.util can't break frontend.src.js.types.Tree.
- Position
- Below the diagonal: frontend.src.js.util uses a module listed above it, which is the healthy direction.
13→3 frontend.src.js.util uses frontend.src.js.types.Workspaces✕
- Connections
- 2 pairs of types, where a type in frontend.src.js.util uses a type in frontend.src.js.types.Workspaces.
- The types involved
frontend.src.js.util.workspaceNavigation→frontend.src.js.types.Workspaces.WorkspaceEntryfrontend.src.js.util.workspaceUtils→frontend.src.js.types.Workspaces.WorkspaceEntry
- Direction
- frontend.src.js.util uses frontend.src.js.types.Workspaces, so a change to frontend.src.js.types.Workspaces can break frontend.src.js.util, while a change to frontend.src.js.util can't break frontend.src.js.types.Workspaces.
- Position
- Below the diagonal: frontend.src.js.util uses a module listed above it, which is the healthy direction.
13→6 frontend.src.js.util uses frontend.src.js.types✕
- Connections
- 1 pair of types, where a type in frontend.src.js.util uses a type in frontend.src.js.types.
- The types involved
frontend.src.js.util.treeUtils→frontend.src.js.types.Tree
- Direction
- frontend.src.js.util uses frontend.src.js.types, so a change to frontend.src.js.types can break frontend.src.js.util, while a change to frontend.src.js.util can't break frontend.src.js.types.
- Position
- Below the diagonal: frontend.src.js.util uses a module listed above it, which is the healthy direction.
13→9 frontend.src.js.util uses frontend.src.js.types.redux.GiantState✕
- Connections
- 1 pair of types, where a type in frontend.src.js.util uses a type in frontend.src.js.types.redux.GiantState.
- The types involved
frontend.src.js.util.resourceUtils→frontend.src.js.types.redux.GiantState.HighlightsState
- Direction
- frontend.src.js.util uses frontend.src.js.types.redux.GiantState, so a change to frontend.src.js.types.redux.GiantState can break frontend.src.js.util, while a change to frontend.src.js.util can't break frontend.src.js.types.redux.GiantState.
- Position
- Below the diagonal: frontend.src.js.util uses a module listed above it, which is the healthy direction.
14→5 services.index uses utils.attempt✕
- Connections
- 5 pairs of types, where a type in services.index uses a type in utils.attempt.
- The types involved
services.index.ElasticsearchPages→utils.attempt.Attemptservices.index.ElasticsearchResources→utils.attempt.Attemptservices.index.Index→utils.attempt.Attemptservices.index.Pages→utils.attempt.Attemptservices.index.Pages2→utils.attempt.Attempt
- Direction
- services.index uses utils.attempt, so a change to utils.attempt can break services.index, while a change to services.index can't break utils.attempt.
- Position
- Below the diagonal: services.index uses a module listed above it, which is the healthy direction.
14→7 services.index uses model.manifest✕
- Connections
- 1 pair of types, where a type in services.index uses a type in model.manifest.
- The types involved
services.index.IngestionData→model.manifest.MimeType
- Direction
- services.index uses model.manifest, so a change to model.manifest can break services.index, while a change to services.index can't break model.manifest.
- Position
- Below the diagonal: services.index uses a module listed above it, which is the healthy direction.
14→8 services.index uses utils✕
- Connections
- 3 pairs of types, where a type in services.index uses a type in utils.
- The types involved
services.index.ElasticsearchPages→utils.Loggingservices.index.ElasticsearchResources→utils.Loggingservices.index.Pages2→utils.Logging
- Direction
- services.index uses utils, so a change to utils can break services.index, while a change to services.index can't break utils.
- Position
- Below the diagonal: services.index uses a module listed above it, which is the healthy direction.
14→10 services.index uses services✕
- Connections
- 3 pairs of types, where a type in services.index uses a type in services.
- The types involved
services.index.ElasticsearchPages→services.ElasticsearchSyntaxservices.index.ElasticsearchResources→services.ElasticsearchSyntaxservices.index.Pages2→services.ElasticsearchSyntax
- Direction
- services.index uses services, so a change to services can break services.index, while a change to services.index can't break services.
- Position
- Below the diagonal: services.index uses a module listed above it, which is the healthy direction.
14→16 services.index uses model.frontend part of a loop✕
- Connections
- 7 pairs of types, where a type in services.index uses a type in model.frontend.
- The types involved
services.index.Aggregations→model.frontend.SearchAggregationservices.index.Aggregations→model.frontend.SearchAggregationBucketservices.index.ElasticsearchResources→model.frontend.SearchResultsservices.index.HighlightFields→model.frontend.Highlightservices.index.HitReaders→model.frontend.DocumentResultDetailsservices.index.HitReaders→model.frontend.EmailResultDetailsservices.index.Index→model.frontend.SearchResults
- Direction
- services.index uses model.frontend, so a change to model.frontend can break services.index, while a change to services.index can't break model.frontend.
- 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.
14→21 services.index uses model.ingestion part of a loop✕
- Connections
- 3 pairs of types, where a type in services.index uses a type in model.ingestion.
- The types involved
services.index.ElasticsearchResources→model.ingestion.WorkspaceItemContextservices.index.Index→model.ingestion.WorkspaceItemContextservices.index.IngestionData→model.ingestion.WorkspaceItemContext
- Direction
- services.index uses model.ingestion, so a change to model.ingestion can break services.index, while a change to services.index can't break model.ingestion.
- 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.
14→22 services.index uses extraction part of a loop✕
- Connections
- 3 pairs of types, where a type in services.index uses a type in extraction.
- The types involved
services.index.ElasticsearchResources→extraction.EnrichedMetadataservices.index.HitReaders→extraction.EnrichedMetadataservices.index.Index→extraction.EnrichedMetadata
- Direction
- services.index uses extraction, so a change to extraction can break services.index, while a change to services.index can't break extraction.
- 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.
14→24 services.index uses model.index part of a loop✕
- Connections
- 14 pairs of types, where a type in services.index uses a type in model.index.
- The types involved
services.index.ElasticsearchPages→model.index.Pageservices.index.ElasticsearchPages→model.index.PageResultservices.index.ElasticsearchResources→model.index.IndexedBlobservices.index.ElasticsearchResources→model.index.IndexedResourceservices.index.ElasticsearchResources→model.index.SearchParametersservices.index.HitReaders→model.index.Documentservices.index.HitReaders→model.index.TranslationDataservices.index.Index→model.index.IndexedBlobservices.index.Index→model.index.IndexedResourceservices.index.Index→model.index.SearchParametersservices.index.Pages→model.index.Pageservices.index.Pages→model.index.PageResultservices.index.Pages2→model.index.PageDimensionsservices.index.Pages2→model.index.PageWithFind
- Direction
- services.index uses model.index, so a change to model.index can break services.index, while a change to services.index can't break model.index.
- 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.
14→26 services.index uses model part of a loop✕
- Connections
- 17 pairs of types, where a type in services.index uses a type in model.
- The types involved
services.index.ElasticsearchPages→model.Languageservices.index.ElasticsearchPages→model.Uriservices.index.ElasticsearchResources→model.Emailservices.index.ElasticsearchResources→model.Languageservices.index.ElasticsearchResources→model.Recipientservices.index.ElasticsearchResources→model.TranscriptionResultservices.index.ElasticsearchResources→model.Uriservices.index.HitReaders→model.Emailservices.index.HitReaders→model.Languageservices.index.HitReaders→model.Recipientservices.index.Index→model.Emailservices.index.Index→model.Languageservices.index.Index→model.TranscriptionResultservices.index.Index→model.Uriservices.index.IngestionData→model.Uriservices.index.Pages→model.Uriservices.index.Pages2→model.Uri
- Direction
- services.index uses model, so a change to model can break services.index, while a change to services.index can't break model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→5 services.previewing uses utils.attempt✕
- Connections
- 3 pairs of types, where a type in services.previewing uses a type in utils.attempt.
- The types involved
services.previewing.DefaultPreviewService→utils.attempt.Attemptservices.previewing.PreviewGenerator→utils.attempt.Attemptservices.previewing.PreviewService→utils.attempt.Attempt
- Direction
- services.previewing uses utils.attempt, so a change to utils.attempt can break services.previewing, while a change to services.previewing can't break utils.attempt.
- Position
- Below the diagonal: services.previewing uses a module listed above it, which is the healthy direction.
15→8 services.previewing uses utils✕
- Connections
- 1 pair of types, where a type in services.previewing uses a type in utils.
- The types involved
services.previewing.PreviewGenerator→utils.Logging
- Direction
- services.previewing uses utils, so a change to utils can break services.previewing, while a change to services.previewing can't break utils.
- Position
- Below the diagonal: services.previewing uses a module listed above it, which is the healthy direction.
15→10 services.previewing uses services✕
- Connections
- 1 pair of types, where a type in services.previewing uses a type in services.
- The types involved
services.previewing.DefaultPreviewService→services.ObjectStorage
- Direction
- services.previewing uses services, so a change to services can break services.previewing, while a change to services.previewing can't break services.
- Position
- Below the diagonal: services.previewing uses a module listed above it, which is the healthy direction.
15→24 services.previewing uses model.index part of a loop✕
- Connections
- 1 pair of types, where a type in services.previewing uses a type in model.index.
- The types involved
services.previewing.DefaultPreviewService→model.index.IndexedResource
- Direction
- services.previewing uses model.index, so a change to model.index can break services.previewing, while a change to services.previewing can't break model.index.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→26 services.previewing uses model part of a loop✕
- Connections
- 4 pairs of types, where a type in services.previewing uses a type in model.
- The types involved
services.previewing.DefaultPreviewService→model.ObjectDataservices.previewing.DefaultPreviewService→model.Uriservices.previewing.PreviewService→model.ObjectDataservices.previewing.PreviewService→model.Uri
- Direction
- services.previewing uses model, so a change to model can break services.previewing, while a change to services.previewing can't break model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→14 model.frontend uses services.index✕
- Connections
- 1 pair of types, where a type in model.frontend uses a type in services.index.
- The types involved
model.frontend.ParsedChips→services.index.WorkspaceSearchContextParams
- Direction
- model.frontend uses services.index, so a change to services.index can break model.frontend, while a change to model.frontend can't break services.index.
- Position
- Below the diagonal: model.frontend uses a module listed above it, which is the healthy direction.
16→15 model.frontend uses services.previewing✕
- Connections
- 4 pairs of types, where a type in model.frontend uses a type in services.previewing.
- The types involved
model.frontend.BasicResource→services.previewing.PreviewStatusmodel.frontend.DocumentResource→services.previewing.PreviewStatusmodel.frontend.EmailResource→services.previewing.PreviewStatusmodel.frontend.Resource→services.previewing.PreviewStatus
- Direction
- model.frontend uses services.previewing, so a change to services.previewing can break model.frontend, while a change to model.frontend can't break services.previewing.
- Position
- Below the diagonal: model.frontend uses a module listed above it, which is the healthy direction.
16→19 model.frontend uses model.annotations part of a loop✕
- Connections
- 2 pairs of types, where a type in model.frontend uses a type in model.annotations.
- The types involved
model.frontend.DocumentResource→model.annotations.Commentmodel.frontend.EmailResource→model.annotations.Comment
- Direction
- model.frontend uses model.annotations, so a change to model.annotations can break model.frontend, while a change to model.frontend can't break model.annotations.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→22 model.frontend uses extraction part of a loop✕
- Connections
- 1 pair of types, where a type in model.frontend uses a type in extraction.
- The types involved
model.frontend.DocumentResource→extraction.EnrichedMetadata
- Direction
- model.frontend uses extraction, so a change to extraction can break model.frontend, while a change to model.frontend can't break extraction.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→24 model.frontend uses model.index part of a loop✕
- Connections
- 1 pair of types, where a type in model.frontend uses a type in model.index.
- The types involved
model.frontend.DocumentResource→model.index.HighlightableTranslationData
- Direction
- model.frontend uses model.index, so a change to model.index can break model.frontend, while a change to model.frontend can't break model.index.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→26 model.frontend uses model part of a loop✕
- Connections
- 4 pairs of types, where a type in model.frontend uses a type in model.
- The types involved
model.frontend.EmailResource→model.Recipientmodel.frontend.EmailResource→model.Sensitivitymodel.frontend.EmailResultDetails→model.Recipientmodel.frontend.ThreadEmail→model.Recipient
- Direction
- model.frontend uses model, so a change to model can break model.frontend, while a change to model.frontend can't break model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→16 model.frontend.user uses model.frontend✕
- Connections
- 2 pairs of types, where a type in model.frontend.user uses a type in model.frontend.
- The types involved
model.frontend.user.NewGenesisUser→model.frontend.TotpActivationmodel.frontend.user.UserRegistration→model.frontend.TotpActivation
- Direction
- model.frontend.user uses model.frontend, so a change to model.frontend can break model.frontend.user, while a change to model.frontend.user can't break model.frontend.
- Position
- Below the diagonal: model.frontend.user uses a module listed above it, which is the healthy direction.
18→5 services.events uses utils.attempt✕
- Connections
- 2 pairs of types, where a type in services.events uses a type in utils.attempt.
- The types involved
services.events.ElasticsearchEvents→utils.attempt.Attemptservices.events.Events→utils.attempt.Attempt
- Direction
- services.events uses utils.attempt, so a change to utils.attempt can break services.events, while a change to services.events can't break utils.attempt.
- Position
- Below the diagonal: services.events uses a module listed above it, which is the healthy direction.
18→8 services.events uses utils✕
- Connections
- 1 pair of types, where a type in services.events uses a type in utils.
- The types involved
services.events.ElasticsearchEvents→utils.Logging
- Direction
- services.events uses utils, so a change to utils can break services.events, while a change to services.events can't break utils.
- Position
- Below the diagonal: services.events uses a module listed above it, which is the healthy direction.
18→10 services.events uses services✕
- Connections
- 1 pair of types, where a type in services.events uses a type in services.
- The types involved
services.events.ElasticsearchEvents→services.ElasticsearchSyntax
- Direction
- services.events uses services, so a change to services can break services.events, while a change to services.events can't break services.
- Position
- Below the diagonal: services.events uses a module listed above it, which is the healthy direction.
18→16 services.events uses model.frontend✕
- Connections
- 1 pair of types, where a type in services.events uses a type in model.frontend.
- The types involved
services.events.FindEventsResponse→model.frontend.Paging
- Direction
- services.events uses model.frontend, so a change to model.frontend can break services.events, while a change to services.events can't break model.frontend.
- Position
- Below the diagonal: services.events uses a module listed above it, which is the healthy direction.
19→16 model.annotations uses model.frontend✕
- Connections
- 1 pair of types, where a type in model.annotations uses a type in model.frontend.
- The types involved
model.annotations.Workspace→model.frontend.TreeEntry
- Direction
- model.annotations uses model.frontend, so a change to model.frontend can break model.annotations, while a change to model.annotations can't break model.frontend.
- Position
- Below the diagonal: model.annotations uses a module listed above it, which is the healthy direction.
19→17 model.annotations uses model.frontend.user✕
- Connections
- 6 pairs of types, where a type in model.annotations uses a type in model.frontend.user.
- The types involved
model.annotations.Comment→model.frontend.user.PartialUsermodel.annotations.Workspace→model.frontend.user.PartialUsermodel.annotations.WorkspaceEntry→model.frontend.user.PartialUsermodel.annotations.WorkspaceLeaf→model.frontend.user.PartialUsermodel.annotations.WorkspaceMetadata→model.frontend.user.PartialUsermodel.annotations.WorkspaceNode→model.frontend.user.PartialUser
- Direction
- model.annotations uses model.frontend.user, so a change to model.frontend.user can break model.annotations, while a change to model.annotations can't break model.frontend.user.
- Position
- Below the diagonal: model.annotations uses a module listed above it, which is the healthy direction.
19→26 model.annotations uses model part of a loop✕
- Connections
- 1 pair of types, where a type in model.annotations uses a type in model.
- The types involved
model.annotations.OcrCommentAnchor→model.Language
- Direction
- model.annotations uses model, so a change to model can break model.annotations, while a change to model.annotations can't break model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→5 utils.auth.providers uses utils.attempt✕
- Connections
- 3 pairs of types, where a type in utils.auth.providers uses a type in utils.attempt.
- The types involved
utils.auth.providers.DatabaseUserProvider→utils.attempt.Attemptutils.auth.providers.PanDomainUserProvider→utils.attempt.Attemptutils.auth.providers.UserProvider→utils.attempt.Attempt
- Direction
- utils.auth.providers uses utils.attempt, so a change to utils.attempt can break utils.auth.providers, while a change to utils.auth.providers can't break utils.attempt.
- Position
- Below the diagonal: utils.auth.providers uses a module listed above it, which is the healthy direction.
20→8 utils.auth.providers uses utils✕
- Connections
- 5 pairs of types, where a type in utils.auth.providers uses a type in utils.
- The types involved
utils.auth.providers.DatabaseUserProvider→utils.Epochutils.auth.providers.DatabaseUserProvider→utils.Loggingutils.auth.providers.PanDomainUserProvider→utils.Epochutils.auth.providers.PanDomainUserProvider→utils.Loggingutils.auth.providers.UserProvider→utils.Epoch
- Direction
- utils.auth.providers uses utils, so a change to utils can break utils.auth.providers, while a change to utils.auth.providers can't break utils.
- Position
- Below the diagonal: utils.auth.providers uses a module listed above it, which is the healthy direction.
20→10 utils.auth.providers uses services✕
- Connections
- 3 pairs of types, where a type in utils.auth.providers uses a type in services.
- The types involved
utils.auth.providers.DatabaseUserProvider→services.DatabaseAuthConfigutils.auth.providers.PanDomainUserProvider→services.PandaAuthConfigutils.auth.providers.UserProvider→services.AuthProviderConfig
- Direction
- utils.auth.providers uses services, so a change to services can break utils.auth.providers, while a change to utils.auth.providers can't break services.
- Position
- Below the diagonal: utils.auth.providers uses a module listed above it, which is the healthy direction.
20→16 utils.auth.providers uses model.frontend✕
- Connections
- 3 pairs of types, where a type in utils.auth.providers uses a type in model.frontend.
- The types involved
utils.auth.providers.DatabaseUserProvider→model.frontend.TotpActivationutils.auth.providers.PanDomainUserProvider→model.frontend.TotpActivationutils.auth.providers.UserProvider→model.frontend.TotpActivation
- Direction
- utils.auth.providers uses model.frontend, so a change to model.frontend can break utils.auth.providers, while a change to utils.auth.providers can't break model.frontend.
- Position
- Below the diagonal: utils.auth.providers uses a module listed above it, which is the healthy direction.
20→17 utils.auth.providers uses model.frontend.user✕
- Connections
- 3 pairs of types, where a type in utils.auth.providers uses a type in model.frontend.user.
- The types involved
utils.auth.providers.DatabaseUserProvider→model.frontend.user.PartialUserutils.auth.providers.PanDomainUserProvider→model.frontend.user.PartialUserutils.auth.providers.UserProvider→model.frontend.user.PartialUser
- Direction
- utils.auth.providers uses model.frontend.user, so a change to model.frontend.user can break utils.auth.providers, while a change to utils.auth.providers can't break model.frontend.user.
- Position
- Below the diagonal: utils.auth.providers uses a module listed above it, which is the healthy direction.
21→16 model.ingestion uses model.frontend✕
- Connections
- 1 pair of types, where a type in model.ingestion uses a type in model.frontend.
- The types involved
model.ingestion.RemoteIngest→model.frontend.TreeEntry
- Direction
- model.ingestion uses model.frontend, so a change to model.frontend can break model.ingestion, while a change to model.ingestion can't break model.frontend.
- Position
- Below the diagonal: model.ingestion uses a module listed above it, which is the healthy direction.
21→17 model.ingestion uses model.frontend.user✕
- Connections
- 1 pair of types, where a type in model.ingestion uses a type in model.frontend.user.
- The types involved
model.ingestion.RemoteIngest→model.frontend.user.PartialUser
- Direction
- model.ingestion uses model.frontend.user, so a change to model.frontend.user can break model.ingestion, while a change to model.ingestion can't break model.frontend.user.
- Position
- Below the diagonal: model.ingestion uses a module listed above it, which is the healthy direction.
21→19 model.ingestion uses model.annotations✕
- Connections
- 1 pair of types, where a type in model.ingestion uses a type in model.annotations.
- The types involved
model.ingestion.RemoteIngest→model.annotations.WorkspaceEntry
- Direction
- model.ingestion uses model.annotations, so a change to model.annotations can break model.ingestion, while a change to model.ingestion can't break model.annotations.
- Position
- Below the diagonal: model.ingestion uses a module listed above it, which is the healthy direction.
21→26 model.ingestion uses model part of a loop✕
- Connections
- 9 pairs of types, where a type in model.ingestion uses a type in model.
- The types involved
model.ingestion.EmailContext→model.Emailmodel.ingestion.EmailContext→model.Languagemodel.ingestion.EmailContext→model.Urimodel.ingestion.FileContext→model.Languagemodel.ingestion.FileContext→model.Urimodel.ingestion.IngestMetadata→model.Languagemodel.ingestion.IngestionFile→model.Urimodel.ingestion.OnDiskFileContext→model.Languagemodel.ingestion.OnDiskFileContext→model.Uri
- Direction
- model.ingestion uses model, so a change to model can break model.ingestion, while a change to model.ingestion can't break model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→1 extraction uses com.gu.transcriptionservice.workerinterface✕
- Connections
- 10 pairs of types, where a type in extraction uses a type in com.gu.transcriptionservice.workerinterface.
- The types involved
extraction.ExternalDocumentTranslationExtractor→com.gu.transcriptionservice.workerinterface.TranslationTaskextraction.ExternalOcrTranslationExtractor→com.gu.transcriptionservice.workerinterface.TranslationTaskextraction.ExternalTranscriptionWorker→com.gu.transcriptionservice.workerinterface.LLMOutputSuccessextraction.ExternalTranscriptionWorker→com.gu.transcriptionservice.workerinterface.OcrOutputextraction.ExternalTranscriptionWorker→com.gu.transcriptionservice.workerinterface.OcrOutputSuccessextraction.ExternalTranscriptionWorker→com.gu.transcriptionservice.workerinterface.TranscriptionOutputextraction.ExternalTranscriptionWorker→com.gu.transcriptionservice.workerinterface.TranscriptionOutputSuccessextraction.ExternalTranscriptionWorker→com.gu.transcriptionservice.workerinterface.TranscriptionResultextraction.ExternalTranscriptionWorker→com.gu.transcriptionservice.workerinterface.TranslationFieldextraction.ExternalTranslationExtractor→com.gu.transcriptionservice.workerinterface.TranslationTask
- Direction
- extraction uses com.gu.transcriptionservice.workerinterface, so a change to com.gu.transcriptionservice.workerinterface can break extraction, while a change to extraction can't break com.gu.transcriptionservice.workerinterface.
- Position
- Below the diagonal: extraction uses a module listed above it, which is the healthy direction.
22→5 extraction uses utils.attempt✕
- Connections
- 9 pairs of types, where a type in extraction uses a type in utils.attempt.
- The types involved
extraction.DocumentBodyExtractor→utils.attempt.Failureextraction.ExternalExtractor→utils.attempt.Failureextraction.ExternalOcrMyPdfExtractor→utils.attempt.Failureextraction.ExternalTranscriptionExtractor→utils.attempt.Failureextraction.ExternalTranscriptionWorker→utils.attempt.Failureextraction.ExternalTranslationExtractor→utils.attempt.Failureextraction.Extractor→utils.attempt.Failureextraction.FileExtractor→utils.attempt.Failureextraction.TranscriptionExtractor→utils.attempt.Failure
- Direction
- extraction uses utils.attempt, so a change to utils.attempt can break extraction, while a change to extraction can't break utils.attempt.
- Position
- Below the diagonal: extraction uses a module listed above it, which is the healthy direction.
22→7 extraction uses model.manifest✕
- Connections
- 9 pairs of types, where a type in extraction uses a type in model.manifest.
- The types involved
extraction.DocumentBodyExtractor→model.manifest.Blobextraction.ExternalExtractor→model.manifest.Blobextraction.ExternalOcrMyPdfExtractor→model.manifest.Blobextraction.ExternalTranscriptionExtractor→model.manifest.Blobextraction.ExternalTranslationExtractor→model.manifest.Blobextraction.Extractor→model.manifest.Blobextraction.Extractor→model.manifest.MimeTypeextraction.FileExtractor→model.manifest.Blobextraction.TranscriptionExtractor→model.manifest.Blob
- Direction
- extraction uses model.manifest, so a change to model.manifest can break extraction, while a change to extraction can't break model.manifest.
- Position
- Below the diagonal: extraction uses a module listed above it, which is the healthy direction.
22→8 extraction uses utils✕
- Connections
- 5 pairs of types, where a type in extraction uses a type in utils.
- The types involved
extraction.DocumentBodyExtractor→utils.Loggingextraction.ExternalExtractor→utils.Loggingextraction.ExternalTranscriptionWorker→utils.Loggingextraction.TranscriptionExtractor→utils.Loggingextraction.Worker→utils.Logging
- Direction
- extraction uses utils, so a change to utils can break extraction, while a change to extraction can't break utils.
- Position
- Below the diagonal: extraction uses a module listed above it, which is the healthy direction.
22→21 extraction uses model.ingestion✕
- Connections
- 1 pair of types, where a type in extraction uses a type in model.ingestion.
- The types involved
extraction.ExtractionParams→model.ingestion.WorkspaceItemContext
- Direction
- extraction uses model.ingestion, so a change to model.ingestion can break extraction, while a change to extraction can't break model.ingestion.
- Position
- Below the diagonal: extraction uses a module listed above it, which is the healthy direction.
22→24 extraction uses model.index part of a loop✕
- Connections
- 3 pairs of types, where a type in extraction uses a type in model.index.
- The types involved
extraction.ExternalDocumentTranslationExtractor→model.index.IndexedResourceextraction.ExternalOcrTranslationExtractor→model.index.IndexedResourceextraction.ExternalTranslationExtractor→model.index.IndexedResource
- Direction
- extraction uses model.index, so a change to model.index can break extraction, while a change to extraction can't break model.index.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→26 extraction uses model part of a loop✕
- Connections
- 2 pairs of types, where a type in extraction uses a type in model.
- The types involved
extraction.ExtractionParams→model.Languageextraction.ExtractionParams→model.Uri
- Direction
- extraction uses model, so a change to model can break extraction, while a change to extraction can't break model.
- 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→5 extraction.email.mbox uses utils.attempt✕
- Connections
- 1 pair of types, where a type in extraction.email.mbox uses a type in utils.attempt.
- The types involved
extraction.email.mbox.MBoxEmailExtractor→utils.attempt.Failure
- Direction
- extraction.email.mbox uses utils.attempt, so a change to utils.attempt can break extraction.email.mbox, while a change to extraction.email.mbox can't break utils.attempt.
- Position
- Below the diagonal: extraction.email.mbox uses a module listed above it, which is the healthy direction.
23→7 extraction.email.mbox uses model.manifest✕
- Connections
- 1 pair of types, where a type in extraction.email.mbox uses a type in model.manifest.
- The types involved
extraction.email.mbox.MBoxEmailExtractor→model.manifest.Blob
- Direction
- extraction.email.mbox uses model.manifest, so a change to model.manifest can break extraction.email.mbox, while a change to extraction.email.mbox can't break model.manifest.
- Position
- Below the diagonal: extraction.email.mbox uses a module listed above it, which is the healthy direction.
23→8 extraction.email.mbox uses utils✕
- Connections
- 1 pair of types, where a type in extraction.email.mbox uses a type in utils.
- The types involved
extraction.email.mbox.MBoxEmailExtractor→utils.Logging
- Direction
- extraction.email.mbox uses utils, so a change to utils can break extraction.email.mbox, while a change to extraction.email.mbox can't break utils.
- Position
- Below the diagonal: extraction.email.mbox uses a module listed above it, which is the healthy direction.
23→22 extraction.email.mbox uses extraction✕
- Connections
- 2 pairs of types, where a type in extraction.email.mbox uses a type in extraction.
- The types involved
extraction.email.mbox.MBoxEmailExtractor→extraction.ExtractionParamsextraction.email.mbox.MBoxEmailExtractor→extraction.FileExtractor
- Direction
- extraction.email.mbox uses extraction, so a change to extraction can break extraction.email.mbox, while a change to extraction.email.mbox can't break extraction.
- Position
- Below the diagonal: extraction.email.mbox uses a module listed above it, which is the healthy direction.
24→14 model.index uses services.index✕
- Connections
- 1 pair of types, where a type in model.index uses a type in services.index.
- The types involved
model.index.SearchParameters→services.index.WorkspaceSearchContextParams
- Direction
- model.index uses services.index, so a change to services.index can break model.index, while a change to model.index can't break services.index.
- Position
- Below the diagonal: model.index uses a module listed above it, which is the healthy direction.
24→16 model.index uses model.frontend✕
- Connections
- 2 pairs of types, where a type in model.index uses a type in model.frontend.
- The types involved
model.index.HighlightableLanguageDataField→model.frontend.HighlightableTextmodel.index.HighlightableOcrLanguageData→model.frontend.HighlightableText
- Direction
- model.index uses model.frontend, so a change to model.frontend can break model.index, while a change to model.index can't break model.frontend.
- Position
- Below the diagonal: model.index uses a module listed above it, which is the healthy direction.
24→22 model.index uses extraction✕
- Connections
- 1 pair of types, where a type in model.index uses a type in extraction.
- The types involved
model.index.Document→extraction.EnrichedMetadata
- Direction
- model.index uses extraction, so a change to extraction can break model.index, while a change to model.index can't break extraction.
- Position
- Below the diagonal: model.index uses a module listed above it, which is the healthy direction.
24→26 model.index uses model part of a loop✕
- Connections
- 4 pairs of types, where a type in model.index uses a type in model.
- The types involved
model.index.Document→model.Urimodel.index.FrontendPage→model.Languagemodel.index.Page→model.Languagemodel.index.PageWithFind→model.Language
- Direction
- model.index uses model, so a change to model can break model.index, while a change to model.index can't break model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→5 extraction.tables uses utils.attempt✕
- Connections
- 3 pairs of types, where a type in extraction.tables uses a type in utils.attempt.
- The types involved
extraction.tables.CsvTableExtractor→utils.attempt.Failureextraction.tables.ExcelTableExtractor→utils.attempt.Attemptextraction.tables.ExcelTableExtractor→utils.attempt.Failure
- Direction
- extraction.tables uses utils.attempt, so a change to utils.attempt can break extraction.tables, while a change to extraction.tables can't break utils.attempt.
- Position
- Below the diagonal: extraction.tables uses a module listed above it, which is the healthy direction.
25→7 extraction.tables uses model.manifest✕
- Connections
- 2 pairs of types, where a type in extraction.tables uses a type in model.manifest.
- The types involved
extraction.tables.CsvTableExtractor→model.manifest.Blobextraction.tables.ExcelTableExtractor→model.manifest.Blob
- Direction
- extraction.tables uses model.manifest, so a change to model.manifest can break extraction.tables, while a change to extraction.tables can't break model.manifest.
- Position
- Below the diagonal: extraction.tables uses a module listed above it, which is the healthy direction.
25→8 extraction.tables uses utils✕
- Connections
- 1 pair of types, where a type in extraction.tables uses a type in utils.
- The types involved
extraction.tables.ExcelTableExtractor→utils.Logging
- Direction
- extraction.tables uses utils, so a change to utils can break extraction.tables, while a change to extraction.tables can't break utils.
- Position
- Below the diagonal: extraction.tables uses a module listed above it, which is the healthy direction.
25→22 extraction.tables uses extraction✕
- Connections
- 4 pairs of types, where a type in extraction.tables uses a type in extraction.
- The types involved
extraction.tables.CsvTableExtractor→extraction.ExtractionParamsextraction.tables.CsvTableExtractor→extraction.FileExtractorextraction.tables.ExcelTableExtractor→extraction.ExtractionParamsextraction.tables.ExcelTableExtractor→extraction.FileExtractor
- Direction
- extraction.tables uses extraction, so a change to extraction can break extraction.tables, while a change to extraction.tables can't break extraction.
- Position
- Below the diagonal: extraction.tables uses a module listed above it, which is the healthy direction.
25→24 extraction.tables uses model.index✕
- Connections
- 1 pair of types, where a type in extraction.tables uses a type in model.index.
- The types involved
extraction.tables.ExcelTableExtractor→model.index.TableRow
- Direction
- extraction.tables uses model.index, so a change to model.index can break extraction.tables, while a change to extraction.tables can't break model.index.
- Position
- Below the diagonal: extraction.tables uses a module listed above it, which is the healthy direction.
26→5 model uses utils.attempt✕
- Connections
- 1 pair of types, where a type in model uses a type in utils.attempt.
- The types involved
model.RichValue→utils.attempt.Attempt
- Direction
- model uses utils.attempt, so a change to utils.attempt can break model, while a change to model can't break utils.attempt.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
26→24 model uses model.index✕
- Connections
- 2 pairs of types, where a type in model uses a type in model.index.
- The types involved
model.Email→model.index.IndexedResourcemodel.Email→model.index.TranslationData
- Direction
- model uses model.index, so a change to model.index can break model, while a change to model can't break model.index.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
27→4 com.gu.pfi.cli.service uses model.user✕
- Connections
- 1 pair of types, where a type in com.gu.pfi.cli.service uses a type in model.user.
- The types involved
com.gu.pfi.cli.service.CliUsers→model.user.NewUser
- Direction
- com.gu.pfi.cli.service uses model.user, so a change to model.user can break com.gu.pfi.cli.service, while a change to com.gu.pfi.cli.service can't break model.user.
- Position
- Below the diagonal: com.gu.pfi.cli.service uses a module listed above it, which is the healthy direction.
27→5 com.gu.pfi.cli.service uses utils.attempt✕
- Connections
- 4 pairs of types, where a type in com.gu.pfi.cli.service uses a type in utils.attempt.
- The types involved
com.gu.pfi.cli.service.CliFiles→utils.attempt.Attemptcom.gu.pfi.cli.service.CliIngestionService→utils.attempt.Attemptcom.gu.pfi.cli.service.CliUsers→utils.attempt.Attemptcom.gu.pfi.cli.service.CliVeracrypt→utils.attempt.Attempt
- Direction
- com.gu.pfi.cli.service uses utils.attempt, so a change to utils.attempt can break com.gu.pfi.cli.service, while a change to com.gu.pfi.cli.service can't break utils.attempt.
- Position
- Below the diagonal: com.gu.pfi.cli.service uses a module listed above it, which is the healthy direction.
27→8 com.gu.pfi.cli.service uses utils✕
- Connections
- 2 pairs of types, where a type in com.gu.pfi.cli.service uses a type in utils.
- The types involved
com.gu.pfi.cli.service.CliIngestionService→utils.Loggingcom.gu.pfi.cli.service.DefaultIngestionS3Client→utils.Logging
- Direction
- com.gu.pfi.cli.service uses utils, so a change to utils can break com.gu.pfi.cli.service, while a change to com.gu.pfi.cli.service can't break utils.
- Position
- Below the diagonal: com.gu.pfi.cli.service uses a module listed above it, which is the healthy direction.
27→21 com.gu.pfi.cli.service uses model.ingestion✕
- Connections
- 2 pairs of types, where a type in com.gu.pfi.cli.service uses a type in model.ingestion.
- The types involved
com.gu.pfi.cli.service.DefaultIngestionS3Client→model.ingestion.OnDiskFileContextcom.gu.pfi.cli.service.IngestionS3Client→model.ingestion.OnDiskFileContext
- Direction
- com.gu.pfi.cli.service uses model.ingestion, so a change to model.ingestion can break com.gu.pfi.cli.service, while a change to com.gu.pfi.cli.service can't break model.ingestion.
- Position
- Below the diagonal: com.gu.pfi.cli.service uses a module listed above it, which is the healthy direction.
27→24 com.gu.pfi.cli.service uses model.index✕
- Connections
- 1 pair of types, where a type in com.gu.pfi.cli.service uses a type in model.index.
- The types involved
com.gu.pfi.cli.service.CliIngestionService→model.index.IndexedBlob
- Direction
- com.gu.pfi.cli.service uses model.index, so a change to model.index can break com.gu.pfi.cli.service, while a change to com.gu.pfi.cli.service can't break model.index.
- Position
- Below the diagonal: com.gu.pfi.cli.service uses a module listed above it, which is the healthy direction.
27→26 com.gu.pfi.cli.service uses model✕
- Connections
- 6 pairs of types, where a type in com.gu.pfi.cli.service uses a type in model.
- The types involved
com.gu.pfi.cli.service.CliIngestionService→model.CliCollectioncom.gu.pfi.cli.service.CliIngestionService→model.CliIngestioncom.gu.pfi.cli.service.CliIngestionService→model.CreateIngestionResponsecom.gu.pfi.cli.service.CliIngestionService→model.Languagecom.gu.pfi.cli.service.DefaultIngestionS3Client→model.Languagecom.gu.pfi.cli.service.IngestionS3Client→model.Language
- Direction
- com.gu.pfi.cli.service uses model, so a change to model can break com.gu.pfi.cli.service, while a change to com.gu.pfi.cli.service can't break model.
- Position
- Below the diagonal: com.gu.pfi.cli.service uses a module listed above it, which is the healthy direction.
28→21 ingestion uses model.ingestion✕
- Connections
- 3 pairs of types, where a type in ingestion uses a type in model.ingestion.
- The types involved
ingestion.IngestionContextBuilder→model.ingestion.EmailContextingestion.IngestionContextBuilder→model.ingestion.FileContextingestion.IngestionContextBuilder→model.ingestion.IngestionFile
- Direction
- ingestion uses model.ingestion, so a change to model.ingestion can break ingestion, while a change to ingestion can't break model.ingestion.
- Position
- Below the diagonal: ingestion uses a module listed above it, which is the healthy direction.
28→26 ingestion uses model✕
- Connections
- 2 pairs of types, where a type in ingestion uses a type in model.
- The types involved
ingestion.IngestionContextBuilder→model.Emailingestion.IngestionContextBuilder→model.Uri
- Direction
- ingestion uses model, so a change to model can break ingestion, while a change to ingestion can't break model.
- Position
- Below the diagonal: ingestion uses a module listed above it, which is the healthy direction.
29→5 services.annotations uses utils.attempt✕
- Connections
- 3 pairs of types, where a type in services.annotations uses a type in utils.attempt.
- The types involved
services.annotations.Annotations→utils.attempt.Attemptservices.annotations.Annotations→utils.attempt.Failureservices.annotations.Neo4jAnnotations→utils.attempt.Failure
- Direction
- services.annotations uses utils.attempt, so a change to utils.attempt can break services.annotations, while a change to services.annotations can't break utils.attempt.
- Position
- Below the diagonal: services.annotations uses a module listed above it, which is the healthy direction.
29→10 services.annotations uses services✕
- Connections
- 1 pair of types, where a type in services.annotations uses a type in services.
- The types involved
services.annotations.Neo4jAnnotations→services.Neo4jQueryLoggingConfig
- Direction
- services.annotations uses services, so a change to services can break services.annotations, while a change to services.annotations can't break services.
- Position
- Below the diagonal: services.annotations uses a module listed above it, which is the healthy direction.
29→16 services.annotations uses model.frontend✕
- Connections
- 1 pair of types, where a type in services.annotations uses a type in model.frontend.
- The types involved
services.annotations.Annotations→model.frontend.TreeEntry
- Direction
- services.annotations uses model.frontend, so a change to model.frontend can break services.annotations, while a change to services.annotations can't break model.frontend.
- Position
- Below the diagonal: services.annotations uses a module listed above it, which is the healthy direction.
29→19 services.annotations uses model.annotations✕
- Connections
- 4 pairs of types, where a type in services.annotations uses a type in model.annotations.
- The types involved
services.annotations.Annotations→model.annotations.Commentservices.annotations.Annotations→model.annotations.CommentAnchorservices.annotations.Annotations→model.annotations.WorkspaceEntryservices.annotations.Annotations→model.annotations.WorkspaceMetadata
- Direction
- services.annotations uses model.annotations, so a change to model.annotations can break services.annotations, while a change to services.annotations can't break model.annotations.
- Position
- Below the diagonal: services.annotations uses a module listed above it, which is the healthy direction.
29→21 services.annotations uses model.ingestion✕
- Connections
- 1 pair of types, where a type in services.annotations uses a type in model.ingestion.
- The types involved
services.annotations.Annotations→model.ingestion.RemoteIngest
- Direction
- services.annotations uses model.ingestion, so a change to model.ingestion can break services.annotations, while a change to services.annotations can't break model.ingestion.
- Position
- Below the diagonal: services.annotations uses a module listed above it, which is the healthy direction.
29→26 services.annotations uses model✕
- Connections
- 1 pair of types, where a type in services.annotations uses a type in model.
- The types involved
services.annotations.Annotations→model.Uri
- Direction
- services.annotations uses model, so a change to model can break services.annotations, while a change to services.annotations can't break model.
- Position
- Below the diagonal: services.annotations uses a module listed above it, which is the healthy direction.
30→5 services.ingestion uses utils.attempt✕
- Connections
- 5 pairs of types, where a type in services.ingestion uses a type in utils.attempt.
- The types involved
services.ingestion.IngestionServices→utils.attempt.Failureservices.ingestion.Neo4jRemoteIngestStore→utils.attempt.Failureservices.ingestion.RemoteIngestStore→utils.attempt.Attemptservices.ingestion.RemoteIngestStore→utils.attempt.Failureservices.ingestion.RemoteIngestWorker→utils.attempt.Failure
- Direction
- services.ingestion uses utils.attempt, so a change to utils.attempt can break services.ingestion, while a change to services.ingestion can't break utils.attempt.
- Position
- Below the diagonal: services.ingestion uses a module listed above it, which is the healthy direction.
30→7 services.ingestion uses model.manifest✕
- Connections
- 1 pair of types, where a type in services.ingestion uses a type in model.manifest.
- The types involved
services.ingestion.IngestionServices→model.manifest.Blob
- Direction
- services.ingestion uses model.manifest, so a change to model.manifest can break services.ingestion, while a change to services.ingestion can't break model.manifest.
- Position
- Below the diagonal: services.ingestion uses a module listed above it, which is the healthy direction.
30→8 services.ingestion uses utils✕
- Connections
- 1 pair of types, where a type in services.ingestion uses a type in utils.
- The types involved
services.ingestion.RemoteIngestWorker→utils.Logging
- Direction
- services.ingestion uses utils, so a change to utils can break services.ingestion, while a change to services.ingestion can't break utils.
- Position
- Below the diagonal: services.ingestion uses a module listed above it, which is the healthy direction.
30→10 services.ingestion uses services✕
- Connections
- 1 pair of types, where a type in services.ingestion uses a type in services.
- The types involved
services.ingestion.Neo4jRemoteIngestStore→services.Neo4jQueryLoggingConfig
- Direction
- services.ingestion uses services, so a change to services can break services.ingestion, while a change to services.ingestion can't break services.
- Position
- Below the diagonal: services.ingestion uses a module listed above it, which is the healthy direction.
30→19 services.ingestion uses model.annotations✕
- Connections
- 1 pair of types, where a type in services.ingestion uses a type in model.annotations.
- The types involved
services.ingestion.RemoteIngestWorker→model.annotations.WorkspaceMetadata
- Direction
- services.ingestion uses model.annotations, so a change to model.annotations can break services.ingestion, while a change to services.ingestion can't break model.annotations.
- Position
- Below the diagonal: services.ingestion uses a module listed above it, which is the healthy direction.
30→21 services.ingestion uses model.ingestion✕
- Connections
- 4 pairs of types, where a type in services.ingestion uses a type in model.ingestion.
- The types involved
services.ingestion.IngestionServices→model.ingestion.EmailContextservices.ingestion.IngestionServices→model.ingestion.FileContextservices.ingestion.RemoteIngestStore→model.ingestion.RemoteIngestservices.ingestion.RemoteIngestWorker→model.ingestion.RemoteIngest
- Direction
- services.ingestion uses model.ingestion, so a change to model.ingestion can break services.ingestion, while a change to services.ingestion can't break model.ingestion.
- Position
- Below the diagonal: services.ingestion uses a module listed above it, which is the healthy direction.
30→22 services.ingestion uses extraction✕
- Connections
- 2 pairs of types, where a type in services.ingestion uses a type in extraction.
- The types involved
services.ingestion.IngestionServices→extraction.ExtractionParamsservices.ingestion.IngestionServices→extraction.Extractor
- Direction
- services.ingestion uses extraction, so a change to extraction can break services.ingestion, while a change to services.ingestion can't break extraction.
- Position
- Below the diagonal: services.ingestion uses a module listed above it, which is the healthy direction.
30→26 services.ingestion uses model✕
- Connections
- 5 pairs of types, where a type in services.ingestion uses a type in model.
- The types involved
services.ingestion.IngestionServices→model.Uriservices.ingestion.RemoteIngestWorker→model.CreateIngestionResponseservices.ingestion.UriJustParent→model.Uriservices.ingestion.UriParent→model.Uriservices.ingestion.UriParentPair→model.Uri
- Direction
- services.ingestion uses model, so a change to model can break services.ingestion, while a change to services.ingestion can't break model.
- Position
- Below the diagonal: services.ingestion uses a module listed above it, which is the healthy direction.
31→5 services.manifest uses utils.attempt✕
- Connections
- 2 pairs of types, where a type in services.manifest uses a type in utils.attempt.
- The types involved
services.manifest.Neo4jManifest→utils.attempt.Failureservices.manifest.WorkerManifest→utils.attempt.Failure
- Direction
- services.manifest uses utils.attempt, so a change to utils.attempt can break services.manifest, while a change to services.manifest can't break utils.attempt.
- Position
- Below the diagonal: services.manifest uses a module listed above it, which is the healthy direction.
31→7 services.manifest uses model.manifest✕
- Connections
- 2 pairs of types, where a type in services.manifest uses a type in model.manifest.
- The types involved
services.manifest.WorkerManifest→model.manifest.Blobservices.manifest.WorkerManifest→model.manifest.WorkItem
- Direction
- services.manifest uses model.manifest, so a change to model.manifest can break services.manifest, while a change to services.manifest can't break model.manifest.
- Position
- Below the diagonal: services.manifest uses a module listed above it, which is the healthy direction.
31→10 services.manifest uses services✕
- Connections
- 1 pair of types, where a type in services.manifest uses a type in services.
- The types involved
services.manifest.Neo4jManifest→services.Neo4jQueryLoggingConfig
- Direction
- services.manifest uses services, so a change to services can break services.manifest, while a change to services.manifest can't break services.
- Position
- Below the diagonal: services.manifest uses a module listed above it, which is the healthy direction.
31→21 services.manifest uses model.ingestion✕
- Connections
- 1 pair of types, where a type in services.manifest uses a type in model.ingestion.
- The types involved
services.manifest.Neo4jManifest→model.ingestion.WorkspaceItemContext
- Direction
- services.manifest uses model.ingestion, so a change to model.ingestion can break services.manifest, while a change to services.manifest can't break model.ingestion.
- Position
- Below the diagonal: services.manifest uses a module listed above it, which is the healthy direction.
31→22 services.manifest uses extraction✕
- Connections
- 2 pairs of types, where a type in services.manifest uses a type in extraction.
- The types involved
services.manifest.WorkerManifest→extraction.ExtractionParamsservices.manifest.WorkerManifest→extraction.Extractor
- Direction
- services.manifest uses extraction, so a change to extraction can break services.manifest, while a change to services.manifest can't break extraction.
- Position
- Below the diagonal: services.manifest uses a module listed above it, which is the healthy direction.
31→26 services.manifest uses model✕
- Connections
- 1 pair of types, where a type in services.manifest uses a type in model.
- The types involved
services.manifest.WorkerManifest→model.Uri
- Direction
- services.manifest uses model, so a change to model can break services.manifest, while a change to services.manifest can't break model.
- Position
- Below the diagonal: services.manifest uses a module listed above it, which is the healthy direction.
32→5 com.gu.pfi.cli uses utils.attempt✕
- Connections
- 4 pairs of types, where a type in com.gu.pfi.cli uses a type in utils.attempt.
- The types involved
com.gu.pfi.cli.CommandValidator→utils.attempt.Attemptcom.gu.pfi.cli.DeleteIngestions→utils.attempt.Attemptcom.gu.pfi.cli.ErrorFormatter→utils.attempt.Failurecom.gu.pfi.cli.RunIngestion→utils.attempt.Attempt
- Direction
- com.gu.pfi.cli uses utils.attempt, so a change to utils.attempt can break com.gu.pfi.cli, while a change to com.gu.pfi.cli can't break utils.attempt.
- Position
- Below the diagonal: com.gu.pfi.cli uses a module listed above it, which is the healthy direction.
32→8 com.gu.pfi.cli uses utils✕
- Connections
- 3 pairs of types, where a type in com.gu.pfi.cli uses a type in utils.
- The types involved
com.gu.pfi.cli.DeleteIngestions→utils.Loggingcom.gu.pfi.cli.HashFiles→utils.Loggingcom.gu.pfi.cli.Main→utils.Logging
- Direction
- com.gu.pfi.cli uses utils, so a change to utils can break com.gu.pfi.cli, while a change to com.gu.pfi.cli can't break utils.
- Position
- Below the diagonal: com.gu.pfi.cli uses a module listed above it, which is the healthy direction.
32→27 com.gu.pfi.cli uses com.gu.pfi.cli.service✕
- Connections
- 1 pair of types, where a type in com.gu.pfi.cli uses a type in com.gu.pfi.cli.service.
- The types involved
com.gu.pfi.cli.Main→com.gu.pfi.cli.service.CliServices
- Direction
- com.gu.pfi.cli uses com.gu.pfi.cli.service, so a change to com.gu.pfi.cli.service can break com.gu.pfi.cli, while a change to com.gu.pfi.cli can't break com.gu.pfi.cli.service.
- Position
- Below the diagonal: com.gu.pfi.cli uses a module listed above it, which is the healthy direction.
33→5 extraction.archives uses utils.attempt✕
- Connections
- 2 pairs of types, where a type in extraction.archives uses a type in utils.attempt.
- The types involved
extraction.archives.RarExtractor→utils.attempt.Failureextraction.archives.ZipExtractor→utils.attempt.Failure
- Direction
- extraction.archives uses utils.attempt, so a change to utils.attempt can break extraction.archives, while a change to extraction.archives can't break utils.attempt.
- Position
- Below the diagonal: extraction.archives uses a module listed above it, which is the healthy direction.
33→7 extraction.archives uses model.manifest✕
- Connections
- 2 pairs of types, where a type in extraction.archives uses a type in model.manifest.
- The types involved
extraction.archives.RarExtractor→model.manifest.Blobextraction.archives.ZipExtractor→model.manifest.Blob
- Direction
- extraction.archives uses model.manifest, so a change to model.manifest can break extraction.archives, while a change to extraction.archives can't break model.manifest.
- Position
- Below the diagonal: extraction.archives uses a module listed above it, which is the healthy direction.
33→8 extraction.archives uses utils✕
- Connections
- 2 pairs of types, where a type in extraction.archives uses a type in utils.
- The types involved
extraction.archives.RarExtractor→utils.Loggingextraction.archives.ZipExtractor→utils.Logging
- Direction
- extraction.archives uses utils, so a change to utils can break extraction.archives, while a change to extraction.archives can't break utils.
- Position
- Below the diagonal: extraction.archives uses a module listed above it, which is the healthy direction.
33→21 extraction.archives uses model.ingestion✕
- Connections
- 1 pair of types, where a type in extraction.archives uses a type in model.ingestion.
- The types involved
extraction.archives.ZipExtractor→model.ingestion.FileContext
- Direction
- extraction.archives uses model.ingestion, so a change to model.ingestion can break extraction.archives, while a change to extraction.archives can't break model.ingestion.
- Position
- Below the diagonal: extraction.archives uses a module listed above it, which is the healthy direction.
33→22 extraction.archives uses extraction✕
- Connections
- 4 pairs of types, where a type in extraction.archives uses a type in extraction.
- The types involved
extraction.archives.RarExtractor→extraction.ExtractionParamsextraction.archives.RarExtractor→extraction.FileExtractorextraction.archives.ZipExtractor→extraction.ExtractionParamsextraction.archives.ZipExtractor→extraction.FileExtractor
- Direction
- extraction.archives uses extraction, so a change to extraction can break extraction.archives, while a change to extraction.archives can't break extraction.
- Position
- Below the diagonal: extraction.archives uses a module listed above it, which is the healthy direction.
33→28 extraction.archives uses ingestion✕
- Connections
- 1 pair of types, where a type in extraction.archives uses a type in ingestion.
- The types involved
extraction.archives.ZipExtractor→ingestion.IngestionContextBuilder
- Direction
- extraction.archives uses ingestion, so a change to ingestion can break extraction.archives, while a change to extraction.archives can't break ingestion.
- Position
- Below the diagonal: extraction.archives uses a module listed above it, which is the healthy direction.
34→5 extraction.email.eml uses utils.attempt✕
- Connections
- 1 pair of types, where a type in extraction.email.eml uses a type in utils.attempt.
- The types involved
extraction.email.eml.EmlEmailExtractor→utils.attempt.Failure
- Direction
- extraction.email.eml uses utils.attempt, so a change to utils.attempt can break extraction.email.eml, while a change to extraction.email.eml can't break utils.attempt.
- Position
- Below the diagonal: extraction.email.eml uses a module listed above it, which is the healthy direction.
34→7 extraction.email.eml uses model.manifest✕
- Connections
- 1 pair of types, where a type in extraction.email.eml uses a type in model.manifest.
- The types involved
extraction.email.eml.EmlEmailExtractor→model.manifest.Blob
- Direction
- extraction.email.eml uses model.manifest, so a change to model.manifest can break extraction.email.eml, while a change to extraction.email.eml can't break model.manifest.
- Position
- Below the diagonal: extraction.email.eml uses a module listed above it, which is the healthy direction.
34→8 extraction.email.eml uses utils✕
- Connections
- 2 pairs of types, where a type in extraction.email.eml uses a type in utils.
- The types involved
extraction.email.eml.EmlEmailExtractor→utils.Loggingextraction.email.eml.EmlParser→utils.Logging
- Direction
- extraction.email.eml uses utils, so a change to utils can break extraction.email.eml, while a change to extraction.email.eml can't break utils.
- Position
- Below the diagonal: extraction.email.eml uses a module listed above it, which is the healthy direction.
34→10 extraction.email.eml uses services✕
- Connections
- 1 pair of types, where a type in extraction.email.eml uses a type in services.
- The types involved
extraction.email.eml.EmlParser→services.ScratchSpace
- Direction
- extraction.email.eml uses services, so a change to services can break extraction.email.eml, while a change to extraction.email.eml can't break services.
- Position
- Below the diagonal: extraction.email.eml uses a module listed above it, which is the healthy direction.
34→22 extraction.email.eml uses extraction✕
- Connections
- 2 pairs of types, where a type in extraction.email.eml uses a type in extraction.
- The types involved
extraction.email.eml.EmlEmailExtractor→extraction.ExtractionParamsextraction.email.eml.EmlEmailExtractor→extraction.Extractor
- Direction
- extraction.email.eml uses extraction, so a change to extraction can break extraction.email.eml, while a change to extraction.email.eml can't break extraction.
- Position
- Below the diagonal: extraction.email.eml uses a module listed above it, which is the healthy direction.
34→26 extraction.email.eml uses model✕
- Connections
- 2 pairs of types, where a type in extraction.email.eml uses a type in model.
- The types involved
extraction.email.eml.EmlParser→model.Emailextraction.email.eml.EmlParser→model.Uri
- Direction
- extraction.email.eml uses model, so a change to model can break extraction.email.eml, while a change to extraction.email.eml can't break model.
- Position
- Below the diagonal: extraction.email.eml uses a module listed above it, which is the healthy direction.
34→28 extraction.email.eml uses ingestion✕
- Connections
- 1 pair of types, where a type in extraction.email.eml uses a type in ingestion.
- The types involved
extraction.email.eml.EmlParser→ingestion.IngestionContextBuilder
- Direction
- extraction.email.eml uses ingestion, so a change to ingestion can break extraction.email.eml, while a change to extraction.email.eml can't break ingestion.
- Position
- Below the diagonal: extraction.email.eml uses a module listed above it, which is the healthy direction.
34→30 extraction.email.eml uses services.ingestion✕
- Connections
- 1 pair of types, where a type in extraction.email.eml uses a type in services.ingestion.
- The types involved
extraction.email.eml.EmlParser→services.ingestion.IngestionServices
- Direction
- extraction.email.eml uses services.ingestion, so a change to services.ingestion can break extraction.email.eml, while a change to extraction.email.eml can't break services.ingestion.
- Position
- Below the diagonal: extraction.email.eml uses a module listed above it, which is the healthy direction.
35→5 extraction.email.olm uses utils.attempt✕
- Connections
- 1 pair of types, where a type in extraction.email.olm uses a type in utils.attempt.
- The types involved
extraction.email.olm.OlmEmailExtractor→utils.attempt.Failure
- Direction
- extraction.email.olm uses utils.attempt, so a change to utils.attempt can break extraction.email.olm, while a change to extraction.email.olm can't break utils.attempt.
- Position
- Below the diagonal: extraction.email.olm uses a module listed above it, which is the healthy direction.
35→7 extraction.email.olm uses model.manifest✕
- Connections
- 1 pair of types, where a type in extraction.email.olm uses a type in model.manifest.
- The types involved
extraction.email.olm.OlmEmailExtractor→model.manifest.Blob
- Direction
- extraction.email.olm uses model.manifest, so a change to model.manifest can break extraction.email.olm, while a change to extraction.email.olm can't break model.manifest.
- Position
- Below the diagonal: extraction.email.olm uses a module listed above it, which is the healthy direction.
35→8 extraction.email.olm uses utils✕
- Connections
- 1 pair of types, where a type in extraction.email.olm uses a type in utils.
- The types involved
extraction.email.olm.OlmEmailExtractor→utils.Logging
- Direction
- extraction.email.olm uses utils, so a change to utils can break extraction.email.olm, while a change to extraction.email.olm can't break utils.
- Position
- Below the diagonal: extraction.email.olm uses a module listed above it, which is the healthy direction.
35→21 extraction.email.olm uses model.ingestion✕
- Connections
- 1 pair of types, where a type in extraction.email.olm uses a type in model.ingestion.
- The types involved
extraction.email.olm.OlmEmailExtractor→model.ingestion.FileContext
- Direction
- extraction.email.olm uses model.ingestion, so a change to model.ingestion can break extraction.email.olm, while a change to extraction.email.olm can't break model.ingestion.
- Position
- Below the diagonal: extraction.email.olm uses a module listed above it, which is the healthy direction.
35→22 extraction.email.olm uses extraction✕
- Connections
- 2 pairs of types, where a type in extraction.email.olm uses a type in extraction.
- The types involved
extraction.email.olm.OlmEmailExtractor→extraction.ExtractionParamsextraction.email.olm.OlmEmailExtractor→extraction.FileExtractor
- Direction
- extraction.email.olm uses extraction, so a change to extraction can break extraction.email.olm, while a change to extraction.email.olm can't break extraction.
- Position
- Below the diagonal: extraction.email.olm uses a module listed above it, which is the healthy direction.
35→26 extraction.email.olm uses model✕
- Connections
- 2 pairs of types, where a type in extraction.email.olm uses a type in model.
- The types involved
extraction.email.olm.OlmEmailExtractor→model.Uriextraction.email.olm.OlmMessage→model.Recipient
- Direction
- extraction.email.olm uses model, so a change to model can break extraction.email.olm, while a change to extraction.email.olm can't break model.
- Position
- Below the diagonal: extraction.email.olm uses a module listed above it, which is the healthy direction.
35→28 extraction.email.olm uses ingestion✕
- Connections
- 1 pair of types, where a type in extraction.email.olm uses a type in ingestion.
- The types involved
extraction.email.olm.OlmEmailExtractor→ingestion.IngestionContextBuilder
- Direction
- extraction.email.olm uses ingestion, so a change to ingestion can break extraction.email.olm, while a change to extraction.email.olm can't break ingestion.
- Position
- Below the diagonal: extraction.email.olm uses a module listed above it, which is the healthy direction.
36→5 extraction.email.pst uses utils.attempt✕
- Connections
- 1 pair of types, where a type in extraction.email.pst uses a type in utils.attempt.
- The types involved
extraction.email.pst.PstEmailExtractor→utils.attempt.Failure
- Direction
- extraction.email.pst uses utils.attempt, so a change to utils.attempt can break extraction.email.pst, while a change to extraction.email.pst can't break utils.attempt.
- Position
- Below the diagonal: extraction.email.pst uses a module listed above it, which is the healthy direction.
36→7 extraction.email.pst uses model.manifest✕
- Connections
- 1 pair of types, where a type in extraction.email.pst uses a type in model.manifest.
- The types involved
extraction.email.pst.PstEmailExtractor→model.manifest.Blob
- Direction
- extraction.email.pst uses model.manifest, so a change to model.manifest can break extraction.email.pst, while a change to extraction.email.pst can't break model.manifest.
- Position
- Below the diagonal: extraction.email.pst uses a module listed above it, which is the healthy direction.
36→8 extraction.email.pst uses utils✕
- Connections
- 1 pair of types, where a type in extraction.email.pst uses a type in utils.
- The types involved
extraction.email.pst.PstEmailExtractor→utils.Logging
- Direction
- extraction.email.pst uses utils, so a change to utils can break extraction.email.pst, while a change to extraction.email.pst can't break utils.
- Position
- Below the diagonal: extraction.email.pst uses a module listed above it, which is the healthy direction.
36→22 extraction.email.pst uses extraction✕
- Connections
- 2 pairs of types, where a type in extraction.email.pst uses a type in extraction.
- The types involved
extraction.email.pst.PstEmailExtractor→extraction.ExtractionParamsextraction.email.pst.PstEmailExtractor→extraction.FileExtractor
- Direction
- extraction.email.pst uses extraction, so a change to extraction can break extraction.email.pst, while a change to extraction.email.pst can't break extraction.
- Position
- Below the diagonal: extraction.email.pst uses a module listed above it, which is the healthy direction.
36→28 extraction.email.pst uses ingestion✕
- Connections
- 1 pair of types, where a type in extraction.email.pst uses a type in ingestion.
- The types involved
extraction.email.pst.PstEmailExtractor→ingestion.IngestionContextBuilder
- Direction
- extraction.email.pst uses ingestion, so a change to ingestion can break extraction.email.pst, while a change to extraction.email.pst can't break ingestion.
- Position
- Below the diagonal: extraction.email.pst uses a module listed above it, which is the healthy direction.
37→4 services.users uses model.user✕
- Connections
- 4 pairs of types, where a type in services.users uses a type in model.user.
- The types involved
services.users.UserManagement→model.user.BCryptPasswordservices.users.UserManagement→model.user.DBUserservices.users.UserManagement→model.user.UserPermissionservices.users.UserManagement→model.user.UserPermissions
- Direction
- services.users uses model.user, so a change to model.user can break services.users, while a change to services.users can't break model.user.
- Position
- Below the diagonal: services.users uses a module listed above it, which is the healthy direction.
37→5 services.users uses utils.attempt✕
- Connections
- 1 pair of types, where a type in services.users uses a type in utils.attempt.
- The types involved
services.users.UserManagement→utils.attempt.Attempt
- Direction
- services.users uses utils.attempt, so a change to utils.attempt can break services.users, while a change to services.users can't break utils.attempt.
- Position
- Below the diagonal: services.users uses a module listed above it, which is the healthy direction.
37→10 services.users uses services✕
- Connections
- 1 pair of types, where a type in services.users uses a type in services.
- The types involved
services.users.Neo4jUserManagement→services.Neo4jQueryLoggingConfig
- Direction
- services.users uses services, so a change to services can break services.users, while a change to services.users can't break services.
- Position
- Below the diagonal: services.users uses a module listed above it, which is the healthy direction.
37→14 services.users uses services.index✕
- Connections
- 2 pairs of types, where a type in services.users uses a type in services.index.
- The types involved
services.users.Neo4jUserManagement→services.index.Indexservices.users.Neo4jUserManagement→services.index.Pages
- Direction
- services.users uses services.index, so a change to services.index can break services.users, while a change to services.users can't break services.index.
- Position
- Below the diagonal: services.users uses a module listed above it, which is the healthy direction.
37→26 services.users uses model✕
- Connections
- 1 pair of types, where a type in services.users uses a type in model.
- The types involved
services.users.UserManagement→model.Uri
- Direction
- services.users uses model, so a change to model can break services.users, while a change to services.users can't break model.
- Position
- Below the diagonal: services.users uses a module listed above it, which is the healthy direction.
37→29 services.users uses services.annotations✕
- Connections
- 1 pair of types, where a type in services.users uses a type in services.annotations.
- The types involved
services.users.Neo4jUserManagement→services.annotations.Annotations
- Direction
- services.users uses services.annotations, so a change to services.annotations can break services.users, while a change to services.users can't break services.annotations.
- Position
- Below the diagonal: services.users uses a module listed above it, which is the healthy direction.
37→31 services.users uses services.manifest✕
- Connections
- 1 pair of types, where a type in services.users uses a type in services.manifest.
- The types involved
services.users.Neo4jUserManagement→services.manifest.Manifest
- Direction
- services.users uses services.manifest, so a change to services.manifest can break services.users, while a change to services.users can't break services.manifest.
- Position
- Below the diagonal: services.users uses a module listed above it, which is the healthy direction.
38→5 commands uses utils.attempt✕
- Connections
- 13 pairs of types, where a type in commands uses a type in utils.attempt.
- The types involved
commands.CreateCollection→utils.attempt.Attemptcommands.CreateIngestion→utils.attempt.Attemptcommands.DeleteResource→utils.attempt.Attemptcommands.EmailThread→utils.attempt.Failurecommands.GetBlobObjectData→utils.attempt.Failurecommands.GetFilters→utils.attempt.Attemptcommands.GetPagePreview→utils.attempt.Attemptcommands.GetPages→utils.attempt.Attemptcommands.GetResource→utils.attempt.Attemptcommands.IngestFile→utils.attempt.Attemptcommands.MoveIngestion→utils.attempt.Attemptcommands.TFACommands→utils.attempt.Attemptcommands.VerifyIngestion→utils.attempt.Failure
- Direction
- commands uses utils.attempt, so a change to utils.attempt can break commands, while a change to commands can't break utils.attempt.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→7 commands uses model.manifest✕
- Connections
- 5 pairs of types, where a type in commands uses a type in model.manifest.
- The types involved
commands.CreateCollection→model.manifest.Collectioncommands.IngestFile→model.manifest.Blobcommands.IngestFile→model.manifest.Ingestioncommands.IngestFileResult→model.manifest.Blobcommands.VerifyIngestion→model.manifest.Blob
- Direction
- commands uses model.manifest, so a change to model.manifest can break commands, while a change to commands can't break model.manifest.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→8 commands uses utils✕
- Connections
- 4 pairs of types, where a type in commands uses a type in utils.
- The types involved
commands.CreateIngestion→utils.Loggingcommands.DeleteResource→utils.Timingcommands.MoveIngestion→utils.Loggingcommands.TFACommands→utils.Epoch
- Direction
- commands uses utils, so a change to utils can break commands, while a change to commands can't break utils.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→10 commands uses services✕
- Connections
- 1 pair of types, where a type in commands uses a type in services.
- The types involved
commands.GetBlobObjectData→services.ObjectStorage
- Direction
- commands uses services, so a change to services can break commands, while a change to commands can't break services.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→14 commands uses services.index✕
- Connections
- 4 pairs of types, where a type in commands uses a type in services.index.
- The types involved
commands.CreateIngestion→services.index.Indexcommands.CreateIngestion→services.index.Pagescommands.GetResource→services.index.Indexcommands.MoveIngestion→services.index.Index
- Direction
- commands uses services.index, so a change to services.index can break commands, while a change to commands can't break services.index.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→16 commands uses model.frontend✕
- Connections
- 4 pairs of types, where a type in commands uses a type in model.frontend.
- The types involved
commands.GetFilters→model.frontend.Filtercommands.GetResource→model.frontend.BasicResourcecommands.GetResource→model.frontend.Resourcecommands.TFACommands→model.frontend.TotpActivation
- Direction
- commands uses model.frontend, so a change to model.frontend can break commands, while a change to commands can't break model.frontend.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→21 commands uses model.ingestion✕
- Connections
- 2 pairs of types, where a type in commands uses a type in model.ingestion.
- The types involved
commands.IngestFile→model.ingestion.FileContextcommands.IngestFile→model.ingestion.WorkspaceItemContext
- Direction
- commands uses model.ingestion, so a change to model.ingestion can break commands, while a change to commands can't break model.ingestion.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→24 commands uses model.index✕
- Connections
- 3 pairs of types, where a type in commands uses a type in model.index.
- The types involved
commands.GetPages→model.index.FrontendPageResultcommands.GetPages→model.index.PageHighlightcommands.GetPages→model.index.PageResult
- Direction
- commands uses model.index, so a change to model.index can break commands, while a change to commands can't break model.index.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→26 commands uses model✕
- Connections
- 12 pairs of types, where a type in commands uses a type in model.
- The types involved
commands.CreateIngestion→model.CreateIngestionRequestcommands.CreateIngestion→model.Uricommands.DeleteResource→model.Languagecommands.DeleteResource→model.Uricommands.GetBlobObjectData→model.ObjectDatacommands.GetBlobObjectData→model.Uricommands.GetPages→model.Languagecommands.GetPages→model.Uricommands.GetResource→model.Uricommands.MoveIngestion→model.Uricommands.VerifyIngestion→model.VerifyRequestFilecommands.VerifyIngestion→model.VerifyResponse
- Direction
- commands uses model, so a change to model can break commands, while a change to commands can't break model.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→29 commands uses services.annotations✕
- Connections
- 2 pairs of types, where a type in commands uses a type in services.annotations.
- The types involved
commands.GetFilters→services.annotations.Annotationscommands.GetResource→services.annotations.Annotations
- Direction
- commands uses services.annotations, so a change to services.annotations can break commands, while a change to commands can't break services.annotations.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→31 commands uses services.manifest✕
- Connections
- 7 pairs of types, where a type in commands uses a type in services.manifest.
- The types involved
commands.CreateCollection→services.manifest.Manifestcommands.CreateIngestion→services.manifest.Manifestcommands.EmailThread→services.manifest.Manifestcommands.GetBlobObjectData→services.manifest.Manifestcommands.GetFilters→services.manifest.Manifestcommands.GetResource→services.manifest.Manifestcommands.MoveIngestion→services.manifest.Manifest
- Direction
- commands uses services.manifest, so a change to services.manifest can break commands, while a change to commands can't break services.manifest.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→37 commands uses services.users✕
- Connections
- 2 pairs of types, where a type in commands uses a type in services.users.
- The types involved
commands.GetFilters→services.users.UserManagementcommands.GetResource→services.users.UserManagement
- Direction
- commands uses services.users, so a change to services.users can break commands, while a change to commands can't break services.users.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
39→4 utils.controller uses model.user✕
- Connections
- 1 pair of types, where a type in utils.controller uses a type in model.user.
- The types involved
utils.controller.AuthApiController→model.user.UserPermission
- Direction
- utils.controller uses model.user, so a change to model.user can break utils.controller, while a change to utils.controller can't break model.user.
- Position
- Below the diagonal: utils.controller uses a module listed above it, which is the healthy direction.
39→5 utils.controller uses utils.attempt✕
- Connections
- 9 pairs of types, where a type in utils.controller uses a type in utils.attempt.
- The types involved
utils.controller.AuthApiController→utils.attempt.Attemptutils.controller.AuthApiController→utils.attempt.Failureutils.controller.CloudWatchReportingFailureToResultMapper→utils.attempt.Failureutils.controller.DefaultFailureToResultMapper→utils.attempt.Failureutils.controller.DownloadHelper→utils.attempt.Attemptutils.controller.FailureToResultMapper→utils.attempt.Failureutils.controller.NoAuthApiController→utils.attempt.Failureutils.controller.PfiApiController→utils.attempt.Failureutils.controller.ResourceDownloadHelper→utils.attempt.Attempt
- Direction
- utils.controller uses utils.attempt, so a change to utils.attempt can break utils.controller, while a change to utils.controller can't break utils.attempt.
- Position
- Below the diagonal: utils.controller uses a module listed above it, which is the healthy direction.
39→8 utils.controller uses utils✕
- Connections
- 3 pairs of types, where a type in utils.controller uses a type in utils.
- The types involved
utils.controller.CloudWatchReportingFailureToResultMapper→utils.Loggingutils.controller.DefaultFailureToResultMapper→utils.Loggingutils.controller.DownloadHelper→utils.Logging
- Direction
- utils.controller uses utils, so a change to utils can break utils.controller, while a change to utils.controller can't break utils.
- Position
- Below the diagonal: utils.controller uses a module listed above it, which is the healthy direction.
39→14 utils.controller uses services.index✕
- Connections
- 1 pair of types, where a type in utils.controller uses a type in services.index.
- The types involved
utils.controller.ResourceDownloadHelper→services.index.Index
- Direction
- utils.controller uses services.index, so a change to services.index can break utils.controller, while a change to utils.controller can't break services.index.
- Position
- Below the diagonal: utils.controller uses a module listed above it, which is the healthy direction.
39→26 utils.controller uses model✕
- Connections
- 1 pair of types, where a type in utils.controller uses a type in model.
- The types involved
utils.controller.DownloadHelper→model.Uri
- Direction
- utils.controller uses model, so a change to model can break utils.controller, while a change to utils.controller can't break model.
- Position
- Below the diagonal: utils.controller uses a module listed above it, which is the healthy direction.
39→29 utils.controller uses services.annotations✕
- Connections
- 1 pair of types, where a type in utils.controller uses a type in services.annotations.
- The types involved
utils.controller.ResourceDownloadHelper→services.annotations.Annotations
- Direction
- utils.controller uses services.annotations, so a change to services.annotations can break utils.controller, while a change to utils.controller can't break services.annotations.
- Position
- Below the diagonal: utils.controller uses a module listed above it, which is the healthy direction.
39→31 utils.controller uses services.manifest✕
- Connections
- 1 pair of types, where a type in utils.controller uses a type in services.manifest.
- The types involved
utils.controller.ResourceDownloadHelper→services.manifest.Manifest
- Direction
- utils.controller uses services.manifest, so a change to services.manifest can break utils.controller, while a change to utils.controller can't break services.manifest.
- Position
- Below the diagonal: utils.controller uses a module listed above it, which is the healthy direction.
39→37 utils.controller uses services.users✕
- Connections
- 2 pairs of types, where a type in utils.controller uses a type in services.users.
- The types involved
utils.controller.AuthControllerComponents→services.users.UserManagementutils.controller.ResourceDownloadHelper→services.users.UserManagement
- Direction
- utils.controller uses services.users, so a change to services.users can break utils.controller, while a change to utils.controller can't break services.users.
- Position
- Below the diagonal: utils.controller uses a module listed above it, which is the healthy direction.
40→5 controllers.api uses utils.attempt✕
- Connections
- 7 pairs of types, where a type in controllers.api uses a type in utils.attempt.
- The types involved
controllers.api.Blobs→utils.attempt.Attemptcontrollers.api.Events→utils.attempt.Attemptcontrollers.api.PagesController→utils.attempt.Attemptcontrollers.api.Previews→utils.attempt.Attemptcontrollers.api.Search→utils.attempt.Attemptcontrollers.api.Users→utils.attempt.Attemptcontrollers.api.Workspaces→utils.attempt.Attempt
- Direction
- controllers.api uses utils.attempt, so a change to utils.attempt can break controllers.api, while a change to controllers.api can't break utils.attempt.
- Position
- Below the diagonal: controllers.api uses a module listed above it, which is the healthy direction.
40→7 controllers.api uses model.manifest✕
- Connections
- 1 pair of types, where a type in controllers.api uses a type in model.manifest.
- The types involved
controllers.api.Users→model.manifest.UserWithCollections
- Direction
- controllers.api uses model.manifest, so a change to model.manifest can break controllers.api, while a change to controllers.api can't break model.manifest.
- Position
- Below the diagonal: controllers.api uses a module listed above it, which is the healthy direction.
40→8 controllers.api uses utils✕
- Connections
- 7 pairs of types, where a type in controllers.api uses a type in utils.
- The types involved
controllers.api.Authentication→utils.Loggingcontrollers.api.Blobs→utils.Loggingcontrollers.api.Documents→utils.Loggingcontrollers.api.Search→utils.Loggingcontrollers.api.Users→utils.Loggingcontrollers.api.VideoVerifier→utils.Loggingcontrollers.api.Workspaces→utils.Logging
- Direction
- controllers.api uses utils, so a change to utils can break controllers.api, while a change to controllers.api can't break utils.
- Position
- Below the diagonal: controllers.api uses a module listed above it, which is the healthy direction.
40→14 controllers.api uses services.index✕
- Connections
- 3 pairs of types, where a type in controllers.api uses a type in services.index.
- The types involved
controllers.api.Documents→services.index.Indexcontrollers.api.Previews→services.index.Indexcontrollers.api.Search→services.index.WorkspaceSearchContextParams
- Direction
- controllers.api uses services.index, so a change to services.index can break controllers.api, while a change to controllers.api can't break services.index.
- Position
- Below the diagonal: controllers.api uses a module listed above it, which is the healthy direction.
40→16 controllers.api uses model.frontend✕
- Connections
- 2 pairs of types, where a type in controllers.api uses a type in model.frontend.
- The types involved
controllers.api.PagesController→model.frontend.TextHighlightcontrollers.api.Workspaces→model.frontend.TreeEntry
- Direction
- controllers.api uses model.frontend, so a change to model.frontend can break controllers.api, while a change to controllers.api can't break model.frontend.
- Position
- Below the diagonal: controllers.api uses a module listed above it, which is the healthy direction.
40→17 controllers.api uses model.frontend.user✕
- Connections
- 1 pair of types, where a type in controllers.api uses a type in model.frontend.user.
- The types involved
controllers.api.Users→model.frontend.user.PartialUser
- Direction
- controllers.api uses model.frontend.user, so a change to model.frontend.user can break controllers.api, while a change to controllers.api can't break model.frontend.user.
- Position
- Below the diagonal: controllers.api uses a module listed above it, which is the healthy direction.
40→18 controllers.api uses services.events✕
- Connections
- 1 pair of types, where a type in controllers.api uses a type in services.events.
- The types involved
controllers.api.Events→services.events.Event
- Direction
- controllers.api uses services.events, so a change to services.events can break controllers.api, while a change to controllers.api can't break services.events.
- Position
- Below the diagonal: controllers.api uses a module listed above it, which is the healthy direction.
40→19 controllers.api uses model.annotations✕
- Connections
- 2 pairs of types, where a type in controllers.api uses a type in model.annotations.
- The types involved
controllers.api.PostCommentData→model.annotations.CommentAnchorcontrollers.api.Workspaces→model.annotations.WorkspaceEntry
- Direction
- controllers.api uses model.annotations, so a change to model.annotations can break controllers.api, while a change to controllers.api can't break model.annotations.
- Position
- Below the diagonal: controllers.api uses a module listed above it, which is the healthy direction.
40→21 controllers.api uses model.ingestion✕
- Connections
- 1 pair of types, where a type in controllers.api uses a type in model.ingestion.
- The types involved
controllers.api.Collections→model.ingestion.WorkspaceItemUploadContext
- Direction
- controllers.api uses model.ingestion, so a change to model.ingestion can break controllers.api, while a change to controllers.api can't break model.ingestion.
- Position
- Below the diagonal: controllers.api uses a module listed above it, which is the healthy direction.
40→24 controllers.api uses model.index✕
- Connections
- 3 pairs of types, where a type in controllers.api uses a type in model.index.
- The types involved
controllers.api.PagesController→model.index.FrontendPagecontrollers.api.PagesController→model.index.HighlightForSearchNavigationcontrollers.api.Search→model.index.SearchParameters
- Direction
- controllers.api uses model.index, so a change to model.index can break controllers.api, while a change to controllers.api can't break model.index.
- Position
- Below the diagonal: controllers.api uses a module listed above it, which is the healthy direction.
40→26 controllers.api uses model✕
- Connections
- 9 pairs of types, where a type in controllers.api uses a type in model.
- The types involved
controllers.api.Collections→model.Uricontrollers.api.Comments→model.Uricontrollers.api.Documents→model.Uricontrollers.api.PagesController→model.Languagecontrollers.api.PagesController→model.Uricontrollers.api.Previews→model.Uricontrollers.api.Resource→model.Languagecontrollers.api.Resource→model.Uricontrollers.api.Workspaces→model.Uri
- Direction
- controllers.api uses model, so a change to model can break controllers.api, while a change to controllers.api can't break model.
- Position
- Below the diagonal: controllers.api uses a module listed above it, which is the healthy direction.
40→29 controllers.api uses services.annotations✕
- Connections
- 2 pairs of types, where a type in controllers.api uses a type in services.annotations.
- The types involved
controllers.api.Documents→services.annotations.Annotationscontrollers.api.Previews→services.annotations.Annotations
- Direction
- controllers.api uses services.annotations, so a change to services.annotations can break controllers.api, while a change to controllers.api can't break services.annotations.
- Position
- Below the diagonal: controllers.api uses a module listed above it, which is the healthy direction.
40→31 controllers.api uses services.manifest✕
- Connections
- 2 pairs of types, where a type in controllers.api uses a type in services.manifest.
- The types involved
controllers.api.Documents→services.manifest.Manifestcontrollers.api.Previews→services.manifest.Manifest
- Direction
- controllers.api uses services.manifest, so a change to services.manifest can break controllers.api, while a change to controllers.api can't break services.manifest.
- Position
- Below the diagonal: controllers.api uses a module listed above it, which is the healthy direction.
40→37 controllers.api uses services.users✕
- Connections
- 2 pairs of types, where a type in controllers.api uses a type in services.users.
- The types involved
controllers.api.Documents→services.users.UserManagementcontrollers.api.Previews→services.users.UserManagement
- Direction
- controllers.api uses services.users, so a change to services.users can break controllers.api, while a change to controllers.api can't break services.users.
- Position
- Below the diagonal: controllers.api uses a module listed above it, which is the healthy direction.
40→38 controllers.api uses commands✕
- Connections
- 1 pair of types, where a type in controllers.api uses a type in commands.
- The types involved
controllers.api.Collections→commands.IngestFileResult
- Direction
- controllers.api uses commands, so a change to commands can break controllers.api, while a change to controllers.api can't break commands.
- Position
- Below the diagonal: controllers.api uses a module listed above it, which is the healthy direction.
40→39 controllers.api uses utils.controller✕
- Connections
- 36 pairs of types, where a type in controllers.api uses a type in utils.controller. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
controllers.api.Authentication→utils.controller.AuthControllerComponentscontrollers.api.Authentication→utils.controller.OptionalAuthApiControllercontrollers.api.Blobs→utils.controller.AuthApiControllercontrollers.api.Blobs→utils.controller.AuthControllerComponentscontrollers.api.Collections→utils.controller.AuthApiControllercontrollers.api.Collections→utils.controller.AuthControllerComponentscontrollers.api.Comments→utils.controller.AuthApiControllercontrollers.api.Comments→utils.controller.AuthControllerComponentscontrollers.api.Documents→utils.controller.AuthControllerComponentscontrollers.api.Documents→utils.controller.OptionalAuthApiControllercontrollers.api.Documents→utils.controller.ResourceDownloadHelpercontrollers.api.Events→utils.controller.AuthApiControllercontrollers.api.Events→utils.controller.AuthControllerComponentscontrollers.api.Filters→utils.controller.AuthApiControllercontrollers.api.Filters→utils.controller.AuthControllerComponentscontrollers.api.Ingestion→utils.controller.AuthApiControllercontrollers.api.Ingestion→utils.controller.AuthControllerComponentscontrollers.api.IngestionEvents→utils.controller.AuthApiControllercontrollers.api.IngestionEvents→utils.controller.AuthControllerComponentscontrollers.api.MimeTypes→utils.controller.AuthApiControllercontrollers.api.MimeTypes→utils.controller.AuthControllerComponentscontrollers.api.PagesController→utils.controller.AuthApiControllercontrollers.api.PagesController→utils.controller.AuthControllerComponentscontrollers.api.Previews→utils.controller.AuthControllerComponentscontrollers.api.Previews→utils.controller.OptionalAuthApiController
- Direction
- controllers.api uses utils.controller, so a change to utils.controller can break controllers.api, while a change to controllers.api can't break utils.controller.
- Position
- Below the diagonal: controllers.api 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 |
|---|---|---|
| A05:2025 — Injection | 30 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 28 | High / Critical |
| A02:2025 — Security Misconfiguration | 7 | High / Critical |
| A07:2025 — Authentication Failures | 6 | High / Critical |
Roadmap
Top priorities: Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED; 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; Resolve the 1 finding(s) in DR & Backup.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED. | +8.0 pts | Low | REDACTED Scanning |
| 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. | +4.0 pts | Medium | Security & performance tooling |
| Resolve the 1 finding(s) in DR & Backup. | +4.0 pts | Medium | DR & Backup |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +3.2 pts | Medium | Keyboard semantics |
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +2.9 pts | Medium | Text alternatives |
| Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED (2). | +1.0 pts | Low | Static Analysis (SAST) |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +1.6 pts | Medium | Dependency Hygiene |
| 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. | +1.5 pts | Medium | Nullable reference types |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.4 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 0.4 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 0.6 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.3 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.1 | Slop | IaC & Container Security: High IaC: REDACTED |
| backend/app/controllers/api/Workspaces.scala | 3.7 | Slop | Change Coupling: Boundary-crossing change coupling: Workspaces.scala ↔ Neo4jRemoteIngestStore.scala |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| backend/app/services/users/Neo4jUserManagement.scala | 5.9 | Mixed | Code Duplication: Edited copy of a member (31 corresponding lines) |
| frontend/src/js/components/VideoVerifier.tsx | 6.0 | Mixed | Explicit Debt: TodoComment |
| frontend/src/js/components/workspace/Workspaces.tsx | 6.0 | Mixed | Explicit Debt: TodoComment |
| frontend/src/js/components/Uploads/UploadFiles.tsx | 6.0 | Mixed | Explicit Debt: TodoComment |
| frontend/src/js/components/PageViewer/VirtualScroll.tsx | 6.0 | Mixed | Explicit Debt: TodoComment |
| backend/app/extraction/ExternalTranscriptionWorker.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| backend/app/services/annotations/Neo4jAnnotations.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| backend/app/services/ingestion/RemoteIngestWorker.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| backend/app/services/ingestion/IngestionServices.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 78 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 — 78 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, 670 of 730 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 .mts, .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 100.0% — 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 266 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 56 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.
- 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.
- 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: 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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) — elasticsearch Pulling garage-ui Pulling cerebro Pulling garage Pulling neo4j Pulling postgres Pulling elasticsearch Error Get "https://docker.elastic.co/v2/": Forbidden postgres Error context canceled cerebro Error context canceled neo4j Error context canceled garage-ui Error context canceled garage Error context canceled Error response from daemon: Get "https://docker.elastic.co/v2/": Forbidden; the earlier `compose pull` step reported: cerebro Pulling garage-ui Pulling neo4j Pulling garage Pulling postgres Pulling elasticsearch Pulling elasticsearch Error Get "https://docker.elastic.co/v2/": Forbidden cerebro Error context canceled postgres Error context canceled garage Error context canceled neo4j Error context canceled garage-ui 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.
- 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. 12 further occurrence(s) are not listed individually; the score already reflects all 52.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X4 Structured logging — 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. 114 further occurrence(s) are not listed individually; the score already reflects all 154.
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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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
23 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was VideoVerifier.VideoVerifier at 50. A further 3 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 FailureToResultMapper.failureToResult at 42 — they are counted neither in the figure above nor in this dimension's score. 2 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: backend/app/utils/controller/FailureToResultMapper.scala (FailureToResultMapper.failureToResult at 42), frontend/src/js/reducers/urlParamsReducer.ts (urlParamsReducer.urlParams at 17). 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 23 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with VideoVerifier.VideoVerifier (cyclomatic 50), PreviewSwitcher.PreviewSwitcher (cyclomatic 46), CaptureFromUrl.CaptureFromUrl (cyclomatic 36). — 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 23 together lifts Cyclomatic Complexity from 6.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
38 method(s) exceeded the cognitive complexity threshold of 15; the worst was RemoteIngestWorker.processFinishedJobs at 104.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with RemoteIngestWorker.processFinishedJobs (cognitive 104). — Refactoring it lifts Cognitive Complexity from 6.0 to about 6.5/10.
D3 · God Classes
26 god class(es) detected.
What to do
- Resolve the 14 FunctionTooLong finding(s) in God Classes — start with CaptureFromUrl.tsx, WorkspaceSummary.tsx, UploadFiles.tsx. — One of this dimension's main actionable groups (14 warning-level).
- Resolve the 4 FileTooLong finding(s) in God Classes — start with Neo4jManifest.scala, Workspaces.tsx, ElasticsearchResources.scala. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 MethodTooLong finding(s) in God Classes — start with Workspaces.tsx (3), Timeline.jsx. — One of this dimension's main actionable groups (4 warning-level).
D4 · Code Duplication
7 duplicated block group(s) detected. 1.9 % of the production lines (971 of 50,413) are in a reported copy. A further 26 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: .tsx, .ts (50% 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 (13 corresponding lines) finding(s) in Code Duplication — start with Blobs.scala, IngestStorage.scala, Neo4jAnnotations.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Workspaces.scala, Neo4jAnnotations.scala, Collection.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with Neo4jRemoteIngestStore.scala, AwsS3Clients.scala. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
7 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; 1 module(s) off the main sequence, with abstractness counted on 6 of the 7 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
9 of 58 classes have LCOM4 above 3.
What to do
- Resolve the 9 Low cohesion finding(s) in Cohesion (LCOM4) — start with Neo4jManifest.scala, Neo4jAnnotations.scala, ElasticsearchResources.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 266 tests. Measured on the JavaScript/TypeScript suite only — at least 56 test source file(s) (.scala) went unread, so its test quality is unmeasured and is not in these counts.
D11 · Test Reliability
0 flaky across 2 measured tier(s). JavaScript/TypeScript (vitest via `npm ci --ignore-scripts` in frontend/ (0 tests); jest via `npm ci --ignore-scripts` in infra/cdk/ (2 tests)): measured (0 flaky); Scala (repository root, 44 test files): measured (0 flaky).
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
3 secret(s) detected.
What to do
- Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
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 3 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. ★ 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: frontend/src/js/components/viewer/PreviewSwitcher.tsx (4×46=184); backend/app/extraction/ExternalTranscriptionWorker.scala (3×24=72); frontend/src/js/components/Uploads/CaptureFromUrl.tsx (2×36=72)
What to do
- Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with PreviewSwitcher.tsx, ExternalTranscriptionWorker.scala, CaptureFromUrl.tsx. — One of this dimension's main actionable groups (4 warning-level).
D16 · Bus Factor
47 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is frontend/src/js/components/VideoVerifier.tsx. Counted over 190 of the 503 production source files in this repository: 304 are under the ~2,400-byte size floor this dimension measures over, and the remaining 9 have no attributable history left to measure.
What to do
- Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 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
116 deducted task-comment markers across 43684 LoC (0.3/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 114 TodoComment finding(s) in Explicit Debt — start with WorkspaceSharingITest.scala (13), Neo4jManifest.scala (8), PagePreview.tsx (6). — One of this dimension's main actionable groups (114 warning-level).
- Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with VideoVerifier.scala, GetPages.scala. — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 11 document(s) read across 9 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
2 naming inconsistencies among 99 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `workspaceID` spells `ID` where 85 names in the project spell it `Id` finding(s) in Naming Consistency — start with reprocessBlob.ts. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `maybeCapturedFromURL` spells `URL` where 12 names in the project spell… finding(s) in Naming Consistency — start with Workspaces.ts. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
3 of 377 judged comments only repeat the code they sit on (0.8 %). 8 comment(s) in another language or script were not judged.
D26 · Project Cohesion
2 of 4 build units (npm, sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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)
30 finding(s): 0 critical, 30 high, 0 medium, 0 low. 22 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `scripts/move-ingestions-to-collection.sh` (line 25, line 27, line 28, …) — 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 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (8 issue-level).
- No action in Static Analysis (SAST) — all 22 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 (22 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
28 finding(s): 0 critical, 14 high, 13 medium, 1 low.
What to do
- Resolve the 14 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10), REDACTED (4). — One of this dimension's main actionable groups (14 issue-level).
- Resolve the 12 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10), REDACTED (2). — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
7 finding(s): 0 critical, 1 high, 6 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
D34 · Knowledge Freshness
50 of 199 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is backend/app/utils/Neo4jHelper.scala. Counted over 199 of the 503 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 50 Orphaned file finding(s) in Knowledge Freshness — start with Resource.scala (2), Neo4jHelper.scala, ElasticsearchPages.scala. — One of this dimension's main actionable groups (50 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: AllIngestionEvents.tsx↔MyUploads.tsx 92%; Workspaces.scala↔Neo4jRemoteIngestStore.scala 68%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with Workspaces.scala. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with AllIngestionEvents.tsx. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 5 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. — frontend/src/js/components/viewer/PageViewer/PagePreview.tsx:184
- Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation). (×2) — frontend/src/js/components/viewer/Preview.tsx:123, frontend/src/js/components/viewer/TranscriptViewer/TranscriptViewer.tsx:139
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×11) — frontend/src/js/components/IngestionEvents/AllIngestionEvents.tsx:111, frontend/src/js/components/IngestionEvents/AllIngestionEvents.tsx:131, frontend/src/js/components/Search/Search.tsx:237, …
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×11) — frontend/src/js/components/Login/Login.jsx:137, frontend/src/js/components/Login/Login.jsx:154, frontend/src/js/components/Login/Login.jsx:181, …
- This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×7) — frontend/src/js/components/Settings/FeatureSwitches.tsx:48, frontend/src/js/components/Uploads/CaptureFromUrl.tsx:229, frontend/src/js/components/Uploads/CaptureFromUrl.tsx:356, …
- This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — frontend/src/js/components/UtilComponents/TreeBrowser/index.tsx:376
- This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — frontend/src/js/components/viewer/DownloadModal.jsx:262
- This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. — frontend/src/js/components/viewer/TranscriptViewer/TranscriptViewer.tsx:163
- 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). — frontend/src/js/components/viewer/ViewerSidebar.jsx:81
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
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — frontend/index.html:2
- 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) — frontend/src/js/components/Settings/About.tsx:16, frontend/src/js/components/Uploads/FileList.tsx:129, frontend/src/js/components/viewer/PagedBrowser.tsx:56
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
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×12) — frontend/src/js/components/SearchSidebar/SearchFilter.jsx:59, frontend/src/js/components/SearchSidebar/SearchFilterOption.jsx:151, frontend/src/js/components/SearchSidebar/SearchFilterValue.jsx:83, …
- 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}. (×3) — frontend/src/js/components/UtilComponents/InputSupper/InlineInput.jsx:138, frontend/src/js/components/viewer/SidebarComments.tsx:87, frontend/src/js/components/viewer/SidebarComments.tsx:183
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
- `.search-navigation__button: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. — frontend/src/stylesheets/components/_document.scss:279
- `.file-browser__entry: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. — frontend/src/stylesheets/components/_file-browser.scss:61
- `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. — backend/public/third-party/pdfjs-2.4.456-dist/web/viewer.css:439
- `#viewerContainer` 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. — backend/public/third-party/pdfjs-2.4.456-dist/web/viewer.css:643
- `.toolbarButton.bookmark` 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. — backend/public/third-party/pdfjs-2.4.456-dist/web/viewer.css:1361
- `#thumbnailView > a: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. — backend/public/third-party/pdfjs-2.4.456-dist/web/viewer.css:1606
- `.comment--animatable` moves (`transition: top 0.4s ease 0s, left 0.4s ease 0s`) 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. — frontend/src/stylesheets/components/_comments.scss:18
- `%progress-bar__bar` moves (`transition: width 0.5s`) 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. — frontend/src/stylesheets/components/_progress-bar.scss:11
- `#loadingBar .progress` moves (`transition: width 200ms`) 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. — backend/public/third-party/pdfjs-2.4.456-dist/web/viewer.css:773
- `#loadingBar .progress.indeterminate .glimmer` moves (`animation: progressIndeterminate 950ms linear infinite`) 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. — backend/public/third-party/pdfjs-2.4.456-dist/web/viewer.css:803
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
- `Annotations` declares 22 abstract members: `setup`, `getAllWorkspacesMetadata`, `getWorkspaceMetadata`, `getWorkspaceContents`, `getBlobUrisInWorkspaceFolder`, `insertWorkspace`, `updateWorkspaceName`, `updateWorkspaceOwner`, `updateWorkspaceIsPublic`, `updateWorkspaceFollowers`, `deleteWorkspace`, `addFolder`, `addOrGetFolder`, `addResourceToWorkspaceFolder`, `renameWorkspaceItem`, `moveWorkspaceItem`, `deleteWorkspaceItem`, `getCopyDestination`, `postComment`, `getComments`, `deleteComment`, `getBlobOwners`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — backend/app/services/annotations/Annotations.scala:12
- `Index` declares 25 abstract members: `setup`, `ingestDocument`, `addDocumentDetails`, `addDocumentOcr`, `addDocumentTranscription`, `addDocumentOcrTranslationData`, `getTextDetectedLanguage`, `ingestEmail`, `query`, `getResource`, `getPageCount`, `getEmailMetadata`, `flag`, `getBlobs`, `countBlobs`, `delete`, `anyWorkspaceOrCollectionContainsAnyResource`, `addResourceToWorkspace`, `removeResourceFromWorkspace`, `deleteWorkspace`, `updateIngestionPath`, `getTotalWordCountForWorkspace`, `getWordCountForBlobs`, `getTextForBlobs`, `addTranslationToLanguageData`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — backend/app/services/index/Index.scala:11
- `Manifest` declares 30 abstract members: `setup`, `insert`, `insertCollection`, `getCollections`, `getCollectionsForBlob`, `getWorkspacesForBlob`, `getResource`, `getIngestions`, `getCollection`, `getIngestionCount`, `getIngestion`, `insertIngestion`, `addTranslationTodoToBlob`, `getFailedExtractions`, `getResourcesForExtractionFailure`, `getMimeTypesCoverage`, `getFilterableMimeTypes`, `getAllMimeTypes`, `rerunSuccessfulExtractorsForBlob`, `rerunFailedExtractorsForBlob`, `rerunFailedExternalExtractorsForBlob`, `getActiveExternalWorkForBlob`, `getBlob`, `getBlobsForFiles`, `getEmailThread`, `getLanguagesProcessedByOcrMyPdf`, `deleteBlob`, `deleteResourceAndDescendants`, `getWorkspaceChildrenWithUri`, `moveIngestionToCollection`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — backend/app/services/manifest/Manifest.scala:56
- `UserManagement` declares 19 abstract members: `listUsers`, `listUsersWithPermission`, `getPermissions`, `createUser`, `importUser`, `registerUser`, `updateUserDisplayName`, `updateUserPassword`, `updateTotpSecret`, `getUser`, `removeUser`, `updateInvalidatedTime`, `getDefaultCollectionUriForUser`, `getAllCollectionUrisAndUsernames`, `getUsersForCollection`, `getVisibleCollectionUrisForUser`, `addUserCollection`, `removeUserCollection`, `setPermissions`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — backend/app/services/users/UserManagement.scala:11
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — frontend/src/js/components/PageViewer/FindInput.tsx:114
- `onMoveItems` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×3) — frontend/src/js/components/Uploads/CaptureFromUrl.tsx:306, frontend/src/js/components/viewer/AddToWorkspaceModal.tsx:168, frontend/src/js/components/viewer/LazyTreeBrowser.tsx:207
- `onContextMenu` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×2) — frontend/src/js/components/Uploads/CaptureFromUrl.tsx:307, frontend/src/js/components/viewer/AddToWorkspaceModal.tsx:170
- `onSelectLeaf` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×2) — frontend/src/js/components/Uploads/CaptureFromUrl.tsx:308, frontend/src/js/components/viewer/AddToWorkspaceModal.tsx:172
- `onExpandLeaf` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×3) — frontend/src/js/components/Uploads/CaptureFromUrl.tsx:309, frontend/src/js/components/viewer/AddToWorkspaceModal.tsx:174, frontend/src/js/components/workspace/Workspaces.tsx:1281
- `onClickColumn` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×3) — frontend/src/js/components/Uploads/CaptureFromUrl.tsx:310, frontend/src/js/components/viewer/AddToWorkspaceModal.tsx:176, frontend/src/js/components/viewer/LazyTreeBrowser.tsx:216
- `mapDispatchToProps` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — frontend/src/js/eui-components/GiantEuiWorkspace.tsx:36
- Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — infra/cdk/lib/postgres.ts:54
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)
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
- `npm run prettier:check` invokes prettier in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--check` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted. — REDACTED:27
What to do
- Add `--check` to the prettier step in `REDACTED` so a change that is not formatted fails CI, instead of being silently reformatted into a checkout that is thrown away — or, if reformatting the branch is the intent, commit the result back so the fix reaches the repository.
P11 · BDD / executable specs
P2 · Observability
- Only 1/2 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 7 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
- `e2e-tests/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — e2e-tests/package.json:14
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.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
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
- `ingest` 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. — cli/src/main/scala/com/gu/pfi/cli/ingestion/CliIngestionPipeline.scala:30
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
R10 · Code Duplication
- 13 duplicated blocks under frontend/src/js/components/ have copies in at least two of the sibling directories Collections, Directory, IngestionEvents, PageViewer, ResourceHandler, Settings (+4 more sibling(s) not listed) — 7 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 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 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 13 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. — frontend/src/js/components/Uploads/FilePicker.tsx:88
- frontend/src/js/components/users/CreateGenesisUser.jsx:41 · frontend/src/js/components/users/RegisterUser.jsx:34 — the two spans are one implementation copied and then locally edited — 823 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. — frontend/src/js/components/users/CreateGenesisUser.jsx:41
- frontend/src/js/components/UtilComponents/TreeBrowser/Leaf.tsx:6 · frontend/src/js/components/UtilComponents/TreeBrowser/Node.tsx:18 — the two spans are one implementation copied and then locally edited — 311 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. — frontend/src/js/components/UtilComponents/TreeBrowser/Leaf.tsx:6
- frontend/src/js/components/Settings/ExtractionFailuresComponent.tsx:89 · frontend/src/js/components/Settings/FeatureSwitches.tsx:53 — the two spans are one implementation copied and then locally edited — 145 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. — frontend/src/js/components/Settings/ExtractionFailuresComponent.tsx:89
- frontend/src/js/components/UtilComponents/InputSupper/Chip.jsx:232 · frontend/src/js/components/UtilComponents/InputSupper/Chip.jsx:281 — 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. — frontend/src/js/components/UtilComponents/InputSupper/Chip.jsx:232
- frontend/src/js/actions/auth/invalidateAuthToken.js:3 · frontend/src/js/actions/auth/sessionKeepalive.js:3 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — frontend/src/js/actions/auth/invalidateAuthToken.js:3
- frontend/src/js/actions/workspaces/addFolderToWorkspace.ts:11 · frontend/src/js/actions/workspaces/renameItem.ts:11 — 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. — frontend/src/js/actions/workspaces/addFolderToWorkspace.ts:11
- frontend/src/js/components/Uploads/FilePicker.tsx:88 · frontend/src/js/components/UtilComponents/TreeBrowser/index.tsx:168 — the two spans are one implementation copied and then locally edited — 108 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. — frontend/src/js/components/Uploads/FilePicker.tsx:88
- frontend/src/js/components/viewer/Viewer.tsx:175 · frontend/src/js/eui-components/GiantEuiSearchResultNav.tsx:17 — the two spans are one implementation copied and then locally edited — 76 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. — frontend/src/js/components/viewer/Viewer.tsx:175
- frontend/src/js/actions/workspaces/renameWorkspace.ts:12 · frontend/src/js/actions/workspaces/setWorkspaceIsPublic.ts:12 · frontend/src/js/actions/workspaces/takeOwnershipOfWorkspace.ts:12 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. 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. — frontend/src/js/actions/workspaces/renameWorkspace.ts:12
- frontend/src/js/actions/workspaces/renameWorkspace.ts:14 · frontend/src/js/actions/workspaces/setWorkspaceFollowers.ts:14 · frontend/src/js/actions/workspaces/setWorkspaceIsPublic.ts:14 · frontend/src/js/actions/workspaces/takeOwnershipOfWorkspace.ts:14 — the 4 copies are spread across 4 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. — frontend/src/js/actions/workspaces/renameWorkspace.ts:14
- frontend/src/js/components/viewer/DeleteButtonModal.tsx:69 · frontend/src/js/components/workspace/ConfirmModal.tsx:138 — 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. — frontend/src/js/components/viewer/DeleteButtonModal.tsx:69
- frontend/src/js/actions/workspaces/deleteItem.ts:11 · frontend/src/js/actions/workspaces/deleteResourceFromWorkspace.ts:11 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — frontend/src/js/actions/workspaces/deleteItem.ts:11
- frontend/src/js/components/viewer/Preview.tsx:114 · frontend/src/js/components/viewer/Preview.tsx:135 — 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. — frontend/src/js/components/viewer/Preview.tsx:114
- frontend/src/js/components/UtilComponents/TreeBrowser/Node.tsx:273 · frontend/src/js/components/UtilComponents/TreeBrowser/Node.tsx:299 — 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. — frontend/src/js/components/UtilComponents/TreeBrowser/Node.tsx:273
- frontend/src/js/actions/workspaces/addFolderToWorkspace.ts:3 · frontend/src/js/actions/workspaces/createWorkspace.ts:4 — 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. — frontend/src/js/actions/workspaces/addFolderToWorkspace.ts:3
- frontend/src/js/components/IngestionEvents/MyUploads.tsx:125 · frontend/src/js/components/workspace/WorkspacesSidebar.tsx:154 — the two spans are one implementation copied and then locally edited — 61 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. — frontend/src/js/components/IngestionEvents/MyUploads.tsx:125
- frontend/src/js/components/users/CreateGenesisUser.jsx:140 · frontend/src/js/components/users/CreateNewUser.jsx:136 · frontend/src/js/components/users/RegisterUser.jsx:207 — 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. — frontend/src/js/components/users/CreateGenesisUser.jsx:140
- frontend/src/js/services/WorkspaceApi.ts:94 · frontend/src/js/services/WorkspaceApi.ts:110 — 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. — frontend/src/js/services/WorkspaceApi.ts:94
- frontend/src/js/actions/workspaces/addFolderToWorkspace.ts:17 · frontend/src/js/actions/workspaces/addResourceToWorkspace.ts:28 · frontend/src/js/actions/workspaces/renameItem.ts:17 — 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. — frontend/src/js/actions/workspaces/addFolderToWorkspace.ts:17
- frontend/src/js/components/SearchResults/SearchResult.jsx:87 · frontend/src/js/components/SearchResults/SearchResult.jsx:108 — 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. — frontend/src/js/components/SearchResults/SearchResult.jsx:87
- frontend/src/js/components/Search/Search.tsx:236 · frontend/src/js/components/Search/Search.tsx:249 — 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. — frontend/src/js/components/Search/Search.tsx:236
- frontend/src/js/components/Settings/DatasetPermissions.jsx:26 · frontend/src/js/components/Settings/FeatureSwitches.tsx:59 — the two spans are one implementation copied and then locally edited — 65 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. — frontend/src/js/components/Settings/DatasetPermissions.jsx:26
- frontend/src/js/components/viewer/DocumentMetadata.jsx:140 · frontend/src/js/components/viewer/EmailMetadata.jsx:24 — 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. — frontend/src/js/components/viewer/DocumentMetadata.jsx:140
- frontend/src/js/components/workspace/Workspaces.tsx:651 · frontend/src/js/components/workspace/Workspaces.tsx:666 — 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. — frontend/src/js/components/workspace/Workspaces.tsx:651
- frontend/src/js/actions/workspaces/addFolderToWorkspace.ts:19 · frontend/src/js/actions/workspaces/addResourceToWorkspace.ts:30 · frontend/src/js/actions/workspaces/createWorkspace.ts:21 · frontend/src/js/actions/workspaces/deleteWorkspace.ts:24 · +5 more site(s) not listed — the 9 copies are spread across 9 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. — frontend/src/js/actions/workspaces/addFolderToWorkspace.ts:19
- frontend/src/js/components/Collections/CurrentCollection/CurrentCollection.tsx:93 · frontend/src/js/components/Directory/Directory.tsx:63 — 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. — frontend/src/js/components/Collections/CurrentCollection/CurrentCollection.tsx:93
- frontend/src/js/components/Settings/FeatureSwitches.tsx:81 · frontend/src/js/eui-components/GiantEuiSettings.tsx:45 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — frontend/src/js/components/Settings/FeatureSwitches.tsx:81
- frontend/src/js/components/Settings/SettingsSidebar.jsx:23 · frontend/src/js/components/Settings/SettingsSidebar.jsx:36 — 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. — frontend/src/js/components/Settings/SettingsSidebar.jsx:23
- frontend/src/js/components/UtilComponents/TreeBrowser/index.tsx:235 · frontend/src/js/components/UtilComponents/TreeBrowser/index.tsx:262 — 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. — frontend/src/js/components/UtilComponents/TreeBrowser/index.tsx:235
- frontend/src/js/components/users/CreateGenesisUser.jsx:246 · frontend/src/js/components/users/CreateNewUser.jsx:209 — 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. — frontend/src/js/components/users/CreateGenesisUser.jsx:246
- frontend/src/js/components/viewer/StatusBar.jsx:75 · frontend/src/js/components/viewer/StatusBar.jsx:98 — 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. — frontend/src/js/components/viewer/StatusBar.jsx:75
- frontend/src/js/services/WorkspaceApi.ts:16 · frontend/src/js/services/WorkspaceApi.ts:32 — 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. — frontend/src/js/services/WorkspaceApi.ts:16
- frontend/src/js/components/SearchSidebar/SearchFilterOption.jsx:38 · frontend/src/js/components/SearchSidebar/SearchFilterOption.jsx:94 — the two spans are one implementation copied and then locally edited — 72 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. — frontend/src/js/components/SearchSidebar/SearchFilterOption.jsx:38
- frontend/src/js/components/UtilComponents/InputSupper/Chip.jsx:57 · frontend/src/js/components/UtilComponents/InputSupper/InlineInput.jsx:58 — 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. — frontend/src/js/components/UtilComponents/InputSupper/Chip.jsx:57
- frontend/src/js/components/viewer/LazyTreeBrowser.tsx:143 · frontend/src/js/components/workspace/Workspaces.tsx:820 — 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. — frontend/src/js/components/viewer/LazyTreeBrowser.tsx:143
- frontend/src/js/components/viewer/Viewer.tsx:255 · frontend/src/js/components/viewer/Viewer.tsx:267 — 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. — frontend/src/js/components/viewer/Viewer.tsx:255
- frontend/src/js/components/workspace/ShareWorkspaceModal.tsx:71 · frontend/src/js/components/workspace/TakeOwnershipOfWorkspaceModal.tsx:36 — 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. — frontend/src/js/components/workspace/ShareWorkspaceModal.tsx:71
- frontend/src/js/components/workspace/Workspaces.tsx:1399 · frontend/src/js/components/workspace/Workspaces.tsx:1410 — 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. — frontend/src/js/components/workspace/Workspaces.tsx:1399
- frontend/src/js/components/PageViewer/PdfHelpers.ts:46 · frontend/src/js/components/viewer/PageViewer/pageViewerPdf.ts:68 — the two spans are one implementation copied and then locally edited — 51 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. — frontend/src/js/components/PageViewer/PdfHelpers.ts:46
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
- infra/cdk/lib/constructs/GuStackWithGiantVPC.ts:1 imports @guardian/cdk/lib/constants/ssm-parameter-paths, 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. — infra/cdk/lib/constructs/GuStackWithGiantVPC.ts:1
- infra/cdk/lib/constructs/GuStackWithGiantVPC.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. — infra/cdk/lib/constructs/GuStackWithGiantVPC.ts:2
- infra/cdk/lib/constructs/GuStackWithGiantVPC.ts:7 imports @guardian/cdk/lib/constructs/ec2/vpc, 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. — infra/cdk/lib/constructs/GuStackWithGiantVPC.ts:7
- infra/cdk/lib/postgres.ts:2 imports @guardian/cdk/lib/constructs/ec2/vpc, 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. — infra/cdk/lib/postgres.ts:2
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
- DocumentFooter has cyclomatic complexity 25 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — frontend/src/js/components/viewer/DocumentFooter.tsx:45
- (anonymous) has cyclomatic complexity 22 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — frontend/src/js/components/Uploads/CaptureFromUrl.tsx:75
- onKeyPress has cyclomatic complexity 19 and cognitive complexity 21; 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. — frontend/src/js/components/UtilComponents/InputSupper/InlineInput.jsx:39
- (anonymous) has cyclomatic complexity 18 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — frontend/src/js/components/workspace/Workspaces.tsx:993
- PageViewerOrFallback has cyclomatic complexity 17 and cognitive complexity 21; 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. — frontend/src/js/components/PageViewerOrFallback.tsx:175
- parseDateNoFallback has cyclomatic complexity 16 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 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. — frontend/src/js/util/parseDate.ts:63
- PreviewSwitcher has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — frontend/src/js/components/viewer/PreviewSwitcher.tsx:45
- UploadFiles has cyclomatic complexity 16 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. — frontend/src/js/components/Uploads/UploadFiles.tsx:314
- Preview has cyclomatic complexity 15 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/src/js/components/viewer/Preview.tsx:47
- (anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — frontend/src/js/components/viewer/PreviewSwitcher.tsx:51
- VideoVerifier has cyclomatic complexity 14 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. — frontend/src/js/components/VideoVerifier.tsx:41
- readFilesFromDragEvent has cyclomatic complexity 13 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/src/js/components/Uploads/dropZoneUtils.ts:34
- buildLink has cyclomatic complexity 12 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. — frontend/src/js/util/buildLink.ts:5
- WorkspaceSummary has cyclomatic complexity 12 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. — frontend/src/js/components/workspace/WorkspaceSummary.tsx:55
- PageViewerContent 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. — frontend/src/js/components/PageViewerOrFallback.tsx:68
- onKeyDownText 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. — frontend/src/js/components/UtilComponents/InputSupper/Chip.jsx:46
R3 · Large Files
- frontend/src/js/components/workspace/Workspaces.tsx has 1401 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/js/components/workspace/Workspaces.tsx:1
- frontend/src/js/components/VideoVerifier.tsx has 567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/js/components/VideoVerifier.tsx:1
- frontend/src/js/components/IngestionEvents/IngestionEvents.tsx has 537 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/js/components/IngestionEvents/IngestionEvents.tsx:1
- frontend/src/js/components/Uploads/UploadFiles.tsx has 476 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/js/components/Uploads/UploadFiles.tsx:1
- frontend/src/js/components/viewer/Viewer.tsx has 416 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/js/components/viewer/Viewer.tsx:1
- frontend/src/js/components/UtilComponents/InputSupper/index.jsx has 412 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/js/components/UtilComponents/InputSupper/index.jsx: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. (×26) — frontend/src/js/components/viewer/StatusBar.jsx:1, frontend/src/js/components/viewer/PageViewer/PagePreview.tsx:1, frontend/src/js/components/UtilComponents/Wizard.jsx:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
- The package in `e2e-tests` declares the lint script `format:check` (`prettier --check .`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run format:check` in `e2e-tests` (or the workspace's task runner). — e2e-tests/package.json:12
R7 · Dead Code
- 4 file(s) (~142 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. — infra/cdk
- Unreachable from the 5 application, 11 tooling and 40 test entry point(s) detected in this repo. Gate removals on `npm run typecheck` — an undetected custom entry would make these reachable.
- no import path from any entry point (5 application, 11 tooling, 40 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×14) — frontend/src/js/components/viewer/StatusBar.jsx, frontend/src/js/components/UtilComponents/Wizard.jsx, frontend/src/js/components/viewer/PageViewer/PageViewer.tsx, …
- no import path from any entry point (5 application, 11 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/src/js/components/viewer/PageViewer/PageViewer.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — frontend/src/js/components/viewer/PageViewer/PagePreview.tsx, frontend/src/js/actions/pages/loadPages.ts
- no import path from any entry point (5 application, 11 tooling, 40 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (frontend/src/js/actions/pages/loadPages.ts, frontend/src/js/components/viewer/PageViewer/PagePreview.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontend/src/js/components/viewer/PageViewer/pageViewerApi.ts
- no import path from any entry point (5 application, 11 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/src/js/components/viewer/PageViewer/PagePreview.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontend/src/js/components/viewer/PageViewer/pageViewerPdf.ts
- no import path from any entry point (5 application, 11 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/src/js/components/viewer/StatusBar.jsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontend/src/js/components/viewer/HighlightToggle.jsx
- no import path from any entry point (5 application, 11 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/src/js/components/viewer/PageViewer/PageViewerStatusBar.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontend/src/js/actions/pages/navigateToHighlight.ts
- no import path from any entry point (5 application, 11 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/src/js/components/DownloadLink/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontend/src/js/components/DownloadLink/DownloadLink.jsx
- no import path from any entry point (5 application, 11 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/src/js/actions/getNodes.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontend/src/js/services/ClusterApi.js
- no import path from any entry point (5 application, 11 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/src/js/components/UtilComponents/Wizard.jsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontend/src/js/types/WizardSlide.js
- Nothing imports this binding — it is safe to review for removal. (×14) — frontend/src/js/components/workspace/ConfirmModal.tsx:183, frontend/src/js/services/UserApi.js:27, frontend/src/js/services/UserApi.js:35, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×2) — frontend/src/js/actions/workspaces/moveItem.ts:10, frontend/src/js/components/Collections/Collections.jsx:4
- Declared in infra/cdk/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2) — infra/cdk/package.json:17, infra/cdk/package.json:28
- 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. — REDACTED:16
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- frontend/src/js/actions/auth/getAuthToken.js → frontend/src/js/services/AuthApi.js → frontend/src/js/util/auth/authFetch.ts → frontend/src/js/util/auth/handleResponseFromAuthRequest.ts → frontend/src/js/actions/auth/getAuthToken.js — frontend/src/js/actions/auth/getAuthToken.js:2
- frontend/src/js/components/Uploads/FileList.tsx → frontend/src/js/components/Uploads/UploadFiles.tsx → frontend/src/js/components/Uploads/FileList.tsx — frontend/src/js/components/Uploads/FileList.tsx:4
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
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. — backend/app/services/observability/Models.scala:223
- This repository runs an HTTP server and nothing in its Scala source or committed configuration secures the transport: no HTTPS served (akka/pekko-http `ConnectionContext.httpsServer`/`enableHttps`, an http4s builder's `withTLS`, Jetty's `SslContextFactory`, zio-http's `SSLConfig`, Play's `https.port`), no `Strict-Transport-Security` header, HSTS middleware or Play `RedirectHttpsFilter`, no `X-Forwarded-Proto` read or Play `play.http.forwarded.trustedProxies` for a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: backend/app/AppComponents.scala:64 — `BuiltInComponentsFromContext`.
- Set: Referrer-Policy, X-Content-Type-Options, X-Frame-Options, X-Permitted-Cross-Domain-Policies. Missing: Content-Security-Policy, Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−1.0 on this card.) The server: backend/app/AppComponents.scala:64 — `BuiltInComponentsFromContext`.
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.
- Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`).
- Add Content-Security-Policy, Strict-Transport-Security beside the headers the Scala server already sets.
X1 · Async correctness
- The `Future` this starts is not kept anywhere, and `scala.concurrent.Future` never reports a failure on its own: `Future { … }` catches any non-fatal exception its body throws and stores it as the future's `Failure` — not rethrown, not printed, not passed to the `ExecutionContext`'s `reportFailure` — so once nobody holds the future the error is gone, and nothing can wait for the work to finish either. Keep the future and compose it into what the caller returns (`for`/`flatMap`, `Future.sequence`), or, for genuine fire-and-forget, attach a handler that reports the failure — `Future { … }.failed.foreach(error => log.error("…", error))` or `.onComplete { case Failure(e) => report(e); case _ => }` — or catch and report inside the body itself. — backend/app/services/previewing/PreviewService.scala:120
What to do
- Future started here is not kept
X12 · Unreachable branch
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `objectToParamString` is exported and takes `obj: object` from its caller, and it calls itself at line 40 (`objectToParamString`) with a piece of `obj` — and nowhere in `objectToParamString` 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. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `objectToParamString` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — frontend/src/js/util/UrlParameters.ts:40
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
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X24 · Document value interpolated into markup unescaped
- `string` 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. (×2) — frontend/src/js/components/UtilComponents/HighlightedText.tsx:10, frontend/src/js/components/UtilComponents/HighlightedText.tsx:24
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
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- 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. — frontend/src/js/components/UtilComponents/documentTitle.ts:68
- `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. — cli/src/main/scala/com/gu/pfi/cli/service/CliVeracrypt.scala:47
- `case NonFatal(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, 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. — backend/app/utils/HtmlToPlainText.scala:31
What to do
- Swallowed exception (empty catch)
X4 · Structured logging
- `info` at line 12 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/src/main/scala/utils/Timing.scala:12
- `info` at line 77 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. — cli/src/main/scala/com/gu/pfi/cli/DeleteIngestions.scala:77
- `info` at line 13 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. — cli/src/main/scala/com/gu/pfi/cli/HashFiles.scala:13
- `error` at line 15 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.error("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. — cli/src/main/scala/com/gu/pfi/cli/HashFiles.scala:15
- `info` at line 68 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. — cli/src/main/scala/com/gu/pfi/cli/Main.scala:68
- `info` at line 146 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. — cli/src/main/scala/com/gu/pfi/cli/Main.scala:146
- `error` at line 162 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.error("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. — cli/src/main/scala/com/gu/pfi/cli/service/CliHttpClient.scala:162
- `info` at line 46 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. — cli/src/main/scala/com/gu/pfi/cli/service/CliIngestionService.scala:46
- `error` at line 28 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.error("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. — cli/src/main/scala/com/gu/pfi/cli/ingestion/CliFileWalker.scala:28
- `info` at line 151 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. — backend/app/AppComponents.scala:151
- `info` at line 47 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. — backend/app/utils/AwsDiscovery.scala:47
- `info` at line 189 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. — backend/app/utils/AwsDiscovery.scala:189
- `info` at line 198 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. — backend/app/utils/AwsDiscovery.scala:198
- `info` at line 222 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. — backend/app/utils/AwsDiscovery.scala:222
- `error` at line 252 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.error("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. — backend/app/utils/AwsDiscovery.scala:252
- `error` at line 257 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.error("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. — backend/app/utils/AwsDiscovery.scala:257
- `warn` at line 127 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.warn("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. — backend/app/utils/Ocr.scala:127
- `warn` at line 157 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.warn("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. — backend/app/utils/Ocr.scala:157
- `info` at line 201 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. — backend/app/utils/Ocr.scala:201
- `warn` at line 207 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.warn("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. — backend/app/utils/Ocr.scala:207
- `info` at line 255 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. — backend/app/utils/Ocr.scala:255
- `info` at line 277 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. — backend/app/utils/Ocr.scala:277
- `info` at line 299 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. — backend/app/utils/Ocr.scala:299
- `error` at line 82 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.error("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. — backend/app/utils/WorkerControl.scala:82
- `info` at line 121 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. — backend/app/utils/WorkerControl.scala:121
- `warn` at line 150 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.warn("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. — backend/app/utils/WorkerControl.scala:150
- `info` at line 214 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. — backend/app/utils/WorkerControl.scala:214
- `info` at line 230 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. — backend/app/utils/WorkerControl.scala:230
- `info` at line 34 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. — backend/app/utils/controller/DownloadHelper.scala:34
- `warn` at line 38 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.warn("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. — backend/app/utils/controller/DownloadHelper.scala:38
- `info` at line 71 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. — backend/app/utils/controller/DownloadHelper.scala:71
- `error` at line 30 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.error("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. — backend/app/utils/controller/FailureToResultMapper.scala:30
- `info` at line 64 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. — backend/app/utils/auth/AuthActionBuilder.scala:64
- `info` at line 76 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. — backend/app/utils/auth/providers/DatabaseUserProvider.scala:76
- `info` at line 84 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. — backend/app/utils/auth/providers/DatabaseUserProvider.scala:84
- `warn` at line 72 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.warn("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. — backend/app/utils/auth/providers/PanDomainUserProvider.scala:72
- `info` at line 89 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. — backend/app/services/ElasticsearchSyntax.scala:89
- `error` 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.error("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. — backend/app/services/ExternalWorkerScheduler.scala:32
- `info` at line 150 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. — backend/app/services/IngestStorage.scala:150
- `warn` at line 85 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.warn("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. — backend/app/services/MetricsService.scala:85
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- No build over this repository's 250 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 | 50.7 | Adequate — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 79.4 | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 77.6 | Strong | Solid. |
| Readiness | 34.3 | Weak — gated by D13, P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 61.3 | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 38.9 | Weak — gated by AC1, AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85.0 | 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 — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 48 check(s) not relevant to this codebase
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- 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) — elasticsearch Pulling garage-ui Pulling cerebro Pulling garage Pulling neo4j Pulling postgres Pulling elasticsearch Error Get "https://docker.elastic.co/v2/": Forbidden postgres Error context canceled cerebro Error context canceled neo4j Error context canceled garage-ui Error context canceled garage Error context canceled Error response from daemon: Get "https://docker.elastic.co/v2/": Forbidden; the earlier `compose pull` step reported: cerebro Pulling garage-ui Pulling neo4j Pulling garage Pulling postgres Pulling elasticsearch Pulling elasticsearch Error Get "https://docker.elastic.co/v2/": Forbidden cerebro Error context canceled postgres Error context canceled garage Error context canceled neo4j Error context canceled garage-ui 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.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- 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 reads resolved call sites in the languages it reads only — this repository's production source is .java, .mts, .py, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- 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): 371 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 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 3 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 tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, 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
- X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X23 Unguarded diagnostic materialisation — 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
- X27 Collection changed while being enumerated — X27 reached only 42% of this repository's production lines — typescript (22,750 lines), javascript (6,729 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 91 finding(s)
- 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 frontend/src/js/components/Login/Login.jsx:137
- <input> without a programmatic label frontend/src/js/components/Login/Login.jsx:154
- <input> without a programmatic label frontend/src/js/components/Login/Login.jsx:181
- <input> without a programmatic label frontend/src/js/components/PageViewer/FindInput.tsx:88
- <input> without a programmatic label frontend/src/js/components/Settings/FeatureSwitches.tsx:48
- <input> without a programmatic label frontend/src/js/components/Uploads/CaptureFromUrl.tsx:229
- <input> without a programmatic label frontend/src/js/components/Uploads/CaptureFromUrl.tsx:356
- <input> without a programmatic label frontend/src/js/components/UtilComponents/ModalAction.tsx:91
- <input> without a programmatic label frontend/src/js/components/UtilComponents/TreeBrowser/MagicTextInput.tsx:37
- <input> without a programmatic label frontend/src/js/components/users/CreateGenesisUser.jsx:146
- <input> without a programmatic label frontend/src/js/components/users/CreateNewUser.jsx:142
- <input> without a programmatic label frontend/src/js/components/viewer/AddToWorkspaceModal.tsx:259
- <input> without a programmatic label frontend/src/js/components/viewer/DownloadModal.jsx:296
- <input> without a programmatic label frontend/src/js/components/workspace/CreateFolderModal.tsx:75
- <input> without a programmatic label frontend/src/js/components/workspace/CreateWorkspaceModal.tsx:61
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Click handler on a non-interactive <div> frontend/src/js/components/SearchSidebar/SearchFilter.jsx:59
- Click handler on a non-interactive <div> frontend/src/js/components/SearchSidebar/SearchFilterOption.jsx:151
- Click handler on a non-interactive <div> frontend/src/js/components/SearchSidebar/SearchFilterValue.jsx:83
- Click handler on a non-interactive <div> frontend/src/js/components/UtilComponents/Checkbox.tsx:18
- Click handler on a non-interactive <div> frontend/src/js/components/UtilComponents/Modal.tsx:48
- Click handler on a non-interactive <div> frontend/src/js/components/UtilComponents/TreeBrowser/index.tsx:376
- Click handler on a non-interactive <div> frontend/src/js/components/viewer/CommentPanel/CommentPanel.tsx:258
- Click handler on a non-interactive <div> frontend/src/js/components/viewer/TextPreview.tsx:140
- Click handler on a non-interactive <div> frontend/src/js/components/viewer/TranscriptViewer/TranscriptViewer.tsx:187
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <textarea> without a programmatic label frontend/src/js/components/viewer/CommentPanel/AddComment.tsx:61
- <textarea> without a programmatic label frontend/src/js/components/viewer/SidebarComments.tsx:114
- Click handler on a non-interactive <span> frontend/src/js/components/UtilComponents/InputSupper/InlineInput.jsx:138
- Click handler on a non-interactive <span> frontend/src/js/components/viewer/SidebarComments.tsx:87
- Click handler on a non-interactive <li> frontend/src/js/components/UtilComponents/InputSupper/SuggestionsPanel.jsx:35
- Click handler on a non-interactive <li> frontend/src/js/components/viewer/SidebarComments.tsx:183
- <select> without a programmatic label frontend/src/js/components/UtilComponents/InputSupper/Chip.jsx:431
- Custom control with no accessible name on <div> frontend/src/js/components/UtilComponents/TreeBrowser/index.tsx:376
- <label> that labels no control frontend/src/js/components/viewer/TranscriptViewer/TranscriptViewer.tsx:163
- <button> with no accessible text frontend/src/js/components/viewer/ViewerSidebar.jsx:81
- Click handler on a non-interactive <th> frontend/src/js/components/UtilComponents/TreeBrowser/index.tsx:331
- Click handler on a non-interactive <h1> frontend/src/js/components/workspace/WorkspaceSummary.tsx:100
- REDACTED
- REDACTED
- Boundary-crossing change coupling: Workspaces.scala ↔ Neo4jRemoteIngestStore.scala backend/app/controllers/api/Workspaces.scala:1
- Unlisted import 'lodash' frontend/src/js/actions/workspaces/moveItem.ts:10
- Unlisted import 'react-router' frontend/src/js/components/Collections/Collections.jsx:4
- Import cycle (4 files) frontend/src/js/actions/auth/getAuthToken.js:2
- Import cycle (2 files) frontend/src/js/components/Uploads/FileList.tsx:4
Serious — 447 finding(s)
- TodoComment frontend/src/js/util/auth/authFetch.ts:32
- TodoComment frontend/src/js/util/auth/authUploadWithProgress.ts:163
- TodoComment frontend/src/js/types/redux/GiantState.ts:76
- TodoComment frontend/src/js/services/SearchApi.ts:59
- TodoComment frontend/src/js/components/Search/Search.tsx:194
- TodoComment frontend/src/js/services/SearchApi.ts:61
- TodoComment frontend/src/js/reducers/pagesReducer.ts:25
- TodoComment frontend/src/js/components/PageViewer/model.ts:32
- TodoComment frontend/src/js/reducers/pagesReducer.ts:28
- TodoComment frontend/src/js/components/PageViewer/model.ts:45
- TodoComment frontend/src/js/eui-components/GiantEuiSearchResultNav.tsx:64
- TodoComment frontend/src/js/components/VideoVerifier.tsx:383
- TodoComment frontend/src/js/components/workspace/CreateFolderModal.tsx:18
- TodoComment frontend/src/js/components/workspace/CreateFolderModal.tsx:51
- TodoComment frontend/src/js/components/workspace/Workspaces.tsx:168
- TodoComment frontend/src/js/components/workspace/Workspaces.tsx:183
- TodoComment frontend/src/js/components/workspace/Workspaces.tsx:979
- TodoComment frontend/src/js/components/workspace/Workspaces.tsx:1121
- TodoComment frontend/src/js/components/workspace/Workspaces.tsx:1137
- TodoComment frontend/src/js/components/viewer/TranscriptViewer/srt.ts:49
- TodoComment frontend/src/js/components/viewer/PageViewer/PagePreview.tsx:15
- TodoComment frontend/src/js/components/viewer/PageViewer/PagePreview.tsx:26
- TodoComment frontend/src/js/components/viewer/PageViewer/PagePreview.tsx:21
- TodoComment frontend/src/js/components/viewer/PageViewer/PagePreview.tsx:42
- TodoComment frontend/src/js/components/viewer/PageViewer/PagePreview.tsx:115
- No test reaches this file frontend/src/js/components/viewer/StatusBar.jsx:1
- No test reaches this file frontend/src/js/components/viewer/PageViewer/PagePreview.tsx:1
- No test reaches this file frontend/src/js/components/UtilComponents/Wizard.jsx:1
- No test reaches this file frontend/src/js/components/viewer/PageViewer/PageViewer.tsx:1
- No test reaches this file frontend/src/js/components/viewer/PageViewer/pageViewerApi.ts:1
- No test reaches this file infra/migrate-db/src/index.ts:1
- No test reaches this file frontend/src/js/components/viewer/PageViewer/pageViewerPdf.ts:1
- No test reaches this file infra/cdk/lib/postgres.ts:1
- No test reaches this file frontend/src/js/components/viewer/PageViewer/PageViewerStatusBar.tsx:1
- No test reaches this file frontend/src/js/components/viewer/HighlightToggle.jsx:1
- No test reaches this file frontend/src/js/actions/workspaces/addResourceToWorkspace.ts:1
- No test reaches this file frontend/src/js/components/UtilComponents/InputSupper/LabelSupper.jsx:1
- No test reaches this file frontend/src/js/actions/getNodes.js:1
- No test reaches this file frontend/src/js/components/UtilComponents/ProgressBar.tsx:1
- No test reaches this file frontend/src/js/actions/pages/navigateToHighlight.ts:1
- No test reaches this file frontend/src/js/components/DownloadLink/DownloadLink.jsx:1
- No test reaches this file infra/cdk/lib/constructs/GuStackWithGiantVPC.ts:1
- No test reaches this file frontend/src/js/actions/pages/loadPages.ts:1
- No test reaches this file frontend/src/js/types/Cluster.js:1
- No test reaches this file frontend/src/js/types/Query.ts:1
- No test reaches this file frontend/src/js/services/ClusterApi.js:1
- No test reaches this file frontend/src/js/actions/pages/resetPages.ts:1
- No test reaches this file frontend/src/js/actions/resources/clearResource.js:1
- No test reaches this file frontend/src/js/types/WizardSlide.js:1
- No test reaches this file frontend/src/js/util/regexEscape.ts:1
- FunctionTooLong: CaptureFromUrl.CaptureFromUrl frontend/src/js/components/Uploads/CaptureFromUrl.tsx:75
- FunctionTooLong: WorkspaceSummary.WorkspaceSummary frontend/src/js/components/workspace/WorkspaceSummary.tsx:55
- FunctionTooLong: UploadFiles.UploadFiles frontend/src/js/components/Uploads/UploadFiles.tsx:314
- FunctionTooLong: PreviewSwitcher.PreviewSwitcher frontend/src/js/components/viewer/PreviewSwitcher.tsx:45
- FunctionTooLong: DownloadTextModal.DownloadTextModal frontend/src/js/components/workspace/DownloadTextModal.tsx:53
- FunctionTooLong: PageViewerOrFallback.PageViewerOrFallback frontend/src/js/components/PageViewerOrFallback.tsx:175
- FunctionTooLong: TranscriptViewer.TranscriptViewer frontend/src/js/components/viewer/TranscriptViewer/TranscriptViewer.tsx:23
- FunctionTooLong: GiantEuiLeftHandNav.GiantEuiLeftHandNav frontend/src/js/eui-components/GiantEuiLeftHandNav.tsx:36
- FunctionTooLong: DocumentFooter.DocumentFooter frontend/src/js/components/viewer/DocumentFooter.tsx:45
- FunctionTooLong: LazyTreeBrowser.LazyTreeBrowser frontend/src/js/components/viewer/LazyTreeBrowser.tsx:97
- FunctionTooLong: AllIngestionEvents.AllIngestionEvents frontend/src/js/components/IngestionEvents/AllIngestionEvents.tsx:33
- FunctionTooLong: IngestionEvents.IngestionEvents frontend/src/js/components/IngestionEvents/IngestionEvents.tsx:427
- FunctionTooLong: SidebarComments.SidebarComments frontend/src/js/components/viewer/SidebarComments.tsx:27
- FunctionTooLong: CommentPanel.CommentPanel frontend/src/js/components/viewer/CommentPanel/CommentPanel.tsx:174
- Markup wires an event to an empty handler frontend/src/js/components/PageViewer/FindInput.tsx:114
- Markup wires an event to an empty handler frontend/src/js/components/Uploads/CaptureFromUrl.tsx:306
- Markup wires an event to an empty handler frontend/src/js/components/Uploads/CaptureFromUrl.tsx:307
- Markup wires an event to an empty handler frontend/src/js/components/Uploads/CaptureFromUrl.tsx:308
- Markup wires an event to an empty handler frontend/src/js/components/Uploads/CaptureFromUrl.tsx:309
- Markup wires an event to an empty handler frontend/src/js/components/Uploads/CaptureFromUrl.tsx:310
- Markup wires an event to an empty handler frontend/src/js/components/viewer/AddToWorkspaceModal.tsx:168
- Markup wires an event to an empty handler frontend/src/js/components/viewer/AddToWorkspaceModal.tsx:170
- Markup wires an event to an empty handler frontend/src/js/components/viewer/AddToWorkspaceModal.tsx:172
- Markup wires an event to an empty handler frontend/src/js/components/viewer/AddToWorkspaceModal.tsx:174
- Markup wires an event to an empty handler frontend/src/js/components/viewer/AddToWorkspaceModal.tsx:176
- Markup wires an event to an empty handler frontend/src/js/components/viewer/LazyTreeBrowser.tsx:207
- Markup wires an event to an empty handler frontend/src/js/components/viewer/LazyTreeBrowser.tsx:216
- Markup wires an event to an empty handler frontend/src/js/components/workspace/Workspaces.tsx:1281
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Low cohesion: Neo4jManifest (LCOM4 40) backend/app/services/manifest/Neo4jManifest.scala:47
- Low cohesion: Neo4jAnnotations (LCOM4 17) backend/app/services/annotations/Neo4jAnnotations.scala:29
- Low cohesion: ElasticsearchResources (LCOM4 16) backend/app/services/index/ElasticsearchResources.scala:28
- Low cohesion: Neo4jUserManagement (LCOM4 10) backend/app/services/users/Neo4jUserManagement.scala:34
- Low cohesion: Collections (LCOM4 9) backend/app/controllers/api/Collections.scala:27
- Low cohesion: Neo4jRemoteIngestStore (LCOM4 7) backend/app/services/ingestion/Neo4jRemoteIngestStore.scala:24
- Low cohesion: Users (LCOM4 6) backend/app/controllers/api/Users.scala:15
- Low cohesion: Workspaces (LCOM4 5) backend/app/controllers/api/Workspaces.scala:79
- Low cohesion: PostgresClientImpl (LCOM4 4) backend/app/services/observability/PostgresClient.scala:34
- Duplicated block (12 lines × 2 locations) frontend/src/js/components/Collections/CurrentCollection/CurrentCollection.tsx:93
- Duplicated block (12 lines × 2 locations) frontend/src/js/components/Settings/FeatureSwitches.tsx:81
- Duplicated block (12 lines × 2 locations) frontend/src/js/components/Settings/SettingsSidebar.jsx:23
- Duplicated block (12 lines × 2 locations) frontend/src/js/components/UtilComponents/TreeBrowser/index.tsx:235
- Duplicated block (12 lines × 2 locations) frontend/src/js/components/users/CreateGenesisUser.jsx:246
- Duplicated block (12 lines × 2 locations) frontend/src/js/components/viewer/StatusBar.jsx:75
- Duplicated block (12 lines × 2 locations) frontend/src/js/services/WorkspaceApi.ts:16
- <Select> field component without a label frontend/src/js/components/Search/Search.tsx:237
- <Select> field component without a label frontend/src/js/components/Search/Search.tsx:250
- <Select> field component without a label frontend/src/js/components/Uploads/CaptureFromUrl.tsx:239
- <Select> field component without a label frontend/src/js/components/viewer/AddToWorkspaceModal.tsx:224
- <Select> field component without a label frontend/src/js/components/viewer/DownloadModal.jsx:262
- <Select> field component without a label frontend/src/js/components/workspace/CreateWorkspaceModal.tsx:92
- Focus outline removed in CSS without a :focus replacement frontend/src/stylesheets/components/_document.scss:279
- Focus outline removed in CSS without a :focus replacement frontend/src/stylesheets/components/_file-browser.scss:61
- Focus outline removed in CSS without a :focus replacement backend/public/third-party/pdfjs-2.4.456-dist/web/viewer.css:439
- Focus outline removed in CSS without a :focus replacement backend/public/third-party/pdfjs-2.4.456-dist/web/viewer.css:643
- Focus outline removed in CSS without a :focus replacement backend/public/third-party/pdfjs-2.4.456-dist/web/viewer.css:1361
- Focus outline removed in CSS without a :focus replacement backend/public/third-party/pdfjs-2.4.456-dist/web/viewer.css:1606
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <AutosizeInput> field component without a label frontend/src/js/components/UtilComponents/InputSupper/Chip.jsx:253
- <AutosizeInput> field component without a label frontend/src/js/components/UtilComponents/InputSupper/Chip.jsx:302
- <AutosizeInput> field component without a label frontend/src/js/components/UtilComponents/InputSupper/Chip.jsx:383
- <AutosizeInput> field component without a label frontend/src/js/components/UtilComponents/InputSupper/InlineInput.jsx:143
- Animation without a prefers-reduced-motion guard frontend/src/stylesheets/components/_comments.scss:18
- Animation without a prefers-reduced-motion guard frontend/src/stylesheets/components/_progress-bar.scss:11
- Animation without a prefers-reduced-motion guard backend/public/third-party/pdfjs-2.4.456-dist/web/viewer.css:773
- Animation without a prefers-reduced-motion guard backend/public/third-party/pdfjs-2.4.456-dist/web/viewer.css:803
- Hotspot: frontend/src/js/components/viewer/PreviewSwitcher.tsx frontend/src/js/components/viewer/PreviewSwitcher.tsx:45
- Hotspot: backend/app/extraction/ExternalTranscriptionWorker.scala backend/app/extraction/ExternalTranscriptionWorker.scala:68
- Hotspot: frontend/src/js/components/Uploads/CaptureFromUrl.tsx frontend/src/js/components/Uploads/CaptureFromUrl.tsx:75
- Hotspot: frontend/src/js/components/viewer/Viewer.tsx frontend/src/js/components/viewer/Viewer.tsx:247
- FileTooLong: manifest/Neo4jManifest.scala backend/app/services/manifest/Neo4jManifest.scala
- FileTooLong: workspace/Workspaces.tsx frontend/src/js/components/workspace/Workspaces.tsx
- FileTooLong: index/ElasticsearchResources.scala backend/app/services/index/ElasticsearchResources.scala
- FileTooLong: annotations/Neo4jAnnotations.scala backend/app/services/annotations/Neo4jAnnotations.scala
- MethodTooLong: WorkspacesUnconnected.renderContextMenu frontend/src/js/components/workspace/Workspaces.tsx:885
- MethodTooLong: WorkspacesUnconnected.renderFolderTree frontend/src/js/components/workspace/Workspaces.tsx:1119
- MethodTooLong: Timeline.renderChart frontend/src/js/components/EmailBrowser/Timeline.jsx:174
- MethodTooLong: WorkspacesUnconnected.render frontend/src/js/components/workspace/Workspaces.tsx:1304
- Duplicated block (11 lines × 2 locations) frontend/src/js/components/UtilComponents/InputSupper/Chip.jsx:57
- Duplicated block (11 lines × 2 locations) frontend/src/js/components/viewer/Viewer.tsx:255
- Duplicated block (11 lines × 2 locations) frontend/src/js/components/workspace/ShareWorkspaceModal.tsx:71
- Duplicated block (11 lines × 2 locations) frontend/src/js/components/workspace/Workspaces.tsx:1399
- Boundary violation [package:third-party-deep-import] infra/cdk/lib/constructs/GuStackWithGiantVPC.ts:1
- Boundary violation [package:third-party-deep-import] infra/cdk/lib/constructs/GuStackWithGiantVPC.ts:2
- Boundary violation [package:third-party-deep-import] infra/cdk/lib/constructs/GuStackWithGiantVPC.ts:7
- Boundary violation [package:third-party-deep-import] infra/cdk/lib/postgres.ts:2
- Data table has no header cells frontend/src/js/components/Settings/About.tsx:16
- Data table has no header cells frontend/src/js/components/Uploads/FileList.tsx:129
- Data table has no header cells frontend/src/js/components/viewer/PagedBrowser.tsx:56
- ClassTooLong: WorkspacesUnconnected frontend/src/js/components/workspace/Workspaces.tsx:134
- ClassTooLong: ElasticsearchResources backend/app/services/index/ElasticsearchResources.scala:28
- ClassTooLong: VideoVerifier frontend/src/js/components/VideoVerifier.tsx:1
- Edited copy of a member (13 corresponding lines) backend/app/controllers/api/Blobs.scala:32
- Edited copy of a member (13 corresponding lines) backend/app/services/IngestStorage.scala:39
- Edited copy of a member (13 corresponding lines) backend/app/services/annotations/Neo4jAnnotations.scala:755
- Duplicated block (5 lines × 2) backend/app/controllers/api/Workspaces.scala:407
- Duplicated block (5 lines × 2) backend/app/services/annotations/Neo4jAnnotations.scala:65
- Duplicated block (5 lines × 2) backend/app/model/manifest/Collection.scala:15
- Duplicated block (13 lines × 2 locations) frontend/src/js/components/Search/Search.tsx:236
- Duplicated block (13 lines × 2 locations) frontend/src/js/components/viewer/DocumentMetadata.jsx:140
- Duplicated block (13 lines × 2 locations) frontend/src/js/components/workspace/Workspaces.tsx:651
- <video> without a captions track frontend/src/js/components/viewer/Preview.tsx:123
- <video> without a captions track frontend/src/js/components/viewer/TranscriptViewer/TranscriptViewer.tsx:139
- <EuiSelect> field component without a label frontend/src/js/components/IngestionEvents/AllIngestionEvents.tsx:111
- <EuiSelect> field component without a label frontend/src/js/components/IngestionEvents/AllIngestionEvents.tsx:131
- FixmeComment backend/app/controllers/api/VideoVerifier.scala:28
- FixmeComment backend/app/commands/GetPages.scala:45
- Edited copy of a member (15 corresponding lines) backend/app/services/ingestion/Neo4jRemoteIngestStore.scala:212
- Edited copy of a member (15 corresponding lines) common/src/main/scala/utils/AwsS3Clients.scala:23
- Edited copy of a member (7 corresponding lines) backend/app/controllers/api/Workspaces.scala:190
- Edited copy of a member (7 corresponding lines) backend/app/model/frontend/TreeEntry.scala:60
- Edited copy of a member (8 corresponding lines) backend/app/controllers/api/Users.scala:53
- Edited copy of a member (8 corresponding lines) backend/app/services/index/Pages2.scala:23
- Tests run only outside the merge gate REDACTED:80
- Tests run only outside the merge gate REDACTED:130
- Duplicated block with local edits (19 matched lines × 2 locations) frontend/src/js/components/Uploads/FilePicker.tsx:88
- Duplicated block with local edits (19 matched lines × 2 locations) frontend/src/js/components/viewer/Viewer.tsx:175
- Duplicated block (17 lines × 2 locations) frontend/src/js/actions/workspaces/deleteItem.ts:11
- Duplicated block (17 lines × 2 locations) frontend/src/js/components/viewer/Preview.tsx:114
- Duplicated block (15 lines × 2 locations) frontend/src/js/actions/workspaces/addFolderToWorkspace.ts:3
- Duplicated block (15 lines × 2 locations) frontend/src/js/services/WorkspaceApi.ts:94
- Duplicated block with local edits (11 matched lines × 2 locations) frontend/src/js/components/SearchSidebar/SearchFilterOption.jsx:38
- Duplicated block with local edits (11 matched lines × 2 locations) frontend/src/js/components/viewer/LazyTreeBrowser.tsx:143
- Dead file (~131 LoC) frontend/src/js/components/viewer/PageViewer/PageViewer.tsx
- Dead file (~131 LoC) frontend/src/js/components/viewer/PageViewer/pageViewerApi.ts
- Untrusted text written into markup unescaped frontend/src/js/components/UtilComponents/HighlightedText.tsx:10
- Untrusted text written into markup unescaped frontend/src/js/components/UtilComponents/HighlightedText.tsx:24
- Swallowed exception (caught, then discarded) cli/src/main/scala/com/gu/pfi/cli/service/CliVeracrypt.scala:47
- Swallowed exception (caught, then discarded) backend/app/utils/HtmlToPlainText.scala:31
- <canvas> without a text alternative frontend/src/js/components/viewer/PageViewer/PagePreview.tsx:184
- Page without a main landmark frontend/index.html:2
- VideoVerifier.VideoVerifier (cyclomatic 50) frontend/src/js/components/VideoVerifier.tsx:41
- PreviewSwitcher.PreviewSwitcher (cyclomatic 46) frontend/src/js/components/viewer/PreviewSwitcher.tsx:45
- CaptureFromUrl.CaptureFromUrl (cyclomatic 36) frontend/src/js/components/Uploads/CaptureFromUrl.tsx:75
- WorkspacesUnconnected.renderContextMenu (cyclomatic 36) frontend/src/js/components/workspace/Workspaces.tsx:885
- DocumentFooter.DocumentFooter (cyclomatic 31) frontend/src/js/components/viewer/DocumentFooter.tsx:45
- UploadFiles.UploadFiles (cyclomatic 29) frontend/src/js/components/Uploads/UploadFiles.tsx:314
- VirtualScroll.VirtualScroll (cyclomatic 26) frontend/src/js/components/PageViewer/VirtualScroll.tsx:57
- TranscriptViewer.TranscriptViewer (cyclomatic 25) frontend/src/js/components/viewer/TranscriptViewer/TranscriptViewer.tsx:23
- PageViewerOrFallback.PageViewerOrFallback (cyclomatic 25) frontend/src/js/components/PageViewerOrFallback.tsx:175
- ExternalTranscriptionWorker.handleMessage (cyclomatic 24) backend/app/extraction/ExternalTranscriptionWorker.scala:68
- Neo4jAnnotations.getWorkspaceContents (cyclomatic 21) backend/app/services/annotations/Neo4jAnnotations.scala:110
- Preview.Preview (cyclomatic 21) frontend/src/js/components/viewer/Preview.tsx:47
- Ocr.invokeOcrMyPdf (cyclomatic 19) backend/app/utils/Ocr.scala:214
- Viewer.renderFullContents (cyclomatic 19) frontend/src/js/components/viewer/Viewer.tsx:247
- DownloadTextModal.DownloadTextModal (cyclomatic 19) frontend/src/js/components/workspace/DownloadTextModal.tsx:53
- InlineInput.onKeyPress (cyclomatic 19) frontend/src/js/components/UtilComponents/InputSupper/InlineInput.jsx:39
- RemoteIngestWorker.processFinishedJobs (cyclomatic 18) backend/app/services/ingestion/RemoteIngestWorker.scala:109
- LazyTreeBrowser.LazyTreeBrowser (cyclomatic 17) frontend/src/js/components/viewer/LazyTreeBrowser.tsx:97
- GiantEuiLeftHandNav.GiantEuiLeftHandNav (cyclomatic 17) frontend/src/js/eui-components/GiantEuiLeftHandNav.tsx:36
- parseDate.parseDateNoFallback (cyclomatic 16) frontend/src/js/util/parseDate.ts:63
- ModalAction.ModalAction (cyclomatic 16) frontend/src/js/components/UtilComponents/ModalAction.tsx:33
- WorkspacesUnconnected.render (cyclomatic 16) frontend/src/js/components/workspace/Workspaces.tsx:1304
- PageViewer.PageViewer (cyclomatic 16) frontend/src/js/components/viewer/PageViewer/PageViewer.tsx:16
- RemoteIngestWorker.processFinishedJobs (cognitive 104) backend/app/services/ingestion/RemoteIngestWorker.scala:109
- Neo4jAnnotations.getWorkspaceContents (cognitive 58) backend/app/services/annotations/Neo4jAnnotations.scala:110
- VideoVerifier.VideoVerifier (cognitive 55) frontend/src/js/components/VideoVerifier.tsx:41
- PreviewSwitcher.PreviewSwitcher (cognitive 48) frontend/src/js/components/viewer/PreviewSwitcher.tsx:45
- ExternalTranscriptionWorker.handleMessage (cognitive 40) backend/app/extraction/ExternalTranscriptionWorker.scala:68
- DeleteResource.deleteResource (cognitive 36) backend/app/commands/DeleteResource.scala:56
- UploadFiles.UploadFiles (cognitive 32) frontend/src/js/components/Uploads/UploadFiles.tsx:314
- DocumentFooter.DocumentFooter (cognitive 32) frontend/src/js/components/viewer/DocumentFooter.tsx:45
- Preview.Preview (cognitive 31) frontend/src/js/components/viewer/Preview.tsx:47
- WorkspacesUnconnected.renderContextMenu (cognitive 31) frontend/src/js/components/workspace/Workspaces.tsx:885
- Viewer.renderFullContents (cognitive 30) frontend/src/js/components/viewer/Viewer.tsx:247
- CaptureFromUrl.CaptureFromUrl (cognitive 30) frontend/src/js/components/Uploads/CaptureFromUrl.tsx:75
- TranscriptViewer.TranscriptViewer (cognitive 28) frontend/src/js/components/viewer/TranscriptViewer/TranscriptViewer.tsx:23
- DownloadTextModal.DownloadTextModal (cognitive 27) frontend/src/js/components/workspace/DownloadTextModal.tsx:53
- VirtualScroll.VirtualScroll (cognitive 27) frontend/src/js/components/PageViewer/VirtualScroll.tsx:57
- PageViewerOrFallback.PageViewerOrFallback (cognitive 25) frontend/src/js/components/PageViewerOrFallback.tsx:175
- MoveIngestion.process (cognitive 23) backend/app/commands/MoveIngestion.scala:18
- ExternalTranslationExtractor.triggerExtraction (cognitive 23) backend/app/extraction/ExternalTranslationExtractor.scala:52
- IngestionServices.apply (cognitive 23) backend/app/services/ingestion/IngestionServices.scala:128
- ExcelTableExtractor.getCellValue (cognitive 21) backend/app/extraction/tables/ExcelTableExtractor.scala:105
- DatabaseUserProvider.genesisUser (cognitive 21) backend/app/utils/auth/providers/DatabaseUserProvider.scala:48
- Blobs.reprocess (cognitive 20) backend/app/controllers/api/Blobs.scala:60
- ExcelTableExtractor.readRows (cognitive 20) backend/app/extraction/tables/ExcelTableExtractor.scala:61
- dropZoneUtils.readFilesFromDragEvent (cognitive 20) frontend/src/js/components/Uploads/dropZoneUtils.ts:34
- InlineInput.onKeyPress (cognitive 20) frontend/src/js/components/UtilComponents/InputSupper/InlineInput.jsx:39
- DefaultAuthActionBuilder.invokeBlockWithTime (cognitive 19) backend/app/utils/auth/AuthActionBuilder.scala:36
- PanDomainUserProvider.authenticate (cognitive 19) backend/app/utils/auth/providers/PanDomainUserProvider.scala:33
- GiantEuiLeftHandNav.GiantEuiLeftHandNav (cognitive 19) frontend/src/js/eui-components/GiantEuiLeftHandNav.tsx:36
- Workspaces.copyItem (cognitive 18) backend/app/controllers/api/Workspaces.scala:421
- Neo4jManifest.moveIngestionToCollection (cognitive 18) backend/app/services/manifest/Neo4jManifest.scala:1441
- DatabaseUserProvider.createUser (cognitive 18) backend/app/utils/auth/providers/DatabaseUserProvider.scala:61
- Timeline.renderChart (cognitive 18) frontend/src/js/components/EmailBrowser/Timeline.jsx:174
- DownloadModal.componentDidUpdate (cognitive 18) frontend/src/js/components/viewer/DownloadModal.jsx:44
- Chips.parseQueryString (cognitive 17) backend/app/model/frontend/Chip.scala:60
- ConfirmModal.DeleteModal (cognitive 17) frontend/src/js/components/workspace/ConfirmModal.tsx:11
- CreateNewUserUnconnected.errors (cognitive 17) frontend/src/js/components/users/CreateNewUser.jsx:48
- ExternalOcrMyPdfExtractor.extract (cognitive 16) backend/app/extraction/ExternalOcrMyPdfExtractor.scala:34
- PageViewer.PageViewer (cognitive 16) frontend/src/js/components/viewer/PageViewer/PageViewer.tsx:16
- TooManyMethods: WorkspacesUnconnected frontend/src/js/components/workspace/Workspaces.tsx:134
- REDACTED
- Change coupling: AllIngestionEvents.tsx ↔ MyUploads.tsx frontend/src/js/components/IngestionEvents/AllIngestionEvents.tsx:1
- Edited copies of one member (3 members, 36+ corresponding lines) backend/app/services/manifest/Neo4jManifest.scala:711
- Edited copy of a member (31 corresponding lines) backend/app/services/users/Neo4jUserManagement.scala:99
- Edited copies of one member (3 members, 21+ corresponding lines) backend/app/services/annotations/Neo4jAnnotations.scala:52
- Edited copy of a member (26 corresponding lines) backend/app/utils/AwsDiscovery.scala:131
- Edited copy of a member (37 corresponding lines) backend/app/services/manifest/Neo4jManifest.scala:1044
- Edited copy of a member (18 corresponding lines) backend/app/utils/RequestLoggingFilter.scala:42
- Edited copy of a member (16 corresponding lines) backend/app/services/index/ElasticsearchResources.scala:235
- Edited copy of a member (19 corresponding lines) backend/app/services/users/Neo4jUserManagement.scala:45
- Edited copy of a member (5 corresponding lines) backend/app/utils/Binders.scala:24
- Edited copies of one member (6 members, 20+ corresponding lines) backend/app/services/annotations/Neo4jAnnotations.scala:288
- Edited copy of a member (9 corresponding lines) backend/app/controllers/api/PagesController.scala:136
- Edited copy of a member (6 corresponding lines) backend/app/model/frontend/TreeEntry.scala:26
- Edited copies of one member (5 members, 10+ corresponding lines) backend/app/controllers/api/Workspaces.scala:206
- Edited copy of a member (14 corresponding lines) backend/app/utils/Neo4jHelper.scala:81
- Edited copies of one member (3 members, 17+ corresponding lines) backend/app/services/manifest/Neo4jManifest.scala:1149
- Edited copy of a member (10 corresponding lines) backend/app/services/ExternalWorkerScheduler.scala:22
- Edited copies of one member (3 members, 4+ corresponding lines) backend/app/services/ExternalWorkerScheduler.scala:37
- Duplicated block (30–34 lines × 2) backend/app/services/manifest/Neo4jManifest.scala:748
- Duplicated block (25–27 lines × 2) backend/app/services/users/Neo4jUserManagement.scala:99
- Duplicated block (7 lines × 2) backend/app/services/index/ElasticsearchPages.scala:223
- Duplicated block (6 lines × 2) backend/app/services/manifest/Neo4jManifest.scala:732
- Off the main sequence: transcriptionWorkerInterface
- Hollow method — returns a constant without doing the work frontend/src/js/eui-components/GiantEuiWorkspace.tsx:36
- Both branches are identical — the condition decides nothing infra/cdk/lib/postgres.ts:54
- CI formatting step cannot fail REDACTED:27
- No DR/backup evidence
- Sync-over-async blocking cli/src/main/scala/com/gu/pfi/cli/ingestion/CliIngestionPipeline.scala:30
- Duplication concentrated across 10 sibling directories (13 clone groups) frontend/src/js/components/Uploads/FilePicker.tsx:88
- Duplicated block with local edits (148 matched lines × 2 locations) frontend/src/js/components/users/CreateGenesisUser.jsx:41
- Duplicated block with local edits (41 matched lines × 2 locations) frontend/src/js/components/UtilComponents/TreeBrowser/Leaf.tsx:6
- Duplicated block with local edits (36 matched lines × 2 locations) frontend/src/js/components/Settings/ExtractionFailuresComponent.tsx:89
- Duplicated block (36 lines × 2 locations) frontend/src/js/components/UtilComponents/InputSupper/Chip.jsx:232
- Duplicated block (27 lines × 2 locations) frontend/src/js/actions/auth/invalidateAuthToken.js:3
- Duplicated block (20 lines × 2 locations) frontend/src/js/actions/workspaces/addFolderToWorkspace.ts:11
- Duplicated block (18 lines × 3 locations) frontend/src/js/actions/workspaces/renameWorkspace.ts:12
- Duplicated block (18 lines × 4 locations) frontend/src/js/actions/workspaces/renameWorkspace.ts:14
- Duplicated block (18 lines × 2 locations) frontend/src/js/components/viewer/DeleteButtonModal.tsx:69
- Duplicated block (16 lines × 2 locations) frontend/src/js/components/UtilComponents/TreeBrowser/Node.tsx:273
- Duplicated block with local edits (15 matched lines × 2 locations) frontend/src/js/components/IngestionEvents/MyUploads.tsx:125
- Duplicated block (15 lines × 3 locations) frontend/src/js/components/users/CreateGenesisUser.jsx:140
- Duplicated block (14 lines × 3 locations) frontend/src/js/actions/workspaces/addFolderToWorkspace.ts:17
- Duplicated block (14 lines × 2 locations) frontend/src/js/components/SearchResults/SearchResult.jsx:87
- Duplicated block with local edits (13 matched lines × 2 locations) frontend/src/js/components/Settings/DatasetPermissions.jsx:26
- Duplicated block (12 lines × 9 locations) frontend/src/js/actions/workspaces/addFolderToWorkspace.ts:19
- Duplicated block with local edits (10 matched lines × 2 locations) frontend/src/js/components/PageViewer/PdfHelpers.ts:46
- Complex function DocumentFooter (cyclomatic 25, cognitive 22) frontend/src/js/components/viewer/DocumentFooter.tsx:45
- Complex function (anonymous) (cyclomatic 22, cognitive 16) frontend/src/js/components/Uploads/CaptureFromUrl.tsx:75
- Complex function onKeyPress (cyclomatic 19, cognitive 21) frontend/src/js/components/UtilComponents/InputSupper/InlineInput.jsx:39
- Complex function (anonymous) (cyclomatic 18, cognitive 16) frontend/src/js/components/workspace/Workspaces.tsx:993
- Complex function PageViewerOrFallback (cyclomatic 17, cognitive 21) frontend/src/js/components/PageViewerOrFallback.tsx:175
- Complex function parseDateNoFallback (cyclomatic 16, cognitive 15) frontend/src/js/util/parseDate.ts:63
- Complex function PreviewSwitcher (cyclomatic 16, cognitive 14) frontend/src/js/components/viewer/PreviewSwitcher.tsx:45
- Complex function UploadFiles (cyclomatic 16, cognitive 13) frontend/src/js/components/Uploads/UploadFiles.tsx:314
- Complex function Preview (cyclomatic 15, cognitive 22) frontend/src/js/components/viewer/Preview.tsx:47
- Complex function (anonymous) (cyclomatic 15, cognitive 14) frontend/src/js/components/viewer/PreviewSwitcher.tsx:51
- Complex function VideoVerifier (cyclomatic 14, cognitive 13) frontend/src/js/components/VideoVerifier.tsx:41
- Complex function readFilesFromDragEvent (cyclomatic 13, cognitive 20) frontend/src/js/components/Uploads/dropZoneUtils.ts:34
- Complex function buildLink (cyclomatic 12, cognitive 11) frontend/src/js/util/buildLink.ts:5
- Complex function WorkspaceSummary (cyclomatic 12, cognitive 9) frontend/src/js/components/workspace/WorkspaceSummary.tsx:55
- Complex function PageViewerContent (cyclomatic 11, cognitive 13) frontend/src/js/components/PageViewerOrFallback.tsx:68
- Complex function onKeyDownText (cyclomatic 11, cognitive 9) frontend/src/js/components/UtilComponents/InputSupper/Chip.jsx:46
- frontend/src/js/components/workspace/Workspaces.tsx: 1401 lines of code frontend/src/js/components/workspace/Workspaces.tsx:1
- frontend/src/js/components/VideoVerifier.tsx: 567 lines of code frontend/src/js/components/VideoVerifier.tsx:1
- frontend/src/js/components/IngestionEvents/IngestionEvents.tsx: 537 lines of code frontend/src/js/components/IngestionEvents/IngestionEvents.tsx:1
- frontend/src/js/components/Uploads/UploadFiles.tsx: 476 lines of code frontend/src/js/components/Uploads/UploadFiles.tsx:1
- frontend/src/js/components/viewer/Viewer.tsx: 416 lines of code frontend/src/js/components/viewer/Viewer.tsx:1
- frontend/src/js/components/UtilComponents/InputSupper/index.jsx: 412 lines of code frontend/src/js/components/UtilComponents/InputSupper/index.jsx:1
- This package's lint script runs in no CI job e2e-tests/package.json:12
- Dead file (~231 LoC) frontend/src/js/components/viewer/StatusBar.jsx
- Dead file (~189 LoC) frontend/src/js/components/viewer/PageViewer/PagePreview.tsx
- Dead file (~135 LoC) frontend/src/js/components/UtilComponents/Wizard.jsx
- Dead file (~104 LoC) frontend/src/js/components/viewer/PageViewer/pageViewerPdf.ts
- Dead file (~90 LoC) frontend/src/js/components/viewer/PageViewer/PageViewerStatusBar.tsx
- Dead file (~58 LoC) frontend/src/js/components/viewer/HighlightToggle.jsx
- Dead file (~42 LoC) frontend/src/js/actions/workspaces/addResourceToWorkspace.ts
- Dead file (~41 LoC) frontend/src/js/components/UtilComponents/InputSupper/LabelSupper.jsx
- Dead file (~36 LoC) frontend/src/js/actions/getNodes.js
- Dead file (~27 LoC) frontend/src/js/components/UtilComponents/ProgressBar.tsx
- Dead file (~26 LoC) frontend/src/js/actions/pages/navigateToHighlight.ts
- Dead file (~25 LoC) frontend/src/js/components/DownloadLink/DownloadLink.jsx
- Dead file (~20 LoC) frontend/src/js/actions/pages/loadPages.ts
- Dead file (~17 LoC) frontend/src/js/types/Cluster.js
- Dead file (~15 LoC) frontend/src/js/types/Query.ts
- Dead file (~11 LoC) frontend/src/js/services/ClusterApi.js
- Dead file (~9 LoC) frontend/src/js/actions/pages/resetPages.ts
- Dead file (~8 LoC) frontend/src/js/actions/resources/clearResource.js
- Dead file (~7 LoC) frontend/src/js/types/WizardSlide.js
- Dead file (~3 LoC) frontend/src/js/util/regexEscape.ts
- Dead file (~1 LoC) frontend/src/js/components/DownloadLink/index.js
- Unused dependency '@guardian/node-riffraff-artifact' infra/cdk/package.json:17
- Unused dependency 'source-map-support' infra/cdk/package.json:28
- Unused dependency 'string-argv' REDACTED:16
- Weak hash algorithm backend/app/services/observability/Models.scala:223
- Future started here is not kept backend/app/services/previewing/PreviewService.scala:120
- Recursive walk over a caller-supplied document has no depth cap frontend/src/js/util/UrlParameters.ts:40
- Swallowed exception (empty catch) frontend/src/js/components/UtilComponents/documentTitle.ts:68
Minor — 145 finding(s)
- Orphaned file backend/app/utils/Neo4jHelper.scala:1
- Orphaned file backend/app/services/index/ElasticsearchPages.scala:1
- Orphaned file common/src/main/scala/utils/attempt/Attempt.scala:1
- Orphaned file backend/app/model/Email.scala:1
- Orphaned file cli/src/main/scala/com/gu/pfi/cli/Options.scala:1
- Orphaned file backend/app/services/previewing/PreviewService.scala:1
- Orphaned file backend/app/model/frontend/Resource.scala:1
- Orphaned file backend/app/controllers/api/Search.scala:1
- Orphaned file backend/app/extraction/email/olm/OlmEmailExtractor.scala:1
- Orphaned file backend/app/services/ElasticsearchSyntax.scala:1
- Orphaned file backend/app/commands/GetResource.scala:1
- Orphaned file cli/src/main/scala/com/gu/pfi/cli/service/CliHttpClient.scala:1
- Orphaned file cli/src/main/scala/com/gu/pfi/cli/ingestion/CliIngestionPipeline.scala:1
- Orphaned file backend/app/extraction/tables/ExcelTableExtractor.scala:1
- Orphaned file backend/app/model/frontend/Chip.scala:1
- Orphaned file backend/app/utils/PDFUtil.scala:1
- Orphaned file backend/app/utils/auth/providers/DatabaseUserProvider.scala:1
- Orphaned file backend/app/utils/auth/totp/Totp.scala:1
- Orphaned file cli/src/main/scala/com/gu/pfi/cli/service/CliIngestionService.scala:1
- Orphaned file frontend/src/js/components/PageViewer/PageCache.ts:1
- Orphaned file backend/app/services/events/Events.scala:1
- Orphaned file backend/app/extraction/email/pst/PstEmailExtractor.scala:1
- Orphaned file backend/app/controllers/api/Users.scala:1
- Orphaned file backend/app/extraction/email/msg/MsgEmailExtractor.scala:1
- Orphaned file backend/app/utils/auth/AuthActionBuilder.scala:1
- Interpolated log message defeats structured logging common/src/main/scala/utils/Timing.scala:12
- Interpolated log message defeats structured logging cli/src/main/scala/com/gu/pfi/cli/DeleteIngestions.scala:77
- Interpolated log message defeats structured logging cli/src/main/scala/com/gu/pfi/cli/HashFiles.scala:13
- Interpolated log message defeats structured logging cli/src/main/scala/com/gu/pfi/cli/HashFiles.scala:15
- Interpolated log message defeats structured logging cli/src/main/scala/com/gu/pfi/cli/Main.scala:68
- Interpolated log message defeats structured logging cli/src/main/scala/com/gu/pfi/cli/Main.scala:146
- Interpolated log message defeats structured logging cli/src/main/scala/com/gu/pfi/cli/service/CliHttpClient.scala:162
- Interpolated log message defeats structured logging cli/src/main/scala/com/gu/pfi/cli/service/CliIngestionService.scala:46
- Interpolated log message defeats structured logging cli/src/main/scala/com/gu/pfi/cli/ingestion/CliFileWalker.scala:28
- Interpolated log message defeats structured logging backend/app/AppComponents.scala:151
- Interpolated log message defeats structured logging backend/app/utils/AwsDiscovery.scala:47
- Interpolated log message defeats structured logging backend/app/utils/AwsDiscovery.scala:189
- Interpolated log message defeats structured logging backend/app/utils/AwsDiscovery.scala:198
- Interpolated log message defeats structured logging backend/app/utils/AwsDiscovery.scala:222
- Interpolated log message defeats structured logging backend/app/utils/AwsDiscovery.scala:252
- Interpolated log message defeats structured logging backend/app/utils/AwsDiscovery.scala:257
- Interpolated log message defeats structured logging backend/app/utils/Ocr.scala:127
- Interpolated log message defeats structured logging backend/app/utils/Ocr.scala:157
- Interpolated log message defeats structured logging backend/app/utils/Ocr.scala:201
- Interpolated log message defeats structured logging backend/app/utils/Ocr.scala:207
- Interpolated log message defeats structured logging backend/app/utils/Ocr.scala:255
- Interpolated log message defeats structured logging backend/app/utils/Ocr.scala:277
- Interpolated log message defeats structured logging backend/app/utils/Ocr.scala:299
- Interpolated log message defeats structured logging backend/app/utils/WorkerControl.scala:82
- Interpolated log message defeats structured logging backend/app/utils/WorkerControl.scala:121
- Duplicated predicate frontend/src/js/components/SearchResults/CollectionLinks.tsx:10
- Duplicated predicate frontend/src/js/components/viewer/Viewer.tsx:116
- Duplicated predicate frontend/src/js/components/users/CreateGenesisUser.jsx:76
- Duplicated predicate frontend/src/js/components/Uploads/CaptureFromUrl.tsx:297
- Duplicated predicate frontend/src/js/components/UtilComponents/documentTitle.ts:15
- Duplicated predicate frontend/src/js/components/SearchSidebar/SearchFilterValue.jsx:126
- Duplicated predicate frontend/src/js/components/UtilComponents/TreeBrowser/Node.tsx:215
- Duplicated predicate frontend/src/js/components/users/CreateGenesisUser.jsx:51
- Duplicated predicate frontend/src/js/components/users/CreateGenesisUser.jsx:66
- Duplicated predicate frontend/src/js/components/users/CreateGenesisUser.jsx:84
- Fat interface: Annotations (22 abstract members) backend/app/services/annotations/Annotations.scala:12
- Fat interface: Index (25 abstract members) backend/app/services/index/Index.scala:11
- Fat interface: Manifest (30 abstract members) backend/app/services/manifest/Manifest.scala:56
- Fat interface: UserManagement (19 abstract members) backend/app/services/users/UserManagement.scala:11
- redundant comment frontend/src/js/components/EmailBrowser/Timeline.jsx:66
- redundant comment frontend/src/js/components/Uploads/dropZoneUtils.spec.ts:9
- redundant comment frontend/src/js/components/viewer/TranscriptViewer/TranscriptViewer.tsx:82
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Projects may be oversized for their cohesion REDACTED:1
- Projects may be oversized for their cohesion frontend/package.json:1
- Pending state with no failure state frontend/src/js/components/workspace/DownloadTextModal.tsx:203
- Pending state with no failure state frontend/src/js/components/Settings/ResourcesForExtractionFailureComponent.tsx:33
- Mock-dominated test: deselects when there is no selection and forwards outside-click events frontend/src/js/components/UtilComponents/SelectionPopover.spec.tsx:82
- Further sole-owners (lower concentration)
- No ADRs found REDACTED:185
- `workspaceID` spells `ID` where 85 names in the project spell it `Id` frontend/src/js/actions/workspaces/reprocessBlob.ts:11
- `maybeCapturedFromURL` spells `URL` where 12 names in the project spell it `Url` frontend/src/js/types/Workspaces.ts:9
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- Logging is not universal
- No SAST .github/workflows/check-labels.yaml:5
- No dependency-update automation e2e-tests/package.json:14
- No changelog
- Unused export 'default' frontend/src/js/components/workspace/ConfirmModal.tsx:183
- Unused export 'updatePasswordApi' frontend/src/js/services/UserApi.js:27
- Unused export 'updateFullnameApi' frontend/src/js/services/UserApi.js:35
- Unused export 'language' frontend/src/js/types/Collection.ts:12
- Unused export 'mimeTypeCoveragePropType' frontend/src/js/types/MimeType.ts:7
- Unused export 'SearchResultHighlight' frontend/src/js/types/SearchResults.ts:60
- Unused export 'SearchAggBucket' frontend/src/js/types/SearchResults.ts:95
- Unused export 'SearchAgg' frontend/src/js/types/SearchResults.ts:96
- Unused export 'suggestedFieldsPropType' frontend/src/js/types/SuggestedFields.ts:18
- Unused export 'partialUser' frontend/src/js/types/User.ts:5
- Unused export 'user' frontend/src/js/types/User.ts:14
- Unused export 'FocusedWorkspace' frontend/src/js/types/Workspaces.ts:58
- Unused export 'canLinkTo' frontend/src/js/util/resourceUtils.ts:37
- Unused export 'hrefFromResource' frontend/src/js/util/resourceUtils.ts:44
- No app-layer HTTPS enforcement detected
- Security headers incomplete
- Scala's null is not held to the type system everywhere
- Silent fallback default in catch cli/src/main/scala/com/gu/pfi/cli/service/CliVeracrypt.scala:47
Minor — 47 finding(s)
- Outdated: ch.qos.logback:logback-classic
- Outdated: com.auth0:java-jwt
- Outdated: com.beachape:enumeratum-play_2.13
- Outdated: com.beachape:enumeratum_2.13
- Outdated: com.github.jai-imageio:jai-imageio-jpeg2000
- Outdated: com.github.junrar:junrar
- Outdated: com.github.jwt-scala:jwt-play_2.13
- Outdated: com.google.guava:guava
- Outdated: com.gu:pan-domain-auth-verification_2.13
- Outdated: com.sksamuel.elastic4s:elastic4s-client-esjava_2.13
- Outdated: com.squareup.okhttp3:okhttp
- Outdated: commons-codec:commons-codec
- Outdated: commons-io:commons-io
- Outdated: net.logstash.logback:logstash-logback-encoder
- Outdated: org.apache.logging.log4j:log4j-api
- Outdated: org.apache.logging.log4j:log4j-core
- Outdated: org.apache.logging.log4j:log4j-to-slf4j
- Outdated: org.apache.pdfbox:jbig2-imageio
- Outdated: org.apache.pekko:pekko-cluster-typed_2.13
- Outdated: org.apache.tika:tika-core
- Outdated: org.apache.tika:tika-langdetect-optimaize
- Outdated: org.apache.tika:tika-parsers-standard-package
- Outdated: org.bouncycastle:bcprov-jdk18on
- Outdated: org.bouncycastle:bcutil-jdk18on
- Outdated: org.eclipse.angus:angus-mail
- doc comments repeat the names frontend/src/js/components/workspace/Workspaces.tsx:851
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 --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-3b874cbe8cbe4e67836fc84b0bc130a5/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-3b874cbe8cbe4e67836fc84b0bc130a5/history-1.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=1088" --report-format json --report-path /tmp/watchdog-gitleaks-3b874cbe8cbe4e67836fc84b0bc130a5/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.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-3b874cbe8cbe4e67836fc84b0bc130a5/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 . | 30 | 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/** . | 28 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 7 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |