Executive summary
creativescala/doodle falls short of our standard for a preview release, in part because 92 files are no longer known to anyone active in the project. It scores 59 out of 100 and is rated Adequate, and all 24 of its critical findings are security problems in the build pipeline and in the packages it uses.
Maturity, at 54, is the weakest lens and counts most in the score. The best first step is having someone learn and document the 92 files no active contributor knows, worth about 5 points. Recording design decisions comes next, worth about 3 points. Raising Maturity to 62 would lift the score to about 61.
Nineteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three known security holes in the packages the code depends on can be used by attackers, and one secret can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting the secret to its own step would close these risks. Correcting the flagged pipeline settings would fix the weakness in the build pipeline's configuration.
The product code is 24,059 lines, about €29,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Maturity rose from 54 to 62, the lowest score rated Strong, the score would rise from 59 to about 61.
New since the last survey: 2 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 1 finding
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Rebuild cost: about €29,000 · Estimate
| Cost to rebuild | €9,700 to €49,000, for 162 to 514 hours of work, about 0.2 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 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 24,059 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 core.font | 2 core.format | 3 algebra.generic.GenericBlend | 4 algebra.generic.GenericShape | 5 algebra.generic.GenericText | 6 core | 7 algebra | 8 core.Gradient | 9 algebra.generic.GenericPath | 10 effect | 11 image | 12 interact.algebra | 13 language | 14 algebra.generic | 15 image.Image.Elements | 16 interact.effect | 17 canvas.algebra | 18 canvas.effect | 19 java2d.algebra.reified | 20 svg.algebra.AlgebraModule | 21 canvas.algebra.CanvasBlend | 22 canvas.algebra.Path | 23 canvas.algebra.Shape | 24 canvas.algebra.Text | 25 interact.animation | 26 interact.syntax.AbstractAnimationRendererSyntax | 27 interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps | 28 interact.syntax.MouseClickSyntax | 29 java2d | 30 java2d.algebra | 31 java2d.algebra.reified.Reified | 32 java2d.algebra.reified.ReifiedPath | 33 java2d.effect | 34 reactor | 35 svg.algebra | 36 svg.algebra.JsAlgebraModule | 37 svg.algebra.JvmAlgebraModule | 38 svg.algebra.SvgModule | 39 svg.effect | 40 doodle |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 core.font | ||||||||||||||||||||||||||||||||||||||||
| 2 core.format | ||||||||||||||||||||||||||||||||||||||||
| 3 algebra.generic.GenericBlend | 2 | |||||||||||||||||||||||||||||||||||||||
| 4 algebra.generic.GenericShape | 2 | |||||||||||||||||||||||||||||||||||||||
| 5 algebra.generic.GenericText | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 6 core | 2 | |||||||||||||||||||||||||||||||||||||||
| 7 algebra | 1 | 6 | 26 | |||||||||||||||||||||||||||||||||||||
| 8 core.Gradient | 4 | |||||||||||||||||||||||||||||||||||||||
| 9 algebra.generic.GenericPath | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 10 effect | 4 | 6 | ||||||||||||||||||||||||||||||||||||||
| 11 image | 8 | 3 | ||||||||||||||||||||||||||||||||||||||
| 12 interact.algebra | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 13 language | 9 | |||||||||||||||||||||||||||||||||||||||
| 14 algebra.generic | 2 | 1 | 1 | 1 | 18 | 9 | 1 | |||||||||||||||||||||||||||||||||
| 15 image.Image.Elements | 10 | 1 | 26 | |||||||||||||||||||||||||||||||||||||
| 16 interact.effect | 2 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 17 canvas.algebra | 2 | 6 | 1 | 11 | ||||||||||||||||||||||||||||||||||||
| 18 canvas.effect | 3 | 5 | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 19 java2d.algebra.reified | 1 | 2 | 2 | 5 | ||||||||||||||||||||||||||||||||||||
| 20 svg.algebra.AlgebraModule | 8 | 1 | 1 | 7 | ||||||||||||||||||||||||||||||||||||
| 21 canvas.algebra.CanvasBlend | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 canvas.algebra.Path | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 23 canvas.algebra.Shape | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 canvas.algebra.Text | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 interact.animation | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 26 interact.syntax.AbstractAnimationRendererSyntax | 1 | 2 | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||||
| 27 interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 28 interact.syntax.MouseClickSyntax | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 java2d | 4 | 1 | 3 | 5 | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||
| 30 java2d.algebra | 2 | 3 | 8 | 7 | 3 | 3 | 1 | 12 | 1 | 5 | ||||||||||||||||||||||||||||||
| 31 java2d.algebra.reified.Reified | 1 | 6 | 12 | 12 | ||||||||||||||||||||||||||||||||||||
| 32 java2d.algebra.reified.ReifiedPath | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 33 java2d.effect | 5 | 15 | 6 | 1 | 2 | 11 | 2 | |||||||||||||||||||||||||||||||||
| 34 reactor | 2 | 1 | 3 | 2 | 1 | 4 | ||||||||||||||||||||||||||||||||||
| 35 svg.algebra | 1 | 1 | 4 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 36 svg.algebra.JsAlgebraModule | 1 | 3 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 37 svg.algebra.JvmAlgebraModule | 1 | 3 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 38 svg.algebra.SvgModule | 1 | 5 | 3 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 39 svg.effect | 1 | 3 | 8 | 4 | 1 | 6 | ||||||||||||||||||||||||||||||||||
| 40 doodle | 1 | 1 | 1 | 1 | 2 | 1 |
3→14 algebra.generic.GenericBlend uses algebra.generic part of a loop✕
- Connections
- 2 pairs of types, where a type in algebra.generic.GenericBlend uses a type in algebra.generic.
- The types involved
doodle.algebra.generic.GenericBlend.BlendApi→doodle.algebra.generic.BlendModedoodle.algebra.generic.GenericBlend.BlendApi→doodle.algebra.generic.Finalized
- Direction
- algebra.generic.GenericBlend uses algebra.generic, so a change to algebra.generic can break algebra.generic.GenericBlend, while a change to algebra.generic.GenericBlend can't break algebra.generic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→14 algebra.generic.GenericShape uses algebra.generic part of a loop✕
- Connections
- 2 pairs of types, where a type in algebra.generic.GenericShape uses a type in algebra.generic.
- The types involved
doodle.algebra.generic.GenericShape.ShapeApi→doodle.algebra.generic.Filldoodle.algebra.generic.GenericShape.ShapeApi→doodle.algebra.generic.Stroke
- Direction
- algebra.generic.GenericShape uses algebra.generic, so a change to algebra.generic can break algebra.generic.GenericShape, while a change to algebra.generic.GenericShape can't break algebra.generic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→1 algebra.generic.GenericText uses core.font✕
- Connections
- 1 pair of types, where a type in algebra.generic.GenericText uses a type in core.font.
- The types involved
doodle.algebra.generic.GenericText.TextApi→doodle.core.font.Font
- Direction
- algebra.generic.GenericText uses core.font, so a change to core.font can break algebra.generic.GenericText, while a change to algebra.generic.GenericText can't break core.font.
- Position
- Below the diagonal: algebra.generic.GenericText uses a module listed above it, which is the healthy direction.
5→14 algebra.generic.GenericText uses algebra.generic part of a loop✕
- Connections
- 2 pairs of types, where a type in algebra.generic.GenericText uses a type in algebra.generic.
- The types involved
doodle.algebra.generic.GenericText.TextApi→doodle.algebra.generic.Filldoodle.algebra.generic.GenericText.TextApi→doodle.algebra.generic.Stroke
- Direction
- algebra.generic.GenericText uses algebra.generic, so a change to algebra.generic can break algebra.generic.GenericText, while a change to algebra.generic.GenericText can't break algebra.generic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→7 core uses algebra part of a loop✕
- Connections
- 2 pairs of types, where a type in core uses a type in algebra.
- The types involved
doodle.core.BoundingBox→doodle.algebra.Transformdoodle.core.Transform→doodle.algebra.Transform
- Direction
- core uses algebra, so a change to algebra can break core, while a change to core can't break algebra.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→1 algebra uses core.font✕
- Connections
- 1 pair of types, where a type in algebra uses a type in core.font.
- The types involved
doodle.algebra.Text→doodle.core.font.Font
- Direction
- algebra uses core.font, so a change to core.font can break algebra, while a change to algebra can't break core.font.
- Position
- Below the diagonal: algebra uses a module listed above it, which is the healthy direction.
7→2 algebra uses core.format✕
- Connections
- 6 pairs of types, where a type in algebra uses a type in core.format.
- The types involved
doodle.algebra.FromGifBase64→doodle.core.format.Gifdoodle.algebra.FromGifBase64Constructor→doodle.core.format.Gifdoodle.algebra.FromJpgBase64→doodle.core.format.Jpgdoodle.algebra.FromJpgBase64Constructor→doodle.core.format.Jpgdoodle.algebra.FromPngBase64→doodle.core.format.Pngdoodle.algebra.FromPngBase64Constructor→doodle.core.format.Png
- Direction
- algebra uses core.format, so a change to core.format can break algebra, while a change to algebra can't break core.format.
- Position
- Below the diagonal: algebra uses a module listed above it, which is the healthy direction.
7→6 algebra uses core✕
- Connections
- 26 pairs of types, where a type in algebra uses a type in core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
doodle.algebra.Debug→doodle.core.Colordoodle.algebra.Filter→doodle.core.Colordoodle.algebra.FromGifBase64→doodle.core.Base64doodle.algebra.FromGifBase64Constructor→doodle.core.Base64doodle.algebra.FromJpgBase64→doodle.core.Base64doodle.algebra.FromJpgBase64Constructor→doodle.core.Base64doodle.algebra.FromPngBase64→doodle.core.Base64doodle.algebra.FromPngBase64Constructor→doodle.core.Base64doodle.algebra.Layout→doodle.core.Angledoodle.algebra.Layout→doodle.core.Landmarkdoodle.algebra.Layout→doodle.core.Pointdoodle.algebra.Layout→doodle.core.Vecdoodle.algebra.Path→doodle.core.ClosedPathdoodle.algebra.Path→doodle.core.OpenPathdoodle.algebra.Path→doodle.core.Pointdoodle.algebra.PathConstructor→doodle.core.Angledoodle.algebra.PathConstructor→doodle.core.ClosedPathdoodle.algebra.PathConstructor→doodle.core.OpenPathdoodle.algebra.PathConstructor→doodle.core.Pointdoodle.algebra.Size→doodle.core.BoundingBoxdoodle.algebra.Style→doodle.core.Capdoodle.algebra.Style→doodle.core.Colordoodle.algebra.Style→doodle.core.Gradientdoodle.algebra.Style→doodle.core.Joindoodle.algebra.Transform→doodle.core.Angle
- Direction
- algebra uses core, so a change to core can break algebra, while a change to algebra can't break core.
- Position
- Below the diagonal: algebra uses a module listed above it, which is the healthy direction.
8→6 core.Gradient uses core✕
- Connections
- 4 pairs of types, where a type in core.Gradient uses a type in core.
- The types involved
doodle.core.Gradient.Linear→doodle.core.Gradientdoodle.core.Gradient.Linear→doodle.core.Pointdoodle.core.Gradient.Radial→doodle.core.Gradientdoodle.core.Gradient.Radial→doodle.core.Point
- Direction
- core.Gradient uses core, so a change to core can break core.Gradient, while a change to core.Gradient can't break core.
- Position
- Below the diagonal: core.Gradient uses a module listed above it, which is the healthy direction.
9→6 algebra.generic.GenericPath uses core✕
- Connections
- 1 pair of types, where a type in algebra.generic.GenericPath uses a type in core.
- The types involved
doodle.algebra.generic.GenericPath.PathApi→doodle.core.PathElement
- Direction
- algebra.generic.GenericPath uses core, so a change to core can break algebra.generic.GenericPath, while a change to algebra.generic.GenericPath can't break core.
- Position
- Below the diagonal: algebra.generic.GenericPath uses a module listed above it, which is the healthy direction.
9→7 algebra.generic.GenericPath uses algebra✕
- Connections
- 1 pair of types, where a type in algebra.generic.GenericPath uses a type in algebra.
- The types involved
doodle.algebra.generic.GenericPath.PathApi→doodle.algebra.Transform
- Direction
- algebra.generic.GenericPath uses algebra, so a change to algebra can break algebra.generic.GenericPath, while a change to algebra.generic.GenericPath can't break algebra.
- Position
- Below the diagonal: algebra.generic.GenericPath uses a module listed above it, which is the healthy direction.
9→14 algebra.generic.GenericPath uses algebra.generic part of a loop✕
- Connections
- 2 pairs of types, where a type in algebra.generic.GenericPath uses a type in algebra.generic.
- The types involved
doodle.algebra.generic.GenericPath.PathApi→doodle.algebra.generic.Filldoodle.algebra.generic.GenericPath.PathApi→doodle.algebra.generic.Stroke
- Direction
- algebra.generic.GenericPath uses algebra.generic, so a change to algebra.generic can break algebra.generic.GenericPath, while a change to algebra.generic.GenericPath can't break algebra.generic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→7 effect uses algebra✕
- Connections
- 4 pairs of types, where a type in effect uses a type in algebra.
- The types involved
doodle.effect.Base64Writer→doodle.algebra.Picturedoodle.effect.BufferedImageWriter→doodle.algebra.Picturedoodle.effect.FileWriter→doodle.algebra.Picturedoodle.effect.Renderer→doodle.algebra.Picture
- Direction
- effect uses algebra, so a change to algebra can break effect, while a change to effect can't break algebra.
- Position
- Below the diagonal: effect uses a module listed above it, which is the healthy direction.
10→18 effect uses canvas.effect part of a loop✕
- Connections
- 6 pairs of types, where a type in effect uses a type in canvas.effect.
- The types involved
doodle.effect.Base64Writer→doodle.canvas.effect.Framedoodle.effect.BufferedImageWriter→doodle.canvas.effect.Framedoodle.effect.DefaultFrame→doodle.canvas.effect.Framedoodle.effect.FileWriter→doodle.canvas.effect.Framedoodle.effect.Renderer→doodle.canvas.effect.Canvasdoodle.effect.Renderer→doodle.canvas.effect.Frame
- Direction
- effect uses canvas.effect, so a change to canvas.effect can break effect, while a change to effect can't break canvas.effect.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→6 image uses core✕
- Connections
- 8 pairs of types, where a type in image uses a type in core.
- The types involved
doodle.image.Image→doodle.core.Angledoodle.image.Image→doodle.core.Capdoodle.image.Image→doodle.core.Colordoodle.image.Image→doodle.core.Gradientdoodle.image.Image→doodle.core.Joindoodle.image.Image→doodle.core.Landmarkdoodle.image.Image→doodle.core.Pointdoodle.image.Image→doodle.core.Vec
- Direction
- image uses core, so a change to core can break image, while a change to image can't break core.
- Position
- Below the diagonal: image uses a module listed above it, which is the healthy direction.
11→7 image uses algebra✕
- Connections
- 3 pairs of types, where a type in image uses a type in algebra.
- The types involved
doodle.image.Image→doodle.algebra.Algebradoodle.image.Image→doodle.algebra.Picturedoodle.image.Image→doodle.algebra.Transform
- Direction
- image uses algebra, so a change to algebra can break image, while a change to image can't break algebra.
- Position
- Below the diagonal: image uses a module listed above it, which is the healthy direction.
12→6 interact.algebra uses core✕
- Connections
- 2 pairs of types, where a type in interact.algebra uses a type in core.
- The types involved
doodle.interact.algebra.MouseClick→doodle.core.Pointdoodle.interact.algebra.MouseMove→doodle.core.Point
- Direction
- interact.algebra uses core, so a change to core can break interact.algebra, while a change to interact.algebra can't break core.
- Position
- Below the diagonal: interact.algebra uses a module listed above it, which is the healthy direction.
12→7 interact.algebra uses algebra✕
- Connections
- 1 pair of types, where a type in interact.algebra uses a type in algebra.
- The types involved
doodle.interact.algebra.MouseOver→doodle.algebra.Algebra
- Direction
- interact.algebra uses algebra, so a change to algebra can break interact.algebra, while a change to interact.algebra can't break algebra.
- Position
- Below the diagonal: interact.algebra uses a module listed above it, which is the healthy direction.
12→18 interact.algebra uses canvas.effect part of a loop✕
- Connections
- 3 pairs of types, where a type in interact.algebra uses a type in canvas.effect.
- The types involved
doodle.interact.algebra.MouseClick→doodle.canvas.effect.Canvasdoodle.interact.algebra.MouseMove→doodle.canvas.effect.Canvasdoodle.interact.algebra.Redraw→doodle.canvas.effect.Canvas
- Direction
- interact.algebra uses canvas.effect, so a change to canvas.effect can break interact.algebra, while a change to interact.algebra can't break canvas.effect.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→7 language uses algebra✕
- Connections
- 9 pairs of types, where a type in language uses a type in algebra.
- The types involved
doodle.language.Basic→doodle.algebra.Algebradoodle.language.Basic→doodle.algebra.Debugdoodle.language.Basic→doodle.algebra.Layoutdoodle.language.Basic→doodle.algebra.Pathdoodle.language.Basic→doodle.algebra.Shapedoodle.language.Basic→doodle.algebra.Sizedoodle.language.Basic→doodle.algebra.Styledoodle.language.Basic→doodle.algebra.Textdoodle.language.Basic→doodle.algebra.Transform
- Direction
- language uses algebra, so a change to algebra can break language, while a change to language can't break algebra.
- Position
- Below the diagonal: language uses a module listed above it, which is the healthy direction.
14→1 algebra.generic uses core.font✕
- Connections
- 2 pairs of types, where a type in algebra.generic uses a type in core.font.
- The types involved
doodle.algebra.generic.DrawingContext→doodle.core.font.Fontdoodle.algebra.generic.GenericText→doodle.core.font.Font
- Direction
- algebra.generic uses core.font, so a change to core.font can break algebra.generic, while a change to algebra.generic can't break core.font.
- Position
- Below the diagonal: algebra.generic uses a module listed above it, which is the healthy direction.
14→3 algebra.generic uses algebra.generic.GenericBlend✕
- Connections
- 1 pair of types, where a type in algebra.generic uses a type in algebra.generic.GenericBlend.
- The types involved
doodle.algebra.generic.GenericBlend→doodle.algebra.generic.GenericBlend.BlendApi
- Direction
- algebra.generic uses algebra.generic.GenericBlend, so a change to algebra.generic.GenericBlend can break algebra.generic, while a change to algebra.generic can't break algebra.generic.GenericBlend.
- Position
- Below the diagonal: algebra.generic uses a module listed above it, which is the healthy direction.
14→4 algebra.generic uses algebra.generic.GenericShape✕
- Connections
- 1 pair of types, where a type in algebra.generic uses a type in algebra.generic.GenericShape.
- The types involved
doodle.algebra.generic.GenericShape→doodle.algebra.generic.GenericShape.ShapeApi
- Direction
- algebra.generic uses algebra.generic.GenericShape, so a change to algebra.generic.GenericShape can break algebra.generic, while a change to algebra.generic can't break algebra.generic.GenericShape.
- Position
- Below the diagonal: algebra.generic uses a module listed above it, which is the healthy direction.
14→5 algebra.generic uses algebra.generic.GenericText✕
- Connections
- 1 pair of types, where a type in algebra.generic uses a type in algebra.generic.GenericText.
- The types involved
doodle.algebra.generic.GenericText→doodle.algebra.generic.GenericText.TextApi
- Direction
- algebra.generic uses algebra.generic.GenericText, so a change to algebra.generic.GenericText can break algebra.generic, while a change to algebra.generic can't break algebra.generic.GenericText.
- Position
- Below the diagonal: algebra.generic uses a module listed above it, which is the healthy direction.
14→6 algebra.generic uses core✕
- Connections
- 18 pairs of types, where a type in algebra.generic uses a type in core.
- The types involved
doodle.algebra.generic.DrawingContext→doodle.core.Capdoodle.algebra.generic.DrawingContext→doodle.core.Colordoodle.algebra.generic.DrawingContext→doodle.core.Gradientdoodle.algebra.generic.DrawingContext→doodle.core.Joindoodle.algebra.generic.Finalized→doodle.core.BoundingBoxdoodle.algebra.generic.GenericDebug→doodle.core.Colordoodle.algebra.generic.GenericLayout→doodle.core.Landmarkdoodle.algebra.generic.GenericPath→doodle.core.BoundingBoxdoodle.algebra.generic.GenericPath→doodle.core.ClosedPathdoodle.algebra.generic.GenericPath→doodle.core.OpenPathdoodle.algebra.generic.GenericPath→doodle.core.PathElementdoodle.algebra.generic.GenericSize→doodle.core.BoundingBoxdoodle.algebra.generic.GenericStyle→doodle.core.Capdoodle.algebra.generic.GenericStyle→doodle.core.Colordoodle.algebra.generic.GenericStyle→doodle.core.Gradientdoodle.algebra.generic.GenericStyle→doodle.core.Joindoodle.algebra.generic.Stroke→doodle.core.Capdoodle.algebra.generic.Stroke→doodle.core.Join
- Direction
- algebra.generic uses core, so a change to core can break algebra.generic, while a change to algebra.generic can't break core.
- Position
- Below the diagonal: algebra.generic uses a module listed above it, which is the healthy direction.
14→7 algebra.generic uses algebra✕
- Connections
- 9 pairs of types, where a type in algebra.generic uses a type in algebra.
- The types involved
doodle.algebra.generic.GenericBlend→doodle.algebra.Blenddoodle.algebra.generic.GenericDebug→doodle.algebra.Debugdoodle.algebra.generic.GenericLayout→doodle.algebra.Layoutdoodle.algebra.generic.GenericPath→doodle.algebra.Pathdoodle.algebra.generic.GenericShape→doodle.algebra.Shapedoodle.algebra.generic.GenericSize→doodle.algebra.Sizedoodle.algebra.generic.GenericStyle→doodle.algebra.Styledoodle.algebra.generic.GenericText→doodle.algebra.Textdoodle.algebra.generic.GenericTransform→doodle.algebra.Transform
- Direction
- algebra.generic uses algebra, so a change to algebra can break algebra.generic, while a change to algebra.generic can't break algebra.
- Position
- Below the diagonal: algebra.generic uses a module listed above it, which is the healthy direction.
14→9 algebra.generic uses algebra.generic.GenericPath✕
- Connections
- 1 pair of types, where a type in algebra.generic uses a type in algebra.generic.GenericPath.
- The types involved
doodle.algebra.generic.GenericPath→doodle.algebra.generic.GenericPath.PathApi
- Direction
- algebra.generic uses algebra.generic.GenericPath, so a change to algebra.generic.GenericPath can break algebra.generic, while a change to algebra.generic can't break algebra.generic.GenericPath.
- Position
- Below the diagonal: algebra.generic uses a module listed above it, which is the healthy direction.
15→6 image.Image.Elements uses core✕
- Connections
- 10 pairs of types, where a type in image.Image.Elements uses a type in core.
- The types involved
doodle.image.Image.Elements.At→doodle.core.Landmarkdoodle.image.Image.Elements.ClosedPath→doodle.core.ClosedPathdoodle.image.Image.Elements.Debug→doodle.core.Colordoodle.image.Image.Elements.FillColor→doodle.core.Colordoodle.image.Image.Elements.FillGradient→doodle.core.Gradientdoodle.image.Image.Elements.OpenPath→doodle.core.OpenPathdoodle.image.Image.Elements.OriginAt→doodle.core.Landmarkdoodle.image.Image.Elements.StrokeCap→doodle.core.Capdoodle.image.Image.Elements.StrokeColor→doodle.core.Colordoodle.image.Image.Elements.StrokeJoin→doodle.core.Join
- Direction
- image.Image.Elements uses core, so a change to core can break image.Image.Elements, while a change to image.Image.Elements can't break core.
- Position
- Below the diagonal: image.Image.Elements uses a module listed above it, which is the healthy direction.
15→7 image.Image.Elements uses algebra✕
- Connections
- 1 pair of types, where a type in image.Image.Elements uses a type in algebra.
- The types involved
doodle.image.Image.Elements.Transform→doodle.algebra.Transform
- Direction
- image.Image.Elements uses algebra, so a change to algebra can break image.Image.Elements, while a change to image.Image.Elements can't break algebra.
- Position
- Below the diagonal: image.Image.Elements uses a module listed above it, which is the healthy direction.
15→11 image.Image.Elements uses image✕
- Connections
- 26 pairs of types, where a type in image.Image.Elements uses a type in image. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
doodle.image.Image.Elements.Above→doodle.image.Imagedoodle.image.Image.Elements.At→doodle.image.Imagedoodle.image.Image.Elements.Beside→doodle.image.Imagedoodle.image.Image.Elements.Circle→doodle.image.Imagedoodle.image.Image.Elements.ClosedPath→doodle.image.Imagedoodle.image.Image.Elements.Debug→doodle.image.Imagedoodle.image.Image.Elements.Empty→doodle.image.Imagedoodle.image.Image.Elements.FillColor→doodle.image.Imagedoodle.image.Image.Elements.FillGradient→doodle.image.Imagedoodle.image.Image.Elements.Font→doodle.image.Imagedoodle.image.Image.Elements.Margin→doodle.image.Imagedoodle.image.Image.Elements.NoFill→doodle.image.Imagedoodle.image.Image.Elements.NoStroke→doodle.image.Imagedoodle.image.Image.Elements.On→doodle.image.Imagedoodle.image.Image.Elements.OpenPath→doodle.image.Imagedoodle.image.Image.Elements.OriginAt→doodle.image.Imagedoodle.image.Image.Elements.Rectangle→doodle.image.Imagedoodle.image.Image.Elements.Size→doodle.image.Imagedoodle.image.Image.Elements.StrokeCap→doodle.image.Imagedoodle.image.Image.Elements.StrokeColor→doodle.image.Imagedoodle.image.Image.Elements.StrokeDash→doodle.image.Imagedoodle.image.Image.Elements.StrokeJoin→doodle.image.Imagedoodle.image.Image.Elements.StrokeWidth→doodle.image.Imagedoodle.image.Image.Elements.Text→doodle.image.Imagedoodle.image.Image.Elements.Transform→doodle.image.Image
- Direction
- image.Image.Elements uses image, so a change to image can break image.Image.Elements, while a change to image.Image.Elements can't break image.
- Position
- Below the diagonal: image.Image.Elements uses a module listed above it, which is the healthy direction.
16→7 interact.effect uses algebra✕
- Connections
- 2 pairs of types, where a type in interact.effect uses a type in algebra.
- The types involved
doodle.interact.effect.AnimationRenderer→doodle.algebra.Picturedoodle.interact.effect.AnimationWriter→doodle.algebra.Picture
- Direction
- interact.effect uses algebra, so a change to algebra can break interact.effect, while a change to interact.effect can't break algebra.
- Position
- Below the diagonal: interact.effect uses a module listed above it, which is the healthy direction.
16→10 interact.effect uses effect✕
- Connections
- 2 pairs of types, where a type in interact.effect uses a type in effect.
- The types involved
doodle.interact.effect.AnimationRenderer→doodle.effect.Rendererdoodle.interact.effect.AnimationWriter→doodle.effect.Writer
- Direction
- interact.effect uses effect, so a change to effect can break interact.effect, while a change to interact.effect can't break effect.
- Position
- Below the diagonal: interact.effect uses a module listed above it, which is the healthy direction.
16→18 interact.effect uses canvas.effect part of a loop✕
- Connections
- 3 pairs of types, where a type in interact.effect uses a type in canvas.effect.
- The types involved
doodle.interact.effect.AnimationRenderer→doodle.canvas.effect.Canvasdoodle.interact.effect.AnimationRenderer→doodle.canvas.effect.Framedoodle.interact.effect.AnimationWriter→doodle.canvas.effect.Frame
- Direction
- interact.effect uses canvas.effect, so a change to canvas.effect can break interact.effect, while a change to interact.effect can't break canvas.effect.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→1 canvas.algebra uses core.font✕
- Connections
- 2 pairs of types, where a type in canvas.algebra uses a type in core.font.
- The types involved
doodle.canvas.algebra.CanvasAlgebra→doodle.core.font.Fontdoodle.canvas.algebra.HasTextBoundingBox→doodle.core.font.Font
- Direction
- canvas.algebra uses core.font, so a change to core.font can break canvas.algebra, while a change to canvas.algebra can't break core.font.
- Position
- Below the diagonal: canvas.algebra uses a module listed above it, which is the healthy direction.
17→7 canvas.algebra uses algebra✕
- Connections
- 6 pairs of types, where a type in canvas.algebra uses a type in algebra.
- The types involved
doodle.canvas.algebra.CanvasAlgebra→doodle.algebra.Algebradoodle.canvas.algebra.CanvasAlgebra→doodle.algebra.Pathdoodle.canvas.algebra.CanvasAlgebra→doodle.algebra.Shapedoodle.canvas.algebra.CanvasAlgebra→doodle.algebra.Textdoodle.canvas.algebra.CanvasAlgebraFrom→doodle.algebra.Algebradoodle.canvas.algebra.CanvasLoadBitmap→doodle.algebra.LoadBitmap
- Direction
- canvas.algebra uses algebra, so a change to algebra can break canvas.algebra, while a change to canvas.algebra can't break algebra.
- Position
- Below the diagonal: canvas.algebra uses a module listed above it, which is the healthy direction.
17→13 canvas.algebra uses language✕
- Connections
- 1 pair of types, where a type in canvas.algebra uses a type in language.
- The types involved
doodle.canvas.algebra.CanvasAlgebra→doodle.language.Basic
- Direction
- canvas.algebra uses language, so a change to language can break canvas.algebra, while a change to canvas.algebra can't break language.
- Position
- Below the diagonal: canvas.algebra uses a module listed above it, which is the healthy direction.
17→14 canvas.algebra uses algebra.generic✕
- Connections
- 11 pairs of types, where a type in canvas.algebra uses a type in algebra.generic.
- The types involved
doodle.canvas.algebra.CanvasAlgebra→doodle.algebra.generic.GenericDebugdoodle.canvas.algebra.CanvasAlgebra→doodle.algebra.generic.GenericLayoutdoodle.canvas.algebra.CanvasAlgebra→doodle.algebra.generic.GenericSizedoodle.canvas.algebra.CanvasAlgebra→doodle.algebra.generic.GenericStyledoodle.canvas.algebra.CanvasAlgebra→doodle.algebra.generic.GenericTransformdoodle.canvas.algebra.CanvasAlgebra→doodle.algebra.generic.GivenApplydoodle.canvas.algebra.CanvasAlgebra→doodle.algebra.generic.GivenFunctordoodle.canvas.algebra.CanvasBlend→doodle.algebra.generic.GenericBlenddoodle.canvas.algebra.Path→doodle.algebra.generic.GenericPathdoodle.canvas.algebra.Shape→doodle.algebra.generic.GenericShapedoodle.canvas.algebra.Text→doodle.algebra.generic.GenericText
- Direction
- canvas.algebra uses algebra.generic, so a change to algebra.generic can break canvas.algebra, while a change to canvas.algebra can't break algebra.generic.
- Position
- Below the diagonal: canvas.algebra uses a module listed above it, which is the healthy direction.
18→6 canvas.effect uses core✕
- Connections
- 3 pairs of types, where a type in canvas.effect uses a type in core.
- The types involved
doodle.canvas.effect.Canvas→doodle.core.Pointdoodle.canvas.effect.CanvasAlgebra→doodle.core.Pointdoodle.canvas.effect.Frame→doodle.core.Color
- Direction
- canvas.effect uses core, so a change to core can break canvas.effect, while a change to canvas.effect can't break core.
- Position
- Below the diagonal: canvas.effect uses a module listed above it, which is the healthy direction.
18→7 canvas.effect uses algebra✕
- Connections
- 5 pairs of types, where a type in canvas.effect uses a type in algebra.
- The types involved
doodle.canvas.effect.Canvas→doodle.algebra.Picturedoodle.canvas.effect.Canvas→doodle.algebra.Transformdoodle.canvas.effect.CanvasAnimationRenderer→doodle.algebra.Picturedoodle.canvas.effect.CanvasRenderer→doodle.algebra.Picturedoodle.canvas.effect.Frame→doodle.algebra.Size
- Direction
- canvas.effect uses algebra, so a change to algebra can break canvas.effect, while a change to canvas.effect can't break algebra.
- Position
- Below the diagonal: canvas.effect uses a module listed above it, which is the healthy direction.
18→10 canvas.effect uses effect✕
- Connections
- 2 pairs of types, where a type in canvas.effect uses a type in effect.
- The types involved
doodle.canvas.effect.CanvasAnimationRenderer→doodle.effect.Rendererdoodle.canvas.effect.CanvasRenderer→doodle.effect.Renderer
- Direction
- canvas.effect uses effect, so a change to effect can break canvas.effect, while a change to canvas.effect can't break effect.
- Position
- Below the diagonal: canvas.effect uses a module listed above it, which is the healthy direction.
18→12 canvas.effect uses interact.algebra✕
- Connections
- 3 pairs of types, where a type in canvas.effect uses a type in interact.algebra.
- The types involved
doodle.canvas.effect.CanvasAlgebra→doodle.interact.algebra.MouseClickdoodle.canvas.effect.CanvasAlgebra→doodle.interact.algebra.MouseMovedoodle.canvas.effect.CanvasAlgebra→doodle.interact.algebra.Redraw
- Direction
- canvas.effect uses interact.algebra, so a change to interact.algebra can break canvas.effect, while a change to canvas.effect can't break interact.algebra.
- Position
- Below the diagonal: canvas.effect uses a module listed above it, which is the healthy direction.
18→16 canvas.effect uses interact.effect✕
- Connections
- 1 pair of types, where a type in canvas.effect uses a type in interact.effect.
- The types involved
doodle.canvas.effect.CanvasAnimationRenderer→doodle.interact.effect.AnimationRenderer
- Direction
- canvas.effect uses interact.effect, so a change to interact.effect can break canvas.effect, while a change to canvas.effect can't break interact.effect.
- Position
- Below the diagonal: canvas.effect uses a module listed above it, which is the healthy direction.
19→1 java2d.algebra.reified uses core.font✕
- Connections
- 1 pair of types, where a type in java2d.algebra.reified uses a type in core.font.
- The types involved
doodle.java2d.algebra.reified.GraphicsContext→doodle.core.font.Font
- Direction
- java2d.algebra.reified uses core.font, so a change to core.font can break java2d.algebra.reified, while a change to java2d.algebra.reified can't break core.font.
- Position
- Below the diagonal: java2d.algebra.reified uses a module listed above it, which is the healthy direction.
19→6 java2d.algebra.reified uses core✕
- Connections
- 2 pairs of types, where a type in java2d.algebra.reified uses a type in core.
- The types involved
doodle.java2d.algebra.reified.GraphicsContext→doodle.core.PathElementdoodle.java2d.algebra.reified.GraphicsContext→doodle.core.Point
- Direction
- java2d.algebra.reified uses core, so a change to core can break java2d.algebra.reified, while a change to java2d.algebra.reified can't break core.
- Position
- Below the diagonal: java2d.algebra.reified uses a module listed above it, which is the healthy direction.
19→7 java2d.algebra.reified uses algebra✕
- Connections
- 2 pairs of types, where a type in java2d.algebra.reified uses a type in algebra.
- The types involved
doodle.java2d.algebra.reified.GraphicsContext→doodle.algebra.Transformdoodle.java2d.algebra.reified.ReifiedBitmap→doodle.algebra.Bitmap
- Direction
- java2d.algebra.reified uses algebra, so a change to algebra can break java2d.algebra.reified, while a change to java2d.algebra.reified can't break algebra.
- Position
- Below the diagonal: java2d.algebra.reified uses a module listed above it, which is the healthy direction.
19→14 java2d.algebra.reified uses algebra.generic✕
- Connections
- 5 pairs of types, where a type in java2d.algebra.reified uses a type in algebra.generic.
- The types involved
doodle.java2d.algebra.reified.GraphicsContext→doodle.algebra.generic.Filldoodle.java2d.algebra.reified.GraphicsContext→doodle.algebra.generic.Strokedoodle.java2d.algebra.reified.ReifiedPath→doodle.algebra.generic.GenericPathdoodle.java2d.algebra.reified.ReifiedShape→doodle.algebra.generic.GenericShapedoodle.java2d.algebra.reified.ReifiedText→doodle.algebra.generic.GenericText
- Direction
- java2d.algebra.reified uses algebra.generic, so a change to algebra.generic can break java2d.algebra.reified, while a change to java2d.algebra.reified can't break algebra.generic.
- Position
- Below the diagonal: java2d.algebra.reified uses a module listed above it, which is the healthy direction.
20→7 svg.algebra.AlgebraModule uses algebra✕
- Connections
- 8 pairs of types, where a type in svg.algebra.AlgebraModule uses a type in algebra.
- The types involved
doodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.algebra.Algebradoodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.algebra.Blenddoodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.algebra.Filterdoodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.algebra.Layoutdoodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.algebra.Pathdoodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.algebra.Shapedoodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.algebra.Sizedoodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.algebra.Text
- Direction
- svg.algebra.AlgebraModule uses algebra, so a change to algebra can break svg.algebra.AlgebraModule, while a change to svg.algebra.AlgebraModule can't break algebra.
- Position
- Below the diagonal: svg.algebra.AlgebraModule uses a module listed above it, which is the healthy direction.
20→11 svg.algebra.AlgebraModule uses image✕
- Connections
- 1 pair of types, where a type in svg.algebra.AlgebraModule uses a type in image.
- The types involved
doodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.image.Image
- Direction
- svg.algebra.AlgebraModule uses image, so a change to image can break svg.algebra.AlgebraModule, while a change to svg.algebra.AlgebraModule can't break image.
- Position
- Below the diagonal: svg.algebra.AlgebraModule uses a module listed above it, which is the healthy direction.
20→13 svg.algebra.AlgebraModule uses language✕
- Connections
- 1 pair of types, where a type in svg.algebra.AlgebraModule uses a type in language.
- The types involved
doodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.language.Basic
- Direction
- svg.algebra.AlgebraModule uses language, so a change to language can break svg.algebra.AlgebraModule, while a change to svg.algebra.AlgebraModule can't break language.
- Position
- Below the diagonal: svg.algebra.AlgebraModule uses a module listed above it, which is the healthy direction.
20→14 svg.algebra.AlgebraModule uses algebra.generic✕
- Connections
- 7 pairs of types, where a type in svg.algebra.AlgebraModule uses a type in algebra.generic.
- The types involved
doodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.algebra.generic.GenericDebugdoodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.algebra.generic.GenericLayoutdoodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.algebra.generic.GenericSizedoodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.algebra.generic.GenericStyledoodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.algebra.generic.GenericTransformdoodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.algebra.generic.GivenApplydoodle.svg.algebra.AlgebraModule.BaseAlgebra→doodle.algebra.generic.GivenFunctor
- Direction
- svg.algebra.AlgebraModule uses algebra.generic, so a change to algebra.generic can break svg.algebra.AlgebraModule, while a change to svg.algebra.AlgebraModule can't break algebra.generic.
- Position
- Below the diagonal: svg.algebra.AlgebraModule uses a module listed above it, which is the healthy direction.
21→3 canvas.algebra.CanvasBlend uses algebra.generic.GenericBlend✕
- Connections
- 1 pair of types, where a type in canvas.algebra.CanvasBlend uses a type in algebra.generic.GenericBlend.
- The types involved
doodle.canvas.algebra.CanvasBlend.BlendApi→doodle.algebra.generic.GenericBlend.BlendApi
- Direction
- canvas.algebra.CanvasBlend uses algebra.generic.GenericBlend, so a change to algebra.generic.GenericBlend can break canvas.algebra.CanvasBlend, while a change to canvas.algebra.CanvasBlend can't break algebra.generic.GenericBlend.
- Position
- Below the diagonal: canvas.algebra.CanvasBlend uses a module listed above it, which is the healthy direction.
21→14 canvas.algebra.CanvasBlend uses algebra.generic✕
- Connections
- 2 pairs of types, where a type in canvas.algebra.CanvasBlend uses a type in algebra.generic.
- The types involved
doodle.canvas.algebra.CanvasBlend.BlendApi→doodle.algebra.generic.BlendModedoodle.canvas.algebra.CanvasBlend.BlendApi→doodle.algebra.generic.Finalized
- Direction
- canvas.algebra.CanvasBlend uses algebra.generic, so a change to algebra.generic can break canvas.algebra.CanvasBlend, while a change to canvas.algebra.CanvasBlend can't break algebra.generic.
- Position
- Below the diagonal: canvas.algebra.CanvasBlend uses a module listed above it, which is the healthy direction.
21→17 canvas.algebra.CanvasBlend uses canvas.algebra✕
- Connections
- 1 pair of types, where a type in canvas.algebra.CanvasBlend uses a type in canvas.algebra.
- The types involved
doodle.canvas.algebra.CanvasBlend.BlendApi→doodle.canvas.algebra.CanvasDrawing
- Direction
- canvas.algebra.CanvasBlend uses canvas.algebra, so a change to canvas.algebra can break canvas.algebra.CanvasBlend, while a change to canvas.algebra.CanvasBlend can't break canvas.algebra.
- Position
- Below the diagonal: canvas.algebra.CanvasBlend uses a module listed above it, which is the healthy direction.
22→6 canvas.algebra.Path uses core✕
- Connections
- 1 pair of types, where a type in canvas.algebra.Path uses a type in core.
- The types involved
doodle.canvas.algebra.Path.PathApi→doodle.core.PathElement
- Direction
- canvas.algebra.Path uses core, so a change to core can break canvas.algebra.Path, while a change to canvas.algebra.Path can't break core.
- Position
- Below the diagonal: canvas.algebra.Path uses a module listed above it, which is the healthy direction.
22→7 canvas.algebra.Path uses algebra✕
- Connections
- 1 pair of types, where a type in canvas.algebra.Path uses a type in algebra.
- The types involved
doodle.canvas.algebra.Path.PathApi→doodle.algebra.Transform
- Direction
- canvas.algebra.Path uses algebra, so a change to algebra can break canvas.algebra.Path, while a change to canvas.algebra.Path can't break algebra.
- Position
- Below the diagonal: canvas.algebra.Path uses a module listed above it, which is the healthy direction.
22→9 canvas.algebra.Path uses algebra.generic.GenericPath✕
- Connections
- 1 pair of types, where a type in canvas.algebra.Path uses a type in algebra.generic.GenericPath.
- The types involved
doodle.canvas.algebra.Path.PathApi→doodle.algebra.generic.GenericPath.PathApi
- Direction
- canvas.algebra.Path uses algebra.generic.GenericPath, so a change to algebra.generic.GenericPath can break canvas.algebra.Path, while a change to canvas.algebra.Path can't break algebra.generic.GenericPath.
- Position
- Below the diagonal: canvas.algebra.Path uses a module listed above it, which is the healthy direction.
22→14 canvas.algebra.Path uses algebra.generic✕
- Connections
- 2 pairs of types, where a type in canvas.algebra.Path uses a type in algebra.generic.
- The types involved
doodle.canvas.algebra.Path.PathApi→doodle.algebra.generic.Filldoodle.canvas.algebra.Path.PathApi→doodle.algebra.generic.Stroke
- Direction
- canvas.algebra.Path uses algebra.generic, so a change to algebra.generic can break canvas.algebra.Path, while a change to canvas.algebra.Path can't break algebra.generic.
- Position
- Below the diagonal: canvas.algebra.Path uses a module listed above it, which is the healthy direction.
22→17 canvas.algebra.Path uses canvas.algebra✕
- Connections
- 1 pair of types, where a type in canvas.algebra.Path uses a type in canvas.algebra.
- The types involved
doodle.canvas.algebra.Path.PathApi→doodle.canvas.algebra.CanvasDrawing
- Direction
- canvas.algebra.Path uses canvas.algebra, so a change to canvas.algebra can break canvas.algebra.Path, while a change to canvas.algebra.Path can't break canvas.algebra.
- Position
- Below the diagonal: canvas.algebra.Path uses a module listed above it, which is the healthy direction.
23→4 canvas.algebra.Shape uses algebra.generic.GenericShape✕
- Connections
- 1 pair of types, where a type in canvas.algebra.Shape uses a type in algebra.generic.GenericShape.
- The types involved
doodle.canvas.algebra.Shape.ShapeApi→doodle.algebra.generic.GenericShape.ShapeApi
- Direction
- canvas.algebra.Shape uses algebra.generic.GenericShape, so a change to algebra.generic.GenericShape can break canvas.algebra.Shape, while a change to canvas.algebra.Shape can't break algebra.generic.GenericShape.
- Position
- Below the diagonal: canvas.algebra.Shape uses a module listed above it, which is the healthy direction.
23→14 canvas.algebra.Shape uses algebra.generic✕
- Connections
- 2 pairs of types, where a type in canvas.algebra.Shape uses a type in algebra.generic.
- The types involved
doodle.canvas.algebra.Shape.ShapeApi→doodle.algebra.generic.Filldoodle.canvas.algebra.Shape.ShapeApi→doodle.algebra.generic.Stroke
- Direction
- canvas.algebra.Shape uses algebra.generic, so a change to algebra.generic can break canvas.algebra.Shape, while a change to canvas.algebra.Shape can't break algebra.generic.
- Position
- Below the diagonal: canvas.algebra.Shape uses a module listed above it, which is the healthy direction.
23→17 canvas.algebra.Shape uses canvas.algebra✕
- Connections
- 1 pair of types, where a type in canvas.algebra.Shape uses a type in canvas.algebra.
- The types involved
doodle.canvas.algebra.Shape.ShapeApi→doodle.canvas.algebra.CanvasDrawing
- Direction
- canvas.algebra.Shape uses canvas.algebra, so a change to canvas.algebra can break canvas.algebra.Shape, while a change to canvas.algebra.Shape can't break canvas.algebra.
- Position
- Below the diagonal: canvas.algebra.Shape uses a module listed above it, which is the healthy direction.
24→1 canvas.algebra.Text uses core.font✕
- Connections
- 1 pair of types, where a type in canvas.algebra.Text uses a type in core.font.
- The types involved
doodle.canvas.algebra.Text.TextApi→doodle.core.font.Font
- Direction
- canvas.algebra.Text uses core.font, so a change to core.font can break canvas.algebra.Text, while a change to canvas.algebra.Text can't break core.font.
- Position
- Below the diagonal: canvas.algebra.Text uses a module listed above it, which is the healthy direction.
24→5 canvas.algebra.Text uses algebra.generic.GenericText✕
- Connections
- 1 pair of types, where a type in canvas.algebra.Text uses a type in algebra.generic.GenericText.
- The types involved
doodle.canvas.algebra.Text.TextApi→doodle.algebra.generic.GenericText.TextApi
- Direction
- canvas.algebra.Text uses algebra.generic.GenericText, so a change to algebra.generic.GenericText can break canvas.algebra.Text, while a change to canvas.algebra.Text can't break algebra.generic.GenericText.
- Position
- Below the diagonal: canvas.algebra.Text uses a module listed above it, which is the healthy direction.
24→14 canvas.algebra.Text uses algebra.generic✕
- Connections
- 2 pairs of types, where a type in canvas.algebra.Text uses a type in algebra.generic.
- The types involved
doodle.canvas.algebra.Text.TextApi→doodle.algebra.generic.Filldoodle.canvas.algebra.Text.TextApi→doodle.algebra.generic.Stroke
- Direction
- canvas.algebra.Text uses algebra.generic, so a change to algebra.generic can break canvas.algebra.Text, while a change to canvas.algebra.Text can't break algebra.generic.
- Position
- Below the diagonal: canvas.algebra.Text uses a module listed above it, which is the healthy direction.
24→17 canvas.algebra.Text uses canvas.algebra✕
- Connections
- 1 pair of types, where a type in canvas.algebra.Text uses a type in canvas.algebra.
- The types involved
doodle.canvas.algebra.Text.TextApi→doodle.canvas.algebra.CanvasDrawing
- Direction
- canvas.algebra.Text uses canvas.algebra, so a change to canvas.algebra can break canvas.algebra.Text, while a change to canvas.algebra.Text can't break canvas.algebra.
- Position
- Below the diagonal: canvas.algebra.Text uses a module listed above it, which is the healthy direction.
25→10 interact.animation uses effect✕
- Connections
- 1 pair of types, where a type in interact.animation uses a type in effect.
- The types involved
doodle.interact.animation.Transducer→doodle.effect.Renderer
- Direction
- interact.animation uses effect, so a change to effect can break interact.animation, while a change to interact.animation can't break effect.
- Position
- Below the diagonal: interact.animation uses a module listed above it, which is the healthy direction.
25→12 interact.animation uses interact.algebra✕
- Connections
- 1 pair of types, where a type in interact.animation uses a type in interact.algebra.
- The types involved
doodle.interact.animation.Transducer→doodle.interact.algebra.Redraw
- Direction
- interact.animation uses interact.algebra, so a change to interact.algebra can break interact.animation, while a change to interact.animation can't break interact.algebra.
- Position
- Below the diagonal: interact.animation uses a module listed above it, which is the healthy direction.
25→16 interact.animation uses interact.effect✕
- Connections
- 1 pair of types, where a type in interact.animation uses a type in interact.effect.
- The types involved
doodle.interact.animation.Transducer→doodle.interact.effect.AnimationRenderer
- Direction
- interact.animation uses interact.effect, so a change to interact.effect can break interact.animation, while a change to interact.animation can't break interact.effect.
- Position
- Below the diagonal: interact.animation uses a module listed above it, which is the healthy direction.
25→18 interact.animation uses canvas.effect✕
- Connections
- 2 pairs of types, where a type in interact.animation uses a type in canvas.effect.
- The types involved
doodle.interact.animation.Transducer→doodle.canvas.effect.Canvasdoodle.interact.animation.Transducer→doodle.canvas.effect.Frame
- Direction
- interact.animation uses canvas.effect, so a change to canvas.effect can break interact.animation, while a change to interact.animation can't break canvas.effect.
- Position
- Below the diagonal: interact.animation uses a module listed above it, which is the healthy direction.
26→7 interact.syntax.AbstractAnimationRendererSyntax uses algebra✕
- Connections
- 1 pair of types, where a type in interact.syntax.AbstractAnimationRendererSyntax uses a type in algebra.
- The types involved
doodle.interact.syntax.AbstractAnimationRendererSyntax.AnimateStreamOps→doodle.algebra.Picture
- Direction
- interact.syntax.AbstractAnimationRendererSyntax uses algebra, so a change to algebra can break interact.syntax.AbstractAnimationRendererSyntax, while a change to interact.syntax.AbstractAnimationRendererSyntax can't break algebra.
- Position
- Below the diagonal: interact.syntax.AbstractAnimationRendererSyntax uses a module listed above it, which is the healthy direction.
26→10 interact.syntax.AbstractAnimationRendererSyntax uses effect✕
- Connections
- 2 pairs of types, where a type in interact.syntax.AbstractAnimationRendererSyntax uses a type in effect.
- The types involved
doodle.interact.syntax.AbstractAnimationRendererSyntax.AnimateStreamOps→doodle.effect.Rendererdoodle.interact.syntax.AbstractAnimationRendererSyntax.AnimateToStreamOps→doodle.effect.Renderer
- Direction
- interact.syntax.AbstractAnimationRendererSyntax uses effect, so a change to effect can break interact.syntax.AbstractAnimationRendererSyntax, while a change to interact.syntax.AbstractAnimationRendererSyntax can't break effect.
- Position
- Below the diagonal: interact.syntax.AbstractAnimationRendererSyntax uses a module listed above it, which is the healthy direction.
26→12 interact.syntax.AbstractAnimationRendererSyntax uses interact.algebra✕
- Connections
- 1 pair of types, where a type in interact.syntax.AbstractAnimationRendererSyntax uses a type in interact.algebra.
- The types involved
doodle.interact.syntax.AbstractAnimationRendererSyntax.AnimateToStreamOps→doodle.interact.algebra.Redraw
- Direction
- interact.syntax.AbstractAnimationRendererSyntax uses interact.algebra, so a change to interact.algebra can break interact.syntax.AbstractAnimationRendererSyntax, while a change to interact.syntax.AbstractAnimationRendererSyntax can't break interact.algebra.
- Position
- Below the diagonal: interact.syntax.AbstractAnimationRendererSyntax uses a module listed above it, which is the healthy direction.
26→16 interact.syntax.AbstractAnimationRendererSyntax uses interact.effect✕
- Connections
- 2 pairs of types, where a type in interact.syntax.AbstractAnimationRendererSyntax uses a type in interact.effect.
- The types involved
doodle.interact.syntax.AbstractAnimationRendererSyntax.AnimateStreamOps→doodle.interact.effect.AnimationRendererdoodle.interact.syntax.AbstractAnimationRendererSyntax.AnimateToStreamOps→doodle.interact.effect.AnimationRenderer
- Direction
- interact.syntax.AbstractAnimationRendererSyntax uses interact.effect, so a change to interact.effect can break interact.syntax.AbstractAnimationRendererSyntax, while a change to interact.syntax.AbstractAnimationRendererSyntax can't break interact.effect.
- Position
- Below the diagonal: interact.syntax.AbstractAnimationRendererSyntax uses a module listed above it, which is the healthy direction.
26→18 interact.syntax.AbstractAnimationRendererSyntax uses canvas.effect✕
- Connections
- 4 pairs of types, where a type in interact.syntax.AbstractAnimationRendererSyntax uses a type in canvas.effect.
- The types involved
doodle.interact.syntax.AbstractAnimationRendererSyntax.AnimateStreamOps→doodle.canvas.effect.Canvasdoodle.interact.syntax.AbstractAnimationRendererSyntax.AnimateStreamOps→doodle.canvas.effect.Framedoodle.interact.syntax.AbstractAnimationRendererSyntax.AnimateToStreamOps→doodle.canvas.effect.Canvasdoodle.interact.syntax.AbstractAnimationRendererSyntax.AnimateToStreamOps→doodle.canvas.effect.Frame
- Direction
- interact.syntax.AbstractAnimationRendererSyntax uses canvas.effect, so a change to canvas.effect can break interact.syntax.AbstractAnimationRendererSyntax, while a change to interact.syntax.AbstractAnimationRendererSyntax can't break canvas.effect.
- Position
- Below the diagonal: interact.syntax.AbstractAnimationRendererSyntax uses a module listed above it, which is the healthy direction.
27→2 interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps uses core.format✕
- Connections
- 2 pairs of types, where a type in interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps uses a type in core.format.
- The types involved
doodle.interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps.AnimationWriterIOOpsHelper→doodle.core.format.Formatdoodle.interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps.AnimationWriterOpsHelper→doodle.core.format.Format
- Direction
- interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps uses core.format, so a change to core.format can break interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps, while a change to interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps can't break core.format.
- Position
- Below the diagonal: interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps uses a module listed above it, which is the healthy direction.
27→16 interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps uses interact.effect✕
- Connections
- 2 pairs of types, where a type in interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps uses a type in interact.effect.
- The types involved
doodle.interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps.AnimationWriterIOOpsHelper→doodle.interact.effect.AnimationWriterdoodle.interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps.AnimationWriterOpsHelper→doodle.interact.effect.AnimationWriter
- Direction
- interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps uses interact.effect, so a change to interact.effect can break interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps, while a change to interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps can't break interact.effect.
- Position
- Below the diagonal: interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps uses a module listed above it, which is the healthy direction.
27→18 interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps uses canvas.effect✕
- Connections
- 2 pairs of types, where a type in interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps uses a type in canvas.effect.
- The types involved
doodle.interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps.AnimationWriterIOOpsHelper→doodle.canvas.effect.Framedoodle.interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps.AnimationWriterOpsHelper→doodle.canvas.effect.Frame
- Direction
- interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps uses canvas.effect, so a change to canvas.effect can break interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps, while a change to interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps can't break canvas.effect.
- Position
- Below the diagonal: interact.syntax.AnimationWriterSyntax.AnimationWriterStreamOps uses a module listed above it, which is the healthy direction.
28→6 interact.syntax.MouseClickSyntax uses core✕
- Connections
- 1 pair of types, where a type in interact.syntax.MouseClickSyntax uses a type in core.
- The types involved
doodle.interact.syntax.MouseClickSyntax.MouseClickOps→doodle.core.Point
- Direction
- interact.syntax.MouseClickSyntax uses core, so a change to core can break interact.syntax.MouseClickSyntax, while a change to interact.syntax.MouseClickSyntax can't break core.
- Position
- Below the diagonal: interact.syntax.MouseClickSyntax uses a module listed above it, which is the healthy direction.
28→12 interact.syntax.MouseClickSyntax uses interact.algebra✕
- Connections
- 1 pair of types, where a type in interact.syntax.MouseClickSyntax uses a type in interact.algebra.
- The types involved
doodle.interact.syntax.MouseClickSyntax.MouseClickOps→doodle.interact.algebra.MouseClick
- Direction
- interact.syntax.MouseClickSyntax uses interact.algebra, so a change to interact.algebra can break interact.syntax.MouseClickSyntax, while a change to interact.syntax.MouseClickSyntax can't break interact.algebra.
- Position
- Below the diagonal: interact.syntax.MouseClickSyntax uses a module listed above it, which is the healthy direction.
28→18 interact.syntax.MouseClickSyntax uses canvas.effect✕
- Connections
- 1 pair of types, where a type in interact.syntax.MouseClickSyntax uses a type in canvas.effect.
- The types involved
doodle.interact.syntax.MouseClickSyntax.MouseClickOps→doodle.canvas.effect.Canvas
- Direction
- interact.syntax.MouseClickSyntax uses canvas.effect, so a change to canvas.effect can break interact.syntax.MouseClickSyntax, while a change to interact.syntax.MouseClickSyntax can't break canvas.effect.
- Position
- Below the diagonal: interact.syntax.MouseClickSyntax uses a module listed above it, which is the healthy direction.
29→2 java2d uses core.format✕
- Connections
- 4 pairs of types, where a type in java2d uses a type in core.format.
- The types involved
doodle.java2d.Java2dPackage→doodle.core.format.Gifdoodle.java2d.Java2dToPicture→doodle.core.format.Gifdoodle.java2d.Java2dToPicture→doodle.core.format.Jpgdoodle.java2d.Java2dToPicture→doodle.core.format.Png
- Direction
- java2d uses core.format, so a change to core.format can break java2d, while a change to java2d can't break core.format.
- Position
- Below the diagonal: java2d uses a module listed above it, which is the healthy direction.
29→6 java2d uses core✕
- Connections
- 1 pair of types, where a type in java2d uses a type in core.
- The types involved
doodle.java2d.Java2dToPicture→doodle.core.Base64
- Direction
- java2d uses core, so a change to core can break java2d, while a change to java2d can't break core.
- Position
- Below the diagonal: java2d uses a module listed above it, which is the healthy direction.
29→7 java2d uses algebra✕
- Connections
- 3 pairs of types, where a type in java2d uses a type in algebra.
- The types involved
doodle.java2d.Java2dPackage→doodle.algebra.Algebradoodle.java2d.Java2dToPicture→doodle.algebra.Algebradoodle.java2d.Java2dToPicture→doodle.algebra.ToPicture
- Direction
- java2d uses algebra, so a change to algebra can break java2d, while a change to java2d can't break algebra.
- Position
- Below the diagonal: java2d uses a module listed above it, which is the healthy direction.
29→10 java2d uses effect✕
- Connections
- 5 pairs of types, where a type in java2d uses a type in effect.
- The types involved
doodle.java2d.Java2dPackage→doodle.effect.BufferedImageWriterdoodle.java2d.Java2dPackage→doodle.effect.DefaultFramedoodle.java2d.Java2dPackage→doodle.effect.FileWriterdoodle.java2d.Java2dPackage→doodle.effect.Rendererdoodle.java2d.repl→doodle.effect.DefaultFrame
- Direction
- java2d uses effect, so a change to effect can break java2d, while a change to java2d can't break effect.
- Position
- Below the diagonal: java2d uses a module listed above it, which is the healthy direction.
29→12 java2d uses interact.algebra✕
- Connections
- 1 pair of types, where a type in java2d uses a type in interact.algebra.
- The types involved
doodle.java2d.Java2dPackage→doodle.interact.algebra.MouseClick
- Direction
- java2d uses interact.algebra, so a change to interact.algebra can break java2d, while a change to java2d can't break interact.algebra.
- Position
- Below the diagonal: java2d uses a module listed above it, which is the healthy direction.
29→16 java2d uses interact.effect✕
- Connections
- 2 pairs of types, where a type in java2d uses a type in interact.effect.
- The types involved
doodle.java2d.Java2dPackage→doodle.interact.effect.AnimationRendererdoodle.java2d.Java2dPackage→doodle.interact.effect.AnimationWriter
- Direction
- java2d uses interact.effect, so a change to interact.effect can break java2d, while a change to java2d can't break interact.effect.
- Position
- Below the diagonal: java2d uses a module listed above it, which is the healthy direction.
29→18 java2d uses canvas.effect✕
- Connections
- 3 pairs of types, where a type in java2d uses a type in canvas.effect.
- The types involved
doodle.java2d.Java2dPackage→doodle.canvas.effect.Canvasdoodle.java2d.Java2dPackage→doodle.canvas.effect.Framedoodle.java2d.repl→doodle.canvas.effect.Frame
- Direction
- java2d uses canvas.effect, so a change to canvas.effect can break java2d, while a change to java2d can't break canvas.effect.
- Position
- Below the diagonal: java2d uses a module listed above it, which is the healthy direction.
30→1 java2d.algebra uses core.font✕
- Connections
- 2 pairs of types, where a type in java2d.algebra uses a type in core.font.
- The types involved
doodle.java2d.algebra.Graphics2DGraphicsContext→doodle.core.font.Fontdoodle.java2d.algebra.Java2D→doodle.core.font.Font
- Direction
- java2d.algebra uses core.font, so a change to core.font can break java2d.algebra, while a change to java2d.algebra can't break core.font.
- Position
- Below the diagonal: java2d.algebra uses a module listed above it, which is the healthy direction.
30→2 java2d.algebra uses core.format✕
- Connections
- 3 pairs of types, where a type in java2d.algebra uses a type in core.format.
- The types involved
doodle.java2d.algebra.Java2dFromBase64→doodle.core.format.Gifdoodle.java2d.algebra.Java2dFromBase64→doodle.core.format.Jpgdoodle.java2d.algebra.Java2dFromBase64→doodle.core.format.Png
- Direction
- java2d.algebra uses core.format, so a change to core.format can break java2d.algebra, while a change to java2d.algebra can't break core.format.
- Position
- Below the diagonal: java2d.algebra uses a module listed above it, which is the healthy direction.
30→6 java2d.algebra uses core✕
- Connections
- 8 pairs of types, where a type in java2d.algebra uses a type in core.
- The types involved
doodle.java2d.algebra.CanvasAlgebra→doodle.core.Pointdoodle.java2d.algebra.Graphics2DGraphicsContext→doodle.core.PathElementdoodle.java2d.algebra.Graphics2DGraphicsContext→doodle.core.Pointdoodle.java2d.algebra.Java2D→doodle.core.BoundingBoxdoodle.java2d.algebra.Java2D→doodle.core.Colordoodle.java2d.algebra.Java2D→doodle.core.PathElementdoodle.java2d.algebra.Java2D→doodle.core.Pointdoodle.java2d.algebra.Java2dFromBase64→doodle.core.Base64
- Direction
- java2d.algebra uses core, so a change to core can break java2d.algebra, while a change to java2d.algebra can't break core.
- Position
- Below the diagonal: java2d.algebra uses a module listed above it, which is the healthy direction.
30→7 java2d.algebra uses algebra✕
- Connections
- 7 pairs of types, where a type in java2d.algebra uses a type in algebra.
- The types involved
doodle.java2d.algebra.Algebra→doodle.algebra.Algebradoodle.java2d.algebra.Java2dFromBase64→doodle.algebra.FromGifBase64doodle.java2d.algebra.Java2dFromBase64→doodle.algebra.FromJpgBase64doodle.java2d.algebra.Java2dFromBase64→doodle.algebra.FromPngBase64doodle.java2d.algebra.Java2dFromBufferedImage→doodle.algebra.FromBufferedImagedoodle.java2d.algebra.Java2dLoadBitmap→doodle.algebra.LoadBitmapdoodle.java2d.algebra.Java2dLoadBitmap→doodle.algebra.Path
- Direction
- java2d.algebra uses algebra, so a change to algebra can break java2d.algebra, while a change to java2d.algebra can't break algebra.
- Position
- Below the diagonal: java2d.algebra uses a module listed above it, which is the healthy direction.
30→8 java2d.algebra uses core.Gradient✕
- Connections
- 3 pairs of types, where a type in java2d.algebra uses a type in core.Gradient.
- The types involved
doodle.java2d.algebra.Java2D→doodle.core.Gradient.CycleMethoddoodle.java2d.algebra.Java2D→doodle.core.Gradient.Lineardoodle.java2d.algebra.Java2D→doodle.core.Gradient.Radial
- Direction
- java2d.algebra uses core.Gradient, so a change to core.Gradient can break java2d.algebra, while a change to java2d.algebra can't break core.Gradient.
- Position
- Below the diagonal: java2d.algebra uses a module listed above it, which is the healthy direction.
30→12 java2d.algebra uses interact.algebra✕
- Connections
- 3 pairs of types, where a type in java2d.algebra uses a type in interact.algebra.
- The types involved
doodle.java2d.algebra.CanvasAlgebra→doodle.interact.algebra.MouseClickdoodle.java2d.algebra.CanvasAlgebra→doodle.interact.algebra.MouseMovedoodle.java2d.algebra.CanvasAlgebra→doodle.interact.algebra.Redraw
- Direction
- java2d.algebra uses interact.algebra, so a change to interact.algebra can break java2d.algebra, while a change to java2d.algebra can't break interact.algebra.
- Position
- Below the diagonal: java2d.algebra uses a module listed above it, which is the healthy direction.
30→13 java2d.algebra uses language✕
- Connections
- 1 pair of types, where a type in java2d.algebra uses a type in language.
- The types involved
doodle.java2d.algebra.Algebra→doodle.language.Basic
- Direction
- java2d.algebra uses language, so a change to language can break java2d.algebra, while a change to java2d.algebra can't break language.
- Position
- Below the diagonal: java2d.algebra uses a module listed above it, which is the healthy direction.
30→14 java2d.algebra uses algebra.generic✕
- Connections
- 12 pairs of types, where a type in java2d.algebra uses a type in algebra.generic.
- The types involved
doodle.java2d.algebra.Algebra→doodle.algebra.generic.GenericDebugdoodle.java2d.algebra.Algebra→doodle.algebra.generic.GenericLayoutdoodle.java2d.algebra.Algebra→doodle.algebra.generic.GenericSizedoodle.java2d.algebra.Algebra→doodle.algebra.generic.GenericStyledoodle.java2d.algebra.Algebra→doodle.algebra.generic.GenericTransformdoodle.java2d.algebra.Algebra→doodle.algebra.generic.GivenApplydoodle.java2d.algebra.Algebra→doodle.algebra.generic.GivenFunctordoodle.java2d.algebra.Graphics2DGraphicsContext→doodle.algebra.generic.Filldoodle.java2d.algebra.Graphics2DGraphicsContext→doodle.algebra.generic.Strokedoodle.java2d.algebra.Java2D→doodle.algebra.generic.DrawingContextdoodle.java2d.algebra.Java2D→doodle.algebra.generic.Filldoodle.java2d.algebra.Java2D→doodle.algebra.generic.Stroke
- Direction
- java2d.algebra uses algebra.generic, so a change to algebra.generic can break java2d.algebra, while a change to java2d.algebra can't break algebra.generic.
- Position
- Below the diagonal: java2d.algebra uses a module listed above it, which is the healthy direction.
30→18 java2d.algebra uses canvas.effect✕
- Connections
- 1 pair of types, where a type in java2d.algebra uses a type in canvas.effect.
- The types involved
doodle.java2d.algebra.CanvasAlgebra→doodle.canvas.effect.Canvas
- Direction
- java2d.algebra uses canvas.effect, so a change to canvas.effect can break java2d.algebra, while a change to java2d.algebra can't break canvas.effect.
- Position
- Below the diagonal: java2d.algebra uses a module listed above it, which is the healthy direction.
30→19 java2d.algebra uses java2d.algebra.reified✕
- Connections
- 5 pairs of types, where a type in java2d.algebra uses a type in java2d.algebra.reified.
- The types involved
doodle.java2d.algebra.Algebra→doodle.java2d.algebra.reified.ReifiedBitmapdoodle.java2d.algebra.Algebra→doodle.java2d.algebra.reified.ReifiedPathdoodle.java2d.algebra.Algebra→doodle.java2d.algebra.reified.ReifiedShapedoodle.java2d.algebra.Algebra→doodle.java2d.algebra.reified.ReifiedTextdoodle.java2d.algebra.Graphics2DGraphicsContext→doodle.java2d.algebra.reified.GraphicsContext
- Direction
- java2d.algebra uses java2d.algebra.reified, so a change to java2d.algebra.reified can break java2d.algebra, while a change to java2d.algebra can't break java2d.algebra.reified.
- Position
- Below the diagonal: java2d.algebra uses a module listed above it, which is the healthy direction.
31→1 java2d.algebra.reified.Reified uses core.font✕
- Connections
- 1 pair of types, where a type in java2d.algebra.reified.Reified uses a type in core.font.
- The types involved
doodle.java2d.algebra.reified.Reified.Text→doodle.core.font.Font
- Direction
- java2d.algebra.reified.Reified uses core.font, so a change to core.font can break java2d.algebra.reified.Reified, while a change to java2d.algebra.reified.Reified can't break core.font.
- Position
- Below the diagonal: java2d.algebra.reified.Reified uses a module listed above it, which is the healthy direction.
31→6 java2d.algebra.reified.Reified uses core✕
- Connections
- 6 pairs of types, where a type in java2d.algebra.reified.Reified uses a type in core.
- The types involved
doodle.java2d.algebra.reified.Reified.FillClosedPath→doodle.core.PathElementdoodle.java2d.algebra.reified.Reified.FillOpenPath→doodle.core.PathElementdoodle.java2d.algebra.reified.Reified.FillPolygon→doodle.core.Pointdoodle.java2d.algebra.reified.Reified.StrokeClosedPath→doodle.core.PathElementdoodle.java2d.algebra.reified.Reified.StrokeOpenPath→doodle.core.PathElementdoodle.java2d.algebra.reified.Reified.StrokePolygon→doodle.core.Point
- Direction
- java2d.algebra.reified.Reified uses core, so a change to core can break java2d.algebra.reified.Reified, while a change to java2d.algebra.reified.Reified can't break core.
- Position
- Below the diagonal: java2d.algebra.reified.Reified uses a module listed above it, which is the healthy direction.
31→14 java2d.algebra.reified.Reified uses algebra.generic✕
- Connections
- 12 pairs of types, where a type in java2d.algebra.reified.Reified uses a type in algebra.generic.
- The types involved
doodle.java2d.algebra.reified.Reified.FillCircle→doodle.algebra.generic.Filldoodle.java2d.algebra.reified.Reified.FillClosedPath→doodle.algebra.generic.Filldoodle.java2d.algebra.reified.Reified.FillOpenPath→doodle.algebra.generic.Filldoodle.java2d.algebra.reified.Reified.FillPolygon→doodle.algebra.generic.Filldoodle.java2d.algebra.reified.Reified.FillRect→doodle.algebra.generic.Filldoodle.java2d.algebra.reified.Reified.StrokeCircle→doodle.algebra.generic.Strokedoodle.java2d.algebra.reified.Reified.StrokeClosedPath→doodle.algebra.generic.Strokedoodle.java2d.algebra.reified.Reified.StrokeOpenPath→doodle.algebra.generic.Strokedoodle.java2d.algebra.reified.Reified.StrokePolygon→doodle.algebra.generic.Strokedoodle.java2d.algebra.reified.Reified.StrokeRect→doodle.algebra.generic.Strokedoodle.java2d.algebra.reified.Reified.Text→doodle.algebra.generic.Filldoodle.java2d.algebra.reified.Reified.Text→doodle.algebra.generic.Stroke
- Direction
- java2d.algebra.reified.Reified uses algebra.generic, so a change to algebra.generic can break java2d.algebra.reified.Reified, while a change to java2d.algebra.reified.Reified can't break algebra.generic.
- Position
- Below the diagonal: java2d.algebra.reified.Reified uses a module listed above it, which is the healthy direction.
31→19 java2d.algebra.reified.Reified uses java2d.algebra.reified✕
- Connections
- 12 pairs of types, where a type in java2d.algebra.reified.Reified uses a type in java2d.algebra.reified.
- The types involved
doodle.java2d.algebra.reified.Reified.Bitmap→doodle.java2d.algebra.reified.Reifieddoodle.java2d.algebra.reified.Reified.FillCircle→doodle.java2d.algebra.reified.Reifieddoodle.java2d.algebra.reified.Reified.FillClosedPath→doodle.java2d.algebra.reified.Reifieddoodle.java2d.algebra.reified.Reified.FillOpenPath→doodle.java2d.algebra.reified.Reifieddoodle.java2d.algebra.reified.Reified.FillPolygon→doodle.java2d.algebra.reified.Reifieddoodle.java2d.algebra.reified.Reified.FillRect→doodle.java2d.algebra.reified.Reifieddoodle.java2d.algebra.reified.Reified.StrokeCircle→doodle.java2d.algebra.reified.Reifieddoodle.java2d.algebra.reified.Reified.StrokeClosedPath→doodle.java2d.algebra.reified.Reifieddoodle.java2d.algebra.reified.Reified.StrokeOpenPath→doodle.java2d.algebra.reified.Reifieddoodle.java2d.algebra.reified.Reified.StrokePolygon→doodle.java2d.algebra.reified.Reifieddoodle.java2d.algebra.reified.Reified.StrokeRect→doodle.java2d.algebra.reified.Reifieddoodle.java2d.algebra.reified.Reified.Text→doodle.java2d.algebra.reified.Reified
- Direction
- java2d.algebra.reified.Reified uses java2d.algebra.reified, so a change to java2d.algebra.reified can break java2d.algebra.reified.Reified, while a change to java2d.algebra.reified.Reified can't break java2d.algebra.reified.
- Position
- Below the diagonal: java2d.algebra.reified.Reified uses a module listed above it, which is the healthy direction.
32→6 java2d.algebra.reified.ReifiedPath uses core✕
- Connections
- 1 pair of types, where a type in java2d.algebra.reified.ReifiedPath uses a type in core.
- The types involved
doodle.java2d.algebra.reified.ReifiedPath.PathApi→doodle.core.PathElement
- Direction
- java2d.algebra.reified.ReifiedPath uses core, so a change to core can break java2d.algebra.reified.ReifiedPath, while a change to java2d.algebra.reified.ReifiedPath can't break core.
- Position
- Below the diagonal: java2d.algebra.reified.ReifiedPath uses a module listed above it, which is the healthy direction.
32→7 java2d.algebra.reified.ReifiedPath uses algebra✕
- Connections
- 1 pair of types, where a type in java2d.algebra.reified.ReifiedPath uses a type in algebra.
- The types involved
doodle.java2d.algebra.reified.ReifiedPath.PathApi→doodle.algebra.Transform
- Direction
- java2d.algebra.reified.ReifiedPath uses algebra, so a change to algebra can break java2d.algebra.reified.ReifiedPath, while a change to java2d.algebra.reified.ReifiedPath can't break algebra.
- Position
- Below the diagonal: java2d.algebra.reified.ReifiedPath uses a module listed above it, which is the healthy direction.
32→9 java2d.algebra.reified.ReifiedPath uses algebra.generic.GenericPath✕
- Connections
- 1 pair of types, where a type in java2d.algebra.reified.ReifiedPath uses a type in algebra.generic.GenericPath.
- The types involved
doodle.java2d.algebra.reified.ReifiedPath.PathApi→doodle.algebra.generic.GenericPath.PathApi
- Direction
- java2d.algebra.reified.ReifiedPath uses algebra.generic.GenericPath, so a change to algebra.generic.GenericPath can break java2d.algebra.reified.ReifiedPath, while a change to java2d.algebra.reified.ReifiedPath can't break algebra.generic.GenericPath.
- Position
- Below the diagonal: java2d.algebra.reified.ReifiedPath uses a module listed above it, which is the healthy direction.
32→14 java2d.algebra.reified.ReifiedPath uses algebra.generic✕
- Connections
- 2 pairs of types, where a type in java2d.algebra.reified.ReifiedPath uses a type in algebra.generic.
- The types involved
doodle.java2d.algebra.reified.ReifiedPath.PathApi→doodle.algebra.generic.Filldoodle.java2d.algebra.reified.ReifiedPath.PathApi→doodle.algebra.generic.Stroke
- Direction
- java2d.algebra.reified.ReifiedPath uses algebra.generic, so a change to algebra.generic can break java2d.algebra.reified.ReifiedPath, while a change to java2d.algebra.reified.ReifiedPath can't break algebra.generic.
- Position
- Below the diagonal: java2d.algebra.reified.ReifiedPath uses a module listed above it, which is the healthy direction.
32→19 java2d.algebra.reified.ReifiedPath uses java2d.algebra.reified✕
- Connections
- 1 pair of types, where a type in java2d.algebra.reified.ReifiedPath uses a type in java2d.algebra.reified.
- The types involved
doodle.java2d.algebra.reified.ReifiedPath.PathApi→doodle.java2d.algebra.reified.Reified
- Direction
- java2d.algebra.reified.ReifiedPath uses java2d.algebra.reified, so a change to java2d.algebra.reified can break java2d.algebra.reified.ReifiedPath, while a change to java2d.algebra.reified.ReifiedPath can't break java2d.algebra.reified.
- Position
- Below the diagonal: java2d.algebra.reified.ReifiedPath uses a module listed above it, which is the healthy direction.
33→6 java2d.effect uses core✕
- Connections
- 5 pairs of types, where a type in java2d.effect uses a type in core.
- The types involved
doodle.java2d.effect.Canvas→doodle.core.Pointdoodle.java2d.effect.Frame→doodle.core.Colordoodle.java2d.effect.Java2d→doodle.core.BoundingBoxdoodle.java2d.effect.Java2d→doodle.core.Colordoodle.java2d.effect.RenderResult→doodle.core.BoundingBox
- Direction
- java2d.effect uses core, so a change to core can break java2d.effect, while a change to java2d.effect can't break core.
- Position
- Below the diagonal: java2d.effect uses a module listed above it, which is the healthy direction.
33→7 java2d.effect uses algebra✕
- Connections
- 15 pairs of types, where a type in java2d.effect uses a type in algebra.
- The types involved
doodle.java2d.effect.Canvas→doodle.algebra.Picturedoodle.java2d.effect.Frame→doodle.algebra.Sizedoodle.java2d.effect.Java2DPanel→doodle.algebra.Picturedoodle.java2d.effect.Java2DPanel→doodle.algebra.Transformdoodle.java2d.effect.Java2d→doodle.algebra.Picturedoodle.java2d.effect.Java2d→doodle.algebra.Sizedoodle.java2d.effect.Java2dAnimationRenderer→doodle.algebra.Picturedoodle.java2d.effect.Java2dAnimationWriter→doodle.algebra.Picturedoodle.java2d.effect.Java2dBufferedImageWriter→doodle.algebra.Picturedoodle.java2d.effect.Java2dPdfWriter→doodle.algebra.Picturedoodle.java2d.effect.Java2dRenderer→doodle.algebra.Picturedoodle.java2d.effect.Java2dWindow→doodle.algebra.Picturedoodle.java2d.effect.Java2dWriter→doodle.algebra.Picturedoodle.java2d.effect.RenderRequest→doodle.algebra.Algebradoodle.java2d.effect.RenderRequest→doodle.algebra.Picture
- Direction
- java2d.effect uses algebra, so a change to algebra can break java2d.effect, while a change to java2d.effect can't break algebra.
- Position
- Below the diagonal: java2d.effect uses a module listed above it, which is the healthy direction.
33→10 java2d.effect uses effect✕
- Connections
- 6 pairs of types, where a type in java2d.effect uses a type in effect.
- The types involved
doodle.java2d.effect.Java2dAnimationRenderer→doodle.effect.Rendererdoodle.java2d.effect.Java2dBufferedImageWriter→doodle.effect.BufferedImageWriterdoodle.java2d.effect.Java2dDefaultFrame→doodle.effect.DefaultFramedoodle.java2d.effect.Java2dRenderer→doodle.effect.Rendererdoodle.java2d.effect.Java2dWriter→doodle.effect.Base64Writerdoodle.java2d.effect.Java2dWriter→doodle.effect.FileWriter
- Direction
- java2d.effect uses effect, so a change to effect can break java2d.effect, while a change to java2d.effect can't break effect.
- Position
- Below the diagonal: java2d.effect uses a module listed above it, which is the healthy direction.
33→12 java2d.effect uses interact.algebra✕
- Connections
- 1 pair of types, where a type in java2d.effect uses a type in interact.algebra.
- The types involved
doodle.java2d.effect.Frame→doodle.interact.algebra.Redraw
- Direction
- java2d.effect uses interact.algebra, so a change to interact.algebra can break java2d.effect, while a change to java2d.effect can't break interact.algebra.
- Position
- Below the diagonal: java2d.effect uses a module listed above it, which is the healthy direction.
33→16 java2d.effect uses interact.effect✕
- Connections
- 2 pairs of types, where a type in java2d.effect uses a type in interact.effect.
- The types involved
doodle.java2d.effect.Java2dAnimationRenderer→doodle.interact.effect.AnimationRendererdoodle.java2d.effect.Java2dAnimationWriter→doodle.interact.effect.AnimationWriter
- Direction
- java2d.effect uses interact.effect, so a change to interact.effect can break java2d.effect, while a change to java2d.effect can't break interact.effect.
- Position
- Below the diagonal: java2d.effect uses a module listed above it, which is the healthy direction.
33→18 java2d.effect uses canvas.effect✕
- Connections
- 11 pairs of types, where a type in java2d.effect uses a type in canvas.effect.
- The types involved
doodle.java2d.effect.BlockingBehavior→doodle.canvas.effect.Canvasdoodle.java2d.effect.Frame→doodle.canvas.effect.Framedoodle.java2d.effect.Java2dAnimationRenderer→doodle.canvas.effect.Canvasdoodle.java2d.effect.Java2dAnimationWriter→doodle.canvas.effect.Framedoodle.java2d.effect.Java2dBufferedImageWriter→doodle.canvas.effect.Framedoodle.java2d.effect.Java2dDefaultFrame→doodle.canvas.effect.Framedoodle.java2d.effect.Java2dPdfWriter→doodle.canvas.effect.Framedoodle.java2d.effect.Java2dRenderer→doodle.canvas.effect.Canvasdoodle.java2d.effect.Java2dRenderer→doodle.canvas.effect.Framedoodle.java2d.effect.Java2dWriter→doodle.canvas.effect.Framedoodle.java2d.effect.RenderRequest→doodle.canvas.effect.Frame
- Direction
- java2d.effect uses canvas.effect, so a change to canvas.effect can break java2d.effect, while a change to java2d.effect can't break canvas.effect.
- Position
- Below the diagonal: java2d.effect uses a module listed above it, which is the healthy direction.
33→19 java2d.effect uses java2d.algebra.reified✕
- Connections
- 2 pairs of types, where a type in java2d.effect uses a type in java2d.algebra.reified.
- The types involved
doodle.java2d.effect.Java2d→doodle.java2d.algebra.reified.Reifieddoodle.java2d.effect.RenderResult→doodle.java2d.algebra.reified.Reified
- Direction
- java2d.effect uses java2d.algebra.reified, so a change to java2d.algebra.reified can break java2d.effect, while a change to java2d.effect can't break java2d.algebra.reified.
- Position
- Below the diagonal: java2d.effect uses a module listed above it, which is the healthy direction.
34→6 reactor uses core✕
- Connections
- 2 pairs of types, where a type in reactor uses a type in core.
- The types involved
doodle.reactor.BaseReactor→doodle.core.Pointdoodle.reactor.Reactor→doodle.core.Point
- Direction
- reactor uses core, so a change to core can break reactor, while a change to reactor can't break core.
- Position
- Below the diagonal: reactor uses a module listed above it, which is the healthy direction.
34→7 reactor uses algebra✕
- Connections
- 1 pair of types, where a type in reactor uses a type in algebra.
- The types involved
doodle.reactor.BaseReactor→doodle.algebra.Picture
- Direction
- reactor uses algebra, so a change to algebra can break reactor, while a change to reactor can't break algebra.
- Position
- Below the diagonal: reactor uses a module listed above it, which is the healthy direction.
34→10 reactor uses effect✕
- Connections
- 3 pairs of types, where a type in reactor uses a type in effect.
- The types involved
doodle.reactor.BaseReactor→doodle.effect.Rendererdoodle.reactor.Reactor→doodle.effect.DefaultFramedoodle.reactor.Reactor→doodle.effect.Renderer
- Direction
- reactor uses effect, so a change to effect can break reactor, while a change to reactor can't break effect.
- Position
- Below the diagonal: reactor uses a module listed above it, which is the healthy direction.
34→11 reactor uses image✕
- Connections
- 2 pairs of types, where a type in reactor uses a type in image.
- The types involved
doodle.reactor.BaseReactor→doodle.image.Imagedoodle.reactor.Reactor→doodle.image.Image
- Direction
- reactor uses image, so a change to image can break reactor, while a change to reactor can't break image.
- Position
- Below the diagonal: reactor uses a module listed above it, which is the healthy direction.
34→13 reactor uses language✕
- Connections
- 1 pair of types, where a type in reactor uses a type in language.
- The types involved
doodle.reactor.BaseReactor→doodle.language.Basic
- Direction
- reactor uses language, so a change to language can break reactor, while a change to reactor can't break language.
- Position
- Below the diagonal: reactor uses a module listed above it, which is the healthy direction.
34→18 reactor uses canvas.effect✕
- Connections
- 4 pairs of types, where a type in reactor uses a type in canvas.effect.
- The types involved
doodle.reactor.BaseReactor→doodle.canvas.effect.Canvasdoodle.reactor.BaseReactor→doodle.canvas.effect.Framedoodle.reactor.Reactor→doodle.canvas.effect.Canvasdoodle.reactor.Reactor→doodle.canvas.effect.Frame
- Direction
- reactor uses canvas.effect, so a change to canvas.effect can break reactor, while a change to reactor can't break canvas.effect.
- Position
- Below the diagonal: reactor uses a module listed above it, which is the healthy direction.
35→1 svg.algebra uses core.font✕
- Connections
- 1 pair of types, where a type in svg.algebra uses a type in core.font.
- The types involved
doodle.svg.algebra.HasTextBoundingBox→doodle.core.font.Font
- Direction
- svg.algebra uses core.font, so a change to core.font can break svg.algebra, while a change to svg.algebra can't break core.font.
- Position
- Below the diagonal: svg.algebra uses a module listed above it, which is the healthy direction.
35→6 svg.algebra uses core✕
- Connections
- 1 pair of types, where a type in svg.algebra uses a type in core.
- The types involved
doodle.svg.algebra.CanvasAlgebra→doodle.core.Point
- Direction
- svg.algebra uses core, so a change to core can break svg.algebra, while a change to svg.algebra can't break core.
- Position
- Below the diagonal: svg.algebra uses a module listed above it, which is the healthy direction.
35→7 svg.algebra uses algebra✕
- Connections
- 4 pairs of types, where a type in svg.algebra uses a type in algebra.
- The types involved
doodle.svg.algebra.Attributed→doodle.algebra.Algebradoodle.svg.algebra.SvgLoadBitmap→doodle.algebra.LoadBitmapdoodle.svg.algebra.SvgToPicture→doodle.algebra.ToPicturedoodle.svg.algebra.Tagged→doodle.algebra.Algebra
- Direction
- svg.algebra uses algebra, so a change to algebra can break svg.algebra, while a change to svg.algebra can't break algebra.
- Position
- Below the diagonal: svg.algebra uses a module listed above it, which is the healthy direction.
35→12 svg.algebra uses interact.algebra✕
- Connections
- 3 pairs of types, where a type in svg.algebra uses a type in interact.algebra.
- The types involved
doodle.svg.algebra.CanvasAlgebra→doodle.interact.algebra.MouseClickdoodle.svg.algebra.CanvasAlgebra→doodle.interact.algebra.MouseMovedoodle.svg.algebra.CanvasAlgebra→doodle.interact.algebra.Redraw
- Direction
- svg.algebra uses interact.algebra, so a change to interact.algebra can break svg.algebra, while a change to svg.algebra can't break interact.algebra.
- Position
- Below the diagonal: svg.algebra uses a module listed above it, which is the healthy direction.
35→18 svg.algebra uses canvas.effect✕
- Connections
- 1 pair of types, where a type in svg.algebra uses a type in canvas.effect.
- The types involved
doodle.svg.algebra.CanvasAlgebra→doodle.canvas.effect.Canvas
- Direction
- svg.algebra uses canvas.effect, so a change to canvas.effect can break svg.algebra, while a change to svg.algebra can't break canvas.effect.
- Position
- Below the diagonal: svg.algebra uses a module listed above it, which is the healthy direction.
36→1 svg.algebra.JsAlgebraModule uses core.font✕
- Connections
- 1 pair of types, where a type in svg.algebra.JsAlgebraModule uses a type in core.font.
- The types involved
doodle.svg.algebra.JsAlgebraModule.JsAlgebra→doodle.core.font.Font
- Direction
- svg.algebra.JsAlgebraModule uses core.font, so a change to core.font can break svg.algebra.JsAlgebraModule, while a change to svg.algebra.JsAlgebraModule can't break core.font.
- Position
- Below the diagonal: svg.algebra.JsAlgebraModule uses a module listed above it, which is the healthy direction.
36→7 svg.algebra.JsAlgebraModule uses algebra✕
- Connections
- 3 pairs of types, where a type in svg.algebra.JsAlgebraModule uses a type in algebra.
- The types involved
doodle.svg.algebra.JsAlgebraModule.JsAlgebra→doodle.algebra.Blenddoodle.svg.algebra.JsAlgebraModule.JsAlgebra→doodle.algebra.Filterdoodle.svg.algebra.JsAlgebraModule.JsAlgebra→doodle.algebra.Text
- Direction
- svg.algebra.JsAlgebraModule uses algebra, so a change to algebra can break svg.algebra.JsAlgebraModule, while a change to svg.algebra.JsAlgebraModule can't break algebra.
- Position
- Below the diagonal: svg.algebra.JsAlgebraModule uses a module listed above it, which is the healthy direction.
36→11 svg.algebra.JsAlgebraModule uses image✕
- Connections
- 1 pair of types, where a type in svg.algebra.JsAlgebraModule uses a type in image.
- The types involved
doodle.svg.algebra.JsAlgebraModule.JsAlgebra→doodle.image.Image
- Direction
- svg.algebra.JsAlgebraModule uses image, so a change to image can break svg.algebra.JsAlgebraModule, while a change to svg.algebra.JsAlgebraModule can't break image.
- Position
- Below the diagonal: svg.algebra.JsAlgebraModule uses a module listed above it, which is the healthy direction.
36→17 svg.algebra.JsAlgebraModule uses canvas.algebra✕
- Connections
- 1 pair of types, where a type in svg.algebra.JsAlgebraModule uses a type in canvas.algebra.
- The types involved
doodle.svg.algebra.JsAlgebraModule.JsAlgebra→doodle.canvas.algebra.HasTextBoundingBox
- Direction
- svg.algebra.JsAlgebraModule uses canvas.algebra, so a change to canvas.algebra can break svg.algebra.JsAlgebraModule, while a change to svg.algebra.JsAlgebraModule can't break canvas.algebra.
- Position
- Below the diagonal: svg.algebra.JsAlgebraModule uses a module listed above it, which is the healthy direction.
36→18 svg.algebra.JsAlgebraModule uses canvas.effect✕
- Connections
- 1 pair of types, where a type in svg.algebra.JsAlgebraModule uses a type in canvas.effect.
- The types involved
doodle.svg.algebra.JsAlgebraModule.JsAlgebra→doodle.canvas.effect.Canvas
- Direction
- svg.algebra.JsAlgebraModule uses canvas.effect, so a change to canvas.effect can break svg.algebra.JsAlgebraModule, while a change to svg.algebra.JsAlgebraModule can't break canvas.effect.
- Position
- Below the diagonal: svg.algebra.JsAlgebraModule uses a module listed above it, which is the healthy direction.
36→20 svg.algebra.JsAlgebraModule uses svg.algebra.AlgebraModule✕
- Connections
- 1 pair of types, where a type in svg.algebra.JsAlgebraModule uses a type in svg.algebra.AlgebraModule.
- The types involved
doodle.svg.algebra.JsAlgebraModule.JsAlgebra→doodle.svg.algebra.AlgebraModule.BaseAlgebra
- Direction
- svg.algebra.JsAlgebraModule uses svg.algebra.AlgebraModule, so a change to svg.algebra.AlgebraModule can break svg.algebra.JsAlgebraModule, while a change to svg.algebra.JsAlgebraModule can't break svg.algebra.AlgebraModule.
- Position
- Below the diagonal: svg.algebra.JsAlgebraModule uses a module listed above it, which is the healthy direction.
37→1 svg.algebra.JvmAlgebraModule uses core.font✕
- Connections
- 1 pair of types, where a type in svg.algebra.JvmAlgebraModule uses a type in core.font.
- The types involved
doodle.svg.algebra.JvmAlgebraModule.JvmAlgebra→doodle.core.font.Font
- Direction
- svg.algebra.JvmAlgebraModule uses core.font, so a change to core.font can break svg.algebra.JvmAlgebraModule, while a change to svg.algebra.JvmAlgebraModule can't break core.font.
- Position
- Below the diagonal: svg.algebra.JvmAlgebraModule uses a module listed above it, which is the healthy direction.
37→7 svg.algebra.JvmAlgebraModule uses algebra✕
- Connections
- 3 pairs of types, where a type in svg.algebra.JvmAlgebraModule uses a type in algebra.
- The types involved
doodle.svg.algebra.JvmAlgebraModule.JvmAlgebra→doodle.algebra.Blenddoodle.svg.algebra.JvmAlgebraModule.JvmAlgebra→doodle.algebra.Filterdoodle.svg.algebra.JvmAlgebraModule.JvmAlgebra→doodle.algebra.Text
- Direction
- svg.algebra.JvmAlgebraModule uses algebra, so a change to algebra can break svg.algebra.JvmAlgebraModule, while a change to svg.algebra.JvmAlgebraModule can't break algebra.
- Position
- Below the diagonal: svg.algebra.JvmAlgebraModule uses a module listed above it, which is the healthy direction.
37→11 svg.algebra.JvmAlgebraModule uses image✕
- Connections
- 1 pair of types, where a type in svg.algebra.JvmAlgebraModule uses a type in image.
- The types involved
doodle.svg.algebra.JvmAlgebraModule.JvmAlgebra→doodle.image.Image
- Direction
- svg.algebra.JvmAlgebraModule uses image, so a change to image can break svg.algebra.JvmAlgebraModule, while a change to svg.algebra.JvmAlgebraModule can't break image.
- Position
- Below the diagonal: svg.algebra.JvmAlgebraModule uses a module listed above it, which is the healthy direction.
37→17 svg.algebra.JvmAlgebraModule uses canvas.algebra✕
- Connections
- 1 pair of types, where a type in svg.algebra.JvmAlgebraModule uses a type in canvas.algebra.
- The types involved
doodle.svg.algebra.JvmAlgebraModule.JvmAlgebra→doodle.canvas.algebra.HasTextBoundingBox
- Direction
- svg.algebra.JvmAlgebraModule uses canvas.algebra, so a change to canvas.algebra can break svg.algebra.JvmAlgebraModule, while a change to svg.algebra.JvmAlgebraModule can't break canvas.algebra.
- Position
- Below the diagonal: svg.algebra.JvmAlgebraModule uses a module listed above it, which is the healthy direction.
37→20 svg.algebra.JvmAlgebraModule uses svg.algebra.AlgebraModule✕
- Connections
- 1 pair of types, where a type in svg.algebra.JvmAlgebraModule uses a type in svg.algebra.AlgebraModule.
- The types involved
doodle.svg.algebra.JvmAlgebraModule.JvmAlgebra→doodle.svg.algebra.AlgebraModule.BaseAlgebra
- Direction
- svg.algebra.JvmAlgebraModule uses svg.algebra.AlgebraModule, so a change to svg.algebra.AlgebraModule can break svg.algebra.JvmAlgebraModule, while a change to svg.algebra.JvmAlgebraModule can't break svg.algebra.AlgebraModule.
- Position
- Below the diagonal: svg.algebra.JvmAlgebraModule uses a module listed above it, which is the healthy direction.
38→1 svg.algebra.SvgModule uses core.font✕
- Connections
- 1 pair of types, where a type in svg.algebra.SvgModule uses a type in core.font.
- The types involved
doodle.svg.algebra.SvgModule.Svg→doodle.core.font.Font
- Direction
- svg.algebra.SvgModule uses core.font, so a change to core.font can break svg.algebra.SvgModule, while a change to svg.algebra.SvgModule can't break core.font.
- Position
- Below the diagonal: svg.algebra.SvgModule uses a module listed above it, which is the healthy direction.
38→6 svg.algebra.SvgModule uses core✕
- Connections
- 5 pairs of types, where a type in svg.algebra.SvgModule uses a type in core.
- The types involved
doodle.svg.algebra.SvgModule.Svg→doodle.core.BoundingBoxdoodle.svg.algebra.SvgModule.Svg→doodle.core.Colordoodle.svg.algebra.SvgModule.Svg→doodle.core.Gradientdoodle.svg.algebra.SvgModule.Svg→doodle.core.PathElementdoodle.svg.algebra.SvgModule.Svg→doodle.core.Point
- Direction
- svg.algebra.SvgModule uses core, so a change to core can break svg.algebra.SvgModule, while a change to svg.algebra.SvgModule can't break core.
- Position
- Below the diagonal: svg.algebra.SvgModule uses a module listed above it, which is the healthy direction.
38→7 svg.algebra.SvgModule uses algebra✕
- Connections
- 3 pairs of types, where a type in svg.algebra.SvgModule uses a type in algebra.
- The types involved
doodle.svg.algebra.SvgModule.Svg→doodle.algebra.Picturedoodle.svg.algebra.SvgModule.Svg→doodle.algebra.Sizedoodle.svg.algebra.SvgModule.Svg→doodle.algebra.Transform
- Direction
- svg.algebra.SvgModule uses algebra, so a change to algebra can break svg.algebra.SvgModule, while a change to svg.algebra.SvgModule can't break algebra.
- Position
- Below the diagonal: svg.algebra.SvgModule uses a module listed above it, which is the healthy direction.
38→8 svg.algebra.SvgModule uses core.Gradient✕
- Connections
- 3 pairs of types, where a type in svg.algebra.SvgModule uses a type in core.Gradient.
- The types involved
doodle.svg.algebra.SvgModule.Svg→doodle.core.Gradient.CycleMethoddoodle.svg.algebra.SvgModule.Svg→doodle.core.Gradient.Lineardoodle.svg.algebra.SvgModule.Svg→doodle.core.Gradient.Radial
- Direction
- svg.algebra.SvgModule uses core.Gradient, so a change to core.Gradient can break svg.algebra.SvgModule, while a change to svg.algebra.SvgModule can't break core.Gradient.
- Position
- Below the diagonal: svg.algebra.SvgModule uses a module listed above it, which is the healthy direction.
38→14 svg.algebra.SvgModule uses algebra.generic✕
- Connections
- 2 pairs of types, where a type in svg.algebra.SvgModule uses a type in algebra.generic.
- The types involved
doodle.svg.algebra.SvgModule.Svg→doodle.algebra.generic.Filldoodle.svg.algebra.SvgModule.Svg→doodle.algebra.generic.Stroke
- Direction
- svg.algebra.SvgModule uses algebra.generic, so a change to algebra.generic can break svg.algebra.SvgModule, while a change to svg.algebra.SvgModule can't break algebra.generic.
- Position
- Below the diagonal: svg.algebra.SvgModule uses a module listed above it, which is the healthy direction.
38→18 svg.algebra.SvgModule uses canvas.effect✕
- Connections
- 1 pair of types, where a type in svg.algebra.SvgModule uses a type in canvas.effect.
- The types involved
doodle.svg.algebra.SvgModule.Svg→doodle.canvas.effect.Frame
- Direction
- svg.algebra.SvgModule uses canvas.effect, so a change to canvas.effect can break svg.algebra.SvgModule, while a change to svg.algebra.SvgModule can't break canvas.effect.
- Position
- Below the diagonal: svg.algebra.SvgModule uses a module listed above it, which is the healthy direction.
39→1 svg.effect uses core.font✕
- Connections
- 1 pair of types, where a type in svg.effect uses a type in core.font.
- The types involved
doodle.svg.effect.Canvas→doodle.core.font.Font
- Direction
- svg.effect uses core.font, so a change to core.font can break svg.effect, while a change to svg.effect can't break core.font.
- Position
- Below the diagonal: svg.effect uses a module listed above it, which is the healthy direction.
39→6 svg.effect uses core✕
- Connections
- 3 pairs of types, where a type in svg.effect uses a type in core.
- The types involved
doodle.svg.effect.Canvas→doodle.core.BoundingBoxdoodle.svg.effect.Canvas→doodle.core.Pointdoodle.svg.effect.Frame→doodle.core.Color
- Direction
- svg.effect uses core, so a change to core can break svg.effect, while a change to svg.effect can't break core.
- Position
- Below the diagonal: svg.effect uses a module listed above it, which is the healthy direction.
39→7 svg.effect uses algebra✕
- Connections
- 8 pairs of types, where a type in svg.effect uses a type in algebra.
- The types involved
doodle.svg.effect.Canvas→doodle.algebra.Algebradoodle.svg.effect.Canvas→doodle.algebra.Picturedoodle.svg.effect.Canvas→doodle.algebra.Transformdoodle.svg.effect.Frame→doodle.algebra.Sizedoodle.svg.effect.SvgAnimationRenderer→doodle.algebra.Picturedoodle.svg.effect.SvgRenderer→doodle.algebra.Picturedoodle.svg.effect.SvgWriter→doodle.algebra.Algebradoodle.svg.effect.SvgWriter→doodle.algebra.Picture
- Direction
- svg.effect uses algebra, so a change to algebra can break svg.effect, while a change to svg.effect can't break algebra.
- Position
- Below the diagonal: svg.effect uses a module listed above it, which is the healthy direction.
39→10 svg.effect uses effect✕
- Connections
- 4 pairs of types, where a type in svg.effect uses a type in effect.
- The types involved
doodle.svg.effect.SvgAnimationRenderer→doodle.effect.Rendererdoodle.svg.effect.SvgRenderer→doodle.effect.Rendererdoodle.svg.effect.SvgWriter→doodle.effect.Base64Writerdoodle.svg.effect.SvgWriter→doodle.effect.FileWriter
- Direction
- svg.effect uses effect, so a change to effect can break svg.effect, while a change to svg.effect can't break effect.
- Position
- Below the diagonal: svg.effect uses a module listed above it, which is the healthy direction.
39→16 svg.effect uses interact.effect✕
- Connections
- 1 pair of types, where a type in svg.effect uses a type in interact.effect.
- The types involved
doodle.svg.effect.SvgAnimationRenderer→doodle.interact.effect.AnimationRenderer
- Direction
- svg.effect uses interact.effect, so a change to interact.effect can break svg.effect, while a change to svg.effect can't break interact.effect.
- Position
- Below the diagonal: svg.effect uses a module listed above it, which is the healthy direction.
39→18 svg.effect uses canvas.effect✕
- Connections
- 6 pairs of types, where a type in svg.effect uses a type in canvas.effect.
- The types involved
doodle.svg.effect.Canvas→doodle.canvas.effect.Framedoodle.svg.effect.Frame→doodle.canvas.effect.Framedoodle.svg.effect.SvgAnimationRenderer→doodle.canvas.effect.Canvasdoodle.svg.effect.SvgRenderer→doodle.canvas.effect.Canvasdoodle.svg.effect.SvgRenderer→doodle.canvas.effect.Framedoodle.svg.effect.SvgWriter→doodle.canvas.effect.Frame
- Direction
- svg.effect uses canvas.effect, so a change to canvas.effect can break svg.effect, while a change to svg.effect can't break canvas.effect.
- Position
- Below the diagonal: svg.effect uses a module listed above it, which is the healthy direction.
40→7 doodle uses algebra✕
- Connections
- 1 pair of types, where a type in doodle uses a type in algebra.
- The types involved
doodle.svg→doodle.algebra.Algebra
- Direction
- doodle uses algebra, so a change to algebra can break doodle, while a change to doodle can't break algebra.
- Position
- Below the diagonal: doodle uses a module listed above it, which is the healthy direction.
40→10 doodle uses effect✕
- Connections
- 1 pair of types, where a type in doodle uses a type in effect.
- The types involved
doodle.svg→doodle.effect.Renderer
- Direction
- doodle uses effect, so a change to effect can break doodle, while a change to doodle can't break effect.
- Position
- Below the diagonal: doodle uses a module listed above it, which is the healthy direction.
40→16 doodle uses interact.effect✕
- Connections
- 1 pair of types, where a type in doodle uses a type in interact.effect.
- The types involved
doodle.svg→doodle.interact.effect.AnimationRenderer
- Direction
- doodle uses interact.effect, so a change to interact.effect can break doodle, while a change to doodle can't break interact.effect.
- Position
- Below the diagonal: doodle uses a module listed above it, which is the healthy direction.
40→17 doodle uses canvas.algebra✕
- Connections
- 1 pair of types, where a type in doodle uses a type in canvas.algebra.
- The types involved
doodle.svg→doodle.canvas.algebra.CanvasAlgebra
- Direction
- doodle uses canvas.algebra, so a change to canvas.algebra can break doodle, while a change to doodle can't break canvas.algebra.
- Position
- Below the diagonal: doodle uses a module listed above it, which is the healthy direction.
40→18 doodle uses canvas.effect✕
- Connections
- 2 pairs of types, where a type in doodle uses a type in canvas.effect.
- The types involved
doodle.svg→doodle.canvas.effect.Canvasdoodle.svg→doodle.canvas.effect.Frame
- Direction
- doodle uses canvas.effect, so a change to canvas.effect can break doodle, while a change to doodle can't break canvas.effect.
- Position
- Below the diagonal: doodle uses a module listed above it, which is the healthy direction.
40→29 doodle uses java2d✕
- Connections
- 1 pair of types, where a type in doodle uses a type in java2d.
- The types involved
doodle.java2d→doodle.java2d.Java2dPackage
- Direction
- doodle uses java2d, so a change to java2d can break doodle, while a change to doodle can't break java2d.
- Position
- Below the diagonal: doodle uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 22 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 14 | High / Critical |
Roadmap
Top priorities: Resolve the 92 Orphaned file finding(s) in Knowledge Freshness — start with Algebra.scala (3), CreativeScala.scala (2), Image.scala (2); 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; Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 92 Orphaned file finding(s) in Knowledge Freshness — start with Algebra.scala (3), CreativeScala.scala (2), Image.scala (2). | +4.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. | +3.1 pts | Medium | Architecture documentation |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +2.8 pts | Medium | Observability |
| Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally. | +2.1 pts | Medium | Security & performance tooling |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +2.0 pts | Medium | Documentation (README) |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +1.7 pts | Medium | Nullable reference types |
| Swallowed exception (empty catch) | +1.2 pts | Medium | Exception handling |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +0.5 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.2 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| svg/js/src/main/scala/doodle/svg/effect/Canvas.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| java2d/src/main/java/doodle/java2d/effect/GifEncoder.java | 7.0 | Near-clean | Cyclomatic Complexity: NeuQuant.map (cyclomatic 17) |
| image/shared/src/main/scala/doodle/image/examples/Epicycloid.scala | 7.8 | Near-clean | Code Duplication: Duplicated block (11 lines × 2) |
| svg/js/src/main/scala/doodle/svg/algebra/JsTagged.scala | 7.8 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| REDACTED | 7.9 | Near-clean | Supply-chain Provenance & Signing: REDACTED |
| svg/shared/src/test/scala/doodle/svg/algebra/TestAlgebra.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| svg/jvm/src/main/scala/doodle/svg/algebra/Algebra.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| svg/js/src/main/scala/doodle/svg/algebra/Algebra.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| java2d/src/main/scala/doodle/java2d/algebra/Algebra.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| canvas/src/main/scala/doodle/canvas/algebra/CanvasAlgebra.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| algebra/shared/src/test/scala/doodle/algebra/generic/TestAlgebra.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| image/shared/src/main/scala/doodle/image/examples/Windswept.scala | 8.5 | Near-clean | Cognitive Complexity: Windswept.image (cognitive 21) |
| image/shared/src/main/scala/doodle/image/Image.scala | 8.5 | Near-clean | God Classes: TooManyMethods: Image |
| core/shared/src/main/scala/doodle/core/PathElement.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (12 lines × 2) |
| java2d/src/main/scala/doodle/java2d/algebra/Java2dFromBase64.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (10–11 lines × 2) |
| svg/shared/src/main/scala/doodle/svg/algebra/Path.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 3) |
| canvas/src/main/scala/doodle/canvas/algebra/CanvasDrawing.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
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 57 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 57 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, 164 of 173 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
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 53 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because repo1.maven.org — the registry that answers it — was asked and did not reply (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/de/erichseifert/vectorgraphics2d/VectorGraphics2D/maven-metadata.xml). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add repo1.maven.org to the allowlist and re-run — not to build anything.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (36 contributor(s) across 1301 commit(s) sampled, automation and bot accounts excluded). One of them holds 86% of the history; the other 35 hold 0.4% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D20 ADR Quality — 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 ADR expectation is gated on whether a repository ships a deployable product. Our repo-kind classifier reads .NET project files and the host and package markers of the other ecosystems it knows (a Go `package main`, a Cargo binary, a package.json `bin`, `start` script or application dev server such as Vite or Next, Python console scripts or a Django/WSGI entry point, a Spring Boot / WAR / Gradle application build, a Rack or Rails app, a Composer project, an OTP release or escript, a Dockerfile, a Procfile, a Platform.sh `.platform/routes.yaml`, and the corresponding published-package manifests, including an OTP `*.app.src`, a Drupal module's `*.info` and a Claude Code `.claude-plugin/plugin.json`), and found none here, so we could not tell what kind of repository this is and did not assess its ADR log. This is a gap in our analyzer, not a finding about this repository.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `canvas/src/main/scala/doodle/canvas/algebra/CanvasAlgebra.scala`, `canvas/src/main/scala/doodle/canvas/algebra/CanvasToPicture.scala`, `canvas/src/main/scala/doodle/canvas/package.scala`, `core/shared/src/main/scala/doodle/core/syntax/all.scala`, `svg/js/src/main/scala/doodle/svg/algebra/JsTagged.scala`, … (+1 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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").
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was NeuQuant.map at 17. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Color.fromHex at 28 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: core/shared/src/main/scala/doodle/core/Color.scala (Color.fromHex at 28), image/shared/src/main/scala/doodle/image/Image.scala (Image.compile at 27), algebra/shared/src/main/scala/doodle/algebra/generic/BlendMode.scala (BlendMode.toCssName at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with NeuQuant.map (cyclomatic 17). — Refactoring it lifts Cyclomatic Complexity from 9.8 to about 10.0/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was NeuQuant.map at 58.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with NeuQuant.map (cognitive 58). — Refactoring it lifts Cognitive Complexity from 8.3 to about 9.0/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
2 god class(es) detected.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with GifEncoder.java. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with Image.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
19 duplicated block group(s) detected. 1 of the 19 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 4 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with JsTagged.scala (2), CanvasDrawing.scala, Background.scala. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with Sine.scala, Canvas.scala, ConcentricCircles.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with GifEncoder.java (2), Graphics2DGraphicsContext.scala. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
11 production modules (sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 0 module(s) off the main sequence, with abstractness counted on 9 of the 11 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 5 classes have LCOM4 above 3.
D9 · Test Distribution
136 test methods: 136 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 136 test case(s) across 30 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
7 deducted task-comment markers across 24059 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 7 TodoComment finding(s) in Explicit Debt — start with Algebra.scala (3), TestAlgebra.scala (2), CanvasAlgebra.scala. — One of this dimension's main actionable groups (7 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D26 · Project Cohesion
1 of 1 build units (sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
22 finding(s): 0 critical, 21 high, 1 medium, 0 low. 19 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 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).
- No action in Static Analysis (SAST) — all 19 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (19 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
7 finding(s): 0 critical, 3 high, 4 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
D34 · Knowledge Freshness
93 of 95 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is java2d/src/main/java/doodle/java2d/effect/GifEncoder.java. Counted over 95 of the 283 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 92 Orphaned file finding(s) in Knowledge Freshness — start with Algebra.scala (3), CreativeScala.scala (2), Image.scala (2). — One of this dimension's main actionable groups (92 recommendation-level).
- Resolve the 1 Concentrated knowledge decay 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 GifEncoder.java. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: SvgRenderer.scala↔Svg.scala 62%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with SvgRenderer.scala. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `Blend` declares 16 abstract members: `normal`, `darken`, `multiply`, `colorBurn`, `lighten`, `screen`, `colorDodge`, `overlay`, `softLight`, `hardLight`, `difference`, `exclusion`, `hue`, `saturation`, `color`, `luminosity`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — algebra/shared/src/main/scala/doodle/algebra/Blend.scala:21
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- `mouseOver` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — interact/shared/src/main/scala/doodle/interact/syntax/MouseOverSyntax.scala:30
What to do
- Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `mouseOver` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — interact/shared/src/main/scala/doodle/interact/syntax/MouseOverSyntax.scala:30
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — java2d/src/main/java/doodle/java2d/effect/GifEncoder.java:970, java2d/src/main/java/doodle/java2d/effect/GifEncoder.java:979
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 278 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 60% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 92% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 54% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 56% | Adequate — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 64% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 60 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.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~3595 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- D12 Dependency Hygiene — Dependency currency not established — repo1.maven.org did not answer
- D14 License Compliance — Not scored — this repository's 2 pinned sbt dependency coordinate(s) were read from its 2 sbt build file(s), but Maven Central could not be asked for the licence of 2 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/de/erichseifert/vectorgraphics2d/VectorGraphics2D/0.13/VectorGraphics2D-0.13.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — Repository kind not determined
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, Scala not measured.
- 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 — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 6 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 80 value object(s); 4 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM 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 — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, 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 applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Java and Scala code has 24,705 production line(s), 4 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- S1 Web-Security Posture — No web surface: 279 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server artifact (akka-http, pekko-http, http4s, Play, Finagle, zio-http, cask, Scalatra, a tapir server, Jetty, Undertow, …) outside test scope in its build, and no server package imported or server bound in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- 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 — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
- 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 — 24 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
Serious — 49 finding(s)
- TodoComment svg/shared/src/test/scala/doodle/svg/algebra/TestAlgebra.scala:68
- TodoComment svg/jvm/src/main/scala/doodle/svg/algebra/Algebra.scala:87
- TodoComment svg/js/src/main/scala/doodle/svg/algebra/Algebra.scala:73
- TodoComment java2d/src/main/scala/doodle/java2d/algebra/Algebra.scala:71
- TodoComment canvas/src/main/scala/doodle/canvas/algebra/CanvasAlgebra.scala:72
- TodoComment algebra/shared/src/test/scala/doodle/algebra/generic/TestAlgebra.scala:62
- TodoComment svg/js/src/main/scala/doodle/svg/effect/Canvas.scala:146
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (10 lines × 2) canvas/src/main/scala/doodle/canvas/algebra/CanvasDrawing.scala:94
- Duplicated block (10 lines × 2) image/jvm/src/main/scala/doodle/image/examples/Background.scala:30
- Duplicated block (10 lines × 2) svg/js/src/main/scala/doodle/svg/algebra/JsTagged.scala:40
- Duplicated block (10 lines × 2) svg/js/src/main/scala/doodle/svg/algebra/JsTagged.scala:59
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (7 lines × 2) image/shared/src/main/scala/doodle/image/examples/Sine.scala:68
- Duplicated block (7 lines × 2) svg/js/src/main/scala/doodle/svg/effect/Canvas.scala:80
- Duplicated block (7 lines × 2) examples/js/src/main/scala/doodle/examples/ConcentricCircles.scala:30
- Duplicated block (5 lines × 2) java2d/src/main/scala/doodle/java2d/algebra/Graphics2DGraphicsContext.scala:82
- Duplicated block (5 lines × 2) java2d/src/main/java/doodle/java2d/effect/GifEncoder.java:968
- Duplicated block (5 lines × 2) java2d/src/main/java/doodle/java2d/effect/GifEncoder.java:792
- Swallowed exception (empty catch) java2d/src/main/java/doodle/java2d/effect/GifEncoder.java:970
- Swallowed exception (empty catch) java2d/src/main/java/doodle/java2d/effect/GifEncoder.java:979
- NeuQuant.map (cyclomatic 17) java2d/src/main/java/doodle/java2d/effect/GifEncoder.java:852
- NeuQuant.map (cognitive 58) java2d/src/main/java/doodle/java2d/effect/GifEncoder.java:852
- NeuQuant.learn (cognitive 23) java2d/src/main/java/doodle/java2d/effect/GifEncoder.java:774
- LZWEncoder.compress (cognitive 22) java2d/src/main/java/doodle/java2d/effect/GifEncoder.java:1188
- Windswept.image (cognitive 21) image/shared/src/main/scala/doodle/image/examples/Windswept.scala:151
- REDACTED
- FileTooLong: effect/GifEncoder.java java2d/src/main/java/doodle/java2d/effect/GifEncoder.java
- TooManyMethods: Image image/shared/src/main/scala/doodle/image/Image.scala:24
- Change coupling: SvgRenderer.scala ↔ Svg.scala svg/js/src/main/scala/doodle/svg/effect/SvgRenderer.scala:1
- REDACTED
- REDACTED
- Duplicated block (12 lines × 2) core/shared/src/main/scala/doodle/core/PathElement.scala:164
- Duplicated block (11 lines × 2) image/shared/src/main/scala/doodle/image/examples/Epicycloid.scala:34
- Duplicated block (10–11 lines × 2) java2d/src/main/scala/doodle/java2d/algebra/Java2dFromBase64.scala:55
- Duplicated block (10 lines × 3) svg/shared/src/main/scala/doodle/svg/algebra/Path.scala:44
- Duplicated block (9 lines × 2) image/shared/src/main/scala/doodle/image/examples/Epicycloid.scala:61
- Duplicated block (6 lines × 3) algebra/js/src/main/scala/doodle/syntax/RendererSyntax.scala:25
- Duplicated block (7 lines × 4) image/shared/src/main/scala/doodle/image/examples/BrownianMotion.scala:34
- Duplicated block (6 lines × 4) image/shared/src/main/scala/doodle/image/examples/CreativeScala.scala:515
- Duplicated block (18 lines × 2) java2d/src/main/java/doodle/java2d/effect/GifEncoder.java:871
- Unfinished stub — body is `???` interact/shared/src/main/scala/doodle/interact/syntax/MouseOverSyntax.scala:30
- Unfinished stub — body is ??? / NotImplementedError interact/shared/src/main/scala/doodle/interact/syntax/MouseOverSyntax.scala:30
- No structured logging
Minor — 100 finding(s)
- Orphaned file image/shared/src/main/scala/doodle/image/examples/CreativeScala.scala:1
- Orphaned file core/shared/src/main/scala/doodle/core/Tailwind4Colors.scala:1
- Orphaned file interact/shared/src/main/scala/doodle/interact/animation/Transducer.scala:1
- Orphaned file core/shared/src/main/scala/doodle/core/Color.scala:1
- Orphaned file core/shared/src/main/scala/doodle/core/CrayolaColors.scala:1
- Orphaned file core/shared/src/main/scala/doodle/core/PathElement.scala:1
- Orphaned file image/shared/src/main/scala/doodle/image/Image.scala:1
- Orphaned file canvas/src/main/scala/doodle/canvas/algebra/CanvasDrawing.scala:1
- Orphaned file build.sbt:1
- Orphaned file core/shared/src/main/scala/doodle/core/Parametric.scala:1
- Orphaned file interact/shared/src/main/scala/doodle/interact/animation/Interpolator.scala:1
- Orphaned file java2d/src/main/scala/doodle/java2d/algebra/reified/Reified.scala:1
- Orphaned file core/shared/src/main/scala/doodle/core/CommonColors.scala:1
- Orphaned file java2d/src/main/scala/doodle/java2d/algebra/Java2D.scala:1
- Orphaned file java2d/src/main/scala/doodle/java2d/effect/Java2DPanel.scala:1
- Orphaned file svg/shared/src/main/scala/doodle/svg/algebra/Filter.scala:1
- Orphaned file algebra/shared/src/main/scala/doodle/syntax/LayoutSyntax.scala:1
- Orphaned file interact/shared/src/main/scala/doodle/interact/syntax/AbstractAnimationRendererSyntax.scala:1
- Orphaned file canvas/src/main/scala/doodle/canvas/effect/Canvas.scala:1
- Orphaned file interact/shared/src/main/scala/doodle/interact/animation/Interpolation.scala:1
- Orphaned file image/shared/src/main/scala/doodle/image/examples/Sine.scala:1
- Orphaned file java2d/src/main/scala/doodle/java2d/algebra/Graphics2DGraphicsContext.scala:1
- Orphaned file java2d/src/main/scala/doodle/java2d/effect/Java2d.scala:1
- Orphaned file core/shared/src/main/scala/doodle/random/Random.scala:1
- Orphaned file java2d/src/main/scala/doodle/java2d/effect/Java2dWriter.scala:1
- Fat interface: Blend (16 abstract members) algebra/shared/src/main/scala/doodle/algebra/Blend.scala:21
- Projects may be oversized for their cohesion
- Concentrated knowledge decay
- Most significant orphaned file java2d/src/main/java/doodle/java2d/effect/GifEncoder.java:1
- REDACTED
- REDACTED
- No ADRs
- Scala's null is not held to the type system everywhere
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-a9c3a08468aa47cbbf0caf89ca69a163/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-a9c3a08468aa47cbbf0caf89ca69a163/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 . | 22 | 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/** . --skip-db-update | 7 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 6 file(s) — `canvas/src/main/scala/doodle/canvas/algebra/CanvasAlgebra.scala`, `canvas/src/main/scala/doodle/canvas/algebra/CanvasToPicture.scala`, `canvas/src/main/scala/doodle/canvas/package.scala`, `core/shared/src/main/scala/doodle/core/syntax/all.scala`, `svg/js/src/main/scala/doodle/svg/algebra/JsTagged.scala`, … (+1 more) — so the PII/GDPR sweep did not cover them at all. | 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/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |