Executive summary
antvis/G6 falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 38.6 out of 100 and is rated Weak, and 50 of its 61 critical findings are security problems.
Security and Compliance, at 33.4, is the weakest lens and counts most in the score. The best first step is adding a reporting contact to the security policy, worth about 2.9 points. Fixing the four pipeline jobs with more access than they need would lift Security and Compliance itself, worth about 1.9 points. Raising Security and Compliance to 70 would lift the score to about 43.3.
Thirty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fourteen secrets can leak from the build pipeline, and two weaknesses in the code could be used by an attacker. Pinning each tool to an exact version, limiting each secret to its own step and fixing the weaknesses the scanner points to would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the password or key in the code's history needs replacing, with the old one switched off. The three parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.
The product code is 52,275 lines, about €67,000 to rebuild.
If Security and Compliance rose from 33.4 to 70, the lowest score rated Strong, the score would rise from 38.6 to about 43.3.
Rebuild cost: about €67,000 · Estimate
| Cost to rebuild | €22,000 to €110,000, for 371 to 1,177 hours of work, about 0.5 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 39. 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: 52,275 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 g6-ssr.src.types | 2 g6.src.elements.shapes.base-shape | 3 g6.src.types.data | 4 g6.src.types.padding | 5 g6.src.types.placement | 6 g6.src.types.point | 7 g6.src.types.size | 8 g6.src.types.vector | 9 g6.src.utils.shortcut | 10 g6.src.runtime.canvas | 11 g6.src.types.node | 12 g6.src.types.viewport | 13 g6.src.types.element | 14 g6.src.elements.edges.base-edge | 15 g6.src.elements.nodes.base-node | 16 g6.src.runtime.data | 17 g6.src.types.event | 18 g6-extension-3d.src.elements.base-node-3d | 19 g6.src.elements.combos.base-combo | 20 g6.src.elements.nodes.circle | 21 g6.src.elements.shapes.polygon | 22 g6.src.utils.event.events | 23 g6.src.runtime.element | 24 g6.src.runtime.types | 25 g6.src.layouts.base-layout | 26 g6.src.registry.extension | 27 g6.src.runtime.graph | 28 g6.src.behaviors.base-behavior | 29 g6.src.plugins.base-plugin | 30 g6.src.transforms.base-transform | 31 g6.src.utils | 32 g6.src.behaviors.auto-adapt-label | 33 g6.src.behaviors.brush-select | 34 g6.src.behaviors.click-select | 35 g6.src.behaviors.drag-canvas | 36 g6.src.behaviors.drag-element | 37 g6.src.behaviors.zoom-canvas | 38 g6.src.plugins.edge-filter-lens | 39 g6.src.plugins.hull | 40 g6.src.plugins.minimap |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 g6-ssr.src.types | ||||||||||||||||||||||||||||||||||||||||
| 2 g6.src.elements.shapes.base-shape | ||||||||||||||||||||||||||||||||||||||||
| 3 g6.src.types.data | ||||||||||||||||||||||||||||||||||||||||
| 4 g6.src.types.padding | ||||||||||||||||||||||||||||||||||||||||
| 5 g6.src.types.placement | ||||||||||||||||||||||||||||||||||||||||
| 6 g6.src.types.point | ||||||||||||||||||||||||||||||||||||||||
| 7 g6.src.types.size | ||||||||||||||||||||||||||||||||||||||||
| 8 g6.src.types.vector | ||||||||||||||||||||||||||||||||||||||||
| 9 g6.src.utils.shortcut | ||||||||||||||||||||||||||||||||||||||||
| 10 g6.src.runtime.canvas | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 g6.src.types.node | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 g6.src.types.viewport | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 g6.src.types.element | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 g6.src.elements.edges.base-edge | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 g6.src.elements.nodes.base-node | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 16 g6.src.runtime.data | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 g6.src.types.event | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 g6-extension-3d.src.elements.base-node-3d | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 g6.src.elements.combos.base-combo | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 20 g6.src.elements.nodes.circle | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 g6.src.elements.shapes.polygon | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 g6.src.utils.event.events | 1 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 23 g6.src.runtime.element | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 g6.src.runtime.types | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 g6.src.layouts.base-layout | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 g6.src.registry.extension | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 g6.src.runtime.graph | 2 | 1 | 2 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 28 g6.src.behaviors.base-behavior | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 g6.src.plugins.base-plugin | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 g6.src.transforms.base-transform | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 g6.src.utils | 2 | 1 | 8 | 2 | 3 | 6 | 4 | 2 | 5 | 1 | 4 | 1 | 1 | 1 | ||||||||||||||||||||||||||
| 32 g6.src.behaviors.auto-adapt-label | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 33 g6.src.behaviors.brush-select | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 34 g6.src.behaviors.click-select | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 g6.src.behaviors.drag-canvas | 1 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 36 g6.src.behaviors.drag-element | 1 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 37 g6.src.behaviors.zoom-canvas | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 38 g6.src.plugins.edge-filter-lens | 1 | 1 | 1 | 2 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 39 g6.src.plugins.hull | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 g6.src.plugins.minimap | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
10→6 g6.src.runtime.canvas uses g6.src.types.point✕
- Connections
- 1 pair of types, where a type in g6.src.runtime.canvas uses a type in g6.src.types.point.
- The types involved
packages.g6.src.runtime.canvas.Canvas→packages.g6.src.types.point.Point
- Direction
- g6.src.runtime.canvas uses g6.src.types.point, so a change to g6.src.types.point can break g6.src.runtime.canvas, while a change to g6.src.runtime.canvas can't break g6.src.types.point.
- Position
- Below the diagonal: g6.src.runtime.canvas uses a module listed above it, which is the healthy direction.
11→5 g6.src.types.node uses g6.src.types.placement✕
- Connections
- 2 pairs of types, where a type in g6.src.types.node uses a type in g6.src.types.placement.
- The types involved
packages.g6.src.types.node.NodeLabelStyleProps→packages.g6.src.types.placement.DirectionalPlacementpackages.g6.src.types.node.NodePortStyleProps→packages.g6.src.types.placement.Placement
- Direction
- g6.src.types.node uses g6.src.types.placement, so a change to g6.src.types.placement can break g6.src.types.node, while a change to g6.src.types.node can't break g6.src.types.placement.
- Position
- Below the diagonal: g6.src.types.node uses a module listed above it, which is the healthy direction.
12→6 g6.src.types.viewport uses g6.src.types.point✕
- Connections
- 1 pair of types, where a type in g6.src.types.viewport uses a type in g6.src.types.point.
- The types involved
packages.g6.src.types.viewport.TransformOptions→packages.g6.src.types.point.Point
- Direction
- g6.src.types.viewport uses g6.src.types.point, so a change to g6.src.types.point can break g6.src.types.viewport, while a change to g6.src.types.viewport can't break g6.src.types.point.
- Position
- Below the diagonal: g6.src.types.viewport uses a module listed above it, which is the healthy direction.
13→6 g6.src.types.element uses g6.src.types.point✕
- Connections
- 2 pairs of types, where a type in g6.src.types.element uses a type in g6.src.types.point.
- The types involved
packages.g6.src.types.element.Combo→packages.g6.src.types.point.Pointpackages.g6.src.types.element.Node→packages.g6.src.types.point.Point
- Direction
- g6.src.types.element uses g6.src.types.point, so a change to g6.src.types.point can break g6.src.types.element, while a change to g6.src.types.element can't break g6.src.types.point.
- Position
- Below the diagonal: g6.src.types.element uses a module listed above it, which is the healthy direction.
13→11 g6.src.types.element uses g6.src.types.node✕
- Connections
- 1 pair of types, where a type in g6.src.types.element uses a type in g6.src.types.node.
- The types involved
packages.g6.src.types.element.Node→packages.g6.src.types.node.Port
- Direction
- g6.src.types.element uses g6.src.types.node, so a change to g6.src.types.node can break g6.src.types.element, while a change to g6.src.types.element can't break g6.src.types.node.
- Position
- Below the diagonal: g6.src.types.element uses a module listed above it, which is the healthy direction.
14→13 g6.src.elements.edges.base-edge uses g6.src.types.element✕
- Connections
- 1 pair of types, where a type in g6.src.elements.edges.base-edge uses a type in g6.src.types.element.
- The types involved
packages.g6.src.elements.edges.base-edge.BaseEdge→packages.g6.src.types.element.Edge
- Direction
- g6.src.elements.edges.base-edge uses g6.src.types.element, so a change to g6.src.types.element can break g6.src.elements.edges.base-edge, while a change to g6.src.elements.edges.base-edge can't break g6.src.types.element.
- Position
- Below the diagonal: g6.src.elements.edges.base-edge uses a module listed above it, which is the healthy direction.
15→6 g6.src.elements.nodes.base-node uses g6.src.types.point✕
- Connections
- 1 pair of types, where a type in g6.src.elements.nodes.base-node uses a type in g6.src.types.point.
- The types involved
packages.g6.src.elements.nodes.base-node.BaseNode→packages.g6.src.types.point.Point
- Direction
- g6.src.elements.nodes.base-node uses g6.src.types.point, so a change to g6.src.types.point can break g6.src.elements.nodes.base-node, while a change to g6.src.elements.nodes.base-node can't break g6.src.types.point.
- Position
- Below the diagonal: g6.src.elements.nodes.base-node uses a module listed above it, which is the healthy direction.
15→7 g6.src.elements.nodes.base-node uses g6.src.types.size✕
- Connections
- 1 pair of types, where a type in g6.src.elements.nodes.base-node uses a type in g6.src.types.size.
- The types involved
packages.g6.src.elements.nodes.base-node.BaseNodeStyleProps→packages.g6.src.types.size.Size
- Direction
- g6.src.elements.nodes.base-node uses g6.src.types.size, so a change to g6.src.types.size can break g6.src.elements.nodes.base-node, while a change to g6.src.elements.nodes.base-node can't break g6.src.types.size.
- Position
- Below the diagonal: g6.src.elements.nodes.base-node uses a module listed above it, which is the healthy direction.
15→11 g6.src.elements.nodes.base-node uses g6.src.types.node✕
- Connections
- 3 pairs of types, where a type in g6.src.elements.nodes.base-node uses a type in g6.src.types.node.
- The types involved
packages.g6.src.elements.nodes.base-node.BaseNode→packages.g6.src.types.node.NodeBadgeStylePropspackages.g6.src.elements.nodes.base-node.BaseNode→packages.g6.src.types.node.NodePortStylePropspackages.g6.src.elements.nodes.base-node.BaseNode→packages.g6.src.types.node.Port
- Direction
- g6.src.elements.nodes.base-node uses g6.src.types.node, so a change to g6.src.types.node can break g6.src.elements.nodes.base-node, while a change to g6.src.elements.nodes.base-node can't break g6.src.types.node.
- Position
- Below the diagonal: g6.src.elements.nodes.base-node uses a module listed above it, which is the healthy direction.
15→13 g6.src.elements.nodes.base-node uses g6.src.types.element✕
- Connections
- 1 pair of types, where a type in g6.src.elements.nodes.base-node uses a type in g6.src.types.element.
- The types involved
packages.g6.src.elements.nodes.base-node.BaseNode→packages.g6.src.types.element.Node
- Direction
- g6.src.elements.nodes.base-node uses g6.src.types.element, so a change to g6.src.types.element can break g6.src.elements.nodes.base-node, while a change to g6.src.elements.nodes.base-node can't break g6.src.types.element.
- Position
- Below the diagonal: g6.src.elements.nodes.base-node uses a module listed above it, which is the healthy direction.
16→3 g6.src.runtime.data uses g6.src.types.data✕
- Connections
- 4 pairs of types, where a type in g6.src.runtime.data uses a type in g6.src.types.data.
- The types involved
packages.g6.src.runtime.data.DataController→packages.g6.src.types.data.ElementDatumpackages.g6.src.runtime.data.DataController→packages.g6.src.types.data.HierarchyKeypackages.g6.src.runtime.data.DataController→packages.g6.src.types.data.NodeLikeDatapackages.g6.src.runtime.data.DataController→packages.g6.src.types.data.PartialEdgeData
- Direction
- g6.src.runtime.data uses g6.src.types.data, so a change to g6.src.types.data can break g6.src.runtime.data, while a change to g6.src.runtime.data can't break g6.src.types.data.
- Position
- Below the diagonal: g6.src.runtime.data uses a module listed above it, which is the healthy direction.
16→6 g6.src.runtime.data uses g6.src.types.point✕
- Connections
- 1 pair of types, where a type in g6.src.runtime.data uses a type in g6.src.types.point.
- The types involved
packages.g6.src.runtime.data.DataController→packages.g6.src.types.point.Point
- Direction
- g6.src.runtime.data uses g6.src.types.point, so a change to g6.src.types.point can break g6.src.runtime.data, while a change to g6.src.runtime.data can't break g6.src.types.point.
- Position
- Below the diagonal: g6.src.runtime.data uses a module listed above it, which is the healthy direction.
16→13 g6.src.runtime.data uses g6.src.types.element✕
- Connections
- 1 pair of types, where a type in g6.src.runtime.data uses a type in g6.src.types.element.
- The types involved
packages.g6.src.runtime.data.DataController→packages.g6.src.types.element.ElementType
- Direction
- g6.src.runtime.data uses g6.src.types.element, so a change to g6.src.types.element can break g6.src.runtime.data, while a change to g6.src.runtime.data can't break g6.src.types.element.
- Position
- Below the diagonal: g6.src.runtime.data uses a module listed above it, which is the healthy direction.
17→3 g6.src.types.event uses g6.src.types.data✕
- Connections
- 1 pair of types, where a type in g6.src.types.event uses a type in g6.src.types.data.
- The types involved
packages.g6.src.types.event.IElementLifeCycleEvent→packages.g6.src.types.data.ElementDatum
- Direction
- g6.src.types.event uses g6.src.types.data, so a change to g6.src.types.data can break g6.src.types.event, while a change to g6.src.types.event can't break g6.src.types.data.
- Position
- Below the diagonal: g6.src.types.event uses a module listed above it, which is the healthy direction.
17→12 g6.src.types.event uses g6.src.types.viewport✕
- Connections
- 1 pair of types, where a type in g6.src.types.event uses a type in g6.src.types.viewport.
- The types involved
packages.g6.src.types.event.IViewportEvent→packages.g6.src.types.viewport.TransformOptions
- Direction
- g6.src.types.event uses g6.src.types.viewport, so a change to g6.src.types.viewport can break g6.src.types.event, while a change to g6.src.types.event can't break g6.src.types.viewport.
- Position
- Below the diagonal: g6.src.types.event uses a module listed above it, which is the healthy direction.
17→13 g6.src.types.event uses g6.src.types.element✕
- Connections
- 1 pair of types, where a type in g6.src.types.event uses a type in g6.src.types.element.
- The types involved
packages.g6.src.types.event.IElementLifeCycleEvent→packages.g6.src.types.element.ElementType
- Direction
- g6.src.types.event uses g6.src.types.element, so a change to g6.src.types.element can break g6.src.types.event, while a change to g6.src.types.event can't break g6.src.types.element.
- Position
- Below the diagonal: g6.src.types.event uses a module listed above it, which is the healthy direction.
18→15 g6-extension-3d.src.elements.base-node-3d uses g6.src.elements.nodes.base-node✕
- Connections
- 1 pair of types, where a type in g6-extension-3d.src.elements.base-node-3d uses a type in g6.src.elements.nodes.base-node.
- The types involved
packages.g6-extension-3d.src.elements.base-node-3d.BaseNode3D→packages.g6.src.elements.nodes.base-node.BaseNode
- Direction
- g6-extension-3d.src.elements.base-node-3d uses g6.src.elements.nodes.base-node, so a change to g6.src.elements.nodes.base-node can break g6-extension-3d.src.elements.base-node-3d, while a change to g6-extension-3d.src.elements.base-node-3d can't break g6.src.elements.nodes.base-node.
- Position
- Below the diagonal: g6-extension-3d.src.elements.base-node-3d uses a module listed above it, which is the healthy direction.
19→4 g6.src.elements.combos.base-combo uses g6.src.types.padding✕
- Connections
- 1 pair of types, where a type in g6.src.elements.combos.base-combo uses a type in g6.src.types.padding.
- The types involved
packages.g6.src.elements.combos.base-combo.BaseComboStyleProps→packages.g6.src.types.padding.Padding
- Direction
- g6.src.elements.combos.base-combo uses g6.src.types.padding, so a change to g6.src.types.padding can break g6.src.elements.combos.base-combo, while a change to g6.src.elements.combos.base-combo can't break g6.src.types.padding.
- Position
- Below the diagonal: g6.src.elements.combos.base-combo uses a module listed above it, which is the healthy direction.
19→6 g6.src.elements.combos.base-combo uses g6.src.types.point✕
- Connections
- 1 pair of types, where a type in g6.src.elements.combos.base-combo uses a type in g6.src.types.point.
- The types involved
packages.g6.src.elements.combos.base-combo.BaseCombo→packages.g6.src.types.point.Point
- Direction
- g6.src.elements.combos.base-combo uses g6.src.types.point, so a change to g6.src.types.point can break g6.src.elements.combos.base-combo, while a change to g6.src.elements.combos.base-combo can't break g6.src.types.point.
- Position
- Below the diagonal: g6.src.elements.combos.base-combo uses a module listed above it, which is the healthy direction.
19→7 g6.src.elements.combos.base-combo uses g6.src.types.size✕
- Connections
- 2 pairs of types, where a type in g6.src.elements.combos.base-combo uses a type in g6.src.types.size.
- The types involved
packages.g6.src.elements.combos.base-combo.BaseCombo→packages.g6.src.types.size.STDSizepackages.g6.src.elements.combos.base-combo.BaseComboStyleProps→packages.g6.src.types.size.Size
- Direction
- g6.src.elements.combos.base-combo uses g6.src.types.size, so a change to g6.src.types.size can break g6.src.elements.combos.base-combo, while a change to g6.src.elements.combos.base-combo can't break g6.src.types.size.
- Position
- Below the diagonal: g6.src.elements.combos.base-combo uses a module listed above it, which is the healthy direction.
19→13 g6.src.elements.combos.base-combo uses g6.src.types.element✕
- Connections
- 1 pair of types, where a type in g6.src.elements.combos.base-combo uses a type in g6.src.types.element.
- The types involved
packages.g6.src.elements.combos.base-combo.BaseCombo→packages.g6.src.types.element.Combo
- Direction
- g6.src.elements.combos.base-combo uses g6.src.types.element, so a change to g6.src.types.element can break g6.src.elements.combos.base-combo, while a change to g6.src.elements.combos.base-combo can't break g6.src.types.element.
- Position
- Below the diagonal: g6.src.elements.combos.base-combo uses a module listed above it, which is the healthy direction.
19→15 g6.src.elements.combos.base-combo uses g6.src.elements.nodes.base-node✕
- Connections
- 1 pair of types, where a type in g6.src.elements.combos.base-combo uses a type in g6.src.elements.nodes.base-node.
- The types involved
packages.g6.src.elements.combos.base-combo.BaseCombo→packages.g6.src.elements.nodes.base-node.BaseNode
- Direction
- g6.src.elements.combos.base-combo uses g6.src.elements.nodes.base-node, so a change to g6.src.elements.nodes.base-node can break g6.src.elements.combos.base-combo, while a change to g6.src.elements.combos.base-combo can't break g6.src.elements.nodes.base-node.
- Position
- Below the diagonal: g6.src.elements.combos.base-combo uses a module listed above it, which is the healthy direction.
20→6 g6.src.elements.nodes.circle uses g6.src.types.point✕
- Connections
- 1 pair of types, where a type in g6.src.elements.nodes.circle uses a type in g6.src.types.point.
- The types involved
packages.g6.src.elements.nodes.circle.Circle→packages.g6.src.types.point.Point
- Direction
- g6.src.elements.nodes.circle uses g6.src.types.point, so a change to g6.src.types.point can break g6.src.elements.nodes.circle, while a change to g6.src.elements.nodes.circle can't break g6.src.types.point.
- Position
- Below the diagonal: g6.src.elements.nodes.circle uses a module listed above it, which is the healthy direction.
20→15 g6.src.elements.nodes.circle uses g6.src.elements.nodes.base-node✕
- Connections
- 1 pair of types, where a type in g6.src.elements.nodes.circle uses a type in g6.src.elements.nodes.base-node.
- The types involved
packages.g6.src.elements.nodes.circle.Circle→packages.g6.src.elements.nodes.base-node.BaseNode
- Direction
- g6.src.elements.nodes.circle uses g6.src.elements.nodes.base-node, so a change to g6.src.elements.nodes.base-node can break g6.src.elements.nodes.circle, while a change to g6.src.elements.nodes.circle can't break g6.src.elements.nodes.base-node.
- Position
- Below the diagonal: g6.src.elements.nodes.circle uses a module listed above it, which is the healthy direction.
21→6 g6.src.elements.shapes.polygon uses g6.src.types.point✕
- Connections
- 1 pair of types, where a type in g6.src.elements.shapes.polygon uses a type in g6.src.types.point.
- The types involved
packages.g6.src.elements.shapes.polygon.Polygon→packages.g6.src.types.point.Point
- Direction
- g6.src.elements.shapes.polygon uses g6.src.types.point, so a change to g6.src.types.point can break g6.src.elements.shapes.polygon, while a change to g6.src.elements.shapes.polygon can't break g6.src.types.point.
- Position
- Below the diagonal: g6.src.elements.shapes.polygon uses a module listed above it, which is the healthy direction.
21→15 g6.src.elements.shapes.polygon uses g6.src.elements.nodes.base-node✕
- Connections
- 1 pair of types, where a type in g6.src.elements.shapes.polygon uses a type in g6.src.elements.nodes.base-node.
- The types involved
packages.g6.src.elements.shapes.polygon.Polygon→packages.g6.src.elements.nodes.base-node.BaseNode
- Direction
- g6.src.elements.shapes.polygon uses g6.src.elements.nodes.base-node, so a change to g6.src.elements.nodes.base-node can break g6.src.elements.shapes.polygon, while a change to g6.src.elements.shapes.polygon can't break g6.src.elements.nodes.base-node.
- Position
- Below the diagonal: g6.src.elements.shapes.polygon uses a module listed above it, which is the healthy direction.
22→3 g6.src.utils.event.events uses g6.src.types.data✕
- Connections
- 1 pair of types, where a type in g6.src.utils.event.events uses a type in g6.src.types.data.
- The types involved
packages.g6.src.utils.event.events.ElementLifeCycleEvent→packages.g6.src.types.data.ElementDatum
- Direction
- g6.src.utils.event.events uses g6.src.types.data, so a change to g6.src.types.data can break g6.src.utils.event.events, while a change to g6.src.utils.event.events can't break g6.src.types.data.
- Position
- Below the diagonal: g6.src.utils.event.events uses a module listed above it, which is the healthy direction.
22→12 g6.src.utils.event.events uses g6.src.types.viewport✕
- Connections
- 1 pair of types, where a type in g6.src.utils.event.events uses a type in g6.src.types.viewport.
- The types involved
packages.g6.src.utils.event.events.ViewportEvent→packages.g6.src.types.viewport.TransformOptions
- Direction
- g6.src.utils.event.events uses g6.src.types.viewport, so a change to g6.src.types.viewport can break g6.src.utils.event.events, while a change to g6.src.utils.event.events can't break g6.src.types.viewport.
- Position
- Below the diagonal: g6.src.utils.event.events uses a module listed above it, which is the healthy direction.
22→13 g6.src.utils.event.events uses g6.src.types.element✕
- Connections
- 1 pair of types, where a type in g6.src.utils.event.events uses a type in g6.src.types.element.
- The types involved
packages.g6.src.utils.event.events.ElementLifeCycleEvent→packages.g6.src.types.element.ElementType
- Direction
- g6.src.utils.event.events uses g6.src.types.element, so a change to g6.src.types.element can break g6.src.utils.event.events, while a change to g6.src.utils.event.events can't break g6.src.types.element.
- Position
- Below the diagonal: g6.src.utils.event.events uses a module listed above it, which is the healthy direction.
22→17 g6.src.utils.event.events uses g6.src.types.event✕
- Connections
- 4 pairs of types, where a type in g6.src.utils.event.events uses a type in g6.src.types.event.
- The types involved
packages.g6.src.utils.event.events.AnimateEvent→packages.g6.src.types.event.IAnimateEventpackages.g6.src.utils.event.events.ElementLifeCycleEvent→packages.g6.src.types.event.IElementLifeCycleEventpackages.g6.src.utils.event.events.GraphLifeCycleEvent→packages.g6.src.types.event.IGraphLifeCycleEventpackages.g6.src.utils.event.events.ViewportEvent→packages.g6.src.types.event.IViewportEvent
- Direction
- g6.src.utils.event.events uses g6.src.types.event, so a change to g6.src.types.event can break g6.src.utils.event.events, while a change to g6.src.utils.event.events can't break g6.src.types.event.
- Position
- Below the diagonal: g6.src.utils.event.events uses a module listed above it, which is the healthy direction.
23→3 g6.src.runtime.element uses g6.src.types.data✕
- Connections
- 1 pair of types, where a type in g6.src.runtime.element uses a type in g6.src.types.data.
- The types involved
packages.g6.src.runtime.element.ElementController→packages.g6.src.types.data.ElementDatum
- Direction
- g6.src.runtime.element uses g6.src.types.data, so a change to g6.src.types.data can break g6.src.runtime.element, while a change to g6.src.runtime.element can't break g6.src.types.data.
- Position
- Below the diagonal: g6.src.runtime.element uses a module listed above it, which is the healthy direction.
23→13 g6.src.runtime.element uses g6.src.types.element✕
- Connections
- 2 pairs of types, where a type in g6.src.runtime.element uses a type in g6.src.types.element.
- The types involved
packages.g6.src.runtime.element.ElementController→packages.g6.src.types.element.Elementpackages.g6.src.runtime.element.ElementController→packages.g6.src.types.element.ElementType
- Direction
- g6.src.runtime.element uses g6.src.types.element, so a change to g6.src.types.element can break g6.src.runtime.element, while a change to g6.src.runtime.element can't break g6.src.types.element.
- Position
- Below the diagonal: g6.src.runtime.element uses a module listed above it, which is the healthy direction.
23→22 g6.src.runtime.element uses g6.src.utils.event.events✕
- Connections
- 1 pair of types, where a type in g6.src.runtime.element uses a type in g6.src.utils.event.events.
- The types involved
packages.g6.src.runtime.element.ElementController→packages.g6.src.utils.event.events.BaseEvent
- Direction
- g6.src.runtime.element uses g6.src.utils.event.events, so a change to g6.src.utils.event.events can break g6.src.runtime.element, while a change to g6.src.runtime.element can't break g6.src.utils.event.events.
- Position
- Below the diagonal: g6.src.runtime.element uses a module listed above it, which is the healthy direction.
23→24 g6.src.runtime.element uses g6.src.runtime.types part of a loop✕
- Connections
- 1 pair of types, where a type in g6.src.runtime.element uses a type in g6.src.runtime.types.
- The types involved
packages.g6.src.runtime.element.ElementController→packages.g6.src.runtime.types.RuntimeContext
- Direction
- g6.src.runtime.element uses g6.src.runtime.types, so a change to g6.src.runtime.types can break g6.src.runtime.element, while a change to g6.src.runtime.element can't break g6.src.runtime.types.
- 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→1 g6.src.runtime.types uses g6-ssr.src.types✕
- Connections
- 1 pair of types, where a type in g6.src.runtime.types uses a type in g6-ssr.src.types.
- The types involved
packages.g6.src.runtime.types.RuntimeContext→packages.g6-ssr.src.types.Graph
- Direction
- g6.src.runtime.types uses g6-ssr.src.types, so a change to g6-ssr.src.types can break g6.src.runtime.types, while a change to g6.src.runtime.types can't break g6-ssr.src.types.
- Position
- Below the diagonal: g6.src.runtime.types uses a module listed above it, which is the healthy direction.
24→10 g6.src.runtime.types uses g6.src.runtime.canvas✕
- Connections
- 1 pair of types, where a type in g6.src.runtime.types uses a type in g6.src.runtime.canvas.
- The types involved
packages.g6.src.runtime.types.RuntimeContext→packages.g6.src.runtime.canvas.Canvas
- Direction
- g6.src.runtime.types uses g6.src.runtime.canvas, so a change to g6.src.runtime.canvas can break g6.src.runtime.types, while a change to g6.src.runtime.types can't break g6.src.runtime.canvas.
- Position
- Below the diagonal: g6.src.runtime.types uses a module listed above it, which is the healthy direction.
24→16 g6.src.runtime.types uses g6.src.runtime.data✕
- Connections
- 1 pair of types, where a type in g6.src.runtime.types uses a type in g6.src.runtime.data.
- The types involved
packages.g6.src.runtime.types.RuntimeContext→packages.g6.src.runtime.data.DataController
- Direction
- g6.src.runtime.types uses g6.src.runtime.data, so a change to g6.src.runtime.data can break g6.src.runtime.types, while a change to g6.src.runtime.types can't break g6.src.runtime.data.
- Position
- Below the diagonal: g6.src.runtime.types uses a module listed above it, which is the healthy direction.
24→23 g6.src.runtime.types uses g6.src.runtime.element✕
- Connections
- 1 pair of types, where a type in g6.src.runtime.types uses a type in g6.src.runtime.element.
- The types involved
packages.g6.src.runtime.types.RuntimeContext→packages.g6.src.runtime.element.ElementController
- Direction
- g6.src.runtime.types uses g6.src.runtime.element, so a change to g6.src.runtime.element can break g6.src.runtime.types, while a change to g6.src.runtime.types can't break g6.src.runtime.element.
- Position
- Below the diagonal: g6.src.runtime.types uses a module listed above it, which is the healthy direction.
25→24 g6.src.layouts.base-layout uses g6.src.runtime.types✕
- Connections
- 1 pair of types, where a type in g6.src.layouts.base-layout uses a type in g6.src.runtime.types.
- The types involved
packages.g6.src.layouts.base-layout.BaseLayout→packages.g6.src.runtime.types.RuntimeContext
- Direction
- g6.src.layouts.base-layout uses g6.src.runtime.types, so a change to g6.src.runtime.types can break g6.src.layouts.base-layout, while a change to g6.src.layouts.base-layout can't break g6.src.runtime.types.
- Position
- Below the diagonal: g6.src.layouts.base-layout uses a module listed above it, which is the healthy direction.
26→24 g6.src.registry.extension uses g6.src.runtime.types✕
- Connections
- 2 pairs of types, where a type in g6.src.registry.extension uses a type in g6.src.runtime.types.
- The types involved
packages.g6.src.registry.extension.BaseExtension→packages.g6.src.runtime.types.RuntimeContextpackages.g6.src.registry.extension.ExtensionController→packages.g6.src.runtime.types.RuntimeContext
- Direction
- g6.src.registry.extension uses g6.src.runtime.types, so a change to g6.src.runtime.types can break g6.src.registry.extension, while a change to g6.src.registry.extension can't break g6.src.runtime.types.
- Position
- Below the diagonal: g6.src.registry.extension uses a module listed above it, which is the healthy direction.
27→3 g6.src.runtime.graph uses g6.src.types.data✕
- Connections
- 2 pairs of types, where a type in g6.src.runtime.graph uses a type in g6.src.types.data.
- The types involved
packages.g6.src.runtime.graph.Graph→packages.g6.src.types.data.ElementDatumpackages.g6.src.runtime.graph.Graph→packages.g6.src.types.data.HierarchyKey
- Direction
- g6.src.runtime.graph uses g6.src.types.data, so a change to g6.src.types.data can break g6.src.runtime.graph, while a change to g6.src.runtime.graph can't break g6.src.types.data.
- Position
- Below the diagonal: g6.src.runtime.graph uses a module listed above it, which is the healthy direction.
27→6 g6.src.runtime.graph uses g6.src.types.point✕
- Connections
- 1 pair of types, where a type in g6.src.runtime.graph uses a type in g6.src.types.point.
- The types involved
packages.g6.src.runtime.graph.Graph→packages.g6.src.types.point.Point
- Direction
- g6.src.runtime.graph uses g6.src.types.point, so a change to g6.src.types.point can break g6.src.runtime.graph, while a change to g6.src.runtime.graph can't break g6.src.types.point.
- Position
- Below the diagonal: g6.src.runtime.graph uses a module listed above it, which is the healthy direction.
27→10 g6.src.runtime.graph uses g6.src.runtime.canvas✕
- Connections
- 2 pairs of types, where a type in g6.src.runtime.graph uses a type in g6.src.runtime.canvas.
- The types involved
packages.g6.src.runtime.graph.Graph→packages.g6.src.runtime.canvas.Canvaspackages.g6.src.runtime.graph.Graph→packages.g6.src.runtime.canvas.DataURLOptions
- Direction
- g6.src.runtime.graph uses g6.src.runtime.canvas, so a change to g6.src.runtime.canvas can break g6.src.runtime.graph, while a change to g6.src.runtime.graph can't break g6.src.runtime.canvas.
- Position
- Below the diagonal: g6.src.runtime.graph uses a module listed above it, which is the healthy direction.
27→12 g6.src.runtime.graph uses g6.src.types.viewport✕
- Connections
- 3 pairs of types, where a type in g6.src.runtime.graph uses a type in g6.src.types.viewport.
- The types involved
packages.g6.src.runtime.graph.Graph→packages.g6.src.types.viewport.FitViewOptionspackages.g6.src.runtime.graph.Graph→packages.g6.src.types.viewport.TransformOptionspackages.g6.src.runtime.graph.Graph→packages.g6.src.types.viewport.ViewportAnimationEffectTiming
- Direction
- g6.src.runtime.graph uses g6.src.types.viewport, so a change to g6.src.types.viewport can break g6.src.runtime.graph, while a change to g6.src.runtime.graph can't break g6.src.types.viewport.
- Position
- Below the diagonal: g6.src.runtime.graph uses a module listed above it, which is the healthy direction.
27→13 g6.src.runtime.graph uses g6.src.types.element✕
- Connections
- 1 pair of types, where a type in g6.src.runtime.graph uses a type in g6.src.types.element.
- The types involved
packages.g6.src.runtime.graph.Graph→packages.g6.src.types.element.ElementType
- Direction
- g6.src.runtime.graph uses g6.src.types.element, so a change to g6.src.types.element can break g6.src.runtime.graph, while a change to g6.src.runtime.graph can't break g6.src.types.element.
- Position
- Below the diagonal: g6.src.runtime.graph uses a module listed above it, which is the healthy direction.
27→24 g6.src.runtime.graph uses g6.src.runtime.types✕
- Connections
- 1 pair of types, where a type in g6.src.runtime.graph uses a type in g6.src.runtime.types.
- The types involved
packages.g6.src.runtime.graph.Graph→packages.g6.src.runtime.types.RuntimeContext
- Direction
- g6.src.runtime.graph uses g6.src.runtime.types, so a change to g6.src.runtime.types can break g6.src.runtime.graph, while a change to g6.src.runtime.graph can't break g6.src.runtime.types.
- Position
- Below the diagonal: g6.src.runtime.graph uses a module listed above it, which is the healthy direction.
28→26 g6.src.behaviors.base-behavior uses g6.src.registry.extension✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.base-behavior uses a type in g6.src.registry.extension.
- The types involved
packages.g6.src.behaviors.base-behavior.BaseBehavior→packages.g6.src.registry.extension.BaseExtension
- Direction
- g6.src.behaviors.base-behavior uses g6.src.registry.extension, so a change to g6.src.registry.extension can break g6.src.behaviors.base-behavior, while a change to g6.src.behaviors.base-behavior can't break g6.src.registry.extension.
- Position
- Below the diagonal: g6.src.behaviors.base-behavior uses a module listed above it, which is the healthy direction.
29→26 g6.src.plugins.base-plugin uses g6.src.registry.extension✕
- Connections
- 1 pair of types, where a type in g6.src.plugins.base-plugin uses a type in g6.src.registry.extension.
- The types involved
packages.g6.src.plugins.base-plugin.BasePlugin→packages.g6.src.registry.extension.BaseExtension
- Direction
- g6.src.plugins.base-plugin uses g6.src.registry.extension, so a change to g6.src.registry.extension can break g6.src.plugins.base-plugin, while a change to g6.src.plugins.base-plugin can't break g6.src.registry.extension.
- Position
- Below the diagonal: g6.src.plugins.base-plugin uses a module listed above it, which is the healthy direction.
30→23 g6.src.transforms.base-transform uses g6.src.runtime.element✕
- Connections
- 1 pair of types, where a type in g6.src.transforms.base-transform uses a type in g6.src.runtime.element.
- The types involved
packages.g6.src.transforms.base-transform.BaseTransform→packages.g6.src.runtime.element.DrawContext
- Direction
- g6.src.transforms.base-transform uses g6.src.runtime.element, so a change to g6.src.runtime.element can break g6.src.transforms.base-transform, while a change to g6.src.transforms.base-transform can't break g6.src.runtime.element.
- Position
- Below the diagonal: g6.src.transforms.base-transform uses a module listed above it, which is the healthy direction.
30→26 g6.src.transforms.base-transform uses g6.src.registry.extension✕
- Connections
- 1 pair of types, where a type in g6.src.transforms.base-transform uses a type in g6.src.registry.extension.
- The types involved
packages.g6.src.transforms.base-transform.BaseTransform→packages.g6.src.registry.extension.BaseExtension
- Direction
- g6.src.transforms.base-transform uses g6.src.registry.extension, so a change to g6.src.registry.extension can break g6.src.transforms.base-transform, while a change to g6.src.transforms.base-transform can't break g6.src.registry.extension.
- Position
- Below the diagonal: g6.src.transforms.base-transform uses a module listed above it, which is the healthy direction.
31→1 g6.src.utils uses g6-ssr.src.types✕
- Connections
- 2 pairs of types, where a type in g6.src.utils uses a type in g6-ssr.src.types.
- The types involved
packages.g6.src.utils.extension→packages.g6-ssr.src.types.Graphpackages.g6.src.utils.relation→packages.g6-ssr.src.types.Graph
- Direction
- g6.src.utils uses g6-ssr.src.types, so a change to g6-ssr.src.types can break g6.src.utils, while a change to g6.src.utils can't break g6-ssr.src.types.
- Position
- Below the diagonal: g6.src.utils uses a module listed above it, which is the healthy direction.
31→2 g6.src.utils uses g6.src.elements.shapes.base-shape✕
- Connections
- 1 pair of types, where a type in g6.src.utils uses a type in g6.src.elements.shapes.base-shape.
- The types involved
packages.g6.src.utils.element→packages.g6.src.elements.shapes.base-shape.BaseShape
- Direction
- g6.src.utils uses g6.src.elements.shapes.base-shape, so a change to g6.src.elements.shapes.base-shape can break g6.src.utils, while a change to g6.src.utils can't break g6.src.elements.shapes.base-shape.
- Position
- Below the diagonal: g6.src.utils uses a module listed above it, which is the healthy direction.
31→3 g6.src.utils uses g6.src.types.data✕
- Connections
- 8 pairs of types, where a type in g6.src.utils uses a type in g6.src.types.data.
- The types involved
packages.g6.src.utils.collapsibility→packages.g6.src.types.data.NodeLikeDatapackages.g6.src.utils.data→packages.g6.src.types.data.ElementDatumpackages.g6.src.utils.edge→packages.g6.src.types.data.NodeLikeDatapackages.g6.src.utils.is→packages.g6.src.types.data.ElementDatumpackages.g6.src.utils.palette→packages.g6.src.types.data.ElementDatapackages.g6.src.utils.position→packages.g6.src.types.data.NodeLikeDatapackages.g6.src.utils.state→packages.g6.src.types.data.ElementDatumpackages.g6.src.utils.z-index→packages.g6.src.types.data.ElementDatum
- Direction
- g6.src.utils uses g6.src.types.data, so a change to g6.src.types.data can break g6.src.utils, while a change to g6.src.utils can't break g6.src.types.data.
- Position
- Below the diagonal: g6.src.utils uses a module listed above it, which is the healthy direction.
31→4 g6.src.utils uses g6.src.types.padding✕
- Connections
- 2 pairs of types, where a type in g6.src.utils uses a type in g6.src.types.padding.
- The types involved
packages.g6.src.utils.bbox→packages.g6.src.types.padding.Paddingpackages.g6.src.utils.padding→packages.g6.src.types.padding.Padding
- Direction
- g6.src.utils uses g6.src.types.padding, so a change to g6.src.types.padding can break g6.src.utils, while a change to g6.src.utils can't break g6.src.types.padding.
- Position
- Below the diagonal: g6.src.utils uses a module listed above it, which is the healthy direction.
31→5 g6.src.utils uses g6.src.types.placement✕
- Connections
- 3 pairs of types, where a type in g6.src.utils uses a type in g6.src.types.placement.
- The types involved
packages.g6.src.utils.element→packages.g6.src.types.placement.Placementpackages.g6.src.utils.placement→packages.g6.src.types.placement.Placementpackages.g6.src.utils.position→packages.g6.src.types.placement.Placement
- Direction
- g6.src.utils uses g6.src.types.placement, so a change to g6.src.types.placement can break g6.src.utils, while a change to g6.src.utils can't break g6.src.types.placement.
- Position
- Below the diagonal: g6.src.utils uses a module listed above it, which is the healthy direction.
31→6 g6.src.utils uses g6.src.types.point✕
- Connections
- 6 pairs of types, where a type in g6.src.utils uses a type in g6.src.types.point.
- The types involved
packages.g6.src.utils.bbox→packages.g6.src.types.point.Pointpackages.g6.src.utils.edge→packages.g6.src.types.point.Pointpackages.g6.src.utils.element→packages.g6.src.types.point.Pointpackages.g6.src.utils.is→packages.g6.src.types.point.Pointpackages.g6.src.utils.point→packages.g6.src.types.point.Pointpackages.g6.src.utils.position→packages.g6.src.types.point.Point
- Direction
- g6.src.utils uses g6.src.types.point, so a change to g6.src.types.point can break g6.src.utils, while a change to g6.src.utils can't break g6.src.types.point.
- Position
- Below the diagonal: g6.src.utils uses a module listed above it, which is the healthy direction.
31→7 g6.src.utils uses g6.src.types.size✕
- Connections
- 4 pairs of types, where a type in g6.src.utils uses a type in g6.src.types.size.
- The types involved
packages.g6.src.utils.edge→packages.g6.src.types.size.Sizepackages.g6.src.utils.node→packages.g6.src.types.size.Sizepackages.g6.src.utils.size→packages.g6.src.types.size.STDSizepackages.g6.src.utils.size→packages.g6.src.types.size.Size
- Direction
- g6.src.utils uses g6.src.types.size, so a change to g6.src.types.size can break g6.src.utils, while a change to g6.src.utils can't break g6.src.types.size.
- Position
- Below the diagonal: g6.src.utils uses a module listed above it, which is the healthy direction.
31→8 g6.src.utils uses g6.src.types.vector✕
- Connections
- 2 pairs of types, where a type in g6.src.utils uses a type in g6.src.types.vector.
- The types involved
packages.g6.src.utils.vector→packages.g6.src.types.vector.Vector2packages.g6.src.utils.vector→packages.g6.src.types.vector.Vector3
- Direction
- g6.src.utils uses g6.src.types.vector, so a change to g6.src.types.vector can break g6.src.utils, while a change to g6.src.utils can't break g6.src.types.vector.
- Position
- Below the diagonal: g6.src.utils uses a module listed above it, which is the healthy direction.
31→11 g6.src.utils uses g6.src.types.node✕
- Connections
- 5 pairs of types, where a type in g6.src.utils uses a type in g6.src.types.node.
- The types involved
packages.g6.src.utils.bbox→packages.g6.src.types.node.TriangleDirectionpackages.g6.src.utils.edge→packages.g6.src.types.node.Portpackages.g6.src.utils.element→packages.g6.src.types.node.NodePortStylePropspackages.g6.src.utils.element→packages.g6.src.types.node.Portpackages.g6.src.utils.element→packages.g6.src.types.node.TriangleDirection
- Direction
- g6.src.utils uses g6.src.types.node, so a change to g6.src.types.node can break g6.src.utils, while a change to g6.src.utils can't break g6.src.types.node.
- Position
- Below the diagonal: g6.src.utils uses a module listed above it, which is the healthy direction.
31→12 g6.src.utils uses g6.src.types.viewport✕
- Connections
- 1 pair of types, where a type in g6.src.utils uses a type in g6.src.types.viewport.
- The types involved
packages.g6.src.utils.extension→packages.g6.src.types.viewport.TransformOptions
- Direction
- g6.src.utils uses g6.src.types.viewport, so a change to g6.src.types.viewport can break g6.src.utils, while a change to g6.src.utils can't break g6.src.types.viewport.
- Position
- Below the diagonal: g6.src.utils uses a module listed above it, which is the healthy direction.
31→13 g6.src.utils uses g6.src.types.element✕
- Connections
- 4 pairs of types, where a type in g6.src.utils uses a type in g6.src.types.element.
- The types involved
packages.g6.src.utils.animation→packages.g6.src.types.element.ElementTypepackages.g6.src.utils.edge→packages.g6.src.types.element.Nodepackages.g6.src.utils.element→packages.g6.src.types.element.Nodepackages.g6.src.utils.relation→packages.g6.src.types.element.ElementType
- Direction
- g6.src.utils uses g6.src.types.element, so a change to g6.src.types.element can break g6.src.utils, while a change to g6.src.utils can't break g6.src.types.element.
- Position
- Below the diagonal: g6.src.utils uses a module listed above it, which is the healthy direction.
31→22 g6.src.utils uses g6.src.utils.event.events✕
- Connections
- 1 pair of types, where a type in g6.src.utils uses a type in g6.src.utils.event.events.
- The types involved
packages.g6.src.utils.index→packages.g6.src.utils.event.events.BaseEvent
- Direction
- g6.src.utils uses g6.src.utils.event.events, so a change to g6.src.utils.event.events can break g6.src.utils, while a change to g6.src.utils can't break g6.src.utils.event.events.
- Position
- Below the diagonal: g6.src.utils uses a module listed above it, which is the healthy direction.
31→24 g6.src.utils uses g6.src.runtime.types✕
- Connections
- 1 pair of types, where a type in g6.src.utils uses a type in g6.src.runtime.types.
- The types involved
packages.g6.src.utils.layout→packages.g6.src.runtime.types.RuntimeContext
- Direction
- g6.src.utils uses g6.src.runtime.types, so a change to g6.src.runtime.types can break g6.src.utils, while a change to g6.src.utils can't break g6.src.runtime.types.
- Position
- Below the diagonal: g6.src.utils uses a module listed above it, which is the healthy direction.
31→25 g6.src.utils uses g6.src.layouts.base-layout✕
- Connections
- 1 pair of types, where a type in g6.src.utils uses a type in g6.src.layouts.base-layout.
- The types involved
packages.g6.src.utils.layout→packages.g6.src.layouts.base-layout.BaseLayout
- Direction
- g6.src.utils uses g6.src.layouts.base-layout, so a change to g6.src.layouts.base-layout can break g6.src.utils, while a change to g6.src.utils can't break g6.src.layouts.base-layout.
- Position
- Below the diagonal: g6.src.utils uses a module listed above it, which is the healthy direction.
32→4 g6.src.behaviors.auto-adapt-label uses g6.src.types.padding✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.auto-adapt-label uses a type in g6.src.types.padding.
- The types involved
packages.g6.src.behaviors.auto-adapt-label.AutoAdaptLabelOptions→packages.g6.src.types.padding.Padding
- Direction
- g6.src.behaviors.auto-adapt-label uses g6.src.types.padding, so a change to g6.src.types.padding can break g6.src.behaviors.auto-adapt-label, while a change to g6.src.behaviors.auto-adapt-label can't break g6.src.types.padding.
- Position
- Below the diagonal: g6.src.behaviors.auto-adapt-label uses a module listed above it, which is the healthy direction.
32→13 g6.src.behaviors.auto-adapt-label uses g6.src.types.element✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.auto-adapt-label uses a type in g6.src.types.element.
- The types involved
packages.g6.src.behaviors.auto-adapt-label.AutoAdaptLabel→packages.g6.src.types.element.Element
- Direction
- g6.src.behaviors.auto-adapt-label uses g6.src.types.element, so a change to g6.src.types.element can break g6.src.behaviors.auto-adapt-label, while a change to g6.src.behaviors.auto-adapt-label can't break g6.src.types.element.
- Position
- Below the diagonal: g6.src.behaviors.auto-adapt-label uses a module listed above it, which is the healthy direction.
32→17 g6.src.behaviors.auto-adapt-label uses g6.src.types.event✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.auto-adapt-label uses a type in g6.src.types.event.
- The types involved
packages.g6.src.behaviors.auto-adapt-label.AutoAdaptLabel→packages.g6.src.types.event.IEvent
- Direction
- g6.src.behaviors.auto-adapt-label uses g6.src.types.event, so a change to g6.src.types.event can break g6.src.behaviors.auto-adapt-label, while a change to g6.src.behaviors.auto-adapt-label can't break g6.src.types.event.
- Position
- Below the diagonal: g6.src.behaviors.auto-adapt-label uses a module listed above it, which is the healthy direction.
32→24 g6.src.behaviors.auto-adapt-label uses g6.src.runtime.types✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.auto-adapt-label uses a type in g6.src.runtime.types.
- The types involved
packages.g6.src.behaviors.auto-adapt-label.AutoAdaptLabel→packages.g6.src.runtime.types.RuntimeContext
- Direction
- g6.src.behaviors.auto-adapt-label uses g6.src.runtime.types, so a change to g6.src.runtime.types can break g6.src.behaviors.auto-adapt-label, while a change to g6.src.behaviors.auto-adapt-label can't break g6.src.runtime.types.
- Position
- Below the diagonal: g6.src.behaviors.auto-adapt-label uses a module listed above it, which is the healthy direction.
32→28 g6.src.behaviors.auto-adapt-label uses g6.src.behaviors.base-behavior✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.auto-adapt-label uses a type in g6.src.behaviors.base-behavior.
- The types involved
packages.g6.src.behaviors.auto-adapt-label.AutoAdaptLabel→packages.g6.src.behaviors.base-behavior.BaseBehavior
- Direction
- g6.src.behaviors.auto-adapt-label uses g6.src.behaviors.base-behavior, so a change to g6.src.behaviors.base-behavior can break g6.src.behaviors.auto-adapt-label, while a change to g6.src.behaviors.auto-adapt-label can't break g6.src.behaviors.base-behavior.
- Position
- Below the diagonal: g6.src.behaviors.auto-adapt-label uses a module listed above it, which is the healthy direction.
33→1 g6.src.behaviors.brush-select uses g6-ssr.src.types✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.brush-select uses a type in g6-ssr.src.types.
- The types involved
packages.g6.src.behaviors.brush-select.BrushSelect→packages.g6-ssr.src.types.Graph
- Direction
- g6.src.behaviors.brush-select uses g6-ssr.src.types, so a change to g6-ssr.src.types can break g6.src.behaviors.brush-select, while a change to g6.src.behaviors.brush-select can't break g6-ssr.src.types.
- Position
- Below the diagonal: g6.src.behaviors.brush-select uses a module listed above it, which is the healthy direction.
33→6 g6.src.behaviors.brush-select uses g6.src.types.point✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.brush-select uses a type in g6.src.types.point.
- The types involved
packages.g6.src.behaviors.brush-select.BrushSelect→packages.g6.src.types.point.Point
- Direction
- g6.src.behaviors.brush-select uses g6.src.types.point, so a change to g6.src.types.point can break g6.src.behaviors.brush-select, while a change to g6.src.behaviors.brush-select can't break g6.src.types.point.
- Position
- Below the diagonal: g6.src.behaviors.brush-select uses a module listed above it, which is the healthy direction.
33→9 g6.src.behaviors.brush-select uses g6.src.utils.shortcut✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.brush-select uses a type in g6.src.utils.shortcut.
- The types involved
packages.g6.src.behaviors.brush-select.BrushSelect→packages.g6.src.utils.shortcut.Shortcut
- Direction
- g6.src.behaviors.brush-select uses g6.src.utils.shortcut, so a change to g6.src.utils.shortcut can break g6.src.behaviors.brush-select, while a change to g6.src.behaviors.brush-select can't break g6.src.utils.shortcut.
- Position
- Below the diagonal: g6.src.behaviors.brush-select uses a module listed above it, which is the healthy direction.
33→17 g6.src.behaviors.brush-select uses g6.src.types.event✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.brush-select uses a type in g6.src.types.event.
- The types involved
packages.g6.src.behaviors.brush-select.BrushSelect→packages.g6.src.types.event.IPointerEvent
- Direction
- g6.src.behaviors.brush-select uses g6.src.types.event, so a change to g6.src.types.event can break g6.src.behaviors.brush-select, while a change to g6.src.behaviors.brush-select can't break g6.src.types.event.
- Position
- Below the diagonal: g6.src.behaviors.brush-select uses a module listed above it, which is the healthy direction.
33→24 g6.src.behaviors.brush-select uses g6.src.runtime.types✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.brush-select uses a type in g6.src.runtime.types.
- The types involved
packages.g6.src.behaviors.brush-select.BrushSelect→packages.g6.src.runtime.types.RuntimeContext
- Direction
- g6.src.behaviors.brush-select uses g6.src.runtime.types, so a change to g6.src.runtime.types can break g6.src.behaviors.brush-select, while a change to g6.src.behaviors.brush-select can't break g6.src.runtime.types.
- Position
- Below the diagonal: g6.src.behaviors.brush-select uses a module listed above it, which is the healthy direction.
33→28 g6.src.behaviors.brush-select uses g6.src.behaviors.base-behavior✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.brush-select uses a type in g6.src.behaviors.base-behavior.
- The types involved
packages.g6.src.behaviors.brush-select.BrushSelect→packages.g6.src.behaviors.base-behavior.BaseBehavior
- Direction
- g6.src.behaviors.brush-select uses g6.src.behaviors.base-behavior, so a change to g6.src.behaviors.base-behavior can break g6.src.behaviors.brush-select, while a change to g6.src.behaviors.brush-select can't break g6.src.behaviors.base-behavior.
- Position
- Below the diagonal: g6.src.behaviors.brush-select uses a module listed above it, which is the healthy direction.
34→9 g6.src.behaviors.click-select uses g6.src.utils.shortcut✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.click-select uses a type in g6.src.utils.shortcut.
- The types involved
packages.g6.src.behaviors.click-select.ClickSelect→packages.g6.src.utils.shortcut.Shortcut
- Direction
- g6.src.behaviors.click-select uses g6.src.utils.shortcut, so a change to g6.src.utils.shortcut can break g6.src.behaviors.click-select, while a change to g6.src.behaviors.click-select can't break g6.src.utils.shortcut.
- Position
- Below the diagonal: g6.src.behaviors.click-select uses a module listed above it, which is the healthy direction.
34→13 g6.src.behaviors.click-select uses g6.src.types.element✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.click-select uses a type in g6.src.types.element.
- The types involved
packages.g6.src.behaviors.click-select.ClickSelect→packages.g6.src.types.element.Element
- Direction
- g6.src.behaviors.click-select uses g6.src.types.element, so a change to g6.src.types.element can break g6.src.behaviors.click-select, while a change to g6.src.behaviors.click-select can't break g6.src.types.element.
- Position
- Below the diagonal: g6.src.behaviors.click-select uses a module listed above it, which is the healthy direction.
34→17 g6.src.behaviors.click-select uses g6.src.types.event✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.click-select uses a type in g6.src.types.event.
- The types involved
packages.g6.src.behaviors.click-select.ClickSelect→packages.g6.src.types.event.IPointerEvent
- Direction
- g6.src.behaviors.click-select uses g6.src.types.event, so a change to g6.src.types.event can break g6.src.behaviors.click-select, while a change to g6.src.behaviors.click-select can't break g6.src.types.event.
- Position
- Below the diagonal: g6.src.behaviors.click-select uses a module listed above it, which is the healthy direction.
34→24 g6.src.behaviors.click-select uses g6.src.runtime.types✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.click-select uses a type in g6.src.runtime.types.
- The types involved
packages.g6.src.behaviors.click-select.ClickSelect→packages.g6.src.runtime.types.RuntimeContext
- Direction
- g6.src.behaviors.click-select uses g6.src.runtime.types, so a change to g6.src.runtime.types can break g6.src.behaviors.click-select, while a change to g6.src.behaviors.click-select can't break g6.src.runtime.types.
- Position
- Below the diagonal: g6.src.behaviors.click-select uses a module listed above it, which is the healthy direction.
34→28 g6.src.behaviors.click-select uses g6.src.behaviors.base-behavior✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.click-select uses a type in g6.src.behaviors.base-behavior.
- The types involved
packages.g6.src.behaviors.click-select.ClickSelect→packages.g6.src.behaviors.base-behavior.BaseBehavior
- Direction
- g6.src.behaviors.click-select uses g6.src.behaviors.base-behavior, so a change to g6.src.behaviors.base-behavior can break g6.src.behaviors.click-select, while a change to g6.src.behaviors.click-select can't break g6.src.behaviors.base-behavior.
- Position
- Below the diagonal: g6.src.behaviors.click-select uses a module listed above it, which is the healthy direction.
35→8 g6.src.behaviors.drag-canvas uses g6.src.types.vector✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.drag-canvas uses a type in g6.src.types.vector.
- The types involved
packages.g6.src.behaviors.drag-canvas.DragCanvas→packages.g6.src.types.vector.Vector2
- Direction
- g6.src.behaviors.drag-canvas uses g6.src.types.vector, so a change to g6.src.types.vector can break g6.src.behaviors.drag-canvas, while a change to g6.src.behaviors.drag-canvas can't break g6.src.types.vector.
- Position
- Below the diagonal: g6.src.behaviors.drag-canvas uses a module listed above it, which is the healthy direction.
35→9 g6.src.behaviors.drag-canvas uses g6.src.utils.shortcut✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.drag-canvas uses a type in g6.src.utils.shortcut.
- The types involved
packages.g6.src.behaviors.drag-canvas.DragCanvas→packages.g6.src.utils.shortcut.Shortcut
- Direction
- g6.src.behaviors.drag-canvas uses g6.src.utils.shortcut, so a change to g6.src.utils.shortcut can break g6.src.behaviors.drag-canvas, while a change to g6.src.behaviors.drag-canvas can't break g6.src.utils.shortcut.
- Position
- Below the diagonal: g6.src.behaviors.drag-canvas uses a module listed above it, which is the healthy direction.
35→12 g6.src.behaviors.drag-canvas uses g6.src.types.viewport✕
- Connections
- 2 pairs of types, where a type in g6.src.behaviors.drag-canvas uses a type in g6.src.types.viewport.
- The types involved
packages.g6.src.behaviors.drag-canvas.DragCanvas→packages.g6.src.types.viewport.ViewportAnimationEffectTimingpackages.g6.src.behaviors.drag-canvas.DragCanvasOptions→packages.g6.src.types.viewport.ViewportAnimationEffectTiming
- Direction
- g6.src.behaviors.drag-canvas uses g6.src.types.viewport, so a change to g6.src.types.viewport can break g6.src.behaviors.drag-canvas, while a change to g6.src.behaviors.drag-canvas can't break g6.src.types.viewport.
- Position
- Below the diagonal: g6.src.behaviors.drag-canvas uses a module listed above it, which is the healthy direction.
35→17 g6.src.behaviors.drag-canvas uses g6.src.types.event✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.drag-canvas uses a type in g6.src.types.event.
- The types involved
packages.g6.src.behaviors.drag-canvas.DragCanvas→packages.g6.src.types.event.IDragEvent
- Direction
- g6.src.behaviors.drag-canvas uses g6.src.types.event, so a change to g6.src.types.event can break g6.src.behaviors.drag-canvas, while a change to g6.src.behaviors.drag-canvas can't break g6.src.types.event.
- Position
- Below the diagonal: g6.src.behaviors.drag-canvas uses a module listed above it, which is the healthy direction.
35→24 g6.src.behaviors.drag-canvas uses g6.src.runtime.types✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.drag-canvas uses a type in g6.src.runtime.types.
- The types involved
packages.g6.src.behaviors.drag-canvas.DragCanvas→packages.g6.src.runtime.types.RuntimeContext
- Direction
- g6.src.behaviors.drag-canvas uses g6.src.runtime.types, so a change to g6.src.runtime.types can break g6.src.behaviors.drag-canvas, while a change to g6.src.behaviors.drag-canvas can't break g6.src.runtime.types.
- Position
- Below the diagonal: g6.src.behaviors.drag-canvas uses a module listed above it, which is the healthy direction.
35→28 g6.src.behaviors.drag-canvas uses g6.src.behaviors.base-behavior✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.drag-canvas uses a type in g6.src.behaviors.base-behavior.
- The types involved
packages.g6.src.behaviors.drag-canvas.DragCanvas→packages.g6.src.behaviors.base-behavior.BaseBehavior
- Direction
- g6.src.behaviors.drag-canvas uses g6.src.behaviors.base-behavior, so a change to g6.src.behaviors.base-behavior can break g6.src.behaviors.drag-canvas, while a change to g6.src.behaviors.drag-canvas can't break g6.src.behaviors.base-behavior.
- Position
- Below the diagonal: g6.src.behaviors.drag-canvas uses a module listed above it, which is the healthy direction.
36→6 g6.src.behaviors.drag-element uses g6.src.types.point✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.drag-element uses a type in g6.src.types.point.
- The types involved
packages.g6.src.behaviors.drag-element.DragElement→packages.g6.src.types.point.Point
- Direction
- g6.src.behaviors.drag-element uses g6.src.types.point, so a change to g6.src.types.point can break g6.src.behaviors.drag-element, while a change to g6.src.behaviors.drag-element can't break g6.src.types.point.
- Position
- Below the diagonal: g6.src.behaviors.drag-element uses a module listed above it, which is the healthy direction.
36→8 g6.src.behaviors.drag-element uses g6.src.types.vector✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.drag-element uses a type in g6.src.types.vector.
- The types involved
packages.g6.src.behaviors.drag-element.DragElement→packages.g6.src.types.vector.Vector2
- Direction
- g6.src.behaviors.drag-element uses g6.src.types.vector, so a change to g6.src.types.vector can break g6.src.behaviors.drag-element, while a change to g6.src.behaviors.drag-element can't break g6.src.types.vector.
- Position
- Below the diagonal: g6.src.behaviors.drag-element uses a module listed above it, which is the healthy direction.
36→9 g6.src.behaviors.drag-element uses g6.src.utils.shortcut✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.drag-element uses a type in g6.src.utils.shortcut.
- The types involved
packages.g6.src.behaviors.drag-element.DragElement→packages.g6.src.utils.shortcut.Shortcut
- Direction
- g6.src.behaviors.drag-element uses g6.src.utils.shortcut, so a change to g6.src.utils.shortcut can break g6.src.behaviors.drag-element, while a change to g6.src.behaviors.drag-element can't break g6.src.utils.shortcut.
- Position
- Below the diagonal: g6.src.behaviors.drag-element uses a module listed above it, which is the healthy direction.
36→17 g6.src.behaviors.drag-element uses g6.src.types.event✕
- Connections
- 2 pairs of types, where a type in g6.src.behaviors.drag-element uses a type in g6.src.types.event.
- The types involved
packages.g6.src.behaviors.drag-element.DragElement→packages.g6.src.types.event.IElementDragEventpackages.g6.src.behaviors.drag-element.DragElement→packages.g6.src.types.event.IPointerEvent
- Direction
- g6.src.behaviors.drag-element uses g6.src.types.event, so a change to g6.src.types.event can break g6.src.behaviors.drag-element, while a change to g6.src.behaviors.drag-element can't break g6.src.types.event.
- Position
- Below the diagonal: g6.src.behaviors.drag-element uses a module listed above it, which is the healthy direction.
36→24 g6.src.behaviors.drag-element uses g6.src.runtime.types✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.drag-element uses a type in g6.src.runtime.types.
- The types involved
packages.g6.src.behaviors.drag-element.DragElement→packages.g6.src.runtime.types.RuntimeContext
- Direction
- g6.src.behaviors.drag-element uses g6.src.runtime.types, so a change to g6.src.runtime.types can break g6.src.behaviors.drag-element, while a change to g6.src.behaviors.drag-element can't break g6.src.runtime.types.
- Position
- Below the diagonal: g6.src.behaviors.drag-element uses a module listed above it, which is the healthy direction.
36→28 g6.src.behaviors.drag-element uses g6.src.behaviors.base-behavior✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.drag-element uses a type in g6.src.behaviors.base-behavior.
- The types involved
packages.g6.src.behaviors.drag-element.DragElement→packages.g6.src.behaviors.base-behavior.BaseBehavior
- Direction
- g6.src.behaviors.drag-element uses g6.src.behaviors.base-behavior, so a change to g6.src.behaviors.base-behavior can break g6.src.behaviors.drag-element, while a change to g6.src.behaviors.drag-element can't break g6.src.behaviors.base-behavior.
- Position
- Below the diagonal: g6.src.behaviors.drag-element uses a module listed above it, which is the healthy direction.
37→6 g6.src.behaviors.zoom-canvas uses g6.src.types.point✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.zoom-canvas uses a type in g6.src.types.point.
- The types involved
packages.g6.src.behaviors.zoom-canvas.ZoomCanvasOptions→packages.g6.src.types.point.Point
- Direction
- g6.src.behaviors.zoom-canvas uses g6.src.types.point, so a change to g6.src.types.point can break g6.src.behaviors.zoom-canvas, while a change to g6.src.behaviors.zoom-canvas can't break g6.src.types.point.
- Position
- Below the diagonal: g6.src.behaviors.zoom-canvas uses a module listed above it, which is the healthy direction.
37→9 g6.src.behaviors.zoom-canvas uses g6.src.utils.shortcut✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.zoom-canvas uses a type in g6.src.utils.shortcut.
- The types involved
packages.g6.src.behaviors.zoom-canvas.ZoomCanvas→packages.g6.src.utils.shortcut.Shortcut
- Direction
- g6.src.behaviors.zoom-canvas uses g6.src.utils.shortcut, so a change to g6.src.utils.shortcut can break g6.src.behaviors.zoom-canvas, while a change to g6.src.behaviors.zoom-canvas can't break g6.src.utils.shortcut.
- Position
- Below the diagonal: g6.src.behaviors.zoom-canvas uses a module listed above it, which is the healthy direction.
37→12 g6.src.behaviors.zoom-canvas uses g6.src.types.viewport✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.zoom-canvas uses a type in g6.src.types.viewport.
- The types involved
packages.g6.src.behaviors.zoom-canvas.ZoomCanvasOptions→packages.g6.src.types.viewport.ViewportAnimationEffectTiming
- Direction
- g6.src.behaviors.zoom-canvas uses g6.src.types.viewport, so a change to g6.src.types.viewport can break g6.src.behaviors.zoom-canvas, while a change to g6.src.behaviors.zoom-canvas can't break g6.src.types.viewport.
- Position
- Below the diagonal: g6.src.behaviors.zoom-canvas uses a module listed above it, which is the healthy direction.
37→24 g6.src.behaviors.zoom-canvas uses g6.src.runtime.types✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.zoom-canvas uses a type in g6.src.runtime.types.
- The types involved
packages.g6.src.behaviors.zoom-canvas.ZoomCanvas→packages.g6.src.runtime.types.RuntimeContext
- Direction
- g6.src.behaviors.zoom-canvas uses g6.src.runtime.types, so a change to g6.src.runtime.types can break g6.src.behaviors.zoom-canvas, while a change to g6.src.behaviors.zoom-canvas can't break g6.src.runtime.types.
- Position
- Below the diagonal: g6.src.behaviors.zoom-canvas uses a module listed above it, which is the healthy direction.
37→28 g6.src.behaviors.zoom-canvas uses g6.src.behaviors.base-behavior✕
- Connections
- 1 pair of types, where a type in g6.src.behaviors.zoom-canvas uses a type in g6.src.behaviors.base-behavior.
- The types involved
packages.g6.src.behaviors.zoom-canvas.ZoomCanvas→packages.g6.src.behaviors.base-behavior.BaseBehavior
- Direction
- g6.src.behaviors.zoom-canvas uses g6.src.behaviors.base-behavior, so a change to g6.src.behaviors.base-behavior can break g6.src.behaviors.zoom-canvas, while a change to g6.src.behaviors.zoom-canvas can't break g6.src.behaviors.base-behavior.
- Position
- Below the diagonal: g6.src.behaviors.zoom-canvas uses a module listed above it, which is the healthy direction.
38→3 g6.src.plugins.edge-filter-lens uses g6.src.types.data✕
- Connections
- 1 pair of types, where a type in g6.src.plugins.edge-filter-lens uses a type in g6.src.types.data.
- The types involved
packages.g6.src.plugins.edge-filter-lens.EdgeFilterLens→packages.g6.src.types.data.ElementDatum
- Direction
- g6.src.plugins.edge-filter-lens uses g6.src.types.data, so a change to g6.src.types.data can break g6.src.plugins.edge-filter-lens, while a change to g6.src.plugins.edge-filter-lens can't break g6.src.types.data.
- Position
- Below the diagonal: g6.src.plugins.edge-filter-lens uses a module listed above it, which is the healthy direction.
38→6 g6.src.plugins.edge-filter-lens uses g6.src.types.point✕
- Connections
- 1 pair of types, where a type in g6.src.plugins.edge-filter-lens uses a type in g6.src.types.point.
- The types involved
packages.g6.src.plugins.edge-filter-lens.EdgeFilterLens→packages.g6.src.types.point.Point
- Direction
- g6.src.plugins.edge-filter-lens uses g6.src.types.point, so a change to g6.src.types.point can break g6.src.plugins.edge-filter-lens, while a change to g6.src.plugins.edge-filter-lens can't break g6.src.types.point.
- Position
- Below the diagonal: g6.src.plugins.edge-filter-lens uses a module listed above it, which is the healthy direction.
38→13 g6.src.plugins.edge-filter-lens uses g6.src.types.element✕
- Connections
- 1 pair of types, where a type in g6.src.plugins.edge-filter-lens uses a type in g6.src.types.element.
- The types involved
packages.g6.src.plugins.edge-filter-lens.EdgeFilterLens→packages.g6.src.types.element.ElementType
- Direction
- g6.src.plugins.edge-filter-lens uses g6.src.types.element, so a change to g6.src.types.element can break g6.src.plugins.edge-filter-lens, while a change to g6.src.plugins.edge-filter-lens can't break g6.src.types.element.
- Position
- Below the diagonal: g6.src.plugins.edge-filter-lens uses a module listed above it, which is the healthy direction.
38→17 g6.src.plugins.edge-filter-lens uses g6.src.types.event✕
- Connections
- 2 pairs of types, where a type in g6.src.plugins.edge-filter-lens uses a type in g6.src.types.event.
- The types involved
packages.g6.src.plugins.edge-filter-lens.EdgeFilterLens→packages.g6.src.types.event.IDragEventpackages.g6.src.plugins.edge-filter-lens.EdgeFilterLens→packages.g6.src.types.event.IPointerEvent
- Direction
- g6.src.plugins.edge-filter-lens uses g6.src.types.event, so a change to g6.src.types.event can break g6.src.plugins.edge-filter-lens, while a change to g6.src.plugins.edge-filter-lens can't break g6.src.types.event.
- Position
- Below the diagonal: g6.src.plugins.edge-filter-lens uses a module listed above it, which is the healthy direction.
38→20 g6.src.plugins.edge-filter-lens uses g6.src.elements.nodes.circle✕
- Connections
- 2 pairs of types, where a type in g6.src.plugins.edge-filter-lens uses a type in g6.src.elements.nodes.circle.
- The types involved
packages.g6.src.plugins.edge-filter-lens.EdgeFilterLens→packages.g6.src.elements.nodes.circle.Circlepackages.g6.src.plugins.edge-filter-lens.EdgeFilterLensOptions→packages.g6.src.elements.nodes.circle.CircleStyleProps
- Direction
- g6.src.plugins.edge-filter-lens uses g6.src.elements.nodes.circle, so a change to g6.src.elements.nodes.circle can break g6.src.plugins.edge-filter-lens, while a change to g6.src.plugins.edge-filter-lens can't break g6.src.elements.nodes.circle.
- Position
- Below the diagonal: g6.src.plugins.edge-filter-lens uses a module listed above it, which is the healthy direction.
38→24 g6.src.plugins.edge-filter-lens uses g6.src.runtime.types✕
- Connections
- 1 pair of types, where a type in g6.src.plugins.edge-filter-lens uses a type in g6.src.runtime.types.
- The types involved
packages.g6.src.plugins.edge-filter-lens.EdgeFilterLens→packages.g6.src.runtime.types.RuntimeContext
- Direction
- g6.src.plugins.edge-filter-lens uses g6.src.runtime.types, so a change to g6.src.runtime.types can break g6.src.plugins.edge-filter-lens, while a change to g6.src.plugins.edge-filter-lens can't break g6.src.runtime.types.
- Position
- Below the diagonal: g6.src.plugins.edge-filter-lens uses a module listed above it, which is the healthy direction.
38→29 g6.src.plugins.edge-filter-lens uses g6.src.plugins.base-plugin✕
- Connections
- 1 pair of types, where a type in g6.src.plugins.edge-filter-lens uses a type in g6.src.plugins.base-plugin.
- The types involved
packages.g6.src.plugins.edge-filter-lens.EdgeFilterLens→packages.g6.src.plugins.base-plugin.BasePlugin
- Direction
- g6.src.plugins.edge-filter-lens uses g6.src.plugins.base-plugin, so a change to g6.src.plugins.base-plugin can break g6.src.plugins.edge-filter-lens, while a change to g6.src.plugins.edge-filter-lens can't break g6.src.plugins.base-plugin.
- Position
- Below the diagonal: g6.src.plugins.edge-filter-lens uses a module listed above it, which is the healthy direction.
39→6 g6.src.plugins.hull uses g6.src.types.point✕
- Connections
- 2 pairs of types, where a type in g6.src.plugins.hull uses a type in g6.src.types.point.
- The types involved
packages.g6.src.plugins.hull.index→packages.g6.src.types.point.Pointpackages.g6.src.plugins.hull.util→packages.g6.src.types.point.Point
- Direction
- g6.src.plugins.hull uses g6.src.types.point, so a change to g6.src.types.point can break g6.src.plugins.hull, while a change to g6.src.plugins.hull can't break g6.src.types.point.
- Position
- Below the diagonal: g6.src.plugins.hull uses a module listed above it, which is the healthy direction.
39→22 g6.src.plugins.hull uses g6.src.utils.event.events✕
- Connections
- 1 pair of types, where a type in g6.src.plugins.hull uses a type in g6.src.utils.event.events.
- The types involved
packages.g6.src.plugins.hull.Hull→packages.g6.src.utils.event.events.ElementLifeCycleEvent
- Direction
- g6.src.plugins.hull uses g6.src.utils.event.events, so a change to g6.src.utils.event.events can break g6.src.plugins.hull, while a change to g6.src.plugins.hull can't break g6.src.utils.event.events.
- Position
- Below the diagonal: g6.src.plugins.hull uses a module listed above it, which is the healthy direction.
39→24 g6.src.plugins.hull uses g6.src.runtime.types✕
- Connections
- 1 pair of types, where a type in g6.src.plugins.hull uses a type in g6.src.runtime.types.
- The types involved
packages.g6.src.plugins.hull.Hull→packages.g6.src.runtime.types.RuntimeContext
- Direction
- g6.src.plugins.hull uses g6.src.runtime.types, so a change to g6.src.runtime.types can break g6.src.plugins.hull, while a change to g6.src.plugins.hull can't break g6.src.runtime.types.
- Position
- Below the diagonal: g6.src.plugins.hull uses a module listed above it, which is the healthy direction.
39→29 g6.src.plugins.hull uses g6.src.plugins.base-plugin✕
- Connections
- 1 pair of types, where a type in g6.src.plugins.hull uses a type in g6.src.plugins.base-plugin.
- The types involved
packages.g6.src.plugins.hull.Hull→packages.g6.src.plugins.base-plugin.BasePlugin
- Direction
- g6.src.plugins.hull uses g6.src.plugins.base-plugin, so a change to g6.src.plugins.base-plugin can break g6.src.plugins.hull, while a change to g6.src.plugins.hull can't break g6.src.plugins.base-plugin.
- Position
- Below the diagonal: g6.src.plugins.hull uses a module listed above it, which is the healthy direction.
40→4 g6.src.plugins.minimap uses g6.src.types.padding✕
- Connections
- 1 pair of types, where a type in g6.src.plugins.minimap uses a type in g6.src.types.padding.
- The types involved
packages.g6.src.plugins.minimap.MinimapOptions→packages.g6.src.types.padding.Padding
- Direction
- g6.src.plugins.minimap uses g6.src.types.padding, so a change to g6.src.types.padding can break g6.src.plugins.minimap, while a change to g6.src.plugins.minimap can't break g6.src.types.padding.
- Position
- Below the diagonal: g6.src.plugins.minimap uses a module listed above it, which is the healthy direction.
40→5 g6.src.plugins.minimap uses g6.src.types.placement✕
- Connections
- 1 pair of types, where a type in g6.src.plugins.minimap uses a type in g6.src.types.placement.
- The types involved
packages.g6.src.plugins.minimap.MinimapOptions→packages.g6.src.types.placement.Placement
- Direction
- g6.src.plugins.minimap uses g6.src.types.placement, so a change to g6.src.types.placement can break g6.src.plugins.minimap, while a change to g6.src.plugins.minimap can't break g6.src.types.placement.
- Position
- Below the diagonal: g6.src.plugins.minimap uses a module listed above it, which is the healthy direction.
40→8 g6.src.plugins.minimap uses g6.src.types.vector✕
- Connections
- 1 pair of types, where a type in g6.src.plugins.minimap uses a type in g6.src.types.vector.
- The types involved
packages.g6.src.plugins.minimap.Minimap→packages.g6.src.types.vector.Vector3
- Direction
- g6.src.plugins.minimap uses g6.src.types.vector, so a change to g6.src.types.vector can break g6.src.plugins.minimap, while a change to g6.src.plugins.minimap can't break g6.src.types.vector.
- Position
- Below the diagonal: g6.src.plugins.minimap uses a module listed above it, which is the healthy direction.
40→10 g6.src.plugins.minimap uses g6.src.runtime.canvas✕
- Connections
- 1 pair of types, where a type in g6.src.plugins.minimap uses a type in g6.src.runtime.canvas.
- The types involved
packages.g6.src.plugins.minimap.Minimap→packages.g6.src.runtime.canvas.Canvas
- Direction
- g6.src.plugins.minimap uses g6.src.runtime.canvas, so a change to g6.src.runtime.canvas can break g6.src.plugins.minimap, while a change to g6.src.plugins.minimap can't break g6.src.runtime.canvas.
- Position
- Below the diagonal: g6.src.plugins.minimap uses a module listed above it, which is the healthy direction.
40→17 g6.src.plugins.minimap uses g6.src.types.event✕
- Connections
- 1 pair of types, where a type in g6.src.plugins.minimap uses a type in g6.src.types.event.
- The types involved
packages.g6.src.plugins.minimap.Minimap→packages.g6.src.types.event.IGraphLifeCycleEvent
- Direction
- g6.src.plugins.minimap uses g6.src.types.event, so a change to g6.src.types.event can break g6.src.plugins.minimap, while a change to g6.src.plugins.minimap can't break g6.src.types.event.
- Position
- Below the diagonal: g6.src.plugins.minimap uses a module listed above it, which is the healthy direction.
40→24 g6.src.plugins.minimap uses g6.src.runtime.types✕
- Connections
- 1 pair of types, where a type in g6.src.plugins.minimap uses a type in g6.src.runtime.types.
- The types involved
packages.g6.src.plugins.minimap.Minimap→packages.g6.src.runtime.types.RuntimeContext
- Direction
- g6.src.plugins.minimap uses g6.src.runtime.types, so a change to g6.src.runtime.types can break g6.src.plugins.minimap, while a change to g6.src.plugins.minimap can't break g6.src.runtime.types.
- Position
- Below the diagonal: g6.src.plugins.minimap uses a module listed above it, which is the healthy direction.
40→29 g6.src.plugins.minimap uses g6.src.plugins.base-plugin✕
- Connections
- 1 pair of types, where a type in g6.src.plugins.minimap uses a type in g6.src.plugins.base-plugin.
- The types involved
packages.g6.src.plugins.minimap.Minimap→packages.g6.src.plugins.base-plugin.BasePlugin
- Direction
- g6.src.plugins.minimap uses g6.src.plugins.base-plugin, so a change to g6.src.plugins.base-plugin can break g6.src.plugins.minimap, while a change to g6.src.plugins.minimap can't break g6.src.plugins.base-plugin.
- Position
- Below the diagonal: g6.src.plugins.minimap 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 — Event-Driven
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 56 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 11 | Medium |
| A07:2025 — Authentication Failures | 2 | High / Critical |
| A02:2025 — Security Misconfiguration | 1 | Medium |
Roadmap
Top priorities: Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED; Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. | +2.9 pts | Low | Vulnerability-disclosure Policy |
| Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with timebar.spec.ts. | +2.5 pts | Low | Test Quality |
| Resolve the 2 Assertions commented out finding(s) in Test Quality — start with canvas.spec.ts, timebar.spec.ts. | +2.5 pts | Low | Test Quality |
| Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.9 pts | Low | Supply-chain Provenance & Signing |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +2.9 pts | Medium | Observability |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +2.9 pts | Medium | Security & performance tooling |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +2.9 pts | Medium | Dependency Hygiene |
| Resolve the 14 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (2), REDACTED. | +2.8 pts | Medium | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| packages/g6/src/runtime/graph.ts | 5.9 | Mixed | God Classes: TooManyMethods: Graph |
| packages/g6/src/runtime/data.ts | 6.0 | Mixed | Explicit Debt: TodoComment |
| packages/g6/src/runtime/element.ts | 6.0 | Mixed | Explicit Debt: TodoComment |
| packages/g6/__tests__/unit/runtime/canvas.spec.ts | 6.2 | Mixed | Test Quality: Assertions commented out: getDevice |
| packages/g6-extension-react/__tests__/unit/attribute-changed-callback.spec.tsx | 6.7 | Mixed | Explicit Debt: TodoComment |
| packages/site/src/MarkdownDocumenter.ts | 7.0 | Mixed | Cyclomatic Complexity: MarkdownDocumenter._writeApiItemPage (cyclomatic 47) |
| packages/g6/__tests__/unit/plugins/timebar.spec.ts | 7.0 | Mixed | Test Quality: No assertions (empty test): chart type |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| packages/site/src/markdown/CustomMarkdownEmitter.ts | 7.4 | Mixed | Cyclomatic Complexity: CustomMarkdownEmitter.writeNode (cyclomatic 28) |
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 70 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 — 70 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, 406 of 423 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D11 Test Reliability — 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. Test reliability for the jest suite in packages/g6-extension-3d/ was NOT MEASURED: the dependency install for packages/g6-extension-3d/ failed in the analyzer sandbox (npm error code EUNSUPPORTEDPROTOCOL), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — 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. Test reliability for the jest suite in packages/g6-extension-react/ was NOT MEASURED: the dependency install for packages/g6-extension-react/ failed in the analyzer sandbox (npm error code EUNSUPPORTEDPROTOCOL), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — 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. Test reliability for the jest suite in packages/g6-ssr/ was NOT MEASURED: the dependency install for packages/g6-ssr/ failed in the analyzer sandbox (npm error code EUNSUPPORTEDPROTOCOL), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — 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. Test reliability for the jest suite in packages/g6/ was NOT MEASURED: the install for packages/g6/ left no `jest` binary under node_modules, so the suite could not be launched. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 48 production npm declaration(s) across 9 package.json (9 of them the product) were read for PINNING discipline (1 defect(s) reported), but the outdated/deprecated signal needs registry.npmjs.org, and no committed lockfile here resolves to the concrete versions that question is asked about, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares package.json manifests but commits no lockfile this pass can resolve (npm, pnpm, yarn and bun each write a different one, and `bun.lockb` is a binary format with no published shape), so the set of packages it actually ships is not resolvable from the checkout: its declarations carry version RANGES, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. Commit the lock and this dimension grades its production dependencies against registry.npmjs.org. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (packages/g6-ssr/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published 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. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/g6/src/types/index.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D43 Malicious Dependencies — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AXB2 Runtime readiness — 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. The dev server exited, and its output does not match a cause we recognise. (rule: unrecognised-exit). The renderer reported: the dev server (`npm run dev` in packages/cli/) exited before it served a page. Likely cause (not identified): the dev server exited, and its output does not match a cause we recognise. Last output: "> @antv/g6-cli@0.0.4 dev / > unbuild --stub / ℹ Stubbing g6-cli / ℹ Cleaning dist directory: ./dist" No runtime evidence was gathered.
- 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 DevServer (dev). the dev server (`npm run dev` in packages/cli/) exited before it served a page. Likely cause (not identified): the dev server exited, and its output does not match a cause we recognise. Last output: "> @antv/g6-cli@0.0.4 dev / > unbuild --stub / ℹ Stubbing g6-cli / ℹ Cleaning dist directory: ./dist" No runtime evidence was gathered.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 reads a prose claim (a path, a setting, a variable, a route, a version, a project, an install, a bare project name in a command) only in text identified as English: the cues that tell a claim from an absence, the past, a plan or an example are an English lexicon, and on other text they would let a false claim through. Links, image targets, fenced commands with an explicit path or a package-manager script, and env-fence variables are checked in every language. 'und' is text the identifier could not name (too short, mixed script, no function words).
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 53 further occurrence(s) are not listed individually; the score already reflects all 93.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 326 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- 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".
- 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
25 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MarkdownDocumenter._writeApiItemPage at 47. 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 MarkdownEmitter.writeNode at 18 — 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: packages/site/src/markdown/MarkdownEmitter.ts (MarkdownEmitter.writeNode at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with MarkdownDocumenter._writeApiItemPage (cyclomatic 47), HTML.normalizeToPointerEvent (cyclomatic 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 6.8 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
40 method(s) exceeded the cognitive complexity threshold of 15; the worst was HTML.normalizeToPointerEvent at 66.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with HTML.normalizeToPointerEvent (cognitive 66). — Refactoring it lifts Cognitive Complexity from 6.4 to about 6.5/10.
D3 · God Classes
17 god class(es) detected.
What to do
- Resolve the 5 FunctionTooLong finding(s) in God Classes — start with robust-orientation.ts (2), base.ts, robust-subtract.ts. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 TooManyMethods finding(s) in God Classes — start with graph.ts, MarkdownDocumenter.ts, data.ts. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 FileTooLong finding(s) in God Classes — start with MarkdownDocumenter.ts, graph.ts, element.ts. — One of this dimension's main actionable groups (4 warning-level).
D5 · Coupling
8 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 7 of the 8 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 50 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D10 · Test Quality
16 skipped (15 with a documented reason), 6 zero-assertion, 1 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 731 tests.
What to do
- Resolve the 2 Assertions commented out finding(s) in Test Quality — start with canvas.spec.ts, timebar.spec.ts. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with timebar.spec.ts. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 No assertions finding(s) in Test Quality — start with optimize-viewport-transform.spec.ts, scroll-canvas.spec.ts, render-change-combo.spec.ts. — One of this dimension's main actionable groups (3 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `npm install --ignore-scripts` (no lockfile) in the repository root (5 tests); jest via `npm install --ignore-scripts` (no lockfile) in packages/cli/template-extension/ (0 tests); jest via `npm install --ignore-scripts` (no lockfile) in packages/g6/; jest via `npm install --ignore-scripts` (no lockfile) in packages/g6-extension-3d/; jest via `npm install --ignore-scripts` (no lockfile) in packages/g6-extension-react/; jest via `npm install --ignore-scripts` (no lockfile) in packages/g6-ssr/): measured (0 flaky).
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
No source file's living knowledge is concentrated in a single author. Counted over 107 of the 305 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
9 deducted task-comment markers across 40381 LoC (0.0/KLoC) → score 10.0. 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 8 TodoComment finding(s) in Explicit Debt — start with Utilities.ts, attribute-changed-callback.spec.tsx, bbox.ts. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with layout-fruchterman-fix.ts. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 291 document(s) read across 9 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
1 naming inconsistencies among 15 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `shapeID` spells `ID` where 14 names in the project spell it `Id` finding(s) in Naming Consistency — start with element.ts. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (7 contexts). Contexts: bundle, cli, g6, g6-extension-3d, g6-extension-react, g6-ssr, site.
D24 · Comment Value
0 of 154 judged comments only repeat the code they sit on (0.0 %). 211 comment(s) in another language or script were not judged.
D26 · Project Cohesion
2 of 9 build units (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 (2). — One of this dimension's main actionable groups (2 recommendation-level).
D27 · Navigability
35 % of calls cross a namespace and 3 % go through an interface, but 97 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
56 finding(s): 0 critical, 49 high, 7 medium, 0 low. 32 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `packages/g6/src/types/index.ts` (line 1, line 2, line 3, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 14 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (14 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 32 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 (32 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D34 · Knowledge Freshness
48 of 107 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/g6/src/runtime/graph.ts. Counted over 107 of the 305 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 45 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (7), util.ts (2), canvas.ts (2). — One of this dimension's main actionable groups (45 recommendation-level).
- Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with graph.ts, element.ts, data.ts. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: graph.ts↔bbox.ts 50%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with graph.ts. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (REDACTED) is present but lists no reporting contact.
What to do
- Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. — packages/g6/src/plugins/watermark/util.ts:12
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — packages/bundle/index.html:9
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — packages/bundle/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.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `marker.animate()` moves (`Web Animations API keyframes`) 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. — packages/site/examples/animation/persistence/demo/fly-marker.js:12
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
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
ED3 · Event naming
- `GraphLifeCycleEvent` reads as an instruction, not a fact that happened: events describe something that already occurred. Name new events for the fact that occurred (e.g. `OrderPlaced`). Do not rename this one if it is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it, and a clearer name does not pay for that. If it has never been written or sent, renaming it now is safe. — packages/g6/src/utils/event/events.ts:17
- `AnimateEvent` reads as an instruction, not a fact that happened: events describe something that already occurred. Name new events for the fact that occurred (e.g. `OrderPlaced`). Do not rename this one if it is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it, and a clearer name does not pay for that. If it has never been written or sent, renaming it now is safe. — packages/g6/src/utils/event/events.ts:40
- `ElementLifeCycleEvent` reads as an instruction, not a fact that happened: events describe something that already occurred. Name new events for the fact that occurred (e.g. `OrderPlaced`). Do not rename this one if it is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it, and a clearer name does not pay for that. If it has never been written or sent, renaming it now is safe. — packages/g6/src/utils/event/events.ts:51
- `ViewportEvent` reads as an instruction, not a fact that happened: events describe something that already occurred. Name new events for the fact that occurred (e.g. `OrderPlaced`). Do not rename this one if it is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it, and a clearer name does not pay for that. If it has never been written or sent, renaming it now is safe. — packages/g6/src/utils/event/events.ts:67
What to do
- Name new events in the past tense: they record facts that already happened. Do not rename an event that is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — packages/g6-extension-react/__tests__/unit/attribute-changed-callback.spec.tsx:4
- `getTransforms` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/g6/src/runtime/transform.ts:22
- `boundHandlePinch` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/g6/src/utils/shortcut.ts:24
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
- 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
- packages/site/docs/manual/behavior/ClickSelect.en.mdx names Node.js 4, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/behavior/ClickSelect.en.mdx:185
- packages/site/docs/manual/behavior/CollapseExpand.en.mdx names Node.js 4, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/behavior/CollapseExpand.en.mdx:189
- packages/site/docs/manual/behavior/CollapseExpand.en.mdx names Node.js 5, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/behavior/CollapseExpand.en.mdx:190
- packages/site/docs/manual/behavior/CreateEdge.zh.mdx names Node.js 4, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/behavior/CreateEdge.zh.mdx:130
- packages/site/docs/manual/behavior/DragCanvas.zh.mdx names Node.js 4, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/behavior/DragCanvas.zh.mdx:200
- packages/site/docs/manual/behavior/OptimizeViewportTransform.zh.mdx names Node.js 4, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/behavior/OptimizeViewportTransform.zh.mdx:209
- packages/site/docs/manual/behavior/ScrollCanvas.zh.mdx names Node.js 4, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/behavior/ScrollCanvas.zh.mdx:216
- packages/site/docs/manual/behavior/ZoomCanvas.zh.mdx names Node.js 4, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/behavior/ZoomCanvas.zh.mdx:272
- packages/site/docs/manual/further-reading/bundle.en.md names Webpack 4, but the manifest declares `webpack` ^5.99.8. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/further-reading/bundle.en.md:44
- packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx names Node.js 4, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:155
- packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx names Node.js 5, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:157
- packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx names Node.js 6, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:158
- packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx names Node.js 7, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:159
- packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx names Node.js 8, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:160
- packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx names Node.js 9, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:161
- packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx names Node.js 10, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:162
- packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx names Node.js 11, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:163
- packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx names Node.js 12, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:164
- packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx names Node.js 13, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:165
- packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx names Node.js 14, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:166
- packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx names Node.js 15, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:167
What to do
- Reconcile the README with reality: packages/site/docs/manual/behavior/ClickSelect.en.mdx names Node.js 4, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`; packages/site/docs/manual/behavior/CollapseExpand.en.mdx names Node.js 4, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`; packages/site/docs/manual/behavior/CollapseExpand.en.mdx names Node.js 5, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`; packages/site/docs/manual/behavior/CreateEdge.zh.mdx names Node.js 4, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`; packages/site/docs/manual/behavior/DragCanvas.zh.mdx names Node.js 4, but the repository declares engines `^18.0.0 || >=20.0.0`, engines `>=22.12.0`.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 10 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:7
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:31
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
- `existsSync` in `exportToFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/g6-ssr/src/graph.ts:53
- `lstatSync` in `exportToFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/g6-ssr/src/graph.ts:54
- `writeFileSync` in `exportToFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/g6-ssr/src/graph.ts:59
- `execSync` in `runApiExtractor` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/site/scripts/generate-api.ts:87, packages/site/scripts/generate-api.ts:89
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety
R10 · Code Duplication
- 8 duplicated blocks under packages/g6/src/ have copies in at least two of the sibling directories behaviors, plugins, runtime, utils — 4 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 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 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. — packages/g6/src/behaviors/create-edge.ts:214
- 8 duplicated blocks under packages/g6/src/plugins/ have copies in at least two of the sibling directories background, contextmenu, edge-bundling, edge-filter-lens, fisheye, minimap (+3 more sibling(s) not listed) — 4 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 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 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. — packages/g6/src/plugins/edge-filter-lens/index.ts:153
- 6 duplicated blocks under packages/ have copies in at least two of the sibling directories cli, g6, g6-extension-3d, g6-extension-react — 5 of them are reported below, and 1 is 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 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 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 6 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. — packages/cli/template-extension/vite.config.js:8
- 6 duplicated blocks under packages/g6/src/elements/ have copies in at least two of the sibling directories combos, edges, nodes, shapes — 5 of them are reported below, and 1 is 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 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 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 6 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. — packages/g6/src/elements/nodes/base-node.ts:245
- packages/g6/src/plugins/hull/hull/robust-subtract.ts:3 · packages/g6/src/plugins/hull/hull/robust-sum.ts:3 — these 2 files are line-for-line copies of one another — 117 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/g6/src/plugins/hull/hull/robust-subtract.ts:3
- packages/g6/src/elements/nodes/circle.ts:25 · packages/g6/src/elements/nodes/ellipse.ts:25 — the two spans are one implementation copied and then locally edited — 214 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. — packages/g6/src/elements/nodes/circle.ts:25
- packages/g6/src/runtime/element.ts:816 · packages/g6/src/runtime/element.ts:854 — 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. — packages/g6/src/runtime/element.ts:816
- packages/g6-extension-3d/src/elements/capsule.ts:15 · packages/g6-extension-3d/src/elements/cylinder.ts:15 · packages/g6-extension-3d/src/elements/torus.ts:15 — the 3 copies are spread across 3 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. — packages/g6-extension-3d/src/elements/capsule.ts:15
- packages/g6/src/runtime/data.ts:565 · packages/g6/src/runtime/data.ts:649 — 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. — packages/g6/src/runtime/data.ts:565
- packages/g6/src/behaviors/drag-canvas.ts:206 · packages/g6/src/behaviors/scroll-canvas.ts:164 — 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. — packages/g6/src/behaviors/drag-canvas.ts:206
- packages/g6/src/plugins/edge-filter-lens/index.ts:153 · packages/g6/src/plugins/fisheye/index.ts:164 — 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. — packages/g6/src/plugins/edge-filter-lens/index.ts:153
- packages/g6/src/plugins/fisheye/index.ts:408 · packages/g6/src/plugins/fisheye/index.ts:436 — 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. — packages/g6/src/plugins/fisheye/index.ts:408
- packages/g6/src/elements/edges/cubic-horizontal.ts:12 · packages/g6/src/elements/edges/cubic-vertical.ts:12 — the 2 copies are spread across 2 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — packages/g6/src/elements/edges/cubic-horizontal.ts:12
- packages/cli/template-extension/vite.config.js:8 · packages/g6/vite.config.js:14 — 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. — packages/cli/template-extension/vite.config.js:8
- packages/g6/src/behaviors/fix-element-size.ts:308 · packages/g6/src/behaviors/optimize-viewport-transform.ts:106 — 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. — packages/g6/src/behaviors/fix-element-size.ts:308
- packages/g6/src/plugins/snapline/index.ts:290 · packages/g6/src/plugins/snapline/index.ts:309 — 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. — packages/g6/src/plugins/snapline/index.ts:290
- packages/g6/src/runtime/data.ts:760 · packages/g6/src/runtime/data.ts:793 — 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. — packages/g6/src/runtime/data.ts:760
- packages/g6/src/utils/layout.ts:64 · packages/g6/src/utils/layout.ts:230 — 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. — packages/g6/src/utils/layout.ts:64
- packages/cli/template-extension/rollup.config.mjs:17 · packages/g6-extension-3d/rollup.config.mjs:15 · packages/g6/rollup.config.mjs:15 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/cli/template-extension/rollup.config.mjs:17
- packages/g6/src/behaviors/scroll-canvas.ts:87 · packages/g6/src/behaviors/zoom-canvas.ts:95 — 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. — packages/g6/src/behaviors/scroll-canvas.ts:87
- packages/g6/src/plugins/edge-filter-lens/index.ts:342 · packages/g6/src/plugins/edge-filter-lens/index.ts:365 — 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. — packages/g6/src/plugins/edge-filter-lens/index.ts:342
- packages/g6/src/plugins/bubble-sets.ts:231 · packages/g6/src/plugins/hull/index.ts:169 — the two spans are one implementation copied and then locally edited — 151 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. — packages/g6/src/plugins/bubble-sets.ts:231
- packages/g6/src/runtime/element.ts:725 · packages/g6/src/runtime/element.ts:774 — 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. — packages/g6/src/runtime/element.ts:725
- packages/g6/src/runtime/graph.ts:303 · packages/g6/src/runtime/graph.ts:363 · packages/g6/src/runtime/graph.ts:445 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/g6/src/runtime/graph.ts:303
- packages/cli/template-extension/rollup.config.mjs:19 · packages/g6-extension-3d/rollup.config.mjs:17 · packages/g6-extension-react/rollup.config.mjs:18 · packages/g6/rollup.config.mjs:17 — the 4 copies are spread across 4 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/cli/template-extension/rollup.config.mjs:19
- packages/g6/src/plugins/edge-bundling/index.ts:289 · packages/g6/src/plugins/title/index.ts:139 — the two spans are one implementation copied and then locally edited — 78 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. — packages/g6/src/plugins/edge-bundling/index.ts:289
- packages/g6-extension-3d/src/behaviors/zoom-canvas-3d.ts:24 · packages/g6/src/behaviors/zoom-canvas.ts:163 — the two spans are one implementation copied and then locally edited — 94 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. — packages/g6-extension-3d/src/behaviors/zoom-canvas-3d.ts:24
- packages/g6/src/behaviors/auto-adapt-label.ts:272 · packages/g6/src/behaviors/scroll-canvas.ts:195 — the two spans are one implementation copied and then locally edited — 65 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/g6/src/behaviors/auto-adapt-label.ts:272
- packages/g6/src/behaviors/drag-element.ts:192 · packages/g6/src/behaviors/drag-element.ts:462 — 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. — packages/g6/src/behaviors/drag-element.ts:192
- packages/g6/src/runtime/graph.ts:1529 · packages/g6/src/runtime/graph.ts:1561 — 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. — packages/g6/src/runtime/graph.ts:1529
- packages/g6/src/behaviors/click-select.ts:121 · packages/g6/src/behaviors/focus-element.ts:58 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/g6/src/behaviors/click-select.ts:121
- packages/g6/src/plugins/hull/hull/robust-orientation.ts:36 · packages/g6/src/plugins/hull/hull/robust-orientation.ts:52 — 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. — packages/g6/src/plugins/hull/hull/robust-orientation.ts:36
- packages/g6/src/runtime/element.ts:485 · packages/g6/src/runtime/element.ts:575 — 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. — packages/g6/src/runtime/element.ts:485
- packages/g6/src/behaviors/brush-select.ts:337 · packages/g6/src/behaviors/click-select.ts:281 · packages/g6/src/behaviors/create-edge.ts:207 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/g6/src/behaviors/brush-select.ts:337
- packages/g6/src/behaviors/create-edge.ts:199 · packages/g6/src/behaviors/drag-element.ts:227 — 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. — packages/g6/src/behaviors/create-edge.ts:199
- packages/g6/src/behaviors/drag-element.ts:370 · packages/g6/src/behaviors/hover-activate.ts:187 — the two spans are one implementation copied and then locally edited — 54 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. — packages/g6/src/behaviors/drag-element.ts:370
- packages/g6/src/elements/nodes/base-node.ts:245 · packages/g6/src/elements/shapes/contour.ts:84 — the two spans are one implementation copied and then locally edited — 53 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. — packages/g6/src/elements/nodes/base-node.ts:245
- packages/g6/src/plugins/hull/hull/robust-orientation.ts:23 · packages/g6/src/plugins/hull/hull/robust-orientation.ts:67 — 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. — packages/g6/src/plugins/hull/hull/robust-orientation.ts:23
- packages/g6/src/plugins/hull/hull/robust-orientation.ts:109 · packages/g6/src/plugins/hull/hull/robust-orientation.ts:179 — 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. — packages/g6/src/plugins/hull/hull/robust-orientation.ts:109
- packages/g6/src/plugins/hull/hull/robust-orientation.ts:147 · packages/g6/src/plugins/hull/hull/robust-orientation.ts:265 — 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. — packages/g6/src/plugins/hull/hull/robust-orientation.ts:147
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
- packages/g6/src/plugins/legend.ts:2 imports @antv/component/lib/ui/legend/types, 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. — packages/g6/src/plugins/legend.ts:2
- packages/g6/src/plugins/minimap/index.ts:5 imports packages/g6/src/spec/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/g6/src/plugins/minimap/index.ts:5
What to do
- Fix the listed violations: import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (1 row); move the shared test helper into a source directory production code may depend on (1 row).
R2 · Cyclomatic Complexity
- inferStyle has cyclomatic complexity 27 and cognitive complexity 36; 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. — packages/g6/src/runtime/animation.ts:82
- robustSubtract has cyclomatic complexity 26 and cognitive complexity 42; 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. — packages/g6/src/plugins/hull/hull/robust-subtract.ts:17
- linearExpansionSum has cyclomatic complexity 26 and cognitive complexity 42; 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. — packages/g6/src/plugins/hull/hull/robust-sum.ts:17
- caseMindmap has cyclomatic complexity 25 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — packages/g6/__tests__/demos/case-mindmap.ts:33
- replaceTranslateInTransform has cyclomatic complexity 21 and cognitive complexity 32; 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. — packages/g6/src/utils/transform.ts:14
- getLabelPositionStyle has cyclomatic complexity 18 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/g6/src/utils/edge.ts:59
- aStarSearch has cyclomatic complexity 17 and cognitive complexity 33; 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. — packages/g6/src/utils/router/shortest-path.ts:255
- getPolygonTextStyleByPlacement has cyclomatic complexity 17 and cognitive complexity 31; 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. — packages/g6/src/utils/polygon.ts:22
- (anonymous) has cyclomatic complexity 17 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/g6/src/plugins/snapline/index.ts:280
- orth has cyclomatic complexity 16 and cognitive complexity 30; 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. — packages/g6/src/utils/router/orth.ts:42
- groupByEndpoints has cyclomatic complexity 16 and cognitive complexity 28; 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. — packages/g6/src/transforms/process-parallel-edges.ts:319
- init has cyclomatic complexity 16 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. — packages/cli/src/index.ts:29
- forwardCanvasEvents has cyclomatic complexity 15 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/g6/src/runtime/behavior.ts:68
- onMaskDrag 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. — packages/g6/src/plugins/minimap/index.ts:424
- (anonymous) has cyclomatic complexity 15 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/g6/src/utils/change.ts:20
- caseIndentedTree 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. — packages/g6/__tests__/demos/case-indented-tree.ts:43
- (anonymous) has cyclomatic complexity 14 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/g6/src/transforms/process-parallel-edges.ts:201
- getArcLoopPath has cyclomatic complexity 14 and cognitive complexity 17; 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. — packages/g6/src/utils/edge.ts:455
- monotoneConvexHull2D has cyclomatic complexity 14 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. — packages/g6/src/plugins/hull/hull/monotone-convex-hull-2d.ts:8
- autoSnapToLine has cyclomatic complexity 13 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/g6/src/plugins/snapline/index.ts:188
- fitView has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/g6/src/runtime/viewport.ts:212
- segmentsIntersect has cyclomatic complexity 13 and cognitive complexity 10; 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. — packages/g6/src/plugins/hull/hull/robust-segment-intersect.ts:18
- _concave has cyclomatic complexity 12 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. — packages/g6/src/plugins/hull/hull/index.ts:120
- _setOptions has cyclomatic complexity 12 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. — packages/g6/src/runtime/graph.ts:134
- execute 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. — packages/g6/src/layouts/snake.ts:141
- enableSnap has cyclomatic complexity 11 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 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. — packages/g6/src/plugins/snapline/index.ts:230
- getEndpoints has cyclomatic complexity 11 and cognitive complexity 10; 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. — packages/g6/src/elements/edges/base-edge.ts:272
- getPolylineLoopControlPoints has cyclomatic complexity 11 and cognitive complexity 10; 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. — packages/g6/src/utils/edge.ts:610
R3 · Large Files
- packages/g6/src/runtime/graph.ts has 1928 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/g6/src/runtime/graph.ts:1
- packages/g6/src/runtime/element.ts has 811 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/g6/src/runtime/element.ts:1
- packages/g6/src/runtime/data.ts has 795 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/g6/src/runtime/data.ts:1
- packages/g6/src/utils/edge.ts has 680 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/g6/src/utils/edge.ts:1
- packages/g6/src/utils/element.ts has 501 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/g6/src/utils/element.ts:1
- packages/g6/src/plugins/minimap/index.ts has 449 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/g6/src/plugins/minimap/index.ts:1
- packages/g6/src/behaviors/drag-element.ts has 447 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/g6/src/behaviors/drag-element.ts:1
- packages/g6/src/plugins/hull/hull/robust-orientation.ts has 429 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/g6/src/plugins/hull/hull/robust-orientation.ts:1
- packages/g6/src/elements/edges/base-edge.ts has 418 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/g6/src/elements/edges/base-edge.ts:1
- packages/g6/src/elements/nodes/base-node.ts has 415 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/g6/src/elements/nodes/base-node.ts:1
- packages/g6/src/utils/router/shortest-path.ts has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/g6/src/utils/router/shortest-path.ts: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. (×6) — packages/cli/src/index.ts:1, packages/g6-ssr/bin/g6-ssr.js:1, packages/bundle/src/index.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- `packages/site` is TypeScript, but a type error in it cannot fail anything this repository runs: its `format` script (`prettier --write "**/*.{js,jsx,ts,tsx,json,md}"`) 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. — packages/site/package.json:31
- The package in `packages/site` declares the lint script `lint` (`eslint ./src --quiet && prettier ./src --check`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `packages/site` (or the workspace's task runner). — packages/site/package.json:33
- The package in `packages/cli/template-extension` declares the lint script `lint` (`eslint ./src __tests__ --quiet && prettier ./src __tests__ --check`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `packages/cli/template-extension` (or the workspace's task runner). — packages/cli/template-extension/package.json:20
R7 · Dead Code
- 15 file(s) (~643 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
- Unreachable from the 26 application, 33 tooling and 470 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (26 application, 33 tooling, 470 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 (×2) — packages/g6/src/types/plugin.ts, packages/g6/src/types/utility.ts
- Nothing imports this binding — it is safe to review for removal. (×4) — packages/g6/src/animations/index.ts:23, packages/g6/src/plugins/hull/hull/format.ts:29, packages/g6/src/utils/position.ts:77, …
- Nothing ultimately consumes this binding: its only referrer is the re-export in packages/g6/src/constants/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 packages/g6/src/constants/index.ts in the same commit, or the barrel will import a name that no longer exists. — packages/g6/src/constants/change.ts:1
- Nothing ultimately consumes this binding: its only referrer is the re-export in packages/g6/src/types/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 packages/g6/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists. (×4) — packages/g6/src/types/animation.ts:7, packages/g6/src/types/element.ts:66, packages/g6/src/types/graphlib.ts:16, …
- Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used. — packages/g6/src/runtime/graph.ts:1937
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. (×2) — scripts/demo-to-test/core/parser.js:4, packages/cli/template-extension/__tests__/utils/to-match-svg-snapshot.ts:6
- Declared in the root 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. (×4) — package.json:36, package.json:45, package.json:55, …
- Declared in packages/bundle/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. — packages/bundle/package.json:19
- Every import is type-only — move it to devDependencies. (×4) — packages/g6-extension-3d/src/utils/geometry.ts:1, packages/g6-extension-3d/src/elements/base-node-3d.ts:4, packages/g6-extension-react/src/react-node/node.tsx:1, …
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- packages/g6/src/elements/base-element.ts → packages/g6/src/elements/shapes/index.ts → packages/g6/src/elements/shapes/badge.ts → packages/g6/src/elements/shapes/base-shape.ts → packages/g6/src/utils/element.ts → packages/g6/src/elements/index.ts → packages/g6/src/elements/combos/index.ts → packages/g6/src/elements/combos/base-combo.ts → packages/g6/src/elements/nodes/index.ts → packages/g6/src/elements/nodes/base-node.ts → packages/g6/src/elements/base-element.ts (one verified cycle inside a mutually-dependent group of 36 files) — packages/g6/src/elements/base-element.ts:5
- packages/g6/src/exports.ts → packages/g6/src/runtime/graph.ts → packages/g6/src/runtime/transform.ts → packages/g6/src/transforms/index.ts → packages/g6/src/transforms/get-edge-actual-ends.ts → packages/g6/src/exports.ts (one verified cycle inside a mutually-dependent group of 6 files) — packages/g6/src/exports.ts:103
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `alignFields` is exported and takes `refObject: Record<string, any>` from its caller, and it calls itself at line 20 (`alignFields`) with a piece of `refObject` — and nowhere in `alignFields` 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 `alignFields` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/g6/src/plugins/history/util.ts:20
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
X24 · Document value interpolated into markup unescaped
- `innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/g6/src/plugins/utils/dom.ts:59
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — packages/g6-extension-react/src/react-node/render18.ts:46
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
- 14/17 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
- ~5.1 `!` null assertions per 1k TypeScript source lines — 201 assertion(s) across the 39464 source line(s) of the 315 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: packages/g6/src/runtime/graph.ts (40), packages/g6/src/runtime/element.ts (12), packages/g6/src/layouts/fishbone.ts (7). 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 |
| 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 | 71.7 | Strong | Strongest area. |
| Architecture | 73.4 | Adequate — gated by R9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 49.0 | Weak — gated by M4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 33.8 | Weak — gated by R8, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 33.4 | Weak — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 43.6 | Weak — gated by AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60.0 | Adequate | Acceptable, with room to improve. |
Unscored — 3 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 6 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 — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 55 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- 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 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.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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 — the dev server (`npm run dev` in packages/cli/) exited before it served a page. Likely cause (not identified): the dev server exited, and its output does not match a cause we recognise. Last output: "> @antv/g6-cli@0.0.4 dev / > unbuild --stub / ℹ Stubbing g6-cli / ℹ Cleaning dist directory: ./dist" No runtime evidence was gathered. 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 — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D12 Dependency Hygiene — Not scored — 48 production npm declaration(s) across 9 package.json (9 of them the product) were read for PINNING discipline (1 defect(s) reported), but the outdated/deprecated signal needs registry.npmjs.org, and no committed lockfile here resolves to the concrete versions that question is asked about, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — npm licences not graded — this npm repository commits no lockfile this pass can resolve
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- 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: the JavaScript/TypeScript half could not be measured — the jest suite in packages/cli/template-extension/ ran and not one test passed (FAIL __tests__/unit/default.spec.ts), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (9 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
- 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 — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage 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 tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, 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.
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: 326 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
- 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 — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 61 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
- Orphaned knowledge packages/g6/src/runtime/graph.ts:1
- Orphaned knowledge packages/g6/src/runtime/element.ts:1
- Orphaned knowledge packages/g6/src/runtime/data.ts:1
- Assertions commented out: getDevice packages/g6/__tests__/unit/runtime/canvas.spec.ts:13
- Assertions commented out: event callback packages/g6/__tests__/unit/plugins/timebar.spec.ts:62
- <select> without a programmatic label packages/bundle/index.html:9
- No assertions (empty test): chart type packages/g6/__tests__/unit/plugins/timebar.spec.ts:58
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import 'lodash' scripts/demo-to-test/core/parser.js:4
- Unlisted import 'xml-formatter' packages/cli/template-extension/__tests__/utils/to-match-svg-snapshot.ts:6
- Import cycle (10 files) packages/g6/src/elements/base-element.ts:5
- Import cycle (5 files) packages/g6/src/exports.ts:103
Serious — 225 finding(s)
- TodoComment packages/site/src/utils/Utilities.ts:32
- TodoComment packages/g6-extension-react/__tests__/unit/attribute-changed-callback.spec.tsx:3
- TodoComment packages/g6/src/utils/bbox.ts:246
- TodoComment packages/g6/src/utils/path.ts:74
- TodoComment packages/g6/src/runtime/data.ts:830
- TodoComment packages/g6/src/runtime/element.ts:645
- TodoComment packages/g6/__tests__/unit/runtime/canvas.spec.ts:20
- TodoComment packages/g6/__tests__/demos/element-node-donut.ts:118
- No test reaches this file packages/cli/src/index.ts:1
- No test reaches this file packages/g6-ssr/bin/g6-ssr.js:1
- No test reaches this file packages/bundle/src/index.ts:1
- No test reaches this file packages/g6/scripts/tag.mjs:1
- No test reaches this file packages/g6/scripts/version.mjs:1
- No test reaches this file packages/cli/index.js:1
- FunctionTooLong: base.create packages/g6/src/themes/base.ts:60
- FunctionTooLong: robust-orientation.orientation_5 packages/g6/src/plugins/hull/hull/robust-orientation.ts:73
- FunctionTooLong: robust-orientation.orientation_5.orientation5Exact packages/g6/src/plugins/hull/hull/robust-orientation.ts:79
- FunctionTooLong: robust-subtract.robustSubtract packages/g6/src/plugins/hull/hull/robust-subtract.ts:17
- FunctionTooLong: robust-sum.linearExpansionSum packages/g6/src/plugins/hull/hull/robust-sum.ts:17
- Sync-over-async blocking packages/g6-ssr/src/graph.ts:53
- Sync-over-async blocking packages/g6-ssr/src/graph.ts:54
- Sync-over-async blocking packages/g6-ssr/src/graph.ts:59
- Sync-over-async blocking packages/site/scripts/generate-api.ts:87
- Sync-over-async blocking packages/site/scripts/generate-api.ts:89
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TooManyMethods: Graph packages/g6/src/runtime/graph.ts:66
- TooManyMethods: MarkdownDocumenter packages/site/src/MarkdownDocumenter.ts:115
- TooManyMethods: DataController packages/g6/src/runtime/data.ts:33
- TooManyMethods: ElementController packages/g6/src/runtime/element.ts:43
- FileTooLong: src/MarkdownDocumenter.ts packages/site/src/MarkdownDocumenter.ts
- FileTooLong: runtime/graph.ts packages/g6/src/runtime/graph.ts
- FileTooLong: runtime/element.ts packages/g6/src/runtime/element.ts
- FileTooLong: runtime/data.ts packages/g6/src/runtime/data.ts
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (11 lines × 2 locations) packages/g6/src/behaviors/create-edge.ts:199
- Duplicated block (11 lines × 2 locations) packages/g6/src/plugins/hull/hull/robust-orientation.ts:23
- Duplicated block (11 lines × 2 locations) packages/g6/src/plugins/hull/hull/robust-orientation.ts:109
- Duplicated block (11 lines × 2 locations) packages/g6/src/plugins/hull/hull/robust-orientation.ts:147
- No assertions: destroy packages/g6/__tests__/unit/behaviors/optimize-viewport-transform.spec.ts:84
- No assertions: destroy packages/g6/__tests__/unit/behaviors/scroll-canvas.spec.ts:125
- No assertions: bug packages/g6/__tests__/bugs/render-change-combo.spec.ts:4
- REDACTED
- REDACTED
- REDACTED
- ClassTooLong: Graph packages/g6/src/runtime/graph.ts:66
- ClassTooLong: ElementController packages/g6/src/runtime/element.ts:43
- ClassTooLong: DataController packages/g6/src/runtime/data.ts:33
- Duplicated block (20 lines × 2 locations) packages/g6/src/behaviors/drag-canvas.ts:206
- Duplicated block (20 lines × 2 locations) packages/g6/src/plugins/edge-filter-lens/index.ts:153
- Duplicated block (20 lines × 2 locations) packages/g6/src/plugins/fisheye/index.ts:408
- Duplicated block (17 lines × 2 locations) packages/g6/src/plugins/snapline/index.ts:290
- Duplicated block (17 lines × 2 locations) packages/g6/src/runtime/data.ts:760
- Duplicated block (17 lines × 2 locations) packages/g6/src/utils/layout.ts:64
- Duplicated block (12 lines × 2 locations) packages/g6/src/behaviors/click-select.ts:121
- Duplicated block (12 lines × 2 locations) packages/g6/src/plugins/hull/hull/robust-orientation.ts:36
- Duplicated block (12 lines × 2 locations) packages/g6/src/runtime/element.ts:485
- Duplication concentrated across 4 sibling directories (6 clone groups) packages/cli/template-extension/vite.config.js:8
- Duplication concentrated across 4 sibling directories (6 clone groups) packages/g6/src/elements/nodes/base-node.ts:245
- Duplicated block (18 lines × 2 locations) packages/cli/template-extension/vite.config.js:8
- Duplicated block (18 lines × 2 locations) packages/g6/src/behaviors/fix-element-size.ts:308
- Duplicated block (16 lines × 2 locations) packages/g6/src/behaviors/scroll-canvas.ts:87
- Duplicated block (16 lines × 2 locations) packages/g6/src/plugins/edge-filter-lens/index.ts:342
- Duplicated block with local edits (13 matched lines × 2 locations) packages/g6-extension-3d/src/behaviors/zoom-canvas-3d.ts:24
- Duplicated block with local edits (13 matched lines × 2 locations) packages/g6/src/behaviors/auto-adapt-label.ts:272
- Duplicated block (13 lines × 2 locations) packages/g6/src/behaviors/drag-element.ts:192
- Duplicated block (13 lines × 2 locations) packages/g6/src/runtime/graph.ts:1529
- Duplicated block with local edits (11 matched lines × 2 locations) packages/g6/src/behaviors/drag-element.ts:370
- Duplicated block with local edits (11 matched lines × 2 locations) packages/g6/src/elements/nodes/base-node.ts:245
- Boundary violation [package:third-party-deep-import] packages/g6/src/plugins/legend.ts:2
- Boundary violation [package:test-suite-dependency] packages/g6/src/plugins/minimap/index.ts:5
- This package's lint script runs in no CI job packages/site/package.json:33
- This package's lint script runs in no CI job packages/cli/template-extension/package.json:20
- Unused dependency '@swc/core' package.json:45
- Unused dependency '@swc/core' packages/bundle/package.json:19
- <canvas> without a text alternative packages/g6/src/plugins/watermark/util.ts:12
- Page without a main landmark packages/bundle/index.html:2
- Animation without a prefers-reduced-motion guard packages/site/examples/animation/persistence/demo/fly-marker.js:12
- MarkdownDocumenter._writeApiItemPage (cyclomatic 47) packages/site/src/MarkdownDocumenter.ts:266
- HTML.normalizeToPointerEvent (cyclomatic 31) packages/g6/src/elements/nodes/html.ts:155
- CustomMarkdownEmitter.writeNode (cyclomatic 28) packages/site/src/markdown/CustomMarkdownEmitter.ts:38
- robust-subtract.robustSubtract (cyclomatic 26) packages/g6/src/plugins/hull/hull/robust-subtract.ts:17
- robust-sum.linearExpansionSum (cyclomatic 26) packages/g6/src/plugins/hull/hull/robust-sum.ts:17
- Animation.inferStyle (cyclomatic 25) packages/g6/src/runtime/animation.ts:82
- index.init (cyclomatic 24) packages/cli/src/index.ts:29
- DataController.computeZIndex (cyclomatic 23) packages/g6/src/runtime/data.ts:411
- MarkdownDocumenter._writeAPIMethods (cyclomatic 23) packages/site/src/MarkdownDocumenter.ts:811
- MarkdownDocumenter._writeExcerptTokens (cyclomatic 21) packages/site/src/MarkdownDocumenter.ts:688
- MarkdownDocumenter._writePackageOrNamespaceTables (cyclomatic 20) packages/site/src/MarkdownDocumenter.ts:1197
- FishboneLayout.doLayout (cyclomatic 19) packages/g6/src/layouts/fishbone.ts:93
- ClickSelect.updateState (cyclomatic 19) packages/g6/src/behaviors/click-select.ts:167
- transform.replaceTranslateInTransform (cyclomatic 19) packages/g6/src/utils/transform.ts:14
- MarkdownDocumenter._writeClassTables (cyclomatic 19) packages/site/src/MarkdownDocumenter.ts:1361
- polygon.getPolygonTextStyleByPlacement (cyclomatic 18) packages/g6/src/utils/polygon.ts:22
- edge.getLabelPositionStyle (cyclomatic 17) packages/g6/src/utils/edge.ts:59
- shortest-path.aStarSearch (cyclomatic 17) packages/g6/src/utils/router/shortest-path.ts:255
- BubbleSets.getPath (cyclomatic 17) packages/g6/src/plugins/bubble-sets.ts:135
- Snapline.calcSnaplineMetadata (cyclomatic 17) packages/g6/src/plugins/snapline/index.ts:264
- MarkdownDocumenter._writeHeritageTypes (cyclomatic 17) packages/site/src/MarkdownDocumenter.ts:991
- orth.orth (cyclomatic 16) packages/g6/src/utils/router/orth.ts:42
- BaseShape.animate (cyclomatic 16) packages/g6/src/elements/shapes/base-shape.ts:164
- process-parallel-edges.groupByEndpoints (cyclomatic 16) packages/g6/src/transforms/process-parallel-edges.ts:319
- MarkdownDocumenter._writeInterfaceTables (cyclomatic 16) packages/site/src/MarkdownDocumenter.ts:1544
- Skipped test: attribute changed callback packages/g6-extension-react/__tests__/unit/attribute-changed-callback.spec.tsx:4
- Fixed-sleep synchronisation: should be collapsed packages/g6/__tests__/bugs/plugin-minimap-combo-collapsed.spec.ts:4
- One package at two majors across the workspace: @antv/layout
- FixmeComment packages/g6/__tests__/demos/layout-fruchterman-fix.ts:21
- HTML.normalizeToPointerEvent (cognitive 66) packages/g6/src/elements/nodes/html.ts:155
- MarkdownDocumenter._writeAPIMethods (cognitive 58) packages/site/src/MarkdownDocumenter.ts:811
- robust-subtract.robustSubtract (cognitive 42) packages/g6/src/plugins/hull/hull/robust-subtract.ts:17
- robust-sum.linearExpansionSum (cognitive 42) packages/g6/src/plugins/hull/hull/robust-sum.ts:17
- MarkdownDocumenter._writeExcerptTokens (cognitive 39) packages/site/src/MarkdownDocumenter.ts:688
- ClickSelect.updateState (cognitive 37) packages/g6/src/behaviors/click-select.ts:167
- MarkdownDocumenter._writeHeritageTypes (cognitive 37) packages/site/src/MarkdownDocumenter.ts:991
- BaseShape.animate (cognitive 35) packages/g6/src/elements/shapes/base-shape.ts:164
- CustomMarkdownEmitter.writeNode (cognitive 35) packages/site/src/markdown/CustomMarkdownEmitter.ts:38
- Animation.inferStyle (cognitive 34) packages/g6/src/runtime/animation.ts:82
- orth.orth (cognitive 30) packages/g6/src/utils/router/orth.ts:42
- shortest-path.aStarSearch (cognitive 30) packages/g6/src/utils/router/shortest-path.ts:255
- transform.replaceTranslateInTransform (cognitive 30) packages/g6/src/utils/transform.ts:14
- process-parallel-edges.groupByEndpoints (cognitive 28) packages/g6/src/transforms/process-parallel-edges.ts:319
- MarkdownDocumenter._localizeSection (cognitive 27) packages/site/src/MarkdownDocumenter.ts:2334
- MarkdownDocumenter._initPageDataForItem (cognitive 26) packages/site/src/MarkdownDocumenter.ts:202
- DataController.computeZIndex (cognitive 24) packages/g6/src/runtime/data.ts:411
- polygon.getPolygonTextStyleByPlacement (cognitive 24) packages/g6/src/utils/polygon.ts:22
- FishboneLayout.doLayout (cognitive 23) packages/g6/src/layouts/fishbone.ts:93
- BubbleSets.getPath (cognitive 23) packages/g6/src/plugins/bubble-sets.ts:135
- excerpt-token.parseExcerptTokens (cognitive 22) packages/site/src/utils/excerpt-token.ts:32
- MarkdownDocumenter._writeApiItemPage (cognitive 21) packages/site/src/MarkdownDocumenter.ts:266
- CollapseExpandCombo.beforeDraw (cognitive 20) packages/g6/src/transforms/collapse-expand-combo.ts:17
- Snapline.autoSnapToLine (cognitive 20) packages/g6/src/plugins/snapline/index.ts:188
- Snapline.calcSnaplineMetadata (cognitive 20) packages/g6/src/plugins/snapline/index.ts:264
- MarkdownDocumenter._writeClassTables (cognitive 20) packages/site/src/MarkdownDocumenter.ts:1361
- index.init (cognitive 19) packages/cli/src/index.ts:29
- BehaviorController.forwardCanvasEvents (cognitive 19) packages/g6/src/runtime/behavior.ts:68
- MarkdownDocumenter._writeParameterTables (cognitive 19) packages/site/src/MarkdownDocumenter.ts:1656
- edge.getLabelPositionStyle (cognitive 18) packages/g6/src/utils/edge.ts:59
- edge.getArcLoopPath (cognitive 17) packages/g6/src/utils/edge.ts:455
- LayoutController.getLayoutData (cognitive 17) packages/g6/src/runtime/layout.ts:287
- monotone-convex-hull-2d.monotoneConvexHull2D (cognitive 17) packages/g6/src/plugins/hull/hull/monotone-convex-hull-2d.ts:8
- MarkdownDocumenter._writePackageOrNamespaceTables (cognitive 17) packages/site/src/MarkdownDocumenter.ts:1197
- MarkdownDocumenter._writeInterfaceTables (cognitive 17) packages/site/src/MarkdownDocumenter.ts:1544
- SnakeLayout.execute (cognitive 16) packages/g6/src/layouts/snake.ts:141
- ElementController.updateElement (cognitive 16) packages/g6/src/runtime/element.ts:513
- Minimap.onMaskDrag (cognitive 16) packages/g6/src/plugins/minimap/index.ts:424
- ProcessParallelEdges.applyMergingStyle (cognitive 16) packages/g6/src/transforms/process-parallel-edges.ts:259
- DocTable.constructor (cognitive 16) packages/site/src/nodes/DocTable.ts:23
- MethodTooLong: CustomMarkdownEmitter.writeNode packages/site/src/markdown/CustomMarkdownEmitter.ts:38
- Change coupling: graph.ts ↔ bbox.ts packages/g6/src/runtime/graph.ts:1
- REDACTED
- REDACTED
- REDACTED
- Off the main sequence: @antv/g6
- Low cohesion: Fullscreen (LCOM4 4) packages/g6/src/plugins/fullscreen/index.ts:53
- Coverage not measured — JavaScript/TypeScript suite
- No structured logging
- Duplication concentrated across 4 sibling directories (8 clone groups) packages/g6/src/behaviors/create-edge.ts:214
- Duplication concentrated across 9 sibling directories (8 clone groups) packages/g6/src/plugins/edge-filter-lens/index.ts:153
- Wholesale file copy (117 identical lines × 2 files) packages/g6/src/plugins/hull/hull/robust-subtract.ts:3
- Duplicated block with local edits (23 matched lines × 2 locations) packages/g6/src/elements/nodes/circle.ts:25
- Duplicated block (22 lines × 2 locations) packages/g6/src/runtime/element.ts:816
- Duplicated block (21 lines × 3 locations) packages/g6-extension-3d/src/elements/capsule.ts:15
- Duplicated block (21 lines × 2 locations) packages/g6/src/runtime/data.ts:565
- Duplicated block (19 lines × 2 locations) packages/g6/src/elements/edges/cubic-horizontal.ts:12
- Duplicated block (16 lines × 3 locations) packages/cli/template-extension/rollup.config.mjs:17
- Duplicated block with local edits (15 matched lines × 2 locations) packages/g6/src/plugins/bubble-sets.ts:231
- Duplicated block (15 lines × 2 locations) packages/g6/src/runtime/element.ts:725
- Duplicated block (15 lines × 3 locations) packages/g6/src/runtime/graph.ts:303
- Duplicated block (14 lines × 4 locations) packages/cli/template-extension/rollup.config.mjs:19
- Duplicated block with local edits (14 matched lines × 2 locations) packages/g6/src/plugins/edge-bundling/index.ts:289
- Duplicated block (11 lines × 3 locations) packages/g6/src/behaviors/brush-select.ts:337
- Complex function inferStyle (cyclomatic 27, cognitive 36) packages/g6/src/runtime/animation.ts:82
- Complex function robustSubtract (cyclomatic 26, cognitive 42) packages/g6/src/plugins/hull/hull/robust-subtract.ts:17
- Complex function linearExpansionSum (cyclomatic 26, cognitive 42) packages/g6/src/plugins/hull/hull/robust-sum.ts:17
- Complex function caseMindmap (cyclomatic 25, cognitive 23) packages/g6/__tests__/demos/case-mindmap.ts:33
- Complex function replaceTranslateInTransform (cyclomatic 21, cognitive 32) packages/g6/src/utils/transform.ts:14
- Complex function getLabelPositionStyle (cyclomatic 18, cognitive 22) packages/g6/src/utils/edge.ts:59
- Complex function aStarSearch (cyclomatic 17, cognitive 33) packages/g6/src/utils/router/shortest-path.ts:255
- Complex function getPolygonTextStyleByPlacement (cyclomatic 17, cognitive 31) packages/g6/src/utils/polygon.ts:22
- Complex function (anonymous) (cyclomatic 17, cognitive 20) packages/g6/src/plugins/snapline/index.ts:280
- Complex function orth (cyclomatic 16, cognitive 30) packages/g6/src/utils/router/orth.ts:42
- Complex function groupByEndpoints (cyclomatic 16, cognitive 28) packages/g6/src/transforms/process-parallel-edges.ts:319
- Complex function init (cyclomatic 16, cognitive 16) packages/cli/src/index.ts:29
- Complex function forwardCanvasEvents (cyclomatic 15, cognitive 19) packages/g6/src/runtime/behavior.ts:68
- Complex function onMaskDrag (cyclomatic 15, cognitive 16) packages/g6/src/plugins/minimap/index.ts:424
- Complex function (anonymous) (cyclomatic 15, cognitive 15) packages/g6/src/utils/change.ts:20
- Complex function caseIndentedTree (cyclomatic 15, cognitive 14) packages/g6/__tests__/demos/case-indented-tree.ts:43
- Complex function (anonymous) (cyclomatic 14, cognitive 22) packages/g6/src/transforms/process-parallel-edges.ts:201
- Complex function getArcLoopPath (cyclomatic 14, cognitive 17) packages/g6/src/utils/edge.ts:455
- Complex function monotoneConvexHull2D (cyclomatic 14, cognitive 16) packages/g6/src/plugins/hull/hull/monotone-convex-hull-2d.ts:8
- Complex function autoSnapToLine (cyclomatic 13, cognitive 20) packages/g6/src/plugins/snapline/index.ts:188
- Complex function fitView (cyclomatic 13, cognitive 11) packages/g6/src/runtime/viewport.ts:212
- Complex function segmentsIntersect (cyclomatic 13, cognitive 10) packages/g6/src/plugins/hull/hull/robust-segment-intersect.ts:18
- Complex function _concave (cyclomatic 12, cognitive 16) packages/g6/src/plugins/hull/hull/index.ts:120
- Complex function _setOptions (cyclomatic 12, cognitive 12) packages/g6/src/runtime/graph.ts:134
- Complex function execute (cyclomatic 12, cognitive 11) packages/g6/src/layouts/snake.ts:141
- Complex function enableSnap (cyclomatic 11, cognitive 11) packages/g6/src/plugins/snapline/index.ts:230
- Complex function getEndpoints (cyclomatic 11, cognitive 10) packages/g6/src/elements/edges/base-edge.ts:272
- Complex function getPolylineLoopControlPoints (cyclomatic 11, cognitive 10) packages/g6/src/utils/edge.ts:610
- packages/g6/src/runtime/graph.ts: 1928 lines of code packages/g6/src/runtime/graph.ts:1
- packages/g6/src/runtime/element.ts: 811 lines of code packages/g6/src/runtime/element.ts:1
- packages/g6/src/runtime/data.ts: 795 lines of code packages/g6/src/runtime/data.ts:1
- packages/g6/src/utils/edge.ts: 680 lines of code packages/g6/src/utils/edge.ts:1
- packages/g6/src/utils/element.ts: 501 lines of code packages/g6/src/utils/element.ts:1
- packages/g6/src/plugins/minimap/index.ts: 449 lines of code packages/g6/src/plugins/minimap/index.ts:1
- packages/g6/src/behaviors/drag-element.ts: 447 lines of code packages/g6/src/behaviors/drag-element.ts:1
- packages/g6/src/plugins/hull/hull/robust-orientation.ts: 429 lines of code packages/g6/src/plugins/hull/hull/robust-orientation.ts:1
- packages/g6/src/elements/edges/base-edge.ts: 418 lines of code packages/g6/src/elements/edges/base-edge.ts:1
- packages/g6/src/elements/nodes/base-node.ts: 415 lines of code packages/g6/src/elements/nodes/base-node.ts:1
- packages/g6/src/utils/router/shortest-path.ts: 402 lines of code packages/g6/src/utils/router/shortest-path.ts:1
- Type errors in this package cannot fail any build or CI step packages/site/package.json:31
- Dead file (~6 LoC) packages/g6/src/types/plugin.ts
- Dead file (~1 LoC) packages/g6/src/types/utility.ts
- Unused dependency '@changesets/cli' package.json:36
- Unused dependency 'd3-hierarchy' package.json:55
- Unused dependency 'tslib' package.json:78
- JavaScript dependencies are not locked package.json:31
- Recursive walk over a caller-supplied document has no depth cap packages/g6/src/plugins/history/util.ts:20
- Untrusted text written into markup unescaped packages/g6/src/plugins/utils/dom.ts:59
- Swallowed exception (empty catch) packages/g6-extension-react/src/react-node/render18.ts:46
Minor — 117 finding(s)
- Orphaned file packages/g6/src/plugins/minimap/index.ts:1
- Orphaned file packages/g6/src/behaviors/drag-element.ts:1
- Orphaned file packages/g6/src/runtime/layout.ts:1
- Orphaned file packages/g6/src/plugins/toolbar/util.ts:1
- Orphaned file packages/g6/src/plugins/hull/hull/robust-orientation.ts:1
- Orphaned file packages/g6/src/runtime/canvas.ts:1
- Orphaned file packages/g6/src/runtime/viewport.ts:1
- Orphaned file packages/g6/src/elements/shapes/base-shape.ts:1
- Orphaned file packages/g6/src/plugins/timebar.ts:1
- Orphaned file packages/g6/src/elements/nodes/html.ts:1
- Orphaned file packages/g6/src/utils/animation.ts:1
- Orphaned file packages/g6/src/utils/pinch.ts:1
- Orphaned file packages/g6/src/plugins/contextmenu/index.ts:1
- Orphaned file packages/g6/src/plugins/title/index.ts:1
- Orphaned file packages/g6/src/runtime/animation.ts:1
- Orphaned file packages/g6/src/behaviors/create-edge.ts:1
- Orphaned file packages/g6/src/behaviors/zoom-canvas.ts:1
- Orphaned file packages/g6/src/plugins/watermark/index.ts:1
- Orphaned file packages/g6/src/plugins/hull/hull/index.ts:1
- Orphaned file packages/g6/src/utils/shortcut.ts:1
- Orphaned file packages/g6/src/layouts/types.ts:1
- Orphaned file packages/g6/src/runtime/behavior.ts:1
- Orphaned file packages/g6/src/utils/prefix.ts:1
- Orphaned file packages/g6/src/plugins/camera-setting.ts:1
- Orphaned file packages/g6/src/elements/nodes/donut.ts:1
- README/code drift packages/site/docs/manual/behavior/ClickSelect.en.mdx:185
- README/code drift packages/site/docs/manual/behavior/CollapseExpand.en.mdx:189
- README/code drift packages/site/docs/manual/behavior/CollapseExpand.en.mdx:190
- README/code drift packages/site/docs/manual/behavior/CreateEdge.zh.mdx:130
- README/code drift packages/site/docs/manual/behavior/DragCanvas.zh.mdx:200
- README/code drift packages/site/docs/manual/behavior/OptimizeViewportTransform.zh.mdx:209
- README/code drift packages/site/docs/manual/behavior/ScrollCanvas.zh.mdx:216
- README/code drift packages/site/docs/manual/behavior/ZoomCanvas.zh.mdx:272
- README/code drift packages/site/docs/manual/further-reading/bundle.en.md:44
- README/code drift packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:155
- README/code drift packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:157
- README/code drift packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:158
- README/code drift packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:159
- README/code drift packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:160
- README/code drift packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:161
- README/code drift packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:162
- README/code drift packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:163
- README/code drift packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:164
- README/code drift packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:165
- README/code drift packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:166
- README/code drift packages/site/docs/manual/layout/ForceAtlas2Layout.zh.mdx:167
- Mock-dominated test: print packages/g6/__tests__/unit/utils/print.spec.ts:5
- Mock-dominated test: print mute packages/g6/__tests__/unit/utils/print.spec.ts:27
- Mock-dominated test: element lifecycle event packages/g6/__tests__/unit/runtime/graph/event.spec.ts:67
- Mock-dominated test: element state packages/g6/__tests__/unit/runtime/graph/event.spec.ts:119
- Mock-dominated test: override onCreate, onUpdate, onDestroy packages/g6/__tests__/unit/elements/override-methods.spec.ts:5
- Mock-dominated test: upsert hooks packages/g6/__tests__/unit/elements/shape.spec.ts:6
- Mock-dominated test: canvas event packages/g6/__tests__/unit/behaviors/zoom-canvas.spec.ts:244
- Duplicated predicate packages/g6/src/transforms/process-parallel-edges.ts:140
- Duplicated predicate packages/g6/src/behaviors/drag-canvas.ts:221
- Duplicated predicate packages/g6/src/behaviors/drag-canvas.ts:224
- Duplicated predicate packages/g6/src/elements/nodes/base-node.ts:430
- Duplicated predicate packages/g6/src/elements/edges/base-edge.ts:308
- Duplicated predicate packages/g6/src/plugins/edge-filter-lens/index.ts:177
- Event not named in past tense: GraphLifeCycleEvent packages/g6/src/utils/event/events.ts:17
- Event not named in past tense: AnimateEvent packages/g6/src/utils/event/events.ts:40
- Event not named in past tense: ElementLifeCycleEvent packages/g6/src/utils/event/events.ts:51
- Event not named in past tense: ViewportEvent packages/g6/src/utils/event/events.ts:67
- Projects may be oversized for their cohesion packages/g6/package.json:1
- Projects may be oversized for their cohesion packages/site/package.json:1
- Empty method body packages/g6/src/runtime/transform.ts:22
- Empty method body packages/g6/src/utils/shortcut.ts:24
- Type-only dependency '@antv/g' in production deps packages/g6-extension-react/src/react-node/node.tsx:1
- Type-only dependency '@antv/g' in production deps packages/g6-ssr/src/types.ts:1
- No ADRs found packages/g6-ssr/package.json:14
- `shapeID` spells `ID` where 14 names in the project spell it `Id` packages/g6/src/types/element.ts:88
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Disabled test packages/g6-extension-react/__tests__/unit/attribute-changed-callback.spec.tsx:4
- No ADRs
- No SAST REDACTED:7
- No dependency-update automation package.json:31
- Unused export 'ComboCollapseExpand' packages/g6/src/animations/index.ts:23
- Unused export 'ChangeEvent' packages/g6/src/constants/change.ts:1
- Unused export 'PointConverter' packages/g6/src/plugins/hull/hull/format.ts:29
- Unused export 'AnimationTask' packages/g6/src/types/animation.ts:7
- Unused export 'ElementOptions' packages/g6/src/types/element.ts:66
- Unused export 'GraphLibGroupedChanges' packages/g6/src/types/graphlib.ts:16
- Unused export 'RouterOptions' packages/g6/src/types/router.ts:31
- Unused export 'getPositionByRectPoints' packages/g6/src/utils/position.ts:77
- Unused export 'ShortcutOptions' packages/g6/src/utils/shortcut.ts:8
- Unused private method 'setElementCollapsibility' packages/g6/src/runtime/graph.ts:1937
- Type-only dependency '@antv/g-device-api' in production deps packages/g6-extension-3d/src/utils/geometry.ts:1
- Type-only dependency '@antv/g-plugin-device-renderer' in production deps packages/g6-extension-3d/src/elements/base-node-3d.ts:4
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) override strict null checking
- Silent fallback default in catch packages/g6/src/runtime/element.ts:170
Minor — 20 finding(s)
- Skipped (documented): (unnamed test) packages/g6/__tests__/unit/runtime/graph/this.spec.ts:25
- Skipped (documented): (unnamed test) packages/g6/__tests__/unit/runtime/graph/this.spec.ts:30
- Skipped (documented): (unnamed test) packages/g6/__tests__/unit/runtime/graph/this.spec.ts:37
- Skipped (documented): (unnamed test) packages/g6/__tests__/unit/runtime/graph/this.spec.ts:45
- Skipped (documented): (unnamed test) packages/g6/__tests__/unit/runtime/graph/this.spec.ts:50
- Skipped (documented): (unnamed test) packages/g6/__tests__/unit/runtime/graph/this.spec.ts:57
- Skipped (documented): (unnamed test) packages/g6/__tests__/unit/runtime/graph/this.spec.ts:65
- Skipped (documented): (unnamed test) packages/g6/__tests__/unit/runtime/graph/this.spec.ts:70
- Skipped (documented): (unnamed test) packages/g6/__tests__/unit/runtime/graph/this.spec.ts:77
- Skipped (documented): (unnamed test) packages/g6/__tests__/unit/runtime/graph/this.spec.ts:92
- Skipped (documented): (unnamed test) packages/g6/__tests__/unit/runtime/graph/this.spec.ts:97
- Skipped (documented): (unnamed test) packages/g6/__tests__/unit/runtime/graph/this.spec.ts:107
- Skipped (documented): (unnamed test) packages/g6/__tests__/unit/runtime/graph/this.spec.ts:130
- Skipped (documented): (unnamed test) packages/g6/__tests__/unit/runtime/graph/this.spec.ts:139
- Skipped (documented): (unnamed test) packages/g6/__tests__/unit/runtime/graph/this.spec.ts:147
- doc comments repeat the names packages/g6/__tests__/utils/create.ts:24
- doc comments repeat the names packages/site/scripts/generate-api.ts:45
- doc comments repeat the names scripts/demo-to-test/core/utils.js:17
- doc comments repeat the names packages/cli/template-extension/__tests__/utils/create.ts:21
- Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (no committed lockfile, so no resolved version to grade)
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-c11fc8f59a3b444ea0264b0ec2015ef5/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-c11fc8f59a3b444ea0264b0ec2015ef5/history-1.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-c11fc8f59a3b444ea0264b0ec2015ef5/history-2.json --exit-code 0 --source . | 4 | 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=2244" --report-format json --report-path /tmp/watchdog-gitleaks-c11fc8f59a3b444ea0264b0ec2015ef5/history-3.json --exit-code 0 --source . | 0 | 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-c11fc8f59a3b444ea0264b0ec2015ef5/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 56 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D30 · Dependency Vulnerabilities | 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 |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `packages/g6/src/types/index.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 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 |