Executive summary
alephdata/aleph is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 47.7 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 39.1, is the weakest lens and counts most in the score. The best first step is making the tests check their results, worth about 6.3 points. Planning backups and recovery would lift Production Readiness itself, worth about 5.3 points. Raising Production Readiness to 70 would lift the score to about 54.8.
Forty-six known security holes in the packages the code depends on can be used by attackers. Fifteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and nine settings leave the servers or containers unsafe. Updating the vulnerable packages, pinning each tool to an exact version and correcting the unsafe settings would close these risks. Limiting each secret to its own step would fix the six secrets exposed to more of the pipeline than needed, and the five passwords or keys in the code's history need replacing, with the old ones switched off. The ten form fields without a label need a label.
The product code is 53,188 lines, about €55,000 to rebuild.
If Production Readiness rose from 39.1 to 70, the lowest score rated Strong, the score would rise from 47.7 to about 54.8.
Rebuild cost: about €55,000 · Estimate
| Cost to rebuild | €18,000 to €93,000, for 307 to 974 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 48. 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: 53,188 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 aleph.model.common | 2 ui.src.components.Settings.ApiKeySettings | 3 ui.src.components.Timeline.types | 4 ui.src.components.common.Entity | 5 ui.src.components.common.Property | 6 ui.src.components.common.Schema | 7 ui.src.react-ftm.components.NetworkDiagram.layout.Point | 8 ui.src.react-ftm.components.NetworkDiagram.layout.Settings | 9 aleph.model.alert | 10 aleph.model.bookmark | 11 aleph.model.collection | 12 aleph.model.document | 13 aleph.model.entity | 14 aleph.model.entityset | 15 ui.src.components.Timeline.TimelineChart | 16 ui.src.components.Timeline.util | 17 ui.src.react-ftm.components.NetworkDiagram.GraphConfig | 18 ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle | 19 ui.src.react-ftm.components.common.types.EntityChanges | 20 ui.src.react-ftm.editors.PropertyEditor | 21 ui.src.react-ftm.types.EdgeType | 22 ui.src.react-ftm.utils | 23 ui.src.react-ftm.components.NetworkDiagram.Viewport | 24 ui.src.react-ftm.components.NetworkDiagram.layout.Edge | 25 ui.src.react-ftm.components.NetworkDiagram.layout.Grouping | 26 ui.src.react-ftm.components.NetworkDiagram.renderer.GraphRenderer | 27 ui.src.react-ftm.components.common.EntityManager | 28 ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout | 29 ui.src.react-ftm.components.common.EdgeCreateDialog | 30 ui.src.react-ftm.components.NetworkDiagram.GraphContext | 31 ui.src.react-ftm.components.NetworkDiagram.History | 32 ui.src.react-ftm.components.NetworkDiagram.layout.Vertex | 33 ui.src.components.Timeline | 34 ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram | 35 ui.src.react-ftm.components.NetworkDiagram.layout.tools.common | 36 ui.src.react-ftm.components.NetworkDiagram.renderer.EdgeRenderer | 37 ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar | 38 ui.src.react-ftm.components.NetworkDiagram.toolbox.Toolbar | 39 ui.src.react-ftm.components.NetworkDiagram.utils | 40 ui.src.react-ftm.components.NetworkDiagram.layout.tools |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 aleph.model.common | ||||||||||||||||||||||||||||||||||||||||
| 2 ui.src.components.Settings.ApiKeySettings | ||||||||||||||||||||||||||||||||||||||||
| 3 ui.src.components.Timeline.types | ||||||||||||||||||||||||||||||||||||||||
| 4 ui.src.components.common.Entity | ||||||||||||||||||||||||||||||||||||||||
| 5 ui.src.components.common.Property | ||||||||||||||||||||||||||||||||||||||||
| 6 ui.src.components.common.Schema | ||||||||||||||||||||||||||||||||||||||||
| 7 ui.src.react-ftm.components.NetworkDiagram.layout.Point | ||||||||||||||||||||||||||||||||||||||||
| 8 ui.src.react-ftm.components.NetworkDiagram.layout.Settings | ||||||||||||||||||||||||||||||||||||||||
| 9 aleph.model.alert | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 aleph.model.bookmark | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 aleph.model.collection | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 aleph.model.document | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 aleph.model.entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 aleph.model.entityset | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 ui.src.components.Timeline.TimelineChart | 3 | |||||||||||||||||||||||||||||||||||||||
| 16 ui.src.components.Timeline.util | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 ui.src.react-ftm.components.NetworkDiagram.GraphConfig | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 ui.src.react-ftm.components.common.types.EntityChanges | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 ui.src.react-ftm.editors.PropertyEditor | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 ui.src.react-ftm.types.EdgeType | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 ui.src.react-ftm.utils | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 ui.src.react-ftm.components.NetworkDiagram.Viewport | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 ui.src.react-ftm.components.NetworkDiagram.layout.Edge | 1 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 25 ui.src.react-ftm.components.NetworkDiagram.layout.Grouping | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 ui.src.react-ftm.components.NetworkDiagram.renderer.GraphRenderer | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 ui.src.react-ftm.components.common.EntityManager | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 29 ui.src.react-ftm.components.common.EdgeCreateDialog | 3 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 ui.src.react-ftm.components.NetworkDiagram.GraphContext | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 ui.src.react-ftm.components.NetworkDiagram.History | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 ui.src.react-ftm.components.NetworkDiagram.layout.Vertex | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 ui.src.components.Timeline | 1 | 1 | 3 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 34 ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||
| 35 ui.src.react-ftm.components.NetworkDiagram.layout.tools.common | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 ui.src.react-ftm.components.NetworkDiagram.renderer.EdgeRenderer | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 ui.src.react-ftm.components.NetworkDiagram.toolbox.Toolbar | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 ui.src.react-ftm.components.NetworkDiagram.utils | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 ui.src.react-ftm.components.NetworkDiagram.layout.tools | 2 | 2 | 2 | 6 |
9→1 aleph.model.alert uses aleph.model.common✕
- Connections
- 1 pair of types, where a type in aleph.model.alert uses a type in aleph.model.common.
- The types involved
aleph.model.alert.Alert→aleph.model.common.DatedModel
- Direction
- aleph.model.alert uses aleph.model.common, so a change to aleph.model.common can break aleph.model.alert, while a change to aleph.model.alert can't break aleph.model.common.
- Position
- Below the diagonal: aleph.model.alert uses a module listed above it, which is the healthy direction.
10→1 aleph.model.bookmark uses aleph.model.common✕
- Connections
- 1 pair of types, where a type in aleph.model.bookmark uses a type in aleph.model.common.
- The types involved
aleph.model.bookmark.Bookmark→aleph.model.common.IdModel
- Direction
- aleph.model.bookmark uses aleph.model.common, so a change to aleph.model.common can break aleph.model.bookmark, while a change to aleph.model.bookmark can't break aleph.model.common.
- Position
- Below the diagonal: aleph.model.bookmark uses a module listed above it, which is the healthy direction.
11→1 aleph.model.collection uses aleph.model.common✕
- Connections
- 2 pairs of types, where a type in aleph.model.collection uses a type in aleph.model.common.
- The types involved
aleph.model.collection.Collection→aleph.model.common.IdModelaleph.model.collection.Collection→aleph.model.common.SoftDeleteModel
- Direction
- aleph.model.collection uses aleph.model.common, so a change to aleph.model.common can break aleph.model.collection, while a change to aleph.model.collection can't break aleph.model.common.
- Position
- Below the diagonal: aleph.model.collection uses a module listed above it, which is the healthy direction.
12→1 aleph.model.document uses aleph.model.common✕
- Connections
- 1 pair of types, where a type in aleph.model.document uses a type in aleph.model.common.
- The types involved
aleph.model.document.Document→aleph.model.common.DatedModel
- Direction
- aleph.model.document uses aleph.model.common, so a change to aleph.model.common can break aleph.model.document, while a change to aleph.model.document can't break aleph.model.common.
- Position
- Below the diagonal: aleph.model.document uses a module listed above it, which is the healthy direction.
13→1 aleph.model.entity uses aleph.model.common✕
- Connections
- 1 pair of types, where a type in aleph.model.entity uses a type in aleph.model.common.
- The types involved
aleph.model.entity.Entity→aleph.model.common.DatedModel
- Direction
- aleph.model.entity uses aleph.model.common, so a change to aleph.model.common can break aleph.model.entity, while a change to aleph.model.entity can't break aleph.model.common.
- Position
- Below the diagonal: aleph.model.entity uses a module listed above it, which is the healthy direction.
14→1 aleph.model.entityset uses aleph.model.common✕
- Connections
- 2 pairs of types, where a type in aleph.model.entityset uses a type in aleph.model.common.
- The types involved
aleph.model.entityset.EntitySet→aleph.model.common.SoftDeleteModelaleph.model.entityset.EntitySetItem→aleph.model.common.SoftDeleteModel
- Direction
- aleph.model.entityset uses aleph.model.common, so a change to aleph.model.common can break aleph.model.entityset, while a change to aleph.model.entityset can't break aleph.model.common.
- Position
- Below the diagonal: aleph.model.entityset uses a module listed above it, which is the healthy direction.
15→3 ui.src.components.Timeline.TimelineChart uses ui.src.components.Timeline.types✕
- Connections
- 3 pairs of types, where a type in ui.src.components.Timeline.TimelineChart uses a type in ui.src.components.Timeline.types.
- The types involved
ui.src.components.Timeline.TimelineChart.TimelineChartGrid→ui.src.components.Timeline.types.TimelineChartZoomLevelui.src.components.Timeline.TimelineChart.TimelineChartLabels→ui.src.components.Timeline.types.TimelineChartZoomLevelui.src.components.Timeline.TimelineChart.util→ui.src.components.Timeline.types.TimelineChartZoomLevel
- Direction
- ui.src.components.Timeline.TimelineChart uses ui.src.components.Timeline.types, so a change to ui.src.components.Timeline.types can break ui.src.components.Timeline.TimelineChart, while a change to ui.src.components.Timeline.TimelineChart can't break ui.src.components.Timeline.types.
- Position
- Below the diagonal: ui.src.components.Timeline.TimelineChart uses a module listed above it, which is the healthy direction.
16→4 ui.src.components.Timeline.util uses ui.src.components.common.Entity✕
- Connections
- 1 pair of types, where a type in ui.src.components.Timeline.util uses a type in ui.src.components.common.Entity.
- The types involved
ui.src.components.Timeline.util.TimelineItem→ui.src.components.common.Entity.Entity
- Direction
- ui.src.components.Timeline.util uses ui.src.components.common.Entity, so a change to ui.src.components.common.Entity can break ui.src.components.Timeline.util, while a change to ui.src.components.Timeline.util can't break ui.src.components.common.Entity.
- Position
- Below the diagonal: ui.src.components.Timeline.util uses a module listed above it, which is the healthy direction.
17→7 ui.src.react-ftm.components.NetworkDiagram.GraphConfig uses ui.src.react-ftm.components.NetworkDiagram.layout.Point✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.GraphConfig uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Point.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.GraphConfig.GraphConfig→ui.src.react-ftm.components.NetworkDiagram.layout.Point.Point
- Direction
- ui.src.react-ftm.components.NetworkDiagram.GraphConfig uses ui.src.react-ftm.components.NetworkDiagram.layout.Point, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Point can break ui.src.react-ftm.components.NetworkDiagram.GraphConfig, while a change to ui.src.react-ftm.components.NetworkDiagram.GraphConfig can't break ui.src.react-ftm.components.NetworkDiagram.layout.Point.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.GraphConfig uses a module listed above it, which is the healthy direction.
18→7 ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle uses ui.src.react-ftm.components.NetworkDiagram.layout.Point✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Point.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle.Rectangle→ui.src.react-ftm.components.NetworkDiagram.layout.Point.Point
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle uses ui.src.react-ftm.components.NetworkDiagram.layout.Point, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Point can break ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle can't break ui.src.react-ftm.components.NetworkDiagram.layout.Point.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle uses a module listed above it, which is the healthy direction.
19→4 ui.src.react-ftm.components.common.types.EntityChanges uses ui.src.components.common.Entity✕
- Connections
- 2 pairs of types, where a type in ui.src.react-ftm.components.common.types.EntityChanges uses a type in ui.src.components.common.Entity.
- The types involved
ui.src.react-ftm.components.common.types.EntityChanges.EntityChangeUpdate→ui.src.components.common.Entity.Entityui.src.react-ftm.components.common.types.EntityChanges.EntityChanges→ui.src.components.common.Entity.Entity
- Direction
- ui.src.react-ftm.components.common.types.EntityChanges uses ui.src.components.common.Entity, so a change to ui.src.components.common.Entity can break ui.src.react-ftm.components.common.types.EntityChanges, while a change to ui.src.react-ftm.components.common.types.EntityChanges can't break ui.src.components.common.Entity.
- Position
- Below the diagonal: ui.src.react-ftm.components.common.types.EntityChanges uses a module listed above it, which is the healthy direction.
20→4 ui.src.react-ftm.editors.PropertyEditor uses ui.src.components.common.Entity✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.editors.PropertyEditor uses a type in ui.src.components.common.Entity.
- The types involved
ui.src.react-ftm.editors.PropertyEditor.IPropertyEditorProps→ui.src.components.common.Entity.Entity
- Direction
- ui.src.react-ftm.editors.PropertyEditor uses ui.src.components.common.Entity, so a change to ui.src.components.common.Entity can break ui.src.react-ftm.editors.PropertyEditor, while a change to ui.src.react-ftm.editors.PropertyEditor can't break ui.src.components.common.Entity.
- Position
- Below the diagonal: ui.src.react-ftm.editors.PropertyEditor uses a module listed above it, which is the healthy direction.
20→5 ui.src.react-ftm.editors.PropertyEditor uses ui.src.components.common.Property✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.editors.PropertyEditor uses a type in ui.src.components.common.Property.
- The types involved
ui.src.react-ftm.editors.PropertyEditor.IPropertyEditorProps→ui.src.components.common.Property.Property
- Direction
- ui.src.react-ftm.editors.PropertyEditor uses ui.src.components.common.Property, so a change to ui.src.components.common.Property can break ui.src.react-ftm.editors.PropertyEditor, while a change to ui.src.react-ftm.editors.PropertyEditor can't break ui.src.components.common.Property.
- Position
- Below the diagonal: ui.src.react-ftm.editors.PropertyEditor uses a module listed above it, which is the healthy direction.
21→4 ui.src.react-ftm.types.EdgeType uses ui.src.components.common.Entity✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.types.EdgeType uses a type in ui.src.components.common.Entity.
- The types involved
ui.src.react-ftm.types.EdgeType.EdgeType→ui.src.components.common.Entity.Entity
- Direction
- ui.src.react-ftm.types.EdgeType uses ui.src.components.common.Entity, so a change to ui.src.components.common.Entity can break ui.src.react-ftm.types.EdgeType, while a change to ui.src.react-ftm.types.EdgeType can't break ui.src.components.common.Entity.
- Position
- Below the diagonal: ui.src.react-ftm.types.EdgeType uses a module listed above it, which is the healthy direction.
21→5 ui.src.react-ftm.types.EdgeType uses ui.src.components.common.Property✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.types.EdgeType uses a type in ui.src.components.common.Property.
- The types involved
ui.src.react-ftm.types.EdgeType.EdgeType→ui.src.components.common.Property.Property
- Direction
- ui.src.react-ftm.types.EdgeType uses ui.src.components.common.Property, so a change to ui.src.components.common.Property can break ui.src.react-ftm.types.EdgeType, while a change to ui.src.react-ftm.types.EdgeType can't break ui.src.components.common.Property.
- Position
- Below the diagonal: ui.src.react-ftm.types.EdgeType uses a module listed above it, which is the healthy direction.
21→6 ui.src.react-ftm.types.EdgeType uses ui.src.components.common.Schema✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.types.EdgeType uses a type in ui.src.components.common.Schema.
- The types involved
ui.src.react-ftm.types.EdgeType.EdgeType→ui.src.components.common.Schema.Schema
- Direction
- ui.src.react-ftm.types.EdgeType uses ui.src.components.common.Schema, so a change to ui.src.components.common.Schema can break ui.src.react-ftm.types.EdgeType, while a change to ui.src.react-ftm.types.EdgeType can't break ui.src.components.common.Schema.
- Position
- Below the diagonal: ui.src.react-ftm.types.EdgeType uses a module listed above it, which is the healthy direction.
22→4 ui.src.react-ftm.utils uses ui.src.components.common.Entity✕
- Connections
- 3 pairs of types, where a type in ui.src.react-ftm.utils uses a type in ui.src.components.common.Entity.
- The types involved
ui.src.react-ftm.utils.isRtl→ui.src.components.common.Entity.Entityui.src.react-ftm.utils.sortEntities→ui.src.components.common.Entity.Entityui.src.react-ftm.utils.validate→ui.src.components.common.Entity.Entity
- Direction
- ui.src.react-ftm.utils uses ui.src.components.common.Entity, so a change to ui.src.components.common.Entity can break ui.src.react-ftm.utils, while a change to ui.src.react-ftm.utils can't break ui.src.components.common.Entity.
- Position
- Below the diagonal: ui.src.react-ftm.utils uses a module listed above it, which is the healthy direction.
22→5 ui.src.react-ftm.utils uses ui.src.components.common.Property✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.utils uses a type in ui.src.components.common.Property.
- The types involved
ui.src.react-ftm.utils.validate→ui.src.components.common.Property.Property
- Direction
- ui.src.react-ftm.utils uses ui.src.components.common.Property, so a change to ui.src.components.common.Property can break ui.src.react-ftm.utils, while a change to ui.src.react-ftm.utils can't break ui.src.components.common.Property.
- Position
- Below the diagonal: ui.src.react-ftm.utils uses a module listed above it, which is the healthy direction.
23→7 ui.src.react-ftm.components.NetworkDiagram.Viewport uses ui.src.react-ftm.components.NetworkDiagram.layout.Point✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.Viewport uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Point.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.Viewport.Viewport→ui.src.react-ftm.components.NetworkDiagram.layout.Point.Point
- Direction
- ui.src.react-ftm.components.NetworkDiagram.Viewport uses ui.src.react-ftm.components.NetworkDiagram.layout.Point, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Point can break ui.src.react-ftm.components.NetworkDiagram.Viewport, while a change to ui.src.react-ftm.components.NetworkDiagram.Viewport can't break ui.src.react-ftm.components.NetworkDiagram.layout.Point.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.Viewport uses a module listed above it, which is the healthy direction.
23→17 ui.src.react-ftm.components.NetworkDiagram.Viewport uses ui.src.react-ftm.components.NetworkDiagram.GraphConfig✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.Viewport uses a type in ui.src.react-ftm.components.NetworkDiagram.GraphConfig.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.Viewport.Viewport→ui.src.react-ftm.components.NetworkDiagram.GraphConfig.GraphConfig
- Direction
- ui.src.react-ftm.components.NetworkDiagram.Viewport uses ui.src.react-ftm.components.NetworkDiagram.GraphConfig, so a change to ui.src.react-ftm.components.NetworkDiagram.GraphConfig can break ui.src.react-ftm.components.NetworkDiagram.Viewport, while a change to ui.src.react-ftm.components.NetworkDiagram.Viewport can't break ui.src.react-ftm.components.NetworkDiagram.GraphConfig.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.Viewport uses a module listed above it, which is the healthy direction.
23→18 ui.src.react-ftm.components.NetworkDiagram.Viewport uses ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.Viewport uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.Viewport.Viewport→ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle.Rectangle
- Direction
- ui.src.react-ftm.components.NetworkDiagram.Viewport uses ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle can break ui.src.react-ftm.components.NetworkDiagram.Viewport, while a change to ui.src.react-ftm.components.NetworkDiagram.Viewport can't break ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.Viewport uses a module listed above it, which is the healthy direction.
24→4 ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses ui.src.components.common.Entity✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses a type in ui.src.components.common.Entity.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.Edge.Edge→ui.src.components.common.Entity.Entity
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses ui.src.components.common.Entity, so a change to ui.src.components.common.Entity can break ui.src.react-ftm.components.NetworkDiagram.layout.Edge, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.Edge can't break ui.src.components.common.Entity.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses a module listed above it, which is the healthy direction.
24→5 ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses ui.src.components.common.Property✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses a type in ui.src.components.common.Property.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.Edge.Edge→ui.src.components.common.Property.Property
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses ui.src.components.common.Property, so a change to ui.src.components.common.Property can break ui.src.react-ftm.components.NetworkDiagram.layout.Edge, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.Edge can't break ui.src.components.common.Property.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses a module listed above it, which is the healthy direction.
24→7 ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses ui.src.react-ftm.components.NetworkDiagram.layout.Point✕
- Connections
- 2 pairs of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Point.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.Edge.Edge→ui.src.react-ftm.components.NetworkDiagram.layout.Point.Pointui.src.react-ftm.components.NetworkDiagram.layout.Edge.IEdgeData→ui.src.react-ftm.components.NetworkDiagram.layout.Point.IPointData
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses ui.src.react-ftm.components.NetworkDiagram.layout.Point, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Point can break ui.src.react-ftm.components.NetworkDiagram.layout.Edge, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.Edge can't break ui.src.react-ftm.components.NetworkDiagram.layout.Point.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses a module listed above it, which is the healthy direction.
24→18 ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.Edge.Edge→ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle.Rectangle
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle can break ui.src.react-ftm.components.NetworkDiagram.layout.Edge, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.Edge can't break ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses a module listed above it, which is the healthy direction.
24→28 ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout part of a loop✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.Edge.Edge→ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.GraphLayout
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout can break ui.src.react-ftm.components.NetworkDiagram.layout.Edge, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.Edge can't break ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→32 ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex part of a loop✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.Edge.Edge→ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.Vertex
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.Edge uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Vertex can break ui.src.react-ftm.components.NetworkDiagram.layout.Edge, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.Edge can't break ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- 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→18 ui.src.react-ftm.components.NetworkDiagram.layout.Grouping uses ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.Grouping uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.Grouping.Grouping→ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle.Rectangle
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.Grouping uses ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle can break ui.src.react-ftm.components.NetworkDiagram.layout.Grouping, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.Grouping can't break ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.Grouping uses a module listed above it, which is the healthy direction.
25→28 ui.src.react-ftm.components.NetworkDiagram.layout.Grouping uses ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout part of a loop✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.Grouping uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.Grouping.Grouping→ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.GraphLayout
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.Grouping uses ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout can break ui.src.react-ftm.components.NetworkDiagram.layout.Grouping, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.Grouping can't break ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.
- 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→32 ui.src.react-ftm.components.NetworkDiagram.layout.Grouping uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex part of a loop✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.Grouping uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.Grouping.Grouping→ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.Vertex
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.Grouping uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Vertex can break ui.src.react-ftm.components.NetworkDiagram.layout.Grouping, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.Grouping can't break ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→7 ui.src.react-ftm.components.NetworkDiagram.renderer.GraphRenderer uses ui.src.react-ftm.components.NetworkDiagram.layout.Point✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.renderer.GraphRenderer uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Point.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.renderer.GraphRenderer.GraphRenderer→ui.src.react-ftm.components.NetworkDiagram.layout.Point.Point
- Direction
- ui.src.react-ftm.components.NetworkDiagram.renderer.GraphRenderer uses ui.src.react-ftm.components.NetworkDiagram.layout.Point, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Point can break ui.src.react-ftm.components.NetworkDiagram.renderer.GraphRenderer, while a change to ui.src.react-ftm.components.NetworkDiagram.renderer.GraphRenderer can't break ui.src.react-ftm.components.NetworkDiagram.layout.Point.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.renderer.GraphRenderer uses a module listed above it, which is the healthy direction.
26→18 ui.src.react-ftm.components.NetworkDiagram.renderer.GraphRenderer uses ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.renderer.GraphRenderer uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.renderer.GraphRenderer.GraphRenderer→ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle.Rectangle
- Direction
- ui.src.react-ftm.components.NetworkDiagram.renderer.GraphRenderer uses ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle can break ui.src.react-ftm.components.NetworkDiagram.renderer.GraphRenderer, while a change to ui.src.react-ftm.components.NetworkDiagram.renderer.GraphRenderer can't break ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.renderer.GraphRenderer uses a module listed above it, which is the healthy direction.
27→4 ui.src.react-ftm.components.common.EntityManager uses ui.src.components.common.Entity✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.common.EntityManager uses a type in ui.src.components.common.Entity.
- The types involved
ui.src.react-ftm.components.common.EntityManager.EntityManager→ui.src.components.common.Entity.Entity
- Direction
- ui.src.react-ftm.components.common.EntityManager uses ui.src.components.common.Entity, so a change to ui.src.components.common.Entity can break ui.src.react-ftm.components.common.EntityManager, while a change to ui.src.react-ftm.components.common.EntityManager can't break ui.src.components.common.Entity.
- Position
- Below the diagonal: ui.src.react-ftm.components.common.EntityManager uses a module listed above it, which is the healthy direction.
27→6 ui.src.react-ftm.components.common.EntityManager uses ui.src.components.common.Schema✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.common.EntityManager uses a type in ui.src.components.common.Schema.
- The types involved
ui.src.react-ftm.components.common.EntityManager.EntityManager→ui.src.components.common.Schema.Schema
- Direction
- ui.src.react-ftm.components.common.EntityManager uses ui.src.components.common.Schema, so a change to ui.src.components.common.Schema can break ui.src.react-ftm.components.common.EntityManager, while a change to ui.src.react-ftm.components.common.EntityManager can't break ui.src.components.common.Schema.
- Position
- Below the diagonal: ui.src.react-ftm.components.common.EntityManager uses a module listed above it, which is the healthy direction.
27→19 ui.src.react-ftm.components.common.EntityManager uses ui.src.react-ftm.components.common.types.EntityChanges✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.common.EntityManager uses a type in ui.src.react-ftm.components.common.types.EntityChanges.
- The types involved
ui.src.react-ftm.components.common.EntityManager.EntityManager→ui.src.react-ftm.components.common.types.EntityChanges.EntityChanges
- Direction
- ui.src.react-ftm.components.common.EntityManager uses ui.src.react-ftm.components.common.types.EntityChanges, so a change to ui.src.react-ftm.components.common.types.EntityChanges can break ui.src.react-ftm.components.common.EntityManager, while a change to ui.src.react-ftm.components.common.EntityManager can't break ui.src.react-ftm.components.common.types.EntityChanges.
- Position
- Below the diagonal: ui.src.react-ftm.components.common.EntityManager uses a module listed above it, which is the healthy direction.
28→4 ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses ui.src.components.common.Entity✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses a type in ui.src.components.common.Entity.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.GraphLayout→ui.src.components.common.Entity.Entity
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses ui.src.components.common.Entity, so a change to ui.src.components.common.Entity can break ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout can't break ui.src.components.common.Entity.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses a module listed above it, which is the healthy direction.
28→7 ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses ui.src.react-ftm.components.NetworkDiagram.layout.Point✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Point.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.GraphLayout→ui.src.react-ftm.components.NetworkDiagram.layout.Point.Point
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses ui.src.react-ftm.components.NetworkDiagram.layout.Point, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Point can break ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout can't break ui.src.react-ftm.components.NetworkDiagram.layout.Point.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses a module listed above it, which is the healthy direction.
28→8 ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses ui.src.react-ftm.components.NetworkDiagram.layout.Settings✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Settings.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.IGraphLayoutData→ui.src.react-ftm.components.NetworkDiagram.layout.Settings.ISettingsData
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses ui.src.react-ftm.components.NetworkDiagram.layout.Settings, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Settings can break ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout can't break ui.src.react-ftm.components.NetworkDiagram.layout.Settings.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses a module listed above it, which is the healthy direction.
28→17 ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses ui.src.react-ftm.components.NetworkDiagram.GraphConfig✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses a type in ui.src.react-ftm.components.NetworkDiagram.GraphConfig.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.GraphLayout→ui.src.react-ftm.components.NetworkDiagram.GraphConfig.GraphConfig
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses ui.src.react-ftm.components.NetworkDiagram.GraphConfig, so a change to ui.src.react-ftm.components.NetworkDiagram.GraphConfig can break ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout can't break ui.src.react-ftm.components.NetworkDiagram.GraphConfig.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses a module listed above it, which is the healthy direction.
28→18 ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.GraphLayout→ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle.Rectangle
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle can break ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout can't break ui.src.react-ftm.components.NetworkDiagram.layout.Rectangle.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses a module listed above it, which is the healthy direction.
28→24 ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses ui.src.react-ftm.components.NetworkDiagram.layout.Edge✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Edge.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.GraphLayout→ui.src.react-ftm.components.NetworkDiagram.layout.Edge.Edge
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses ui.src.react-ftm.components.NetworkDiagram.layout.Edge, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Edge can break ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout can't break ui.src.react-ftm.components.NetworkDiagram.layout.Edge.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses a module listed above it, which is the healthy direction.
28→25 ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses ui.src.react-ftm.components.NetworkDiagram.layout.Grouping✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Grouping.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.GraphLayout→ui.src.react-ftm.components.NetworkDiagram.layout.Grouping.Grouping
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses ui.src.react-ftm.components.NetworkDiagram.layout.Grouping, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Grouping can break ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout can't break ui.src.react-ftm.components.NetworkDiagram.layout.Grouping.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses a module listed above it, which is the healthy direction.
28→32 ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex part of a loop✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.GraphLayout→ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.Vertex
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Vertex can break ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout can't break ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- 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.
29→4 ui.src.react-ftm.components.common.EdgeCreateDialog uses ui.src.components.common.Entity✕
- Connections
- 3 pairs of types, where a type in ui.src.react-ftm.components.common.EdgeCreateDialog uses a type in ui.src.components.common.Entity.
- The types involved
ui.src.react-ftm.components.common.EdgeCreateDialog.IEdgeCreateDialogProps→ui.src.components.common.Entity.Entityui.src.react-ftm.components.common.EdgeCreateDialog.IEdgeCreateDialogState→ui.src.components.common.Entity.Entityui.src.react-ftm.components.common.EdgeCreateDialog.UnwrappedEdgeCreateDialog→ui.src.components.common.Entity.Entity
- Direction
- ui.src.react-ftm.components.common.EdgeCreateDialog uses ui.src.components.common.Entity, so a change to ui.src.components.common.Entity can break ui.src.react-ftm.components.common.EdgeCreateDialog, while a change to ui.src.react-ftm.components.common.EdgeCreateDialog can't break ui.src.components.common.Entity.
- Position
- Below the diagonal: ui.src.react-ftm.components.common.EdgeCreateDialog uses a module listed above it, which is the healthy direction.
29→21 ui.src.react-ftm.components.common.EdgeCreateDialog uses ui.src.react-ftm.types.EdgeType✕
- Connections
- 2 pairs of types, where a type in ui.src.react-ftm.components.common.EdgeCreateDialog uses a type in ui.src.react-ftm.types.EdgeType.
- The types involved
ui.src.react-ftm.components.common.EdgeCreateDialog.IEdgeCreateDialogState→ui.src.react-ftm.types.EdgeType.EdgeTypeui.src.react-ftm.components.common.EdgeCreateDialog.UnwrappedEdgeCreateDialog→ui.src.react-ftm.types.EdgeType.EdgeType
- Direction
- ui.src.react-ftm.components.common.EdgeCreateDialog uses ui.src.react-ftm.types.EdgeType, so a change to ui.src.react-ftm.types.EdgeType can break ui.src.react-ftm.components.common.EdgeCreateDialog, while a change to ui.src.react-ftm.components.common.EdgeCreateDialog can't break ui.src.react-ftm.types.EdgeType.
- Position
- Below the diagonal: ui.src.react-ftm.components.common.EdgeCreateDialog uses a module listed above it, which is the healthy direction.
29→27 ui.src.react-ftm.components.common.EdgeCreateDialog uses ui.src.react-ftm.components.common.EntityManager✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.common.EdgeCreateDialog uses a type in ui.src.react-ftm.components.common.EntityManager.
- The types involved
ui.src.react-ftm.components.common.EdgeCreateDialog.IEdgeCreateDialogProps→ui.src.react-ftm.components.common.EntityManager.EntityManager
- Direction
- ui.src.react-ftm.components.common.EdgeCreateDialog uses ui.src.react-ftm.components.common.EntityManager, so a change to ui.src.react-ftm.components.common.EntityManager can break ui.src.react-ftm.components.common.EdgeCreateDialog, while a change to ui.src.react-ftm.components.common.EdgeCreateDialog can't break ui.src.react-ftm.components.common.EntityManager.
- Position
- Below the diagonal: ui.src.react-ftm.components.common.EdgeCreateDialog uses a module listed above it, which is the healthy direction.
30→23 ui.src.react-ftm.components.NetworkDiagram.GraphContext uses ui.src.react-ftm.components.NetworkDiagram.Viewport✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.GraphContext uses a type in ui.src.react-ftm.components.NetworkDiagram.Viewport.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.GraphContext.IGraphContext→ui.src.react-ftm.components.NetworkDiagram.Viewport.Viewport
- Direction
- ui.src.react-ftm.components.NetworkDiagram.GraphContext uses ui.src.react-ftm.components.NetworkDiagram.Viewport, so a change to ui.src.react-ftm.components.NetworkDiagram.Viewport can break ui.src.react-ftm.components.NetworkDiagram.GraphContext, while a change to ui.src.react-ftm.components.NetworkDiagram.GraphContext can't break ui.src.react-ftm.components.NetworkDiagram.Viewport.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.GraphContext uses a module listed above it, which is the healthy direction.
30→27 ui.src.react-ftm.components.NetworkDiagram.GraphContext uses ui.src.react-ftm.components.common.EntityManager✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.GraphContext uses a type in ui.src.react-ftm.components.common.EntityManager.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.GraphContext.IGraphContext→ui.src.react-ftm.components.common.EntityManager.EntityManager
- Direction
- ui.src.react-ftm.components.NetworkDiagram.GraphContext uses ui.src.react-ftm.components.common.EntityManager, so a change to ui.src.react-ftm.components.common.EntityManager can break ui.src.react-ftm.components.NetworkDiagram.GraphContext, while a change to ui.src.react-ftm.components.NetworkDiagram.GraphContext can't break ui.src.react-ftm.components.common.EntityManager.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.GraphContext uses a module listed above it, which is the healthy direction.
30→28 ui.src.react-ftm.components.NetworkDiagram.GraphContext uses ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.GraphContext uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.GraphContext.IGraphContext→ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.GraphLayout
- Direction
- ui.src.react-ftm.components.NetworkDiagram.GraphContext uses ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout can break ui.src.react-ftm.components.NetworkDiagram.GraphContext, while a change to ui.src.react-ftm.components.NetworkDiagram.GraphContext can't break ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.GraphContext uses a module listed above it, which is the healthy direction.
31→19 ui.src.react-ftm.components.NetworkDiagram.History uses ui.src.react-ftm.components.common.types.EntityChanges✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.History uses a type in ui.src.react-ftm.components.common.types.EntityChanges.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.History.IHistoryObject→ui.src.react-ftm.components.common.types.EntityChanges.EntityChanges
- Direction
- ui.src.react-ftm.components.NetworkDiagram.History uses ui.src.react-ftm.components.common.types.EntityChanges, so a change to ui.src.react-ftm.components.common.types.EntityChanges can break ui.src.react-ftm.components.NetworkDiagram.History, while a change to ui.src.react-ftm.components.NetworkDiagram.History can't break ui.src.react-ftm.components.common.types.EntityChanges.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.History uses a module listed above it, which is the healthy direction.
31→28 ui.src.react-ftm.components.NetworkDiagram.History uses ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.History uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.History.IHistoryObject→ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.IGraphLayoutData
- Direction
- ui.src.react-ftm.components.NetworkDiagram.History uses ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout can break ui.src.react-ftm.components.NetworkDiagram.History, while a change to ui.src.react-ftm.components.NetworkDiagram.History can't break ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.History uses a module listed above it, which is the healthy direction.
32→4 ui.src.react-ftm.components.NetworkDiagram.layout.Vertex uses ui.src.components.common.Entity✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.Vertex uses a type in ui.src.components.common.Entity.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.Vertex→ui.src.components.common.Entity.Entity
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.Vertex uses ui.src.components.common.Entity, so a change to ui.src.components.common.Entity can break ui.src.react-ftm.components.NetworkDiagram.layout.Vertex, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.Vertex can't break ui.src.components.common.Entity.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.Vertex uses a module listed above it, which is the healthy direction.
32→5 ui.src.react-ftm.components.NetworkDiagram.layout.Vertex uses ui.src.components.common.Property✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.Vertex uses a type in ui.src.components.common.Property.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.Vertex→ui.src.components.common.Property.Property
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.Vertex uses ui.src.components.common.Property, so a change to ui.src.components.common.Property can break ui.src.react-ftm.components.NetworkDiagram.layout.Vertex, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.Vertex can't break ui.src.components.common.Property.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.Vertex uses a module listed above it, which is the healthy direction.
32→7 ui.src.react-ftm.components.NetworkDiagram.layout.Vertex uses ui.src.react-ftm.components.NetworkDiagram.layout.Point✕
- Connections
- 2 pairs of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.Vertex uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Point.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.IVertexData→ui.src.react-ftm.components.NetworkDiagram.layout.Point.IPointDataui.src.react-ftm.components.NetworkDiagram.layout.Vertex.Vertex→ui.src.react-ftm.components.NetworkDiagram.layout.Point.Point
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.Vertex uses ui.src.react-ftm.components.NetworkDiagram.layout.Point, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Point can break ui.src.react-ftm.components.NetworkDiagram.layout.Vertex, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.Vertex can't break ui.src.react-ftm.components.NetworkDiagram.layout.Point.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.Vertex uses a module listed above it, which is the healthy direction.
32→28 ui.src.react-ftm.components.NetworkDiagram.layout.Vertex uses ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.Vertex uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.Vertex→ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.GraphLayout
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.Vertex uses ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout can break ui.src.react-ftm.components.NetworkDiagram.layout.Vertex, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.Vertex can't break ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.Vertex uses a module listed above it, which is the healthy direction.
33→2 ui.src.components.Timeline uses ui.src.components.Settings.ApiKeySettings✕
- Connections
- 1 pair of types, where a type in ui.src.components.Timeline uses a type in ui.src.components.Settings.ApiKeySettings.
- The types involved
ui.src.components.Timeline.state→ui.src.components.Settings.ApiKeySettings.Action
- Direction
- ui.src.components.Timeline uses ui.src.components.Settings.ApiKeySettings, so a change to ui.src.components.Settings.ApiKeySettings can break ui.src.components.Timeline, while a change to ui.src.components.Timeline can't break ui.src.components.Settings.ApiKeySettings.
- Position
- Below the diagonal: ui.src.components.Timeline uses a module listed above it, which is the healthy direction.
33→3 ui.src.components.Timeline uses ui.src.components.Timeline.types✕
- Connections
- 1 pair of types, where a type in ui.src.components.Timeline uses a type in ui.src.components.Timeline.types.
- The types involved
ui.src.components.Timeline.state→ui.src.components.Timeline.types.TimelineChartZoomLevel
- Direction
- ui.src.components.Timeline uses ui.src.components.Timeline.types, so a change to ui.src.components.Timeline.types can break ui.src.components.Timeline, while a change to ui.src.components.Timeline can't break ui.src.components.Timeline.types.
- Position
- Below the diagonal: ui.src.components.Timeline uses a module listed above it, which is the healthy direction.
33→4 ui.src.components.Timeline uses ui.src.components.common.Entity✕
- Connections
- 3 pairs of types, where a type in ui.src.components.Timeline uses a type in ui.src.components.common.Entity.
- The types involved
ui.src.components.Timeline.TimelineItemCaption→ui.src.components.common.Entity.Entityui.src.components.Timeline.state→ui.src.components.common.Entity.Entityui.src.components.Timeline.util→ui.src.components.common.Entity.Entity
- Direction
- ui.src.components.Timeline uses ui.src.components.common.Entity, so a change to ui.src.components.common.Entity can break ui.src.components.Timeline, while a change to ui.src.components.Timeline can't break ui.src.components.common.Entity.
- Position
- Below the diagonal: ui.src.components.Timeline uses a module listed above it, which is the healthy direction.
33→6 ui.src.components.Timeline uses ui.src.components.common.Schema✕
- Connections
- 3 pairs of types, where a type in ui.src.components.Timeline uses a type in ui.src.components.common.Schema.
- The types involved
ui.src.components.Timeline.EntityViewerProperties→ui.src.components.common.Schema.Schemaui.src.components.Timeline.TimelineItemCreateForm→ui.src.components.common.Schema.Schemaui.src.components.Timeline.util→ui.src.components.common.Schema.Schema
- Direction
- ui.src.components.Timeline uses ui.src.components.common.Schema, so a change to ui.src.components.common.Schema can break ui.src.components.Timeline, while a change to ui.src.components.Timeline can't break ui.src.components.common.Schema.
- Position
- Below the diagonal: ui.src.components.Timeline uses a module listed above it, which is the healthy direction.
33→16 ui.src.components.Timeline uses ui.src.components.Timeline.util✕
- Connections
- 2 pairs of types, where a type in ui.src.components.Timeline uses a type in ui.src.components.Timeline.util.
- The types involved
ui.src.components.Timeline.state→ui.src.components.Timeline.util.TimelineItemui.src.components.Timeline.util→ui.src.components.Timeline.util.TimelineItem
- Direction
- ui.src.components.Timeline uses ui.src.components.Timeline.util, so a change to ui.src.components.Timeline.util can break ui.src.components.Timeline, while a change to ui.src.components.Timeline can't break ui.src.components.Timeline.util.
- Position
- Below the diagonal: ui.src.components.Timeline uses a module listed above it, which is the healthy direction.
33→32 ui.src.components.Timeline uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex✕
- Connections
- 1 pair of types, where a type in ui.src.components.Timeline uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- The types involved
ui.src.components.Timeline.util→ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.Vertex
- Direction
- ui.src.components.Timeline uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Vertex can break ui.src.components.Timeline, while a change to ui.src.components.Timeline can't break ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- Position
- Below the diagonal: ui.src.components.Timeline uses a module listed above it, which is the healthy direction.
34→4 ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.components.common.Entity✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a type in ui.src.components.common.Entity.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram.NetworkDiagramBase→ui.src.components.common.Entity.Entity
- Direction
- ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.components.common.Entity, so a change to ui.src.components.common.Entity can break ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram, while a change to ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram can't break ui.src.components.common.Entity.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a module listed above it, which is the healthy direction.
34→7 ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.components.NetworkDiagram.layout.Point✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Point.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram.NetworkDiagramBase→ui.src.react-ftm.components.NetworkDiagram.layout.Point.Point
- Direction
- ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.components.NetworkDiagram.layout.Point, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Point can break ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram, while a change to ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram can't break ui.src.react-ftm.components.NetworkDiagram.layout.Point.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a module listed above it, which is the healthy direction.
34→17 ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.components.NetworkDiagram.GraphConfig✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a type in ui.src.react-ftm.components.NetworkDiagram.GraphConfig.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram.INetworkDiagramProps→ui.src.react-ftm.components.NetworkDiagram.GraphConfig.GraphConfig
- Direction
- ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.components.NetworkDiagram.GraphConfig, so a change to ui.src.react-ftm.components.NetworkDiagram.GraphConfig can break ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram, while a change to ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram can't break ui.src.react-ftm.components.NetworkDiagram.GraphConfig.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a module listed above it, which is the healthy direction.
34→19 ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.components.common.types.EntityChanges✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a type in ui.src.react-ftm.components.common.types.EntityChanges.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram.NetworkDiagramBase→ui.src.react-ftm.components.common.types.EntityChanges.EntityChanges
- Direction
- ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.components.common.types.EntityChanges, so a change to ui.src.react-ftm.components.common.types.EntityChanges can break ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram, while a change to ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram can't break ui.src.react-ftm.components.common.types.EntityChanges.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a module listed above it, which is the healthy direction.
34→21 ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.types.EdgeType✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a type in ui.src.react-ftm.types.EdgeType.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram.NetworkDiagramBase→ui.src.react-ftm.types.EdgeType.EdgeType
- Direction
- ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.types.EdgeType, so a change to ui.src.react-ftm.types.EdgeType can break ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram, while a change to ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram can't break ui.src.react-ftm.types.EdgeType.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a module listed above it, which is the healthy direction.
34→23 ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.components.NetworkDiagram.Viewport✕
- Connections
- 2 pairs of types, where a type in ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a type in ui.src.react-ftm.components.NetworkDiagram.Viewport.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram.INetworkDiagramProps→ui.src.react-ftm.components.NetworkDiagram.Viewport.Viewportui.src.react-ftm.components.NetworkDiagram.NetworkDiagram.NetworkDiagramBase→ui.src.react-ftm.components.NetworkDiagram.Viewport.Viewport
- Direction
- ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.components.NetworkDiagram.Viewport, so a change to ui.src.react-ftm.components.NetworkDiagram.Viewport can break ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram, while a change to ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram can't break ui.src.react-ftm.components.NetworkDiagram.Viewport.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a module listed above it, which is the healthy direction.
34→27 ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.components.common.EntityManager✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a type in ui.src.react-ftm.components.common.EntityManager.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram.INetworkDiagramProps→ui.src.react-ftm.components.common.EntityManager.EntityManager
- Direction
- ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.components.common.EntityManager, so a change to ui.src.react-ftm.components.common.EntityManager can break ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram, while a change to ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram can't break ui.src.react-ftm.components.common.EntityManager.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a module listed above it, which is the healthy direction.
34→28 ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout✕
- Connections
- 2 pairs of types, where a type in ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram.INetworkDiagramProps→ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.GraphLayoutui.src.react-ftm.components.NetworkDiagram.NetworkDiagram.NetworkDiagramBase→ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.GraphLayout
- Direction
- ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout can break ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram, while a change to ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram can't break ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a module listed above it, which is the healthy direction.
34→31 ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.components.NetworkDiagram.History✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a type in ui.src.react-ftm.components.NetworkDiagram.History.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram.NetworkDiagramBase→ui.src.react-ftm.components.NetworkDiagram.History.History
- Direction
- ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.components.NetworkDiagram.History, so a change to ui.src.react-ftm.components.NetworkDiagram.History can break ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram, while a change to ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram can't break ui.src.react-ftm.components.NetworkDiagram.History.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a module listed above it, which is the healthy direction.
34→32 ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram.NetworkDiagramBase→ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.Vertex
- Direction
- ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Vertex can break ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram, while a change to ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram can't break ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.NetworkDiagram uses a module listed above it, which is the healthy direction.
35→24 ui.src.react-ftm.components.NetworkDiagram.layout.tools.common uses ui.src.react-ftm.components.NetworkDiagram.layout.Edge✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.tools.common uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Edge.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.tools.common.IPositioningProps→ui.src.react-ftm.components.NetworkDiagram.layout.Edge.Edge
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.tools.common uses ui.src.react-ftm.components.NetworkDiagram.layout.Edge, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Edge can break ui.src.react-ftm.components.NetworkDiagram.layout.tools.common, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.tools.common can't break ui.src.react-ftm.components.NetworkDiagram.layout.Edge.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.tools.common uses a module listed above it, which is the healthy direction.
35→25 ui.src.react-ftm.components.NetworkDiagram.layout.tools.common uses ui.src.react-ftm.components.NetworkDiagram.layout.Grouping✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.tools.common uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Grouping.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.tools.common.IPositioningProps→ui.src.react-ftm.components.NetworkDiagram.layout.Grouping.Grouping
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.tools.common uses ui.src.react-ftm.components.NetworkDiagram.layout.Grouping, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Grouping can break ui.src.react-ftm.components.NetworkDiagram.layout.tools.common, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.tools.common can't break ui.src.react-ftm.components.NetworkDiagram.layout.Grouping.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.tools.common uses a module listed above it, which is the healthy direction.
35→32 ui.src.react-ftm.components.NetworkDiagram.layout.tools.common uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.tools.common uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.tools.common.IPositioningProps→ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.Vertex
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.tools.common uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Vertex can break ui.src.react-ftm.components.NetworkDiagram.layout.tools.common, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.tools.common can't break ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.tools.common uses a module listed above it, which is the healthy direction.
36→24 ui.src.react-ftm.components.NetworkDiagram.renderer.EdgeRenderer uses ui.src.react-ftm.components.NetworkDiagram.layout.Edge✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.renderer.EdgeRenderer uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Edge.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.renderer.EdgeRenderer.IEdgeRendererProps→ui.src.react-ftm.components.NetworkDiagram.layout.Edge.Edge
- Direction
- ui.src.react-ftm.components.NetworkDiagram.renderer.EdgeRenderer uses ui.src.react-ftm.components.NetworkDiagram.layout.Edge, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Edge can break ui.src.react-ftm.components.NetworkDiagram.renderer.EdgeRenderer, while a change to ui.src.react-ftm.components.NetworkDiagram.renderer.EdgeRenderer can't break ui.src.react-ftm.components.NetworkDiagram.layout.Edge.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.renderer.EdgeRenderer uses a module listed above it, which is the healthy direction.
36→32 ui.src.react-ftm.components.NetworkDiagram.renderer.EdgeRenderer uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.renderer.EdgeRenderer uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.renderer.EdgeRenderer.IEdgeRendererProps→ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.Vertex
- Direction
- ui.src.react-ftm.components.NetworkDiagram.renderer.EdgeRenderer uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Vertex can break ui.src.react-ftm.components.NetworkDiagram.renderer.EdgeRenderer, while a change to ui.src.react-ftm.components.NetworkDiagram.renderer.EdgeRenderer can't break ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.renderer.EdgeRenderer uses a module listed above it, which is the healthy direction.
37→4 ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar uses ui.src.components.common.Entity✕
- Connections
- 2 pairs of types, where a type in ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar uses a type in ui.src.components.common.Entity.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar.ISidebarProps→ui.src.components.common.Entity.Entityui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar.Sidebar→ui.src.components.common.Entity.Entity
- Direction
- ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar uses ui.src.components.common.Entity, so a change to ui.src.components.common.Entity can break ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar, while a change to ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar can't break ui.src.components.common.Entity.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar uses a module listed above it, which is the healthy direction.
37→25 ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar uses ui.src.react-ftm.components.NetworkDiagram.layout.Grouping✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Grouping.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar.Sidebar→ui.src.react-ftm.components.NetworkDiagram.layout.Grouping.Grouping
- Direction
- ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar uses ui.src.react-ftm.components.NetworkDiagram.layout.Grouping, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Grouping can break ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar, while a change to ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar can't break ui.src.react-ftm.components.NetworkDiagram.layout.Grouping.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar uses a module listed above it, which is the healthy direction.
37→32 ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar.Sidebar→ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.Vertex
- Direction
- ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Vertex can break ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar, while a change to ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar can't break ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.toolbox.Sidebar uses a module listed above it, which is the healthy direction.
38→31 ui.src.react-ftm.components.NetworkDiagram.toolbox.Toolbar uses ui.src.react-ftm.components.NetworkDiagram.History✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.toolbox.Toolbar uses a type in ui.src.react-ftm.components.NetworkDiagram.History.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.toolbox.Toolbar.IToolbarProps→ui.src.react-ftm.components.NetworkDiagram.History.History
- Direction
- ui.src.react-ftm.components.NetworkDiagram.toolbox.Toolbar uses ui.src.react-ftm.components.NetworkDiagram.History, so a change to ui.src.react-ftm.components.NetworkDiagram.History can break ui.src.react-ftm.components.NetworkDiagram.toolbox.Toolbar, while a change to ui.src.react-ftm.components.NetworkDiagram.toolbox.Toolbar can't break ui.src.react-ftm.components.NetworkDiagram.History.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.toolbox.Toolbar uses a module listed above it, which is the healthy direction.
39→23 ui.src.react-ftm.components.NetworkDiagram.utils uses ui.src.react-ftm.components.NetworkDiagram.Viewport✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.utils uses a type in ui.src.react-ftm.components.NetworkDiagram.Viewport.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.utils.exportSvg→ui.src.react-ftm.components.NetworkDiagram.Viewport.Viewport
- Direction
- ui.src.react-ftm.components.NetworkDiagram.utils uses ui.src.react-ftm.components.NetworkDiagram.Viewport, so a change to ui.src.react-ftm.components.NetworkDiagram.Viewport can break ui.src.react-ftm.components.NetworkDiagram.utils, while a change to ui.src.react-ftm.components.NetworkDiagram.utils can't break ui.src.react-ftm.components.NetworkDiagram.Viewport.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.utils uses a module listed above it, which is the healthy direction.
39→28 ui.src.react-ftm.components.NetworkDiagram.utils uses ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.utils uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.utils.exportSvg→ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.GraphLayout
- Direction
- ui.src.react-ftm.components.NetworkDiagram.utils uses ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout can break ui.src.react-ftm.components.NetworkDiagram.utils, while a change to ui.src.react-ftm.components.NetworkDiagram.utils can't break ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.utils uses a module listed above it, which is the healthy direction.
39→32 ui.src.react-ftm.components.NetworkDiagram.utils uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex✕
- Connections
- 1 pair of types, where a type in ui.src.react-ftm.components.NetworkDiagram.utils uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.utils.filterVerticesByText→ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.Vertex
- Direction
- ui.src.react-ftm.components.NetworkDiagram.utils uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Vertex can break ui.src.react-ftm.components.NetworkDiagram.utils, while a change to ui.src.react-ftm.components.NetworkDiagram.utils can't break ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.utils uses a module listed above it, which is the healthy direction.
40→24 ui.src.react-ftm.components.NetworkDiagram.layout.tools uses ui.src.react-ftm.components.NetworkDiagram.layout.Edge✕
- Connections
- 2 pairs of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.tools uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Edge.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.tools.alignHorizontal→ui.src.react-ftm.components.NetworkDiagram.layout.Edge.Edgeui.src.react-ftm.components.NetworkDiagram.layout.tools.alignVertical→ui.src.react-ftm.components.NetworkDiagram.layout.Edge.Edge
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.tools uses ui.src.react-ftm.components.NetworkDiagram.layout.Edge, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Edge can break ui.src.react-ftm.components.NetworkDiagram.layout.tools, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.tools can't break ui.src.react-ftm.components.NetworkDiagram.layout.Edge.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.tools uses a module listed above it, which is the healthy direction.
40→28 ui.src.react-ftm.components.NetworkDiagram.layout.tools uses ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout✕
- Connections
- 2 pairs of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.tools uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.tools.centerAround→ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.GraphLayoutui.src.react-ftm.components.NetworkDiagram.layout.tools.positionSelection→ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.GraphLayout
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.tools uses ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout can break ui.src.react-ftm.components.NetworkDiagram.layout.tools, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.tools can't break ui.src.react-ftm.components.NetworkDiagram.layout.GraphLayout.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.tools uses a module listed above it, which is the healthy direction.
40→32 ui.src.react-ftm.components.NetworkDiagram.layout.tools uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex✕
- Connections
- 2 pairs of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.tools uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.tools.centerAround→ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.Vertexui.src.react-ftm.components.NetworkDiagram.layout.tools.common→ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.Vertex
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.tools uses ui.src.react-ftm.components.NetworkDiagram.layout.Vertex, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.Vertex can break ui.src.react-ftm.components.NetworkDiagram.layout.tools, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.tools can't break ui.src.react-ftm.components.NetworkDiagram.layout.Vertex.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.tools uses a module listed above it, which is the healthy direction.
40→35 ui.src.react-ftm.components.NetworkDiagram.layout.tools uses ui.src.react-ftm.components.NetworkDiagram.layout.tools.common✕
- Connections
- 6 pairs of types, where a type in ui.src.react-ftm.components.NetworkDiagram.layout.tools uses a type in ui.src.react-ftm.components.NetworkDiagram.layout.tools.common.
- The types involved
ui.src.react-ftm.components.NetworkDiagram.layout.tools.alignCircle→ui.src.react-ftm.components.NetworkDiagram.layout.tools.common.IPositioningPropsui.src.react-ftm.components.NetworkDiagram.layout.tools.alignHorizontal→ui.src.react-ftm.components.NetworkDiagram.layout.tools.common.IPositioningPropsui.src.react-ftm.components.NetworkDiagram.layout.tools.alignVertical→ui.src.react-ftm.components.NetworkDiagram.layout.tools.common.IPositioningPropsui.src.react-ftm.components.NetworkDiagram.layout.tools.arrangeTree→ui.src.react-ftm.components.NetworkDiagram.layout.tools.common.IPositioningPropsui.src.react-ftm.components.NetworkDiagram.layout.tools.forceLayout→ui.src.react-ftm.components.NetworkDiagram.layout.tools.common.IPositioningPropsui.src.react-ftm.components.NetworkDiagram.layout.tools.getForceData→ui.src.react-ftm.components.NetworkDiagram.layout.tools.common.IPositioningProps
- Direction
- ui.src.react-ftm.components.NetworkDiagram.layout.tools uses ui.src.react-ftm.components.NetworkDiagram.layout.tools.common, so a change to ui.src.react-ftm.components.NetworkDiagram.layout.tools.common can break ui.src.react-ftm.components.NetworkDiagram.layout.tools, while a change to ui.src.react-ftm.components.NetworkDiagram.layout.tools can't break ui.src.react-ftm.components.NetworkDiagram.layout.tools.common.
- Position
- Below the diagonal: ui.src.react-ftm.components.NetworkDiagram.layout.tools 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 |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 86 | High / Critical |
| A05:2025 — Injection | 44 | High / Critical |
| A02:2025 — Security Misconfiguration | 42 | High / Critical |
| A07:2025 — Authentication Failures | 6 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with TimelineChartItem.test.tsx; Resolve the 2 Banned license finding(s) in License Compliance; Resolve the 1 finding(s) in DR & Backup.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with TimelineChartItem.test.tsx. | +6.3 pts | Low | Test Quality |
| Resolve the 2 Banned license finding(s) in License Compliance. | +6.3 pts | Low | License Compliance |
| Resolve the 1 finding(s) in DR & Backup. | +5.3 pts | Medium | DR & Backup |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with setup.py. | +2.0 pts | Low | ADR Quality |
| Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing. | +2.6 pts | Medium | Security & performance tooling |
| Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker. | +2.6 pts | Medium | Outbound HTTP resilience |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +2.1 pts | Medium | Keyboard semantics |
| 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. | +1.7 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.2 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| ui/src/components/Timeline/Timeline.test.tsx | 6.6 | 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 81 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 — 81 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, 751 of 799 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: the Python half could not be measured — the pytest suite ran no test, so nothing was measured (its dependency install failed (pip exit 1: Failed building wheel for pyicu), so its suite was not run against dependencies it does not declare). Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- 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 118 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 52 test source file(s) (.py) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.tsx, .py, .jsx, .js, .ts) and this repository declares a Python test suite (repository root, 41 test files), but it was not re-run: its dependency install failed (pip exit 1: Failed building wheel for pyicu), so its suite was not run against dependencies it does not declare. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 package.json, but the licence verdict published here was taken over its Python distribution 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.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 250 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 237 of the 591 production source files in this repository: 341 are under the ~2,400-byte size floor this dimension measures over, and the remaining 13 have no attributable history left to measure.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- 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 package.json'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.
- D41 Kernel & Syscall Confinement — 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. Helm/charts/aleph/templates/aleph-upgrade-job.yaml:2, REDACTED:2, REDACTED:3, REDACTED:2, REDACTED:9, REDACTED:2, REDACTED:2 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
- 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 14 — a file the compose project references is missing) — env file aleph.env not found: stat aleph.env: no such file or directory; 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. 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.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- 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. 57 further occurrence(s) are not listed individually; the score already reflects all 97.
- R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 187 further occurrence(s) are not listed individually; the score already reflects all 227.
- X16 Unfloored truncation loop — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- 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.
- X29 Per-element action decided by a fixed element — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- 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 REDACTED, 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.
- D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
- D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was entityEditorWrapper.entityEditorWrapper at 20. A further 1 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 QueryFilterTag.label at 23 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: ui/src/components/QueryTags/QueryFilterTag.jsx (QueryFilterTag.label at 23). 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 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with entityEditorWrapper.entityEditorWrapper (cyclomatic 20), CollectionInfo.render (cyclomatic 18), PropertyValue.render (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
16 method(s) exceeded the cognitive complexity threshold of 15; the worst was GraphLayout.generate at 30.
What to do
- Bring the 16 bodies over 15 down to 15 or less in Cognitive Complexity — start with GraphLayout.generate (cognitive 30), Query.get_aggregations (cognitive 26), entitysets.replace_layout_ids (cognitive 25). — 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 16 together lifts Cognitive Complexity from 8.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
23 god class(es) detected.
What to do
- Resolve the 16 MethodTooLong finding(s) in God Classes — start with CollectionEditDialog.jsx, Navbar.jsx, MappingEditor.jsx. — One of this dimension's main actionable groups (16 warning-level).
- Resolve the 3 TooManyMethods finding(s) in God Classes — start with GraphLayout.ts, Query.js, TableEditor.tsx. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with PasswordSettings.jsx, PasswordAuth.jsx. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
10 duplicated block group(s) detected. 1.1 % of the production lines (601 of 53,188) are in a reported copy. A further 10 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 20 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .jsx, .tsx (62% 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 2 Members sharing a duplicated core (5 members, 50+ identical tokens) finding(s) in Code Duplication — start with 1519391870a0_create_diagram.py (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (18 corresponding lines) finding(s) in Code Duplication — start with reconcile_api.py. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copies of one member (3 members, 22+ corresponding lines) finding(s) in Code Duplication — start with collectors.py. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
3 production modules (npm+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 2 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 21 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 118 tests. Measured on the JavaScript/TypeScript suite only — at least 52 test source file(s) (.py) went unread, so its test quality is unmeasured and is not in these counts.
What to do
- Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with TimelineChartItem.test.tsx. — One of this dimension's main actionable groups (1 issue-level).
D12 · Dependency Hygiene
32 outdated, 0 yanked pinned Python distributions. 39 of 45 shipped distributions were graded against pypi.org (0 not published there, 6 declared without an exact pin, which installs the newest release the declaration admits and so cannot be behind one). Only EXACT pins are graded for currency: a floor or a range already installs the newest release it admits, so reporting one would report this repository for being current. Whether a deliberate upper cap has itself gone stale is a different and weaker question, and is not asked. Whether any distribution is UNMAINTAINED is not graded — PyPI publishes no maintenance status, and release age does not stand in for one. Lockfiles are not read (poetry.lock, uv.lock, Pipfile.lock, pdm.lock), so a lock-resolved install is outside this verdict. Known CVEs in this dependency graph are D30's question.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
D14 · License Compliance
2 of 109 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 45 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (64 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. 6 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's Python distribution dependencies and nothing else. The repository also declares package.json, 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.
What to do
- Resolve the 2 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (2 issue-level).
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
14 deducted task-comment markers across 26157 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 13 TodoComment finding(s) in Explicit Debt — start with Timeline.test.tsx (4), filterVerticesByText.ts, Edge.ts. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with expand.py. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 80 document(s) read across 3 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 setup.py. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
0 of 180 judged comments only repeat the code they sit on (0.0 %). 8 comment(s) in another language or script were not judged.
D26 · Project Cohesion
2 of 2 build units (Python, npm) 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 package.json, setup.py. — One of this dimension's main actionable groups (2 recommendation-level).
D28 · Secrets (history)
5 finding(s): 0 critical, 5 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 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
47 finding(s): 0 critical, 22 high, 25 medium, 0 low. 15 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 15 file(s) — `REDACTED` (lines 1–3, line 15), `REDACTED` (lines 1–3, line 15), `REDACTED` (lines 1–3, line 19), `REDACTED` (lines 1–3, line 21), `REDACTED` (lines 1–3, line 9), … (+10 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 15 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 (15 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
76 finding(s): 9 critical, 37 high, 23 medium, 7 low.
What to do
- Resolve the 35 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (32), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (35 issue-level).
- Resolve the 9 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8), REDACTED. — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D31 · IaC & Container Security
42 finding(s): 0 critical, 9 high, 24 medium, 9 low.
What to do
- Resolve the 24 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (11), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (24 warning-level).
- Resolve the 9 High IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 9 Low IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (2), REDACTED.production. — One of this dimension's main actionable groups (9 recommendation-level).
D34 · Knowledge Freshness
250 of 250 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is ui/src/react-ftm/components/EntityTable/TableEditor.tsx. Counted over 250 of the 591 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 248 Orphaned file finding(s) in Knowledge Freshness — start with util.py (3), util.js (3), xref.py (2). — One of this dimension's main actionable groups (248 recommendation-level).
- Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with TableEditor.tsx, entities_api.py. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: index.js↔index.js 76%; index.js↔selectors.js 63%; PdfViewer.jsx↔PdfViewerSearch.jsx 50%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with index.js (2), PdfViewer.jsx. — One of this dimension's main actionable groups (3 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D40 · Network Egress Confinement
0/2 network-egress controls present (network policy, egress restriction).
What to do
- Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
D41 · Kernel & Syscall Confinement
No workload manifest could be read as a pod spec, so no confinement was judged.
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 0 platform declaration(s) and 45 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
- 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). — ui/src/viewers/VideoViewer.jsx:13
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — docs/src/components/Annotation.astro:37
- 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. (×14) — ui/src/components/Collection/CollectionReference.jsx:24, ui/src/components/Collection/CollectionReference.jsx:36, ui/src/components/SortingBar/SortingBar.jsx:103, …
- 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. (×2) — ui/src/components/EntitySearch/FacetedEntitySearch.jsx:241, ui/src/components/EntitySearch/FacetedEntitySearch.jsx:371
- 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). — ui/src/components/SearchAlert/SearchAlert.jsx:99
- 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. (×7) — ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:167, ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:208, ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:228, …
- This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×3) — ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:186, ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:308, ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:387
- This <path> 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. — ui/src/react-ftm/components/NetworkDiagram/renderer/EdgeRenderer.tsx:115
- 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. — ui/src/react-ftm/components/common/EntityList.tsx:35
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — ui/public/index.html:2
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — ui/public/index.html:2
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. (×7) — ui/src/react-ftm/components/NetworkDiagram/renderer/EdgeLabelRenderer.tsx:139, ui/src/react-ftm/components/NetworkDiagram/renderer/EdgeRenderer.tsx:115, ui/src/react-ftm/components/NetworkDiagram/renderer/VertexLabelRenderer.tsx:64, …
- This <g> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus. — ui/src/react-ftm/components/NetworkDiagram/renderer/GroupingRenderer.tsx:136
- This <circle> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus. — ui/src/react-ftm/components/NetworkDiagram/renderer/VertexRenderer.tsx:213
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
- `.RadiusPicker__slider . -slider-handle` 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. — ui/src/react-ftm/editors/RadiusPicker.scss:23
- `.NetworkDiagram__main` 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. — ui/src/react-ftm/components/NetworkDiagram/NetworkDiagram.scss:47
- `.TableEditor .data-grid-container .data-grid .cell.checkbox . -control-indicator` 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. — ui/src/react-ftm/components/EntityTable/TableEditor.scss:77
- `.SearchBox__input` moves (`transition: max-width 500ms ease-in-out`) 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. — ui/src/react-ftm/components/NetworkDiagram/toolbox/SearchBox.scss:22
- `.InvestigationHeading__divider` moves (`transition: width $transition-duration ease-in-out, margin 1s ease-in-out`) 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. — ui/src/components/Investigation/InvestigationHeading.scss:41
- `.InvestigationHeading__metadata` moves (`transition: max-height 1s ease-in-out`) 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. — ui/src/components/Investigation/InvestigationHeading.scss:55
- `.Facet > .opener > .caret` moves (`transition: transform 100ms`) 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. — ui/src/components/Facet/Facet.scss:30
- `.FacetedEntitySearch__side-placeholder.SidePane` moves (`transition: width 120ms linear`) 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. — ui/src/components/EntitySearch/FacetedEntitySearch.scss:76
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
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×3) — ui/src/components/auth/PasswordAuth.jsx:13, ui/src/dialogs/CreateInvestigationDialog/CreateInvestigationDialog.jsx:41, ui/src/dialogs/EntitySetCreateDialog/EntitySetCreateDialog.jsx:325
What to do
- Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack 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. — REDACTED:4
What to do
- Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
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
P7 · Outbound HTTP resilience
- `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — contrib/play/esnames.py:26
What to do
- Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
P8 · Schema migrations
PF3 · Async & latency hygiene
R1 · Type Safety
- 166 typed · 323 plain JS — the untyped files are ui/i18n/concatTranslations.js, ui/src/actions/alertActions.js, ui/src/actions/asyncActionCreator.js, ui/src/actions/bookmarkActions.js, ui/src/actions/collectionActions.js, ui/src/actions/configActions.js (+317 more).
R10 · Code Duplication
- 40 duplicated blocks under ui/src/ have copies in at least two of the sibling directories components, dialogs, react-ftm, screens, viewers — 12 of them are reported below, and 28 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 40 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 40 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 40 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. — ui/src/components/Collection/CollectionXrefMode.jsx:41
- 40 duplicated blocks under ui/src/components/ have copies in at least two of the sibling directories AdvancedSearch, AlertsManager, AuthButtons, Collection, Dashboard, Document (+16 more sibling(s) not listed) — 19 of them are reported below, and 21 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 40 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 40 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 40 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. — ui/src/components/Entity/EntitySimilarMode.jsx:128
- 15 duplicated blocks under ui/src/dialogs/ have copies in at least two of the sibling directories CollectionAccessDialog, CollectionDeleteDialog, CollectionEditDialog, CollectionXrefDialog, CreateInvestigationDialog, DocumentFolderDialog (+10 more sibling(s) not listed) — 11 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — ui/src/dialogs/EntitySetCreateDialog/EntitySetCreateDialog.jsx:82
- 10 duplicated blocks under ui/src/screens/ have copies in at least two of the sibling directories AlertsScreen, CollectionScreen, DatasetIndexScreen, DiagramScreen, EntityScreen, EntitySetIndexScreen (+6 more sibling(s) not listed) — 6 of them are reported below, and 4 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 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 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 10 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. — ui/src/screens/ListScreen/ListScreen.jsx:24
- ui/src/dialogs/EntitySetCreateDialog/EntitySetCreateDialog.jsx:82 · ui/src/dialogs/EntitySetEditDialog/EntitySetEditDialog.jsx:65 — the two spans are one implementation copied and then locally edited — 594 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. — ui/src/dialogs/EntitySetCreateDialog/EntitySetCreateDialog.jsx:82
- ui/src/components/Profile/ProfileItemsMode.jsx:23 · ui/src/components/Profile/ProfileSimilarMode.jsx:23 — the two spans are one implementation copied and then locally edited — 522 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. — ui/src/components/Profile/ProfileItemsMode.jsx:23
- ui/src/react-ftm/components/NetworkDiagram/renderer/GroupingRenderer.tsx:19 · ui/src/react-ftm/components/NetworkDiagram/renderer/VertexRenderer.tsx:18 — the two spans are one implementation copied and then locally edited — 530 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. — ui/src/react-ftm/components/NetworkDiagram/renderer/GroupingRenderer.tsx:19
- ui/src/dialogs/CollectionDeleteDialog/CollectionDeleteDialog.jsx:11 · ui/src/dialogs/EntitySetDeleteDialog/EntitySetDeleteDialog.jsx:12 — the two spans are one implementation copied and then locally edited — 254 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. — ui/src/dialogs/CollectionDeleteDialog/CollectionDeleteDialog.jsx:11
- ui/src/components/Collection/CollectionReindexAlert.jsx:20 · ui/src/components/Collection/CollectionReingestAlert.jsx:20 — 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. — ui/src/components/Collection/CollectionReindexAlert.jsx:20
- ui/src/components/Entity/EntitySimilarMode.jsx:128 · ui/src/components/Profile/ProfileSimilarMode.jsx:56 — the two spans are one implementation copied and then locally edited — 292 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. — ui/src/components/Entity/EntitySimilarMode.jsx:128
- ui/src/screens/ListScreen/ListScreen.jsx:24 · ui/src/screens/TimelineScreen/TimelineScreen.jsx:36 — the two spans are one implementation copied and then locally edited — 304 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. — ui/src/screens/ListScreen/ListScreen.jsx:24
- ui/src/react-ftm/components/NetworkDiagram/layout/Edge.ts:29 · ui/src/react-ftm/components/NetworkDiagram/layout/Vertex.ts:33 — the two spans are one implementation copied and then locally edited — 255 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — ui/src/react-ftm/components/NetworkDiagram/layout/Edge.ts:29
- ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:353 · ui/src/dialogs/CreateInvestigationDialog/CreateInvestigationDialog.jsx:178 — the two spans are one implementation copied and then locally edited — 186 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. — ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:353
- ui/src/react-ftm/components/common/EdgeCreateDialog.tsx:239 · ui/src/react-ftm/components/common/EdgeCreateDialog.tsx:284 — 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. — ui/src/react-ftm/components/common/EdgeCreateDialog.tsx:239
- ui/src/dialogs/EntitySetDeleteDialog/EntitySetDeleteDialog.jsx:42 · ui/src/dialogs/EntitySetDeleteDialog/EntitySetDeleteDialog.jsx:79 — 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. — ui/src/dialogs/EntitySetDeleteDialog/EntitySetDeleteDialog.jsx:42
- ui/src/viewers/ArticleViewer.jsx:9 · ui/src/viewers/EmailViewer.jsx:10 — the two spans are one implementation copied and then locally edited — 197 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. — ui/src/viewers/ArticleViewer.jsx:9
- ui/src/components/Investigation/InvestigationQuickLinks.jsx:84 · ui/src/components/Investigation/InvestigationQuickLinks.jsx:116 — 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. — ui/src/components/Investigation/InvestigationQuickLinks.jsx:84
- ui/src/components/Settings/NotificationSettings.jsx:9 · ui/src/components/Settings/ProfileSettings.jsx:15 — 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. — ui/src/components/Settings/NotificationSettings.jsx:9
- ui/src/components/Entity/EntitySimilarMode.jsx:76 · ui/src/components/Profile/ProfileSimilarMode.jsx:94 — 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. — ui/src/components/Entity/EntitySimilarMode.jsx:76
- ui/src/react-ftm/components/NetworkDiagram/layout/tools/alignHorizontal.ts:13 · ui/src/react-ftm/components/NetworkDiagram/layout/tools/alignVertical.ts:13 — 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. — ui/src/react-ftm/components/NetworkDiagram/layout/tools/alignHorizontal.ts:13
- ui/src/screens/AlertsScreen/AlertsScreen.jsx:30 · ui/src/screens/ExportsScreen/ExportsScreen.jsx:16 — 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. — ui/src/screens/AlertsScreen/AlertsScreen.jsx:30
- ui/src/dialogs/MappingCreateDialog/MappingCreateDialog.jsx:13 · ui/src/dialogs/MappingDeleteDialog/MappingDeleteDialog.jsx:13 · ui/src/dialogs/MappingFlushDialog/MappingFlushDialog.jsx:13 · ui/src/dialogs/MappingSaveDialog/MappingSaveDialog.jsx:13 — 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. — ui/src/dialogs/MappingCreateDialog/MappingCreateDialog.jsx:13
- ui/src/components/Collection/CollectionMappingsMode.jsx:44 · ui/src/components/Entity/EntityMappingMode.jsx:124 — 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. — ui/src/components/Collection/CollectionMappingsMode.jsx:44
- ui/src/screens/HomeScreen/HomeScreen.jsx:157 · ui/src/screens/HomeScreen/HomeScreen.jsx:177 — 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. — ui/src/screens/HomeScreen/HomeScreen.jsx:157
- ui/src/components/Investigation/InvestigationQuickLinks.jsx:146 · ui/src/components/Investigation/InvestigationQuickLinks.jsx:171 — 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. — ui/src/components/Investigation/InvestigationQuickLinks.jsx:146
- ui/src/components/Investigation/InvestigationSidebar.jsx:77 · ui/src/components/Investigation/InvestigationSidebar.jsx:105 — 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. — ui/src/components/Investigation/InvestigationSidebar.jsx:77
- ui/src/dialogs/MappingCreateDialog/MappingCreateDialog.jsx:22 · ui/src/dialogs/MappingDeleteDialog/MappingDeleteDialog.jsx:22 · ui/src/dialogs/MappingFlushDialog/MappingFlushDialog.jsx:22 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — ui/src/dialogs/MappingCreateDialog/MappingCreateDialog.jsx:22
- ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:158 · ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:219 · ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:239 · ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:259 · +1 more site(s) not listed — all 5 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. — ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:158
- ui/src/components/AuthButtons/AuthButtons.jsx:104 · ui/src/components/Dashboard/Dashboard.jsx:87 — the two spans are one implementation copied and then locally edited — 112 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. — ui/src/components/AuthButtons/AuthButtons.jsx:104
- ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:231 · ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:251 · ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:271 · ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:291 — all 4 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. — ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:231
- ui/src/queries.js:175 · ui/src/queries.js:197 — 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. — ui/src/queries.js:175
- ui/src/components/common/LandingQuickLinks.jsx:14 · ui/src/components/common/LandingQuickLinks.jsx:30 · ui/src/components/common/LandingQuickLinks.jsx:46 · ui/src/components/common/LandingQuickLinks.jsx:62 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — ui/src/components/common/LandingQuickLinks.jsx:14
- ui/src/dialogs/CollectionAccessDialog/CollectionAccessDialog.jsx:194 · ui/src/dialogs/CollectionAccessDialog/CollectionAccessDialog.jsx:211 — 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. — ui/src/dialogs/CollectionAccessDialog/CollectionAccessDialog.jsx:194
- ui/src/dialogs/CreateInvestigationDialog/CreateInvestigationDialog.jsx:158 · ui/src/dialogs/EntitySetEditDialog/EntitySetEditDialog.jsx:154 — 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. — ui/src/dialogs/CreateInvestigationDialog/CreateInvestigationDialog.jsx:158
- ui/src/dialogs/EntitySetCreateDialog/EntitySetCreateDialog.jsx:347 · ui/src/dialogs/EntitySetEditDialog/EntitySetEditDialog.jsx:179 — 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. — ui/src/dialogs/EntitySetCreateDialog/EntitySetCreateDialog.jsx:347
- ui/src/react-ftm/components/NetworkDiagram/dialogs/SettingsDialog.tsx:124 · ui/src/react-ftm/components/common/EdgeCreateDialog.tsx:326 — the two spans are one implementation copied and then locally edited — 71 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. — ui/src/react-ftm/components/NetworkDiagram/dialogs/SettingsDialog.tsx:124
- ui/src/react-ftm/components/NetworkDiagram/layout/GraphLayout.ts:120 · ui/src/react-ftm/components/NetworkDiagram/layout/GraphLayout.ts:136 — 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. — ui/src/react-ftm/components/NetworkDiagram/layout/GraphLayout.ts:120
- ui/src/components/Entity/EntityTagsMode.jsx:81 · ui/src/components/Profile/ProfileItemsMode.jsx:116 · ui/src/components/Profile/ProfileSimilarMode.jsx:107 — the 3 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. 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. — ui/src/components/Entity/EntityTagsMode.jsx:81
- ui/src/components/Exports/Export.jsx:15 · ui/src/components/Notification/Notification.jsx:49 — 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. — ui/src/components/Exports/Export.jsx:15
- ui/src/actions/entityActions.js:16 · ui/src/actions/profileActions.js:6 · ui/src/actions/roleActions.js:14 — 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. — ui/src/actions/entityActions.js:16
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
- ui/src/components/common/SignInCallout.jsx:5 imports @blueprintjs/core/lib/esm/components/button/buttons, 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. — ui/src/components/common/SignInCallout.jsx:5
- ui/src/components/common/Tag.jsx:2 imports @blueprintjs/core/lib/esm/components/icon/icon, 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. — ui/src/components/common/Tag.jsx: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
- render has cyclomatic complexity 18 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. — ui/src/components/Collection/CollectionInfo.jsx:8
- validate 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. — ui/src/react-ftm/utils/validate.ts:72
- render 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. — ui/src/components/Facet/Facet.jsx:151
- renderContent has cyclomatic complexity 15 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 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. — ui/src/components/Document/DocumentViewMode.jsx:26
- render 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. — ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:144
- reducer has cyclomatic complexity 13 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 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. — ui/src/components/Timeline/state.ts:97
- render has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ui/src/components/Screen/Screen.jsx:35
- render 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. (×4) — ui/src/components/Dashboard/Dashboard.jsx:69, ui/src/components/Document/DocumentManager.jsx:110, ui/src/components/EntityTable/EntityTable.jsx:191, …
- getParam has cyclomatic complexity 11 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 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. — ui/src/components/Notification/Notification.jsx:17
- getSortValue has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — ui/src/react-ftm/types/Property.tsx:79
- filterDateIntervals 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. — ui/src/components/Facet/util.js:54
R3 · Large Files
- ui/src/react-ftm/components/EntityTable/TableEditor.tsx has 695 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — ui/src/react-ftm/components/EntityTable/TableEditor.tsx:1
- ui/src/react-ftm/components/NetworkDiagram/NetworkDiagram.tsx has 541 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — ui/src/react-ftm/components/NetworkDiagram/NetworkDiagram.tsx:1
- ui/src/react-ftm/components/NetworkDiagram/layout/GraphLayout.ts has 481 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — ui/src/react-ftm/components/NetworkDiagram/layout/GraphLayout.ts:1
- ui/src/selectors.js has 417 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — ui/src/selectors.js:1
- ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx 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. — ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:1
- ui/src/components/EntitySearch/FacetedEntitySearch.jsx has 409 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — ui/src/components/EntitySearch/FacetedEntitySearch.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. (×40) — ui/src/components/EntitySearch/FacetedEntitySearch.jsx:1, ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:1, ui/src/components/Entity/EntityViews.jsx:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
- `ui` is TypeScript, but a type error in it cannot fail anything this repository runs: its `lint` script (`eslint --ext js,jsx,ts,tsx src --max-warnings 0`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles. — ui/package.json:65
- The package in `docs` declares the lint script `format:check` (`prettier --check 'src/'`), 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 `docs` (or the workspace's task runner). — docs/package.json:11
- The package in `ui` declares the lint script `lint` (`eslint --ext js,jsx,ts,tsx src --max-warnings 0`), 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 lint` in `ui` (or the workspace's task runner). — ui/package.json:65
What to do
- Add `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 6 application, 5 tooling and 25 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (6 application, 5 tooling, 25 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 (×23) — ui/src/viewers/PdfViewer.jsx, ui/src/components/Investigation/InvestigationSidebar.jsx, ui/src/components/Exports/ExportsList.jsx, …
- no import path from any entry point (6 application, 5 tooling, 25 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/components/Investigation/InvestigationSidebar.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 — ui/src/components/Investigation/InvestigationHeading.jsx
- no import path from any entry point (6 application, 5 tooling, 25 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/viewers/PdfViewer.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 — ui/src/viewers/PdfViewerPage.jsx
- no import path from any entry point (6 application, 5 tooling, 25 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (ui/src/util/getEntityLink.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 — ui/src/util/getProfileLink.js
- Nothing ultimately consumes this binding: its only referrer is the re-export in ui/src/actions/index.js, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in ui/src/actions/index.js in the same commit, or the barrel will import a name that no longer exists. (×2) — ui/src/actions/exportActions.js:5, ui/src/actions/exportActions.js:14
- Nothing imports this binding — it is safe to review for removal. (×8) — ui/src/components/Timeline/types.ts:8, ui/src/reducers/util.js:105, ui/src/selectors.js:201, …
- Nothing ultimately consumes this binding: its only referrer is the re-export in ui/src/react-ftm/types/index.tsx, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in ui/src/react-ftm/types/index.tsx in the same commit, or the barrel will import a name that no longer exists. — ui/src/react-ftm/types/MIMEType.tsx:56
- Nothing ultimately consumes this binding: its only referrer is the re-export in ui/src/react-ftm/utils/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in ui/src/react-ftm/utils/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — ui/src/react-ftm/utils/toaster.ts:15, ui/src/react-ftm/utils/validate.ts:115
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 package.json — installs work only by hoisting accident. — ui/src/react-ftm/types/FileSize.tsx:2
- Declared in ui/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) — ui/package.json:21, ui/package.json:53
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- ui/src/components/common/index.jsx → ui/src/components/common/AnimatedCount.jsx → ui/src/components/common/index.jsx (one verified cycle inside a mutually-dependent group of 21 files) — ui/src/components/common/index.jsx:1
- ui/src/components/Timeline/EntityViewer2.tsx → ui/src/components/Timeline/Timeline.tsx → ui/src/components/Timeline/EntityViewer2.tsx (one verified cycle inside a mutually-dependent group of 13 files) — ui/src/components/Timeline/EntityViewer2.tsx:4
- ui/src/dialogs/DocumentUploadDialog/DocumentUploadStatus.jsx → ui/src/dialogs/DocumentUploadDialog/DocumentUploadTrace.jsx → ui/src/dialogs/DocumentUploadDialog/DocumentUploadStatus.jsx — ui/src/dialogs/DocumentUploadDialog/DocumentUploadStatus.jsx:4
- ui/src/react-ftm/components/EntityTable/EntityTable.tsx → ui/src/react-ftm/components/EntityTable/index.ts → ui/src/react-ftm/components/EntityTable/EntityTable.tsx — ui/src/react-ftm/components/EntityTable/EntityTable.tsx:11
- ui/src/react-ftm/components/NetworkDiagram/GraphConfig.ts → ui/src/react-ftm/components/NetworkDiagram/layout/index.ts → ui/src/react-ftm/components/NetworkDiagram/layout/Edge.ts → ui/src/react-ftm/components/NetworkDiagram/layout/GraphLayout.ts → ui/src/react-ftm/components/NetworkDiagram/GraphConfig.ts (one verified cycle inside a mutually-dependent group of 26 files) — ui/src/react-ftm/components/NetworkDiagram/GraphConfig.ts:2
- ui/src/react-ftm/components/NetworkDiagram/toolbox/Sidebar.tsx → ui/src/react-ftm/components/NetworkDiagram/toolbox/index.ts → ui/src/react-ftm/components/NetworkDiagram/toolbox/Sidebar.tsx (one verified cycle inside a mutually-dependent group of 3 files) — ui/src/react-ftm/components/NetworkDiagram/toolbox/Sidebar.tsx:7
- ui/src/react-ftm/types/EnumValue.tsx → ui/src/react-ftm/utils/index.ts → ui/src/react-ftm/utils/sortEntities.ts → ui/src/react-ftm/types/index.tsx → ui/src/react-ftm/types/EnumValue.tsx (one verified cycle inside a mutually-dependent group of 6 files) — ui/src/react-ftm/types/EnumValue.tsx:2
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- Set: Referrer-Policy, X-Content-Type-Options, X-Frame-Options. 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.) — ui/nginx.conf:25
What to do
- Add Content-Security-Policy, Strict-Transport-Security beside the headers already set; Content-Security-Policy is the one that pays for itself first, then Strict-Transport-Security, then nosniff and a frame policy.
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `renderHidden` is exported and takes `items: any` from its caller, and it calls itself at line 92 (`this.renderHidden`) with a piece of `items` — and nowhere in `renderHidden` 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 `renderHidden` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — ui/src/react-ftm/components/NetworkDiagram/toolbox/ToolbarButtonGroup.tsx:92
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.
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `latestUpdate.safeHtmlBody` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:48
- `value` 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) — ui/src/viewers/EmailViewer.jsx:83, ui/src/viewers/HtmlViewer.jsx:14
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
- `queryEndpoint` accepts `result` from the caller and keeps it in `result` on line 21, where only it can read the value — but nothing ever reads `result`. Setting `result` therefore changes nothing: every caller gets the same behaviour whatever they pass, and nothing reports that the option was ignored. Read `result` where the behaviour it configures is decided — or, if the behaviour genuinely is fixed, remove `result` from the accepted options so callers stop setting a knob that does nothing. — ui/src/actions/util.js:21
What to do
- Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
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. (×2) — ui/src/react-ftm/utils/validate.ts:53, ui/src/react-ftm/utils/validate.ts:64
- `except Exception` 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. (×2) — aleph/views/util.py:139, aleph/model/document.py:161
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug` at line 51 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — aleph/worker.py:51
- `info` at line 62 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — aleph/worker.py:62
- `info` at line 170 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — aleph/worker.py:170
- `info` at line 202 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — aleph/worker.py:202
- `info` at line 212 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — aleph/worker.py:212
- `info` at line 247 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — aleph/worker.py:247
- `exception` at line 100 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.exception("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.exception("order moved", order_id=order_id, status=status)` with structlog. — aleph/views/serializers.py:100
- `warning` at line 134 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — REDACTED:134
- `info` at line 93 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — REDACTED:93
- `info` at line 133 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — REDACTED:133
- `info` at line 134 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — REDACTED:134
- `debug` at line 149 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — aleph/logic/collections.py:149
- `info` at line 270 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — aleph/logic/xref.py:270
- `info` at line 273 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — aleph/logic/xref.py:273
- `info` at line 278 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — aleph/logic/xref.py:278
- `info` at line 306 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — aleph/index/util.py:306
- `info` at line 310 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — aleph/index/util.py:310
- `info` at line 314 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — aleph/index/util.py:314
- `info` at line 315 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — aleph/index/util.py:315
- `info` at line 318 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — aleph/index/util.py:318
- `info` at line 325 is handed an f-string as its message, 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 record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — aleph/index/util.py:325
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- ~0.7 `!` null assertions per 1k TypeScript source lines — 10 assertion(s) across the 13963 source line(s) of the 146 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: ui/src/react-ftm/components/NetworkDiagram/renderer/VertexRenderer.tsx (10). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
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 | 62.2 | Adequate — gated by R1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 64.9 | Adequate — gated by D26, R9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 53.2 | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 39.1 | Weak — gated by P3, P5, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 68.7 | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 48.4 | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — a class or table named for it — django-simple-history, django-auditlog, django-reversion, django-pghistory or SQLAlchemy-Continuum recording each change, or an event-sourced store beside one) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — C4 reached only 26% of this repository's production lines — javascript (27,031 lines), typescript (12,294 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. A delete/anonymise identifier was seen but did not co-occur with GDPR vocabulary or a subject-id shape, so it was not credited (e.g. a save-slot DeleteAccount()). Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 43 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 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 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.
- 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 14 — a file the compose project references is missing) — env file aleph.env not found: stat aleph.env: no such file or directory; 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 — C2 reached only 26% of this repository's production lines — javascript (27,031 lines), typescript (12,294 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- D11 Test Reliability — Test reliability not included — the .py suite was found but not re-run
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (6654 declarations, no unit with a dominant convention).
- 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. Aggregate roots were found in only one source directory (aleph), which is a layered codebase, not two contexts. 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 .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.
- D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
- 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 — Python suite
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (11 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit))
- 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, 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
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — X27 reached only 26% of this repository's production lines — javascript (27,031 lines), typescript (12,294 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — 119 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:167
- <input> without a programmatic label ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:228
- <input> without a programmatic label ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:248
- <input> without a programmatic label ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:268
- <input> without a programmatic label ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:288
- <input> without a programmatic label ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:387
- <input> without a programmatic label ui/src/dialogs/DocumentFolderDialog/DocumentFolderDialog.jsx:94
- Import cycle (2 files) ui/src/components/common/index.jsx:1
- Import cycle (2 files) ui/src/components/Timeline/EntityViewer2.tsx:4
- Import cycle (2 files) ui/src/dialogs/DocumentUploadDialog/DocumentUploadStatus.jsx:4
- Import cycle (2 files) ui/src/react-ftm/components/EntityTable/EntityTable.tsx:11
- Import cycle (2 files) ui/src/react-ftm/components/NetworkDiagram/toolbox/Sidebar.tsx:7
- Click handler on a non-interactive <div> ui/src/react-ftm/components/common/EditableProperty.tsx:65
- Click handler on a non-interactive <div> ui/src/react-ftm/components/common/EntityList.tsx:27
- Click handler on a non-interactive <div> ui/src/react-ftm/components/common/EntityList.tsx:35
- Click handler on a non-interactive <div> ui/src/react-ftm/editors/ColorPicker.tsx:81
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <select> without a programmatic label ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:186
- <select> without a programmatic label ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:308
- Banned license: zipstream-new
- Banned license: fuzzywuzzy
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Import cycle (4 files) ui/src/react-ftm/components/NetworkDiagram/GraphConfig.ts:2
- Import cycle (4 files) ui/src/react-ftm/types/EnumValue.tsx:2
- Link with no accessible name docs/src/components/Annotation.astro:37
- <button> with no accessible text ui/src/components/SearchAlert/SearchAlert.jsx:99
- <textarea> without a programmatic label ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:208
- Custom control with no accessible name on <path> ui/src/react-ftm/components/NetworkDiagram/renderer/EdgeRenderer.tsx:115
- Custom control with no accessible name on <div> ui/src/react-ftm/components/common/EntityList.tsx:35
- <html> without a lang ui/public/index.html:2
- Document without a <title> ui/public/index.html:2
- Click handler on a non-interactive <g> ui/src/react-ftm/components/NetworkDiagram/renderer/EdgeLabelRenderer.tsx:139
- Click handler on a non-interactive <path> ui/src/react-ftm/components/NetworkDiagram/renderer/EdgeRenderer.tsx:115
- Hover-only interaction on <g> ui/src/react-ftm/components/NetworkDiagram/renderer/GroupingRenderer.tsx:136
- Click handler on a non-interactive <text> ui/src/react-ftm/components/NetworkDiagram/renderer/VertexLabelRenderer.tsx:64
- Hover-only interaction on <circle> ui/src/react-ftm/components/NetworkDiagram/renderer/VertexRenderer.tsx:213
- No assertions (empty test): renders entity caption ui/src/components/Timeline/TimelineChart/TimelineChartItem.test.tsx:60
- REDACTED
- REDACTED
- REDACTED
- Unlisted import 'filesize' ui/src/react-ftm/types/FileSize.tsx:2
Serious — 328 finding(s)
- No test reaches this file ui/src/components/EntitySearch/FacetedEntitySearch.jsx:1
- No test reaches this file ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:1
- No test reaches this file ui/src/components/Entity/EntityViews.jsx:1
- No test reaches this file ui/src/dialogs/EntitySetCreateDialog/EntitySetCreateDialog.jsx:1
- No test reaches this file ui/src/components/EntityTable/EntityTable.jsx:1
- No test reaches this file ui/src/components/MappingEditor/MappingEditor.jsx:1
- No test reaches this file ui/src/dialogs/DocumentUploadDialog/DocumentUploadDialog.jsx:1
- No test reaches this file ui/src/screens/SystemStatusScreen/SystemStatusScreen.jsx:1
- No test reaches this file ui/src/components/MappingEditor/MappingKeyAssign.jsx:1
- No test reaches this file ui/src/viewers/PdfViewer.jsx:1
- No test reaches this file REDACTED:1
- No test reaches this file ui/src/components/AdvancedSearch/AdvancedSearch.jsx:1
- No test reaches this file ui/src/components/Navbar/Navbar.jsx:1
- No test reaches this file ui/src/components/MappingEditor/MappingManageMenu.jsx:1
- No test reaches this file ui/src/components/Facet/DateFacet.jsx:1
- No test reaches this file ui/src/components/MappingEditor/MappingPropertyAssign.jsx:1
- No test reaches this file ui/src/components/Entity/EntityReferencesMode.jsx:1
- No test reaches this file ui/src/dialogs/CollectionAccessDialog/CollectionAccessDialog.jsx:1
- No test reaches this file ui/src/components/Document/DocumentManager.jsx:1
- No test reaches this file ui/src/components/Facet/Facet.jsx:1
- No test reaches this file ui/src/components/Settings/ApiKeySettings.tsx:1
- No test reaches this file ui/src/screens/TimelineScreen/TimelineScreen.jsx:1
- No test reaches this file ui/src/components/MappingEditor/MappingVerify.jsx:1
- No test reaches this file ui/src/components/EntitySet/EntitySetSelector.jsx:1
- No test reaches this file ui/src/dialogs/CreateInvestigationDialog/CreateInvestigationDialog.jsx:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: CollectionEditDialog.render ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:144
- MethodTooLong: Navbar.render ui/src/components/Navbar/Navbar.jsx:91
- MethodTooLong: MappingEditor.render ui/src/components/MappingEditor/MappingEditor.jsx:145
- MethodTooLong: Toolbar.render ui/src/react-ftm/components/NetworkDiagram/toolbox/Toolbar.tsx:194
- MethodTooLong: NetworkDiagramBase.render ui/src/react-ftm/components/NetworkDiagram/NetworkDiagram.tsx:442
- MethodTooLong: EntitySetCreateDialog.render ui/src/dialogs/EntitySetCreateDialog/EntitySetCreateDialog.jsx:206
- MethodTooLong: InvestigationOverview.render ui/src/components/Investigation/InvestigationOverview.jsx:19
- MethodTooLong: FacetedEntitySearch.render ui/src/components/EntitySearch/FacetedEntitySearch.jsx:264
- MethodTooLong: CollectionInfo.render ui/src/components/Collection/CollectionInfo.jsx:8
- MethodTooLong: Dashboard.render ui/src/components/Dashboard/Dashboard.jsx:69
- MethodTooLong: EntityTable.render ui/src/components/EntityTable/EntityTable.jsx:191
- MethodTooLong: UnwrappedEdgeCreateDialog.render ui/src/react-ftm/components/common/EdgeCreateDialog.tsx:214
- MethodTooLong: HomeScreen.render ui/src/screens/HomeScreen/HomeScreen.jsx:75
- MethodTooLong: DocumentManager.render ui/src/components/Document/DocumentManager.jsx:110
- MethodTooLong: InvestigationQuickLinks.render ui/src/components/Investigation/InvestigationQuickLinks.jsx:72
- MethodTooLong: CollectionAccessDialog.render ui/src/dialogs/CollectionAccessDialog/CollectionAccessDialog.jsx:141
- TodoComment ui/src/react-ftm/components/NetworkDiagram/utils/filterVerticesByText.ts:10
- TodoComment ui/src/react-ftm/components/NetworkDiagram/layout/Edge.ts:95
- TodoComment ui/src/components/Timeline/Timeline.test.tsx:77
- TodoComment ui/src/components/Timeline/Timeline.test.tsx:119
- TodoComment ui/src/components/Timeline/Timeline.test.tsx:349
- TodoComment ui/src/components/Timeline/Timeline.test.tsx:409
- TodoComment ui/src/components/Timeline/TimelineItemCreateForm.test.tsx:25
- TodoComment e2e/models/investigations.py:42
- TodoComment contrib/play/tripler.py:27
- TodoComment aleph/model/collection.py:25
- TodoComment REDACTED:214
- TodoComment REDACTED:159
- TodoComment aleph/index/xref.py:32
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Animation without a prefers-reduced-motion guard ui/src/react-ftm/components/NetworkDiagram/toolbox/SearchBox.scss:22
- Animation without a prefers-reduced-motion guard ui/src/components/Investigation/InvestigationHeading.scss:41
- Animation without a prefers-reduced-motion guard ui/src/components/Investigation/InvestigationHeading.scss:55
- Animation without a prefers-reduced-motion guard ui/src/components/Facet/Facet.scss:30
- Animation without a prefers-reduced-motion guard ui/src/components/EntitySearch/FacetedEntitySearch.scss:76
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (16 lines × 2 locations) ui/src/dialogs/CollectionAccessDialog/CollectionAccessDialog.jsx:194
- Duplicated block (16 lines × 2 locations) ui/src/dialogs/CreateInvestigationDialog/CreateInvestigationDialog.jsx:158
- Duplicated block (16 lines × 2 locations) ui/src/dialogs/EntitySetCreateDialog/EntitySetCreateDialog.jsx:347
- Duplicated block (16 lines × 2 locations) ui/src/react-ftm/components/NetworkDiagram/layout/GraphLayout.ts:120
- Complex function render (cyclomatic 12, cognitive 11) ui/src/components/Dashboard/Dashboard.jsx:69
- Complex function render (cyclomatic 12, cognitive 11) ui/src/components/Document/DocumentManager.jsx:110
- Complex function render (cyclomatic 12, cognitive 11) ui/src/components/EntityTable/EntityTable.jsx:191
- Complex function render (cyclomatic 12, cognitive 11) ui/src/components/Navbar/Navbar.jsx:91
- Dead file (~3 LoC) ui/src/util/getEntitySetLink.js
- Dead file (~3 LoC) ui/src/util/normalizeDegreeValue.js
- Dead file (~3 LoC) ui/src/util/timestamp.js
- Dead file (~3 LoC) ui/src/util/validAlertQuery.js
- <PropertySelect> field component without a label ui/src/components/Timeline/EntityViewerProperties.tsx:82
- <PropertySelect> field component without a label ui/src/react-ftm/components/EntityTable/TableEditor.tsx:552
- <PropertySelect> field component without a label ui/src/react-ftm/components/NetworkDiagram/toolbox/EntityViewer.tsx:167
- Focus outline removed in CSS without a :focus replacement ui/src/react-ftm/editors/RadiusPicker.scss:23
- Focus outline removed in CSS without a :focus replacement ui/src/react-ftm/components/NetworkDiagram/NetworkDiagram.scss:47
- Focus outline removed in CSS without a :focus replacement ui/src/react-ftm/components/EntityTable/TableEditor.scss:77
- REDACTED
- REDACTED
- REDACTED
- TooManyMethods: GraphLayout ui/src/react-ftm/components/NetworkDiagram/layout/GraphLayout.ts:23
- TooManyMethods: Query ui/src/app/Query.js:6
- TooManyMethods: TableEditorBase ui/src/react-ftm/components/EntityTable/TableEditor.tsx:82
- Change coupling: index.js ↔ index.js ui/src/actions/index.js:1
- Change coupling: index.js ↔ selectors.js ui/src/reducers/index.js:1
- Change coupling: PdfViewer.jsx ↔ PdfViewerSearch.jsx ui/src/viewers/PdfViewer.jsx:1
- Untrusted text written into markup unescaped REDACTED:48
- Untrusted text written into markup unescaped ui/src/viewers/EmailViewer.jsx:83
- Untrusted text written into markup unescaped ui/src/viewers/HtmlViewer.jsx:14
- <ClipboardInput> field component without a label ui/src/components/Collection/CollectionReference.jsx:24
- <ClipboardInput> field component without a label ui/src/components/Collection/CollectionReference.jsx:36
- <SearchFieldSelect> field component without a label ui/src/components/EntitySearch/FacetedEntitySearch.jsx:241
- <SearchFieldSelect> field component without a label ui/src/components/EntitySearch/FacetedEntitySearch.jsx:371
- <SchemaSelect> field component without a label ui/src/react-ftm/components/EntityTable/EntityTable.tsx:161
- <SchemaSelect> field component without a label ui/src/react-ftm/components/common/EntityCreateDialog.tsx:201
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: PasswordSettings.PasswordSettings ui/src/components/Settings/PasswordSettings.jsx:17
- FunctionTooLong: PasswordAuth.PasswordAuth ui/src/components/auth/PasswordAuth.jsx:15
- REDACTED
- REDACTED
- Members sharing a duplicated core (5 members, 50+ identical tokens) aleph/migrate/versions/1519391870a0_create_diagram.py:18
- Members sharing a duplicated core (5 members, 50+ identical tokens) aleph/migrate/versions/1519391870a0_create_diagram.py:18
- Duplicated block with local edits (51 matched lines × 2 locations) ui/src/components/Entity/EntitySimilarMode.jsx:128
- Duplicated block with local edits (51 matched lines × 2 locations) ui/src/screens/ListScreen/ListScreen.jsx:24
- Duplicated block (25 lines × 2 locations) ui/src/react-ftm/components/NetworkDiagram/layout/tools/alignHorizontal.ts:13
- Duplicated block (25 lines × 2 locations) ui/src/screens/AlertsScreen/AlertsScreen.jsx:30
- Duplicated block (19 lines × 2 locations) ui/src/components/Investigation/InvestigationQuickLinks.jsx:146
- Duplicated block (19 lines × 2 locations) ui/src/components/Investigation/InvestigationSidebar.jsx:77
- Boundary violation [package:third-party-deep-import] ui/src/components/common/SignInCallout.jsx:5
- Boundary violation [package:third-party-deep-import] ui/src/components/common/Tag.jsx:2
- This package's lint script runs in no CI job docs/package.json:11
- This package's lint script runs in no CI job ui/package.json:65
- Dead file (~13 LoC) ui/src/testUtils.jsx
- Dead file (~13 LoC) ui/src/util/fetchCsvData.js
- Dead file (~8 LoC) ui/src/util/convertUTCDateToLocalDate.js
- Dead file (~8 LoC) ui/src/util/ensureArray.js
- Dead file (~6 LoC) ui/src/util/getCategoryLink.js
- Dead file (~6 LoC) ui/src/util/getProfileLink.js
- Swallowed exception (empty catch) ui/src/react-ftm/utils/validate.ts:53
- Swallowed exception (empty catch) ui/src/react-ftm/utils/validate.ts:64
- Swallowed exception (caught, then discarded) aleph/views/util.py:139
- Swallowed exception (caught, then discarded) aleph/model/document.py:161
- <video> without a captions track ui/src/viewers/VideoViewer.jsx:13
- <SortingBarSelect> field component without a label ui/src/components/SortingBar/SortingBar.jsx:103
- <VLEntitySelect> field component without a label ui/src/components/common/EntitySelect.jsx:13
- <Select> field component without a label ui/src/components/common/EntitySet.jsx:80
- <EntitySelect> field component without a label ui/src/react-ftm/components/common/EntityCreateDialog.tsx:217
- <Slider> field component without a label ui/src/react-ftm/editors/RadiusPicker.tsx:32
- <TextArea> field component without a label ui/src/react-ftm/editors/TextEdit.tsx:117
- <TagInput> field component without a label ui/src/react-ftm/editors/TextEdit.tsx:151
- entityEditorWrapper.entityEditorWrapper (cyclomatic 20) ui/src/components/Entity/entityEditorWrapper.jsx:27
- CollectionInfo.render (cyclomatic 18) ui/src/components/Collection/CollectionInfo.jsx:8
- PropertyValue.render (cyclomatic 18) ui/src/react-ftm/types/Property.tsx:104
- GroupingRenderer.render (cyclomatic 17) ui/src/react-ftm/components/NetworkDiagram/renderer/GroupingRenderer.tsx:92
- validate.validate (cyclomatic 17) ui/src/react-ftm/utils/validate.ts:72
- Facet.render (cyclomatic 16) ui/src/components/Facet/Facet.jsx:151
- CollectionEditDialog.render (cyclomatic 16) ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:144
- FixmeComment aleph/logic/expand.py:201
- GraphLayout.generate (cognitive 30) ui/src/react-ftm/components/NetworkDiagram/layout/GraphLayout.ts:106
- Query.get_aggregations (cognitive 26) aleph/search/query.py:138
- entitysets.replace_layout_ids (cognitive 25) aleph/logic/entitysets.py:64
- util.filter_text (cognitive 21) aleph/index/util.py:144
- entityEditorWrapper.entityEditorWrapper (cognitive 21) ui/src/components/Entity/entityEditorWrapper.jsx:27
- validate.validate (cognitive 21) ui/src/react-ftm/utils/validate.ts:72
- profiles.get_profile (cognitive 20) aleph/logic/profiles.py:34
- expand._counted_msearch (cognitive 19) aleph/logic/expand.py:147
- PropertyValue.render (cognitive 19) ui/src/react-ftm/types/Property.tsx:104
- entities.entities_by_ids (cognitive 18) aleph/index/entities.py:112
- EntitySerializer._serialize (cognitive 18) aleph/views/serializers.py:209
- tripler.export_entity (cognitive 17) contrib/play/tripler.py:19
- matching.match_query (cognitive 16) aleph/logic/matching.py:43
- DocumentViewMode.renderContent (cognitive 16) ui/src/components/Document/DocumentViewMode.jsx:26
- state.reducer (cognitive 16) ui/src/components/Timeline/state.ts:97
- Toolbar.render (cognitive 16) ui/src/react-ftm/components/NetworkDiagram/toolbox/Toolbar.tsx:194
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- ClassTooLong: TableEditorBase ui/src/react-ftm/components/EntityTable/TableEditor.tsx:82
- FileTooLong: EntityTable/TableEditor.tsx ui/src/react-ftm/components/EntityTable/TableEditor.tsx
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (18 corresponding lines) aleph/views/reconcile_api.py:206
- Edited copies of one member (3 members, 22+ corresponding lines) aleph/metrics/collectors.py:86
- Edited copy of a member (59 corresponding lines) aleph/views/entities_api.py:512
- Edited copy of a member (10 corresponding lines) aleph/manage.py:446
- Edited copy of a member (9 corresponding lines) REDACTED:108
- Edited copy of a member (40 corresponding lines) aleph/views/mappings_api.py:111
- Edited copies of one member (4 members, 3+ corresponding lines) aleph/model/document.py:105
- Duplicated block (17 lines × 2) aleph/migrate/versions/aac638b04072_add_linkage.py:28
- Duplicated block (13–16 lines × 6) aleph/migrate/versions/1519391870a0_create_diagram.py:31
- Duplicated block (15 lines × 2) aleph/metrics/collectors.py:118
- Duplicated block (9–14 lines × 7) aleph/migrate/versions/1519391870a0_create_diagram.py:34
- Duplicated block (9 lines × 3) aleph/migrate/versions/af9b37868cf3_init.py:50
- Duplicated block (6 lines × 2) aleph/manage.py:450
- Duplicated block (5 lines × 6) aleph/migrate/versions/1519391870a0_create_diagram.py:18
- Duplicated block (5 lines × 5) aleph/migrate/versions/5b681871c1ab_introduce_export_model.py:19
- Duplicated block (5 lines × 2) aleph/migrate/versions/aac638b04072_add_linkage.py:17
- Duplicated block (25 lines × 2) aleph/views/alerts_api.py:16
- Edited copy of a member (17 corresponding lines) contrib/email/generate_test_emails.py:72
- No DR/backup evidence
- Outbound HTTP without resilience contrib/play/esnames.py:26
- Type Safety
- Duplication concentrated across 5 sibling directories (40 clone groups) ui/src/components/Collection/CollectionXrefMode.jsx:41
- Duplication concentrated across 22 sibling directories (40 clone groups) ui/src/components/Entity/EntitySimilarMode.jsx:128
- Duplication concentrated across 16 sibling directories (15 clone groups) ui/src/dialogs/EntitySetCreateDialog/EntitySetCreateDialog.jsx:82
- Duplication concentrated across 12 sibling directories (10 clone groups) ui/src/screens/ListScreen/ListScreen.jsx:24
- Duplicated block with local edits (103 matched lines × 2 locations) ui/src/dialogs/EntitySetCreateDialog/EntitySetCreateDialog.jsx:82
- Duplicated block with local edits (100 matched lines × 2 locations) ui/src/components/Profile/ProfileItemsMode.jsx:23
- Duplicated block with local edits (81 matched lines × 2 locations) ui/src/react-ftm/components/NetworkDiagram/renderer/GroupingRenderer.tsx:19
- Duplicated block with local edits (64 matched lines × 2 locations) ui/src/dialogs/CollectionDeleteDialog/CollectionDeleteDialog.jsx:11
- Duplicated block (62 lines × 2 locations) ui/src/components/Collection/CollectionReindexAlert.jsx:20
- Duplicated block with local edits (49 matched lines × 2 locations) ui/src/react-ftm/components/NetworkDiagram/layout/Edge.ts:29
- Duplicated block with local edits (39 matched lines × 2 locations) ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:353
- Duplicated block (34 lines × 2 locations) ui/src/react-ftm/components/common/EdgeCreateDialog.tsx:239
- Duplicated block (30 lines × 2 locations) ui/src/dialogs/EntitySetDeleteDialog/EntitySetDeleteDialog.jsx:42
- Duplicated block with local edits (30 matched lines × 2 locations) ui/src/viewers/ArticleViewer.jsx:9
- Duplicated block (29 lines × 2 locations) ui/src/components/Investigation/InvestigationQuickLinks.jsx:84
- Duplicated block with local edits (28 matched lines × 2 locations) ui/src/components/Settings/NotificationSettings.jsx:9
- Duplicated block (26 lines × 2 locations) ui/src/components/Entity/EntitySimilarMode.jsx:76
- Duplicated block (23 lines × 4 locations) ui/src/dialogs/MappingCreateDialog/MappingCreateDialog.jsx:13
- Duplicated block with local edits (21 matched lines × 2 locations) ui/src/components/Collection/CollectionMappingsMode.jsx:44
- Duplicated block (20 lines × 2 locations) ui/src/screens/HomeScreen/HomeScreen.jsx:157
- Duplicated block (19 lines × 3 locations) ui/src/dialogs/MappingCreateDialog/MappingCreateDialog.jsx:22
- Duplicated block (18 lines × 5 locations) ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:158
- Duplicated block with local edits (17 matched lines × 2 locations) ui/src/components/AuthButtons/AuthButtons.jsx:104
- Duplicated block (17 lines × 4 locations) ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:231
- Duplicated block (17 lines × 2 locations) ui/src/queries.js:175
- Duplicated block (16 lines × 4 locations) ui/src/components/common/LandingQuickLinks.jsx:14
- Duplicated block with local edits (16 matched lines × 2 locations) ui/src/react-ftm/components/NetworkDiagram/dialogs/SettingsDialog.tsx:124
- Duplicated block (15 lines × 3 locations) ui/src/components/Entity/EntityTagsMode.jsx:81
- Duplicated block (15 lines × 2 locations) ui/src/components/Exports/Export.jsx:15
- Duplicated block (14 lines × 3 locations) ui/src/actions/entityActions.js:16
- Complex function render (cyclomatic 18, cognitive 13) ui/src/components/Collection/CollectionInfo.jsx:8
- Complex function validate (cyclomatic 17, cognitive 21) ui/src/react-ftm/utils/validate.ts:72
- Complex function render (cyclomatic 16, cognitive 13) ui/src/components/Facet/Facet.jsx:151
- Complex function renderContent (cyclomatic 15, cognitive 16) ui/src/components/Document/DocumentViewMode.jsx:26
- Complex function render (cyclomatic 15, cognitive 14) ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:144
- Complex function reducer (cyclomatic 13, cognitive 16) ui/src/components/Timeline/state.ts:97
- Complex function render (cyclomatic 13, cognitive 12) ui/src/components/Screen/Screen.jsx:35
- Complex function getParam (cyclomatic 11, cognitive 14) ui/src/components/Notification/Notification.jsx:17
- Complex function getSortValue (cyclomatic 11, cognitive 12) ui/src/react-ftm/types/Property.tsx:79
- Complex function filterDateIntervals (cyclomatic 11, cognitive 9) ui/src/components/Facet/util.js:54
- ui/src/react-ftm/components/EntityTable/TableEditor.tsx: 695 lines of code ui/src/react-ftm/components/EntityTable/TableEditor.tsx:1
- ui/src/react-ftm/components/NetworkDiagram/NetworkDiagram.tsx: 541 lines of code ui/src/react-ftm/components/NetworkDiagram/NetworkDiagram.tsx:1
- ui/src/react-ftm/components/NetworkDiagram/layout/GraphLayout.ts: 481 lines of code ui/src/react-ftm/components/NetworkDiagram/layout/GraphLayout.ts:1
- ui/src/selectors.js: 417 lines of code ui/src/selectors.js:1
- ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx: 416 lines of code ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:1
- ui/src/components/EntitySearch/FacetedEntitySearch.jsx: 409 lines of code ui/src/components/EntitySearch/FacetedEntitySearch.jsx:1
- No typecheck script
- Type errors in this package cannot fail any build or CI step ui/package.json:65
- Dead file (~295 LoC) ui/src/viewers/PdfViewer.jsx
- Dead file (~141 LoC) ui/src/components/Investigation/InvestigationSidebar.jsx
- Dead file (~86 LoC) ui/src/components/Exports/ExportsList.jsx
- Dead file (~64 LoC) ui/src/components/Investigation/InvestigationHeading.jsx
- Dead file (~60 LoC) ui/src/viewers/PdfViewerPage.jsx
- Dead file (~57 LoC) ui/src/components/Exports/Export.jsx
- Dead file (~43 LoC) ui/src/screens/ExportsScreen/ExportsScreen.jsx
- Dead file (~34 LoC) ui/src/util/pdfFragId.js
- Dead file (~30 LoC) ui/src/util/togglePreview.js
- Dead file (~24 LoC) ui/src/util/convertPathsToTree.js
- Dead file (~16 LoC) ui/src/util/getCollectionLink.js
- Dead file (~14 LoC) ui/src/reducers/similar.js
- Dead file (~12 LoC) ui/src/util/getValueLink.js
- Dead file (~10 LoC) ui/src/util/getEntityLink.js
- Dead file (~9 LoC) ui/src/util/wordList.js
- Dead file (~5 LoC) ui/src/components/Entity/index.jsx
- Unused dependency 'crypto' ui/package.json:21
- Unused dependency 'stream' ui/package.json:53
- Recursive walk over a caller-supplied document has no depth cap ui/src/react-ftm/components/NetworkDiagram/toolbox/ToolbarButtonGroup.tsx:92
- Option is kept and never read ui/src/actions/util.js:21
Minor — 320 finding(s)
- Orphaned file ui/src/react-ftm/components/NetworkDiagram/NetworkDiagram.tsx:1
- Orphaned file aleph/manage.py:1
- Orphaned file aleph/views/serializers.py:1
- Orphaned file ui/src/react-ftm/components/NetworkDiagram/layout/GraphLayout.ts:1
- Orphaned file ui/src/dialogs/CollectionEditDialog/CollectionEditDialog.jsx:1
- Orphaned file aleph/model/entityset.py:1
- Orphaned file ui/src/selectors.js:1
- Orphaned file aleph/views/entitysets_api.py:1
- Orphaned file ui/src/components/EntitySearch/FacetedEntitySearch.jsx:1
- Orphaned file aleph/logic/xref.py:1
- Orphaned file aleph/views/collections_api.py:1
- Orphaned file aleph/index/util.py:1
- Orphaned file ui/src/react-ftm/components/NetworkDiagram/toolbox/Toolbar.tsx:1
- Orphaned file ui/src/react-ftm/components/NetworkDiagram/renderer/Canvas.tsx:1
- Orphaned file ui/src/dialogs/EntitySetCreateDialog/EntitySetCreateDialog.jsx:1
- Orphaned file aleph/search/query.py:1
- Orphaned file REDACTED:1
- Orphaned file ui/src/components/MappingEditor/MappingEditor.jsx:1
- Orphaned file aleph/model/collection.py:1
- Orphaned file ui/src/components/Entity/EntityViews.jsx:1
- Orphaned file REDACTED:1
- Orphaned file ui/src/components/EntityTable/EntityTable.jsx:1
- Orphaned file aleph/views/mappings_api.py:1
- Orphaned file ui/src/react-ftm/components/common/EdgeCreateDialog.tsx:1
- Orphaned file aleph/worker.py:1
- Interpolated log message defeats structured logging aleph/worker.py:51
- Interpolated log message defeats structured logging aleph/worker.py:62
- Interpolated log message defeats structured logging aleph/worker.py:170
- Interpolated log message defeats structured logging aleph/worker.py:202
- Interpolated log message defeats structured logging aleph/worker.py:212
- Interpolated log message defeats structured logging aleph/worker.py:247
- Interpolated log message defeats structured logging aleph/views/serializers.py:100
- Interpolated log message defeats structured logging REDACTED:134
- Interpolated log message defeats structured logging REDACTED:93
- Interpolated log message defeats structured logging REDACTED:133
- Interpolated log message defeats structured logging REDACTED:134
- Interpolated log message defeats structured logging aleph/logic/collections.py:149
- Interpolated log message defeats structured logging aleph/logic/xref.py:270
- Interpolated log message defeats structured logging aleph/logic/xref.py:273
- Interpolated log message defeats structured logging aleph/logic/xref.py:278
- Interpolated log message defeats structured logging aleph/index/util.py:306
- Interpolated log message defeats structured logging aleph/index/util.py:310
- Interpolated log message defeats structured logging aleph/index/util.py:314
- Interpolated log message defeats structured logging aleph/index/util.py:315
- Interpolated log message defeats structured logging aleph/index/util.py:318
- Interpolated log message defeats structured logging aleph/index/util.py:325
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Blanket warning suppression ui/src/components/auth/PasswordAuth.jsx:13
- Blanket warning suppression ui/src/dialogs/CreateInvestigationDialog/CreateInvestigationDialog.jsx:41
- Blanket warning suppression ui/src/dialogs/EntitySetCreateDialog/EntitySetCreateDialog.jsx:325
- Projects may be oversized for their cohesion ui/package.json:1
- Projects may be oversized for their cohesion setup.py:1
- Most significant orphaned file ui/src/react-ftm/components/EntityTable/TableEditor.tsx:1
- Most significant orphaned file aleph/views/entities_api.py:1
- Duplicated predicate ui/src/components/Timeline/TimelineChart/TimelineChartLabels.tsx:26
- Duplicated predicate aleph/model/collection.py:207
- No ADRs found setup.py:23
- REDACTED
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No network policy
- No ADRs
- No SAST REDACTED:4
- Unused export 'fetchExports' ui/src/actions/exportActions.js:5
- Unused export 'triggerQueryExport' ui/src/actions/exportActions.js:14
- Unused export 'TimelineEntity' ui/src/components/Timeline/types.ts:8
- Unused export 'default' ui/src/react-ftm/types/MIMEType.tsx:56
- Unused export 'showInfoToast' ui/src/react-ftm/utils/toaster.ts:15
- Unused export 'checkEntityRequiredProps' ui/src/react-ftm/utils/validate.ts:115
- Unused export 'objectReload' ui/src/reducers/util.js:105
- Unused export 'selectEntitySets' ui/src/selectors.js:201
- Unused export 'selectDocumentContent' ui/src/selectors.js:283
- Unused export 'selectCollectionXref' ui/src/selectors.js:439
- Unused export 'selectQueryLogsLimited' ui/src/selectors.js:464
- Unused export 'selectConfigValue' ui/src/selectors.js:493
- Unused export 'encode' ui/src/util/htmlEntities.js:20
- Security headers incomplete ui/nginx.conf:25
- Null assertions (`!`) override strict null checking
- Silent fallback default in catch aleph/views/util.py:139
Minor — 32 finding(s)
- Outdated: alembic
- Outdated: apispec
- Outdated: apispec-webframeworks
- Outdated: authlib
- Outdated: babel
- Outdated: banal
- Outdated: blinker
- Outdated: elasticsearch
- Outdated: fingerprints
- Outdated: flask
- Outdated: flask-cors
- Outdated: flask-mail
- Outdated: flask-migrate
- Outdated: flask-sqlalchemy
- Outdated: followthemoney
- Outdated: gunicorn
- Outdated: jsonschema
- Outdated: lxml
- Outdated: lxml-html-clean
- Outdated: marshmallow
- Outdated: normality
- Outdated: pika
- Outdated: prometheus-client
- Outdated: pyicu
- Outdated: pytest
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-697ec0681eb14384a13b90c9849c9097/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-697ec0681eb14384a13b90c9849c9097/history-1.json --exit-code 0 --source . | 0 | 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=3200" --report-format json --report-path /tmp/watchdog-gitleaks-697ec0681eb14384a13b90c9849c9097/history-2.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=7394" --report-format json --report-path /tmp/watchdog-gitleaks-697ec0681eb14384a13b90c9849c9097/history-3.json --exit-code 0 --source . | 8 | artifacts/raw/gitleaks-history-3.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-697ec0681eb14384a13b90c9849c9097/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 . | 47 | 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/** . | 76 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 42 | 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 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess. | 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 |