Executive summary
raquo/Laminar falls short of our standard for production, in part because we found no recorded design decisions and no architecture document or diagram. It scores 59 out of 100 and is rated Adequate, and nine of its ten critical findings are security problems in the build pipeline.
Maturity, at 51, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 7 points. Adding build and run instructions to the README is another step, worth about 5 points. Raising Maturity to 70 would lift the score to about 64.
Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One set of files in separate parts keeps changing together, which points to a hidden dependency. Pinning each tool to an exact version and making the hidden dependencies explicit would close both risks.
The product code is 17,760 lines, about €37,000 to rebuild.
If Maturity rose from 51 to 70, the lowest score rated Strong, the score would rise from 59 to about 64.
New since the last survey: 2 findings
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 1 finding
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €37,000 · Estimate
| Cost to rebuild | €12,000 to €61,000, for 204 to 646 hours of work, about 0.3 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 | Small: 17,760 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 raquo | 2 raquo.laminar.api.StyleUnitsApi | 3 raquo.laminar.codecs | 4 raquo.laminar.defs.styles.units | 5 raquo.laminar.defs.symbols | 6 raquo.laminar.domapi.DomKeysRaw | 7 raquo.laminar.domext | 8 raquo.laminar.lifecycle | 9 raquo.laminar.api.Laminar.mathml | 10 raquo.laminar.modifiers.SimpleKeySetter | 11 raquo.laminar.defs.styles.traits | 12 raquo.laminar.keys | 13 raquo.laminar.defs.attrs | 14 raquo.laminar.defs.complex | 15 raquo.laminar.defs.eventProps | 16 raquo.laminar.defs.props | 17 raquo.laminar.defs.styles | 18 raquo.laminar.inputs | 19 raquo.laminar.inputs.InputController | 20 raquo.laminar.keys.HtmlProp | 21 raquo.laminar.modifiers | 22 raquo.laminar.keys.SimpleKey | 23 raquo.laminar.tags | 24 raquo.laminar.defs.tags | 25 raquo.laminar.nodes | 26 raquo.laminar.inserters | 27 raquo.laminar.api.Implicits | 28 raquo.laminar.inserters.InserterType | 29 raquo.laminar.receivers | 30 raquo.laminar.receivers.ChildOptionReceiver | 31 raquo.laminar.receivers.ChildReceiver | 32 raquo.laminar.receivers.ChildrenReceiver | 33 raquo.laminar.api | 34 raquo.laminar | 35 raquo.laminar.api.Laminar | 36 raquo.laminar.domapi | 37 raquo.laminar.inserters.CollectionCommand | 38 raquo.laminar.keys.CompositeValueMapper.Implicits | 39 raquo.laminar.modifiers.RenderableSeq | 40 raquo.laminar.domapi.DomApi |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 raquo | ||||||||||||||||||||||||||||||||||||||||
| 2 raquo.laminar.api.StyleUnitsApi | ||||||||||||||||||||||||||||||||||||||||
| 3 raquo.laminar.codecs | ||||||||||||||||||||||||||||||||||||||||
| 4 raquo.laminar.defs.styles.units | ||||||||||||||||||||||||||||||||||||||||
| 5 raquo.laminar.defs.symbols | ||||||||||||||||||||||||||||||||||||||||
| 6 raquo.laminar.domapi.DomKeysRaw | ||||||||||||||||||||||||||||||||||||||||
| 7 raquo.laminar.domext | ||||||||||||||||||||||||||||||||||||||||
| 8 raquo.laminar.lifecycle | ||||||||||||||||||||||||||||||||||||||||
| 9 raquo.laminar.api.Laminar.mathml | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 raquo.laminar.modifiers.SimpleKeySetter | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 11 raquo.laminar.defs.styles.traits | 5 | 47 | ||||||||||||||||||||||||||||||||||||||
| 12 raquo.laminar.keys | 8 | 1 | 2 | 1 | 5 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 13 raquo.laminar.defs.attrs | 5 | 5 | ||||||||||||||||||||||||||||||||||||||
| 14 raquo.laminar.defs.complex | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 raquo.laminar.defs.eventProps | 4 | |||||||||||||||||||||||||||||||||||||||
| 16 raquo.laminar.defs.props | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 raquo.laminar.defs.styles | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 raquo.laminar.inputs | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 raquo.laminar.inputs.InputController | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 raquo.laminar.keys.HtmlProp | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 raquo.laminar.modifiers | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 22 raquo.laminar.keys.SimpleKey | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 raquo.laminar.tags | 1 | 1 | 3 | 3 | ||||||||||||||||||||||||||||||||||||
| 24 raquo.laminar.defs.tags | 3 | |||||||||||||||||||||||||||||||||||||||
| 25 raquo.laminar.nodes | 6 | 1 | 2 | 4 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 26 raquo.laminar.inserters | 6 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 27 raquo.laminar.api.Implicits | 2 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 raquo.laminar.inserters.InserterType | 3 | |||||||||||||||||||||||||||||||||||||||
| 29 raquo.laminar.receivers | 4 | 6 | ||||||||||||||||||||||||||||||||||||||
| 30 raquo.laminar.receivers.ChildOptionReceiver | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 raquo.laminar.receivers.ChildReceiver | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 raquo.laminar.receivers.ChildrenReceiver | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 raquo.laminar.api | 2 | 4 | 1 | 1 | 5 | 2 | 1 | 1 | 1 | 1 | 11 | 3 | 1 | 7 | 4 | 1 | ||||||||||||||||||||||||
| 34 raquo.laminar | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 35 raquo.laminar.api.Laminar | 7 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 raquo.laminar.domapi | 5 | 1 | 7 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 37 raquo.laminar.inserters.CollectionCommand | 7 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 raquo.laminar.keys.CompositeValueMapper.Implicits | 8 | 4 | ||||||||||||||||||||||||||||||||||||||
| 39 raquo.laminar.modifiers.RenderableSeq | 8 | 8 | ||||||||||||||||||||||||||||||||||||||
| 40 raquo.laminar.domapi.DomApi | 2 |
9→5 raquo.laminar.api.Laminar.mathml uses raquo.laminar.defs.symbols✕
- Connections
- 1 pair of types, where a type in raquo.laminar.api.Laminar.mathml uses a type in raquo.laminar.defs.symbols.
- The types involved
com.raquo.laminar.api.Laminar.mathml.symbols→com.raquo.laminar.defs.symbols.MathMlSymbols
- Direction
- raquo.laminar.api.Laminar.mathml uses raquo.laminar.defs.symbols, so a change to raquo.laminar.defs.symbols can break raquo.laminar.api.Laminar.mathml, while a change to raquo.laminar.api.Laminar.mathml can't break raquo.laminar.defs.symbols.
- Position
- Below the diagonal: raquo.laminar.api.Laminar.mathml uses a module listed above it, which is the healthy direction.
10→12 raquo.laminar.modifiers.SimpleKeySetter uses raquo.laminar.keys part of a loop✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.modifiers.SimpleKeySetter uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.modifiers.SimpleKeySetter.DerivedStyleSetter→com.raquo.laminar.keys.DerivedStylePropcom.raquo.laminar.modifiers.SimpleKeySetter.StyleSetter→com.raquo.laminar.keys.StyleProp
- Direction
- raquo.laminar.modifiers.SimpleKeySetter uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.modifiers.SimpleKeySetter, while a change to raquo.laminar.modifiers.SimpleKeySetter can't break raquo.laminar.keys.
- 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→21 raquo.laminar.modifiers.SimpleKeySetter uses raquo.laminar.modifiers part of a loop✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.modifiers.SimpleKeySetter uses a type in raquo.laminar.modifiers.
- The types involved
com.raquo.laminar.modifiers.SimpleKeySetter.DerivedStyleSetter→com.raquo.laminar.modifiers.SimpleKeySettercom.raquo.laminar.modifiers.SimpleKeySetter.StyleSetter→com.raquo.laminar.modifiers.SimpleKeySetter
- Direction
- raquo.laminar.modifiers.SimpleKeySetter uses raquo.laminar.modifiers, so a change to raquo.laminar.modifiers can break raquo.laminar.modifiers.SimpleKeySetter, while a change to raquo.laminar.modifiers.SimpleKeySetter can't break raquo.laminar.modifiers.
- 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→4 raquo.laminar.defs.styles.traits uses raquo.laminar.defs.styles.units✕
- Connections
- 5 pairs of types, where a type in raquo.laminar.defs.styles.traits uses a type in raquo.laminar.defs.styles.units.
- The types involved
com.raquo.laminar.defs.styles.traits.BackgroundSize→com.raquo.laminar.defs.styles.units.Lengthcom.raquo.laminar.defs.styles.traits.FontSize→com.raquo.laminar.defs.styles.units.Lengthcom.raquo.laminar.defs.styles.traits.LineWidth→com.raquo.laminar.defs.styles.units.Lengthcom.raquo.laminar.defs.styles.traits.MinMaxLength→com.raquo.laminar.defs.styles.units.Lengthcom.raquo.laminar.defs.styles.traits.VerticalAlign→com.raquo.laminar.defs.styles.units.Length
- Direction
- raquo.laminar.defs.styles.traits uses raquo.laminar.defs.styles.units, so a change to raquo.laminar.defs.styles.units can break raquo.laminar.defs.styles.traits, while a change to raquo.laminar.defs.styles.traits can't break raquo.laminar.defs.styles.units.
- Position
- Below the diagonal: raquo.laminar.defs.styles.traits uses a module listed above it, which is the healthy direction.
11→10 raquo.laminar.defs.styles.traits uses raquo.laminar.modifiers.SimpleKeySetter✕
- Connections
- 47 pairs of types, where a type in raquo.laminar.defs.styles.traits uses a type in raquo.laminar.modifiers.SimpleKeySetter. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.raquo.laminar.defs.styles.traits.AlignContent→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.Auto→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.BackfaceVisibility→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.BackgroundAttachment→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.BackgroundSize→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.BorderCollapse→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.BoxSizing→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.Clear→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.Color→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.Cursor→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.Direction→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.Display→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.EmptyCells→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.FlexDirection→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.FlexPosition→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.FlexWrap→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.Float→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.FontFeatureSettings→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.FontSize→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.FontStyle→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.FontWeight→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.GlobalKeywords→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.JustifyContent→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.Line→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSettercom.raquo.laminar.defs.styles.traits.LineWidth→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSetter
- Direction
- raquo.laminar.defs.styles.traits uses raquo.laminar.modifiers.SimpleKeySetter, so a change to raquo.laminar.modifiers.SimpleKeySetter can break raquo.laminar.defs.styles.traits, while a change to raquo.laminar.defs.styles.traits can't break raquo.laminar.modifiers.SimpleKeySetter.
- Position
- Below the diagonal: raquo.laminar.defs.styles.traits uses a module listed above it, which is the healthy direction.
12→3 raquo.laminar.keys uses raquo.laminar.codecs✕
- Connections
- 8 pairs of types, where a type in raquo.laminar.keys uses a type in raquo.laminar.codecs.
- The types involved
com.raquo.laminar.keys.AriaAttr→com.raquo.laminar.codecs.Codeccom.raquo.laminar.keys.CompositeKey→com.raquo.laminar.codecs.CompositeCodeccom.raquo.laminar.keys.GlobalAttr→com.raquo.laminar.codecs.Codeccom.raquo.laminar.keys.HtmlAttr→com.raquo.laminar.codecs.Codeccom.raquo.laminar.keys.HtmlProp→com.raquo.laminar.codecs.Codeccom.raquo.laminar.keys.MathMlAttr→com.raquo.laminar.codecs.Codeccom.raquo.laminar.keys.SimpleAttr→com.raquo.laminar.codecs.Codeccom.raquo.laminar.keys.SvgAttr→com.raquo.laminar.codecs.Codec
- Direction
- raquo.laminar.keys uses raquo.laminar.codecs, so a change to raquo.laminar.codecs can break raquo.laminar.keys, while a change to raquo.laminar.keys can't break raquo.laminar.codecs.
- Position
- Below the diagonal: raquo.laminar.keys uses a module listed above it, which is the healthy direction.
12→4 raquo.laminar.keys uses raquo.laminar.defs.styles.units✕
- Connections
- 1 pair of types, where a type in raquo.laminar.keys uses a type in raquo.laminar.defs.styles.units.
- The types involved
com.raquo.laminar.keys.StyleProp→com.raquo.laminar.defs.styles.units.GlobalUnits
- Direction
- raquo.laminar.keys uses raquo.laminar.defs.styles.units, so a change to raquo.laminar.defs.styles.units can break raquo.laminar.keys, while a change to raquo.laminar.keys can't break raquo.laminar.defs.styles.units.
- Position
- Below the diagonal: raquo.laminar.keys uses a module listed above it, which is the healthy direction.
12→10 raquo.laminar.keys uses raquo.laminar.modifiers.SimpleKeySetter✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.keys uses a type in raquo.laminar.modifiers.SimpleKeySetter.
- The types involved
com.raquo.laminar.keys.DerivedStyleProp→com.raquo.laminar.modifiers.SimpleKeySetter.DerivedStyleSettercom.raquo.laminar.keys.StyleProp→com.raquo.laminar.modifiers.SimpleKeySetter.StyleSetter
- Direction
- raquo.laminar.keys uses raquo.laminar.modifiers.SimpleKeySetter, so a change to raquo.laminar.modifiers.SimpleKeySetter can break raquo.laminar.keys, while a change to raquo.laminar.keys can't break raquo.laminar.modifiers.SimpleKeySetter.
- Position
- Below the diagonal: raquo.laminar.keys uses a module listed above it, which is the healthy direction.
12→11 raquo.laminar.keys uses raquo.laminar.defs.styles.traits✕
- Connections
- 1 pair of types, where a type in raquo.laminar.keys uses a type in raquo.laminar.defs.styles.traits.
- The types involved
com.raquo.laminar.keys.StyleProp→com.raquo.laminar.defs.styles.traits.GlobalKeywords
- Direction
- raquo.laminar.keys uses raquo.laminar.defs.styles.traits, so a change to raquo.laminar.defs.styles.traits can break raquo.laminar.keys, while a change to raquo.laminar.keys can't break raquo.laminar.defs.styles.traits.
- Position
- Below the diagonal: raquo.laminar.keys uses a module listed above it, which is the healthy direction.
12→21 raquo.laminar.keys uses raquo.laminar.modifiers part of a loop✕
- Connections
- 5 pairs of types, where a type in raquo.laminar.keys uses a type in raquo.laminar.modifiers.
- The types involved
com.raquo.laminar.keys.CompositeKey→com.raquo.laminar.modifiers.CompositeKeySettercom.raquo.laminar.keys.CompositeKey→com.raquo.laminar.modifiers.CompositeKeyUpdatercom.raquo.laminar.keys.EventProcessor→com.raquo.laminar.modifiers.EventListenercom.raquo.laminar.keys.SimpleKey→com.raquo.laminar.modifiers.SimpleKeySettercom.raquo.laminar.keys.SimpleKey→com.raquo.laminar.modifiers.SimpleKeyUpdater
- Direction
- raquo.laminar.keys uses raquo.laminar.modifiers, so a change to raquo.laminar.modifiers can break raquo.laminar.keys, while a change to raquo.laminar.keys can't break raquo.laminar.modifiers.
- 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.
12→33 raquo.laminar.keys uses raquo.laminar.api part of a loop✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.keys uses a type in raquo.laminar.api.
- The types involved
com.raquo.laminar.keys.EventProcessor→com.raquo.laminar.api.UnitArrowsFeaturecom.raquo.laminar.keys.LockedEventKey→com.raquo.laminar.api.UnitArrowsFeature
- Direction
- raquo.laminar.keys uses raquo.laminar.api, so a change to raquo.laminar.api can break raquo.laminar.keys, while a change to raquo.laminar.keys can't break raquo.laminar.api.
- 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.
12→34 raquo.laminar.keys uses raquo.laminar part of a loop✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.keys uses a type in raquo.laminar.
- The types involved
com.raquo.laminar.keys.CompositeKey→com.raquo.laminar.Seqcom.raquo.laminar.keys.StyleProp→com.raquo.laminar.Seq
- Direction
- raquo.laminar.keys uses raquo.laminar, so a change to raquo.laminar can break raquo.laminar.keys, while a change to raquo.laminar.keys can't break raquo.laminar.
- 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→3 raquo.laminar.defs.attrs uses raquo.laminar.codecs✕
- Connections
- 5 pairs of types, where a type in raquo.laminar.defs.attrs uses a type in raquo.laminar.codecs.
- The types involved
com.raquo.laminar.defs.attrs.AriaAttrs→com.raquo.laminar.codecs.Codeccom.raquo.laminar.defs.attrs.GlobalAttrs→com.raquo.laminar.codecs.Codeccom.raquo.laminar.defs.attrs.HtmlAttrs→com.raquo.laminar.codecs.Codeccom.raquo.laminar.defs.attrs.MathMlAttrs→com.raquo.laminar.codecs.Codeccom.raquo.laminar.defs.attrs.SvgAttrs→com.raquo.laminar.codecs.Codec
- Direction
- raquo.laminar.defs.attrs uses raquo.laminar.codecs, so a change to raquo.laminar.codecs can break raquo.laminar.defs.attrs, while a change to raquo.laminar.defs.attrs can't break raquo.laminar.codecs.
- Position
- Below the diagonal: raquo.laminar.defs.attrs uses a module listed above it, which is the healthy direction.
13→12 raquo.laminar.defs.attrs uses raquo.laminar.keys✕
- Connections
- 5 pairs of types, where a type in raquo.laminar.defs.attrs uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.defs.attrs.AriaAttrs→com.raquo.laminar.keys.AriaAttrcom.raquo.laminar.defs.attrs.GlobalAttrs→com.raquo.laminar.keys.GlobalAttrcom.raquo.laminar.defs.attrs.HtmlAttrs→com.raquo.laminar.keys.HtmlAttrcom.raquo.laminar.defs.attrs.MathMlAttrs→com.raquo.laminar.keys.MathMlAttrcom.raquo.laminar.defs.attrs.SvgAttrs→com.raquo.laminar.keys.SvgAttr
- Direction
- raquo.laminar.defs.attrs uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.defs.attrs, while a change to raquo.laminar.defs.attrs can't break raquo.laminar.keys.
- Position
- Below the diagonal: raquo.laminar.defs.attrs uses a module listed above it, which is the healthy direction.
14→12 raquo.laminar.defs.complex uses raquo.laminar.keys✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.defs.complex uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.defs.complex.ComplexGlobalKeys→com.raquo.laminar.keys.HtmlAttrcom.raquo.laminar.defs.complex.ComplexHtmlKeys→com.raquo.laminar.keys.HtmlAttr
- Direction
- raquo.laminar.defs.complex uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.defs.complex, while a change to raquo.laminar.defs.complex can't break raquo.laminar.keys.
- Position
- Below the diagonal: raquo.laminar.defs.complex uses a module listed above it, which is the healthy direction.
15→12 raquo.laminar.defs.eventProps uses raquo.laminar.keys✕
- Connections
- 4 pairs of types, where a type in raquo.laminar.defs.eventProps uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.defs.eventProps.DocumentEventProps→com.raquo.laminar.keys.EventPropcom.raquo.laminar.defs.eventProps.EventProps→com.raquo.laminar.keys.EventPropcom.raquo.laminar.defs.eventProps.GlobalEventProps→com.raquo.laminar.keys.EventPropcom.raquo.laminar.defs.eventProps.WindowEventProps→com.raquo.laminar.keys.EventProp
- Direction
- raquo.laminar.defs.eventProps uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.defs.eventProps, while a change to raquo.laminar.defs.eventProps can't break raquo.laminar.keys.
- Position
- Below the diagonal: raquo.laminar.defs.eventProps uses a module listed above it, which is the healthy direction.
16→3 raquo.laminar.defs.props uses raquo.laminar.codecs✕
- Connections
- 1 pair of types, where a type in raquo.laminar.defs.props uses a type in raquo.laminar.codecs.
- The types involved
com.raquo.laminar.defs.props.HtmlProps→com.raquo.laminar.codecs.Codec
- Direction
- raquo.laminar.defs.props uses raquo.laminar.codecs, so a change to raquo.laminar.codecs can break raquo.laminar.defs.props, while a change to raquo.laminar.defs.props can't break raquo.laminar.codecs.
- Position
- Below the diagonal: raquo.laminar.defs.props uses a module listed above it, which is the healthy direction.
16→12 raquo.laminar.defs.props uses raquo.laminar.keys✕
- Connections
- 1 pair of types, where a type in raquo.laminar.defs.props uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.defs.props.HtmlProps→com.raquo.laminar.keys.HtmlProp
- Direction
- raquo.laminar.defs.props uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.defs.props, while a change to raquo.laminar.defs.props can't break raquo.laminar.keys.
- Position
- Below the diagonal: raquo.laminar.defs.props uses a module listed above it, which is the healthy direction.
17→12 raquo.laminar.defs.styles uses raquo.laminar.keys✕
- Connections
- 1 pair of types, where a type in raquo.laminar.defs.styles uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.defs.styles.StyleProps→com.raquo.laminar.keys.StyleProp
- Direction
- raquo.laminar.defs.styles uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.defs.styles, while a change to raquo.laminar.defs.styles can't break raquo.laminar.keys.
- Position
- Below the diagonal: raquo.laminar.defs.styles uses a module listed above it, which is the healthy direction.
18→12 raquo.laminar.inputs uses raquo.laminar.keys✕
- Connections
- 1 pair of types, where a type in raquo.laminar.inputs uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.inputs.InputController→com.raquo.laminar.keys.EventProp
- Direction
- raquo.laminar.inputs uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.inputs, while a change to raquo.laminar.inputs can't break raquo.laminar.keys.
- Position
- Below the diagonal: raquo.laminar.inputs uses a module listed above it, which is the healthy direction.
19→12 raquo.laminar.inputs.InputController uses raquo.laminar.keys✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.inputs.InputController uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.inputs.InputController.InputControllerConfig→com.raquo.laminar.keys.EventPropcom.raquo.laminar.inputs.InputController.InputControllerConfig→com.raquo.laminar.keys.HtmlProp
- Direction
- raquo.laminar.inputs.InputController uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.inputs.InputController, while a change to raquo.laminar.inputs.InputController can't break raquo.laminar.keys.
- Position
- Below the diagonal: raquo.laminar.inputs.InputController uses a module listed above it, which is the healthy direction.
19→25 raquo.laminar.inputs.InputController uses raquo.laminar.nodes part of a loop✕
- Connections
- 1 pair of types, where a type in raquo.laminar.inputs.InputController uses a type in raquo.laminar.nodes.
- The types involved
com.raquo.laminar.inputs.InputController.InputControllerConfig→com.raquo.laminar.nodes.ReactiveHtmlElement
- Direction
- raquo.laminar.inputs.InputController uses raquo.laminar.nodes, so a change to raquo.laminar.nodes can break raquo.laminar.inputs.InputController, while a change to raquo.laminar.inputs.InputController can't break raquo.laminar.nodes.
- 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.
20→3 raquo.laminar.keys.HtmlProp uses raquo.laminar.codecs✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.keys.HtmlProp uses a type in raquo.laminar.codecs.
- The types involved
com.raquo.laminar.keys.HtmlProp.SlotHtmlProp→com.raquo.laminar.codecs.Codeccom.raquo.laminar.keys.HtmlProp.ValueHtmlProp→com.raquo.laminar.codecs.Codec
- Direction
- raquo.laminar.keys.HtmlProp uses raquo.laminar.codecs, so a change to raquo.laminar.codecs can break raquo.laminar.keys.HtmlProp, while a change to raquo.laminar.keys.HtmlProp can't break raquo.laminar.codecs.
- Position
- Below the diagonal: raquo.laminar.keys.HtmlProp uses a module listed above it, which is the healthy direction.
20→12 raquo.laminar.keys.HtmlProp uses raquo.laminar.keys✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.keys.HtmlProp uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.keys.HtmlProp.SlotHtmlProp→com.raquo.laminar.keys.HtmlPropcom.raquo.laminar.keys.HtmlProp.ValueHtmlProp→com.raquo.laminar.keys.HtmlProp
- Direction
- raquo.laminar.keys.HtmlProp uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.keys.HtmlProp, while a change to raquo.laminar.keys.HtmlProp can't break raquo.laminar.keys.
- Position
- Below the diagonal: raquo.laminar.keys.HtmlProp uses a module listed above it, which is the healthy direction.
21→12 raquo.laminar.modifiers uses raquo.laminar.keys✕
- Connections
- 1 pair of types, where a type in raquo.laminar.modifiers uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.modifiers.EventListener→com.raquo.laminar.keys.EventProcessor
- Direction
- raquo.laminar.modifiers uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.modifiers, while a change to raquo.laminar.modifiers can't break raquo.laminar.keys.
- Position
- Below the diagonal: raquo.laminar.modifiers uses a module listed above it, which is the healthy direction.
21→26 raquo.laminar.modifiers uses raquo.laminar.inserters part of a loop✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.modifiers uses a type in raquo.laminar.inserters.
- The types involved
com.raquo.laminar.modifiers.RenderableInserter→com.raquo.laminar.inserters.Insertercom.raquo.laminar.modifiers.RenderableNode→com.raquo.laminar.inserters.Inserter
- Direction
- raquo.laminar.modifiers uses raquo.laminar.inserters, so a change to raquo.laminar.inserters can break raquo.laminar.modifiers, while a change to raquo.laminar.modifiers can't break raquo.laminar.inserters.
- 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.
21→34 raquo.laminar.modifiers uses raquo.laminar part of a loop✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.modifiers uses a type in raquo.laminar.
- The types involved
com.raquo.laminar.modifiers.RenderableNode→com.raquo.laminar.Seqcom.raquo.laminar.modifiers.RenderableSeq→com.raquo.laminar.Seq
- Direction
- raquo.laminar.modifiers uses raquo.laminar, so a change to raquo.laminar can break raquo.laminar.modifiers, while a change to raquo.laminar.modifiers can't break raquo.laminar.
- 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.
22→12 raquo.laminar.keys.SimpleKey uses raquo.laminar.keys✕
- Connections
- 1 pair of types, where a type in raquo.laminar.keys.SimpleKey uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.keys.SimpleKey.SimpleKeyExt→com.raquo.laminar.keys.SimpleKey
- Direction
- raquo.laminar.keys.SimpleKey uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.keys.SimpleKey, while a change to raquo.laminar.keys.SimpleKey can't break raquo.laminar.keys.
- Position
- Below the diagonal: raquo.laminar.keys.SimpleKey uses a module listed above it, which is the healthy direction.
22→21 raquo.laminar.keys.SimpleKey uses raquo.laminar.modifiers✕
- Connections
- 1 pair of types, where a type in raquo.laminar.keys.SimpleKey uses a type in raquo.laminar.modifiers.
- The types involved
com.raquo.laminar.keys.SimpleKey.SimpleKeyExt→com.raquo.laminar.modifiers.SimpleKeyUpdater
- Direction
- raquo.laminar.keys.SimpleKey uses raquo.laminar.modifiers, so a change to raquo.laminar.modifiers can break raquo.laminar.keys.SimpleKey, while a change to raquo.laminar.keys.SimpleKey can't break raquo.laminar.modifiers.
- Position
- Below the diagonal: raquo.laminar.keys.SimpleKey uses a module listed above it, which is the healthy direction.
23→12 raquo.laminar.tags uses raquo.laminar.keys✕
- Connections
- 1 pair of types, where a type in raquo.laminar.tags uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.tags.CustomHtmlTag→com.raquo.laminar.keys.HtmlProp
- Direction
- raquo.laminar.tags uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.tags, while a change to raquo.laminar.tags can't break raquo.laminar.keys.
- Position
- Below the diagonal: raquo.laminar.tags uses a module listed above it, which is the healthy direction.
23→19 raquo.laminar.tags uses raquo.laminar.inputs.InputController✕
- Connections
- 1 pair of types, where a type in raquo.laminar.tags uses a type in raquo.laminar.inputs.InputController.
- The types involved
com.raquo.laminar.tags.CustomHtmlTag→com.raquo.laminar.inputs.InputController.InputControllerConfig
- Direction
- raquo.laminar.tags uses raquo.laminar.inputs.InputController, so a change to raquo.laminar.inputs.InputController can break raquo.laminar.tags, while a change to raquo.laminar.tags can't break raquo.laminar.inputs.InputController.
- Position
- Below the diagonal: raquo.laminar.tags uses a module listed above it, which is the healthy direction.
23→21 raquo.laminar.tags uses raquo.laminar.modifiers✕
- Connections
- 3 pairs of types, where a type in raquo.laminar.tags uses a type in raquo.laminar.modifiers.
- The types involved
com.raquo.laminar.tags.HtmlTag→com.raquo.laminar.modifiers.Modifiercom.raquo.laminar.tags.MathMlTag→com.raquo.laminar.modifiers.Modifiercom.raquo.laminar.tags.SvgTag→com.raquo.laminar.modifiers.Modifier
- Direction
- raquo.laminar.tags uses raquo.laminar.modifiers, so a change to raquo.laminar.modifiers can break raquo.laminar.tags, while a change to raquo.laminar.tags can't break raquo.laminar.modifiers.
- Position
- Below the diagonal: raquo.laminar.tags uses a module listed above it, which is the healthy direction.
23→25 raquo.laminar.tags uses raquo.laminar.nodes part of a loop✕
- Connections
- 3 pairs of types, where a type in raquo.laminar.tags uses a type in raquo.laminar.nodes.
- The types involved
com.raquo.laminar.tags.HtmlTag→com.raquo.laminar.nodes.ReactiveHtmlElementcom.raquo.laminar.tags.MathMlTag→com.raquo.laminar.nodes.ReactiveMathMlElementcom.raquo.laminar.tags.SvgTag→com.raquo.laminar.nodes.ReactiveSvgElement
- Direction
- raquo.laminar.tags uses raquo.laminar.nodes, so a change to raquo.laminar.nodes can break raquo.laminar.tags, while a change to raquo.laminar.tags can't break raquo.laminar.nodes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→23 raquo.laminar.defs.tags uses raquo.laminar.tags✕
- Connections
- 3 pairs of types, where a type in raquo.laminar.defs.tags uses a type in raquo.laminar.tags.
- The types involved
com.raquo.laminar.defs.tags.HtmlTags→com.raquo.laminar.tags.HtmlTagcom.raquo.laminar.defs.tags.MathMlTags→com.raquo.laminar.tags.MathMlTagcom.raquo.laminar.defs.tags.SvgTags→com.raquo.laminar.tags.SvgTag
- Direction
- raquo.laminar.defs.tags uses raquo.laminar.tags, so a change to raquo.laminar.tags can break raquo.laminar.defs.tags, while a change to raquo.laminar.defs.tags can't break raquo.laminar.tags.
- Position
- Below the diagonal: raquo.laminar.defs.tags uses a module listed above it, which is the healthy direction.
25→12 raquo.laminar.nodes uses raquo.laminar.keys✕
- Connections
- 6 pairs of types, where a type in raquo.laminar.nodes uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.nodes.ReactiveElement→com.raquo.laminar.keys.CompositeKeycom.raquo.laminar.nodes.ReactiveElement→com.raquo.laminar.keys.EventProcessorcom.raquo.laminar.nodes.ReactiveElement→com.raquo.laminar.keys.SimpleKeycom.raquo.laminar.nodes.ReactiveHtmlElement→com.raquo.laminar.keys.SimpleKeycom.raquo.laminar.nodes.ReactiveMathMlElement→com.raquo.laminar.keys.SimpleKeycom.raquo.laminar.nodes.ReactiveSvgElement→com.raquo.laminar.keys.SimpleKey
- Direction
- raquo.laminar.nodes uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.nodes, while a change to raquo.laminar.nodes can't break raquo.laminar.keys.
- Position
- Below the diagonal: raquo.laminar.nodes uses a module listed above it, which is the healthy direction.
25→18 raquo.laminar.nodes uses raquo.laminar.inputs✕
- Connections
- 1 pair of types, where a type in raquo.laminar.nodes uses a type in raquo.laminar.inputs.
- The types involved
com.raquo.laminar.nodes.ReactiveHtmlElement→com.raquo.laminar.inputs.InputController
- Direction
- raquo.laminar.nodes uses raquo.laminar.inputs, so a change to raquo.laminar.inputs can break raquo.laminar.nodes, while a change to raquo.laminar.nodes can't break raquo.laminar.inputs.
- Position
- Below the diagonal: raquo.laminar.nodes uses a module listed above it, which is the healthy direction.
25→21 raquo.laminar.nodes uses raquo.laminar.modifiers✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.nodes uses a type in raquo.laminar.modifiers.
- The types involved
com.raquo.laminar.nodes.ReactiveElement→com.raquo.laminar.modifiers.EventListenercom.raquo.laminar.nodes.ReactiveElement→com.raquo.laminar.modifiers.Modifier
- Direction
- raquo.laminar.nodes uses raquo.laminar.modifiers, so a change to raquo.laminar.modifiers can break raquo.laminar.nodes, while a change to raquo.laminar.nodes can't break raquo.laminar.modifiers.
- Position
- Below the diagonal: raquo.laminar.nodes uses a module listed above it, which is the healthy direction.
25→23 raquo.laminar.nodes uses raquo.laminar.tags✕
- Connections
- 4 pairs of types, where a type in raquo.laminar.nodes uses a type in raquo.laminar.tags.
- The types involved
com.raquo.laminar.nodes.ReactiveElement→com.raquo.laminar.tags.Tagcom.raquo.laminar.nodes.ReactiveHtmlElement→com.raquo.laminar.tags.HtmlTagcom.raquo.laminar.nodes.ReactiveMathMlElement→com.raquo.laminar.tags.MathMlTagcom.raquo.laminar.nodes.ReactiveSvgElement→com.raquo.laminar.tags.SvgTag
- Direction
- raquo.laminar.nodes uses raquo.laminar.tags, so a change to raquo.laminar.tags can break raquo.laminar.nodes, while a change to raquo.laminar.nodes can't break raquo.laminar.tags.
- Position
- Below the diagonal: raquo.laminar.nodes uses a module listed above it, which is the healthy direction.
25→26 raquo.laminar.nodes uses raquo.laminar.inserters part of a loop✕
- Connections
- 3 pairs of types, where a type in raquo.laminar.nodes uses a type in raquo.laminar.inserters.
- The types involved
com.raquo.laminar.nodes.ChildNode→com.raquo.laminar.inserters.DiffableInsertercom.raquo.laminar.nodes.ChildNode→com.raquo.laminar.inserters.InsertContextcom.raquo.laminar.nodes.ChildNode→com.raquo.laminar.inserters.StaticInserter
- Direction
- raquo.laminar.nodes uses raquo.laminar.inserters, so a change to raquo.laminar.inserters can break raquo.laminar.nodes, while a change to raquo.laminar.nodes can't break raquo.laminar.inserters.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→34 raquo.laminar.nodes uses raquo.laminar part of a loop✕
- Connections
- 1 pair of types, where a type in raquo.laminar.nodes uses a type in raquo.laminar.
- The types involved
com.raquo.laminar.nodes.Slot→com.raquo.laminar.Seq
- Direction
- raquo.laminar.nodes uses raquo.laminar, so a change to raquo.laminar can break raquo.laminar.nodes, while a change to raquo.laminar.nodes can't break raquo.laminar.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→21 raquo.laminar.inserters uses raquo.laminar.modifiers✕
- Connections
- 6 pairs of types, where a type in raquo.laminar.inserters uses a type in raquo.laminar.modifiers.
- The types involved
com.raquo.laminar.inserters.ChildInserter→com.raquo.laminar.modifiers.RenderableNodecom.raquo.laminar.inserters.ChildTextInserter→com.raquo.laminar.modifiers.RenderableTextcom.raquo.laminar.inserters.ChildrenCommandInserter→com.raquo.laminar.modifiers.RenderableNodecom.raquo.laminar.inserters.ChildrenInserter→com.raquo.laminar.modifiers.RenderableInsertercom.raquo.laminar.inserters.ChildrenInserter→com.raquo.laminar.modifiers.RenderableSeqcom.raquo.laminar.inserters.Inserter→com.raquo.laminar.modifiers.Modifier
- Direction
- raquo.laminar.inserters uses raquo.laminar.modifiers, so a change to raquo.laminar.modifiers can break raquo.laminar.inserters, while a change to raquo.laminar.inserters can't break raquo.laminar.modifiers.
- Position
- Below the diagonal: raquo.laminar.inserters uses a module listed above it, which is the healthy direction.
26→25 raquo.laminar.inserters uses raquo.laminar.nodes✕
- Connections
- 3 pairs of types, where a type in raquo.laminar.inserters uses a type in raquo.laminar.nodes.
- The types involved
com.raquo.laminar.inserters.DynamicInserter→com.raquo.laminar.nodes.CommentNodecom.raquo.laminar.inserters.InsertContext→com.raquo.laminar.nodes.CommentNodecom.raquo.laminar.inserters.NestedGroup→com.raquo.laminar.nodes.CommentNode
- Direction
- raquo.laminar.inserters uses raquo.laminar.nodes, so a change to raquo.laminar.nodes can break raquo.laminar.inserters, while a change to raquo.laminar.inserters can't break raquo.laminar.nodes.
- Position
- Below the diagonal: raquo.laminar.inserters uses a module listed above it, which is the healthy direction.
26→34 raquo.laminar.inserters uses raquo.laminar part of a loop✕
- Connections
- 3 pairs of types, where a type in raquo.laminar.inserters uses a type in raquo.laminar.
- The types involved
com.raquo.laminar.inserters.ChildrenCommandInserter→com.raquo.laminar.Seqcom.raquo.laminar.inserters.ChildrenInserter→com.raquo.laminar.Seqcom.raquo.laminar.inserters.SlottableChildrenInserter→com.raquo.laminar.Seq
- Direction
- raquo.laminar.inserters uses raquo.laminar, so a change to raquo.laminar can break raquo.laminar.inserters, while a change to raquo.laminar.inserters can't break raquo.laminar.
- 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.
27→12 raquo.laminar.api.Implicits uses raquo.laminar.keys✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.api.Implicits uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.api.Implicits.EventProcessorArrowSyntaxFixType→com.raquo.laminar.keys.EventProcessorcom.raquo.laminar.api.Implicits.EventProcessorSyntaxFixType→com.raquo.laminar.keys.EventProcessor
- Direction
- raquo.laminar.api.Implicits uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.api.Implicits, while a change to raquo.laminar.api.Implicits can't break raquo.laminar.keys.
- Position
- Below the diagonal: raquo.laminar.api.Implicits uses a module listed above it, which is the healthy direction.
27→21 raquo.laminar.api.Implicits uses raquo.laminar.modifiers✕
- Connections
- 3 pairs of types, where a type in raquo.laminar.api.Implicits uses a type in raquo.laminar.modifiers.
- The types involved
com.raquo.laminar.api.Implicits.EventProcessorArrowSyntaxFixType→com.raquo.laminar.modifiers.EventListenercom.raquo.laminar.api.Implicits.LowPriorityImplicits→com.raquo.laminar.modifiers.RenderableNodecom.raquo.laminar.api.Implicits.LowPriorityImplicits→com.raquo.laminar.modifiers.RenderableSeq
- Direction
- raquo.laminar.api.Implicits uses raquo.laminar.modifiers, so a change to raquo.laminar.modifiers can break raquo.laminar.api.Implicits, while a change to raquo.laminar.api.Implicits can't break raquo.laminar.modifiers.
- Position
- Below the diagonal: raquo.laminar.api.Implicits uses a module listed above it, which is the healthy direction.
27→26 raquo.laminar.api.Implicits uses raquo.laminar.inserters✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.api.Implicits uses a type in raquo.laminar.inserters.
- The types involved
com.raquo.laminar.api.Implicits.LowPriorityImplicits→com.raquo.laminar.inserters.SlottableChildInsertercom.raquo.laminar.api.Implicits.LowPriorityImplicits→com.raquo.laminar.inserters.SlottableChildrenInserter
- Direction
- raquo.laminar.api.Implicits uses raquo.laminar.inserters, so a change to raquo.laminar.inserters can break raquo.laminar.api.Implicits, while a change to raquo.laminar.api.Implicits can't break raquo.laminar.inserters.
- Position
- Below the diagonal: raquo.laminar.api.Implicits uses a module listed above it, which is the healthy direction.
27→33 raquo.laminar.api.Implicits uses raquo.laminar.api part of a loop✕
- Connections
- 1 pair of types, where a type in raquo.laminar.api.Implicits uses a type in raquo.laminar.api.
- The types involved
com.raquo.laminar.api.Implicits.SourceArrowSyntax→com.raquo.laminar.api.UnitArrowsFeature
- Direction
- raquo.laminar.api.Implicits uses raquo.laminar.api, so a change to raquo.laminar.api can break raquo.laminar.api.Implicits, while a change to raquo.laminar.api.Implicits can't break raquo.laminar.api.
- 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.
28→26 raquo.laminar.inserters.InserterType uses raquo.laminar.inserters✕
- Connections
- 3 pairs of types, where a type in raquo.laminar.inserters.InserterType uses a type in raquo.laminar.inserters.
- The types involved
com.raquo.laminar.inserters.InserterType.ChildType→com.raquo.laminar.inserters.InserterTypecom.raquo.laminar.inserters.InserterType.ChildrenCommandType→com.raquo.laminar.inserters.InserterTypecom.raquo.laminar.inserters.InserterType.ChildrenType→com.raquo.laminar.inserters.InserterType
- Direction
- raquo.laminar.inserters.InserterType uses raquo.laminar.inserters, so a change to raquo.laminar.inserters can break raquo.laminar.inserters.InserterType, while a change to raquo.laminar.inserters.InserterType can't break raquo.laminar.inserters.
- Position
- Below the diagonal: raquo.laminar.inserters.InserterType uses a module listed above it, which is the healthy direction.
29→21 raquo.laminar.receivers uses raquo.laminar.modifiers✕
- Connections
- 4 pairs of types, where a type in raquo.laminar.receivers uses a type in raquo.laminar.modifiers.
- The types involved
com.raquo.laminar.receivers.ChildTextOptionReceiver→com.raquo.laminar.modifiers.RenderableTextcom.raquo.laminar.receivers.ChildTextReceiver→com.raquo.laminar.modifiers.RenderableTextcom.raquo.laminar.receivers.ChildrenCommandReceiver→com.raquo.laminar.modifiers.RenderableNodecom.raquo.laminar.receivers.FocusReceiver→com.raquo.laminar.modifiers.Binder
- Direction
- raquo.laminar.receivers uses raquo.laminar.modifiers, so a change to raquo.laminar.modifiers can break raquo.laminar.receivers, while a change to raquo.laminar.receivers can't break raquo.laminar.modifiers.
- Position
- Below the diagonal: raquo.laminar.receivers uses a module listed above it, which is the healthy direction.
29→26 raquo.laminar.receivers uses raquo.laminar.inserters✕
- Connections
- 6 pairs of types, where a type in raquo.laminar.receivers uses a type in raquo.laminar.inserters.
- The types involved
com.raquo.laminar.receivers.ChildOptionReceiver→com.raquo.laminar.inserters.DynamicInsertercom.raquo.laminar.receivers.ChildReceiver→com.raquo.laminar.inserters.DynamicInsertercom.raquo.laminar.receivers.ChildTextOptionReceiver→com.raquo.laminar.inserters.DynamicInsertercom.raquo.laminar.receivers.ChildTextReceiver→com.raquo.laminar.inserters.DynamicInsertercom.raquo.laminar.receivers.ChildrenCommandReceiver→com.raquo.laminar.inserters.CollectionCommandcom.raquo.laminar.receivers.ChildrenCommandReceiver→com.raquo.laminar.inserters.DynamicInserter
- Direction
- raquo.laminar.receivers uses raquo.laminar.inserters, so a change to raquo.laminar.inserters can break raquo.laminar.receivers, while a change to raquo.laminar.receivers can't break raquo.laminar.inserters.
- Position
- Below the diagonal: raquo.laminar.receivers uses a module listed above it, which is the healthy direction.
30→21 raquo.laminar.receivers.ChildOptionReceiver uses raquo.laminar.modifiers✕
- Connections
- 1 pair of types, where a type in raquo.laminar.receivers.ChildOptionReceiver uses a type in raquo.laminar.modifiers.
- The types involved
com.raquo.laminar.receivers.ChildOptionReceiver.RichChildOptionReceiver→com.raquo.laminar.modifiers.RenderableNode
- Direction
- raquo.laminar.receivers.ChildOptionReceiver uses raquo.laminar.modifiers, so a change to raquo.laminar.modifiers can break raquo.laminar.receivers.ChildOptionReceiver, while a change to raquo.laminar.receivers.ChildOptionReceiver can't break raquo.laminar.modifiers.
- Position
- Below the diagonal: raquo.laminar.receivers.ChildOptionReceiver uses a module listed above it, which is the healthy direction.
30→26 raquo.laminar.receivers.ChildOptionReceiver uses raquo.laminar.inserters✕
- Connections
- 1 pair of types, where a type in raquo.laminar.receivers.ChildOptionReceiver uses a type in raquo.laminar.inserters.
- The types involved
com.raquo.laminar.receivers.ChildOptionReceiver.RichChildOptionReceiver→com.raquo.laminar.inserters.DynamicInserter
- Direction
- raquo.laminar.receivers.ChildOptionReceiver uses raquo.laminar.inserters, so a change to raquo.laminar.inserters can break raquo.laminar.receivers.ChildOptionReceiver, while a change to raquo.laminar.receivers.ChildOptionReceiver can't break raquo.laminar.inserters.
- Position
- Below the diagonal: raquo.laminar.receivers.ChildOptionReceiver uses a module listed above it, which is the healthy direction.
31→21 raquo.laminar.receivers.ChildReceiver uses raquo.laminar.modifiers✕
- Connections
- 1 pair of types, where a type in raquo.laminar.receivers.ChildReceiver uses a type in raquo.laminar.modifiers.
- The types involved
com.raquo.laminar.receivers.ChildReceiver.RichChildReceiver→com.raquo.laminar.modifiers.RenderableNode
- Direction
- raquo.laminar.receivers.ChildReceiver uses raquo.laminar.modifiers, so a change to raquo.laminar.modifiers can break raquo.laminar.receivers.ChildReceiver, while a change to raquo.laminar.receivers.ChildReceiver can't break raquo.laminar.modifiers.
- Position
- Below the diagonal: raquo.laminar.receivers.ChildReceiver uses a module listed above it, which is the healthy direction.
31→26 raquo.laminar.receivers.ChildReceiver uses raquo.laminar.inserters✕
- Connections
- 1 pair of types, where a type in raquo.laminar.receivers.ChildReceiver uses a type in raquo.laminar.inserters.
- The types involved
com.raquo.laminar.receivers.ChildReceiver.RichChildReceiver→com.raquo.laminar.inserters.DynamicInserter
- Direction
- raquo.laminar.receivers.ChildReceiver uses raquo.laminar.inserters, so a change to raquo.laminar.inserters can break raquo.laminar.receivers.ChildReceiver, while a change to raquo.laminar.receivers.ChildReceiver can't break raquo.laminar.inserters.
- Position
- Below the diagonal: raquo.laminar.receivers.ChildReceiver uses a module listed above it, which is the healthy direction.
32→21 raquo.laminar.receivers.ChildrenReceiver uses raquo.laminar.modifiers✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.receivers.ChildrenReceiver uses a type in raquo.laminar.modifiers.
- The types involved
com.raquo.laminar.receivers.ChildrenReceiver.RichChildrenReceiver→com.raquo.laminar.modifiers.RenderableInsertercom.raquo.laminar.receivers.ChildrenReceiver.RichChildrenReceiver→com.raquo.laminar.modifiers.RenderableSeq
- Direction
- raquo.laminar.receivers.ChildrenReceiver uses raquo.laminar.modifiers, so a change to raquo.laminar.modifiers can break raquo.laminar.receivers.ChildrenReceiver, while a change to raquo.laminar.receivers.ChildrenReceiver can't break raquo.laminar.modifiers.
- Position
- Below the diagonal: raquo.laminar.receivers.ChildrenReceiver uses a module listed above it, which is the healthy direction.
32→26 raquo.laminar.receivers.ChildrenReceiver uses raquo.laminar.inserters✕
- Connections
- 1 pair of types, where a type in raquo.laminar.receivers.ChildrenReceiver uses a type in raquo.laminar.inserters.
- The types involved
com.raquo.laminar.receivers.ChildrenReceiver.RichChildrenReceiver→com.raquo.laminar.inserters.DynamicInserter
- Direction
- raquo.laminar.receivers.ChildrenReceiver uses raquo.laminar.inserters, so a change to raquo.laminar.inserters can break raquo.laminar.receivers.ChildrenReceiver, while a change to raquo.laminar.receivers.ChildrenReceiver can't break raquo.laminar.inserters.
- Position
- Below the diagonal: raquo.laminar.receivers.ChildrenReceiver uses a module listed above it, which is the healthy direction.
33→2 raquo.laminar.api uses raquo.laminar.api.StyleUnitsApi✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.api uses a type in raquo.laminar.api.StyleUnitsApi.
- The types involved
com.raquo.laminar.api.ImplicitsPlatformSpecific→com.raquo.laminar.api.StyleUnitsApi.StyleEncodercom.raquo.laminar.api.StyleUnitsApi→com.raquo.laminar.api.StyleUnitsApi.StyleEncoder
- Direction
- raquo.laminar.api uses raquo.laminar.api.StyleUnitsApi, so a change to raquo.laminar.api.StyleUnitsApi can break raquo.laminar.api, while a change to raquo.laminar.api can't break raquo.laminar.api.StyleUnitsApi.
- Position
- Below the diagonal: raquo.laminar.api uses a module listed above it, which is the healthy direction.
33→4 raquo.laminar.api uses raquo.laminar.defs.styles.units✕
- Connections
- 4 pairs of types, where a type in raquo.laminar.api uses a type in raquo.laminar.defs.styles.units.
- The types involved
com.raquo.laminar.api.StyleUnitsApi→com.raquo.laminar.defs.styles.units.GlobalUnitscom.raquo.laminar.api.StyleUnitsApi→com.raquo.laminar.defs.styles.units.Lengthcom.raquo.laminar.api.StyleUnitsApi→com.raquo.laminar.defs.styles.units.Timecom.raquo.laminar.api.StyleUnitsApi→com.raquo.laminar.defs.styles.units.Url
- Direction
- raquo.laminar.api uses raquo.laminar.defs.styles.units, so a change to raquo.laminar.defs.styles.units can break raquo.laminar.api, while a change to raquo.laminar.api can't break raquo.laminar.defs.styles.units.
- Position
- Below the diagonal: raquo.laminar.api uses a module listed above it, which is the healthy direction.
33→8 raquo.laminar.api uses raquo.laminar.lifecycle✕
- Connections
- 1 pair of types, where a type in raquo.laminar.api uses a type in raquo.laminar.lifecycle.
- The types involved
com.raquo.laminar.api.MountHooks→com.raquo.laminar.lifecycle.MountContext
- Direction
- raquo.laminar.api uses raquo.laminar.lifecycle, so a change to raquo.laminar.lifecycle can break raquo.laminar.api, while a change to raquo.laminar.api can't break raquo.laminar.lifecycle.
- Position
- Below the diagonal: raquo.laminar.api uses a module listed above it, which is the healthy direction.
33→11 raquo.laminar.api uses raquo.laminar.defs.styles.traits✕
- Connections
- 1 pair of types, where a type in raquo.laminar.api uses a type in raquo.laminar.defs.styles.traits.
- The types involved
com.raquo.laminar.api.StyleUnitsApi→com.raquo.laminar.defs.styles.traits.Color
- Direction
- raquo.laminar.api uses raquo.laminar.defs.styles.traits, so a change to raquo.laminar.defs.styles.traits can break raquo.laminar.api, while a change to raquo.laminar.api can't break raquo.laminar.defs.styles.traits.
- Position
- Below the diagonal: raquo.laminar.api uses a module listed above it, which is the healthy direction.
33→12 raquo.laminar.api uses raquo.laminar.keys✕
- Connections
- 5 pairs of types, where a type in raquo.laminar.api uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.api.Implicits→com.raquo.laminar.keys.EventProcessorcom.raquo.laminar.api.Implicits→com.raquo.laminar.keys.EventPropcom.raquo.laminar.api.Laminar→com.raquo.laminar.keys.HtmlPropcom.raquo.laminar.api.StyleUnitsApi→com.raquo.laminar.keys.DerivedStyleBuildercom.raquo.laminar.api.StyleUnitsApi→com.raquo.laminar.keys.StyleBuilder
- Direction
- raquo.laminar.api uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.api, while a change to raquo.laminar.api can't break raquo.laminar.keys.
- Position
- Below the diagonal: raquo.laminar.api uses a module listed above it, which is the healthy direction.
33→13 raquo.laminar.api uses raquo.laminar.defs.attrs✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.api uses a type in raquo.laminar.defs.attrs.
- The types involved
com.raquo.laminar.api.Laminar→com.raquo.laminar.defs.attrs.GlobalAttrscom.raquo.laminar.api.Laminar→com.raquo.laminar.defs.attrs.HtmlAttrs
- Direction
- raquo.laminar.api uses raquo.laminar.defs.attrs, so a change to raquo.laminar.defs.attrs can break raquo.laminar.api, while a change to raquo.laminar.api can't break raquo.laminar.defs.attrs.
- Position
- Below the diagonal: raquo.laminar.api uses a module listed above it, which is the healthy direction.
33→14 raquo.laminar.api uses raquo.laminar.defs.complex✕
- Connections
- 1 pair of types, where a type in raquo.laminar.api uses a type in raquo.laminar.defs.complex.
- The types involved
com.raquo.laminar.api.Laminar→com.raquo.laminar.defs.complex.ComplexHtmlKeys
- Direction
- raquo.laminar.api uses raquo.laminar.defs.complex, so a change to raquo.laminar.defs.complex can break raquo.laminar.api, while a change to raquo.laminar.api can't break raquo.laminar.defs.complex.
- Position
- Below the diagonal: raquo.laminar.api uses a module listed above it, which is the healthy direction.
33→15 raquo.laminar.api uses raquo.laminar.defs.eventProps✕
- Connections
- 1 pair of types, where a type in raquo.laminar.api uses a type in raquo.laminar.defs.eventProps.
- The types involved
com.raquo.laminar.api.Laminar→com.raquo.laminar.defs.eventProps.GlobalEventProps
- Direction
- raquo.laminar.api uses raquo.laminar.defs.eventProps, so a change to raquo.laminar.defs.eventProps can break raquo.laminar.api, while a change to raquo.laminar.api can't break raquo.laminar.defs.eventProps.
- Position
- Below the diagonal: raquo.laminar.api uses a module listed above it, which is the healthy direction.
33→16 raquo.laminar.api uses raquo.laminar.defs.props✕
- Connections
- 1 pair of types, where a type in raquo.laminar.api uses a type in raquo.laminar.defs.props.
- The types involved
com.raquo.laminar.api.Laminar→com.raquo.laminar.defs.props.HtmlProps
- Direction
- raquo.laminar.api uses raquo.laminar.defs.props, so a change to raquo.laminar.defs.props can break raquo.laminar.api, while a change to raquo.laminar.api can't break raquo.laminar.defs.props.
- Position
- Below the diagonal: raquo.laminar.api uses a module listed above it, which is the healthy direction.
33→17 raquo.laminar.api uses raquo.laminar.defs.styles✕
- Connections
- 1 pair of types, where a type in raquo.laminar.api uses a type in raquo.laminar.defs.styles.
- The types involved
com.raquo.laminar.api.Laminar→com.raquo.laminar.defs.styles.StyleProps
- Direction
- raquo.laminar.api uses raquo.laminar.defs.styles, so a change to raquo.laminar.defs.styles can break raquo.laminar.api, while a change to raquo.laminar.api can't break raquo.laminar.defs.styles.
- Position
- Below the diagonal: raquo.laminar.api uses a module listed above it, which is the healthy direction.
33→21 raquo.laminar.api uses raquo.laminar.modifiers✕
- Connections
- 11 pairs of types, where a type in raquo.laminar.api uses a type in raquo.laminar.modifiers.
- The types involved
com.raquo.laminar.api.Implicits→com.raquo.laminar.modifiers.Modifiercom.raquo.laminar.api.Implicits→com.raquo.laminar.modifiers.RenderableNodecom.raquo.laminar.api.Implicits→com.raquo.laminar.modifiers.RenderableSeqcom.raquo.laminar.api.Implicits→com.raquo.laminar.modifiers.RenderableTextcom.raquo.laminar.api.Implicits→com.raquo.laminar.modifiers.Settercom.raquo.laminar.api.Laminar→com.raquo.laminar.modifiers.Bindercom.raquo.laminar.api.Laminar→com.raquo.laminar.modifiers.EventListenercom.raquo.laminar.api.Laminar→com.raquo.laminar.modifiers.Modifiercom.raquo.laminar.api.Laminar→com.raquo.laminar.modifiers.SimpleKeyUpdatercom.raquo.laminar.api.LaminarPlatformSpecific→com.raquo.laminar.modifiers.Modifiercom.raquo.laminar.api.MountHooks→com.raquo.laminar.modifiers.Modifier
- Direction
- raquo.laminar.api uses raquo.laminar.modifiers, so a change to raquo.laminar.modifiers can break raquo.laminar.api, while a change to raquo.laminar.api can't break raquo.laminar.modifiers.
- Position
- Below the diagonal: raquo.laminar.api uses a module listed above it, which is the healthy direction.
33→23 raquo.laminar.api uses raquo.laminar.tags✕
- Connections
- 3 pairs of types, where a type in raquo.laminar.api uses a type in raquo.laminar.tags.
- The types involved
com.raquo.laminar.api.Laminar→com.raquo.laminar.tags.HtmlTagcom.raquo.laminar.api.Laminar→com.raquo.laminar.tags.MathMlTagcom.raquo.laminar.api.Laminar→com.raquo.laminar.tags.SvgTag
- Direction
- raquo.laminar.api uses raquo.laminar.tags, so a change to raquo.laminar.tags can break raquo.laminar.api, while a change to raquo.laminar.api can't break raquo.laminar.tags.
- Position
- Below the diagonal: raquo.laminar.api uses a module listed above it, which is the healthy direction.
33→24 raquo.laminar.api uses raquo.laminar.defs.tags✕
- Connections
- 1 pair of types, where a type in raquo.laminar.api uses a type in raquo.laminar.defs.tags.
- The types involved
com.raquo.laminar.api.Laminar→com.raquo.laminar.defs.tags.HtmlTags
- Direction
- raquo.laminar.api uses raquo.laminar.defs.tags, so a change to raquo.laminar.defs.tags can break raquo.laminar.api, while a change to raquo.laminar.api can't break raquo.laminar.defs.tags.
- Position
- Below the diagonal: raquo.laminar.api uses a module listed above it, which is the healthy direction.
33→25 raquo.laminar.api uses raquo.laminar.nodes✕
- Connections
- 7 pairs of types, where a type in raquo.laminar.api uses a type in raquo.laminar.nodes.
- The types involved
com.raquo.laminar.api.Implicits→com.raquo.laminar.nodes.TextNodecom.raquo.laminar.api.Laminar→com.raquo.laminar.nodes.CommentNodecom.raquo.laminar.api.Laminar→com.raquo.laminar.nodes.DetachedRootcom.raquo.laminar.api.Laminar→com.raquo.laminar.nodes.ReactiveHtmlElementcom.raquo.laminar.api.Laminar→com.raquo.laminar.nodes.ReactiveMathMlElementcom.raquo.laminar.api.Laminar→com.raquo.laminar.nodes.ReactiveSvgElementcom.raquo.laminar.api.Laminar→com.raquo.laminar.nodes.RootNode
- Direction
- raquo.laminar.api uses raquo.laminar.nodes, so a change to raquo.laminar.nodes can break raquo.laminar.api, while a change to raquo.laminar.api can't break raquo.laminar.nodes.
- Position
- Below the diagonal: raquo.laminar.api uses a module listed above it, which is the healthy direction.
33→27 raquo.laminar.api uses raquo.laminar.api.Implicits✕
- Connections
- 4 pairs of types, where a type in raquo.laminar.api uses a type in raquo.laminar.api.Implicits.
- The types involved
com.raquo.laminar.api.Implicits→com.raquo.laminar.api.Implicits.EventProcessorSyntaxFixTypecom.raquo.laminar.api.Implicits→com.raquo.laminar.api.Implicits.LowPriorityImplicitscom.raquo.laminar.api.Implicits→com.raquo.laminar.api.Implicits.SourceArrowSyntaxcom.raquo.laminar.api.Implicits→com.raquo.laminar.api.Implicits.SourceSyntaxFixType
- Direction
- raquo.laminar.api uses raquo.laminar.api.Implicits, so a change to raquo.laminar.api.Implicits can break raquo.laminar.api, while a change to raquo.laminar.api can't break raquo.laminar.api.Implicits.
- Position
- Below the diagonal: raquo.laminar.api uses a module listed above it, which is the healthy direction.
33→34 raquo.laminar.api uses raquo.laminar part of a loop✕
- Connections
- 1 pair of types, where a type in raquo.laminar.api uses a type in raquo.laminar.
- The types involved
com.raquo.laminar.api.Laminar→com.raquo.laminar.Seq
- Direction
- raquo.laminar.api uses raquo.laminar, so a change to raquo.laminar can break raquo.laminar.api, while a change to raquo.laminar.api can't break raquo.laminar.
- 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.
34→3 raquo.laminar uses raquo.laminar.codecs✕
- Connections
- 1 pair of types, where a type in raquo.laminar uses a type in raquo.laminar.codecs.
- The types involved
com.raquo.laminar.codecs→com.raquo.laminar.codecs.Codec
- Direction
- raquo.laminar uses raquo.laminar.codecs, so a change to raquo.laminar.codecs can break raquo.laminar, while a change to raquo.laminar can't break raquo.laminar.codecs.
- Position
- Below the diagonal: raquo.laminar uses a module listed above it, which is the healthy direction.
34→33 raquo.laminar uses raquo.laminar.api✕
- Connections
- 2 pairs of types, where a type in raquo.laminar uses a type in raquo.laminar.api.
- The types involved
com.raquo.laminar.api→com.raquo.laminar.api.AirstreamAliasescom.raquo.laminar.api→com.raquo.laminar.api.Laminar
- Direction
- raquo.laminar uses raquo.laminar.api, so a change to raquo.laminar.api can break raquo.laminar, while a change to raquo.laminar can't break raquo.laminar.api.
- Position
- Below the diagonal: raquo.laminar uses a module listed above it, which is the healthy direction.
35→13 raquo.laminar.api.Laminar uses raquo.laminar.defs.attrs✕
- Connections
- 7 pairs of types, where a type in raquo.laminar.api.Laminar uses a type in raquo.laminar.defs.attrs.
- The types involved
com.raquo.laminar.api.Laminar.aria→com.raquo.laminar.defs.attrs.AriaAttrscom.raquo.laminar.api.Laminar.mathml→com.raquo.laminar.defs.attrs.AriaAttrscom.raquo.laminar.api.Laminar.mathml→com.raquo.laminar.defs.attrs.GlobalAttrscom.raquo.laminar.api.Laminar.mathml→com.raquo.laminar.defs.attrs.MathMlAttrscom.raquo.laminar.api.Laminar.svg→com.raquo.laminar.defs.attrs.AriaAttrscom.raquo.laminar.api.Laminar.svg→com.raquo.laminar.defs.attrs.GlobalAttrscom.raquo.laminar.api.Laminar.svg→com.raquo.laminar.defs.attrs.SvgAttrs
- Direction
- raquo.laminar.api.Laminar uses raquo.laminar.defs.attrs, so a change to raquo.laminar.defs.attrs can break raquo.laminar.api.Laminar, while a change to raquo.laminar.api.Laminar can't break raquo.laminar.defs.attrs.
- Position
- Below the diagonal: raquo.laminar.api.Laminar uses a module listed above it, which is the healthy direction.
35→14 raquo.laminar.api.Laminar uses raquo.laminar.defs.complex✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.api.Laminar uses a type in raquo.laminar.defs.complex.
- The types involved
com.raquo.laminar.api.Laminar.mathml→com.raquo.laminar.defs.complex.ComplexGlobalKeyscom.raquo.laminar.api.Laminar.svg→com.raquo.laminar.defs.complex.ComplexGlobalKeys
- Direction
- raquo.laminar.api.Laminar uses raquo.laminar.defs.complex, so a change to raquo.laminar.defs.complex can break raquo.laminar.api.Laminar, while a change to raquo.laminar.api.Laminar can't break raquo.laminar.defs.complex.
- Position
- Below the diagonal: raquo.laminar.api.Laminar uses a module listed above it, which is the healthy direction.
35→24 raquo.laminar.api.Laminar uses raquo.laminar.defs.tags✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.api.Laminar uses a type in raquo.laminar.defs.tags.
- The types involved
com.raquo.laminar.api.Laminar.mathml→com.raquo.laminar.defs.tags.MathMlTagscom.raquo.laminar.api.Laminar.svg→com.raquo.laminar.defs.tags.SvgTags
- Direction
- raquo.laminar.api.Laminar uses raquo.laminar.defs.tags, so a change to raquo.laminar.defs.tags can break raquo.laminar.api.Laminar, while a change to raquo.laminar.api.Laminar can't break raquo.laminar.defs.tags.
- Position
- Below the diagonal: raquo.laminar.api.Laminar uses a module listed above it, which is the healthy direction.
35→33 raquo.laminar.api.Laminar uses raquo.laminar.api✕
- Connections
- 1 pair of types, where a type in raquo.laminar.api.Laminar uses a type in raquo.laminar.api.
- The types involved
com.raquo.laminar.api.Laminar.style→com.raquo.laminar.api.StyleUnitsApi
- Direction
- raquo.laminar.api.Laminar uses raquo.laminar.api, so a change to raquo.laminar.api can break raquo.laminar.api.Laminar, while a change to raquo.laminar.api.Laminar can't break raquo.laminar.api.
- Position
- Below the diagonal: raquo.laminar.api.Laminar uses a module listed above it, which is the healthy direction.
36→12 raquo.laminar.domapi uses raquo.laminar.keys✕
- Connections
- 5 pairs of types, where a type in raquo.laminar.domapi uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.domapi.DomKeys→com.raquo.laminar.keys.CompositeAttrcom.raquo.laminar.domapi.DomKeys→com.raquo.laminar.keys.DerivedStylePropcom.raquo.laminar.domapi.DomKeys→com.raquo.laminar.keys.HtmlPropcom.raquo.laminar.domapi.DomKeys→com.raquo.laminar.keys.SimpleAttrcom.raquo.laminar.domapi.DomKeys→com.raquo.laminar.keys.StyleProp
- Direction
- raquo.laminar.domapi uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.domapi, while a change to raquo.laminar.domapi can't break raquo.laminar.keys.
- Position
- Below the diagonal: raquo.laminar.domapi uses a module listed above it, which is the healthy direction.
36→21 raquo.laminar.domapi uses raquo.laminar.modifiers✕
- Connections
- 1 pair of types, where a type in raquo.laminar.domapi uses a type in raquo.laminar.modifiers.
- The types involved
com.raquo.laminar.domapi.DomEvents→com.raquo.laminar.modifiers.EventListener
- Direction
- raquo.laminar.domapi uses raquo.laminar.modifiers, so a change to raquo.laminar.modifiers can break raquo.laminar.domapi, while a change to raquo.laminar.domapi can't break raquo.laminar.modifiers.
- Position
- Below the diagonal: raquo.laminar.domapi uses a module listed above it, which is the healthy direction.
36→23 raquo.laminar.domapi uses raquo.laminar.tags✕
- Connections
- 7 pairs of types, where a type in raquo.laminar.domapi uses a type in raquo.laminar.tags.
- The types involved
com.raquo.laminar.domapi.DomParser→com.raquo.laminar.tags.HtmlTagcom.raquo.laminar.domapi.DomParser→com.raquo.laminar.tags.MathMlTagcom.raquo.laminar.domapi.DomParser→com.raquo.laminar.tags.SvgTagcom.raquo.laminar.domapi.DomTags→com.raquo.laminar.tags.HtmlTagcom.raquo.laminar.domapi.DomTags→com.raquo.laminar.tags.MathMlTagcom.raquo.laminar.domapi.DomTags→com.raquo.laminar.tags.SvgTagcom.raquo.laminar.domapi.DomTags→com.raquo.laminar.tags.Tag
- Direction
- raquo.laminar.domapi uses raquo.laminar.tags, so a change to raquo.laminar.tags can break raquo.laminar.domapi, while a change to raquo.laminar.domapi can't break raquo.laminar.tags.
- Position
- Below the diagonal: raquo.laminar.domapi uses a module listed above it, which is the healthy direction.
36→25 raquo.laminar.domapi uses raquo.laminar.nodes✕
- Connections
- 3 pairs of types, where a type in raquo.laminar.domapi uses a type in raquo.laminar.nodes.
- The types involved
com.raquo.laminar.domapi.DomTags→com.raquo.laminar.nodes.CommentNodecom.raquo.laminar.domapi.DomTags→com.raquo.laminar.nodes.ReactiveElementcom.raquo.laminar.domapi.DomTags→com.raquo.laminar.nodes.TextNode
- Direction
- raquo.laminar.domapi uses raquo.laminar.nodes, so a change to raquo.laminar.nodes can break raquo.laminar.domapi, while a change to raquo.laminar.domapi can't break raquo.laminar.nodes.
- Position
- Below the diagonal: raquo.laminar.domapi uses a module listed above it, which is the healthy direction.
36→34 raquo.laminar.domapi uses raquo.laminar✕
- Connections
- 1 pair of types, where a type in raquo.laminar.domapi uses a type in raquo.laminar.
- The types involved
com.raquo.laminar.domapi.DomKeysRaw→com.raquo.laminar.Seq
- Direction
- raquo.laminar.domapi uses raquo.laminar, so a change to raquo.laminar can break raquo.laminar.domapi, while a change to raquo.laminar.domapi can't break raquo.laminar.
- Position
- Below the diagonal: raquo.laminar.domapi uses a module listed above it, which is the healthy direction.
37→26 raquo.laminar.inserters.CollectionCommand uses raquo.laminar.inserters✕
- Connections
- 7 pairs of types, where a type in raquo.laminar.inserters.CollectionCommand uses a type in raquo.laminar.inserters.
- The types involved
com.raquo.laminar.inserters.CollectionCommand.Append→com.raquo.laminar.inserters.CollectionCommandcom.raquo.laminar.inserters.CollectionCommand.Insert→com.raquo.laminar.inserters.CollectionCommandcom.raquo.laminar.inserters.CollectionCommand.Prepend→com.raquo.laminar.inserters.CollectionCommandcom.raquo.laminar.inserters.CollectionCommand.Remove→com.raquo.laminar.inserters.CollectionCommandcom.raquo.laminar.inserters.CollectionCommand.RemoveAll→com.raquo.laminar.inserters.CollectionCommandcom.raquo.laminar.inserters.CollectionCommand.Replace→com.raquo.laminar.inserters.CollectionCommandcom.raquo.laminar.inserters.CollectionCommand.ReplaceAll→com.raquo.laminar.inserters.CollectionCommand
- Direction
- raquo.laminar.inserters.CollectionCommand uses raquo.laminar.inserters, so a change to raquo.laminar.inserters can break raquo.laminar.inserters.CollectionCommand, while a change to raquo.laminar.inserters.CollectionCommand can't break raquo.laminar.inserters.
- Position
- Below the diagonal: raquo.laminar.inserters.CollectionCommand uses a module listed above it, which is the healthy direction.
37→34 raquo.laminar.inserters.CollectionCommand uses raquo.laminar✕
- Connections
- 1 pair of types, where a type in raquo.laminar.inserters.CollectionCommand uses a type in raquo.laminar.
- The types involved
com.raquo.laminar.inserters.CollectionCommand.ReplaceAll→com.raquo.laminar.Seq
- Direction
- raquo.laminar.inserters.CollectionCommand uses raquo.laminar, so a change to raquo.laminar can break raquo.laminar.inserters.CollectionCommand, while a change to raquo.laminar.inserters.CollectionCommand can't break raquo.laminar.
- Position
- Below the diagonal: raquo.laminar.inserters.CollectionCommand uses a module listed above it, which is the healthy direction.
38→12 raquo.laminar.keys.CompositeValueMapper.Implicits uses raquo.laminar.keys✕
- Connections
- 8 pairs of types, where a type in raquo.laminar.keys.CompositeValueMapper.Implicits uses a type in raquo.laminar.keys.
- The types involved
com.raquo.laminar.keys.CompositeValueMapper.Implicits.JsDictionaryValueMapper→com.raquo.laminar.keys.CompositeValueMappercom.raquo.laminar.keys.CompositeValueMapper.Implicits.MapValueMapper→com.raquo.laminar.keys.CompositeValueMappercom.raquo.laminar.keys.CompositeValueMapper.Implicits.StringBooleanSeqSeqValueMapper→com.raquo.laminar.keys.CompositeValueMappercom.raquo.laminar.keys.CompositeValueMapper.Implicits.StringBooleanSeqValueMapper→com.raquo.laminar.keys.CompositeValueMappercom.raquo.laminar.keys.CompositeValueMapper.Implicits.StringOptionValueMapper→com.raquo.laminar.keys.CompositeValueMappercom.raquo.laminar.keys.CompositeValueMapper.Implicits.StringSeqSeqValueMapper→com.raquo.laminar.keys.CompositeValueMappercom.raquo.laminar.keys.CompositeValueMapper.Implicits.StringSeqValueMapper→com.raquo.laminar.keys.CompositeValueMappercom.raquo.laminar.keys.CompositeValueMapper.Implicits.StringValueMapper→com.raquo.laminar.keys.CompositeValueMapper
- Direction
- raquo.laminar.keys.CompositeValueMapper.Implicits uses raquo.laminar.keys, so a change to raquo.laminar.keys can break raquo.laminar.keys.CompositeValueMapper.Implicits, while a change to raquo.laminar.keys.CompositeValueMapper.Implicits can't break raquo.laminar.keys.
- Position
- Below the diagonal: raquo.laminar.keys.CompositeValueMapper.Implicits uses a module listed above it, which is the healthy direction.
38→34 raquo.laminar.keys.CompositeValueMapper.Implicits uses raquo.laminar✕
- Connections
- 4 pairs of types, where a type in raquo.laminar.keys.CompositeValueMapper.Implicits uses a type in raquo.laminar.
- The types involved
com.raquo.laminar.keys.CompositeValueMapper.Implicits.StringBooleanSeqSeqValueMapper→com.raquo.laminar.Seqcom.raquo.laminar.keys.CompositeValueMapper.Implicits.StringBooleanSeqValueMapper→com.raquo.laminar.Seqcom.raquo.laminar.keys.CompositeValueMapper.Implicits.StringSeqSeqValueMapper→com.raquo.laminar.Seqcom.raquo.laminar.keys.CompositeValueMapper.Implicits.StringSeqValueMapper→com.raquo.laminar.Seq
- Direction
- raquo.laminar.keys.CompositeValueMapper.Implicits uses raquo.laminar, so a change to raquo.laminar can break raquo.laminar.keys.CompositeValueMapper.Implicits, while a change to raquo.laminar.keys.CompositeValueMapper.Implicits can't break raquo.laminar.
- Position
- Below the diagonal: raquo.laminar.keys.CompositeValueMapper.Implicits uses a module listed above it, which is the healthy direction.
39→21 raquo.laminar.modifiers.RenderableSeq uses raquo.laminar.modifiers✕
- Connections
- 8 pairs of types, where a type in raquo.laminar.modifiers.RenderableSeq uses a type in raquo.laminar.modifiers.
- The types involved
com.raquo.laminar.modifiers.RenderableSeq.collectionSeqRenderable→com.raquo.laminar.modifiers.RenderableSeqcom.raquo.laminar.modifiers.RenderableSeq.jsArrayRenderable→com.raquo.laminar.modifiers.RenderableSeqcom.raquo.laminar.modifiers.RenderableSeq.jsUndefOrRenderable→com.raquo.laminar.modifiers.RenderableSeqcom.raquo.laminar.modifiers.RenderableSeq.jsVectorRenderable→com.raquo.laminar.modifiers.RenderableSeqcom.raquo.laminar.modifiers.RenderableSeq.laminarSeqRenderable→com.raquo.laminar.modifiers.RenderableSeqcom.raquo.laminar.modifiers.RenderableSeq.optionRenderable→com.raquo.laminar.modifiers.RenderableSeqcom.raquo.laminar.modifiers.RenderableSeq.scalaArrayRenderable→com.raquo.laminar.modifiers.RenderableSeqcom.raquo.laminar.modifiers.RenderableSeq.sjsArrayRenderable→com.raquo.laminar.modifiers.RenderableSeq
- Direction
- raquo.laminar.modifiers.RenderableSeq uses raquo.laminar.modifiers, so a change to raquo.laminar.modifiers can break raquo.laminar.modifiers.RenderableSeq, while a change to raquo.laminar.modifiers.RenderableSeq can't break raquo.laminar.modifiers.
- Position
- Below the diagonal: raquo.laminar.modifiers.RenderableSeq uses a module listed above it, which is the healthy direction.
39→34 raquo.laminar.modifiers.RenderableSeq uses raquo.laminar✕
- Connections
- 8 pairs of types, where a type in raquo.laminar.modifiers.RenderableSeq uses a type in raquo.laminar.
- The types involved
com.raquo.laminar.modifiers.RenderableSeq.collectionSeqRenderable→com.raquo.laminar.Seqcom.raquo.laminar.modifiers.RenderableSeq.jsArrayRenderable→com.raquo.laminar.Seqcom.raquo.laminar.modifiers.RenderableSeq.jsUndefOrRenderable→com.raquo.laminar.Seqcom.raquo.laminar.modifiers.RenderableSeq.jsVectorRenderable→com.raquo.laminar.Seqcom.raquo.laminar.modifiers.RenderableSeq.laminarSeqRenderable→com.raquo.laminar.Seqcom.raquo.laminar.modifiers.RenderableSeq.optionRenderable→com.raquo.laminar.Seqcom.raquo.laminar.modifiers.RenderableSeq.scalaArrayRenderable→com.raquo.laminar.Seqcom.raquo.laminar.modifiers.RenderableSeq.sjsArrayRenderable→com.raquo.laminar.Seq
- Direction
- raquo.laminar.modifiers.RenderableSeq uses raquo.laminar, so a change to raquo.laminar can break raquo.laminar.modifiers.RenderableSeq, while a change to raquo.laminar.modifiers.RenderableSeq can't break raquo.laminar.
- Position
- Below the diagonal: raquo.laminar.modifiers.RenderableSeq uses a module listed above it, which is the healthy direction.
40→36 raquo.laminar.domapi.DomApi uses raquo.laminar.domapi✕
- Connections
- 2 pairs of types, where a type in raquo.laminar.domapi.DomApi uses a type in raquo.laminar.domapi.
- The types involved
com.raquo.laminar.domapi.DomApi.raw→com.raquo.laminar.domapi.DomKeysRawcom.raquo.laminar.domapi.DomApi.raw→com.raquo.laminar.domapi.DomTreeRaw
- Direction
- raquo.laminar.domapi.DomApi uses raquo.laminar.domapi, so a change to raquo.laminar.domapi can break raquo.laminar.domapi.DomApi, while a change to raquo.laminar.domapi.DomApi can't break raquo.laminar.domapi.
- Position
- Below the diagonal: raquo.laminar.domapi.DomApi 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 | 12 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
| A08:2025 — Software or Data Integrity Failures | 1 | Medium |
Roadmap
First, resolve the missing Architectural Decision Records by documenting significant design choices in a dedicated folder to ensure traceability. Next, improve onboarding by adding a quick-start build and run section to the root README. Then, integrate static analysis into the CI pipeline to automatically fail builds on security regressions. Finally, optimize hot paths by increasing the use of allocation-aware idioms to improve runtime efficiency.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +7.4 pts | Low | ADR Quality |
| 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. | +6.9 pts | Medium | Architecture documentation |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +4.9 pts | Medium | Documentation (README) |
| Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +2.6 pts | Medium | Security & performance tooling |
| Raise allocation-aware density on the hot paths — currently 10 use(s) across 21,918 production line(s) (~0.5/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10. | +2.6 pts | Medium | Allocation hygiene |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +1.7 pts | Medium | Deployment & Rollback |
| 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. | +0.8 pts | Medium | Nullable reference types |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.3 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.8 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| website/pages/en/index.js | 7.0 | Mixed | God Classes: MethodTooLong: Index.render |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/main/scala/com/raquo/laminar/inserters/ChildrenCommandInserter.scala | 7.8 | Mixed | Cyclomatic Complexity: ChildrenCommandInserter.updateList (cyclomatic 21) |
| project/project/ProjectVersions.scala | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: ProjectVersions.scala ↔ HtmlProps.scala |
| src/test/scala/com/raquo/laminar/tests/InserterMoveSpec.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/scala/com/raquo/laminar/inserters/ChildrenInserter.scala | 8.5 | Near-clean | Cognitive Complexity: ChildrenInserter.updateChildren (cognitive 27) |
| src/main/scala/com/raquo/laminar/defs/styles/StyleProps.scala | 8.5 | Near-clean | God Classes: TooManyMethods: StyleProps |
| src/main/scala/com/raquo/laminar/keys/EventProcessor.scala | 8.5 | Near-clean | God Classes: TooManyMethods: EventProcessor |
| src/main/scala/com/raquo/laminar/inserters/ChildTextInserter.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (18–25 lines × 2) |
| src/main/scala/com/raquo/laminar/Seq.scala | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: Seq (LCOM4 4) |
| src/main/scala/com/raquo/laminar/defs/props/HtmlProps.scala | 8.5 | Near-clean | Change Coupling: Change coupling: HtmlProps.scala ↔ HtmlTags.scala |
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
Watchdog 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. 56 of 56 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 56 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, 37 of 53 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog 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 |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog 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 — Watchdog 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, 65 test files), but it was not re-run: no test result was produced. 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 — 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. This repository's 2 package.json manifest(s) WERE read and their pinning discipline assessed; what went unanswered is the currency half, because answering it needs a lockfile resolved to CONCRETE versions and this repository commits none — a package.json states version RANGES, and a range names no particular release to be behind. So registry.npmjs.org was never asked, and there was nothing here for it to grade. This is a true statement about the repository and NOT a gap on our side: no lockfile reader we could write would find anything here to read, so there is no capability behind this row to build.
- D14 License Compliance — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's 4 sbt build file(s) (build.sbt and project/*.scala) were read and none of the production library dependencies they declare carries a version this pass can resolve from the file itself (1 declared with a version computed rather than written as a literal, or cross-built with `%%` where the build states no scalaVersion to form the Scala binary suffix from). sbt is a program rather than a manifest: a val holding one string literal is read, but anything computed would need the build run, and this pass does not run it. Licences are resolved from the POMs Maven Central publishes, which requires an exact coordinate to ask about. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- 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 (21 contributor(s) across 815 commit(s) sampled, automation and bot accounts excluded). One of them holds 95% of the history; the other 20 hold 0.2% 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.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (project/plugins.sbt), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — Watchdog 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 — Watchdog 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.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; REDACTED was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that REDACTED is free of known-vulnerable dependencies.
- D43 Malicious Dependencies — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; REDACTED was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that REDACTED is free of known-vulnerable dependencies.
- D44 Platform End-of-Life — not measured this run — Watchdog 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.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
- C1 Data Protection — not measured this run — Watchdog 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 — Watchdog 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
- 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.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ChildrenCommandInserter.updateList at 21.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with ChildrenCommandInserter.updateList (cyclomatic 21). — Refactoring it lifts Cyclomatic Complexity from 9.6 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
2 method(s) exceeded the cognitive complexity threshold of 15; the worst was ChildrenCommandInserter.updateList at 30.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with ChildrenCommandInserter.updateList (cognitive 30), ChildrenInserter.updateChildren (cognitive 27). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- 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
3 god class(es) detected.
What to do
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with StyleProps.scala, EventProcessor.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with index.js. — 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
1 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (18–25 lines × 2) finding(s) in Code Duplication — start with ChildTextInserter.scala. — One of this dimension's main actionable groups (1 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.
D6 · Cohesion (LCOM4)
1 of 18 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with Seq.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
393 test methods: 393 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 393 test case(s) across 52 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
Top hotspots: src/main/scala/com/raquo/laminar/inserters/ChildrenCommandInserter.scala (10×21=210); src/main/scala/com/raquo/laminar/domapi/DomTags.scala (4×15=60) Repeated repair below the complexity floor: src/main/scala/com/raquo/laminar/inserters/NestedGroup.scala (8 of 10 changes were fixes); src/main/scala/com/raquo/laminar/inserters/InsertContext.scala (7 of 11 changes were fixes); src/main/scala/com/raquo/laminar/inserters/ChildrenInserter.scala (6 of 11 changes were fixes)
What to do
- Resolve the 9 Repeated repair finding(s) in Churn × Complexity Hotspots — start with NestedGroup.scala, InsertContext.scala, ChildrenInserter.scala. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with ChildrenCommandInserter.scala, DomTags.scala. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
1 deducted task-comment markers across 17760 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with InserterMoveSpec.scala. — One of this dimension's main actionable groups (1 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 7 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 3 build units (npm, 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)
12 finding(s): 0 critical, 9 high, 3 medium, 0 low. 8 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.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-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 8 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 (8 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. REDACTED was not scanned (REDACTED: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 67 of the 175 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: index.js↔siteConfig.js 50%; ProjectVersions.scala↔HtmlProps.scala 50%; HtmlProps.scala↔HtmlTags.scala 50%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with ProjectVersions.scala. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with index.js, HtmlProps.scala. — One of this dimension's main actionable groups (2 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. REDACTED was not scanned (REDACTED: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
Frontend & cross-cutting dimensions
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
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
- 80 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
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.
- Add a README to the 1 of 2 project(s) that lack one — worth up to 1 pts.
- Review the README against recent changes; refresh the parts that drifted.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1762 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 10 use(s) across 21,918 production line(s) (~0.5/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
- Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.
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
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 168 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 | 74% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 89% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 51% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 60% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 74% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 62% | Adequate | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 63 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 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 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — 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 — ~17208 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 — this repository commits no lockfile to resolve
- D14 License Compliance — sbt licences not graded — no production declaration in build.sbt carries a literal version
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, 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+ projects each declaring an entity of their own. 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# and Visual Basic comments only — this repository's production source is .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) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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
- D5 Coupling — Not applicable — this sbt build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 10 value object(s)
- 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
- M4 Documentation accuracy — Not applicable: the 7 current-state document(s) make no claim of a kind M4 checks. 2 claim(s) of kinds M4 does not check were not checked (path 2); M4 checks only links and versions.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JVM, JavaScript/TypeScript source (3 module(s), 174 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — 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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 168 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 was 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
- 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 Scala was read, and it logs through none that an interpolated message defeats: scala-logging takes an `s"…"` message apart into SLF4J's pattern and arguments at compile time, and log4s, grizzled-slf4j, Play's Logger, Akka's LoggingAdapter, sbt's Logger and Spark's Logging take one finished message (as log4net does in C#). Calls made straight through SLF4J (`org.slf4j.Logger`) 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 — 10 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: ProjectVersions.scala ↔ HtmlProps.scala project/project/ProjectVersions.scala:1
Serious — 30 finding(s)
- Repeated repair: src/main/scala/com/raquo/laminar/inserters/NestedGroup.scala src/main/scala/com/raquo/laminar/inserters/NestedGroup.scala:153
- Repeated repair: src/main/scala/com/raquo/laminar/inserters/InsertContext.scala src/main/scala/com/raquo/laminar/inserters/InsertContext.scala:253
- Repeated repair: src/main/scala/com/raquo/laminar/inserters/ChildrenInserter.scala src/main/scala/com/raquo/laminar/inserters/ChildrenInserter.scala:63
- Repeated repair: src/main/scala/com/raquo/laminar/inserters/ChildInserter.scala src/main/scala/com/raquo/laminar/inserters/ChildInserter.scala:13
- Repeated repair: src/main/scala/com/raquo/laminar/nodes/ReactiveElement.scala src/main/scala/com/raquo/laminar/nodes/ReactiveElement.scala:59
- Repeated repair: src/main/scala/com/raquo/laminar/nodes/ChildNode.scala src/main/scala/com/raquo/laminar/nodes/ChildNode.scala:93
- Repeated repair: src/main/scala/com/raquo/laminar/inserters/ChildTextInserter.scala src/main/scala/com/raquo/laminar/inserters/ChildTextInserter.scala:43
- Repeated repair: src/main/scala/com/raquo/laminar/domapi/DomTree.scala src/main/scala/com/raquo/laminar/domapi/DomTree.scala:176
- Repeated repair: src/main/scala/com/raquo/laminar/nodes/TextNode.scala src/main/scala/com/raquo/laminar/nodes/TextNode.scala:14
- REDACTED
- REDACTED
- REDACTED
- Hotspot: src/main/scala/com/raquo/laminar/inserters/ChildrenCommandInserter.scala src/main/scala/com/raquo/laminar/inserters/ChildrenCommandInserter.scala:55
- Hotspot: src/main/scala/com/raquo/laminar/domapi/DomTags.scala src/main/scala/com/raquo/laminar/domapi/DomTags.scala:252
- TooManyMethods: StyleProps src/main/scala/com/raquo/laminar/defs/styles/StyleProps.scala:16
- TooManyMethods: EventProcessor src/main/scala/com/raquo/laminar/keys/EventProcessor.scala:25
- Change coupling: index.js ↔ siteConfig.js website/pages/en/index.js:1
- Change coupling: HtmlProps.scala ↔ HtmlTags.scala src/main/scala/com/raquo/laminar/defs/props/HtmlProps.scala:1
- REDACTED
- REDACTED
- ChildrenCommandInserter.updateList (cyclomatic 21) src/main/scala/com/raquo/laminar/inserters/ChildrenCommandInserter.scala:55
- TodoComment src/test/scala/com/raquo/laminar/tests/InserterMoveSpec.scala:1095
- ChildrenCommandInserter.updateList (cognitive 30) src/main/scala/com/raquo/laminar/inserters/ChildrenCommandInserter.scala:55
- ChildrenInserter.updateChildren (cognitive 27) src/main/scala/com/raquo/laminar/inserters/ChildrenInserter.scala:63
- MethodTooLong: Index.render website/pages/en/index.js:77
- REDACTED
- Duplicated block (18–25 lines × 2) src/main/scala/com/raquo/laminar/inserters/ChildTextInserter.scala:19
- Low cohesion: Seq (LCOM4 4) src/main/scala/com/raquo/laminar/Seq.scala:31
- README may be stale
- JavaScript dependencies are not locked
Minor — 12 finding(s)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- No release approval gate
- Scala's null is not held to the type system everywhere
Minor — 1 finding(s)
- Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (no committed lockfile, so no resolved version to grade)
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-83b3f665a620470984accbc516650024/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/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-83b3f665a620470984accbc516650024/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/watchdog-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 . | 12 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |