Executive summary
Shopify/draggable is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 61 out of 100, which the At risk rating leaves unchanged.
Code Health, at 58, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is recording design decisions, worth about 4 points. Having someone learn and document the 23 files no active contributor knows comes next, also worth about 4.
Seventy-four known security holes in the packages the code depends on can be used by attackers. Three secrets can leak from the build pipeline, and one automatic update takes new releases before a bad one can be spotted. Updating the vulnerable packages, limiting each secret to its own step and setting a waiting period for automatic updates would close these risks. Pinning each tool to an exact version would fix the pipeline tool referenced by a changeable name, and giving the pull-request workflow read-only access would deal with the pipeline that outsiders can trigger with write access.
The product code is 6,748 lines, about €12,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 75 findings
- Cyclomatic Complexity · Mirror.positionMirror.<returned closure> (cyclomatic 16) REDACTED
- Cyclomatic Complexity · positionMirror (cyclomatic 16) REDACTED
- Cognitive Complexity · Mirror.positionMirror.<returned closure> (cognitive 19) REDACTED
- Cognitive Complexity · positionMirror (cognitive 19) REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Code Duplication · Duplicated block (16 lines × 2 locations) src/Draggable/Draggable.js
Fixed since the last survey: 7 findings
- Cyclomatic Complexity · Mirror.positionMirror (cyclomatic 16) REDACTED
- Cognitive Complexity · Mirror.positionMirror (cognitive 19) REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) src/Draggable/Draggable.js
Rebuild cost: about €12,000 · Estimate
| Cost to rebuild | €3,900 to €19,000, for 65 to 205 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 61. 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 | Small: 6,748 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 Draggable | 2 Draggable.Draggable | 3 Draggable.Plugins.Announcement | 4 Draggable.Plugins.Focusable | 5 Draggable.Plugins.Mirror | 6 Draggable.Plugins.Scrollable | 7 Draggable.Sensors.MouseSensor | 8 Draggable.Sensors.Sensor.Sensor | 9 shared.AbstractEvent.AbstractEvent | 10 shared.AbstractPlugin.AbstractPlugin | 11 shared.utils.closest.closest | 12 Draggable.DragEvent | 13 Draggable.DraggableEvent.DraggableEvent | 14 Draggable.Emitter.Emitter | 15 Draggable.Plugins.Announcement.Announcement | 16 Draggable.Plugins.Focusable.Focusable | 17 Draggable.Plugins.Mirror.Mirror | 18 Draggable.Plugins.Scrollable.Scrollable | 19 Draggable.Sensors.DragSensor.DragSensor | 20 Draggable.Sensors.ForceTouchSensor.ForceTouchSensor | 21 Draggable.Sensors.MouseSensor.MouseSensor | 22 Draggable.Sensors.SensorEvent.SensorEvent | 23 Draggable.Sensors.TouchSensor.TouchSensor | 24 Droppable.Droppable | 25 Plugins.Collidable.Collidable | 26 Plugins.Snappable.Snappable | 27 Plugins.SortAnimation.SortAnimation | 28 Plugins.SwapAnimation.SwapAnimation | 29 Sortable.Sortable | 30 Swappable.Swappable | 31 shared.utils.closest | 32 Draggable.DragEvent.DragEvent | 33 Plugins.SwapAnimation | 34 Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent | 35 Droppable.DroppableEvent.DroppableEvent | 36 Plugins.Collidable.CollidableEvent.CollidableEvent | 37 Plugins.Snappable.SnappableEvent.SnappableEvent | 38 Sortable.SortableEvent.SortableEvent | 39 Swappable.SwappableEvent.SwappableEvent | 40 Plugins.ResizeMirror.ResizeMirror |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Draggable | ||||||||||||||||||||||||||||||||||||||||
| 2 Draggable.Draggable | ||||||||||||||||||||||||||||||||||||||||
| 3 Draggable.Plugins.Announcement | ||||||||||||||||||||||||||||||||||||||||
| 4 Draggable.Plugins.Focusable | ||||||||||||||||||||||||||||||||||||||||
| 5 Draggable.Plugins.Mirror | ||||||||||||||||||||||||||||||||||||||||
| 6 Draggable.Plugins.Scrollable | ||||||||||||||||||||||||||||||||||||||||
| 7 Draggable.Sensors.MouseSensor | ||||||||||||||||||||||||||||||||||||||||
| 8 Draggable.Sensors.Sensor.Sensor | ||||||||||||||||||||||||||||||||||||||||
| 9 shared.AbstractEvent.AbstractEvent | ||||||||||||||||||||||||||||||||||||||||
| 10 shared.AbstractPlugin.AbstractPlugin | ||||||||||||||||||||||||||||||||||||||||
| 11 shared.utils.closest.closest | ||||||||||||||||||||||||||||||||||||||||
| 12 Draggable.DragEvent | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 Draggable.DraggableEvent.DraggableEvent | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Draggable.Emitter.Emitter | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Draggable.Plugins.Announcement.Announcement | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Draggable.Plugins.Focusable.Focusable | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Draggable.Plugins.Mirror.Mirror | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Draggable.Plugins.Scrollable.Scrollable | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Draggable.Sensors.DragSensor.DragSensor | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Draggable.Sensors.ForceTouchSensor.ForceTouchSensor | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 Draggable.Sensors.MouseSensor.MouseSensor | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 Draggable.Sensors.SensorEvent.SensorEvent | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Draggable.Sensors.TouchSensor.TouchSensor | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 Droppable.Droppable | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 Plugins.Collidable.Collidable | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Plugins.Snappable.Snappable | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 Plugins.SortAnimation.SortAnimation | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Plugins.SwapAnimation.SwapAnimation | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 Sortable.Sortable | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 Swappable.Swappable | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 shared.utils.closest | 2 | |||||||||||||||||||||||||||||||||||||||
| 32 Draggable.DragEvent.DragEvent | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 Plugins.SwapAnimation | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 35 Droppable.DroppableEvent.DroppableEvent | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 36 Plugins.Collidable.CollidableEvent.CollidableEvent | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 Plugins.Snappable.SnappableEvent.SnappableEvent | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 38 Sortable.SortableEvent.SortableEvent | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 39 Swappable.SwappableEvent.SwappableEvent | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 40 Plugins.ResizeMirror.ResizeMirror | 1 | 1 |
12→9 Draggable.DragEvent uses shared.AbstractEvent.AbstractEvent✕
- Connections
- 1 pair of types, where a type in Draggable.DragEvent uses a type in shared.AbstractEvent.AbstractEvent.
- The types involved
src.Draggable.DragEvent.DragEvent→src.shared.AbstractEvent.AbstractEvent.AbstractEvent
- Direction
- Draggable.DragEvent uses shared.AbstractEvent.AbstractEvent, so a change to shared.AbstractEvent.AbstractEvent can break Draggable.DragEvent, while a change to Draggable.DragEvent can't break shared.AbstractEvent.AbstractEvent.
- Position
- Below the diagonal: Draggable.DragEvent uses a module listed above it, which is the healthy direction.
13→9 Draggable.DraggableEvent.DraggableEvent uses shared.AbstractEvent.AbstractEvent✕
- Connections
- 1 pair of types, where a type in Draggable.DraggableEvent.DraggableEvent uses a type in shared.AbstractEvent.AbstractEvent.
- The types involved
src.Draggable.DraggableEvent.DraggableEvent.DraggableEvent→src.shared.AbstractEvent.AbstractEvent.AbstractEvent
- Direction
- Draggable.DraggableEvent.DraggableEvent uses shared.AbstractEvent.AbstractEvent, so a change to shared.AbstractEvent.AbstractEvent can break Draggable.DraggableEvent.DraggableEvent, while a change to Draggable.DraggableEvent.DraggableEvent can't break shared.AbstractEvent.AbstractEvent.
- Position
- Below the diagonal: Draggable.DraggableEvent.DraggableEvent uses a module listed above it, which is the healthy direction.
14→9 Draggable.Emitter.Emitter uses shared.AbstractEvent.AbstractEvent✕
- Connections
- 1 pair of types, where a type in Draggable.Emitter.Emitter uses a type in shared.AbstractEvent.AbstractEvent.
- The types involved
src.Draggable.Emitter.Emitter.Emitter→src.shared.AbstractEvent.AbstractEvent.AbstractEvent
- Direction
- Draggable.Emitter.Emitter uses shared.AbstractEvent.AbstractEvent, so a change to shared.AbstractEvent.AbstractEvent can break Draggable.Emitter.Emitter, while a change to Draggable.Emitter.Emitter can't break shared.AbstractEvent.AbstractEvent.
- Position
- Below the diagonal: Draggable.Emitter.Emitter uses a module listed above it, which is the healthy direction.
15→10 Draggable.Plugins.Announcement.Announcement uses shared.AbstractPlugin.AbstractPlugin✕
- Connections
- 1 pair of types, where a type in Draggable.Plugins.Announcement.Announcement uses a type in shared.AbstractPlugin.AbstractPlugin.
- The types involved
src.Draggable.Plugins.Announcement.Announcement.Announcement→src.shared.AbstractPlugin.AbstractPlugin.AbstractPlugin
- Direction
- Draggable.Plugins.Announcement.Announcement uses shared.AbstractPlugin.AbstractPlugin, so a change to shared.AbstractPlugin.AbstractPlugin can break Draggable.Plugins.Announcement.Announcement, while a change to Draggable.Plugins.Announcement.Announcement can't break shared.AbstractPlugin.AbstractPlugin.
- Position
- Below the diagonal: Draggable.Plugins.Announcement.Announcement uses a module listed above it, which is the healthy direction.
16→10 Draggable.Plugins.Focusable.Focusable uses shared.AbstractPlugin.AbstractPlugin✕
- Connections
- 1 pair of types, where a type in Draggable.Plugins.Focusable.Focusable uses a type in shared.AbstractPlugin.AbstractPlugin.
- The types involved
src.Draggable.Plugins.Focusable.Focusable.Focusable→src.shared.AbstractPlugin.AbstractPlugin.AbstractPlugin
- Direction
- Draggable.Plugins.Focusable.Focusable uses shared.AbstractPlugin.AbstractPlugin, so a change to shared.AbstractPlugin.AbstractPlugin can break Draggable.Plugins.Focusable.Focusable, while a change to Draggable.Plugins.Focusable.Focusable can't break shared.AbstractPlugin.AbstractPlugin.
- Position
- Below the diagonal: Draggable.Plugins.Focusable.Focusable uses a module listed above it, which is the healthy direction.
17→10 Draggable.Plugins.Mirror.Mirror uses shared.AbstractPlugin.AbstractPlugin✕
- Connections
- 1 pair of types, where a type in Draggable.Plugins.Mirror.Mirror uses a type in shared.AbstractPlugin.AbstractPlugin.
- The types involved
src.Draggable.Plugins.Mirror.Mirror.Mirror→src.shared.AbstractPlugin.AbstractPlugin.AbstractPlugin
- Direction
- Draggable.Plugins.Mirror.Mirror uses shared.AbstractPlugin.AbstractPlugin, so a change to shared.AbstractPlugin.AbstractPlugin can break Draggable.Plugins.Mirror.Mirror, while a change to Draggable.Plugins.Mirror.Mirror can't break shared.AbstractPlugin.AbstractPlugin.
- Position
- Below the diagonal: Draggable.Plugins.Mirror.Mirror uses a module listed above it, which is the healthy direction.
18→10 Draggable.Plugins.Scrollable.Scrollable uses shared.AbstractPlugin.AbstractPlugin✕
- Connections
- 1 pair of types, where a type in Draggable.Plugins.Scrollable.Scrollable uses a type in shared.AbstractPlugin.AbstractPlugin.
- The types involved
src.Draggable.Plugins.Scrollable.Scrollable.Scrollable→src.shared.AbstractPlugin.AbstractPlugin.AbstractPlugin
- Direction
- Draggable.Plugins.Scrollable.Scrollable uses shared.AbstractPlugin.AbstractPlugin, so a change to shared.AbstractPlugin.AbstractPlugin can break Draggable.Plugins.Scrollable.Scrollable, while a change to Draggable.Plugins.Scrollable.Scrollable can't break shared.AbstractPlugin.AbstractPlugin.
- Position
- Below the diagonal: Draggable.Plugins.Scrollable.Scrollable uses a module listed above it, which is the healthy direction.
19→8 Draggable.Sensors.DragSensor.DragSensor uses Draggable.Sensors.Sensor.Sensor✕
- Connections
- 1 pair of types, where a type in Draggable.Sensors.DragSensor.DragSensor uses a type in Draggable.Sensors.Sensor.Sensor.
- The types involved
src.Draggable.Sensors.DragSensor.DragSensor.DragSensor→src.Draggable.Sensors.Sensor.Sensor.Sensor
- Direction
- Draggable.Sensors.DragSensor.DragSensor uses Draggable.Sensors.Sensor.Sensor, so a change to Draggable.Sensors.Sensor.Sensor can break Draggable.Sensors.DragSensor.DragSensor, while a change to Draggable.Sensors.DragSensor.DragSensor can't break Draggable.Sensors.Sensor.Sensor.
- Position
- Below the diagonal: Draggable.Sensors.DragSensor.DragSensor uses a module listed above it, which is the healthy direction.
20→8 Draggable.Sensors.ForceTouchSensor.ForceTouchSensor uses Draggable.Sensors.Sensor.Sensor✕
- Connections
- 1 pair of types, where a type in Draggable.Sensors.ForceTouchSensor.ForceTouchSensor uses a type in Draggable.Sensors.Sensor.Sensor.
- The types involved
src.Draggable.Sensors.ForceTouchSensor.ForceTouchSensor.ForceTouchSensor→src.Draggable.Sensors.Sensor.Sensor.Sensor
- Direction
- Draggable.Sensors.ForceTouchSensor.ForceTouchSensor uses Draggable.Sensors.Sensor.Sensor, so a change to Draggable.Sensors.Sensor.Sensor can break Draggable.Sensors.ForceTouchSensor.ForceTouchSensor, while a change to Draggable.Sensors.ForceTouchSensor.ForceTouchSensor can't break Draggable.Sensors.Sensor.Sensor.
- Position
- Below the diagonal: Draggable.Sensors.ForceTouchSensor.ForceTouchSensor uses a module listed above it, which is the healthy direction.
21→8 Draggable.Sensors.MouseSensor.MouseSensor uses Draggable.Sensors.Sensor.Sensor✕
- Connections
- 1 pair of types, where a type in Draggable.Sensors.MouseSensor.MouseSensor uses a type in Draggable.Sensors.Sensor.Sensor.
- The types involved
src.Draggable.Sensors.MouseSensor.MouseSensor.MouseSensor→src.Draggable.Sensors.Sensor.Sensor.Sensor
- Direction
- Draggable.Sensors.MouseSensor.MouseSensor uses Draggable.Sensors.Sensor.Sensor, so a change to Draggable.Sensors.Sensor.Sensor can break Draggable.Sensors.MouseSensor.MouseSensor, while a change to Draggable.Sensors.MouseSensor.MouseSensor can't break Draggable.Sensors.Sensor.Sensor.
- Position
- Below the diagonal: Draggable.Sensors.MouseSensor.MouseSensor uses a module listed above it, which is the healthy direction.
22→9 Draggable.Sensors.SensorEvent.SensorEvent uses shared.AbstractEvent.AbstractEvent✕
- Connections
- 1 pair of types, where a type in Draggable.Sensors.SensorEvent.SensorEvent uses a type in shared.AbstractEvent.AbstractEvent.
- The types involved
src.Draggable.Sensors.SensorEvent.SensorEvent.SensorEvent→src.shared.AbstractEvent.AbstractEvent.AbstractEvent
- Direction
- Draggable.Sensors.SensorEvent.SensorEvent uses shared.AbstractEvent.AbstractEvent, so a change to shared.AbstractEvent.AbstractEvent can break Draggable.Sensors.SensorEvent.SensorEvent, while a change to Draggable.Sensors.SensorEvent.SensorEvent can't break shared.AbstractEvent.AbstractEvent.
- Position
- Below the diagonal: Draggable.Sensors.SensorEvent.SensorEvent uses a module listed above it, which is the healthy direction.
23→8 Draggable.Sensors.TouchSensor.TouchSensor uses Draggable.Sensors.Sensor.Sensor✕
- Connections
- 1 pair of types, where a type in Draggable.Sensors.TouchSensor.TouchSensor uses a type in Draggable.Sensors.Sensor.Sensor.
- The types involved
src.Draggable.Sensors.TouchSensor.TouchSensor.TouchSensor→src.Draggable.Sensors.Sensor.Sensor.Sensor
- Direction
- Draggable.Sensors.TouchSensor.TouchSensor uses Draggable.Sensors.Sensor.Sensor, so a change to Draggable.Sensors.Sensor.Sensor can break Draggable.Sensors.TouchSensor.TouchSensor, while a change to Draggable.Sensors.TouchSensor.TouchSensor can't break Draggable.Sensors.Sensor.Sensor.
- Position
- Below the diagonal: Draggable.Sensors.TouchSensor.TouchSensor uses a module listed above it, which is the healthy direction.
24→2 Droppable.Droppable uses Draggable.Draggable✕
- Connections
- 1 pair of types, where a type in Droppable.Droppable uses a type in Draggable.Draggable.
- The types involved
src.Droppable.Droppable.Droppable→src.Draggable.Draggable.Draggable
- Direction
- Droppable.Droppable uses Draggable.Draggable, so a change to Draggable.Draggable can break Droppable.Droppable, while a change to Droppable.Droppable can't break Draggable.Draggable.
- Position
- Below the diagonal: Droppable.Droppable uses a module listed above it, which is the healthy direction.
25→10 Plugins.Collidable.Collidable uses shared.AbstractPlugin.AbstractPlugin✕
- Connections
- 1 pair of types, where a type in Plugins.Collidable.Collidable uses a type in shared.AbstractPlugin.AbstractPlugin.
- The types involved
src.Plugins.Collidable.Collidable.Collidable→src.shared.AbstractPlugin.AbstractPlugin.AbstractPlugin
- Direction
- Plugins.Collidable.Collidable uses shared.AbstractPlugin.AbstractPlugin, so a change to shared.AbstractPlugin.AbstractPlugin can break Plugins.Collidable.Collidable, while a change to Plugins.Collidable.Collidable can't break shared.AbstractPlugin.AbstractPlugin.
- Position
- Below the diagonal: Plugins.Collidable.Collidable uses a module listed above it, which is the healthy direction.
26→10 Plugins.Snappable.Snappable uses shared.AbstractPlugin.AbstractPlugin✕
- Connections
- 1 pair of types, where a type in Plugins.Snappable.Snappable uses a type in shared.AbstractPlugin.AbstractPlugin.
- The types involved
src.Plugins.Snappable.Snappable.Snappable→src.shared.AbstractPlugin.AbstractPlugin.AbstractPlugin
- Direction
- Plugins.Snappable.Snappable uses shared.AbstractPlugin.AbstractPlugin, so a change to shared.AbstractPlugin.AbstractPlugin can break Plugins.Snappable.Snappable, while a change to Plugins.Snappable.Snappable can't break shared.AbstractPlugin.AbstractPlugin.
- Position
- Below the diagonal: Plugins.Snappable.Snappable uses a module listed above it, which is the healthy direction.
27→10 Plugins.SortAnimation.SortAnimation uses shared.AbstractPlugin.AbstractPlugin✕
- Connections
- 1 pair of types, where a type in Plugins.SortAnimation.SortAnimation uses a type in shared.AbstractPlugin.AbstractPlugin.
- The types involved
src.Plugins.SortAnimation.SortAnimation.SortAnimation→src.shared.AbstractPlugin.AbstractPlugin.AbstractPlugin
- Direction
- Plugins.SortAnimation.SortAnimation uses shared.AbstractPlugin.AbstractPlugin, so a change to shared.AbstractPlugin.AbstractPlugin can break Plugins.SortAnimation.SortAnimation, while a change to Plugins.SortAnimation.SortAnimation can't break shared.AbstractPlugin.AbstractPlugin.
- Position
- Below the diagonal: Plugins.SortAnimation.SortAnimation uses a module listed above it, which is the healthy direction.
28→10 Plugins.SwapAnimation.SwapAnimation uses shared.AbstractPlugin.AbstractPlugin✕
- Connections
- 1 pair of types, where a type in Plugins.SwapAnimation.SwapAnimation uses a type in shared.AbstractPlugin.AbstractPlugin.
- The types involved
src.Plugins.SwapAnimation.SwapAnimation.SwapAnimation→src.shared.AbstractPlugin.AbstractPlugin.AbstractPlugin
- Direction
- Plugins.SwapAnimation.SwapAnimation uses shared.AbstractPlugin.AbstractPlugin, so a change to shared.AbstractPlugin.AbstractPlugin can break Plugins.SwapAnimation.SwapAnimation, while a change to Plugins.SwapAnimation.SwapAnimation can't break shared.AbstractPlugin.AbstractPlugin.
- Position
- Below the diagonal: Plugins.SwapAnimation.SwapAnimation uses a module listed above it, which is the healthy direction.
29→2 Sortable.Sortable uses Draggable.Draggable✕
- Connections
- 1 pair of types, where a type in Sortable.Sortable uses a type in Draggable.Draggable.
- The types involved
src.Sortable.Sortable.Sortable→src.Draggable.Draggable.Draggable
- Direction
- Sortable.Sortable uses Draggable.Draggable, so a change to Draggable.Draggable can break Sortable.Sortable, while a change to Sortable.Sortable can't break Draggable.Draggable.
- Position
- Below the diagonal: Sortable.Sortable uses a module listed above it, which is the healthy direction.
30→2 Swappable.Swappable uses Draggable.Draggable✕
- Connections
- 1 pair of types, where a type in Swappable.Swappable uses a type in Draggable.Draggable.
- The types involved
src.Swappable.Swappable.Swappable→src.Draggable.Draggable.Draggable
- Direction
- Swappable.Swappable uses Draggable.Draggable, so a change to Draggable.Draggable can break Swappable.Swappable, while a change to Swappable.Swappable can't break Draggable.Draggable.
- Position
- Below the diagonal: Swappable.Swappable uses a module listed above it, which is the healthy direction.
31→11 shared.utils.closest uses shared.utils.closest.closest✕
- Connections
- 2 pairs of types, where a type in shared.utils.closest uses a type in shared.utils.closest.closest.
- The types involved
src.shared.utils.closest.closest→src.shared.utils.closest.closest.Nodesrc.shared.utils.closest.closest→src.shared.utils.closest.closest.Value
- Direction
- shared.utils.closest uses shared.utils.closest.closest, so a change to shared.utils.closest.closest can break shared.utils.closest, while a change to shared.utils.closest can't break shared.utils.closest.closest.
- Position
- Below the diagonal: shared.utils.closest uses a module listed above it, which is the healthy direction.
32→9 Draggable.DragEvent.DragEvent uses shared.AbstractEvent.AbstractEvent✕
- Connections
- 1 pair of types, where a type in Draggable.DragEvent.DragEvent uses a type in shared.AbstractEvent.AbstractEvent.
- The types involved
src.Draggable.DragEvent.DragEvent.DragEvent→src.shared.AbstractEvent.AbstractEvent.AbstractEvent
- Direction
- Draggable.DragEvent.DragEvent uses shared.AbstractEvent.AbstractEvent, so a change to shared.AbstractEvent.AbstractEvent can break Draggable.DragEvent.DragEvent, while a change to Draggable.DragEvent.DragEvent can't break shared.AbstractEvent.AbstractEvent.
- Position
- Below the diagonal: Draggable.DragEvent.DragEvent uses a module listed above it, which is the healthy direction.
32→22 Draggable.DragEvent.DragEvent uses Draggable.Sensors.SensorEvent.SensorEvent✕
- Connections
- 1 pair of types, where a type in Draggable.DragEvent.DragEvent uses a type in Draggable.Sensors.SensorEvent.SensorEvent.
- The types involved
src.Draggable.DragEvent.DragEvent.DragEventData→src.Draggable.Sensors.SensorEvent.SensorEvent.SensorEvent
- Direction
- Draggable.DragEvent.DragEvent uses Draggable.Sensors.SensorEvent.SensorEvent, so a change to Draggable.Sensors.SensorEvent.SensorEvent can break Draggable.DragEvent.DragEvent, while a change to Draggable.DragEvent.DragEvent can't break Draggable.Sensors.SensorEvent.SensorEvent.
- Position
- Below the diagonal: Draggable.DragEvent.DragEvent uses a module listed above it, which is the healthy direction.
33→28 Plugins.SwapAnimation uses Plugins.SwapAnimation.SwapAnimation✕
- Connections
- 1 pair of types, where a type in Plugins.SwapAnimation uses a type in Plugins.SwapAnimation.SwapAnimation.
- The types involved
src.Plugins.SwapAnimation.SwapAnimation→src.Plugins.SwapAnimation.SwapAnimation.Options
- Direction
- Plugins.SwapAnimation uses Plugins.SwapAnimation.SwapAnimation, so a change to Plugins.SwapAnimation.SwapAnimation can break Plugins.SwapAnimation, while a change to Plugins.SwapAnimation can't break Plugins.SwapAnimation.SwapAnimation.
- Position
- Below the diagonal: Plugins.SwapAnimation uses a module listed above it, which is the healthy direction.
34→9 Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent uses shared.AbstractEvent.AbstractEvent✕
- Connections
- 1 pair of types, where a type in Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent uses a type in shared.AbstractEvent.AbstractEvent.
- The types involved
src.Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent.MirrorEvent→src.shared.AbstractEvent.AbstractEvent.AbstractEvent
- Direction
- Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent uses shared.AbstractEvent.AbstractEvent, so a change to shared.AbstractEvent.AbstractEvent can break Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent, while a change to Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent can't break shared.AbstractEvent.AbstractEvent.
- Position
- Below the diagonal: Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent uses a module listed above it, which is the healthy direction.
34→22 Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent uses Draggable.Sensors.SensorEvent.SensorEvent✕
- Connections
- 1 pair of types, where a type in Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent uses a type in Draggable.Sensors.SensorEvent.SensorEvent.
- The types involved
src.Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent.MirrorEventData→src.Draggable.Sensors.SensorEvent.SensorEvent.SensorEvent
- Direction
- Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent uses Draggable.Sensors.SensorEvent.SensorEvent, so a change to Draggable.Sensors.SensorEvent.SensorEvent can break Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent, while a change to Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent can't break Draggable.Sensors.SensorEvent.SensorEvent.
- Position
- Below the diagonal: Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent uses a module listed above it, which is the healthy direction.
34→32 Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent uses Draggable.DragEvent.DragEvent✕
- Connections
- 2 pairs of types, where a type in Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent uses a type in Draggable.DragEvent.DragEvent.
- The types involved
src.Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent.MirrorEventData→src.Draggable.DragEvent.DragEvent.DragEventsrc.Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent.MirrorEventData→src.Draggable.DragEvent.DragEvent.DragEventData
- Direction
- Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent uses Draggable.DragEvent.DragEvent, so a change to Draggable.DragEvent.DragEvent can break Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent, while a change to Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent can't break Draggable.DragEvent.DragEvent.
- Position
- Below the diagonal: Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent uses a module listed above it, which is the healthy direction.
35→9 Droppable.DroppableEvent.DroppableEvent uses shared.AbstractEvent.AbstractEvent✕
- Connections
- 1 pair of types, where a type in Droppable.DroppableEvent.DroppableEvent uses a type in shared.AbstractEvent.AbstractEvent.
- The types involved
src.Droppable.DroppableEvent.DroppableEvent.DroppableEvent→src.shared.AbstractEvent.AbstractEvent.AbstractEvent
- Direction
- Droppable.DroppableEvent.DroppableEvent uses shared.AbstractEvent.AbstractEvent, so a change to shared.AbstractEvent.AbstractEvent can break Droppable.DroppableEvent.DroppableEvent, while a change to Droppable.DroppableEvent.DroppableEvent can't break shared.AbstractEvent.AbstractEvent.
- Position
- Below the diagonal: Droppable.DroppableEvent.DroppableEvent uses a module listed above it, which is the healthy direction.
35→32 Droppable.DroppableEvent.DroppableEvent uses Draggable.DragEvent.DragEvent✕
- Connections
- 2 pairs of types, where a type in Droppable.DroppableEvent.DroppableEvent uses a type in Draggable.DragEvent.DragEvent.
- The types involved
src.Droppable.DroppableEvent.DroppableEvent.DroppableEventData→src.Draggable.DragEvent.DragEvent.DragEventsrc.Droppable.DroppableEvent.DroppableEvent.DroppableEventData→src.Draggable.DragEvent.DragEvent.DragEventData
- Direction
- Droppable.DroppableEvent.DroppableEvent uses Draggable.DragEvent.DragEvent, so a change to Draggable.DragEvent.DragEvent can break Droppable.DroppableEvent.DroppableEvent, while a change to Droppable.DroppableEvent.DroppableEvent can't break Draggable.DragEvent.DragEvent.
- Position
- Below the diagonal: Droppable.DroppableEvent.DroppableEvent uses a module listed above it, which is the healthy direction.
36→9 Plugins.Collidable.CollidableEvent.CollidableEvent uses shared.AbstractEvent.AbstractEvent✕
- Connections
- 1 pair of types, where a type in Plugins.Collidable.CollidableEvent.CollidableEvent uses a type in shared.AbstractEvent.AbstractEvent.
- The types involved
src.Plugins.Collidable.CollidableEvent.CollidableEvent.CollidableEvent→src.shared.AbstractEvent.AbstractEvent.AbstractEvent
- Direction
- Plugins.Collidable.CollidableEvent.CollidableEvent uses shared.AbstractEvent.AbstractEvent, so a change to shared.AbstractEvent.AbstractEvent can break Plugins.Collidable.CollidableEvent.CollidableEvent, while a change to Plugins.Collidable.CollidableEvent.CollidableEvent can't break shared.AbstractEvent.AbstractEvent.
- Position
- Below the diagonal: Plugins.Collidable.CollidableEvent.CollidableEvent uses a module listed above it, which is the healthy direction.
36→32 Plugins.Collidable.CollidableEvent.CollidableEvent uses Draggable.DragEvent.DragEvent✕
- Connections
- 2 pairs of types, where a type in Plugins.Collidable.CollidableEvent.CollidableEvent uses a type in Draggable.DragEvent.DragEvent.
- The types involved
src.Plugins.Collidable.CollidableEvent.CollidableEvent.CollidableEventData→src.Draggable.DragEvent.DragEvent.DragEventsrc.Plugins.Collidable.CollidableEvent.CollidableEvent.CollidableEventData→src.Draggable.DragEvent.DragEvent.DragEventData
- Direction
- Plugins.Collidable.CollidableEvent.CollidableEvent uses Draggable.DragEvent.DragEvent, so a change to Draggable.DragEvent.DragEvent can break Plugins.Collidable.CollidableEvent.CollidableEvent, while a change to Plugins.Collidable.CollidableEvent.CollidableEvent can't break Draggable.DragEvent.DragEvent.
- Position
- Below the diagonal: Plugins.Collidable.CollidableEvent.CollidableEvent uses a module listed above it, which is the healthy direction.
37→9 Plugins.Snappable.SnappableEvent.SnappableEvent uses shared.AbstractEvent.AbstractEvent✕
- Connections
- 1 pair of types, where a type in Plugins.Snappable.SnappableEvent.SnappableEvent uses a type in shared.AbstractEvent.AbstractEvent.
- The types involved
src.Plugins.Snappable.SnappableEvent.SnappableEvent.SnapEvent→src.shared.AbstractEvent.AbstractEvent.AbstractEvent
- Direction
- Plugins.Snappable.SnappableEvent.SnappableEvent uses shared.AbstractEvent.AbstractEvent, so a change to shared.AbstractEvent.AbstractEvent can break Plugins.Snappable.SnappableEvent.SnappableEvent, while a change to Plugins.Snappable.SnappableEvent.SnappableEvent can't break shared.AbstractEvent.AbstractEvent.
- Position
- Below the diagonal: Plugins.Snappable.SnappableEvent.SnappableEvent uses a module listed above it, which is the healthy direction.
37→32 Plugins.Snappable.SnappableEvent.SnappableEvent uses Draggable.DragEvent.DragEvent✕
- Connections
- 2 pairs of types, where a type in Plugins.Snappable.SnappableEvent.SnappableEvent uses a type in Draggable.DragEvent.DragEvent.
- The types involved
src.Plugins.Snappable.SnappableEvent.SnappableEvent.SnapEventData→src.Draggable.DragEvent.DragEvent.DragEventsrc.Plugins.Snappable.SnappableEvent.SnappableEvent.SnapEventData→src.Draggable.DragEvent.DragEvent.DragEventData
- Direction
- Plugins.Snappable.SnappableEvent.SnappableEvent uses Draggable.DragEvent.DragEvent, so a change to Draggable.DragEvent.DragEvent can break Plugins.Snappable.SnappableEvent.SnappableEvent, while a change to Plugins.Snappable.SnappableEvent.SnappableEvent can't break Draggable.DragEvent.DragEvent.
- Position
- Below the diagonal: Plugins.Snappable.SnappableEvent.SnappableEvent uses a module listed above it, which is the healthy direction.
38→9 Sortable.SortableEvent.SortableEvent uses shared.AbstractEvent.AbstractEvent✕
- Connections
- 1 pair of types, where a type in Sortable.SortableEvent.SortableEvent uses a type in shared.AbstractEvent.AbstractEvent.
- The types involved
src.Sortable.SortableEvent.SortableEvent.SortableEvent→src.shared.AbstractEvent.AbstractEvent.AbstractEvent
- Direction
- Sortable.SortableEvent.SortableEvent uses shared.AbstractEvent.AbstractEvent, so a change to shared.AbstractEvent.AbstractEvent can break Sortable.SortableEvent.SortableEvent, while a change to Sortable.SortableEvent.SortableEvent can't break shared.AbstractEvent.AbstractEvent.
- Position
- Below the diagonal: Sortable.SortableEvent.SortableEvent uses a module listed above it, which is the healthy direction.
38→32 Sortable.SortableEvent.SortableEvent uses Draggable.DragEvent.DragEvent✕
- Connections
- 2 pairs of types, where a type in Sortable.SortableEvent.SortableEvent uses a type in Draggable.DragEvent.DragEvent.
- The types involved
src.Sortable.SortableEvent.SortableEvent.SortableEventData→src.Draggable.DragEvent.DragEvent.DragEventsrc.Sortable.SortableEvent.SortableEvent.SortableEventData→src.Draggable.DragEvent.DragEvent.DragEventData
- Direction
- Sortable.SortableEvent.SortableEvent uses Draggable.DragEvent.DragEvent, so a change to Draggable.DragEvent.DragEvent can break Sortable.SortableEvent.SortableEvent, while a change to Sortable.SortableEvent.SortableEvent can't break Draggable.DragEvent.DragEvent.
- Position
- Below the diagonal: Sortable.SortableEvent.SortableEvent uses a module listed above it, which is the healthy direction.
39→9 Swappable.SwappableEvent.SwappableEvent uses shared.AbstractEvent.AbstractEvent✕
- Connections
- 1 pair of types, where a type in Swappable.SwappableEvent.SwappableEvent uses a type in shared.AbstractEvent.AbstractEvent.
- The types involved
src.Swappable.SwappableEvent.SwappableEvent.SwappableEvent→src.shared.AbstractEvent.AbstractEvent.AbstractEvent
- Direction
- Swappable.SwappableEvent.SwappableEvent uses shared.AbstractEvent.AbstractEvent, so a change to shared.AbstractEvent.AbstractEvent can break Swappable.SwappableEvent.SwappableEvent, while a change to Swappable.SwappableEvent.SwappableEvent can't break shared.AbstractEvent.AbstractEvent.
- Position
- Below the diagonal: Swappable.SwappableEvent.SwappableEvent uses a module listed above it, which is the healthy direction.
39→32 Swappable.SwappableEvent.SwappableEvent uses Draggable.DragEvent.DragEvent✕
- Connections
- 2 pairs of types, where a type in Swappable.SwappableEvent.SwappableEvent uses a type in Draggable.DragEvent.DragEvent.
- The types involved
src.Swappable.SwappableEvent.SwappableEvent.SwappableEventData→src.Draggable.DragEvent.DragEvent.DragEventsrc.Swappable.SwappableEvent.SwappableEvent.SwappableEventData→src.Draggable.DragEvent.DragEvent.DragEventData
- Direction
- Swappable.SwappableEvent.SwappableEvent uses Draggable.DragEvent.DragEvent, so a change to Draggable.DragEvent.DragEvent can break Swappable.SwappableEvent.SwappableEvent, while a change to Swappable.SwappableEvent.SwappableEvent can't break Draggable.DragEvent.DragEvent.
- Position
- Below the diagonal: Swappable.SwappableEvent.SwappableEvent uses a module listed above it, which is the healthy direction.
40→10 Plugins.ResizeMirror.ResizeMirror uses shared.AbstractPlugin.AbstractPlugin✕
- Connections
- 1 pair of types, where a type in Plugins.ResizeMirror.ResizeMirror uses a type in shared.AbstractPlugin.AbstractPlugin.
- The types involved
src.Plugins.ResizeMirror.ResizeMirror.ResizeMirror→src.shared.AbstractPlugin.AbstractPlugin.AbstractPlugin
- Direction
- Plugins.ResizeMirror.ResizeMirror uses shared.AbstractPlugin.AbstractPlugin, so a change to shared.AbstractPlugin.AbstractPlugin can break Plugins.ResizeMirror.ResizeMirror, while a change to Plugins.ResizeMirror.ResizeMirror can't break shared.AbstractPlugin.AbstractPlugin.
- Position
- Below the diagonal: Plugins.ResizeMirror.ResizeMirror uses a module listed above it, which is the healthy direction.
40→34 Plugins.ResizeMirror.ResizeMirror uses Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent✕
- Connections
- 1 pair of types, where a type in Plugins.ResizeMirror.ResizeMirror uses a type in Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent.
- The types involved
src.Plugins.ResizeMirror.ResizeMirror.ResizeMirror→src.Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent.MirrorCreatedEvent
- Direction
- Plugins.ResizeMirror.ResizeMirror uses Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent, so a change to Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent can break Plugins.ResizeMirror.ResizeMirror, while a change to Plugins.ResizeMirror.ResizeMirror can't break Draggable.Plugins.Mirror.MirrorEvent.MirrorEvent.
- Position
- Below the diagonal: Plugins.ResizeMirror.ResizeMirror 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 122 | High / Critical |
| A05:2025 — Injection | 18 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json; Resolve the 23 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED, Scrollable.js, Sortable.js; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. | +3.8 pts | Low | ADR Quality |
| Resolve the 23 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED, Scrollable.js, Sortable.js. | +3.8 pts | Medium | Knowledge Freshness |
| 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. | +2.3 pts | Medium | Architecture documentation |
| 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 `?`). | +2.1 pts | Medium | Nullable reference types |
| Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with .nvmrc. | +1.0 pts | Low | Platform End-of-Life |
| 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. | +1.7 pts | Medium | Code Duplication |
| Resolve the 62 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (62). | +1.3 pts | Medium | Dependency Vulnerabilities |
| Resolve the 1 finding(s) in Type Safety. | +1.1 pts | Medium | Type Safety |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Draggable/Plugins/Scrollable/Scrollable.js | 7.8 | Mixed | Cognitive Complexity: Scrollable.[scroll] (cognitive 18) |
| src/Draggable/tests/Draggable.test.js | 7.8 | Mixed | Test Quality: Skipped test: should set containers |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| .nvmrc | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: Node.js 20 |
| package.json | 8.0 | Near-clean | Dependency Hygiene: Deprecated: eslint |
| src/Draggable/Sensors/ForceTouchSensor/ForceTouchSensor.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/Draggable/Sensors/ForceTouchSensor/ForceTouchSensor.js |
| src/Plugins/Collidable/Collidable.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/Plugins/Collidable/Collidable.js |
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 50 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 — 50 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, 244 of 253 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
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 24 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 23 of the 81 production source files in this repository: 57 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- 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 start`) 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: "> @shopify/draggable@1.2.1 start / > concurrently "yarn watch" "cd examples && yarn && yarn start" / [0] /bin/sh: 1: yarn: not found / [1] /bin/sh: 1: yarn: not found / [1] cd examples && yarn && yarn start exited with code 127 / [0] yarn watch exited with code 127" 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 (start). the dev server (`npm run start`) 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: "> @shopify/draggable@1.2.1 start / > concurrently "yarn watch" "cd examples && yarn && yarn start" / [0] /bin/sh: 1: yarn: not found / [1] /bin/sh: 1: yarn: not found / [1] cd examples && yarn && yarn start exited with code 127 / [0] yarn watch exited with code 127" 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 none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 77 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Mirror.positionMirror.<returned closure> at 16.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Mirror.positionMirror.<returned closure> (cyclomatic 16), positionMirror (cyclomatic 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was Mirror.positionMirror.<returned closure> at 19.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with Mirror.positionMirror.<returned closure> (cognitive 19), positionMirror (cognitive 19), Scrollable.[scroll] (cognitive 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
0 god class(es) detected.
D6 · Cohesion (LCOM4)
0 of 12 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 76.5% — 9 file(s) below 50%. Measured from the JavaScript/TypeScript suite (jest via `yarn install --frozen-lockfile --ignore-scripts` in the repository root).
What to do
- Resolve the 9 Low coverage finding(s) in Code Coverage — start with ForceTouchSensor.js, Collidable.js, CollidableEvent.ts. — One of this dimension's main actionable groups (9 warning-level).
D10 · Test Quality
3 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 216 tests.
What to do
- Resolve the 3 Skipped test finding(s) in Test Quality — start with Draggable.test.js (2), DragSensor.test.js. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Mock-dominated test finding(s) in Test Quality — start with Swappable.test.js, Sortable.test.js, Emitter.test.ts. — One of this dimension's main actionable groups (3 recommendation-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `yarn install --frozen-lockfile --ignore-scripts` in the repository root (220 tests)): measured (0 flaky).
D12 · Dependency Hygiene
1 outdated direct production npm dependency(ies) of 1 graded, 0 pinning defect(s), across 2 package.json (1 of them the product) and 2 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 1 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 16 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (16). — One of this dimension's main actionable groups (16 recommendation-level).
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 1 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 1 package(s) this repository's committed lockfile installs for a consumer — its 1 production, optional and peer dependency(ies), across 1 product package.json manifest(s), and everything those install in turn. Its 59 `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. This repository publishes itself under MIT, 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 1865 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 1 documentation facets pass in full. 39 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
37 % of calls cross a namespace and 0 % go through an interface, but 48 % of collaborators are co-located — so following a call takes several hops. 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)
18 finding(s): 0 critical, 5 high, 13 medium, 0 low. 1 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 4 file(s) — `examples/src/components/Document/Head.html` (lines 1–24, lines 42–43), `REDACTED`, `examples/src/components/PageHeader/PageHeader.html`, `examples/src/components/Sidebar/Sidebar.html` (lines 1–3, line 19) — 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
115 finding(s): 11 critical, 63 high, 27 medium, 14 low.
What to do
- Resolve the 62 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (62). — One of this dimension's main actionable groups (62 issue-level).
- Resolve the 10 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
24 of 24 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Draggable/Draggable.js. Counted over 24 of the 81 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 23 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED, Scrollable.js, Sortable.js. — One of this dimension's main actionable groups (23 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with Draggable.js. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with .nvmrc. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×3) — src/Draggable/Sensors/DragSensor/tests/DragSensor.test.js:57, src/Draggable/tests/Draggable.test.js:80, src/Draggable/tests/Draggable.test.js:88
What to do
- Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 5 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
R1 · Type Safety
- 61 typed · 46 plain JS — the untyped files are src/Draggable/Draggable.js, src/Draggable/Plugins/Announcement/Announcement.js, src/Draggable/Plugins/Announcement/index.js, src/Draggable/Plugins/Focusable/Focusable.js, src/Draggable/Plugins/Focusable/index.js, src/Draggable/Plugins/Focusable/tests/Focusable.test.js (+40 more). 0 production file(s) opt out entirely with @ts-nocheck · 1 @ts-ignore suppression(s).
R10 · Code Duplication
- 13 duplicated blocks under src/ have copies in at least two of the sibling directories Draggable, Droppable, Plugins, Sortable, Swappable — 5 of them are reported below, and 8 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/Droppable/DroppableEvent/DroppableEvent.ts:5
- src/Draggable/Sensors/MouseSensor/MouseSensor.js:86 · src/Draggable/Sensors/TouchSensor/TouchSensor.js:118 — the two spans are one implementation copied and then locally edited — 440 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. — src/Draggable/Sensors/MouseSensor/MouseSensor.js:86
- REDACTED:46 · src/Draggable/Plugins/Scrollable/Scrollable.js:29 — the two spans are one implementation copied and then locally edited — 177 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:46
- src/Draggable/Sensors/ForceTouchSensor/ForceTouchSensor.js:53 · src/Draggable/Sensors/ForceTouchSensor/ForceTouchSensor.js:80 — 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. — src/Draggable/Sensors/ForceTouchSensor/ForceTouchSensor.js:53
- src/Sortable/Sortable.js:175 · src/Sortable/Sortable.js:222 — 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. — src/Sortable/Sortable.js:175
- src/Draggable/Plugins/Announcement/Announcement.js:29 · src/Draggable/Plugins/Focusable/Focusable.js:19 — the two spans are one implementation copied and then locally edited — 110 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. — src/Draggable/Plugins/Announcement/Announcement.js:29
- src/Draggable/Draggable.js:459 · src/Draggable/Draggable.js:616 — the two spans are one implementation copied and then locally edited — 103 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. — src/Draggable/Draggable.js:459
- src/Draggable/Sensors/ForceTouchSensor/ForceTouchSensor.js:204 · src/Draggable/Sensors/MouseSensor/MouseSensor.js:193 — 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. — src/Draggable/Sensors/ForceTouchSensor/ForceTouchSensor.js:204
- src/Droppable/DroppableEvent/DroppableEvent.ts:3 · src/Plugins/Collidable/CollidableEvent/CollidableEvent.ts:3 · src/Sortable/SortableEvent/SortableEvent.ts:10 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/Droppable/DroppableEvent/DroppableEvent.ts:3
- src/Draggable/Draggable.js:223 · src/Draggable/Draggable.js:260 — 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. — src/Draggable/Draggable.js:223
- src/Droppable/DroppableEvent/DroppableEvent.ts:3 · src/Plugins/Collidable/CollidableEvent/CollidableEvent.ts:3 · src/Sortable/SortableEvent/SortableEvent.ts:10 · src/Swappable/SwappableEvent/SwappableEvent.ts:3 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/Droppable/DroppableEvent/DroppableEvent.ts:3
- src/Sortable/SortableEvent/SortableEvent.ts:148 · src/Sortable/SortableEvent/SortableEvent.ts:205 — all 2 copies are in the same file, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — src/Sortable/SortableEvent/SortableEvent.ts:148
- src/Draggable/Plugins/Scrollable/Scrollable.js:79 · src/Droppable/Droppable.js:118 — the two spans are one implementation copied and then locally edited — 113 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. — src/Draggable/Plugins/Scrollable/Scrollable.js:79
- src/Droppable/Droppable.js:111 · src/Swappable/Swappable.js:61 — 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. — src/Droppable/Droppable.js:111
- src/Plugins/Snappable/Snappable.js:116 · src/Plugins/Snappable/Snappable.js:156 — 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. — src/Plugins/Snappable/Snappable.js:116
- src/Draggable/Sensors/DragSensor/DragSensor.js:125 · src/Draggable/Sensors/DragSensor/DragSensor.js:156 — 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. — src/Draggable/Sensors/DragSensor/DragSensor.js:125
- src/Droppable/Droppable.js:120 · src/Plugins/Collidable/Collidable.js:44 — the two spans are one implementation copied and then locally edited — 76 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/Droppable/Droppable.js:120
- src/Plugins/Snappable/Snappable.js:52 · src/Plugins/Snappable/Snappable.js:67 — 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. — src/Plugins/Snappable/Snappable.js:52
- src/Draggable/Draggable.js:171 · src/Draggable/Draggable.js:201 — 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. — src/Draggable/Draggable.js:171
- src/Draggable/Sensors/DragSensor/DragSensor.js:226 · src/Draggable/Sensors/DragSensor/DragSensor.js:257 — 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. — src/Draggable/Sensors/DragSensor/DragSensor.js:226
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.
R2 · Cyclomatic Complexity
- (anonymous) has cyclomatic complexity 16 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:528
- (computed) has cyclomatic complexity 15 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/Draggable/Plugins/Scrollable/Scrollable.js:209
- (computed) has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/Draggable/Draggable.js:502
R3 · Large Files
- src/Draggable/Draggable.js has 632 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/Draggable/Draggable.js:1
- REDACTED has 528 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED: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. (×11) — src/Plugins/Snappable/Snappable.js:1, src/Plugins/Collidable/Collidable.js:1, src/Plugins/SortAnimation/SortAnimation.js:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
R7 · Dead Code
R8 · Dependency Hygiene
R9 · Circular Imports
X12 · Unreachable branch
X16 · Unfloored truncation loop
X3 · Exception handling
X5 · Nullable reference types
- This repository commits no tsconfig, so whatever type-checks it uses tsc's own defaults, in which `strict` and `strictNullChecks` are OFF: `string` admits `null` and `undefined`, and a value that is null is compiled through to the property access that throws. If the build passes `--strict` on a command line instead, put it in a committed tsconfig — this check reads configuration, and configuration is all it can read.
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 `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 58% | Adequate — gated by R10, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 99% | Exemplary | Strongest area. |
| Maturity | 59% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 68% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 59% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 77 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- 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
- AX6 Interface segregation — no exported interface declares behaviour
- 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 start`) 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: "> @shopify/draggable@1.2.1 start / > concurrently "yarn watch" "cd examples && yarn && yarn start" / [0] /bin/sh: 1: yarn: not found / [1] /bin/sh: 1: yarn: not found / [1] cd examples && yarn && yarn start exited with code 127 / [0] yarn watch exited with code 127" 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.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (941 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (20 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (5958 LoC, 89 module-visible types across 35 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- 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) — 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.
- 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, .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.
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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
- 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 — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JavaScript/TypeScript source (1 module(s), 77 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 35 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a 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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: 77 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — 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.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- X7 Silent fallback defaults — 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 — 80 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 102 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No test reaches this file src/Plugins/Snappable/Snappable.js:1
- No test reaches this file src/Plugins/Collidable/Collidable.js:1
- No test reaches this file src/Plugins/SortAnimation/SortAnimation.js:1
- No test reaches this file src/Plugins/SwapAnimation/SwapAnimation.ts:1
- No test reaches this file src/Plugins/Collidable/CollidableEvent/CollidableEvent.ts:1
- No test reaches this file src/Plugins/Snappable/SnappableEvent/SnappableEvent.ts:1
- No test reaches this file src/index.js:1
- No test reaches this file src/Plugins/Collidable/index.js:1
- No test reaches this file src/Plugins/Snappable/index.js:1
- No test reaches this file src/Plugins/SortAnimation/index.js:1
- No test reaches this file src/Plugins/SwapAnimation/index.ts:1
- Low coverage: src/Draggable/Sensors/ForceTouchSensor/ForceTouchSensor.js src/Draggable/Sensors/ForceTouchSensor/ForceTouchSensor.js:1
- Low coverage: src/Plugins/Collidable/Collidable.js src/Plugins/Collidable/Collidable.js:1
- Low coverage: src/Plugins/Collidable/CollidableEvent/CollidableEvent.ts src/Plugins/Collidable/CollidableEvent/CollidableEvent.ts:1
- Low coverage: src/Plugins/Snappable/Snappable.js src/Plugins/Snappable/Snappable.js:1
- Low coverage: src/Plugins/Snappable/SnappableEvent/SnappableEvent.ts src/Plugins/Snappable/SnappableEvent/SnappableEvent.ts:1
- Low coverage: src/Plugins/SortAnimation/SortAnimation.js src/Plugins/SortAnimation/SortAnimation.js:1
- Low coverage: src/Plugins/SwapAnimation/SwapAnimation.ts src/Plugins/SwapAnimation/SwapAnimation.ts:1
- Low coverage: src/Sortable/SortableEvent/SortableEvent.ts src/Sortable/SortableEvent/SortableEvent.ts:1
- Low coverage: src/shared/AbstractPlugin/AbstractPlugin.ts src/shared/AbstractPlugin/AbstractPlugin.ts:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Skipped test: should set containers src/Draggable/tests/Draggable.test.js:80
- Skipped test: should set single container if a list is not passed src/Draggable/tests/Draggable.test.js:88
- Skipped test: mousedown handler adds draggable attribute src/Draggable/Sensors/DragSensor/tests/DragSensor.test.js:57
- REDACTED
- REDACTED
- Duplicated block (12 lines × 2 locations) src/Droppable/Droppable.js:111
- Duplicated block (12 lines × 2 locations) src/Plugins/Snappable/Snappable.js:116
- Duplicated block (5 lines × 2 locations) src/Draggable/Draggable.js:171
- Duplicated block (5 lines × 2 locations) src/Draggable/Sensors/DragSensor/DragSensor.js:226
- Mirror.positionMirror.<returned closure> (cyclomatic 16) REDACTED:513
- positionMirror (cyclomatic 16) REDACTED:512
- Deprecated: eslint package.json:70
- Mirror.positionMirror.<returned closure> (cognitive 19) REDACTED:513
- positionMirror (cognitive 19) REDACTED:512
- Scrollable.[scroll] (cognitive 18) src/Draggable/Plugins/Scrollable/Scrollable.js:209
- (computed) (cognitive 18) src/Draggable/Plugins/Scrollable/Scrollable.js:209
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- End-of-life runtime: Node.js 20 .nvmrc:1
- Type Safety
- Duplication concentrated across 5 sibling directories (13 clone groups) src/Droppable/DroppableEvent/DroppableEvent.ts:5
- Duplicated block with local edits (68 matched lines × 2 locations) src/Draggable/Sensors/MouseSensor/MouseSensor.js:86
- Duplicated block with local edits (28 matched lines × 2 locations) REDACTED:46
- Duplicated block (23 lines × 2 locations) src/Draggable/Sensors/ForceTouchSensor/ForceTouchSensor.js:53
- Duplicated block (22 lines × 2 locations) src/Sortable/Sortable.js:175
- Duplicated block with local edits (19 matched lines × 2 locations) src/Draggable/Plugins/Announcement/Announcement.js:29
- Duplicated block with local edits (17 matched lines × 2 locations) src/Draggable/Draggable.js:459
- Duplicated block (17 lines × 2 locations) src/Draggable/Sensors/ForceTouchSensor/ForceTouchSensor.js:204
- Duplicated block (17 lines × 3 locations) src/Droppable/DroppableEvent/DroppableEvent.ts:3
- Duplicated block (16 lines × 2 locations) src/Draggable/Draggable.js:223
- Duplicated block (15 lines × 4 locations) src/Droppable/DroppableEvent/DroppableEvent.ts:3
- Duplicated block (14 lines × 2 locations) src/Sortable/SortableEvent/SortableEvent.ts:148
- Duplicated block with local edits (12 matched lines × 2 locations) src/Draggable/Plugins/Scrollable/Scrollable.js:79
- Duplicated block (10 lines × 2 locations) src/Draggable/Sensors/DragSensor/DragSensor.js:125
- Duplicated block with local edits (10 matched lines × 2 locations) src/Droppable/Droppable.js:120
- Duplicated block (6 lines × 2 locations) src/Plugins/Snappable/Snappable.js:52
- Complex function (anonymous) (cyclomatic 16, cognitive 19) REDACTED:528
- Complex function (computed) (cyclomatic 15, cognitive 18) src/Draggable/Plugins/Scrollable/Scrollable.js:209
- Complex function (computed) (cyclomatic 13, cognitive 11) src/Draggable/Draggable.js:502
- src/Draggable/Draggable.js: 632 lines of code src/Draggable/Draggable.js:1
- REDACTED: 528 lines of code REDACTED:1
Minor — 70 finding(s)
- Orphaned file REDACTED:1
- Orphaned file src/Draggable/Plugins/Scrollable/Scrollable.js:1
- Orphaned file src/Sortable/Sortable.js:1
- Orphaned file src/Droppable/Droppable.js:1
- Orphaned file src/Draggable/Sensors/TouchSensor/TouchSensor.js:1
- Orphaned file src/Draggable/Sensors/DragSensor/DragSensor.js:1
- Orphaned file src/Draggable/Sensors/MouseSensor/MouseSensor.js:1
- Orphaned file src/Draggable/Sensors/ForceTouchSensor/ForceTouchSensor.js:1
- Orphaned file src/Draggable/DragEvent/DragEvent.ts:1
- Orphaned file src/Draggable/Plugins/Mirror/MirrorEvent/MirrorEvent.ts:1
- Orphaned file src/Sortable/SortableEvent/SortableEvent.ts:1
- Orphaned file src/Plugins/Collidable/Collidable.js:1
- Orphaned file src/Plugins/Snappable/Snappable.js:1
- Orphaned file src/Swappable/Swappable.js:1
- Orphaned file src/Plugins/SortAnimation/SortAnimation.js:1
- Orphaned file src/Plugins/SwapAnimation/SwapAnimation.ts:1
- Orphaned file src/Plugins/ResizeMirror/ResizeMirror.ts:1
- Orphaned file src/Draggable/Plugins/Announcement/Announcement.js:1
- Orphaned file src/Draggable/Sensors/Sensor/Sensor.js:1
- Orphaned file src/Draggable/Plugins/Focusable/Focusable.js:1
- Orphaned file src/Droppable/DroppableEvent/DroppableEvent.ts:1
- Orphaned file src/Swappable/SwappableEvent/SwappableEvent.ts:1
- Orphaned file src/Draggable/Sensors/SensorEvent/SensorEvent.ts:1
- Deprecated: @humanwhocodes/config-array REDACTED:1272
- Deprecated: @humanwhocodes/object-schema REDACTED:1286
- Deprecated: abab REDACTED:1988
- Deprecated: abab REDACTED:1993
- Deprecated: core-js REDACTED:2858
- Deprecated: domexception REDACTED:3189
- Deprecated: glob REDACTED:4168
- Deprecated: glob REDACTED:4180
- Deprecated: har-validator REDACTED:4254
- Deprecated: inflight REDACTED:4467
- Deprecated: lodash.pick REDACTED:5564
- Deprecated: request REDACTED:6498
- Deprecated: rimraf REDACTED:6584
- Deprecated: sourcemap-codec REDACTED:6814
- Deprecated: uuid REDACTED:7425
- Deprecated: whatwg-encoding REDACTED:7492
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Mock-dominated test: triggers events src/Swappable/tests/Swappable.test.js:70
- Mock-dominated test: triggers events src/Sortable/tests/Sortable.test.js:70
- Mock-dominated test: catches errors from listeners and re-throws at the end of the trigger phase src/Draggable/Emitter/tests/Emitter.test.ts:59
- Disabled test src/Draggable/Sensors/DragSensor/tests/DragSensor.test.js:57
- Disabled test src/Draggable/tests/Draggable.test.js:80
- Disabled test src/Draggable/tests/Draggable.test.js:88
- Duplicated predicate src/Draggable/Sensors/MouseSensor/MouseSensor.js:93
- Duplicated predicate src/Draggable/Draggable.js:431
- No ADRs found package.json:31
- Dormant codebase
- Most significant orphaned file src/Draggable/Draggable.js:1
- REDACTED
- No ADRs
- No SAST REDACTED:4
- Dependabot does not watch npm REDACTED:2
- No release approval gate
- Strict null checking is not enabled everywhere the repository type-checks
Minor — 1 finding(s)
- Outdated (npm): core-js
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8b79d751c30e4113bdaac6990a5a682d/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8b79d751c30e4113bdaac6990a5a682d/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 18 | 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/** . | 115 | 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. | 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 |