Executive summary
cosmiciron/vmprint falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no logging, tracing or health checks in the code. It scores 35.5 out of 100 and is rated Weak, and five of its ten critical findings are security problems in the packages it uses and in its code.
Production Readiness, at 26.2, is the weakest lens and counts most in the score. The best first step is pinning the dependencies taken from a moving source, worth about 6.0 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 3.3 points. Raising Production Readiness to 70 would lift the score to about 43.4.
Four known security holes in the packages the code depends on can be used by attackers. One place in the code runs text as code, which an attacker could use. Updating the vulnerable packages and replacing text run as code with direct calls would close both risks. The two labels or groups of fields with no name need connecting to their fields or naming.
The product code is 230,167 lines, about €210,000 to rebuild.
If Production Readiness rose from 26.2 to 70, the lowest score rated Strong, the score would rise from 35.5 to about 43.4.
Rebuild cost: about €210,000 · Estimate
| Cost to rebuild | €71,000 to €360,000, for 1,178 to 3,738 hours of work, about 1.5 person-years for 1 to 3 engineers |
|---|---|
| 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 36. 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 | Large: 230,167 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 contracts.src.context | 2 contracts.src.font-manager | 3 contracts.src.text-delegate | 4 engine.src.engine.layout.runtime.session.session-pagination-types | 5 engine.src.engine.layout.script-runtime-host | 6 engine.src.engine.types | 7 contexts.canvas.src | 8 contracts.src.overlay | 9 engine.src.engine.layout.collider-field | 10 engine.src.engine.layout.lifecycle-runtime | 11 engine.src.engine.layout.runtime.session.session-lifecycle-types | 12 engine.src.engine.layout.session-world-runtime | 13 engine.src.engine.runtime-types | 14 engine.src.engine.runtime.simulation.types | 15 transmuters.markdown-core.src.context | 16 engine.src.engine.context-renderer | 17 engine.src.engine.layout.font-processor | 18 engine.src.engine.layout.layout-core | 19 engine.src.engine.layout.packagers.spatial-map | 20 engine.src.engine.layout-engine | 21 engine.src.engine.layout.packagers.packager-types | 22 engine.src.engine.layout.collision-runtime | 23 engine.src.engine.layout.packagers.flow-box-packager | 24 engine.src.engine.layout.packagers.hosted-region-packager | 25 engine.src.engine.layout.physics-runtime | 26 engine.src.engine.layout.runtime.session.session-runtime-types | 27 engine.src.engine.vmprint-engine | 28 engine.src.engine | 29 engine.src.engine.layout.collaborators.temporal-presentation-collaborator | 30 engine.src.engine.layout.event-dispatcher | 31 engine.src.engine.layout.placement-session-runtime | 32 engine.src.engine.layout.runtime.page-finalization.page-region-finalization | 33 engine.src.engine.layout.runtime.scripting.script-runtime-pass | 34 engine.src.engine.layout | 35 engine.src.engine.layout.runtime.session.session-collaboration-runtime | 36 engine.src.engine.layout.layout-session | 37 engine.src.engine.layout.packagers | 38 engine.src.engine.layout.packagers.script-document-packager | 39 engine.src.engine.layout.packagers.scripted-flow-box-packager | 40 engine.src.engine.runtime.simulation.runtime.march-runner |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 contracts.src.context | ||||||||||||||||||||||||||||||||||||||||
| 2 contracts.src.font-manager | ||||||||||||||||||||||||||||||||||||||||
| 3 contracts.src.text-delegate | ||||||||||||||||||||||||||||||||||||||||
| 4 engine.src.engine.layout.runtime.session.session-pagination-types | ||||||||||||||||||||||||||||||||||||||||
| 5 engine.src.engine.layout.script-runtime-host | ||||||||||||||||||||||||||||||||||||||||
| 6 engine.src.engine.types | ||||||||||||||||||||||||||||||||||||||||
| 7 contexts.canvas.src | 5 | |||||||||||||||||||||||||||||||||||||||
| 8 contracts.src.overlay | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 engine.src.engine.layout.collider-field | 10 | 5 | ||||||||||||||||||||||||||||||||||||||
| 10 engine.src.engine.layout.lifecycle-runtime | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 engine.src.engine.layout.runtime.session.session-lifecycle-types | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 engine.src.engine.layout.session-world-runtime | 4 | |||||||||||||||||||||||||||||||||||||||
| 13 engine.src.engine.runtime-types | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 14 engine.src.engine.runtime.simulation.types | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 transmuters.markdown-core.src.context | 3 | |||||||||||||||||||||||||||||||||||||||
| 16 engine.src.engine.context-renderer | 1 | 3 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 17 engine.src.engine.layout.font-processor | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 engine.src.engine.layout.layout-core | 1 | 6 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 engine.src.engine.layout.packagers.spatial-map | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 engine.src.engine.layout-engine | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 engine.src.engine.layout.packagers.packager-types | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 engine.src.engine.layout.collision-runtime | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 23 engine.src.engine.layout.packagers.flow-box-packager | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 24 engine.src.engine.layout.packagers.hosted-region-packager | 4 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 25 engine.src.engine.layout.physics-runtime | 5 | 2 | ||||||||||||||||||||||||||||||||||||||
| 26 engine.src.engine.layout.runtime.session.session-runtime-types | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 engine.src.engine.vmprint-engine | 1 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 28 engine.src.engine | 1 | 1 | 14 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 29 engine.src.engine.layout.collaborators.temporal-presentation-collaborator | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 engine.src.engine.layout.event-dispatcher | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 engine.src.engine.layout.placement-session-runtime | 5 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 engine.src.engine.layout.runtime.page-finalization.page-region-finalization | 2 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 33 engine.src.engine.layout.runtime.scripting.script-runtime-pass | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 34 engine.src.engine.layout | 23 | 1 | 2 | 4 | 1 | |||||||||||||||||||||||||||||||||||
| 35 engine.src.engine.layout.runtime.session.session-collaboration-runtime | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 engine.src.engine.layout.layout-session | 2 | 6 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 37 engine.src.engine.layout.packagers | 1 | 30 | 7 | 3 | 15 | 6 | 2 | |||||||||||||||||||||||||||||||||
| 38 engine.src.engine.layout.packagers.script-document-packager | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 engine.src.engine.layout.packagers.scripted-flow-box-packager | 1 | 1 | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 40 engine.src.engine.runtime.simulation.runtime.march-runner | 1 | 1 | 2 | 1 | 1 | 1 |
7→1 contexts.canvas.src uses contracts.src.context✕
- Connections
- 5 pairs of types, where a type in contexts.canvas.src uses a type in contracts.src.context.
- The types involved
contexts.canvas.src.CanvasContext→contracts.src.context.Contextcontexts.canvas.src.CanvasContext→contracts.src.context.ContextFontRegistrationOptionscontexts.canvas.src.CanvasContext→contracts.src.context.ContextImageOptionscontexts.canvas.src.CanvasContext→contracts.src.context.ContextTextOptionscontexts.canvas.src.CanvasContext→contracts.src.context.VmprintOutputStream
- Direction
- contexts.canvas.src uses contracts.src.context, so a change to contracts.src.context can break contexts.canvas.src, while a change to contexts.canvas.src can't break contracts.src.context.
- Position
- Below the diagonal: contexts.canvas.src uses a module listed above it, which is the healthy direction.
8→1 contracts.src.overlay uses contracts.src.context✕
- Connections
- 1 pair of types, where a type in contracts.src.overlay uses a type in contracts.src.context.
- The types involved
contracts.src.overlay.OverlayContext→contracts.src.context.ContextTextOptions
- Direction
- contracts.src.overlay uses contracts.src.context, so a change to contracts.src.context can break contracts.src.overlay, while a change to contracts.src.overlay can't break contracts.src.context.
- Position
- Below the diagonal: contracts.src.overlay uses a module listed above it, which is the healthy direction.
9→6 engine.src.engine.layout.collider-field uses engine.src.engine.types✕
- Connections
- 10 pairs of types, where a type in engine.src.engine.layout.collider-field uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout.collider-field.CircleCollider→engine.src.engine.types.StoryWrapModeengine.src.engine.layout.collider-field.CircleCollider→engine.src.engine.types.TraversalInteractionPolicyengine.src.engine.layout.collider-field.CompiledCollider→engine.src.engine.types.StoryWrapModeengine.src.engine.layout.collider-field.CompiledCollider→engine.src.engine.types.TraversalInteractionPolicyengine.src.engine.layout.collider-field.EllipseCollider→engine.src.engine.types.StoryWrapModeengine.src.engine.layout.collider-field.EllipseCollider→engine.src.engine.types.TraversalInteractionPolicyengine.src.engine.layout.collider-field.PolygonCollider→engine.src.engine.types.StoryWrapModeengine.src.engine.layout.collider-field.PolygonCollider→engine.src.engine.types.TraversalInteractionPolicyengine.src.engine.layout.collider-field.RectCollider→engine.src.engine.types.StoryWrapModeengine.src.engine.layout.collider-field.RectCollider→engine.src.engine.types.TraversalInteractionPolicy
- Direction
- engine.src.engine.layout.collider-field uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout.collider-field, while a change to engine.src.engine.layout.collider-field can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout.collider-field uses a module listed above it, which is the healthy direction.
9→19 engine.src.engine.layout.collider-field uses engine.src.engine.layout.packagers.spatial-map part of a loop✕
- Connections
- 5 pairs of types, where a type in engine.src.engine.layout.collider-field uses a type in engine.src.engine.layout.packagers.spatial-map.
- The types involved
engine.src.engine.layout.collider-field.CircleCollider→engine.src.engine.layout.packagers.spatial-map.OccupiedRectengine.src.engine.layout.collider-field.ColliderField→engine.src.engine.layout.packagers.spatial-map.OccupiedRectengine.src.engine.layout.collider-field.EllipseCollider→engine.src.engine.layout.packagers.spatial-map.OccupiedRectengine.src.engine.layout.collider-field.PolygonCollider→engine.src.engine.layout.packagers.spatial-map.OccupiedRectengine.src.engine.layout.collider-field.RectCollider→engine.src.engine.layout.packagers.spatial-map.OccupiedRect
- Direction
- engine.src.engine.layout.collider-field uses engine.src.engine.layout.packagers.spatial-map, so a change to engine.src.engine.layout.packagers.spatial-map can break engine.src.engine.layout.collider-field, while a change to engine.src.engine.layout.collider-field can't break engine.src.engine.layout.packagers.spatial-map.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→4 engine.src.engine.layout.lifecycle-runtime uses engine.src.engine.layout.runtime.session.session-pagination-types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.lifecycle-runtime uses a type in engine.src.engine.layout.runtime.session.session-pagination-types.
- The types involved
engine.src.engine.layout.lifecycle-runtime.LifecycleRuntime→engine.src.engine.layout.runtime.session.session-pagination-types.PaginationLoopAction
- Direction
- engine.src.engine.layout.lifecycle-runtime uses engine.src.engine.layout.runtime.session.session-pagination-types, so a change to engine.src.engine.layout.runtime.session.session-pagination-types can break engine.src.engine.layout.lifecycle-runtime, while a change to engine.src.engine.layout.lifecycle-runtime can't break engine.src.engine.layout.runtime.session.session-pagination-types.
- Position
- Below the diagonal: engine.src.engine.layout.lifecycle-runtime uses a module listed above it, which is the healthy direction.
10→6 engine.src.engine.layout.lifecycle-runtime uses engine.src.engine.types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.lifecycle-runtime uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout.lifecycle-runtime.LifecycleRuntime→engine.src.engine.types.Page
- Direction
- engine.src.engine.layout.lifecycle-runtime uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout.lifecycle-runtime, while a change to engine.src.engine.layout.lifecycle-runtime can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout.lifecycle-runtime uses a module listed above it, which is the healthy direction.
11→6 engine.src.engine.layout.runtime.session.session-lifecycle-types uses engine.src.engine.types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.runtime.session.session-lifecycle-types uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout.runtime.session.session-lifecycle-types.PageSurface→engine.src.engine.types.Page
- Direction
- engine.src.engine.layout.runtime.session.session-lifecycle-types uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout.runtime.session.session-lifecycle-types, while a change to engine.src.engine.layout.runtime.session.session-lifecycle-types can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout.runtime.session.session-lifecycle-types uses a module listed above it, which is the healthy direction.
12→6 engine.src.engine.layout.session-world-runtime uses engine.src.engine.types✕
- Connections
- 4 pairs of types, where a type in engine.src.engine.layout.session-world-runtime uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout.session-world-runtime.SessionWorldRuntime→engine.src.engine.types.PageReservationSelectorengine.src.engine.layout.session-world-runtime.SessionWorldRuntime→engine.src.engine.types.SimulationProgressionConfigengine.src.engine.layout.session-world-runtime.SessionWorldRuntime→engine.src.engine.types.SimulationProgressionPolicyengine.src.engine.layout.session-world-runtime.SessionWorldRuntime→engine.src.engine.types.SimulationStopReason
- Direction
- engine.src.engine.layout.session-world-runtime uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout.session-world-runtime, while a change to engine.src.engine.layout.session-world-runtime can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout.session-world-runtime uses a module listed above it, which is the healthy direction.
13→2 engine.src.engine.runtime-types uses contracts.src.font-manager✕
- Connections
- 1 pair of types, where a type in engine.src.engine.runtime-types uses a type in contracts.src.font-manager.
- The types involved
engine.src.engine.runtime-types.EngineRuntime→contracts.src.font-manager.FontManager
- Direction
- engine.src.engine.runtime-types uses contracts.src.font-manager, so a change to contracts.src.font-manager can break engine.src.engine.runtime-types, while a change to engine.src.engine.runtime-types can't break contracts.src.font-manager.
- Position
- Below the diagonal: engine.src.engine.runtime-types uses a module listed above it, which is the healthy direction.
13→3 engine.src.engine.runtime-types uses contracts.src.text-delegate✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.runtime-types uses a type in contracts.src.text-delegate.
- The types involved
engine.src.engine.runtime-types.EngineRuntime→contracts.src.text-delegate.TextDelegateengine.src.engine.runtime-types.EngineRuntime→contracts.src.text-delegate.TextDelegateState
- Direction
- engine.src.engine.runtime-types uses contracts.src.text-delegate, so a change to contracts.src.text-delegate can break engine.src.engine.runtime-types, while a change to engine.src.engine.runtime-types can't break contracts.src.text-delegate.
- Position
- Below the diagonal: engine.src.engine.runtime-types uses a module listed above it, which is the healthy direction.
14→6 engine.src.engine.runtime.simulation.types uses engine.src.engine.types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.runtime.simulation.types uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.runtime.simulation.types.SimulationRunner→engine.src.engine.types.SimulationStopReason
- Direction
- engine.src.engine.runtime.simulation.types uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.runtime.simulation.types, while a change to engine.src.engine.runtime.simulation.types can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.runtime.simulation.types uses a module listed above it, which is the healthy direction.
15→6 transmuters.markdown-core.src.context uses engine.src.engine.types✕
- Connections
- 3 pairs of types, where a type in transmuters.markdown-core.src.context uses a type in engine.src.engine.types.
- The types involved
transmuters.markdown-core.src.context.FormatContext→engine.src.engine.types.Elementtransmuters.markdown-core.src.context.FormatContextImpl→engine.src.engine.types.Elementtransmuters.markdown-core.src.context.FormatContextImpl→engine.src.engine.types.ElementStyle
- Direction
- transmuters.markdown-core.src.context uses engine.src.engine.types, so a change to engine.src.engine.types can break transmuters.markdown-core.src.context, while a change to transmuters.markdown-core.src.context can't break engine.src.engine.types.
- Position
- Below the diagonal: transmuters.markdown-core.src.context uses a module listed above it, which is the healthy direction.
16→1 engine.src.engine.context-renderer uses contracts.src.context✕
- Connections
- 1 pair of types, where a type in engine.src.engine.context-renderer uses a type in contracts.src.context.
- The types involved
engine.src.engine.context-renderer.ContextRenderer→contracts.src.context.Context
- Direction
- engine.src.engine.context-renderer uses contracts.src.context, so a change to contracts.src.context can break engine.src.engine.context-renderer, while a change to engine.src.engine.context-renderer can't break contracts.src.context.
- Position
- Below the diagonal: engine.src.engine.context-renderer uses a module listed above it, which is the healthy direction.
16→6 engine.src.engine.context-renderer uses engine.src.engine.types✕
- Connections
- 3 pairs of types, where a type in engine.src.engine.context-renderer uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.context-renderer.ContextRenderer→engine.src.engine.types.Boxengine.src.engine.context-renderer.ContextRenderer→engine.src.engine.types.LayoutConfigengine.src.engine.context-renderer.ContextRenderer→engine.src.engine.types.Page
- Direction
- engine.src.engine.context-renderer uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.context-renderer, while a change to engine.src.engine.context-renderer can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.context-renderer uses a module listed above it, which is the healthy direction.
16→8 engine.src.engine.context-renderer uses contracts.src.overlay✕
- Connections
- 3 pairs of types, where a type in engine.src.engine.context-renderer uses a type in contracts.src.overlay.
- The types involved
engine.src.engine.context-renderer.ContextRenderer→contracts.src.overlay.OverlayContextengine.src.engine.context-renderer.ContextRenderer→contracts.src.overlay.OverlayPageengine.src.engine.context-renderer.ContextRenderer→contracts.src.overlay.OverlayProvider
- Direction
- engine.src.engine.context-renderer uses contracts.src.overlay, so a change to contracts.src.overlay can break engine.src.engine.context-renderer, while a change to engine.src.engine.context-renderer can't break contracts.src.overlay.
- Position
- Below the diagonal: engine.src.engine.context-renderer uses a module listed above it, which is the healthy direction.
16→13 engine.src.engine.context-renderer uses engine.src.engine.runtime-types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.context-renderer uses a type in engine.src.engine.runtime-types.
- The types involved
engine.src.engine.context-renderer.ContextRenderer→engine.src.engine.runtime-types.EngineRuntime
- Direction
- engine.src.engine.context-renderer uses engine.src.engine.runtime-types, so a change to engine.src.engine.runtime-types can break engine.src.engine.context-renderer, while a change to engine.src.engine.context-renderer can't break engine.src.engine.runtime-types.
- Position
- Below the diagonal: engine.src.engine.context-renderer uses a module listed above it, which is the healthy direction.
17→6 engine.src.engine.layout.font-processor uses engine.src.engine.types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.font-processor uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout.font-processor.FontProcessor→engine.src.engine.types.LayoutConfig
- Direction
- engine.src.engine.layout.font-processor uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout.font-processor, while a change to engine.src.engine.layout.font-processor can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout.font-processor uses a module listed above it, which is the healthy direction.
17→13 engine.src.engine.layout.font-processor uses engine.src.engine.runtime-types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.font-processor uses a type in engine.src.engine.runtime-types.
- The types involved
engine.src.engine.layout.font-processor.FontProcessor→engine.src.engine.runtime-types.EngineRuntime
- Direction
- engine.src.engine.layout.font-processor uses engine.src.engine.runtime-types, so a change to engine.src.engine.runtime-types can break engine.src.engine.layout.font-processor, while a change to engine.src.engine.layout.font-processor can't break engine.src.engine.runtime-types.
- Position
- Below the diagonal: engine.src.engine.layout.font-processor uses a module listed above it, which is the healthy direction.
18→5 engine.src.engine.layout.layout-core uses engine.src.engine.layout.script-runtime-host✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.layout-core uses a type in engine.src.engine.layout.script-runtime-host.
- The types involved
engine.src.engine.layout.layout-core.LayoutProcessor→engine.src.engine.layout.script-runtime-host.ScriptRuntimeHost
- Direction
- engine.src.engine.layout.layout-core uses engine.src.engine.layout.script-runtime-host, so a change to engine.src.engine.layout.script-runtime-host can break engine.src.engine.layout.layout-core, while a change to engine.src.engine.layout.layout-core can't break engine.src.engine.layout.script-runtime-host.
- Position
- Below the diagonal: engine.src.engine.layout.layout-core uses a module listed above it, which is the healthy direction.
18→6 engine.src.engine.layout.layout-core uses engine.src.engine.types✕
- Connections
- 6 pairs of types, where a type in engine.src.engine.layout.layout-core uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout.layout-core.LayoutProcessor→engine.src.engine.types.BoxMetaengine.src.engine.layout.layout-core.LayoutProcessor→engine.src.engine.types.Elementengine.src.engine.layout.layout-core.LayoutProcessor→engine.src.engine.types.ElementStyleengine.src.engine.layout.layout-core.LayoutProcessor→engine.src.engine.types.OverflowPolicyengine.src.engine.layout.layout-core.LayoutProcessor→engine.src.engine.types.PageRegionContentengine.src.engine.layout.layout-core.LayoutProcessor→engine.src.engine.types.SimulationProgressionConfig
- Direction
- engine.src.engine.layout.layout-core uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout.layout-core, while a change to engine.src.engine.layout.layout-core can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout.layout-core uses a module listed above it, which is the healthy direction.
18→14 engine.src.engine.layout.layout-core uses engine.src.engine.runtime.simulation.types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.layout-core uses a type in engine.src.engine.runtime.simulation.types.
- The types involved
engine.src.engine.layout.layout-core.LayoutProcessor→engine.src.engine.runtime.simulation.types.SimulationRunner
- Direction
- engine.src.engine.layout.layout-core uses engine.src.engine.runtime.simulation.types, so a change to engine.src.engine.runtime.simulation.types can break engine.src.engine.layout.layout-core, while a change to engine.src.engine.layout.layout-core can't break engine.src.engine.runtime.simulation.types.
- Position
- Below the diagonal: engine.src.engine.layout.layout-core uses a module listed above it, which is the healthy direction.
19→6 engine.src.engine.layout.packagers.spatial-map uses engine.src.engine.types✕
- Connections
- 3 pairs of types, where a type in engine.src.engine.layout.packagers.spatial-map uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout.packagers.spatial-map.OccupiedRect→engine.src.engine.types.StoryFloatAlignengine.src.engine.layout.packagers.spatial-map.OccupiedRect→engine.src.engine.types.StoryWrapModeengine.src.engine.layout.packagers.spatial-map.OccupiedRect→engine.src.engine.types.TraversalInteractionPolicy
- Direction
- engine.src.engine.layout.packagers.spatial-map uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout.packagers.spatial-map, while a change to engine.src.engine.layout.packagers.spatial-map can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.spatial-map uses a module listed above it, which is the healthy direction.
19→9 engine.src.engine.layout.packagers.spatial-map uses engine.src.engine.layout.collider-field✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers.spatial-map uses a type in engine.src.engine.layout.collider-field.
- The types involved
engine.src.engine.layout.packagers.spatial-map.SpatialMap→engine.src.engine.layout.collider-field.ColliderField
- Direction
- engine.src.engine.layout.packagers.spatial-map uses engine.src.engine.layout.collider-field, so a change to engine.src.engine.layout.collider-field can break engine.src.engine.layout.packagers.spatial-map, while a change to engine.src.engine.layout.packagers.spatial-map can't break engine.src.engine.layout.collider-field.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.spatial-map uses a module listed above it, which is the healthy direction.
20→5 engine.src.engine.layout-engine uses engine.src.engine.layout.script-runtime-host✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout-engine uses a type in engine.src.engine.layout.script-runtime-host.
- The types involved
engine.src.engine.layout-engine.LayoutEngine→engine.src.engine.layout.script-runtime-host.ScriptRuntimeHost
- Direction
- engine.src.engine.layout-engine uses engine.src.engine.layout.script-runtime-host, so a change to engine.src.engine.layout.script-runtime-host can break engine.src.engine.layout-engine, while a change to engine.src.engine.layout-engine can't break engine.src.engine.layout.script-runtime-host.
- Position
- Below the diagonal: engine.src.engine.layout-engine uses a module listed above it, which is the healthy direction.
20→6 engine.src.engine.layout-engine uses engine.src.engine.types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout-engine uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout-engine.LayoutEngine→engine.src.engine.types.LayoutConfig
- Direction
- engine.src.engine.layout-engine uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout-engine, while a change to engine.src.engine.layout-engine can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout-engine uses a module listed above it, which is the healthy direction.
20→13 engine.src.engine.layout-engine uses engine.src.engine.runtime-types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout-engine uses a type in engine.src.engine.runtime-types.
- The types involved
engine.src.engine.layout-engine.LayoutEngine→engine.src.engine.runtime-types.EngineRuntime
- Direction
- engine.src.engine.layout-engine uses engine.src.engine.runtime-types, so a change to engine.src.engine.runtime-types can break engine.src.engine.layout-engine, while a change to engine.src.engine.layout-engine can't break engine.src.engine.runtime-types.
- Position
- Below the diagonal: engine.src.engine.layout-engine uses a module listed above it, which is the healthy direction.
20→18 engine.src.engine.layout-engine uses engine.src.engine.layout.layout-core✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout-engine uses a type in engine.src.engine.layout.layout-core.
- The types involved
engine.src.engine.layout-engine.LayoutEngine→engine.src.engine.layout.layout-core.LayoutProcessor
- Direction
- engine.src.engine.layout-engine uses engine.src.engine.layout.layout-core, so a change to engine.src.engine.layout.layout-core can break engine.src.engine.layout-engine, while a change to engine.src.engine.layout-engine can't break engine.src.engine.layout.layout-core.
- Position
- Below the diagonal: engine.src.engine.layout-engine uses a module listed above it, which is the healthy direction.
21→6 engine.src.engine.layout.packagers.packager-types uses engine.src.engine.types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers.packager-types uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout.packagers.packager-types.PackagerContext→engine.src.engine.types.SimulationProgressionConfig
- Direction
- engine.src.engine.layout.packagers.packager-types uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout.packagers.packager-types, while a change to engine.src.engine.layout.packagers.packager-types can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.packager-types uses a module listed above it, which is the healthy direction.
21→19 engine.src.engine.layout.packagers.packager-types uses engine.src.engine.layout.packagers.spatial-map✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers.packager-types uses a type in engine.src.engine.layout.packagers.spatial-map.
- The types involved
engine.src.engine.layout.packagers.packager-types.PackagerContext→engine.src.engine.layout.packagers.spatial-map.SpatialMap
- Direction
- engine.src.engine.layout.packagers.packager-types uses engine.src.engine.layout.packagers.spatial-map, so a change to engine.src.engine.layout.packagers.spatial-map can break engine.src.engine.layout.packagers.packager-types, while a change to engine.src.engine.layout.packagers.packager-types can't break engine.src.engine.layout.packagers.spatial-map.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.packager-types uses a module listed above it, which is the healthy direction.
22→4 engine.src.engine.layout.collision-runtime uses engine.src.engine.layout.runtime.session.session-pagination-types✕
- Connections
- 3 pairs of types, where a type in engine.src.engine.layout.collision-runtime uses a type in engine.src.engine.layout.runtime.session.session-pagination-types.
- The types involved
engine.src.engine.layout.collision-runtime.CollisionRuntime→engine.src.engine.layout.runtime.session.session-pagination-types.ActorOverflowEntryHandlingOutcomeengine.src.engine.layout.collision-runtime.CollisionRuntime→engine.src.engine.layout.runtime.session.session-pagination-types.ActorOverflowEntrySettlementOutcomeengine.src.engine.layout.collision-runtime.CollisionRuntime→engine.src.engine.layout.runtime.session.session-pagination-types.ActorOverflowResolution
- Direction
- engine.src.engine.layout.collision-runtime uses engine.src.engine.layout.runtime.session.session-pagination-types, so a change to engine.src.engine.layout.runtime.session.session-pagination-types can break engine.src.engine.layout.collision-runtime, while a change to engine.src.engine.layout.collision-runtime can't break engine.src.engine.layout.runtime.session.session-pagination-types.
- Position
- Below the diagonal: engine.src.engine.layout.collision-runtime uses a module listed above it, which is the healthy direction.
22→21 engine.src.engine.layout.collision-runtime uses engine.src.engine.layout.packagers.packager-types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout.collision-runtime uses a type in engine.src.engine.layout.packagers.packager-types.
- The types involved
engine.src.engine.layout.collision-runtime.CollisionRuntime→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.collision-runtime.CollisionRuntime→engine.src.engine.layout.packagers.packager-types.PackagerUnit
- Direction
- engine.src.engine.layout.collision-runtime uses engine.src.engine.layout.packagers.packager-types, so a change to engine.src.engine.layout.packagers.packager-types can break engine.src.engine.layout.collision-runtime, while a change to engine.src.engine.layout.collision-runtime can't break engine.src.engine.layout.packagers.packager-types.
- Position
- Below the diagonal: engine.src.engine.layout.collision-runtime uses a module listed above it, which is the healthy direction.
23→18 engine.src.engine.layout.packagers.flow-box-packager uses engine.src.engine.layout.layout-core✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers.flow-box-packager uses a type in engine.src.engine.layout.layout-core.
- The types involved
engine.src.engine.layout.packagers.flow-box-packager.FlowBoxPackager→engine.src.engine.layout.layout-core.LayoutProcessor
- Direction
- engine.src.engine.layout.packagers.flow-box-packager uses engine.src.engine.layout.layout-core, so a change to engine.src.engine.layout.layout-core can break engine.src.engine.layout.packagers.flow-box-packager, while a change to engine.src.engine.layout.packagers.flow-box-packager can't break engine.src.engine.layout.layout-core.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.flow-box-packager uses a module listed above it, which is the healthy direction.
23→19 engine.src.engine.layout.packagers.flow-box-packager uses engine.src.engine.layout.packagers.spatial-map✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers.flow-box-packager uses a type in engine.src.engine.layout.packagers.spatial-map.
- The types involved
engine.src.engine.layout.packagers.flow-box-packager.FlowBoxPackager→engine.src.engine.layout.packagers.spatial-map.SpatialMap
- Direction
- engine.src.engine.layout.packagers.flow-box-packager uses engine.src.engine.layout.packagers.spatial-map, so a change to engine.src.engine.layout.packagers.spatial-map can break engine.src.engine.layout.packagers.flow-box-packager, while a change to engine.src.engine.layout.packagers.flow-box-packager can't break engine.src.engine.layout.packagers.spatial-map.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.flow-box-packager uses a module listed above it, which is the healthy direction.
23→21 engine.src.engine.layout.packagers.flow-box-packager uses engine.src.engine.layout.packagers.packager-types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout.packagers.flow-box-packager uses a type in engine.src.engine.layout.packagers.packager-types.
- The types involved
engine.src.engine.layout.packagers.flow-box-packager.FlowBoxPackager→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.packagers.flow-box-packager.FlowBoxPackager→engine.src.engine.layout.packagers.packager-types.PackagerUnit
- Direction
- engine.src.engine.layout.packagers.flow-box-packager uses engine.src.engine.layout.packagers.packager-types, so a change to engine.src.engine.layout.packagers.packager-types can break engine.src.engine.layout.packagers.flow-box-packager, while a change to engine.src.engine.layout.packagers.flow-box-packager can't break engine.src.engine.layout.packagers.packager-types.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.flow-box-packager uses a module listed above it, which is the healthy direction.
24→6 engine.src.engine.layout.packagers.hosted-region-packager uses engine.src.engine.types✕
- Connections
- 4 pairs of types, where a type in engine.src.engine.layout.packagers.hosted-region-packager uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout.packagers.hosted-region-packager.FrozenHostedRegionPackager→engine.src.engine.types.ZoneWorldBehaviorengine.src.engine.layout.packagers.hosted-region-packager.HostedRegionPackager→engine.src.engine.types.Boxengine.src.engine.layout.packagers.hosted-region-packager.HostedRegionPackager→engine.src.engine.types.Elementengine.src.engine.layout.packagers.hosted-region-packager.HostedRegionPackager→engine.src.engine.types.ZoneWorldBehavior
- Direction
- engine.src.engine.layout.packagers.hosted-region-packager uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout.packagers.hosted-region-packager, while a change to engine.src.engine.layout.packagers.hosted-region-packager can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.hosted-region-packager uses a module listed above it, which is the healthy direction.
24→18 engine.src.engine.layout.packagers.hosted-region-packager uses engine.src.engine.layout.layout-core✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers.hosted-region-packager uses a type in engine.src.engine.layout.layout-core.
- The types involved
engine.src.engine.layout.packagers.hosted-region-packager.HostedRegionPackager→engine.src.engine.layout.layout-core.LayoutProcessor
- Direction
- engine.src.engine.layout.packagers.hosted-region-packager uses engine.src.engine.layout.layout-core, so a change to engine.src.engine.layout.layout-core can break engine.src.engine.layout.packagers.hosted-region-packager, while a change to engine.src.engine.layout.packagers.hosted-region-packager can't break engine.src.engine.layout.layout-core.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.hosted-region-packager uses a module listed above it, which is the healthy direction.
24→21 engine.src.engine.layout.packagers.hosted-region-packager uses engine.src.engine.layout.packagers.packager-types✕
- Connections
- 4 pairs of types, where a type in engine.src.engine.layout.packagers.hosted-region-packager uses a type in engine.src.engine.layout.packagers.packager-types.
- The types involved
engine.src.engine.layout.packagers.hosted-region-packager.FrozenHostedRegionPackager→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.packagers.hosted-region-packager.FrozenHostedRegionPackager→engine.src.engine.layout.packagers.packager-types.PackagerUnitengine.src.engine.layout.packagers.hosted-region-packager.HostedRegionPackager→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.packagers.hosted-region-packager.HostedRegionPackager→engine.src.engine.layout.packagers.packager-types.PackagerUnit
- Direction
- engine.src.engine.layout.packagers.hosted-region-packager uses engine.src.engine.layout.packagers.packager-types, so a change to engine.src.engine.layout.packagers.packager-types can break engine.src.engine.layout.packagers.hosted-region-packager, while a change to engine.src.engine.layout.packagers.hosted-region-packager can't break engine.src.engine.layout.packagers.packager-types.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.hosted-region-packager uses a module listed above it, which is the healthy direction.
25→4 engine.src.engine.layout.physics-runtime uses engine.src.engine.layout.runtime.session.session-pagination-types✕
- Connections
- 5 pairs of types, where a type in engine.src.engine.layout.physics-runtime uses a type in engine.src.engine.layout.runtime.session.session-pagination-types.
- The types involved
engine.src.engine.layout.physics-runtime.PhysicsRuntime→engine.src.engine.layout.runtime.session.session-pagination-types.ActorPlacementAttemptOutcomeengine.src.engine.layout.physics-runtime.PhysicsRuntime→engine.src.engine.layout.runtime.session.session-pagination-types.ActorPlacementCommitOutcomeengine.src.engine.layout.physics-runtime.PhysicsRuntime→engine.src.engine.layout.runtime.session.session-pagination-types.ActorPlacementExecutionOutcomeengine.src.engine.layout.physics-runtime.PhysicsRuntime→engine.src.engine.layout.runtime.session.session-pagination-types.PaginationLoopActionengine.src.engine.layout.physics-runtime.PhysicsRuntime→engine.src.engine.layout.runtime.session.session-pagination-types.PaginationPlacementPreparation
- Direction
- engine.src.engine.layout.physics-runtime uses engine.src.engine.layout.runtime.session.session-pagination-types, so a change to engine.src.engine.layout.runtime.session.session-pagination-types can break engine.src.engine.layout.physics-runtime, while a change to engine.src.engine.layout.physics-runtime can't break engine.src.engine.layout.runtime.session.session-pagination-types.
- Position
- Below the diagonal: engine.src.engine.layout.physics-runtime uses a module listed above it, which is the healthy direction.
25→21 engine.src.engine.layout.physics-runtime uses engine.src.engine.layout.packagers.packager-types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout.physics-runtime uses a type in engine.src.engine.layout.packagers.packager-types.
- The types involved
engine.src.engine.layout.physics-runtime.PhysicsRuntime→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.physics-runtime.PhysicsRuntime→engine.src.engine.layout.packagers.packager-types.PackagerUnit
- Direction
- engine.src.engine.layout.physics-runtime uses engine.src.engine.layout.packagers.packager-types, so a change to engine.src.engine.layout.packagers.packager-types can break engine.src.engine.layout.physics-runtime, while a change to engine.src.engine.layout.physics-runtime can't break engine.src.engine.layout.packagers.packager-types.
- Position
- Below the diagonal: engine.src.engine.layout.physics-runtime uses a module listed above it, which is the healthy direction.
26→11 engine.src.engine.layout.runtime.session.session-runtime-types uses engine.src.engine.layout.runtime.session.session-lifecycle-types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.runtime.session.session-runtime-types uses a type in engine.src.engine.layout.runtime.session.session-lifecycle-types.
- The types involved
engine.src.engine.layout.runtime.session.session-runtime-types.Collaborator→engine.src.engine.layout.runtime.session.session-lifecycle-types.PageSurface
- Direction
- engine.src.engine.layout.runtime.session.session-runtime-types uses engine.src.engine.layout.runtime.session.session-lifecycle-types, so a change to engine.src.engine.layout.runtime.session.session-lifecycle-types can break engine.src.engine.layout.runtime.session.session-runtime-types, while a change to engine.src.engine.layout.runtime.session.session-runtime-types can't break engine.src.engine.layout.runtime.session.session-lifecycle-types.
- Position
- Below the diagonal: engine.src.engine.layout.runtime.session.session-runtime-types uses a module listed above it, which is the healthy direction.
26→21 engine.src.engine.layout.runtime.session.session-runtime-types uses engine.src.engine.layout.packagers.packager-types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout.runtime.session.session-runtime-types uses a type in engine.src.engine.layout.packagers.packager-types.
- The types involved
engine.src.engine.layout.runtime.session.session-runtime-types.Collaborator→engine.src.engine.layout.packagers.packager-types.PackagerUnitengine.src.engine.layout.runtime.session.session-runtime-types.CollaboratorHost→engine.src.engine.layout.packagers.packager-types.PackagerUnit
- Direction
- engine.src.engine.layout.runtime.session.session-runtime-types uses engine.src.engine.layout.packagers.packager-types, so a change to engine.src.engine.layout.packagers.packager-types can break engine.src.engine.layout.runtime.session.session-runtime-types, while a change to engine.src.engine.layout.runtime.session.session-runtime-types can't break engine.src.engine.layout.packagers.packager-types.
- Position
- Below the diagonal: engine.src.engine.layout.runtime.session.session-runtime-types uses a module listed above it, which is the healthy direction.
27→1 engine.src.engine.vmprint-engine uses contracts.src.context✕
- Connections
- 1 pair of types, where a type in engine.src.engine.vmprint-engine uses a type in contracts.src.context.
- The types involved
engine.src.engine.vmprint-engine.VMPrintEngine→contracts.src.context.Context
- Direction
- engine.src.engine.vmprint-engine uses contracts.src.context, so a change to contracts.src.context can break engine.src.engine.vmprint-engine, while a change to engine.src.engine.vmprint-engine can't break contracts.src.context.
- Position
- Below the diagonal: engine.src.engine.vmprint-engine uses a module listed above it, which is the healthy direction.
27→2 engine.src.engine.vmprint-engine uses contracts.src.font-manager✕
- Connections
- 1 pair of types, where a type in engine.src.engine.vmprint-engine uses a type in contracts.src.font-manager.
- The types involved
engine.src.engine.vmprint-engine.VMPrintEngine→contracts.src.font-manager.FontManager
- Direction
- engine.src.engine.vmprint-engine uses contracts.src.font-manager, so a change to contracts.src.font-manager can break engine.src.engine.vmprint-engine, while a change to engine.src.engine.vmprint-engine can't break contracts.src.font-manager.
- Position
- Below the diagonal: engine.src.engine.vmprint-engine uses a module listed above it, which is the healthy direction.
27→6 engine.src.engine.vmprint-engine uses engine.src.engine.types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.vmprint-engine uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.vmprint-engine.VMPrintEngine→engine.src.engine.types.DocumentIRengine.src.engine.vmprint-engine.VMPrintEngine→engine.src.engine.types.LayoutConfig
- Direction
- engine.src.engine.vmprint-engine uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.vmprint-engine, while a change to engine.src.engine.vmprint-engine can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.vmprint-engine uses a module listed above it, which is the healthy direction.
27→8 engine.src.engine.vmprint-engine uses contracts.src.overlay✕
- Connections
- 1 pair of types, where a type in engine.src.engine.vmprint-engine uses a type in contracts.src.overlay.
- The types involved
engine.src.engine.vmprint-engine.RenderOptions→contracts.src.overlay.OverlayProvider
- Direction
- engine.src.engine.vmprint-engine uses contracts.src.overlay, so a change to contracts.src.overlay can break engine.src.engine.vmprint-engine, while a change to engine.src.engine.vmprint-engine can't break contracts.src.overlay.
- Position
- Below the diagonal: engine.src.engine.vmprint-engine uses a module listed above it, which is the healthy direction.
27→13 engine.src.engine.vmprint-engine uses engine.src.engine.runtime-types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.vmprint-engine uses a type in engine.src.engine.runtime-types.
- The types involved
engine.src.engine.vmprint-engine.VMPrintEngine→engine.src.engine.runtime-types.EngineRuntime
- Direction
- engine.src.engine.vmprint-engine uses engine.src.engine.runtime-types, so a change to engine.src.engine.runtime-types can break engine.src.engine.vmprint-engine, while a change to engine.src.engine.vmprint-engine can't break engine.src.engine.runtime-types.
- Position
- Below the diagonal: engine.src.engine.vmprint-engine uses a module listed above it, which is the healthy direction.
27→20 engine.src.engine.vmprint-engine uses engine.src.engine.layout-engine✕
- Connections
- 1 pair of types, where a type in engine.src.engine.vmprint-engine uses a type in engine.src.engine.layout-engine.
- The types involved
engine.src.engine.vmprint-engine.VMPrintEngine→engine.src.engine.layout-engine.LayoutEngine
- Direction
- engine.src.engine.vmprint-engine uses engine.src.engine.layout-engine, so a change to engine.src.engine.layout-engine can break engine.src.engine.vmprint-engine, while a change to engine.src.engine.vmprint-engine can't break engine.src.engine.layout-engine.
- Position
- Below the diagonal: engine.src.engine.vmprint-engine uses a module listed above it, which is the healthy direction.
28→1 engine.src.engine uses contracts.src.context✕
- Connections
- 1 pair of types, where a type in engine.src.engine uses a type in contracts.src.context.
- The types involved
engine.src.engine.vmprint-engine→contracts.src.context.Context
- Direction
- engine.src.engine uses contracts.src.context, so a change to contracts.src.context can break engine.src.engine, while a change to engine.src.engine can't break contracts.src.context.
- Position
- Below the diagonal: engine.src.engine uses a module listed above it, which is the healthy direction.
28→2 engine.src.engine uses contracts.src.font-manager✕
- Connections
- 1 pair of types, where a type in engine.src.engine uses a type in contracts.src.font-manager.
- The types involved
engine.src.engine.vmprint-engine→contracts.src.font-manager.FontManager
- Direction
- engine.src.engine uses contracts.src.font-manager, so a change to contracts.src.font-manager can break engine.src.engine, while a change to engine.src.engine can't break contracts.src.font-manager.
- Position
- Below the diagonal: engine.src.engine uses a module listed above it, which is the healthy direction.
28→6 engine.src.engine uses engine.src.engine.types✕
- Connections
- 14 pairs of types, where a type in engine.src.engine uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.document→engine.src.engine.types.DocumentIRengine.src.engine.document→engine.src.engine.types.DocumentInputengine.src.engine.document→engine.src.engine.types.Elementengine.src.engine.document→engine.src.engine.types.LayoutConfigengine.src.engine.image-data→engine.src.engine.types.EmbeddedImagePayloadengine.src.engine.image-data→engine.src.engine.types.ImageFitModeengine.src.engine.interaction-model→engine.src.engine.types.Boxengine.src.engine.layout-engine→engine.src.engine.types.Boxengine.src.engine.layout-engine→engine.src.engine.types.Elementengine.src.engine.spatial-document→engine.src.engine.types.DocumentInputengine.src.engine.spatial-document→engine.src.engine.types.Elementengine.src.engine.spatial-document→engine.src.engine.types.ElementPropertiesengine.src.engine.viewport→engine.src.engine.types.Pageengine.src.engine.vmprint-engine→engine.src.engine.types.AnnotatedLayoutStream
- Direction
- engine.src.engine uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine, while a change to engine.src.engine can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine uses a module listed above it, which is the healthy direction.
28→13 engine.src.engine uses engine.src.engine.runtime-types✕
- Connections
- 1 pair of types, where a type in engine.src.engine uses a type in engine.src.engine.runtime-types.
- The types involved
engine.src.engine.runtime→engine.src.engine.runtime-types.EngineRuntime
- Direction
- engine.src.engine uses engine.src.engine.runtime-types, so a change to engine.src.engine.runtime-types can break engine.src.engine, while a change to engine.src.engine can't break engine.src.engine.runtime-types.
- Position
- Below the diagonal: engine.src.engine uses a module listed above it, which is the healthy direction.
28→27 engine.src.engine uses engine.src.engine.vmprint-engine✕
- Connections
- 1 pair of types, where a type in engine.src.engine uses a type in engine.src.engine.vmprint-engine.
- The types involved
engine.src.engine.vmprint-engine→engine.src.engine.vmprint-engine.RenderOptions
- Direction
- engine.src.engine uses engine.src.engine.vmprint-engine, so a change to engine.src.engine.vmprint-engine can break engine.src.engine, while a change to engine.src.engine can't break engine.src.engine.vmprint-engine.
- Position
- Below the diagonal: engine.src.engine uses a module listed above it, which is the healthy direction.
29→11 engine.src.engine.layout.collaborators.temporal-presentation-collaborator uses engine.src.engine.layout.runtime.session.session-lifecycle-types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.collaborators.temporal-presentation-collaborator uses a type in engine.src.engine.layout.runtime.session.session-lifecycle-types.
- The types involved
engine.src.engine.layout.collaborators.temporal-presentation-collaborator.TemporalPresentationCollaborator→engine.src.engine.layout.runtime.session.session-lifecycle-types.PageSurface
- Direction
- engine.src.engine.layout.collaborators.temporal-presentation-collaborator uses engine.src.engine.layout.runtime.session.session-lifecycle-types, so a change to engine.src.engine.layout.runtime.session.session-lifecycle-types can break engine.src.engine.layout.collaborators.temporal-presentation-collaborator, while a change to engine.src.engine.layout.collaborators.temporal-presentation-collaborator can't break engine.src.engine.layout.runtime.session.session-lifecycle-types.
- Position
- Below the diagonal: engine.src.engine.layout.collaborators.temporal-presentation-collaborator uses a module listed above it, which is the healthy direction.
29→26 engine.src.engine.layout.collaborators.temporal-presentation-collaborator uses engine.src.engine.layout.runtime.session.session-runtime-types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout.collaborators.temporal-presentation-collaborator uses a type in engine.src.engine.layout.runtime.session.session-runtime-types.
- The types involved
engine.src.engine.layout.collaborators.temporal-presentation-collaborator.TemporalPresentationCollaborator→engine.src.engine.layout.runtime.session.session-runtime-types.Collaboratorengine.src.engine.layout.collaborators.temporal-presentation-collaborator.TemporalPresentationCollaborator→engine.src.engine.layout.runtime.session.session-runtime-types.CollaboratorHost
- Direction
- engine.src.engine.layout.collaborators.temporal-presentation-collaborator uses engine.src.engine.layout.runtime.session.session-runtime-types, so a change to engine.src.engine.layout.runtime.session.session-runtime-types can break engine.src.engine.layout.collaborators.temporal-presentation-collaborator, while a change to engine.src.engine.layout.collaborators.temporal-presentation-collaborator can't break engine.src.engine.layout.runtime.session.session-runtime-types.
- Position
- Below the diagonal: engine.src.engine.layout.collaborators.temporal-presentation-collaborator uses a module listed above it, which is the healthy direction.
30→11 engine.src.engine.layout.event-dispatcher uses engine.src.engine.layout.runtime.session.session-lifecycle-types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.event-dispatcher uses a type in engine.src.engine.layout.runtime.session.session-lifecycle-types.
- The types involved
engine.src.engine.layout.event-dispatcher.EventDispatcher→engine.src.engine.layout.runtime.session.session-lifecycle-types.PageSurface
- Direction
- engine.src.engine.layout.event-dispatcher uses engine.src.engine.layout.runtime.session.session-lifecycle-types, so a change to engine.src.engine.layout.runtime.session.session-lifecycle-types can break engine.src.engine.layout.event-dispatcher, while a change to engine.src.engine.layout.event-dispatcher can't break engine.src.engine.layout.runtime.session.session-lifecycle-types.
- Position
- Below the diagonal: engine.src.engine.layout.event-dispatcher uses a module listed above it, which is the healthy direction.
30→21 engine.src.engine.layout.event-dispatcher uses engine.src.engine.layout.packagers.packager-types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.event-dispatcher uses a type in engine.src.engine.layout.packagers.packager-types.
- The types involved
engine.src.engine.layout.event-dispatcher.EventDispatcher→engine.src.engine.layout.packagers.packager-types.PackagerUnit
- Direction
- engine.src.engine.layout.event-dispatcher uses engine.src.engine.layout.packagers.packager-types, so a change to engine.src.engine.layout.packagers.packager-types can break engine.src.engine.layout.event-dispatcher, while a change to engine.src.engine.layout.event-dispatcher can't break engine.src.engine.layout.packagers.packager-types.
- Position
- Below the diagonal: engine.src.engine.layout.event-dispatcher uses a module listed above it, which is the healthy direction.
30→26 engine.src.engine.layout.event-dispatcher uses engine.src.engine.layout.runtime.session.session-runtime-types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.event-dispatcher uses a type in engine.src.engine.layout.runtime.session.session-runtime-types.
- The types involved
engine.src.engine.layout.event-dispatcher.EventDispatcher→engine.src.engine.layout.runtime.session.session-runtime-types.CollaboratorHost
- Direction
- engine.src.engine.layout.event-dispatcher uses engine.src.engine.layout.runtime.session.session-runtime-types, so a change to engine.src.engine.layout.runtime.session.session-runtime-types can break engine.src.engine.layout.event-dispatcher, while a change to engine.src.engine.layout.event-dispatcher can't break engine.src.engine.layout.runtime.session.session-runtime-types.
- Position
- Below the diagonal: engine.src.engine.layout.event-dispatcher uses a module listed above it, which is the healthy direction.
31→4 engine.src.engine.layout.placement-session-runtime uses engine.src.engine.layout.runtime.session.session-pagination-types✕
- Connections
- 5 pairs of types, where a type in engine.src.engine.layout.placement-session-runtime uses a type in engine.src.engine.layout.runtime.session.session-pagination-types.
- The types involved
engine.src.engine.layout.placement-session-runtime.PlacementSessionRuntime→engine.src.engine.layout.runtime.session.session-pagination-types.ActorOverflowEntryHandlingOutcomeengine.src.engine.layout.placement-session-runtime.PlacementSessionRuntime→engine.src.engine.layout.runtime.session.session-pagination-types.ActorOverflowEntrySettlementOutcomeengine.src.engine.layout.placement-session-runtime.PlacementSessionRuntime→engine.src.engine.layout.runtime.session.session-pagination-types.ActorOverflowResolutionengine.src.engine.layout.placement-session-runtime.PlacementSessionRuntime→engine.src.engine.layout.runtime.session.session-pagination-types.ActorPlacementAttemptOutcomeengine.src.engine.layout.placement-session-runtime.PlacementSessionRuntime→engine.src.engine.layout.runtime.session.session-pagination-types.PaginationLoopAction
- Direction
- engine.src.engine.layout.placement-session-runtime uses engine.src.engine.layout.runtime.session.session-pagination-types, so a change to engine.src.engine.layout.runtime.session.session-pagination-types can break engine.src.engine.layout.placement-session-runtime, while a change to engine.src.engine.layout.placement-session-runtime can't break engine.src.engine.layout.runtime.session.session-pagination-types.
- Position
- Below the diagonal: engine.src.engine.layout.placement-session-runtime uses a module listed above it, which is the healthy direction.
31→21 engine.src.engine.layout.placement-session-runtime uses engine.src.engine.layout.packagers.packager-types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout.placement-session-runtime uses a type in engine.src.engine.layout.packagers.packager-types.
- The types involved
engine.src.engine.layout.placement-session-runtime.PlacementSessionRuntime→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.placement-session-runtime.PlacementSessionRuntime→engine.src.engine.layout.packagers.packager-types.PackagerUnit
- Direction
- engine.src.engine.layout.placement-session-runtime uses engine.src.engine.layout.packagers.packager-types, so a change to engine.src.engine.layout.packagers.packager-types can break engine.src.engine.layout.placement-session-runtime, while a change to engine.src.engine.layout.placement-session-runtime can't break engine.src.engine.layout.packagers.packager-types.
- Position
- Below the diagonal: engine.src.engine.layout.placement-session-runtime uses a module listed above it, which is the healthy direction.
31→22 engine.src.engine.layout.placement-session-runtime uses engine.src.engine.layout.collision-runtime✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.placement-session-runtime uses a type in engine.src.engine.layout.collision-runtime.
- The types involved
engine.src.engine.layout.placement-session-runtime.PlacementSessionRuntime→engine.src.engine.layout.collision-runtime.CollisionRuntime
- Direction
- engine.src.engine.layout.placement-session-runtime uses engine.src.engine.layout.collision-runtime, so a change to engine.src.engine.layout.collision-runtime can break engine.src.engine.layout.placement-session-runtime, while a change to engine.src.engine.layout.placement-session-runtime can't break engine.src.engine.layout.collision-runtime.
- Position
- Below the diagonal: engine.src.engine.layout.placement-session-runtime uses a module listed above it, which is the healthy direction.
31→25 engine.src.engine.layout.placement-session-runtime uses engine.src.engine.layout.physics-runtime✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.placement-session-runtime uses a type in engine.src.engine.layout.physics-runtime.
- The types involved
engine.src.engine.layout.placement-session-runtime.PlacementSessionRuntime→engine.src.engine.layout.physics-runtime.PhysicsRuntime
- Direction
- engine.src.engine.layout.placement-session-runtime uses engine.src.engine.layout.physics-runtime, so a change to engine.src.engine.layout.physics-runtime can break engine.src.engine.layout.placement-session-runtime, while a change to engine.src.engine.layout.placement-session-runtime can't break engine.src.engine.layout.physics-runtime.
- Position
- Below the diagonal: engine.src.engine.layout.placement-session-runtime uses a module listed above it, which is the healthy direction.
32→6 engine.src.engine.layout.runtime.page-finalization.page-region-finalization uses engine.src.engine.types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout.runtime.page-finalization.page-region-finalization uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout.runtime.page-finalization.page-region-finalization.PageRegionCollaborator→engine.src.engine.types.LayoutConfigengine.src.engine.layout.runtime.page-finalization.page-region-finalization.ReactivePageRegionActor→engine.src.engine.types.PageRegionContent
- Direction
- engine.src.engine.layout.runtime.page-finalization.page-region-finalization uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout.runtime.page-finalization.page-region-finalization, while a change to engine.src.engine.layout.runtime.page-finalization.page-region-finalization can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout.runtime.page-finalization.page-region-finalization uses a module listed above it, which is the healthy direction.
32→11 engine.src.engine.layout.runtime.page-finalization.page-region-finalization uses engine.src.engine.layout.runtime.session.session-lifecycle-types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.runtime.page-finalization.page-region-finalization uses a type in engine.src.engine.layout.runtime.session.session-lifecycle-types.
- The types involved
engine.src.engine.layout.runtime.page-finalization.page-region-finalization.PageRegionCollaborator→engine.src.engine.layout.runtime.session.session-lifecycle-types.PageSurface
- Direction
- engine.src.engine.layout.runtime.page-finalization.page-region-finalization uses engine.src.engine.layout.runtime.session.session-lifecycle-types, so a change to engine.src.engine.layout.runtime.session.session-lifecycle-types can break engine.src.engine.layout.runtime.page-finalization.page-region-finalization, while a change to engine.src.engine.layout.runtime.page-finalization.page-region-finalization can't break engine.src.engine.layout.runtime.session.session-lifecycle-types.
- Position
- Below the diagonal: engine.src.engine.layout.runtime.page-finalization.page-region-finalization uses a module listed above it, which is the healthy direction.
32→21 engine.src.engine.layout.runtime.page-finalization.page-region-finalization uses engine.src.engine.layout.packagers.packager-types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout.runtime.page-finalization.page-region-finalization uses a type in engine.src.engine.layout.packagers.packager-types.
- The types involved
engine.src.engine.layout.runtime.page-finalization.page-region-finalization.ReactivePageRegionActor→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.runtime.page-finalization.page-region-finalization.ReactivePageRegionActor→engine.src.engine.layout.packagers.packager-types.PackagerUnit
- Direction
- engine.src.engine.layout.runtime.page-finalization.page-region-finalization uses engine.src.engine.layout.packagers.packager-types, so a change to engine.src.engine.layout.packagers.packager-types can break engine.src.engine.layout.runtime.page-finalization.page-region-finalization, while a change to engine.src.engine.layout.runtime.page-finalization.page-region-finalization can't break engine.src.engine.layout.packagers.packager-types.
- Position
- Below the diagonal: engine.src.engine.layout.runtime.page-finalization.page-region-finalization uses a module listed above it, which is the healthy direction.
32→26 engine.src.engine.layout.runtime.page-finalization.page-region-finalization uses engine.src.engine.layout.runtime.session.session-runtime-types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout.runtime.page-finalization.page-region-finalization uses a type in engine.src.engine.layout.runtime.session.session-runtime-types.
- The types involved
engine.src.engine.layout.runtime.page-finalization.page-region-finalization.PageRegionCollaborator→engine.src.engine.layout.runtime.session.session-runtime-types.Collaboratorengine.src.engine.layout.runtime.page-finalization.page-region-finalization.PageRegionCollaborator→engine.src.engine.layout.runtime.session.session-runtime-types.CollaboratorHost
- Direction
- engine.src.engine.layout.runtime.page-finalization.page-region-finalization uses engine.src.engine.layout.runtime.session.session-runtime-types, so a change to engine.src.engine.layout.runtime.session.session-runtime-types can break engine.src.engine.layout.runtime.page-finalization.page-region-finalization, while a change to engine.src.engine.layout.runtime.page-finalization.page-region-finalization can't break engine.src.engine.layout.runtime.session.session-runtime-types.
- Position
- Below the diagonal: engine.src.engine.layout.runtime.page-finalization.page-region-finalization uses a module listed above it, which is the healthy direction.
33→5 engine.src.engine.layout.runtime.scripting.script-runtime-pass uses engine.src.engine.layout.script-runtime-host✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.runtime.scripting.script-runtime-pass uses a type in engine.src.engine.layout.script-runtime-host.
- The types involved
engine.src.engine.layout.runtime.scripting.script-runtime-pass.ScriptRuntimeCollaborator→engine.src.engine.layout.script-runtime-host.ScriptRuntimeHost
- Direction
- engine.src.engine.layout.runtime.scripting.script-runtime-pass uses engine.src.engine.layout.script-runtime-host, so a change to engine.src.engine.layout.script-runtime-host can break engine.src.engine.layout.runtime.scripting.script-runtime-pass, while a change to engine.src.engine.layout.runtime.scripting.script-runtime-pass can't break engine.src.engine.layout.script-runtime-host.
- Position
- Below the diagonal: engine.src.engine.layout.runtime.scripting.script-runtime-pass uses a module listed above it, which is the healthy direction.
33→6 engine.src.engine.layout.runtime.scripting.script-runtime-pass uses engine.src.engine.types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.runtime.scripting.script-runtime-pass uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout.runtime.scripting.script-runtime-pass.ScriptRuntimeCollaborator→engine.src.engine.types.Element
- Direction
- engine.src.engine.layout.runtime.scripting.script-runtime-pass uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout.runtime.scripting.script-runtime-pass, while a change to engine.src.engine.layout.runtime.scripting.script-runtime-pass can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout.runtime.scripting.script-runtime-pass uses a module listed above it, which is the healthy direction.
33→26 engine.src.engine.layout.runtime.scripting.script-runtime-pass uses engine.src.engine.layout.runtime.session.session-runtime-types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout.runtime.scripting.script-runtime-pass uses a type in engine.src.engine.layout.runtime.session.session-runtime-types.
- The types involved
engine.src.engine.layout.runtime.scripting.script-runtime-pass.ScriptRuntimeCollaborator→engine.src.engine.layout.runtime.session.session-runtime-types.Collaboratorengine.src.engine.layout.runtime.scripting.script-runtime-pass.ScriptRuntimeCollaborator→engine.src.engine.layout.runtime.session.session-runtime-types.CollaboratorHost
- Direction
- engine.src.engine.layout.runtime.scripting.script-runtime-pass uses engine.src.engine.layout.runtime.session.session-runtime-types, so a change to engine.src.engine.layout.runtime.session.session-runtime-types can break engine.src.engine.layout.runtime.scripting.script-runtime-pass, while a change to engine.src.engine.layout.runtime.scripting.script-runtime-pass can't break engine.src.engine.layout.runtime.session.session-runtime-types.
- Position
- Below the diagonal: engine.src.engine.layout.runtime.scripting.script-runtime-pass uses a module listed above it, which is the healthy direction.
34→6 engine.src.engine.layout uses engine.src.engine.types✕
- Connections
- 23 pairs of types, where a type in engine.src.engine.layout uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout.actor-communication-runtime→engine.src.engine.types.Boxengine.src.engine.layout.actor-communication-runtime→engine.src.engine.types.Pageengine.src.engine.layout.flow-fragment-state→engine.src.engine.types.BoxMetaengine.src.engine.layout.flow-fragment-state→engine.src.engine.types.ElementStyleengine.src.engine.layout.layout-flow-splitting→engine.src.engine.types.BoxMetaengine.src.engine.layout.layout-session→engine.src.engine.types.Boxengine.src.engine.layout.layout-table→engine.src.engine.types.Elementengine.src.engine.layout.layout-table→engine.src.engine.types.ElementStyleengine.src.engine.layout.normalized-list→engine.src.engine.types.Elementengine.src.engine.layout.normalized-list→engine.src.engine.types.ListKindengine.src.engine.layout.normalized-list→engine.src.engine.types.ListLayoutOptionsengine.src.engine.layout.normalized-list→engine.src.engine.types.ListMarkerStyleengine.src.engine.layout.normalized-story→engine.src.engine.types.Elementengine.src.engine.layout.normalized-story→engine.src.engine.types.StoryLayoutDirectiveengine.src.engine.layout.normalized-table→engine.src.engine.types.Elementengine.src.engine.layout.normalized-table→engine.src.engine.types.TableLayoutOptionsengine.src.engine.layout.page-region-summary→engine.src.engine.types.DebugRegionengine.src.engine.layout.page-region-summary→engine.src.engine.types.Pageengine.src.engine.layout.rich-text-extractor→engine.src.engine.types.Elementengine.src.engine.layout.runtime-formatting→engine.src.engine.types.Elementengine.src.engine.layout.spatial-field-reflow→engine.src.engine.types.Elementengine.src.engine.layout.spatial-field-reflow→engine.src.engine.types.ElementStyleengine.src.engine.layout.text-justification→engine.src.engine.types.RichLine
- Direction
- engine.src.engine.layout uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout, while a change to engine.src.engine.layout can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout uses a module listed above it, which is the healthy direction.
34→9 engine.src.engine.layout uses engine.src.engine.layout.collider-field✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout uses a type in engine.src.engine.layout.collider-field.
- The types involved
engine.src.engine.layout.collider-field→engine.src.engine.layout.collider-field.CompiledCollider
- Direction
- engine.src.engine.layout uses engine.src.engine.layout.collider-field, so a change to engine.src.engine.layout.collider-field can break engine.src.engine.layout, while a change to engine.src.engine.layout can't break engine.src.engine.layout.collider-field.
- Position
- Below the diagonal: engine.src.engine.layout uses a module listed above it, which is the healthy direction.
34→19 engine.src.engine.layout uses engine.src.engine.layout.packagers.spatial-map✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout uses a type in engine.src.engine.layout.packagers.spatial-map.
- The types involved
engine.src.engine.layout.collider-field→engine.src.engine.layout.packagers.spatial-map.OccupiedRectengine.src.engine.layout.spatial-field-reflow→engine.src.engine.layout.packagers.spatial-map.SpatialMap
- Direction
- engine.src.engine.layout uses engine.src.engine.layout.packagers.spatial-map, so a change to engine.src.engine.layout.packagers.spatial-map can break engine.src.engine.layout, while a change to engine.src.engine.layout can't break engine.src.engine.layout.packagers.spatial-map.
- Position
- Below the diagonal: engine.src.engine.layout uses a module listed above it, which is the healthy direction.
34→21 engine.src.engine.layout uses engine.src.engine.layout.packagers.packager-types✕
- Connections
- 4 pairs of types, where a type in engine.src.engine.layout uses a type in engine.src.engine.layout.packagers.packager-types.
- The types involved
engine.src.engine.layout.layout-session→engine.src.engine.layout.packagers.packager-types.PackagerUnitengine.src.engine.layout.runtime-formatting→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.runtime-formatting→engine.src.engine.layout.packagers.packager-types.PackagerUnitengine.src.engine.layout.transitions-runtime→engine.src.engine.layout.packagers.packager-types.PackagerContext
- Direction
- engine.src.engine.layout uses engine.src.engine.layout.packagers.packager-types, so a change to engine.src.engine.layout.packagers.packager-types can break engine.src.engine.layout, while a change to engine.src.engine.layout can't break engine.src.engine.layout.packagers.packager-types.
- Position
- Below the diagonal: engine.src.engine.layout uses a module listed above it, which is the healthy direction.
34→29 engine.src.engine.layout uses engine.src.engine.layout.collaborators.temporal-presentation-collaborator✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout uses a type in engine.src.engine.layout.collaborators.temporal-presentation-collaborator.
- The types involved
engine.src.engine.layout.simulation-report→engine.src.engine.layout.collaborators.temporal-presentation-collaborator.TemporalPresentationTimeline
- Direction
- engine.src.engine.layout uses engine.src.engine.layout.collaborators.temporal-presentation-collaborator, so a change to engine.src.engine.layout.collaborators.temporal-presentation-collaborator can break engine.src.engine.layout, while a change to engine.src.engine.layout can't break engine.src.engine.layout.collaborators.temporal-presentation-collaborator.
- Position
- Below the diagonal: engine.src.engine.layout uses a module listed above it, which is the healthy direction.
35→6 engine.src.engine.layout.runtime.session.session-collaboration-runtime uses engine.src.engine.types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout.runtime.session.session-collaboration-runtime uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout.runtime.session.session-collaboration-runtime.SessionCollaborationRuntime→engine.src.engine.types.Pageengine.src.engine.layout.runtime.session.session-collaboration-runtime.SessionCollaborationRuntime→engine.src.engine.types.PageReservationSelector
- Direction
- engine.src.engine.layout.runtime.session.session-collaboration-runtime uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout.runtime.session.session-collaboration-runtime, while a change to engine.src.engine.layout.runtime.session.session-collaboration-runtime can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout.runtime.session.session-collaboration-runtime uses a module listed above it, which is the healthy direction.
35→10 engine.src.engine.layout.runtime.session.session-collaboration-runtime uses engine.src.engine.layout.lifecycle-runtime✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.runtime.session.session-collaboration-runtime uses a type in engine.src.engine.layout.lifecycle-runtime.
- The types involved
engine.src.engine.layout.runtime.session.session-collaboration-runtime.SessionCollaborationRuntime→engine.src.engine.layout.lifecycle-runtime.LifecycleRuntime
- Direction
- engine.src.engine.layout.runtime.session.session-collaboration-runtime uses engine.src.engine.layout.lifecycle-runtime, so a change to engine.src.engine.layout.lifecycle-runtime can break engine.src.engine.layout.runtime.session.session-collaboration-runtime, while a change to engine.src.engine.layout.runtime.session.session-collaboration-runtime can't break engine.src.engine.layout.lifecycle-runtime.
- Position
- Below the diagonal: engine.src.engine.layout.runtime.session.session-collaboration-runtime uses a module listed above it, which is the healthy direction.
35→12 engine.src.engine.layout.runtime.session.session-collaboration-runtime uses engine.src.engine.layout.session-world-runtime✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.runtime.session.session-collaboration-runtime uses a type in engine.src.engine.layout.session-world-runtime.
- The types involved
engine.src.engine.layout.runtime.session.session-collaboration-runtime.SessionCollaborationRuntime→engine.src.engine.layout.session-world-runtime.SessionWorldRuntime
- Direction
- engine.src.engine.layout.runtime.session.session-collaboration-runtime uses engine.src.engine.layout.session-world-runtime, so a change to engine.src.engine.layout.session-world-runtime can break engine.src.engine.layout.runtime.session.session-collaboration-runtime, while a change to engine.src.engine.layout.runtime.session.session-collaboration-runtime can't break engine.src.engine.layout.session-world-runtime.
- Position
- Below the diagonal: engine.src.engine.layout.runtime.session.session-collaboration-runtime uses a module listed above it, which is the healthy direction.
35→30 engine.src.engine.layout.runtime.session.session-collaboration-runtime uses engine.src.engine.layout.event-dispatcher✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.runtime.session.session-collaboration-runtime uses a type in engine.src.engine.layout.event-dispatcher.
- The types involved
engine.src.engine.layout.runtime.session.session-collaboration-runtime.SessionCollaborationRuntime→engine.src.engine.layout.event-dispatcher.EventDispatcher
- Direction
- engine.src.engine.layout.runtime.session.session-collaboration-runtime uses engine.src.engine.layout.event-dispatcher, so a change to engine.src.engine.layout.event-dispatcher can break engine.src.engine.layout.runtime.session.session-collaboration-runtime, while a change to engine.src.engine.layout.runtime.session.session-collaboration-runtime can't break engine.src.engine.layout.event-dispatcher.
- Position
- Below the diagonal: engine.src.engine.layout.runtime.session.session-collaboration-runtime uses a module listed above it, which is the healthy direction.
36→4 engine.src.engine.layout.layout-session uses engine.src.engine.layout.runtime.session.session-pagination-types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout.layout-session uses a type in engine.src.engine.layout.runtime.session.session-pagination-types.
- The types involved
engine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.layout.runtime.session.session-pagination-types.PaginationLoopActionengine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.layout.runtime.session.session-pagination-types.PaginationPlacementPreparation
- Direction
- engine.src.engine.layout.layout-session uses engine.src.engine.layout.runtime.session.session-pagination-types, so a change to engine.src.engine.layout.runtime.session.session-pagination-types can break engine.src.engine.layout.layout-session, while a change to engine.src.engine.layout.layout-session can't break engine.src.engine.layout.runtime.session.session-pagination-types.
- Position
- Below the diagonal: engine.src.engine.layout.layout-session uses a module listed above it, which is the healthy direction.
36→6 engine.src.engine.layout.layout-session uses engine.src.engine.types✕
- Connections
- 6 pairs of types, where a type in engine.src.engine.layout.layout-session uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.types.LayoutConfigengine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.types.Pageengine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.types.PageReservationSelectorengine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.types.SimulationProgressionConfigengine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.types.SimulationProgressionPolicyengine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.types.SimulationStopReason
- Direction
- engine.src.engine.layout.layout-session uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout.layout-session, while a change to engine.src.engine.layout.layout-session can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout.layout-session uses a module listed above it, which is the healthy direction.
36→10 engine.src.engine.layout.layout-session uses engine.src.engine.layout.lifecycle-runtime✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.layout-session uses a type in engine.src.engine.layout.lifecycle-runtime.
- The types involved
engine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.layout.lifecycle-runtime.LifecycleRuntime
- Direction
- engine.src.engine.layout.layout-session uses engine.src.engine.layout.lifecycle-runtime, so a change to engine.src.engine.layout.lifecycle-runtime can break engine.src.engine.layout.layout-session, while a change to engine.src.engine.layout.layout-session can't break engine.src.engine.layout.lifecycle-runtime.
- Position
- Below the diagonal: engine.src.engine.layout.layout-session uses a module listed above it, which is the healthy direction.
36→12 engine.src.engine.layout.layout-session uses engine.src.engine.layout.session-world-runtime✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.layout-session uses a type in engine.src.engine.layout.session-world-runtime.
- The types involved
engine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.layout.session-world-runtime.SessionWorldRuntime
- Direction
- engine.src.engine.layout.layout-session uses engine.src.engine.layout.session-world-runtime, so a change to engine.src.engine.layout.session-world-runtime can break engine.src.engine.layout.layout-session, while a change to engine.src.engine.layout.layout-session can't break engine.src.engine.layout.session-world-runtime.
- Position
- Below the diagonal: engine.src.engine.layout.layout-session uses a module listed above it, which is the healthy direction.
36→13 engine.src.engine.layout.layout-session uses engine.src.engine.runtime-types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.layout-session uses a type in engine.src.engine.runtime-types.
- The types involved
engine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.runtime-types.EngineRuntime
- Direction
- engine.src.engine.layout.layout-session uses engine.src.engine.runtime-types, so a change to engine.src.engine.runtime-types can break engine.src.engine.layout.layout-session, while a change to engine.src.engine.layout.layout-session can't break engine.src.engine.runtime-types.
- Position
- Below the diagonal: engine.src.engine.layout.layout-session uses a module listed above it, which is the healthy direction.
36→21 engine.src.engine.layout.layout-session uses engine.src.engine.layout.packagers.packager-types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout.layout-session uses a type in engine.src.engine.layout.packagers.packager-types.
- The types involved
engine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.layout.packagers.packager-types.PackagerUnit
- Direction
- engine.src.engine.layout.layout-session uses engine.src.engine.layout.packagers.packager-types, so a change to engine.src.engine.layout.packagers.packager-types can break engine.src.engine.layout.layout-session, while a change to engine.src.engine.layout.layout-session can't break engine.src.engine.layout.packagers.packager-types.
- Position
- Below the diagonal: engine.src.engine.layout.layout-session uses a module listed above it, which is the healthy direction.
36→22 engine.src.engine.layout.layout-session uses engine.src.engine.layout.collision-runtime✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.layout-session uses a type in engine.src.engine.layout.collision-runtime.
- The types involved
engine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.layout.collision-runtime.CollisionRuntime
- Direction
- engine.src.engine.layout.layout-session uses engine.src.engine.layout.collision-runtime, so a change to engine.src.engine.layout.collision-runtime can break engine.src.engine.layout.layout-session, while a change to engine.src.engine.layout.layout-session can't break engine.src.engine.layout.collision-runtime.
- Position
- Below the diagonal: engine.src.engine.layout.layout-session uses a module listed above it, which is the healthy direction.
36→25 engine.src.engine.layout.layout-session uses engine.src.engine.layout.physics-runtime✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.layout-session uses a type in engine.src.engine.layout.physics-runtime.
- The types involved
engine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.layout.physics-runtime.PhysicsRuntime
- Direction
- engine.src.engine.layout.layout-session uses engine.src.engine.layout.physics-runtime, so a change to engine.src.engine.layout.physics-runtime can break engine.src.engine.layout.layout-session, while a change to engine.src.engine.layout.layout-session can't break engine.src.engine.layout.physics-runtime.
- Position
- Below the diagonal: engine.src.engine.layout.layout-session uses a module listed above it, which is the healthy direction.
36→30 engine.src.engine.layout.layout-session uses engine.src.engine.layout.event-dispatcher✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.layout-session uses a type in engine.src.engine.layout.event-dispatcher.
- The types involved
engine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.layout.event-dispatcher.EventDispatcher
- Direction
- engine.src.engine.layout.layout-session uses engine.src.engine.layout.event-dispatcher, so a change to engine.src.engine.layout.event-dispatcher can break engine.src.engine.layout.layout-session, while a change to engine.src.engine.layout.layout-session can't break engine.src.engine.layout.event-dispatcher.
- Position
- Below the diagonal: engine.src.engine.layout.layout-session uses a module listed above it, which is the healthy direction.
36→31 engine.src.engine.layout.layout-session uses engine.src.engine.layout.placement-session-runtime✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.layout-session uses a type in engine.src.engine.layout.placement-session-runtime.
- The types involved
engine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.layout.placement-session-runtime.PlacementSessionRuntime
- Direction
- engine.src.engine.layout.layout-session uses engine.src.engine.layout.placement-session-runtime, so a change to engine.src.engine.layout.placement-session-runtime can break engine.src.engine.layout.layout-session, while a change to engine.src.engine.layout.layout-session can't break engine.src.engine.layout.placement-session-runtime.
- Position
- Below the diagonal: engine.src.engine.layout.layout-session uses a module listed above it, which is the healthy direction.
36→35 engine.src.engine.layout.layout-session uses engine.src.engine.layout.runtime.session.session-collaboration-runtime✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.layout-session uses a type in engine.src.engine.layout.runtime.session.session-collaboration-runtime.
- The types involved
engine.src.engine.layout.layout-session.LayoutSession→engine.src.engine.layout.runtime.session.session-collaboration-runtime.SessionCollaborationRuntime
- Direction
- engine.src.engine.layout.layout-session uses engine.src.engine.layout.runtime.session.session-collaboration-runtime, so a change to engine.src.engine.layout.runtime.session.session-collaboration-runtime can break engine.src.engine.layout.layout-session, while a change to engine.src.engine.layout.layout-session can't break engine.src.engine.layout.runtime.session.session-collaboration-runtime.
- Position
- Below the diagonal: engine.src.engine.layout.layout-session uses a module listed above it, which is the healthy direction.
37→3 engine.src.engine.layout.packagers uses contracts.src.text-delegate✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers uses a type in contracts.src.text-delegate.
- The types involved
engine.src.engine.layout.packagers.dropcap-packager→contracts.src.text-delegate.TextDelegate
- Direction
- engine.src.engine.layout.packagers uses contracts.src.text-delegate, so a change to contracts.src.text-delegate can break engine.src.engine.layout.packagers, while a change to engine.src.engine.layout.packagers can't break contracts.src.text-delegate.
- Position
- Below the diagonal: engine.src.engine.layout.packagers uses a module listed above it, which is the healthy direction.
37→6 engine.src.engine.layout.packagers uses engine.src.engine.types✕
- Connections
- 30 pairs of types, where a type in engine.src.engine.layout.packagers uses a type in engine.src.engine.types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
engine.src.engine.layout.packagers.contained-field-geometry→engine.src.engine.types.Elementengine.src.engine.layout.packagers.contained-flow-packager→engine.src.engine.types.Elementengine.src.engine.layout.packagers.contained-overflow-fragments→engine.src.engine.types.Boxengine.src.engine.layout.packagers.contained-overflow-fragments→engine.src.engine.types.Elementengine.src.engine.layout.packagers.contained-overflow-fragments→engine.src.engine.types.ElementStyleengine.src.engine.layout.packagers.create-packagers→engine.src.engine.types.Elementengine.src.engine.layout.packagers.dropcap-packager→engine.src.engine.types.Elementengine.src.engine.layout.packagers.field-actor-packager→engine.src.engine.types.Elementengine.src.engine.layout.packagers.field-actor-packager→engine.src.engine.types.ElementStyleengine.src.engine.layout.packagers.hosted-region-packager→engine.src.engine.types.Boxengine.src.engine.layout.packagers.hosted-region-runtime→engine.src.engine.types.Boxengine.src.engine.layout.packagers.hosted-region-settlement→engine.src.engine.types.Boxengine.src.engine.layout.packagers.hosted-region-settlement→engine.src.engine.types.Elementengine.src.engine.layout.packagers.hosted-region-settlement→engine.src.engine.types.SpatialFieldDirectiveengine.src.engine.layout.packagers.hosted-region-settlement→engine.src.engine.types.StoryFloatAlignengine.src.engine.layout.packagers.list-packager→engine.src.engine.types.Boxengine.src.engine.layout.packagers.list-packager→engine.src.engine.types.Elementengine.src.engine.layout.packagers.list-packager→engine.src.engine.types.ElementStyleengine.src.engine.layout.packagers.list-packager→engine.src.engine.types.ListMarkerStyleengine.src.engine.layout.packagers.packager-identity→engine.src.engine.types.Elementengine.src.engine.layout.packagers.script-document-packager→engine.src.engine.types.Elementengine.src.engine.layout.packagers.scripted-flow-box-packager→engine.src.engine.types.Elementengine.src.engine.layout.packagers.spatial-field-capability→engine.src.engine.types.SimulationMotionAxisengine.src.engine.layout.packagers.spatial-grid-packager→engine.src.engine.types.Boxengine.src.engine.layout.packagers.story-packager→engine.src.engine.types.Box
- Direction
- engine.src.engine.layout.packagers uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout.packagers, while a change to engine.src.engine.layout.packagers can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout.packagers uses a module listed above it, which is the healthy direction.
37→18 engine.src.engine.layout.packagers uses engine.src.engine.layout.layout-core✕
- Connections
- 7 pairs of types, where a type in engine.src.engine.layout.packagers uses a type in engine.src.engine.layout.layout-core.
- The types involved
engine.src.engine.layout.packagers.contained-overflow-fragments→engine.src.engine.layout.layout-core.LayoutProcessorengine.src.engine.layout.packagers.create-packagers→engine.src.engine.layout.layout-core.LayoutProcessorengine.src.engine.layout.packagers.field-actor-packager→engine.src.engine.layout.layout-core.LayoutProcessorengine.src.engine.layout.packagers.hosted-region-runtime→engine.src.engine.layout.layout-core.LayoutProcessorengine.src.engine.layout.packagers.hosted-region-settlement→engine.src.engine.layout.layout-core.LayoutProcessorengine.src.engine.layout.packagers.region-actor-queues→engine.src.engine.layout.layout-core.LayoutProcessorengine.src.engine.layout.packagers.world-plain-packager→engine.src.engine.layout.layout-core.LayoutProcessor
- Direction
- engine.src.engine.layout.packagers uses engine.src.engine.layout.layout-core, so a change to engine.src.engine.layout.layout-core can break engine.src.engine.layout.packagers, while a change to engine.src.engine.layout.packagers can't break engine.src.engine.layout.layout-core.
- Position
- Below the diagonal: engine.src.engine.layout.packagers uses a module listed above it, which is the healthy direction.
37→19 engine.src.engine.layout.packagers uses engine.src.engine.layout.packagers.spatial-map✕
- Connections
- 3 pairs of types, where a type in engine.src.engine.layout.packagers uses a type in engine.src.engine.layout.packagers.spatial-map.
- The types involved
engine.src.engine.layout.packagers.contained-field-geometry→engine.src.engine.layout.packagers.spatial-map.SpatialMapengine.src.engine.layout.packagers.hosted-region-settlement→engine.src.engine.layout.packagers.spatial-map.OccupiedRectengine.src.engine.layout.packagers.hosted-region-settlement→engine.src.engine.layout.packagers.spatial-map.SpatialMap
- Direction
- engine.src.engine.layout.packagers uses engine.src.engine.layout.packagers.spatial-map, so a change to engine.src.engine.layout.packagers.spatial-map can break engine.src.engine.layout.packagers, while a change to engine.src.engine.layout.packagers can't break engine.src.engine.layout.packagers.spatial-map.
- Position
- Below the diagonal: engine.src.engine.layout.packagers uses a module listed above it, which is the healthy direction.
37→21 engine.src.engine.layout.packagers uses engine.src.engine.layout.packagers.packager-types✕
- Connections
- 15 pairs of types, where a type in engine.src.engine.layout.packagers uses a type in engine.src.engine.layout.packagers.packager-types.
- The types involved
engine.src.engine.layout.packagers.create-packagers→engine.src.engine.layout.packagers.packager-types.PackagerUnitengine.src.engine.layout.packagers.hosted-region-packager→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.packagers.hosted-region-packager→engine.src.engine.layout.packagers.packager-types.PackagerUnitengine.src.engine.layout.packagers.hosted-region-runtime→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.packagers.hosted-region-settlement→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.packagers.hosted-region-settlement→engine.src.engine.layout.packagers.packager-types.PackagerUnitengine.src.engine.layout.packagers.list-packager→engine.src.engine.layout.packagers.packager-types.PackagerUnitengine.src.engine.layout.packagers.packager-types→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.packagers.packager-types→engine.src.engine.layout.packagers.packager-types.PackagerPreparationPhaseengine.src.engine.layout.packagers.packager-types→engine.src.engine.layout.packagers.packager-types.PackagerUnitengine.src.engine.layout.packagers.script-document-packager→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.packagers.scripted-flow-box-packager→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.packagers.spatial-field-capability→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.packagers.story-packager→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.packagers.text-hit-testing→engine.src.engine.layout.packagers.packager-types.LayoutBox
- Direction
- engine.src.engine.layout.packagers uses engine.src.engine.layout.packagers.packager-types, so a change to engine.src.engine.layout.packagers.packager-types can break engine.src.engine.layout.packagers, while a change to engine.src.engine.layout.packagers can't break engine.src.engine.layout.packagers.packager-types.
- Position
- Below the diagonal: engine.src.engine.layout.packagers uses a module listed above it, which is the healthy direction.
37→33 engine.src.engine.layout.packagers uses engine.src.engine.layout.runtime.scripting.script-runtime-pass✕
- Connections
- 6 pairs of types, where a type in engine.src.engine.layout.packagers uses a type in engine.src.engine.layout.runtime.scripting.script-runtime-pass.
- The types involved
engine.src.engine.layout.packagers.script-document-packager→engine.src.engine.layout.runtime.scripting.script-runtime-pass.InsertPositionengine.src.engine.layout.packagers.script-document-packager→engine.src.engine.layout.runtime.scripting.script-runtime-pass.ReplaceResultengine.src.engine.layout.packagers.script-document-packager→engine.src.engine.layout.runtime.scripting.script-runtime-pass.StructuralOperationengine.src.engine.layout.packagers.scripted-flow-box-packager→engine.src.engine.layout.runtime.scripting.script-runtime-pass.InsertPositionengine.src.engine.layout.packagers.scripted-flow-box-packager→engine.src.engine.layout.runtime.scripting.script-runtime-pass.ReplaceResultengine.src.engine.layout.packagers.scripted-flow-box-packager→engine.src.engine.layout.runtime.scripting.script-runtime-pass.StructuralOperation
- Direction
- engine.src.engine.layout.packagers uses engine.src.engine.layout.runtime.scripting.script-runtime-pass, so a change to engine.src.engine.layout.runtime.scripting.script-runtime-pass can break engine.src.engine.layout.packagers, while a change to engine.src.engine.layout.packagers can't break engine.src.engine.layout.runtime.scripting.script-runtime-pass.
- Position
- Below the diagonal: engine.src.engine.layout.packagers uses a module listed above it, which is the healthy direction.
37→36 engine.src.engine.layout.packagers uses engine.src.engine.layout.layout-session✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout.packagers uses a type in engine.src.engine.layout.layout-session.
- The types involved
engine.src.engine.layout.packagers.script-document-packager→engine.src.engine.layout.layout-session.LayoutSessionengine.src.engine.layout.packagers.scripted-flow-box-packager→engine.src.engine.layout.layout-session.LayoutSession
- Direction
- engine.src.engine.layout.packagers uses engine.src.engine.layout.layout-session, so a change to engine.src.engine.layout.layout-session can break engine.src.engine.layout.packagers, while a change to engine.src.engine.layout.packagers can't break engine.src.engine.layout.layout-session.
- Position
- Below the diagonal: engine.src.engine.layout.packagers uses a module listed above it, which is the healthy direction.
38→5 engine.src.engine.layout.packagers.script-document-packager uses engine.src.engine.layout.script-runtime-host✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers.script-document-packager uses a type in engine.src.engine.layout.script-runtime-host.
- The types involved
engine.src.engine.layout.packagers.script-document-packager.ScriptDocumentPackager→engine.src.engine.layout.script-runtime-host.ScriptRuntimeHost
- Direction
- engine.src.engine.layout.packagers.script-document-packager uses engine.src.engine.layout.script-runtime-host, so a change to engine.src.engine.layout.script-runtime-host can break engine.src.engine.layout.packagers.script-document-packager, while a change to engine.src.engine.layout.packagers.script-document-packager can't break engine.src.engine.layout.script-runtime-host.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.script-document-packager uses a module listed above it, which is the healthy direction.
38→6 engine.src.engine.layout.packagers.script-document-packager uses engine.src.engine.types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers.script-document-packager uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout.packagers.script-document-packager.ScriptDocumentPackager→engine.src.engine.types.Element
- Direction
- engine.src.engine.layout.packagers.script-document-packager uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout.packagers.script-document-packager, while a change to engine.src.engine.layout.packagers.script-document-packager can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.script-document-packager uses a module listed above it, which is the healthy direction.
38→21 engine.src.engine.layout.packagers.script-document-packager uses engine.src.engine.layout.packagers.packager-types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout.packagers.script-document-packager uses a type in engine.src.engine.layout.packagers.packager-types.
- The types involved
engine.src.engine.layout.packagers.script-document-packager.ScriptDocumentPackager→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.packagers.script-document-packager.ScriptDocumentPackager→engine.src.engine.layout.packagers.packager-types.PackagerUnit
- Direction
- engine.src.engine.layout.packagers.script-document-packager uses engine.src.engine.layout.packagers.packager-types, so a change to engine.src.engine.layout.packagers.packager-types can break engine.src.engine.layout.packagers.script-document-packager, while a change to engine.src.engine.layout.packagers.script-document-packager can't break engine.src.engine.layout.packagers.packager-types.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.script-document-packager uses a module listed above it, which is the healthy direction.
38→33 engine.src.engine.layout.packagers.script-document-packager uses engine.src.engine.layout.runtime.scripting.script-runtime-pass✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers.script-document-packager uses a type in engine.src.engine.layout.runtime.scripting.script-runtime-pass.
- The types involved
engine.src.engine.layout.packagers.script-document-packager.ScriptDocumentPackager→engine.src.engine.layout.runtime.scripting.script-runtime-pass.InsertPosition
- Direction
- engine.src.engine.layout.packagers.script-document-packager uses engine.src.engine.layout.runtime.scripting.script-runtime-pass, so a change to engine.src.engine.layout.runtime.scripting.script-runtime-pass can break engine.src.engine.layout.packagers.script-document-packager, while a change to engine.src.engine.layout.packagers.script-document-packager can't break engine.src.engine.layout.runtime.scripting.script-runtime-pass.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.script-document-packager uses a module listed above it, which is the healthy direction.
38→36 engine.src.engine.layout.packagers.script-document-packager uses engine.src.engine.layout.layout-session✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers.script-document-packager uses a type in engine.src.engine.layout.layout-session.
- The types involved
engine.src.engine.layout.packagers.script-document-packager.ScriptDocumentPackager→engine.src.engine.layout.layout-session.LayoutSession
- Direction
- engine.src.engine.layout.packagers.script-document-packager uses engine.src.engine.layout.layout-session, so a change to engine.src.engine.layout.layout-session can break engine.src.engine.layout.packagers.script-document-packager, while a change to engine.src.engine.layout.packagers.script-document-packager can't break engine.src.engine.layout.layout-session.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.script-document-packager uses a module listed above it, which is the healthy direction.
39→5 engine.src.engine.layout.packagers.scripted-flow-box-packager uses engine.src.engine.layout.script-runtime-host✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers.scripted-flow-box-packager uses a type in engine.src.engine.layout.script-runtime-host.
- The types involved
engine.src.engine.layout.packagers.scripted-flow-box-packager.ScriptedFlowBoxPackager→engine.src.engine.layout.script-runtime-host.ScriptRuntimeHost
- Direction
- engine.src.engine.layout.packagers.scripted-flow-box-packager uses engine.src.engine.layout.script-runtime-host, so a change to engine.src.engine.layout.script-runtime-host can break engine.src.engine.layout.packagers.scripted-flow-box-packager, while a change to engine.src.engine.layout.packagers.scripted-flow-box-packager can't break engine.src.engine.layout.script-runtime-host.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.scripted-flow-box-packager uses a module listed above it, which is the healthy direction.
39→6 engine.src.engine.layout.packagers.scripted-flow-box-packager uses engine.src.engine.types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers.scripted-flow-box-packager uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.layout.packagers.scripted-flow-box-packager.ScriptedFlowBoxPackager→engine.src.engine.types.Element
- Direction
- engine.src.engine.layout.packagers.scripted-flow-box-packager uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.layout.packagers.scripted-flow-box-packager, while a change to engine.src.engine.layout.packagers.scripted-flow-box-packager can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.scripted-flow-box-packager uses a module listed above it, which is the healthy direction.
39→18 engine.src.engine.layout.packagers.scripted-flow-box-packager uses engine.src.engine.layout.layout-core✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers.scripted-flow-box-packager uses a type in engine.src.engine.layout.layout-core.
- The types involved
engine.src.engine.layout.packagers.scripted-flow-box-packager.ScriptedFlowBoxPackager→engine.src.engine.layout.layout-core.LayoutProcessor
- Direction
- engine.src.engine.layout.packagers.scripted-flow-box-packager uses engine.src.engine.layout.layout-core, so a change to engine.src.engine.layout.layout-core can break engine.src.engine.layout.packagers.scripted-flow-box-packager, while a change to engine.src.engine.layout.packagers.scripted-flow-box-packager can't break engine.src.engine.layout.layout-core.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.scripted-flow-box-packager uses a module listed above it, which is the healthy direction.
39→21 engine.src.engine.layout.packagers.scripted-flow-box-packager uses engine.src.engine.layout.packagers.packager-types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.layout.packagers.scripted-flow-box-packager uses a type in engine.src.engine.layout.packagers.packager-types.
- The types involved
engine.src.engine.layout.packagers.scripted-flow-box-packager.ScriptedFlowBoxPackager→engine.src.engine.layout.packagers.packager-types.PackagerContextengine.src.engine.layout.packagers.scripted-flow-box-packager.ScriptedFlowBoxPackager→engine.src.engine.layout.packagers.packager-types.PackagerUnit
- Direction
- engine.src.engine.layout.packagers.scripted-flow-box-packager uses engine.src.engine.layout.packagers.packager-types, so a change to engine.src.engine.layout.packagers.packager-types can break engine.src.engine.layout.packagers.scripted-flow-box-packager, while a change to engine.src.engine.layout.packagers.scripted-flow-box-packager can't break engine.src.engine.layout.packagers.packager-types.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.scripted-flow-box-packager uses a module listed above it, which is the healthy direction.
39→23 engine.src.engine.layout.packagers.scripted-flow-box-packager uses engine.src.engine.layout.packagers.flow-box-packager✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers.scripted-flow-box-packager uses a type in engine.src.engine.layout.packagers.flow-box-packager.
- The types involved
engine.src.engine.layout.packagers.scripted-flow-box-packager.ScriptedFlowBoxPackager→engine.src.engine.layout.packagers.flow-box-packager.FlowBoxPackager
- Direction
- engine.src.engine.layout.packagers.scripted-flow-box-packager uses engine.src.engine.layout.packagers.flow-box-packager, so a change to engine.src.engine.layout.packagers.flow-box-packager can break engine.src.engine.layout.packagers.scripted-flow-box-packager, while a change to engine.src.engine.layout.packagers.scripted-flow-box-packager can't break engine.src.engine.layout.packagers.flow-box-packager.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.scripted-flow-box-packager uses a module listed above it, which is the healthy direction.
39→33 engine.src.engine.layout.packagers.scripted-flow-box-packager uses engine.src.engine.layout.runtime.scripting.script-runtime-pass✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers.scripted-flow-box-packager uses a type in engine.src.engine.layout.runtime.scripting.script-runtime-pass.
- The types involved
engine.src.engine.layout.packagers.scripted-flow-box-packager.ScriptedFlowBoxPackager→engine.src.engine.layout.runtime.scripting.script-runtime-pass.InsertPosition
- Direction
- engine.src.engine.layout.packagers.scripted-flow-box-packager uses engine.src.engine.layout.runtime.scripting.script-runtime-pass, so a change to engine.src.engine.layout.runtime.scripting.script-runtime-pass can break engine.src.engine.layout.packagers.scripted-flow-box-packager, while a change to engine.src.engine.layout.packagers.scripted-flow-box-packager can't break engine.src.engine.layout.runtime.scripting.script-runtime-pass.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.scripted-flow-box-packager uses a module listed above it, which is the healthy direction.
39→36 engine.src.engine.layout.packagers.scripted-flow-box-packager uses engine.src.engine.layout.layout-session✕
- Connections
- 1 pair of types, where a type in engine.src.engine.layout.packagers.scripted-flow-box-packager uses a type in engine.src.engine.layout.layout-session.
- The types involved
engine.src.engine.layout.packagers.scripted-flow-box-packager.ScriptedFlowBoxPackager→engine.src.engine.layout.layout-session.LayoutSession
- Direction
- engine.src.engine.layout.packagers.scripted-flow-box-packager uses engine.src.engine.layout.layout-session, so a change to engine.src.engine.layout.layout-session can break engine.src.engine.layout.packagers.scripted-flow-box-packager, while a change to engine.src.engine.layout.packagers.scripted-flow-box-packager can't break engine.src.engine.layout.layout-session.
- Position
- Below the diagonal: engine.src.engine.layout.packagers.scripted-flow-box-packager uses a module listed above it, which is the healthy direction.
40→4 engine.src.engine.runtime.simulation.runtime.march-runner uses engine.src.engine.layout.runtime.session.session-pagination-types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.runtime.simulation.runtime.march-runner uses a type in engine.src.engine.layout.runtime.session.session-pagination-types.
- The types involved
engine.src.engine.runtime.simulation.runtime.march-runner.SimulationMarchRunner→engine.src.engine.layout.runtime.session.session-pagination-types.PaginationLoopAction
- Direction
- engine.src.engine.runtime.simulation.runtime.march-runner uses engine.src.engine.layout.runtime.session.session-pagination-types, so a change to engine.src.engine.layout.runtime.session.session-pagination-types can break engine.src.engine.runtime.simulation.runtime.march-runner, while a change to engine.src.engine.runtime.simulation.runtime.march-runner can't break engine.src.engine.layout.runtime.session.session-pagination-types.
- Position
- Below the diagonal: engine.src.engine.runtime.simulation.runtime.march-runner uses a module listed above it, which is the healthy direction.
40→6 engine.src.engine.runtime.simulation.runtime.march-runner uses engine.src.engine.types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.runtime.simulation.runtime.march-runner uses a type in engine.src.engine.types.
- The types involved
engine.src.engine.runtime.simulation.runtime.march-runner.SimulationMarchRunner→engine.src.engine.types.SimulationStopReason
- Direction
- engine.src.engine.runtime.simulation.runtime.march-runner uses engine.src.engine.types, so a change to engine.src.engine.types can break engine.src.engine.runtime.simulation.runtime.march-runner, while a change to engine.src.engine.runtime.simulation.runtime.march-runner can't break engine.src.engine.types.
- Position
- Below the diagonal: engine.src.engine.runtime.simulation.runtime.march-runner uses a module listed above it, which is the healthy direction.
40→14 engine.src.engine.runtime.simulation.runtime.march-runner uses engine.src.engine.runtime.simulation.types✕
- Connections
- 2 pairs of types, where a type in engine.src.engine.runtime.simulation.runtime.march-runner uses a type in engine.src.engine.runtime.simulation.types.
- The types involved
engine.src.engine.runtime.simulation.runtime.march-runner.SimulationMarchRunner→engine.src.engine.runtime.simulation.types.SimulationRunnerengine.src.engine.runtime.simulation.runtime.march-runner.SimulationMarchRunner→engine.src.engine.runtime.simulation.types.SimulationUpdateSource
- Direction
- engine.src.engine.runtime.simulation.runtime.march-runner uses engine.src.engine.runtime.simulation.types, so a change to engine.src.engine.runtime.simulation.types can break engine.src.engine.runtime.simulation.runtime.march-runner, while a change to engine.src.engine.runtime.simulation.runtime.march-runner can't break engine.src.engine.runtime.simulation.types.
- Position
- Below the diagonal: engine.src.engine.runtime.simulation.runtime.march-runner uses a module listed above it, which is the healthy direction.
40→18 engine.src.engine.runtime.simulation.runtime.march-runner uses engine.src.engine.layout.layout-core✕
- Connections
- 1 pair of types, where a type in engine.src.engine.runtime.simulation.runtime.march-runner uses a type in engine.src.engine.layout.layout-core.
- The types involved
engine.src.engine.runtime.simulation.runtime.march-runner.SimulationMarchRunner→engine.src.engine.layout.layout-core.LayoutProcessor
- Direction
- engine.src.engine.runtime.simulation.runtime.march-runner uses engine.src.engine.layout.layout-core, so a change to engine.src.engine.layout.layout-core can break engine.src.engine.runtime.simulation.runtime.march-runner, while a change to engine.src.engine.runtime.simulation.runtime.march-runner can't break engine.src.engine.layout.layout-core.
- Position
- Below the diagonal: engine.src.engine.runtime.simulation.runtime.march-runner uses a module listed above it, which is the healthy direction.
40→21 engine.src.engine.runtime.simulation.runtime.march-runner uses engine.src.engine.layout.packagers.packager-types✕
- Connections
- 1 pair of types, where a type in engine.src.engine.runtime.simulation.runtime.march-runner uses a type in engine.src.engine.layout.packagers.packager-types.
- The types involved
engine.src.engine.runtime.simulation.runtime.march-runner.SimulationMarchRunner→engine.src.engine.layout.packagers.packager-types.PackagerContext
- Direction
- engine.src.engine.runtime.simulation.runtime.march-runner uses engine.src.engine.layout.packagers.packager-types, so a change to engine.src.engine.layout.packagers.packager-types can break engine.src.engine.runtime.simulation.runtime.march-runner, while a change to engine.src.engine.runtime.simulation.runtime.march-runner can't break engine.src.engine.layout.packagers.packager-types.
- Position
- Below the diagonal: engine.src.engine.runtime.simulation.runtime.march-runner uses a module listed above it, which is the healthy direction.
40→36 engine.src.engine.runtime.simulation.runtime.march-runner uses engine.src.engine.layout.layout-session✕
- Connections
- 1 pair of types, where a type in engine.src.engine.runtime.simulation.runtime.march-runner uses a type in engine.src.engine.layout.layout-session.
- The types involved
engine.src.engine.runtime.simulation.runtime.march-runner.SimulationMarchRunner→engine.src.engine.layout.layout-session.LayoutSession
- Direction
- engine.src.engine.runtime.simulation.runtime.march-runner uses engine.src.engine.layout.layout-session, so a change to engine.src.engine.layout.layout-session can break engine.src.engine.runtime.simulation.runtime.march-runner, while a change to engine.src.engine.runtime.simulation.runtime.march-runner can't break engine.src.engine.layout.layout-session.
- Position
- Below the diagonal: engine.src.engine.runtime.simulation.runtime.march-runner uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 8 | High / Critical |
| A05:2025 — Injection | 3 | High / Critical |
Roadmap
Top priorities: Resolve the 37 Floating npm dependency finding(s) in Dependency Hygiene; 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; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 37 Floating npm dependency finding(s) in Dependency Hygiene. | +6.0 pts | Medium | Dependency Hygiene |
| 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. | +3.3 pts | Medium | Text alternatives |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +3.3 pts | Medium | Keyboard semantics |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +3.3 pts | Medium | Visual & motion safety |
| Add a CI workflow that builds and runs the test suite on every push/PR. The repository declares its tests as `npm test` (`package.json`): run that. | +3.3 pts | Medium | CI/CD gates |
| 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. | +3.3 pts | Medium | Observability |
| Run what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing. | +3.3 pts | Medium | Security & performance tooling |
| Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail. | +2.2 pts | Medium | Outbound HTTP resilience |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| engine/src/engine/layout-engine.ts | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: LayoutEngine (LCOM4 4) |
| engine/src/engine/layout/layout-session.ts | 8.5 | Near-clean | Change Coupling: Change coupling: layout-session.ts ↔ execute-simulation-march.ts |
| engine/src/engine/layout/packagers/execute-simulation-march.ts | 8.5 | Near-clean | Change Coupling: Change coupling: execute-simulation-march.ts ↔ simulation-report.ts |
| engine/src/engine/layout/packagers/hosted-region-settlement.ts | 8.5 | Near-clean | Change Coupling: Change coupling: hosted-region-settlement.ts ↔ story-packager.ts |
| engine/src/engine/document.ts | 8.5 | Near-clean | Change Coupling: Change-coupling hub: document.ts → hosted-region-settlement.ts, world-plain-packager.ts, zone-packager.ts, spatial-field-reflow.ts |
| engine/src/engine/layout/packagers/world-plain-packager.ts | 8.5 | Near-clean | Change Coupling: Change coupling: world-plain-packager.ts ↔ zone-packager.ts |
| engine/src/engine/layout/packagers/dropcap-packager.ts | 8.5 | Near-clean | Change Coupling: Change coupling: dropcap-packager.ts ↔ story-packager.ts |
| transmuters/markdown-core/README.md | 9.5 | Near-clean | Documentation Quality: Documentation: no build, run or usage example |
| pressrun/src/index.ts | 9.5 | Near-clean | Comment Value: redundant comment |
| package.json | 9.5 | Near-clean | Project Cohesion: Projects may be oversized for their cohesion |
| engine/package.json | 9.5 | Near-clean | Project Cohesion: Projects may be oversized for their cohesion |
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 66 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 — 66 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, 340 of 396 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
- D1 Cyclomatic Complexity — 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. Most of this repository's production source (.js, .mjs) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — 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. Most of this repository's production source (.js, .mjs) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.ts) and its test script runs a plain-node harness, which the reliability runner re-ran on its own: `node scripts/test-packaged-vmprint-integration.mjs` in the repository root exited cleanly on 0 of 3 runs. The harness executes every test file inside its own process and starts none of them as a separate `node` process, so each run yields a single pass/fail for the whole suite — too coarse to tell which test is flaky. Not scored — this is a limit of what a one-process harness reports, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 339 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 2 hold 1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- 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. `contexts/pdf/src/index.ts`, `engine/src/engine/layout/layout-core.ts`, `engine/src/engine/layout/simulation-report.ts`, `engine/src/engine/runtime-types.ts`, `engine/src/engine/spatial-document.ts`, … (+1 more) 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.
- 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 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: "> @vmprint/cli@1.0.6 dev / > tsx --tsconfig tsconfig.dev.json src/index.ts / [vmprint] Failed: You must specify either --input <path> or --render-from-layout <path> / npm error Lifecycle script `dev` failed with error: / npm error code 1 / npm error path <repo>/cli / npm error workspace @vmprint/cli@1.0.6 / npm error location <repo>/cli / npm error command failed / npm error command sh -c tsx --tsconfig tsconfig.dev.json src/index.ts" 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 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: "> @vmprint/cli@1.0.6 dev / > tsx --tsconfig tsconfig.dev.json src/index.ts / [vmprint] Failed: You must specify either --input <path> or --render-from-layout <path> / npm error Lifecycle script `dev` failed with error: / npm error code 1 / npm error path <repo>/cli / npm error workspace @vmprint/cli@1.0.6 / npm error location <repo>/cli / npm error command failed / npm error command sh -c tsx --tsconfig tsconfig.dev.json src/index.ts" 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 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- 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. 246 further occurrence(s) are not listed individually; the score already reflects all 286.
- R2 Cyclomatic Complexity — 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. 271 further occurrence(s) are not listed individually; the score already reflects all 311.
- R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
- R7 Dead Code — 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. 22 further occurrence(s) are not listed individually; the score already reflects all 62.
- X10 Duplicated predicate — 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. 64 further occurrence(s) are not listed individually; the score already reflects all 104.
- 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
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages 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.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
D5 · Coupling
20 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 4 module(s) off the main sequence.
What to do
- Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
D6 · Cohesion (LCOM4)
1 of 82 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with layout-engine.ts. — One of this dimension's main actionable groups (1 warning-level).
D12 · Dependency Hygiene
7 outdated direct production npm dependency(ies) of 13 graded, 37 pinning defect(s), across 21 package.json (21 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
What to do
- Resolve the 37 Floating npm dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (37 warning-level).
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 114 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 114 package(s) this repository's committed lockfile installs for a consumer — its 13 production, optional and peer dependency(ies), across 21 product package.json manifest(s), and everything those install in turn. Its 103 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. Third-party code that ships WITHOUT a manifest entry was read too: 12 component(s) whose licence travels in the tree (vendored or copied-in directories, licence comments preserved in committed bundles, compiled wasm modules) and 0 bundled package(s) named only by a bundle's module path, graded on the registry; 0 use a banned licence. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 73321 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.
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 37 document(s) read across 21 unit(s).
D22 · Internal API Consistency
0 API inconsistencies among 48 exposed members measured against a convention their peers follow.
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (19 contexts). Contexts: canvas, cli, contracts, dev-cli, engine, local, markdown-core, mkd-academic, mkd-literature, mkd-manuscript, mkd-mkd, mkd-screenplay and 7 more.
D24 · Comment Value
1 of 428 judged comments only repeat the code they sit on (0.2 %). 29 comment(s) in another language or script were not judged.
D26 · Project Cohesion
2 of 21 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
18 % of calls cross a namespace and 3 % go through an interface, but 94 % 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)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
4 finding(s): 0 critical, 1 high, 3 medium, 0 low. semgrep hit a parse error in 20 file(s) — `contexts/pdf/src/index.ts` (line 275), `docs/examples/ast-to-canvas-webfonts/assets/vmprint-context-canvas.js`, `docs/examples/ast-to-canvas-webfonts/assets/vmprint-engine.js`, `docs/examples/ast-to-canvas-webfonts/assets/vmprint-fontkit.js`, `docs/examples/ast-to-canvas-webfonts/assets/vmprint-web-fonts.js`, … (+15 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D30 · Dependency Vulnerabilities
8 finding(s): 0 critical, 4 high, 3 medium, 1 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Low vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 165 of the 242 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: layout-session.ts↔execute-simulation-march.ts 74%; execute-simulation-march.ts↔simulation-report.ts 67%; hosted-region-settlement.ts↔story-packager.ts 64%
What to do
- Resolve the 5 Change coupling finding(s) in Change Coupling — start with layout-session.ts, execute-simulation-march.ts, hosted-region-settlement.ts. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with document.ts. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
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. (×2) — preview/playground/index.html:107, preview/src/index.ts:423
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 <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×2) — preview/playground/index.html:40, preview/playground/index.html:54
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — preview/playground/index.html:79
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
AC4 · Keyboard semantics
- The repo's own CSS styles .brand with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — preview/playground/index.html:32
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.btn-primary` sets color: white on background-color: #10b981 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — preview/playground/styles.css:368, docs/examples/preview/styles.css:368
- `#preview-footer` sets color: #6b7280 on background-color: #111827 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — preview/playground/styles.css:376, docs/examples/preview/styles.css:376
- `#markdown-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — preview/playground/styles.css:287, docs/examples/preview/styles.css:287
- `.scale-picker select:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/examples/ast-to-canvas-webfonts/styles.css:147
- `#font-progress-bar` moves (`transition: width 0.3s`) 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. (×2) — preview/playground/styles.css:386, docs/examples/preview/styles.css:386
- `#ast-drawer` moves (`transition: transform 0.3s cubic-bezier(0.4, 0, 0.2, 1)`) 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. (×2) — preview/playground/styles.css:392, docs/examples/preview/styles.css:392
- `.loader` moves (`animation: spin 0.8s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — preview/playground/styles.css:416, docs/examples/preview/styles.css:416
- `.button-link` moves (`transition: transform 0.16s ease, box-shadow 0.16s ease, background-color 0.16s ease, color 0.16s ease`) 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. — docs/assets/docs.css:241
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
- `Context` declares 30 required operations: `addPage`, `end`, `pipe`, `registerFont`, `font`, `fontSize`, `save`, `restore`, `translate`, `rotate`, `opacity`, `fillColor`, `strokeColor`, `lineWidth`, `dash`, `undash`, `moveTo`, `lineTo`, `bezierCurveTo`, `circle`, `rect`, `roundedRect`, `clip`, `fill`, `stroke`, `fillAndStroke`, `text`, `showShapedGlyphs`, `image`, `getSize`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — contracts/src/context.ts:18, engine/src/contracts/context.ts:12
- `OverlayContext` declares 21 required operations: `font`, `fontSize`, `translate`, `rotate`, `opacity`, `fillColor`, `strokeColor`, `lineWidth`, `dash`, `undash`, `moveTo`, `lineTo`, `bezierCurveTo`, `rect`, `roundedRect`, `fill`, `stroke`, `fillAndStroke`, `text`, `save`, `restore`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — contracts/src/overlay.ts:27, engine/src/contracts/overlay.ts:27
- `CollaboratorHost` declares 39 required operations: `recordProfile`, `recordKeepWithNextPrepare`, `publishActorSignal`, `getActorSignalSequence`, `publishArtifact`, `getPaginationLoopState`, `getKeepWithNextPlan`, `setKeepWithNextPlan`, `getSplitMarkerReserve`, `reserveCurrentPageSpace`, `reservePageSpace`, `excludePageSpace`, `ensureContinuationArtifacts`, `stageMarkersAfterSplit`, `stageActorsBeforeContinuation`, `getFinalizedPages`, `getPageFinalizationStates`, `getPageFinalizationState`, `getPageCaptures`, `getSimulationTick`, `getRegisteredActors`, `getPageReservations`, `getReservationPageIndices`, `getPageExclusions`, `getExclusionPageIndices`, `getSpatialConstraintPageIndices`, `getPageRegionSummaries`, `getFragmentTransitionSourceIds`, `getFragmentTransitionsBySource`, `getScriptRegions`, `findScriptRegionByName`, `getActorSignals`, `allocateLogicalPageNumber`, `resetLogicalPageNumbering`, `notifyActorSpawn`, `recordPageCapture`, `recordPageFinalization`, `resolveChunkOriginWorldY`, `createPageCaptureState`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — engine/src/engine/layout/runtime/session/session-runtime-types.ts:60
- `SimulationRunner` declares 18 required operations: `getCurrentTick`, `getCurrentPageIndex`, `getCurrentPageCount`, `getProgression`, `getCurrentUpdateSummary`, `getCurrentDiagnosticSnapshot`, `getCurrentPageCaptures`, `getSimulationStopReason`, `isFinished`, `getCurrentPages`, `runToCompletion`, `restoreSafeCheckpoint`, `advanceTick`, `continueUntil`, `continueUntilPage`, `continueUntilY`, `sendExternalMessage`, `hasExternalMessageAck`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — engine/src/engine/runtime/simulation/types.ts:97
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- The guard above `return 0x20;` also returns `0x20`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. (×2) — contexts/pdf/src/standard-font-encoding.ts:179, engine/src/font-management/standard-font-encoding.ts:184
- The guard above `return outcome;` also returns `outcome`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — engine/src/engine/layout/ai-runtime.ts:153
- Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — engine/src/engine/runtime/simulation/runtime/march-runner.ts:1165
What to do
- Remove the dead code that looks live: delete dead if(false) branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async functions, which promise work they never wait for.
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
- README.md links to `guides/`, but `guides` does not exist. 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. — README.md:75
- README.md links to `references/`, but `references` does not exist. 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. — README.md:76
- docs/README.md links to `./api/`, but `docs/api` does not exist. 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. — docs/README.md:11
- transmuters/markdown-core/README.md links to `../draft2final/`, but `transmuters/draft2final` does not exist. 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. — transmuters/markdown-core/README.md:24
- transmuters/markdown-core/README.md links to `../transmuters/mkd-mkd/`, but `transmuters/transmuters/mkd-mkd` does not exist. 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. — transmuters/markdown-core/README.md:25
What to do
- Reconcile the README with reality: README.md links to `guides/`, but `guides` does not exist; README.md links to `references/`, but `references` does not exist; docs/README.md links to `./api/`, but `docs/api` does not exist; transmuters/markdown-core/README.md links to `../draft2final/`, but `transmuters/draft2final` does not exist; transmuters/markdown-core/README.md links to `../transmuters/mkd-mkd/`, but `transmuters/transmuters/mkd-mkd` does not exist.
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR. The repository declares its tests as `npm test` (`package.json`): run that.
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 — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
- `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:37
What to do
- Run what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add 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.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — preview/playground/app.js:1054, preview/playground/app.ts:1088
What to do
- Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
PF3 · Async & latency hygiene
- `fsMod.existsSync` in `resolveLocalPath` 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. (×3) — font-managers/local/src/LocalFontManager.ts:108, font-managers/local/src/LocalFontManager.ts:118, font-managers/local/src/LocalFontManager.ts:147
- `fs.readFileSync` in `loadFontBuffer` 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. — font-managers/local/src/LocalFontManager.ts:155
- `fs.mkdirSync` in `loadFontBuffer` 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. — font-managers/local/src/LocalFontManager.ts:204
- `fs.writeFileSync` in `loadFontBuffer` 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. — font-managers/local/src/LocalFontManager.ts:205
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
- 25 duplicated blocks under the repository root have copies in at least two of the sibling directories cli, contexts, contracts, engine, font-managers, pressrun (+3 more sibling(s) not listed) — 16 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 25 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 25 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 25 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. — contexts/pdf/src/standard-font-data.ts:1
- 10 duplicated blocks under engine/src/engine/layout/ have copies in at least two of the sibling directories collaborators, packagers, runtime — 9 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 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — engine/src/engine/layout/collaborators/heading-telemetry-collaborator.ts:17
- 7 duplicated blocks under transmuters/ have copies in at least two of the sibling directories markdown-core, mkd-academic, mkd-literature, mkd-manuscript, mkd-mkd, mkd-screenplay (+1 more sibling(s) not listed) — 6 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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. — transmuters/mkd-manuscript/src/format.ts:1
- 6 of the duplicated blocks reported below have copies in at least two of the sibling directories geometry, layout, render, runtime under engine/src/engine/. 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. — engine/src/engine/layout/session-world-runtime.ts:159
- transmuters/mkd-manuscript/src/format.ts:1 · transmuters/mkd-zh-manuscript/src/format.ts:1 — these 2 files are line-for-line copies of one another — 418 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. — transmuters/mkd-manuscript/src/format.ts:1
- preview/playground/app.js:1015 · preview/playground/app.ts:1045 — the two spans are one implementation copied and then locally edited — 3074 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. — preview/playground/app.js:1015
- contexts/pdf/src/standard-font-data.ts:1 · engine/src/font-management/afm-tables.ts:1 — the two spans are one implementation copied and then locally edited — 1291 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. — contexts/pdf/src/standard-font-data.ts:1
- engine/src/engine/layout/packagers/script-document-packager.ts:68 · engine/src/engine/layout/packagers/scripted-flow-box-packager.ts:58 — the two spans are one implementation copied and then locally edited — 1725 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. — engine/src/engine/layout/packagers/script-document-packager.ts:68
- engine/src/engine/layout/packagers/script-document-packager.ts:539 · engine/src/engine/layout/packagers/scripted-flow-box-packager.ts:409 — the two spans are one implementation copied and then locally edited — 1444 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. — engine/src/engine/layout/packagers/script-document-packager.ts:539
- contexts/pdf/src/standard-font-encoding.ts:4 · engine/src/font-management/standard-font-encoding.ts:6 — these 2 files are line-for-line copies of one another — 170 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. — contexts/pdf/src/standard-font-encoding.ts:4
- contexts/dev-cli/src/index.ts:25 · transmuters/dev-cli/src/index.ts:38 — the two spans are one implementation copied and then locally edited — 702 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. — contexts/dev-cli/src/index.ts:25
- transmuters/mkd-manuscript/src/validator.ts:3 · transmuters/mkd-zh-manuscript/src/validator.ts:3 — the two spans are one implementation copied and then locally edited — 791 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. — transmuters/mkd-manuscript/src/validator.ts:3
- contracts/src/context.ts:7 · engine/src/contracts/context.ts:1 — these 2 files are line-for-line copies of one another — 79 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. — contracts/src/context.ts:7
- engine/src/font-management/sentinel.ts:1 · font-managers/standard/src/sentinel.ts:1 — these 2 files are line-for-line copies of one another — 77 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. — engine/src/font-management/sentinel.ts:1
- contexts/pdf-lite/src/index.ts:427 · contexts/pdf/src/index.ts:70 — the two spans are one implementation copied and then locally edited — 346 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. — contexts/pdf-lite/src/index.ts:427
- engine/src/engine/layout-engine.ts:2333 · engine/src/engine/layout-engine.ts:2546 — 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. — engine/src/engine/layout-engine.ts:2333
- engine/src/engine/layout/packagers/list-packager.ts:864 · engine/src/engine/layout/packagers/story-packager.ts:2385 — 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. — engine/src/engine/layout/packagers/list-packager.ts:864
- contracts/src/overlay.ts:1 · engine/src/contracts/overlay.ts:1 — these 2 files are line-for-line copies of one another — 50 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. — contracts/src/overlay.ts:1
- transmuters/mkd-manuscript/src/index.ts:280 · transmuters/mkd-zh-manuscript/src/index.ts:182 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — transmuters/mkd-manuscript/src/index.ts:280
- engine/src/engine/layout/transitions-runtime.ts:304 · engine/src/engine/layout/transitions-runtime.ts:539 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — engine/src/engine/layout/transitions-runtime.ts:304
- engine/src/engine/runtime/simulation/runtime/march-runner.ts:1030 · engine/src/engine/runtime/simulation/runtime/march-runner.ts:1073 — the two spans are one implementation copied and then locally edited — 242 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — engine/src/engine/runtime/simulation/runtime/march-runner.ts:1030
- contracts/src/text-delegate.ts:11 · engine/src/contracts/text-delegate.ts:13 — the 2 copies are spread across 2 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. — contracts/src/text-delegate.ts:11
- engine/src/engine/layout-engine.ts:339 · engine/src/engine/layout/packagers/list-packager.ts:451 — the two spans are one implementation copied and then locally edited — 428 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. — engine/src/engine/layout-engine.ts:339
- engine/src/engine/layout/collaborators/heading-telemetry-collaborator.ts:17 · engine/src/engine/layout/runtime/signals/heading-signal-publisher.ts:7 — the two spans are one implementation copied and then locally edited — 288 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. — engine/src/engine/layout/collaborators/heading-telemetry-collaborator.ts:17
- engine/src/engine/layout/text-wrap-core.ts:546 · engine/src/engine/layout/text-wrap-core.ts:624 — 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. — engine/src/engine/layout/text-wrap-core.ts:546
- font-managers/local/src/LocalFontManager.ts:45 · font-managers/web/src/WebFontManager.ts:112 — 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. — font-managers/local/src/LocalFontManager.ts:45
- engine/src/engine/layout/packagers/list-packager.ts:1813 · engine/src/engine/layout/packagers/list-packager.ts:1865 — 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. — engine/src/engine/layout/packagers/list-packager.ts:1813
- engine/src/engine/layout/physics-runtime.ts:444 · engine/src/engine/layout/transitions-runtime.ts:488 · engine/src/engine/layout/transitions-runtime.ts:642 — the 3 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. — engine/src/engine/layout/physics-runtime.ts:444
- engine/src/engine/layout/packagers/hosted-region-packager.ts:156 · engine/src/engine/layout/packagers/hosted-region-packager.ts:622 — 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. — engine/src/engine/layout/packagers/hosted-region-packager.ts:156
- engine/src/engine/layout/packagers/hosted-region-packager.ts:652 · engine/src/engine/layout/packagers/story-packager.ts:436 — 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. — engine/src/engine/layout/packagers/hosted-region-packager.ts:652
- engine/src/engine/layout/packagers/story-packager.ts:485 · engine/src/engine/layout/packagers/story-packager.ts:523 — 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. — engine/src/engine/layout/packagers/story-packager.ts:485
- contracts/src/font-manager.ts:1 · engine/src/contracts/font-manager.ts:1 — the 2 copies are spread across 2 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. — contracts/src/font-manager.ts:1
- engine/src/engine/layout-engine.ts:2228 · engine/src/engine/layout-engine.ts:2429 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — engine/src/engine/layout-engine.ts:2228
- engine/src/engine/layout-engine.ts:1547 · engine/src/engine/layout-engine.ts:2260 · engine/src/engine/layout-engine.ts:2465 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — engine/src/engine/layout-engine.ts:1547
- engine/src/engine/layout/packagers/hosted-region-settlement.ts:903 · engine/src/engine/layout/packagers/hosted-region-settlement.ts:1142 — 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. — engine/src/engine/layout/packagers/hosted-region-settlement.ts:903
- engine/src/engine/layout/packagers/list-packager.ts:1010 · engine/src/engine/layout/packagers/list-packager.ts:1602 — 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. — engine/src/engine/layout/packagers/list-packager.ts:1010
- engine/src/engine/layout/runtime-formatting.ts:402 · engine/src/engine/layout/runtime-formatting.ts:451 — 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. — engine/src/engine/layout/runtime-formatting.ts:402
- engine/src/engine/layout/session-world-runtime.ts:159 · engine/src/engine/runtime/simulation/runtime/march-runner.ts:185 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — engine/src/engine/layout/session-world-runtime.ts:159
- engine/src/engine/layout/collision-runtime.ts:107 · engine/src/engine/layout/placement-session-runtime.ts:64 — the two spans are one implementation copied and then locally edited — 79 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. — engine/src/engine/layout/collision-runtime.ts:107
- engine/src/engine/layout/packagers/contained-flow-packager.ts:93 · engine/src/engine/layout/packagers/flow-box-packager.ts:186 — 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. — engine/src/engine/layout/packagers/contained-flow-packager.ts:93
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
- engine/scripts/text-measure-server.ts:6 imports engine/tests/harness/engine-harness.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. — engine/scripts/text-measure-server.ts:6
What to do
- Fix the listed violations: move the shared test helper into a source directory production code may depend on (1 row).
R2 · Cyclomatic Complexity
- pourColumns has cyclomatic complexity 97 and cognitive complexity 245; 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. — engine/src/engine/layout/packagers/story-packager.ts:1257
- applyRuntimeFormattingBatchIntent has cyclomatic complexity 73 and cognitive complexity 143; 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. — engine/src/engine/layout-engine.ts:1401
- (anonymous) has cyclomatic complexity 73 and cognitive complexity 81; 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. — engine/src/engine/render/rich-line-draw.ts:56
- run has cyclomatic complexity 70 and cognitive complexity 120; 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. — engine/tests/engine-regression.spec.ts:3015
- reflowTextElementAgainstSpatialField has cyclomatic complexity 70 and cognitive complexity 67; 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. — engine/src/engine/layout/spatial-field-reflow.ts:67
- (anonymous) has cyclomatic complexity 68 and cognitive complexity 75; 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. — engine/src/engine/render/box-paint.ts:175
- materialize has cyclomatic complexity 66 and cognitive complexity 73; 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. — engine/src/engine/layout/packagers/dropcap-packager.ts:361
- buildRichWrapTokens has cyclomatic complexity 65 and cognitive complexity 141; 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. — engine/src/engine/layout/text-wrap-core.ts:127
- trySplitSpatialItemAtBoundary has cyclomatic complexity 65 and cognitive complexity 101; 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. — engine/src/engine/layout/packagers/list-packager.ts:1552
- positionSpatialGridFlowBoxes has cyclomatic complexity 63 and cognitive complexity 92; 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. — engine/src/engine/layout/layout-table.ts:882
- measureInlineObject has cyclomatic complexity 60 and cognitive complexity 49; 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. — engine/src/engine/layout/text-processor.ts:213
- validateLayout has cyclomatic complexity 59 and cognitive complexity 83; 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. — engine/src/engine/document.ts:267
- materializeSpatialGridFlowBox has cyclomatic complexity 55 and cognitive complexity 88; 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. — engine/src/engine/layout/layout-table.ts:403
- validateStyleObject has cyclomatic complexity 54 and cognitive complexity 53; 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. — engine/src/engine/document.ts:469
- pourAll has cyclomatic complexity 53 and cognitive complexity 124; 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. — engine/src/engine/layout/packagers/story-packager.ts:582
- splitResult has cyclomatic complexity 51 and cognitive complexity 140; 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. — engine/src/engine/layout/packagers/story-packager.ts:1968
- applyRuntimeFormattingIntentInternal has cyclomatic complexity 50 and cognitive complexity 50; 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. — engine/src/engine/layout-engine.ts:2406
- wrapTokenStream has cyclomatic complexity 48 and cognitive complexity 159; 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. — engine/src/engine/layout/text-wrap-core.ts:357
- validateElementNode has cyclomatic complexity 48 and cognitive complexity 64; 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. — engine/src/engine/document.ts:1022
- (anonymous) has cyclomatic complexity 48 and cognitive complexity 40; 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. — preview/src/index.ts:882
- runHostedRegionSessionBounded has cyclomatic complexity 47 and cognitive complexity 102; 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. — engine/src/engine/layout/packagers/hosted-region-settlement.ts:943
- applyRuntimeFormattingRestoreIntentInternal has cyclomatic complexity 44 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 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. — engine/src/engine/layout-engine.ts:2210
- inlineToElements has cyclomatic complexity 41 and cognitive complexity 71; 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. — transmuters/markdown-core/src/inline.ts:54
- materializeTableCell has cyclomatic complexity 41 and cognitive complexity 48; 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. — engine/src/engine/layout/layout-table.ts:189
- flush has cyclomatic complexity 40 and cognitive complexity 77; 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. — transmuters/mkd-screenplay/src/format.ts:190
- flush has cyclomatic complexity 40 and cognitive complexity 65; 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. (×2) — transmuters/mkd-manuscript/src/format.ts:141, transmuters/mkd-zh-manuscript/src/format.ts:149
- normalizeElementNode has cyclomatic complexity 39 and cognitive complexity 46; 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. — engine/src/engine/document.ts:1277
- updateCommittedState has cyclomatic complexity 38 and cognitive complexity 46; 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. — engine/src/engine/layout/packagers/script-document-packager.ts:1001
- normalizeElementStyle has cyclomatic complexity 38 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — engine/src/engine/layout/layout-core.ts:389
- (anonymous) has cyclomatic complexity 37 and cognitive complexity 51; 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. — engine/src/engine/layout/spatial-field-reflow.ts:171
- parseSvgPathSubpaths has cyclomatic complexity 35 and cognitive complexity 67; 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. — engine/src/engine/geometry/svg-path.ts:18
- (anonymous) has cyclomatic complexity 35 and cognitive complexity 55; 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. — engine/src/engine/render/direction.ts:100
- hitTestPoint has cyclomatic complexity 35 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 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. — engine/src/engine/layout-engine.ts:443
- createDynamicPackager has cyclomatic complexity 35 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — engine/tests/support/reactive-proof-packagers.ts:932
- tryPrepareItemsAgainstSpatialField has cyclomatic complexity 34 and cognitive complexity 52; 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. — engine/src/engine/layout/packagers/list-packager.ts:962
- splitSpatialGridFlowBox has cyclomatic complexity 33 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 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. — engine/src/engine/layout/layout-table.ts:645
- hitTestRichTextBox has cyclomatic complexity 33 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — engine/src/engine/layout/packagers/text-hit-testing.ts:178
- run has cyclomatic complexity 32 and cognitive complexity 34; 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. — engine/tests/scripting-performance.ts:49
- resolveContainedFieldFrame has cyclomatic complexity 32 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — engine/src/engine/layout/packagers/contained-field-geometry.ts:16
R3 · Large Files
- engine/src/font-management/afm-tables.ts has 8162 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/font-management/afm-tables.ts:1
- contexts/pdf/src/standard-font-data.ts has 4147 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — contexts/pdf/src/standard-font-data.ts:1
- engine/src/engine/layout-engine.ts has 2518 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout-engine.ts:1
- engine/src/engine/layout/packagers/story-packager.ts has 2516 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/packagers/story-packager.ts:1
- engine/src/engine/layout/packagers/list-packager.ts has 1801 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/packagers/list-packager.ts:1
- engine/src/engine/layout/layout-session.ts has 1754 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/layout-session.ts:1
- engine/src/engine/document.ts has 1646 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/document.ts:1
- engine/src/engine/layout/layout-core.ts has 1518 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/layout-core.ts:1
- engine/src/engine/runtime/simulation/runtime/march-runner.ts has 1190 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/runtime/simulation/runtime/march-runner.ts:1
- engine/src/engine/layout/packagers/hosted-region-settlement.ts has 1166 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/packagers/hosted-region-settlement.ts:1
- engine/src/engine/interaction-model.ts has 1094 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/interaction-model.ts:1
- engine/src/engine/layout/packagers/script-document-packager.ts has 1091 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/packagers/script-document-packager.ts:1
- preview/src/index.ts has 1045 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — preview/src/index.ts:1
- engine/src/engine/layout/layout-table.ts has 1037 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/layout-table.ts:1
- engine/src/engine/layout/packagers/scripted-flow-box-packager.ts has 1036 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/packagers/scripted-flow-box-packager.ts:1
- engine/src/engine/layout/text-processor.ts has 861 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/text-processor.ts:1
- engine/src/engine/layout/transitions-runtime.ts has 783 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/transitions-runtime.ts:1
- contexts/pdf-lite/src/index.ts has 765 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — contexts/pdf-lite/src/index.ts:1
- engine/src/engine/layout/packagers/dropcap-packager.ts has 728 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/packagers/dropcap-packager.ts:1
- engine/src/engine/layout/packagers/hosted-region-packager.ts has 706 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/packagers/hosted-region-packager.ts:1
- engine/src/engine/layout/collider-field.ts has 645 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/collider-field.ts:1
- contexts/canvas/src/index.ts has 641 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — contexts/canvas/src/index.ts:1
- engine/src/engine/layout/spatial-field-reflow.ts has 635 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/spatial-field-reflow.ts:1
- engine/src/engine/layout/actor-communication-runtime.ts has 631 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/actor-communication-runtime.ts:1
- engine/src/engine/layout/text-wrap-core.ts has 616 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/text-wrap-core.ts:1
- engine/src/engine/spatial-document.ts has 594 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/spatial-document.ts:1
- engine/src/engine/layout/runtime/scripting/script-runtime-pass.ts has 587 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/runtime/scripting/script-runtime-pass.ts:1
- transmuters/mkd-manuscript/src/format.ts has 584 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — transmuters/mkd-manuscript/src/format.ts:1
- transmuters/mkd-zh-manuscript/src/format.ts has 581 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — transmuters/mkd-zh-manuscript/src/format.ts:1
- engine/src/engine/layout/session-world-runtime.ts has 559 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/session-world-runtime.ts:1
- engine/src/engine/layout/runtime/page-finalization/page-region-finalization.ts has 526 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/runtime/page-finalization/page-region-finalization.ts:1
- documents/assets/specimen-blueprint.overlay.mjs has 507 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — documents/assets/specimen-blueprint.overlay.mjs:1
- engine/src/engine/context-renderer.ts has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/context-renderer.ts:1
- engine/src/engine/layout/physics-runtime.ts has 496 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/physics-runtime.ts:1
- engine/src/engine/render/box-paint.ts has 469 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/render/box-paint.ts:1
- engine/src/engine/layout/runtime-formatting.ts has 432 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — engine/src/engine/layout/runtime-formatting.ts:1
- engine/src/engine/layout/packagers/packager-types.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. — engine/src/engine/layout/packagers/packager-types.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. (×40) — contexts/pdf/src/standard-font-data.ts:1, preview/playground/app.ts:1, preview/playground/app.js:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
- test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
- `contexts/dev-cli` is TypeScript, but a type error in it cannot fail anything this repository runs: its `build` script (`esbuild src/index.ts --bundle --packages=external --platform=node --target=no…`) 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. — contexts/dev-cli/package.json:11
- `transmuters/dev-cli` is TypeScript, but a type error in it cannot fail anything this repository runs: its `build` script (`esbuild src/index.ts --bundle --packages=external --platform=node --target=no…`) 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. — transmuters/dev-cli/package.json:11
- `transmuters/markdown-core` is TypeScript, but a type error in it cannot fail anything this repository runs: its `build:js` script (`esbuild src/index.ts --bundle --platform=node --target=node18 --external:yaml…`) 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. — transmuters/markdown-core/package.json:23
- `transmuters/mkd-academic` is TypeScript, but a type error in it cannot fail anything this repository runs: its `build:js` script (`esbuild src/index.ts --bundle --platform=node --target=node18 --external:@vmp…`) 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. — transmuters/mkd-academic/package.json:23
- `transmuters/mkd-literature` is TypeScript, but a type error in it cannot fail anything this repository runs: its `build:js` script (`esbuild src/index.ts --bundle --platform=node --target=node18 --external:@vmp…`) 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. — transmuters/mkd-literature/package.json:23
- `transmuters/mkd-manuscript` is TypeScript, but a type error in it cannot fail anything this repository runs: its `build:js` script (`esbuild src/index.ts --bundle --platform=node --target=node18 --external:@vmp…`) 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. — transmuters/mkd-manuscript/package.json:23
- `transmuters/mkd-mkd` is TypeScript, but a type error in it cannot fail anything this repository runs: its `build:js` script (`esbuild src/index.ts --bundle --platform=node --target=node18 --external:@vmp…`) 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. — transmuters/mkd-mkd/package.json:23
- `transmuters/mkd-screenplay` is TypeScript, but a type error in it cannot fail anything this repository runs: its `build:js` script (`esbuild src/index.ts --bundle --platform=node --target=node18 --external:@vmp…`) 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. — transmuters/mkd-screenplay/package.json:23
- `transmuters/mkd-zh-manuscript` is TypeScript, but a type error in it cannot fail anything this repository runs: its `build:js` script (`esbuild src/index.ts --bundle --platform=node --target=node18 --external:@vmp…`) 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. — transmuters/mkd-zh-manuscript/package.json:23
What to do
- Add eslint as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 63 application, 16 tooling and 53 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (63 application, 16 tooling, 53 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 (×9) — preview/playground/app.ts, preview/playground/app.js, engine/src/font-management/generate-afm-tables.mjs, …
- Nothing imports this binding — it is safe to review for removal. (×23) — contexts/pdf/src/standard-font-metadata.ts:2, contexts/pdf/src/standard-font-metadata.ts:3, contexts/pdf/src/standard-font-metadata.ts:4, …
- Nothing ultimately consumes this binding: its only referrer is the re-export in engine/src/font-management/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 engine/src/font-management/index.ts in the same commit, or the barrel will import a name that no longer exists. (×6) — engine/src/font-management/ops.ts:22, engine/src/font-management/ops.ts:24, engine/src/font-management/ops.ts:27, …
- This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments. — contexts/canvas/src/index.ts:169
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
- Declared in engine/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) — engine/package.json:85, engine/package.json:87, engine/package.json:88, …
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- engine/src/engine/layout/packagers/packager-types.ts → engine/src/engine/layout/layout-core.ts → engine/src/engine/layout/collaborators/transform-capability-artifact-collaborator.ts → engine/src/engine/layout/packagers/packager-types.ts (one verified cycle inside a mutually-dependent group of 37 files) — engine/src/engine/layout/packagers/packager-types.ts:3
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- `server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) (×2) — engine/scripts/text-measure-server.ts:149, preview/scripts/playground-server.cjs:50
What to do
- Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `deepMerge` is exported and takes `target: Record<string, unknown>` from its caller, and it calls itself at line 38 (`deepMerge`) with a piece of `target` — and nowhere in `deepMerge` 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 `deepMerge` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — transmuters/markdown-core/src/theme.ts:38
- `notifyActorSpawn` is exported and takes `actor: PackagerUnit` from its caller, and it calls itself at line 617 (`this.notifyActorSpawn`) with a piece of `actor` — and nowhere in `notifyActorSpawn` 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 `notifyActorSpawn` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — engine/src/engine/layout/layout-session.ts:617
- `notifyActorDespawn` is exported and takes `actor: PackagerUnit` from its caller, and it calls itself at line 624 (`this.notifyActorDespawn`) with a piece of `actor` — and nowhere in `notifyActorDespawn` 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 `notifyActorDespawn` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — engine/src/engine/layout/layout-session.ts:624
- `getElementText` is exported and takes `element: Element` from its caller, and it calls itself at line 100 (`getElementText`) with a piece of `element` — and nowhere in `getElementText` 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 `getElementText` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — engine/src/engine/layout/rich-text-extractor.ts:100
- `getNodeText` is exported and takes `node: any` from its caller, and it calls itself at line 136 (`getNodeText`) with a piece of `node` — and nowhere in `getNodeText` 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 `getNodeText` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — engine/src/engine/layout/rich-text-extractor.ts:136
- `getRichSegments` is exported, takes a document from its caller (line 141) and hands it to `getRichSegmentsAtOffset`, which calls itself at line 243 (`getRichSegmentsAtOffset`) with a piece of `element` — and nowhere in `getRichSegmentsAtOffset` 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 `getRichSegmentsAtOffset` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — engine/src/engine/layout/rich-text-extractor.ts:243
- `applyRuntimeRangeFormattingPatch` is exported, takes a document from its caller (line 266) and hands it to `runtimeInlinePartLength`, which calls itself at line 142 (`runtimeInlinePartLength`) with a piece of `part` — and nowhere in `runtimeInlinePartLength` 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 `runtimeInlinePartLength` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — engine/src/engine/layout/runtime-formatting.ts:142
- `getStyleSignature` is exported, takes a document from its caller (line 26) and hands it to `serializeStyleValue`, which calls itself at line 18 (`this.serializeStyleValue`) with a piece of `value` (and at line 23) — and nowhere in `serializeStyleValue` 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 `serializeStyleValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — engine/src/engine/layout/text-wrap-utils.ts:18
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.
X2 · Cancellation propagation
- Only 0/4 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `fetchResolvedImage` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — preview/playground/app.ts:1086, preview/playground/app.js:1052
- `syncRegistryFromCDN` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — font-managers/local/src/LocalFontManager.ts:28
- `loadFontBuffer` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — font-managers/local/src/LocalFontManager.ts:84
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X24 · Document value interpolated into markup unescaped
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. (×6) — transmuters/markdown-core/src/theme.ts:53, font-managers/web/src/WebFontManager.ts:363, engine/src/font-management/generate-afm-tables.mjs:393, …
- `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — font-managers/local/src/LocalFontManager.ts:35
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
- ~1.0 `!` null assertions per 1k TypeScript source lines — 76 assertion(s) across the 77178 source line(s) of the 234 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: engine/src/engine/layout/spatial-field-reflow.ts (14), engine/src/engine/geometry/svg-path.ts (10), engine/src/engine/layout/packagers/list-packager.ts (9). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 44.1 | Weak — gated by R10, R2, R3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 80.1 | Strong | Solid. |
| Maturity | 58.2 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 26.2 | Weak — gated by P1, P2, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 82.5 | Strong | Strongest area. |
| Accessibility | 30.4 | Weak — gated by AC1, AC4, 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 — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 40 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 — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 59 check(s) not relevant to this codebase
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's 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 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: "> @vmprint/cli@1.0.6 dev / > tsx --tsconfig tsconfig.dev.json src/index.ts / [vmprint] Failed: You must specify either --input <path> or --render-from-layout <path> / npm error Lifecycle script `dev` failed with error: / npm error code 1 / npm error path <repo>/cli / npm error workspace @vmprint/cli@1.0.6 / npm error location <repo>/cli / npm error command failed / npm error command sh -c tsx --tsconfig tsconfig.dev.json src/index.ts" 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.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .js, .mjs exposed no member bodies
- D10 Test Quality — ~16434 lines of test source are present (.ts) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not scored — the plain-node test harness runs every file in one process
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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.
- D2 Cognitive Complexity — cognitive complexity not measured — .js, .mjs exposed no member bodies
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
- D25 ADR Conformance — no ADRs to check
- D3 God Classes — Most of this repository's production source (.js, .mjs) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
- 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) — 6 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D4 Code Duplication — This repository's production source (.js, .mjs, .ts) 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 its own test command under node's V8 coverage suite in the repository root ran and not one test passed ([packaged-integration] FAIL: Error: Missing required build artifact: engine/dist/index.js), so the coverage report describes 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 none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — no CI workflow found
- 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 10 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <label> that labels no control preview/playground/index.html:40
- <label> that labels no control preview/playground/index.html:54
- <textarea> without a programmatic label preview/playground/index.html:79
- Clickable element isn't keyboard-operable preview/playground/index.html:32
- REDACTED
- Import cycle (3 files) engine/src/engine/layout/packagers/packager-types.ts:3
Serious — 284 finding(s)
- No test reaches this file contexts/pdf/src/standard-font-data.ts:1
- No test reaches this file preview/playground/app.ts:1
- No test reaches this file preview/playground/app.js:1
- No test reaches this file preview/src/index.ts:1
- No test reaches this file contexts/canvas/src/index.ts:1
- No test reaches this file transmuters/mkd-manuscript/src/format.ts:1
- No test reaches this file transmuters/mkd-zh-manuscript/src/format.ts:1
- No test reaches this file documents/assets/specimen-blueprint.overlay.mjs:1
- No test reaches this file transmuters/mkd-academic/src/index.ts:1
- No test reaches this file contexts/pdf/src/index.ts:1
- No test reaches this file engine/src/font-management/generate-afm-tables.mjs:1
- No test reaches this file REDACTED:1
- No test reaches this file font-managers/web/src/WebFontManager.ts:1
- No test reaches this file transmuters/mkd-literature/src/index.ts:1
- No test reaches this file transmuters/mkd-manuscript/src/index.ts:1
- No test reaches this file transmuters/mkd-screenplay/src/format.ts:1
- No test reaches this file transmuters/dev-cli/src/index.ts:1
- No test reaches this file transmuters/mkd-screenplay/src/index.ts:1
- No test reaches this file transmuters/markdown-core/src/semantic.ts:1
- No test reaches this file transmuters/markdown-core/src/inline.ts:1
- No test reaches this file cli/src/index.ts:1
- No test reaches this file engine/tools/image-to-assembly.ts:1
- No test reaches this file transmuters/mkd-zh-manuscript/src/index.ts:1
- No test reaches this file transmuters/markdown-core/src/context.ts:1
- No test reaches this file contexts/pdf/src/standard-font-encoding.ts:1
- Floating npm dependency: @vmprint/context-canvas
- Floating npm dependency: @vmprint/context-canvas
- Floating npm dependency: @vmprint/context-pdf
- Floating npm dependency: @vmprint/context-pdf
- Floating npm dependency: @vmprint/context-pdf
- Floating npm dependency: @vmprint/context-pdf
- Floating npm dependency: @vmprint/context-pdf-lite
- Floating npm dependency: @vmprint/context-pdf-lite
- Floating npm dependency: @vmprint/contracts
- Floating npm dependency: @vmprint/contracts
- Floating npm dependency: @vmprint/contracts
- Floating npm dependency: @vmprint/contracts
- Floating npm dependency: @vmprint/contracts
- Floating npm dependency: @vmprint/contracts
- Floating npm dependency: @vmprint/contracts
- Floating npm dependency: @vmprint/contracts
- Floating npm dependency: @vmprint/contracts
- Floating npm dependency: @vmprint/contracts
- Floating npm dependency: @vmprint/contracts
- Floating npm dependency: @vmprint/contracts
- Floating npm dependency: @vmprint/contracts
- Floating npm dependency: @vmprint/contracts
- Floating npm dependency: @vmprint/engine
- Floating npm dependency: @vmprint/engine
- Floating npm dependency: @vmprint/engine
- Type errors in this package cannot fail any build or CI step contexts/dev-cli/package.json:11
- Type errors in this package cannot fail any build or CI step transmuters/dev-cli/package.json:11
- Type errors in this package cannot fail any build or CI step transmuters/markdown-core/package.json:23
- Type errors in this package cannot fail any build or CI step transmuters/mkd-academic/package.json:23
- Type errors in this package cannot fail any build or CI step transmuters/mkd-literature/package.json:23
- Type errors in this package cannot fail any build or CI step transmuters/mkd-manuscript/package.json:23
- Type errors in this package cannot fail any build or CI step transmuters/mkd-mkd/package.json:23
- Type errors in this package cannot fail any build or CI step transmuters/mkd-screenplay/package.json:23
- Type errors in this package cannot fail any build or CI step transmuters/mkd-zh-manuscript/package.json:23
- Recursive walk over a caller-supplied document has no depth cap transmuters/markdown-core/src/theme.ts:38
- Recursive walk over a caller-supplied document has no depth cap engine/src/engine/layout/layout-session.ts:617
- Recursive walk over a caller-supplied document has no depth cap engine/src/engine/layout/layout-session.ts:624
- Recursive walk over a caller-supplied document has no depth cap engine/src/engine/layout/rich-text-extractor.ts:100
- Recursive walk over a caller-supplied document has no depth cap engine/src/engine/layout/rich-text-extractor.ts:136
- Recursive walk over a caller-supplied document has no depth cap engine/src/engine/layout/rich-text-extractor.ts:243
- Recursive walk over a caller-supplied document has no depth cap engine/src/engine/layout/runtime-formatting.ts:142
- Recursive walk over a caller-supplied document has no depth cap engine/src/engine/layout/text-wrap-utils.ts:18
- Animation without a prefers-reduced-motion guard preview/playground/styles.css:386
- Animation without a prefers-reduced-motion guard preview/playground/styles.css:392
- Animation without a prefers-reduced-motion guard preview/playground/styles.css:416
- Animation without a prefers-reduced-motion guard docs/examples/preview/styles.css:386
- Animation without a prefers-reduced-motion guard docs/examples/preview/styles.css:392
- Animation without a prefers-reduced-motion guard docs/examples/preview/styles.css:416
- Animation without a prefers-reduced-motion guard docs/assets/docs.css:241
- Sync-over-async blocking font-managers/local/src/LocalFontManager.ts:108
- Sync-over-async blocking font-managers/local/src/LocalFontManager.ts:118
- Sync-over-async blocking font-managers/local/src/LocalFontManager.ts:147
- Sync-over-async blocking font-managers/local/src/LocalFontManager.ts:155
- Sync-over-async blocking font-managers/local/src/LocalFontManager.ts:204
- Sync-over-async blocking font-managers/local/src/LocalFontManager.ts:205
- Swallowed exception (empty catch) transmuters/markdown-core/src/theme.ts:53
- Swallowed exception (empty catch) font-managers/web/src/WebFontManager.ts:363
- Swallowed exception (empty catch) engine/src/font-management/generate-afm-tables.mjs:393
- Swallowed exception (empty catch) engine/src/engine/render/font-registration.ts:114
- Swallowed exception (empty catch) contexts/pdf-lite/src/index.ts:838
- Swallowed exception (empty catch) contexts/canvas/src/index.ts:661
- Change coupling: layout-session.ts ↔ execute-simulation-march.ts engine/src/engine/layout/layout-session.ts:1
- Change coupling: execute-simulation-march.ts ↔ simulation-report.ts engine/src/engine/layout/packagers/execute-simulation-march.ts:1
- Change coupling: hosted-region-settlement.ts ↔ story-packager.ts engine/src/engine/layout/packagers/hosted-region-settlement.ts:1
- Change coupling: world-plain-packager.ts ↔ zone-packager.ts engine/src/engine/layout/packagers/world-plain-packager.ts:1
- Change coupling: dropcap-packager.ts ↔ story-packager.ts engine/src/engine/layout/packagers/dropcap-packager.ts:1
- Off the main sequence: @vmprint/engine
- Off the main sequence: @vmprint/markdown-core
- Off the main sequence: @vmprint/local-fonts
- Off the main sequence: @vmprint/context-pdf
- Duplicated block (23 lines × 2 locations) engine/src/engine/layout/packagers/hosted-region-settlement.ts:903
- Duplicated block (23 lines × 2 locations) engine/src/engine/layout/packagers/list-packager.ts:1010
- Duplicated block (23 lines × 2 locations) engine/src/engine/layout/runtime-formatting.ts:402
- Duplicated block (23 lines × 2 locations) engine/src/engine/layout/session-world-runtime.ts:159
- Async function without AbortSignal: fetchResolvedImage preview/playground/app.ts:1086
- Async function without AbortSignal: fetchResolvedImage preview/playground/app.js:1052
- Async function without AbortSignal: syncRegistryFromCDN font-managers/local/src/LocalFontManager.ts:28
- Async function without AbortSignal: loadFontBuffer font-managers/local/src/LocalFontManager.ts:84
- Focus outline removed in CSS without a :focus replacement preview/playground/styles.css:287
- Focus outline removed in CSS without a :focus replacement docs/examples/preview/styles.css:287
- Focus outline removed in CSS without a :focus replacement docs/examples/ast-to-canvas-webfonts/styles.css:147
- REDACTED
- REDACTED
- REDACTED
- Guard cannot change the result — returns what the code already falls through to contexts/pdf/src/standard-font-encoding.ts:179
- Guard cannot change the result — returns what the code already falls through to engine/src/engine/layout/ai-runtime.ts:153
- Guard cannot change the result — returns what the code already falls through to engine/src/font-management/standard-font-encoding.ts:184
- Duplicated block (26 lines × 2 locations) engine/src/engine/layout/packagers/hosted-region-packager.ts:156
- Duplicated block (26 lines × 2 locations) engine/src/engine/layout/packagers/hosted-region-packager.ts:652
- Duplicated block (26 lines × 2 locations) engine/src/engine/layout/packagers/story-packager.ts:485
- <canvas> without a text alternative preview/playground/index.html:107
- <canvas> without a text alternative preview/src/index.ts:423
- Low contrast colour pair in CSS (2.5:1) preview/playground/styles.css:368
- Low contrast colour pair in CSS (2.5:1) docs/examples/preview/styles.css:368
- Low contrast colour pair in CSS (3.7:1) preview/playground/styles.css:376
- Low contrast colour pair in CSS (3.7:1) docs/examples/preview/styles.css:376
- REDACTED
- REDACTED
- Outbound HTTP without resilience preview/playground/app.js:1054
- Outbound HTTP without resilience preview/playground/app.ts:1088
- Complex function flush (cyclomatic 40, cognitive 65) transmuters/mkd-manuscript/src/format.ts:141
- Complex function flush (cyclomatic 40, cognitive 65) transmuters/mkd-zh-manuscript/src/format.ts:149
- Dead file (~1 LoC) engine/src/engine/layout/packagers/table-packager.ts
- Dead file (~1 LoC) engine/src/engine/layout/text-delegate-errors.ts
- Change-coupling hub: document.ts → hosted-region-settlement.ts, world-plain-packager.ts, zone-packager.ts, spatial-field-reflow.ts engine/src/engine/document.ts
- Low cohesion: LayoutEngine (LCOM4 4) engine/src/engine/layout-engine.ts:987
- Coverage not measured — JavaScript/TypeScript suite
- Both branches are identical — the condition decides nothing engine/src/engine/runtime/simulation/runtime/march-runner.ts:1165
- No CI pipeline
- No structured logging
- Duplication concentrated across 9 sibling directories (25 clone groups) contexts/pdf/src/standard-font-data.ts:1
- Duplication concentrated across 3 sibling directories (10 clone groups) engine/src/engine/layout/collaborators/heading-telemetry-collaborator.ts:17
- Duplication concentrated across 7 sibling directories (7 clone groups) transmuters/mkd-manuscript/src/format.ts:1
- Duplication concentrated across 4 sibling directories (6 clone groups) engine/src/engine/layout/session-world-runtime.ts:159
- Wholesale file copy (418 identical lines × 2 files) transmuters/mkd-manuscript/src/format.ts:1
- Duplicated block with local edits (384 matched lines × 2 locations) preview/playground/app.js:1015
- Duplicated block with local edits (321 matched lines × 2 locations) contexts/pdf/src/standard-font-data.ts:1
- Duplicated block with local edits (223 matched lines × 2 locations) engine/src/engine/layout/packagers/script-document-packager.ts:68
- Duplicated block with local edits (198 matched lines × 2 locations) engine/src/engine/layout/packagers/script-document-packager.ts:539
- Wholesale file copy (170 identical lines × 2 files) contexts/pdf/src/standard-font-encoding.ts:4
- Duplicated block with local edits (108 matched lines × 2 locations) contexts/dev-cli/src/index.ts:25
- Duplicated block with local edits (82 matched lines × 2 locations) transmuters/mkd-manuscript/src/validator.ts:3
- Wholesale file copy (79 identical lines × 2 files) contracts/src/context.ts:7
- Wholesale file copy (77 identical lines × 2 files) engine/src/font-management/sentinel.ts:1
- Duplicated block with local edits (61 matched lines × 2 locations) contexts/pdf-lite/src/index.ts:427
- Duplicated block (52 lines × 2 locations) engine/src/engine/layout-engine.ts:2333
- Duplicated block (51 lines × 2 locations) engine/src/engine/layout/packagers/list-packager.ts:864
- Wholesale file copy (50 identical lines × 2 files) contracts/src/overlay.ts:1
- Duplicated block (38 lines × 2 locations) transmuters/mkd-manuscript/src/index.ts:280
- Duplicated block (37 lines × 2 locations) engine/src/engine/layout/transitions-runtime.ts:304
- Duplicated block with local edits (35 matched lines × 2 locations) engine/src/engine/runtime/simulation/runtime/march-runner.ts:1030
- Duplicated block (34 lines × 2 locations) contracts/src/text-delegate.ts:11
- Duplicated block with local edits (34 matched lines × 2 locations) engine/src/engine/layout-engine.ts:339
- Duplicated block with local edits (33 matched lines × 2 locations) engine/src/engine/layout/collaborators/heading-telemetry-collaborator.ts:17
- Duplicated block (33 lines × 2 locations) engine/src/engine/layout/text-wrap-core.ts:546
- Duplicated block (32 lines × 2 locations) font-managers/local/src/LocalFontManager.ts:45
- Duplicated block (31 lines × 2 locations) engine/src/engine/layout/packagers/list-packager.ts:1813
- Duplicated block (28 lines × 3 locations) engine/src/engine/layout/physics-runtime.ts:444
- Duplicated block (25 lines × 2 locations) contracts/src/font-manager.ts:1
- Duplicated block (24 lines × 2 locations) engine/src/engine/layout-engine.ts:2228
- Duplicated block (23 lines × 3 locations) engine/src/engine/layout-engine.ts:1547
- Duplicated block with local edits (22 matched lines × 2 locations) engine/src/engine/layout/collision-runtime.ts:107
- Duplicated block (22 lines × 2 locations) engine/src/engine/layout/packagers/contained-flow-packager.ts:93
- Boundary violation [package:test-suite-dependency] engine/scripts/text-measure-server.ts:6
- Complex function pourColumns (cyclomatic 97, cognitive 245) engine/src/engine/layout/packagers/story-packager.ts:1257
- Complex function applyRuntimeFormattingBatchIntent (cyclomatic 73, cognitive 143) engine/src/engine/layout-engine.ts:1401
- Complex function (anonymous) (cyclomatic 73, cognitive 81) engine/src/engine/render/rich-line-draw.ts:56
- Complex function run (cyclomatic 70, cognitive 120) engine/tests/engine-regression.spec.ts:3015
- Complex function reflowTextElementAgainstSpatialField (cyclomatic 70, cognitive 67) engine/src/engine/layout/spatial-field-reflow.ts:67
- Complex function (anonymous) (cyclomatic 68, cognitive 75) engine/src/engine/render/box-paint.ts:175
- Complex function materialize (cyclomatic 66, cognitive 73) engine/src/engine/layout/packagers/dropcap-packager.ts:361
- Complex function buildRichWrapTokens (cyclomatic 65, cognitive 141) engine/src/engine/layout/text-wrap-core.ts:127
- Complex function trySplitSpatialItemAtBoundary (cyclomatic 65, cognitive 101) engine/src/engine/layout/packagers/list-packager.ts:1552
- Complex function positionSpatialGridFlowBoxes (cyclomatic 63, cognitive 92) engine/src/engine/layout/layout-table.ts:882
- Complex function measureInlineObject (cyclomatic 60, cognitive 49) engine/src/engine/layout/text-processor.ts:213
- Complex function validateLayout (cyclomatic 59, cognitive 83) engine/src/engine/document.ts:267
- Complex function materializeSpatialGridFlowBox (cyclomatic 55, cognitive 88) engine/src/engine/layout/layout-table.ts:403
- Complex function validateStyleObject (cyclomatic 54, cognitive 53) engine/src/engine/document.ts:469
- Complex function pourAll (cyclomatic 53, cognitive 124) engine/src/engine/layout/packagers/story-packager.ts:582
- Complex function splitResult (cyclomatic 51, cognitive 140) engine/src/engine/layout/packagers/story-packager.ts:1968
- Complex function applyRuntimeFormattingIntentInternal (cyclomatic 50, cognitive 50) engine/src/engine/layout-engine.ts:2406
- Complex function wrapTokenStream (cyclomatic 48, cognitive 159) engine/src/engine/layout/text-wrap-core.ts:357
- Complex function validateElementNode (cyclomatic 48, cognitive 64) engine/src/engine/document.ts:1022
- Complex function (anonymous) (cyclomatic 48, cognitive 40) preview/src/index.ts:882
- Complex function runHostedRegionSessionBounded (cyclomatic 47, cognitive 102) engine/src/engine/layout/packagers/hosted-region-settlement.ts:943
- Complex function applyRuntimeFormattingRestoreIntentInternal (cyclomatic 44, cognitive 42) engine/src/engine/layout-engine.ts:2210
- Complex function inlineToElements (cyclomatic 41, cognitive 71) transmuters/markdown-core/src/inline.ts:54
- Complex function materializeTableCell (cyclomatic 41, cognitive 48) engine/src/engine/layout/layout-table.ts:189
- Complex function flush (cyclomatic 40, cognitive 77) transmuters/mkd-screenplay/src/format.ts:190
- Complex function normalizeElementNode (cyclomatic 39, cognitive 46) engine/src/engine/document.ts:1277
- Complex function updateCommittedState (cyclomatic 38, cognitive 46) engine/src/engine/layout/packagers/script-document-packager.ts:1001
- Complex function normalizeElementStyle (cyclomatic 38, cognitive 29) engine/src/engine/layout/layout-core.ts:389
- Complex function (anonymous) (cyclomatic 37, cognitive 51) engine/src/engine/layout/spatial-field-reflow.ts:171
- Complex function parseSvgPathSubpaths (cyclomatic 35, cognitive 67) engine/src/engine/geometry/svg-path.ts:18
- Complex function (anonymous) (cyclomatic 35, cognitive 55) engine/src/engine/render/direction.ts:100
- Complex function hitTestPoint (cyclomatic 35, cognitive 33) engine/src/engine/layout-engine.ts:443
- Complex function createDynamicPackager (cyclomatic 35, cognitive 29) engine/tests/support/reactive-proof-packagers.ts:932
- Complex function tryPrepareItemsAgainstSpatialField (cyclomatic 34, cognitive 52) engine/src/engine/layout/packagers/list-packager.ts:962
- Complex function splitSpatialGridFlowBox (cyclomatic 33, cognitive 30) engine/src/engine/layout/layout-table.ts:645
- Complex function hitTestRichTextBox (cyclomatic 33, cognitive 29) engine/src/engine/layout/packagers/text-hit-testing.ts:178
- Complex function run (cyclomatic 32, cognitive 34) engine/tests/scripting-performance.ts:49
- Complex function resolveContainedFieldFrame (cyclomatic 32, cognitive 21) engine/src/engine/layout/packagers/contained-field-geometry.ts:16
- engine/src/font-management/afm-tables.ts: 8162 lines of code engine/src/font-management/afm-tables.ts:1
- contexts/pdf/src/standard-font-data.ts: 4147 lines of code contexts/pdf/src/standard-font-data.ts:1
- engine/src/engine/layout-engine.ts: 2518 lines of code engine/src/engine/layout-engine.ts:1
- engine/src/engine/layout/packagers/story-packager.ts: 2516 lines of code engine/src/engine/layout/packagers/story-packager.ts:1
- engine/src/engine/layout/packagers/list-packager.ts: 1801 lines of code engine/src/engine/layout/packagers/list-packager.ts:1
- engine/src/engine/layout/layout-session.ts: 1754 lines of code engine/src/engine/layout/layout-session.ts:1
- engine/src/engine/document.ts: 1646 lines of code engine/src/engine/document.ts:1
- engine/src/engine/layout/layout-core.ts: 1518 lines of code engine/src/engine/layout/layout-core.ts:1
- engine/src/engine/runtime/simulation/runtime/march-runner.ts: 1190 lines of code engine/src/engine/runtime/simulation/runtime/march-runner.ts:1
- engine/src/engine/layout/packagers/hosted-region-settlement.ts: 1166 lines of code engine/src/engine/layout/packagers/hosted-region-settlement.ts:1
- engine/src/engine/interaction-model.ts: 1094 lines of code engine/src/engine/interaction-model.ts:1
- engine/src/engine/layout/packagers/script-document-packager.ts: 1091 lines of code engine/src/engine/layout/packagers/script-document-packager.ts:1
- preview/src/index.ts: 1045 lines of code preview/src/index.ts:1
- engine/src/engine/layout/layout-table.ts: 1037 lines of code engine/src/engine/layout/layout-table.ts:1
- engine/src/engine/layout/packagers/scripted-flow-box-packager.ts: 1036 lines of code engine/src/engine/layout/packagers/scripted-flow-box-packager.ts:1
- engine/src/engine/layout/text-processor.ts: 861 lines of code engine/src/engine/layout/text-processor.ts:1
- engine/src/engine/layout/transitions-runtime.ts: 783 lines of code engine/src/engine/layout/transitions-runtime.ts:1
- contexts/pdf-lite/src/index.ts: 765 lines of code contexts/pdf-lite/src/index.ts:1
- engine/src/engine/layout/packagers/dropcap-packager.ts: 728 lines of code engine/src/engine/layout/packagers/dropcap-packager.ts:1
- engine/src/engine/layout/packagers/hosted-region-packager.ts: 706 lines of code engine/src/engine/layout/packagers/hosted-region-packager.ts:1
- engine/src/engine/layout/collider-field.ts: 645 lines of code engine/src/engine/layout/collider-field.ts:1
- contexts/canvas/src/index.ts: 641 lines of code contexts/canvas/src/index.ts:1
- engine/src/engine/layout/spatial-field-reflow.ts: 635 lines of code engine/src/engine/layout/spatial-field-reflow.ts:1
- engine/src/engine/layout/actor-communication-runtime.ts: 631 lines of code engine/src/engine/layout/actor-communication-runtime.ts:1
- engine/src/engine/layout/text-wrap-core.ts: 616 lines of code engine/src/engine/layout/text-wrap-core.ts:1
- engine/src/engine/spatial-document.ts: 594 lines of code engine/src/engine/spatial-document.ts:1
- engine/src/engine/layout/runtime/scripting/script-runtime-pass.ts: 587 lines of code engine/src/engine/layout/runtime/scripting/script-runtime-pass.ts:1
- transmuters/mkd-manuscript/src/format.ts: 584 lines of code transmuters/mkd-manuscript/src/format.ts:1
- transmuters/mkd-zh-manuscript/src/format.ts: 581 lines of code transmuters/mkd-zh-manuscript/src/format.ts:1
- engine/src/engine/layout/session-world-runtime.ts: 559 lines of code engine/src/engine/layout/session-world-runtime.ts:1
- engine/src/engine/layout/runtime/page-finalization/page-region-finalization.ts: 526 lines of code engine/src/engine/layout/runtime/page-finalization/page-region-finalization.ts:1
- documents/assets/specimen-blueprint.overlay.mjs: 507 lines of code documents/assets/specimen-blueprint.overlay.mjs:1
- engine/src/engine/context-renderer.ts: 497 lines of code engine/src/engine/context-renderer.ts:1
- engine/src/engine/layout/physics-runtime.ts: 496 lines of code engine/src/engine/layout/physics-runtime.ts:1
- engine/src/engine/render/box-paint.ts: 469 lines of code engine/src/engine/render/box-paint.ts:1
- engine/src/engine/layout/runtime-formatting.ts: 432 lines of code engine/src/engine/layout/runtime-formatting.ts:1
- engine/src/engine/layout/packagers/packager-types.ts: 415 lines of code engine/src/engine/layout/packagers/packager-types.ts:1
- No lint script
- Dead file (~1506 LoC) preview/playground/app.ts
- Dead file (~1404 LoC) preview/playground/app.js
- Dead file (~394 LoC) engine/src/font-management/generate-afm-tables.mjs
- Dead file (~15 LoC) engine/src/engine/layout/text-delegate.ts
- Dead file (~11 LoC) engine/src/engine/layout/browser-text-preprocessing.ts
- Dead file (~9 LoC) engine/src/engine/layout/text-measurer.ts
- Dead file (~4 LoC) engine/src/font-management/index.ts
- Unused dependency 'dfa' engine/package.json:85
- Unused dependency 'restructure' engine/package.json:87
- Unused dependency 'unicode-properties' engine/package.json:88
- Unused dependency 'unicode-trie' engine/package.json:89
- Swallowed exception (caught, then discarded) font-managers/local/src/LocalFontManager.ts:35
Minor — 95 finding(s)
- Duplicated predicate engine/src/engine/document.ts:16
- Duplicated predicate engine/src/engine/layout/packagers/text-hit-testing.ts:226
- Duplicated predicate engine/src/engine/layout/spatial-field-reflow.ts:341
- Duplicated predicate engine/src/engine/layout/layout-core.ts:667
- Duplicated predicate engine/src/engine/layout/packagers/script-document-packager.ts:209
- Duplicated predicate engine/src/engine/geometry/svg-path.ts:167
- Duplicated predicate engine/src/engine/layout/packagers/script-document-packager.ts:195
- Duplicated predicate engine/src/engine/layout-engine.ts:826
- Duplicated predicate engine/src/engine/layout/exclusion-field.ts:91
- Duplicated predicate engine/src/engine/layout/packagers/hosted-region-packager.ts:667
- Duplicated predicate engine/src/engine/layout/collaborators/contained-content-artifact-collaborator.ts:64
- Duplicated predicate preview/playground/app.js:1376
- Duplicated predicate preview/playground/app.js:1047
- Duplicated predicate preview/src/index.ts:384
- Duplicated predicate engine/src/engine/layout/packagers/contained-flow-packager.ts:100
- Duplicated predicate engine/src/engine/layout/packagers/contained-flow-packager.ts:187
- Duplicated predicate engine/src/engine/context-renderer.ts:141
- Duplicated predicate engine/src/engine/layout/text-script-segmentation.ts:92
- Duplicated predicate engine/src/font-management/sentinel.ts:103
- Duplicated predicate transmuters/mkd-manuscript/src/format.ts:142
- Duplicated predicate engine/src/engine/layout/layout-core.ts:165
- Duplicated predicate engine/src/engine/layout/packagers/script-document-packager.ts:185
- Duplicated predicate engine/src/engine/layout/packagers/script-document-packager.ts:206
- Duplicated predicate engine/src/engine/layout/packagers/script-document-packager.ts:192
- Duplicated predicate engine/src/engine/layout/packagers/dropcap-packager.ts:313
- Fat interface: Context (30 required operations) contracts/src/context.ts:18
- Fat interface: OverlayContext (21 required operations) contracts/src/overlay.ts:27
- Fat interface: Context (30 required operations) engine/src/contracts/context.ts:12
- Fat interface: OverlayContext (21 required operations) engine/src/contracts/overlay.ts:27
- Fat interface: CollaboratorHost (39 required operations) engine/src/engine/layout/runtime/session/session-runtime-types.ts:60
- Fat interface: SimulationRunner (18 required operations) engine/src/engine/runtime/simulation/types.ts:97
- README/code drift README.md:75
- README/code drift README.md:76
- README/code drift docs/README.md:11
- README/code drift transmuters/markdown-core/README.md:24
- README/code drift transmuters/markdown-core/README.md:25
- Projects may be oversized for their cohesion package.json:1
- Projects may be oversized for their cohesion engine/package.json:1
- No app-layer HTTPS enforcement detected engine/scripts/text-measure-server.ts:149
- No app-layer HTTPS enforcement detected preview/scripts/playground-server.cjs:50
- Deprecated: jpeg-exif REDACTED:2552
- Documentation: no build, run or usage example transmuters/markdown-core/README.md:1
- redundant comment pressrun/src/index.ts:87
- REDACTED
- No ADRs
- No SAST
- No dependency-update automation package.json:37
- Unused export 'STANDARD_FONT_MAGIC_BYTES' contexts/pdf/src/standard-font-metadata.ts:2
- Unused export 'STANDARD_FONT_SENTINEL_VERSION' contexts/pdf/src/standard-font-metadata.ts:3
- Unused export 'STANDARD_FONT_SENTINEL_LENGTH' contexts/pdf/src/standard-font-metadata.ts:4
- Unused export 'parseEmbeddedImagePayload' engine/src/engine/image-data.ts:204
- Unused export 'isTableRowElement' engine/src/engine/layout/layout-table.ts:60
- Unused export 'isTableCellElement' engine/src/engine/layout/layout-table.ts:65
- Unused export 'TableLayoutContext' engine/src/engine/layout/layout-table.ts:1112
- Unused export 'materializeTableFlowBox' engine/src/engine/layout/layout-table.ts:1113
- Unused export 'splitTableFlowBox' engine/src/engine/layout/layout-table.ts:1114
- Unused export 'positionTableFlowBoxes' engine/src/engine/layout/layout-table.ts:1115
- Unused export 'ActorActivationState' engine/src/engine/layout/packagers/packager-types.ts:21
- Unused export 'PackagerTransformKind' engine/src/engine/layout/packagers/packager-types.ts:218
- Unused export 'PackagerTransformCapability' engine/src/engine/layout/packagers/packager-types.ts:220
- Unused export 'resolvePackagerTransformProfile' engine/src/engine/layout/packagers/packager-types.ts:466
- Unused export 'KeepWithNextCollaborator' engine/src/engine/layout/runtime/passes/keep-with-next-pass.ts:170
- Unused export 'findScriptRegionByName' engine/src/engine/layout/script-region-query.ts:150
- Unused export 'resolvePlainLayoutInfo' engine/src/engine/layout/text-tokenizer.ts:4
- Unused export 'resolveLineDirection' engine/src/engine/render/direction.ts:62
- Unused export 'registerFontBuffer' engine/src/font-management/font-cache-loader.ts:46
- Unused export 'getFontRegistrySnapshot' engine/src/font-management/ops.ts:22
- Unused export 'getAllFonts' engine/src/font-management/ops.ts:24
- Unused export 'getEnabledFallbackFonts' engine/src/font-management/ops.ts:27
- Unused export 'getFallbackFamilies' engine/src/font-management/ops.ts:33
- Unused export 'registerFallbackFont' engine/src/font-management/ops.ts:40
- Unused export 'encodeStandardFontTextToHex' engine/src/font-management/standard-font-encoding.ts:230
- Unused export 'isStandardFontSentinelBuffer' font-managers/standard/src/sentinel.ts:85
- Unused export 'attachStandardFontMetadata' font-managers/standard/src/sentinel.ts:88
- Unused export 'getStandardFontMetadata' font-managers/standard/src/sentinel.ts:98
- Unused export 'parseConfig' transmuters/markdown-core/src/theme.ts:47
- Write-only private field 'isEnded' contexts/canvas/src/index.ts:169
- Not all async functions that make a request accept an AbortSignal
- Null assertions (`!`) override strict null checking
- Silent fallback default in catch transmuters/markdown-core/src/index.ts:98
Minor — 7 finding(s)
- Outdated (npm): bidi-js
- Outdated (npm): dfa
- Outdated (npm): fontkit
- Outdated (npm): pdfkit
- Outdated (npm): unicode-properties
- Outdated (npm): unicode-trie
- Outdated (npm): yaml
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-468fcae6eea7404f9a15bcd0f382aff3/history.json --exit-code 0 --source . | 2 | 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=66" --report-format json --report-path /tmp/watchdog-gitleaks-468fcae6eea7404f9a15bcd0f382aff3/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=266 --max-count=28" --report-format json --report-path /tmp/watchdog-gitleaks-468fcae6eea7404f9a15bcd0f382aff3/history-2.json --exit-code 0 --source . | 0 | 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=294 --max-count=30" --report-format json --report-path /tmp/watchdog-gitleaks-468fcae6eea7404f9a15bcd0f382aff3/history-3.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-3.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=324 --max-count=15" --report-format json --report-path /tmp/watchdog-gitleaks-468fcae6eea7404f9a15bcd0f382aff3/history-4.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-4.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-468fcae6eea7404f9a15bcd0f382aff3/tree.json --exit-code 0 --source . | 2 | 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 . | 4 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 8 | 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 6 file(s) — `contexts/pdf/src/index.ts`, `engine/src/engine/layout/layout-core.ts`, `engine/src/engine/layout/simulation-report.ts`, `engine/src/engine/runtime-types.ts`, `engine/src/engine/spatial-document.ts`, … (+1 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |